Some firmware builds require two reboot cycles to work properly, Garrett noted. Rebooting is needed so the firmware can perform garbage collection, effectively cleaning up unused memory.
Report that, delete the files again and marvel at the benefits that technology has brought to your life. 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. Users can either make sure they're using the most up-to-date kernel, boot the machine in plain-old BIOS mode, or try the following: 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. He also submitted a patch to the kernel source code to ensure Linux does not use more than 50 per cent of the UEFI firmware's flash memory.
Garrett’s advice is to make sure you’ve got plenty of space in the machine’s protected storage area to avoid being bitten by the boot bug on Linux. The UEFI specification states this sort of failure shouldn't happen.
According to Garrett, if this area becomes more than 50 per cent full, the Samsung laptop may refuse to start-up. When the Linux kernel triggers an exception (such as a hardware driver poking the wrong bit of memory), it writes diagnostic data to the UEFI firmware's variable storage space.