I've been battling random kernel panics since I got my MB. I figured it was my 3rd party RAM but memtest after memtest turned up nothing. I swapped chips, ran tests, everything and still get on average one per day. I finally figured out that OSX logs the panics and here is what every one in the log says:
Thu Feb 23 18:29:02 2006
panic(cpu 0 caller 0x0019CACE): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
Sure. Here is the log. They all appear to match this most recent example. I can't think of anything. Sometimes I'm just sitting online idling. Yesterday it happened when I booted up and had just got to the desktop.
I've been having kernel panics also. I think I've tracked it down to the Apple Airport Card. I have been using my (one week old) MacBook Pro all day today plugged into ethernet no problems. Over the weekend it kernel paniced 9 times at home before I gave up on using it. I use an an Apple Airport hub at home. I am ordering a replacement AirPort card today. I'll see if that fixes it.
I see these every time I try to use Airport.
Sometimes it happens when I am working but it always happens if I leave the machine for a couple of hours without sleeping it.
Any suggestions?
I'm convinced there is a problem with the wireless driver. My panic.log looks just like that. I've gotten them right at boot when associating...sometimes it goes days. It's not heat. It's not memory.
What type of security is everyone using? I'm using WPA-PSK.
I too suspect the driver and see the same behavior. Sometimes it happens once a day or once a week or maybe twice in the same day. I'm on a consumer level NetGear 802.11g MAX Range router using WPA personal. My Airport 802.11b at home never gives me a panic.
The last thing I changed was to disable Appletalk support in Network preferences. It's a total guess, but my finger's crossed that might help.
After that I'm going to try rolling back to 10.4.5 to see if it was introduced by 10.4.6 (which is something I suspect).
After that I'm going to try rolling back to 10.4.5 to
see if it was introduced by 10.4.6 (which is
something I suspect).
I have had this issue since first receiving MacBook. Certainly occured prior to 10.4.6 for me.
AppleCare wants me to take machine in but it is clear from talking to them that they have no idea of the problem so I am quite reluctant to give up the machine without some prospect of resolution.
Same problem here...
Has anyone successfully returned its MacBook Pro to AppleCare and/or changed the Airport card ; or does it seems to be a software issue (bad driver) ?
My panic logs look the same on a 10 day old machine. I initially thought it was wireless-related, because panics occurred using Airtunes and Safari. I have moved to a new location with an all-Airport network, still getting panics. Turned off the Airport card to gain stability while talking with AppleCare, and got a panic while trying to save the panic.log to send to AppleCare.
Well, disabling AppleTalk had no effect as the crash just happened again. Not surprising, but it would have been nice.
I know it happened prior to 10.4.6 for you, but I might try going to 10.4.5. But before that I think I'll log every tcp packet with tcpdump to see it there's a particular network message causing it.
I'm going to try calling AppleCare too, but I share your fears about sending in a machine for 5-7 days with no resolution. Don't know what else to do though.
