Messages in this thread | | | Subject | kernel BUG at ll_rw_blk.c:711 | Date | Sun, 01 Oct 2000 01:08:49 -0200 | From | Christoph Simon <> |
| |
This is the first time in a long time I'm experiencing problems with the Linux kernel. A wonderful job. The backside is that it's also a very long time ago since the last time I read (parts of) the kernel.
One of my users complained of netscape hanging frequently while reading news. I tried to find out what was happening and found netscape in the ``uninterruptible sleep' state. When checking dmesg I found this message:
------------------------------------------------------------------------------- kernel BUG at ll_rw_blk.c:711! invalid operand: 0000 CPU: 0 EIP: 0010:[<c016857a>] EFLAGS: 00210282 eax: 0000001f ebx: c15853c0 ecx: c1377180 edx: ffffffff esi: c15853c0 edi: c02b9760 ebp: 00000001 esp: c39a3ea8 ds: 0018 es: 0018 ss: 0018 Process communicator-sm (pid: 1415, stackpage=c39a3000) Stack: c0207405 c02076a2 000002c7 c15853c0 00000001 0000000c 00000000 c135fd54 c02b9778 c02b9770 00000000 00000008 00000000 00000000 c0167f22 000000fe c0168b81 c02b9760 00000001 c15853c0 c15853c0 00000000 00000001 c39a3f38 Call Trace: [<c0207405>] [<c02076a2>] [<c0167f22>] [<c0168b81>] [<c0168ce1>] [<c01221c5>] [<c0122268>] [<c01222bd>] [<c0122190>] [<c0148aff>] [<c012bb8b>] [<c012ca99>] [<c010a4cf>] Code: 0f 0b 83 c4 0c 90 0f b6 46 15 0f b7 4e 14 8b 14 85 e0 dc 2a -------------------------------------------------------------------------------
Well, if the kernel says it's a bug, it'll be a bug, right? But I really don't know what to do with this. I checked out that line and got the message that this is something for 2.5. The kernel is 2.4.0pre8 using APIC on a mono CPU, compiled with gcc 2.95.2, debian/woody box (Athlon CPU, Biostar motherboard, VIA chipset).
I wonder if there is anything I can do in this situation beside switching off APIC and waiting for 2.5.0. The bad thing is, that after this has happened, sync, shutdown (and some other programs?) also fall asleep, forcing me to powercycle the computer. I can't really tell how to reproduce the problem, but as it is popping up quite frequently, a more knowledable writer on this list might be able to tell me how to prepare such an event to make it reproducible. In both cases, please CC to me, as I'm not on this list.
TIA Christoph
- 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/
| |