public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Albert Herranz <albert_herranz@yahoo.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: console remains blanked
Date: Sat, 16 Jul 2005 00:25:35 +1000	[thread overview]
Message-ID: <1121437536.5963.24.camel@gaston> (raw)
In-Reply-To: <20050713231200.24037.qmail@web25801.mail.ukl.yahoo.com>

On Thu, 2005-07-14 at 01:12 +0200, Albert Herranz wrote:
> Hi,
> 
> Looks like, since [1] was merged, a blanked console
> (due to inactivity for example) doesn't get unblanked
> anymore when new output is written to it.
> 
> This hunk of the already metioned patch, which
> modifies vt_console_print() in drivers/char/vt.c, is
> possibly the cause:

Yes. We discussed that with Linus back then. The problem is that the
printk subsystem tend to abuse calling low level drivers at interrupt
time, and in the case of blanking/unblanking, this can be a problem.
Radeonfb for example relies on beeing able to schedule() at
blank/unblank time.

If this "feature" is really important, maybe the best is to trigger the
workqueue and do the ublank from there.

Ben.



  parent reply	other threads:[~2005-07-15 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 23:12 console remains blanked Albert Herranz
2005-07-14  9:35 ` Jan Engelhardt
2005-07-14 10:18   ` Albert Herranz
2005-07-14 11:38     ` Jan Engelhardt
2005-07-15 14:27       ` Benjamin Herrenschmidt
2005-07-15 14:26     ` Benjamin Herrenschmidt
2005-07-15 14:25 ` Benjamin Herrenschmidt [this message]
2005-07-15 15:09   ` Albert Herranz

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=1121437536.5963.24.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=albert_herranz@yahoo.es \
    --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