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:17:36 +0200 [thread overview]
Message-ID: <1557911856.2950.10.camel@suse.com> (raw)
In-Reply-To: <4e7f0267-eba8-81c3-4036-25924ea9df98@gmail.com>
On Mi, 2019-05-15 at 09:54 +0200, StarostaCZ@gmail.com wrote:
> Hello,
> can I still help with this problem? It's very important for us. Thank you.
Your first step would be t verify whether your kernel has the
fix coming in the patch Joerg mentioned.
Regards
Oliver
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Neukum <oneukum@suse.com>
To: "StarostaCZ@gmail.com" <starostacz@gmail.com>,
Joerg Roedel <joro@8bytes.org>, Johan Hovold <johan@kernel.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
iommu@lists.linux-foundation.org, linux-usb@vger.kernel.org
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Wed, 15 May 2019 11:17:36 +0200 [thread overview]
Message-ID: <1557911856.2950.10.camel@suse.com> (raw)
In-Reply-To: <4e7f0267-eba8-81c3-4036-25924ea9df98@gmail.com>
On Mi, 2019-05-15 at 09:54 +0200, StarostaCZ@gmail.com wrote:
> Hello,
> can I still help with this problem? It's very important for us. Thank you.
Your first step would be t verify whether your kernel has the
fix coming in the patch Joerg mentioned.
Regards
Oliver
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 [this message]
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
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=1557911856.2950.10.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.