From: Chris Ball <cjb@laptop.org>
To: "Michael Niederle" <mniederle@gmx.at>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG
Date: Thu, 23 Dec 2010 19:19:32 -0500 [thread overview]
Message-ID: <m3d3os3tuz.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20101223215500.4f177913@simplux> (Michael Niederle's message of "Thu, 23 Dec 2010 21:55:00 +0100")
Hi Michael,
>> in write_all_supers(). Does dmesg say anything about the nature
>> of the errors above the BUG() line?
> The message was output to the console of the crashed system - so
> I'm sorry I cannot supply further informations.
Ah, okay. You could consider installing kgdb/kdb -- it will let you
drop to the kdb shell after the crash and run dmesg through a pager.
Just:
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
CONFIG_KGDB_TESTS=y
# CONFIG_KGDB_TESTS_ON_BOOT is not set
CONFIG_KGDB_LOW_LEVEL_TRAP=y
CONFIG_KGDB_KDB=y
CONFIG_KDB_KEYBOARD=y
and then boot with "kgdboc=kms,kbd" added.
> 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.
Josef/Chris, any knowledge about hitting this BUG() on -rc5?
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2010-12-24 0:19 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 [this message]
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
-- 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=m3d3os3tuz.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-btrfs@vger.kernel.org \
--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