From: Peter Chen <peter.chen@nxp.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
USB list <linux-usb@vger.kernel.org>,
"linux-block@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: Fri, 27 Sep 2019 09:04:19 +0000 [thread overview]
Message-ID: <20190927090640.GB2609@b29397-desktop> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1909251429370.4444-100000@netrider.rowland.org>
On 19-09-25 14:31:58, Alan Stern wrote:
> On Wed, 25 Sep 2019, Piergiorgio Sartor wrote:
>
> > 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.
>
> One thing you can try is git bisect from 5.1.20 (or maybe just 5.1.0)
> to 5.2.8. If you can identify a particular commit which caused the
> problem to start, that would help.
>
> Alan Stern
Hi Piergiorgio,
Would you please check if below patch helps?
commit 449fa54d6815be8c2c1f68fa9dbbae9384a7c03e
Author: Fugang Duan <fugang.duan@nxp.com>
Date: Fri Jul 19 17:26:48 2019 +0800
dma-direct: correct the physical addr in dma_direct_sync_sg_for_cpu/device
--
Thanks,
Peter Chen
next prev parent reply other threads:[~2019-09-27 9:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 9:54 reeze while write on external usb 3.0 hard disk [Bug 204095] Piergiorgio Sartor
2019-08-19 14:14 ` Alan Stern
2019-08-20 7:23 ` Christoph Hellwig
2019-08-20 16:37 ` Piergiorgio Sartor
2019-08-26 17:38 ` Piergiorgio Sartor
2019-08-29 14:08 ` Christoph Hellwig
2019-09-25 17:07 ` Piergiorgio Sartor
2019-09-25 18:31 ` Alan Stern
2019-09-27 9:04 ` Peter Chen [this message]
2019-09-29 20:13 ` Piergiorgio Sartor
2019-09-30 1:01 ` Alan Stern
2019-09-30 18:25 ` Piergiorgio Sartor
2019-10-13 18:11 ` Piergiorgio Sartor
2019-10-16 17:01 ` Alan Stern
2019-10-17 17:53 ` Piergiorgio Sartor
2019-10-17 19:23 ` Alan Stern
2019-11-08 23:05 ` Piergiorgio Sartor
2019-10-21 15:48 ` [PATCH] usb-storage: Revert commit 747668dbc061 ("usb-storage: Set virt_boundary_mask to avoid SG overflows") Alan Stern
2019-10-23 1:53 ` Christoph Hellwig
2019-10-23 14:12 ` Alan Stern
2019-10-23 15:34 ` [PATCH] UAS: Revert commit 3ae62a42090f ("UAS: fix alignment of scatter/gather segments") Alan Stern
2019-10-24 1:10 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190927090640.GB2609@b29397-desktop \
--to=peter.chen@nxp.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).