Oops on booting 2.4.4
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines
May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, stackpage=c7845000) May 23 02:46:24 localhost kernel: Stack: c12607e0 00000400 00000400 c73aa000 c122a060 c122a05c c122a058 c88fbb20 May 23 02:46:24 localhost kernel: 000003f1 000003f1 c014ab80 c73aa3f1 c7845f9c 00000000 00000400 ffffffea May 23 02:46:24 localhost kernel: c7f43f60 00000400 bffff4b8 c7f2e220 c12607e0 00000000 00000000 c73aa000 May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>] [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>] [<c014ab80>]
Quoted 1 line
[<
c012e83e>] [<c0106aeb>]
A module deregistered incorrectly, or has a race between post-load activities and unload. One way or another it left a dangling proc entry.
The oops does not provide off-stack information, so it's impossible to tell what particular modules is the culprit.
Quoted 4 lines
May 23 02:46:24 localhost kernel: hub.c: USB new device connect on bus1/2, assigned device number 2 May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod0x4a9/0x2204) is not claimed by any active driver.
What is this thing you have on USB? Try to run without it.
-- Pete
Quoted 20 lines · Pete Zaitcev
Quoted 11 lines
May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, stackpage=c7845000) May 23 02:46:24 localhost kernel: Stack: c12607e0 00000400 00000400 c73aa000 c122a060 c122a05c c122a058 c88fbb20 May 23 02:46:24 localhost kernel: 000003f1 000003f1 c014ab80 c73aa3f1 c7845f9c 00000000 00000400 ffffffea May 23 02:46:24 localhost kernel: c7f43f60 00000400 bffff4b8 c7f2e220 c12607e0 00000000 00000000 c73aa000 May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>] [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>] [<c014ab80>]Quoted 1 line
[<
c012e83e>] [<c0106aeb>]A module deregistered incorrectly, or has a race between post-load activities and unload. One way or another it left a dangling proc entry.
The oops does not provide off-stack information, so it's impossible to tell what particular modules is the culprit.
Quoted 8 lines
Quoted 4 lines
May 23 02:46:24 localhost kernel: hub.c: USB new device connect on bus1/2, assigned device number 2 May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod0x4a9/0x2204) is not claimed by any active driver.
What is this thing you have on USB? Try to run without it.
-- Pete
It's a canon usb scanner.
running with or without it does not make any difference.
kind regards,
Harm