linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: invalid opcode 0000 / kernel bug with defect HDD
Date: Tue, 28 Jun 2016 09:26:43 +0000 (UTC)	[thread overview]
Message-ID: <pan$278cb$db1a74f8$df6075a2$e36deafd@cox.net> (raw)
In-Reply-To: CAEtw4r1OMSwMpoyiaO0oqKM+cWbt0AEo3apwJS5qybG3HsPn-g@mail.gmail.com

Peter Becker posted on Tue, 28 Jun 2016 10:16:58 +0200 as excerpted:

> Cause of kernel bugs was a defective HDD (/dev/sdd).

Just a short note to mention that invalid opcode 0000 doesn't say much.  
I'm just another user and list regular, but apparently, opcode 0000 is 
used as a deliberate way to trigger a kernel bugon, when the kernel hits 
code that it isn't expected to ever hit in normal operations.  Given that 
common usage, opcode 0000 itself says very little except that something 
went wrong, which we already know given the triggered backtrace.

While the 0000 opcode isn't of much help, however, devs can make more 
sense of the backtrace, particularly in cases such as this where it has 
the file and line number that triggered the bugon.  That and the other 
information provided does help quite a bit to trace down the bug.

(At first I was wondering about all these opcode 0000 traces too, until 
someone explained that to me.)

-- 
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


  reply	other threads:[~2016-06-28  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  8:16 invalid opcode 0000 / kernel bug with defect HDD Peter Becker
2016-06-28  9:26 ` Duncan [this message]
2016-06-29  1:43 ` Liu Bo

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$278cb$db1a74f8$df6075a2$e36deafd@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;
as well as URLs for NNTP newsgroup(s).