Opened 4 years ago

Last modified 15 months ago

#16406 new bug

Monitor does not power off with DPMS, screensaver freezes instead

Reported by: dogcow Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/intel_extreme/haswell Version:
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

System: Dell Optiplex 7020 i5-4590T, Intel HD/Iris (Haswell Desktop) graphics driver, monitor connected via DisplayPort

Reproducible on: R1/B2+116 and hrev54428 nightly (64-bit)

Symptoms: When the Turn off screen setting is enabled in ScreenSaver preferences, instead of the monitor powering down at the specified time interval, the screensaver "freezes" and the monitor stays on. Keyboard/mouse input exits the screensaver.

Attachments (4)

syslog (437.9 KB ) - added by dogcow 4 years ago.
syslog.2 (437.9 KB ) - added by dogcow 4 years ago.
syslog.old (512.1 KB ) - added by smallstepforman 2 years ago.
syslog for hrev55954, Intel Iris Pro (Haswell) MacBookPro 11.3
syslog.3 (203.1 KB ) - added by dogcow 2 years ago.
Syslog 2022-MAY-20

Download all attachments as: .zip

Change History (10)

comment:1 by pulkomandy, 4 years ago

You're lucky that the display works at all in Haswell :)

Please attach a syslog in any case, it will maybe help when we get to actually implementing Haswell support

by dogcow, 4 years ago

Attachment: syslog added

by dogcow, 4 years ago

Attachment: syslog.2 added

comment:2 by smallstepforman, 2 years ago

I have a MacBook Pro 11.3, with Intel Iris Extreme (Haswell). It locks on rocket icon. Attaching syslog. hrev55954

by smallstepforman, 2 years ago

Attachment: syslog.old added

syslog for hrev55954, Intel Iris Pro (Haswell) MacBookPro 11.3

comment:3 by korli, 2 years ago

dogcow, could you please test with a current nightly and attach a syslog?

by dogcow, 2 years ago

Attachment: syslog.3 added

Syslog 2022-MAY-20

comment:4 by dogcow, 2 years ago

I'm sorry to say I no longer have the computer that was experiencing this problem.

I just tried it on another system with a similar vintage CPU (i7-4500U, but its a laptop instead of a desktop: HP ProBook 430 G1) and the screen actually blanks (instead of screensaver freezing), but the display does not actually switch off. The backlight stays on. This was on hrev56119.

Attached a syslog from the HP ProBook in case its helpful.

Edit: Also tested hrev56119 on an HP EliteBook 8460p laptop with an i7-2620M CPU, and it works correctly: the display completely powers off.

Replying to korli:

dogcow, could you please test with a current nightly and attach a syslog?

Last edited 2 years ago by dogcow (previous) (diff)

comment:5 by mbrumbelow, 15 months ago

I see this on my i5 NUC, but in a different way. If I choose blank screensaver or gravity, set the screensaver to 1 hour and the screen off to 5 hours, when the 5 hour mark arrives the screen actually blanks (no freezing as described above), but the display does not actually switch off. The screen's backlight stays on.

Is this a driver issue or a code issue with the screensavers?

comment:6 by pulkomandy, 15 months ago

It's drivers. If you use the EFI driver I don't know if putting the screen to sleep is possible at all? For other drivers it depends on being able to send the correct EDIuD commands to the display, and it may be yet differents for laptops.

Maybe it's better to create your own ticket (referencing this one in the description) and provide full insormation: syslog, hardware list, etc.

Note: See TracTickets for help on using tickets.