From: "Rainer Mager" <rmager@vgkk.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Is this kernel related (signal 11)?
Date: Wed, 24 Jan 2001 09:56:00 +0900 [thread overview]
Message-ID: <NEBBJBCAFMMNIHGDLFKGIENPCNAA.rmager@vgkk.com> (raw)
In-Reply-To: <NEBBJBCAFMMNIHGDLFKGKEMACNAA.rmager@vgkk.com>
As per Russell King's suggestion, I ran memtest86 on my system for about 12
hours last night. I found no memory errors. Note that the tests did not
complete because I had to stop them this morning. I'll contiue them tonight.
They got through test 9 of 11.
As per David Ford's suggestion, I am looking into upgrading to glibc 2.2.1.
Can someone please give hints on doing this. I tried to upgrade to 2.2 a few
weeks ago and after the 'make install' and then reboot my system was very
broken and I had to reinstall the RedHat glibc RPM from CD to recover. I
found a howto but it seems pretty old. How do other people do this?
I've also done a strace on X. Now what do I do with this 4 MB log file?
Thanks,
--Rainer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 1:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 22:27 [patch] smbfs cache rewrite for 2.4.1-pre Urban Widmark
2001-01-22 5:17 ` Is this kernel related (signal 11)? Rainer Mager
2001-01-22 7:34 ` David Woodhouse
2001-01-22 8:03 ` Rainer Mager
2001-01-23 2:47 ` David Ford
2001-01-23 8:37 ` Rainer Mager
2001-01-24 0:56 ` Rainer Mager [this message]
2001-01-25 0:45 ` Rainer Mager
2001-01-22 7:53 ` Rogier Wolff
2001-01-22 21:47 ` Russell King
2001-01-23 0:15 ` Paul Jakma
2001-01-22 14:27 ` Barry K. Nathan
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=NEBBJBCAFMMNIHGDLFKGIENPCNAA.rmager@vgkk.com \
--to=rmager@vgkk.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