Bug 1079667

Summary: unknown cause random crashes on the same system
Product: [Fedora] Fedora Reporter: Arnaud Lacombe <lacombar>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, sgruszka
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a36bb9f2df31467ce085105e943bc5ccc8a250af
Whiteboard: abrt_hash:d0aa6e681a3c7280bea663376a49d283b64fc72c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-23 14:40:36 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:
Attachments:
Description Flags
File: dmesg none

Description Arnaud Lacombe 2014-03-22 19:46:10 UTC 
Additional info:
reporter:       libreport-2.1.12
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff8132bcf1>] __list_del_entry+0x31/0xd0
PGD 0 
Oops: 0000 [#1] SMP 
Modules linked in: usb_storage tun udp_diag tcp_diag inet_diag rfcomm ipt_MASQUERADE xt_CHECKSUM ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth rfkill 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 dm_crypt vfat fat x86_pkg_temp_thermal coretemp kvm_intel snd_hda_codec_realtek snd_hda_codec_hdmi kvm snd_hda_intel snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hwdep crc32c_intel snd_seq snd_seq_device ghash_clmulni_intel joydev iTCO_wdt snd_pcm iTCO_vendor_support ppdev r8169 microcode snd_page_alloc mxm_wmi serio_raw i2c_i801 snd_timer mii snd lpc_ich mei_me soundcore shpchp mei mfd_core parport_pc parport wmi uinput binfmt_misc i915 i2c_algo_bit drm_kms_helper drm i2c_core video
CPU: 5 PID: 3795 Comm: qemu-system-x86 Not tainted 3.13.6-100.fc19.x86_64 #1
Hardware name: MSI MS-7850/Z87-G41 PC Mate(MS-7850), BIOS V1.2 06/07/2013
task: ffff88040660dee0 ti: ffff88007b6e2000 task.ti: ffff88007b6e2000
RIP: 0010:[<ffffffff8132bcf1>]  [<ffffffff8132bcf1>] __list_del_entry+0x31/0xd0
RSP: 0018:ffff88007b6e3f28  EFLAGS: 00010046
RAX: ffff8800ab2e2ae8 RBX: ffff8800d773c000 RCX: dead000000200200
RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff8800d773c000
RBP: ffff88007b6e3f28 R08: ffff8800d773c000 R09: 00007f7cd35a97d8
R10: 00007fffd8e1dd20 R11: 0000000000000202 R12: ffff88040660dee0
R13: ffffffff81c515c0 R14: ffffffff81c45800 R15: 00007f7cdabdc3b8
FS:  00007f7cda05ba40(0000) GS:ffff88041fb40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000008 CR3: 0000000061b85000 CR4: 00000000001427e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Stack:
 ffff88007b6e3f40 ffffffff8132bd9d ffff8800d773c000 ffff88007b6e3f78
 ffffffff8108e7d8 0000000000000246 00007f7cdc970770 0000000000000001
 00007f7cdc9532c0 00007f7cdabe03c0 00007f7cd35a96e8 ffffffff8168f969
Call Trace:
 [<ffffffff8132bd9d>] list_del+0xd/0x30
 [<ffffffff8108e7d8>] SyS_timer_delete+0xc8/0x160
 [<ffffffff8168f969>] system_call_fastpath+0x16/0x1b
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 
RIP  [<ffffffff8132bcf1>] __list_del_entry+0x31/0xd0
 RSP <ffff88007b6e3f28>
CR2: 0000000000000008
Comment 1 Arnaud Lacombe 2014-03-22 19:46:16 UTC 
Created attachment 877661 [details]
File: dmesg
Comment 2 Stanislaw Gruszka 2014-03-28 10:05:05 UTC 
It does not look like bug on SyS_timer_delete, but rather a some kind of memory corruption. 

Please install kernel-debug and run it for some time. That kernel variant include various debug facilities, which perhaps will help to identify problem on your system.
Comment 3 Stanislaw Gruszka 2014-03-28 10:07:52 UTC 
*** Bug 1076882 has been marked as a duplicate of this bug. ***
Comment 4 Stanislaw Gruszka 2014-03-28 10:11:20 UTC 
*** Bug 1059497 has been marked as a duplicate of this bug. ***
Comment 5 Stanislaw Gruszka 2014-03-28 10:11:27 UTC 
*** Bug 1060584 has been marked as a duplicate of this bug. ***
Comment 6 Stanislaw Gruszka 2014-03-28 10:11:41 UTC 
*** Bug 1073229 has been marked as a duplicate of this bug. ***
Comment 7 Stanislaw Gruszka 2014-03-28 10:11:53 UTC 
*** Bug 1076329 has been marked as a duplicate of this bug. ***
Comment 8 Stanislaw Gruszka 2014-03-28 10:12:13 UTC 
*** Bug 1079865 has been marked as a duplicate of this bug. ***
Comment 9 Stanislaw Gruszka 2014-03-28 10:13:28 UTC 
*** Bug 1073156 has been marked as a duplicate of this bug. ***
Comment 10 Stanislaw Gruszka 2014-03-28 10:18:15 UTC 
*** Bug 1067141 has been marked as a duplicate of this bug. ***
Comment 11 Arnaud Lacombe 2014-04-01 01:37:54 UTC 
I've been running the following:

% uname -a
Linux hanoli 3.13.7-100.fc19.x86_64.debug #1 SMP Mon Mar 24 21:37:36 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

For 3 days, and nothing has happened so far. I will update this issue when something will happen.
Comment 12 Justin M. Forbes 2014-05-21 19:29:59 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.14.4-100.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 13 Justin M. Forbes 2014-06-23 14:40:36 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.