All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 62829] New: On S1 suspend, attached monitor does not enter low power state, MX420 NV17 AGP 4x card
Date: Wed, 27 Mar 2013 17:26:27 +0000	[thread overview]
Message-ID: <bug-62829-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2526 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=62829

          Priority: medium
            Bug ID: 62829
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: On S1 suspend, attached monitor does not enter low
                    power state, MX420 NV17 AGP 4x card
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: paula-VL1tVIhH15Ot+zzwz018cpVzexx5G7lz@public.gmane.org
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 77117
  --> https://bugs.freedesktop.org/attachment.cgi?id=77117&action=edit
dmesg output, suspend logs, other detail

Platform:

Computer: Dell Dimension 4100 circa 2001
Graphics card: NVIDIA MX420, P17, AGP 4x, circa 2002-2003
Distribution: Debian Wheezy with LXDE and nouveau graphics driver

Symptoms:

Once the computer is suspended, the attached monitor should also enter its
low power state (signified by the blue power led turning orange). This happens
properly when suspending Windows XP but does not happen when suspending Debian
Wheezy. With Debian Wheezy, the monitor first goes blank but not completely 
dark. After a few seconds, the monitor fades from mostly dark to completely 
dark but the power led remains blue when it should change to amber.

The machine wakes properly from the S1 suspend state.

I am new to linux but I believe that this problem is related to the nouveau
driver. The monitor can be placed into its low power state with xset. Also,
if the pm-util 99video shell script is modified to xset the monitor to its
low power state when suspending, it will go into that state but will awake 
once the nouveau kernel module does its suspend stuff. See attachment.

The Dimension 4100 enters the S1 state upon suspend, S3 is not supported.
This behavior is identical with  both Windows XP and Debian Wheezy.
Current draw in the S1 state is .20A under Windows XP and .25A with Wheezy.
The current draw difference may not be related to the graphics card but it is
interesting nevertheless. I have looked for related bugs but can't find any.
I speculate, however, that this problem may be common but just overlooked. It
appears that most people are interested in major failures like kernel panics
and what not.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4005 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-03-27 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 17:26 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-62829-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-03-27 17:33   ` [Bug 62829] On S1 suspend, attached monitor does not enter low power state, MX420 NV17 AGP 4x card bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02  6:00   ` [Bug 62829] [NV17] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-62829-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.