Bug 80829 - general protection fault: 0000 [#1] SMP
Summary: general protection fault: 0000 [#1] SMP
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-02 20:27 UTC by mikhail.v.gavrilov
Modified: 2017-07-24 22:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
kernel log (124.78 KB, text/plain)
2014-07-02 20:27 UTC, mikhail.v.gavrilov
no flags Details
kernel log (246.81 KB, text/plain)
2014-07-15 17:36 UTC, mikhail.v.gavrilov
no flags Details
kernel log (237.29 KB, text/plain)
2014-07-21 15:33 UTC, mikhail.v.gavrilov
no flags Details

Description mikhail.v.gavrilov 2014-07-02 20:27:33 UTC
Created attachment 102158 [details]
kernel log

# uname -a
Linux localhost.localdomain 3.14.8-200.fc20.x86_64+debug #1 SMP Mon Jun 16 21:39:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


Description of problem:
[232538.886893] general protection fault: 0000 [#1] SMP 
[232538.886913] Modules linked in: rfcomm nls_utf8 isofs fuse ipt_MASQUERADE xt_CHECKSUM ip6t_rpfilter ip6t_REJECT xt_conntrack cfg80211 ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw tun bnep iTCO_wdt iTCO_vendor_support ppdev btrfs raid6_pq xor vfat fat x86_pkg_temp_thermal coretemp kvm_intel kvm btusb bluetooth crct10dif_pclmul crc32_pclmul 6lowpan_iphc crc32c_intel rfkill ghash_clmulni_intel microcode serio_raw snd_hda_codec_realtek snd_hda_codec_generic snd_emu10k1 snd_hda_codec_hdmi snd_util_mem i2c_i801 snd_rawmidi snd_hda_intel
[232538.887114]  snd_hda_codec snd_ac97_codec snd_hwdep ac97_bus snd_seq snd_seq_device emu10k1_gp gameport snd_pcm mei_me lpc_ich mfd_core snd_timer shpchp mei snd soundcore parport_pc parport hid_logitech_dj binfmt_misc nfsd auth_rpcgss nfs_acl lockd sunrpc usb_storage i915 firewire_ohci i2c_algo_bit firewire_core r8169 crc_itu_t drm_kms_helper mii drm i2c_core video
[232538.887212] CPU: 3 PID: 1059 Comm: Xorg Tainted: G        W    3.14.8-200.fc20.x86_64+debug #1
[232538.887231] Hardware name: Gigabyte Technology Co., Ltd. Z87M-D3H/Z87M-D3H, BIOS F10 04/09/2014
[232538.887250] task: ffff88003f322590 ti: ffff8807daf34000 task.ti: ffff8807daf34000
[232538.887266] RIP: 0010:[<ffffffff813e5a21>]  [<ffffffff813e5a21>] __list_del_entry+0x31/0xd0
[232538.887289] RSP: 0018:ffff8807daf35d10  EFLAGS: 00010246
[232538.887301] RAX: ffff88080d2b2cf0 RBX: ffff88080c596140 RCX: dead000000200200
[232538.887316] RDX: fff788080d2b2cf0 RSI: ffff880799ee9658 RDI: ffff88080c596268
[232538.887332] RBP: ffff8807daf35d10 R08: ffff88080c596268 R09: 0000000000000000
[232538.887347] R10: 0000000000000000 R11: ffff8807daf35e10 R12: ffff88080c596268
[232538.887363] R13: ffff88007cbd8718 R14: 0000000000c7f6f1 R15: ffff88080d2b2d00
[232538.887378] FS:  00007f5077b5d9c0(0000) GS:ffff88081f200000(0000) knlGS:0000000000000000
[232538.887396] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[232538.887408] CR2: 00007f183887b000 CR3: 00000007dbc9f000 CR4: 00000000001407e0
[232538.887424] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[232538.887439] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[232538.887454] Stack:
[232538.887460]  ffff8807daf35d38 ffffffffa00d1c27 ffff88080d2b2c00 ffff88080d2b2cf0
[232538.887479]  ffff88080d2b2d00 ffff8807daf35d80 ffffffffa00d31b5 ffff88080d2b2d00
[232538.887498]  ffff88077acbb480 0000000000000000 ffff88080d07c000 ffff88080c596300
[232538.887518] Call Trace:
[232538.887535]  [<ffffffffa00d1c27>] i915_gem_object_move_to_inactive+0xa7/0x140 [i915]
[232538.887557]  [<ffffffffa00d31b5>] i915_gem_retire_requests_ring+0xa5/0x1e0 [i915]
[232538.887580]  [<ffffffffa00d4c95>] i915_gem_busy_ioctl+0xd5/0xf0 [i915]
[232538.887600]  [<ffffffffa0021e82>] drm_ioctl+0x4f2/0x630 [drm]
[232538.887617]  [<ffffffff8135cae3>] ? inode_has_perm.isra.51+0x53/0x80
[232538.887632]  [<ffffffff8124c140>] do_vfs_ioctl+0x300/0x520
[232538.887645]  [<ffffffff81258255>] ? __fget+0x5/0x300
[232538.887658]  [<ffffffff8124c3e1>] SyS_ioctl+0x81/0xa0
[232538.887670]  [<ffffffff811578ec>] ? __audit_syscall_entry+0x9c/0xf0
[232538.887686]  [<ffffffff817eaca9>] system_call_fastpath+0x16/0x1b
[232538.887699] Code: 00 01 10 00 00 00 ad de 48 8b 47 08 48 89 e5 48 39 ca 74 29 48 b9 00 02 20 00 00 00 ad de 48 39 c8 74 7a 4c 8b 00 4c 39 c7 75 53 <4c> 8b 42 08 4c 39 c7 75 2b 48 89 42 08 48 89 10 5d c3 49 89 d0 
[232538.887785] RIP  [<ffffffff813e5a21>] __list_del_entry+0x31/0xd0
[232538.887800]  RSP <ffff8807daf35d10>
[232538.893184] ---[ end trace c62a95bce413089c ]---
Comment 1 Paulo Zanoni 2014-07-03 15:17:01 UTC
How often does this happen?

Do you have any reliable way to reproduce the problem?

Can you please boot with drm.debug=0xe, reproduce the problem, then attach the dmesg here?
Comment 2 mikhail.v.gavrilov 2014-07-14 16:33:45 UTC
I am afraid I don't know how reproduce this. Because this occurred once at night when I was not near a computer.

I can set drm.debug=0xe and wait next time ...
Comment 3 mikhail.v.gavrilov 2014-07-15 17:36:36 UTC
Created attachment 102865 [details]
kernel log
Comment 4 Chris Wilson 2014-07-19 10:03:51 UTC
That points towards more general corruption. Try i915.enable_fbc=0 for starters.
Comment 5 mikhail.v.gavrilov 2014-07-21 15:33:36 UTC
Created attachment 103198 [details]
kernel log
Comment 6 Chris Wilson 2014-07-21 16:18:56 UTC
There is nothing in that trace that indicates a i915.ko fault - first there is a locking bug in snd, then a slow ext4 write and a false positive report from the dmar debugger that doesn't until the cache coherency of the processor.
Comment 7 Rodrigo Vivi 2014-10-08 21:25:50 UTC
Feel free to reopen if you are sure this is i915 error.
In this case please try latest drm-intel-nightly.


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.