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]

 



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.

Alan Stern

--
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