Re: framebuffer console code triggered might_sleep assertion.

On Sat, Jul 08, 2006 at 08:56:03AM +0800, Antonino A. Daplas wrote:

 > Looks like the printk buffer was flushed on release_console_sem() while
 > the irqs are disabled. But the console (fbcon) thinks that it's still
 > okay to schedule() which triggered might_sleep().
 > 
 > Would the attached patch help? It disables console scheduling before
 > calling the console drivers.

This seemed to do the trick. I've not seen this since applying your patch.

		Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • framebuffer console code triggered might_sleep assertion.
    • From: Dave Jones <[email protected]>
  • Re: framebuffer console code triggered might_sleep assertion.
    • From: "Antonino A. Daplas" <[email protected]>

• Prev by Date: [git pull] jfs update
• Next by Date: Re: [test patch] seccomp: add code to disable TSC when enabling seccomp
• Previous by thread: Re: framebuffer console code triggered might_sleep assertion.
• Next by thread: BUG: soft lockup detected
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]