From: Denis Perchine <dyp@perchine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
Date: Wed, 29 Oct 2003 22:07:24 +0700 [thread overview]
Message-ID: <200310292107.24077.dyp@perchine.com> (raw)
On Wednesday 29 October 2003 20:52, Brad House wrote:
> Interesting, I'll search through lkml for that. The only thing
> I can say is that we're not seeing that on nForce3 w/x86_64, which
> is the only nforce mb I have access to, and it uses basically the
> same driver.
The same problem with nforce2 mobos on the latest 2.4.
It hangs. The only solution is to disable local APIC in BIOS.
After that it seems that there are no hangups.
> -Brad
>
> ross.alexander@uk.neceur.com wrote:
> > Brad,
> >
> > My problem is one of the infamous nforce2 hardlockups. You don't get any
> > kernel panic or anything that useful. The system just locks up
> > completely and has to be manually reset.
> >
> > The problem is known to associate with IDE activity and is thought (as
> > far as I know) to originate somewhere in the IDE driver.
--
Denis
next reply other threads:[~2003-10-29 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 15:07 Denis Perchine [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 5:08 nforce2 stability on 2.6.0-test5 and 2.6.0-test9 Justin Ossevoort
2003-11-05 0:38 Allen Martin
2003-11-04 9:00 ross.alexander
2003-11-03 18:36 Allen Martin
2003-10-29 19:17 Allen Martin
2003-10-30 9:11 ` ross.alexander
2003-10-30 12:46 ` really bensoo_at_soo_dot_com
2003-10-29 11:57 ross.alexander
2003-10-29 14:13 ` Brad House
2003-10-29 14:35 ` ross.alexander
2003-10-29 14:52 ` Brad House
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=200310292107.24077.dyp@perchine.com \
--to=dyp@perchine.com \
--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