From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DqvJ2-0007Nm-QA for garchives@archives.gentoo.org; Fri, 08 Jul 2005 16:02:25 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j68FxG8n019386; Fri, 8 Jul 2005 15:59:16 GMT Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j68FxGA3012486 for ; Fri, 8 Jul 2005 15:59:16 GMT Received: from gaia.prhnet (unknown [84.12.164.30]) by smtp.nildram.co.uk (Postfix) with ESMTP id 2FBBE254B81 for ; Fri, 8 Jul 2005 16:59:23 +0100 (BST) Received: from [192.168.129.25] (wstn.home [192.168.129.25]) by gaia.prhnet (Postfix) with ESMTP id F0ACC122B8 for ; Fri, 8 Jul 2005 16:59:26 +0100 (BST) Message-ID: <42CEA2DC.70205@gotadsl.co.uk> Date: Fri, 08 Jul 2005 16:59:24 +0100 From: Peter Humphrey User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050704) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Incipient hardware failure? References: <42CA5774.9060907@gotadsl.co.uk> <1120624277.23834.3.camel@athlon> <42CB993E.1090402@gotadsl.co.uk> In-Reply-To: <42CB993E.1090402@gotadsl.co.uk> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Archives-Salt: aa22f71f-8e3b-4133-a30a-fef6a6ba167b X-Archives-Hash: d50e290fe14c60fdf3d9c1ee56c2490b 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