public inbox for iommu@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<starostacz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Mathias Nyman
	<mathias.nyman-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Mon, 29 Apr 2019 11:48:47 +0200	[thread overview]
Message-ID: <20190429094847.GI26546@localhost> (raw)
In-Reply-To: <04503197-a0a9-8b35-6c65-c10f296aab57-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, Apr 26, 2019 at 03:47:15PM +0200, StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Hello all,
> we are development and manufacturing company that use your FT232R serial 
> converter for couple of years with our software. We consume about a 
> hundreds pcs of FT232R per yer. We use FT232R as USB serial converter 
> with direct access (no virtual serial port) and as a "hardware key" 
> using FTDIChip-ID. We operate our software with FT232R converters on 
> Windows and Debian Linux operating system.
> 
> We have used Intel motherboards with Intel processors so far. We want to 
> use AMD motherboards with AMD processors too. *We made a couple of tests 
> on AMD motherboards with AMD processors and Debian Linux 9.6, but we 
> have come across a big problem.
> **When we open internal EEPROM of FT232R for reading, there will arise 
> many error messages in system log files. And then Debian Linux crash 
> after some time!*
> 
> 
> _1) Hardware configurations:_
> - motherboards with AMD A320M chipset:
>    - MSI A320M PRO-VD PLUS, 
> https://www.msi.com/Motherboard/support/A320M-PRO-VD-PLUS
>    - ASUS PRIME A320M-K, https://www.asus.com/Motherboards/PRIME-A320M-K
>    - GIGABYTE A320M-S2H, 
> https://www.gigabyte.com/Motherboard/GA-A320M-S2H-rev-1x#kf
> - latest bios installed, default bios configuration loaded,
> - CPU AMD Athlon 200GE, AMD Ryzen 3 2200G
> - 4GB RAM, SSD drive Kingston A400 120GB
> 
> _2a) Operating system A:_
> - Debian Linux 9.6 64bit, https://www.debian.org/distrib/, 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.6.0-amd64-netinst.iso
> - installed from Netinst installer WITHOUT graphic dekstop, default 
> configuration
> - tested kernels
>    - default kernel 4.9.0.8-amd64, 
> https://packages.debian.org/stretch/linux-image-4.9.0-8-amd64
>    - backports kernel 4.18.0-0.bpo.1-amd64, 
> https://packages.debian.org/stretch-backports/linux-image-4.18.0-0.bpo.1-amd64
> 
> _2b) Operating system B:_
> - Ubuntu server 19.04 64bit, http://releases.ubuntu.com/19.04/, 
> http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso
> - installed WITHOUT graphic dekstop, default configuration
> - tested kernels
>    - default kernel 5.0.0-amd64, 
> https://packages.debian.org/stretch/linux-image-4.9.0-8-amd64
>    - experimental kernel 5.0.9-050009-generic amd64, 
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.9/
> 
> _3) Drivers_
> - libftd2xx drivers version 1.4.8, https://www.ftdichip.com/Drivers/D2XX.htm
> 
> _4) Performed tests_
> You can repeat this test:
> - connect FT232R into USB2.0 port (not USB3 port!)
> - use examples in directory: ...\libftd2xx-i386-1.4.8.tar\release\examples\
> - add parameter "-m32" to "CFLAGS" variable into "Rules.make" file
> - compiled "\examples\EEPROM\user\read\"
> - run script "test.sh" - see attached file
> - *Debian Linux or Ubuntu server crashes after some minutes* - see 
> attached kernel logs from our system
> - see "kern.log" https://paste.ee/p/xxIZ2

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).

> _5) Very important note_
> *This problem occurs when FT232R is connected into USB2.0 port only!*
> When it is connected into USB3 port, all works fine, no error messages, 
> no crash.
> 
> _6) Other test that we made_
> - we made other tests on Windows 10
>    - same configuration with ASUS PRIME A320M-K motherboard
>    - latest drivers + latest FTDI drivers
>    - FT232R connected to USB2.0 or USB3 - no problem
> 
> - we made the same tests on Intel architecture (that we use now)
>    - motherboard MSI B250M PRO-VH, CPU Intel Pentium G4560, 4GB RAM, SSD 
> drive Kingston A400 120GB
>    - same operating system Debian Linux 9.6 64bit as descripted above
>    - FT232R connected to USB2.0 or USB3 - no problem

Johan

WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: "StarostaCZ@gmail.com" <starostacz@gmail.com>
Cc: linux-usb@vger.kernel.org, iommu@lists.linux-foundation.org,
	Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Mon, 29 Apr 2019 11:48:47 +0200	[thread overview]
Message-ID: <20190429094847.GI26546@localhost> (raw)
Message-ID: <20190429094847.5cRga3ik5MgHzUE9gFJJRMoE9JasOVflu3M2SHQnJCQ@z> (raw)
In-Reply-To: <04503197-a0a9-8b35-6c65-c10f296aab57@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4191 bytes --]

On Fri, Apr 26, 2019 at 03:47:15PM +0200, StarostaCZ@gmail.com wrote:
> Hello all,
> we are development and manufacturing company that use your FT232R serial 
> converter for couple of years with our software. We consume about a 
> hundreds pcs of FT232R per yer. We use FT232R as USB serial converter 
> with direct access (no virtual serial port) and as a "hardware key" 
> using FTDIChip-ID. We operate our software with FT232R converters on 
> Windows and Debian Linux operating system.
> 
> We have used Intel motherboards with Intel processors so far. We want to 
> use AMD motherboards with AMD processors too. *We made a couple of tests 
> on AMD motherboards with AMD processors and Debian Linux 9.6, but we 
> have come across a big problem.
> **When we open internal EEPROM of FT232R for reading, there will arise 
> many error messages in system log files. And then Debian Linux crash 
> after some time!*
> 
> 
> _1) Hardware configurations:_
> - motherboards with AMD A320M chipset:
>    - MSI A320M PRO-VD PLUS, 
> https://www.msi.com/Motherboard/support/A320M-PRO-VD-PLUS
>    - ASUS PRIME A320M-K, https://www.asus.com/Motherboards/PRIME-A320M-K
>    - GIGABYTE A320M-S2H, 
> https://www.gigabyte.com/Motherboard/GA-A320M-S2H-rev-1x#kf
> - latest bios installed, default bios configuration loaded,
> - CPU AMD Athlon 200GE, AMD Ryzen 3 2200G
> - 4GB RAM, SSD drive Kingston A400 120GB
> 
> _2a) Operating system A:_
> - Debian Linux 9.6 64bit, https://www.debian.org/distrib/, 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.6.0-amd64-netinst.iso
> - installed from Netinst installer WITHOUT graphic dekstop, default 
> configuration
> - tested kernels
>    - default kernel 4.9.0.8-amd64, 
> https://packages.debian.org/stretch/linux-image-4.9.0-8-amd64
>    - backports kernel 4.18.0-0.bpo.1-amd64, 
> https://packages.debian.org/stretch-backports/linux-image-4.18.0-0.bpo.1-amd64
> 
> _2b) Operating system B:_
> - Ubuntu server 19.04 64bit, http://releases.ubuntu.com/19.04/, 
> http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso
> - installed WITHOUT graphic dekstop, default configuration
> - tested kernels
>    - default kernel 5.0.0-amd64, 
> https://packages.debian.org/stretch/linux-image-4.9.0-8-amd64
>    - experimental kernel 5.0.9-050009-generic amd64, 
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.9/
> 
> _3) Drivers_
> - libftd2xx drivers version 1.4.8, https://www.ftdichip.com/Drivers/D2XX.htm
> 
> _4) Performed tests_
> You can repeat this test:
> - connect FT232R into USB2.0 port (not USB3 port!)
> - use examples in directory: ...\libftd2xx-i386-1.4.8.tar\release\examples\
> - add parameter "-m32" to "CFLAGS" variable into "Rules.make" file
> - compiled "\examples\EEPROM\user\read\"
> - run script "test.sh" - see attached file
> - *Debian Linux or Ubuntu server crashes after some minutes* - see 
> attached kernel logs from our system
> - see "kern.log" https://paste.ee/p/xxIZ2

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).

> _5) Very important note_
> *This problem occurs when FT232R is connected into USB2.0 port only!*
> When it is connected into USB3 port, all works fine, no error messages, 
> no crash.
> 
> _6) Other test that we made_
> - we made other tests on Windows 10
>    - same configuration with ASUS PRIME A320M-K motherboard
>    - latest drivers + latest FTDI drivers
>    - FT232R connected to USB2.0 or USB3 - no problem
> 
> - we made the same tests on Intel architecture (that we use now)
>    - motherboard MSI B250M PRO-VH, CPU Intel Pentium G4560, 4GB RAM, SSD 
> drive Kingston A400 120GB
>    - same operating system Debian Linux 9.6 64bit as descripted above
>    - FT232R connected to USB2.0 or USB3 - no problem

Johan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

       reply	other threads:[~2019-04-29  9:48 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   ` Johan Hovold [this message]
2019-04-29  9:48     ` Linux crash when using FTDI FT232R USB to serial converter on AMD boards 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
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=20190429094847.GI26546@localhost \
    --to=johan-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mathias.nyman-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=starostacz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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