From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Qebp9-0006mb-JS for garchives@archives.gentoo.org; Wed, 06 Jul 2011 23:48:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 82DD021C042; Wed, 6 Jul 2011 23:46:40 +0000 (UTC) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 5422121C042 for ; Wed, 6 Jul 2011 23:46:40 +0000 (UTC) Received: by qyk9 with SMTP id 9so260152qyk.19 for ; Wed, 06 Jul 2011 16:46:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=qA686hd3G724ZsBl8BDAc8hb0U4bbJaldONH9+ctgHI=; b=pgtZpPbWRYnfovZY2a7XjuHtrcWl7Ma3iBstpNZXGoUL2/nw+hhQPQrPgnVssZS6JS ZVguApYhY8gTvUfau/zmsg6U5icvilP9JGMWIloZ6pA6qBDzGOGBk5pDXbwaFDmeMb3h VdiCAe1YwZBOI59QNXcw4ncoHY5WtYbftFVTA= 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 Received: by 10.224.104.14 with SMTP id m14mr128842qao.102.1309995999725; Wed, 06 Jul 2011 16:46:39 -0700 (PDT) Received: by 10.224.46.3 with HTTP; Wed, 6 Jul 2011 16:46:39 -0700 (PDT) In-Reply-To: <4E14DAF3.7050908@gmail.com> References: <4E11EEF3.70804@gmail.com> <1402354.G0EMuDhieW@nazgul> <4E122A95.7060707@gmail.com> <4E1364B6.3090405@gmail.com> <4E1376E9.6010103@gmail.com> <4E1392D6.2090904@gmail.com> <4E14B72C.6080004@gmail.com> <4E14DAF3.7050908@gmail.com> Date: Wed, 6 Jul 2011 16:46:39 -0700 Message-ID: Subject: Re: [gentoo-user] KDE and HARD lock ups. From: Mark Knecht To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 801cbf3ffdcaf618ffbb7e6e22344ecb On Wed, Jul 6, 2011 at 3:00 PM, Dale wrote: > Mark Knecht wrote: >> >> If I had to guess I'd say, since this followed a power failure where >> the machine was live and operating (if I've understood the thread >> through a quick scan) that some file on disk has gotten corrupted and >> it's that corruption that's causing the problem. You've checked >> memory. Let's assume that te processor and MB weren't damaged by this >> event. If that's the case - and unfortunately I don't know of any way >> to ensure it hasn't as it requires one to have a bit-accurate image of >> the machine before the power failure - there's probably no way to >> eliminate this as a possibility short of an emerge -e @world. >> >> It's not where I'd start. I'd probably look for core dump files or >> very carefully do experiment s trying to isolate exactly what part of >> KDE is firing off the problem. re-emerging the NVidia driver is a >> no-brainer as it takes no more than 1-2 minutes to test things. >> Rebuilding the machine is certainly more involved. >> >> If you have lots of disk space you might rsync the whole machine to a >> new partition to do the work, then using something other than KDE >> which doesn't crash rebuild the copy from a chroot which leaves the >> machine usable while the rebuild is going on. >> >> None of this sounds like fun... >> >> - Mark >> >> >> > > I did something similar at least. =C2=A0I have two drives in here that ar= e for my > OS. =C2=A0I have a third that is for data, videos, audio stuff and docume= nts. > =C2=A0The data drive is a 750Gb. =C2=A0The old main OS drive is a 160Gb a= nd the spare > OS drive is a 250Gb. =C2=A0I downloaded a stage3 tarball. =C2=A0I then se= t up the > spare OS drive and mounted the partitions basically following the docs. = =C2=A0I > then copied over /etc, disfiles and the world file. =C2=A0After that, I d= id a > emerge -e world which installed everything that I had before. =C2=A0It al= so has a > slightly newer kernel as well. > > So, after running my memtest this morning while I took a nap, I booted in= to > the new install. =C2=A0I checked with the mount command to make sure I wa= s in the > new install too. =C2=A0I deleted EVERYTHING KDE in my home directory. =C2= =A0After > that, I logged into KDE. =C2=A0A box popped up that composite was disable= d. =C2=A0It > said I could hit shift alt F12 to enable. =C2=A0After I started Firefox, = it > locked up complete with my keyboard lights blinking again. > > What does Fluxbox use as opposed to KDE? =C2=A0Both use the Nvidia driver= s right? > =C2=A0I use KDM for my login screen and I think nvidia is loaded when it = starts > and it uses nvidia thereafter. =C2=A0So, if it was the driver, would it n= ot mess > up in Fluxbox too? =C2=A0 What makes Fluxbox work and KDE fail? > > Could my video card be having issues? =C2=A0I may take the sides off and = unplug > replug everything and give it all a once over. =C2=A0Maybe just a bad con= nection > or something. =C2=A0Maybe? > > If one of you guys were me, would you order a video card and try that? = =C2=A0Keep > in mind, I have surge protection inside the UPS on the wall side. =C2=A0I= also > have a surge protector strip that my modem, router, puter and monitor plu= gs > into. =C2=A0It's kind of hard to imagine that a surge could make it throu= gh all > that and not at least smell up =C2=A0the place a bit. =C2=A0I'm not sayin= g it couldn't > but just hard to imagine. =C2=A0I got surge protection coming out the ear= s here. > > Thoughts? > > Dale And this is your newer machine machine, correct? The one you built a few months ago IIRC? Sounds like you've takn the right steps to eliminate lots of problem sites and it just isn't working. What a drag! A machine lockup can come from almost anything not working. Bad software is the easy one, but it could be hardware. As for fluxbox vs KDE that's apples and oranges. They probably use totally different parts of X and do it in very different ways. However if fluxbox works perfectly for weeks then it wouldn't seem likely to be a hardware issue unless it's a really unlikely corner case, but you wouldn't think KDE would hit is every time and fluxbox never hits it. Have you tried the most up to date ~amd64 drivers?