From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: MT76x2U crashes XHCI driver on AMD Ryzen system
Date: Fri, 11 Jan 2019 18:29:02 +0100 [thread overview]
Message-ID: <CAJ0CqmVNF83bWgc+LSQ3_i=zfp-sXC5Nf=nKfqB3SWa8r7sKdQ@mail.gmail.com> (raw)
In-Reply-To: <CAKxU2N9o5WeUwFMUwwXKHaPj7R+oiSKV1c2n8RtXwGNZRtw5Sw@mail.gmail.com>
>
> 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
next prev parent reply other threads:[~2019-01-11 17:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 22:55 MT76x2U crashes XHCI driver on AMD Ryzen system Rosen Penev
2019-01-11 17:29 ` Lorenzo Bianconi [this message]
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
2019-02-18 14:37 ` Stanislaw Gruszka
2019-02-18 15:15 ` Lorenzo Bianconi
2019-02-18 17:01 ` Robin Murphy
2019-02-19 11:08 ` Stanislaw Gruszka
2019-02-26 10:05 ` Joerg Roedel
2019-02-26 10:34 ` Stanislaw Gruszka
2019-02-26 10:44 ` Joerg Roedel
2019-02-26 11:24 ` Stanislaw Gruszka
2019-02-28 9:04 ` Stanislaw Gruszka
2019-02-28 10:42 ` Stanislaw Gruszka
2019-02-28 12:19 ` Stanislaw Gruszka
2019-02-28 13:40 ` Joerg Roedel
2019-03-04 7:10 ` Stanislaw Gruszka
2019-03-04 7:20 ` Rosen Penev
2019-03-11 8:43 ` Stanislaw Gruszka
2019-03-11 9:03 ` [PATCH] iommu/amd: fix sg->dma_address for sg->offset bigger than PAGE_SIZE Stanislaw Gruszka
2019-03-11 15:47 ` Alexander Duyck
2019-03-12 7:08 ` Stanislaw Gruszka
2019-03-12 15:18 ` Alexander Duyck
2019-03-13 9:03 ` [PATCH v2] " Stanislaw Gruszka
2019-03-18 10:17 ` Joerg Roedel
2019-03-12 7:13 ` MT76x2U crashes XHCI driver on AMD Ryzen system Stanislaw Gruszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ0CqmVNF83bWgc+LSQ3_i=zfp-sXC5Nf=nKfqB3SWa8r7sKdQ@mail.gmail.com' \
--to=lorenzo.bianconi@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rosenp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).