I don't think this will be fixed. If the MAC address is invalid, what is the driver to do? Other things can break if the kernel driver accepts the invalid data.
I think that this really should be marked as a "kernel bug", as it is the kernel driver doing this, not udev. If only launchpad allowed you to file hardware bugs and they were sent to the appropriate vendor ...
I don't think this will be fixed. If the MAC address is invalid, what is the driver to do? Other things can break if the kernel driver accepts the invalid data.
I have blogged about my experience and hack for it at http:// davehall. com.au/ blog/dave/ 2008/02/ 10/flakey- bios-gigabyte- ga-m68sm- s2l-makes- mac-address- change- reboot
I think that this really should be marked as a "kernel bug", as it is the kernel driver doing this, not udev. If only launchpad allowed you to file hardware bugs and they were sent to the appropriate vendor ...