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 1QlRLA-0008UG-TD for garchives@archives.gentoo.org; Mon, 25 Jul 2011 20:01:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DD8F621C151; Mon, 25 Jul 2011 20:01:12 +0000 (UTC) Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 8C9B321C0D6 for ; Mon, 25 Jul 2011 20:00:09 +0000 (UTC) Received: by gxk9 with SMTP id 9so3313132gxk.40 for ; Mon, 25 Jul 2011 13:00:09 -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=IUJ7kd788OvwkEd1n/gIFz9trMe42GFB4H4jTID0yAQ=; b=KEFYSgvgvSpufqr39lpmYezK42N5N02p1SFPQ6s73s1MoJE4blHdj6UpsUErxB3+q5 0fjkvNfTei78ego5OUsCfdeEFcRPULhYZyYbT1qHGDo+5HgpzPeoMKvgm0sClhvPmo8g +l1lwcn9FXxlztiDzXaE55id+ZTYPNZCZGXtY= Received: by 10.150.47.35 with SMTP id u35mr3512890ybu.88.1311624009024; Mon, 25 Jul 2011 13:00:09 -0700 (PDT) Received: from [192.168.2.5] (adsl-98-95-151-157.jan.bellsouth.net [98.95.151.157]) by mx.google.com with ESMTPS id c11sm777850ybh.4.2011.07.25.13.00.07 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 13:00:08 -0700 (PDT) Message-ID: <4E2DCB46.9050106@gmail.com> Date: Mon, 25 Jul 2011 15:00:06 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110708 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] X Freezes With Firefox on Many Post 2.6.38 Kernels References: <20110725182047.GM30008@ns1.bonedaddy.net> <4E2DBFCB.7040003@gmail.com> <20110725185322.GA28131@ns1.bonedaddy.net> In-Reply-To: <20110725185322.GA28131@ns1.bonedaddy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 5e11ddd3b85d8188d22d92d805346c32 Todd Goodman wrote: > * Dale [110725 14:43]: > >> Todd Goodman wrote: >> >>> Dale (and whoever else was having problems with Firefox and X hangs,) >>> >>> I don't know if you've seen it but: >>> >>> http://lkml.org/lkml/2011/7/24/54 >>> >>> looks like a thread that might be applicable? >>> >>> Todd >>> >>> >>> >>> >> That does look interesting. I had a few times where mine would just >> hang and I could use the SysReq keys but most of the time it just plain >> paniced. >> > Yes, I remember that. But depending on your kernel config you could be > getting a "panic" based on settings (I believe.) > > That is true. I think .39 was the one that always paniced. It seems the later .38 wold sometimes give me a change to use the SysReq keys. It' shard to recall now. :/ >> I'm not subscribed so if you see something interesting, let me know. I >> wish I could let them know it also causes kernel panics as well. I >> suspect tho that whatever fix they come up with, it will fix it all. I >> may go back to a older kernel too. lol That may work for a temp fix >> anyway. >> > I'll let you know if I see anything that looks related. It would be > interesting if going back to 2.6.38 is a temp fix for you. I know you'd > tried older kernels before but... > > As someone else mentioned, you can certainly report it. However, it > would be very helpful if you can get the panic information. I know it's > difficult with X hanging and needing X to reproduce the problem but > SSHing to the machine and/or a netconsole might allow something to be > seen. And the panic information would likely be quite illuminating. > > I'm not subscribed there and that is a very high traffic list. I did take a look at the option of subscribing tho. I also tried to ssh into my rig from my old rig, it refused. It couldn't even find my box. It worked fine after I rebooted tho. >> Thanks very much for the link. At least it is not just me and they know >> about it now. >> > Yes, though hearing from more than one person with the issue might help > get it solved quicker. There may be similarities between your machines > that point he finger at a certain area... > > Todd > > >> Dale >> >> :-) :-) >> Yea, having more info would be helpful but it appears that more than I have has already been given. I may see if I can email someone directly or something. Maybe that will work, if I don't go to spam or something. Is this related to a specific nic driver? I wasn't able to really tell much from all the error messages they posted. I still haven't tried a different nic. I sort of been busy. Dale :-) :-)