From: John R Lenton <john@grulic.org.ar>
To: linux-kernel@vger.kernel.org
Subject: oopsen in 2.4.0-pre9
Date: Tue, 31 Oct 2000 09:47:55 -0300 [thread overview]
Message-ID: <20001031094755.A1029@grulic.org.ar> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Several oops come up when using a lot of memory (using
imagemagick on PIA00001.tif from photojournal.jpl.nasa.gov/tiff,
on a 64MB machine, for example)
The weird thing is the oops happen *after* I've finished with
imagemagick (or the gimp, or ...). In this particular situation
netscape suddenly died, together with wmtime, and then the whole
of X hung. I entered via the network, to find that xfs had died
(explaining X's hanging), and as soon as I restarted X the whole
box was gone. It still responded to pings, but even the active
ssh session was dead and I couldn't get a new one.
Please email me if you need anything else (other than the
attached ksymoops output, that is).
--
John Lenton (john@grulic.org.ar) -- Random fortune:
1 + 1 = 3, for large values of 1.
[-- Attachment #2: oopsen.txt.gz --]
[-- Type: application/octet-stream, Size: 2137 bytes --]
next reply other threads:[~2000-10-31 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 12:47 John R Lenton [this message]
2000-10-31 14:28 ` oopsen in 2.4.0-pre9 Richard Torkar
2000-10-31 14:33 ` Richard Torkar
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=20001031094755.A1029@grulic.org.ar \
--to=john@grulic.org.ar \
--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