PDA

View Full Version : Multiple kernel panics...


gfroyle
May 24, 2004, 09:07 AM
Hi,

I am running 10.3.3 on a 1.25PB15 and have been having intermittent problems with repeated kernel panics, often several in a row. Searching on the Internet today, I learned about "panicdump" which somehow managed to create the file /Library/logs/panic.log.

I don't understand much about the technical details inside this file, but there was something repetitive about each entry - they all had the *same* list of "kernel loadable modules" with every single one of them mentioning "com.apple.iokit.AppleAirPort2(3.4.1)". (I have included a short extract at the end of this message)


At home, I use the computer wirelessly all the time and now that I think back, I don't think that I have ever had a kernel panic while "wired".

Has this happened to anyone else? Should I report it to Apple and if so how?

Thanks

Gordon

------ Sample extract from panic.log -------


Mon May 24 21:23:45 2004




Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x000000001C13E008 PC=0x00000000004154D4
Latest crash info for cpu 0:
Exception state (sv=0x206D9000)
PC=0x004154D4; MSR=0x00149030; DAR=0x1C13E008; DSISR=0x40000000; LR=0x00426D5C; R1=0x11F43D30; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0019FA24 0x00426D5C 0x002617FC 0x002606DC 0x00260640
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(3.4.1)@0x3e6000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x38d000
dependency: com.apple.iokit.IONetworkingFamily(1.4.0)@0x3c9000
Proceeding back via exception chain:
Exception state (sv=0x206D9000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x25A82280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC


panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
Backtrace:
0x000834B8 0x0008399C 0x0001EDA4 0x000909C0 0x00093C8C
Proceeding back via exception chain:
Exception state (sv=0x206D9000)
PC=0x004154D4; MSR=0x00149030; DAR=0x1C13E008; DSISR=0x40000000; LR=0x00426D5C; R1=0x11F43D30; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0019FA24 0x00426D5C 0x002617FC 0x002606DC 0x00260640
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(3.4.1)@0x3e6000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x38d000
dependency: com.apple.iokit.IONetworkingFamily(1.4.0)@0x3c9000
Exception state (sv=0x25A82280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

IJ Reilly
May 24, 2004, 11:47 AM
Try running the Hardware Test CD looking especially for RAM problems. Even if it passes the RAM test, try removing whatever RAM you can and running it the PB that way for a while. A surprising number of these problems can be traced to bad RAM.

rogerw
May 24, 2004, 01:43 PM
what is a kernal panic?

Mord
May 24, 2004, 03:30 PM
like blue screen but less common

FuzzyBallz
May 24, 2004, 05:22 PM
LOL, less common... I've seen more instances of kernal panic on a Mac then blue screen on a PC. But then again, it's not on my Mac, and it's my PC. User error, always.

Get Disk Warrior for Mac and run it on your system. Your kernal panic could just be simple corrupted system files, DW will fix it easy.

Macmaniac
May 24, 2004, 06:24 PM
Run some hardware tests, run diskwarrior, try system works as well, also try pulling one stick of RAM and seeing how things run, if it still KP's try the other stick of RAM, if the problem continues and you have run various utilities your logic board may need to be replaced, however this is a last resort.

gfroyle
May 24, 2004, 08:08 PM
Thanks for the feedback.

I am aware that faulty RAM is a possible cause of kernel panics, and I *do* have a 512Mb stick replacing one of the original 256s (it was pre-installed by the reseller so its not a botchy self-install). I have no other peripherals, or third party antiviral software or anything like that permanently attached/installed.

BUT - and I am speaking from ignorance here - I would naively imagine that faulty RAM would cause pretty much random kernel panics... and I was hoping to use the panic log information to narrow down the possibilities before I go back to first principles and start hauling out sticks of RAM etc.

I also have a Windows XP machine and while I have frequent program crashes, Microsoft have (finally) done a good job of catching them (and they pop up a little "do you want to report this error to Microsoft" box) before they crash the entire system! So I don't get the BS of D any more and would really like to not get the dreaded "You need to restart your computer" any more. I would rather get a little "Do you want to report this error to Apple" box so that at least some statistical information was being collected..