Hide Forgot
Description of problem: [ 0.498689] ------------[ cut here ]------------ [ 0.503511] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/smpboot.c:414 topology_sane.isra.4+0x8a/0x90 [ 0.512457] sched: CPU #1's llc-sibling CPU #0 is not on the same node! [node: 0 != 1]. Ignoring dependency. [ 0.522268] Modules linked in: [ 0.525338] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G I 4.7.4-200.fc24.x86_64 #1 [ 0.533768] Hardware name: SGI.COM AltixXE500/X8DAH, BIOS 1.0b 12/10/2009 [ 0.540806] 0000000000000086 1f04324d300b8068 ffff8804aa97fde8 ffffffffaa3d994f [ 0.548259] ffff8804aa97fe38 0000000000000000 ffff8804aa97fe28 ffffffffaa09faab [ 0.555712] 0000019eaa10d7a9 0000000000000001 0000000000000000 ffff8804adc0a040 [ 0.563165] Call Trace: [ 0.565616] [<ffffffffaa3d994f>] dump_stack+0x63/0x84 [ 0.570752] [<ffffffffaa09faab>] __warn+0xcb/0xf0 [ 0.575544] [<ffffffffaa09fb2f>] warn_slowpath_fmt+0x5f/0x80 [ 0.581289] [<ffffffffaa0303cc>] ? calibrate_delay_is_known+0x4c/0x80 [ 0.587806] [<ffffffffaa00283e>] ? calibrate_delay+0x7e/0x690 [ 0.593630] [<ffffffffaa048f8a>] topology_sane.isra.4+0x8a/0x90 [ 0.599627] [<ffffffffaa049248>] set_cpu_sibling_map+0x158/0x500 [ 0.605712] [<ffffffffaa04968a>] start_secondary+0x9a/0x190 [ 0.611367] ---[ end trace 4d29e2f9d4f7ef57 ]--- Version-Release number of selected component (if applicable): Fedora 24 GA (kernel-4.5.5-300.fc24.x86_64) How reproducible: rarely Steps to Reproduce: 1. Install and boot Actual results: dmesg complains about: WARNING: CPU: 1 PID: 0 at arch/x86/kernel/smpboot.c:414 topology_sane.isra.4+0x8a/0x90 Expected results: No warning in dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
so ,what's this solution？i also find the same problem when i boot my vm.