#5138: PANIC: remove page 0x82868278 from cache 0xd19e7680: page still has mappings! ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Keywords: | Blockedby: Platform: All | Blocking: 5216 ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:14 anevilyak]: > Update: I likewise managed to hit a hang with the scheduling recorder. However, I did eventually panic in acquire_spinlock: Sounds not related, so maybe better open a new ticket. > [...] > Anything worth investigating if I hit it again? Sure. If you have DEBUG_SPINLOCKS enabled, "spinlock ..." might tell you which function last called acquire_spinlock() on the spinlock in question. If it's not just an unbalanced call, a stack trace from the other CPU will help tremendously. -- Ticket URL: <http://dev.haiku-os.org/ticket/5138#comment:16> Haiku <http://dev.haiku-os.org> Haiku - the operating system.