Aaron Zang wrote:

> Hi J?rgen,
> I am trying to answer your question as hard as I can.
> I understand that the reason you raising these questions to this alias is that
> you are using our experimental Xorg binaries.

Yes.


> But actually virtual console
> has nothing to do with specific graphic card drivers or Xorg hardware
> specific parts.

I also suspect that the bug is in the nvidia graphics driver,
not in the Xorg server.


> The thing I would like to mention here is that the Xorg you are using is
> only an experimental version based on around snv_95.
> 
> If you really wants to S/R your system, I suggest you upgrade your Xorg
> to the latest Solaris one.

Of cause I would like to have both S/R and vconsole support
in Xorg on this system... :-)

Ok, on my amd64 boxes with nvidia chipsets / nvidia graphics there
are other issues with suspend/resume, anyway.  These have to be
fixed first, before the Xorg nvidia S3 resume SIGSEGV becomes
a real problem.

Fortunately, on my intel Notebook with ATI graphics hw there i
no S3 resume SIGSEGV with the (experimental) Xorg server.


> And pm-discuss at opensolaris.org is the proper alias, I saw you have
> already raised your question there. So most likely guys in that alias
> will also want to you upgrade your Xorg to the standard one.
> 
> Regards,
> Aaron
> 
> J?rgen Keil wrote:
> > What exactly is supposed to work (at this time)
> with
> > suspend-to-ram and the nvidia graphics kernel
> module?
> >
> > I'm running
> >
> > - SX:CE 96, bfu'ed to onnv.-gate nightly 2008-11-05
> >
> > - the latest version of the nvidia driver
> >
> 
> ttp://www.opensolaris.org/jive/thread.jspa?threadID=81
> 020&tstart=0
> >   The NVDAgraphicsr package version is
> VERSION=177.80,REV=2008.11.05.10.16
> >
> > - the (prototype) Xorg server with vtconsole
> support
> >
> 
> ttp://www.opensolaris.org/os/community/on/flag-days/pa
> ges/2008092402/
> >
> > - ASUS M2NPV-VM mainboard with GeForce 6150 GPU
> >   or
> >   ASUS M2N-SLI deluxe mainboard with GeForce 6200
> PCI-e card
> >
> >
> > In Randy's blog
> (http://blogs.sun.com/randyf/entry/solaris_suspend_and
> _resume_how)
> > there is an old entry that tells me that Xorg needs
> to be running
> > otherwise the nvidia module would not be able to
> suspend/resume the
> > system.  Is that still the case?
> >
> >
> > What I'm observing:  When I try a test
> suspend-to-ram (uadmin 3 22),
> > all drivers suspend, followed by all drivers
> resuming, but  Xorg crashes
> > with a SIGSEGV.
> >
> >
> > Nov  6 12:33:31 tiger2 nvidia: [ID 702911
> kern.notice] NOTICE: NVRM: RmPowerManagement: 5
> > Nov  6 12:33:31 tiger2 acpica: [ID 388040
> kern.notice] ACPI Error (dsopcode-0714): Field [IRQW]
> at 216 exceeds Buffer [NULL] size 192 (bits)
> [20080829]
> > Nov  6 12:33:31 tiger2 acpica: [ID 100000
> kern.notice]
> > Nov  6 12:33:31 tiger2 acpica: [ID 214508
> kern.notice] **** Exception AE_AML_BUFFER_LIMIT
> during execution of method
> [\_SB_.PCI0.VT86.FDC0._SRS] (Node ffffff02d2508610)
> > Nov  6 12:33:31 tiger2 acpica: [ID 100000
> kern.notice]
> > Nov  6 12:33:31 tiger2 acpica: [ID 652514
> kern.notice] Method Execution Stack:
> > Nov  6 12:33:31 tiger2 acpica: [ID 629890
> kern.notice]     Method [_SRS] executing:
> CreateWordField (Arg0, 0x19, IRQW)
> > Nov  6 12:33:31 tiger2 acpica: [ID 100000
> kern.notice]
> > Nov  6 12:33:31 tiger2 last message repeated 1 time
> > Nov  6 12:33:31 tiger2 acpica: [ID 800694
> kern.notice] Local Variables for method [_SRS]:
> > Nov  6 12:33:31 tiger2 acpica: [ID 168412
> kern.notice]     Local0: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 170460
> kern.notice]     Local1: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 172508
> kern.notice]     Local2: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 174556
> kern.notice]     Local3: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 176604
> kern.notice]     Local4: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 178652
> kern.notice]     Local5: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 180700
> kern.notice]     Local6: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 182748
> kern.notice]     Local7: 0 <Null Object>
> > Nov  6 12:33:31 tiger2 acpica: [ID 100000
> kern.notice]
> > Nov  6 12:33:31 tiger2 acpica: [ID 491357
> kern.notice] Arguments for Method [_SRS]:  (1
> arguments defined, max concurrency = 0)
> > Nov  6 12:33:31 tiger2 acpica: [ID 726733
> kern.notice]     Arg0:   ffffff02d2566ab8 <Obj>
>             Buffer(24) 47  1 F0  3 F0  3  1  6
> 33:31 tiger2 acpica: [ID 975561 kern.notice]
>     Arg1:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 975563 kern.notice]
>     Arg2:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 975565 kern.notice]
>     Arg3:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 975567 kern.notice]
>     Arg4:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 975569 kern.notice]
>     Arg5:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 975571 kern.notice]
>     Arg6:   0 <Null Object>
> v  6 12:33:31 tiger2 acpica: [ID 100000 kern.notice]
> > Nov  6 12:33:31 tiger2 acpica: [ID 317695
> kern.notice] ACPI Error (psparse-0627): Method
> parse/execution failed [\_SB_.PCI0.VT86.FDC0._SRS]
> (Node ffffff02d2508610), AE_AML_BUFFER_LIMIT
> > Nov  6 12:33:57 tiger2 genunix: [ID 603404
> kern.notice] NOTICE: core_log: Xorg[1027] core
> dumped: /cores/Xorg-1027
> > Nov  6 12:33:58 tiger2 cpr: [ID 208601 kern.notice]
> > Nov  6 12:33:58 tiger2 The system is back where you
> left!
> > Nov  6 12:33:58 tiger2 genunix: [ID 583038
> kern.notice] System has been resumed.
> >
> >
> > The acpica messages are about a problem with
> resuming the
> > ps/2 floppy controller; it appears to be an Asus
> acpi bios
> > problem.  I suspect it's not relevant for the nvdia
> resume
> > problem.
> >
> > Xorg core dump looks like this:
> > # pstack Xorg-1027
> > core 'Xorg-1027' of 1027:   /usr/X11/bin/Xorg :0
> -depth 24 -nolisten tcp -nobanner -auth /var/dt/A
> >  fffffd7fff239d10 strlen () + 40
> >  fffffd7fff28ee03 vsnprintf () + 7b
> >  00000000004b8aa7 LogVWrite () + 117
> >  00000000004b8c47 LogVMessageVerb () + a7
> >  00000000004ec2b8 xf86Msg () + a8
> >  00000000004ca92b sunKbdSetLeds () + 5b
> >  00000000004ca953 sunKbdOff () + 13
> >  00000000004ca280 xf86KbdOff () + 10
> >  00000000004e3565 xf86KbdProc () + 35
> >  00000000004c35ad AbortDDX () + 17d
> >  00000000004b8553 AbortServer () + 13
> >  00000000004b8974 FatalError () + e4
> >  00000000004e2823 xf86SigHandler () + b3
> >  fffffd7fff2ca3b6 __sighndlr () + 6
> >  fffffd7fff2bd5ff call_user_handler () + 2a7
> >  fffffd7fff2bd80e sigacthandler (b, 0,
> fffffd7fffdf5120) + c6
> >  --- called from signal handler with signal 11
> (SIGSEGV) ---
> >  fffffd7ff9d8faa9 ???????? ()
> >  0000000000000020 ???????? ()
> >
> > The %eip at the point of the SEGSEGV is in the
> > nvidia_drv.so shared library:
> >
> > # pmap Xorg-1027
> > core 'Xorg-1027' of 1027:   /usr/X11/bin/Xorg :0
> -depth 24 -nolisten tcp -nobanner -auth /var/dt/A
> > 0000000000400000       2036K r-x--
>  /usr/X11/bin/amd64/Xorg
> 000000000060D000         80K rw---
>   /usr/X11/bin/amd64/Xorg
> 0000000000800000      22524K rw---    [ heap ]
> > FFFFFD7FF9400000        264K r-x--
>  /usr/X11/lib/modules/amd64/libfb.so
> FFFFFD7FF9452000          8K rw---
>   /usr/X11/lib/modules/amd64/libfb.so
> FFFFFD7FF9800000          4K rw---
>  /usr/X11/lib/modules/amd64/libfb.so
> FFFFFD7FF9C00000       4256K r-x--
>   /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> FFFFFD7FFA128000        784K rw---
>  /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> FFFFFD7FFA1EC000        120K rw---
>   /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> FFFFFD7FFA3F0000          4K rwx--    [ anon ]
> > ...
> >
> >
> > OTOH, when I quit from dtlogin / Xorg and login on
> the 
> > text console and try the uadmin 3 22, the system
> suspends 
> > and resumes all drivers, but the video signal
> appears to 
> > be lost, that is, all I see is a black screen.
> >
> > The issue with the black screen does not happen
> when I
> > reboot into single user mode and use uadmin 3 22
> from
> > single user mode (that is, Xorg was never started).
> >   
> 
> _______________________________________________
> vconsole-discuss mailing list
> vconsole-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/vconsole-
> discuss
-- 
This message posted from opensolaris.org

Reply via email to