public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mierswa <impulze@impulze.org>
To: linux-kernel@vger.kernel.org
Subject: ASUS M2NPV-VM APIC/ACPI Bug (patched)
Date: Wed, 18 Oct 2006 08:44:02 +0200	[thread overview]
Message-ID: <4535CD32.2010502@impulze.org> (raw)

Some people have deeper problems with the Asus M2NPV-VM mainboard
(rather the chipset of the mainboard).
A google for "Asus M2NPV-VM apic" shows that. I'm one of them,
desperately searching a way to fix that, using that board with an AMD
Athlon64 X2 3800+ Dual Core Processor.
It wouldn't boot because of APIC and ACPI errors. There were "kind of"
workarounds by passing acpi=off/noirq and noapic to the kernel which
resulted in sometimes bad internal clock. I for myself had the same
problem and due to the error with my internal system clock all
applications and drivers gone mad, including
sound,video,graphics,usb,etc.. I googled around and saw the following:
http://lkml.org/lkml/2006/8/13/25
Actually that was a patch created for the 2.6.18-rc4 kernel. I tried
several kernels all with the same results. Some of them are
2.6.18-mm3, 2.6.19-rc2, 2.6.17, 2.6.18, 2.6.18.1, some gentoo patched
sources and what not. All will hang after the io scheduler gets loaded,
passing acpi=off/noirq to the kernel will workaround that one. Then it
will boot on and finally reach the ochi_hcd driver which will not load
because of shared IRQ problems, passing nousb to the kernel will
workaround that. It will boot more and come to the dhcp client, where it
fails because of an Interrupt error.
Some people passing noapic acpi=off/noirq to the kernel got later sound
problems, they fixed that by passing "snd-hda-intel model=3stack
position_fix=1" which worked around that interrupt problem. So with the
patch provided on http://lkml.org/lkml/2006/8/13/25 it all works out.
The internal system clock works just fine, the drivers load
 all fine, no need to patch the sound,graphics or anything at all. No
need for kernel parameters either. Here's the patch again, created by
diff -ur on the current 2.6.18.1 kernel:

--- io_apic.c.orig	2006-10-18 08:02:50.000000000 +0200
+++ io_apic.c	2006-10-18 07:40:48.000000000 +0200
@@ -337,12 +337,12 @@
 					nvidia_hpet_detected = 0;
 					acpi_table_parse(ACPI_HPET,
 							nvidia_hpet_check);
-					if (nvidia_hpet_detected == 0) {
+/*					if (nvidia_hpet_detected == 0) {
 						acpi_skip_timer_override = 1;
 						printk(KERN_INFO "Nvidia board "
 						    "detected. Ignoring ACPI "
 						    "timer override.\n");
-					}
+					}*/
 #endif
 					/* RED-PEN skip them on mptables too? */
 					return;

Is there a small chance by getting that fixed in next kernel versions?
Greets impulze


             reply	other threads:[~2006-10-18  6:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  6:44 Daniel Mierswa [this message]
2006-10-18  7:30 ` ASUS M2NPV-VM APIC/ACPI Bug (patched) Len Brown
2006-10-19 12:41   ` Andi Kleen
     [not found] <fa.09mXx81eXfIStK3wap/U1OZn+kg@ifi.uio.no>
     [not found] ` <fa.1/QTOTFQC91cwKwinVDxrePnGHo@ifi.uio.no>
2006-10-19  0:42   ` Robert Hancock
2006-10-19 12:44     ` Andi Kleen
2006-10-19 15:52     ` Allen Martin
2006-10-19 16:11       ` Andi Kleen
2006-10-20  1:08         ` Allen Martin
2006-10-20 13:04           ` Andi Kleen
2006-11-01 14:21             ` impulze
2006-11-01 14:27               ` Arjan van de Ven

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=4535CD32.2010502@impulze.org \
    --to=impulze@impulze.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