Bug 44608 - Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume
Summary: Freeze after Fn-F8 - Next boots: screen remains off after suspend/resume
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-09 18:17 UTC by Vincent Lefevre
Modified: 2013-08-24 23:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
drm.debug=6 dmesg before the suspend (124.10 KB, application/octet-stream)
2012-01-09 18:19 UTC, Vincent Lefevre
no flags Details
drm.debug=6 dmesg after the resume (123.61 KB, application/octet-stream)
2012-01-09 18:20 UTC, Vincent Lefevre
no flags Details

Description Vincent Lefevre 2012-01-09 18:17:14 UTC
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.
Comment 1 Vincent Lefevre 2012-01-09 18:19:57 UTC
Created attachment 55360 [details]
drm.debug=6 dmesg before the suspend

This is from a test with the linux-image-3.2.0-rc7-amd64 3.2~rc7-1~experimental.1 Debian package.
Comment 2 Vincent Lefevre 2012-01-09 18:20:52 UTC
Created attachment 55361 [details]
drm.debug=6 dmesg after the resume
Comment 3 Ilia Mirkin 2013-08-24 03:37:37 UTC
Does this persist with kernel 3.10? A lot of suspend bugs have been fixed and introduced since you filed that bug.

Also, I'm not particularly clear on what all is going wrong. Note that "Fn-F8" and "Fn-F1" hold no special significance to most people. If the problem persists, please add a clearer description.
Comment 4 Vincent Lefevre 2013-08-24 23:36:04 UTC
I'm closing the bug since I can no longer reproduce any problem with my external screen. However, when I got the problem, it was with a projector, but I can't test with that.

"Fn-F8" does display switching. It seems to be a standard BIOS thing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.