From: Dave Jones <davej@redhat.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Willy Tarreau" <wtarreau@hera.kernel.org>,
"Dirk Hohndel" <hohndel@infradead.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
FBDEV-ML <linux-fbdev@vger.kernel.org>,
IDE-ML <linux-ide@vger.kernel.org>,
"Randy Dunlap" <rdunlap@xenotime.net>,
"James Bottomley" <James.Bottomley@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86-ML <x86@kernel.org>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
"Ingo Molnar" <mingo@redhat.com>, "Ingo Molnar" <mingo@elte.hu>,
"Jeff Garzik" <jgarzik@pobox.com>,
"Vivek Goyal" <vgoyal@redhat.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Hohndel, Dirk" <dirk.hohndel@intel.com>,
"Borislav Petkov" <bp@alien8.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Mark Lord" <kernel@teksavvy.com>,
"Arjan van de Ven" <arjan@infradead.org>,
KEXEC-ML <kexec@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Haren Myneni" <hbabu@us.ibm.com>,
"Eric Biederman" <ebiederm@xmission.com>,
"Tejun Heo" <tj@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Willy Tarreau" <w@1wt.eu>
Subject: Re: [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic
Date: Wed, 26 Jan 2011 18:16:21 -0500 [thread overview]
Message-ID: <20110126231620.GA14807@redhat.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53019438EABF@orsmsx505.amr.corp.intel.com>
On Wed, Jan 26, 2011 at 03:07:44PM -0800, Luck, Tony wrote:
> >- The latest approach (proposed by Linus) is to forget the disk: jump to
> > real-mode, but display the kernel log in a fancy format (with scroll
> > ups and downs) instead.
>
> A while ago (first Plumbers conference?) someone was talking about
> using a 2-d barcode to display the tail of the kernel log & oops
> register data - with the plan that you could capture the image with
> a cell phone camera, and then get all the oops data without worrying
> about transcription errors as you wrote down & re-typed all the hex.
>
> Anyone know what happened to that plan?
How is this more useful than a photograph of the backtrace ?
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-01-26 23:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110125134748.GA10051@laptop>
[not found] ` <AANLkTinU0KYiCd4p=z+=ojbkeEoT2G+CAYvdRU02KJEn@mail.gmail.com>
2011-01-26 12:49 ` [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic Ahmed S. Darwish
2011-01-26 12:58 ` Ingo Molnar
2011-01-26 13:34 ` Ahmed S. Darwish
2011-01-26 14:00 ` Ingo Molnar
2011-01-27 4:35 ` H. Peter Anvin
2011-01-27 11:41 ` Ingo Molnar
2011-01-27 15:47 ` Eric W. Biederman
2011-01-27 16:12 ` H. Peter Anvin
2011-01-26 23:07 ` Luck, Tony
2011-01-26 23:16 ` Dave Jones [this message]
2011-01-26 23:21 ` Luck, Tony
2011-01-27 1:09 ` Ahmed S. Darwish
[not found] ` <20110127021338.GA20334@redhat.com>
2011-01-27 3:33 ` Ahmed S. Darwish
2011-01-27 4:44 ` H. Peter Anvin
2011-01-27 5:26 ` Ahmed S. Darwish
2011-01-27 7:51 ` Eric W. Biederman
2011-02-02 11:13 ` Ahmed S. Darwish
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=20110126231620.GA14807@redhat.com \
--to=davej@redhat.com \
--cc=James.Bottomley@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bp@alien8.de \
--cc=darwish.07@gmail.com \
--cc=dirk.hohndel@intel.com \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=hbabu@us.ibm.com \
--cc=hohndel@infradead.org \
--cc=hpa@zytor.com \
--cc=jgarzik@pobox.com \
--cc=kernel@teksavvy.com \
--cc=kexec@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=w@1wt.eu \
--cc=wtarreau@hera.kernel.org \
--cc=x86@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