From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Tue, 2 Dec 2003 16:12:56 -0500 [thread overview]
Message-ID: <20031202211256.GB28090@forming> (raw)
In-Reply-To: <OFF4FC9A17.547F8D5E-ON80256DF0.00356F93-80256DF0.00383157@uk.neceur.com>
To me the strangest thing is that when I first got this board a month or
so ago it would hang with APIC or LAPIC enabled. Now it works fine
without disabling APIC. All I did was update the BIOS and use it for a
while with APIC disabled. 2.6.0-test9-mm through 2.6.0-test11 all work
just fine. Still at the same time some people are reporting that it
works, some are reporting that it doesn't. I probably wouldn't think to
much of this except I was one of the ones that said APIC causes crashes
with IDE load, but now it doesn't?
On approximately Tue, Dec 02, 2003 at 10:13:46AM +0000, ross.alexander@uk.neceur.com wrote:
> Alistair,
>
> I upgraded the BIOS about a week ago to 1007. I personally found it to be
> less
> stable than 1006. I don't believe it is a problem with my hardware
> combination
> since it has been stable for long periods of time. I was running the SMP
> kernel
> simply because I (wrongly) presumed a) you needed it to get the IO-APIC
> working,
> and b) it didn't do any harm.
>
> It is clear that the UP kernel is considerable more stable than the SMP
> kernel. This
> is a very useful fact since it suggests that it is not a problem with the
> IDE device
> driver per se. The whole purpose of my testing is to try to determine
> which options
> increased the stability and hence highlight where the problem could be.
>
> One of the reasons I don't like ACPI is the huge amount of additional
> complexity
> it adds and the amount of stuff it could screw up. Now I have not heard
> that any
> of the VIA KTxxx based motherboards have any problems. If this is true
> then the
> problem does not lie with the LAPIC, since that is in the processor, not
> the MB.
> The fact that it seems to only occur with the NForce2 chipset means it
> could
> well be some interrupt coming into the LAPIC from Interrupt Bus. However
> I certainly don't claim to be an expert on this so I could well be talking
> complete
> crap.
>
> Conclusion: More testing required.
>
> Cheers,
>
> Ross
>
> ---------------------------------------------------------------------------------
> Ross Alexander "We demand clearly defined
> MIS - NEC Europe Limited boundaries of uncertainty and
> Work ph: +44 20 8752 3394 doubt."
>
>
>
>
> Alistair John Strachan <s0348365@sms.ed.ac.uk>
> 28/11/2003 04:46 p.m.
>
> To: ross.alexander@uk.neceur.com, "Brendan Howes"
> <brendan@netzentry.com>
> cc: linux-kernel@vger.kernel.org
> Subject: Re: NForce2 pseudoscience stability testing
> (2.6.0-test11)
>
>
> On Friday 28 November 2003 15:13, ross.alexander@uk.neceur.com wrote:
> [snip]
> >
> > The conclusion to this is the problem is in Local APIC with SMP. I'm
> not
> > saying this is actually true
> > only that is what the data suggests. If anybody wants me to try some
> > other stuff feel free to suggest
> > ideas.
> >
> > Cheers,
> >
> > Ross
> >
>
> It's evidently a configuration problem, albeit BIOS, mainboard revision,
> memory quality, etc. because I and many others like me are able to run
> Linux
> 2.4/2.6 with all the options you tested and still achieve absolute
> stability,
> on the nForce 2 platform.
>
> My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton) overclocked to
> 2.2Ghz, and 2x256MB TwinMOS PC3200 dimms. FSB is at 400Mhz, and the ram
> timings are 4,2,2,2. One might expect such a configuration to be unstable,
>
> but it is not.
>
> I'm currently running 2.6.0-test10-mm1 with full ACPI (+ routing), APIC
> and
> local APIC, no preempt, UP, and everything has been rock-solid, despite
> the
> machine being under constant 100% CPU load and fairly active IO load.
>
> Also, many others have found that just disabling local apic (and the MPS
> setting in the BIOS) as well as ACPI solves their problem, so I'm
> skeptical
> that SMP really causes *nForce 2 specific* instability.
>
> --
> Cheers,
> Alistair.
>
> personal: alistair()devzero!co!uk
> university: s0348365()sms!ed!ac!uk
> student: CS/AI Undergraduate
> contact: 7/10 Darroch Court,
> University of Edinburgh.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
| They that can give up essential liberty
Linux, the choice -o) | to obtain a little temporary safety deserve
of the GNU generation /\ | neither liberty or safety.
_\_v | -Benjamin Franklin
next prev parent reply other threads:[~2003-12-02 21:18 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a01c3b515$b6030de0$0f00a8c0@client.attbi.com>
2003-11-28 15:13 ` NForce2 pseudoscience stability testing (2.6.0-test11) ross.alexander
2003-11-28 16:46 ` Alistair John Strachan
2003-11-28 18:13 ` Julien Oster
2003-11-28 18:24 ` Prakash K. Cheemplavam
2003-11-29 2:55 ` Josh McKinney
2003-11-29 16:33 ` Julien Oster
2003-11-29 17:15 ` Josh McKinney
2003-12-02 10:13 ` ross.alexander
2003-12-02 21:12 ` Josh McKinney [this message]
2003-12-03 16:23 ` Julien Oster
2003-11-28 18:00 ` Julien Oster
2003-11-28 18:18 ` Prakash K. Cheemplavam
2003-11-29 10:25 bug in -test11 make xconfig Christopher Sawtell
2003-11-29 11:18 ` NForce2 pseudoscience stability testing (2.6.0-test11) Craig Bradney
2003-11-29 16:34 ` Julien Oster
2003-11-29 16:47 ` Craig Bradney
2003-11-29 16:54 ` Craig Bradney
2003-12-07 11:32 ` Jussi Laako
2003-12-07 15:49 ` Prakash K. Cheemplavam
2003-12-01 18:30 ` Pavel Machek
2003-12-01 20:20 ` Craig Bradney
[not found] <WSA7.6D.39@gated-at.bofh.it>
[not found] ` <WTYM.3ua.7@gated-at.bofh.it>
[not found] ` <WVoa.73O.17@gated-at.bofh.it>
2003-11-30 13:06 ` Lenar Lõhmus
[not found] <3FCD21E1.5080300@netzentry.com>
2003-12-03 0:28 ` Craig Bradney
2003-12-03 0:48 ` Prakash K. Cheemplavam
2003-12-03 8:15 ` Craig Bradney
2003-12-03 17:09 ` bill davidsen
[not found] ` <200312031709.MAA18860@gatekeeper.tmr.com>
2003-12-03 17:37 ` Prakash K. Cheemplavam
2003-12-03 0:47 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 0:58 Allen Martin
2003-12-03 1:09 ` Ian Kumlien
2003-12-03 1:23 b
2003-12-03 1:30 ` Ian Kumlien
2003-12-03 1:32 Allen Martin
[not found] <fa.nmlihqm.16j6n38@ifi.uio.no>
[not found] ` <fa.f27m7i8.1vk0j84@ifi.uio.no>
2003-12-04 1:08 ` walt
2003-12-04 1:41 b
2003-12-04 2:45 ` Jesse Allen
2003-12-04 7:42 ` Prakash K. Cheemplavam
2003-12-04 4:45 ` Josh McKinney
2003-12-04 11:47 ` ross.alexander
2003-12-04 2:57 b
2003-12-04 5:11 Allen Martin
2003-12-04 20:04 ` Jesse Allen
2003-12-04 20:41 ` Craig Bradney
2003-12-04 20:55 ` Craig Bradney
2003-12-04 22:03 ` Bob
2003-12-04 5:37 b
2003-12-04 7:00 ` Craig Bradney
2003-12-04 8:59 b
2003-12-04 9:09 b
2003-12-04 12:17 b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32 ` Josh McKinney
2003-12-04 17:08 ` Julien Oster
2003-12-04 17:55 ` Josh McKinney
2003-12-05 13:28 ` Pat Erley
2003-12-04 13:07 Dan Creswell
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=20031202211256.GB28090@forming \
--to=forming@charter.net \
--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 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.