From: Patrick Dreker <patrick@dreker.de>
To: kenton.groombridge@us.army.mil, linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Thu, 21 Aug 2003 13:05:05 +0200 [thread overview]
Message-ID: <200308211305.05848.patrick@dreker.de> (raw)
In-Reply-To: <2224f3e221f996.221f9962224f3e@us.army.mil>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Thursday 21 August 2003 03:39 schrieb kenton.groombridge@us.army.mil 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-----
next prev parent reply other threads:[~2003-08-21 11:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 1:39 nforce2 lockups kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` Clock
2003-08-15 16:38 ` Alistair J Strachan
2003-08-15 19:06 ` Clock
2003-08-15 17:47 ` Alistair J Strachan
2003-08-15 21:15 ` Clock
2003-08-17 19:27 ` Jussi Laako
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
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=200308211305.05848.patrick@dreker.de \
--to=patrick@dreker.de \
--cc=kenton.groombridge@us.army.mil \
--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