mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Any SYSRQ key to force mode switch to console mode when using KMS?
Date: Tue, 21 Sep 2010 15:10:33 -0700	[thread overview]
Message-ID: <20100921151033.80e61747.randy.dunlap@oracle.com> (raw)
In-Reply-To: <19601.1301.803816.92851@elektron.ikp.physik.tu-darmstadt.de>

On Wed, 15 Sep 2010 19:40:37 +0200 Uwe Bonnes wrote:

> Hello,
> 
> is there any SYSRQ key that forces the video system to console mode,
> especially when using KMS and allows to work on. 

sysrq-v help message says:

force-fb(V) = "Restore framebuffer console"

> Since going to KMS on a Thinkpad R50 with ATI Radeon RV250 via going from
> Opensuse-11.2 to Opensuse-11.3 I experience frequent situations where I am
> left with a black screen, with only ALT-SYSREQ-C switching the screen back
> on and hard reboot as only chance to escape that situation.
> 
> Situations that result in a black screen are:
> 
> * Going with the mouse over the NOSCRIPT buttom in firefox. Load goes up and
> screen goes black after some seconds. xorg.log ends with "Backtrace", but no
> backtrace output...
> 
> * Calling pm-hibernate on a system that has hibernated before. First
>   pm-hibernate/wake-up-per power buttom sequence is successfull.
> 
> Disabling KMS results in very slow "kaffeine" full screen output...
> 
> pm-hibernate and firefox/noscript worked pre-KMS on opensuse-11.2.
> 
> Some traces of other people hitting the NOSCRIPT xorg crash and others
> hitting the black unresponsive screen with KMS on RV250 are
> found on the net, but I didn't find a conclusive resolution.
> 
> Opensuse default kernel and the recent Opensuse 2.6.36-rc3 kernel-of-the day
> were tested with no difference
> 
> Thanks
> 
> PS: I only follow linux-kernel via gmane.org, so if you need fast feedback,
> please CC me. 

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-21 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 17:40 Uwe Bonnes
2010-09-21 22:10 ` Randy Dunlap [this message]
2010-09-22  9:44   ` Uwe Bonnes
2010-09-22 15:24     ` Randy Dunlap
2010-09-23  9:51       ` Uwe Bonnes
2010-09-23 13:01         ` Uwe Bonnes
2010-09-23 15:02           ` Randy Dunlap
2010-09-23 16:31             ` Uwe Bonnes
2010-09-24 15:07               ` Randy Dunlap
2010-10-06 18:44                 ` Jason Wessel

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=20100921151033.80e61747.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=bon@elektron.ikp.physik.tu-darmstadt.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®