Bug 1048442

Created attachment 845294 [details]
File: dmesg

Is this recreateable?  If so, can you attach the full dmesg output from a fresh boot?

Created attachment 847033 [details]
journal dump incl. kernel messages from yesterday's boot

Hi,
I still don't know what to do to reproduce this, but it happened again yesterday, when I just switched on the machine to ssh into it.

complete journal (incl. kernel messages) from yesterday included.

I have been facing the similar issue. I could reproduce this when running "rsync" with large number of files (between USB drive and local filesystem). Kernel version 3.12.9-301.fc20.x86_64.

vendor_id	: AuthenticAMD
cpu family	: 21
model		: 1
model name	: AMD FX(tm)-8120 Eight-Core Processor
stepping	: 2
microcode	: 0x600063d
cpu MHz		: 1400.000
cache size	: 2048 KB
physical id	: 0
siblings	: 8
core id		: 0
cpu cores	: 4
apicid		: 16
initial apicid	: 0
fpu		: yes

Backtrace:

BUG: Bad page state in process swapper  pfn:2f3cd
page:ffffea0000bcf340 count:0 mapcount:-33554432 mapping:          (null) index:0x0
page flags: 0x3ff00000000000()
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.9-301.fc20.x86_64 #1
Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 LE R2.0, BIOS 1903 07/11/2013
 00000000fe000000 ffffffff81c01e00 ffffffff81667af7 ffffea0000bcf340
 ffffffff81c01e18 ffffffff81664c44 0000000000000000 ffffffff81c01e60
 ffffffff81149715 ffffea0000bd0000 0000000000000002 ffffea0000bcf000
Call Trace:
 [<ffffffff81667af7>] dump_stack+0x45/0x56
 [<ffffffff81664c44>] bad_page.part.67+0xcf/0xe8
 [<ffffffff81149715>] free_pages_prepare+0x165/0x170
 [<ffffffff8114a2ad>] __free_pages+0x2d/0x70
 [<ffffffff81d4423f>] __free_pages_bootmem+0xba/0xc6
 [<ffffffff81d472ba>] __free_memory_core+0xee/0x130
 [<ffffffff81d474d2>] free_all_bootmem+0x45/0x92
 [<ffffffff81d3569e>] mem_init+0x5c/0x8d
 [<ffffffff81d1dccb>] start_kernel+0x1de/0x415
 [<ffffffff81d1d8f6>] ? repair_env_string+0x5c/0x5c
 [<ffffffff81d1d120>] ? early_idt_handlers+0x120/0x120
 [<ffffffff81d1d5de>] x86_64_start_reservations+0x2a/0x2c
 [<ffffffff81d1d6e8>] x86_64_start_kernel+0x108/0x117

# cat os_info 
NAME=Fedora
VERSION="20 (Heisenbug)"
ID=fedora
VERSION_ID=20
PRETTY_NAME="Fedora 20 (Heisenbug)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:20"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=20
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=20

*********** 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.13.4-200.fc20.  Please test this kernel update 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.

Installed the memory test in grub using memtest-setup and upon running it showed many memory errors. Had to replace the memory with compatible to that of the motherboard. Running rsync after that went find without any issues. It turns out to be incompatible memory module.