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 44608] New: Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume
Date: Tue, 10 Jan 2012 02:17:14 +0000	[thread overview]
Message-ID: <bug-44608-8800@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 44608
           Summary: Freeze after Fn-F8 - Next boots: screen remains off
                    after suspend/resume
    Classification: Unclassified
           Product: xorg
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: vincent-fdt-buymaDBGzMOsTnJN9+BGXg@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


On my DELL Latitude E6400 laptop, when I type Fn-F8, the machine almost
completely freezes: the mouse pointer no longer moves, I can no longer connect
to the machine by SSH, and I can no longer control the screen brightness;
however I can still control the keyboard backlight. Once this is done, after
the following reboots, when I suspend the machine with Fn-F1 and resume it, the
screen remains off. I can still connect to the machine by SSH.

To solve this problem, I need to type: "xrandr --output LVDS-1 --auto". Then
the screen-off-after-resume bug no longer occurs... until I type Fn-F8 again.

lspci info: VGA compatible controller: nVidia Corporation G98M [Quadro NVS
160M] (rev a1)

When the resume fails to work correctly, I get the following additional lines
in the logs:

kernel: detected fb_set_par error, error code: -16
kernel: [drm] nouveau 0000:01:00.0: bo ffff8801186ef800 pinned elsewhere:
0x00000002 vs 0x00000004
kernel: [drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0080 Data 0x00000000 (0x0005
0x05)
kernel: [drm] nouveau 0000:01:00.0: bo ffff8801186ef800 pinned elsewhere:
0x00000002 vs 0x00000004
kernel: [drm:drm_helper_resume_force_mode] *ERROR* failed to set mode on crtc
ffff880117cb0000
kernel: [drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0080 Data 0x00000000 (0x1005
0x05)

The log files are provided in my bug report on the Debian BTS:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655183

Also, I don't know whether this matters, but in the syslog messages, I can see:

Jan 10 01:57:08 xvii kernel: [    0.171552] [Firmware Bug]: ACPI: BIOS
_OSI(Linux) query ignored
Jan 10 01:57:08 xvii kernel: [   13.152045] [Firmware Bug]: Duplicate ACPI
video bus devices for the same VGA controller, please try module parameter
"video.allow_duplicates=1"if the current driver doesn't work.

As requested in the Debian BTS, I'll attach drm.debug=6 dmesg.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-01-10  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  2:17 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-44608-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-01-10  2:19   ` [Bug 44608] Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-01-10  2:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24  3:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 23:36   ` 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-44608-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.