Kernel PANIC!

[TH-Gunner]

I was with a friend today, and his MacBook[2,1] kernel panicked. This is the first one I've ever seen with my own eyes. He says it happens every so often, and I'm determined to find out what the cause is. He says it happens every month or so, and he has reinstalled the OS several times before. Here's a log of the kernel panic:

Thu Sep 18 17:44:00 2008
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xc0aab3ff, CR3: 0x01eae000, CR4: 0x000006e0
EAX: 0xc0aab3cf, EBX: 0x8e0c53cf, ECX: 0x420a62d0, EDX: 0x0f6b6ba0
CR2: 0xc0aab3ff, EBP: 0x152abd28, ESI: 0x4209cba0, EDI: 0x136392c8
EFL: 0x00010202, EIP: 0x009c303d, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x152abae8 : 0x128d08 (0x3cb204 0x152abb0c 0x131de5 0x0)
0x152abb28 : 0x1a429b (0x3d0f1c 0x0 0xe 0x3d0740)
0x152abc38 : 0x19ada4 (0x152abc50 0x26c07800 0x1 0x1)
0x152abd28 : 0x99c1b7 (0x1375f004 0x4209cba0 0xf6b6ba0 0xc0aab3cf)
0x152abf08 : 0x39a533 (0x136392c8 0x3b6f480 0x1 0x36e680c)
0x152abf58 : 0x399705 (0x3b6f480 0x135eb4 0x0 0x36e680c)
0x152abf88 : 0x39943b (0x3b65040 0x3b83bc0 0x450 0x1203)
0x152abfc8 : 0x19ac1c (0x3b65040 0x0 0x10 0x0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x96b000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6ac000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7b0000

Kernel version:
Darwin Kernel Version 8.9.3: Fri Apr 27 14:50:07 PDT 2007; root:xnu-792.19.5~2/RELEASE_I386


*********

Are there any clues that someone could translate?

Thanks.

 

[Eidorian]

I'm going to say it's a hardware issue.

 

[Sun Baked]

A program like Azureus overloaded the Aiport buffer and crashed the machine.

Something like that, been a reoccurring problem for Leopard.

Some got it with Azureus, others with non Apple base stations.

For the people that kept on using Azureus, they just plugged into an ethernet hub.

---

Were some notes where turning off IPv6 worked for some people, and if you look there are a lot of people that had hoped 10.5.5 fixed the Airport issues.

 

[TH-Gunner]

I'm going to say it's a hardware issue.

Well... He said it happened the first week he got it. But a few months ago, his system started crashing so that it wouldn't boot, and he would have to reinstall the OS.

I know he uses the camera a lot, and that causes his temperatures to stay around 85˚C. He keeps it like that most of the time he's using it. My guess was that it was overheating. I told him to lay off of the camera for a while, and he says it hasn't crashed since.

But now that he's KPing again... I'm not sure whether to attribute it to permanent CPU damage or if it's whatever happened since that first week he had it (he's had it for a little over a year now).

A program like Azureus overloaded the Aiport buffer and crashed the machine.

Something like that, been a reoccurring problem for Leopard.

He does to limewire... But I'm pretty sure not Azuereus. And what do you mean by "overloaded the airport buffer?" All he had open was Safari where he was doing some online homework.

Also, he's running Tiger, not Leopard.

 

[Eidorian]

Well... He said it happened the first week he got it. But a few months ago, his system started crashing so that it wouldn't boot, and he would have to reinstall the OS.

I know he uses the camera a lot, and that causes his temperatures to stay around 85˚C. He keeps it like that most of the time he's using it. My guess was that it was overheating. I told him to lay off of the camera for a while, and he says it hasn't crashed since.

But now that he's KPing again... I'm not sure whether to attribute it to permanent CPU damage or if it's whatever happened since that first week he had it (he's had it for a little over a year now).



He does to limewire... But I'm pretty sure not Azuereus. And what do you mean by "overloaded the airport buffer?" All he had open was Safari where he was doing some online homework.

Also, he's running Tiger, not Leopard.

After that back story it sounds like it's time to use the warranty to get the hardware fixed.

 

[Peace]

Also, he's running Tiger, not Leopard.

There's the problem if the macbook is the late 2006 model. The one that introduced 802.11n with the "enabler" patch.
If it is install Leopard with all updates,firmware updates, airport updates.. You get the idea.

I can almost guarantee you that problem will go away.

If it's the early 2006 without 802.11n I'd venture to guess bad drivers or possibly hardware. Have you run any extensive tests on it?

 

[Sun Baked]

Still happens in Tiger v10+, there is a list of various things to try to get around it, including using the Airport Drivers from a version prior to 10.4.10

Should have said it was like a buffer overflow, but it isn't, happens more often when the connection was running full, or when a certain call was made -- aka, click here and boom.

 

[TH-Gunner]

There's the problem if the macbook is the late 2006 model. The one that introduced 802.11n with the "enabler" patch.
If it is install Leopard with all updates,firmware updates, airport updates.. You get the idea.

I can almost guarantee you that problem will go away.

If it's the early 2006 without 802.11n I'd venture to guess bad drivers or possibly hardware. Have you run any extensive tests on it?

It's a model from 2007, definitely, but I'm not sure what month. He got it in August of 2007.

I'll see if he's up-to-date with system updates.

Still happens in Tiger v10+, there is a list of various things to try to get around it, including using the Airport Drivers from a version prior to 10.4.10

Should have said it was like a buffer overflow, but it isn't, happens more often when the connection was running full, or when a certain call was made -- aka, click here and boom.

Would there be a fix for that? It has never ever happened to me since I've had my MacBook (June 2007). But then again, I take extra good care of mine (I have a much above average computer background).

 

[Peace]

It's a model from 2007, definitely, but I'm not sure what month. He got it in August of 2007.

I'll see if he's up-to-date with system updates.

Why is he running Tiger on it then ?

 

[TH-Gunner]

Why is he running Tiger on it then ?

Because Leopard came out in October of 2007, which is 2 months after he got his laptop.

Leopard has been tried on his system before, but it crashed and ruined the install, causing him to have to reinstall. He doesn't own Leopard, so he went back to his Tiger.