Re: OHCI root_port_reset() deadly loop...
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
> To add some more information here, I think the EHCI idea might > hold some water. > > What I have here are two NEC OHCI USB interfaces and one NEC EHCI > USB interface on PCI. Aparently they all go through a shared > USB hub, mapped like this: > > HUB Port 1: OHCI #1, EHCI > HUB Port 2: OHCI #2, EHCI > HUB Port 3: OHCI #1, EHCI > HUB Port 4: OHCI #2, EHCI > HUB Port 5: OHCI #1, EHCI > > The OHCI ports go out to external USB connectors on the back panel of > the machine, whereas the EHCI is connected up to an internal USB > storage CDROM device and what appears to be another USB hub. There's actually no such thing as an "EHCI port" or an "OHCI port". Instead, there's a set of ports, each of which can be switched so the USB differential data signals go up to either controller. When EHCI starts, that switch points to EHCI so that devices can try enumerating with high speed signaling. When a device doesn't respond to that "chirp", the EHCI root hub driver switches the port to the companion controller. (Which is OHCI here, UHCI on some PCs, etc.) > The problem seems to be very strongly tied to timing. For example > simply adding "ignore_loglevel" to the kernel boot command line can > make the problem go away. > > This got me thinking about your EHCI comment. > > If these controllers are going through the same HUB, things might go > south if OHCI initialized first, then khubd et al. are asynchronously > accessing the segments behind OHCI at the same time that the EHCI > driver is initializing. Perhaps, this is the kind of sequence of > events which makes one of the root ports reset in such a way that the > the reset bit never clears. > > Given that this machine has 64 cpus, the likelyhood for such parallel > accesses is very likely :-) > > Does this make any sense? Yes, that's why I asked about EHCI. My speculation would be that OHCI starts the reset, and EHCI claims the port before it completes; or contrariwise OHCI starts the reset right after EHCI claims it. And there's some point in that process where a hardware race makes the trouble you've observed. I believe there are plenty of other places where it's perfectly fine if EHCI grabs the port, or this little race would have shown up many times before. - Dave ------------------------------------------------------------------------- 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/ _______________________________________________ Linux-usb-users@xxxxxxxxxxxxxxxxxxxxx To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux USB] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Photo] [Yosemite News] [Yosemite Photos] [Video Projectors] [PDAs] [Free Online Dating] [Hacking TiVo] [Linux Kernel] [Linux SCSI] [XFree86] [Devices] [Big List of Linux Books] [16.7MP]