| Summary: | arch/x86/kernel/cpu/mcheck/mce.c:194 suspicious rcu_dereference_index_check() usage! | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | fullung, gansalmon, itamar, johannbg, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-3.3.0-8.fc16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 821464 (view as bug list) | Environment: | |||||
| Last Closed: | 2012-02-21 02:22:42 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 821464 | ||||||
| Attachments: |
|
||||||
This is likely fixed by https://lkml.org/lkml/2012/1/26/237 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 *** Bug 795012 has been marked as a duplicate of this bug. *** 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. Looks like there's still an issue.
[ 37.578198] ===============================
[ 37.578200] [ INFO: suspicious RCU usage. ]
[ 37.578203] 3.3.0-4.fc16.x86_64.debug #1 Not tainted
[ 37.578204] -------------------------------
[ 37.578207] arch/x86/kernel/cpu/mcheck/mce.c:194 suspicious rcu_dereference_index_check() usage!
[ 37.578209]
[ 37.578210] other info that might help us debug this:
[ 37.578213]
[ 37.578214]
[ 37.578216] rcu_scheduler_active = 1, debug_locks = 0
[ 37.578219] 3 locks held by modprobe/235:
[ 37.578221] #0: (&__lockdep_no_validate__){......}, at: [<ffffffff8141242b>] __driver_attach+0x5b/0xb0
[ 37.578231] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff81412439>] __driver_attach+0x69/0xb0
[ 37.578238] #2: (i7core_edac_lock){+.+.+.}, at: [<ffffffffa00bcb3e>] i7core_probe+0x22/0xcb8 [i7core_edac]
[ 37.578248]
[ 37.578249] stack backtrace:
[ 37.578252] Pid: 235, comm: modprobe Not tainted 3.3.0-4.fc16.x86_64.debug #1
[ 37.578255] Call Trace:
[ 37.578264] [<ffffffff810c9ae5>] lockdep_rcu_suspicious+0xe5/0x100
[ 37.578270] [<ffffffff81031f9d>] mce_register_decode_chain+0x1bd/0x1e0
[ 37.578276] [<ffffffff8151ee74>] ? dmi_walk+0x74/0x90
[ 37.578280] [<ffffffffa00bd6b5>] i7core_probe+0xb99/0xcb8 [i7core_edac]
[ 37.578286] [<ffffffff810a3e7f>] ? local_clock+0x6f/0x80
[ 37.578292] [<ffffffff813498dc>] local_pci_probe+0x5c/0xd0
[ 37.578296] [<ffffffff8134b1d9>] pci_device_probe+0x109/0x130
[ 37.578300] [<ffffffff8141216c>] driver_probe_device+0x9c/0x300
[ 37.578305] [<ffffffff8141247b>] __driver_attach+0xab/0xb0
[ 37.578309] [<ffffffff814123d0>] ? driver_probe_device+0x300/0x300
[ 37.578313] [<ffffffff814104fe>] bus_for_each_dev+0x5e/0x90
[ 37.578316] [<ffffffff81411d6e>] driver_attach+0x1e/0x20
[ 37.578319] [<ffffffff81411960>] bus_add_driver+0x1c0/0x2b0
[ 37.578324] [<ffffffffa0031000>] ? 0xffffffffa0030fff
[ 37.578327] [<ffffffff814129f6>] driver_register+0x76/0x140
[ 37.578334] [<ffffffff813325a8>] ? __raw_spin_lock_init+0x38/0x70
[ 37.578338] [<ffffffffa0031000>] ? 0xffffffffa0030fff
[ 37.578341] [<ffffffff8134ae96>] __pci_register_driver+0x66/0xe0
[ 37.578347] [<ffffffffa0031093>] i7core_init+0x93/0x1000 [i7core_edac]
[ 37.578354] [<ffffffff8100203f>] do_one_initcall+0x3f/0x170
[ 37.578360] [<ffffffff810dbb82>] sys_init_module+0xc82/0x21f0
[ 37.578365] [<ffffffff816abb29>] system_call_fastpath+0x16/0x1b
(In reply to comment #10) > Looks like there's still an issue. > > [ 37.578198] =============================== > [ 37.578200] [ INFO: suspicious RCU usage. ] > [ 37.578203] 3.3.0-4.fc16.x86_64.debug #1 Not tainted > [ 37.578204] ------------------------------- > [ 37.578207] arch/x86/kernel/cpu/mcheck/mce.c:194 suspicious > rcu_dereference_index_check() usage! F16 is missing that fix. I'll get it backported and into the next update. kernel-3.3.0-8.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.3.0-8.fc16 kernel-3.3.0-8.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 561167 [details] dmesg output Description of problem: [ 12.391229] =============================== [ 12.391298] [ INFO: suspicious RCU usage. ] [ 12.391367] 3.3.0-0.rc3.git3.1.fc17.x86_64 #1 Tainted: G W [ 12.391437] ------------------------------- [ 12.391505] arch/x86/kernel/cpu/mcheck/mce.c:194 suspicious rcu_dereference_index_check() usage! [ 12.391636] [ 12.391637] other info that might help us debug this: [ 12.391639] [ 12.391832] [ 12.391832] rcu_scheduler_active = 1, debug_locks = 0 [ 12.391963] no locks held by modprobe/213. [ 12.392044] [ 12.392045] stack backtrace: [ 12.392173] Pid: 213, comm: modprobe Tainted: G W 3.3.0-0.rc3.git3.1.fc17.x86_64 #1 [ 12.392305] Call Trace: [ 12.392381] [<ffffffff810c8785>] lockdep_rcu_suspicious+0xe5/0x100 [ 12.392457] [<ffffffffa006d000>] ? 0xffffffffa006cfff [ 12.392531] [<ffffffff81031050>] mce_register_decode_chain+0x1c0/0x1e0 [ 12.392605] [<ffffffffa006d000>] ? 0xffffffffa006cfff [ 12.392678] [<ffffffffa006d176>] mce_amd_init+0x176/0x1000 [edac_mce_amd] [ 12.392752] [<ffffffff8100212a>] do_one_initcall+0x12a/0x180 [ 12.392825] [<ffffffff810da756>] sys_init_module+0x1146/0x2260 [ 12.392897] [<ffffffff816a64a9>] system_call_fastpath+0x16/0x1b 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: