On Mon, 9 Jul 2012, Manuel Lauss wrote: > Hello, > > Current 3.5-rc5-git panics on my MIPS targets during USB host > controller initialization. > Disabling CONFIG_PRINTK fixes it. > > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > au1xxx-ehci au1xxx-ehci.0: Au1xxx EHCI > au1xxx-ehci au1xxx-ehci.0: new USB bus registered, assigned bus number 1 > au1xxx-ehci au1xxx-ehci.0: irq 98, io mem 0x14020000 > Unhandled kernel unaligned access[#1]: > Cpu 0 > $ 0 : 00000000 10003c00 00000000 b4696540 > $ 4 : 80776278 00000000 74696540 00000000 > $ 8 : 10003c00 1000001e 00000000 00000000 > $12 : 807d12d8 807d123c 3b9aca00 00000000 > $16 : 74696540 74696475 80776278 00000028 > $20 : 80830000 00000000 00000000 00000000 > $24 : 00000000 801444b0 > $28 : 80776000 807761b0 00030000 80104f60 > Hi : 00000000 > Lo : 00000000 > epc : 8010c948 do_page_fault+0x68/0x350 > kra : 80104f60 ret_from_exception+0x0/0x18 > Status: 10003c02 KERNEL EXL > Cause : 80808410 > BadVA : 7469653d > PrId : 800c8000 (Au1300) > Process (pid: 0, threadinfo=80776000, task=8084ebe4, tls=00000020) > Stack : 45524f4e 53455551 00000054 5f515249 48544f4e 44414552 00000000 5f515249 > 55414f4e 00030001 00000000 53515249 5455415f 5445444f 00544345 53515249 > 5045525f 0059414c 53515249 4941575f 474e4954 00000000 53515249 4e45505f > 474e4944 00000000 6d6f682f 616d2f65 642f6f6e 30323162 656b2f30 6c656e72 > 6e696c2f 6b2f7875 656e7265 72692f6c 61682f71 656c646e 0000632e 20717269 > ... > Call Trace: > [<8010c948>] do_page_fault+0x68/0x350 > > > Code: 00809021 00a0b021 00c08021 <14400093> 8e3500c8 8f830014 > 3c02efff 3442ffff 00621024 > > 8/wÇ > ÿ'wÇ╚( ... This looks like a pretty difficult sort of problem to track down. Still, since the problem occurs in printk rather than in the USB subsystem, maybe you should send the bug report to the people who recently modified the printk code. Can you bisect to find an individual commit where the problem started? Alan Stern -- 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
