From: Valdis.Kletnieks@vt.edu
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: "Udo A. Steinberg" <udo@hypervisor.org>,
Dave Airlie <airlied@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Kernel panic with intel_iommu=on
Date: Wed, 12 Oct 2011 20:18:38 -0400 [thread overview]
Message-ID: <11892.1318465118@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 12 Oct 2011 10:19:55 PDT." <1318439995.4465.8.camel@nimitz>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Wed, 12 Oct 2011 10:19:55 PDT, Dave Hansen said:
> I'm seeing this all of a sudden on 3.1 kernels. It might be because of
> the firefox upgrade to 5.0 that others were talking about. But, it's
> quite easy to trigger. Seems to happen in the first 10 minutes of using
> the system. I was only able to capture this with netconsole.
I was seeing DMAR issues as well, but I figured it was self-inflicted because
it was due to the NVidia binary driver. Rebooted with 'intel_iommu=off' and it
behaved itself. Basically, I got a flood of messages like these:
Oct 12 17:20:09 turing-police kernel: [ 301.401157] DRHD: handling fault status reg 2
Oct 12 17:20:09 turing-police kernel: [ 301.401164] DMAR:[DMA Read] Request device [01:00.0] fault addr d5b76000
Oct 12 17:20:09 turing-police kernel: [ 301.401166] DMAR:[fault reason 01] Present bit in root entry is clear
Oct 12 17:20:13 turing-police kernel: [ 305.615039] DRHD: handling fault status reg 2
Oct 12 17:20:13 turing-police kernel: [ 305.615047] DMAR:[DMA Read] Request device [01:00.0] fault addr 110de9000
Oct 12 17:20:13 turing-police kernel: [ 305.615048] DMAR:[fault reason 01] Present bit in root entry is clear
Oct 12 17:20:14 turing-police kernel: [ 306.056109] DRHD: handling fault status reg 2
Oct 12 17:20:14 turing-police kernel: [ 306.056116] DMAR:[DMA Read] Request device [01:00.0] fault addr ca861000
Oct 12 17:20:14 turing-police kernel: [ 306.056117] DMAR:[fault reason 01] Present bit in root entry is clear
Oct 12 17:20:14 turing-police kernel: [ 306.059950] DRHD: handling fault status reg 2
Oct 12 17:20:14 turing-police kernel: [ 306.059959] DMAR:[DMA Read] Request device [01:00.0] fault addr ca861000
Oct 12 17:20:14 turing-police kernel: [ 306.059960] DMAR:[fault reason 01] Present bit in root entry is clear
Oct 12 17:20:14 turing-police kernel: [ 306.064171] DRHD: handling fault status reg 2
Oct 12 17:20:14 turing-police kernel: [ 306.064179] DMAR:[DMA Read] Request device [01:00.0] fault addr ca861000
Oct 12 17:20:14 turing-police kernel: [ 306.064180] DMAR:[fault reason 01] Present bit in root entry is clear
If that tells the iommu people something, fine. If it doesn't, that's OK too, I'll
take it up with NVidia.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-10-13 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 12:58 Udo A. Steinberg
2011-08-12 13:51 ` Dave Airlie
2011-08-12 14:08 ` Udo A. Steinberg
2011-10-12 17:19 ` Dave Hansen
2011-10-13 0:18 ` Valdis.Kletnieks [this message]
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=11892.1318465118@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=airlied@gmail.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=udo@hypervisor.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
all inboxes | Powered by JetHome®