[PlanetCCRMA] weird kernel error

Fernando Pablo Lopez-Lezcano nando@ccrma.Stanford.EDU
Sun Dec 8 15:56:01 2002


> I just plugged my Z into my new RH7.3 setup (with the usbdnet patch on
> the 2.4.19-2.ll.acpi kernel).
> 
> I had a shell open with /var/log/messages in it, to see the what
> happened when I plugged it in, and below is what I noticed after a few
> minutes.  I had to run the hotplug script by hand, but the connection
> works fine, VNC came right up, and everything looks good.  But I never
> saw anything like this error with the 2.4.18 kernel.  Anybody else seen
> this, or know what it means?
> 
> At first I thought it was the usb stuff because of the bottom, but
> there's an apt-get refernce buried in there.  What's up?
> 
> Dec  7 22:06:04 rama /etc/hotplug/usb.agent: Setup usbdnet acm for USB
> product 4dd/8004/0
> Dec  7 22:07:39 rama kernel: ip_tables: (C) 2000-2002 Netfilter core
> team
> Dec  7 22:07:40 rama kernel: ip_conntrack version 2.1 (2047 buckets,
> 16376 max) - 292 bytes per conntrack
> Dec  7 22:10:45 rama kernel: kernel BUG at page_alloc.c:231!
> Dec  7 22:10:45 rama kernel: invalid operand: 0000
> Dec  7 22:10:45 rama kernel: CPU:    0
> Dec  7 22:10:45 rama kernel: EIP:    0010:[<c0133004>]    Not tainted
> Dec  7 22:10:45 rama kernel: EFLAGS: 00010202
> Dec  7 22:10:45 rama kernel: eax: 00000040   ebx: c10dd7e0   ecx:
> 00001000   edx: 000049d4
> Dec  7 22:10:45 rama kernel: esi: c022e0b4   edi: 00000001   ebp:
> 00000000   esp: c4339e58
> Dec  7 22:10:45 rama kernel: ds: 0018   es: 0018   ss: 0018
> Dec  7 22:10:45 rama kernel: Process apt-get (pid: 19018,
> stackpage=c4339000)
> Dec  7 22:10:45 rama kernel: Stack: 00001000 c4338000 000039d4 00000292
> 00000000 c022e0b4 c022e240 000001ff 
> Dec  7 22:10:45 rama kernel:        00000000 0000016c c013329f c022e0b4
> c022e23c 000001d2 c10989c0 c4338000 
> Dec  7 22:10:45 rama kernel:        00000000 c532e730 0000016c c012b58a
> cff4f0c8 c733edc0 0000001b 00000151 
> Dec  7 22:10:45 rama kernel: Call Trace:    [<c013329f>] [<c012b58a>]
> [<c012bcc5>] [<c012bf1b>] [<c011555b>]
> Dec  7 22:10:45 rama kernel:   [<c012c4ea>] [<c012c380>] [<c0139fd5>]
> [<c0149f78>] [<c011d67b>] [<c0108a7b>]
> Dec  7 22:10:45 rama kernel: 
> Dec  7 22:10:45 rama kernel: Code: 0f 0b e7 00 ba f7 20 c0 8b 43 18 a9
> 80 00 00 00 74 08 0f 0b 
> Dec  7 22:12:33 rama kernel:  <3>usb-uhci.c: process_transfer: fixed
> toggle
> Dec  7 22:12:33 rama kernel: usb-uhci.c: process_transfer: fixed toggle
> Dec  7 22:33:16 rama last message repeated 242 times

This is, as the log says, a kernel BUG :-) Something went very wrong
with the operation of a kernel module and you got a stack dump in the
logs. After something like this happens I would not trust the kernel too
much until you reboot, it depends on what module failed. You can try to
decode it by copying and pasting all the messages from the log (related
to the bug) and supplying that to ksymoops, which will transform most of
the numbers into names of functions within the kernel. With that you can
have an idea of where in the kernel the problem happened. 

-- Fernando