[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKcLGm9kVOw6D8kPECfhfohH4pAT=09qws7-jRsh1TZJTyh1_A@mail.gmail.com>
Date: Thu, 19 Jan 2012 10:24:19 -0600
From: Mitch Harder <mitch.harder@...ayonlinux.org>
To: Vincent Vanackere <vincent.vanackere@...il.com>
Cc: linux-btrfs@...r.kernel.org,
Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [BUG - btrfs] kernel oops in extent_range_uptodate
On Thu, Jan 19, 2012 at 8:42 AM, Vincent Vanackere
<vincent.vanackere@...il.com> wrote:
> Hi,
>
> With the most current git kernel (90a4c0f51e8e44111a926be6f4c87af3938a79c3)
> I'm still getting the same reproducible kernel panic when trying to read a
> particular file stored on a btrfs filesystem (as seen in the log there are
> indeed disk media errors on this disk).
> I'd like the "software" part of this to be fixed - btrfs should definitely
> not oops even in case of media error - before sending the disk to RMA. Is
> there anything I can do to make progress on this ?
>
Is this kernel compiled with "Compile the kernel with debug info" (in
the "Kernel hacking --->" configuration section)?
It would be nice to have the specific line of code passing the NULL pointer.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists