Bug 109541 - WARNING: CPU: 2 PID: 4801 at drivers/gpu/drm/i915/intel_display.c:9151 hsw_enable_pc8+0x5e3/0x730 [i915]()
Summary: WARNING: CPU: 2 PID: 4801 at drivers/gpu/drm/i915/intel_display.c:9151 hsw_en...
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: IA-64 Linux
: P1 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-18 15:57 UTC by Marcel Ziswiler
Modified: 2016-02-17 18:19 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.2.7-300.fc23.x86_64
Subsystem:
Regression: No
Bisected commit-id:

Attachments
full journal of gnome session crash (1.84 MB, application/octet-stream)
2015-12-18 15:57 UTC, Marcel Ziswiler 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Marcel Ziswiler 2015-12-18 15:57:35 UTC 
Created attachment 197681 [details]
full journal of gnome session crash

I resumed from suspend in UltraDock with DisplayPort screen connected.

Dec 17 10:08:19 localhost.localdomain kernel: WARNING: CPU: 2 PID: 4801 at drivers/gpu/drm/i915/intel_display.c:9151 hsw_enable_pc8+0x5e3/0x730 [i915]()

It resumend fine but 10 minutes later when attempting to click something on the application panel on the left the gnome session just crashed.

Dec 17 10:19:47 localhost.localdomain gnome-session-binary[2716]: WARNING: Lost name on bus: org.gnome.SessionManager
...
Dec 17 10:19:47 localhost.localdomain gnome-session-binary[2716]: WARNING: App 'gnome-shell.desktop' exited with code 1
...
Dec 17 10:19:48 localhost.localdomain kernel: WARNING: CPU: 0 PID: 2662 at drivers/gpu/drm/i915/intel_display.c:1362 assert_plane.constprop.99+0x6f/0x90 [i915]()
Dec 17 10:19:48 localhost.localdomain kernel: plane A assertion failure (expected on, current off)

Full logs attached.
Comment 1 Jani Nikula 2015-12-21 12:57:42 UTC 
Please file new i915 bugs at the freedesktop.org bugzilla:
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel

Before doing so, please also try the latest kernels, and try to look for duplicates on the fdo bugzilla.
Note You need to log in before you can comment on or make changes to this bug.