WARNING: at kernel/time/tick-broadcast.c

[poma]

After further testing with suspend.target what happens is,

- resume from systemctl suspend - 3.9.9:

Enabling non-boot CPUs ...
[Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #1
[Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #2
[Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #3
ACPI: Waking up from system sleep state S3


- resume from systemctl suspend - 3.10.0/3.10.1:

Enabling non-boot CPUs ...
[Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #1
WARNING: at kernel/time/tick-broadcast.c:585
tick_broadcast_oneshot_control+0x170/0x180()
Call Trace:
 [<ffffffff81641d36>] dump_stack+0x19/0x1b
 [<ffffffff8105c221>] warn_slowpath_common+0x61/0x80
 [<ffffffff8105c2fa>] warn_slowpath_null+0x1a/0x20
 [<ffffffff810b5c30>] tick_broadcast_oneshot_control+0x170/0x180
 [<ffffffff810b512d>] tick_notify+0x2fd/0x440
 [<ffffffff8164c0cc>] notifier_call_chain+0x4c/0x70
 [<ffffffff810862e6>] raw_notifier_call_chain+0x16/0x20
 [<ffffffff810b4679>] clockevents_notify+0x39/0x140
 [<ffffffff81019675>] amd_e400_idle+0x75/0x100
 [<ffffffff81019e36>] arch_cpu_idle+0x26/0x30
 [<ffffffff810acabe>] cpu_startup_entry+0xce/0x280
 [<ffffffff810b4835>] ? clockevents_register_device+0xb5/0x120
 [<ffffffff81636e0e>] start_secondary+0x24e/0x250
[Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #2
[Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #3
ACPI: Waking up from system sleep state S3


- resume from systemctl suspend - 3.11.0-0.rc1:

Enabling non-boot CPUs ...
[Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #1
WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667
tick_broadcast_oneshot_control+0x170/0x180()
Call Trace:
 [<ffffffff8164db04>] dump_stack+0x45/0x56
 [<ffffffff810670bd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106719a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff810c0090>] tick_broadcast_oneshot_control+0x170/0x180
 [<ffffffff810be8f8>] clockevents_notify+0x178/0x1a0
 [<ffffffff8101ae75>] amd_e400_idle+0x75/0x100
 [<ffffffff8101b626>] arch_cpu_idle+0x26/0x30
 [<ffffffff810b64de>] cpu_startup_entry+0xce/0x280
 [<ffffffff810be9dc>] ? clockevents_register_device+0xbc/0x120
 [<ffffffff8103ed17>] start_secondary+0x217/0x2c0
[Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #2
[Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #3
ACPI: Waking up from system sleep state S3


Kernel 3.10.1 with an additional four patches[1] doesn't change anything,
also as seen in the kernel 3.11.0-0.rc1.
Does anyone else chase the same case?


poma


[1]
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/kernel/time/tick-broadcast.c
- tick: Make oneshot broadcast robust vs. CPU offlining
- tick: Prevent uncontrolled switch to oneshot mode
- tick: Sanitize broadcast control logic
- tick: broadcast: Check broadcast mode on CPU hotplug