From: Andi Kleen <ak@muc.de>
To: David Ford <david+challenge-response@blue-labs.org>
Cc: akpm@osdl.org, B.Zolnierkiewicz@elka.pw.edu.pl,
linux-kernel@vger.kernel.org
Subject: Re: [culprit found] Re: [boot hang] 2.6.7-rc2, VIA VT8237
Date: Sat, 12 Jun 2004 15:58:17 +0200 [thread overview]
Message-ID: <m34qpgzxmu.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2652y-760-19@gated-at.bofh.it> (David Ford's message of "Sat, 12 Jun 2004 03:00:18 +0200")
David Ford <david+challenge-response@blue-labs.org> writes:
> Culprit found. If CONFIG_IOMMU_DEBUG is enabled, the machine will
> hang on boot at the partition check when using the VIA driver.
The real culprit is buggy VIA silicon. Use this patch.
-Andi
---------------------------------------------------------------
Enable VIA softmmu workaround for iommu=force/IOMMU_DEBUG too
diff -u linux-2.6.7rc3-bk3/arch/x86_64/kernel/io_apic.c-o linux-2.6.7rc3-bk3/arch/x86_64/kernel/io_apic.c
--- linux-2.6.7rc3-bk3/arch/x86_64/kernel/io_apic.c-o 2004-06-11 03:02:42.000000000 +0200
+++ linux-2.6.7rc3-bk3/arch/x86_64/kernel/io_apic.c 2004-06-12 15:46:35.000000000 +0200
@@ -252,7 +252,8 @@
switch (vendor) {
case PCI_VENDOR_ID_VIA:
#ifdef CONFIG_GART_IOMMU
- if (end_pfn >= (0xffffffff>>PAGE_SHIFT) &&
+ if ((end_pfn >= (0xffffffff>>PAGE_SHIFT) ||
+ force_iommu) &&
!iommu_aperture_allowed) {
printk(KERN_INFO
"Looks like a VIA chipset. Disabling IOMMU. Overwrite with \"iommu=allowed\"\n");
next parent reply other threads:[~2004-06-12 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23tuk-7Os-7@gated-at.bofh.it>
[not found] ` <23tDX-7UV-17@gated-at.bofh.it>
[not found] ` <23tNH-834-27@gated-at.bofh.it>
[not found] ` <23wix-1FP-19@gated-at.bofh.it>
[not found] ` <2652y-760-19@gated-at.bofh.it>
2004-06-12 13:58 ` Andi Kleen [this message]
2004-06-12 18:14 ` [culprit found] Re: [boot hang] 2.6.7-rc2, VIA VT8237 David Ford
2004-06-04 20:18 David Ford
2004-06-04 20:38 ` Bartlomiej Zolnierkiewicz
2004-06-04 20:42 ` David Ford
2004-06-04 23:12 ` David Ford
2004-06-12 0:53 ` [culprit found] " David Ford
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=m34qpgzxmu.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=david+challenge-response@blue-labs.org \
--cc=linux-kernel@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