PANIC: Invalid concurrent access to page 0x82a87348 (start), currently accessed by: 6

[mmadia]

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.

[mmadia]

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.

[bonefish]

In case you encounter it again, a back trace of the other thread (6 in this case) would be helpful. If it is currently running on another CPU (check "running") you'll have to switch the debugger to that CPU first ("cpu ...").

[mmadia]

per ingo's request.

[mmadia]

bt 6 is towards the bottom.

[bonefish]

Fixed in hrev35020.