I made the mistake of downloading Lion the day it was available from the app store. Thanks to your posts and conversations, and after many kernal panics on my dual quad MacPro, I've decided to disable my wi-fi airport during my production times. I hope from your posts I can avoid these kernal panics until Apple does something about them.
I'm having the same issue of repeated kernel panics, but the causes are inconsistent. The last one reported problems with the Nvidia driver, and after the reboot I was able to use it for about 2 minutes before getting
Kernel Extensions in backtrace:
when I tried to connect my magic mouse. Unfortunately I don't think this is an airport/wi-fi problem.
Found out it was Elmedia was the culprit...
Here is the solution:
Elmedia Player crashes Lion even though the app is not open. When viewing video (in Chrome, Safari or Quicktime) an Elmedia Player process triggers a crash. If you've ever installed Elmedia Player then you need to remove it from your system in a few places in order to prevent system crashes on Mac OS 10.7. I originally thought this was a bug in Google Chrome because the crashes seemed to occur while using Chrome. Thanks to the crash logs (viewable in Console under /Library/Logs/DiagnosticReports) I was able to see a pattern of repeat offenders, primarily the following failure:
Kernel Extensions in backtrace:
BSD process name corresponding to current thread: kernel_task
Steps to resolve:
1) Browse to your applications folder - Delete Elmedia Player
2) Browse to the following location and delete this file - System/Library/Extensions/ElmediaPlayer.kext
3) Browse to the following location and delete this file - username/Library/LaunchAgents/com.eltima.ElmediaPlayer.plist
Hope this helps someone else. Cheers!
If the help already provided does not rapidly resolve or work around the issue, some long shots.
Do you have any USB-attached devices?
Do you use any third party sensing software, such as iStat Menus or Little Snitch? Anything third party that might monitor network traffic or disk input/output?
(I'm not suggesting that you should add such things to the mix. Rather, I wonder whether such things might be contributory to the issue.)
I think I've fixed my WI-FI problems, at least its been up for two days without a kernel panic and heavy wi-fi use.
Instead of trying to upgrade again I reformatted my drive and reinstalled a fresh copy from the DMG. I also created a new account and copied everything but the Library folder back into my new account.
You can try reinstalling without formatting but make sure there are no permission problems before you start.
hope it helps....
Iomega USB device?
USB Device: USB to Serial-ATA bridge, 0x059b (Iomega Corporation), 0x0577, 0xfa140000 / 5
Kernel panics can be from any device anyway, so USB printer, driver, cable, etc and strip down so you don't have any peripherals other than basic.
Let me clarify my setup.
I unplugged any peripherals - didn't work
I did a clean install of Snow Leopard and then I installed Lion so no Little Snitch or other 3rd Party apps were installed - didn't work
I stumbled across this bug even before Lion came out. And then I tried all the solutions you guys already posted - clean installs and whatnots and nothing solved it. I thought by the time Lion would come out Apple would have solved this, with all the reports I (at least) sent them every 5 minutes of crashes....
The only thing that worked for me was, unfortunately, getting a 10m Ethernet cable and disconnecting my WiFi
So the download over wifi was bad to begin with? and a good install when using wired connection and Lion is stable?
There are some bugs and issues with wifi.
Thanks to The hatter and to h3yaz, the answers help me with hunches in another area.
Reproducibility with clean installations is most informative. We might check Open Radar to see whether for Build 11A511 anyone else has reported similar.
h3yaz, without breaking confidentiality (without answering here) ask yourself whether your iMac11,2 (mid 2010, according to MacTracker) was equally prone to kernel panics with clean installations of either of the following:
- Build 11A480b (seeded around WWDC time)
- Build 11A494a
… the reports I … sent …
For the unreleased operating system, did you use only the reporting that's integral to the system?
Or did any report gain an acknowledgement from Apple, with a reference (typically a number)? If confidental you probably should not share that number, but I'd like a better idea of your test environment. Depending on your answer, I might be able to offer you a bigger picture.