From: Larry McVoy <lm@bitmover.com>
To: Samuel Dupas <samuel@dupas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to handle kernel paging request at virtual address 3b617b05 ( was Re: swap_free: swap-space map bad (entry 00000100) )
Date: Fri, 27 Jul 2001 08:29:18 -0700 [thread overview]
Message-ID: <20010727082918.A27780@work.bitmover.com> (raw)
In-Reply-To: <20010727111313.1da63aca.samuel@dupas.com> <20010727162423.2fb6fc80.samuel@dupas.com>
In-Reply-To: <20010727162423.2fb6fc80.samuel@dupas.com>; from samuel@dupas.com on Fri, Jul 27, 2001 at 04:24:23PM +0100
On Fri, Jul 27, 2001 at 04:24:23PM +0100, Samuel Dupas wrote:
> I change the kernel (now 2.2.19) and I still have the same problem. It
> begin by a "Unable to handle kernel paging request at virtual address"
Did you change memory or CPU lately? I had a pile of these yesterday
after we dropped in a 1.3Ghz K7. Turned out our memory was border line,
I swapped in some new mem and no more problems.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-07-27 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 10:13 swap_free: swap-space map bad (entry 00000100) Samuel Dupas
2001-07-27 15:24 ` Unable to handle kernel paging request at virtual address 3b617b05 ( was Re: swap_free: swap-space map bad (entry 00000100) ) Samuel Dupas
2001-07-27 15:29 ` Larry McVoy [this message]
2001-07-27 15:35 ` Samuel Dupas
2001-07-27 15:40 ` Unable to handle kernel paging request at virtual address 3b617b05 (was " Sunny Zhou
2001-07-27 15:55 ` Samuel Dupas
[not found] ` <018e01c116c1$aba28aa0$bef7020a@mammon>
2001-07-27 17:37 ` swap_free: swap-space map bad (entry 00000100) Samuel Dupas
2001-07-27 19:17 ` Rik van Riel
2001-07-27 20:26 ` Jeremy Linton
2001-07-27 19:13 ` Linus Torvalds
2001-07-28 1:53 ` Thanks Josh Wyatt
2001-07-28 2:55 ` Thanks John Polyakov
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=20010727082918.A27780@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel@dupas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.