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 15:54:43 +0200 [thread overview]
Message-ID: <1557928483.2950.18.camel@suse.com> (raw)
In-Reply-To: <c57ccafd-7ad4-63e4-54c1-e1fb136ebeed@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1156 bytes --]
On Mi, 2019-05-15 at 13:21 +0200, StarostaCZ@gmail.com wrote:
> Dne 15.5.2019 v 11:46 Oliver Neukum napsal(a):
>
>
> > Most helpful. First, try to replicate this with the iommu
> > disabled.
> >
>
> I am trying this with "iommu disabled" in bios, but system crash
> too: https://paste.ee/p/wUgHl
>
>
>
>
> > Secondly, make a proper bugreport mentioning the affected
> > kernel version (5.1)
> >
>
> How can I do this?
1. Determine whether the bug depends on the use of an IOMMU
2.Send a new report to the corresponding mailing list
>
>
>
> > Thirdly, if possible replicate this with the vanilla kernel
> > from kernel.org
> >
>
> I am afraid, that is not possible. My skills is not too good - is
> there some procedure to how do this?
>
> I made test with mainline kernel 5.1.2 from
> https://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> but computer crash on boot (kernel panic: unable to mount root
> fs...).
Your initrd has most likely not included a driver for the filesystem on
your root device.
Regards
Oliver
[-- Attachment #1.2: Type: text/html, Size: 2236 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 14:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04503197-a0a9-8b35-6c65-c10f296aab57@gmail.com>
[not found] ` <04503197-a0a9-8b35-6c65-c10f296aab57-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-29 9:48 ` Linux crash when using FTDI FT232R USB to serial converter on AMD boards 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
[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:48 ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2019-04-29 11:48 ` StarostaCZ@gmail.com
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-15 7:54 ` StarostaCZ@gmail.com
2019-05-15 9:17 ` Oliver Neukum
2019-05-15 9:43 ` StarostaCZ@gmail.com
2019-05-15 9:46 ` Oliver Neukum
2019-05-15 11:21 ` StarostaCZ@gmail.com
2019-05-15 13:54 ` Oliver Neukum [this message]
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
2019-05-15 11:22 ` 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=1557928483.2950.18.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox