From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/extent-tree.c:4754 followed by BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Thu, 08 Dec 2011 17:03:55 +0100 [thread overview]
Message-ID: <4EE0DFEB.2000904@jan-o-sch.net> (raw)
In-Reply-To: <vhv4r8-hb5.ln1@hurikhan.ath.cx>
On 07.12.2011 21:40, Kai Krakow wrote:
> Scrubbing reports 1 uncorrectable error. I have this error since my system
> froze due to some xorg graphic driver instability (was trying out SNA
> acceleration for sandybridge).
>
> The problematic file seems to be in /usr/portage but scrubbing doesn't tell
> me the filename (I was under the impression 3.2.x adds a patch which should
> report filenames).
It should. Did you take a look at dmesg output after scrubbing? If it
doesn't contain a hint on the file or block, please paste what you get.
> Everytime I run "emerge" (it is a gentoo system) my
> screen goes black after a few seconds and I can only revert to using ssh.
>
> Problem is: As soon as this happens, some filesystem accesses block the
> process in disk state, it cannot be killed. This initiates some feedback
> loop: From now on any other process trying to access the FS freezes. I can
> only reisub now. It seems to be fine if data comes from cache instead from
> disk.
Please try to grab sysrq+w output in this state.
-Jan
next prev parent reply other threads:[~2011-12-08 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 20:40 WARNING: at fs/btrfs/extent-tree.c:4754 followed by BUG: unable to handle kernel NULL pointer dereference at (null) Kai Krakow
2011-12-08 16:03 ` Jan Schmidt [this message]
2011-12-09 13:34 ` Kai Krakow
2011-12-15 4:11 ` Kai Krakow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE0DFEB.2000904@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.