> > > suspending device display at 0
> >
> > The above is more of a concern, and is probably why you are having
> > roblems. What is the framebuffer you are using? Can you provide a
> > 'prtconf -D' or scanpci?
>
> Problem is that the nvidia module stops sending debug output to
> the VGA console as soon as the nvidia module gets suspended.
> With a test suspend on my AMD box with mainboard integrated
> nvidia graphics I get no more debug output after suspending of the
> "display" / "nvidia" module, until "display" / "nvidia" resumes.
>
> That is, the bug could be in the nvidia module, but it could also be
> in any module that gets suspend after nvidia has suspend.
>
>
> I think Ettore has to repeat this test with the console redirected
> to a serial port, e.g. boot with " -B console=ttyb ", and run the
> suspend / test suspend on the COM2 serial console.
Agreed (or at least enable logging to the serial port).
Unfortunately, on the U20, this is a bit more difficult, as there
isn't an external serial port interface. The machine will need to be
opened and a DB9 header will need to be added. I will see if I can
dig up a procedure for adding this header.
>
> Btw. with my Toshiba Laptop and ATI video hardware ("vgatext"
> driver is used for "display"), screen output continues to work
> after suspending the vgatext device.
Some BIOS's re-POST on resume. Your Toshiba might be one (I
actually have an older SuperMicro that does). vgatext has no real
understanding of how it can save and restore the underlying hardware,
so setting 'vgatext_force_suspend' does nothing more than tell vgatext
to return success instead of failure on response to a suspend/resume.
Depending on this behavior could cause grief on other platforms.
Cheers!
---- Randy
