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 1Qn94V-0005my-Du for garchives@archives.gentoo.org; Sat, 30 Jul 2011 12:55:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2B7B21C150; Sat, 30 Jul 2011 12:54:59 +0000 (UTC) Received: from mail-fx0-f53.google.com (mail-fx0-f53.google.com [209.85.161.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 3EFFC21C05E for ; Sat, 30 Jul 2011 12:53:52 +0000 (UTC) Received: by fxd23 with SMTP id 23so4344577fxd.40 for ; Sat, 30 Jul 2011 05:53:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=0Vbp4Y9FIuysrRS/IsaHifkghMyQX0kw07Mj0lIovDk=; b=lXUuXaRsBTjFOH+EN8yPZhY55ZQqWsw5UaDgdg8Fj2//sx1ffXemJ3m3UdYiwHmlaQ siJUI23UcZ5XDRzbVZs3El4KL7+MID6DsrXGZNnf6PHN/5Tvh0kuwhakac4KWIWRxOm9 FJPlTEoel7iJcl6pU5xWVEyMfR7HhWIpQ5YRA= 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 Received: by 10.223.161.74 with SMTP id q10mr3422507fax.117.1312030432335; Sat, 30 Jul 2011 05:53:52 -0700 (PDT) Received: by 10.223.28.139 with HTTP; Sat, 30 Jul 2011 05:53:52 -0700 (PDT) In-Reply-To: <201107301303.19667.peter@humphrey.ukfsn.org> References: <20110725182047.GM30008@ns1.bonedaddy.net> <201107301104.37945.michaelkintzios@gmail.com> <4E33DA50.6090001@gmail.com> <201107301303.19667.peter@humphrey.ukfsn.org> Date: Sat, 30 Jul 2011 08:53:52 -0400 Message-ID: Subject: Re: [gentoo-user] X Freezes With Firefox on Many Post 2.6.38 Kernels From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 7621c6d16c2a375e40c3b4827304d230 On Sat, Jul 30, 2011 at 8:03 AM, Peter Humphrey wrote: > On Saturday 30 July 2011 11:17:52 Dale wrote: > >> What could have caused this? =C2=A0Could it be a file system problem? = =C2=A0I >> don't think it is a physical failure since it is working now after >> giving it a fresh start. =C2=A0I just don't get how this could have caus= ed a >> kernel panic. =C2=A0This is plain weird. > > One possibility is that, having now written to almost every location on t= he > disk, its controller has marked some faulty blocks that used to contain c= ode > in the disk subsystem. If it was reading damaged data, there's no surpris= e > in anything that happened next! Well, except that it should have thrown some errors when the on-platter reed-solomon encoding didn't quite match. If the controller flagged some faulty blocks, it should show up via smartctl -A $DEVICE_NODE --=20 :wq