Opened 10 years ago

Closed 10 years ago

#5242 closed bug (fixed)

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

Reported by: mmadia Owned by: bonefish
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description (last modified by 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.

Attachments (2)

35012-different-kdl.txt (4.8 KB ) - added by mmadia 10 years ago.
kdl-bt_6.txt (9.4 KB ) - added by mmadia 10 years ago.
per ingo's request.

Download all attachments as: .zip

Change History (7)

by mmadia, 10 years ago

Attachment: 35012-different-kdl.txt added

comment:1 by mmadia, 10 years ago

Description: modified (diff)

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.

comment:2 by bonefish, 10 years ago

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 ...").

by mmadia, 10 years ago

Attachment: kdl-bt_6.txt added

per ingo's request.

comment:3 by mmadia, 10 years ago

bt 6 is towards the bottom.

comment:4 by bonefish, 10 years ago

Status: newin-progress

comment:5 by bonefish, 10 years ago

Resolution: fixed
Status: in-progressclosed

Fixed in hrev35020.

Note: See TracTickets for help on using tickets.