[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100519173449.6babbdfa@virtuousgeek.org>
Date: Wed, 19 May 2010 17:34:49 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: unlisted-recipients:; (no To-header on input)
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Airlie <airlied@...il.com>,
James Simmons <jsimmons@...radead.org>
Subject: Re: [RFC] Try a bit harder to get output on the screen at panic
time
On Fri, 9 Apr 2010 15:10:50 -0700
Jesse Barnes <jbarnes@...tuousgeek.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists