Bug 85407 - driver keeps crashin with kwin in plasma 5.1
Summary: driver keeps crashin with kwin in plasma 5.1
Status: RESOLVED DUPLICATE of bug 85389
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium critical
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-24 14:54 UTC by Paulo Dias
Modified: 2014-10-24 15:12 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error dump (66.61 KB, text/plain)
2014-10-24 14:55 UTC, Paulo Dias
no flags Details

Description Paulo Dias 2014-10-24 14:54:32 UTC
the driver is very unstable with kde plasma 5.1

[ 3541.843554] ------------[ cut here ]------------
[ 3541.843618] WARNING: CPU: 1 PID: 5812 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3486 gen6_enable_rps_interrupts+0xa3/0xb0 [i915]()
[ 3541.843622] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rtsx_usb_ms memstick dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common dell_laptop videodev dcdbas ath3k btusb media intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dm_multipath crct10dif_pclmul scsi_dh crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd rtc_efi joydev serio_raw lpc_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event arc4 snd_rawmidi ath9k bnep ath9k_common ath9k_hw rfcomm snd_seq bluetooth ath mac80211 snd_seq_device snd_timer snd cfg80211 soundcore mei_me mei shpchp soc_button_array
[ 3541.843730]  mac_hid eeprom binfmt_misc nls_iso8859_1 parport_pc ppdev lp parport btrfs xor raid6_pq dm_mirror dm_region_hash dm_log rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid radeon i915 psmouse ttm i2c_algo_bit ahci drm_kms_helper libahci drm r8169 mii wmi video
[ 3541.843784] CPU: 1 PID: 5812 Comm: kworker/1:0 Tainted: G           OE  3.17.0-031700-generic #201410051635
[ 3541.843789] Hardware name: Dell Inc. Latitude 3540/02R0J9, BIOS A08 07/17/2014
[ 3541.843824] Workqueue: events intel_gen6_powersave_work [i915]
[ 3541.843829]  0000000000000d9e ffff880156ab7d08 ffffffff82796bd7 0000000000000007
[ 3541.843838]  0000000000000000 ffff880156ab7d48 ffffffff82074a3c ffff880035dad800
[ 3541.843846]  ffff880035f80000 ffff880035f87180 0000000000040000 ffff880035f80000
[ 3541.843855] Call Trace:
[ 3541.843869]  [<ffffffff82796bd7>] dump_stack+0x46/0x58
[ 3541.843879]  [<ffffffff82074a3c>] warn_slowpath_common+0x8c/0xc0
[ 3541.843887]  [<ffffffff82074a8a>] warn_slowpath_null+0x1a/0x20
[ 3541.843921]  [<ffffffffc02ba543>] gen6_enable_rps_interrupts+0xa3/0xb0 [i915]
[ 3541.843957]  [<ffffffffc02bf349>] gen6_enable_rps+0x339/0x500 [i915]
[ 3541.843993]  [<ffffffffc02c0b0b>] intel_gen6_powersave_work+0x6b/0xc0 [i915]
[ 3541.844003]  [<ffffffff8208ce2e>] process_one_work+0x14e/0x460
[ 3541.844012]  [<ffffffff8208d7ab>] worker_thread+0x11b/0x3f0
[ 3541.844021]  [<ffffffff8208d690>] ? create_worker+0x1e0/0x1e0
[ 3541.844028]  [<ffffffff820932b9>] kthread+0xc9/0xe0
[ 3541.844037]  [<ffffffff820931f0>] ? flush_kthread_worker+0x90/0x90
[ 3541.844045]  [<ffffffff827a467c>] ret_from_fork+0x7c/0xb0
[ 3541.844052]  [<ffffffff820931f0>] ? flush_kthread_worker+0x90/0x90
[ 3541.844058] ---[ end trace b74f982fbde47364 ]---
[ 6402.227369] [drm] stuck on render ring
[ 6402.228305] [drm] GPU HANG: ecode 0:0x85dffffd, in Xorg [1510], reason: Ring hung, action: reset
[ 6444.240013] [drm] stuck on render ring
[ 6444.241446] [drm] GPU HANG: ecode 0:0x85dffffd, in Xorg [1510], reason: Ring hung, action: reset
Comment 1 Paulo Dias 2014-10-24 14:55:54 UTC
Created attachment 108356 [details]
/sys/class/drm/card0/error dump
Comment 2 Chris Wilson 2014-10-24 15:12:09 UTC

*** This bug has been marked as a duplicate of bug 85389 ***


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.