Re: console_lock too early in printk???

[James Simmons]

> 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 :-(

> 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.