public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21-pre5-ac2:  kernel oops with "swapoff -a"
Date: Sat, 08 Mar 2003 11:07:37 +0000	[thread overview]
Message-ID: <3E69CEF9.9050808@myrealbox.com> (raw)

Hi Alan,

When I do "swapoff -a" I still see the kernel oops that began with -pre4-ac7
and has propagated to every 'ac' kernel since then.

It's a "null-pointer dereference" oops which does not crash the system --
I still don't understand how that is possible.

Am I really the only person having this problem?  The oops is 100% reproducible
so it's hard to believe no one else is seeing it.  It happens on all three of
the machines I try it on, so it doesn't seem to be hardware-specific.

Plain 2.4.21-pre5 does NOT show this problem, so it seems to be a patch that
was specifically introduced in -pre4-ac7 and I don't know enough to narrow
it any further than that.  I'm not an accomplished kernel debugger so I
can't offer much more info than that, but I'd like to help if you can give
me some hints what kind of information you might need to find the problem.


             reply	other threads:[~2003-03-08 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 11:07 walt [this message]
2003-03-08 22:40 ` 2.4.21-pre5-ac2: kernel oops with "swapoff -a" Alan Cox
2003-03-08 21:42   ` John Bradford
     [not found] <fa.ft2aqc1.154k31h@ifi.uio.no>
     [not found] ` <fa.ohdbn4e.1rgcs92@ifi.uio.no>
2003-03-08 16:52   ` walt
     [not found] <fa.hhhab3c.11n83hg@ifi.uio.no>
     [not found] ` <fa.fk1qpc0.s4022c@ifi.uio.no>
2003-03-08 18:51   ` walt

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=3E69CEF9.9050808@myrealbox.com \
    --to=wa1ter@myrealbox.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