From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Thomas Molina <tmolina@cox.net>,
Thomas Schlichter <schlicht@uni-mannheim.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: fbcon sleeping function call from illegal context
Date: 26 Mar 2003 22:57:44 +0100 [thread overview]
Message-ID: <1048715864.10475.61.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0303261811350.18664-100000@phoenix.infradead.org>
On Wed, 2003-03-26 at 19:33, James Simmons wrote:
> > Running with the patch as posted by Mr. Simmons I didn't get any further
> > instances of the sleeping function call from illegal context messages I
> > reported before, until screenblanking went into effect. I then got the
> > following:
>
> Oh no!!! I just look at the console timer blanking code. It calls alot of
> stuff. Not only does this mean we are limited in using kmalloc if we need
> it but also using a semaphore to sync up the fb_pixmap stuff. At present
> we use a spinlock. I tried it with a semphore but it kept hosing my
> system. Now I know why.
Junk. Move that console blanking stuff to process context too.
Actually, I've never fully understood some of the console blanking
code, especially the PM callback in there which does really weird
things. On pmacs, this code cause the screen to first blank, then
unblank, then blank again when the machine is going to sleep.
Ben.
prev parent reply other threads:[~2003-03-26 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 14:31 Thomas Molina
2003-03-26 14:48 ` Thomas Schlichter
2003-03-26 16:58 ` Thomas Molina
2003-03-26 18:33 ` James Simmons
2003-03-26 21:57 ` Benjamin Herrenschmidt [this message]
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=1048715864.10475.61.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@uni-mannheim.de \
--cc=tmolina@cox.net \
/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®