[haiku-bugs] Re: [Haiku] #11032: Panic with message "failed to acquire spinlock %p for a long time" in usleep
- From: "mmlr" <trac@xxxxxxxxxxxx>
- Date: Thu, 30 Oct 2014 07:02:12 -0000
#11032: Panic with message "failed to acquire spinlock %p for a long time" in
usleep
-----------------------------+----------------------------
Reporter: zhuowei | Owner: pdziepak
Type: bug | Status: assigned
Priority: normal | Milestone: R1
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 11314, 11344
Has a Patch: 0 | Platform: All
-----------------------------+----------------------------
Comment (by mmlr):
Replying to [comment:7 jessicah]:
> FYI, the workaround only half fixes the issue. It still panics in
BKernel::TeamSignalEvent::DoDPC.
No, that must be a different issue and is not tracked here. DoDPC uses a
different spinlock (the team signal spinlock) and none of the 6 total
backtraces in these tickets point to it. The panic message is pointing out
a general failure to lock a spinlock, any number of places with a
deadlock/double lock can be responsible for that and each of those places
are different issues. Please open a new ticket with a backtrace and steps
to reproduce for the DoDPC case.
--
Ticket URL: <https://dev.haiku-os.org/ticket/11032#comment:8>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
