linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "b@netzentry.com" <b@netzentry.com>
To: dan@dcrdev.demon.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: RE: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Thu, 04 Dec 2003 04:17:54 -0800	[thread overview]
Message-ID: <3FCF25F2.6060008@netzentry.com> (raw)

Dan Creswell wrote:

Thanks for the input, I'll pass it to the list.

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,
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.

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.

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 .


 >Hi,
 >Been following this thread silently for a while and thought
 >I'd drop you
 >a line as I have some other data you may find useful.
 >
 >My machine is a dual Xeon with 2Gb, E1000 NIC, MPT LSI SCSI
 >disks and an
 >IDE CDROM.
 >
 >2.6-test9 is only stable on this machine with noapic passed in the
 >kernel parameters - otherwise, it lock's up in no time flat.
 >I can also
 >run this kernel in single-processor mode with the APIC enabled and
 >that's stable.
 >
 >2.4.23-rc2 runs fine on the same machine with the APIC enabled
 >in SMP mode.
 >
 >2.4.23-rc5 locks up on this machine if I use the same .config as
for
 >-rc2.  However, if I disable ACPI and pass "pci=noacpi" to the
kernel,
 >this too runs fine.
 >    - Seems like the ACPI changes in -rc3 are a problem for my
machine.
 >
 >All of these behaviors have been observed with MPS 1.4 (I've
changed
 >that BIOS setting to 1.1 today in preparation for more testing of
the
 >above to see if that makes a difference).
 >
 >I mention all of this because none of my lock-ups have happened
whilst
 >accessing the IDE subsystem.  I *have* had lockups with
simultaneous
 >network and disk access and I've also seen it with simply
 >mouse-waggling.  I suspect that the problem is *very* low-level
and
 >likely related to the interrupt load.  In my case, the problems
only
 >seem to occur with SMP configurations which makes me suspect there
may
 >be a locking/simultaneous update problem.
 >
 >Oh, forgot to say, my motherboard is a Tyan Thunder S2665
 >(based on the
 >intel E7505 chipset).
 >
 >Hope that helps,
 >
 >Dan.


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

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 12:17 b [this message]
2003-12-04 15:19 ` NForce2 pseudoscience stability testing (2.6.0-test11) 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-04 20:02         ` NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ? cheuche+lkml
2003-12-04 20:48           ` Bob
2003-12-04 23:05           ` Jesse Allen
2003-12-04 23:14             ` Prakash K. Cheemplavam
2003-12-04 23:21               ` Craig Bradney
2003-12-04 23:36                 ` Prakash K. Cheemplavam
2003-12-05  5:47                 ` Bob
2003-12-05  7:01                   ` Craig Bradney
2003-12-05 12:33                   ` Prakash K. Cheemplavam
2003-12-05  8:16           ` cheuche+lkml
2003-12-05 13:28 ` NForce2 pseudoscience stability testing (2.6.0-test11) Pat Erley
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04 13:07 Dan Creswell
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=3FCF25F2.6060008@netzentry.com \
    --to=b@netzentry.com \
    --cc=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).