Kernel Panic - network related?

I get a Panic whenever I run Mail on OSX whilst running Parallel - it seems like checking mail, or doing other network-intensive things, caused a kernel panic in OSX.

Anyone else getting this a lot?

imac Core Duo 20", 2GB Ram, 256mb Video Card

 

Same here, using ICQ or try to share file.

imac 17, 1,5 g of ram.

 

i am having the same issue here.

first i thought it was related to OmniOutliner, because it crashed twice while i tried to print from it to a network printer, but i then realized while i way doing that Parallels was running windows update in the background.

After another crash i decided to let PW to finish windows update first, but it crashed with the same IONetwork kernel panic right after i started installing SP2


thanks
i

 

It seems to happen whenever the Mac is doing a lot of network activity, whether on the OSX or Windows side.

I've caused it to happen when the Windows side is just idling, but I've just booted Mail under OSX, or opened Safari, for example.

Any developer care to comment?

 

Me too. I installed XP without problems, but when I clicked on the workgroup in My Computer's folder pane, it panicked - and after restarting the machine, it panicked immediately when I started the virtual machine.

 

I see this panic already.
We fix this in next version, can you tell me which guest you use and which network interface (ethernet or airport).
The panic is sounds like a "free freeing mbuf". Is this right then we known about this, but else please send error reports to us (use [email protected] for this)

 

I'm using Windows 2000 with SP4, via ethernet, on an iMac 2.0Ghz with 256mb vram and 2GB ram.

Will I have less problems if I use the airport for networking instead of ethernet? I can use either at this location. Thanks for the response, and good luck with the fix!

By the way, tell me how to check what caused the panic and I'll do so - is there a log I can check or something?

 

Looks like this is invalid IOKit usage in driver or bug in IOKit. Anyway you can try to use airport.
Also can you tell version of your OS X.

 

OS X 10.4.6, Build 8l1119

Are there any other issues that cause kernel panics I can try to avoid, aside from network matters?

And is there any reason why using airport should avoid kernel panics - I have to say the constant panics are driving me nuts and I don't want to crash my machine again

 

This is another type of interface with another drivers and logick. But if you don't want to crash you host, you can wait a little while we release another beta-version.

This bug have a highter priotiy !

 

That's my panic. Windows XP SP2 guest, OS X 10.4.6 with Boot Camp installed, MacBook Pro 2 GHz/1 GB/100 GB disk, Ethernet. (My Airport isn't reliable: for some reason, it keeps dropping the connection with my home access point - but no others.)

I'll try the next release. Right now, I'm using Disk Utility to repair my boot volume after the last panic.

 

I saw a panic as well. It was while logging in. The other issue is I noticed that the CAPS lock isn't recognized properly most of the time.

Thu Apr 6 16:15:37 2006
panic(cpu 0 caller 0x0034FC40): freeing free mbuf
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x145cb934 : 0x128b5e (0x3bbeb8 0x145cb958 0x131bbc 0x0)
0x145cb974 : 0x34fc40 (0x3db934 0x263d1f00 0x145cb9a4 0x26301d00)
0x145cb994 : 0x34ffe7 (0x26301d00 0x321303f 0x6 0x26301d00)
0x145cb9b4 : 0x2a63c983 (0x26301d00 0xe 0x145cb9f4 0x145cba64)
0x145cb9f4 : 0x1f7240 (0x3594a04 0x26301d00 0x2 0x145cba64)
0x145cba54 : 0x227af5 (0x3594a04 0x2 0x26301d00 0x49c5c04)
0x145cbb94 : 0x230681 (0x263d1f00 0x0 0x0 0x145cbc00)
0x145cbc44 : 0x22d671 (0x0 0x263d1f34 0x263d1f48 0x263d1f00)
0x145cbe14 : 0x222007 (0x263d1f00 0x14 0x3c 0x196c9f)
0x145cbe54 : 0x223a8b (0x263d1f00 0x14 0x6 0x0)
0x145cbf64 : 0x211109 (0x263d1f00 0x263d1f00 0x42cb5c 0x498038)
0x145cbfa4 : 0x1f773d (0x3594a04 0x263d1f00 0x263d1f34 0x19c183)
0x145cbfd4 : 0x197a21 (0x0 0x0 0x2e57278 0x134aec) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IONetworkingFamily(1.5.0)@0x2a632000

Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386

Hope this helps.

J

 

I've switched to using Airport and haven't had a single kernel panic now - looks like its the ethernet interface for sure.

 

Thank you for this !

 

I thought airport was not supported, but only wired ethernet?

 

If you click on Network Adapter on the properties page (the VM must be powered off to change this), you can select en1 instead of en0. This will switch to your Airport adapter. I've made the switch on my MacBook Pro, and am reinstalling XP on it now. I'm not going to be able to do much with it this way due to Airport problems, but at least I can get the reinstall out of the way.

 

Also having the same problem

Just wanted to add my experience too. I have been using Win2K under OSX, and I've had two kernel panics, both seemingly related to the network IO.

Otherwise, great product! When it is released I will be purchasing it!

 

I'm running purely with airport and running many different programs. No panics yet for me.

 

I have experienced a kernel panic as well. Sent the report to Apple, but I didn't save it. Next time it happens I'll forward it to you guys. Here are the details of what was happening:

Was inside Windows 2000 VM trying to use the network... realized my ethernet wasn't plugged in. So I plugged it in, opened a command prompt and did a "IPCONFIG /RENEW" and then blamo! big kernel panic. OS X was doing other network activity at the same time, but using the Airport card. The VM was configured to use only en0 Ethernet. It's possible Win2k was trying to get a DHCP address already when I manually issued the command. But with a kernel panic it's a hard reset and quite nasty, since we lose all data on open documents. Not nice for a userland application to cause a kernel panic...

Details: MacBook Pro with Parallels beta for OS X; Windows 2000 SP4 with all updates.

 

It is supported, but you have to change the interface from en0 to en1 before you start the VM. Can't do it while the VM is running. You can also use Airport for OS X and wired Ethernet with VM like I was doing, but I did get one kernel panic as mentioned in the previous post.