Bugzilla – Bug 171517
APIC problems on Asus M2N-SLI Deluxe (chipset nForce 570; socket AM2) needs noapic to boot
Last modified: 2007-01-10 12:43:46 UTC
ASUS ACPI doesn't support all known systems. There are a couple of ASUS system for which we have specific DSDT keys but are not yet included in asus_acpi.c. We should add them to the driver.
Actually my system hangs during installation. Only boot param: "acpi=none" helps. Even "acpi=debug" causes the machine to stop on acpi. Mainboard: Asus M2N-SLI Deluxe (chipset nForce 570; socket AM2). Additional info from text-mode installation: **** ENABLING IO-APIC IRQS TIMER: vector 0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set timer (IRQ0) through the 8259A ...failed ...trying to set timer as Virtual Wire IRQ ...failed ...trying to set timer as ExtINT IRQ faild :( Kernel panic - not syncing. IO-APIC timer doesn't work! Boot with apic=debug and send a report. Then try booting with 'noapic' option **** Please make Suse run with Asus M2N-Sli Deluxe motherboard. Regards Mark
I have mixed acpi with apic. In fact param "noapic" helps to boot my system. Sorry for mistake.
And you mixed up bug contents, this should be a separate bug. No problem though. Timo, I will change the title of this bug so that Mark does not need to open a separate one and create a new one with old contents and assign it to you. This is about OpenSuse 10.2, right? This version/kernel is evolving quickly. Can tell us the kernel verion you used, pls. You may also want to attach hwinfo, so that we have more details about the machine if needed...
Can you also post last lines of dmesg after trying to load asus_acpi module, pls (if it does not load properly) and attach acpidump. Not sure whether this is all needed so that Timo can add support for this machine, but I think so.
Created attachment 98468 [details] Hwinfo Output from hwinfo.
Created attachment 98469 [details] Last lines of dmesg
Created attachment 98470 [details] Acpidump
Kernel version is 2.6.18-rc5-git6-2-default. commands: "rmmod asus_acpi" and "modprobe asus_acpi" - both give no errors.
*** Bug 204876 has been marked as a duplicate of this bug. ***
Thomas, is there progress on this one?
(In reply to comment #8) > Kernel version is 2.6.18-rc5-git6-2-default. > commands: "rmmod asus_acpi" and "modprobe asus_acpi" - both give no errors. This does not help, Mark. The ASUS ACPI driver is just an enhancement for ASUS laptops and has nothing in common with the APIC (APIC, not ACPI) issue.
In general, the bug is invalid. This was about noapic and now it is about asus_acpi (which seem to work? If not, pls open a new bug and assign it to thoenig@novell.com). A lot machines need noapic boot param and I think we cannot do much about it, ak might want to comment here (I will CC him at later point). Hmm, this DSDT makes use of a NamePath in Source field of APIC PRT (PCI Routing Table). I can't find anything similar, maybe there is a real bug in kernel/ACPI code there? Can you attach dmesg output with apic=debug boot param, pls. Not sure whether this is enough. Maybe also an ACPI_DEBUG compiled kernel is needed to see things. You may want to try to boot the kernel-debug kernel. If it boots I will search for proper debug option to get the right values out of it.
I have just compiled kernel (2.6.18-rc5-git6-2) (cloneconfig) with: [make menuconfig] Power management (Added) +[*]Power management debug *ACPI support (Added) +[*]Debug statements But *still* "apic=debug" causes my screen to become blank and system does not respond - so I can't perform "dmesg". There is no any output on screen. Please inform me if I shall reboot and retrieve some logs after attempt to "apic=debug". As regards "ACPI_DEBUG" - I don't know how to find this. Is it in "menuconfig"? If it is needed - give me the way to compile with this option, because I only know how to change things in menuconfig.
That's strange. In comment #1 you showed us some output, it should at least come that far? Have you removed the vga= and splash=silent boot parameter in grub (ESC then modify the boot entry)? If it's still blank you might want to try earlyprintk=vga
Output was copied to paper from installation from CD (perhaps grub as a bootmanager). But during installation I installed LILO as a boot manager. I don't know Grub so I prefer Lilo.
I just want to summarize the problem for Andi again: This happens with a 10.2 installation without modifing any params (with a 2.6.18-rc5 or earlier kernel): comment #1: ENABLING IO-APIC IRQS TIMER: vector 0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set timer (IRQ0) through the 8259A ...failed ...trying to set timer as Virtual Wire IRQ ...failed ...trying to set timer as ExtINT IRQ faild :( Kernel panic - not syncing. IO-APIC timer doesn't work! Boot with apic=debug and send a report. Then try booting with 'noapic' option The apic problem is workarounded by passing noapic option, but sound card has interrupt problems then. AFAIK the board is quite new and apic should work, then probably the sound problem is also solved. Andi: Do you know about above message: 8254 timer not connected to IO-APIC Maybe Mark should try the latest 10.2 Beta1 which should be out now. IMO it's likely that this got fixed?
Yes known problem. When you remove the nvidia quirk in io_apic.c it will work, but then older Nvidia systems won't work anymore. The problem is that older nvidia systems all have wrong timer overrides so we ignore them, but the newer systems actually require a timer override that is not ignored. Normally we handle this by distingushing them based on HPET availability or not, but Asus "forgot" to enable the HPET in their BIOS either so it breaks there. I've been working on a solution for mainline to work around these various bios bugs. I don't know when it will be ready.
Can you take over then and close this one if there is a solution. There possibly is a duplicate? Tks.
I added a workaround for RC2 -- boot with acpi_use_timer_override Sorry no automatic detection this time. Perhaps we should add it to the release notes (reassigning) Something like On some Nvidia NForce 5 motherboards (in particular from Asus) or others that don't support a HPET timer proper booting might require the acpi_use_timer_override kernel option
Karl, please add this!
I propose this text: <sect3> <title>Booting Systems with HPET Timer Problems</title> <para> On some NVIDIA nForce 5 motherboards (in particular from ASUS) or others that do not support a HPET timer proper booting might require the <option>acpi_use_timer_override</option> kernel option at the boot prompt. </sect3>
I have tried the acpi_use_timer_override with the RC5 kernel: Unfortunately I still get a kernel panic. So I reassign to Andi again. I'll attach the boot messages grabbed from a serial console. Do you need any more information?
Created attachment 108005 [details] boot messages
Fixed with the latest BIOS update. Neither noapic nor acpi_use_timer_override is necessary any more on my Asus M2N-SLI Deluxe system. I think, this bug can be closed now.
After upgreading BIOS to the latest version, my Suse now also works without need for "noapic". Motherboard Asus M2N-SLI Deluxe.
Closing since BIOS update fixes it