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 1QdqRH-0003Kq-Ty for garchives@archives.gentoo.org; Mon, 04 Jul 2011 21:12:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8A5A321C061; Mon, 4 Jul 2011 21:10:55 +0000 (UTC) Received: from mail-yi0-f53.google.com (mail-yi0-f53.google.com [209.85.218.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 5D0D321C061 for ; Mon, 4 Jul 2011 21:10:55 +0000 (UTC) Received: by yic15 with SMTP id 15so3014634yic.40 for ; Mon, 04 Jul 2011 14:10:54 -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=movQYgVgMZAfN+Bwy3suSaQ1ZrJkaZ8u2InrP48cQZc=; b=bAvbj41VHq3H9FHVBCnWOY844Ai4X7Wfwi6dEcsy56x/iDlJyWBdi3aJwpxsZAlgLM TGUx11pE/4IavzFVZcfi+//dKEokEZzWRpdsT+y87gU/jI/DmLqE7ABoR1KGAmAyFnD1 BUF1JXNngLuXJIg4sbxVp4IwTxB/fJ4gj/bAs= Received: by 10.91.5.40 with SMTP id h40mr5464166agi.106.1309813400082; Mon, 04 Jul 2011 14:03:20 -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 w1sm6021552anh.3.2011.07.04.14.03.18 (version=SSLv3 cipher=OTHER); Mon, 04 Jul 2011 14:03:19 -0700 (PDT) Message-ID: <4E122A95.7060707@gmail.com> Date: Mon, 04 Jul 2011 16:03:17 -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> <1402354.G0EMuDhieW@nazgul> In-Reply-To: <1402354.G0EMuDhieW@nazgul> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 562c94601c961d002e001f16adc6f782 Alan McKinnon wrote: > On Monday 04 July 2011 19:12:50 Jes=C3=BAs J. Guerrero Botella did opin= e > thusly: > =20 >> 2011/7/4 Dale: >> =20 >>> Hi, >>> >>> What mine does: It sort of varies but usually when I login, it >>> may last 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 SysReq 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 longer moves >>> either. At this point, I hit the reset button which causes >>> steam 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 >>> Right now, I am in Fluxbox and it >>> works fine. I also booted to single user and compiled a bunch >>> of stuff and also tried a different kernel too. I think if it >>> was hardware, it would have had some kind of hick-up during the >>> compile. I did check temps and all is nice and cool, very cool >>> since my A/C is on full blast. I think the oven is outside on >>> full blast instead of in the kitchen. lol It's HOT here, >>> 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 get frequent crashes that seem to be related to nouveau. > When I used nvidia drivers, they seemed to have a mind of their own > when it came to memory usage and segfaults. > And the entire abomination that shall not be suffered to live called > "kdepim" *definitely* has a mind of it's own. > > > =20 >> =20 >>> 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 Well, I tried a different kernel. Same thing. I tried reseting the=20 BIOS and lurking around in there for a bit as well. Same thing. So,=20 right now I'm chewing on a emerge -e kde-meta. After I remembered the=20 power failure the other day, I suspect a corrupt file somewhere. I'm=20 just glad I have Fluxbox on here. I'm in it right now and it works OK. =20 I just wish the little bar at the bottom was larger. So far, nothing I=20 click changes that. Tough on my eyes too. Teeny tiny stuff down=20 there. o_o Thinking back, I should have booted the CD and run file system checks. =20 Crap, the one thing I didn't think of. < sighs > I still use Nvidia's driver here. it has worked well for me at least. =20 I don't use any fancy hardware or play any serious games so it works=20 well, so far at least. That may change next week. lol You know me. =20 Something new pretty regular. I don't guess I use kdepim stuff. It's installed so who knows. Any=20 relation to pam? Dale :-) :-)