Re: console_lock too early in printk???

[Chris L. <sa...@sk...>]

> > Moral of this story:  Don't you DARE use printk for debugging, you might
> > introduce more problems than you started with.  :)
> Especially with video drivers :-(

Or in my case... the VM system.  :)

> > On a more serious note... couldn't issues like these be temporarily side
> > stepped by making the console_lock recursive, similar to the monster
> > kernel_lock?  You could keep one copy of the entrance count with the lock
> > itself, rather than one copy each in the "current" task_struct...

> If we really want to fix this problem we have to rethink the console lock.
> See my other post.

I agree that a more general solution would be better... but it would
probably not be appropriate for 2.4.0...

-Chris