Re: Kernel panic with PCI EHCI on AMCC Sequoia

On Tuesday 21 August 2007, Mike Nuss wrote:
> I haven't done any testing to track this down. I'm using the Denx 2.6.22
> kernel with the on-chip setup fix on a PPC440EPx.
> 
> I have both the onboard controller and a PCI controller running, with
> ehci-hcd loaded as a module. The onboard controller seems to be working
> fine, and if I plug in a USB mass-storage key to the PCI controller,
> that seems to work fine as well. But if I plug in a high-speed hub to
> the PCI controller, I get an immediate kernel panic:
> 
> Oops: kernel access of bad area, sig: 11 [#1]
> NIP: d106752c LR: d106786c CTR: 00000008
> REGS: c028bcf0 TRAP: 0300   Not tainted  (2.6.22-ts-1-ppc)
> MSR: 00021000 <ME>  CR: 28d12524  XER: 00000000
> DAR: 0101000e, DSISR: 00000000
> TASK = c026d9d0[0] 'swapper' THREAD: c028a000
> GPR00: ff105104 c028bda0 c026d9d0 00000000 c0270de8 00000058 00000058
> 00012102 
> GPR08: ff105104 00000000 00000000 ff105100 ffffffb5 00000000 0ffb3100
> cf7f595c 
> GPR16: 0000004d 0000026f 00000800 ffffffb9 000003fc 00000008 ff1073fc
> 000007ff 
> GPR24: cf3323fc cf7f5800 00000000 00000000 ff105100 01010000 cf7f58b8
> 00000000 
> NIP [d106752c] ehci_work+0x6a8/0x814 [ehci_hcd]
> LR [d106786c] ehci_watchdog+0x98/0xd4 [ehci_hcd]
> Call Trace:
> [c028bda0] [d1067028] ehci_work+0x1a4/0x814 [ehci_hcd] (unreliable)
> [c028bdf0] [d106786c] ehci_watchdog+0x98/0xd4 [ehci_hcd]
> [c028be00] [c00228bc] run_timer_softirq+0xe4/0x198
> [c028be40] [c001e4d0] __do_softirq+0x78/0xe4
> [c028be70] [c0006534] do_softirq+0x54/0x58
> [c028be80] [c001e228] irq_exit+0x48/0x58
> [c028be90] [c0003464] timer_interrupt+0xa0/0x224
> [c028bed0] [c00020bc] ret_from_except+0x0/0x18
> [c028bf90] [c00092f4] cpu_idle+0xc0/0xd0
> [c028bfb0] [c01fc9a8] rest_init+0x58/0x68
> [c028bfc0] [c028c720] start_kernel+0x220/0x29c
> [c028bff0] [c0000200] skpinv+0x1a8/0x1e4
> Instruction dump:
> 4bfffb8c 39200006 4bffff94 801e00b4 7d3a4b78 74090800 57492036 7ca64a14 
> 7c0a4214 41820050 7cea402e 906b0004 <a01d000e> 893d0038 74e47000
> 7c090050 
> Kernel panic - not syncing: Aiee, killing interrupt handler!
> Rebooting in 180 seconds..
> 
> Any ideas?

Is this a case where one controller uses one byteorder and
the other uses a different one?


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel