Re: [PATCH] ACPI drop back to pic mode -- linux-2.6.0-test2-acpi-picmode.patch

[Patrick Dreker <patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Mittwoch, 30. Juli 2003 22:00 schrieb Andrew de Quincey 
<adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org> zum Thema [ACPI] [PATCH] ACPI drop back to pic mode 
- -- linux-2.6.0-test2-acpi-picmode.patch:
> Hi, this is my patch which detects problems in APIC mode and drops back to
> PIC mode. I've tested this on my system and my laptop by hacking APIC mode
> to fail. Seems to be fine.
>
> To apply:
> Grab linux-2.6.0-test2
> Apply the latest interim ACPI patch from http://sf.net/projects/acpi
> Apply linux-2.6.0-test2-acpi-picmode.patch
> See if it works!
>
> Any probs, let me know.
OK, here you go...

System: Asus A7N8X-Deluxe (NForce2), AMD Barton 2800+, Kernel 2.6.0-test2, 
patches as indicated above, CONFIG_ACPI=y, CONFIG_ACPI_BOOT=y, 
CONFIG_X86_UP_APIC=y, CONFIG_X86_UP_IOAPIC=y.

First I noticed something minor during compile:
drivers/acpi/pic_irq.c: In function acpi_pci_irq_init:
drivers/acpi/pic_irq.c:519: warning: implicit declaration of function 
'pic_parse_prt'
Pretty sure that wasn't there before the patches...

After accidentally booting the patched kernel with acpi=off I got the 
following oops very early in the boot process (NOTE: handcopied from the 
screen, no serial console attached):
EIP: acpi_pci_link_penalties+0x8/0x79
Call Trace:
acpi_pci_irq_init+0x8/0x5a
pci_acpi_init+0x22/0x80
do_initcalls+0x2b/0xa0
init_workqueues+0xf/0x30
init+0x2a/0x180
init+0x0/0x180
kernel_thread_helper=0x5/0x10

Before patching the kernel with the picmode.patch booting with acpi=off was no 
problem (aside from some devices not getting an IRQ assigned). Whether I 
enable or disable the APIC (at compile time, as well as with the "noapic" 
kernel option) does not matter. If ACPI is enabled all is fine. The APIC is 
enabled and all devices are assigned IRQs (which is not the case without 
ACPI).

I will now have to watch for more lockups, but I am not even sure they are in 
any way related to ACPI/APIC (though it "feels" like the machine is hung with 
all interrupts disabled, and the watchdog does not kick in, Magic SysRq 
doesn't work either)

Addendum: one reboot later: the machine still randomly locks up hard. The 
hardware has been tested (memtest, no overclocking, heatsinks, PSU etc. 
OK...). Any tipps, how I can find out where or when it locks up?

- -- 
Patrick Dreker

GPG KeyID  : 0xFCC2F7A7 (Patrick Dreker)
Fingerprint: 7A21 FC7F 707A C498 F370  1008 7044 66DA FCC2 F7A7
Key available from keyservers or http://www.dreker.de/pubkey.asc


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/KGKycERm2vzC96cRAh/1AJ9CHXJ6gHOSJvelDmKknLU2PQOVdQCcCl3J
bp+ntHQYMtArLiK8LjpOpQk=
=FQO4
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01