Linux 64 Standalone: "Got a bad hardware address length"

One of my players reports that my Unity game (Adventurezator: When Pigs Fly on Steam) crashes after launching, and strace reveals “Got a bad hardware address length for an AF_PACKET 16 8”.

Apparently it’s something with libmono.so. Several Unity games have this same problem, but not all.

Any Unity devs out there aware of this issue?

Full starting post and discussion:

Which version of Unity is your app built with?

What’s your memory usage like? There was a bug fixed in one of the 4.5.5 patch releases which dealt with Mono generating incorrect code under 64-bit when jumping large distances in memory (more likely to happen when your usage is above 2GB).

This happened with 4.5.3 and my update yesterday built with 4.5.5 didn’t fix it. I won’t even try 4.6 because libmono.so didn’t change between 4.5.5 and 4.6.

Which 4.5.5 release? The mono fixes I’m thinking of were in patch release 4. They’re not in the 4.6 release but will arrive in 4.6.0p1 (due out December 4th).

If you try that release and still get the same crash, please file a bug - I think you’ll need to attach a build of your game - and post the number here.

2 Likes

Ok, I’ll try a build today with 4.5.5p4, and I’ll report the results back here.

Thanks!

I’m having the same exact problem. The linux headless build (32 or 64bit) simply get stuck in an endless loop of “Got a bad hardware address length for an AF_PACKET 16 8” errors.

I tried with unity 4.5.2, 4.6.0 and 4.6.1 with no luck.

Any news or workaround?

I haven’t heard back from my Linux player, so I’m not sure if it’s been solved with 4.5.5p4 or not. You should file a bug report with a build attached.

Bug reported (case 658048) with a build attached, now I can just hope someone will try it and find a fix soon

We’ve tracked down the fix for this - it will be landing in an upcoming patch release. (I’ll try to hit 5.0p2 and 4.6.3p3)

Awesome, thanks!