From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@digeo.com>
Cc: Steven Cole <elenstev@mesatop.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm1
Date: 06 May 2003 09:36:38 -0600 [thread overview]
Message-ID: <m17k949jeh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030506083358.348edb4d.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> writes:
> 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 ;)
The biggest issue with kexec when you are in X is that nothing
tells X to shutdown. So you have to at least shutdown X manually.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@digeo.com>
Cc: Steven Cole <elenstev@mesatop.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm1
Date: 06 May 2003 09:36:38 -0600 [thread overview]
Message-ID: <m17k949jeh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030506083358.348edb4d.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> writes:
> 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 ;)
The biggest issue with kexec when you are in X is that nothing
tells X to shutdown. So you have to at least shutdown X manually.
Eric
--
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:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 6:16 2.5.69-mm1 Andrew Morton
2003-05-05 6:16 ` 2.5.69-mm1 Andrew Morton
2003-05-05 15:32 ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 16:45 ` 2.5.69-mm1 Greg KH
2003-05-06 9:49 ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 18:44 ` 2.5.69-mm1 Andrew Morton
2003-05-05 21:01 ` 2.5.69-mm1 William Lee Irwin III
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 11:09 ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 12:02 ` 2.5.69-mm1 David S. Miller
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 15:25 ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 14:20 ` 2.5.69-mm1 David S. Miller
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-06 15:47 ` 2.5.69-mm1 Dipankar Sarma
2003-05-05 21:02 ` 2.5.69-mm1 William Lee Irwin III
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 14:33 ` 2.5.69-mm1 Steven Cole
2003-05-06 15:33 ` 2.5.69-mm1 Andrew Morton
2003-05-06 15:33 ` 2.5.69-mm1 Andrew Morton
2003-05-06 15:36 ` Eric W. Biederman [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
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=m17k949jeh.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=akpm@digeo.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 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.