public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Shane Y. Gibson" <sgibson@digitalimpact.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform
Date: Mon, 19 Mar 2001 11:49:56 -0500	[thread overview]
Message-ID: <3AB638B3.545D7B26@digitalimpact.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103151954260.4383-100000@freak.distro.conectiva> <3AB13E47.7C777DF3@digitalimpact.com>

"Shane Y. Gibson" wrote:
> 
> Marcelo Tosatti wrote:
> >
> > Did'nt you get a message similar to
> >
> > "kernel BUG at page_alloc.c line xxx!"

Okay, I set the nmi_watchdog=0 options for LILO.  Now on crashes,
I get ZERO panic output in the log files.  I found some old
PII 450s, and don't seem to get any panics when I run the PII450s.

I'll remove the nmi_watchdog option, and put the 750s back in,
and see if I can get anymore panic output.

v/r
Shane

--
Shane Y. Gibson                     sgibson@digitalimpact.com
Network Architect                        (408) 447-8253  work
IT Data Center Operations                (650) 302-0193  cell
Digital Impact, Inc.                     (408) 447-8298   fax

     "The whole problem with the world is that fools and
      fanatics are always so certain of themselves,  and
      wiser people so full of doubts."  Bertrand Russell

  parent reply	other threads:[~2001-03-19 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 21:16 Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform Shane Y. Gibson
2001-03-15 22:56 ` Marcelo Tosatti
     [not found]   ` <3AB13E47.7C777DF3@digitalimpact.com>
2001-03-16  2:13     ` Marcelo Tosatti
2001-03-16 16:20       ` Shane Y. Gibson
2001-03-16 22:00         ` Marcelo Tosatti
2001-03-19 16:49     ` Shane Y. Gibson [this message]
2001-03-16  0:53 ` Brian Gerst
2001-03-16  3:17 ` Andrew Morton

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=3AB638B3.545D7B26@digitalimpact.com \
    --to=sgibson@digitalimpact.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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