> > > What output does it produce? Does it supend?
> >
> > Here's the output:
> >
> > Saving system state. Please wait...
> >
> > suspending drivers... suspending device mouse at 3
> > suspending device keyboard at 4
> > suspending device hub at 1
> > suspending device pci108e,534d at 2
> > suspending device pci108e,534d at 2,1
> > suspending device ide at 0
> > suspending device pci-ide at 4
> > suspending device disk at 0,0
> > suspending device disk at 1,0
> > suspending device pci108e,534d at 5
> > suspending device pci108e,534d at 5,1
> > suspending device pci108e,534d at 6
> > suspending device pci10de,370 at 6
> > suspending device pci108e,534d at 6,1
> > device pci108e,534d at 8 ica_ddi_setwake: could not
> evaluate _PRWg dev
> > 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.
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.
--
This message posted from opensolaris.org
