All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Decky <martin@decky.cz>
To: linux-fbdev@vger.kernel.org
Subject: Re: [RFC] fbdev: allow multiple concurrent visible consoles
Date: Thu, 11 Aug 2011 10:57:21 +0000	[thread overview]
Message-ID: <4E43B591.8050009@decky.cz> (raw)
In-Reply-To: <1312799864-3468-1-git-send-email-FlorianSchandinat@gmx.de>

Hello Florian,

> This patch allows having multiple visible consoles that receive
> display updates. For example one can have running "top" to monitor
> the system on fb0 and at the same time work on a shell on fb1.

I hate to report this, because I would really appreciate this feature, 
but your patch (applied against kernel 3.0) breaks my machine.

I have an x86-64 machine with a dual-GPU ATI Radeon HD 4850 X2 (which 
acts essentially as two discrete R700s) driven by the "radeon" KMS driver.

If I use the "fbcon=map:01" boot option to map the even-numbered VCs to 
the first GPU and the odd-numbered VCs to the second GPU, the kernel 
patched with your patch encounters some sort of soft-lockup when 
initializing the second GPU (i.e. creating the fb1) while booting. The 
is no panic or oops message and I can reset the machine by hitting 
ctrl+alt+del, but there is no further progress. I can provide further 
observations if you would like to.


Best regards

Martin Decky

  reply	other threads:[~2011-08-11 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 10:37 [RFC] fbdev: allow multiple concurrent visible consoles Florian Tobias Schandinat
2011-08-08 10:37 ` Florian Tobias Schandinat
2011-08-11 10:57 ` Martin Decky [this message]
2011-08-16  6:41 ` Florian Tobias Schandinat

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=4E43B591.8050009@decky.cz \
    --to=martin@decky.cz \
    --cc=linux-fbdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.