From: jstrand1@rochester.rr.com (James D Strandboge)
To: LINUX-KERNEL <linux-kernel@vger.kernel.org>
Subject: Re: Oops in 2.4.10-- Unable to handle kernel paging request
Date: Tue, 23 Oct 2001 08:32:14 -0400 [thread overview]
Message-ID: <20011023083214.A28405@rochester.rr.com> (raw)
In-Reply-To: <20011017110045.A5444@rochester.rr.com>
In-Reply-To: <20011017110045.A5444@rochester.rr.com>
Well I thought I would send a reply to my own Oops, so when this
hits the archives, maybe someone can get something from it. As it
turns out, it was bad RAM that was causing the problem. With 2.2 I
never got Sig 11s on kernel compiles, but I tried a 2.4 compile on
this machine and sure enough, Sig 11. Other tests revealed it was
NOT a kernel bug, but instead RAM.
Sorry for the posts.
Jamie
--
GPG/PGP Info
Email: jstrand1@rochester.rr.com
ID: 26384A3A
Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
--
prev parent reply other threads:[~2001-10-23 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 15:00 Oops in 2.4.10-- Unable to handle kernel paging request James D Strandboge
2001-10-23 12:32 ` James D Strandboge [this message]
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=20011023083214.A28405@rochester.rr.com \
--to=jstrand1@rochester.rr.com \
--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