Why kernel panic when connecting to DHCP/Thunderbolt-Ethernet and Bluetooth Trackpad?

I called Apple and they very quickly suggested sending me a replacement Thunderbolt Ethernet Adapter. Its been ~two weeks with the new adaptor and no kernel panics. Looks like this may be as simple as a faulty adaptor. Still disconcerting that a faulty adaptor can crash my system, but that's a topic for a different day.

Hi,

That is remarkable. I figured since so many of us have problems when using this adapter, it would have to be related to a software issue. It's unlikely that there are so many faulty adapters. Reading back your previous post you had about 2 KP's a month. So 2 weeks is your average and we need some more time to establish that this in fact is a solution that works for you. Which, of course, I really hope will work out for you :-) Please keep us posted.

Note that "machine check" panics are most often hardware related.

Very strange. I had another KP today, just like the other ones I had before. But I don't use the Thunderbolt-Ethernet adapter anymore. I've run for over 4 weeks without KP's but today I had another one. Software running:

Sabnzbd, VLC (again!), Notes, Mail, Safari.

If it was another Machine Check panic, I'd be concerned about bad RAM.

Hi William, thank you for your reply and concern. I have two questions:

1. How do I recognise a Machine Check panic as such? Can I find it in a log?

2. Can I assess bad RAM myself or do I need to go to an Apple Service Provider?

Thanks!

There was one machine check panic in the tracebacks., as seen by:

panic(cpu 1 caller 0xffffff80044dca29): "Machine Check at 0xffffff7f865edba7

The panics due to the assertion failure:

panic(cpu 0 caller 0xffffff800b7ebe52): assertion failed: igi->igi_version == IGMP_VERSION_3, file: /SourceCache/xnu/xnu-2422.1.72/bsd/netinet/igmp.c, line: 3720

are due to a bug in Apple's IGMP code.

Notably this line of code is failing:

VERIFY(igi->igi_version == IGMP_VERSION_3);

Whether it's because the data structure is corrupt or it contains data from a previous version of IGMP and an assumption was made it was IGMP V3 data I couldn't tell you.

If you feel that you might have a RAM issue, this article gives a brief summary of ways to test your Mac's RAM.

Hi William, thank you for your reply, though I'm afraid it's too tech savvy for me. Today I had a different restart: a "Sleep Wake Failure". I didn't even know this was happening until I reopened the lid of my computer and it was restarting the applications that were open before.

This may still be software related. The AHT was fine, no errors. I've run without errors for about a month, so I may need to check which apps I added since then and try an older disk image.

Here is the Sleep Wake Failure log (or at least the start of it, I don't want to pollute this thread with endless lines of log). What seems strange to me is the date/time stamp.

-------------------------------------------------------------------------------- -

Date/Time: 2014-06-29 14:43:31 +0200

OS Version: 10.9.2 (Build 13C1021)

Architecture: x86_64

Report Version: 18

Event: Sleep Wake Failure

Steps: 62

Hardware model: MacBookPro11,3

Active cpus: 8

Powerstats for: kernel_task

Start time: 1970-01-01 01:00:00 +0100

End time: 1970-01-01 01:00:00 +0100

Microstackshots: 34 samples

Primary state: 34 samples Non-Frontmost App, Non-Background Priority, User mode

User Activity: 0 samples Idle, 0 samples Active, 34 samples Unknown

Power Source: 0 samples on Battery, 0 samples on AC, 34 samples Unknown

-------------------------------------------------------------------------------- -

Same here:

- Brand new machine

- Wireless + Ethernet = KP

- But also; it often panicked on its own, just sitting idle, while both were connected.

- For a week used only WiFi, no problem.

- For a week used only Ethernet, no problem.

- It only seems to happen at home

So I doubt it's the connector. Also, it happens IMMEDIATELY on connecting Ethernet when WiFi is on

This morning it happened while I was running Screen Sharing, which I use a lot. I tested this by shutting everything down then connecting both wifi then ethernet, then ethernet adding wifi several times without a problem. Launched Screen Sharing with WiFi, added Ethernet: immediate KP. Repeated it once, but the third time did not crash.

So my question: do any of you use Screen Sharing? Could that be part of the mix?

Just after finishing this post I set the laptop down, Screen Sharing was NOT running, (only Firefox, Mail, System Prefs) and it panicked out of the blue.

- I've gone two weeks without a panic using just WiFi or just Ethernet, but USING BOTH. So I don't think it's the adapter.

- It's crashed four times this morning, within 20 minutes, with WiFi and Ethernet connected. Three times when I made a change, once after about 5 minutes of both WiFi and Ethernet running.

Hello, same problem on my MBP early 2013. In my home network and only there it crashes after I connect my Thunderbold network adapter.

Wifi is always off.

Ethernet switch is: D-Link DGS-1008D

Router: AVM Fritzbox 7390

panic(cpu 0 caller 0xffffff801efef952): assertion failed: igi->igi_version == IGMP_VERSION_3, file: /SourceCache/xnu/xnu-2422.115.10/bsd/netinet/igmp.c, line: 3720

Backtrace (CPU 0), Frame : Return Address

Regards,

Sebastian

Hi all!

I think we have identified the problem at my shop: we just recently switched to IGMP v3 when we moved to new routers. All of a sudden we saw crashes occur consistently when we moved VLANs to the new hardware. Far from all the computers with Ethernet adapters crashed, but with the ones that did, we've changed a few of the affected VLANs back to IGMP 2. That seems to have stopped the crashes. We've only seen it with 10.9.x, but that is by far our prevalent OS here. I'm not sure to which extent this affects other OS versions, since it's only about 5% of the machines with ethernet adapter that's been crashing. However, worth checking with your network guys if they are running IGMP v 3.

As a comparison, our shop has about 800 Macs that we can monitor through JSS, and about 10 of them has had this problem. We're running approximately 1.5 B class networks.

Hello all,

I know this is old, but this thread was one that I kept stumbling on when I was having this issue after upgrading to El Capitan. Hopefully this information will prove helpful to the next person stumbling upon it.

In my case it ended up being an older version (I think v9) Citrix Receiver application kernel extension. I used 'kextstat |grep -v apple' to identify the non-apple extensions and just went through them one at a time.

-Cheers, Peter.

Thanks very much for this Peter! Was having this issue for months and was driving me mad. Turns out that an old Citrix Receiver app was also causing the issue for me. I've just unloaded using

sudo kextunload -b com.citrix.driver.net6im

sudo kextunload -b com.deterministicnetworks.driver.dne

sudo kextunload -b com.deterministicnetworks.driver.dniregistry

and all was find after that!

Thanks

Mark