public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: arapov@gmail.com, poros@redhat.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, matt@console-pimps.org
Subject: FW/BIOS Bug category for oops.kernel.org
Date: Mon, 3 Nov 2014 22:26:10 +0100	[thread overview]
Message-ID: <20141103212610.GA10501@worktop.programming.kicks-ass.net> (raw)

Hi oops.kernel.org folks,

I'm wanting to collect information on FW/BIOS bugs, and I figured that
we could use the oops.kernel.org infrastructure to do this.

Now, I'd prefer to not use the regular BUG/WARN because it might confuse
users and the stacktrace is entirely pointless -- we know were/why we
generate the msgs.

Is everything between:

        pr_warn("------------[ cut here ]------------\n");
and:
        pr_warn("---[ end trace %016llx ]---\n", (unsigned long long)oops_id);

sucked in automagically, or do we need more magic?

I was thinking of adding a body like:

	FW/BIOS fail: $msg
	Hardware name: $dump_stack_arc_desc_str
	CPU model name: $cpuinfo_x86->x86_model_id

Which would allow us to index on both CPU and Hardware.


Can we make this happen?

             reply	other threads:[~2014-11-03 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 21:26 Peter Zijlstra [this message]
2014-11-03 21:34 ` FW/BIOS Bug category for oops.kernel.org Borislav Petkov
2014-11-03 21:51   ` Peter Zijlstra

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=20141103212610.GA10501@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=arapov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=poros@redhat.com \
    --cc=tglx@linutronix.de \
    /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