Bug 789641
| Summary: | WARNING: at include/linux/rcupdate.h:242 __atomic_notifier_call_chain+0xf1/0x130() | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> | ||||
| 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: | rawhide | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-3.3.0-0.rc3.git7.2.fc17 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-02 19:26:36 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: |
|
||||||
*** Bug 789642 has been marked as a duplicate of this bug. *** I believe this might be fixed by https://lkml.org/lkml/2012/1/24/441 Can you try this scratch build when it completes and let me know if this traceback goes away: http://koji.fedoraproject.org/koji/taskinfo?taskID=3788809 Yup the traceback went away Thank you for testing. I've committed the changes and it should be in f17/rawhide soon. kernel-3.3.0-0.rc3.git6.2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.3.0-0.rc3.git6.2.fc17 Package kernel-3.3.0-0.rc3.git6.2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.3.0-0.rc3.git6.2.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1820/kernel-3.3.0-0.rc3.git6.2.fc17 then log in and leave karma (feedback). kernel-3.3.0-0.rc3.git7.2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.3.0-0.rc3.git7.2.fc17 kernel-3.3.0-0.rc3.git7.2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Have to reopen this, as the patch checked in seems to have caused some large slowdowns for people (see bug 795050) (In reply to comment #10) > Have to reopen this, as the patch checked in seems to have caused some large > slowdowns for people (see bug 795050) Lot of slowness drama on that bug report. I'm running 3.3.0-0.rc4.git0.1.fc17.x86_64 here on F16 without experiencing all that slowness epicness... *** This bug has been marked as a duplicate of bug 799303 *** |
Created attachment 561164 [details] dmesg output Description of problem: [ 0.614605] ------------[ cut here ]------------ [ 0.614614] WARNING: at include/linux/rcupdate.h:242 __atomic_notifier_call_chain+0xf1/0x130() [ 0.614617] Hardware name: HP Pavilion dm1 Notebook PC [ 0.614619] Modules linked in: [ 0.614623] Pid: 0, comm: swapper/0 Not tainted 3.3.0-0.rc3.git3.1.fc17.x86_64 #1 [ 0.614626] Call Trace: [ 0.614633] [<ffffffff8106047f>] warn_slowpath_common+0x7f/0xc0 [ 0.614638] [<ffffffff810604da>] warn_slowpath_null+0x1a/0x20 [ 0.614642] [<ffffffff816a1d71>] __atomic_notifier_call_chain+0xf1/0x130 [ 0.614646] [<ffffffff816a1dc6>] atomic_notifier_call_chain+0x16/0x20 [ 0.614650] [<ffffffff813e7299>] notify_write+0x29/0x30 [ 0.614654] [<ffffffff813e813b>] vt_console_print+0x1ab/0x3c0 [ 0.614658] [<ffffffff8106063d>] __call_console_drivers+0x8d/0xb0 [ 0.614662] [<ffffffff81060899>] _call_console_drivers+0x49/0x70 [ 0.614666] [<ffffffff81060c84>] console_unlock+0x114/0x290 [ 0.614670] [<ffffffff810613b2>] vprintk+0x482/0x600 [ 0.614675] [<ffffffff810a27bf>] ? local_clock+0x6f/0x80 [ 0.614679] [<ffffffff81691134>] printk+0x51/0x53 [ 0.614683] [<ffffffff81022bff>] amd_e400_idle+0x11f/0x130 [ 0.614688] [<ffffffff81018266>] cpu_idle+0x106/0x140 [ 0.614693] [<ffffffff81677b8f>] rest_init+0x133/0x144 [ 0.614696] [<ffffffff81677ad5>] ? rest_init+0x79/0x144 [ 0.614701] [<ffffffff81ef6c42>] start_kernel+0x3fc/0x407 [ 0.614705] [<ffffffff81ef6346>] x86_64_start_reservations+0x131/0x135 [ 0.614708] [<ffffffff81ef644a>] x86_64_start_kernel+0x100/0x10f [ 0.614713] ---[ end trace 6d450e935ee1897c ]--- [ 0.614715] ------------[ cut here ]------------ 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: