linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Thu, 4 Dec 2003 12:55:48 -0500	[thread overview]
Message-ID: <20031204175548.GB10471@forming> (raw)
In-Reply-To: <frodoid.frodo.87vfow33zm.fsf@usenet.frodoid.org>

On approximately Thu, Dec 04, 2003 at 06:08:29PM +0100, Julien Oster wrote:
> Josh McKinney <forming@charter.net> writes:
> 
> Hello Josh,
> 
> > Just to add more inconsistency into the mix, I am running with preempt
> > enabled, generic ide disabled, and can't make it crash.  Ran netperf for
> > an hour over a crossover cable on 100mbit, a couple make -j 30 kernel
> > compiles, dbench, and playing some mp3's all at the same time and
> > nothing happens despite load average reaching over 100.  Maybe I am just
> > lucky.
> 
> Or maybe not.
> 
> In the very beginning, 1 or 2 months ago right after I bought the
> board, it did crash but it actually didn't crash very often. In fact,
> most of the time (not every time, but most!) it crashed while the
> system being rather idle. To add even more perplexity to it: I could
> work on the system for hours and then leave the computer half an hour
> alone for talking a walk or jogging or whatever and, after coming
> back, run across a complete lockup. Normally, the clock applet on my
> desktop told me that the box crashed several minutes after I went out,
> since the clock of course froze with the mainboard as well.
> 
> A lot changed by now, hardware and software, and now I'm hardly able
> to run the system with ACPI/APIC enabled at all. If the boot procedure
> goes fine, it locks up shortly after. If fsck decides to check the
> disks, the mainboard is doomed to lock up away immediately.
> 
> That really is a nasty problem.
> 

This issue seems to be funny like that.  When I first recieved this
mobo I too had crashes like you say you are having now.  Doing
practically anything would make it crash, passing noapic and nolapic
on boot solved the problems.  Now, as I said, stable with all ACPI
APIC LAPIC enabled.  I haven't changed any hardware or anything
either, except for now I am using the nvidia ethernet with the
forcedeth driver, but I somehow don't think that has anything to do
with it, maybe it is worth looking into. 

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

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

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=20031204175548.GB10471@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 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).