Kernel: !m_in_critical assertion failure in Processor::check_invoke_scheduler in multi-core mode
To reproduce: stress-ng --null 6 in multi-core mode.
Trace:
[stress-ng(40:40)]: ASSERTION FAILED: !m_in_critical
[stress-ng(40:40)]: ../../Kernel/Arch/x86/common/Processor.cpp:663 in void Kernel::Processor::check_invoke_scheduler()
[stress-ng(40:40)]: KERNEL PANIC! :^(
[stress-ng(40:40)]: Aborted
[stress-ng(40:40)]: at ../../Kernel/Arch/x86/common/CPU.cpp:29 in void abort()
[stress-ng(40:40)]: Kernel + 0x0083e622 Kernel::__panic(char const*, unsigned int, char const*) +0x68
[stress-ng(40:40)]: Kernel + 0x00c154ae abort.localalias +0x1f0
[stress-ng(40:40)]: Kernel + 0x00c1553f void AK::critical_dmesgln<char const*>(AK::Format::Detail::CheckedFormatString<AK::Detail::__IdentityType<char const*>::Type>&&, char const* const&) +0x0
[stress-ng(40:40)]: Kernel + 0x00c2072a Kernel::Processor::check_invoke_scheduler() [clone .localalias] +0x1ec
[stress-ng(40:40)]: Kernel + 0x001c1678 Kernel::ScopedSpinLock<Kernel::RecursiveSpinLock>::~ScopedSpinLock() +0x5d8
[stress-ng(40:40)]: Kernel + 0x00b6ce3f Kernel::Thread::check_dispatch_pending_signal() +0x233
[stress-ng(40:40)]: Kernel + 0x008efab7 syscall_handler +0x254d
[stress-ng(40:40)]: Kernel + 0x008eabb1 syscall_asm_entry +0x3
SerenityOS / serenity
The Serenity Operating System 🐞
30.6k
Contributors get 100% of received funds after fees
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too