Re: 3.2.12: eSATA device plugin results in reset of EXTERNAL USB2.0 hub-connected devices?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Alan,

Alan Stern wrote:
> On Wed, 11 Apr 2012, Martin Mokrejs wrote:
> 
>> Hi,
>>   I did not see this for the first time, but this time I am going
>> to report this. I know there were some patches last week or two about
>> EHCI resets but please pardon me that am not sure whether they apply
>> to my case as well. Anyway, I have a Dell Vostro 3550 Laptop,
>> with a combined eSATA/USB2.0 port. An external USB2.0 hub is connected
>> to a different usb socket on the laptop case.
>>
>>   I re-plugged an external eSATA drive over eSATA to SATA cable.
>> Less than one minute ago there was another drive as ata6. I am not saying
>> this is important neither that I fiddled more with this.
>>
>>
>> Here is what I got on new plugin:
>>
>> ata6: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
>> ata6: irq_stat 0x00400040, connection status changed
>> ata6: SError: { HostInt PHYRdyChg 10B8B DevExch }
>> ata6: hard resetting link
>> ata6: SATA link down (SStatus 0 SControl 300)
>> ata6: hard resetting link
>> ata6: SATA link down (SStatus 0 SControl 300)
>> ata6: limiting SATA link speed to 1.5 Gbps
>> ata6: hard resetting link
>> ata6: SATA link down (SStatus 0 SControl 310)
>> ata6.00: disabled
>> ata6: EH complete
>> ata6.00: detaching (SCSI 5:0:0:0)
>> sd 5:0:0:0: [sdd] Synchronizing SCSI cache
>> sd 5:0:0:0: [sdd]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
>> sd 5:0:0:0: [sdd] Stopping disk
>> sd 5:0:0:0: [sdd] START_STOP FAILED
>> sd 5:0:0:0: [sdd]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
>> hub 2-1.2:1.0: port 1 disabled by hub (EMI?), re-enabling...
>> usb 2-1.2.1: USB disconnect, device number 6
>> usb 2-1.2.1: new low-speed USB device number 12 using ehci_hcd
>> usb 2-1.2.1: New USB device found, idVendor=04f2, idProduct=0116
>> usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>> usb 2-1.2.1: Product: USB Keyboard
>> usb 2-1.2.1: Manufacturer: CHICONY
>> input: CHICONY USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.0/input/input17
>> generic-usb 0003:04F2:0116.0006: input,hidraw0: USB HID v1.10 Keyboard [CHICONY USB Keyboard] on usb-0000:00:1d.0-1.2.1/input0
> 
> ...
> 
>> Can anybody explain me why USB had to be reset when eSATA device was plugged in?
> 
> The message in your log says what happened:
> 
>> hub 2-1.2:1.0: port 1 disabled by hub (EMI?), re-enabling...
> 
> Some sort of electrical noise caused the second hub to disable the port 
> that the keyboard was plugged into.

I reproduced that again, but took 3.5" drive as I thought I am dealing with
some "undercurrent" situation ... The external drive has its own power source,
and turning it on and off does not trigger the issue. Only once, after I started
up the drive and while it was spinning up its plates I plugged in the eSATA cable:


Apr 11 23:41:12 vostro kernel: ata6: hard resetting link
Apr 11 23:41:12 vostro kernel: usb 2-1.2.4: USB disconnect, device number 9
Apr 11 23:41:13 vostro kernel: usb 2-1.2.4: new low-speed USB device number 13 using ehci_hcd
Apr 11 23:41:13 vostro kernel: usb 2-1.2.4: New USB device found, idVendor=046d, idProduct=c050
Apr 11 23:41:13 vostro kernel: usb 2-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 11 23:41:13 vostro kernel: usb 2-1.2.4: Product: USB-PS/2 Optical Mouse
Apr 11 23:41:13 vostro kernel: usb 2-1.2.4: Manufacturer: Logitech
Apr 11 23:41:13 vostro kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4:1.0/input/input18
Apr 11 23:41:13 vostro kernel: generic-usb 0003:046D:C050.0007: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.2.4/input0
Apr 11 23:41:13 vostro kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 11 23:41:13 vostro kernel: ata6.00: ATA-8: ST3000DM001-9YN166, CC4C, max UDMA/133
Apr 11 23:41:13 vostro kernel: ata6.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Apr 11 23:41:13 vostro kernel: ata6.00: configured for UDMA/133
Apr 11 23:41:13 vostro kernel: ata6: EH complete
Apr 11 23:41:13 vostro kernel: scsi 5:0:0:0: Direct-Access     ATA      ST3000DM001-9YN1 CC4C PQ: 0 ANSI: 5
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: [sdd] 4096-byte physical blocks
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: Attached scsi generic sg4 type 0
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: [sdd] Write Protect is off
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 11 23:41:13 vostro kernel:  sdd: sdd1
Apr 11 23:41:13 vostro kernel: sd 5:0:0:0: [sdd] Attached SCSI disk


Ah, /var/log/messages does not have all messages seen in dmesg(1). :( Are some
written with different priority/severity?


ata6: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
ata6: irq_stat 0x00000040, connection status changed
ata6: SError: { CommWake DevExch }
ata6: hard resetting link
hub 2-1.2:1.0: port 4 disabled by hub (EMI?), re-enabling...
usb 2-1.2.4: USB disconnect, device number 9
usb 2-1.2.4: new low-speed USB device number 13 using ehci_hcd
usb 2-1.2.4: New USB device found, idVendor=046d, idProduct=c050
usb 2-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.2.4: Product: USB-PS/2 Optical Mouse
usb 2-1.2.4: Manufacturer: Logitech
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4:1.0/input/input18
generic-usb 0003:046D:C050.0007: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.2.4/input0
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: ATA-8: ST3000DM001-9YN166, CC4C, max UDMA/133
ata6.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata6.00: configured for UDMA/133
ata6: EH complete
scsi 5:0:0:0: Direct-Access     ATA      ST3000DM001-9YN1 CC4C PQ: 0 ANSI: 5
sd 5:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
sd 5:0:0:0: [sdd] 4096-byte physical blocks
sd 5:0:0:0: Attached scsi generic sg4 type 0
sd 5:0:0:0: [sdd] Write Protect is off
sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd1
sd 5:0:0:0: [sdd] Attached SCSI disk

Interesting. The external USB hub has its own power supply. So once it reset the
keyboard connection, now it reset the mouse. s it Linux making the external HUB
to reset do you think it is the external hub itself?

Thank you,
Martin
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux