Q: Kernel Panic in Lion

I know this is responding to an old post, but we have the exact same issue at the school I work for.  We purchased about 30 mid-2011 iMacs and none of them work wirelessly without Kernel Panics before the login screen.  We too had to disable the wireless in order to have them work properly.  We are running them on Snow Leopard 10.6.8 currenty because we have not migrated to Lion (we are this summer).

I have scoured the web and Apple GSX for anything about this issue and have not found anything but angry forum posts.  Have you found another solution or fix for this?

Thank you for any information.

I had this same problem; it ended up being specific to my Belkin N router. I switched to the latest Airport Extreme router, and the problem went away.

Unfortunately we've just spent £90,000 upgrading our network to an enterprise-level wireless system, so buying an Apple router certainly isn't the fix I'm looking for.

So far I've done everything suggested anywhere regarding this issue (using the next utility to swap the .kxt file for the snow leopard version being the last thing I've tried), but we still have 40 Macs in a classroom which aren't able to have their wireless cards enabled without them crashing instantly. Ironically, the windows 7 bootcamp partition works flawlessly on the wireless network on every single one of them. It's a total joke.

Add this to the whole situation with Logic, education licences and the App Store and despite me being the Mac technician at work, I'm talking most departments out of buying Macs for the new academic year. They just aren't suitable for network use any more. Even without this wireless issue none of the Lion Macs will bind to an Active Directory network.

Anyway, I'm going off topic but I'm watching this thread with interest. I hope the next Lion update will make me eat my words, but I'm not holding my breath.

You might want to start troubleshooting using wireless on a base install of Lion. If you still get kernel panics start a separate thread detailing the steps you've taken to troubleshoot. People here who have the most experience tend to not read pages long threads. Even if no one can help here you will be in a must stronger position to have your problem addressed by Apple engineering.

It is seldom a good idea to expect that any issue will be fixed in an upcoming update if Apple doesn't have solid data for the specifics, particularly for wireless issues when there never seems to be a single silver bullet that works for everyone.

Already done it.  Wiped one of the offending Macs, fresh install of Lion.  Everything works until literally the instant you hit Enter after putting in the wireless network password. Bang - kernel panic.   It happens so quickly the wireless network manager software doesn't even pick up that it connected (I was trying to catch what sort of data, if any, was being transferred - I've got a feeling it's something to do with the Mac trying to connect to iCloud/search for AirDrop target machines/whatever else Lion tries to connect to...).  After the restart it kerel panics on virtually every reboot unless you boot in safe mode or into the Windows partition.

I've sent a report to Apple after every reboot - they must have hundreds from me alone!

You can use the developers' bug reporting system for free using the same Apple ID you use here although you have to register separately. That will at least open a direct dialog with Apple engineers about your problem which just automatically sending in the panic reports don't do. Be very detailed about your hardware and what steps have failed to resolve the problem.

Alternatively, you can call Apple for help. If they can't fix your problem you can ask them to file a bug report from their end.

You could also try here by posting a new topic. Many of the most experienced people here simply don't look at these long threads. The causes of kernel panics are usually very specific to particular hardware and/or OS X installation and the same goes for wifi issues. Post a panic log, details about all the hardware involved and all the steps you have already taken that have failed to solve your problem.

My issue was similar to Martin's. I have a mid-2010 iMac with the Intel i7 quad-core CPU. I was having all kinds of kernel panic messages, which is a productivity-killer. I wiped everything, did a clean install of OS X Lion (from a USB drive) and started having panics again. I turned off the WiFi (Airport) and have not had a lick of trouble since then (two days ago- wish me continued good fortune). What a pity that Apple's driver is junk. I say this because when I boot Win7, I have no issues at all.

Also having the same problems with my brand new 27" 2011 iMac, bought last december with Lion pre-installed. Right out-of-the-box I had problems with the wi-fi dropping the data connection (randomly, sometimes every 5 minutes, sometimes twice a day) which can always be fixed by turning wi-fi off and on again. Sometimes I get the same Kernel panics, referring to Atheros drivers. I submit them to Apple every time.

Really hurting my workflow overhere and not expected to find such a long thread overhere without any response from Apple.

Apple, please do something about this! (BTW, all my other Apple devices (iPhone 3GS, iPad, 2008 MacBook on Snow Leopard) work perfectly with the same connection. Also tried different brands/types of routers, same thing.))

And here's a sample of one of the kernel panics that I got out-of-the-box with a 2011 27" iMac (frequently dropping wifi and sometimes generating these kernel panics related to Atheros drivers somehow):

Panics Since Last Report:          2

Tue Jan 10 11:21:33 2012

Panic(CPU 2): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0

RAX: 0x00000000ffffffff, RBX: 0x0000000000002710, RCX: 0x0000000000007000, RDX: 0x0000000000000001

RSP: 0xffffff8080c5bc8c, RBP: 0xffffff8080c5bc90, RSI: 0x0000000000007000, RDI: 0xffffff806bef2004

R8:  0xffffff807a65d2c8, R9:  0x0000000000000000, R10: 0x8000000000100000, R11: 0xffffff80002d8200

R12: 0x0000000000007000, R13: 0xffffff806bef2004, R14: 0x0000000000000066, R15: 0x0000000000000000

RFL: 0x0000000000000292, RIP: 0xffffff7f80f3e7b7, CS:  0x0000000000000008, SS:  0x0000000000000000

Backtrace (CPU 2), Frame : Return Address

0xffffff807a70ff50 : 0xffffff80002c781c

0xffffff807a70ff80 : 0xffffff80002c2790

0xffffff807a70ffd0 : 0xffffff80002d7bd2

0xffffff8080c5bc90 : 0xffffff7f80f1c94a

0xffffff8080c5bcf0 : 0xffffff7f80f66dee

0xffffff8080c5bd10 : 0xffffff7f80f67b24

0xffffff8080c5bd30 : 0xffffff7f80f67f0f

0xffffff8080c5bda0 : 0xffffff7f80f167a7

0xffffff8080c5be20 : 0xffffff7f80f0fc94

0xffffff8080c5be60 : 0xffffff7f80f40295

0xffffff8080c5be80 : 0xffffff7f80f0bcbd

0xffffff8080c5bec0 : 0xffffff7f80ecc542

0xffffff8080c5bef0 : 0xffffff8000639966

0xffffff8080c5bf30 : 0xffffff80006386e0

0xffffff8080c5bf70 : 0xffffff8000638584

0xffffff8080c5bfb0 : 0xffffff8000820057

      Kernel Extensions in backtrace:

         com.apple.driver.AirPort.Atheros40(501.58.1)[13BE9AFD-5158-3CD9-B5E9-AAF5BE3062 B4]@0xffffff7f80ead000->0xffffff7f80fecfff

            dependency: com.apple.iokit.IOPCIFamily(2.6.7)[6D54F06A-46B7-37FC-AF22-DE68DC18A1A3]@0xffff ff7f80862000

            dependency: com.apple.iokit.IO80211Family(411.1)[BF69D46E-3F5C-35C5-8167-9F872E3B20AA]@0xff ffff7f80e75000

            dependency: com.apple.iokit.IONetworkingFamily(2.0)[025587B0-DC55-3E39-A129-51843993A0AB]@0 xffffff7f80950000

      Kernel Extensions in backtrace:

         com.apple.driver.AirPort.Atheros40(501.58.1)[13BE9AFD-5158-3CD9-B5E9-AAF5BE3062 B4]@0xffffff7f80ead000->0xffffff7f80fecfff

            dependency: com.apple.iokit.IOPCIFamily(2.6.7)[6D54F06A-46B7-37FC-AF22-DE68DC18A1A3]@0xffff ff7f80862000

            dependency: com.apple.iokit.IO80211Family(411.1)[BF69D46E-3F5C-35C5-8167-9F872E3B20AA]@0xff ffff7f80e75000

            dependency: com.apple.iokit.IONetworkingFamily(2.0)[025587B0-DC55-3E39-A129-51843993A0AB]@0 xffffff7f80950000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

11C74

Kernel version:

Darwin Kernel Version 11.2.0: Tue Aug  9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64

System model name: iMac12,2 (Mac-942B59F58194171B)

Exactly the same problem here: With Snow-Leopard installed my 2011 iMac losses connection to the wifi-network every few hours and now with Lion my Mac regulary crashes.

Im very disappointed because Apple obviously has done nothing yet to fix it

I too have this problem. A brand you iMac, worked for a few days and now it always crashes during start up. Seems to be a problem with the Airport.Atheros drivers. I get the same kernal panic message as dutchipoduser, every single time I turn the computer on.

Hi, having similar issues to a lot of people in this thread, 2011 iMac, infrequent kernel panics and a lot of wifi drops. I've performed the Atheros kext rollback (4.0->3.2 I believe) but it hasn't helped at all, slightly worse if anything. My question is, how do I reverse this procedure? I thought I backed the Lion kext up somewhere, but I can't find it . I have the Lion installer, is it in there somewhere? Will 10.7.3 update automatically restore it? Does anyone have a download link?

Managed to locate my original 80211 kext, thanks.

dutchipoduser wrote:

 

Also having the same problems with my brand new 27" 2011 iMac, bought last december with Lion pre-installed. Right out-of-the-box I had problems with the wi-fi dropping the data connection (randomly, sometimes every 5 minutes, sometimes twice a day) which can always be fixed by turning wi-fi off and on again. Sometimes I get the same Kernel panics, referring to Atheros drivers. I submit them to Apple every time.

 

Really hurting my workflow overhere and not expected to find such a long thread overhere without any response from Apple.

 

Apple, please do something about this! (BTW, all my other Apple devices (iPhone 3GS, iPad, 2008 MacBook on Snow Leopard) work perfectly with the same connection. Also tried different brands/types of routers, same thing.))

In addition to the above I've tried:

- the kext downgrade (and reverted) -> didn't work

- adding other DNS servers (as suggested on some forums as a temp fix) -> didn't work

- adding an additional 'location' to the network panel (as suggested by some) -> didn't work

- doing a SMC reset -> didn't work

- updated to the recently available Airport Utility 6.0 -> really hoped this would fix it but no...

In fact my problems have became far worse... now my connection drops continiously almost, making work impossible. (* and to think I bought this one for a more stable dedicated workstation next to my windows desktop *) Also, next to the occasional kernel panic described in my previous post I now have frequent freezing desktops with no normal warning message, after which I can only force the whole thing to turn off using the power button.

I'm getting really desperate here... almost want to buy a long LAN cable tomorrow to run through my room or buy an additional USB Wi-Fi adapter to fix these issues, but I somehow refuse to give into this regarding I've just bought a 1600+ euro systems mainly to avoid these kind of things...

Anyone any additional tips?

I hoped so much that there will be a fix for our problem in the new 10.7.3-Update. But that was an Illusion: My iMac freezed with a Kernel-Panic a few minutes ago and now I'm really pi*** off!

Apple is leaving us alone with our problem and they can't say, that they're not recognizing the problem, because I (and most of the other people with the same issue i guess) send an Error-Report to Apple every time the Error occures.

It's a very bad joke, that runnig the iMac with Windows, is the only way to work with a stable system using W-Lan.

Maybe it's time to switch back to Windows completely.