From: Nigel Cunningham <ncunningham@linuxmail.org>
To: "Georg C. F. Greve" <greve@gnu.org>
Cc: ACPI List <acpi-devel@lists.sourceforge.net>,
SoftwareSuspend-Devel <softwaresuspend-devel@lists.berlios.de>
Subject: Re: status update for current development on ASUS M2N
Date: Wed, 06 Oct 2004 09:44:23 +1000 [thread overview]
Message-ID: <1097019863.16541.47.camel@desktop.cunninghams> (raw)
In-Reply-To: <m3ekkiqdcy.fsf@brain.gnuhh.org>
Hi.
On Sat, 2004-10-02 at 08:31, Georg C. F. Greve wrote:
> || On Fri, 01 Oct 2004 07:48:08 +1000
> || "Nigel Cunningham" <ncunningham@linuxmail.org> wrote:
>
> >> Can you tell me how to do this, please?
>
> nc> The simplest way is to do a digital photograph, I'm afraid. The
> nc> 'nice' way is to hook up a serial console and capture the output.
>
> That is rather inconvenient.
>
> I'm curious. Any reason that nobody implemented something to do this?
>
> I would assume that a kdb buffer that is reserved at startup,
> initalized with 0s and into which only kdb can write during debugging.
>
> When kdb is left and the buffer is different from 0, the contents are
> dumped to dmesg/syslog.
Something like printk :> It wouldn't work with suspending because we're
overwriting such buffers when copying the original kernel back (with the
contents from suspend-time). Furthermore, it won't help if you get such
a crash because you're never going to start syslogd and get the data
written.
Sorry.
Nigel
next prev parent reply other threads:[~2004-10-05 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 21:48 status update for current development on ASUS M2N Nigel Cunningham
2004-10-01 22:31 ` Georg C. F. Greve
2004-10-04 10:05 ` Georg C. F. Greve
2004-10-05 23:44 ` Nigel Cunningham [this message]
2004-10-06 10:22 ` Georg C. F. Greve
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 8:47 Georg C. F. Greve
2004-09-27 10:11 ` Nigel Cunningham
2004-09-27 16:48 ` Georg C. F. Greve
2004-09-27 12:33 ` Karol Kozimor
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=1097019863.16541.47.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greve@gnu.org \
--cc=softwaresuspend-devel@lists.berlios.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