> 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.
What should be done is the console blank timer be passed onto
console_callback.
P.S
I reversed some of the cursor changes. It uses static buffers again
until we have these issues solved. The code works as long as you don't use
more than one framebuffer device but it is rock solid like before for a
single framebuffer device. I will have a patch ready in the hour.
-
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/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:24 EST