Messages in this thread |  | | Date | Wed, 13 Sep 2000 09:14:06 -0400 | From | "Eloy A. Paris" <> | Subject | kernel BUG at ll_rw_blk.c:711! |
| |
Hi!
I got an Oops with 2.4.0test8. The message written to syslog said:
Sep 13 02:51:49 antenas kernel: kernel BUG at ll_rw_blk.c:711!
This machine has 128MBytes of memory and at the time of the Opps I was running Netscape and a big find was running in the background as well (Debian's daily maintenance script). The machine was pretty irresponsive (as everytime this daily maintenance script runs).
I have been running -test8 (and all the different -testxx releases) with no problems at all. This is the first time I get an Oops. After the Opps I was able to continue to use the machine but after a little bit I had to cycle power because all processes that had to access the disk where hanging in the D state.
I don't think I can reproduce this...
Decoded oops is attached.
Cheers,
Eloy.-
P.S. I am not subscribed to linux-kernel.
ksymoops 2.3.4 on i686 2.4.0-test8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test8/ (default) -m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.
invalid operand: 0000 CPU: 0 EIP: 0010:[<c014f9dd>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010282 eax: 0000001f ebx: c7db9f20 ecx: c7580b40 edx: 00000008 esi: c7db9f20 edi: c02303c0 ebp: 00000001 esp: c4639ea8 ds: 0018 es: 0018 ss: 0018 Process communicator-sm (pid: 445, stackpage=c4639000) Stack: c01bc6c5 c01bc962 000002c7 c7db9f20 00000001 0000000c 00000000 001e8480 c02303d8 c02303d0 00000000 00000002 00000000 00000000 c014f422 000000fe c014ffe1 c02303c0 00000001 c7db9f20 c7db9f20 00000000 00000001 c4639f38 Call Trace: [<c01bc6c5>] [<c01bc962>] [<c014f422>] [<c014ffe1>] [<c0150141>] [<c0120ef5>] [<c0120f94>] [<c0120fe5>] [<c0120ebc>] [<c0144c1b>] [<c012a4fb>] [<c012b351>] [<c010a2df>] Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 c0 4b 22 c0
>>EIP; c014f9dd <__make_request+a1/5a4> <===== Trace; c01bc6c5 <tvecs+a0dd/ba78> Trace; c01bc962 <tvecs+a37a/ba78> Trace; c014f422 <blk_get_queue+32/40> Trace; c014ffe1 <generic_make_request+101/110> Trace; c0150141 <ll_rw_block+151/1c0> Trace; c0120ef5 <writeout_one_page+39/50> Trace; c0120f94 <do_buffer_fdatasync+48/7c> Trace; c0120fe5 <generic_buffer_fdatasync+1d/38> Trace; c0120ebc <writeout_one_page+0/50> Trace; c0144c1b <ext2_sync_file+2f/a4> Trace; c012a4fb <sys_write+8b/a0> Trace; c012b351 <sys_fsync+49/68> Trace; c010a2df <system_call+33/38> Code; c014f9dd <__make_request+a1/5a4> 00000000 <_EIP>: Code; c014f9dd <__make_request+a1/5a4> <===== 0: 0f 0b ud2a <===== Code; c014f9df <__make_request+a3/5a4> 2: 83 c4 0c add $0xc,%esp Code; c014f9e2 <__make_request+a6/5a4> 5: 0f b6 46 15 movzbl 0x15(%esi),%eax Code; c014f9e6 <__make_request+aa/5a4> 9: 0f b7 4e 14 movzwl 0x14(%esi),%ecx Code; c014f9ea <__make_request+ae/5a4> d: 8b 14 85 c0 4b 22 c0 mov 0xc0224bc0(,%eax,4),%edx
1 warning issued. Results may not be reliable.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |