Re: [Linux-fbdev-users] vesafb - high CPU usage after suspend-to-RAM

[Antonino A. D. <ad...@gm...>]

On Sun, 2007-08-19 at 20:28 +1000, William Pettersson wrote:
> Hey list,
> I've got a new Dell laptop, with an Nvidia 8400GS video card.  I can
> suspend to RAM fine, and waking up "works".  However, when waking up,
> the [vesafb] process starts hogging 100% of one of the cores (core2duo).
> 
> I've tried attaching strace to the vesafb process, but since it's a
> kernel thing (I assume), it doesn't print anything.  I've tried
> Alt+SysRq+T, but that doesn't show any stack trace for vesafb for some
> reason.  The only "interesting" thing that I've found is the following,
> in dmesg:
> Just after/during a suspend:
> vesafb: BUG, returned from vm86 with 0 (EIP: 0xc7e9b)
> vesafb: mode switch failed (eax: 0x0)
> 
> While trying to shut down after a suspend (doesn't print if I don't
> suspend, just shutdown):
> vesafb: BUG, returned from vm86 with 0 (EIP: 0xc18b2)
> vesafb: mode switch failed (eax: 0x4f02)
> 
> Can anyone clue me in on how to best debug this?  It's essentially
> leaving me one core down after a suspend, which is very annoying to say
> the least.
> 

You're probably using vesafb-tng, not the vanilla vesafb.  vesafb-tng is
maintained outside the kernel tree, so you have to ask for help
somewhere.

Tony