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.62)
(envelope-from <gentoo-user+bounces-64256-garchives=archives.gentoo.org@gentoo.org>)
id 1Hq4DN-0007N0-Al
for garchives@archives.gentoo.org; Mon, 21 May 2007 09:30:06 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4L9Sl5X010088;
Mon, 21 May 2007 09:28:47 GMT
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171])
by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4L9OaNd005392
for <gentoo-user@lists.gentoo.org>; Mon, 21 May 2007 09:24:37 GMT
Received: by ug-out-1314.google.com with SMTP id z38so935600ugc
for <gentoo-user@lists.gentoo.org>; Mon, 21 May 2007 02:24:36 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
b=McKB4mXDjAXINsA+j91pZJMRgthanw2otDTgpRBx0G7B3Vw9TJkUz1sBF+VnItiRj7ndIc6mAxvT+zVvbAWUwpcxUZsO+Cpz+X5JU1mrD7tXqW6TReUIwaQumZIwkuERs38VEJsklYzXnq+7ifaTdtqmMPpGNNOTPKfquJBbHf8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
b=kwcWkKSP7X37Rd8gkLAllbPrLt+5SFGLbowgsfNVIXaMnBFCNmeogLPFPgzg0IJNsBoidyG6opIyh0HNtQtGAgT+KK3CRxc4eTibNIba9QzS4zN4zvGXaLoeM/2Y4Du62La8n1BU61eQpbNCaO5zFZnvludbkpMzF7LujohFVRc=
Received: by 10.82.150.20 with SMTP id x20mr8200050bud.1179739476516;
Mon, 21 May 2007 02:24:36 -0700 (PDT)
Received: from ?89.33.117.40? ( [89.33.117.40])
by mx.google.com with ESMTP id y37sm9588082iky.2007.05.21.02.24.33;
Mon, 21 May 2007 02:24:35 -0700 (PDT)
From: Nistor Andrei <coder.tux@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange system behaviour.
Date: Mon, 21 May 2007 12:24:37 +0300
User-Agent: KMail/1.9.6
References: <464CB912.7060107@gmail.com> <200705210030.52954.coder.tux@gmail.com> <1179703004.14221.1.camel@orpheus>
In-Reply-To: <1179703004.14221.1.camel@orpheus>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705211224.37799.coder.tux@gmail.com>
X-Archives-Salt: 378c2d4a-bf43-4d22-8ef9-6db56d18450e
X-Archives-Hash: 08f3ada61f267a46e9cf98f4ecce4f34
On Monday 21 May 2007, Iain Buchanan wrote:
> On Mon, 2007-05-21 at 00:30 +0300, Nistor Andrei wrote:
> > On Monday 21 May 2007, Marek Miller wrote:
> > > Yes, it is a RAM defect. Is there a way to define upper limit of RAM,
> > > so I can perform some back-up before
> > > I take my laptop to a warranty service?
> >
> > Try badram-sources. I've never used them, but they should do the trick. I
> > think you can find them in the custom-kernels overlay.
>
> ha! good luck trying to compile the kernel with faulty RAM. Can you
> remove one stick, or borrow some from a friend / other machine? That
> might help with your backups...
He could compile it remotely and then just copy it...
>
> cya,
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
> Dismissed. That's a Star Fleet expression for, "Get out."
> -- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud"
--
gentoo-user@gentoo.org mailing list