During normal operation about once per 30min my screen only shows horizontal lines. After about 10sec I can continue to use the system normally.. The bug does not occur when I choose older kernel (3.19.8-031908-generic) with grub. my hardware (yes, quite old..) LG R400-EPRAG running Kubuntu 15.10 with kernel: 4.2.0-16-generic except from syslog: Nov 5 11:34:09 trage-kubuntu-R400-EPRAG smartd[709]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 62 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.000067] [drm] stuck on render ring Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001344] [drm] GPU HANG: ecode 3:0:0x0271ffc0, in Xorg [1249], reason: Ring hung, action: reset Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001434] ------------[ cut here ]------------ Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001479] WARNING: CPU: 1 PID: 13646 at /build/linux-hXawIp/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:3294 intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915]() Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001482] WARN_ON(ret) Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001484] Modules linked in: nls_iso8859_1 hid_generic usbhid hid drbg ansi_cprng ctr ccm nvram msr pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc arc4 ath5k snd_hda_codec_hdmi input_leds ath pcspkr joydev mac80211 snd_hda_codec_realtek serio_raw snd_hda_codec_generic cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device shpchp snd_timer snd soundcore mac_hid coretemp parport_pc ppdev lp parport autofs4 uas usb_storage i915 ahci psmouse i2c_algo_bit libahci pata_acpi drm_kms_helper drm sky2 wmi video Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001550] CPU: 1 PID: 13646 Comm: kworker/u4:0 Tainted: G W OE 4.2.0-16-generic #19-Ubuntu Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001553] Hardware name: LG Electronics R400-EPRAG/LHOTSE , BIOS LHONSF04 03/22/2007 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001578] Workqueue: i915-hangcheck i915_hangcheck_elapsed [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001582] c1a629a7 4ff65f30 00000000 d048bd48 c175dae1 d048bd88 d048bd78 c106a687 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001589] f8bd78e9 d048bda8 0000354e f8bc9a44 00000cde f8b6c22c f8b6c22c f5410000 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001595] c006fc34 00000001 d048bd94 c106a6fe 00000009 d048bd88 f8bd78e9 d048bda8 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001602] Call Trace: Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001610] [<c175dae1>] dump_stack+0x41/0x52 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001616] [<c106a687>] warn_slowpath_common+0x87/0xc0 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001643] [<f8b6c22c>] ? intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001671] [<f8b6c22c>] ? intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001674] [<c106a6fe>] warn_slowpath_fmt+0x3e/0x60 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001701] [<f8b6c22c>] intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001730] [<f891ffd4>] ? drm_modeset_lock_all_crtcs+0x84/0x90 [drm] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001757] [<f8b6d5f4>] intel_crtc_disable_planes+0x34/0xf0 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001784] [<f8b6d75a>] intel_prepare_reset+0x6a/0x80 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001810] [<f8b3f7b7>] i915_handle_error+0x147/0x6e0 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001815] [<c10be1bd>] ? log_store+0x1cd/0x210 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001820] [<c10bfa91>] ? vprintk_default+0x41/0x60 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001843] [<f8b3ffd3>] i915_hangcheck_elapsed+0x233/0x410 [i915] Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001849] [<c10810b5>] process_one_work+0x155/0x3e0 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001852] [<c1081377>] worker_thread+0x37/0x490 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001855] [<c1081340>] ? process_one_work+0x3e0/0x3e0 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001859] [<c1086a56>] kthread+0xa6/0xc0 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001864] [<c1763741>] ret_from_kernel_thread+0x21/0x30 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001868] [<c10869b0>] ? kthread_create_on_node+0x170/0x170 Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.001871] ---[ end trace a79e4baed554a835 ]--- Nov 5 11:38:36 trage-kubuntu-R400-EPRAG kernel: [33458.041241] drm/i915: Resetting chip after gpu hang
Created attachment 119443 [details] syslog
Created attachment 119458 [details] gpu-crash-dump GPU crash dump from /sys/class/drm/card0/error
Hi, the bug does not occur anymore with updated ubuntu-kernel-version: 4.2.0-18-generic
Created attachment 120100 [details] syslog with 4.2.0-18-generic
sorry, the bug does still occur, only less often. Appr. once every 4 hours. I have attached some fresh logfiles. uname gives the following output: Linux kubuntu-R400-EPRAG 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 23:32:28 UTC 2015 i686 i686 i686 GNU/Linux
Created attachment 120101 [details] gpu-crash-dump with 4.2.0-18-generic
Created attachment 120102 [details] dmesg with 4.2.0-18-generic
Normally the bug recovers after about 10 sec without any actions needed. But a few days ago, my Computer made a reboot!
Created attachment 120334 [details] complete dmesg I have read, the complete dmesg-output from boot is better, so I have added this from a new crash today... The according gpu-crash-dump-file will follow
Created attachment 120335 [details] gpu-crash-dump
(In reply to Leon from comment #10) > Created attachment 120335 [details] > gpu-crash-dump We seem to have neglected the bug a bit, apologies. There were improvements pushed in kernel (after yours : 4.2.0-19-generic) and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.
Hi Yann, I have updated and am using kubuntu 4.4.0-38-generic now. It seems to be working fine. Thanks!
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.