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 1QdoLi-0004AM-UA for garchives@archives.gentoo.org; Mon, 04 Jul 2011 18:58:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 263E621C03B; Mon, 4 Jul 2011 18:57:00 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id E688021C03B for ; Mon, 4 Jul 2011 18:56:59 +0000 (UTC) Received: by ywm21 with SMTP id 21so2993648ywm.40 for ; Mon, 04 Jul 2011 11:56:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=OpWanjtL0z/FrtGqw7D4uVjPtul27yIPjM8VgTrSLzU=; b=t/UQ7HEtzukyb3CXbR2JndGZO86S+6j2zHZDviyv31LnUfO8miJER/gsFGZtZ2Mycl ZJqDx+FUbGKY0UTSnVh0T0VKH/iBKD9fjhJSUBD+gQ45DgzIKOSHBnt43b7RT5pYcMpQ QhjDlshjKEMsVI/77uX6WcUyySsJ+rpp7y5hM= Received: by 10.150.236.3 with SMTP id j3mr681100ybh.294.1309805819247; Mon, 04 Jul 2011 11:56:59 -0700 (PDT) Received: from [192.168.2.5] (adsl-98-95-129-33.jan.bellsouth.net [98.95.129.33]) by mx.google.com with ESMTPS id e24sm4255522yhk.9.2011.07.04.11.56.57 (version=SSLv3 cipher=OTHER); Mon, 04 Jul 2011 11:56:58 -0700 (PDT) Message-ID: <4E120CF8.7030107@gmail.com> Date: Mon, 04 Jul 2011 13:56:56 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110606 Gentoo/2.0.14-r1 SeaMonkey/2.0.14 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] KDE and HARD lock ups. References: <4E11EEF3.70804@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: e7cb292489bcacbc6d02bfce19957fe3 Jes=C3=BAs J. Guerrero Botella wrote: > 2011/7/4 Dale: > =20 >> Hi, >> >> What mine does: It sort of varies but usually when I login, it may la= st a >> couple minutes, usually less, then the Caps Lock and Scroll Lock LED's >> blink. The Num Lock key is off if that means anything. I tried the S= ysReq >> keys but it doesn't do anything at all. According to the messages at = the >> next boot, it doesn't sync or umount either. The mouse pointer no lon= ger >> moves either. At this point, I hit the reset button which causes stea= m to >> come out my ears. I HATE using that button. >> >> I'm fairly sure this is not hardware. >> =20 > You can never be sure about that. > =20 That's why I said "fairly". One can never be sure but after some=20 testing, I don't think it is hardware. I'm getting more sure of that as=20 time goes on too. ;-) > =20 >> Right now, I am in Fluxbox and it >> works fine. I also booted to single user and compiled a bunch of stuf= f and >> also tried a different kernel too. I think if it was hardware, it wou= ld >> have had some kind of hick-up during the compile. I did check temps a= nd all >> is nice and cool, very cool since my A/C is on full blast. I think th= e oven >> is outside on full blast instead of in the kitchen. lol It's HOT her= e, >> steamy hot. >> =20 > You can try turning off the compositing system altogether. You can do > that by disabling the desktop effects in systemsettings. If lockups > stop then it's probably something to do with your graphics driver and > if that's the case you might have better luck with an alternative > driver. > > =20 I don't think I am logged in long enough to change the settings. I may=20 try my test user but I think a file got corrupted or something. I did=20 have a power failure the other day and the relay on my UPS was not quite=20 fast enough. I think the contacts may need some cleaning. My UPS does=20 some odd things at times. I need a new one but they are pricey. I had=20 forgot about the power failure issue. That has lead me down a different=20 path now. >> I checked messages and the only thing I saw was about a bad option for >> hp-systray. Surely that wouldn't cause a crash? I'm going to unmerge= and >> test it tho, just to be sure. >> =20 > I don't think so. > > =20 I have seen this cause my desktop to freeze before. Usually when it has=20 trouble seeing the printer or starting itself then kills itself after a=20 few seconds. Once it dies, the desktop comes back. This is just a more=20 permanent freeze. I did wait a couple times but it never come back. Working on a re-emerge to see if it corrects this issue. Thanks. Dale :-) :-)