2003-08-21 01:47:46

by kenton.groombridge

[permalink] [raw]
Subject: Re: nforce2 lockups

I downloaded and applied the acpi patch patch_2.4.22-rc2_to_acpi-2.4-20030813.bz2 from:

http://sourceforge.net/project/showfiles.php?group_id=36832

and it did cure my spurious interrupt problem, but unfortunately, my lockups have returned.

It is strange that kernel 2.4.22-rc2 had never locked up at all (only with apic enabled). Ran it for a good week or so with absolutely no lockup (again, only with apic enabled). I tried my best to make it lockup and it never did, but the spurious interrupts made any device that loaded with IRQ 16 and above pretty much worthless. If I disabled apic, my lockups returned.

So there was something about 2.4.22-rc2 (with acpi enabled), that prevented lockups (but had tons os spurious interrupts). Something in patch_2.4.22-rc2_to_acpi-2.4-20030813.bz2 cured the spurious interrupts, but brought back the lockups.

Ken Groombridge

----- Original Message -----
> > I have ASUS A7N8X Deluxe mobo with nForce2 rev 162 without any
> problems> (if not counting unability to enabe SiI SATA DMA mode
> with attached
> > Seagate Barracuda drive).
>
> I have the exact same Board (except I'm not using SATA), and it's
> a nightmare.
> Best uptime so far: a little more than 16 hours. Usually it locks
> up a lot
> earlier. When I do network transfers I can cause it to lock within
> a few
> minutes. Under "the other OS" it runs without any problems.
>
> - --
> Patrick Dreker


2003-08-21 11:05:14

by Patrick Dreker

[permalink] [raw]
Subject: Re: nforce2 lockups

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

Am Thursday 21 August 2003 03:39 schrieb [email protected] zum
Thema Re: nforce2 lockups:
> and it did cure my spurious interrupt problem, but unfortunately, my
> lockups have returned.
I managed to stabilize my Board, but I don't think the trick was obvious:
Disable alle APIC related kernel Options (Local APIC and IO-APIC), disable
APIC Mode in the BIOS. Check on reboot if it still talks about the APIC in
the boot messages (How? IIRC mine did, which was why I did not think that
disabling the APIC helped... Actually somehow it still was activated. Could
ACPI be part of this?). If it does try noapic and/or nolapic boot options.

If you completely shut off the APIC it runs stable, but 1 of the 3 USB
Controllers is not assigned an interrupt. All this with ACPI enabled (ACPI
patch 20030730 and kernel 2.6.0-test3).

- --
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/RKdhcERm2vzC96cRAtjAAJ4y5oOm7uhtPqWtaS/S+mnWTr9C5gCdF3hK
2JQZ86psKDmWO74wxrINSRE=
=YbYq
-----END PGP SIGNATURE-----