From: Roland Dreier <rdreier@cisco.com>
To: landman@scalableinformatics.com
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Anand Babu Periasamy <ab@gluster.com>
Subject: Re: kernel BUG at drivers/pci/intel-iommu.c:1278
Date: Fri, 16 Oct 2009 11:58:36 -0700 [thread overview]
Message-ID: <ada63afxj1f.fsf@cisco.com> (raw)
In-Reply-To: <4AD8A393.3040907@scalableinformatics.com> (Joe Landman's message of "Fri, 16 Oct 2009 12:47:15 -0400")
> Anything I should look for? I know 2.6.28 is not being developed any
> further. Should I start looking at 2.6.31 to help with this?
Definitely looking at 2.6.31 or even 2.6.32-rc kernels to see if this
still happens would be a good idea. I've not done much IB work with
VT-d enabled, but the fact that the BUG() is in drivers/pci seems to
indicate that the problem is fairly likely to be some internal
corruption in the intel_iommu code, caused by a bug there, rather than
anything IB related.
- R.
prev parent reply other threads:[~2009-10-16 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 16:47 kernel BUG at drivers/pci/intel-iommu.c:1278 Joe Landman
2009-10-16 18:58 ` Roland Dreier [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=ada63afxj1f.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ab@gluster.com \
--cc=landman@scalableinformatics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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