Bug 891389 - Kernel oops, trigerred by intel i915 on an Asus P8Z77-V
Summary: Kernel oops, trigerred by intel i915 on an Asus P8Z77-V
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-02 19:27 UTC by George B. Magklaras
Modified: 2013-07-31 18:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-31 18:08:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Compressed abrt-oops fir tarball (21.52 KB, application/x-gzip)
2013-01-02 19:27 UTC, George B. Magklaras
no flags Details

Description George B. Magklaras 2013-01-02 19:27:51 UTC
Created attachment 671633 [details]
Compressed abrt-oops fir tarball

Description of problem:
kernel oops - system needs a hardware reset to recover.

Version-Release number of selected component (if applicable):
[root@strider oops-2013-01-02-18:50:06-3717-1]# uname -a
Linux strider.internal.biotek 3.6.10-2.fc17.x86_64 #1 SMP Tue Dec 11 18:07:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

The system is wearing an onboard i915 card:
lspci -vv

00:02.0 VGA compatible controller: Intel Corporation Device 0162 (rev 09) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 84ca
	Flags: bus master, fast devsel, latency 0, IRQ 54
	Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915


How reproducible:
Consistently reproducible

Steps to Reproduce:
1. Boot the system with X enabled
2. Use the system VGA adapter intensively by launching OpnGL apps (glxgears, playing Flash content in 1080p and doing a lot of disk I/O in the background) 
3. System produces a blank screen, keyboard unresponsive, perform hardware reset
  
Actual results:
System crashes

Expected results:
I expect the system not to crash.

Additional info:
1)System is wearing the latest BIOS/Firmware and works perfectly with Windows :-(, so hardware problems are ruled out. 
2)I attach the gzip-ed tarball of the abrt-oops dir with backtrace info.

GM

Comment 1 Josh Boyer 2013-01-03 13:30:19 UTC
general protection fault: 0000 [#1] SMP 
Modules linked in: fuse bnep bluetooth nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables xfs snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support eeepc_wmi asus_wmi sparse_keymap coretemp kvm arc4 microcode i2c_i801 serio_raw ath9k ath9k_common ath9k_hw ath snd_hda_intel lpc_ich mac80211 mfd_core snd_hda_codec snd_hwdep snd_seq snd_seq_device cfg80211 snd_pcm rfkill e1000e uinput snd_page_alloc snd_timer snd mei soundcore crc32c_intel ghash_clmulni_intel mxm_wmi wmi i915 video i2c_algo_bit drm_kms_helper drm i2c_core
CPU 1 
Pid: 798, comm: Xorg Not tainted 3.6.10-2.fc17.x86_64 #1 System manufacturer System Product Name/P8Z77-V
RIP: 0010:[<ffffffff812f6ab0>]  [<ffffffff812f6ab0>] swiotlb_unmap_sg_attrs+0x30/0x70
RSP: 0018:ffff8803f9125c18  EFLAGS: 00010202
RAX: ffffffff812f6a80 RBX: fffb880404832e00 RCX: 0000000000000000
RDX: 0000000000000004 RSI: fffb880404832e00 RDI: ffff8804094e5098
RBP: ffff8803f9125c48 R08: 0000000000000000 R09: 000000003681f005
R10: 0000000000000000 R11: 000000000000003d R12: 0000000000000000
R13: 0000000000000004 R14: 0000000000000000 R15: ffff8804094e5098
FS:  00007f1d314e88c0(0000) GS:ffff88041fa40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001a9dd18 CR3: 00000003fb2d2000 CR4: 00000000001407e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process Xorg (pid: 798, threadinfo ffff8803f9124000, task ffff880408699710)
Stack:
 ffff8803f9125cf0 0000000000000004 fffb880404832e00 0000000000000001
 ffff880404c93000 ffff880404c93000 ffff8803f9125c78 ffffffff813b92f9
 ffff8803eb332200 0000000000000001 ffff8803eb332200 ffff880404aa8000
Call Trace:
 [<ffffffff813b92f9>] intel_gtt_unmap_memory+0x49/0x80
 [<ffffffffa008b265>] i915_gem_gtt_finish_object+0x55/0xc0 [i915]
 [<ffffffffa0084310>] i915_gem_object_unbind+0xc0/0x200 [i915]
 [<ffffffff812de99f>] ? prio_tree_remove+0xaf/0xf0
 [<ffffffffa0086d13>] i915_gem_free_object+0x63/0x140 [i915]
 [<ffffffffa001687a>] drm_gem_object_free+0x2a/0x30 [drm]
 [<ffffffffa0016f20>] drm_gem_handle_delete+0xf0/0x120 [drm]
 [<ffffffffa0017368>] drm_gem_close_ioctl+0x28/0x30 [drm]
 [<ffffffffa00153c3>] drm_ioctl+0x4d3/0x580 [drm]
 [<ffffffffa0017340>] ? drm_gem_destroy+0x60/0x60 [drm]
 [<ffffffff8117ac79>] ? kfree+0x139/0x160
 [<ffffffff811a2289>] do_vfs_ioctl+0x99/0x580
 [<ffffffff81282f3a>] ? inode_has_perm.isra.31.constprop.61+0x2a/0x30
 [<ffffffff81284367>] ? file_has_perm+0x97/0xb0
 [<ffffffff811a2809>] sys_ioctl+0x99/0xa0
 [<ffffffff816270e9>] system_call_fastpath+0x16/0x1b
Code: 57 41 56 41 89 ce 41 55 41 54 53 48 83 ec 08 83 f9 03 74 4c 45 31 e4 85 d2 49 89 ff 41 89 d5 48 89 f3 7e 2d 0f 1f 80 00 00 00 00 <8b> 53 18 48 8b 73 10 44 89 f1 4c 89 ff 41 83 c4 01 e8 4a ff ff 
RIP  [<ffffffff812f6ab0>] swiotlb_unmap_sg_attrs+0x30/0x70
 RSP <ffff8803f9125c18>

Comment 2 Fedora End Of Life 2013-07-03 19:31:56 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2013-07-31 18:08:08 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.