SIOCPROTODETACH_IN6:en0 error=43

Question

Level 1

70 points

SIOCPROTODETACH_IN6:en0 error=43

I have here a 20" iMac that when booting freezes up. Booting in verbose mode shows the following errors when it hangs:

SIOCPROTODETACH_IN6:en0 error=43
SIOCPROTODETACH_IN6:fw2 error=43

There are no references in apple's internal knowledge base or anywhere on these discussion forums. Anyone seen this before? Seems like it just needs a new logic board...

Posted on Feb 27, 2006 9:27 AM

Reply

Answer 1

Mar 12, 2006 7:42 AM in response to Josh T

Josh,

I'll chip in as no-one else has... I don't recognise the errors....

How is the iMac freezing? It is a kernel panic? If so working through Dr Smoke's guide is the best way to cure it - and far far far cheaper than a new logic board - which might not even be at fault.

regards

mrtotes

Reply

Answer 2

Josh T Author

Level 1

70 points

Mar 13, 2006 9:38 AM in response to Adam Coates

No kernal panics at all. It would literally freeze at the blue screen. When booted to verbose mode it stops when those errors show up.

I was able to boot to external drives with no problem and since this machine lives in a lab and has no important data on it I just zeroed the drive and re-imaged. Looks like this was a software problem after all.

Reply

Answer 3

pixitha

Level 1

0 points

Jun 6, 2006 12:06 AM in response to Josh T

not that this helps that much...but i have the same error in my console log

Jun 5 23:53:45 localhost kernel: SIOCPROTODETACH_IN6: en0 error=43
Jun 5 23:53:45 localhost kernel: SIOCPROTODETACH_IN6: fw0 error=43

my machine works ok for the most part, no booting failures but no idea what that error is upposed to be.

This was the only thing (yea, that ONLY) thng that turns up on google with that string in it...odd

my guess is thats its an issue with the fw and the eth0 (en0) and ipv6 based on what little info is in the error.

-pix

Quicksilver G4 733 Mac OS X (10.3.9)

Reply

Answer 4

Josh T Author

Level 1

70 points

Jun 6, 2006 8:36 AM in response to pixitha

I had assumed a bad logic board but that assumption was totally wrong. I simply zeroed the drive, re-imaged it and put it back in the lab. It has had no problems at all since then. If you don't have a good backup then an archive & install might fix things but I dunno.

Reply