From: "Michael Niederle" <mniederle@gmx.at>
To: Chris Ball <cjb@laptop.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG
Date: Fri, 24 Dec 2010 01:32:24 +0100 [thread overview]
Message-ID: <20101224013224.43c0f9b3@simplux> (raw)
In-Reply-To: <m3d3os3tuz.fsf@pullcord.laptop.org>
Hi, Chris!
> > But exactly the same crash happened again some minutes ago. (I'm
> > now back to my old kernel.)
>
> Not sure I understand. Do you mean that the same crash happens on
> your older kernel now, or that you've reverted to your older kernel
> because you had another -rc5 crash? If the crash happens on -rc5 but
> not the older kernel (what revision is the older kernel?), that's
> extremely interesting.
It happened again on -rc5.
But the reason for the crashes could also be a hardware problem - today I used
(unintentionally) another USB-port (USB 2.0) for the drive containing the
btrfs-file-system then I used (for several month) before (USB 3.0).
Currently I'm running with -rc7. If the system still runs tomorrow morning I
will do another test with -rc5 - this time on the USB 3.0 port. This should show
whether this is a hardware or software problem.
Greetings, Michael
next prev parent reply other threads:[~2010-12-24 0:32 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 [this message]
2010-12-24 0:51 ` Chris Ball
2010-12-25 9:50 ` Michael Niederle
2010-12-25 11:46 ` Christian Thaeter
-- 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=20101224013224.43c0f9b3@simplux \
--to=mniederle@gmx.at \
--cc=cjb@laptop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox