Summary: | [i915] Kernel warning about intel_display_power_put | Kernel 3.16 | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | quachtlc | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED INVALID | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
quachtlc
2015-03-23 18:09:43 UTC
Does the bug happen with any newer kernels? If it does, please add drm.debug=0xe to your kernel command line and attach the output of dmesg to this bug report. This doesn't happen with the 4.0 kernel, it also occurs on the 2015 X1 Carbon and X250. I can't really use the 4.0 kernel though, we require LTS releases or backported trusty kernels. I can reproduce this by suspending my laptop (closing the lid) on the login screen. When I resume, I get this error in syslog. (In reply to quachtlc from comment #3) > I can reproduce this by suspending my laptop (closing the lid) on the login > screen. When I resume, I get this error in syslog. As requested in comment 1, please add drm.debug=0xe to your kernel command line and attach the output of dmesg to this bug report. Created attachment 116579 [details]
dmesg
There wasn't a stack trace this time, but I got i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment (In reply to quachtlc from comment #2) > This doesn't happen with the 4.0 kernel, it also occurs on the 2015 X1 > Carbon and X250. I can't really use the 4.0 kernel though, we require LTS > releases or backported trusty kernels. You should ask your distro for support with their LTS kernels. (In reply to quachtlc from comment #3) > I can reproduce this by suspending my laptop (closing the lid) on the login > screen. When I resume, I get this error in syslog. If I understand correctly, this triggers the issue with 3.16, but not with 4.0, right? There's nothing we can do about kernel 3.16 as it reached EOL, so I'm closing this bug. |
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.