From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12222] kernel BUG at drivers/pci/intel-iommu.c:1373!
Date: Mon, 15 Dec 2008 13:40:07 -0800 (PST) [thread overview]
Message-ID: <20081215214007.0C058108041@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12222-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12222
------- Comment #4 from grundler@parisc-linux.org 2008-12-15 13:40 -------
In 2.6.28-rc8 kernel, the BUG_ON is now at line 1276.
The BUG_ON is just indicating the IOMMU page table entry is already (or still)
in use.
My guess is either the IOMMU space allocator is buggy *OR* the unmap code isn't
clearing dma_pte_addr() (off by one?). Perhaps there needs to be a wmb() in
intel_unmap_sg() between dma_pte_clear_range() and the later __free_iova()
call.
intel_iommu=off means no IOMMU will be used. For normal workloads with modern
PCIe devices (which are all 64-bit, right?), there would be no perf impact. Not
until you wanted to get better isolation for virtual guest OSs or used a device
driver that only offers 32-bit DMA support, will it matter.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-12-15 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 17:35 [Bug 12222] New: kernel BUG at drivers/pci/intel-iommu.c:1373! bugme-daemon
2008-12-14 17:59 ` [Bug 12222] " bugme-daemon
2008-12-14 18:21 ` [Bug 12222] New: " FUJITA Tomonori
2008-12-14 18:21 ` [Bug 12222] " bugme-daemon
2008-12-14 21:21 ` bugme-daemon
2008-12-15 21:40 ` bugme-daemon [this message]
2008-12-18 10:32 ` bugme-daemon
2008-12-18 21:22 ` bugme-daemon
2009-01-07 15:08 ` bugme-daemon
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=20081215214007.0C058108041@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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