smp tainted kernel warning

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

Moderators: spender, PaX Team

smp tainted kernel warning

Postby osea » Sat Jan 14, 2017 8:31 pm

There is another issue I see in boot logs. Its harmless and doesn't cause panics or anything, but I'd appreciate you taking a look.


Call trace from a kernel with debug:

Code: Select all
Jan 15 00:16:02 host kernel: [    0.124000] x86: Booting SMP configuration:
Jan 15 00:16:02 host kernel: [    0.124000] .... node  #0, CPUs:      #1
Jan 15 00:16:02 host kernel: [    0.016000] Initializing CPU#1
Jan 15 00:16:02 host kernel: [    0.016000] ------------[ cut here ]------------
Jan 15 00:16:02 host kernel: [    0.016000] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/amd.c:266 init_amd+0x78a/0x8f0
Jan 15 00:16:02 host kernel: [    0.016000] WARNING: This combination of AMD processors is not suitable for SMP.
Jan 15 00:16:02 host kernel: [    0.016000] Modules linked in:
Jan 15 00:16:02 host kernel: [    0.016000] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.17-grsec #2
Jan 15 00:16:02 host kernel: [    0.016000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1 04/01/2014
Jan 15 00:16:02 host kernel: [    0.016000]  00000000 00200086 f6493ea4 0027a3de 00200086 f6493ee8 c24e5ef4 f6493ed4
Jan 15 00:16:02 host kernel: [    0.016000]  0005459d c24da34c f6493f04 00000000 c24e5ef4 0000010a 0002d96a 0000010a
Jan 15 00:16:02 host kernel: [    0.016000]  00000000 f6b16000 00000000 f6493ef0 000545f4 00000009 00000000 f6493ee8
Jan 15 00:16:02 host kernel: [    0.016000] Call Trace:
Jan 15 00:16:02 host kernel: [    0.016000]  [<00200086>] ? key_instantiate_and_link+0x86/0xf0
Jan 15 00:16:02 host kernel: [    0.016000]  [<0027a3de>] dump_stack+0x52/0x74
Jan 15 00:16:02 host kernel: [    0.016000]  [<00200086>] ? key_instantiate_and_link+0x86/0xf0
Jan 15 00:16:02 host kernel: [    0.016000]  [<0005459d>] __warn+0xed/0x110
Jan 15 00:16:02 host kernel: [    0.016000]  [<0002d96a>] ? init_amd+0x78a/0x8f0
Jan 15 00:16:02 host kernel: [    0.016000]  [<000545f4>] warn_slowpath_fmt+0x34/0x40
Jan 15 00:16:02 host kernel: [    0.016000]  [<0002d96a>] init_amd+0x78a/0x8f0
Jan 15 00:16:02 host kernel: [    0.016000]  [<00003028>] ? backtrace_address+0x48/0x70
Jan 15 00:16:02 host kernel: [    0.016000]  [<0002adc0>] ? get_cpu_cap+0x200/0x280
Jan 15 00:16:02 host kernel: [    0.016000]  [<0002b0c3>] identify_cpu+0x283/0x550
Jan 15 00:16:02 host kernel: [    0.016000]  [<000f4240>] ? perf_output_read+0x140/0xa20
Jan 15 00:16:02 host kernel: [    0.016000]  [<0002b3bf>] identify_secondary_cpu+0xf/0x30
Jan 15 00:16:02 host kernel: [    0.016000]  [<0003b288>] smp_store_cpu_info+0x48/0x60
Jan 15 00:16:02 host kernel: [    0.016000]  [<0003b69f>] start_secondary+0x3f/0x1a0
Jan 15 00:16:02 host kernel: [    0.016000]  [<00037b12>] ? load_ucode_ap+0x92/0xd0
Jan 15 00:16:02 host kernel: [    0.016000]  [<01000800>] ? 0x1000800
Jan 15 00:16:02 host kernel: [    0.016000] ---[ end trace 2e0fbb669abe6a75 ]---
Jan 15 00:16:02 host kernel: [    0.016000] Disabling lock debugging due to kernel taint
Jan 15 00:16:02 host kernel: [    0.160000]  #2<6>[    0.016000] Initializing CPU#2
Jan 15 00:16:02 host kernel: [    0.016000]  #3
Jan 15 00:16:02 host kernel: [    0.016000] Initializing CPU#3
Jan 15 00:16:02 host kernel: [    0.232000] x86: Booted up 1 node, 4 CPUs
osea
 
Posts: 21
Joined: Thu Oct 27, 2016 3:17 pm

Re: smp tainted kernel warning

Postby spender » Sat Jan 14, 2017 8:55 pm

I don't think this is a grsecurity issue, it's something to do with your kernel configuration/hardware.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm
Location: VA, USA

Re: smp tainted kernel warning

Postby osea » Sat Jan 14, 2017 8:59 pm

ok thanks.
osea
 
Posts: 21
Joined: Thu Oct 27, 2016 3:17 pm


Return to grsecurity support