From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 6 May 2003 08:33:58 -0700 From: Andrew Morton Subject: Re: 2.5.69-mm1 Message-Id: <20030506083358.348edb4d.akpm@digeo.com> In-Reply-To: <1052231590.2166.141.camel@spc9.esa.lanl.gov> References: <20030504231650.75881288.akpm@digeo.com> <1052231590.2166.141.camel@spc9.esa.lanl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Steven Cole Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, ebiederm@xmission.com List-ID: 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 ;) -- 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