From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: unlisted-recipients:; (no To-header on input)
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@gmail.com>,
James Simmons <jsimmons@infradead.org>
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 [thread overview]
Message-ID: <20100519173449.6babbdfa@virtuousgeek.org> (raw)
In-Reply-To: <20100409151050.74ef6dcd@virtuousgeek.org>
On Fri, 9 Apr 2010 15:10:50 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> 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
next prev parent reply other threads:[~2010-05-20 0:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 22:10 [RFC] Try a bit harder to get output on the screen at panic time Jesse Barnes
2010-04-09 22:11 ` [PATCH] drm: add locked variant of drm_fb_helper_force_kernel_mode Jesse Barnes
2010-04-12 0:05 ` Dave Airlie
2010-04-12 15:46 ` Jesse Barnes
2010-04-12 16:05 ` Jesse Barnes
2010-04-09 22:12 ` [PATCH] vt: try harder to print output when panicing Jesse Barnes
2010-04-09 22:12 ` [PATCH] fbcon: assume console is active if panicing Jesse Barnes
2010-04-19 22:05 ` [RFC] Try a bit harder to get output on the screen at panic time Jesse Barnes
2010-05-20 0:34 ` Jesse Barnes [this message]
2010-05-20 1:13 ` Maxim Levitsky
2010-05-20 1:27 ` Maxim Levitsky
2010-05-20 16:28 ` Jesse Barnes
2010-05-20 21:14 ` Maxim Levitsky
2010-05-21 21:57 ` Maxim Levitsky
2010-05-21 22:02 ` Jesse Barnes
2010-05-21 22:26 ` Maxim Levitsky
2010-05-30 14:48 ` Maxim Levitsky
2010-06-06 16:36 ` James Simmons
2010-06-08 23:20 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 5:03 Jesse Barnes
2010-05-31 6:09 ` Dave Airlie
2010-05-31 7:06 ` Maxim Levitsky
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=20100519173449.6babbdfa@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox