From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-146016-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 703AC198005
for <garchives@archives.gentoo.org>; Wed, 20 Mar 2013 08:17:52 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 1C5B8E064B;
Wed, 20 Mar 2013 08:17:39 +0000 (UTC)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 9DA1FE05C7
for <gentoo-user@lists.gentoo.org>; Wed, 20 Mar 2013 08:17:37 +0000 (UTC)
Received: by mail-wi0-f172.google.com with SMTP id ez12so4903787wid.17
for <gentoo-user@lists.gentoo.org>; Wed, 20 Mar 2013 01:17:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=x-received:from:reply-to:to:subject:date:user-agent:references
:in-reply-to:mime-version:content-type:content-transfer-encoding
:message-id;
bh=lDGiJFcrxGT0jHxgiVB4bGijMJRLA3KU3XPRsyHgAl8=;
b=KmeaxCcgLcem9bJAWR5QGWpE3jU3E9LKid4TWPtGCa2PSYw2RJDfPHuV1IRVq7UwKM
Bp8klJEU4OrFKpd2YJTQwHzFmiF0ywVxRstt3qk9opLMx5GO0Ef4znjjZnFoxkmuOH2d
g0y21ByqvKRGw94DSZZ4QvVjkbBJ/70FydJWBwCp1Od6GZdD+mC3TigYRjB8NFDe+cgE
UuicMlce7ArZXxC+8C/G9hz1mXIdmm5oqrYUJSw6Kil3dzegD3lf2UKqKA6Gs0Urqr/k
m/xwNDu82fLMe9JELiP3duB4XeGHbrIzXjQNaEMF/LR5sFoteBGE3//KvtqHHjv7tsdh
pwaQ==
X-Received: by 10.194.76.37 with SMTP id h5mr8734276wjw.21.1363767456295;
Wed, 20 Mar 2013 01:17:36 -0700 (PDT)
Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230])
by mx.google.com with ESMTPS id ex1sm1481874wib.7.2013.03.20.01.17.34
(version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 20 Mar 2013 01:17:35 -0700 (PDT)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System freezes during compiles
Date: Wed, 20 Mar 2013 08:17:11 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.10-gentoo; KDE/4.9.5; x86_64; ; )
References: <1363754548.1800.1.camel@hydra>
In-Reply-To: <1363754548.1800.1.camel@hydra>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart10914865.mjCaBtheBV";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201303200817.25863.michaelkintzios@gmail.com>
X-Archives-Salt: 5bfe4dd8-e3e4-46d2-bb2d-0ec33d79eb94
X-Archives-Hash: 242e51f9fb8d49710468715e857d2963
--nextPart10914865.mjCaBtheBV
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
On Wednesday 20 Mar 2013 04:42:28 Carlos Hendson wrote:
> Hello,
>=20
> For last few weeks or so, I've been getting intermittent hard lock-ups
> during the emerge of various packages. It appears the more compile
> intensive the package, the more likely the lock-up. These lock-ups have
> occurred under kernels 3.4.9 and 3.7.10 with gcc 4.5.4 and 4.6.3.
>=20
> Once the machine is in a frozen state, the only thing that responds is
> the soft power reset button. Some times the machine lock-ups again
> after the button is pressed (this is because the compile resumes once
> the system comes out of it's frozen state).
>=20
> If the system subsequently lock-ups because I wasn't able to cancel the
> compile fast enough only a only option left is a hard power reset (10sec
> + hold power button). If I cancel the compile, the system is perfectly
> responsive and functions normally.
>=20
> There are kernel stack traces in /var/log/messages which I'm unable to
> decipher and diagnose as to what caused the lock-up.
>=20
> If I had to guess, I'd blame an incorrect setting in the .config, but
> since I'm stuck in the diagnostic of what part of the kernel might be
> experiencing the problem, I need a bit of help to pin point the issue.
>=20
> I believe it to be a kernel configuration issue because when I booted
> the machine using a system rescue Live CD, I was able to chroot into the
> system and emerge packages like gcc without the lock-up problem
> occurring.
>=20
> That's by no means conclusive, however, I've also run a complete pass of
> memcheck for over an hour without any issues reported.
>=20
> I'd like to completely rule out hardware failure, what diagnostic tools
> tools are recommend to try identify potential hardware issue of this
> type?
>=20
> The various kernel stack traces are attached in case someone wants to
> take a look. I can provide more information should it be needed.
>=20
> Any help or advice would be appreciated.
>=20
> Regards,
> Carlos
Stating the obvious, it seems that the kernel is struggling and indeed you =
may=20
have come across some nasty kernel bug. However, it could well be that it =
is=20
not related to the kernel you're running, or your kernel config. It could =
be=20
a problem with the power supply being faulty and causing these lock ups.
Unless someone else comes up with a better idea to troubleshoot it further,=
I=20
would consider replacing the power supply with another of a known good=20
condition.
=2D-=20
Regards,
Mick
--nextPart10914865.mjCaBtheBV
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEABECAAYFAlFJcJUACgkQVTDTR3kpaLYTBQCfX7KTczpL7RyUxH6pmhQts1xx
4psAoNTteB/CXQu0Rp+n6hDu8q9UfuCd
=uRt1
-----END PGP SIGNATURE-----
--nextPart10914865.mjCaBtheBV--