From: Brian Gerst <bgerst@didntduck.org>
To: "Shane Y. Gibson" <sgibson@digitalimpact.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform
Date: Thu, 15 Mar 2001 19:53:08 -0500 [thread overview]
Message-ID: <3AB163F4.EB7EF5E2@didntduck.org> (raw)
In-Reply-To: <3AB13120.AE7187B@digitalimpact.com>
"Shane Y. Gibson" wrote:
>
> All,
>
> I just compiled 2.4.2 and installed it on a otherwise stock
> Redhat 7.0 platform. The system is a SuperMicro PIIISME,
> running dual PIII 750s, with 256 cache. It appears that about
> every 10 to 18 hours, the system is panicing, and freezing
> up. The first time, I got an oops 0000, the second time an
> oops 0002. Both crashes have occured only when the systems is
> at 100% cpu utlization; processing several hundred MRTG
> indexmaker operations.
>
> I ran ksymoops on both outputs, and the results are pasted
> below. Note, I compiled the kernel without loadable module
> support. Please let me know if there is anything else I can
> do/provide to help. Unfortunately, the second didn't output
> enough for ksymoops to extract anything usefull.
>
> v/r
> Shane
>
> Code; 00000000 Before first symbol
> 0: 0f 0b ud2a
There should be a line just before the oops saying "kernel BUG at..."
--
Brian Gerst
next prev parent reply other threads:[~2001-03-16 0:45 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
2001-03-16 0:53 ` Brian Gerst [this message]
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=3AB163F4.EB7EF5E2@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgibson@digitalimpact.com \
/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