From: Mark Lord <lkml@rtr.ca>
To: Oliver Neukum <oliver@neukum.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Hans de Bruin <bruinjm@xs4all.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Kernelmessage to usbstick?
Date: Sun, 11 Jan 2009 13:07:35 -0500 [thread overview]
Message-ID: <496A3567.3090900@rtr.ca> (raw)
In-Reply-To: <200901102358.00984.oliver@neukum.org>
Oliver Neukum wrote:
> Am Saturday 10 January 2009 23:53:15 schrieb Andi Kleen:
>> Hans de Bruin <bruinjm@xs4all.nl> writes:
>>
>>> Would it be possible to send kernel messages to an usbstick? On
>>> poweroff my laptop displays a kernel trace and a final message:
>>> poweroff[3114] exited with preempt_count 2
>>> /etc/rc.d/rc.0: line 265: 3114 Segementation fault /sbin/poweroff.
>>> I don't have a serial cable within reach, but plenty of usbsticks.
>> There's a mtdoops.c indeed, but it currently only works on
>> MTD controlled flash devices, not usb sticks.
>>
>> However usb sticks would need the USB subsystem to be running and it's
>> unlikely that will be the case really late in poweroff. So it might
>> not help.
>
> USB in turn needs PCI, interrupts and DMA.
..
Dunno about an oops, but I currently use a USB device to
display debug messages from the shutdown procedure,
all the way to kernel_halt().
So long as the Oops doesn't kill too much low level stuff,
it's probably feasible. Except for the very slow write times
for many USB storage devices.
next prev parent reply other threads:[~2009-01-11 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 19:13 Kernelmessage to usbstick? Hans de Bruin
2009-01-10 22:53 ` Andi Kleen
2009-01-10 22:58 ` Oliver Neukum
2009-01-11 13:18 ` Hans de Bruin
2009-01-11 18:07 ` Mark Lord [this message]
2009-01-13 21:31 ` Hans de Bruin
2009-01-18 8:14 ` Pavel Machek
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=496A3567.3090900@rtr.ca \
--to=lkml@rtr.ca \
--cc=andi@firstfloor.org \
--cc=bruinjm@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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