![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mjg59The 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. I ended up using this feature to help someone get a backtrace from a kernel oops during suspend today, and realised that it's not been terribly well publicised, so.
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.
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.
no subject
Date: 2013-03-20 12:33 pm (UTC)no subject
Date: 2013-03-20 12:46 pm (UTC)Cool !
Date: 2013-03-22 08:35 am (UTC)Yeah, this is good stuff
Date: 2013-03-22 07:59 pm (UTC)We should start seeing a whole bunch of these bugs that were hard to work on before become surmountable.
NP300E5C-A01UB
Date: 2013-03-28 05:46 am (UTC)Since it doesn't boot anything at all now, I'm trying to figure out how to clean the flash area so it will boot again. If anyone is curious what an affected firmware looks like, you can find the full dump here: https://github.com/rimunroe/SamsungUEFI