All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laine Stump <laine-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Joerg Roedel <jroedel-l3A5Bk7waGM@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, 12 Nov 2015 12:33:53 -0500	[thread overview]
Message-ID: <5644CD81.2020304@redhat.com> (raw)
In-Reply-To: <563A3F64.50808-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

(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: 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.

That is actually a bit misleading/incorrect - the igb device is 
apparently loaded for one of the two devices in the 82576 card 
(02:00.0), and one (out of expected 7) VF device entries is created in 
/sys/devices/pci0000:00/*, but something happens that results in none of 
these devices being put in /sys/class/net, the other 6 VFs don't get 
entries in /sys/device/pci0000:00/*, and the igb driver isn't loaded for 
the 2nd PF (02:00.1).

> 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).

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, adding it causes failure (and a very long 
delay during boot). Joerg, do you have any ideas for debugging the 
problem further to see what in the commit causes this problem? (note 
that 2 other people with the same chipset but slightly different 
hardware plugged into it report no failure - see the other replies to 
the parent of this message for more detail). I'm happy to build a kernel 
with any suggested patches and report results...

commit aafd8ba0ca74894b9397e412bbd7f8ea2662ead8
Author: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
Date:   Thu May 28 18:41:39 2015 +0200

     iommu/amd: Implement add_device and remove_device

     Implement these two iommu-ops call-backs to make use of the
     initialization and notifier features of the iommu core.

     Signed-off-by: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>

  parent reply	other threads:[~2015-11-12 17:33 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
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 [this message]
     [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=5644CD81.2020304@redhat.com \
    --to=laine-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jroedel-l3A5Bk7waGM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.