Messages in this thread | | | From | "Luck, Tony" <> | Date | Wed, 13 Jul 2011 09:58:18 -0700 | Subject | RE: pstore dump inside an nmi handler |
| |
> Actually, is it expected that the ERST can handle only 8 records? Also if > you remove those records with pstore mount under /mnt; 'rm -rf > /mnt/dmesg-*', are those records removed immediately or are they cached to > be removed later? IOW, if a did a 'rm -rf ..' and then an 'echo c > > /proc/sysrq-trigger' immediately after it, would I expect those records to > be removed or not? Testing shows they are removed on reboot but the later > 'echo c > ..' didn't save any new error records. :-/
It isn't specified how much storage will be provided by ERST. I tried to find a limit on the system on which I did the original development, but got bored at a hundred ... which seemed to be plenty enough since the usual mode of operation ought to be to copy the records from pstore to some other storage and remove them from pstore early in boot.
The unlink from pstore is passed immediately to the backing store to do it's clear/erase operation ... but whether the BIOS implementation of ERST makes that space immediately available might vary from platform to platform.
-Tony
| |