Jon
On Wednesday, August 20, 2003, at 01:21 AM, Phil Wade wrote:
Andrew,
>> ��It might help to give the With folks the screen output of your kernel
>> panics.
>
> I have sent a few of the kernel panics to the With folks in a bug report
> and at least one email, but it's been several days now and no reply, so I'm
> not holding my breath on a resolution from them.
We received your email last Friday and we have been looking into what the cause may be.
> the very first non-OS software I put on was
> Dev Studio. �It also Kernel panics within 3 days every single time if I
> leave it running.
This has puzzled us as the Dev Studio is actually a carbon app and is several layers away from the kernel and drivers driver and is completely different code to the server. �It should crash before it can tear down the kernel. �We are also puzzled as to how the Dev Studio can cause a kernal panic when it is not doing anything at all. �It is not consuming CPU or memory. �It is just resident in memory.
> panic(cpu 0): cpu_signal_handler: Lock pass timed out
>
> Latest stack backtrace for cpu 0:
> �����Backtrace:
> ��������0x0008581C 0x00085C4C 0x000287B4 0x00084118 0x1D51DAC8 0x0023E300
> 0x00094568 0x00092D84
> �����Kernel loadable modules in backtrace (with dependencies):
> ��������com.apple.driver.AppleMPIC(1.1)@0x1d51c000
> Proceeding back via exception chain:
> ��Exception state (sv=0x1E00A780)
> �����PC=0x00034174; MSR=0x00209030; DAR=0x0D99BB98; DSISR=0x40000000;
> LR=0x00034174; R1=0x0D99BD50; XCP=0x00000014 (0x500 - Ext int)
> �����Backtrace:
> ��������0x00034018 0x000345C8 0x00035534 0x000353D0
> ��Exception state (sv=0x1E010C80)
> �����PC=0x90073C28; MSR=0x0000F030; DAR=0x0DA13B98; DSISR=0x40000000;
> LR=0x90005F70; R1=0xF0305C80; XCP=0x00000030 (0xC00 - System call)
>
> Kernel version:
> Darwin Kernel Version 6.6:
> Thu May �1 21:48:54 PDT 2003; root:xnu/xnu-344.34.obj~1/RELEASE_PPC
>
>
>
> *********
>
> Wed Aug 13 14:18:44 2003
>
>
> panic(cpu 0): cpu_signal_handler: Lock pass timed out
>
> Latest stack backtrace for cpu 0:
> �����Backtrace:
> ��������0x0008581C 0x00085C4C 0x000287B4 0x00084118 0x1D51DAC8 0x0023E300
> 0x00094568 0x00092D84
> �����Kernel loadable modules in backtrace (with dependencies):
> ��������com.apple.driver.AppleMPIC(1.1)@0x1d51c000
> Proceeding back via exception chain:
> ��Exception state (sv=0x1DB78780)
> �����PC=0x000343F0; MSR=0x00209030; DAR=0x0D983B98; DSISR=0x40000000;
> LR=0x000343F0; R1=0x0D8D3E40; XCP=0x00000014 (0x500 - Ext int)
> �����Backtrace:
> ��������0x000343C0 0x00000000
> ��Exception state (sv=0x1D508C80)
> �����PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000;
> LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
>
> Kernel version:
> Darwin Kernel Version 6.6:
> Thu May �1 21:48:54 PDT 2003; root:xnu/xnu-344.34.obj~1/RELEASE_PPC
All your kernal panics are occuring in the MPIC driver which is the multiprocessor interrupt controller which interfaces the Multi processors to the other sub systems.
�������Kernel loadable modules in backtrace (with dependencies):
����������com.apple.driver.AppleMPIC(1.1)@0x1d51c000
It is also always happening on CPU 0 and it is always a cpu_signal_handler: Lock pass timed out. �These subsystems are invisible to us and are not called directly by the Witango Dev Studio or Server but through calls to APIs. ��Can you ask your apple engineer what can cause these types of panics in the MPIC driver. �He should also be able to give you a detailed description of the meaning of the panics. �Can you pass this information on to me as it may lead us to what is causing the panics. �Can he explain how a carbon app and a mach-o daemon can cause the same panic when sitting idle in memory not consuming CPU or other system resources?
The MPIC driver is part of the opendarwin project. �We have been trying to check bugzilla on the opendarwin site to see if there are any known bugs, but the bugzilla system has been down. �Actually a lot of the Open Darwin site is not working.
E.g
Links off the home page:
Warning : �Supplied argument is not a valid MySQL result resource in /Library/WebServer/Documents/en/news.php on line 51
There are no announcements.
Link to Bugzilla:
Software error:
Bugzilla is currently broken. Please try again later. If the problem persists, please contact [EMAIL PROTECTED] The error you should quote is: Unknown database 'bugs' at globals.pl line 140.
We are endeavouring to resolve this issue but until we can reproduce it or find another user having the same issue it is like finding a needle in a haystack. ��Are you able to switch processors around or disable CPU0? �Do you have another Dual processor G4 you can test the apps on.
Phil
