Bug 794998

Summary:	[abrt] kernel: WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0x130()
Product:	[Fedora] Fedora	Reporter:	Michael Young <m.a.young>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:1603315c5c5884706943fffa0f00b8a7c956ba14
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-02 19:32:56 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 Michael Young 2012-02-18 15:44:20 UTC

libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        root=/dev/mapper/VolGroup-lv_root ro rd.md=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.lvm.lv=VolGroup/lv_swap rd.lvm.lv=VolGroup/lv_root rd.luks=0  KEYTABLE=uk LANG=en_US.UTF-8 rhgb quiet 
comment:        I get this very early in the boot (between 0.01-0.02 seconds according to the timestamp) as a xen guest. It looks to be the same sort of problem as Bug 789641 but probably specific to xen.
kernel:         3.3.0-0.rc3.git7.2.fc17.x86_64
reason:         WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0x130()
time:           Sat 18 Feb 2012 03:29:42 PM GMT

backtrace:
:WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0x130()
:Modules linked in:
:Pid: 0, comm: swapper/1 Tainted: G        W    3.3.0-0.rc3.git7.2.fc17.x86_64 #1
:Call Trace:
: <IRQ>  [<ffffffff81060bef>] warn_slowpath_common+0x7f/0xc0
: [<ffffffff81060c4a>] warn_slowpath_null+0x1a/0x20
: [<ffffffff816a2817>] __atomic_notifier_call_chain+0x117/0x130
: [<ffffffff816a274d>] ? __atomic_notifier_call_chain+0x4d/0x130
: [<ffffffff810c7467>] ? trace_hardirqs_off_caller+0x67/0xb0
: [<ffffffff816a2846>] atomic_notifier_call_chain+0x16/0x20
: [<ffffffff81018153>] exit_idle+0x43/0x50
: [<ffffffff813c8105>] xen_evtchn_do_upcall+0x25/0x50
: [<ffffffff816a84be>] xen_do_hypervisor_callback+0x1e/0x30
: <EOI>  [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
: [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
: [<ffffffff8100f010>] ? xen_safe_halt+0x10/0x20
: [<ffffffff81022649>] ? default_idle+0x59/0x4e0
: [<ffffffff81018256>] ? cpu_idle+0xf6/0x130
: [<ffffffff8100f8e9>] ? xen_irq_enable_direct_reloc+0x4/0x4
: [<ffffffff81684dff>] ? cpu_bringup_and_idle+0xe/0x10

Comment 1 Josh Boyer 2012-03-02 19:32:56 UTC


*** This bug has been marked as a duplicate of bug 799303 ***