From: Brad House <brad@mainstreetsoftworks.com>
To: ross.alexander@uk.neceur.com
Cc: Brad House <brad@mcve.com>, linux-kernel@vger.kernel.org
Subject: Re: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
Date: Wed, 29 Oct 2003 09:52:31 -0500 [thread overview]
Message-ID: <3F9FD42F.3080706@mainstreetsoftworks.com> (raw)
In-Reply-To: <OFD0D30073.3921A657-ON80256DCE.004EDE5F-80256DCE.0050215F@uk.neceur.com>
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.
-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.
>
> Cheers,
>
> Ross
>
> ---------------------------------------------------------------------------------
> Ross Alexander "We demand clearly defined
> MIS - NEC Europe Limited boundaries of uncertainty and
> Work ph: +44 20 8752 3394 doubt."
>
>
>
>
> Brad House <brad@mcve.com>
> 10/29/2003 02:13 PM
>
> To: ross.alexander@uk.neceur.com
> cc: Brad House <brad_mssw@gentoo.org>,
> linux-kernel@vger.kernel.org
> Subject: Re: nforce2 stability on 2.6.0-test5 and
> 2.6.0-test9
>
>
> Hmm, interesting. The patches I submitted were strictly
> for IDE/ATA133 improvements, apparently your problems don't
> lie there. I'd assume this was a kernel panic you had, any
> output available that would tell you where it paniced ?
>
> -Brad
>
> ross.alexander@uk.neceur.com wrote:
>
>>Brad,
>>
>>I'm running an ASUS A7N8X Deluxe mobo (nforce2 chipset) and still
>>getting hardlockups. I applied your patch but my system still locked
>>up after about a day. However 2.6.0-test5 seems to be stable. I have
>>had my system up for over three weeks with APIC and ACPI turned on.
>>
>>Just to let you know,
>>
>>Ross
>>
>>
>
> ---------------------------------------------------------------------------------
>
>>Ross Alexander "We demand clearly defined
>>MIS - NEC Europe Limited boundaries of uncertainty and
>>Work ph: +44 20 8752 3394 doubt."
>>
>
>
>
>
>
>
--
-----------------------------
Brad House
Sr. Developer
Main Street Softworks, Inc.
brad@mainstreetsoftworks.com
(386) 462-9522 Ext. 112
-----------------------------
next prev parent reply other threads:[~2003-10-29 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 11:57 nforce2 stability on 2.6.0-test5 and 2.6.0-test9 ross.alexander
2003-10-29 14:13 ` Brad House
2003-10-29 14:35 ` ross.alexander
2003-10-29 14:52 ` Brad House [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 15:07 Denis Perchine
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-11-03 18:36 Allen Martin
2003-11-04 9:00 ross.alexander
2003-11-05 0:38 Allen Martin
2003-11-05 5:08 Justin Ossevoort
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=3F9FD42F.3080706@mainstreetsoftworks.com \
--to=brad@mainstreetsoftworks.com \
--cc=brad@mcve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.alexander@uk.neceur.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.