[Bug 44608] New: Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume

* [Bug 44608] New: Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume
@ 2012-01-10  2:17 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
       [not found] ` <bug-44608-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
  0 siblings, 1 reply; 5+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2012-01-10  2:17 UTC (permalink / raw)
  To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

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.

^ permalink raw reply	[flat|nested] 5+ messages in thread