From: CACook@quantum-sci.com
To: ath10k@lists.infradead.org
Subject: Re: Buss Reset Problem
Date: Thu, 09 Jul 2015 06:33:21 -0700 [thread overview]
Message-ID: <3319636.gBuGFxuZFH@andromeda> (raw)
In-Reply-To: <3969592.crxpsBTBQa@andromeda>
On Monday 06 July 2015 8:04:39 CACook@quantum-sci.com wrote:
>
> CPU: Intel(R) Xeon(R) CPU E3-1265L v3 @ 2.50GHz
> KVM: qemu-kvm-1.5.3-86.el7_1.2.x86_64
> Kernel: 4.1.1-1.el7.elrepo.x86_64, and kernel-3.10.0-229.7.2.el7.x86_64
> Host & Guest: CentOS 7.1
> Using virt-manager-1.1.0-12.el7.noarch to create, configure, and start guest
> I am trying to do a PCI passthrough of a QCA988X wifi card. It's a Doodle Labs military-grade 802.11ac miniPCI card. This card configures nicely on the host, and seems to pass through to the KVM guest, but early in the boot of the guest it says "Unknown header type" at the wifi's bus address. And sure enough, lspci -vv on the host then shows:
> !!! Unknown header type 7f
> Kernel driver in use: vfio-pci
> It seems to be the buss reset problem, as outlined here:
> http://www.gossamer-threads.com/lists/linux/kernel/2054846
>
> ... Except my card locks up on boot of the KVM guest.
>
> When I logged a bug at QEMU (https://bugs.launchpad.net/qemu/+bug/1471583), Alex suggested I add to the patch:
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x003c, quirk_no_bus_reset);
>
> ... So I am in the process of trying that now.
So that's it for the Doodle Labs ACE-DB-3. It went back yesterday -- doesn't work with Linux.
It's not the buss reset problem as I patched quirks.c.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-07-09 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:04 Buss Reset Problem CACook
2015-07-09 13:33 ` CACook [this message]
2015-07-09 13:46 ` Michal Kazior
2015-07-09 14:11 ` CACook
2015-07-10 5:48 ` Michal Kazior
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=3319636.gBuGFxuZFH@andromeda \
--to=cacook@quantum-sci.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox