From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel lockup, might be helpful log.
Date: Mon, 14 Dec 2015 12:38:32 +0000 (UTC) [thread overview]
Message-ID: <pan$e38ea$87a57c38$77699913$c9fa489c@cox.net> (raw)
In-Reply-To: 20151214083524.GD26782@carfax.org.uk
Hugo Mills posted on Mon, 14 Dec 2015 08:35:24 +0000 as excerpted:
> It's not just btrfs. Invalid opcode is the way that the kernel's BUG and
> BUG_ON macro is implemented.
Thanks. I indicated that I suspected broader kernel use further down the
reply, but it's very nice to have confirmation, both of invalid opcode
use elsewhere, and of it being the kernel's general implementation for
BUG and BUG_ON.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-12-14 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 22:55 Kernel lockup, might be helpful log Birdsarenice
2015-12-14 6:51 ` Duncan
2015-12-14 8:35 ` Hugo Mills
2015-12-14 12:38 ` Duncan [this message]
2015-12-14 7:36 ` Chris Murphy
2015-12-14 8:28 ` Birdsarenice
2015-12-14 12:06 ` Filipe Manana
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='pan$e38ea$87a57c38$77699913$c9fa489c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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