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 1Qn8IA-0000Dv-Tj for garchives@archives.gentoo.org; Sat, 30 Jul 2011 12:05:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DD0F921C2EE; Sat, 30 Jul 2011 12:04:54 +0000 (UTC) Received: from mail.ukfsn.org (unknown [77.75.108.3]) by pigeon.gentoo.org (Postfix) with ESMTP id BD3E121C2CD for ; Sat, 30 Jul 2011 12:03:22 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id BE7EDDED33 for ; Sat, 30 Jul 2011 13:03:20 +0100 (BST) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id x65woqZ58TP2 for ; Sat, 30 Jul 2011 13:03:57 +0100 (BST) Received: from wstn.localnet (unknown [78.32.181.186]) by mail.ukfsn.org (Postfix) with ESMTP id 91785DED27 for ; Sat, 30 Jul 2011 13:03:20 +0100 (BST) From: Peter Humphrey Organization: at home To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] X Freezes With Firefox on Many Post 2.6.38 Kernels Date: Sat, 30 Jul 2011 13:03:19 +0100 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo-r3; KDE/4.6.3; x86_64; ; ) References: <20110725182047.GM30008@ns1.bonedaddy.net> <201107301104.37945.michaelkintzios@gmail.com> <4E33DA50.6090001@gmail.com> In-Reply-To: <4E33DA50.6090001@gmail.com> 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 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107301303.19667.peter@humphrey.ukfsn.org> X-Archives-Salt: X-Archives-Hash: af7c51b341ac3b0088d2ffa322c81f90 On Saturday 30 July 2011 11:17:52 Dale wrote: > What could have caused this? Could it be a file system problem? I > don't think it is a physical failure since it is working now after > giving it a fresh start. I just don't get how this could have caused a > kernel panic. This is plain weird. One possibility is that, having now written to almost every location on the disk, its controller has marked some faulty blocks that used to contain code in the disk subsystem. If it was reading damaged data, there's no surprise in anything that happened next! > Would love to hear some thoughts on what caused this problem given the > fix. That's mine :-) (And it's not far off what I suggested to you before: that the lightning strike had damaged your hardware.) -- Rgds Peter Linux Counter 5290, 1994-04-23