Linux-Wireless Archive on lore.kernel.org
 help / Atom feed
* MT76x2U crashes XHCI driver on AMD Ryzen system
@ 2019-01-10 22:55 Rosen Penev
  2019-01-11 17:29 ` Lorenzo Bianconi
  0 siblings, 1 reply; 11+ messages in thread
From: Rosen Penev @ 2019-01-10 22:55 UTC (permalink / raw)
  To: linux-wireless; +Cc: lorenzo.bianconi

I have an ALFA AWUS036ACM and whenever I plug it in, the XHCI driver
dies. This is on an ASRock X370 motherboard. Kernel 4.20 Arch Linux.

After plugging in the adapter, the integrated wireless chip (Intel
3168) also dies. Disabling the motherboard wireless does not help.
Here are two fairly similar logs. First with Intel 3168 and the second
with it disabled in UEFI.

kernel: xhci_hcd 0000:03:00.0: xHCI host not responding to stop
endpoint command.
kernel: xhci_hcd 0000:03:00.0: xHCI host controller not responding, assume dead
kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up
kernel: usb 1-9: USB disconnect, device number 2
kernel: usb 1-14: USB disconnect, device number 3
bluetoothd[506]: Endpoint unregistered: sender=:1.151
path=/MediaEndpoint/A2DPSource
bluetoothd[506]: Endpoint unregistered: sender=:1.151
path=/MediaEndpoint/A2DPSink
systemd[1]: Starting Load/Save RF Kill Switch Status...
NetworkManager[512]: <info>  [1547157527.0255] bluez5: NAP: removed
interface B0:35:9F:2D:73:1D
systemd[1]: Stopped target Bluetooth.
systemd[1]: Started Load/Save RF Kill Switch Status.
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
kkuid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
kernel: audit: type=1131 audit(1547157532.035:57): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
kernel: iwlwifi 0000:27:00.0: iwl_pcie_cmdq_reclaim: Read index for
DMA queue txq id (0), index 0 is out of range [0-256] 61 60.
iwlwifi 0000:27:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x00000000ff442000 flags=0x0020]
kernel: iwlwifi 0000:27:00.0: HCMD_ACTIVE already clear for command
REPLY_SF_CFG_CMD
iwlwifi 0000:27:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue
txq id (0), index 0 is out of range [0-256] 61 60.

Folllowed by more iwlwifi errors as well as kernel crashdumps.

Without iwlwifi:

kernel: usb 1-14: new high-speed USB device number 3 using xhci_hcd
kernel: usb 1-14: New USB device found, idVendor=0e8d, idProduct=7612,
bcdDevice= 1.00
kernel: usb 1-14: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-14: Product: Wireless
kernel: usb 1-14: Manufacturer: MediaTek Inc.
kernel: usb 1-14: SerialNumber: 000000000
mtp-probe[1400]: checking bus 1, device 3:
"/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-14"
mtp-probe[1400]: bus: 1, device: 3 was not an MTP device
kernel: usb 1-14: reset high-speed USB device number 3 using xhci_hcd
kernel: mt76x2u 1-14:1.0: ASIC revision: 76120044
kernel: mt76x2u 1-14:1.0: ROM patch build: 20140408060640a
kernel: xhci_hcd 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x00000000f6d5c400 flags=0x0000]
kernel: mt76x2u 1-14:1.0: firmware upload timed out
kernel: xhci_hcd 0000:03:00.0: xHCI host not responding to stop
endpoint command.
kernel: xhci_hcd 0000:03:00.0: xHCI host controller not responding, assume dead
kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up
kernel: usb 1-9: USB disconnect, device number 2
bluetoothd[489]: Endpoint unregistered: sender=:1.150
path=/MediaEndpoint/A2DPSource
kernel: usb 1-14: USB disconnect, device number 3
NetworkManager[496]: <info>  [1547157974.3360] bluez5: NAP: removed
interface B0:35:9F:2D:73:1D
bluetoothd[489]: Endpoint unregistered: sender=:1.150
path=/MediaEndpoint/A2DPSink
systemd[1]: Starting Load/Save RF Kill Switch Status...
systemd[1]: Stopped target Bluetooth.
systemd[1]: Started Load/Save RF Kill Switch Status.
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
kernel: audit: type=1130 audit(1547157974.336:52): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-localed comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-hostnamed comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
kernel: audit: type=1131 audit(1547157977.826:53): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=systemd-localed
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
audit: type=1131 audit(1547157977.826:54): pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-hostnamed comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
kernel: audit: type=1131 audit(1547157979.346:55): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
kernel: mt76x2u 1-14:1.0: MAC RX failed to stop
kernel: mt76x2u: probe of 1-14:1.0 failed with error -5
kernel: usbcore: registered new interface driver mt76x2u
geoclue[785]: Service not used for 60 seconds. Shutting down..
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
kernel: audit: type=1131 audit(1547157990.969:56): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-10 22:55 MT76x2U crashes XHCI driver on AMD Ryzen system Rosen Penev
@ 2019-01-11 17:29 ` Lorenzo Bianconi
  2019-01-11 19:01   ` Rosen Penev
  0 siblings, 1 reply; 11+ messages in thread
From: Lorenzo Bianconi @ 2019-01-11 17:29 UTC (permalink / raw)
  To: Rosen Penev; +Cc: linux-wireless

>
> I have an ALFA AWUS036ACM and whenever I plug it in, the XHCI driver
> dies. This is on an ASRock X370 motherboard. Kernel 4.20 Arch Linux.
>
> After plugging in the adapter, the integrated wireless chip (Intel
> 3168) also dies. Disabling the motherboard wireless does not help.
> Here are two fairly similar logs. First with Intel 3168 and the second
> with it disabled in UEFI.
>

[...]

> Without iwlwifi:
>
> kernel: usb 1-14: new high-speed USB device number 3 using xhci_hcd
> kernel: usb 1-14: New USB device found, idVendor=0e8d, idProduct=7612,
> bcdDevice= 1.00
> kernel: usb 1-14: New USB device strings: Mfr=2, Product=3, SerialNumber=4
> usb 1-14: Product: Wireless
> kernel: usb 1-14: Manufacturer: MediaTek Inc.
> kernel: usb 1-14: SerialNumber: 000000000
> mtp-probe[1400]: checking bus 1, device 3:
> "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-14"
> mtp-probe[1400]: bus: 1, device: 3 was not an MTP device
> kernel: usb 1-14: reset high-speed USB device number 3 using xhci_hcd
> kernel: mt76x2u 1-14:1.0: ASIC revision: 76120044
> kernel: mt76x2u 1-14:1.0: ROM patch build: 20140408060640a
> kernel: xhci_hcd 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT

Are you using the driver in a VM or directly in the host? This is an
error reported by AMD iommu driver

Regards,
Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-11 17:29 ` Lorenzo Bianconi
@ 2019-01-11 19:01   ` Rosen Penev
  2019-01-13 13:33     ` Lorenzo Bianconi
  0 siblings, 1 reply; 11+ messages in thread
From: Rosen Penev @ 2019-01-11 19:01 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: linux-wireless



On Jan 11, 2019, at 09:29, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:

>> 
>> I have an ALFA AWUS036ACM and whenever I plug it in, the XHCI driver
>> dies. This is on an ASRock X370 motherboard. Kernel 4.20 Arch Linux.
>> 
>> After plugging in the adapter, the integrated wireless chip (Intel
>> 3168) also dies. Disabling the motherboard wireless does not help.
>> Here are two fairly similar logs. First with Intel 3168 and the second
>> with it disabled in UEFI.
>> 
> 
> [...]
> 
>> Without iwlwifi:
>> 
>> kernel: usb 1-14: new high-speed USB device number 3 using xhci_hcd
>> kernel: usb 1-14: New USB device found, idVendor=0e8d, idProduct=7612,
>> bcdDevice= 1.00
>> kernel: usb 1-14: New USB device strings: Mfr=2, Product=3, SerialNumber=4
>> usb 1-14: Product: Wireless
>> kernel: usb 1-14: Manufacturer: MediaTek Inc.
>> kernel: usb 1-14: SerialNumber: 000000000
>> mtp-probe[1400]: checking bus 1, device 3:
>> "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-14"
>> mtp-probe[1400]: bus: 1, device: 3 was not an MTP device
>> kernel: usb 1-14: reset high-speed USB device number 3 using xhci_hcd
>> kernel: mt76x2u 1-14:1.0: ASIC revision: 76120044
>> kernel: mt76x2u 1-14:1.0: ROM patch build: 20140408060640a
>> kernel: xhci_hcd 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
> 
> Are you using the driver in a VM or directly in the host? This is an
> error reported by AMD iommu driver
Direct. No VM used. This is the only peripheral causing this issue.
> 
> Regards,
> Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-11 19:01   ` Rosen Penev
@ 2019-01-13 13:33     ` Lorenzo Bianconi
       [not found]       ` <1547404075.1582.0@smtp.gmail.com>
  0 siblings, 1 reply; 11+ messages in thread
From: Lorenzo Bianconi @ 2019-01-13 13:33 UTC (permalink / raw)
  To: Rosen Penev; +Cc: linux-wireless

>
> Direct. No VM used. This is the only peripheral causing this issue.

Is the device connected to a usb3.0 port? If so, could you please try
to connect the dongle to a 2.0 one?
Could you please double check if IOMMU is enabled?

Regards,
Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
       [not found]       ` <1547404075.1582.0@smtp.gmail.com>
@ 2019-01-13 19:00         ` Lorenzo Bianconi
  2019-01-14  2:20           ` Rosen Penev
  0 siblings, 1 reply; 11+ messages in thread
From: Lorenzo Bianconi @ 2019-01-13 19:00 UTC (permalink / raw)
  To: Rosen Penev; +Cc: linux-wireless

>
>
> On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
>
> Direct. No VM used. This is the only peripheral causing this issue.
>
> Is the device connected to a usb3.0 port? If so, could you please try to connect the dongle to a 2.0 one?
>
> I tried through a USB 2.0 port. Shouldn't make a difference as they both use the xhci driver.
>

mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)

> Could you please double check if IOMMU is enabled?
>

Have you tried to disable it? Does it make any difference?

Regards,
Lorenzo

> It is.
>
> Note that this does not happen on kernel 4.15 (Ubuntu's kernel) as mt76 lacks support.
>
> Regards, Lorenzo
>
>
>

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-13 19:00         ` Lorenzo Bianconi
@ 2019-01-14  2:20           ` Rosen Penev
  2019-01-14  3:13             ` Samuel Sieb
  2019-01-14  9:18             ` Lorenzo Bianconi
  0 siblings, 2 replies; 11+ messages in thread
From: Rosen Penev @ 2019-01-14  2:20 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: linux-wireless

On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
<lorenzo.bianconi@redhat.com> wrote:
>
> >
> >
> > On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> >
> > Direct. No VM used. This is the only peripheral causing this issue.
> >
> > Is the device connected to a usb3.0 port? If so, could you please try to connect the dongle to a 2.0 one?
> >
> > I tried through a USB 2.0 port. Shouldn't make a difference as they both use the xhci driver.
> >
>
> mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)
Tried a USB 3 port. Same result.
>
> > Could you please double check if IOMMU is enabled?
> >
>
> Have you tried to disable it? Does it make any difference?
No idea how. UEFI doesn't seem to show anything similar.

Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241
>
> Regards,
> Lorenzo
>
> > It is.
> >
> > Note that this does not happen on kernel 4.15 (Ubuntu's kernel) as mt76 lacks support.
> >
> > Regards, Lorenzo
> >
> >
> >

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-14  2:20           ` Rosen Penev
@ 2019-01-14  3:13             ` Samuel Sieb
  2019-01-14  9:18             ` Lorenzo Bianconi
  1 sibling, 0 replies; 11+ messages in thread
From: Samuel Sieb @ 2019-01-14  3:13 UTC (permalink / raw)
  To: linux-wireless

On 1/13/19 6:20 PM, Rosen Penev wrote:
> On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
> <lorenzo.bianconi@redhat.com> wrote:
>>> Could you please double check if IOMMU is enabled?
>>>
>>
>> Have you tried to disable it? Does it make any difference?
> No idea how. UEFI doesn't seem to show anything similar.
> 
> Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241

As mentioned in that bug report, adding "iommu=off" to the kernel 
command line will disable it.  I think there's also an "iommu=soft" 
option, but I'm not sure what that does.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-14  2:20           ` Rosen Penev
  2019-01-14  3:13             ` Samuel Sieb
@ 2019-01-14  9:18             ` Lorenzo Bianconi
  2019-01-14  9:22               ` Tom Psyborg
  2019-01-14 20:06               ` Rosen Penev
  1 sibling, 2 replies; 11+ messages in thread
From: Lorenzo Bianconi @ 2019-01-14  9:18 UTC (permalink / raw)
  To: Rosen Penev; +Cc: linux-wireless

> On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
> <lorenzo.bianconi@redhat.com> wrote:
> >
> > >
> > >
> > > On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> > >
> > > Direct. No VM used. This is the only peripheral causing this issue.
> > >
> > > Is the device connected to a usb3.0 port? If so, could you please try to connect the dongle to a 2.0 one?
> > >
> > > I tried through a USB 2.0 port. Shouldn't make a difference as they both use the xhci driver.
> > >
> >
> > mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)
> Tried a USB 3 port. Same result.
> >
> > > Could you please double check if IOMMU is enabled?
> > >
> >
> > Have you tried to disable it? Does it make any difference?
> No idea how. UEFI doesn't seem to show anything similar.
> 
> Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241

You should be able to disable iommu using GRUB_CMDLINE_LINUX in
/etc/default/grub (I guess setting iommu=off and reinstalling grub)
https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB

Regards,
Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-14  9:18             ` Lorenzo Bianconi
@ 2019-01-14  9:22               ` Tom Psyborg
  2019-01-14 20:06               ` Rosen Penev
  1 sibling, 0 replies; 11+ messages in thread
From: Tom Psyborg @ 2019-01-14  9:22 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: Rosen Penev, linux-wireless

On 14/01/2019, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
>> On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
>> <lorenzo.bianconi@redhat.com> wrote:
>> >
>> > >
>> > >
>> > > On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi
>> > > <lorenzo.bianconi@redhat.com> wrote:
>> > >
>> > > Direct. No VM used. This is the only peripheral causing this issue.
>> > >
>> > > Is the device connected to a usb3.0 port? If so, could you please try
>> > > to connect the dongle to a 2.0 one?
>> > >
>> > > I tried through a USB 2.0 port. Shouldn't make a difference as they
>> > > both use the xhci driver.
>> > >
>> >
>> > mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)
>> Tried a USB 3 port. Same result.
>> >
>> > > Could you please double check if IOMMU is enabled?
>> > >
>> >
>> > Have you tried to disable it? Does it make any difference?
>> No idea how. UEFI doesn't seem to show anything similar.
>>
>> Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241
>
> You should be able to disable iommu using GRUB_CMDLINE_LINUX in
> /etc/default/grub (I guess setting iommu=off and reinstalling grub)
> https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB
>
> Regards,
> Lorenzo
>

updating grub, not reinstalling

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-14  9:18             ` Lorenzo Bianconi
  2019-01-14  9:22               ` Tom Psyborg
@ 2019-01-14 20:06               ` Rosen Penev
  2019-01-15  9:04                 ` Lorenzo Bianconi
  1 sibling, 1 reply; 11+ messages in thread
From: Rosen Penev @ 2019-01-14 20:06 UTC (permalink / raw)
  To: Lorenzo Bianconi; +Cc: linux-wireless

On Mon, Jan 14, 2019 at 1:18 AM Lorenzo Bianconi
<lorenzo.bianconi@redhat.com> wrote:
>
> > On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
> > <lorenzo.bianconi@redhat.com> wrote:
> > >
> > > >
> > > >
> > > > On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> > > >
> > > > Direct. No VM used. This is the only peripheral causing this issue.
> > > >
> > > > Is the device connected to a usb3.0 port? If so, could you please try to connect the dongle to a 2.0 one?
> > > >
> > > > I tried through a USB 2.0 port. Shouldn't make a difference as they both use the xhci driver.
> > > >
> > >
> > > mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)
> > Tried a USB 3 port. Same result.
> > >
> > > > Could you please double check if IOMMU is enabled?
> > > >
> > >
> > > Have you tried to disable it? Does it make any difference?
> > No idea how. UEFI doesn't seem to show anything similar.
> >
> > Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241
>
> You should be able to disable iommu using GRUB_CMDLINE_LINUX in
> /etc/default/grub (I guess setting iommu=off and reinstalling grub)
> https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB
Yep. Working great now. I wonder what mt76 is doing to cause the crash though...
>
> Regards,
> Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: MT76x2U crashes XHCI driver on AMD Ryzen system
  2019-01-14 20:06               ` Rosen Penev
@ 2019-01-15  9:04                 ` Lorenzo Bianconi
  0 siblings, 0 replies; 11+ messages in thread
From: Lorenzo Bianconi @ 2019-01-15  9:04 UTC (permalink / raw)
  To: Rosen Penev; +Cc: linux-wireless

> On Mon, Jan 14, 2019 at 1:18 AM Lorenzo Bianconi
> <lorenzo.bianconi@redhat.com> wrote:
> >
> > > On Sun, Jan 13, 2019 at 11:00 AM Lorenzo Bianconi
> > > <lorenzo.bianconi@redhat.com> wrote:
> > > >
> > > > >
> > > > >
> > > > > On Sun, Jan 13, 2019 at 5:33 AM, Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> > > > >
> > > > > Direct. No VM used. This is the only peripheral causing this issue.
> > > > >
> > > > > Is the device connected to a usb3.0 port? If so, could you please try to connect the dongle to a 2.0 one?
> > > > >
> > > > > I tried through a USB 2.0 port. Shouldn't make a difference as they both use the xhci driver.
> > > > >
> > > >
> > > > mt76x2u supports scatter-gather on usb 3.0 (not on 2.0)
> > > Tried a USB 3 port. Same result.
> > > >
> > > > > Could you please double check if IOMMU is enabled?
> > > > >
> > > >
> > > > Have you tried to disable it? Does it make any difference?
> > > No idea how. UEFI doesn't seem to show anything similar.
> > >
> > > Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202241
> >
> > You should be able to disable iommu using GRUB_CMDLINE_LINUX in
> > /etc/default/grub (I guess setting iommu=off and reinstalling grub)
> > https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB
> Yep. Working great now. I wonder what mt76 is doing to cause the crash though...

Thanks for bisecting the issue. I think amd iommu does not support well usb scatter-gather
(used by default in mt76u). I am working on a series in order to add the possibility to
disable it.

Regards,
Lorenzo

> >
> > Regards,
> > Lorenzo

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, back to index

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-10 22:55 MT76x2U crashes XHCI driver on AMD Ryzen system Rosen Penev
2019-01-11 17:29 ` Lorenzo Bianconi
2019-01-11 19:01   ` Rosen Penev
2019-01-13 13:33     ` Lorenzo Bianconi
     [not found]       ` <1547404075.1582.0@smtp.gmail.com>
2019-01-13 19:00         ` Lorenzo Bianconi
2019-01-14  2:20           ` Rosen Penev
2019-01-14  3:13             ` Samuel Sieb
2019-01-14  9:18             ` Lorenzo Bianconi
2019-01-14  9:22               ` Tom Psyborg
2019-01-14 20:06               ` Rosen Penev
2019-01-15  9:04                 ` Lorenzo Bianconi

Linux-Wireless Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-wireless/0 linux-wireless/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wireless linux-wireless/ https://lore.kernel.org/linux-wireless \
		linux-wireless@vger.kernel.org linux-wireless@archiver.kernel.org
	public-inbox-index linux-wireless


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wireless


AGPL code for this site: git clone https://public-inbox.org/ public-inbox