Este é um bug conhecido com a implementação da UEFI da Samsung em determinados notebooks. Você pode saber mais sobre isso por googling "bug do Samsung UEFI" .
Tem sido mencionado em vários lugares como em este relatório de erros de imagem de CD do Ubuntu e este artigo da Wikipédia
Em seu diário on-line, Matthew Garret explica o problema com a implementação de UEFI da Samsung :
The problem with Samsung laptops bricking themselves turned out to be down to the UEFI variable store becoming more than 50% full and Samsung's firmware being dreadful, but the trigger was us writing a crash dump to the nvram.
E como depurá-lo:
First, make sure pstore is mounted. If you're on 3.9 then do:
mount -t pstore /sys/fs/pstore /sys/fs/pstore
For earlier kernels you'll need to find somewhere else to stick it. If there's anything in there, delete it - we want to make sure there's enough space to save future dumps. Now reboot twice
[1]. Next time you get a system crash that doesn't make it to system logs, mount pstore again and (with luck) there'll be a bunch of files there. For tedious reasons these need to be assembled in reverse order (part 12 comes before part 11, and so on) but you should have a crash log. Report that, delete the files again and marvel at the benefits that technology has brought to your life.
[1]UEFI implementations generally handle variable deletion by flagging the space as reclaimable rather than immediately making it available again. You need to reboot in order for the firmware to garbage collect it. Some firmware seems to require two reboot cycles to do this properly. Thanks, firmware.
A correção? Isso terá que vir da Samsung. Enquanto isso, o Garret enviou um patch para a fonte do kernel Linux que toma precauções contra isso. Então, usar uma distro com o kernel Linux mais recente não deve acionar o bug.