public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
To: ncunningham@linuxmail.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 12:22:43 +0200	[thread overview]
Message-ID: <m31xgcxi18.fsf@brain.gnuhh.org> (raw)
In-Reply-To: <1097019863.16541.47.camel@desktop.cunninghams> (Nigel Cunningham's message of "Wed, 06 Oct 2004 09:44:23 +1000")

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

 || On Wed, 06 Oct 2004 09:44:23 +1000
 || Nigel Cunningham <ncunningham@linuxmail.org> wrote: 

 >> When kdb is left and the buffer is different from 0, the contents
 >> are dumped to dmesg/syslog.

 nc> Something like printk :> It wouldn't work with suspending because
 nc> we're overwriting such buffers when copying the original kernel
 nc> back (with the contents from suspend-time). Furthermore, it won't
 nc> help if you get such a crash because you're never going to start
 nc> syslogd and get the data written.

I agree that it would not help in all cases.

In this case it would have helped, though. The machine is running,
syslog is doing its job -- that is how I got the sysrq-T output.

So if kbd had support for that, we could have saved ourselves the
trouble of taking a photograph of the screen and mailing that around.

Speaking of which: Since you told me that you did not see it, I just
resent it, please let me know whether it reaches you this time.

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2004-10-06 10:22 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
2004-10-06 10:22     ` Georg C. F. Greve [this message]
  -- 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=m31xgcxi18.fsf@brain.gnuhh.org \
    --to=greve@gnu.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ncunningham@linuxmail.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