On 2 March 2018 at 14:35, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the const read-only array 'buf' on the stack but instead
> make it static. Makes the object code smaller by 64 bytes:
>
> Before:
>textdata bss
Sigh, and now I was just able to do this:
saruman:/sys/fs/pstore# \rm *
saruman:/sys/fs/pstore# l
total 0
drwxr-x--- 2 root root 0 Mar 2 11:28 ./
drwxr-xr-x 10 root root 0 Mar 2 10:20 ../
Ok, so forget linux, I think it's just a stupid EFI bios.
If I were to venture a guess:
1) I went in
[+linux-efi and fixed Matthew's Email]
As an update, I got my NVME drive to boot once at least, it seem that I need
to wait about 2mn for the bios to do whatever, hang, recover and then
finally continue booting.
If I take over and force a boot on the M2 Sata drive instead, then it boots
near
On Thu, 9 Nov 2017 17:30:36 + David Howells wrote:
> Here's a set of patches to institute a "locked-down mode" in the kernel and
> to trigger that mode if the kernel is booted in secure-boot mode or through
> the command line.
>
> Enabling CONFIG_LOCK_DOWN_KERNEL makes
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Young
[ Upstream commit 835bcec5fdf3f9e880111b482177e7e70e3596da ]
'add_efi_memmap' is an early param, but do_add_efi_memmap() has no
chance to run because the code
From: Colin Ian King
Don't populate the const read-only array 'buf' on the stack but instead
make it static. Makes the object code smaller by 64 bytes:
Before:
textdata bss dec hex filename
9264 1 1692812441
On 3/2/2018 12:53 AM, AKASHI Takahiro wrote:
Tyler, Jeffrey,
[Note: This issue takes place in kexec, not kdump. So to be precise,
it is not the same phenomenon as what I addressed in [1],[2]:
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2018-February/557254.html
[2]