From: Joerg Roedel <joro@8bytes.org>
To: Borislav Petkov <bp@alien8.de>,
suravee.suthikulpanit@amd.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iommu/amd: Add logic to decode AMD IOMMU event flag
Date: Tue, 2 Apr 2013 17:03:04 +0200 [thread overview]
Message-ID: <20130402150302.GF15687@8bytes.org> (raw)
In-Reply-To: <20130402144037.GE5488@pd.tnic>
On Tue, Apr 02, 2013 at 04:40:37PM +0200, Borislav Petkov wrote:
> While you guys are at it, can someone fix this too pls (ASUS board with
> a PD on it).
>
> [ 0.220342] [Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
> [ 0.220398] [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
> [ 0.220451] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
> [ 0.220506] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
That is actually a BIOS problem. I wonder whether it would help to turn this
into a WARN_ON to get the board vendors to release working BIOSes.
Opinions?
Joerg
next prev parent reply other threads:[~2013-04-02 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 23:51 [PATCH 1/3] iommu/amd: Add logic to decode AMD IOMMU event flag suravee.suthikulpanit
2013-04-01 13:47 ` Suravee Suthikulanit
2013-04-02 14:33 ` Joerg Roedel
2013-04-02 14:39 ` Suravee Suthikulanit
2013-04-02 14:40 ` Borislav Petkov
2013-04-02 15:03 ` Joerg Roedel [this message]
2013-04-02 15:29 ` Borislav Petkov
2013-04-02 15:41 ` Suravee Suthikulpanit
2013-04-02 16:06 ` Joerg Roedel
2013-04-02 16:04 ` Joerg Roedel
2013-04-02 16:17 ` Borislav Petkov
2013-04-02 16:33 ` Joerg Roedel
2013-04-02 19:32 ` Borislav Petkov
2013-04-02 20:59 ` Joerg Roedel
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=20130402150302.GF15687@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.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