From: Patrick Dreker <patrick@dreker.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: kenton.groombridge@us.army.mil, linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Sat, 23 Aug 2003 20:52:40 +0200 [thread overview]
Message-ID: <200308232052.46684.patrick@dreker.de> (raw)
In-Reply-To: <200308231550.h7NFoZtr022365@harpo.it.uu.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Samstag, 23. August 2003 17:50 schrieb Mikael Pettersson <mikpe@csd.uu.se>
zum Thema Re: nforce2 lockups:
> On Sat, 23 Aug 2003 14:48:06 +0200, Patrick Dreker <patrick@dreker.de>
> > >Am Samstag, 23. August 2003 14:20 schrieb Mikael Pettersson
> >zum Thema Re: nforce2 lockups:
> >> On Sat, 23 Aug 2003 10:41:46 +0900, kenton.groombridge@us.army.mil
> >> "noapic" (note: no "l") might very well fix your board, but that's
> >see above. noapic had no effect on the freezes. On boot it still said
> > "found and enabling local APIC"
> Of course it did. "noapic" and BIOS APIC mode relate to the I/O-APIC,
> not the local APIC.
Well it's my first board which has an APIC, so I'm still learning how that all
belongs together...
> My guess is that your BIOS or graphics card can't handle the local
> APIC, presumably due to a crap SMM# handler or you using APM's
> CPU_IDLE or DISPLAY_BLANK options.
Someone else already hinted, that it might be the BIOS/SMM problem. APM is
completely disabled
> Kernel 2.6.0-test4 supports "nolapic", so that's an option too.
> I'll send that patch to Marcelo for 2.4.23-pre so it should be
> in 2.4 eventually.
I'll try that, and Asus have updated their BIOS for the Board, so I'll give
that a shot, too.
- --
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/R7f+cERm2vzC96cRAvwXAJ9M49KQUWCI37LJXAUamJiM0628lwCfXPjO
eapurx/Indgk60tVCJ96ztc=
=bebd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-08-23 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 15:50 nforce2 lockups Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
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=200308232052.46684.patrick@dreker.de \
--to=patrick@dreker.de \
--cc=kenton.groombridge@us.army.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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