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 1QnA7t-0006eb-Gy for garchives@archives.gentoo.org; Sat, 30 Jul 2011 14:02:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57D6521C26E; Sat, 30 Jul 2011 14:02:25 +0000 (UTC) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 9C73521C0D9 for ; Sat, 30 Jul 2011 14:00:30 +0000 (UTC) Received: by yxi13 with SMTP id 13so3618492yxi.40 for ; Sat, 30 Jul 2011 07:00:30 -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=OEMu06NZ7vJ0syKatWVfyuYA3INK32xbojZ1yv+go7s=; b=roFif/z+WP/xnIVEbS4vFrZ782x1Jdkislcf8NyRWrC7Lka3QeYAzEXoM9+jkjJryW 4geFId6vuuzNc2RVtl0i8YviIscf/N6YSuX3O9O/pyWHdGrSfnxJjAuP/R9TGOdm25Wj eyprpa7YEzn3pQCjq6lvRVUGbTpPQOb3xC2oo= Received: by 10.91.20.10 with SMTP id x10mr1975968agi.204.1312034430033; Sat, 30 Jul 2011 07:00:30 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-90-236.jan.bellsouth.net [65.0.90.236]) by mx.google.com with ESMTPS id k20sm2223723and.5.2011.07.30.07.00.28 (version=SSLv3 cipher=OTHER); Sat, 30 Jul 2011 07:00:29 -0700 (PDT) Message-ID: <4E340E7B.8010205@gmail.com> Date: Sat, 30 Jul 2011 09:00:27 -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> <201107301104.37945.michaelkintzios@gmail.com> <4E33DA50.6090001@gmail.com> <201107301303.19667.peter@humphrey.ukfsn.org> In-Reply-To: <201107301303.19667.peter@humphrey.ukfsn.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 11521492ff5f4e0921b01fda7c09bb21 Peter Humphrey wrote: > 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.) > > It could be that it was some bad bocks. It wasn't lightning tho. It was just a plain power failure where my UPS failed. The relay just didn't act quick enough that time I guess. Still weird that it caused a kernel panic. Dale :-) :-)