Bug 1071992

Summary: [abrt] general protection fault: 0000 [#1] SMP
Product: [Fedora] Fedora Reporter: Paul Finnigan <paul>
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: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/12152b1ac8eb00331351684653ae6952c6b43ba1
Whiteboard: abrt_hash:9e58977d27c90d480c771be4ffbe237ce4f78636
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-18 14:23:41 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 Paul Finnigan 2014-03-03 16:13:21 UTC 
Description of problem:
Problem happened during boot phase when my laptop was starting. Cannot reproduce.

Additional info:
reporter:       libreport-2.1.12
general protection fault: 0000 [#1] SMP 
Modules linked in: cfg80211 ssb mmc_core acer_wmi sparse_keymap rfkill uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media snd_hda_codec_hdmi kvm_amd kvm snd_hda_codec_realtek microcode joydev serio_raw snd_hda_intel k10temp edac_core edac_mce_amd snd_hda_codec snd_seq snd_hwdep snd_seq_device sp5100_tco i2c_piix4 broadcom snd_pcm tg3 ptp pps_core snd_page_alloc snd_timer snd soundcore bcma shpchp wmi video acpi_cpufreq nfsd auth_rpcgss nfs_acl binfmt_misc lockd sunrpc btrfs libcrc32c xor raid6_pq dm_crypt ata_generic pata_acpi radeon i2c_algo_bit drm_kms_helper ttm drm pata_atiixp i2c_core
CPU: 1 PID: 504 Comm: systemd-udevd Not tainted 3.13.5-200.fc20.x86_64 #1
Hardware name: Acer             Aspire 5551     /Aspire 5551     , BIOS V1.04 04/23/2010
task: ffff880036e4e780 ti: ffff880203160000 task.ti: ffff880203160000
RIP: 0010:[<ffffffff8117bc41>] 
 [<ffffffff8117bc41>] mmap_region+0xa1/0x5d0
RSP: 0018:ffff880203161df0  EFLAGS: 00010246
RAX: 0000000000000000 RBX: f7ff880201995c08 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 00007fe168d9c000 RDI: ffff880201995c00
RBP: ffff880203161e60 R08: 00000007fe168d9c R09: 00000007fe168d9c
R10: 00007fe168d9d000 R11: 0000000000001000 R12: 00007fe168d9c000
R13: 0000000000000000 R14: f7ff880201995c08 R15: 0000000000000000
FS:  00007fe168d7f880(0000) GS:ffff88020fc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe168da0000 CR3: 0000000203163000 CR4: 00000000000007e0
Stack:
 0000000000000001
 0000000000001000
 0000000000001000
 00000007fe168d9c
 0000000000000001
 0000000000000073
 0000000000001000
 0000000000001000
 ffff880201995c00
 0000000000000003
 0000000000000000
 0000000000000022
Call Trace:
 [<ffffffff8117c4be>] do_mmap_pgoff+0x34e/0x3d0
 [<ffffffff811669ad>] vm_mmap_pgoff+0x8d/0xc0
 [<ffffffff8117a976>] SyS_mmap_pgoff+0x116/0x270
 [<ffffffff81018002>] SyS_mmap+0x22/0x30
 [<ffffffff81695fa9>] system_call_fastpath+0x16/0x1b
Code: 45 d0 4c 8d 78 08 4c 89 f0 4d 89 fe 49 89 c7 4c 89 f3 31 d2 45 31 ed eb 12 90 4c 3b 50 e0 0f 87 26 01 00 00 48 8d 58 10 49 89 c5 <48> 8b 03 48 85 c0 74 17 4c 3b 60 e8 72 e1 48 8d 58 08 48 89 c2 
RIP  [<ffffffff8117bc41>] mmap_region+0xa1/0x5d0
 RSP <ffff880203161df0>
Comment 1 Paul Finnigan 2014-03-03 16:13:30 UTC 
Created attachment 870024 [details]
File: dmesg
Comment 2 Dave Jones 2014-03-04 05:03:11 UTC 
the code decodes to..
  2b:*	48 8b 03             	mov    (%rbx),%rax  

and rbx is f7ff880201995c08.  If that was ffff880201995c08 it'd be a believable address. (Indeed, there's a similar address in RDI)

It looks like somehow you had a single bit in memory flip from 1 to 0.
This sort of thing is usually indicative of a hardware fault of some kind.
Comment 3 Justin M. Forbes 2014-05-21 19:38:50 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  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 experience different issues, please open a new bug report for those.
Comment 4 Josh Boyer 2014-06-18 14:23:41 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.