* Problems with USB Drive
@ 2003-11-05 17:56 Rogério Brito
2003-11-06 2:25 ` Rogério Brito
0 siblings, 1 reply; 10+ messages in thread
From: Rogério Brito @ 2003-11-05 17:56 UTC (permalink / raw)
To: linux-usb-users
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Dear developers,
Last July, I bought myself an USB Drive (a Leading Driver UD-11, with
128MB) with the intention of carrying my personal files on it.
Despite being able to fully use it under MacOS X and Windows, I have
been having problems with it with Linux.
It is funny that my USB printer (an HP Deskjet 840C) works wonderfully
under Linux, which leads me to think that something may be wrong with
usb-storage.
My longest experience is with the Linux 2.4 series and I've had problems
with at least kernels 2.4.x, with x >= 20 (the ones I tried). The
problem is still present in the recent 2.4.23-pre9 that Marcelo
released.
The funny part of the problem is that I sometimes *can* mount my drive,
but only part of the time (like 20% of the times that I try). The other
times, the kernel just spews a lot of error messages to my console.
Trying to see if the problem would go away with a 2.6 kernel, I
downloaded 2.6.0-test9 and tried it anyway. The problems still persist.
Thus, I am including some files from the 2.6 kernel that I am running
now and I would appreciate any help that you could provide me with
getting this drive working under Linux, as it is my main OS.
The files that I found relevant are attached.
If anything is missing or if other information is needed, please don't
hesitate to ask.
Thanks in advance for any help, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 6302 bytes --]
[-- Attachment #3: dmesg.txt --]
[-- Type: text/plain, Size: 13061 bytes --]
Linux version 2.6.0-test9-1 (root@dumont) (gcc version 3.3.2 (Debian)) #1 Wed Nov 5 14:50:36 BRST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000007fec000 (usable)
BIOS-e820: 0000000007fec000 - 0000000007fef000 (ACPI data)
BIOS-e820: 0000000007fef000 - 0000000007fff000 (reserved)
BIOS-e820: 0000000007fff000 - 0000000008000000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB LOWMEM available.
On node 0 totalpages: 32748
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 28652 pages, LIFO batch:6
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
Building zonelist for node : 0
Kernel command line: BOOT_IMAGE=Linux root=303 hdd=ide-scsi
ide_setup: hdd=ide-scsi
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Detected 605.655 MHz processor.
Console: colour VGA+ 80x25
Memory: 127124k/130992k available (1312k kernel code, 3324k reserved, 428k data, 104k init, 0k highmem)
Calibrating delay loop... 1191.93 BogoMIPS
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) Processor stepping 00
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf1010, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 02): [55] 81 & 1f -> 01
PCI: Using IRQ router VIA [1106/0686] at 0000:00:04.0
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
Initializing Cryptographic API
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 94M
agpgart: AGP aperture is 64M @ 0xe4000000
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:04.1
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:04.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLlct15 30, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ASUS DVD-ROM E608, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PDC20265: IDE controller at PCI slot 0000:00:11.0
PCI: Found IRQ 10 for device 0000:00:11.0
PDC20265: chipset revision 2
PDC20265: 100% native mode on irq 10
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x8000-0x8007, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8008-0x800f, BIOS settings: hdg:pio, hdh:pio
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(66)
hda: hda1 hda2 hda3
mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 104k freed
Adding 248996k swap on /dev/hda2. Priority:-1 extents:1
EXT3 FS on hda3, internal journal
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 9 for device 0000:00:0d.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
eth0: RealTek RTL8139 at 0xc883f000, 00:e0:7d:96:28:8f, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'
SCSI subsystem initialized
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: ASUS Model: DVD-ROM E608 Rev: l.40
Type: CD-ROM ANSI SCSI revision: 02
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: CD-Writer+ 9100 Rev: 1.0a
Type: CD-ROM ANSI SCSI revision: 02
es1371: version v0.32 time 15:04:30 Nov 5 2003
PCI: Found IRQ 9 for device 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:0d.0
es1371: found chip, vendor id 0x1274 device id 0x5880 revision 0x02
es1371: found es1371 rev 2 at io 0xa400 irq 9 joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport_pc: Via 686A parallel port: io=0x378
lp0: using parport0 (polling).
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
quotaon: numerical sysctl 5 16 8 is obsolete.
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
PCI: Found IRQ 9 for device 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:0d.0
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: irq 9, io base 0000d400
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci_hcd 0000:00:04.2: root hub device address 1
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
drivers/usb/core/message.c: USB device number 1 default language ID 0x409
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.0-test9-1 uhci_hcd
usb usb1: SerialNumber: 0000:00:04.2
drivers/usb/core/usb.c: usb_hotplug
usb usb1: registering 1-0:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: ganged power switching
hub 1-0:1.0: global over-current protection
hub 1-0:1.0: Port indicators are not supported
hub 1-0:1.0: power on to power good time: 2ms
hub 1-0:1.0: hub controller current requirement: 0mA
hub 1-0:1.0: local power source is good
hub 1-0:1.0: no over-current condition exists
hub 1-0:1.0: enabling power on all ports
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.0-test9-1 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 1-0:1.0: port 1, status 300, change 3, 1.5 Mb/s
hub 1-0:1.0: port 2, status 300, change 3, 1.5 Mb/s
hub 2-0:1.0: port 1, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 1, assigned address 2
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 2-1: Product: DeskJet 840C
usb 2-1: Manufacturer: Hewlett-Packard
usb 2-1: SerialNumber: BR1391S0WNKV
drivers/usb/core/usb.c: usb_hotplug
usb 2-1: registering 2-1:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 2, assigned address 3
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
drivers/usb/core/message.c: USB device number 3 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
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
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 1-0:1.0: port 1 enable change, status 300
hub 1-0:1.0: port 2 enable change, status 300
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
drivers/usb/host/uhci-hcd.c: d400: suspend_hc
usblp 2-1:1.0: usb_probe_interface
usblp 2-1:1.0: usb_probe_interface - got id
drivers/usb/class/usblp.c: Disabling reads from problem bidirectional printer on usblp0
drivers/usb/class/usblp.c: usblp0: USB Unidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x0604
drivers/usb/core/file.c: looking for a minor, starting at 0
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb 2-1: hcd_unlink_urb c74e3f80 fail -22
usb 2-1: hcd_unlink_urb c74e3f80 fail -22
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
hub 2-2:1.0: port 2, status 101, change 1, 12 Mb/s
hub 2-2:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 2-2:1.0: new USB device on port 2, assigned address 4
usb 2-2.2: new device strings: Mfr=1, Product=3, SerialNumber=0
drivers/usb/core/message.c: USB device number 4 default language ID 0x409
usb 2-2.2: Product: USB Embedded Hub
usb 2-2.2: Manufacturer: Leading Driver Co.,LTD.
drivers/usb/core/usb.c: usb_hotplug
usb 2-2.2: registering 2-2.2:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-2.2:1.0: usb_probe_interface
hub 2-2.2:1.0: usb_probe_interface - got id
hub 2-2.2:1.0: USB hub found
hub 2-2.2:1.0: 2 ports detected
hub 2-2.2:1.0: compound device; port removable status: FF
hub 2-2.2:1.0: individual port power switching
hub 2-2.2:1.0: individual port over-current protection
hub 2-2.2:1.0: Port indicators are not supported
hub 2-2.2:1.0: power on to power good time: 100ms
hub 2-2.2:1.0: hub controller current requirement: 100mA
hub 2-2.2:1.0: local power source is lost (inactive)
hub 2-2.2:1.0: no over-current condition exists
hub 2-2.2:1.0: enabling power on all ports
hub 2-2.2:1.0: port 1, status 101, change 1, 12 Mb/s
hub 2-2.2:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 2-2.2:1.0: new USB device on port 1, assigned address 5
hub 2-2.2:1.0: transfer --> -75
usb 2-2.2.1: control timeout on ep0in
[-- Attachment #4: lspci-v.txt --]
[-- Type: text/plain, Size: 3687 bytes --]
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
Subsystem: Asustek Computer, Inc. A7V Mainboard
Flags: bus master, medium devsel, latency 0
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e0800000-e1dfffff
Prefetchable memory behind bridge: e1f00000-e3ffffff
Capabilities: [80] Power Management version 2
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
Subsystem: Asustek Computer, Inc. A7V Mainboard
Flags: bus master, stepping, medium devsel, latency 0
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at d800 [size=16]
Capabilities: [c0] Power Management version 2
00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 10) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
00:04.3 USB Controller: VIA Technologies, Inc. USB (rev 10) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
Flags: medium devsel, IRQ 9
Capabilities: [68] Power Management version 2
00:09.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
Subsystem: Ensoniq Creative SoundBlaster AudioPCI 128
Flags: bus master, slow devsel, latency 32, IRQ 9
I/O ports at a400 [size=64]
Capabilities: [dc] Power Management version 1
00:0a.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
Subsystem: 5610 56K FaxModem USR 56k Internal Voice Modem (Model 2976)
Flags: medium devsel, IRQ 5
I/O ports at a000 [size=8]
Capabilities: [dc] Power Management version 2
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at 9800 [size=256]
Memory at e0000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 02)
Subsystem: Promise Technology, Inc. Ultra100
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at 9400 [size=8]
I/O ports at 9000 [size=4]
I/O ports at 8800 [size=8]
I/O ports at 8400 [size=4]
I/O ports at 8000 [size=64]
Memory at df800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [58] Power Management version 1
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at e2000000 (32-bit, prefetchable) [size=32M]
Memory at e1000000 (32-bit, non-prefetchable) [size=16K]
Memory at e0800000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at e1ff0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Capabilities: [f0] AGP version 2.0
[-- Attachment #5: lspci.txt --]
[-- Type: text/plain, Size: 952 bytes --]
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 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:09.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:0a.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610 (rev 01)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 02)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)
[-- Attachment #6: mount.txt --]
[-- Type: text/plain, Size: 45 bytes --]
mount: /dev/sda1 is not a valid block device
[-- Attachment #7: uname-a.txt --]
[-- Type: text/plain, Size: 74 bytes --]
Linux dumont 2.6.0-test9-1 #1 Wed Nov 5 14:50:36 BRST 2003 i686 GNU/Linux
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Problems with USB Drive
2003-11-05 17:56 Problems with USB Drive Rogério Brito
@ 2003-11-06 2:25 ` Rogério Brito
2003-11-06 22:49 ` Rogério Brito
0 siblings, 1 reply; 10+ messages in thread
From: Rogério Brito @ 2003-11-06 2:25 UTC (permalink / raw)
To: linux-usb-users, linux-kernel
On Nov 05 2003, Rogério Brito wrote:
> Dear developers,
(...)
> Trying to see if the problem would go away with a 2.6 kernel, I
> downloaded 2.6.0-test9 and tried it anyway. The problems still persist.
(...)
Just as some extra information, when I try to shutdown the hotplug
service (via /etc/init.d/hotplug stop), the program hangs and I get
processes in the D state in the output of ps.
Also, when this occurs, lsmod also hangs and is also unkillable.
I am using Debian testing's hotplug, which has version 0.0.20031013-2.
Thanks again for your work, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Problems with USB Drive
2003-11-06 2:25 ` Rogério Brito
@ 2003-11-06 22:49 ` Rogério Brito
2003-11-07 19:58 ` Oops trying to use an USB Drive (was: Re: Problems with USB Drive) Rogério Brito
0 siblings, 1 reply; 10+ messages in thread
From: Rogério Brito @ 2003-11-06 22:49 UTC (permalink / raw)
To: linux-usb-users, linux-kernel
On Nov 06 2003, Rogério Brito wrote:
> Just as some extra information, when I try to shutdown the hotplug
> service (via /etc/init.d/hotplug stop), the program hangs and I get
> processes in the D state in the output of ps.
>
> Also, when this occurs, lsmod also hangs and is also unkillable.
(...)
Here are some extra pieces of information regarding what people told me
or recommended me:
* I am already using UHCI, and not OHCI (in particular, I am using the
uhci_hcd module);
* I tried inserting my USB drive slowly, but it seemed to make no
difference;
* Before inserting the USB drive, I already have scsi_mod, ide_scsi,
sd_mod, usbcore and usblp loaded.
The bad thing is that apart from not being able to store my files in my
drive, this process is leaving some unkillable processes in my system as
shows the following excerpt from an execution of the command "ps aux":
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2650 0.0 1.2 2648 1536 pts/0 S 20:14 0:00 -su
root 2757 0.0 0.3 1524 464 pts/0 T 20:19 0:00 /bin/sh /etc/init.d/hotplug status
root 2772 0.0 0.9 2384 1184 pts/0 T 20:19 0:00 /bin/bash /etc/hotplug/usb.rc status
root 2778 0.0 0.3 1504 448 pts/0 D 20:19 0:00 grep ^[TPSI]: /proc/bus/usb/devices
root 2795 0.0 0.6 2452 828 pts/0 R 20:22 0:00 ps aux
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
As a reminder, the last lines of my dmesg output that seems relevant to
the problem is attached to this message. After that, I get the message
that /dev/sda1 is not a valid block device.
I put all the relevant files that I can think of on my homepage, at
<http://www.ime.usp.br/~rbrito/usb/> for further reference.
Please feel free to ask me whatever you feel is important and I will do
my best to answer to get this working correctly.
Thanks in advance, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
^ permalink raw reply [flat|nested] 10+ messages in thread
* Oops trying to use an USB Drive (was: Re: Problems with USB Drive)
2003-11-06 22:49 ` Rogério Brito
@ 2003-11-07 19:58 ` Rogério Brito
2003-11-12 20:46 ` [BUG] Still having problems with an USB Drive Rogério Brito
0 siblings, 1 reply; 10+ messages in thread
From: Rogério Brito @ 2003-11-07 19:58 UTC (permalink / raw)
To: linux-usb-users, linux-kernel; +Cc: linux-usb-devel
On Nov 06 2003, Rogério Brito wrote:
> On Nov 06 2003, Rogério Brito wrote:
> > Just as some extra information, when I try to shutdown the hotplug
> > service (via /etc/init.d/hotplug stop), the program hangs and I get
> > processes in the D state in the output of ps.
> (...)
>
> Please feel free to ask me whatever you feel is important and I will do
> my best to answer to get this working correctly.
Unfortunately, when using a kernel from the 2.4 series, I am still not
able to use my USB Drive.
Just as a reminder, I was having problems with various 2.4 kernels and
decided to try a 2.6 kernel (2.6.0-test9). Since I also had problems
there (with data available at http://www.ime.usp.br/~rbrito/usb/), I
decided to go back to a 2.4 kernel, 2.4.23-pre9 + the current packet
writing patch.
I got many errors when I booted my system. Then, I tried playing with
the hotplug scripts (disabling hotplug). And I got an Oops.
The decoded oops is here:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ksymoops 2.4.9 on i686 2.4.23-pre9-pkt-1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.23-pre9-pkt-1/ (default)
-m /boot/System.map-2.4.23-pre9-pkt-1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
kernel BUG at slab.c:815!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c012a6f3>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: c7feaae0 ecx: c7feaa6c edx: c7feaa6c
esi: c7feaa66 edi: c8899a2a ebp: c027b1d8 esp: c368deec
ds: 0018 es: 0018 ss: 0018
Process modprobe.moduti (pid: 1259, stackpage=c368d000)
Stack: fffffffc 0000001c fffffff4 00000001 00000001 ffffffea c88994b5 c8899a1c
0000003c 00000010 00000000 00000000 00000000 c8895000 c0116935 c889ab60
0808c6e0 00005a90 00000060 00000060 00000004 c61a3d00 c393a000 c38f4000
Call Trace: [<c88994b5>] [<c8899a1c>] [<c0116935>] [<c889ab60>] [<c8895060>]
[<c0106e93>]
Code: 0f 0b 2f 03 62 fb 1f c0 8b 12 81 fa a4 78 22 c0 75 d3 8d 43
>>EIP; c012a6f3 <kmem_cache_create+28b/338> <=====
>>ebx; c7feaae0 <_end+7d4f0c8/859a648>
>>ecx; c7feaa6c <_end+7d4f054/859a648>
>>edx; c7feaa6c <_end+7d4f054/859a648>
>>esi; c7feaa66 <_end+7d4f04e/859a648>
>>edi; c8899a2a <[uhci].text.end+425/13db>
>>ebp; c027b1d8 <cache_chain_sem+0/10>
>>esp; c368deec <_end+33f24d4/859a648>
Trace; c88994b5 <[uhci]uhci_hcd_init+69/f4>
Trace; c8899a1c <[uhci].text.end+417/13db>
Trace; c0116935 <sys_init_module+4d1/62c>
Trace; c889ab60 <[uhci]__module_license+45/85>
Trace; c8895060 <[uhci]uhci_show_td+0/198>
Trace; c0106e93 <system_call+33/38>
Code; c012a6f3 <kmem_cache_create+28b/338>
00000000 <_EIP>:
Code; c012a6f3 <kmem_cache_create+28b/338> <=====
0: 0f 0b ud2a <=====
Code; c012a6f5 <kmem_cache_create+28d/338>
2: 2f das
Code; c012a6f6 <kmem_cache_create+28e/338>
3: 03 62 fb add 0xfffffffb(%edx),%esp
Code; c012a6f9 <kmem_cache_create+291/338>
6: 1f pop %ds
Code; c012a6fa <kmem_cache_create+292/338>
7: c0 8b 12 81 fa a4 78 rorb $0x78,0xa4fa8112(%ebx)
Code; c012a701 <kmem_cache_create+299/338>
e: 22 c0 and %al,%al
Code; c012a703 <kmem_cache_create+29b/338>
10: 75 d3 jne ffffffe5 <_EIP+0xffffffe5>
Code; c012a705 <kmem_cache_create+29d/338>
12: 8d 43 00 lea 0x0(%ebx),%eax
1 warning issued. Results may not be reliable.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please, can anybody help? :-(
Thanks in advance for any feedback, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
^ permalink raw reply [flat|nested] 10+ messages in thread
* [BUG] Still having problems with an USB Drive
2003-11-07 19:58 ` Oops trying to use an USB Drive (was: Re: Problems with USB Drive) Rogério Brito
@ 2003-11-12 20:46 ` Rogério Brito
2003-11-13 20:24 ` [linux-usb-devel] " Alan Stern
0 siblings, 1 reply; 10+ messages in thread
From: Rogério Brito @ 2003-11-12 20:46 UTC (permalink / raw)
To: linux-usb-devel; +Cc: linux-usb-users, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]
Dear developers and other users,
One week ago, I reported problems with my USB Drive (a Leading Driver
UD-11), when trying to use it with Linux.
The problems still persist after many different kernel releases, using
both kernels from the 2.4 and the 2.6 series.
Unfortunately, it seems that my messages were ignored after some point,
but if it is for lack of information, then I would like to know which
information is needed (I even provided a decoded Oops, but if that is
not sufficient, please let me know).
The problems that I have is that, despite all my efforts, the drive is
only part of the time recognized as a valid block device. About 80% of
the time, it simply is not recognized as a block device and I see many
error messages generated by the kernel (see attached dmesg).
I can use my drive without any problems under both MacOS X and under
Windows and sometimes under Linux, which leads me to think that it is
not a problem with the drive itself but only with the kernel.
Using a 2.6.0-test9 kernel, when my drive is not recognized, I remove
the drive and then plug it again, I see khub enter the "D" state. From
there on, if I try to disable the hotplug subsystem (via
/etc/init.d/hotplug stop), hotplug also becomes ininterruptible.
If you want to see my earlier messages about the problem, please see:
http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0650.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0652.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0850.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0998.html
I put here attached both a dmesg after a fresh boot (and the device
ignored) and a dmesg of the system after I remove and reinsert the USB
Drive.
Please, help.
Thanks in advance, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[-- Attachment #2: dmesg-usb-fail.txt --]
[-- Type: text/plain, Size: 12666 bytes --]
Linux version 2.6.0-test9-1 (root@dumont) (gcc version 3.3.2 (Debian)) #1 Wed Nov 5 14:50:36 BRST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000007fec000 (usable)
BIOS-e820: 0000000007fec000 - 0000000007fef000 (ACPI data)
BIOS-e820: 0000000007fef000 - 0000000007fff000 (reserved)
BIOS-e820: 0000000007fff000 - 0000000008000000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB LOWMEM available.
On node 0 totalpages: 32748
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 28652 pages, LIFO batch:6
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=Linux root=303 hdd=ide-scsi
ide_setup: hdd=ide-scsi
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Detected 605.648 MHz processor.
Console: colour VGA+ 80x25
Memory: 127124k/130992k available (1312k kernel code, 3324k reserved, 428k data, 104k init, 0k highmem)
Calibrating delay loop... 1191.93 BogoMIPS
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) Processor stepping 00
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf1010, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 02): [55] 81 & 1f -> 01
PCI: Using IRQ router VIA [1106/0686] at 0000:00:04.0
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
Initializing Cryptographic API
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 94M
agpgart: AGP aperture is 64M @ 0xe4000000
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:04.1
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:04.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLlct15 30, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ASUS DVD-ROM E608, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PDC20265: IDE controller at PCI slot 0000:00:11.0
PCI: Found IRQ 10 for device 0000:00:11.0
PDC20265: chipset revision 2
PDC20265: 100% native mode on irq 10
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x8000-0x8007, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8008-0x800f, BIOS settings: hdg:pio, hdh:pio
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(66)
hda: hda1 hda2 hda3
mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 104k freed
Adding 248996k swap on /dev/hda2. Priority:-1 extents:1
EXT3 FS on hda3, internal journal
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 9 for device 0000:00:0d.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
eth0: RealTek RTL8139 at 0xc883f000, 00:e0:7d:96:28:8f, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'
SCSI subsystem initialized
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: ASUS Model: DVD-ROM E608 Rev: l.40
Type: CD-ROM ANSI SCSI revision: 02
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: CD-Writer+ 9100 Rev: 1.0a
Type: CD-ROM ANSI SCSI revision: 02
es1371: version v0.32 time 15:04:30 Nov 5 2003
PCI: Found IRQ 9 for device 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:0d.0
es1371: found chip, vendor id 0x1274 device id 0x5880 revision 0x02
es1371: found es1371 rev 2 at io 0xa400 irq 9 joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport_pc: Via 686A parallel port: io=0x378
lp0: using parport0 (polling).
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
quotaon: numerical sysctl 5 16 8 is obsolete.
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
PCI: Found IRQ 9 for device 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:0d.0
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: irq 9, io base 0000d400
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci_hcd 0000:00:04.2: root hub device address 1
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
drivers/usb/core/message.c: USB device number 1 default language ID 0x409
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.0-test9-1 uhci_hcd
usb usb1: SerialNumber: 0000:00:04.2
drivers/usb/core/usb.c: usb_hotplug
usb usb1: registering 1-0:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: ganged power switching
hub 1-0:1.0: global over-current protection
hub 1-0:1.0: Port indicators are not supported
hub 1-0:1.0: power on to power good time: 2ms
hub 1-0:1.0: hub controller current requirement: 0mA
hub 1-0:1.0: local power source is good
hub 1-0:1.0: no over-current condition exists
hub 1-0:1.0: enabling power on all ports
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.0-test9-1 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 1-0:1.0: port 1, status 300, change 3, 1.5 Mb/s
hub 1-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
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: transfer --> -75
hub 1-0:1.0: port 1 enable change, status 300
hub 2-0:1.0: port 1, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 1, assigned address 2
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 2-1: Product: DeskJet 840C
usb 2-1: Manufacturer: Hewlett-Packard
usb 2-1: SerialNumber: BR1391S0WNKV
drivers/usb/core/usb.c: usb_hotplug
usb 2-1: registering 2-1:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 2, assigned address 3
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
drivers/usb/core/message.c: USB device number 3 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
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
usblp 2-1:1.0: usb_probe_interface
usblp 2-1:1.0: usb_probe_interface - got id
drivers/usb/class/usblp.c: Disabling reads from problem bidirectional printer on usblp0
drivers/usb/class/usblp.c: usblp0: USB Unidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x0604
drivers/usb/core/file.c: looking for a minor, starting at 0
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb 2-1: hcd_unlink_urb c71fc480 fail -22
usb 2-1: hcd_unlink_urb c71fc480 fail -22
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[-- Attachment #3: dmesg-usb-fail2.txt --]
[-- Type: text/plain, Size: 13397 bytes --]
Linux version 2.6.0-test9-1 (root@dumont) (gcc version 3.3.2 (Debian)) #1 Wed Nov 5 14:50:36 BRST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000007fec000 (usable)
BIOS-e820: 0000000007fec000 - 0000000007fef000 (ACPI data)
BIOS-e820: 0000000007fef000 - 0000000007fff000 (reserved)
BIOS-e820: 0000000007fff000 - 0000000008000000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB LOWMEM available.
On node 0 totalpages: 32748
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 28652 pages, LIFO batch:6
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=Linux root=303 hdd=ide-scsi
ide_setup: hdd=ide-scsi
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Detected 605.648 MHz processor.
Console: colour VGA+ 80x25
Memory: 127124k/130992k available (1312k kernel code, 3324k reserved, 428k data, 104k init, 0k highmem)
Calibrating delay loop... 1191.93 BogoMIPS
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) Processor stepping 00
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf1010, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 02): [55] 81 & 1f -> 01
PCI: Using IRQ router VIA [1106/0686] at 0000:00:04.0
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
Initializing Cryptographic API
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 94M
agpgart: AGP aperture is 64M @ 0xe4000000
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:04.1
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:04.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLlct15 30, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ASUS DVD-ROM E608, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PDC20265: IDE controller at PCI slot 0000:00:11.0
PCI: Found IRQ 10 for device 0000:00:11.0
PDC20265: chipset revision 2
PDC20265: 100% native mode on irq 10
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x8000-0x8007, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8008-0x800f, BIOS settings: hdg:pio, hdh:pio
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(66)
hda: hda1 hda2 hda3
mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 104k freed
Adding 248996k swap on /dev/hda2. Priority:-1 extents:1
EXT3 FS on hda3, internal journal
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 9 for device 0000:00:0d.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
eth0: RealTek RTL8139 at 0xc883f000, 00:e0:7d:96:28:8f, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'
SCSI subsystem initialized
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: ASUS Model: DVD-ROM E608 Rev: l.40
Type: CD-ROM ANSI SCSI revision: 02
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: CD-Writer+ 9100 Rev: 1.0a
Type: CD-ROM ANSI SCSI revision: 02
es1371: version v0.32 time 15:04:30 Nov 5 2003
PCI: Found IRQ 9 for device 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:0d.0
es1371: found chip, vendor id 0x1274 device id 0x5880 revision 0x02
es1371: found es1371 rev 2 at io 0xa400 irq 9 joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport_pc: Via 686A parallel port: io=0x378
lp0: using parport0 (polling).
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
quotaon: numerical sysctl 5 16 8 is obsolete.
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
PCI: Found IRQ 9 for device 0000:00:04.2
PCI: Sharing IRQ 9 with 0000:00:04.3
PCI: Sharing IRQ 9 with 0000:00:09.0
PCI: Sharing IRQ 9 with 0000:00:0d.0
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: irq 9, io base 0000d400
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci_hcd 0000:00:04.2: root hub device address 1
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
drivers/usb/core/message.c: USB device number 1 default language ID 0x409
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.0-test9-1 uhci_hcd
usb usb1: SerialNumber: 0000:00:04.2
drivers/usb/core/usb.c: usb_hotplug
usb usb1: registering 1-0:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: ganged power switching
hub 1-0:1.0: global over-current protection
hub 1-0:1.0: Port indicators are not supported
hub 1-0:1.0: power on to power good time: 2ms
hub 1-0:1.0: hub controller current requirement: 0mA
hub 1-0:1.0: local power source is good
hub 1-0:1.0: no over-current condition exists
hub 1-0:1.0: enabling power on all ports
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.0-test9-1 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 1-0:1.0: port 1, status 300, change 3, 1.5 Mb/s
hub 1-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
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: transfer --> -75
hub 1-0:1.0: port 1 enable change, status 300
hub 2-0:1.0: port 1, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 1, assigned address 2
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 2-1: Product: DeskJet 840C
usb 2-1: Manufacturer: Hewlett-Packard
usb 2-1: SerialNumber: BR1391S0WNKV
drivers/usb/core/usb.c: usb_hotplug
usb 2-1: registering 2-1:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
hub 2-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 2-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 2-0:1.0: new USB device on port 2, assigned address 3
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
drivers/usb/core/message.c: USB device number 3 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
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
usblp 2-1:1.0: usb_probe_interface
usblp 2-1:1.0: usb_probe_interface - got id
drivers/usb/class/usblp.c: Disabling reads from problem bidirectional printer on usblp0
drivers/usb/class/usblp.c: usblp0: USB Unidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x0604
drivers/usb/core/file.c: looking for a minor, starting at 0
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb 2-1: hcd_unlink_urb c71fc480 fail -22
usb 2-1: hcd_unlink_urb c71fc480 fail -22
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
hub 1-0:1.0: port 2, status 100, change 3, 12 Mb/s
usb 1-2: USB disconnect, address 2
usb 1-2: usb_disable_device nuking all URBs
uhci_hcd 0000:00:04.2: shutdown urb c780ea80 pipe 40408280 ep1in-intr
usb 1-2: unregistering interface 1-2:1.0
usb 1-2: hcd_unlink_urb c780ea80 fail -16
drivers/usb/core/usb.c: usb_hotplug
usb 1-2: unregistering device
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:1.0: port 2 enable change, status 100
drivers/usb/host/uhci-hcd.c: d400: suspend_hc
drivers/usb/host/uhci-hcd.c: d400: wakeup_hc
hub 1-0:1.0: port 2, status 101, change 3, 12 Mb/s
hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:1.0: new USB device on port 2, assigned address 3
usb 1-2: control timeout on ep0out
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [linux-usb-devel] [BUG] Still having problems with an USB Drive
2003-11-12 20:46 ` [BUG] Still having problems with an USB Drive Rogério Brito
@ 2003-11-13 20:24 ` Alan Stern
2003-11-13 23:36 ` Rogério Brito
0 siblings, 1 reply; 10+ messages in thread
From: Alan Stern @ 2003-11-13 20:24 UTC (permalink / raw)
To: Rogério Brito; +Cc: linux-usb-devel, linux-usb-users, linux-kernel
On Wed, 12 Nov 2003, Rogério Brito wrote:
>
> Dear developers and other users,
>
> One week ago, I reported problems with my USB Drive (a Leading Driver
> UD-11), when trying to use it with Linux.
>
> The problems still persist after many different kernel releases, using
> both kernels from the 2.4 and the 2.6 series.
>
> Unfortunately, it seems that my messages were ignored after some point,
> but if it is for lack of information, then I would like to know which
> information is needed (I even provided a decoded Oops, but if that is
> not sufficient, please let me know).
>
> The problems that I have is that, despite all my efforts, the drive is
> only part of the time recognized as a valid block device. About 80% of
> the time, it simply is not recognized as a block device and I see many
> error messages generated by the kernel (see attached dmesg).
>
> I can use my drive without any problems under both MacOS X and under
> Windows and sometimes under Linux, which leads me to think that it is
> not a problem with the drive itself but only with the kernel.
>
> Using a 2.6.0-test9 kernel, when my drive is not recognized, I remove
> the drive and then plug it again, I see khub enter the "D" state. From
> there on, if I try to disable the hotplug subsystem (via
> /etc/init.d/hotplug stop), hotplug also becomes ininterruptible.
>
> If you want to see my earlier messages about the problem, please see:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0650.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0652.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0850.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0998.html
>
> I put here attached both a dmesg after a fresh boot (and the device
> ignored) and a dmesg of the system after I remove and reinsert the USB
> Drive.
>
> Please, help.
>
>
> Thanks in advance, Rogério Brito.
The dmesg files you included and posted don't contain much useful
information relating to this problem.
Forget about usb-storage and hotplug scripts. If you can't even get to
the point where your device show up in /proc/bus/usb/devices then nothing
else will work.
Judging from your dmesg output, you have an external hub (ALCOR Generic
USB Hub) into which your device is plugged. The device contains an
internal hub (Leading Driver Co., LTD. USB Embedded Hub) and the drive is
attached through that internal hub. But an attempt to communicate with
the drive failed. It could be a problem with the external hub, the
internal hub, or the drive itself; it's not likely to be a problem with
the kernel. The error message
hub 2-2.2:1.0: transfer --> -75
indicates a problem with the internal hub, but there's no way to tell what
that problem is. The other error message
usb 2-2.2.1: control timeout on ep0in
indicates a problem communicating with the drive, but that could be caused
by the internal hub not working right.
You might try plugging your device directly into the PC to see if that
makes a difference. Better yet, try plugging your device into a
completely different PC running Linux 2.6 and see what happens.
Alan Stern
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [linux-usb-devel] [BUG] Still having problems with an USB Drive
2003-11-13 20:24 ` [linux-usb-devel] " Alan Stern
@ 2003-11-13 23:36 ` Rogério Brito
2003-11-13 23:50 ` Rogério Brito
2003-11-14 15:57 ` Alan Stern
0 siblings, 2 replies; 10+ messages in thread
From: Rogério Brito @ 2003-11-13 23:36 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb-devel, linux-usb-users, linux-kernel
On Nov 13 2003, Alan Stern wrote:
> On Wed, 12 Nov 2003, Rogério Brito wrote:
> > One week ago, I reported problems with my USB Drive (a Leading Driver
> > UD-11), when trying to use it with Linux.
(...)
>
> The dmesg files you included and posted don't contain much useful
> information relating to this problem.
First of all, thank you very much for your concern.
Yes, thinking more about the problem, that seems to be the case. David
Brownell already told me that.
I sent him an e-mail telling what I see when I modify my
/etc/hotplug/usb.rc script to contain "modprobe -q uhci-hcd debug=2".
I don't know if that is sufficient, though (I think he has not had the
time to reply to me yet).
> Forget about usb-storage and hotplug scripts. If you can't even get
> to the point where your device show up in /proc/bus/usb/devices then
> nothing else will work.
Yes, the strange thing is that sometimes, the drive is detected and it
works. Sometimes, it doesn't. Most of the time, it doesn't. And when
it doesn't work and I try to turn hotplug off, I get unkillable
processes (khubd is in state D).
Anyway, what should I do? Should I just boot into single user mode
without hotplug enabled and load the modules by hand?
> Judging from your dmesg output, you have an external hub (ALCOR
> Generic USB Hub) into which your device is plugged. The device
> contains an internal hub (Leading Driver Co., LTD. USB Embedded Hub)
> and the drive is attached through that internal hub.
I don't really know much about my USB setup. I have an Asus A7V
motherboad and according to its manual (which I just checked), it has 2
USB ports and two USB "leads" (in one of those, I plugged a small cable
to a daughterboard, which gives me more USB ports).
Perhaps this small daughterboard is a new hub?
Anyway, it seems that I have problems regardless of which port I connect
my USB drive to. But I can make tests to confirm that if anybody tells
me what to do.
Oh, BTW, Leading Driver is the USB drive (perhaps it's an internal hub
in the drive?). It may be recognized as more than just one USB device,
but I'm not certain of that, since I don't know what I'm talking about.
BTW, the only USB devices that I have are:
1 - this USB drive;
2 - one keyboard + one mouse;
3 - a HP printer.
> But an attempt to communicate with the drive failed. It could be a
> problem with the external hub, the internal hub, or the drive itself;
> it's not likely to be a problem with the kernel. The error message
Ok.
> hub 2-2.2:1.0: transfer --> -75
>
> indicates a problem with the internal hub, but there's no way to tell what
> that problem is. The other error message
Is there any way to discover what may be the reason of the problem? Any
higher debugging level would help with that?
> usb 2-2.2.1: control timeout on ep0in
>
> indicates a problem communicating with the drive, but that could be caused
> by the internal hub not working right.
Right.
> You might try plugging your device directly into the PC to see if that
> makes a difference.
Well, I can try plugging the drive directly into the first ports of the
PC (instead of those of the daughterboard). I will report what I see.
> Better yet, try plugging your device into a completely different PC
> running Linux 2.6 and see what happens.
Ok, I will compile a new kernel for an old computer that I have and I
will also report what I see.
For the time being, I put new files at http://www.ime.usp.br/~rbrito/usb
for the situation without any USB devices plugged after a warm boot. I
hope that they're more helpful than the files I posted before.
> Alan Stern
Thank you very much for your help, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [linux-usb-devel] [BUG] Still having problems with an USB Drive
2003-11-13 23:36 ` Rogério Brito
@ 2003-11-13 23:50 ` Rogério Brito
2003-11-14 15:57 ` Alan Stern
1 sibling, 0 replies; 10+ messages in thread
From: Rogério Brito @ 2003-11-13 23:50 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb-devel, linux-usb-users, linux-kernel
On Nov 13 2003, Rogério Brito wrote:
> For the time being, I put new files at http://www.ime.usp.br/~rbrito/usb
> for the situation without any USB devices plugged after a warm boot. I
> hope that they're more helpful than the files I posted before.
Well, I just tried plugging the drive into one of the ports that come
right from the motherboard and the diff relative to what I saw earlier
is the following:
--- /root/dmesg-no-devices-plugged.txt 2003-11-13 20:58:06.000000000 -0200
+++ dmesg-drive-plugged-unplugged-plugged.txt 2003-11-13 21:41:37.000000000 -0200
@@ -228,3 +228,30 @@
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
drivers/usb/host/uhci-hcd.c: d400: suspend_hc
+drivers/usb/host/uhci-hcd.c: d400: wakeup_hc
+hub 1-0:1.0: port 1, status 101, change 1, 12 Mb/s
+hub 1-0:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
+hub 1-0:1.0: new USB device on port 1, assigned address 2
+usb 1-1: new device strings: Mfr=1, Product=3, SerialNumber=0
+drivers/usb/core/message.c: USB device number 2 default language ID 0x409
+usb 1-1: Product: USB Embedded Hub
+usb 1-1: Manufacturer: Leading Driver Co.,LTD.
+drivers/usb/core/usb.c: usb_hotplug
+usb 1-1: registering 1-1:1.0 (config #1, interface 0)
+drivers/usb/core/usb.c: usb_hotplug
+hub 1-1:1.0: usb_probe_interface
+hub 1-1:1.0: usb_probe_interface - got id
+hub 1-1:1.0: USB hub found
+hub 1-1:1.0: 2 ports detected
+hub 1-1:1.0: compound device; port removable status: FF
+hub 1-1:1.0: individual port power switching
+hub 1-1:1.0: individual port over-current protection
+hub 1-1:1.0: Port indicators are not supported
+hub 1-1:1.0: power on to power good time: 100ms
+hub 1-1:1.0: hub controller current requirement: 100mA
+hub 1-1:1.0: local power source is lost (inactive)
+hub 1-1:1.0: no over-current condition exists
+hub 1-1:1.0: enabling power on all ports
+hub 1-1:1.0: port 1, status 101, change 1, 12 Mb/s
+hub 1-1:1.0: transfer --> -75
+usb 1-1: control timeout on ep0in
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
So, it seems that my drive indeed has an embedded hub in it. After the
lines above, my khubd thread enters the D state.
If I try to issue a "cat /proc/bus/usb/devices" command, it hangs. BTW,
I just received another line saying control timeout on ep0in. :-(
Is there anything else that I can do?
Thank you very much for your attention, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [linux-usb-devel] [BUG] Still having problems with an USB Drive
2003-11-13 23:36 ` Rogério Brito
2003-11-13 23:50 ` Rogério Brito
@ 2003-11-14 15:57 ` Alan Stern
2003-11-14 17:11 ` David Brownell
1 sibling, 1 reply; 10+ messages in thread
From: Alan Stern @ 2003-11-14 15:57 UTC (permalink / raw)
To: Rogério Brito; +Cc: linux-usb-devel, linux-usb-users, linux-kernel
On Thu, 13 Nov 2003, Rogério Brito wrote:
> Yes, thinking more about the problem, that seems to be the case. David
> Brownell already told me that.
>
> I sent him an e-mail telling what I see when I modify my
> /etc/hotplug/usb.rc script to contain "modprobe -q uhci-hcd debug=2".
An alternative is after you have loaded uhci-hcd but before your device is
plugged in, do
echo 4 > /proc/driver/uhci/...
where ... is the file corresponding to the controller you plug your device
into. Debugging level 4 will provide more information than level 2, in
any case.
> > Forget about usb-storage and hotplug scripts. If you can't even get
> > to the point where your device show up in /proc/bus/usb/devices then
> > nothing else will work.
>
> Yes, the strange thing is that sometimes, the drive is detected and it
> works. Sometimes, it doesn't. Most of the time, it doesn't. And when
> it doesn't work and I try to turn hotplug off, I get unkillable
> processes (khubd is in state D).
>
> Anyway, what should I do? Should I just boot into single user mode
> without hotplug enabled and load the modules by hand?
That would be a good way of testing.
> > Judging from your dmesg output, you have an external hub (ALCOR
> > Generic USB Hub) into which your device is plugged. The device
> > contains an internal hub (Leading Driver Co., LTD. USB Embedded Hub)
> > and the drive is attached through that internal hub.
>
> I don't really know much about my USB setup. I have an Asus A7V
> motherboad and according to its manual (which I just checked), it has 2
> USB ports and two USB "leads" (in one of those, I plugged a small cable
> to a daughterboard, which gives me more USB ports).
>
> Perhaps this small daughterboard is a new hub?
Judging from your latest dmesg postings, it is.
> Anyway, it seems that I have problems regardless of which port I connect
> my USB drive to. But I can make tests to confirm that if anybody tells
> me what to do.
>
> Oh, BTW, Leading Driver is the USB drive (perhaps it's an internal hub
> in the drive?). It may be recognized as more than just one USB device,
> but I'm not certain of that, since I don't know what I'm talking about.
It definitely is getting recognized as more than one USB device, but
that's the point where things go wrong.
> > But an attempt to communicate with the drive failed. It could be a
> > problem with the external hub, the internal hub, or the drive itself;
> > it's not likely to be a problem with the kernel. The error message
>
> Ok.
>
> > hub 2-2.2:1.0: transfer --> -75
> >
> > indicates a problem with the internal hub, but there's no way to tell what
> > that problem is. The other error message
>
> Is there any way to discover what may be the reason of the problem? Any
> higher debugging level would help with that?
The only way I can think of is by comparison with what happens when the
device works. That's why I suggested trying another computer. Another
approach would be to use a USB logging programs to see what happens when
you use your device under Windows.
> > usb 2-2.2.1: control timeout on ep0in
> >
> > indicates a problem communicating with the drive, but that could be caused
> > by the internal hub not working right.
>
> Right.
Also, if you can collect and post the dmesg output from one of those
occasions when the device does work, perhaps that will help.
Alan Stern
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [linux-usb-devel] [BUG] Still having problems with an USB Drive
2003-11-14 15:57 ` Alan Stern
@ 2003-11-14 17:11 ` David Brownell
0 siblings, 0 replies; 10+ messages in thread
From: David Brownell @ 2003-11-14 17:11 UTC (permalink / raw)
To: Alan Stern, Rogério Brito
Cc: linux-usb-devel, linux-usb-users, linux-kernel
Alan Stern wrote:
> On Thu, 13 Nov 2003, Rogério Brito wrote:
>
>
>>Yes, thinking more about the problem, that seems to be the case. David
>>Brownell already told me that.
>>
>>I sent him an e-mail telling what I see when I modify my
>>/etc/hotplug/usb.rc script to contain "modprobe -q uhci-hcd debug=2".
He never got it, and the webpages you put up with that info didn't
have that information either. Please just keep the list updated;
I don't have much time for such things.
And for that matter, all followups _only_ to linux-usb-devel please!
This discussion shouldn't be CC'd to three large lists (IMO).
>>> hub 2-2.2:1.0: transfer --> -75
>>>
>>>indicates a problem with the internal hub, but there's no way to tell what
>>>that problem is. The other error message
>>
>>Is there any way to discover what may be the reason of the problem? Any
>>higher debugging level would help with that?
The message only comes out in one place (drivers/usb/core/hub.c),
so there's only one way it could appear...
Clearly this external hub is misbehaving, that should never happen.
Maybe it needs more power than it's getting.
However, even if the hub driver does see a fault, that's no excuse
for khubd to lock up.
- Dave
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-11-14 17:05 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-05 17:56 Problems with USB Drive Rogério Brito
2003-11-06 2:25 ` Rogério Brito
2003-11-06 22:49 ` Rogério Brito
2003-11-07 19:58 ` Oops trying to use an USB Drive (was: Re: Problems with USB Drive) Rogério Brito
2003-11-12 20:46 ` [BUG] Still having problems with an USB Drive Rogério Brito
2003-11-13 20:24 ` [linux-usb-devel] " Alan Stern
2003-11-13 23:36 ` Rogério Brito
2003-11-13 23:50 ` Rogério Brito
2003-11-14 15:57 ` Alan Stern
2003-11-14 17:11 ` David Brownell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).