Kernel Panics

[LPZ]

I still get something when I search using the terminal command attached.

I'm hoping to find the last strands of the Tether kexts and hopefully be panic free.

Perhaps you should reboot and then try

kextstat -b com.quark.driver.Tether64

again.

Unfortunately, your panic is not related to Tether. The very first panic log in the thread I linked to in my last post is essentially the same as yours, and nothing related to Tether is loaded there. In fact, the only loaded extensions in that report are Apple extensions.

It appears there's a bug in com.apple.driver.AirPort.Atheros40 that is exposed when lots of data is flowing through the wifi connection.

 

[MrNomNoms]

I'm not sure if you're referring to blackberry tethering or iPhone tethering, but I bought Tether because it was a one time fee of $14.99 vs the $20 or so a month through AT&T or Verizon.

Ok, I was unaware that you were in the US given that were I live I can tether it to my computer without any additional costs.

Seems unrelated to the OP's problem. Didn't see anything in that thread about kernel panics.

I'm now convinced this is a driver bug, and has nothing to do with com.quark.driver.Tether64. Please see this thread.

The reason why I keep coming back to com.quark.driver.tether64 is because I've got an iMac with an Atheros Wifi chip using the same driver and I have yet to experience the same issue which leads me to wonder whether it is related to memory (faulty module?), the Atheros chip itself or some software conflict in the equation. I keep seeing, "I upgraded to Lion" which leaves me asking whether they upgraded or whether they did a clean install - if they did upgrade have they tried to do a clean install instead?

 

[LPZ]

wonder whether it is related to memory (faulty module?), the Atheros chip itself or some software conflict in the equation.

Memory was the first thing I asked about too. The OP ran a memory test and found no problems.

Sure seems like some sort of buffer overflow bug in that driver, exposed under heavy data transfer. But I'm certainly no expert.

 

[MrNomNoms]

Memory was the first thing I asked about too. The OP ran a memory test and found no problems.

Sure seems like some sort of buffer overflow bug in that driver, exposed under heavy data transfer. But I'm certainly no expert.

I had a look through the Apple Forum and it appears to affect non-Atheros drivers too - maybe it is further up the Wifi stack given that it is made up of multiple components these days.

Hopefully 10.7.3 in still development and we'll see the issue being addressed.