Extessive timeout warning on some machines with i915_bdw
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Robert Hooker | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
SRU Justification:
Impact: Kernel warning every boot making it seem like the system is faulty but it is harmless. This only applies to i915_bdw on trusty, and is impacting certification on some prerelease machines.
Fix: Upstream increased the timeout required to hit it so it will not affect the machines we have anymore in 3.14, and also demoted it from a warning to DRM_INFO_ONCE.
Testcase: Boot trusty on an affected broadwell machine, check dmesg for warning
[Results]
Expected: There should be no WARNING messages for i915_bdw.
Actual: This warning is displayed
[ 13.157688] ------------[ cut here ]------------
[ 13.157726] WARNING: CPU: 3 PID: 395 at /build/
[ 13.157729] excessive driver sleep timeout (DSPL) 1000
[ 13.157732] Modules linked in: crct10dif_pclmul(+) lib80211_crypt_tkip crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_intel(OF+) snd_hda_
[ 13.157779] CPU: 3 PID: 395 Comm: systemd-udevd Tainted: PF O 3.13.0-32-generic #57-Ubuntu
[ 13.157783] Hardware name: Dell Inc. FOOBAR, BIOS R21 07/17/2014
[ 13.157785] 0000000000000009 ffff880156921818 ffffffff8171bcb4 ffff880156921860
[ 13.157790] ffff880156921850 ffffffff810676cd ffffc900106a0218 ffff88003598d800
[ 13.157794] 00000000000001f4 0000000000000008 ffff880156921928 ffff8801569218b0
[ 13.157799] Call Trace:
[ 13.157807] [<ffffffff8171b
[ 13.157812] [<ffffffff81067
[ 13.157815] [<ffffffff81067
[ 13.157847] [<ffffffffa02bc
[ 13.157870] [<ffffffffa02bd
[ 13.157903] [<ffffffffa02e2
[ 13.157927] [<ffffffffa01a2
[ 13.157943] [<ffffffffa01a4
[ 13.157966] [<ffffffffa0263
[ 13.157972] [<ffffffff813a6
[ 13.157976] [<ffffffff813a7
[ 13.157981] [<ffffffff813a7
[ 13.157987] [<ffffffff81493
[ 13.157991] [<ffffffff81493
[ 13.157995] [<ffffffff81493
[ 13.158000] [<ffffffff81491
[ 13.158004] [<ffffffff81492
[ 13.158007] [<ffffffff81492
[ 13.158013] [<ffffffffa032f
[ 13.158017] [<ffffffff81493
[ 13.158021] [<ffffffffa032f
[ 13.158026] [<ffffffff813a5
[ 13.158039] [<ffffffffa01a4
[ 13.158044] [<ffffffffa032f
[ 13.158066] [<ffffffffa032f
[ 13.158070] [<ffffffff81002
[ 13.158076] [<ffffffff81059
[ 13.158082] [<ffffffff810e1
[ 13.158087] [<ffffffff810dd
[ 13.158093] [<ffffffff810e2
[ 13.158098] [<ffffffff8172c
[ 13.158101] ---[ end trace 5b57c64d53011e99 ]---
[Additional Information]
Base Image: somerville-
Kernel Version: 3.13.0-32-generic
CPU: Genuine Intel(R) CPU 0000 @ 1.60GHz
GPU: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 06)
description: | updated |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Trusty): | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in hwe-next: | |
status: | New → Fix Released |
assignee: | nobody → Robert Hooker (sarvatt) |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1351014
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.