Messages in this thread | | | Subject | Re: console remains blanked | From | Benjamin Herrenschmidt <> | Date | Sat, 16 Jul 2005 00:25:35 +1000 |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |