From: "Stephen C. Tweedie" <sct@redhat.com>
To: Dave Mielke <dave@mielke.cc>
Cc: "Linux Kernel (mailing list)" <linux-kernel@vger.kernel.org>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: Swap space deallocation speed. (fwd)
Date: Fri, 4 May 2001 12:26:43 +0100 [thread overview]
Message-ID: <20010504122643.A6125@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0105030001060.22875-200000@dave.private.mielke.cc>
In-Reply-To: <Pine.LNX.4.30.0105030001060.22875-200000@dave.private.mielke.cc>; from dave@mielke.cc on Thu, May 03, 2001 at 12:03:39AM -0400
Hi,
On Thu, May 03, 2001 at 12:03:39AM -0400, Dave Mielke wrote:
> unresponsive. The relevant line in the log, as you can find in the attached
> "crash.log" file, appears to be:
>
> Unable to handle kernel paging request at virtual address 00020024
> Apr 16 11:23:06 dave kernel: esi: 00020000 edi: c14ff5d0 ebp: c3e6a6d0 esp: c142ff30
This looks like a random bit flip in a page table. That's almost
always a hardware problem. Stop overclocking if you are doing that;
check that the CPU fan is still working, etc.
Cheers,
Stephen
prev parent reply other threads:[~2001-05-04 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 4:03 Swap space deallocation speed. (fwd) Dave Mielke
2001-05-04 11:26 ` Stephen C. Tweedie [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=20010504122643.A6125@redhat.com \
--to=sct@redhat.com \
--cc=dave@mielke.cc \
--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