Kristofer T. Karas wrote: > I sent a bug report some time ago to linux-kernel about the EHCI-HCD > driver triggering an instant reboot. Greg KH suggested I post something > here. Then I got side-tracked; well, finally...
I remember replying to your post, suggesting that you try a few things first ... like enabling slab poisoning (see if that changes the failure mode), and if you still get that "instant reboot" failure mode, running with KDB to get more information (like a stack backtrace). I'll repeat that advice here ... you're not yet providing usable info about your failure mode, unfortunately! Some websearching found a mention (http://www.amd3d.com/review/sl75drv4/) that sometimes your board would lock up. It's possible you've got some hardware issues, fixed later (the DRV4 also fixed "it's not purple" :). > Since I gather other people have had good success with EHCI-HCD and the > NEC controller chip, I'm wondering if the driver is interacting with the > Hint PCI bridge in some odd fashion (else shared IRQs). I'd certainly hope that extra PCI bridges don't matter, but I could understand how they might. Do try this board without involving that PCI-to-PCI bridge. Seems like your VIA-KT266A based mobo has enough spare slots to do that, and EHCI will certainly be driving that bridge a lot harder than OHCI could; it can even saturate some poorly tuned PCI busses. Given the various problems VIA has had with PCI, adding an extra bridge and non-light PCI usage might easily unearth some trouble. I've seen "ehci-hcd" share interrupts quite happily with other USB host controller drivers, and wouldn't initially suspect that sharing as being a problem. But you might want to verify that this happens with _only_ EHCI using that IRQ, not going through the bridge. Otherwise I'd suspect your hardware. > Attached are some files from /proc describing the hardware found, as > well as an excert from syslog with usb-storage verbose-debug enabled > (right up to the moment of instant-reboot). It'd have been more useful if you included /proc/interrupts with the EHCI driver loaded, but I'll guess that it's just another IRQ-11 user (based on /proc/pci) and that it's actually behaving (else you'd not have gotten any responses at all) until this reboot. Also, in general with USB problem reports, include /proc/bus/usb/devices output (as it says in the FAQ :). I'm deducing that yours will show three UHCI buses (root hubs), two OHCI ones, and one EHCI ... with an HP DeskJet on one OHCI bus, and a Maxtor disk connected to the EHCI one. Again, see if this happens without any other USB devices. - Dave ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
