Bug#782442: USB3 external HDD not recognized [regression]

[Lu, Baolu]

On 06/06/2015 04:56 AM, Ralf Jung wrote:

Hi,


I got some untested and not yet reviewed usb3 resume race fixes from Zhuang Jin 
Can
If you can try them out and see if they help it would be great.
They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
(5 extra patches on top of current usb-linus)

git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git xhci_usb3_pm_fixes

This is my production and (main and only) work machine. If you tell me
testing that branch is safe and won't mess up my file systems or
hardware, I can give it a try.


I tested that branch (HEAD commit 190f6b0b), and the issue is still the
same. Directly after booting, if I plug in the disk, it doesn't work
(with the "root hub lost power" error). Removing the cable, setting
power/control to "on" for all PCI devices, then plugging it back in, the
disk works fine.


"root hub lost power" is not an error message. It shows when host controller
needs to reset on a resume.

Do you mind sending a dmesg data with usbcore and xhci_hcd dynamic debug
enabled? Sorry if you have posted one.

echo -n 'module xhci_hcd +p' > /sys/kernel/debug/dynamic_debug/control
echo -n 'module usbcore +p' > /sys/kernel/debug/dynamic_debug/control

Thanks,
Baolu




What was the  model of the USB3 disk again? some Seagate Expansion Disk?
I'll see If I can find one of those myself somehow

lsusb says:
Bus 003 Device 002: ID 0bc2:3312 Seagate RSS LLC

The package says "Seagate Expansion 5TB". But I'm not sure these are all
using the same controller; for example, I also have a "Seagate Expansion
3TB" that works fine.

(I'm removing Wang, Yu  from the recipients, as I
keep getting bounces from that address.)

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




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi,

>>> I got some untested and not yet reviewed usb3 resume race fixes from Zhuang 
>>> Jin Can
>>> If you can try them out and see if they help it would be great.
>>> They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
>>> (5 extra patches on top of current usb-linus)
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git 
>>> xhci_usb3_pm_fixes
>>
>> This is my production and (main and only) work machine. If you tell me
>> testing that branch is safe and won't mess up my file systems or
>> hardware, I can give it a try.
>>

I tested that branch (HEAD commit 190f6b0b), and the issue is still the
same. Directly after booting, if I plug in the disk, it doesn't work
(with the "root hub lost power" error). Removing the cable, setting
power/control to "on" for all PCI devices, then plugging it back in, the
disk works fine.

> What was the  model of the USB3 disk again? some Seagate Expansion Disk?
> I'll see If I can find one of those myself somehow

lsusb says:
Bus 003 Device 002: ID 0bc2:3312 Seagate RSS LLC

The package says "Seagate Expansion 5TB". But I'm not sure these are all
using the same controller; for example, I also have a "Seagate Expansion
3TB" that works fine.

(I'm removing Wang, Yu  from the recipients, as I
keep getting bounces from that address.)

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Mathias Nyman]

On 02.06.2015 15:59, Ralf Jung wrote:
> Hi,
> 
 Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
 fixes the problem: When I subsequently plug in the disk, it is
 recognized correctly. I confirmed this with an older kernel (the 3.16
 Debian kernel, to be more precise). That's good to know, now I don't
 need to reboot to a different kernel anymore to do fast backups ;-)
>>>
>>> Is there any news on this? Any further information I can provide to help
>>> fix the issue?
>>>
>>
>> I got some untested and not yet reviewed usb3 resume race fixes from Zhuang 
>> Jin Can
>> If you can try them out and see if they help it would be great.
>> They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
>> (5 extra patches on top of current usb-linus)
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git 
>> xhci_usb3_pm_fixes
> 
> This is my production and (main and only) work machine. If you tell me
> testing that branch is safe and won't mess up my file systems or
> hardware, I can give it a try.
> 

Can't give any guarantees, the five additional patches only touch usb resume 
code, and
it's based on Greg's usb-linus tree.

What was the  model of the USB3 disk again? some Seagate Expansion Disk?
I'll see If I can find one of those myself somehow

-Mathias
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi,

>>> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
>>> fixes the problem: When I subsequently plug in the disk, it is
>>> recognized correctly. I confirmed this with an older kernel (the 3.16
>>> Debian kernel, to be more precise). That's good to know, now I don't
>>> need to reboot to a different kernel anymore to do fast backups ;-)
>>
>> Is there any news on this? Any further information I can provide to help
>> fix the issue?
>>
> 
> I got some untested and not yet reviewed usb3 resume race fixes from Zhuang 
> Jin Can
> If you can try them out and see if they help it would be great.
> They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
> (5 extra patches on top of current usb-linus)
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git 
> xhci_usb3_pm_fixes

This is my production and (main and only) work machine. If you tell me
testing that branch is safe and won't mess up my file systems or
hardware, I can give it a try.

Kind regards,
Ralf

> 
> If not, then the we need to change xhci resume code so that we resume the 
> roothubs as default
> except if we are runtime suspended and woken up just to be (system) suspended.
> 
> -Mathias
> 
> 
>  
> 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Mathias Nyman]

Hi

On 29.05.2015 15:35, Ralf Jung wrote:
> Hi again,
> 
>> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
>> fixes the problem: When I subsequently plug in the disk, it is
>> recognized correctly. I confirmed this with an older kernel (the 3.16
>> Debian kernel, to be more precise). That's good to know, now I don't
>> need to reboot to a different kernel anymore to do fast backups ;-)
> 
> Is there any news on this? Any further information I can provide to help
> fix the issue?
> 

I got some untested and not yet reviewed usb3 resume race fixes from Zhuang Jin 
Can
If you can try them out and see if they help it would be great.
They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
(5 extra patches on top of current usb-linus)

git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git xhci_usb3_pm_fixes

If not, then the we need to change xhci resume code so that we resume the 
roothubs as default
except if we are runtime suspended and woken up just to be (system) suspended.

-Mathias


 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi again,

> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
> fixes the problem: When I subsequently plug in the disk, it is
> recognized correctly. I confirmed this with an older kernel (the 3.16
> Debian kernel, to be more precise). That's good to know, now I don't
> need to reboot to a different kernel anymore to do fast backups ;-)

Is there any news on this? Any further information I can provide to help
fix the issue?

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi,

> Attached a testpatch based on 4.1-rc2

Thanks. Unfortunately, this patch did not help: I saw no change in
behavior compared to vanilla 4.1-rc2.

I should probably mention that there is a slight difference in the log
output of the 3.16 and 4.1 kernels: The "xhci_hcd :04:00.0: irq 42
for MSI/MSI-X" messages only show up with the older kernels.

>> ACTION=="add", SUBSYSTEM=="pci", ATTR{power/control}="auto"
>>
>> Sorry that I forgot to mention this.
> 
> No worries, we need to get the usb3 drive detected even if the controller is 
> in runtime suspend.

Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
fixes the problem: When I subsequently plug in the disk, it is
recognized correctly. I confirmed this with an older kernel (the 3.16
Debian kernel, to be more precise). That's good to know, now I don't
need to reboot to a different kernel anymore to do fast backups ;-)

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Mathias Nyman]

On 11.05.2015 17:44, Ralf Jung wrote:
> Hi,
> 
>> Ok, xhci is reset in resume in your case (indicated by the "root hub lost 
>> power or was reset" messages)
>> That patch adds an additional check that ensures there was some event before 
>> resuming the roothub.
>>
>> Could you try out the following and see if it helps? If the event is 
>> lost/cleared during reset
>> then this change should work.
> 
> Sure. What version is this patch against? I did "patch -p1" with
> v4.1-rc2 checked out, and all three hunks fail.
> 

Attached a testpatch based on 4.1-rc2

>> Can you try with auto-pm disabled for PCI xHCI host?
>>
>> # echo 'on' | tee /sys/bus/pci/devices/*/power/control 
> 
> I'll also try the PM settings mentioned by baolu. In fact, he reminded
> me that I added the following udev rule to save some power (and powertop
> got happy ;-):
> 
> ACTION=="add", SUBSYSTEM=="pci", ATTR{power/control}="auto"
> 
> Sorry that I forgot to mention this.

No worries, we need to get the usb3 drive detected even if the controller is in 
runtime suspend.

-Mathias 


>From 7e0326dd33ab53edef694cb2ec0a4d6ec46b9c97 Mon Sep 17 00:00:00 2001
From: Mathias Nyman 
Date: Tue, 12 May 2015 13:40:34 +0300
Subject: [PATCH] xhci: check if roothubs need to be resumed early in xhci
 resume

Testpatch for Ralf Jung to check if we got a pending event interrupt
early when resuming the host, and make sure resume the roothubs in that case.

A theory is that the cases we need to re-initialize the xhci host in resume we
will lose the event interrupt, and refuse to resume the roothubs as there are
no pending event to handle.

Signed-off-by: Mathias Nyman 
---
 drivers/usb/host/xhci.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index ec8ac16..2e0d6ba 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -982,6 +982,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
 	struct usb_hcd		*secondary_hcd;
 	int			retval = 0;
 	bool			comp_timer_running = false;
+	int			resume_hubs;
 
 	/* Wait a bit if either of the roothubs need to settle from the
 	 * transition into bus suspend.
@@ -1017,6 +1018,8 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
 		temp = readl(&xhci->op_regs->status);
 	}
 
+	resume_hubs = readl(&xhci->op_regs->status) & STS_EINT;
+
 	/* If restore operation fails, re-initialize the HC during resume */
 	if ((temp & STS_SRE) || hibernated) {
 
@@ -1097,7 +1100,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
 	if (retval == 0) {
 		/* Resume root hubs only when have pending events. */
 		status = readl(&xhci->op_regs->status);
-		if (status & STS_EINT) {
+		if (status & STS_EINT || resume_hubs) {
 			usb_hcd_resume_root_hub(hcd);
 			usb_hcd_resume_root_hub(xhci->shared_hcd);
 		}
-- 
1.8.3.2

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi,

> Ok, xhci is reset in resume in your case (indicated by the "root hub lost 
> power or was reset" messages)
> That patch adds an additional check that ensures there was some event before 
> resuming the roothub.
> 
> Could you try out the following and see if it helps? If the event is 
> lost/cleared during reset
> then this change should work.

Sure. What version is this patch against? I did "patch -p1" with
v4.1-rc2 checked out, and all three hunks fail.

> Can you try with auto-pm disabled for PCI xHCI host?
> 
> # echo 'on' | tee /sys/bus/pci/devices/*/power/control 

I'll also try the PM settings mentioned by baolu. In fact, he reminded
me that I added the following udev rule to save some power (and powertop
got happy ;-):

ACTION=="add", SUBSYSTEM=="pci", ATTR{power/control}="auto"

Sorry that I forgot to mention this.

(I'll do all this tomorrow.)

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Mathias Nyman]

Hi

Thanks for bringing this to my attention. 

On 10.05.2015 18:08, Alan Stern wrote:
> Sending to author of the offending commit and maintainer of the 
> xhci-hcd driver.
> 
> On Sat, 9 May 2015, Ralf Jung wrote:
> 
>> Hi,
>>
>> I did a bisect on these files only, and here's the result:
>>
>>> d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit
>>> commit d6236f6d1d885aa19d1cd7317346fe795227a3cc
>>> Author: Wang, Yu 
>>> Date:   Tue Jun 24 17:14:44 2014 +0300
>>>
>>> xhci: Fix runtime suspended xhci from blocking system suspend.
>>
>> I confirmed that reverting this commit on top of v3.16 indeed fixes the
>> issue.

Ok, xhci is reset in resume in your case (indicated by the "root hub lost power 
or was reset" messages)
That patch adds an additional check that ensures there was some event before 
resuming the roothub.

Could you try out the following and see if it helps? If the event is 
lost/cleared during reset
then this change should work.

diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 52acd1d..75db3ad 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -982,6 +982,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
struct usb_hcd  *secondary_hcd;
int retval = 0;
boolcomp_timer_running = false;
+   int resume_hubs = 0;
 
/* Wait a bit if either of the roothubs need to settle from the
 * transition into bus suspend.
@@ -1017,6 +1018,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
temp = readl(&xhci->op_regs->status);
}
 
+   resume_hubs = readl(&xhci->op_regs->status) & STS_EINT;
/* If restore operation fails, re-initialize the HC during resume */
if ((temp & STS_SRE) || hibernated) {
 
@@ -1097,7 +1099,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
if (retval == 0) {
/* Resume root hubs only when have pending events. */
status = readl(&xhci->op_regs->status);
-   if (status & STS_EINT) {
+   if (status & STS_EINT || resume_hubs) {
usb_hcd_resume_root_hub(hcd);
usb_hcd_resume_root_hub(xhci->shared_hcd);
}

-Mathias


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Alan Stern]

Sending to author of the offending commit and maintainer of the 
xhci-hcd driver.

Alan Stern

On Sat, 9 May 2015, Ralf Jung wrote:

> Hi,
> 
> > The USB-3 driver is made up of these files:  drivers/usb/host/xhci*
> 
> I did a bisect on these files only, and here's the result:
> 
> > d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit
> > commit d6236f6d1d885aa19d1cd7317346fe795227a3cc
> > Author: Wang, Yu 
> > Date:   Tue Jun 24 17:14:44 2014 +0300
> > 
> > xhci: Fix runtime suspended xhci from blocking system suspend.
> 
> I confirmed that reverting this commit on top of v3.16 indeed fixes the
> issue.
> 
> (Just to remind you, the context is the following bug report:
> ).
> 
> Kind regards,
> Ralf

> I just tested the v4.1-rc2 kernel to confirm that the issue is still
> present. Reverting above commit again fixed the issue.
>
> Please let me know if there is any other information you need from me.
>
> Kind regards,
> Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi again,

>> d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit
>> commit d6236f6d1d885aa19d1cd7317346fe795227a3cc
>> Author: Wang, Yu 
>> Date:   Tue Jun 24 17:14:44 2014 +0300
>>
>> xhci: Fix runtime suspended xhci from blocking system suspend.
> 
> I confirmed that reverting this commit on top of v3.16 indeed fixes the
> issue.

I just tested the v4.1-rc2 kernel to confirm that the issue is still
present. Reverting above commit again fixed the issue.

Please let me know if there is any other information you need from me.

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi,

> The USB-3 driver is made up of these files:  drivers/usb/host/xhci*

I did a bisect on these files only, and here's the result:

> d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit
> commit d6236f6d1d885aa19d1cd7317346fe795227a3cc
> Author: Wang, Yu 
> Date:   Tue Jun 24 17:14:44 2014 +0300
> 
> xhci: Fix runtime suspended xhci from blocking system suspend.

I confirmed that reverting this commit on top of v3.16 indeed fixes the
issue.

(Just to remind you, the context is the following bug report:
).

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Alan Stern]

On Wed, 15 Apr 2015, Ralf Jung wrote:

> Hi all,
> 
> One of my external hard disks does not work anymore with current
> kernels, when I plug it into my USB3 port.

...

> I can do a git bisect when I am back from travel (in ~1 week), but I
> would appreciate some guess of which folder I should restrict the bisect
> to - otherwise, this would take way too long.

The USB-3 driver is made up of these files:  drivers/usb/host/xhci*

Alan Stern


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782442: USB3 external HDD not recognized [regression]

[Ralf Jung]

Hi all,

One of my external hard disks does not work anymore with current
kernels, when I plug it into my USB3 port.

Steps to reproduce:
* Boot the system without the disk being connected
* Plug the disk into my Laptop's USB3 port
* Watch dmesg and my DE's removable media notification

Behavior with kernel v3.16:
The following repeats in dmesg:

> bad (new kernel) dmesg start <<
[   62.057690] usb usb2: root hub lost power or was reset
[   62.057699] usb usb3: root hub lost power or was reset
[   62.062338] xhci_hcd :04:00.0: irq 42 for MSI/MSI-X
[   62.062357] xhci_hcd :04:00.0: irq 43 for MSI/MSI-X
[   62.062373] xhci_hcd :04:00.0: irq 44 for MSI/MSI-X
[   62.062390] xhci_hcd :04:00.0: irq 45 for MSI/MSI-X
[   62.062405] xhci_hcd :04:00.0: irq 46 for MSI/MSI-X
> bad (new kernel) dmesg end <<

The disk is not recognized. It spins up though, so it seems to notice
that there is "something" at the other end of the cable. When I call
"lsusb" with the disk connected (while the kernel prints all these
errors), no additional device shows up.

Behavior with v3.15 and older kernels (I tried v3.14):
The disk is recognized correctly, and I can access my data at USB3 speed.
Here's the dmesg that is printed in that case:

> successfull (old kernel) dmesg start <<
[   37.930632] usb usb1: root hub lost power or was reset
[   37.930641] usb usb3: root hub lost power or was reset
[   37.935270] xhci_hcd :04:00.0: irq 43 for MSI/MSI-X
[   37.935290] xhci_hcd :04:00.0: irq 44 for MSI/MSI-X
[   37.935308] xhci_hcd :04:00.0: irq 45 for MSI/MSI-X
[   37.935324] xhci_hcd :04:00.0: irq 46 for MSI/MSI-X
[   37.935338] xhci_hcd :04:00.0: irq 47 for MSI/MSI-X
[   38.258763] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd
[   38.275187] usb 3-1: Parent hub missing LPM exit latency info.  Power
management will be impacted.
[   38.276132] usb 3-1: New USB device found, idVendor=0bc2, idProduct=3312
[   38.276140] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[   38.276144] usb 3-1: Product: Expansion Desk
[   38.276148] usb 3-1: Manufacturer: Seagate
[   38.276152] usb 3-1: SerialNumber: NA4NANTR
[   38.301581] usb-storage 3-1:1.0: USB Mass Storage device detected
[   38.301753] scsi7 : usb-storage 3-1:1.0
[   38.301905] usbcore: registered new interface driver usb-storage
[   39.300862] scsi 7:0:0:0: Direct-Access Seagate  Expansion Desk
 0739 PQ: 0 ANSI: 6
[   39.301577] sd 7:0:0:0: Attached scsi generic sg3 type 0
[   39.303473] sd 7:0:0:0: [sdd] Spinning up disk...
[   44.758288] .ready
[   52.799760] sd 7:0:0:0: [sdd] 1220942645 4096-byte logical blocks:
(5.00 TB/4.54 TiB)
[   52.800311] sd 7:0:0:0: [sdd] Write Protect is off
[   52.800314] sd 7:0:0:0: [sdd] Mode Sense: 2b 00 10 08
[   52.800857] sd 7:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, supports DPO and FUA
[   52.801638] sd 7:0:0:0: [sdd] 1220942645 4096-byte logical blocks:
(5.00 TB/4.54 TiB)
[   53.080785]  sdd: sdd1

[   53.081595] sd 7:0:0:0: [sdd] 1220942645 4096-byte logical blocks:
(5.00 TB/4.54 TiB)
[   53.082717] sd 7:0:0:0: [sdd] Attached SCSI disk
> successfull (old kernel) dmesg end <<

Further information:
I reported this bug in Debian first, at
. That page
contains a lot of automatically gathered information about my laptop
model, loaded drivers, etc.  I added the bug to CC - I hope thats okay.
Interestingly, the bug already appears in version 3.14 of the Debian
kernels (but not in 3.13). My assumption here is that it was introduced
by some patch that Debian already applied with 3.14, but only landed
upstream with 3.16.
I also reported this in the Kernel bugzilla at
.

With all kernels I tried, if I connect the same disk to a USB2 port, it
works all right. But of course, disk access is much slower then.

The USB3 port also sometimes makes problems with other devices, but
that's way less reproducible - hence I am concentrating on this
particular disk. In particular, after unsuccessfully connecting the disk
to the USB3 port, with high likelihood, no USB device whatsoever will
work on that port until a reboot.

I can do a git bisect when I am back from travel (in ~1 week), but I
would appreciate some guess of which folder I should restrict the bisect
to - otherwise, this would take way too long.

Please keep me in CC, as I am not subscribed to the list.

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org