From: Pavel Machek <pavel@ucw.cz>
To: Clock <clock@twibright.com>
Cc: kenton.groombridge@us.army.mil, linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Mon, 18 Aug 2003 15:28:40 +0200 [thread overview]
Message-ID: <20030818132840.GC861@elf.ucw.cz> (raw)
In-Reply-To: <20030815171521.A683@beton.cybernet.src>
Hi!
> > I don't think the problem is the the IDE. I have used a promise controller
> > and disabled the onboard IDE and still had lockups. If you find a solution,
> > please let me know. If I find one, I will do likewise.
>
> It looks like the problem is in APIC. When you disable it, it vanishes.
> And, when you enable NMI watchdog, which is handled by APIC,
Another BIOS that dislikes APIC on when entering SMM mode? Perhaps
that board needs blacklist entry that panics box if APIC is activated?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-08-18 13:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` nforce2 lockups 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 [this message]
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
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=20030818132840.GC861@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=clock@twibright.com \
--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;
as well as URLs for NNTP newsgroup(s).