Bug 862080

Summary:	[abrt]: BUG: unable to handle kernel paging request at ffff88007bc71fd8
Product:	[Fedora] Fedora	Reporter:	Jan Lippert <lippertsjan>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	eharney, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, rabdulatipoff, sgruszka, steven
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:b6c5d2e1c369f9386600ab4f243d1601e4c3f68e
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-17 16:45:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Lippert 2012-10-01 19:44:57 UTC

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
cmdline:        BOOT_IMAGE=/vmlinuz-3.5.4-1.fc17.x86_64 root=/dev/mapper/vg_mini--jan-lv_root ro rd.md=0 rd.luks.uuid=luks-4cdc211d-53b2-4b53-b050-6bf7ab290bd3 rd.dm=0 rd.lvm.lv=vg_mini-jan/lv_swap rd.lvm.lv=vg_mini-jan/lv_root KEYTABLE=de-latin1-nodeadkeys SYSFONT=True LANG=en_US.UTF-8 rhgb quiet
kernel:         3.5.4-1.fc17.x86_64

backtrace:
:BUG: unable to handle kernel paging request at ffff88007bc71fd8
:IP: [<ffff88007bc71fd8>] 0xffff88007bc71fd7
:PGD 1c0c063 PUD 1fc02067 PMD 800000007bc001e3 
:Oops: 0011 [#1] SMP 
:CPU 1 Modules linked in: fuse bnep bluetooth ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_state ip6_tables nf_conntrack binfmt_misc acer_wmi sparse_keymap coretemp microcode uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media arc4 ath9k i2c_i801 ath9k_common lpc_ich mfd_core ath9k_hw ath snd_hda_codec_realtek mac80211 cfg80211 snd_hda_intel snd_hda_codec<6>[11336.340551] Enabling non-boot CPUs ...
: snd_hwdep rfkill snd_seq snd_seq_device snd_pcm snd_page_alloc atl1c snd_timer snd soundcore uinput xts gf128mul dm_crypt wmi i915 video i2c_algo_bit drm_kms_helper drm i2c_core [last unloaded: scsi_wait_scan]
:Pid: 0, comm: swapper/1 Not tainted 3.5.4-1.fc17.x86_64 #1 Acer             AOD255          /AOD255          
:RIP: 0010:[<ffff88007bc71fd8>]  [<ffff88007bc71fd8>] 0xffff88007bc71fd7
:RSP: 0018:ffff88007bc71ef0  EFLAGS: 00010002
:RAX: 0000000000000001 RBX: ffff88007bc70010 RCX: 0000000000000000
:RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
:RBP: ffff88007bc71ef8 R08: ffff88007bc70000 R09: ffff88007bc71ed0
:R10: ffff88007bc71ed4 R11: 0000000000000000 R12: 0000000000000031
:R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
:FS:  0000000000000000(0000) GS:ffff88007f280000(0000) knlGS:0000000000000000
:CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
:CR2: ffff88007bc71fd8 CR3: 0000000001c0b000 CR4: 00000000000007e0
:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
:Process swapper/1 (pid: 0, threadinfo ffff88007bc70000, task ffff88007bc02e20)
:Stack:
: ffffffff81cd83b0 ffff88007bc71f28 ffffffff8101c5b8 ffff88007bc71f18
: 86067dc99b52e9b8 0000000000000000 0000000000000000 ffff88007bc71f48
: ffffffff815fb565 0000118420020400 a278271bb3a7b8cc 0000000000000000
:Call Trace:
: [<ffffffff8101c5b8>] cpu_idle+0x108/0x120
: [<ffffffff815fb565>] start_secondary+0x248/0x24a
:Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
:RIP  [<ffff88007bc71fd8>] 0xffff88007bc71fd7
: RSP <ffff88007bc71ef0>
:CR2: ffff88007bc71fd8

Comment 1 Stanislaw Gruszka 2012-10-05 12:31:53 UTC

This looks like some kind corruption, is not possible from above calltrace tell where where exactly the problem is. Please install kernel-debug and try to reproduce this issue, then more informative messages should be printed in dmesg.

Comment 2 Jan Lippert 2012-10-08 12:22:14 UTC

I don't think that I'll be able to reproduce this problem. But I installed kernel-debug for later reports.

Comment 3 Stanislaw Gruszka 2012-12-17 16:45:12 UTC

Ok, I assume this is fixed. Please reopen if not.

Comment 4 Rustam 2012-12-24 02:44:49 UTC

For me it happened on Fedora 17 with 3.6.10 tuxonice kernel. While hibernating, tuxonice fbsplash displayed "writing kernel data" and then was panic. If you run /sbin/tuxoniceui --test, something happens to VRAM and I see the screen corruption