From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [RFC] Try a bit harder to get output on the screen at panic time Date: Wed, 19 May 2010 17:34:49 -0700 Message-ID: <20100519173449.6babbdfa@virtuousgeek.org> References: <20100409151050.74ef6dcd@virtuousgeek.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100409151050.74ef6dcd@virtuousgeek.org> Sender: linux-kernel-owner@vger.kernel.org Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Linus Torvalds , Dave Airlie , James Simmons List-Id: dri-devel@lists.freedesktop.org On Fri, 9 Apr 2010 15:10:50 -0700 Jesse Barnes wrote: > This set of 3 patches makes it a little more likely we'll get panic > output onto the screen even when X is running, assuming a KMS enabled > stack anyway. > > It gets me from a blank or very sparsely populated black screen at > panic time, to one including the full backtrace and panic output at > panic time (tested with "echo c > /proc/sysrq-trigger" from an X > session). > > It doesn't cover every case; for instance I think it'll fail when X has > disabled the display, but those cases need to be handled with separate > patches anyway (need to add atomic DPMS paths for instance). > > Anyway, please test these out and let me know if they work for you. Ping Linus & Dave again. Have you guys tried these? Really, it's cool. -- Jesse Barnes, Intel Open Source Technology Center