https://bugzilla.novell.com/show_bug.cgi?id=744938 https://bugzilla.novell.com/show_bug.cgi?id=744938#c0 Summary: Suspend or S1 sleep do not completely cut off monitor signal. Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: arun.chandrashekhar@lsi.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; .NET4.0C; MS-RTC LM 8) On one of the newer Hardware platforms, it is observed that when the "Suspend" operation is executed monitor signal is not completely going off. The monitor goes blank but the Monitor signal is till on. (Signal state is Green. This signal should turn amber. The suspend/S1 sleep is executed using on of the options. - Either by a GUI menu - Or by command "echo -n standby > /sys/power/state" - We tried both with Onboard Graphics controller and also with an External Video Card (ATI Radeon). The issue remains same. But when the system power button is pressed, the system wakes up from S1 sleep. So looks like the S1 functionality is working, but the due to monitor not turning off, the user is not clear whether S1 sleep process completed ot not. Reproducible: Always Steps to Reproduce: 1. From GUI mode Click on suspend. 2. From CLI mode, type "echo -n standby > /sys/power/state" 3. Actual Results: The monitor goes blank. But the signal is green. So by seeing the monitor signal, user is not clear whether s1 has actually occcurred or not. Expected Results: THe monotor should be turned off. (Signal should turn amber). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.