Kernel Panic, Can You Inspect This Log File?

dstranathan

This was found in my SecurityAgent.crash.log after I rebooted from a panic:



--------------------------

Date/Time: 2003-01-22 19:46:11 -0600

OS Version: 10.2.3 (Build 6G30)

Host: TiBook-667.local.



Command: SecurityAgent

PID: 428



Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000



Thread 0:

#0 0x90073c48 in mach_msg_trap

#1 0x90005f90 in mach_msg

#2 0x90148b10 in __CFRunLoopRun

#3 0x90180fe4 in CFRunLoopRunSpecific

#4 0x969a36a0 in RunCurrentEventLoopInMode

#5 0x969b34c8 in ReceiveNextEventCommon

#6 0x969da584 in BlockUntilNextEventMatchingListInMode

#7 0x9308d8ac in _DPSNextEvent

#8 0x9309fb04 in -[NSApplication nextEventMatchingMask:untilDate:inMode equeue:]

#9 0x930b15e4 in -[NSApplication run]

#10 0x0000af30 in 0xaf30

#11 0x0000b2f0 in 0xb2f0

#12 0x0000b170 in 0xb170



Thread 1 Crashed:

#0 0x92be298c in _ZN8Security12MachPlusPlus17MachRunLoopServer20cfI nvalidateCallbackEP12__CFMachPortPv

#1 0x9015ee40 in CFMachPortInvalidate

#2 0x9015f778 in __CFNotifyDeadMachPort

#3 0x9015be4c in __CFMachPortPerform

#4 0x9015bcb8 in __CFRunLoopDoSource1

#5 0x90148dbc in __CFRunLoopRun

#6 0x90180fe4 in CFRunLoopRunSpecific

#7 0x90148360 in CFRunLoopRun

#8 0x01ea6320 in -[MyCameraCentral wiringThread:]

#9 0x9081cd38 in forkThreadForFunction

#10 0x90020d48 in _pthread_body



Thread 2:

#0 0x90014d28 in syscall_thread_switch

#1 0x907f4304 in +[NSThread sleepUntilDate:]

#2 0x93081694 in -[NSUIHeartBeat _heartBeatThread:]

#3 0x9081cd38 in forkThreadForFunction

#4 0x90020d48 in _pthread_body



PPC Thread State:

srr0: 0x92be298c srr1: 0x0000d030 vrsave: 0x00000000

xer: 0x00000000 lr: 0x92be2984 ctr: 0x90000ee0 mq: 0x00000000

r0: 0x92be2984 r1: 0xf005f580 r2: 0x24002288 r3: 0x00000000

r4: 0x00002603 r5: 0x00000000 r6: 0x00000003 r7: 0xa1b1c1d3

r8: 0x00000000 r9: 0x018c765c r10: 0x92ba22ac r11: 0xa00046fc

r12: 0x90000ee0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000

r16: 0x00000001 r17: 0x00000000 r18: 0x24002280 r19: 0x00000000

r20: 0x00005603 r21: 0x00000000 r22: 0x018c8ae8 r23: 0xf005fc94

r24: 0x00000024 r25: 0x00000000 r26: 0x00002603 r27: 0x00000000

r28: 0x000e44f0 r29: 0x018c9760 r30: 0x00000000 r31: 0x92be28c4



--------------------------



Any ideas?

paul

send it to apple

scott

FYI ...





If you're going to post this stuff using the [code][code][ /code]</pre><hr></blockquote> tags



That was this [code] </pre><hr></blockquote> is not this







[ 01-22-2003: Message edited by: Scott ]</p>

scott

WTF? I can't get it right. Post whatever you want

rogue27

how do you send those logs to apple, and where are they found?

chucker

Were you running iPhoto?

dstranathan

[quote]Originally posted by Chucker:

<strong>Were you running iPhoto?</strong><hr></blockquote>



Nope, not running iPhoto. I get the panic almost every day now. I usually am running a comconation of these fave apps:

A web browser (IE or Safari these days)

MTNewsWatcher

Mail.app

Yahoo Messenger or AIM

GraphicConverter

Transmit

Terminal

QT 6.1



I haven't upgraded any of those apps in a long time, except QT 6.1.

scott

Check the reports on Keynote crashing with some graphics cards. See if that matches your set up. My thinking is that Keynote crashes for some, which uses quicktime/openGL, and you running QT maybe ...

dstranathan

[quote]Originally posted by Scott:

<strong>Check the reports on Keynote crashing with some graphics cards. See if that matches your set up. My thinking is that Keynote crashes for some, which uses quicktime/openGL, and you running QT maybe ...</strong><hr></blockquote>



Yes, it was QT related! It was a 3rd party QT extension called MacCam! I found it! :0)



woOt!