WARNING: CPU: 1 PID: 207 at /build/linux-lts-vivid-3x86XO/linux-lts-vivid-3.19.0/drivers/gpu/drm/i915/intel_display.c:958

Bug #1479321 reported by CB on 2015-07-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Every now and than my desktop freezes for a couple of minutes. I can move the mouse pointer but it gets stuck in a single display (I have two).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
Uname: Linux 3.16.0-45-generic x86_64

ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jul 29 08:38:07 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
 virtualbox, 4.3.10, 3.16.0-43-generic, x86_64: installed
 virtualbox, 4.3.10, 3.16.0-45-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:339a]
InstallationDate: Installed on 2015-04-10 (109 days ago)
InstallationMedia: It
MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-45-generic root=UUID=88d8ecda-fb83-4942-83db-bbb2ee83be80 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: BRJ40510V4
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: BRJ40510V4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq Pro 6300 MT
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jul 29 08:19:44 2015
xserver.configfile: default
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input CHICONY HP Basic USB Keyboard KEYBOARD, id 8
 input PixArt USB Optical Mouse MOUSE, id 9
 input HP WMI hotkeys KEYBOARD, id 10

xserver.logfile: /var/log/Xorg.0.log
 product id 12387
 vendor HWP
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

CB (cbrchrt) wrote :
tags: added: bios-outdated-2.98
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
CB (cbrchrt) wrote :
Download full text (4.9 KiB)

Hi Christopher,

Sometime ago, after I reported this bug, I had already updated my BIOS to 2.98:

~ $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
K01 v02.98

Since then I've got less video issues, but I cannot tell if they were fixed by the BIOS update or by some other update like the new kernel I have now (3.19).

Those 1-2 minutes freezes definitely have stopped or at least they are not so frequent. But sometimes my Unity still freezes for a few seconds like the first time when I press the Super key to bring up the Dash Home screen or when I run apt-get install and it starts configuring some package. I don't know if they are related. And also I am still seeing i915 crashes and errors in dmesg:

[ 10.132760] WARNING! power/level is deprecated; use power/control instead
[ 10.287641] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to update link training
[ 10.300577] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to update link training
[ 10.327787] usbcore: registered new interface driver snd-usb-audio
[ 10.449263] ------------[ cut here ]------------
[ 10.449288] WARNING: CPU: 1 PID: 207 at /build/linux-lts-vivid-3x86XO/linux-lts-vivid-3.19.0/drivers/gpu/drm/i915/intel_display.c:958 intel_disable_pipe+0x2b6/0x2c0 [i91
[ 10.449289] pipe_off wait timed out
[ 10.449290] Modules linked in: x86_pkg_temp_thermal intel_powerclamp snd_usb_audio kvm_intel snd_usbmidi_lib snd_hda_codec_hdmi hp_wmi snd_hda_codec_realtek snd_hda_code
[ 10.449312] CPU: 1 PID: 207 Comm: plymouthd Not tainted 3.19.0-28-generic #30~14.04.1-Ubuntu
[ 10.449313] Hardware name: Hewlett-Packard HP Compaq Pro 6300 MT/339A, BIOS K01 v02.98 03/18/2015
[ 10.449314] ffffffffc075f6c8 ffff8802145c3a98 ffffffff817aed97 0000000000002f5c
[ 10.449316] ffff8802145c3ae8 ffff8802145c3ad8 ffffffff81074d8a 00000000fffee53b
[ 10.449317] ffff8800d99f0000 0000000000071008 00000000fffee539 0000000000000001
[ 10.449319] Call Trace:
[ 10.449324] [<ffffffff817aed97>] dump_stack+0x45/0x57
[ 10.449326] [<ffffffff81074d8a>] warn_slowpath_common+0x8a/0xc0
[ 10.449328] [<ffffffff81074e06>] warn_slowpath_fmt+0x46/0x50
[ 10.449338] [<ffffffffc06fe126>] intel_disable_pipe+0x2b6/0x2c0 [i915]
[ 10.449348] [<ffffffffc0704d6d>] ironlake_crtc_disable+0xad/0x7c0 [i915]
[ 10.449358] [<ffffffffc0706439>] __intel_set_mode+0xa49/0xc60 [i915]
[ 10.449367] [<ffffffffc070cbb2>] intel_crtc_set_config+0x9e2/0xf60 [i915]
[ 10.449377] [<ffffffffc056783f>] drm_mode_set_config_internal+0x6f/0x110 [drm]
[ 10.449381] [<ffffffffc068a598>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper]
[ 10.449385] [<ffffffffc068c4b9>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper]
[ 10.449395] [<ffffffffc071a22e>] intel_fbdev_restore_mode+0x1e/0x50 [i915]
[ 10.449406] [<ffffffffc073e88e>] i915_driver_lastclose+0xe/0x20 [i915]
[ 10.449411] [<ffffffffc055ac4e>] drm_lastclose+0x2e/0x130 [drm]
[ 10.449415] [<ffffffffc055b088>] drm_release+0x338/0x540 [drm]
[ 10.449418] [<ffffffff811edf77>] __fput+0xe7/0x220 ...


CB, given you are experiencing a kernel crash in a graphics driver, this would be the cause of your displays freezes.

Hence, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

summary: - Xorg freeze
+ WARNING: CPU: 1 PID: 207 at /build/linux-lts-vivid-3x86XO/linux-lts-
+ vivid-3.19.0/drivers/gpu/drm/i915/intel_display.c:958
Changed in xorg (Ubuntu):
importance: Low → Medium
affects: xorg (Ubuntu) → linux (Ubuntu)
CB (cbrchrt) wrote :
Download full text (4.7 KiB)

I just booted with 4.3.0-040300rc2-generic and there is still one kernel crash and some i915 errors:

[ 12.072417] ------------[ cut here ]------------
[ 12.072443] WARNING: CPU: 2 PID: 173 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1056 intel_disable_pipe+0x2a2/0x2d0 [i915]()
[ 12.072444] pipe_off wait timed out
[ 12.072462] Modules linked in: crct10dif_pclmul nf_conntrack crc32_pclmul ghash_clmulni_intel iptable_filter ip_tables aesni_intel x_tables aes_x86_64 hp_wmi lrw gf128mul sparse_keymap glue_helper ablk_helper cryptd snd_hda_intel(+) snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi i915(+) snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ppdev coretemp snd_timer drm_kms_helper snd drm soundcore lp parport_pc serio_raw wmi 8250_fintek ie31200_edac input_leds parport i2c_algo_bit lpc_ich tpm_infineon fb_sys_fops mei_me syscopyarea sysfillrect sysimgblt video mei mac_hid edac_core hid_generic usbhid hid psmouse e1000e ahci r8169 libahci ptp mii pps_core fjes
[ 12.072463] CPU: 2 PID: 173 Comm: kworker/u8:5 Not tainted 4.3.0-040300rc2-generic #201509201830
[ 12.072464] Hardware name: Hewlett-Packard HP Compaq Pro 6300 MT/339A, BIOS K01 v02.98 03/18/2015
[ 12.072467] Workqueue: events_unbound async_run_entry_fn
[ 12.072469] ffffffffc037dd08 ffff88003640b830 ffffffff813a5f9d ffff88003640b878
[ 12.072470] ffff88003640b868 ffffffff8107a566 ffff88020d060000 0000000000071008
[ 12.072470] 00000000fffee6ce 0000000000071008 ffff880036b25000 ffff88003640b8c8
[ 12.072471] Call Trace:
[ 12.072476] [<ffffffff813a5f9d>] dump_stack+0x44/0x57
[ 12.072477] [<ffffffff8107a566>] warn_slowpath_common+0x86/0xc0
[ 12.072478] [<ffffffff8107a5ec>] warn_slowpath_fmt+0x4c/0x50
[ 12.072494] [<ffffffffc03159f2>] intel_disable_pipe+0x2a2/0x2d0 [i915]
[ 12.072509] [<ffffffffc0315d95>] ironlake_crtc_disable+0x85/0x7c0 [i915]
[ 12.072522] [<ffffffffc0310d7c>] ? intel_crtc_disable_planes+0xdc/0xf0 [i915]
[ 12.072535] [<ffffffffc031e6c5>] intel_atomic_commit+0xf5/0x5f0 [i915]
[ 12.072547] [<ffffffffc01aea69>] ? drm_atomic_get_connector_state+0x49/0x130 [drm]
[ 12.072554] [<ffffffffc01af1b7>] drm_atomic_commit+0x37/0x60 [drm]
[ 12.072559] [<ffffffffc02304be>] drm_atomic_helper_set_config+0x38e/0x400 [drm_kms_helper]
[ 12.072566] [<ffffffffc019ed74>] drm_mode_set_config_internal+0x64/0x100 [drm]
[ 12.072570] [<ffffffffc023309e>] restore_fbdev_mode+0xbe/0xe0 [drm_kms_helper]
[ 12.072573] [<ffffffffc0234e05>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
[ 12.072576] [<ffffffffc0234e7c>] drm_fb_helper_set_par+0x2c/0x50 [drm_kms_helper]
[ 12.072591] [<ffffffffc0332bea>] intel_fbdev_set_par+0x1a/0x60 [i915]
[ 12.072593] [<ffffffff8141d566>] fbcon_init+0x4c6/0x550
[ 12.072596] [<ffffffff814a7d4a>] visual_init+0xca/0x130
[ 12.072597] [<ffffffff814aa366>] do_bind_con_driver+0x146/0x310
[ 12.072598] [<ffffffff814aa851>] do_take_over_console+0x141/0x1b0
[ 12.072600] [<ffffffff81418767>] do_fbcon_takeover+0x57/0xb0
[ 12.072600] [<ffffffff8141df6b>] fbcon_event_notify+0x60b/0x750
[ 12.072602] [<ffffffff81099229>] notifier_call_chain+0x49/...


tags: added: kernel-bug-exists-upstream kernel-fixed-upstream-4.3-rc2
tags: added: kernel-bug-exists-upstream-4.3-rc2
removed: kernel-fixed-upstream-4.3-rc2
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

CB, did this problem not occur in a kernel series prior to 3.16?

tags: added: latest-bios-2.98
removed: bios-outdated-2.98
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
CB (cbrchrt) wrote :

If my memory doesn't fail me, it occurred since when I've got this machine and it had Ubuntu 14.04 or 14.04.1.

CB, the issue you are reporting is an upstream one. Could you please report this problem following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
CB (cbrchrt) wrote :

Hi Christopher, the steps are a little confusing for me. I've prepared the report according to the instructions from Ubuntu's Wiki, but looking at Intel's instructions it looks like they need other information. I will have to build and and redo the test using their nightly release. Is that so? In case yes, I will need a few to more days to be able to test it properly.

CB, binaries of intel-drm-nightly are already available via the mainline kernel support article, so you don't need to build anything:

CB (cbrchrt) wrote :
Download full text (5.3 KiB)

Still present in 4.3.3:

[ 9.819672] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 9.819721] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 9.819770] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 9.819819] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 9.819861] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 9.895263] ------------[ cut here ]------------
[ 9.895308] WARNING: CPU: 3 PID: 171 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1056 intel_disable_pipe+0x2b6/0x2c0 [i915]()
[ 9.895308] pipe_off wait timed out
[ 9.895339] Modules linked in: kvm_intel kvm snd_hda_codec_hdmi hp_wmi snd_hda_codec_realtek snd_hda_codec_generic sparse_keymap crct10dif_pclmul crc32_pclmul snd_hda_intel snd_hda_codec i915 snd_hda_core drm_kms_helper snd_hwdep aesni_intel snd_pcm aes_x86_64 lrw snd_seq_midi snd_seq_midi_event snd_rawmidi gf128mul glue_helper drm snd_seq ablk_helper snd_seq_device snd_timer cryptd snd i2c_algo_bit wmi fb_sys_fops syscopyarea sysfillrect ie31200_edac mei_me sysimgblt serio_raw soundcore mei edac_core lpc_ich tpm_infineon 8250_fintek mac_hid video parport_pc ppdev coretemp lp parport hid_generic usbhid hid psmouse e1000e ahci r8169 libahci ptp mii pps_core fjes
[ 9.895340] CPU: 3 PID: 171 Comm: kworker/u8:4 Not tainted 4.3.3-040303-generic #201512150130
[ 9.895341] Hardware name: Hewlett-Packard HP Compaq Pro 6300 MT/339A, BIOS K01 v02.98 03/18/2015
[ 9.895344] Workqueue: events_unbound async_run_entry_fn
[ 9.895346] 0000000000000000 00000000ffcb7bbf ffff8802125437e0 ffffffff813c2b24
[ 9.895347] ffff880212543828 ffff880212543818 ffffffff8107d152 ffff880213d30000
[ 9.895347] 0000000000071008 00000000fffee4ae 0000000000071008 ffff880213d9f000
[ 9.895348] Call Trace:
[ 9.895352] [<ffffffff813c2b24>] dump_stack+0x44/0x60
[ 9.895354] [<ffffffff8107d152>] warn_slowpath_common+0x82/0xc0
[ 9.895355] [<ffffffff8107d1ec>] warn_slowpath_fmt+0x5c/0x80
[ 9.895369] [<ffffffffc0386f66>] intel_disable_pipe+0x2b6/0x2c0 [i915]
[ 9.895379] [<ffffffffc03872e5>] ironlake_crtc_disable+0x85/0x7c0 [i915]
[ 9.895388] [<ffffffffc0382b2c>] ? intel_crtc_disable_planes+0xdc/0xf0 [i915]
[ 9.895400] [<ffffffffc03902a0>] intel_atomic_commit+0x110/0x670 [i915]
[ 9.895410] [<ffffffffc0219945>] ? drm_atomic_check_only+0x215/0x540 [drm]
[ 9.895417] [<ffffffffc0219ca7>] drm_atomic_commit+0x37/0x60 [drm]
[ 9.895421] [<ffffffffc02dcb3f>] drm_atomic_helper_set_config+0x1bf/0x420 [drm_kms_helper]
[ 9.895427] [<ffffffffc0209162>] drm_mode_set_config_internal+0x62/0x100 [drm]
[ 9.895430] [<ffffffffc02df9c3>] restore_fbdev_mode+0xb3/0x110 [drm_kms_helper]
[ 9.895433] [<ffffffffc02e18b5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
[ 9.895436] [<ffffffffc02e192d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
[ 9.895450] [<ffffffffc03a4fea>] intel_fbdev_set_par+0x1a/0x60 [i915]
[ 9.895452] [<ffffffff8143dc90>] fbco...


CB, if one wants to provide current results, one would test the latest mainline kernel 4.4-rc5 (not 4.3.x), and if still reproducible there drm-intel-nightly.

CB (cbrchrt) wrote :

It looks like it was finally fixed on 4.7.0-040700-generic. I've just upgraded and for the first time there aren't any call traces in my dmesg.

tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.7 needs-reverse-bisect
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.