Opened 14 years ago
Last modified 14 years ago
#5242 closed bug
PANIC: Invalid concurrent access to page 0x82a87348 (start), currently accessed by: 6 — at Version 1
Reported by: | mmadia | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description (last modified by )
hrev35012-gcc2hybrid. while trying to reproduce #5138 with user_config_headers/tracing_config.h:
// enable tracing (0/1) #ifndef ENABLE_TRACING # define ENABLE_TRACING 1 #endif // tracing buffer size (in bytes) #ifndef MAX_TRACE_SIZE # define MAX_TRACE_SIZE (300 * 1024 * 1024) #endif ... #define SYSCALL_TRACING_IGNORE_KTRACE_OUTPUT 1 ... #define VM_CACHE_TRACING 2 ...
a KDL PANIC: Invalid concurrent access to page 0x82a87348 (start), currently accessed by: 6
occured within seconds of starting jam -aqj3 @alpha-raw
After several 'co', Haiku recovered.
backtrace attached.
Change History (2)
by , 14 years ago
Attachment: | 35012-different-kdl.txt added |
---|
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.
In the same session of Haiku, I've reproduced it about 5 times. Looking at jam -dx -aqj3 @alpha-raw, the kdl occurs after a gcc command -- as opposed to ar: or ranlib.