From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Incipient hardware failure?
Date: Fri, 08 Jul 2005 16:59:24 +0100 [thread overview]
Message-ID: <42CEA2DC.70205@gotadsl.co.uk> (raw)
In-Reply-To: <42CB993E.1090402@gotadsl.co.uk>
I wrote:
>So on balance I think I won't pursue your suggestion, thanks all the same.
>
On the other hand, I've been playing with the script that Jani Averbach recommended in article 20050705155357.GA12533@jaa.iki.fi in this thread. First I tried it from the console, with no X, but it showed up no errors. Then I tried it from an x-term and got the same null result. Then I remembered I'd compiled swap out of the kernel and recompiled with it included. Still no errors.
I have my Linux partitions on the second disk, with a swap partition on the first to reduce latency. Running in /tmp in /dev/hdb9 (after expanding it to make space for all those copies of the kernel - 17 in my case with 2GB RAM) I watched the disk activity in gkrellm. I saw lots of activity on hdb but none at all on hda. so nothing is being swapped out. I'll try it soon with parallel instances to see if that will flush out some swap (while running in serial the disk activity is in flushing and re-reading file buffers), but in the meantime I get either segmentation or bus errors every time I compile anything. Well, actually, I kept trying to emerge --resume part-way through emerge -e world, which was failing on xorg-x11.
That makes me think again of your bad file left lying around, and wondering if my compiler is similarly affected, so I'm doing another emerge -e world at the moment to see if I can build a good tool chain. I fear it won't work, but it's got to 7 of 274 binutils so far.
Watch this space...
--
Rgds
Peter Humphrey
Linux Counter 5290, Aug 93.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-08 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42CA5774.9060907@gotadsl.co.uk>
[not found] ` <42CA5930.7010508@tiscali.fr>
[not found] ` <42CA667E.7060701@gotadsl.co.uk>
[not found] ` <pan.2005.07.05.13.21.52.33248@cox.net>
[not found] ` <42CA9646.5060200@gotadsl.co.uk>
[not found] ` <pan.2005.07.05.16.33.27.506035@cox.net>
[not found] ` <42CABC63.7060007@gotadsl.co.uk>
[not found] ` <20050705182345.GA3876@crud.crud.mn.org>
[not found] ` <42CAE7B0.3050002@gotadsl.co.uk>
[not found] ` <20050705214000.GA25907@crud.crud.mn.org>
2005-07-05 22:40 ` [gentoo-amd64] Re: Re: Incipient hardware failure? Peter Humphrey
[not found] ` <42CA9F34.1030305@gotadsl.co.uk>
[not found] ` <20050705155357.GA12533@jaa.iki.fi>
2005-07-06 2:19 ` [gentoo-amd64] PCI Wireless Cards with 64bit support and drivers Terry Ellis
2005-07-06 3:40 ` Benny Pedersen
2005-07-06 4:11 ` Terry Ellis
2005-07-06 7:22 ` Peter Humphrey
2005-07-06 10:39 ` [gentoo-amd64] " Duncan
2005-07-06 14:47 ` [gentoo-amd64] " Terry Ellis
2005-07-06 17:05 ` [gentoo-amd64] " Duncan
2005-07-13 9:42 ` [gentoo-amd64] Re: Incipient hardware failure? Peter Humphrey
2005-07-06 4:31 ` [gentoo-amd64] " Kyle Liddell
2005-07-06 8:41 ` Peter Humphrey
2005-07-08 15:59 ` Peter Humphrey [this message]
2005-07-09 1:10 ` [gentoo-amd64] " Duncan
2005-07-09 8:27 ` Peter Humphrey
2005-07-09 8:49 ` Peter Humphrey
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=42CEA2DC.70205@gotadsl.co.uk \
--to=prh@gotadsl.co.uk \
--cc=gentoo-amd64@lists.gentoo.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