iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
To: Alex Williamson
	<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Laine Stump <laine-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Regression in kernel 4.2.3+ (relative to 4.1.10) on AMD 990FX system with IOMMU enabled
Date: Thu, 5 Nov 2015 09:11:15 -0500	[thread overview]
Message-ID: <563B6383.50701@compro.net> (raw)
In-Reply-To: <1446671291.3692.147.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

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. [AMD/ATI] SBx00
>> Azalia (Intel HDA) (rev 40)
>>
>> * 02:00.[01] Ethernet controller: Intel Corporation 82576 Gigabit
>> Network Connection
>>
>> * 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
>> HDMI Audio [Radeon HD 5400/6300 Series]
>>
>> (The 1st is integrated on the motherboard, the 2nd & 3rd are behind an
>> AMD RD890 pci-pci bridge. There may be other devices failing, but these
>> are the ones immediately obvious.)
>>
>> Whatever is the source of the failure, it ends up that the drivers for
>> these devices aren't loaded.
>>
>> At Alex Williamson's suggestion, I tried disabling IOMMU in the BIOS,
>> and magically all the devices resumed normal operation (except that I
>> can't do vfio device assignment because the IOMMU is disabled).
>>
>> Reverting to kernel 4.1.10 very definitely eliminates the problem. I've
>> also tried kernel 4.2.5 and it has the same problem as 4.2.3 (these
>> three are the only pre-built kernels for F22). I can provide dmesg /
>> lspci output from each of these, or any other debug info anyone might
>> like me to gather.
>
> 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?  Does 'lsmod'
> show the drivers loaded, igb and snd_hda_intel?  If not, does manually
> modprobe'ing either of those drivers change anything?  You haven't
> installed a script that writes to driver_override or setup a
> configuration where those devices are claimed by pci-stub and forgotten
> about it, have you? (it's happened to me)  Otherwise, dmesg is probably
> a good place to start.  Thanks,
>
> Alex

I'm also running one of these with a 4.2.5 kernel with no IOMMU issues.

mark

  parent reply	other threads:[~2015-11-05 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:24 Regression in kernel 4.2.3+ (relative to 4.1.10) on AMD 990FX system with IOMMU enabled Laine Stump
     [not found] ` <563A3F64.50808-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-04 21:08   ` Alex Williamson
     [not found]     ` <1446671291.3692.147.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-05 14:11       ` Mark Hounschell [this message]
2015-11-05 19:05       ` Laine Stump
     [not found]         ` <563BA893.4020202-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-08 16:52           ` Laine Stump
2015-11-12 17:33   ` Laine Stump
     [not found]     ` <5644CD81.2020304-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-18 15:18       ` Joerg Roedel
     [not found]         ` <20151118151841.GA2517-l3A5Bk7waGM@public.gmane.org>
2015-12-02 19:56           ` Laine Stump
     [not found]             ` <565F4CF5.90107-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-01-20 12:39               ` Joerg Roedel
2016-01-20 14:10               ` Baoquan He
     [not found]                 ` <20160120141025.GA13677-ejN7fcUYdH/by3iVrkZq2A@public.gmane.org>
2016-01-20 14:43                   ` Laine Stump
     [not found]                     ` <569F9D0E.20309-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-05 21:09                       ` Laine Stump

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=563B6383.50701@compro.net \
    --to=markh-n2qnkt385d+stnjn9+bgxg@public.gmane.org \
    --cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=laine-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).