From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9A35F198005 for ; Wed, 20 Mar 2013 17:43:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5FD36E0759; Wed, 20 Mar 2013 17:43:40 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by pigeon.gentoo.org (Postfix) with ESMTP id E2207E0720 for ; Wed, 20 Mar 2013 17:43:38 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.31]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MEpV6-1UTsa80KWg-00G4a5 for ; Wed, 20 Mar 2013 18:43:38 +0100 Received: (qmail invoked by alias); 20 Mar 2013 17:43:37 -0000 Received: from sign-4d094813.pool.mediaWays.net (EHLO Taschenheizung) [77.9.72.19] by mail.gmx.net (mp031) with SMTP; 20 Mar 2013 18:43:37 +0100 X-Authenticated: #41475677 X-Provags-ID: V01U2FsdGVkX18VxftKfDAVtR4pnu9XVj/VyVkrTDWeODleh0b7uz w8YrzT89R78KeJ Date: Wed, 20 Mar 2013 18:43:17 +0100 From: Daniel Wagener To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] System freezes during compiles Message-Id: <20130320184317.da16a0b7fe9d3e8f7853e72d@gmx.net> In-Reply-To: <1363754548.1800.1.camel@hydra> References: <1363754548.1800.1.camel@hydra> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.12; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Archives-Salt: fc35c4ea-55ad-4058-b440-5e8d0b2d8cbb X-Archives-Hash: ce3d767de8de23ed85a67c280970c0ca On Wed, 20 Mar 2013 05:42:28 +0100 Carlos Hendson wrote: > Hello, > > 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. > > 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). > > 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. > > There are kernel stack traces in /var/log/messages which I'm unable to > decipher and diagnose as to what caused the lock-up. > > 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. > > 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. > > That's by no means conclusive, however, I've also run a complete pass of > memcheck for over an hour without any issues reported. > > I'd like to completely rule out hardware failure, what diagnostic tools > tools are recommend to try identify potential hardware issue of this > type? > > The various kernel stack traces are attached in case someone wants to > take a look. I can provide more information should it be needed. > > Any help or advice would be appreciated. > > Regards, > Carlos "Frozen" means there is no Hard Drive Activity going on right? And there is no other indication, that you are just running out of memory? --