PANIC: page 0x82d22930 has mapping for area 0xce048920 (0x1805e000), but has no page table entry

[arfonzo]

See screenshot of panic attached.

• Haiku in a Virtualbox VM.
• If the processors are set to anything more than 1, this type of panic occurs.
• It happens, if not shortly after boot, 100% of the time with me, when I open Terminal and run installoptionalpackage.
• I've tried with 43882.

[anevilyak]

Could potentially be related to #5413.

[franxico]

I have almost the same thing running rev43911 on Virtualbox.

PANIC: remove page 0x82f7c44c from cache 0x80d07558: page still has mappings!

[bonefish]

Replying to franxico:

I have almost the same thing running rev43911 on Virtualbox.

PANIC: remove page 0x82f7c44c from cache 0x80d07558: page still has mappings!

While it might theoretically be related, it's actually in rather different parts of the kernel (x86 specific low-level paging code vs. generic VM cache management code). If you still have the KDL stack trace, please open a new ticket. Don't bother if you don't have a stack trace -- the panic line alone isn't sufficient information. Information about the general context in which the panic occurred -- amount of RAM, size of swap file, things that happened before in this session, a syslog, etc. -- is also something that might help.

Note that both kernel panics are continuable (though multiple such panics for different page might occur). It is advisable to shutdown/restart the system as soon as possible, though.

[HAL]

Is this bug related: #8435? I have a similar terminal output in that bug to the reporter except it happens installing anything, but the report is when installing OpenSSH. I found as with this bug here, disabling all but one CPU core works.

[bonefish]

This ticket reports a kernel issue while the cause of #8435 is unknown. Hence it is also unknown whether they are related.

However, #7904 is likely related, though the panics are different ones.

[nielx]

Remove milestone for tickets with status = closed and resolution != fixed