From: Jonathan Morton <chromi@cyberspace.org>
To: cate@dplanet.ch, manfred@colorfullife.com
Cc: puckwork@madz.net, linux-kernel@vger.kernel.org
Subject: Re: URGENT : System hands on "Freeing unused kernel memory: "
Date: Tue, 27 Mar 2001 12:19:35 +0100 [thread overview]
Message-ID: <l03130331b6e6277ea3bd@[192.168.239.101]> (raw)
In-Reply-To: <3AC06651.1ECB7B5@math.ethz.ch>
In-Reply-To: <fa.it9nv9v.g08l8a@ifi.uio.no>
>> I have 2 ideas:
>> * glibc corrupted
>> * did you downgrade the cpu?
>
>These happen frequently to me (when compiling and installing a
>new glibc)
>But in this case you would have other messages (IIRC something
>like
>respawn too fast).
>Thus the problem is not this!
How about running memtest86 - could be that a RAM module blew up or worked
loose and caused the initial crash and this misbehaviour both at once.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
next prev parent reply other threads:[~2001-03-27 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.it9nv9v.g08l8a@ifi.uio.no>
2001-03-27 10:07 ` Giacomo Catenazzi
2001-03-27 11:19 ` Jonathan Morton [this message]
2001-03-27 9:23 Thomas Foerster
-- strict thread matches above, loose matches on Subject: below --
2001-03-27 9:12 Hen, Shmulik
2001-03-27 9:06 Studierende der Universitaet des Saarlandes
2001-03-27 8:40 Thomas Foerster
2001-03-27 6:48 Thomas Foerster
2001-03-27 7:50 ` J . A . Magallon
2001-03-27 14:40 ` Stuart MacDonald
2001-03-27 16:21 ` Alan Cox
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='l03130331b6e6277ea3bd@[192.168.239.101]' \
--to=chromi@cyberspace.org \
--cc=cate@dplanet.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=puckwork@madz.net \
/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®