Bug 99848 - [BDW] intel_display.c:14180 intel_atomic_commit_tail+0xf2b/0xf50 [i915]
Summary: [BDW] intel_display.c:14180 intel_atomic_commit_tail+0xf2b/0xf50 [i915]
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-17 14:11 UTC by pj.crommen
Modified: 2017-06-29 14:29 UTC (History)
1 user (show)

See Also:
i915 platform: BDW
i915 features: display/atomic


Attachments
boot-log.txt (30.17 KB, text/plain)
2017-02-17 14:11 UTC, pj.crommen
no flags Details
screen lock log (19.20 KB, text/plain)
2017-02-17 14:12 UTC, pj.crommen
no flags Details

Description pj.crommen 2017-02-17 14:11:00 UTC
Created attachment 129689 [details]
boot-log.txt

4.9.6-3
Debian Stretch 
Dell E5550 (Core I5 5300U HD5500 GPU)
eDP
X.Org X Server 1.19.1

Intel AMT KVM (Keyboard, Video, Mouse) over network using Meshcommander (0.4.4 (http://www.meshcommander.com/meshcommander) ) 

Booting from poweroff to login screen with Meshcommander "Remote Desktop" causes a GPU freeze.
Same issue happens when Xscreensaver locks the screen in a connected session.

However when establishing a connection from a booted system, it does works correctly.
Comment 1 pj.crommen 2017-02-17 14:12:18 UTC
Created attachment 129690 [details]
screen lock log
Comment 2 pj.crommen 2017-02-17 15:13:00 UTC
(In reply to pj.crommen from comment #0)
> Created attachment 129689 [details]
> boot-log.txt
> 
> 4.9.6-3
> Debian Stretch 
> Dell E5550 (Core I5 5300U HD5500 GPU)
> eDP
> X.Org X Server 1.19.1
> 
> Intel AMT KVM (Keyboard, Video, Mouse) over network using Meshcommander
> (0.4.4 (http://www.meshcommander.com/meshcommander) ) 
> 
> Booting from poweroff to login screen with Meshcommander "Remote Desktop"
> causes a GPU freeze.
> Same issue happens when Xscreensaver locks the screen in a connected session.
> 
> However when establishing a connection from a booted system, it does work
> correctly.
Comment 3 Elizabeth 2017-06-27 21:49:01 UTC
(In reply to pj.crommen from comment #2)
> 

Hello,
Is this bug still valid? Is the problem still reproducible? If so, could you add dmesg please? Thank you.
Comment 4 pj.crommen 2017-06-29 10:06:53 UTC
We are currently not using AMT anymore due to it's limitations (keyboard layout support and authentication security concerns). 

Sorry,
Pieter-Jan
Comment 5 Elizabeth 2017-06-29 14:29:01 UTC
(In reply to pj.crommen from comment #4)
> We are currently not using AMT anymore due to it's limitations (keyboard
> layout support and authentication security concerns). 
> 
> Sorry,
> Pieter-Jan

Thanks for the answer Pieter-Jan,
It would had been good to know if the problem persisted, but since we can't validate it now, I'm going to close the bug. If later any new information about this case is gathered, please share it and mark as REOPEN. Thank you.


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.