From: Christian Thaeter <ct@pipapo.org>
To: "Michael Niederle" <mniederle@gmx.at>
Cc: linux-btrfs@vger.kernel.org, Chris Ball <cjb@laptop.org>,
Christian Kujau <lists@nerdbynature.de>
Subject: Re: kernel BUG
Date: Sat, 25 Dec 2010 12:46:28 +0100 [thread overview]
Message-ID: <20101225124628.33c47ed0@pluto.pipapo.org> (raw)
In-Reply-To: <20101225105028.7891342b@simplux>
Am Sat, 25 Dec 2010 10:50:28 +0100
schrieb "Michael Niederle" <mniederle@gmx.at>:
> Hi!
>
> It seems that in my case the bug (fs/btrfs/disk-io.c:2311) was caused
> by a hardware problem.
>
> I plugged by accident an usb-3.0-drive (that worked quite well for
> several weeks) into an usb-2.0-port (which worked quite well for
> several years). It seems that the two didn't like each other and
> caused these crashes after some time of idling (it seems that the
> idling is necessary for the crash, cause it never crashed while I was
> actually working).
>
> Greetings, Michael
yes looks the same case here too, I only wanted to point
out that this has to be fixed *someday*, Retrying after a bus reset,
mounting the filesystem readonly or block all IO on the filesystem, but
not bring down the kernel.
Christian
next prev parent reply other threads:[~2010-12-25 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 18:12 kernel BUG Dipl.-Ing. Michael Niederle
2010-12-23 19:43 ` Chris Ball
2010-12-23 20:55 ` Michael Niederle
2010-12-24 0:19 ` Chris Ball
2010-12-24 0:32 ` Michael Niederle
2010-12-24 0:51 ` Chris Ball
2010-12-25 9:50 ` Michael Niederle
2010-12-25 11:46 ` Christian Thaeter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-24 19:26 kernel bug Roman Kapusta
2011-09-24 19:45 ` Roman Kapusta
2011-09-26 0:50 ` Li Zefan
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=20101225124628.33c47ed0@pluto.pipapo.org \
--to=ct@pipapo.org \
--cc=cjb@laptop.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mniederle@gmx.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox