[opensuse-virtual] new "efi: Could not map UEFI random seed!" booting Xen 4.9.0 Dom0 + kernel 4.11.0-4 ?
Booting Xen 4.9.0 on kernel-default 4.11.0-4, I currently see a non-fatal WARNING efi: Could not map UEFI random seed! ... (XEN) Xen version 4.9.0_04-493 (abuild@suse.de) (gcc (SUSE Linux) 4.8.5) debug=y Wed May 10 21:26:38 UTC 2017 (XEN) Latest ChangeSet: (XEN) Bootloader: EFI (XEN) Command line: dom0_mem=4096M,max:4096M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 c pufreq=xen vga=gfx-1920x1080x16 com1=115200,8n1,pci console=com1,vga console_timestamps conso le_to_ring conring_size=64 reboot=acpi sched=credit2 clocksource=hpet iommu=verbose log_buf_l en=16M sched_debug apic_verbosity=verbose loglvl=warning guest_loglvl=none/warning (XEN) Xen image load base address: 0x8c200000 ... [ 0.000000] console [xenboot0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.31 by American Megatrends [ 0.000000] efi: ESRT=0x9ef8d998 ACPI 2.0=0x9e819000 ACPI=0x9e819000 SMBIOS=0xf04c0 M PS=0xfd490 [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: CPU: 0 PID: 0 at ../mm/early_ioremap.c:137 __early_ioremap+0xf4/0x1b9 [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.11.0-4.gcb15206-default #1 [ 0.000000] Call Trace: [ 0.000000] dump_stack+0x5c/0x78 [ 0.000000] __warn+0xbe/0xe0 [ 0.000000] __early_ioremap+0xf4/0x1b9 [ 0.000000] efi_config_parse_tables+0x10d/0x1a7 [ 0.000000] ? __early_set_fixmap+0x8b/0x8e [ 0.000000] ? efi_config_init+0x71/0x93 [ 0.000000] ? efi_config_init+0x71/0x93 [ 0.000000] ? efi_init+0x35f/0x45d [ 0.000000] ? 0xffffffff81000000 [ 0.000000] ? setup_arch+0x471/0xcea [ 0.000000] ? printk+0x43/0x4b [ 0.000000] ? start_kernel+0x9d/0x43e [ 0.000000] ? xen_start_kernel+0x4de/0x4e8 [ 0.000000] ---[ end trace c06508679cc2dcf2 ]--- [ 0.000000] efi: Could not map UEFI random seed! [ 0.000000] efi: memattr: Unexpected EFI Memory Attributes table version -268402688 [ 0.000000] SMBIOS 2.7 present. [ 0.000000] DMI: Supermicro X10SAT/X10SAT, BIOS 3.0 05/26/2015 [ 0.000000] Hypervisor detected: Xen ... The notice is relatively new; tho can't tell you specifically when it appeared. The system *does* boot successfully, and *appears* to be functioning. Digging, I found Patchwork [1/2] efi: add support for seeding the RNG from a UEFI config table https://patchwork.kernel.org/patch/9364581/ Is this WARNING, in fact, related to that patch? Is the 'fix' for the warning the inclusion of that patch? Or, is there a kernel boot option needed? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 12.05.17 at 19:46, <pgnet.dev@gmail.com> wrote: Booting Xen 4.9.0 on kernel-default 4.11.0-4, I currently see a non-fatal WARNING
efi: Could not map UEFI random seed!
As a general remark, I think such issues should rather be brought up on xen-devel.
[ 0.000000] efi: Could not map UEFI random seed!
This will need to go through a (to be created) hypercall (to retrieve the address). I've added this to me todo list, but of course it would be better for someone who can actually test this to write that code.
[ 0.000000] efi: memattr: Unexpected EFI Memory Attributes table version -268402688
When running as Dom0 under Xen I don't think the kernel has any business looking at the memory attributes table, irrespective of whether Xen itself makes use of it (it currently doesn't, and making it do is already on my todo list, but the same remark as above applies). The memory map (and that's what the attributes table applies to) is under the sole control of Xen. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (2)
-
Jan Beulich -
PGNet Dev