On Fri, 11 Feb 2000, Andrea Arcangeli wrote:
> On Fri, 11 Feb 2000, Manfred Spraul wrote:
>
> >He wrote that the process is stuck in __wait_on_buffer(), I'm not sure
> >if the semaphore deadlock detector will detect this.
>
> Sorry I didn't know. Thus new debugging way is suggested: enable kdb
> instead, press PAUSE and `btp xxx` where xxx is the pid of the deadlocked
> task.
>
I now have recompiled with gcc 2.7.2 to be safe and I am still getting
a process stuck in D state; this time it is a simple /bin/cp command.
Details follow:
# version
Linux version 2.2.14aa7 (root@vmebox) (gcc version 2.7.2.3) #5 Mon Feb 21
10:26:58 EST 2000
# ps ax
.
.
135 tty1 S 0:00 -bash
136 tty1 D 0:08 cp tmpfile tmpfile2
138 ? S 0:00 in.rlogind
139 ttyp0 S 0:00 -bash
182 ttyp0 R 0:00 ps ax
------------
Using ikd:
Entering kdb due to Keyboard Entry
kdb> btp 136
EBP EIP Function(args)
0xc6ad3e40 0xc0112a58 schedule+0x150( )
0xc6ad3e60 0xc012825e __wait_on_buffer+0x92( 0xc54d6c00)
0xc6ad3e70 0xc012922c bread+0x50( 0x806, 0x59cd9, 0x400)
0xc6ad3ea4 0xc01413e5 ext2_bmap+0x181( 0xc6933ba0, 0x47b0c)
0xc6ad3ee4 0xc012a041 generic_readpage+0x59( 0xc6b82720, 0xc039b380)
0xc6ad3f08 0xc011ee5b try_to_read_ahead+0xff( 0xc6b82720, 0x11ec3000,
0xc5db0000)
0xc6ad3f54 0xc011f21b do_generic_file_read+0x2c7( 0xc6b82720, 0xc6b82734,
0xc6ad3f7c, 0xc011f508)
0xc6ad3f8c 0xc011f5e1 generic_file_read+0x5d( 0xc6b82720, 0xbfffe610,
0x1000, 0xc6b82734)
0xc6ad3fbc 0xc01274b8 sys_read+0xbc( 0x3, 0xbfffe610, 0x1000, 0x1000,
0xbfffe610)
0xbffff694 0xc0108c1c system_call
kdb> go
-------------
Any ideas?
Wm
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:28 EST