From: Oliver Neukum <oneukum@suse.com>
To: "StarostaCZ@gmail.com" <starostacz@gmail.com>,
Joerg Roedel <joro@8bytes.org>, Johan Hovold <johan@kernel.org>
Cc: iommu@lists.linux-foundation.org, linux-usb@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Wed, 15 May 2019 11:46:22 +0200 [thread overview]
Message-ID: <1557913582.2950.15.camel@suse.com> (raw)
In-Reply-To: <3e7ec2f2-ac47-a031-96ba-fa2b9f21ed2e@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1045 bytes --]
On Mi, 2019-05-15 at 11:43 +0200, StarostaCZ@gmail.com wrote:
> As I wrote, I made new test on kernel Linux version
> 5.1.0-050100-generic amd64:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1/
>
> Same problem, system crash after a few seconds. Full kern.log: https://paste.ee/p/EmLsw
Most helpful. First, try to replicate this with the iommu disabled.
Secondly, make a proper bugreport mentioning the affected kernel version (5.1)
Thirdly, if possible replicate this with the vanilla kernel from kernel.org
>
>
> Unfortunately, I can't judge if the patch is there, but
> I found, that this patch was added to kernel 5.0.2:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/iommu/amd_iommu.c?id=4e50ce03976fbc8ae995a000c4b10c737467beaa
>
> Can I somehow
> verify that the patch is in this ubuntu kernel 5.1.0?
You would need to look into the kernel source, but this is not necessary.
Joerg's guess was incorrect.
Regards
Oliver
[-- Attachment #1.2: Type: text/html, Size: 2186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-05-15 10:48 UTC|newest]
Thread overview: 44+ 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
[not found] ` <04503197-a0a9-8b35-6c65-c10f296aab57-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-29 9:48 ` Johan Hovold
2019-04-29 9:48 ` Johan Hovold
2019-04-29 9:48 ` Johan Hovold
2019-04-29 10:51 ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2019-04-29 10:51 ` StarostaCZ@gmail.com
2019-04-29 10:51 ` StarostaCZ@gmail.com
[not found] ` <26c4a175-dae2-3410-6924-92fe7c8ec6fe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-29 11:22 ` Johan Hovold
2019-04-29 11:22 ` Johan Hovold
2019-04-29 11:22 ` Johan Hovold
2019-04-29 11:48 ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2019-04-29 11:48 ` StarostaCZ@gmail.com
2019-04-29 11:48 ` StarostaCZ@gmail.com
2019-05-03 15:37 ` Joerg Roedel
2019-05-03 15:37 ` Joerg Roedel
2019-05-06 7:09 ` StarostaCZ@gmail.com
2019-05-06 7:10 ` StarostaCZ@gmail.com
2019-05-06 7:10 ` StarostaCZ@gmail.com
2019-05-15 7:54 ` StarostaCZ@gmail.com
2019-05-15 7:54 ` StarostaCZ@gmail.com
2019-05-15 9:17 ` Oliver Neukum
2019-05-15 9:17 ` Oliver Neukum
2019-05-15 9:43 ` StarostaCZ@gmail.com
2019-05-15 9:46 ` Oliver Neukum [this message]
2019-05-15 11:21 ` StarostaCZ@gmail.com
2019-05-15 13:54 ` Oliver Neukum
2019-05-15 14:15 ` StarostaCZ@gmail.com
2019-05-15 14:15 ` StarostaCZ@gmail.com
2019-05-16 7:58 ` Oliver Neukum
2019-05-16 7:58 ` Oliver Neukum
2019-05-16 8:20 ` StarostaCZ@gmail.com
2019-05-16 8:20 ` StarostaCZ@gmail.com
2019-05-16 8:34 ` Oliver Neukum
2019-05-16 8:34 ` Oliver Neukum
2019-05-16 12:29 ` StarostaCZ@gmail.com
2019-05-16 12:29 ` StarostaCZ@gmail.com
2019-05-16 13:11 ` Oliver Neukum
2019-05-16 13:11 ` Oliver Neukum
2019-05-16 13:36 ` StarostaCZ@gmail.com
2019-05-16 13:36 ` StarostaCZ@gmail.com
2019-05-15 11:22 ` StarostaCZ@gmail.com
2019-05-15 11:22 ` StarostaCZ@gmail.com
2019-05-15 9:43 ` StarostaCZ@gmail.com
2019-05-15 9:43 ` 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=1557913582.2950.15.camel@suse.com \
--to=oneukum@suse.com \
--cc=iommu@lists.linux-foundation.org \
--cc=johan@kernel.org \
--cc=joro@8bytes.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.