On 01/20/2016 09:43 AM, Laine Stump wrote:
On 01/20/2016 09:10 AM, Baoquan He wrote:
I found it archived in this place well:
https://www.mail-archive.com/iommu@lists.linux-foundation.org/msg10687.html
But pasted dmesg has been lost. putting "lspci -tv" and "lspci -vvv&q
tes, it now hangs "forever" (I
accidentally rebooted with that kernel and left without checking;
several hours later when I returned it was still hung).
I'll also grab the latest upstream sources and build/test that today.
Thanks
Baoquan
On 12/02/15 at 02:56pm, Laine Stump wrote
On 11/18/2015 10:18 AM, Joerg Roedel wrote:
Hello Laine,
On Thu, Nov 12, 2015 at 12:33:53PM -0500, Laine Stump wrote:
After a crash course in kernel building from Alex, I bisected down
to commit aafd8ba - a kernel built without this commit succeeds in
setting up all the devices mentioned
(Cc'ing Joerg because I have a question for him down towards the bottom...)
On 11/04/2015 12:24 PM, Laine Stump wrote:
Last week I upgraded my Fedora 22 AMD 990FX system from kernel 4.1.10 to
4.2.3 (standard Fedora builds) and multiple devices stopped working:
* 00:14.2 Audio device: Adv
On 11/05/2015 02:05 PM, Laine Stump wrote:
On 11/04/2015 04:08 PM, Alex Williamson wrote:
I built a 4.2.3 kernel for my 990fx system and can't seem to reproduce
it. Does 'lspci -k' for those devices show any driver?
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/AT
On 11/04/2015 04:08 PM, Alex Williamson wrote:
On Wed, 2015-11-04 at 12:24 -0500, Laine Stump wrote:
Last week I upgraded my Fedora 22 AMD 990FX system from kernel 4.1.10 to
4.2.3 (standard Fedora builds) and multiple devices stopped working:
* 00:14.2 Audio device: Advanced Micro Devices, Inc
Last week I upgraded my Fedora 22 AMD 990FX system from kernel 4.1.10 to
4.2.3 (standard Fedora builds) and multiple devices stopped working:
* 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00
Azalia (Intel HDA) (rev 40)
* 02:00.[01] Ethernet controller: Intel Corporation 82
On 05/20/2014 05:53 PM, Alex Williamson wrote:
> The driver_override field allows us to specify the driver for a device
> rather than relying on the driver to provide a positive match of the
> device. This shortcuts the existing process of looking up the vendor
> and device ID, adding them to the
