mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Lewis" <dlewis@vnxsolutions.com>
To: "Marc-Christian Petersen" <m.c.p@wolk-project.de>,
	<linux-kernel@vger.kernel.org>
Cc: "Erin Britz" <ebritz@vnxsolutions.com>
Subject: RE: [OOPS] kswapd 2.4.20
Date: Thu, 22 May 2003 12:01:40 -0400	[thread overview]
Message-ID: <EMEOIBCHEHCPNABJGHGOOEKPCNAA.dlewis@vnxsolutions.com> (raw)
In-Reply-To: <200305221027.00184.m.c.p@wolk-project.de>

Hiya Marc,

Thanks for the pointers to the new VM systems. I changed the kernel over to
2.4.21-rc2-ac2 (has rmap in it, right?) and I am rerunning my tests to see
if that solves the problem.

I agree with Andrea about bugs.. I certainly accept them as a necessary
evil. I tend to get frustrated when faced with something that I dont have
the skill to solve myself however. Especially so when I cant seem to get
pointed in the right direction by anyone. :)

Thanks again for your suggestion, and I will let you know if it works out!

David Lewis
Senior Security Engineer
VNX Solutions, Inc <http://www.vnxsolutions.com>
dlewis@vnxsolutions.com <mailto:dlewis@vnxsolutions.com>
410-459-7428 Cell



-----Original Message-----
From: Marc-Christian Petersen [mailto:m.c.p@wolk-project.de]
Sent: Thursday, May 22, 2003 4:41 AM
To: David Lewis; linux-kernel@vger.kernel.org
Cc: Erin Britz
Subject: Re: [OOPS] kswapd 2.4.20


On Wednesday 21 May 2003 16:45, David Lewis wrote:

Hi David,

> Fourth one sent to list.. Please advise if any other information is
needed.
> A reply would be appreciated even if it is to say that this is the wrong
> place.
> May 21 03:23:50 nicebox kernel: Unable to handle kernel paging request at
> virtual address 938a909e
> May 21 03:23:50 nicebox kernel: Process kswapd (pid: 5,
stackpage=df6d5000)
I really don't know how often I've seen this in recent 2.4 kernels
(.17,.18,.19,.20 (mainstream) and so on).

For me, I use the rmap VM. The problem is eliminated in that tree. Also the
-aa VM does not have that problem.

I am pretty sure Andrea sent a fix for this issue more than once a while ago
to the list cc'ed Marcelo (correct me if I am wrong), but to quote Andrea:
"We are here to fix bugs. If bug fixes are not accepted we can stop right
here
to fix bugs".

ciao, Marc



  reply	other threads:[~2003-05-22 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 14:45 David Lewis
2003-05-22  8:41 ` Marc-Christian Petersen
2003-05-22 16:01   ` David Lewis [this message]
2003-05-22 16:16     ` Carl-Daniel Hailfinger
2003-05-22 16:51     ` Marc-Christian Petersen

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=EMEOIBCHEHCPNABJGHGOOEKPCNAA.dlewis@vnxsolutions.com \
    --to=dlewis@vnxsolutions.com \
    --cc=ebritz@vnxsolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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

all inboxes | Powered by JetHome®