Linked by Thom Holwerda on Sun 18th Mar 2012 19:08 UTC
Hardware, Embedded Systems "Some of my recent time has been devoted to making our boot media more Mac friendly, which has entailed rather a lot of rebooting. This would have been fine, if tedious, except that some number of boots would fall over with either a clearly impossible kernel panic or userspace segfaulting in places that made no sense. Something was clearly wrong. Crashes that shouldn't happen are generally an indication of memory corruption. The question is how that corruption is being triggered. Hunting that down wasn't terribly easy." Very interesting - and, unlike what the title suggest, not particularly related to the secure boot stuff.
Permalink for comment 511015
To read all comments associated with this story, please click here.
Like everything else
by Poseidon on Sun 18th Mar 2012 23:06 UTC
Member since:

Every time there's a major hardware foundation switch, this is expected to happen. Like ISA to PCI, PCI to AGP (for graphics) etc. The sad reality is that developers need to actually dig in to the UEFI standard and learn its innars, issues and limitations. You just can't expect it to work seamlessly given the astounding changes done to the whole hardware and language.

UEFI is here to stay and hopefully everyone does their homework/provide feedback also to the developers so that in future versions the issues are take care of.

Reply Score: 1