Opened 10 years ago
Closed 10 years ago
#11314 closed bug (duplicate)
PANIC: acquire_spinlock: attempt to acquire lock twice on non-SMP system
Reported by: | nicsma | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #11032 | Blocking: | |
Platform: | All |
Description
I'm trying to get the GHC Haskell compiler running on Haiku. At some point in the configure script, it runs a C program which reliably gives the kernel panic above on the hrev47958 nightly (x86, GCC 2/4 hybrid). I've attached the C program (panic.c) but I haven't tried to minimise it because I don't really know what it does.
I'm running on QEMU, single-processor. If I enable SMP I get a different panic most of the time:
PANIC: acquire_spinlock(): Failed to acquire spinlock 0xce99c850 for a long time!
I've also attached the serial debug output from the UP and SMP runs.
Attachments (5)
Change History (9)
by , 10 years ago
comment:1 by , 10 years ago
Component: | - General → System/Kernel |
---|---|
Owner: | changed from | to
by , 10 years ago
Attachment: | 20141005_024319.jpg added |
---|
comment:2 by , 10 years ago
For what it's worth, it's also happening on actual hardware too with the same level of reproducibility. Even when SMP is disabled (gives the double spinlock error instead).
My KDL is slightly different, but same set of circumstances leading to the KDL; see attached photo.
comment:3 by , 10 years ago
I managed to reduce the test case quite a bit - just a call to timer_create followed by timer_settime triggers the bug.
It KDLs if I use CLOCK_PROCESS_CPUTIME_ID or CLOCK_THREAD_CPUTIME_ID in timer_create, but not if I use CLOCK_MONOTONIC or CLOCK_REALTIME.
comment:4 by , 10 years ago
Blocked By: | 11032 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
This is the same as #11032.
The offending program