From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Caleb Moore <donscarletti@ozemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swapping problem on kernel >= 2.4.14
Date: Sun, 16 Dec 2001 22:02:07 -0200 [thread overview]
Message-ID: <01121622020701.01821@manta> (raw)
In-Reply-To: <20011213204810.A2759@Duron> <01121312062800.02011@manta> <20011215142824.A1306@Duron>
In-Reply-To: <20011215142824.A1306@Duron>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="PT 154", Size: 1133 bytes --]
On Saturday 15 December 2001 01:28, Caleb Moore wrote:
> Ok I checked my system with one swap partition, no swap partitions and a
> swap file. One partition resulted in a crash but after a longer duration
> (two or three times as long. I cannot understand this). A swap file acted
> in a similar way to the single swap. After removing all swap the system
> was as stable as linux is rightly reputed to be.
>
> The kernel does produce an oops when i crash it but for some reason the
> screen blacks out a few minutes later and i am unnable to finish recording
> the sym-debug stuff and cannot get useful information from it. It is not
> logged by klogd and I don't get much further then the registers. The
> message It gives me is unnable to handle kernel paging request at virtual
> address 00015e00 although of course this adress changes.
Sorry, but this info is not enough. Guys most likely won't be able to
fix this if they don't know where your kernel crashed, CPU registers at the
crash time etc.
Screen blanking: some power-saving? Try to disable.
Maybe you can photograph it if it turns off by itself too fast? :-)
--
vda
prev parent reply other threads:[~2001-12-16 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 9:48 swapping problem on kernel >= 2.4.14 Caleb Moore
2001-12-13 14:06 ` vda
2001-12-15 3:28 ` Caleb Moore
2001-12-17 0:02 ` vda [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=01121622020701.01821@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=donscarletti@ozemail.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