Created attachment 122018 [details] gpu crash dump Ubuntu 15.10, Intel Atom N280, Intel 945GME integrated graphics. On occasion, the screen will appear to stop responding, although the cursor will still move. The screen then goes black, before coming back as a corrupted mess. The corruption appears as incoherent horizontal lines, and the screen appears to be comprised of multiple small tiles of the same image, as movement of the cursor or scrolling of the open application causes identical change in each tile. Pressing the Super (Windows) key causes the Ubuntu 'Start' (I forget what it's actually called) menu to display normally, and the corruption and tiling to resolve itself. Some corruption does remain in the applications display, although scrolling the content or otherwise modifying the window geometry does cause this to disappear. I have observed this happening in Midori, Firefox, Gnome Terminal, Geany, and likely other applications I cannot remember right now.
Output from dmesg after another one. [55812.000283] [drm] stuck on render ring [55812.006832] [drm] GPU HANG: ecode 3:0:0x6adfffc1, in Xorg [774], reason: Ring hung, action: reset [55812.009398] ------------[ cut here ]------------ [55812.009488] WARNING: CPU: 0 PID: 14534 at /build/linux-DW8ESA/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:3296 intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915]() [55812.009493] WARN_ON(ret) [55812.009498] Modules linked in: [55812.009503] bnep drbg ansi_cprng ctr ccm btusb btrtl btbcm btintel bluetooth snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec uvcvideo snd_hda_core videobuf2_vmalloc snd_hwdep videobuf2_memops videobuf2_core snd_pcm arc4 v4l2_common videodev snd_seq_midi snd_seq_midi_event media ath9k coretemp snd_rawmidi ath9k_common ath9k_hw snd_seq joydev input_leds ath serio_raw mac80211 lpc_ich cfg80211 snd_seq_device snd_timer snd soundcore shpchp toshiba_acpi sparse_keymap toshiba_haps wmi toshiba_bluetooth mac_hid parport_pc ppdev lp parport autofs4 i915 ahci psmouse libahci pata_acpi i2c_algo_bit drm_kms_helper drm r8169 mii video [55812.009671] CPU: 0 PID: 14534 Comm: kworker/u4:43 Not tainted 4.2.0-30-generic #35-Ubuntu [55812.009677] Hardware name: TOSHIBA TOSHIBA NB205/KAVAA, BIOS V1.70 09/30/2009 [55812.009743] Workqueue: i915-hangcheck i915_hangcheck_elapsed [i915] [55812.009750] c1a689a7 a5c50c8a 00000000 c6073d48 c1760bfb c6073d88 c6073d78 c106ad97 [55812.009767] f8a4a97d c6073da8 000038c6 f8a3ca90 00000ce0 f89df1ec f89df1ec f5d50000 [55812.009783] c01b2434 00000001 c6073d94 c106ae0e 00000009 c6073d88 f8a4a97d c6073da8 [55812.009799] Call Trace: [55812.009813] [<c1760bfb>] dump_stack+0x41/0x52 [55812.009824] [<c106ad97>] warn_slowpath_common+0x87/0xc0 [55812.009896] [<f89df1ec>] ? intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] [55812.009966] [<f89df1ec>] ? intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] [55812.009977] [<c106ae0e>] warn_slowpath_fmt+0x3e/0x60 [55812.010047] [<f89df1ec>] intel_crtc_wait_for_pending_flips+0x17c/0x220 [i915] [55812.010100] [<f8800094>] ? drm_modeset_lock_all_crtcs+0x84/0x90 [drm] [55812.010175] [<f89e05b4>] intel_crtc_disable_planes+0x34/0xf0 [i915] [55812.010251] [<f89e071a>] intel_prepare_reset+0x6a/0x80 [i915] [55812.010321] [<f89b2947>] i915_handle_error+0x147/0x6e0 [i915] [55812.010343] [<c10c0251>] ? vprintk_default+0x41/0x60 [55812.010410] [<f89b3163>] i915_hangcheck_elapsed+0x233/0x410 [i915] [55812.010427] [<c1081825>] process_one_work+0x155/0x3e0 [55812.010439] [<c1081ae7>] worker_thread+0x37/0x490 [55812.010448] [<c1081ab0>] ? process_one_work+0x3e0/0x3e0 [55812.010456] [<c10871a6>] kthread+0xa6/0xc0 [55812.010468] [<c1766881>] ret_from_kernel_thread+0x21/0x30 [55812.010477] [<c1087100>] ? kthread_create_on_node+0x170/0x170 [55812.010486] ---[ end trace 1a8a7f8a2fb381ad ]--- [55812.054863] drm/i915: Resetting chip after gpu hang
*** This bug has been marked as a duplicate of bug 90841 ***
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.