From: Andrew Morton <akpm@digeo.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, ebiederm@xmission.com
Subject: Re: 2.5.69-mm1
Date: Tue, 6 May 2003 08:33:58 -0700 [thread overview]
Message-ID: <20030506083358.348edb4d.akpm@digeo.com> (raw)
In-Reply-To: <1052231590.2166.141.camel@spc9.esa.lanl.gov>
Steven Cole <elenstev@mesatop.com> wrote:
>
> I have one machine for testing which is running X, and a kexec reboot
> glitches the video system when initiated from runlevel 5. Kexec works fine
> from runlevel 3.
Yes, there are a lot of driver issues with kexec. Device drivers will assume
that the hardware is in the state which the BIOS left behind.
In this case, the Linus device driver's shutdown functions are obviously not
leaving the card in a pristine state. A lot of drivers _do_ do this
correctly. But some don't.
It seems that kexec is really supposed to be invoked from run level 1. ie:
you run all your system's shutdown scripts before switching. If you'd done
that then you wouldn't have been running X and all would be well.
do-kexec.sh is for the very impatient ;)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-06 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 6:16 2.5.69-mm1 Andrew Morton
2003-05-05 21:01 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 11:09 ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 12:02 ` 2.5.69-mm1 David S. Miller
2003-05-06 15:25 ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 14:20 ` 2.5.69-mm1 David S. Miller
2003-05-06 15:47 ` 2.5.69-mm1 Dipankar Sarma
2003-05-05 21:02 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 14:33 ` 2.5.69-mm1 Steven Cole
2003-05-06 15:33 ` Andrew Morton [this message]
2003-05-06 15:36 ` 2.5.69-mm1 Eric W. Biederman
2003-05-06 16:35 ` 2.5.69-mm1 Steven Cole
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=20030506083358.348edb4d.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=ebiederm@xmission.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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