[XonX-Users] emacs kernel panic still there; who to make noise to?
Brought to you by:
torrey
From: Ron C. <rc...@ll...> - 2001-11-20 21:08:42
|
The Darwin kernel bug that causes xemacs to crash on dual-processor G4's still seems to be there, even after the 10.1.1 udpate. The kernel panic traceback has changed slightly. What is the best way to get this on Apple's radar screen? Old and new kernel panic logs below. Note I changed versions of xemacs in between, as I had to wipe my hard disk after my first install of 10.1.1, and so went to a more current xemacs (21.4.5 instead of 21.4.3). Also as far as I can tell, as before the crash only occurs if xemacs appears in its own xwindow (under X11); running inside a terminal window is OK. -Ron Cohen- ------------------------------------- Old (OS 10.1) panic(cpu 0): lockmgr: pid -2, thread 0x 180cd04, not exclusive lock holder pid -2 thread 0x 1c8e354 unlocking, exclusive count 1 Latest stack backtrace for cpu 0: Backtrace: 0x0008122c 0x000815cc 0x00027d38 0x001831b0 0x001886c8 0x00188bf8 0x00026794 0x0008ec0c 0x0008e9a0 0x0050b13e Proceeding back via exception chain: Exception state (sv=0x0c4cd000) PC=0x70001318; MSR=0x0000f030; DAR=0x01f250ce; DSIR=0x00002004; LR=0x0008449e8; R1=0xbfffe140; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 1.4: Sun Sep 9 15:39:59 PDT 2001; root:xnu/xnu-201.obj~1/RELEASE_PPC Debugger(panic) Waiting for remote debugger connection ---------------------------- New (OS 10.1.1) panic(cpu 0): lockmgr: non-zero exclusive count Latest stack backtrace for cpu 0: Backtrace: 0x000819b8 0x00081d58 0x00028520 0x001840bc 0x00187d28 0x001892dc 0x00189b78 0x00026f7c 0x0008f40c 0x001920e8 0x0018a41c 0x0018a29c Proceeding back via exception chain: Exception state (sv=0x0c4cd000) PC=0x70025CAB; MSR=0x0000f030; DAR=0x01fc7aee; DSIR=0x00002004; LR=0x0078e8e4; R1=0xbfffe800; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 5.1: Tue Oct 30 00:06:34 PST 2001; root:xnu/xnu-201.5.obj~1/RELEASE_PPC Debugger(panic) Waiting for remote debugger connection |