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.
Thread beginning with comment 511029
To read all comments associated with this story, please click here.
coreyography
Member since:
2009-03-06

The firmware activated the wifi (ostensibly to netboot) and left it DMA-ing into RAM? Peachy. Between this and SMM (thanks again, Intel) it will be impossible to remove malware in the future ;)

Reply Score: 1

Kivada Member since:
2010-07-07

Push for Coreboot then.

Reply Parent Score: 4