From: "Alan J. Wylie" <alan@wylie.me.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Regression in 5.19.0: USB errors during boot
Date: Sun, 21 Aug 2022 09:21:22 +0100 [thread overview]
Message-ID: <25345.60162.942383.502797@wylie.me.uk> (raw)
In-Reply-To: <20220821062345.GA26598@lst.de>
at 08:23 on Sun 21-Aug-2022 Christoph Hellwig (hch@lst.de) wrote:
> On Thu, Aug 18, 2022 at 04:47:14PM +0200, Greg Kroah-Hartman wrote:
> > What is the output of the lspci -v for the USB 3 controller?
> >
> > Christoph, any ideas?
>
> Well, with that commit it must be related to dma ops selection.
> As this appears to be an AMD system the options here are direct,
> amd_iommu and possibly amd_gart as the odd one in the mix.
>
> Alan, can you send me your .config?
I hope that with the following information there is no need for me to
do so.
It is indeed an old AMD CPU
Model name: AMD FX(tm)-4300 Quad-Core Processor
CPU family: 21
Model: 2
Comparing with another AMD system that doesn't show the problem,
I see that CONFIG_GART_IOMMU is only set on the one with the problem.
The configs have just had "make oldconfig" run on them for years, I
have no idea why one has it set.
Clearing it fixes the problem!
Thanks for the hint, although there is a still wider issue with this
regression.
$ diff .config.old .config
353c353
< CONFIG_GART_IOMMU=y
---
> # CONFIG_GART_IOMMU is not set
4683d4682
< CONFIG_IOMMU_HELPER=y
4987d4985
< # CONFIG_IOMMU_DEBUG is not set
$
--
Alan J. Wylie https://www.wylie.me.uk/
Dance like no-one's watching. / Encrypt like everyone is.
Security is inversely proportional to convenience
next prev parent reply other threads:[~2022-08-21 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 14:36 Regression in 5.19.0: USB errors during boot Alan J. Wylie
2022-08-18 14:47 ` Greg Kroah-Hartman
2022-08-18 14:56 ` Alan J. Wylie
2022-08-21 6:23 ` Christoph Hellwig
2022-08-21 8:21 ` Alan J. Wylie [this message]
2022-08-21 14:26 ` Christoph Hellwig
2022-08-21 16:50 ` Alan J. Wylie
2022-09-08 11:18 ` Regression in 5.19.0: USB errors during boot #forregzbot Thorsten Leemhuis
2022-08-24 8:45 ` Regression in 5.19.0: USB errors during boot Thorsten Leemhuis
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=25345.60162.942383.502797@wylie.me.uk \
--to=alan@wylie.me.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).