* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
[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
` (2 more replies)
0 siblings, 3 replies; 26+ messages in thread
From: Johan Hovold @ 2019-04-29 9:48 UTC (permalink / raw)
To: StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA, Mathias Nyman
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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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-05-03 15:37 ` Joerg Roedel
2 siblings, 0 replies; 26+ messages in thread
From: Johan Hovold @ 2019-04-29 9:48 UTC (permalink / raw)
To: StarostaCZ@gmail.com; +Cc: linux-usb, iommu, Mathias Nyman
[-- 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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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-05-03 15:37 ` Joerg Roedel
2 siblings, 2 replies; 26+ messages in thread
From: StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org @ 2019-04-29 10:51 UTC (permalink / raw)
To: Johan Hovold
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA, Mathias Nyman
Hello,
sorry for other questions, but I am new in this list:
Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
test?
Can I add attachments to this lists?
And who is xhci and iommu maintainers? Are they CC in this mail?
starosta
Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
> 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).
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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>
1 sibling, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-04-29 10:51 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb, iommu, Mathias Nyman
Hello,
sorry for other questions, but I am new in this list:
Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
test?
Can I add attachments to this lists?
And who is xhci and iommu maintainers? Are they CC in this mail?
starosta
Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
> 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).
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
[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
0 siblings, 2 replies; 26+ messages in thread
From: Johan Hovold @ 2019-04-29 11:22 UTC (permalink / raw)
To: StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA, Johan Hovold, Mathias Nyman,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA
On Mon, Apr 29, 2019 at 12:51:20PM +0200, StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Hello,
> sorry for other questions, but I am new in this list:
> Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
> test?
Yes, that might do depending on what else debian put in that kernel.
> Can I add attachments to this lists?
Sure, it's even preferred. Just try to trim non-relevant bits, and
perhaps provide a link to the full log.
> And who is xhci and iommu maintainers? Are they CC in this mail?
Yes, that's Mathias and Joerg, respectively, that I added on CC.
> Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
> > 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).
Here's an excerpt from the 4.18 log meanwhile:
[ 0.000000] Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13)
...
[ 960.145603] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 1790.293623] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff50000 flags=0x0020]
[ 1790.300905] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fde9e000 flags=0x0020]
...
[ 4789.145364] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 4789.310916] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff63c000 flags=0x0020]
[ 4789.317023] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff5c6000 flags=0x0020]
[ 4789.702446] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 4789.766842] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fdeaf000 flags=0x0020]
[ 4789.781531] AMD-Vi: Event logged [IO_PAGE_FAULT device=15:00.0 domain=0x0000 address=0x00000000fdeaf040 flags=0x0020]
[ 4790.093644] general protection fault: 0000 [#1] SMP NOPTI
[ 4790.094186] CPU: 2 PID: 24561 Comm: readua Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
[ 4790.094738] Hardware name: Micro-Star International Co., Ltd MS-7B38/A320M PRO-VD PLUS (MS-7B38), BIOS 1.C0 11/02/2018
[ 4790.095333] RIP: 0010:prefetch_freepointer+0x10/0x20
[ 4790.095936] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
[ 4790.097314] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
[ 4790.098016] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
[ 4790.098711] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
[ 4790.099413] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
[ 4790.100141] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
[ 4790.100871] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
[ 4790.101619] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
[ 4790.102387] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 4790.103157] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
[ 4790.103954] Call Trace:
[ 4790.104753] kmem_cache_alloc_trace+0xb5/0x1c0
[ 4790.105580] ? proc_do_submiturb+0x35a/0xda0 [usbcore]
[ 4790.106382] proc_do_submiturb+0x35a/0xda0 [usbcore]
[ 4790.107189] ? futex_wake+0x94/0x170
[ 4790.108009] proc_submiturb_compat+0xb1/0xe0 [usbcore]
[ 4790.108851] usbdev_do_ioctl+0x894/0x1170 [usbcore]
[ 4790.109704] usbdev_compat_ioctl+0xc/0x10 [usbcore]
[ 4790.110553] __ia32_compat_sys_ioctl+0xc0/0x250
[ 4790.111413] do_fast_syscall_32+0x98/0x1e0
[ 4790.112280] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
[ 4790.113167] Modules linked in: ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c iptable_filter binfmt_misc nls_ascii nls_cp437 vfat fat efi_pstore edac_mce_amd ccp rng_core kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_intel ghash_clmulni_intel wmi_bmof snd_hda_codec efivars pcspkr snd_hda_core snd_hwdep snd_pcm k10temp snd_timer sg snd soundcore sp5100_tco evdev pcc_cpufreq acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod hid_generic usbhid hid crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper amdgpu ch
ash gpu_sched
[ 4790.120417] i2c_algo_bit i2c_piix4 ttm drm_kms_helper ahci xhci_pci libahci xhci_hcd drm libata r8169 mii usbcore scsi_mod usb_common wmi video gpio_amdpt gpio_generic button
[ 4790.122857] ---[ end trace bdd21237253335ac ]---
[ 4791.452933] RIP: 0010:prefetch_freepointer+0x10/0x20
[ 4791.461318] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
[ 4791.479889] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
[ 4791.490112] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
[ 4791.500551] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
[ 4791.509946] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
[ 4791.519575] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
[ 4791.530038] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
[ 4791.541665] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
[ 4791.544526] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 4791.546019] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
Johan
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-04-29 11:22 ` Johan Hovold
@ 2019-04-29 11:22 ` Johan Hovold
2019-04-29 11:48 ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
1 sibling, 0 replies; 26+ messages in thread
From: Johan Hovold @ 2019-04-29 11:22 UTC (permalink / raw)
To: StarostaCZ@gmail.com; +Cc: linux-usb, Johan Hovold, Mathias Nyman, iommu
On Mon, Apr 29, 2019 at 12:51:20PM +0200, StarostaCZ@gmail.com wrote:
> Hello,
> sorry for other questions, but I am new in this list:
> Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
> test?
Yes, that might do depending on what else debian put in that kernel.
> Can I add attachments to this lists?
Sure, it's even preferred. Just try to trim non-relevant bits, and
perhaps provide a link to the full log.
> And who is xhci and iommu maintainers? Are they CC in this mail?
Yes, that's Mathias and Joerg, respectively, that I added on CC.
> Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
> > 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).
Here's an excerpt from the 4.18 log meanwhile:
[ 0.000000] Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13)
...
[ 960.145603] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 1790.293623] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff50000 flags=0x0020]
[ 1790.300905] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fde9e000 flags=0x0020]
...
[ 4789.145364] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 4789.310916] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff63c000 flags=0x0020]
[ 4789.317023] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff5c6000 flags=0x0020]
[ 4789.702446] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 4789.766842] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fdeaf000 flags=0x0020]
[ 4789.781531] AMD-Vi: Event logged [IO_PAGE_FAULT device=15:00.0 domain=0x0000 address=0x00000000fdeaf040 flags=0x0020]
[ 4790.093644] general protection fault: 0000 [#1] SMP NOPTI
[ 4790.094186] CPU: 2 PID: 24561 Comm: readua Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
[ 4790.094738] Hardware name: Micro-Star International Co., Ltd MS-7B38/A320M PRO-VD PLUS (MS-7B38), BIOS 1.C0 11/02/2018
[ 4790.095333] RIP: 0010:prefetch_freepointer+0x10/0x20
[ 4790.095936] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
[ 4790.097314] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
[ 4790.098016] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
[ 4790.098711] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
[ 4790.099413] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
[ 4790.100141] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
[ 4790.100871] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
[ 4790.101619] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
[ 4790.102387] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 4790.103157] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
[ 4790.103954] Call Trace:
[ 4790.104753] kmem_cache_alloc_trace+0xb5/0x1c0
[ 4790.105580] ? proc_do_submiturb+0x35a/0xda0 [usbcore]
[ 4790.106382] proc_do_submiturb+0x35a/0xda0 [usbcore]
[ 4790.107189] ? futex_wake+0x94/0x170
[ 4790.108009] proc_submiturb_compat+0xb1/0xe0 [usbcore]
[ 4790.108851] usbdev_do_ioctl+0x894/0x1170 [usbcore]
[ 4790.109704] usbdev_compat_ioctl+0xc/0x10 [usbcore]
[ 4790.110553] __ia32_compat_sys_ioctl+0xc0/0x250
[ 4790.111413] do_fast_syscall_32+0x98/0x1e0
[ 4790.112280] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
[ 4790.113167] Modules linked in: ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c iptable_filter binfmt_misc nls_ascii nls_cp437 vfat fat efi_pstore edac_mce_amd ccp rng_core kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_intel ghash_clmulni_intel wmi_bmof snd_hda_codec efivars pcspkr snd_hda_core snd_hwdep snd_pcm k10temp snd_timer sg snd soundcore sp5100_tco evdev pcc_cpufreq acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod hid_generic usbhid hid crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper amdgpu chash gpu_sched
[ 4790.120417] i2c_algo_bit i2c_piix4 ttm drm_kms_helper ahci xhci_pci libahci xhci_hcd drm libata r8169 mii usbcore scsi_mod usb_common wmi video gpio_amdpt gpio_generic button
[ 4790.122857] ---[ end trace bdd21237253335ac ]---
[ 4791.452933] RIP: 0010:prefetch_freepointer+0x10/0x20
[ 4791.461318] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
[ 4791.479889] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
[ 4791.490112] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
[ 4791.500551] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
[ 4791.509946] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
[ 4791.519575] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
[ 4791.530038] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
[ 4791.541665] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
[ 4791.544526] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 4791.546019] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
Johan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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
1 sibling, 1 reply; 26+ messages in thread
From: StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org @ 2019-04-29 11:48 UTC (permalink / raw)
To: Johan Hovold
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA, Mathias Nyman
[-- Attachment #1: Type: text/plain, Size: 6926 bytes --]
Ok,
I attach log from today test on Ubuntu 19.04 with5.0.9-050009-generickernel.
Full kern.log: https://paste.ee/p/yF3Qi#section0
Dmesg log: https://paste.ee/p/yF3Qi#section1
Summary:
- motherboard with AMD A320M chipset, CPU AMD Athlon 200GE
- Ubuntu 19.04 default instalation, kernel 5.0.9-050009-generic
- connected "FTDI FT232R" (USB to serial converter) to USB port, latest
FTDI libftd2xx drivers version 1.4.8 installed,
https://www.ftdichip.com/Drivers/D2XX.htm
- ftdi_sio driver is unloaded (rmmod ftdi_sio)
- problem is with reading EEPROM content from FTDI FT232R chip
- problem is on USB2.0 port only, on USB3 port it works fine
starosta
Dne 29.4.2019 v 13:22 Johan Hovold napsal(a):
> On Mon, Apr 29, 2019 at 12:51:20PM +0200, StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>> Hello,
>> sorry for other questions, but I am new in this list:
>> Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
>> test?
> Yes, that might do depending on what else debian put in that kernel.
>
>> Can I add attachments to this lists?
> Sure, it's even preferred. Just try to trim non-relevant bits, and
> perhaps provide a link to the full log.
>
>> And who is xhci and iommu maintainers? Are they CC in this mail?
> Yes, that's Mathias and Joerg, respectively, that I added on CC.
>
>> Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
>>> 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).
> Here's an excerpt from the 4.18 log meanwhile:
>
> [ 0.000000] Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13)
>
> ...
>
> [ 960.145603] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 1790.293623] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff50000 flags=0x0020]
> [ 1790.300905] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fde9e000 flags=0x0020]
>
> ...
>
> [ 4789.145364] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 4789.310916] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff63c000 flags=0x0020]
> [ 4789.317023] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff5c6000 flags=0x0020]
> [ 4789.702446] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 4789.766842] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fdeaf000 flags=0x0020]
> [ 4789.781531] AMD-Vi: Event logged [IO_PAGE_FAULT device=15:00.0 domain=0x0000 address=0x00000000fdeaf040 flags=0x0020]
> [ 4790.093644] general protection fault: 0000 [#1] SMP NOPTI
> [ 4790.094186] CPU: 2 PID: 24561 Comm: readua Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
> [ 4790.094738] Hardware name: Micro-Star International Co., Ltd MS-7B38/A320M PRO-VD PLUS (MS-7B38), BIOS 1.C0 11/02/2018
> [ 4790.095333] RIP: 0010:prefetch_freepointer+0x10/0x20
> [ 4790.095936] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
> [ 4790.097314] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
> [ 4790.098016] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
> [ 4790.098711] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
> [ 4790.099413] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
> [ 4790.100141] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
> [ 4790.100871] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
> [ 4790.101619] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
> [ 4790.102387] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
> [ 4790.103157] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
> [ 4790.103954] Call Trace:
> [ 4790.104753] kmem_cache_alloc_trace+0xb5/0x1c0
> [ 4790.105580] ? proc_do_submiturb+0x35a/0xda0 [usbcore]
> [ 4790.106382] proc_do_submiturb+0x35a/0xda0 [usbcore]
> [ 4790.107189] ? futex_wake+0x94/0x170
> [ 4790.108009] proc_submiturb_compat+0xb1/0xe0 [usbcore]
> [ 4790.108851] usbdev_do_ioctl+0x894/0x1170 [usbcore]
> [ 4790.109704] usbdev_compat_ioctl+0xc/0x10 [usbcore]
> [ 4790.110553] __ia32_compat_sys_ioctl+0xc0/0x250
> [ 4790.111413] do_fast_syscall_32+0x98/0x1e0
> [ 4790.112280] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
> [ 4790.113167] Modules linked in: ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c iptable_filter binfmt_misc nls_ascii nls_cp437 vfat fat efi_pstore edac_mce_amd ccp rng_core kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_intel ghash_clmulni_intel wmi_bmof snd_hda_codec efivars pcspkr snd_hda_core snd_hwdep snd_pcm k10temp snd_timer sg snd soundcore sp5100_tco evdev pcc_cpufreq acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod hid_generic usbhid hid crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper amdgpu
chash gpu_sched
> [ 4790.120417] i2c_algo_bit i2c_piix4 ttm drm_kms_helper ahci xhci_pci libahci xhci_hcd drm libata r8169 mii usbcore scsi_mod usb_common wmi video gpio_amdpt gpio_generic button
> [ 4790.122857] ---[ end trace bdd21237253335ac ]---
> [ 4791.452933] RIP: 0010:prefetch_freepointer+0x10/0x20
> [ 4791.461318] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
> [ 4791.479889] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
> [ 4791.490112] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
> [ 4791.500551] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
> [ 4791.509946] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
> [ 4791.519575] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
> [ 4791.530038] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
> [ 4791.541665] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
> [ 4791.544526] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
> [ 4791.546019] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
>
> Johan
[-- Attachment #2: excerpt-kern.log --]
[-- Type: text/plain, Size: 23588 bytes --]
Apr 29 12:39:39 test-ubnt kernel: [ 0.000000] Linux version 5.0.9-050009-generic (kernel@kathleen) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)) #201904200830 SMP Sat Apr 20 08:32:44 UTC 2019
...
Apr 29 12:42:30 test-ubnt kernel: [ 184.230060] usbserial: USB Serial deregistering driver FTDI USB Serial Device
Apr 29 12:42:30 test-ubnt kernel: [ 184.230265] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Apr 29 12:42:30 test-ubnt kernel: [ 184.230281] usbcore: deregistering interface driver ftdi_sio
Apr 29 12:42:30 test-ubnt kernel: [ 184.230310] ftdi_sio 1-9:1.0: device disconnected
Apr 29 12:42:32 test-ubnt kernel: [ 186.736091] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:33 test-ubnt kernel: [ 186.908142] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe80b000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 186.910476] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfff0a000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 187.295439] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:33 test-ubnt kernel: [ 187.469145] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe995000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 187.469944] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffdae000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 187.854873] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:34 test-ubnt kernel: [ 188.027196] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffdbe000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 188.029621] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfc77f000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 188.414536] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:34 test-ubnt kernel: [ 188.587169] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc20000 flags=0x0070]
Apr 29 12:42:34 test-ubnt kernel: [ 188.589694] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe9af000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 188.974027] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:35 test-ubnt kernel: [ 189.146304] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffb73000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.149188] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf963e000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.533697] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:35 test-ubnt kernel: [ 189.706380] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe68f000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.708841] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffb0e000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.093821] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:36 test-ubnt kernel: [ 190.266544] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffbd3000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.268330] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9a7000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.653335] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:37 test-ubnt kernel: [ 190.825548] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe2d1000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 190.827980] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf9584000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.212976] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:37 test-ubnt kernel: [ 191.385639] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf957b000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.388194] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf957d000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.772941] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:38 test-ubnt kernel: [ 191.945695] amd_iommu_report_page_fault: 8 callbacks suppressed
...
Apr 29 12:51:41 test-ubnt kernel: [ 735.067290] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe99b000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.069095] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc4d000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.453621] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:41 test-ubnt kernel: [ 735.626419] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc24000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.628747] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2d5000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.013655] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:42 test-ubnt kernel: [ 736.186434] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf961b000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.188821] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa016000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.573822] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:42 test-ubnt kernel: [ 736.746622] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2d2000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.133262] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:43 test-ubnt kernel: [ 737.305606] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfff22000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.307978] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfc77e000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.693013] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:44 test-ubnt kernel: [ 737.865686] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc50000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 737.868055] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe3f7000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.252398] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:44 test-ubnt kernel: [ 738.424709] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9a3000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.427524] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffda9000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.812021] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:45 test-ubnt kernel: [ 738.984861] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffb1c000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 738.987200] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe2bb000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 739.372120] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:45 test-ubnt kernel: [ 739.544897] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf93d5000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 739.547272] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9bb000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 739.931640] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:46 test-ubnt kernel: [ 740.004937] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfff31000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.010755] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfa016000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.395707] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:46 test-ubnt kernel: [ 740.569013] amd_iommu_report_page_fault: 9 callbacks suppressed
Apr 29 12:51:46 test-ubnt kernel: [ 740.569018] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf967d000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.570406] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe67e000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 740.955326] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:47 test-ubnt kernel: [ 741.128009] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe9b3000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.130463] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf93d5000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.515382] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:47 test-ubnt kernel: [ 741.688177] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2ab000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.689972] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe999000 flags=0x0020]
Apr 29 12:51:48 test-ubnt kernel: [ 742.074489] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:48 test-ubnt kernel: [ 742.249652] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2c5000 flags=0x0020]
Apr 29 12:51:48 test-ubnt kernel: [ 742.592126] ------------[ cut here ]------------
Apr 29 12:51:48 test-ubnt kernel: [ 742.592129] kernel BUG at mm/slub.c:3955!
Apr 29 12:51:48 test-ubnt kernel: [ 742.593844] invalid opcode: 0000 [#1] SMP NOPTI
Apr 29 12:51:48 test-ubnt kernel: [ 742.595550] CPU: 0 PID: 7254 Comm: readua Not tainted 5.0.9-050009-generic #201904200830
Apr 29 12:51:48 test-ubnt kernel: [ 742.597220] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
Apr 29 12:51:48 test-ubnt kernel: [ 742.598923] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:51:48 test-ubnt kernel: [ 742.600587] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.604117] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:51:48 test-ubnt kernel: [ 742.605879] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:51:48 test-ubnt kernel: [ 742.607661] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.609410] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.611174] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:51:48 test-ubnt kernel: [ 742.612959] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.614708] FS: 0000000000000000(0000) GS:ffff9f0a1ae00000(0063) knlGS:00000000f7513b40
Apr 29 12:51:48 test-ubnt kernel: [ 742.616446] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr 29 12:51:48 test-ubnt kernel: [ 742.618197] CR2: 00000000f6c00008 CR3: 000000010bfe2000 CR4: 00000000003406f0
Apr 29 12:51:48 test-ubnt kernel: [ 742.619973] Call Trace:
Apr 29 12:51:48 test-ubnt kernel: [ 742.621725] free_async+0xec/0x100
Apr 29 12:51:48 test-ubnt kernel: [ 742.623474] usbdev_do_ioctl+0x117/0x1100
Apr 29 12:51:48 test-ubnt kernel: [ 742.625193] usbdev_compat_ioctl+0x10/0x20
Apr 29 12:51:48 test-ubnt kernel: [ 742.626918] __ia32_compat_sys_ioctl+0x13d/0x230
Apr 29 12:51:48 test-ubnt kernel: [ 742.628661] ? __ia32_sys_poll+0xa3/0x140
Apr 29 12:51:48 test-ubnt kernel: [ 742.630360] do_fast_syscall_32+0x9b/0x210
Apr 29 12:51:48 test-ubnt kernel: [ 742.632048] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Apr 29 12:51:48 test-ubnt kernel: [ 742.633711] RIP: 0023:0xf7f6a939
Apr 29 12:51:48 test-ubnt kernel: [ 742.635379] Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 34 24 c3 8b 3c 24 c3 90 90 90 90 90 90 90 90 51 52 55 89 cd 0f 05 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.638890] RSP: 002b:00000000f75131c8 EFLAGS: 00000206 ORIG_RAX: 0000000000000036
Apr 29 12:51:48 test-ubnt kernel: [ 742.640668] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 000000004004550d
Apr 29 12:51:48 test-ubnt kernel: [ 742.642425] RDX: 00000000f751320c RSI: 0000000000000001 RDI: 00000000f7f1e000
Apr 29 12:51:48 test-ubnt kernel: [ 742.644201] RBP: 00000000f7513228 R08: 0000000000000000 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.645970] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.647697] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.649426] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core eeepc_wmi snd_hwdep asus_wmi snd_pcm sparse_keymap wmi_bmof joydev k10temp input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu chash aesni_intel amd_iommu_v2 gpu_sched i2c_algo_bit ttm aes_x86_64 drm_kms_helper crypto_simd cryptd glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops r8169 ahci drm realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
Apr 29 12:51:48 test-ubnt kernel: [ 742.662927] ---[ end trace a4090e5de93b0c0a ]---
Apr 29 12:51:48 test-ubnt kernel: [ 742.665363] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:51:48 test-ubnt kernel: [ 742.667359] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.671526] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:51:48 test-ubnt kernel: [ 742.673718] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:51:48 test-ubnt kernel: [ 742.675852] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.677942] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.680072] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:51:48 test-ubnt kernel: [ 742.682160] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.684297] FS: 0000000000000000(0000) GS:ffff9f0a1ae00000(0063) knlGS:00000000f7513b40
Apr 29 12:51:48 test-ubnt kernel: [ 742.686432] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr 29 12:51:48 test-ubnt kernel: [ 742.688533] CR2: 00000000f6c00008 CR3: 000000010bfe2000 CR4: 00000000003406f0
Apr 29 12:52:57 test-ubnt kernel: [ 810.994316] general protection fault: 0000 [#2] SMP NOPTI
Apr 29 12:52:57 test-ubnt kernel: [ 810.996043] CPU: 1 PID: 7275 Comm: snap Tainted: G D 5.0.9-050009-generic #201904200830
Apr 29 12:52:57 test-ubnt kernel: [ 810.997671] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
Apr 29 12:52:57 test-ubnt kernel: [ 810.999199] RIP: 0010:__kmalloc_node+0x18f/0x2b0
Apr 29 12:52:57 test-ubnt kernel: [ 811.000687] Code: 46 0b 04 0f 84 07 ff ff ff 4c 89 f7 e8 aa e3 01 00 49 89 c1 e9 f7 fe ff ff 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 0f 84
Apr 29 12:52:57 test-ubnt kernel: [ 811.003780] RSP: 0018:ffffb8824be4fab0 EFLAGS: 00010202
Apr 29 12:52:57 test-ubnt kernel: [ 811.005329] RAX: 477a9f9cb590bccd RBX: 477a9f9cb590bccd RCX: 000000000001519c
Apr 29 12:52:57 test-ubnt kernel: [ 811.006899] RDX: 000000000001519b RSI: 0000000000480020 RDI: 0000000000027040
Apr 29 12:52:57 test-ubnt kernel: [ 811.008448] RBP: ffffb8824be4fae8 R08: ffff9f0a1ae67040 R09: ffff9f0a1a807c00
Apr 29 12:52:57 test-ubnt kernel: [ 811.009991] R10: ffff9f0a1a827fa0 R11: 0000000000000000 R12: 0000000000480020
Apr 29 12:52:57 test-ubnt kernel: [ 811.012240] R13: 0000000000000008 R14: ffff9f0a1a807c00 R15: 477a9f9cb590bccd
Apr 29 12:52:57 test-ubnt kernel: [ 811.014464] FS: 00007fd5cb7fe700(0000) GS:ffff9f0a1ae40000(0000) knlGS:0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.016698] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 12:52:57 test-ubnt kernel: [ 811.018911] CR2: 00007fd5bc000010 CR3: 000000007340e000 CR4: 00000000003406e0
Apr 29 12:52:57 test-ubnt kernel: [ 811.021105] Call Trace:
Apr 29 12:52:57 test-ubnt kernel: [ 811.023259] ? alloc_cpumask_var_node+0x1f/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.025377] ? flush_tlb_func_common.constprop.9+0x230/0x230
Apr 29 12:52:57 test-ubnt kernel: [ 811.027503] alloc_cpumask_var_node+0x1f/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.029606] alloc_cpumask_var+0xe/0x10
Apr 29 12:52:57 test-ubnt kernel: [ 811.031705] native_send_call_func_ipi+0x2e/0x120
Apr 29 12:52:57 test-ubnt kernel: [ 811.033805] smp_call_function_many+0x1b0/0x250
Apr 29 12:52:57 test-ubnt kernel: [ 811.035898] native_flush_tlb_others+0x48/0x130
Apr 29 12:52:57 test-ubnt kernel: [ 811.037985] flush_tlb_mm_range+0xec/0x120
Apr 29 12:52:57 test-ubnt kernel: [ 811.040051] tlb_flush_mmu+0x71/0x100
Apr 29 12:52:57 test-ubnt kernel: [ 811.042106] arch_tlb_finish_mmu+0x1b/0xb0
Apr 29 12:52:57 test-ubnt kernel: [ 811.044141] tlb_finish_mmu+0x23/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.046160] exit_mmap+0xde/0x190
Apr 29 12:52:57 test-ubnt kernel: [ 811.048177] mmput+0x57/0x130
Apr 29 12:52:57 test-ubnt kernel: [ 811.050199] do_exit+0x288/0xb30
Apr 29 12:52:57 test-ubnt kernel: [ 811.052211] ? mem_cgroup_try_charge+0x8b/0x190
Apr 29 12:52:57 test-ubnt kernel: [ 811.054235] do_group_exit+0x43/0xb0
Apr 29 12:52:57 test-ubnt kernel: [ 811.056251] get_signal+0x12e/0x6d0
Apr 29 12:52:57 test-ubnt kernel: [ 811.058273] do_signal+0x34/0x710
Apr 29 12:52:57 test-ubnt kernel: [ 811.060275] ? recalc_sigpending+0x1b/0x50
Apr 29 12:52:57 test-ubnt kernel: [ 811.062277] ? __x64_sys_futex+0x143/0x180
Apr 29 12:52:57 test-ubnt kernel: [ 811.064235] exit_to_usermode_loop+0x8e/0x100
Apr 29 12:52:57 test-ubnt kernel: [ 811.066151] do_syscall_64+0xda/0x110
Apr 29 12:52:57 test-ubnt kernel: [ 811.068044] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 29 12:52:57 test-ubnt kernel: [ 811.069940] RIP: 0033:0x55c38e2d4383
Apr 29 12:52:57 test-ubnt kernel: [ 811.071827] Code: Bad RIP value.
Apr 29 12:52:57 test-ubnt kernel: [ 811.073712] RSP: 002b:00007fd5cb7fdda8 EFLAGS: 00000286 ORIG_RAX: 00000000000000ca
Apr 29 12:52:57 test-ubnt kernel: [ 811.075646] RAX: fffffffffffffe00 RBX: 000000c420045000 RCX: 000055c38e2d4383
Apr 29 12:52:57 test-ubnt kernel: [ 811.077628] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000055c38ecb8098
Apr 29 12:52:57 test-ubnt kernel: [ 811.079545] RBP: 00007fd5cb7fddf0 R08: 0000000000000000 R09: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.081400] R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffe68ebdb7e
Apr 29 12:52:57 test-ubnt kernel: [ 811.083218] R13: 00007ffe68ebdb7f R14: 00007ffe68ebdc80 R15: 00007fd5cb7fdfc0
Apr 29 12:52:57 test-ubnt kernel: [ 811.084978] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core eeepc_wmi snd_hwdep asus_wmi snd_pcm sparse_keymap wmi_bmof joydev k10temp input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu chash aesni_intel amd_iommu_v2 gpu_sched i2c_algo_bit ttm aes_x86_64 drm_kms_helper crypto_simd cryptd glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops r8169 ahci drm realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
Apr 29 12:52:57 test-ubnt kernel: [ 811.097944] ---[ end trace a4090e5de93b0c0b ]---
Apr 29 12:52:57 test-ubnt kernel: [ 811.100472] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:52:57 test-ubnt kernel: [ 811.102334] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:52:57 test-ubnt kernel: [ 811.106243] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:52:57 test-ubnt kernel: [ 811.108200] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:52:57 test-ubnt kernel: [ 811.110167] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.112132] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.114067] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:52:57 test-ubnt kernel: [ 811.116011] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.117931] FS: 00007fd5cb7fe700(0000) GS:ffff9f0a1ae40000(0000) knlGS:0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.119869] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 12:52:57 test-ubnt kernel: [ 811.121774] CR2: 000055c38e2d4359 CR3: 000000007340e000 CR4: 00000000003406e0
Apr 29 12:52:57 test-ubnt kernel: [ 811.123701] Fixing recursive fault but reboot is needed!
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-04-29 11:48 ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
@ 2019-04-29 11:48 ` StarostaCZ@gmail.com
0 siblings, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-04-29 11:48 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb, iommu, Mathias Nyman
[-- Attachment #1: Type: text/plain, Size: 6871 bytes --]
Ok,
I attach log from today test on Ubuntu 19.04 with5.0.9-050009-generickernel.
Full kern.log: https://paste.ee/p/yF3Qi#section0
Dmesg log: https://paste.ee/p/yF3Qi#section1
Summary:
- motherboard with AMD A320M chipset, CPU AMD Athlon 200GE
- Ubuntu 19.04 default instalation, kernel 5.0.9-050009-generic
- connected "FTDI FT232R" (USB to serial converter) to USB port, latest
FTDI libftd2xx drivers version 1.4.8 installed,
https://www.ftdichip.com/Drivers/D2XX.htm
- ftdi_sio driver is unloaded (rmmod ftdi_sio)
- problem is with reading EEPROM content from FTDI FT232R chip
- problem is on USB2.0 port only, on USB3 port it works fine
starosta
Dne 29.4.2019 v 13:22 Johan Hovold napsal(a):
> On Mon, Apr 29, 2019 at 12:51:20PM +0200, StarostaCZ@gmail.com wrote:
>> Hello,
>> sorry for other questions, but I am new in this list:
>> Is Ubuntu server 19.04 with "kernel 5.0.9-050009-generic" good for this
>> test?
> Yes, that might do depending on what else debian put in that kernel.
>
>> Can I add attachments to this lists?
> Sure, it's even preferred. Just try to trim non-relevant bits, and
> perhaps provide a link to the full log.
>
>> And who is xhci and iommu maintainers? Are they CC in this mail?
> Yes, that's Mathias and Joerg, respectively, that I added on CC.
>
>> Dne 29.4.2019 v 11:48 Johan Hovold napsal(a):
>>> 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).
> Here's an excerpt from the 4.18 log meanwhile:
>
> [ 0.000000] Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13)
>
> ...
>
> [ 960.145603] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 1790.293623] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff50000 flags=0x0020]
> [ 1790.300905] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fde9e000 flags=0x0020]
>
> ...
>
> [ 4789.145364] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 4789.310916] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff63c000 flags=0x0020]
> [ 4789.317023] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ff5c6000 flags=0x0020]
> [ 4789.702446] xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> [ 4789.766842] xhci_hcd 0000:15:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fdeaf000 flags=0x0020]
> [ 4789.781531] AMD-Vi: Event logged [IO_PAGE_FAULT device=15:00.0 domain=0x0000 address=0x00000000fdeaf040 flags=0x0020]
> [ 4790.093644] general protection fault: 0000 [#1] SMP NOPTI
> [ 4790.094186] CPU: 2 PID: 24561 Comm: readua Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
> [ 4790.094738] Hardware name: Micro-Star International Co., Ltd MS-7B38/A320M PRO-VD PLUS (MS-7B38), BIOS 1.C0 11/02/2018
> [ 4790.095333] RIP: 0010:prefetch_freepointer+0x10/0x20
> [ 4790.095936] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
> [ 4790.097314] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
> [ 4790.098016] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
> [ 4790.098711] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
> [ 4790.099413] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
> [ 4790.100141] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
> [ 4790.100871] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
> [ 4790.101619] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
> [ 4790.102387] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
> [ 4790.103157] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
> [ 4790.103954] Call Trace:
> [ 4790.104753] kmem_cache_alloc_trace+0xb5/0x1c0
> [ 4790.105580] ? proc_do_submiturb+0x35a/0xda0 [usbcore]
> [ 4790.106382] proc_do_submiturb+0x35a/0xda0 [usbcore]
> [ 4790.107189] ? futex_wake+0x94/0x170
> [ 4790.108009] proc_submiturb_compat+0xb1/0xe0 [usbcore]
> [ 4790.108851] usbdev_do_ioctl+0x894/0x1170 [usbcore]
> [ 4790.109704] usbdev_compat_ioctl+0xc/0x10 [usbcore]
> [ 4790.110553] __ia32_compat_sys_ioctl+0xc0/0x250
> [ 4790.111413] do_fast_syscall_32+0x98/0x1e0
> [ 4790.112280] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
> [ 4790.113167] Modules linked in: ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c iptable_filter binfmt_misc nls_ascii nls_cp437 vfat fat efi_pstore edac_mce_amd ccp rng_core kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_intel ghash_clmulni_intel wmi_bmof snd_hda_codec efivars pcspkr snd_hda_core snd_hwdep snd_pcm k10temp snd_timer sg snd soundcore sp5100_tco evdev pcc_cpufreq acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod hid_generic usbhid hid crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper amdgpu chash gpu_sched
> [ 4790.120417] i2c_algo_bit i2c_piix4 ttm drm_kms_helper ahci xhci_pci libahci xhci_hcd drm libata r8169 mii usbcore scsi_mod usb_common wmi video gpio_amdpt gpio_generic button
> [ 4790.122857] ---[ end trace bdd21237253335ac ]---
> [ 4791.452933] RIP: 0010:prefetch_freepointer+0x10/0x20
> [ 4791.461318] Code: 58 48 c7 c7 30 09 a5 b0 e8 4b 64 eb ff eb 90 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 85 f6 74 13 8b 47 20 48 01 c6 <48> 33 36 48 33 b7 38 01 00 00 0f 18 0e f3 c3 90 0f 1f 44 00 00 8b
> [ 4791.479889] RSP: 0018:ffffb6e303e67ce0 EFLAGS: 00010286
> [ 4791.490112] RAX: 0000000000000000 RBX: 93773f762ca13047 RCX: 00000000000077df
> [ 4791.500551] RDX: 00000000000077de RSI: 93773f762ca13047 RDI: ffff9a30de807c00
> [ 4791.509946] RBP: ffff9a30d20cc018 R08: ffff9a30deca4de0 R09: 0000000000000000
> [ 4791.519575] R10: ffff9a306f3c6638 R11: 0000000000000000 R12: 00000000006000c0
> [ 4791.530038] R13: 0000000000000008 R14: ffff9a30de807c00 R15: ffff9a30de807c00
> [ 4791.541665] FS: 0000000000000000(0000) GS:ffff9a30dec80000(0063) knlGS:00000000f7d6a700
> [ 4791.544526] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
> [ 4791.546019] CR2: 00000000ffc77e3c CR3: 00000000af0c0000 CR4: 00000000003406e0
>
> Johan
[-- Attachment #2: excerpt-kern.log --]
[-- Type: text/plain, Size: 23588 bytes --]
Apr 29 12:39:39 test-ubnt kernel: [ 0.000000] Linux version 5.0.9-050009-generic (kernel@kathleen) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)) #201904200830 SMP Sat Apr 20 08:32:44 UTC 2019
...
Apr 29 12:42:30 test-ubnt kernel: [ 184.230060] usbserial: USB Serial deregistering driver FTDI USB Serial Device
Apr 29 12:42:30 test-ubnt kernel: [ 184.230265] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Apr 29 12:42:30 test-ubnt kernel: [ 184.230281] usbcore: deregistering interface driver ftdi_sio
Apr 29 12:42:30 test-ubnt kernel: [ 184.230310] ftdi_sio 1-9:1.0: device disconnected
Apr 29 12:42:32 test-ubnt kernel: [ 186.736091] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:33 test-ubnt kernel: [ 186.908142] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe80b000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 186.910476] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfff0a000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 187.295439] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:33 test-ubnt kernel: [ 187.469145] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe995000 flags=0x0020]
Apr 29 12:42:33 test-ubnt kernel: [ 187.469944] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffdae000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 187.854873] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:34 test-ubnt kernel: [ 188.027196] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffdbe000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 188.029621] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfc77f000 flags=0x0020]
Apr 29 12:42:34 test-ubnt kernel: [ 188.414536] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:34 test-ubnt kernel: [ 188.587169] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc20000 flags=0x0070]
Apr 29 12:42:34 test-ubnt kernel: [ 188.589694] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe9af000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 188.974027] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:35 test-ubnt kernel: [ 189.146304] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffb73000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.149188] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf963e000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.533697] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:35 test-ubnt kernel: [ 189.706380] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe68f000 flags=0x0020]
Apr 29 12:42:35 test-ubnt kernel: [ 189.708841] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffb0e000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.093821] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:36 test-ubnt kernel: [ 190.266544] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffbd3000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.268330] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9a7000 flags=0x0020]
Apr 29 12:42:36 test-ubnt kernel: [ 190.653335] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:37 test-ubnt kernel: [ 190.825548] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe2d1000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 190.827980] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf9584000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.212976] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:37 test-ubnt kernel: [ 191.385639] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf957b000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.388194] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf957d000 flags=0x0020]
Apr 29 12:42:37 test-ubnt kernel: [ 191.772941] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:42:38 test-ubnt kernel: [ 191.945695] amd_iommu_report_page_fault: 8 callbacks suppressed
...
Apr 29 12:51:41 test-ubnt kernel: [ 735.067290] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe99b000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.069095] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc4d000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.453621] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:41 test-ubnt kernel: [ 735.626419] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc24000 flags=0x0020]
Apr 29 12:51:41 test-ubnt kernel: [ 735.628747] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2d5000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.013655] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:42 test-ubnt kernel: [ 736.186434] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf961b000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.188821] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa016000 flags=0x0020]
Apr 29 12:51:42 test-ubnt kernel: [ 736.573822] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:42 test-ubnt kernel: [ 736.746622] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2d2000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.133262] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:43 test-ubnt kernel: [ 737.305606] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfff22000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.307978] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfc77e000 flags=0x0020]
Apr 29 12:51:43 test-ubnt kernel: [ 737.693013] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:44 test-ubnt kernel: [ 737.865686] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc50000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 737.868055] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe3f7000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.252398] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:44 test-ubnt kernel: [ 738.424709] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9a3000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.427524] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffda9000 flags=0x0020]
Apr 29 12:51:44 test-ubnt kernel: [ 738.812021] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:45 test-ubnt kernel: [ 738.984861] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xffb1c000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 738.987200] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe2bb000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 739.372120] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:45 test-ubnt kernel: [ 739.544897] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xf93d5000 flags=0x0020]
Apr 29 12:51:45 test-ubnt kernel: [ 739.547272] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfe9bb000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 739.931640] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:46 test-ubnt kernel: [ 740.004937] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfff31000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.010755] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0xfa016000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.395707] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:46 test-ubnt kernel: [ 740.569013] amd_iommu_report_page_fault: 9 callbacks suppressed
Apr 29 12:51:46 test-ubnt kernel: [ 740.569018] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf967d000 flags=0x0020]
Apr 29 12:51:46 test-ubnt kernel: [ 740.570406] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe67e000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 740.955326] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:47 test-ubnt kernel: [ 741.128009] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe9b3000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.130463] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xf93d5000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.515382] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:47 test-ubnt kernel: [ 741.688177] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2ab000 flags=0x0020]
Apr 29 12:51:47 test-ubnt kernel: [ 741.689972] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe999000 flags=0x0020]
Apr 29 12:51:48 test-ubnt kernel: [ 742.074489] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Apr 29 12:51:48 test-ubnt kernel: [ 742.249652] xhci_hcd 0000:01:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe2c5000 flags=0x0020]
Apr 29 12:51:48 test-ubnt kernel: [ 742.592126] ------------[ cut here ]------------
Apr 29 12:51:48 test-ubnt kernel: [ 742.592129] kernel BUG at mm/slub.c:3955!
Apr 29 12:51:48 test-ubnt kernel: [ 742.593844] invalid opcode: 0000 [#1] SMP NOPTI
Apr 29 12:51:48 test-ubnt kernel: [ 742.595550] CPU: 0 PID: 7254 Comm: readua Not tainted 5.0.9-050009-generic #201904200830
Apr 29 12:51:48 test-ubnt kernel: [ 742.597220] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
Apr 29 12:51:48 test-ubnt kernel: [ 742.598923] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:51:48 test-ubnt kernel: [ 742.600587] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.604117] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:51:48 test-ubnt kernel: [ 742.605879] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:51:48 test-ubnt kernel: [ 742.607661] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.609410] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.611174] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:51:48 test-ubnt kernel: [ 742.612959] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.614708] FS: 0000000000000000(0000) GS:ffff9f0a1ae00000(0063) knlGS:00000000f7513b40
Apr 29 12:51:48 test-ubnt kernel: [ 742.616446] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr 29 12:51:48 test-ubnt kernel: [ 742.618197] CR2: 00000000f6c00008 CR3: 000000010bfe2000 CR4: 00000000003406f0
Apr 29 12:51:48 test-ubnt kernel: [ 742.619973] Call Trace:
Apr 29 12:51:48 test-ubnt kernel: [ 742.621725] free_async+0xec/0x100
Apr 29 12:51:48 test-ubnt kernel: [ 742.623474] usbdev_do_ioctl+0x117/0x1100
Apr 29 12:51:48 test-ubnt kernel: [ 742.625193] usbdev_compat_ioctl+0x10/0x20
Apr 29 12:51:48 test-ubnt kernel: [ 742.626918] __ia32_compat_sys_ioctl+0x13d/0x230
Apr 29 12:51:48 test-ubnt kernel: [ 742.628661] ? __ia32_sys_poll+0xa3/0x140
Apr 29 12:51:48 test-ubnt kernel: [ 742.630360] do_fast_syscall_32+0x9b/0x210
Apr 29 12:51:48 test-ubnt kernel: [ 742.632048] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Apr 29 12:51:48 test-ubnt kernel: [ 742.633711] RIP: 0023:0xf7f6a939
Apr 29 12:51:48 test-ubnt kernel: [ 742.635379] Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 34 24 c3 8b 3c 24 c3 90 90 90 90 90 90 90 90 51 52 55 89 cd 0f 05 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.638890] RSP: 002b:00000000f75131c8 EFLAGS: 00000206 ORIG_RAX: 0000000000000036
Apr 29 12:51:48 test-ubnt kernel: [ 742.640668] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 000000004004550d
Apr 29 12:51:48 test-ubnt kernel: [ 742.642425] RDX: 00000000f751320c RSI: 0000000000000001 RDI: 00000000f7f1e000
Apr 29 12:51:48 test-ubnt kernel: [ 742.644201] RBP: 00000000f7513228 R08: 0000000000000000 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.645970] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.647697] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.649426] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core eeepc_wmi snd_hwdep asus_wmi snd_pcm sparse_keymap wmi_bmof joydev k10temp input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu chash aesni_intel amd_iommu_v2 gpu_sched i2c_algo_bit ttm aes_x86_64 drm_kms_helper crypto_simd cryptd glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops r8169 ahci drm realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
Apr 29 12:51:48 test-ubnt kernel: [ 742.662927] ---[ end trace a4090e5de93b0c0a ]---
Apr 29 12:51:48 test-ubnt kernel: [ 742.665363] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:51:48 test-ubnt kernel: [ 742.667359] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:51:48 test-ubnt kernel: [ 742.671526] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:51:48 test-ubnt kernel: [ 742.673718] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:51:48 test-ubnt kernel: [ 742.675852] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.677942] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.680072] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:51:48 test-ubnt kernel: [ 742.682160] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:51:48 test-ubnt kernel: [ 742.684297] FS: 0000000000000000(0000) GS:ffff9f0a1ae00000(0063) knlGS:00000000f7513b40
Apr 29 12:51:48 test-ubnt kernel: [ 742.686432] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr 29 12:51:48 test-ubnt kernel: [ 742.688533] CR2: 00000000f6c00008 CR3: 000000010bfe2000 CR4: 00000000003406f0
Apr 29 12:52:57 test-ubnt kernel: [ 810.994316] general protection fault: 0000 [#2] SMP NOPTI
Apr 29 12:52:57 test-ubnt kernel: [ 810.996043] CPU: 1 PID: 7275 Comm: snap Tainted: G D 5.0.9-050009-generic #201904200830
Apr 29 12:52:57 test-ubnt kernel: [ 810.997671] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
Apr 29 12:52:57 test-ubnt kernel: [ 810.999199] RIP: 0010:__kmalloc_node+0x18f/0x2b0
Apr 29 12:52:57 test-ubnt kernel: [ 811.000687] Code: 46 0b 04 0f 84 07 ff ff ff 4c 89 f7 e8 aa e3 01 00 49 89 c1 e9 f7 fe ff ff 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 0f 84
Apr 29 12:52:57 test-ubnt kernel: [ 811.003780] RSP: 0018:ffffb8824be4fab0 EFLAGS: 00010202
Apr 29 12:52:57 test-ubnt kernel: [ 811.005329] RAX: 477a9f9cb590bccd RBX: 477a9f9cb590bccd RCX: 000000000001519c
Apr 29 12:52:57 test-ubnt kernel: [ 811.006899] RDX: 000000000001519b RSI: 0000000000480020 RDI: 0000000000027040
Apr 29 12:52:57 test-ubnt kernel: [ 811.008448] RBP: ffffb8824be4fae8 R08: ffff9f0a1ae67040 R09: ffff9f0a1a807c00
Apr 29 12:52:57 test-ubnt kernel: [ 811.009991] R10: ffff9f0a1a827fa0 R11: 0000000000000000 R12: 0000000000480020
Apr 29 12:52:57 test-ubnt kernel: [ 811.012240] R13: 0000000000000008 R14: ffff9f0a1a807c00 R15: 477a9f9cb590bccd
Apr 29 12:52:57 test-ubnt kernel: [ 811.014464] FS: 00007fd5cb7fe700(0000) GS:ffff9f0a1ae40000(0000) knlGS:0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.016698] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 12:52:57 test-ubnt kernel: [ 811.018911] CR2: 00007fd5bc000010 CR3: 000000007340e000 CR4: 00000000003406e0
Apr 29 12:52:57 test-ubnt kernel: [ 811.021105] Call Trace:
Apr 29 12:52:57 test-ubnt kernel: [ 811.023259] ? alloc_cpumask_var_node+0x1f/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.025377] ? flush_tlb_func_common.constprop.9+0x230/0x230
Apr 29 12:52:57 test-ubnt kernel: [ 811.027503] alloc_cpumask_var_node+0x1f/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.029606] alloc_cpumask_var+0xe/0x10
Apr 29 12:52:57 test-ubnt kernel: [ 811.031705] native_send_call_func_ipi+0x2e/0x120
Apr 29 12:52:57 test-ubnt kernel: [ 811.033805] smp_call_function_many+0x1b0/0x250
Apr 29 12:52:57 test-ubnt kernel: [ 811.035898] native_flush_tlb_others+0x48/0x130
Apr 29 12:52:57 test-ubnt kernel: [ 811.037985] flush_tlb_mm_range+0xec/0x120
Apr 29 12:52:57 test-ubnt kernel: [ 811.040051] tlb_flush_mmu+0x71/0x100
Apr 29 12:52:57 test-ubnt kernel: [ 811.042106] arch_tlb_finish_mmu+0x1b/0xb0
Apr 29 12:52:57 test-ubnt kernel: [ 811.044141] tlb_finish_mmu+0x23/0x30
Apr 29 12:52:57 test-ubnt kernel: [ 811.046160] exit_mmap+0xde/0x190
Apr 29 12:52:57 test-ubnt kernel: [ 811.048177] mmput+0x57/0x130
Apr 29 12:52:57 test-ubnt kernel: [ 811.050199] do_exit+0x288/0xb30
Apr 29 12:52:57 test-ubnt kernel: [ 811.052211] ? mem_cgroup_try_charge+0x8b/0x190
Apr 29 12:52:57 test-ubnt kernel: [ 811.054235] do_group_exit+0x43/0xb0
Apr 29 12:52:57 test-ubnt kernel: [ 811.056251] get_signal+0x12e/0x6d0
Apr 29 12:52:57 test-ubnt kernel: [ 811.058273] do_signal+0x34/0x710
Apr 29 12:52:57 test-ubnt kernel: [ 811.060275] ? recalc_sigpending+0x1b/0x50
Apr 29 12:52:57 test-ubnt kernel: [ 811.062277] ? __x64_sys_futex+0x143/0x180
Apr 29 12:52:57 test-ubnt kernel: [ 811.064235] exit_to_usermode_loop+0x8e/0x100
Apr 29 12:52:57 test-ubnt kernel: [ 811.066151] do_syscall_64+0xda/0x110
Apr 29 12:52:57 test-ubnt kernel: [ 811.068044] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 29 12:52:57 test-ubnt kernel: [ 811.069940] RIP: 0033:0x55c38e2d4383
Apr 29 12:52:57 test-ubnt kernel: [ 811.071827] Code: Bad RIP value.
Apr 29 12:52:57 test-ubnt kernel: [ 811.073712] RSP: 002b:00007fd5cb7fdda8 EFLAGS: 00000286 ORIG_RAX: 00000000000000ca
Apr 29 12:52:57 test-ubnt kernel: [ 811.075646] RAX: fffffffffffffe00 RBX: 000000c420045000 RCX: 000055c38e2d4383
Apr 29 12:52:57 test-ubnt kernel: [ 811.077628] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000055c38ecb8098
Apr 29 12:52:57 test-ubnt kernel: [ 811.079545] RBP: 00007fd5cb7fddf0 R08: 0000000000000000 R09: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.081400] R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffe68ebdb7e
Apr 29 12:52:57 test-ubnt kernel: [ 811.083218] R13: 00007ffe68ebdb7f R14: 00007ffe68ebdc80 R15: 00007fd5cb7fdfc0
Apr 29 12:52:57 test-ubnt kernel: [ 811.084978] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core eeepc_wmi snd_hwdep asus_wmi snd_pcm sparse_keymap wmi_bmof joydev k10temp input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu chash aesni_intel amd_iommu_v2 gpu_sched i2c_algo_bit ttm aes_x86_64 drm_kms_helper crypto_simd cryptd glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops r8169 ahci drm realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
Apr 29 12:52:57 test-ubnt kernel: [ 811.097944] ---[ end trace a4090e5de93b0c0b ]---
Apr 29 12:52:57 test-ubnt kernel: [ 811.100472] RIP: 0010:kfree+0x16e/0x180
Apr 29 12:52:57 test-ubnt kernel: [ 811.102334] Code: e8 f7 bf f8 ff eb 8b 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 11 f6 ff ff e9 72 ff ff ff 0f 0b 49 8b 42 08 a8 01 75 c2 <0f> 0b 48 8b 3d a9 a3 39 01 e9 c5 fe ff ff 0f 1f 40 00 0f 1f 44 00
Apr 29 12:52:57 test-ubnt kernel: [ 811.106243] RSP: 0018:ffffb8824be07df0 EFLAGS: 00010246
Apr 29 12:52:57 test-ubnt kernel: [ 811.108200] RAX: dead000000000100 RBX: ffff9f0a18ab97b0 RCX: ffff9f0a10999080
Apr 29 12:52:57 test-ubnt kernel: [ 811.110167] RDX: 0000000000000000 RSI: ffff9f0a18ab97b2 RDI: 000060f680000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.112132] RBP: ffffb8824be07e08 R08: 0000000000000001 R09: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.114067] R10: ffffe24c4462ae40 R11: 000000000000000d R12: ffff9f0a0bd2c900
Apr 29 12:52:57 test-ubnt kernel: [ 811.116011] R13: ffffffffa438875c R14: ffff9f0a0a445f90 R15: 0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.117931] FS: 00007fd5cb7fe700(0000) GS:ffff9f0a1ae40000(0000) knlGS:0000000000000000
Apr 29 12:52:57 test-ubnt kernel: [ 811.119869] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 12:52:57 test-ubnt kernel: [ 811.121774] CR2: 000055c38e2d4359 CR3: 000000007340e000 CR4: 00000000003406e0
Apr 29 12:52:57 test-ubnt kernel: [ 811.123701] Fixing recursive fault but reboot is needed!
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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-05-03 15:37 ` Joerg Roedel
2019-05-06 7:09 ` StarostaCZ@gmail.com
2019-05-06 7:10 ` StarostaCZ@gmail.com
2 siblings, 2 replies; 26+ messages in thread
From: Joerg Roedel @ 2019-05-03 15:37 UTC (permalink / raw)
To: Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman, StarostaCZ@gmail.com
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
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-03 15:37 ` Joerg Roedel
@ 2019-05-06 7:09 ` StarostaCZ@gmail.com
2019-05-06 7:10 ` StarostaCZ@gmail.com
1 sibling, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-06 7:09 UTC (permalink / raw)
To: Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
[-- Attachment #1: Type: text/html, Size: 1368 bytes --]
[-- Attachment #2: kern.log --]
[-- Type: text/plain, Size: 10357 bytes --]
May 6 08:35:39 test-ubnt kernel: [ 0.000000] Linux version 5.1.0-050100-generic (kernel@gloin) (gcc version 8.3.0 (Ubuntu 8.3.0-7ubuntu1)) #201905052130 SMP Mon May 6 01:32:59 UTC 2019
May 6 08:35:39 test-ubnt kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.0-050100-generic root=UUID=91232716-4b81-4e1d-9d58-c2ad4d090e93 ro
...
May 6 08:37:31 test-ubnt kernel: [ 123.968163] usbserial: USB Serial deregistering driver FTDI USB Serial Device
May 6 08:37:31 test-ubnt kernel: [ 123.968416] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
May 6 08:37:31 test-ubnt kernel: [ 123.968438] usbcore: deregistering interface driver ftdi_sio
May 6 08:37:31 test-ubnt kernel: [ 123.968504] ftdi_sio 1-9:1.0: device disconnected
May 6 08:37:36 test-ubnt kernel: [ 129.425748] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:36 test-ubnt kernel: [ 129.597852] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa02000 flags=0x0020]
May 6 08:37:36 test-ubnt kernel: [ 129.600253] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa26000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 129.985262] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:37 test-ubnt kernel: [ 130.157935] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffb8a000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.159739] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xff9f8000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.544683] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:37 test-ubnt kernel: [ 130.716992] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfea16000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.719369] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffbfb000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.104350] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:38 test-ubnt kernel: [ 131.279479] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa3c000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.664426] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:38 test-ubnt kernel: [ 131.837112] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa32000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.839540] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc5d000 flags=0x0020]
May 6 08:37:39 test-ubnt kernel: [ 132.223953] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:39 test-ubnt kernel: [ 132.397215] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc46000 flags=0x0020]
May 6 08:37:39 test-ubnt kernel: [ 132.398608] amd_iommu_report_page_fault: 5 callbacks suppressed
...
May 6 08:38:07 test-ubnt kernel: [ 160.289771] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa532000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.292232] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa53d000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.677243] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:38:07 test-ubnt kernel: [ 160.849877] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa532000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.852303] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc70000 flags=0x0020]
May 6 08:38:08 test-ubnt kernel: [ 161.237342] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:38:08 test-ubnt kernel: [ 161.412400] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe8f0000 flags=0x0020]
May 6 08:38:08 test-ubnt kernel: [ 161.562930] general protection fault: 0000 [#1] SMP NOPTI
May 6 08:38:08 test-ubnt kernel: [ 161.563709] CPU: 0 PID: 1632 Comm: readua Not tainted 5.1.0-050100-generic #201905052130
May 6 08:38:08 test-ubnt kernel: [ 161.564493] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
May 6 08:38:08 test-ubnt kernel: [ 161.565323] RIP: 0010:__kmalloc+0xa5/0x220
May 6 08:38:08 test-ubnt kernel: [ 161.566116] Code: 65 49 8b 50 08 65 4c 03 05 80 c5 78 79 4d 8b 38 4d 85 ff 0f 84 2e 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd
May 6 08:38:08 test-ubnt kernel: [ 161.567913] RSP: 0018:ffffa8614237bcd0 EFLAGS: 00010202
May 6 08:38:08 test-ubnt kernel: [ 161.568840] RAX: 534d1cbf998a8f86 RBX: 534d1cbf998a8f86 RCX: 00000000000062cb
May 6 08:38:08 test-ubnt kernel: [ 161.569801] RDX: 00000000000062ca RSI: 0000000000000cc0 RDI: 0000000000028040
May 6 08:38:08 test-ubnt kernel: [ 161.570779] RBP: ffffa8614237bd00 R08: ffff9cfa9ae28040 R09: ffff9cfa9a807c00
May 6 08:38:08 test-ubnt kernel: [ 161.571778] R10: 0000000000000009 R11: ffff9cfa36fcc100 R12: 0000000000000cc0
May 6 08:38:08 test-ubnt kernel: [ 161.572796] R13: 0000000000000002 R14: ffff9cfa9a807c00 R15: 534d1cbf998a8f86
May 6 08:38:08 test-ubnt kernel: [ 161.573825] FS: 0000000000000000(0000) GS:ffff9cfa9ae00000(0063) knlGS:00000000f7d01700
May 6 08:38:08 test-ubnt kernel: [ 161.574882] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
May 6 08:38:08 test-ubnt kernel: [ 161.575907] CR2: 00000000ff82280c CR3: 00000000b59ec000 CR4: 00000000003406f0
May 6 08:38:08 test-ubnt kernel: [ 161.576966] Call Trace:
May 6 08:38:08 test-ubnt kernel: [ 161.578028] ? proc_do_submiturb+0xaf1/0xc70
May 6 08:38:08 test-ubnt kernel: [ 161.579109] proc_do_submiturb+0xaf1/0xc70
May 6 08:38:08 test-ubnt kernel: [ 161.580202] proc_submiturb_compat+0x81/0xb0
May 6 08:38:08 test-ubnt kernel: [ 161.581304] usbdev_do_ioctl+0x930/0xd70
May 6 08:38:08 test-ubnt kernel: [ 161.582415] ? _copy_from_user+0x3e/0x60
May 6 08:38:08 test-ubnt kernel: [ 161.583534] usbdev_compat_ioctl+0x10/0x20
May 6 08:38:08 test-ubnt kernel: [ 161.584622] __ia32_compat_sys_ioctl+0x13d/0x230
May 6 08:38:08 test-ubnt kernel: [ 161.585722] do_fast_syscall_32+0x9b/0x210
May 6 08:38:08 test-ubnt kernel: [ 161.586831] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
May 6 08:38:08 test-ubnt kernel: [ 161.587962] RIP: 0023:0xf7f56929
May 6 08:38:08 test-ubnt kernel: [ 161.589096] Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 34 24 c3 8b 3c 24 c3 90 90 90 90 90 90 90 90 51 52 55 89 cd 0f 05 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
May 6 08:38:08 test-ubnt kernel: [ 161.591579] RSP: 002b:00000000ff822588 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
May 6 08:38:08 test-ubnt kernel: [ 161.592871] RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00000000802c550a
May 6 08:38:08 test-ubnt kernel: [ 161.594185] RDX: 0000000057b89bd0 RSI: 0000000000000033 RDI: 0000000000000002
May 6 08:38:08 test-ubnt kernel: [ 161.595508] RBP: 00000000ff8225e8 R08: 0000000000000000 R09: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.596797] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.598089] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.599382] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec k10temp wmi_bmof snd_hda_core joydev eeepc_wmi asus_wmi snd_hwdep sparse_keymap snd_pcm input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu aesni_intel chash gpu_sched amd_iommu_v2 i2c_algo_bit ttm aes_x86_64 crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_piix4 drm r8169 ahci realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
May 6 08:38:08 test-ubnt kernel: [ 161.610416] ---[ end trace e32a9be49aaeee88 ]---
May 6 08:38:08 test-ubnt kernel: [ 161.612558] RIP: 0010:__kmalloc+0xa5/0x220
May 6 08:38:08 test-ubnt kernel: [ 161.614259] Code: 65 49 8b 50 08 65 4c 03 05 80 c5 78 79 4d 8b 38 4d 85 ff 0f 84 2e 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd
May 6 08:38:08 test-ubnt kernel: [ 161.617879] RSP: 0018:ffffa8614237bcd0 EFLAGS: 00010202
May 6 08:38:08 test-ubnt kernel: [ 161.619761] RAX: 534d1cbf998a8f86 RBX: 534d1cbf998a8f86 RCX: 00000000000062cb
May 6 08:38:08 test-ubnt kernel: [ 161.621665] RDX: 00000000000062ca RSI: 0000000000000cc0 RDI: 0000000000028040
May 6 08:38:08 test-ubnt kernel: [ 161.623586] RBP: ffffa8614237bd00 R08: ffff9cfa9ae28040 R09: ffff9cfa9a807c00
May 6 08:38:08 test-ubnt kernel: [ 161.625513] R10: 0000000000000009 R11: ffff9cfa36fcc100 R12: 0000000000000cc0
May 6 08:38:08 test-ubnt kernel: [ 161.627475] R13: 0000000000000002 R14: ffff9cfa9a807c00 R15: 534d1cbf998a8f86
May 6 08:38:08 test-ubnt kernel: [ 161.629383] FS: 0000000000000000(0000) GS:ffff9cfa9ae00000(0063) knlGS:00000000f7d01700
May 6 08:38:08 test-ubnt kernel: [ 161.631335] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
May 6 08:38:08 test-ubnt kernel: [ 161.633289] CR2: 00000000ff82280c CR3: 00000000b59ec000 CR4: 00000000003406f0
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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
1 sibling, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-06 7:10 UTC (permalink / raw)
To: Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
New test on kernel Linux version 5.1.0-050100-generic. Same problem,
system crash after a few seconds.
Full kern.log: https://paste.ee/p/EmLsw
I can do access to my pc through SSH if useful.
starosta
Dne 3.5.2019 v 17:37 Joerg Roedel napsal(a):
> 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
>
[-- Attachment #2: kern.log --]
[-- Type: text/plain, Size: 10359 bytes --]
May 6 08:35:39 test-ubnt kernel: [ 0.000000] Linux version 5.1.0-050100-generic (kernel@gloin) (gcc version 8.3.0 (Ubuntu 8.3.0-7ubuntu1)) #201905052130 SMP Mon May 6 01:32:59 UTC 2019
May 6 08:35:39 test-ubnt kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.0-050100-generic root=UUID=91232716-4b81-4e1d-9d58-c2ad4d090e93 ro
...
May 6 08:37:31 test-ubnt kernel: [ 123.968163] usbserial: USB Serial deregistering driver FTDI USB Serial Device
May 6 08:37:31 test-ubnt kernel: [ 123.968416] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
May 6 08:37:31 test-ubnt kernel: [ 123.968438] usbcore: deregistering interface driver ftdi_sio
May 6 08:37:31 test-ubnt kernel: [ 123.968504] ftdi_sio 1-9:1.0: device disconnected
May 6 08:37:36 test-ubnt kernel: [ 129.425748] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:36 test-ubnt kernel: [ 129.597852] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa02000 flags=0x0020]
May 6 08:37:36 test-ubnt kernel: [ 129.600253] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa26000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 129.985262] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:37 test-ubnt kernel: [ 130.157935] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffb8a000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.159739] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xff9f8000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.544683] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:37 test-ubnt kernel: [ 130.716992] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfea16000 flags=0x0020]
May 6 08:37:37 test-ubnt kernel: [ 130.719369] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffbfb000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.104350] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:38 test-ubnt kernel: [ 131.279479] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa3c000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.664426] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:38 test-ubnt kernel: [ 131.837112] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffa32000 flags=0x0020]
May 6 08:37:38 test-ubnt kernel: [ 131.839540] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc5d000 flags=0x0020]
May 6 08:37:39 test-ubnt kernel: [ 132.223953] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:37:39 test-ubnt kernel: [ 132.397215] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc46000 flags=0x0020]
May 6 08:37:39 test-ubnt kernel: [ 132.398608] amd_iommu_report_page_fault: 5 callbacks suppressed
...
May 6 08:38:07 test-ubnt kernel: [ 160.289771] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa532000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.292232] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa53d000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.677243] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:38:07 test-ubnt kernel: [ 160.849877] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfa532000 flags=0x0020]
May 6 08:38:07 test-ubnt kernel: [ 160.852303] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xffc70000 flags=0x0020]
May 6 08:38:08 test-ubnt kernel: [ 161.237342] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May 6 08:38:08 test-ubnt kernel: [ 161.412400] xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfe8f0000 flags=0x0020]
May 6 08:38:08 test-ubnt kernel: [ 161.562930] general protection fault: 0000 [#1] SMP NOPTI
May 6 08:38:08 test-ubnt kernel: [ 161.563709] CPU: 0 PID: 1632 Comm: readua Not tainted 5.1.0-050100-generic #201905052130
May 6 08:38:08 test-ubnt kernel: [ 161.564493] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 4602 03/07/2019
May 6 08:38:08 test-ubnt kernel: [ 161.565323] RIP: 0010:__kmalloc+0xa5/0x220
May 6 08:38:08 test-ubnt kernel: [ 161.566116] Code: 65 49 8b 50 08 65 4c 03 05 80 c5 78 79 4d 8b 38 4d 85 ff 0f 84 2e 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd
May 6 08:38:08 test-ubnt kernel: [ 161.567913] RSP: 0018:ffffa8614237bcd0 EFLAGS: 00010202
May 6 08:38:08 test-ubnt kernel: [ 161.568840] RAX: 534d1cbf998a8f86 RBX: 534d1cbf998a8f86 RCX: 00000000000062cb
May 6 08:38:08 test-ubnt kernel: [ 161.569801] RDX: 00000000000062ca RSI: 0000000000000cc0 RDI: 0000000000028040
May 6 08:38:08 test-ubnt kernel: [ 161.570779] RBP: ffffa8614237bd00 R08: ffff9cfa9ae28040 R09: ffff9cfa9a807c00
May 6 08:38:08 test-ubnt kernel: [ 161.571778] R10: 0000000000000009 R11: ffff9cfa36fcc100 R12: 0000000000000cc0
May 6 08:38:08 test-ubnt kernel: [ 161.572796] R13: 0000000000000002 R14: ffff9cfa9a807c00 R15: 534d1cbf998a8f86
May 6 08:38:08 test-ubnt kernel: [ 161.573825] FS: 0000000000000000(0000) GS:ffff9cfa9ae00000(0063) knlGS:00000000f7d01700
May 6 08:38:08 test-ubnt kernel: [ 161.574882] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
May 6 08:38:08 test-ubnt kernel: [ 161.575907] CR2: 00000000ff82280c CR3: 00000000b59ec000 CR4: 00000000003406f0
May 6 08:38:08 test-ubnt kernel: [ 161.576966] Call Trace:
May 6 08:38:08 test-ubnt kernel: [ 161.578028] ? proc_do_submiturb+0xaf1/0xc70
May 6 08:38:08 test-ubnt kernel: [ 161.579109] proc_do_submiturb+0xaf1/0xc70
May 6 08:38:08 test-ubnt kernel: [ 161.580202] proc_submiturb_compat+0x81/0xb0
May 6 08:38:08 test-ubnt kernel: [ 161.581304] usbdev_do_ioctl+0x930/0xd70
May 6 08:38:08 test-ubnt kernel: [ 161.582415] ? _copy_from_user+0x3e/0x60
May 6 08:38:08 test-ubnt kernel: [ 161.583534] usbdev_compat_ioctl+0x10/0x20
May 6 08:38:08 test-ubnt kernel: [ 161.584622] __ia32_compat_sys_ioctl+0x13d/0x230
May 6 08:38:08 test-ubnt kernel: [ 161.585722] do_fast_syscall_32+0x9b/0x210
May 6 08:38:08 test-ubnt kernel: [ 161.586831] entry_SYSCALL_compat_after_hwframe+0x45/0x4d
May 6 08:38:08 test-ubnt kernel: [ 161.587962] RIP: 0023:0xf7f56929
May 6 08:38:08 test-ubnt kernel: [ 161.589096] Code: 85 d2 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 34 24 c3 8b 3c 24 c3 90 90 90 90 90 90 90 90 51 52 55 89 cd 0f 05 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
May 6 08:38:08 test-ubnt kernel: [ 161.591579] RSP: 002b:00000000ff822588 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
May 6 08:38:08 test-ubnt kernel: [ 161.592871] RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00000000802c550a
May 6 08:38:08 test-ubnt kernel: [ 161.594185] RDX: 0000000057b89bd0 RSI: 0000000000000033 RDI: 0000000000000002
May 6 08:38:08 test-ubnt kernel: [ 161.595508] RBP: 00000000ff8225e8 R08: 0000000000000000 R09: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.596797] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.598089] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
May 6 08:38:08 test-ubnt kernel: [ 161.599382] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ccp kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec k10temp wmi_bmof snd_hda_core joydev eeepc_wmi asus_wmi snd_hwdep sparse_keymap snd_pcm input_leds snd_timer snd soundcore usbserial mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu aesni_intel chash gpu_sched amd_iommu_v2 i2c_algo_bit ttm aes_x86_64 crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_piix4 drm r8169 ahci realtek libahci wmi video gpio_amdpt gpio_generic [last unloaded: ftdi_sio]
May 6 08:38:08 test-ubnt kernel: [ 161.610416] ---[ end trace e32a9be49aaeee88 ]---
May 6 08:38:08 test-ubnt kernel: [ 161.612558] RIP: 0010:__kmalloc+0xa5/0x220
May 6 08:38:08 test-ubnt kernel: [ 161.614259] Code: 65 49 8b 50 08 65 4c 03 05 80 c5 78 79 4d 8b 38 4d 85 ff 0f 84 2e 01 00 00 41 8b 59 20 49 8b 39 48 8d 4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 99 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd
May 6 08:38:08 test-ubnt kernel: [ 161.617879] RSP: 0018:ffffa8614237bcd0 EFLAGS: 00010202
May 6 08:38:08 test-ubnt kernel: [ 161.619761] RAX: 534d1cbf998a8f86 RBX: 534d1cbf998a8f86 RCX: 00000000000062cb
May 6 08:38:08 test-ubnt kernel: [ 161.621665] RDX: 00000000000062ca RSI: 0000000000000cc0 RDI: 0000000000028040
May 6 08:38:08 test-ubnt kernel: [ 161.623586] RBP: ffffa8614237bd00 R08: ffff9cfa9ae28040 R09: ffff9cfa9a807c00
May 6 08:38:08 test-ubnt kernel: [ 161.625513] R10: 0000000000000009 R11: ffff9cfa36fcc100 R12: 0000000000000cc0
May 6 08:38:08 test-ubnt kernel: [ 161.627475] R13: 0000000000000002 R14: ffff9cfa9a807c00 R15: 534d1cbf998a8f86
May 6 08:38:08 test-ubnt kernel: [ 161.629383] FS: 0000000000000000(0000) GS:ffff9cfa9ae00000(0063) knlGS:00000000f7d01700
May 6 08:38:08 test-ubnt kernel: [ 161.631335] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
May 6 08:38:08 test-ubnt kernel: [ 161.633289] CR2: 00000000ff82280c CR3: 00000000b59ec000 CR4: 00000000003406f0
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-06 7:10 ` StarostaCZ@gmail.com
@ 2019-05-15 7:54 ` StarostaCZ@gmail.com
2019-05-15 9:17 ` Oliver Neukum
0 siblings, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 7:54 UTC (permalink / raw)
To: Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
Hello,
can I still help with this problem? It's very important for us. Thank you.
starosta
Dne 6.5.2019 v 9:10 StarostaCZ@gmail.com napsal(a):
> New test on kernel Linux version 5.1.0-050100-generic. Same problem,
> system crash after a few seconds.
> Full kern.log: https://paste.ee/p/EmLsw
> I can do access to my pc through SSH if useful.
>
> starosta
>
> Dne 3.5.2019 v 17:37 Joerg Roedel napsal(a):
>> 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
>>
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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:43 ` StarostaCZ@gmail.com
0 siblings, 2 replies; 26+ messages in thread
From: Oliver Neukum @ 2019-05-15 9:17 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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 9:43 ` StarostaCZ@gmail.com
1 sibling, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 9:43 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
[-- Attachment #1: Type: text/html, Size: 2231 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-15 9:17 ` Oliver Neukum
2019-05-15 9:43 ` StarostaCZ@gmail.com
@ 2019-05-15 9:43 ` StarostaCZ@gmail.com
1 sibling, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 9:43 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
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
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?
starosta
Dne 15.5.2019 v 11:17 Oliver Neukum napsal(a):
> 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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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 11:22 ` StarostaCZ@gmail.com
0 siblings, 2 replies; 26+ messages in thread
From: Oliver Neukum @ 2019-05-15 9:46 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
[-- 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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
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 11:22 ` StarostaCZ@gmail.com
1 sibling, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 11:21 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
[-- Attachment #1: Type: text/html, Size: 1428 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-15 9:46 ` Oliver Neukum
2019-05-15 11:21 ` StarostaCZ@gmail.com
@ 2019-05-15 11:22 ` StarostaCZ@gmail.com
1 sibling, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 11:22 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
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?
> 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...).
starosta
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-15 11:21 ` StarostaCZ@gmail.com
@ 2019-05-15 13:54 ` Oliver Neukum
2019-05-15 14:15 ` StarostaCZ@gmail.com
0 siblings, 1 reply; 26+ messages in thread
From: Oliver Neukum @ 2019-05-15 13:54 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
[-- 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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-15 13:54 ` Oliver Neukum
@ 2019-05-15 14:15 ` StarostaCZ@gmail.com
2019-05-16 7:58 ` Oliver Neukum
0 siblings, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-15 14:15 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
Dne 15.5.2019 v 15:54 Oliver Neukum napsal(a):
> 1. Determine whether the bug depends on the use of an IOMMU
No, bug not depends on the use of an IOMMU. System crash on both cases.
> 2.Send a new report to the corresponding mailing list
Which mailing list is correct?
starosta
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-15 14:15 ` StarostaCZ@gmail.com
@ 2019-05-16 7:58 ` Oliver Neukum
2019-05-16 8:20 ` StarostaCZ@gmail.com
0 siblings, 1 reply; 26+ messages in thread
From: Oliver Neukum @ 2019-05-16 7:58 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
On Mi, 2019-05-15 at 16:15 +0200, StarostaCZ@gmail.com wrote:
> Dne 15.5.2019 v 15:54 Oliver Neukum napsal(a):
> > 1. Determine whether the bug depends on the use of an IOMMU
>
> No, bug not depends on the use of an IOMMU. System crash on both cases.
Interesting.
> > 2.Send a new report to the corresponding mailing list
>
> Which mailing list is correct?
In that case linux-usb@vger.kernel.org
HTH
Oliver
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-16 7:58 ` Oliver Neukum
@ 2019-05-16 8:20 ` StarostaCZ@gmail.com
2019-05-16 8:34 ` Oliver Neukum
0 siblings, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-16 8:20 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
Dne 16.5.2019 v 9:58 Oliver Neukum napsal(a):
>>> 2.Send a new report to the corresponding mailing list
>> Which mailing list is correct?
> In that case linux-usb@vger.kernel.org
>
> HTH
> Oliver
>
Is there some rules how to send bug report? Or I can send report with
"my amateur description"?
starosta
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-16 8:20 ` StarostaCZ@gmail.com
@ 2019-05-16 8:34 ` Oliver Neukum
2019-05-16 12:29 ` StarostaCZ@gmail.com
0 siblings, 1 reply; 26+ messages in thread
From: Oliver Neukum @ 2019-05-16 8:34 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
On Do, 2019-05-16 at 10:20 +0200, StarostaCZ@gmail.com wrote:
> Dne 16.5.2019 v 9:58 Oliver Neukum napsal(a):
> > > > 2.Send a new report to the corresponding mailing list
> > >
> > > Which mailing list is correct?
> >
> > In that case linux-usb@vger.kernel.org
> >
> > HTH
> > Oliver
> >
>
> Is there some rules how to send bug report? Or I can send report with
> "my amateur description"?
Mention
1. kernel version
2. whether this is known to be a regression
3. include the log with iommu disabled and mention that you disabled
the IOMMU
4. Include the output of lsusb
HTH
Oliver
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-16 8:34 ` Oliver Neukum
@ 2019-05-16 12:29 ` StarostaCZ@gmail.com
2019-05-16 13:11 ` Oliver Neukum
0 siblings, 1 reply; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-16 12:29 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
Dne 16.5.2019 v 10:34 Oliver Neukum napsal(a):
> Mention
>
> 1. kernel version
> 2. whether this is known to be a regression
Sorry for question, can you more specify what you mean?
> 3. include the log with iommu disabled and mention that you disabled
> the IOMMU
> 4. Include the output of lsusb
>
> HTH
> Oliver
Thank you
starosta
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-16 12:29 ` StarostaCZ@gmail.com
@ 2019-05-16 13:11 ` Oliver Neukum
2019-05-16 13:36 ` StarostaCZ@gmail.com
0 siblings, 1 reply; 26+ messages in thread
From: Oliver Neukum @ 2019-05-16 13:11 UTC (permalink / raw)
To: StarostaCZ@gmail.com, Joerg Roedel, Johan Hovold
Cc: iommu, linux-usb, Mathias Nyman
On Do, 2019-05-16 at 14:29 +0200, StarostaCZ@gmail.com wrote:
> Dne 16.5.2019 v 10:34 Oliver Neukum napsal(a):
> > Mention
> >
> > 1. kernel version
> > 2. whether this is known to be a regression
>
> Sorry for question, can you more specify what you mean?
You will be asked whether this worked in earlier version of the
kernel. The answer would be: yes, no, unknown (why)
HTH
Oliver
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
2019-05-16 13:11 ` Oliver Neukum
@ 2019-05-16 13:36 ` StarostaCZ@gmail.com
0 siblings, 0 replies; 26+ messages in thread
From: StarostaCZ@gmail.com @ 2019-05-16 13:36 UTC (permalink / raw)
To: Oliver Neukum, Joerg Roedel, Johan Hovold; +Cc: iommu, linux-usb, Mathias Nyman
Dne 16.5.2019 v 15:11 Oliver Neukum napsal(a):
>
> You will be asked whether this worked in earlier version of the
> kernel. The answer would be: yes, no, unknown (why)
>
> HTH
> Oliver
>
Thank you, I sent new report.
starosta
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2019-05-16 13:38 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox