Reply to thread

Message

<blockquote data-quote="hype.it" data-source="post: 44805" data-attributes="member: 4085">New machine, new install... it's normal. It's only a serious worry if it happens on a regular basis. On a new machine with next to nothing installed, running the crons and permission is rather meaningless since nothing's been really running, hence not alot has been processed. Crons and permission only become messed up or corrupted when data and application get shifted about, like when it's been in uses.If you want a detailed explination as to why your machine had a kernal panic you can check the log files, located in:User &gt; Logs &gt; CrashReporterJust double click on each file and it'll open. Your system records just about every action into this useful log, that can be used for debugging.For example (my last reported system crash)[code]**********Host Name:&nbsp; &nbsp; &nbsp; xxxxxxxx.netvigator.comDate/Time:&nbsp; &nbsp; &nbsp; 2004-08-13 11:53:21 +0800OS Version:&nbsp; &nbsp;&nbsp; 10.3.5 (Build 7M34)Report Version: 2Command: SystemUIServerPath:&nbsp; &nbsp; /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServerVersion: 1.2.1 (1.2.1)PID:&nbsp; &nbsp;&nbsp; 375Thread:&nbsp; 0Exception:&nbsp; EXC_BAD_ACCESS (0x0001)Codes:&nbsp; &nbsp; &nbsp; KERN_PROTECTION_FAILURE (0x0002) at 0x00000614Thread 0 Crashed:0&nbsp;&nbsp; libobjc.A.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x908311ec objc_msgSend + 0xc1&nbsp;&nbsp; com.apple.menuextra.bluetooth&nbsp; &nbsp;&nbsp; 0x017db410 BluetoothPreferencesChanged + 0x1b8c2&nbsp;&nbsp; com.apple.Foundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x909f7184 _nsnote_callback + 0xb03&nbsp;&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x901aa650 __CFXNotificationPost + 0x1b44&nbsp;&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x901af060 _CFXNotificationPostNotification + 0x3405&nbsp;&nbsp; com.apple.Foundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x909f4fd0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 0x746&nbsp;&nbsp; com.apple.Bluetooth&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x93f72484 btNotificationDevicePublished + 0xf87&nbsp;&nbsp; com.apple.framework.IOKit&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x9058e568 IODispatchCalloutFromCFMessage + 0x1b88&nbsp;&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x901ad330 __CFMachPortPerform + 0xe09&nbsp;&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x901a9ab4 __CFRunLoopDoSource1 + 0xc810&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x90191980 __CFRunLoopRun + 0x54011&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x90195f1c CFRunLoopRunSpecific + 0x14812&nbsp; com.apple.HIToolbox&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x927d5f88 RunCurrentEventLoopInMode + 0xac13&nbsp; com.apple.HIToolbox&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x927dc6f0 ReceiveNextEventCommon + 0x17c14&nbsp; com.apple.HIToolbox&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x927fe6c8 BlockUntilNextEventMatchingListInMode + 0x6015&nbsp; com.apple.AppKit&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x92dd227c _DPSNextEvent + 0x18016&nbsp; com.apple.AppKit&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x92de8c24 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x7417&nbsp; com.apple.AppKit&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x92dfcf8c -[NSApplication run] + 0x21c18&nbsp; com.apple.systemuiserver&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x0000afcc 0x1000 + 0x9fcc19&nbsp; com.apple.systemuiserver&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x0000ae34 0x1000 + 0x9e3420&nbsp; com.apple.systemuiserver&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x0000aca8 0x1000 + 0x9ca8Thread 1:0&nbsp;&nbsp; libSystem.B.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x900074c8 mach_msg_trap + 0x81&nbsp;&nbsp; libSystem.B.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x90007018 mach_msg + 0x382&nbsp;&nbsp; com.unsanity.ape&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0xc000a954 __ape_internal + 0x90b83&nbsp;&nbsp; com.unsanity.ape&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0xc0001328 __ape_agent + 0x404&nbsp;&nbsp; libSystem.B.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x900246e8 _pthread_body + 0x28Thread 2:0&nbsp;&nbsp; libSystem.B.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x9000b20c select + 0xc1&nbsp;&nbsp; com.apple.CoreFoundation&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0x90196ba0 __CFSocketManager + 0x1fc2&nbsp;&nbsp; libSystem.B.dylib&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 0x900246e8 _pthread_body + 0x28PPC Thread State:&nbsp; srr0: 0x908311ec srr1: 0x0000f030&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; vrsave: 0x00000000&nbsp; &nbsp; cr: 0x44822484&nbsp; xer: 0x00000004&nbsp;&nbsp; lr: 0x017db410&nbsp; ctr: 0x908311e0&nbsp; &nbsp; r0: 0x017db410&nbsp;&nbsp; r1: 0xbfffe350&nbsp;&nbsp; r2: 0x0034ffdc&nbsp;&nbsp; r3: 0x06503c00&nbsp; &nbsp; r4: 0x90893514&nbsp;&nbsp; r5: 0x003fa470&nbsp;&nbsp; r6: 0xbfffe4d0&nbsp;&nbsp; r7: 0x00000004&nbsp; &nbsp; r8: 0x00000003&nbsp;&nbsp; r9: 0x00000000&nbsp; r10: 0x00000078&nbsp; r11: 0xa453001c&nbsp;&nbsp; r12: 0x000005f4&nbsp; r13: 0x00000000&nbsp; r14: 0x00000000&nbsp; r15: 0x00000001&nbsp;&nbsp; r16: 0x00000001&nbsp; r17: 0x00000000&nbsp; r18: 0x00000000&nbsp; r19: 0x00000000&nbsp;&nbsp; r20: 0x003fd270&nbsp; r21: 0x1776fb6d&nbsp; r22: 0x0000008c&nbsp; r23: 0x0030d524&nbsp;&nbsp; r24: 0x00000000&nbsp; r25: 0x0030d510&nbsp; r26: 0xa3f70fc0&nbsp; r27: 0x0030d510&nbsp;&nbsp; r28: 0x00000000&nbsp; r29: 0xbfffe7e0&nbsp; r30: 0x017df204&nbsp; r31: 0x017db35c...(way too long to post)[/code]</blockquote>

[QUOTE="hype.it, post: 44805, member: 4085"] New machine, new install... it's normal. It's only a serious worry if it happens on a regular basis. On a new machine with next to nothing installed, running the crons and permission is rather meaningless since nothing's been really running, hence not alot has been processed. Crons and permission only become messed up or corrupted when data and application get shifted about, like when it's been in uses. If you want a detailed explination as to why your machine had a kernal panic you can check the log files, located in: [b]User > Logs > CrashReporter[/b] Just double click on each file and it'll open. Your system records just about every action into this useful log, that can be used for debugging. For example (my last reported system crash) [code]********** Host Name: xxxxxxxx.netvigator.com Date/Time: 2004-08-13 11:53:21 +0800 OS Version: 10.3.5 (Build 7M34) Report Version: 2 Command: SystemUIServer Path: /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer Version: 1.2.1 (1.2.1) PID: 375 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000614 Thread 0 Crashed: 0 libobjc.A.dylib 0x908311ec objc_msgSend + 0xc 1 com.apple.menuextra.bluetooth 0x017db410 BluetoothPreferencesChanged + 0x1b8c 2 com.apple.Foundation 0x909f7184 _nsnote_callback + 0xb0 3 com.apple.CoreFoundation 0x901aa650 __CFXNotificationPost + 0x1b4 4 com.apple.CoreFoundation 0x901af060 _CFXNotificationPostNotification + 0x340 5 com.apple.Foundation 0x909f4fd0 -[NSNotificationCenter postNotificationName:object:userInfo:] + 0x74 6 com.apple.Bluetooth 0x93f72484 btNotificationDevicePublished + 0xf8 7 com.apple.framework.IOKit 0x9058e568 IODispatchCalloutFromCFMessage + 0x1b8 8 com.apple.CoreFoundation 0x901ad330 __CFMachPortPerform + 0xe0 9 com.apple.CoreFoundation 0x901a9ab4 __CFRunLoopDoSource1 + 0xc8 10 com.apple.CoreFoundation 0x90191980 __CFRunLoopRun + 0x540 11 com.apple.CoreFoundation 0x90195f1c CFRunLoopRunSpecific + 0x148 12 com.apple.HIToolbox 0x927d5f88 RunCurrentEventLoopInMode + 0xac 13 com.apple.HIToolbox 0x927dc6f0 ReceiveNextEventCommon + 0x17c 14 com.apple.HIToolbox 0x927fe6c8 BlockUntilNextEventMatchingListInMode + 0x60 15 com.apple.AppKit 0x92dd227c _DPSNextEvent + 0x180 16 com.apple.AppKit 0x92de8c24 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74 17 com.apple.AppKit 0x92dfcf8c -[NSApplication run] + 0x21c 18 com.apple.systemuiserver 0x0000afcc 0x1000 + 0x9fcc 19 com.apple.systemuiserver 0x0000ae34 0x1000 + 0x9e34 20 com.apple.systemuiserver 0x0000aca8 0x1000 + 0x9ca8 Thread 1: 0 libSystem.B.dylib 0x900074c8 mach_msg_trap + 0x8 1 libSystem.B.dylib 0x90007018 mach_msg + 0x38 2 com.unsanity.ape 0xc000a954 __ape_internal + 0x90b8 3 com.unsanity.ape 0xc0001328 __ape_agent + 0x40 4 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28 Thread 2: 0 libSystem.B.dylib 0x9000b20c select + 0xc 1 com.apple.CoreFoundation 0x90196ba0 __CFSocketManager + 0x1fc 2 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28 PPC Thread State: srr0: 0x908311ec srr1: 0x0000f030 vrsave: 0x00000000 cr: 0x44822484 xer: 0x00000004 lr: 0x017db410 ctr: 0x908311e0 r0: 0x017db410 r1: 0xbfffe350 r2: 0x0034ffdc r3: 0x06503c00 r4: 0x90893514 r5: 0x003fa470 r6: 0xbfffe4d0 r7: 0x00000004 r8: 0x00000003 r9: 0x00000000 r10: 0x00000078 r11: 0xa453001c r12: 0x000005f4 r13: 0x00000000 r14: 0x00000000 r15: 0x00000001 r16: 0x00000001 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000 r20: 0x003fd270 r21: 0x1776fb6d r22: 0x0000008c r23: 0x0030d524 r24: 0x00000000 r25: 0x0030d510 r26: 0xa3f70fc0 r27: 0x0030d510 r28: 0x00000000 r29: 0xbfffe7e0 r30: 0x017df204 r31: 0x017db35c ...(way too long to post) [/code] [/QUOTE]

Verification

Name this item. 🍎