[haiku-bugs] Re: [Haiku] #11390: BKernel::TeamSignalEvent::DoDPC: failed to acquire spinlock for a long time
- From: "mmlr" <trac@xxxxxxxxxxxx>
- Date: Fri, 31 Oct 2014 07:26:09 -0000
#11390: BKernel::TeamSignalEvent::DoDPC: failed to acquire spinlock for a long
time
-----------------------------+----------------------------
Reporter: jessicah | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords: spinlock
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-----------------------------+----------------------------
Comment (by mmlr):
OK, I was able to reproduce this under KVM. Since I've ran with a single
virtual core I got the double lock panic instead:
{{{
PANIC: acquire_spinlock: attempt to acquire lock 0xd2e5afec twice on non-
SMP sys
tem (last caller: 0x00000000, value -559038737)
}}}
The interesting part being the printed value of -559038737, which
translates nicely to 0xdeadbeef. When continuing out of the panic, the
next KDL immediately hits with a page fault accessing 0xdeadbeff in
BKernel::PendingSignals::AddSignal(). So this is definitely caused by
using a freed kernel structure and an already freed spinlock.
Investigating...
--
Ticket URL: <https://dev.haiku-os.org/ticket/11390#comment:1>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
