Hyper-Fan Kernal Crash - iMac G5
in [Mac Applications]
|
Prev: High Quality Seiko Watches Collection - Discount Seiko Watches
Next: How do I get MacCouponPrinter to work?
From: gtr on 17 Nov 2008 12:27 I'm using OS 10.5.5 on a 2.1 Ghz PowerPC iMac G5. Starting loosely 2 months ago once or twice a week, when I am not doing anything on the mac it is sleeping it goes into hyper-fan mode and will not respond to the keyboard. I reboot and it tells me I had a system crash and offers the report, which generally looks like the following. All is then find for another 3 to 5 days. I called Applecare and went through a host of diagnoses applications and found no problems in logic board, memory, video RAM, etc. Did a utility check from the original disks and found a minor disc error in the header and repaired it. That was Friday. It crashed this morning. Any guesses appreciated. The report looks like this: Sun Nov 16 22:04:12 2008 panic(cpu 0 caller 0x000AA860): timeout on attempt to acquire lock (0x03900A6C), value = 0x00000000 Latest stack backtrace for cpu 0: Backtrace: 0x0009B518 0x0009BEBC 0x00029DD8 0x000AA860 0x00074550 0x00364C48 0x00364D84 0x003652E8 0x003690C0 0x00365654 0x00365750 0x344A145C 0x344A1630 0x343CC398 0x343CC5DC 0x0003F94C 0x000B0654 Kernel loadable modules in backtrace (with dependencies): com.apple.iokit.IONDRVSupport(1.5.2)@0x34494000->0x344abfff dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0x343b3000 dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x29e54000 com.apple.iokit.IOGraphicsFamily(1.5.2)@0x343b3000->0x343d8fff dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x29e54000 Proceeding back via exception chain: Exception state (sv=0x29e05780) PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown) BSD process name corresponding to current thread: kernel_task Mac OS version: 9F33 Kernel version: Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC System model name: PowerMac12,1 -- Thank you and have a nice day.
From: gtr on 17 Nov 2008 16:55 On 2008-11-17 09:29:47 -0800, Jolly Roger <jollyroger(a)pobox.com> said: >> Any guesses appreciated. >> >> The report looks like this: >> >> Sun Nov 16 22:04:12 2008 >> panic(cpu 0 caller 0x000AA860): timeout on attempt to acquire lock >> (0x03900A6C), value = 0x00000000 >> >> Latest stack backtrace for cpu 0: >> Backtrace: >> 0x0009B518 0x0009BEBC 0x00029DD8 0x000AA860 0x00074550 >> 0x00364C48 0x00364D84 0x003652E8 >> 0x003690C0 0x00365654 0x00365750 0x344A145C 0x344A1630 >> 0x343CC398 0x343CC5DC 0x0003F94C >> 0x000B0654 >> Kernel loadable modules in backtrace (with dependencies): >> com.apple.iokit.IONDRVSupport(1.5.2)@0x34494000->0x344abfff >> dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0x343b3000 >> dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x29e54000 >> com.apple.iokit.IOGraphicsFamily(1.5.2)@0x343b3000->0x343d8fff >> dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x29e54000 >> Proceeding back via exception chain: >> Exception state (sv=0x29e05780) >> PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; >> LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown) >> >> BSD process name corresponding to current thread: kernel_task >> >> Mac OS version: >> 9F33 >> >> Kernel version: >> Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; >> root:xnu-1228.7.58~1/RELEASE_PPC >> System model name: PowerMac12,1 > > Any system or console log entries at or just before this time?: > > Sun Nov 16 22:04:12 2008 Fascinating question: I hadn't thought to look because poking around in there provides more questions than answers. I wasn't quite sure where to look, so looked at the system.log. I found the following. Do you see anything worthy of further exploration? Are there any other logs that would provide clues? I had no idea there WERE so many potential logs for investigation! Nov 16 22:03:59: --- last message repeated 4 times --- Nov 16 22:03:59 localhost kernel[0]: M-FW: M-Audio FireWire device found. Nov 16 22:03:59 localhost kextd[10]: 411 cached, 0 uncached personalities to catalog Nov 16 22:03:59 localhost kernel[0]: M-FW: FireWire bus reset completed. Nov 16 22:03:59 localhost kernel[0]: M-FW: In MakeAppleFWAudioGoAway:1 Nov 16 22:04:01: --- last message repeated 1 time --- Nov 16 22:04:01 localhost kernel[0]: M-FW: metanub 0x2E24800 GUID:d6c0b00995320 Nov 16 22:04:06 localhost DirectoryService[11]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:06 localhost mDNSResponder mDNSResponder-176.2 (Aug 15 2008 14:58:56)[16]: starting Nov 16 22:04:06 localhost mDNSResponder[16]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:06 localhost securityd[21]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:07 localhost configd[14]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:09 localhost kernel[0]: Sound assertion "1" failed in "AppleOnboardAudio/PlatformInterfaceI2C_PlatformFunction.cpp" at line 328 goto handler Nov 16 22:04:09 localhost kernel[0]: ^PSound assertion "!result" failed in "AppleOnboardAudio/PlatformInterface.cpp" at line 138 goto Exit Nov 16 22:04:09 localhost kernel[0]: ^PSound assertion "!mPlatformInterface->init ( provider, this, AppleDBDMAAudio::kDBDMADeviceIndex, mPlatformInterfaceSupport, irqEnableMask )" failed in "AppleOnboardAudio/AppleOnboardAudio.cpp" at line 3076 goto Exit Nov 16 22:04:09 localhost kernel[0]: ^PSound assertion "!result" failed in "AppleOnboardAudio/AppleOnboardAudio.cpp" at line 173 goto Exit Nov 16 22:04:09 localhost kernel[0]: ^P Nov 16 22:04:12 localhost cupsd[27]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:12 localhost bootlog[47]: BOOT_TIME: 1226901823 0 Nov 16 22:04:12 localhost DumpPanic[43]: Panic data written to /Library/Logs/PanicReporter/2008-11-16-220413.panic Nov 16 22:04:12 localhost rpc.statd[32]: statd.notify - no notifications needed Nov 16 22:04:12 localhost fseventsd[40]: event logs in /.fseventsd out of sync with volume. destroying old logs. (263462 29 278376) Nov 16 22:04:12 localhost fseventsd[40]: log dir: /.fseventsd getting new uuid: BB7C9E2E-2A58-4958-8007-FE35623268F2 Nov 16 22:04:12 localhost socketfilterfw[50]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:13 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:12 localhost hermesctl[52]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:14 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:13 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[35]: Login Window Application Started Nov 16 22:04:12 localhost mds[34]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:14 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:12 localhost M-Audio FireWire Device Helper[53]: MAudioFireWireHelper server: could not find server. You need to start one on this machine first. Nov 16 22:04:14 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:12 localhost M-Audio FireWire Device Helper[53]: starting Nov 16 22:04:15 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:14 localhost /usr/sbin/ocspd[67]: starting Nov 16 22:04:13 localhost M-Audio FireWire Device Helper[53]: started Nov 16 22:04:15 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:13 localhost lsd[54]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:16 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:13 localhost diskarbitrationd[44]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:16 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:14 localhost loginwindow[35]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:17 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:14 localhost CoreRAIDServer[45]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:17 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:14 localhost ifcstart[38]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:17 localhost kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55 Nov 16 22:04:18: --- last message repeated 2 times --- Nov 16 22:04:18 localhost ATSServer[75]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:23 localhost kextd[10]: writing kernel link data to /var/run/mach.sym Nov 16 22:04:23 localhost WindowServer[66]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:24 localhost kernel[0]: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex (PHY regs 5,6:0x45e1,0x0005) Nov 16 22:04:24 localhost configd[14]: AppleTalk startup Nov 16 22:04:24 Orson-4 kernel[0]: AirPort: Link Down on en1 Nov 16 22:04:24 Orson-4 configd[14]: setting hostname to "Orson-4.local" Nov 16 22:04:25 Orson-4 airportd[24]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35 Nov 16 22:04:25 Orson-4 kernel[0]: krb5kdc 59 FS_READ_DATA SBF /usr/share/icu/icudt36b.dat 13 (seatbelt) Nov 16 22:04:25: --- last message repeated 1 time --- -- Thank you and have a nice day.
From: gtr on 17 Nov 2008 19:59
On 2008-11-17 16:22:40 -0800, Jolly Roger <jollyroger(a)pobox.com> said: > Seems fairly probable to me that the driver for you M-Audio device is > malfunctioning, which may be causing the kernel panic. Perhaps the > driver is not handling sleep events properly. > > A couple Google searches for "M-Audio mac kernel panic" and "M-Audio mac > kernel panic sleep" found numerous reports of kernel panics related to > M-Audio devices; so I'd think you might want to contact M-Audio support > about this and send them the relevant logs and kernel panic info. Many thanks! -- Thank you and have a nice day. |