Opened 4 years ago

Last modified 4 years ago

#16355 new bug

[intel_extreme] Switching between workspaces may result in a black screen

Reported by: accessays Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: display, framebuffer, workspace, black screen Cc:
Blocked By: Blocking:
Platform: x86-64

Description

Steps to reproduce:

  1. CTRL + ALT + arrow keys
  2. Repeat 1. randomly until it hits

Usually happens when I reach workspace 4 (rightmost bottommost).

Driver: intel_extreme
HRev: hrev54384
CPU: Intel Core i7-3635QM
Laptop: Samsung Series 7 Chronos

The driver seems to support my display quite nicely, with backlight control being available. Workspace switching is a hit or miss though.

Looking at the syslog, this might just be the problem:
KERN: intel_extreme: intel_set_display_mode: Failed to allocate framebuffer !

Attachments (3)

syslog-3​ (429.5 KB ) - added by accessays 4 years ago.
1to2.diff​ (3.9 KB ) - added by accessays 4 years ago.
Switching from workspace 1 to workspace 2 (right)
2to4.diff​ (1.5 KB ) - added by accessays 4 years ago.
Switching from workspace 2 to workspace 4 (down)

Download all attachments as: .zip

Change History (5)

by accessays, 4 years ago

Attachment: syslog-3​ added

comment:1 by diver, 4 years ago

Component: Drivers → Drivers/Graphics/intel_extreme
Owner: changed from nobody to pulkomandy

by accessays, 4 years ago

Attachment: 1to2.diff​ added

Switching from workspace 1 to workspace 2 (right)

by accessays, 4 years ago

Attachment: 2to4.diff​ added

Switching from workspace 2 to workspace 4 (down)

comment:2 by accessays, 4 years ago

Those are diffs of the syslog after switching from WP 1 to 2, and then 2 to 4
Framebuffer allocation fails in both cases, but only in the second one does it result in screen turning black. This can be reliably reproduced. Only workspace 4 causes this.

Note: See TracTickets for help on using tickets.