Bug 711072

Summary:	[abrt] kernel: kernel BUG at mm/huge_memory.c:1897!: TAINTED Die
Product:	[Fedora] Fedora	Reporter:	redhatbug <mjmccaffrey>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:fa032cd5319c79dc145af45cf4a79ae7b10de7df
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-26 20:02:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description redhatbug 2011-06-06 12:54:17 UTC

abrt version: 2.0.1
architecture:   x86_64
cmdline:        ro root=LABEL=hu1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=uk max_loop=255
component:      kernel
kernel:         2.6.38.6-27.fc15.x86_64
kernel_tainted: 128
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         kernel BUG at mm/huge_memory.c:1897!
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Mon Jun  6 13:51:40 2011

backtrace:
:kernel BUG at mm/huge_memory.c:1897!
:invalid opcode: 0000 [#1] SMP 
:last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
:CPU 1 
:Modules linked in: md4 nls_utf8 cifs nfs fscache tcp_lp vboxvideo drm nfsd vboxsf lockd nfs_acl auth_rpcgss exportfs sunrpc 8021q garp stp llc snd_intel8x0 snd_ac97_codec ac97_bus snd_seq ppdev microcode snd_seq_device snd_pcm joydev parport_pc snd_timer vboxguest e1000 snd parport soundcore snd_page_alloc i2c_piix4 i2c_core ipv6 [last unloaded: speedstep_lib]
:Pid: 28, comm: khugepaged Not tainted 2.6.38.6-27.fc15.x86_64 #1 innotek GmbH VirtualBox
:RIP: 0010:[<ffffffff81117744>]  [<ffffffff81117744>] khugepaged+0xb62/0xf2d
:RSP: 0018:ffff8800398b1db0  EFLAGS: 00010202
:RAX: 000000000000069c RBX: ffff88003bf6fb80 RCX: 00000000fffffff0
:RDX: 000000000000069c RSI: ffff88001c3be8a0 RDI: ffff88003bf6fc08
:RBP: ffff8800398b1ee0 R08: ffff88003ffdc700 R09: 00000000000169e6
:R10: 00000000000169e6 R11: 0000000000016990 R12: 0000000002400000
:R13: ffff88001c3be8a0 R14: ffffea0000214b28 R15: ffff880020e9e090
:FS:  0000000000000000(0000) GS:ffff88003fd00000(0000) knlGS:0000000000000000
:CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
:CR2: 00007ff4d4b9b1c0 CR3: 0000000001a03000 CR4: 00000000000006e0
:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
:Process khugepaged (pid: 28, threadinfo ffff8800398b0000, task ffff88003cf7ae40)
:Stack:
: ffffea0000214b28 ffff8800057ff000 ffff880009834000 ffff88003cf7ae40
: ffff88003cf7ae40 0000000009833067 ffff880009834000 ffff8800398b1ea0
: 00000000000005fd ffffea0000214b28 0000000000000000 0000000002600000
:Call Trace:
: [<ffffffff8106f212>] ? autoremove_wake_function+0x0/0x3d
: [<ffffffff81116be2>] ? khugepaged+0x0/0xf2d
: [<ffffffff8106eb53>] kthread+0x84/0x8c
: [<ffffffff8100a9e4>] kernel_thread_helper+0x4/0x10
: [<ffffffff8106eacf>] ? kthread+0x0/0x8c
: [<ffffffff8100a9e0>] ? kernel_thread_helper+0x0/0x10
:Code: 4c 89 ee 48 89 c7 e8 40 ec ff ff 0c 80 48 89 c7 e8 61 ea ff ff 48 89 45 90 48 8b bd 70 ff ff ff e8 da e0 35 00 49 83 3f 00 74 02 <0f> 0b 48 8b 7d 80 4c 89 e2 4c 89 ee e8 c1 51 fe ff 48 8b 4d 90 
:RIP  [<ffffffff81117744>] khugepaged+0xb62/0xf2d
: RSP <ffff8800398b1db0>

event_log:
:2011-06-06-13:54:10> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-06-06-13:54:11  Kernel oops report was uploaded

Comment 1 Josh Boyer 2011-09-26 18:01:33 UTC

Can you recreate this with the latest 2.6.40.x F15 kernel and without the vbox modules loaded?

Comment 2 redhatbug 2011-09-26 19:52:22 UTC

(In reply to comment #1)
> Can you recreate this with the latest 2.6.40.x F15 kernel and without the vbox
> modules loaded?

I am running fedora 15 on two virtual machines (both on a windows vista host) and on two of my servers. In general I keep them all pretty much up to date.

For two months or more I have not experienced any of the crashes/bugs that were occurring when Fedora 15 first came out and things are a lot more stable.

As far as I can tell from my records this kernel event only happened on a virtual machine so it may well have been due to the interaction between the vbox modules and the kernel at that time. As well as  the fedora 15 programs, the Virtual box programs I am now using are also now a few more versions advanced than they were at the time of this bug.

I filed this bug in response to the abrt message which asks if you want to report the event to the kernel developers. It was just something that happened while I was working and I do not think I could reproduce it easily or at all.

However I do hope the above is of some help to you.

Comment 3 Josh Boyer 2011-09-26 20:02:31 UTC

Thanks for letting us know.  We'll close this out as WORKSFORME since it is difficult to recreate and we haven't really seen many reports of it.