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 1QekDz-0004Wl-Hn for garchives@archives.gentoo.org; Thu, 07 Jul 2011 08:46:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 96B0B21C027; Thu, 7 Jul 2011 08:44:49 +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 5E7CC21C027 for ; Thu, 7 Jul 2011 08:44:49 +0000 (UTC) Received: by yic15 with SMTP id 15so400469yic.40 for ; Thu, 07 Jul 2011 01:44:48 -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=Qn5a+A0dLPQNIe92t99upVgWZn09aR1lvnzXuX3CH5Y=; b=IJXhrKquu14+UpuSdYR40spmj4AdKy930Izxgk/tohgXbVXCZ8IYtgZHjuAsWW5YoH wUp9OrP0mWCDGogNhkCnWnnEW+gj/luAFuh7ZpiOgVF5p0LqRkzStWpzROXxqNhKm2Fr 4lsxBDPPArrTg6wi3E1FCEdxDx5CnI0meWFbM= Received: by 10.150.230.12 with SMTP id c12mr650877ybh.304.1310028288816; Thu, 07 Jul 2011 01:44:48 -0700 (PDT) Received: from [192.168.2.5] (adsl-98-95-147-233.jan.bellsouth.net [98.95.147.233]) by mx.google.com with ESMTPS id e14sm6173727anm.20.2011.07.07.01.44.47 (version=SSLv3 cipher=OTHER); Thu, 07 Jul 2011 01:44:47 -0700 (PDT) Message-ID: <4E1571FE.1060405@gmail.com> Date: Thu, 07 Jul 2011 03:44:46 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110705 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> <4E122A95.7060707@gmail.com> <4E1364B6.3090405@gmail.com> <4E1376E9.6010103@gmail.com> <4E1392D6.2090904@gmail.com> <4E14B72C.6080004@gmail.com> <4E15604E.90907@gmail.com> In-Reply-To: <4E15604E.90907@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 5edb88a13cd4a9115aee8aa194bec9e6 Dale wrote: > > You have a good point but there is a problem. Some of the kernels I > tried ran on this machine with uptimes of several weeks and not one > lock up. It could be some upgrade that affected this but who knows > what that was since I have updated a lot. As for nvidia, I tried both > versions that work with my card that are in portage. I got the same > with that no matter what I tried. > > As for .39 kernels, I mentioned in this mess somewhere that I had > upgraded but ran into problems with that series so I deleted them. I > may just be adding to the problems I am having if I do upgrade again. > But since I got to try something, I'll try the latest .39 and see what > it does. > > I remember having this type of problem once before. It turned out to > be a gcc problem if I recall correctly. I went back a version of gcc > and then did a emerge -e world. After that, things worked fine. > Thing is, I have had the same gcc since I built this rig according to > genlop. > > Weird. > > Dale > > :-) :-) > I tried the latest .39 kernel. It does the exact same thing as a .38 kernel. I also tried a kernel that was the first one I made when I built this rig. It locked up as well. It appears to me that either every single kernel, including ones that worked fine before, are either broke or it is not related to the kernel itself. I'm starting to bet on the last one. I did notice one thing tho. When I tried to emerge the nvidia drivers for the .39 kernel, emerge wanted to DOWNGRADE glibc. This ain't my first trip to Linux land. Can someone explain to me why the heck emerge wants to do something as crazy as that? I think every one here knows that is a really bad thing to even think of much less actually try. Is it possible that something in glibc is causing trouble and this is someone's wet dream to fix it? Thanks. Dale :-) :-)