From: walt <wa1ter@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: [2.4.21-pre4-ac7] Um, is this a kernel oops? Or not.
Date: Fri, 28 Feb 2003 22:47:42 -0800 [thread overview]
Message-ID: <3E60578E.4050608@hotmail.com> (raw)
Hi Alan,
I see this only with ac7, not with ac6 or earlier:
# swapon -s
Filename Type Size Used Priority
/dev/ide/host0/bus0/target1/lun0/part3 partition 136544 0 -3
# swapoff -va
swapoff on /dev/ide/host0/bus0/target1/lun0/part3
swapoff on /dev/hdb3
Unable to handle kernel NULL pointer dereference at virtual address 00000015
printing eip:
c01454ce
pde*=00000000
oops:002
<lots of hex numbers snipped>
Segmentation fault </sbin/swapoff is the process that segfaults>
At this point after an oops I expect to see a system crash/reboot but it this
case the system continues on as if nothing had gone wrong, so I'm confused
about what is happening here. If the rest of the oops message would be
useful I will transcribe and post it for you.
The swapspace is actually deactivated, BTW, before swapoff crashes, and I
can turn it back on with swapon as if nothing had happened.
reply other threads:[~2003-03-01 5:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E60578E.4050608@hotmail.com \
--to=wa1ter@hotmail.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