Re: reeze while write on external usb 3.0 hard disk [Bug 204095]

From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: Christoph Hellwig <hch@lst.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	Jens Axboe <axboe@kernel.dk>,
	USB list <linux-usb@vger.kernel.org>,
	linux-block@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: reeze while write on external usb 3.0 hard disk [Bug 204095]
Date: Wed, 25 Sep 2019 19:07:41 +0200	[thread overview]
Message-ID: <20190925170741.GA5235@lazy.lzy> (raw)
In-Reply-To: <20190826173833.GA4166@lazy.lzy>

On Mon, Aug 26, 2019 at 07:38:33PM +0200, Piergiorgio Sartor wrote:
> On Tue, Aug 20, 2019 at 06:37:22PM +0200, Piergiorgio Sartor wrote:
> > On Tue, Aug 20, 2019 at 09:23:26AM +0200, Christoph Hellwig wrote:
> > > On Mon, Aug 19, 2019 at 10:14:25AM -0400, Alan Stern wrote:
> > > > Let's bring this to the attention of some more people.
> > > > 
> > > > It looks like the bug that was supposed to be fixed by commit
> > > > d74ffae8b8dd ("usb-storage: Add a limitation for
> > > > blk_queue_max_hw_sectors()"), which is part of 5.2.5, but apparently
> > > > the bug still occurs.
> > > 
> > > Piergiorgio,
> > > 
> > > can you dump the content of max_hw_sectors_kb file for your USB storage
> > > device and send that to this thread?
> > 
> > Hi all,
> > 
> > for both kernels, 5.1.20 (working) and 5.2.8 (not working),
> > the content of /sys/dev/x:y/queue/max_hw_sectors_kb is 512
> > for USB storage devices (2.0 and 3.0).
> > 
> > This is for the PC showing the issue.
> > 
> > In an other PC, which does not show the issus at the moment,
> > the values are 120, for USB2.0, and 256, for USB3.0.
> 
> Hi again,
> 
> any news on this?
> 
> Is there anything I can do to help?
> 
> Should I report this somewhere else too?
> 
> Currently this is quite a huge problem for me,
> since the only working external storage is an
> old 1394 HDD...

Hi all,

I'm now on kernel 5.2.16, from Fedora, and still I
see the same issue.

I guess it is not a chipset quirk, since there
are two involved here.
For the USB 2.0 I've (with "lspci"):

USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])

For USB 3.0 I've:

USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI])

Any idea on how to proceed?

Thanks a lot.

bye,

-- 

piergiorgio