On Feb 03 2004, Alan Stern wrote:
> I just came across some new information that might be relevant for your
> problem. Do you remember if your desktop system uses a USB controller by
> VIA? If it does, that would explain a lot.
(...)
Hi, Alan.
Here I am again. And concerning your question, here are the relevant
lines from the output of lspci from my Desktop (which indeed has a VIA
Southbridge):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:04.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 10)
00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:04.3 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Just out of curiosity, maybe you can try this patch and see what shows
> up in the debugging log. It enlarges the size of the packets the
> system asks for; maybe that will prevent the controller from shutting
> down.
Ok, after I read your reply, I understood what the patch made. Sorry for
the stupid question that I sent you earlier. I had understood that my
system was requesting packets larger than the internal hub could handle,
not the other way round (like per your second explanation).
Anyway, here follows the logs with some slight comments interspersed.
The USB Drive worked fine with this new patch, after both cold and warm
reboots. The system also identified the drive correctly after unplugging
and replugging it.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(...) Loading uhci-hcd
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
(...)
hub 1-0:1.0: port 1 power on: 0
hub 1-0:1.0: port 2 power on: 0
PCI: Found IRQ 9 for device 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:0d.0
uhci_hcd 0000:00:04.3: UHCI Host Controller
uhci_hcd 0000:00:04.3: irq 9, io base 0000d000
uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci_hcd 0000:00:04.3: root hub device address 1
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
drivers/usb/core/message.c: USB device number 1 default language ID 0x409
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.1-7 uhci_hcd
usb usb2: SerialNumber: 0000:00:04.3
drivers/usb/core/usb.c: usb_hotplug
usb usb2: registering 2-0:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-0:1.0: usb_probe_interface
hub 2-0:1.0: usb_probe_interface - got id
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hub 2-0:1.0: standalone hub
hub 2-0:1.0: ganged power switching
hub 2-0:1.0: global over-current protection
hub 2-0:1.0: Port indicators are not supported
hub 2-0:1.0: power on to power good time: 2ms
hub 2-0:1.0: hub controller current requirement: 0mA
hub 2-0:1.0: local power source is good
hub 2-0:1.0: no over-current condition exists
hub 2-0:1.0: enabling power on all ports
hub 2-0:1.0: port 1 power on: 0
hub 2-0:1.0: port 2 power on: 0
hub 1-0:1.0: initial port 1 status: ret = 0
hub 1-0:1.0: port 1, status 300, change 3, 1.5 Mb/s
hub 1-0:1.0: clear C_CONNECTION1 = 0
hub 1-0:1.0: initial port 2 status: ret = 0
hub 1-0:1.0: port 2, status 300, change 3, 1.5 Mb/s
hub 1-0:1.0: clear C_CONNECTION1 = 0
hub 2-0:1.0: initial port 1 status: ret = 0
hub 2-0:1.0: port 1, status 300, change 3, 1.5 Mb/s
hub 2-0:1.0: clear C_CONNECTION1 = 0
hub 2-0:1.0: initial port 2 status: ret = 0
hub 2-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 2-0:1.0: clear C_CONNECTION1 = 0
hub 2-0:1.0: port_status= 0, port 2 status 101 change 2
hub 2-0:1.0: port_status= 0, port 2 status 101 change 2
hub 2-0:1.0: port_status= 0, port 2 status 101 change 2
hub 2-0:1.0: port_status= 0, port 2 status 101 change 2
hub 2-0:1.0: port_status= 0, port 2 status 101 change 2
hub 2-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 2-0:1.0: port reset = 0
hub 2-0:1.0: wait_reset 0, port 2, status 103, change 0
hub 2-0:1.0: new USB device on port 2, assigned address 2
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 2-2: Product: Generic USB Hub
usb 2-2: Manufacturer: ALCOR
drivers/usb/core/usb.c: usb_hotplug
usb 2-2: registering 2-2:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-2:1.0: usb_probe_interface
hub 2-2:1.0: usb_probe_interface - got id
hub 2-2:1.0: USB hub found
hub 2-2:1.0: 4 ports detected
hub 2-2:1.0: standalone hub
hub 2-2:1.0: ganged power switching
hub 2-2:1.0: global over-current protection
hub 2-2:1.0: Port indicators are not supported
hub 2-2:1.0: power on to power good time: 44ms
hub 2-2:1.0: hub controller current requirement: 100mA
hub 2-2:1.0: local power source is good
hub 2-2:1.0: no over-current condition exists
hub 2-2:1.0: enabling power on all ports
hub 2-2:1.0: port 1 power on: 0
hub 2-2:1.0: port 2 power on: 0
hub 2-2:1.0: port 3 power on: 0
hub 2-2:1.0: port 4 power on: 0
hub 2-0:1.0: initial port 1 status: ret = 0
hub 2-0:1.0: port 1 enable change, status 300
hub 2-0:1.0: initial port 2 status: ret = 0
hub 1-0:1.0: initial port 1 status: ret = 0
hub 1-0:1.0: port 1 enable change, status 300
hub 1-0:1.0: initial port 2 status: ret = 0
hub 1-0:1.0: port 2 enable change, status 300
drivers/usb/host/uhci-hcd.c: d400: suspend_hc
(...) Here I plugged the drive.
drivers/usb/host/uhci-hcd.c: d400: wakeup_hc
hub 1-0:1.0: initial port 1 status: ret = 0
hub 1-0:1.0: initial port 2 status: ret = 0
hub 1-0:1.0: port 2, status 101, change 1, 12 Mb/s
hub 1-0:1.0: clear C_CONNECTION1 = 0
hub 1-0:1.0: port_status= 0, port 2 status 101 change 0
hub 1-0:1.0: port_status= 0, port 2 status 101 change 0
hub 1-0:1.0: port_status= 0, port 2 status 101 change 0
hub 1-0:1.0: port_status= 0, port 2 status 101 change 0
hub 1-0:1.0: port_status= 0, port 2 status 101 change 0
hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:1.0: port reset = 0
hub 1-0:1.0: wait_reset 0, port 2, status 103, change 0
hub 1-0:1.0: new USB device on port 2, assigned address 2
usb 1-2: new device strings: Mfr=1, Product=3, SerialNumber=0
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 1-2: Product: USB Embedded Hub
usb 1-2: Manufacturer: Leading Driver Co.,LTD.
drivers/usb/core/usb.c: usb_hotplug
usb 1-2: registering 1-2:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-2:1.0: usb_probe_interface
hub 1-2:1.0: usb_probe_interface - got id
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 2 ports detected
hub 1-2:1.0: compound device; port removable status: FF
hub 1-2:1.0: individual port power switching
hub 1-2:1.0: individual port over-current protection
hub 1-2:1.0: Port indicators are not supported
hub 1-2:1.0: power on to power good time: 100ms
hub 1-2:1.0: hub controller current requirement: 100mA
hub 1-2:1.0: local power source is lost (inactive)
hub 1-2:1.0: no over-current condition exists
hub 1-2:1.0: enabling power on all ports
hub 1-2:1.0: port 1 power on: 0
hub 1-2:1.0: port 2 power on: 0
hub 1-2:1.0: initial port 1 status: ret = 0
hub 1-2:1.0: port 1, status 101, change 1, 12 Mb/s
hub 1-2:1.0: clear C_CONNECTION1 = 0
hub 1-2:1.0: port_status= 0, port 1 status 101 change 0
hub 1-2:1.0: port_status= 0, port 1 status 101 change 0
hub 1-2:1.0: port_status= 0, port 1 status 101 change 0
hub 1-2:1.0: port_status= 0, port 1 status 101 change 0
hub 1-2:1.0: port_status= 0, port 1 status 101 change 0
hub 1-2:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 1-2:1.0: port reset = 0
hub 1-2:1.0: wait_reset 0, port 1, status 103, change 10
hub 1-2:1.0: new USB device on port 1, assigned address 3
hub 1-2:1.0: int length 8
usb 1-2.1: new device strings: Mfr=1, Product=4, SerialNumber=0
drivers/usb/core/message.c: USB device number 3 default language ID 0x409
usb 1-2.1: Product: USB Mass Storage Device
usb 1-2.1: Manufacturer: Leading Driver Co.,LTD.
drivers/usb/core/usb.c: usb_hotplug
usb 1-2.1: registering 1-2.1:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-2:1.0: initial port 2 status: ret = 0
hub 1-2:1.0: port 2, status 101, change 1, 12 Mb/s
hub 1-2:1.0: clear C_CONNECTION1 = 0
hub 1-2:1.0: port_status= 0, port 2 status 101 change 0
hub 1-2:1.0: port_status= 0, port 2 status 101 change 0
hub 1-2:1.0: port_status= 0, port 2 status 101 change 0
hub 1-2:1.0: port_status= 0, port 2 status 101 change 0
hub 1-2:1.0: port_status= 0, port 2 status 101 change 0
hub 1-2:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-2:1.0: port reset = 0
hub 1-2:1.0: wait_reset 0, port 2, status 103, change 10
hub 1-2:1.0: new USB device on port 2, assigned address 4
usb 1-2.2: new device strings: Mfr=1, Product=5, SerialNumber=0
drivers/usb/core/message.c: USB device number 4 default language ID 0x409
usb 1-2.2: Product: USB Security Device
usb 1-2.2: Manufacturer: Leading Driver Co.,LTD.
drivers/usb/core/usb.c: usb_hotplug
usb 1-2.2: registering 1-2.2:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-2:1.0: initial port 1 status: ret = 0
hub 1-2:1.0: initial port 2 status: ret = 0
(...) Here I loaded usb-storage.
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usb-storage 1-2.1:1.0: usb_probe_interface
usb-storage 1-2.1:1.0: usb_probe_interface - got id
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Prolific Model: USB Flash Disk Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
request_module: failed /sbin/modprobe -- block-major-8-1. error = 256
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
SCSI error: host 0 id 0 lun 0 return code = 8000002
Sense class 7, sense error 0, extended sense 0
sda: sda1
SCSI error: host 0 id 0 lun 0 return code = 8000002
Sense class 7, sense error 0, extended sense 0
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI error: host 0 id 0 lun 0 return code = 8000002
Sense class 7, sense error 0, extended sense 0
Unable to load NLS charset cp437
SCSI error: host 0 id 0 lun 0 return code = 8000002
Sense class 7, sense error 0, extended sense 0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
As you can see, the error messages from the SCSI layer are still there,
but I can use the drive quite well (well, at least I think so).
Thanks, Rogério.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
