From: Joerg Roedel <joro@8bytes.org>
To: Johan Hovold <johan@kernel.org>
Cc: "StarostaCZ@gmail.com" <starostacz@gmail.com>,
linux-usb@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>,
iommu@lists.linux-foundation.org
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Fri, 3 May 2019 17:37:16 +0200 [thread overview]
Message-ID: <20190503153716.GE11605@8bytes.org> (raw)
In-Reply-To: <20190429094847.GI26546@localhost>
On Mon, Apr 29, 2019 at 11:48:47AM +0200, Johan Hovold wrote:
> So this is a debian 4.18 kernel seemingly crashing due to a xhci or
> iommu issue.
>
> Can you reproduce this on a mainline kernel?
>
> If so, please post the corresponding logs to the lists and CC the xhci
> and iommu maintainers (added to CC).
Your kernel is probably missing this upstream fix:
4e50ce03976f iommu/amd: fix sg->dma_address for sg->offset bigger than PAGE_SIZE
Regards,
Joerg
next prev parent reply other threads:[~2019-05-03 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 13:47 Linux crash when using FTDI FT232R USB to serial converter on AMD boards StarostaCZ@gmail.com
2019-04-29 9:48 ` Johan Hovold
2019-04-29 10:51 ` StarostaCZ@gmail.com
2019-04-29 11:22 ` Johan Hovold
2019-04-29 11:48 ` StarostaCZ@gmail.com
2019-05-03 15:37 ` Joerg Roedel [this message]
2019-05-06 7:10 ` StarostaCZ@gmail.com
2019-05-15 7:54 ` StarostaCZ@gmail.com
2019-05-15 9:17 ` Oliver Neukum
2019-05-15 9:43 ` StarostaCZ@gmail.com
[not found] ` <3e7ec2f2-ac47-a031-96ba-fa2b9f21ed2e@gmail.com>
[not found] ` <1557913582.2950.15.camel@suse.com>
2019-05-15 11:22 ` StarostaCZ@gmail.com
[not found] ` <c57ccafd-7ad4-63e4-54c1-e1fb136ebeed@gmail.com>
[not found] ` <1557928483.2950.18.camel@suse.com>
2019-05-15 14:15 ` StarostaCZ@gmail.com
2019-05-16 7:58 ` Oliver Neukum
2019-05-16 8:20 ` StarostaCZ@gmail.com
2019-05-16 8:34 ` Oliver Neukum
2019-05-16 12:29 ` StarostaCZ@gmail.com
2019-05-16 13:11 ` Oliver Neukum
2019-05-16 13:36 ` StarostaCZ@gmail.com
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=20190503153716.GE11605@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=starostacz@gmail.com \
/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).