On Thu, 17 Mar 2005, HARDY, Steven wrote: > Hello, > > I am currently experiencing problems getting a 2.6.x system working on a > Radisys 6315 PMC Processor board. This board has a Raisys 82600 chip > interfacing to an EZ-USB device onboard. > > The system has been tested with the following kernels : > OK - 2.4.17, 2.4.29 > FAILS - 2.6.5, 2.6.9, 2.6.11, 2.6.11-bk6 > > The failure behavior is somewhat strange - there are two USB ports on each > card, and the fault *only* occurrs when only a single port is in use. On > the cards where two devices are connected, everything seems to work OK. > > The fault occurs immediately after the "fxload" program is called to load > the hex file onto the EZ-USB device. This causes all of the devices to get > disconnected and re-enumerated, at which point a large number of spurious > uhci_hcd interrupts are generated (~150000 on average), and all of the > devices fail to accept their descriptors. > > I am aware that this could easily be a hardware quirk/issue, but having > successfully used the hardware with 2.4.x, it is neccesary for me to find a > workaround that will allow the hardware to work with the new USB subsystem > in 2.6.x > > Below I have attached kmsg output (verbose USB debugging enabled), > before/after proc/interrupts, and a lspci output. > > If anyone could provide any suggestions, it would be much appreciated.
> bash-2.05b# cat /proc/kmsg > <4>Linux version 2.6.5 ([EMAIL PROTECTED]) (gcc version 3.3.3 20040412 (Red > Hat > Linux 3.3.3-7)) #1 Wed Mar 16 13:39:37 GMT > 2005 It would be better if you used 2.6.11. > <7>uhci_hcd 0000:00:00.2: port 2 portsc 0099 > <7>uhci_hcd 0000:00:00.2: port 2 portsc 0099 > <7>uhci_hcd 0000:00:00.2: port 2 portsc 0099 > <7>uhci_hcd 0000:00:00.2: port 2 portsc 0099 > <7>hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101 > <6>usb 1-2: new full speed USB device using address 2 > <7>usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0 > <7>drivers/usb/core/usb.c: usb_hotplug > <7>usb 1-2: registering 1-2:1.0 (config #1, interface 0) > <7>drivers/usb/core/usb.c: usb_hotplug > <6>drivers/usb/core/usb.c: registered new driver usbdevicedriver > <6>/home/user/usb_device_driver/usbdevicedriver.c: v0.1 Astrium Limited > <6>/home/user/usb_device_driver/usbdevicedriver.c: USB Driver > <6>e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex > <7>uhci_hcd 0000:00:00.2: port 2 portsc 0182 > <7>hub 1-0:1.0: port 2, status 300, change 1, 1.5 Mb/s > <6>usb 1-2: USB disconnect, address 2 > <7>usb 1-2: usb_disable_device nuking all URBs > <7>usb 1-2: unregistering interface 1-2:1.0 > <7>drivers/usb/core/usb.c: usb_hotplug > <7>usb 1-2: unregistering device > <7>drivers/usb/core/usb.c: usb_hotplug > <7>uhci_hcd 0000:00:00.2: suspend_hc Presumably that was your device connecting on port 1 and receiving its firmware update. > <7>uhci_hcd 0000:00:00.2: wakeup_hc > <7>uhci_hcd 0000:00:00.2: port 1 portsc 10c3 This indicates that port 1 was suspended! That shouldn't have happened. > <7>hub 1-0:1.0: port 1, status 101, change 1, 12 Mb/s > <7>uhci_hcd 0000:00:00.2: port 1 portsc 0182 > <7>hub 1-0:1.0: debounce: port 1: delay 400ms stable 0 status 0x300 > <3>hub 1-0:1.0: connect-debounce failed, port 1 disabled > <7>uhci_hcd 0000:00:00.2: port 2 portsc 1093 And this shows that port 2 was suspended! While it's not clear what's going on, this could be related to your problem. 2.6.11 should handle such things better. Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
