On Tue, 30 Jun 2009 10:25:47 -0400 (EDT) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 29 Jun 2009, Andrew Morton wrote: > > > On Thu, 18 Jun 2009 12:44:49 GMT > > bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=13564 > > > > > > Summary: random general protection fault at boot time caused by > > > khubd. > > > > I firt saw this in the kernel 2.6.30-8 from Ubuntu Karmic. > > > Afer that I have upgraded to 2.6.30-9 which has caused same problem. > > > Now I wanted to try vanila git kernel with radeon KMS so I compiled my own > > > kernel from git. Today I saw it first time also with this kernel. > > > > > > What happens: > > > 1. I make cold boot or restart > > > 2. Computer boots normaly except all USB ports are dead > > > 3. dmesg shows general protection error caused by khubd > > > > > > This problem doen't happen even nearly every boot. I would give around 20% > > > chance for khubd failure without collecting statistics. > > > > > > > This is a regression in 2.6.30.8. However we are not told which kernel > > version we regresed against. Which is the latest kernel which was > > known to work OK? > > > > The bad bit is: > > > > > > : [ 1.604937] Write protecting the kernel read-only data: 1732k > > : [ 1.672060] Clocksource tsc unstable (delta = 736134769 ns) > > : [ 1.704695] usb 3-1: new low speed USB device using uhci_hcd and address 2 > > : [ 1.858154] general protection fault: 0000 [#1] SMP > > : [ 1.858277] last sysfs file: > > : [ 1.858318] Modules linked in: > > : [ 1.858393] > > : [ 1.858435] Pid: 231, comm: khubd Not tainted (2.6.30-9-generic #10kms5-Ubuntu) Aspire 1350 > > : [ 1.858485] EIP: 0060:[<c053595b>] EFLAGS: 00010202 CPU: 0 > > : [ 1.858541] EIP is at schedule_timeout+0x12b/0x1b0 > > : [ 1.858585] EAX: 000004e0 EBX: 000004e0 ECX: c07eed54 EDX: b48c4368 > > : [ 1.858631] ESI: df97fd14 EDI: c07ee440 EBP: df97fd54 ESP: df97fd00 > > : [ 1.858677] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 > > : [ 1.858723] Process khubd (pid: 231, ti=df97e000 task=df973e30 task.ti=df97e000) > > : [ 1.858771] Stack: > > : [ 1.858809] de118b60 1c800000 fffedcd6 000004e2 00000296 00000000 00200200 fffee1b8 > > : [ 1.859102] c0144100 df973e30 c07ee440 c05356d2 6275686b 64640064 00000000 00000000 > > : [ 1.859462] 000000e7 b48c4368 df97fda4 000004e2 df97fda8 df97fd8c c05356d2 df97fdb0 > > : [ 1.859857] Call Trace: > > : [ 1.859898] [<c0144100>] ? process_timeout+0x0/0x10 > > : [ 1.859985] [<c05356d2>] ? wait_for_common+0xa2/0x120 > > : [ 1.860029] [<c05356d2>] ? wait_for_common+0xa2/0x120 > > : [ 1.860029] [<c0131260>] ? default_wake_function+0x0/0x10 > > : [ 1.860029] [<c05357cd>] ? wait_for_completion_timeout+0xd/0x10 > > : [ 1.860029] [<c03da8c9>] ? usb_start_wait_urb+0x99/0xb0 > > This looks like a bug in schedule_timeout, to judge by the EIP value. > Which would make it a core kernel issue, unrelated to USB. > That sounds pretty unlikely. The oops is a bit odd though - maybe some interrupt went off and scribbled on the stack? Or some DMA operation? Also there is: > 2. Computer boots normaly except all USB ports are dead -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
