Bug 789642 - WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0x130()
Summary: WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0...
Keywords:
Status: CLOSED DUPLICATE of bug 789641
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-11 23:30 UTC by Jóhann B. Guðmundsson
Modified: 2012-02-12 22:36 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-12 22:36:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (64.46 KB, text/plain)
2012-02-11 23:30 UTC, Jóhann B. Guðmundsson
no flags Details

Description Jóhann B. Guðmundsson 2012-02-11 23:30:27 UTC
Created attachment 561165 [details]
dmesg output

Description of problem:

[    0.614715] ------------[ cut here ]------------
[    0.614718] WARNING: at include/linux/rcupdate.h:248 __atomic_notifier_call_chain+0x117/0x130()
[    0.614721] Hardware name: HP Pavilion dm1 Notebook PC
[    0.614722] Modules linked in:
[    0.614725] Pid: 0, comm: swapper/0 Tainted: G        W    3.3.0-0.rc3.git3.1.fc17.x86_64 #1
[    0.614728] Call Trace:
[    0.614731]  [<ffffffff8106047f>] warn_slowpath_common+0x7f/0xc0
[    0.614735]  [<ffffffff810604da>] warn_slowpath_null+0x1a/0x20
[    0.614738]  [<ffffffff816a1d97>] __atomic_notifier_call_chain+0x117/0x130
[    0.614742]  [<ffffffff816a1ccd>] ? __atomic_notifier_call_chain+0x4d/0x130
[    0.614746]  [<ffffffff816a1dc6>] atomic_notifier_call_chain+0x16/0x20
[    0.614750]  [<ffffffff813e7299>] notify_write+0x29/0x30
[    0.614753]  [<ffffffff813e813b>] vt_console_print+0x1ab/0x3c0
[    0.614757]  [<ffffffff8106063d>] __call_console_drivers+0x8d/0xb0
[    0.614761]  [<ffffffff81060899>] _call_console_drivers+0x49/0x70
[    0.614764]  [<ffffffff81060c84>] console_unlock+0x114/0x290
[    0.614768]  [<ffffffff810613b2>] vprintk+0x482/0x600
[    0.614772]  [<ffffffff810a27bf>] ? local_clock+0x6f/0x80
[    0.614775]  [<ffffffff81691134>] printk+0x51/0x53
[    0.614778]  [<ffffffff81022bff>] amd_e400_idle+0x11f/0x130
[    0.614782]  [<ffffffff81018266>] cpu_idle+0x106/0x140
[    0.614785]  [<ffffffff81677b8f>] rest_init+0x133/0x144
[    0.614789]  [<ffffffff81677ad5>] ? rest_init+0x79/0x144
[    0.614792]  [<ffffffff81ef6c42>] start_kernel+0x3fc/0x407
[    0.614795]  [<ffffffff81ef6346>] x86_64_start_reservations+0x131/0x135
[    0.614799]  [<ffffffff81ef644a>] x86_64_start_kernel+0x100/0x10f
[    0.614801] ---[ end trace 6d450e935ee1897d ]---


Version-Release number of selected component (if applicable):

kernel-3.3.0-0.rc3.git3.1.fc17.x86_64

How reproducible:

Always

Steps to Reproduce:
1. boot
2. run dmesg
3.
  
Actual results:

The above msg

Expected results:

No msg

Additional info:

Comment 1 Dave Jones 2012-02-12 22:36:18 UTC

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


Note You need to log in before you can comment on or make changes to this bug.