All of lore.kernel.org
 help / color / mirror / Atom feed
From: "willy tarreau" <wtarreau@yahoo.fr>
To: "Randy.Dunlap" <rddunlap@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Cc: willy@meta-x.org
Subject: Re: announce: kmsgdump update for 2.5.75
Date: Wed, 23 Jul 2003 10:20:46 +0200 (CEST)	[thread overview]
Message-ID: <20030723082046.42027.qmail@web41609.mail.yahoo.com> (raw)
In-Reply-To: <20030718140309.623ff4c9.rddunlap@osdl.org>

Hi Randy, all.

OK finally I tested 2.5.74, 2.5.75 and 2.6.0-test1 on a PIII/800. They
all allowed be to get to the interactive screen after Sysrq-D (eventhough
the keyboard was dead after that, as always on this crappy machine/bios).

I noticed that you had a #define KDEBUG which puts printk's at every
checkpoint. I wonder if it's not risky to do this within the last ones,
when the machine is nearly ready to reboot. I'm not sure if this could
work with serial consoles or frame buffer. Could you please retry with
#undef KDEBUG ?

BTW, I'm not certain that the current code is still totally compatible
with standard kernel reboot techniques. I've read through it rather
quickly and compare it to other functions such as machine_real_restart(),
etc... It may be possible that we have to stop/notify some subsystems
prior to this.

FYI, on this machine, I enabled ACPI and local APIC, but disabled preempt.
Unfortunately, I don't have enough time to recheck with different combinations
of these options.

Hoping this helps a bit...

Cheers,
Willy


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

      reply	other threads:[~2003-07-23  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 21:03 announce: kmsgdump update for 2.5.75 Randy.Dunlap
2003-07-23  8:20 ` willy tarreau [this message]

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=20030723082046.42027.qmail@web41609.mail.yahoo.com \
    --to=wtarreau@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=willy@meta-x.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.