From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: 2.5.69-mm1 References: <20030504231650.75881288.akpm@digeo.com> <1052231590.2166.141.camel@spc9.esa.lanl.gov> <20030506083358.348edb4d.akpm@digeo.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: 06 May 2003 09:36:38 -0600 In-Reply-To: <20030506083358.348edb4d.akpm@digeo.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: Steven Cole , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: 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 -- 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