From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: 2.5.69-mm1 From: Steven Cole In-Reply-To: References: <20030504231650.75881288.akpm@digeo.com> <1052231590.2166.141.camel@spc9.esa.lanl.gov> <20030506083358.348edb4d.akpm@digeo.com> Content-Type: text/plain Message-Id: <1052238949.2166.145.camel@spc9.esa.lanl.gov> Mime-Version: 1.0 Date: 06 May 2003 10:35:50 -0600 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: "Eric W. Biederman" Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On Tue, 2003-05-06 at 09:36, Eric W. Biederman wrote: > Andrew Morton writes: > > > Steven Cole 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 Thanks for the answers. Kexec is pretty cool as it stands. I hope Linus merges it soon. Steven "very impatient" Cole -- 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: aart@kvack.org