linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Thu, 04 Dec 2003 13:07:01 +0000	[thread overview]
Message-ID: <3FCF3175.8010302@dcrdev.demon.co.uk> (raw)

Sorry, should've sent this CC'd to list first time (time to make some 
more coffee :)


-------- Original Message --------
Subject: 	Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: 	Thu, 04 Dec 2003 12:38:21 +0000
From: 	Dan Creswell <dan@dcrdev.demon.co.uk>
To: 	b@netzentry.com
References: 	<3FCF25F2.6060008@netzentry.com>



b@netzentry.com wrote:

> Dan Creswell wrote:
>
> Thanks for the input, I'll pass it to the list.
>
You're welcome.

> Most of these Athlon victims are UP users, in fact, I
> believe they are exclusively UP. Does MPS 1.1/1.4 play a role
> in a UP system ever? I dont think the NForce2 chipset,

No, MPS shouldn't matter on a UP system.

> where we are seeing these hard hangs (no ping, no screen,
> no blinking cursor, no toggling the caps lock, nothing) is
> capable of SMP operation.
>
> Now whats interesting is you finger the IDE as a potential
> culprit and think its very low level. Interesting.
>
Well, I actually finger heavy duty disk access - my system locks under 
*SCSI* load (via a PCI-card - the motherboard doesn't have built in 
SCSI), I've not had it happen with my CDROM which is on the IDE 
subsystem.  This leads me to my conclusion in respect of interrupt 
load.  It seems to be an issue with simultaneous interrupts from another 
source but that's subjective......

> By the way, I've had trouble with SMP on a Tyan board with an
> i840 chipset with Linux before - I was never able to resolve
> the issue and had to return the board.
>
Interesting - I've had a number of Tyan boards and this is the first one 
I've had any issues with.  What bugs me more is that 2.4 seems fine 
(caveat 2.4.23-rc5 - wondering if the ACPI changes here are back-ported 
from 2.6) whilst 2.6 is horrid.  This is the only thing changing in the 
system which implies that something different goes on in 2.6 from 2.4 
and that it break's things.  Now it could be 2.6 is using some 
additional features - but the problem (once located) would be simply 
removed by providing an "off" switch to stop usage of those features.

> I've beaten on an Intel SR1300 and SR2300 dual Xeon (aka
> Micron's Netframe 1610/2610 aka Sun 60x / 65x) and never run
> into these hangs with kernels up to 2.4.22. The motherboard
> is an Intel SE7501WV2 .
>
Okay - well my Tyan also runs on kernels up to 2.4.22 no problem - 
useful information though.

Thanks,

Dan.




             reply	other threads:[~2003-12-04 13:07 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 13:07 Dan Creswell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04 12:17 NForce2 pseudoscience stability testing (2.6.0-test11) 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  9:09 b
2003-12-04  8:59 b
2003-12-04  5:37 b
2003-12-04  7:00 ` Craig Bradney
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  2:57 b
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
     [not found] <fa.nmlihqm.16j6n38@ifi.uio.no>
     [not found] ` <fa.f27m7i8.1vk0j84@ifi.uio.no>
2003-12-04  1:08   ` walt
2003-12-03  1:32 Allen Martin
2003-12-03  1:23 b
2003-12-03  1:30 ` Ian Kumlien
2003-12-03  0:58 Allen Martin
2003-12-03  1:09 ` Ian Kumlien
     [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
     [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
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] <001a01c3b515$b6030de0$0f00a8c0@client.attbi.com>
2003-11-28 15:13 ` 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
2003-12-03 16:23       ` Julien Oster
2003-11-28 18:00   ` Julien Oster
2003-11-28 18:18     ` Prakash K. Cheemplavam

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=3FCF3175.8010302@dcrdev.demon.co.uk \
    --to=dan@dcrdev.demon.co.uk \
    --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).