You are not logged in.

#26 2021-02-15 18:13:45

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

V1del wrote:

It's UUID not UIDD

I've check that I do not know how many times!!!


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#27 2021-02-15 18:14:50

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Xwang wrote:

I'm still using GRUB. Moving to systemd-boot could change something or help solve the issue anyway?

Anything's possible. Maybe it can shift the bug out of the way.

Are you on latest BIOS already?
https://www.asus.com/supportonly/N752VX/HelpDesk_BIOS/

Last edited by Maniaxx (2021-02-15 18:15:58)


sys2064

Offline

#28 2021-02-15 18:17:46

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Maniaxx wrote:
Xwang wrote:

I'm still using GRUB. Moving to systemd-boot could change something or help solve the issue anyway?

Aynthing's possible. Maybe it can shift the bug out of the way.

Are you on latest BIOS already?
https://www.asus.com/supportonly/N752VX/HelpDesk_BIOS/

I'm on the latest BIOS and now I will check if moving fstab to UUID changes something, otherwise I'll start to see how to move from grub to systemd-boot.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#29 2021-02-15 18:34:03

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Have you checked the kernel log (dmesg) for anything suspicious in the beginning area? Maybe the kernel fights for some resources or something.
Did you check BIOS settings to disable some functions/features you don't need? It might shuffle the memory/ACPI map.

Last edited by Maniaxx (2021-02-15 18:38:25)


sys2064

Offline

#30 2021-02-15 19:04:50

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Maniaxx wrote:

Have you checked the kernel log (dmesg) for anything suspicious in the beginning area? Maybe the kernel fights for some resources or something.
Did you check BIOS settings to disable some functions/features you don't need? It might shuffle the memory/ACPI map.

In dmesg I see

[    0.104481] printk: console [tty0] enabled

does it mean that the issue happens in the first 0.1 seconds (otherwise I should see something on the screen)?

then I see this one:

[    0.104858] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x000000007affffff], contact BIOS vendor for fixes
[    0.104861] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x0000000078800000-0x000000007affffff]
               BIOS vendor: American Megatrends Inc.; Ver: N752VX.303; Product Version: 1.0       
[    0.104865] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
[    0.104866] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
[    0.104868] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.104870] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.104872] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.104872] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    0.106440] DMAR-IR: Enabled IRQ remapping in xapic mode
[    0.106441] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.110563] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.114745] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
[    0.114751] Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=2599992)
[    0.114754] pid_max: default: 32768 minimum: 301
[    0.116778] LSM: Security Framework initializing
[    0.116784] Yama: becoming mindful.

Should I try  'intremap=no_x2apic_optout' to override the BIOS setting as suggested by the kernel?

And then this one:

[    0.202074] ACPI: Using IOAPIC for interrupt routing
[    0.202106] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.202729] ACPI: Enabled 8 GPEs in block 00 to 7F

Should I use "pci=nocrs" , too?

This is the complete dmesg till systemd log is started:

[    0.000000] microcode: microcode updated early to revision 0xe2, date = 2020-07-14
[    0.000000] Linux version 5.10.16-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36) #1 ZEN SMP PREEMPT Sat, 13 Feb 2021 20:51:02 +0000
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw earlyprintk=vga,keep loglevel=7 rd.systemd.show_status=auto rd.udev.log_priority=3 splash mitigations=auto,nosmt pci=noaer nvidia-drm.modeset=1
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007255efff] usable
[    0.000000] BIOS-e820: [mem 0x000000007255f000-0x000000007255ffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000072560000-0x00000000725a9fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000725aa000-0x0000000075519fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007551a000-0x0000000076228fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000076229000-0x0000000076502fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000076503000-0x00000000770a6fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000770a7000-0x0000000077f08fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000077f09000-0x0000000077f7efff] type 20
[    0.000000] BIOS-e820: [mem 0x0000000077f7f000-0x0000000077ffefff] usable
[    0.000000] BIOS-e820: [mem 0x0000000078000000-0x00000000780fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000483ffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.40 by American Megatrends
[    0.000000] efi: ESRT=0x77e48e18 ACPI=0x7660b000 ACPI 2.0=0x7660b000 SMBIOS=0x77662000 SMBIOS 3.0=0x77661000 
[    0.000000] SMBIOS 3.0.0 present.
[    0.000000] DMI: ASUSTeK COMPUTER INC. N752VX/N752VX, BIOS N752VX.303 04/17/2019
[    0.000000] tsc: Detected 2600.000 MHz processor
[    0.000000] tsc: Detected 2599.992 MHz TSC
[    0.001161] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.001164] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.001170] last_pfn = 0x484000 max_arch_pfn = 0x400000000
[    0.001174] MTRR default type: write-back
[    0.001174] MTRR fixed ranges enabled:
[    0.001175]   00000-9FFFF write-back
[    0.001176]   A0000-BFFFF uncachable
[    0.001177]   C0000-FFFFF write-protect
[    0.001177] MTRR variable ranges enabled:
[    0.001179]   0 base 0080000000 mask 7F80000000 uncachable
[    0.001179]   1 base 007C000000 mask 7FFC000000 uncachable
[    0.001180]   2 base 007A000000 mask 7FFE000000 uncachable
[    0.001181]   3 base 0079000000 mask 7FFF000000 uncachable
[    0.001182]   4 base 0078800000 mask 7FFF800000 uncachable
[    0.001182]   5 disabled
[    0.001183]   6 disabled
[    0.001183]   7 disabled
[    0.001184]   8 disabled
[    0.001184]   9 disabled
[    0.001471] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.001925] last_pfn = 0x77fff max_arch_pfn = 0x400000000
[    0.008308] esrt: Reserving ESRT space from 0x0000000077e48e18 to 0x0000000077e48e50.
[    0.008314] check: Scanning 1 areas for low memory corruption
[    0.008318] Using GB pages for direct mapping
[    0.008740] Secure boot could not be determined
[    0.008741] RAMDISK: [mem 0x32ee3000-0x35768fff]
[    0.008748] ACPI: Early table checksum verification disabled
[    0.008750] ACPI: RSDP 0x000000007660B000 000024 (v02 _ASUS_)
[    0.008754] ACPI: XSDT 0x000000007660B0A8 0000D4 (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008758] ACPI: FACP 0x0000000076630D18 00010C (v05 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008763] ACPI: DSDT 0x000000007660B210 025B03 (v02 _ASUS_ Notebook 01072009 INTL 20120913)
[    0.008766] ACPI: FACS 0x00000000770A5F80 000040
[    0.008768] ACPI: APIC 0x0000000076630E28 0000BC (v03 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008771] ACPI: FPDT 0x0000000076630EE8 000044 (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008773] ACPI: FIDT 0x0000000076630F30 00009C (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008776] ACPI: MCFG 0x0000000076630FD0 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
[    0.008779] ACPI: HPET 0x0000000076631010 000038 (v01 _ASUS_ Notebook 01072009 AMI. 0005000B)
[    0.008781] ACPI: SSDT 0x0000000076631048 000315 (v01 SataRe SataTabl 00001000 INTL 20120913)
[    0.008784] ACPI: ECDT 0x0000000076631360 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
[    0.008787] ACPI: LPIT 0x0000000076631428 000094 (v01 INTEL  SKL      00000000 MSFT 0000005F)
[    0.008790] ACPI: SSDT 0x00000000766314C0 000248 (v02 INTEL  sensrhub 00000000 INTL 20120913)
[    0.008792] ACPI: DBGP 0x0000000076631708 000034 (v01 INTEL           00000000 MSFT 0000005F)
[    0.008795] ACPI: DBG2 0x0000000076631740 000054 (v00 INTEL           00000000 MSFT 0000005F)
[    0.008797] ACPI: SSDT 0x0000000076631798 003C45 (v02 DptfTa DptfTabl 00001000 INTL 20120913)
[    0.008800] ACPI: SSDT 0x00000000766353E0 0066B0 (v02 SaSsdt SaSsdt   00003000 INTL 20120913)
[    0.008803] ACPI: UEFI 0x000000007663BA90 000042 (v01                 00000000      00000000)
[    0.008806] ACPI: SSDT 0x000000007663BAD8 000E58 (v02 CpuRef CpuSsdt  00003000 INTL 20120913)
[    0.008809] ACPI: BGRT 0x000000007663C930 000038 (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.008811] ACPI: SSDT 0x000000007663C968 0000A5 (v02 SgRef  SgPeg    00001000 INTL 20120913)
[    0.008814] ACPI: DMAR 0x000000007663CA10 0000F0 (v01 INTEL  SKL      00000001 INTL 00000001)
[    0.008817] ACPI: TPM2 0x000000007663CB00 000034 (v03        Tpm2Tabl 00000001 AMI  00000000)
[    0.008819] ACPI: SSDT 0x000000007663CB38 001A3F (v01 OptRef OptTabl  00001000 INTL 20120913)
[    0.008822] ACPI: MSDM 0x0000000075FC2F18 000055 (v03 _ASUS_ Notebook 00000000 ASUS 00000001)
[    0.008829] ACPI: Local APIC address 0xfee00000
[    0.008925] No NUMA configuration found
[    0.008926] Faking a node at [mem 0x0000000000000000-0x0000000483ffffff]
[    0.008929] NODE_DATA(0) allocated [mem 0x483ffc000-0x483ffffff]
[    0.030347] Zone ranges:
[    0.030349]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.030350]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.030352]   Normal   [mem 0x0000000100000000-0x0000000483ffffff]
[    0.030353]   Device   empty
[    0.030354] Movable zone start for each node
[    0.030355] Early memory node ranges
[    0.030356]   node   0: [mem 0x0000000000001000-0x0000000000057fff]
[    0.030357]   node   0: [mem 0x0000000000059000-0x000000000009dfff]
[    0.030358]   node   0: [mem 0x0000000000100000-0x000000007255efff]
[    0.030359]   node   0: [mem 0x00000000725aa000-0x0000000075519fff]
[    0.030360]   node   0: [mem 0x0000000076229000-0x0000000076502fff]
[    0.030360]   node   0: [mem 0x0000000077f7f000-0x0000000077ffefff]
[    0.030361]   node   0: [mem 0x0000000100000000-0x0000000483ffffff]
[    0.030548] Zeroed struct page in unavailable ranges: 26683 pages
[    0.030549] Initmem setup node 0 [mem 0x0000000000001000-0x0000000483ffffff]
[    0.030551] On node 0 totalpages: 4167621
[    0.030552]   DMA zone: 64 pages used for memmap
[    0.030553]   DMA zone: 22 pages reserved
[    0.030553]   DMA zone: 3996 pages, LIFO batch:0
[    0.030582]   DMA32 zone: 7457 pages used for memmap
[    0.030582]   DMA32 zone: 477225 pages, LIFO batch:63
[    0.033042]   Normal zone: 57600 pages used for memmap
[    0.033042]   Normal zone: 3686400 pages, LIFO batch:63
[    0.052580] Reserving Intel graphics memory at [mem 0x79000000-0x7affffff]
[    0.052870] ACPI: PM-Timer IO Port: 0x1808
[    0.052871] ACPI: Local APIC address 0xfee00000
[    0.052877] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.052877] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.052878] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.052879] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.052880] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.052881] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.052881] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.052882] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.052909] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[    0.052910] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.052912] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.052913] ACPI: IRQ0 used by override.
[    0.052914] ACPI: IRQ9 used by override.
[    0.052915] Using ACPI (MADT) for SMP configuration information
[    0.052917] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[    0.052921] e820: update [mem 0x741b1000-0x741dffff] usable ==> reserved
[    0.052930] TSC deadline timer available
[    0.052931] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[    0.052945] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.052947] PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
[    0.052948] PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[    0.052949] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[    0.052951] PM: hibernation: Registered nosave memory: [mem 0x7255f000-0x7255ffff]
[    0.052952] PM: hibernation: Registered nosave memory: [mem 0x72560000-0x725a9fff]
[    0.052953] PM: hibernation: Registered nosave memory: [mem 0x741b1000-0x741dffff]
[    0.052954] PM: hibernation: Registered nosave memory: [mem 0x7551a000-0x76228fff]
[    0.052956] PM: hibernation: Registered nosave memory: [mem 0x76503000-0x770a6fff]
[    0.052956] PM: hibernation: Registered nosave memory: [mem 0x770a7000-0x77f08fff]
[    0.052957] PM: hibernation: Registered nosave memory: [mem 0x77f09000-0x77f7efff]
[    0.052959] PM: hibernation: Registered nosave memory: [mem 0x77fff000-0x77ffffff]
[    0.052960] PM: hibernation: Registered nosave memory: [mem 0x78000000-0x780fffff]
[    0.052960] PM: hibernation: Registered nosave memory: [mem 0x78100000-0x78ffffff]
[    0.052961] PM: hibernation: Registered nosave memory: [mem 0x79000000-0x7affffff]
[    0.052962] PM: hibernation: Registered nosave memory: [mem 0x7b000000-0xdfffffff]
[    0.052963] PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[    0.052963] PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
[    0.052964] PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
[    0.052965] PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfebfffff]
[    0.052966] PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[    0.052966] PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfedfffff]
[    0.052967] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[    0.052968] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
[    0.052969] PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    0.052970] [mem 0x7b000000-0xdfffffff] available for PCI devices
[    0.052971] Booting paravirtualized kernel on bare hardware
[    0.052974] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.057200] setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:8 nr_node_ids:1
[    0.057327] percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
[    0.057332] pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
[    0.057333] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
[    0.057350] Built 1 zonelists, mobility grouping on.  Total pages: 4102478
[    0.057351] Policy zone: Normal
[    0.057352] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw earlyprintk=vga,keep loglevel=7 rd.systemd.show_status=auto rd.udev.log_priority=3 splash mitigations=auto,nosmt pci=noaer nvidia-drm.modeset=1
[    0.058060] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.058341] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.058397] mem auto-init: stack:byref_all(zero), heap alloc:on, heap free:off
[    0.089559] Memory: 16189060K/16670484K available (14344K kernel code, 2034K rwdata, 8680K rodata, 1716K init, 4252K bss, 481164K reserved, 0K cma-reserved)
[    0.089566] random: get_random_u64 called from __kmem_cache_create+0x28/0x630 with crng_init=0
[    0.089664] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.089675] Kernel/User page tables isolation: enabled
[    0.089691] ftrace: allocating 39442 entries in 155 pages
[    0.100745] ftrace: allocated 155 pages with 5 groups
[    0.100830] rcu: Preemptible hierarchical RCU implementation.
[    0.100831] rcu:     RCU dyntick-idle grace-period acceleration is enabled.
[    0.100832] rcu:     RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=8.
[    0.100833] rcu:     RCU priority boosting: priority 1 delay 500 ms.
[    0.100834]  Trampoline variant of Tasks RCU enabled.
[    0.100835]  Rude variant of Tasks RCU enabled.
[    0.100835]  Tracing variant of Tasks RCU enabled.
[    0.100836] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.100837] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.103850] NR_IRQS: 20736, nr_irqs: 2048, preallocated irqs: 16
[    0.104259] spurious 8259A interrupt: IRQ7.
[    0.104281] Console: colour dummy device 80x25
[    0.104481] printk: console [tty0] enabled
[    0.104496] ACPI: Core revision 20200925
[    0.104735] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
[    0.104836] APIC: Switch to symmetric I/O mode setup
[    0.104839] DMAR: Host address width 39
[    0.104840] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.104845] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0501e
[    0.104847] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.104851] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.104853] DMAR: RMRR base: 0x00000075fa2000 end: 0x00000075fc1fff
[    0.104855] DMAR: RMRR base: 0x00000078800000 end: 0x0000007affffff
[    0.104858] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x000000007affffff], contact BIOS vendor for fixes
[    0.104861] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x0000000078800000-0x000000007affffff]
               BIOS vendor: American Megatrends Inc.; Ver: N752VX.303; Product Version: 1.0       
[    0.104865] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
[    0.104866] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
[    0.104868] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.104870] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.104872] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.104872] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    0.106440] DMAR-IR: Enabled IRQ remapping in xapic mode
[    0.106441] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.110563] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.114745] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
[    0.114751] Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=2599992)
[    0.114754] pid_max: default: 32768 minimum: 301
[    0.116778] LSM: Security Framework initializing
[    0.116784] Yama: becoming mindful.
[    0.116789] LSM support for eBPF active
[    0.116820] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.116843] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.117077] mce: CPU0: Thermal monitoring enabled (TM1)
[    0.117094] process: using mwait in idle threads
[    0.117097] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[    0.117098] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[    0.117101] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.117105] Spectre V2 : Mitigation: Full generic retpoline
[    0.117106] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.117108] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.117110] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.117113] Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl
[    0.117115] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.117117] SMT: disabled
[    0.117120] SMT: disabled
[    0.117121] SMT: disabled
[    0.117122] TAA: Mitigation: Clear CPU buffers
[    0.117125] SRBDS: Mitigation: Microcode
[    0.117126] MDS: Mitigation: Clear CPU buffers
[    0.117129] clr: Applying alternatives
[    0.117335] clr: Applying alternatives done
[    0.117344] Freeing SMP alternatives memory: 40K
[    0.118828] smpboot: CPU0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (family: 0x6, model: 0x5e, stepping: 0x3)
[    0.118929] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.118940] ... version:                4
[    0.118941] ... bit width:              48
[    0.118942] ... generic registers:      4
[    0.118943] ... value mask:             0000ffffffffffff
[    0.118945] ... max period:             00007fffffffffff
[    0.118946] ... fixed-purpose events:   3
[    0.118948] ... event mask:             000000070000000f
[    0.119032] rcu: Hierarchical SRCU implementation.
[    0.119748] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.119760] smp: Bringing up secondary CPUs ...
[    0.119848] x86: Booting SMP configuration:
[    0.119850] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
[    0.130991] smp: Brought up 1 node, 4 CPUs
[    0.130997] smpboot: Max logical packages: 2
[    0.130999] smpboot: Total of 4 processors activated (20799.93 BogoMIPS)
[    0.132062] devtmpfs: initialized
[    0.132062] x86/mm: Memory block size: 128MB
[    0.132929] PM: Registering ACPI NVS region [mem 0x7255f000-0x7255ffff] (4096 bytes)
[    0.132929] PM: Registering ACPI NVS region [mem 0x76503000-0x770a6fff] (12206080 bytes)
[    0.132953] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.132965] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.133008] pinctrl core: initialized pinctrl subsystem
[    0.133150] PM: RTC time: 18:35:36, date: 2021-02-15
[    0.133254] NET: Registered protocol family 16
[    0.133465] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    0.133774] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.133912] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.133921] audit: initializing netlink subsys (disabled)
[    0.133927] audit: type=2000 audit(1613414136.026:1): state=initialized audit_enabled=0 res=1
[    0.133927] thermal_sys: Registered thermal governor 'fair_share'
[    0.133927] thermal_sys: Registered thermal governor 'bang_bang'
[    0.133927] thermal_sys: Registered thermal governor 'step_wise'
[    0.133927] thermal_sys: Registered thermal governor 'user_space'
[    0.133927] thermal_sys: Registered thermal governor 'power_allocator'
[    0.133927] cpuidle: using governor ladder
[    0.133927] cpuidle: using governor menu
[    0.133927] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.133927] ACPI: bus type PCI registered
[    0.133927] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.133927] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.133927] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[    0.133927] PCI: Using configuration type 1 for base access
[    0.134166] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.135338] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.135338] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.135818] fbcon: Taking over console
[    0.135835] ACPI: Added _OSI(Module Device)
[    0.135840] ACPI: Added _OSI(Processor Device)
[    0.135842] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.135844] ACPI: Added _OSI(Processor Aggregator Device)
[    0.135846] ACPI: Added _OSI(Linux-Dell-Video)
[    0.135847] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.135849] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.174282] ACPI: 8 ACPI AML tables successfully acquired and loaded
[    0.175805] ACPI: EC: EC started
[    0.175806] ACPI: EC: interrupt blocked
[    0.177661] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.177663] ACPI: EC: Boot ECDT EC used to handle transactions
[    0.178947] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.185799] ACPI: Dynamic OEM Table Load:
[    0.185806] ACPI: SSDT 0xFFFF97A200C2D800 0005DC (v02 PmRef  Cpu0Ist  00003000 INTL 20120913)
[    0.187273] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked
[    0.188668] ACPI: Dynamic OEM Table Load:
[    0.188674] ACPI: SSDT 0xFFFF97A20123BC00 00037F (v02 PmRef  Cpu0Cst  00003001 INTL 20120913)
[    0.190092] ACPI: Dynamic OEM Table Load:
[    0.190096] ACPI: SSDT 0xFFFF97A201280300 00008E (v02 PmRef  Cpu0Hwp  00003000 INTL 20120913)
[    0.191375] ACPI: Dynamic OEM Table Load:
[    0.191379] ACPI: SSDT 0xFFFF97A200FB8400 000130 (v02 PmRef  HwpLvt   00003000 INTL 20120913)
[    0.193041] ACPI: Dynamic OEM Table Load:
[    0.193047] ACPI: SSDT 0xFFFF97A200C29800 0005AA (v02 PmRef  ApIst    00003000 INTL 20120913)
[    0.194725] ACPI: Dynamic OEM Table Load:
[    0.194730] ACPI: SSDT 0xFFFF97A200FB8200 000119 (v02 PmRef  ApHwp    00003000 INTL 20120913)
[    0.196099] ACPI: Dynamic OEM Table Load:
[    0.196104] ACPI: SSDT 0xFFFF97A200FBA800 000119 (v02 PmRef  ApCst    00003000 INTL 20120913)
[    0.202036] ACPI: Interpreter enabled
[    0.202072] ACPI: (supports S0 S3 S4 S5)
[    0.202074] ACPI: Using IOAPIC for interrupt routing
[    0.202106] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.202729] ACPI: Enabled 8 GPEs in block 00 to 7F
[    0.205291] ACPI: Power Resource [PG00] (on)
[    0.228084] ACPI: Power Resource [PG01] (on)
[    0.228465] ACPI: Power Resource [PG02] (on)
[    0.229131] ACPI: Power Resource [WRST] (off)
[    0.229462] ACPI: Power Resource [WRST] (off)
[    0.229795] ACPI: Power Resource [WRST] (off)
[    0.230123] ACPI: Power Resource [WRST] (off)
[    0.230448] ACPI: Power Resource [WRST] (off)
[    0.230777] ACPI: Power Resource [WRST] (off)
[    0.231104] ACPI: Power Resource [WRST] (off)
[    0.231720] ACPI: Power Resource [WRST] (off)
[    0.232084] ACPI: Power Resource [WRST] (off)
[    0.232457] ACPI: Power Resource [WRST] (off)
[    0.233032] ACPI: Power Resource [WRST] (off)
[    0.233359] ACPI: Power Resource [WRST] (off)
[    0.233684] ACPI: Power Resource [WRST] (off)
[    0.234011] ACPI: Power Resource [WRST] (off)
[    0.234342] ACPI: Power Resource [WRST] (off)
[    0.234669] ACPI: Power Resource [WRST] (off)
[    0.234995] ACPI: Power Resource [WRST] (off)
[    0.235319] ACPI: Power Resource [WRST] (off)
[    0.235645] ACPI: Power Resource [WRST] (off)
[    0.235974] ACPI: Power Resource [WRST] (off)
[    0.246357] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[    0.246365] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.247937] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR DPC]
[    0.247939] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.248523] PCI host bridge to bus 0000:00
[    0.248525] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.248528] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.248530] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.248532] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window]
[    0.248534] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window]
[    0.248536] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window]
[    0.248538] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window]
[    0.248540] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
[    0.248542] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
[    0.248544] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
[    0.248546] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
[    0.248548] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
[    0.248550] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
[    0.248552] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window]
[    0.248554] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window]
[    0.248557] pci_bus 0000:00: root bus resource [mem 0x7b000000-0xdfffffff window]
[    0.248559] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window]
[    0.248561] pci_bus 0000:00: root bus resource [bus 00-fe]
[    0.248573] pci 0000:00:00.0: [8086:1910] type 00 class 0x060000
[    0.248679] pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
[    0.248716] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    0.248993] pci 0000:00:02.0: [8086:191b] type 00 class 0x030000
[    0.249002] pci 0000:00:02.0: reg 0x10: [mem 0xdd000000-0xddffffff 64bit]
[    0.249007] pci 0000:00:02.0: reg 0x18: [mem 0xb0000000-0xbfffffff 64bit pref]
[    0.249012] pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
[    0.249027] pci 0000:00:02.0: BAR 2: assigned to efifb
[    0.249159] pci 0000:00:04.0: [8086:1903] type 00 class 0x118000
[    0.249167] pci 0000:00:04.0: reg 0x10: [mem 0xdf420000-0xdf427fff 64bit]
[    0.249395] pci 0000:00:14.0: [8086:a12f] type 00 class 0x0c0330
[    0.249412] pci 0000:00:14.0: reg 0x10: [mem 0xdf410000-0xdf41ffff 64bit]
[    0.249470] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.249639] pci 0000:00:14.2: [8086:a131] type 00 class 0x118000
[    0.249654] pci 0000:00:14.2: reg 0x10: [mem 0xdf438000-0xdf438fff 64bit]
[    0.249876] pci 0000:00:15.0: [8086:a160] type 00 class 0x118000
[    0.249908] pci 0000:00:15.0: reg 0x10: [mem 0xdf437000-0xdf437fff 64bit]
[    0.250245] pci 0000:00:15.1: [8086:a161] type 00 class 0x118000
[    0.250278] pci 0000:00:15.1: reg 0x10: [mem 0xdf436000-0xdf436fff 64bit]
[    0.250582] pci 0000:00:16.0: [8086:a13a] type 00 class 0x078000
[    0.250601] pci 0000:00:16.0: reg 0x10: [mem 0xdf435000-0xdf435fff 64bit]
[    0.250668] pci 0000:00:16.0: PME# supported from D3hot
[    0.250837] pci 0000:00:17.0: [8086:a103] type 00 class 0x010601
[    0.250849] pci 0000:00:17.0: reg 0x10: [mem 0xdf430000-0xdf431fff]
[    0.250856] pci 0000:00:17.0: reg 0x14: [mem 0xdf434000-0xdf4340ff]
[    0.250863] pci 0000:00:17.0: reg 0x18: [io  0xf090-0xf097]
[    0.250870] pci 0000:00:17.0: reg 0x1c: [io  0xf080-0xf083]
[    0.250877] pci 0000:00:17.0: reg 0x20: [io  0xf060-0xf07f]
[    0.250884] pci 0000:00:17.0: reg 0x24: [mem 0xdf433000-0xdf4337ff]
[    0.250919] pci 0000:00:17.0: PME# supported from D3hot
[    0.251101] pci 0000:00:1c.0: [8086:a112] type 01 class 0x060400
[    0.251165] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.251438] pci 0000:00:1c.3: [8086:a113] type 01 class 0x060400
[    0.251502] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[    0.251766] pci 0000:00:1c.4: [8086:a114] type 01 class 0x060400
[    0.251836] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    0.252119] pci 0000:00:1f.0: [8086:a14e] type 00 class 0x060100
[    0.252373] pci 0000:00:1f.2: [8086:a121] type 00 class 0x058000
[    0.252387] pci 0000:00:1f.2: reg 0x10: [mem 0xdf42c000-0xdf42ffff]
[    0.252593] pci 0000:00:1f.3: [8086:a170] type 00 class 0x040300
[    0.252615] pci 0000:00:1f.3: reg 0x10: [mem 0xdf428000-0xdf42bfff 64bit]
[    0.252645] pci 0000:00:1f.3: reg 0x20: [mem 0xdf400000-0xdf40ffff 64bit]
[    0.252691] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[    0.252978] pci 0000:00:1f.4: [8086:a123] type 00 class 0x0c0500
[    0.253037] pci 0000:00:1f.4: reg 0x10: [mem 0xdf432000-0xdf4320ff 64bit]
[    0.253108] pci 0000:00:1f.4: reg 0x20: [io  0xf040-0xf05f]
[    0.253379] pci 0000:01:00.0: [10de:139a] type 00 class 0x030200
[    0.253399] pci 0000:01:00.0: reg 0x10: [mem 0xde000000-0xdeffffff]
[    0.253416] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
[    0.253433] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[    0.253445] pci 0000:01:00.0: reg 0x24: [io  0xe000-0xe07f]
[    0.253456] pci 0000:01:00.0: reg 0x30: [mem 0xdf000000-0xdf07ffff pref]
[    0.253479] pci 0000:01:00.0: Enabling HDA controller
[    0.253693] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.253696] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    0.253698] pci 0000:00:01.0:   bridge window [mem 0xde000000-0xdf0fffff]
[    0.253702] pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
[    0.253837] pci 0000:02:00.0: [8086:095a] type 00 class 0x028000
[    0.253922] pci 0000:02:00.0: reg 0x10: [mem 0xdf300000-0xdf301fff 64bit]
[    0.254213] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[    0.254702] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.254707] pci 0000:00:1c.0:   bridge window [mem 0xdf300000-0xdf3fffff]
[    0.254771] pci 0000:03:00.0: [10ec:5287] type 00 class 0xff0000
[    0.254790] pci 0000:03:00.0: reg 0x10: [mem 0xdf215000-0xdf215fff]
[    0.254843] pci 0000:03:00.0: reg 0x30: [mem 0xdf200000-0xdf20ffff pref]
[    0.254934] pci 0000:03:00.0: supports D1 D2
[    0.254936] pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.255144] pci 0000:03:00.1: [10ec:8168] type 00 class 0x020000
[    0.255162] pci 0000:03:00.1: reg 0x10: [io  0xd000-0xd0ff]
[    0.255186] pci 0000:03:00.1: reg 0x18: [mem 0xdf214000-0xdf214fff 64bit]
[    0.255202] pci 0000:03:00.1: reg 0x20: [mem 0xdf210000-0xdf213fff 64bit]
[    0.255297] pci 0000:03:00.1: supports D1 D2
[    0.255299] pci 0000:03:00.1: PME# supported from D0 D1 D2 D3hot D3cold
[    0.255415] pci 0000:00:1c.3: PCI bridge to [bus 03]
[    0.255418] pci 0000:00:1c.3:   bridge window [io  0xd000-0xdfff]
[    0.255422] pci 0000:00:1c.3:   bridge window [mem 0xdf200000-0xdf2fffff]
[    0.255525] pci 0000:04:00.0: [1b21:1242] type 00 class 0x0c0330
[    0.255548] pci 0000:04:00.0: reg 0x10: [mem 0xdf100000-0xdf107fff 64bit]
[    0.255597] pci 0000:04:00.0: enabling Extended Tags
[    0.255673] pci 0000:04:00.0: PME# supported from D3hot D3cold
[    0.255906] pci 0000:00:1c.4: PCI bridge to [bus 04]
[    0.255910] pci 0000:00:1c.4:   bridge window [mem 0xdf100000-0xdf1fffff]
[    0.258214] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258273] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.258329] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258385] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258441] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258498] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258553] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.258609] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.259269] ACPI: EC: interrupt unblocked
[    0.259271] ACPI: EC: event unblocked
[    0.259283] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.259284] ACPI: EC: GPE=0x23
[    0.259286] ACPI: \_SB_.PCI0.LPCB.EC0_: Boot ECDT EC initialization complete
[    0.259288] ACPI: \_SB_.PCI0.LPCB.EC0_: EC: Used to handle transactions and events
[    0.259335] iommu: Default domain type: Translated 
[    0.259452] SCSI subsystem initialized
[    0.259461] libata version 3.00 loaded.
[    0.259461] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.259461] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.259461] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.259461] vgaarb: loaded
[    0.259461] ACPI: bus type USB registered
[    0.259461] usbcore: registered new interface driver usbfs
[    0.259461] usbcore: registered new interface driver hub
[    0.259461] usbcore: registered new device driver usb
[    0.259461] pps_core: LinuxPPS API ver. 1 registered
[    0.259461] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.259461] PTP clock support registered
[    0.259461] EDAC MC: Ver: 3.0.0
[    0.259957] Registered efivars operations
[    0.259957] NetLabel: Initializing
[    0.259957] NetLabel:  domain hash size = 128
[    0.259957] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.259957] NetLabel:  unlabeled traffic allowed by default
[    0.259957] PCI: Using ACPI for IRQ routing
[    0.288549] PCI: pci_cache_line_size set to 64 bytes
[    0.288982] e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
[    0.288983] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
[    0.288984] e820: reserve RAM buffer [mem 0x7255f000-0x73ffffff]
[    0.288985] e820: reserve RAM buffer [mem 0x741b1000-0x77ffffff]
[    0.288986] e820: reserve RAM buffer [mem 0x7551a000-0x77ffffff]
[    0.288987] e820: reserve RAM buffer [mem 0x76503000-0x77ffffff]
[    0.288988] e820: reserve RAM buffer [mem 0x77fff000-0x77ffffff]
[    0.289473] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.289479] hpet0: 8 comparators, 64-bit 24.000000 MHz counter
[    0.291781] clocksource: Switched to clocksource tsc-early
[    0.300589] VFS: Disk quotas dquot_6.6.0
[    0.300604] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.300662] pnp: PnP ACPI init
[    0.301135] system 00:00: [io  0x0680-0x069f] has been reserved
[    0.301138] system 00:00: [io  0xffff] has been reserved
[    0.301140] system 00:00: [io  0xffff] has been reserved
[    0.301142] system 00:00: [io  0xffff] has been reserved
[    0.301144] system 00:00: [io  0x1800-0x18fe] has been reserved
[    0.301146] system 00:00: [io  0x164e-0x164f] has been reserved
[    0.301151] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.301234] system 00:01: [io  0x0800-0x087f] has been reserved
[    0.301238] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.301257] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.301290] system 00:03: [io  0x1854-0x1857] has been reserved
[    0.301294] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.301410] system 00:04: [io  0x0240-0x0259] has been reserved
[    0.301414] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.301447] pnp 00:05: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
[    0.301611] system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
[    0.301614] system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.301616] system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.301618] system 00:06: [mem 0xe0000000-0xefffffff] has been reserved
[    0.301620] system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.301622] system 00:06: [mem 0xfed90000-0xfed93fff] could not be reserved
[    0.301624] system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.301626] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
[    0.301628] system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.301631] system 00:06: [mem 0xdffe0000-0xdfffffff] has been reserved
[    0.301634] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.301673] system 00:07: [mem 0xfd000000-0xfdabffff] has been reserved
[    0.301675] system 00:07: [mem 0xfdad0000-0xfdadffff] has been reserved
[    0.301677] system 00:07: [mem 0xfdb00000-0xfdffffff] has been reserved
[    0.301679] system 00:07: [mem 0xfe000000-0xfe01ffff] could not be reserved
[    0.301681] system 00:07: [mem 0xfe036000-0xfe03bfff] has been reserved
[    0.301683] system 00:07: [mem 0xfe03d000-0xfe3fffff] has been reserved
[    0.301685] system 00:07: [mem 0xfe410000-0xfe7fffff] has been reserved
[    0.301689] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.301989] system 00:08: [io  0xff00-0xfffe] has been reserved
[    0.301993] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.303165] system 00:09: [mem 0xfdaf0000-0xfdafffff] has been reserved
[    0.303168] system 00:09: [mem 0xfdae0000-0xfdaeffff] has been reserved
[    0.303170] system 00:09: [mem 0xfdac0000-0xfdacffff] has been reserved
[    0.303173] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.304064] pnp: PnP ACPI: found 10 devices
[    0.309508] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.309551] NET: Registered protocol family 2
[    0.309660] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    0.309736] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.309930] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.309996] TCP: Hash tables configured (established 131072 bind 65536)
[    0.310061] MPTCP token hash table entries: 16384 (order: 6, 393216 bytes, linear)
[    0.310128] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.310165] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.310241] NET: Registered protocol family 1
[    0.310245] NET: Registered protocol family 44
[    0.310255] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.310258] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    0.310262] pci 0000:00:01.0:   bridge window [mem 0xde000000-0xdf0fffff]
[    0.310265] pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
[    0.310269] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.310273] pci 0000:00:1c.0:   bridge window [mem 0xdf300000-0xdf3fffff]
[    0.310279] pci 0000:00:1c.3: PCI bridge to [bus 03]
[    0.310281] pci 0000:00:1c.3:   bridge window [io  0xd000-0xdfff]
[    0.310284] pci 0000:00:1c.3:   bridge window [mem 0xdf200000-0xdf2fffff]
[    0.310290] pci 0000:00:1c.4: PCI bridge to [bus 04]
[    0.310294] pci 0000:00:1c.4:   bridge window [mem 0xdf100000-0xdf1fffff]
[    0.310301] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.310303] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.310305] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.310307] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window]
[    0.310309] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window]
[    0.310311] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window]
[    0.310313] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window]
[    0.310314] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window]
[    0.310316] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window]
[    0.310318] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window]
[    0.310320] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window]
[    0.310322] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window]
[    0.310324] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window]
[    0.310326] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window]
[    0.310328] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window]
[    0.310330] pci_bus 0000:00: resource 19 [mem 0x7b000000-0xdfffffff window]
[    0.310332] pci_bus 0000:00: resource 20 [mem 0xfd000000-0xfe7fffff window]
[    0.310334] pci_bus 0000:01: resource 0 [io  0xe000-0xefff]
[    0.310335] pci_bus 0000:01: resource 1 [mem 0xde000000-0xdf0fffff]
[    0.310337] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xd1ffffff 64bit pref]
[    0.310340] pci_bus 0000:02: resource 1 [mem 0xdf300000-0xdf3fffff]
[    0.310341] pci_bus 0000:03: resource 0 [io  0xd000-0xdfff]
[    0.310343] pci_bus 0000:03: resource 1 [mem 0xdf200000-0xdf2fffff]
[    0.310345] pci_bus 0000:04: resource 1 [mem 0xdf100000-0xdf1fffff]
[    0.310484] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.311798] PCI: CLS 0 bytes, default 64
[    0.311824] Trying to unpack rootfs image as initramfs...
[    0.607145] Freeing initrd memory: 41496K
[    0.607173] DMAR: ACPI device "device:76" under DMAR at fed91000 as 00:15.0
[    0.607177] DMAR: ACPI device "device:77" under DMAR at fed91000 as 00:15.1
[    0.607193] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.607195] software IO TLB: mapped [mem 0x000000006d509000-0x0000000071509000] (64MB)
[    0.607525] check: Scanning for low memory corruption every 60 seconds
[    0.607765] Initialise system trusted keyrings
[    0.607778] Key type blacklist registered
[    0.607812] workingset: timestamp_bits=41 max_order=22 bucket_order=0
[    0.608670] zbud: loaded
[    0.616133] Key type asymmetric registered
[    0.616136] Asymmetric key parser 'x509' registered
[    0.616141] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[    0.616189] io scheduler mq-deadline registered
[    0.616190] io scheduler kyber registered
[    0.616206] io scheduler bfq registered
[    0.616257] atomic64_test: passed for x86-64 platform with CX8 and with SSE
[    0.616501] pcieport 0000:00:01.0: PME: Signaling with IRQ 122
[    0.616653] pcieport 0000:00:1c.0: PME: Signaling with IRQ 123
[    0.616812] pcieport 0000:00:1c.3: PME: Signaling with IRQ 124
[    0.616886] pcieport 0000:00:1c.4: PME: Signaling with IRQ 125
[    0.616950] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    0.616975] efifb: probing for efifb
[    0.616988] efifb: framebuffer at 0xb0000000, using 8128k, total 8128k
[    0.616990] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[    0.616991] efifb: scrolling: redraw
[    0.616993] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.617048] Console: switching to colour frame buffer device 240x67
[    0.620670] fb0: EFI VGA frame buffer device
[    0.620688] intel_idle: MWAIT substates: 0x11142120
[    0.620689] intel_idle: v0.5.1 model 0x5E
[    0.620920] intel_idle: Local APIC timer is reliable in all C-states
[    0.621101] ACPI: AC Adapter [AC0] (on-line)
[    0.621167] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[    0.621202] ACPI: Lid Switch [LID]
[    0.621229] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[    0.621795] ACPI: Sleep Button [SLPB]
[    0.621863] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    0.625865] ACPI: Power Button [PWRF]
[    0.627944] thermal LNXTHERM:00: registered as thermal_zone0
[    0.627962] ACPI: Thermal Zone [THRM] (61 C)
[    0.628237] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.631657] Non-volatile memory driver v1.3
[    0.631685] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[    0.631704] AMD-Vi: AMD IOMMUv2 functionality not available on this system
[    0.634592] ahci 0000:00:17.0: version 3.0
[    0.639368] battery: ACPI: Battery Slot [BAT0] (battery present)
[    0.647023] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf impl SATA mode
[    0.647061] ahci 0000:00:17.0: flags: 64bit ncq sntf pm led clo only pio slum part ems deso sadm sds apst 
[    0.656679] scsi host0: ahci
[    0.657169] scsi host1: ahci
[    0.657579] scsi host2: ahci
[    0.657694] scsi host3: ahci
[    0.657730] ata1: SATA max UDMA/133 abar m2048@0xdf433000 port 0xdf433100 irq 126
[    0.657755] ata2: SATA max UDMA/133 abar m2048@0xdf433000 port 0xdf433180 irq 126
[    0.657813] ata3: SATA max UDMA/133 abar m2048@0xdf433000 port 0xdf433200 irq 126
[    0.657851] ata4: SATA max UDMA/133 abar m2048@0xdf433000 port 0xdf433280 irq 126
[    0.657910] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.657952] ehci-pci: EHCI PCI platform driver
[    0.658009] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.658062] ohci-pci: OHCI PCI platform driver
[    0.658096] uhci_hcd: USB Universal Host Controller Interface driver
[    0.658153] usbcore: registered new interface driver usbserial_generic
[    0.658223] usbserial: USB Serial support registered for generic
[    0.658297] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[    0.658316] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    0.659373] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.659615] rtc_cmos 00:02: RTC can wake from S4
[    0.660223] rtc_cmos 00:02: registered as rtc0
[    0.660376] rtc_cmos 00:02: setting system clock to 2021-02-15T18:35:36 UTC (1613414136)
[    0.660438] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    0.660482] intel_pstate: Intel P-state driver initializing
[    0.660853] intel_pstate: HWP enabled
[    0.660885] ledtrig-cpu: registered to indicate activity on CPUs
[    0.668016] pstore: Registered efi as persistent store backend
[    0.669081] hid: raw HID events driver (C) Jiri Kosina
[    0.670179] intel_pmc_core INT33A1:00:  initialized
[    0.671292] drop_monitor: Initializing network drop monitor service
[    0.672560] Initializing XFRM netlink socket
[    0.673845] NET: Registered protocol family 10
[    0.682603] Segment Routing with IPv6
[    0.684248] RPL Segment Routing with IPv6
[    0.685895] NET: Registered protocol family 17
[    0.688363] microcode: sig=0x506e3, pf=0x20, revision=0xe2
[    0.690133] microcode: Microcode Update Driver: v2.2.
[    0.690138] IPI shorthand broadcast: enabled
[    0.693395] sched_clock: Marking stable (689737217, 3636611)->(700557462, -7183634)
[    0.695300] registered taskstats version 1
[    0.696940] Loading compiled-in X.509 certificates
[    0.699039] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    0.704585] Loaded X.509 cert 'Build time autogenerated kernel key: 171a26c9f62e51c230fc049a2078c3fe79ddd398'
[    0.706684] zswap: loaded using pool lz4/z3fold
[    0.708939] Key type ._fscrypt registered
[    0.710686] Key type .fscrypt registered
[    0.712405] Key type fscrypt-provisioning registered
[    0.714360] pstore: Using crash dump compression: zstd
[    0.718263] PM:   Magic number: 9:42:595
[    0.720019] ahci 0000:00:17.0: hash matches
[    0.721952] RAS: Correctable Errors collector initialized.
[    0.981876] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.984965] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.987992] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.990957] ata3: SATA link down (SStatus 4 SControl 300)
[    0.993969] ata4.00: supports DRM functions and may not be fully accessible
[    0.996917] ata4.00: ATA-10: CT1000MX500SSD1, M3CR032, max UDMA/133
[    0.999804] ata4.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    1.002685] ata1.00: ATA-8: HFS256G39MND-2300A, 20200L00, max UDMA/133
[    1.005582] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.008476] ata2.00: ATA-8: HGST HTS721010A9E630, JB0OA3J0, max UDMA/133
[    1.011385] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.014775] ata1.00: configured for UDMA/133
[    1.016967] ahci 0000:00:17.0: port does not support device sleep
[    1.019124] ata4.00: supports DRM functions and may not be fully accessible
[    1.019216] scsi 0:0:0:0: Direct-Access     ATA      HFS256G39MND-230 0L00 PQ: 0 ANSI: 5
[    1.021107] ata2.00: configured for UDMA/133
[    1.022747] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[    1.024270] scsi 1:0:0:0: Direct-Access     ATA      HGST HTS721010A9 A3J0 PQ: 0 ANSI: 5
[    1.024452] ata4.00: configured for UDMA/133
[    1.025554] sd 0:0:0:0: [sda] Write Protect is off
[    1.026976] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.028085] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.028095] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.029381] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    1.032865] sd 1:0:0:0: [sdb] Write Protect is off
[    1.033992] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.034001] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.034789] ahci 0000:00:17.0: port does not support device sleep
[    1.036442] scsi 3:0:0:0: Direct-Access     ATA      CT1000MX500SSD1  032  PQ: 0 ANSI: 5
[    1.036918]  sda: sda1 sda2 sda3 sda4 sda5 sda6
[    1.037722] sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.039201] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.039891] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[    1.039897] sd 3:0:0:0: [sdc] Write Protect is off
[    1.043305] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    1.043317] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.046030]  sdc: sdc1
[    1.047432] sd 3:0:0:0: [sdc] supports TCG Opal
[    1.048557] sd 3:0:0:0: [sdc] Attached SCSI disk
[    1.105393]  sdb: sdb1
[    1.109155] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.114871] Freeing unused decrypted memory: 2036K
[    1.118530] Freeing unused kernel image (initmem) memory: 1716K
[    1.121682] Write protecting the kernel read-only data: 26624k
[    1.125879] Freeing unused kernel image (text/rodata gap) memory: 2036K
[    1.129722] Freeing unused kernel image (rodata/data gap) memory: 1560K
[    1.191027] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.191855] rodata_test: all tests were successful
[    1.192672] x86/mm: Checking user space page tables
[    1.235553] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.236344] CFS CPU scheduler.
[    1.237127] Run /init as init process
[    1.237911]   with arguments:
[    1.237912]     /init
[    1.237912]     splash
[    1.237913]   with environment:
[    1.237913]     HOME=/
[    1.237914]     TERM=linux
[    1.237914]     BOOT_IMAGE=/vmlinuz-linux-zen
[    1.261524] systemd[1]: systemd 247.3-1-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    1.275099] systemd[1]: Detected architecture x86-64.
[    1.276020] systemd[1]: Running in initial RAM disk.
[    1.290214] systemd[1]: Initializing machine ID from random generator.
[    1.314007] systemd[1]: Queued start job for default target Initrd Default Target.
[    1.315011] systemd[1]: Reached target Local File Systems.
[    1.316930] systemd[1]: Reached target Paths.
[    1.318785] systemd[1]: Reached target Slices.
[    1.320635] systemd[1]: Reached target Swap.
[    1.322478] systemd[1]: Reached target Timers.
[    1.324429] systemd[1]: Listening on Journal Audit Socket.
[    1.326381] systemd[1]: Listening on Journal Socket (/dev/log).
[    1.328344] systemd[1]: Listening on Journal Socket.
[    1.330286] systemd[1]: Listening on udev Control Socket.
[    1.332229] systemd[1]: Listening on udev Kernel Socket.
[    1.334126] systemd[1]: Reached target Sockets.
[    1.335960] systemd[1]: Condition check resulted in Create list of static device nodes for the current kernel being skipped.
[    1.343857] systemd[1]: Starting Journal Service...
[    1.347062] systemd[1]: Starting Load Kernel Modules...
[    1.349597] systemd[1]: Starting Create Static Device Nodes in /dev...
[    1.351374] Linux agpgart interface v0.103
[    1.353226] systemd[1]: Starting Coldplug All udev Devices...
[    1.355837] systemd[1]: Finished Create Static Device Nodes in /dev.
[    1.358805] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    1.386131] systemd[1]: Started Rule-based Manager for Device Events and Files.
[    1.388458] audit: type=1130 audit(1613414137.226:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/init" hostname=? addr=? terminal=? res=success'
[    1.401517] systemd[1]: Started Journal Service.

I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#31 2021-02-15 21:10:36

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Xwang wrote:

does it mean that the issue happens in the first 0.1 seconds (otherwise I should see something on the screen)?

The initramfs gets unpacked later. I think the error occurs after that.

[    0.311824] Trying to unpack rootfs image as initramfs...
Xwang wrote:

Should I try  'intremap=no_x2apic_optout' to override the BIOS setting as suggested by the kernel?

I don't think any of these suggestions will lead to any success.

Do you really need 'splash'? Beside being just cosmetics it might be error prone.
Are you sure you need 'pci=noaer'? That's disabling 'PCI advanced error reporting'. Also that 'mitigations=auto,nosmt' could be running wild.

Last edited by Maniaxx (2021-02-15 21:19:07)


sys2064

Offline

#32 2021-02-15 22:28:17

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Maniaxx wrote:
Xwang wrote:

does it mean that the issue happens in the first 0.1 seconds (otherwise I should see something on the screen)?

The initramfs gets unpacked later. I think the error occurs after that.

[    0.311824] Trying to unpack rootfs image as initramfs...
Xwang wrote:

Should I try  'intremap=no_x2apic_optout' to override the BIOS setting as suggested by the kernel?

I don't think any of these suggestions will lead to any success.

Do you really need 'splash'? Beside being just cosmetics it might be error prone.
Are you sure you need 'pci=noaer'? That's disabling 'PCI advanced error reporting'. Also that 'mitigations=auto,nosmt' could be running wild.

I removed splash and pci=noaer and still the issue is present.

When does grub terminate its work and starts the linux kernel? When "Trying to unpack rootfs image as initramfs..." appears?

Last edited by Xwang (2021-02-15 22:32:18)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#33 2021-02-16 15:22:14

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

The bootloader has to place the initramfs image and the kernel into memory first. You could try to do that in GRUB console manually.

It wouldn't be the worst decision to test systemd-boot just to see how it behaves.

You could also do a memtest. Just to make sure basic functionality is ok.

Last edited by Maniaxx (2021-02-16 15:41:56)


sys2064

Offline

#34 2021-02-16 18:59:05

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

I'm reading https://wiki.archlinux.org/index.php/sy … g_XBOOTLDR which is the way I want to install systemd-boot because I already have and esp partition mounted as /efi and a /boot partition (/dev/sda6) where grub is installed and the kernel images are stored (since some weeks ago esp was mounted as /boot but I had to change because it didn't have enough free space).
This is the output of  sudo fdisk -x /dev/sda

Disk /dev/sda: 238,47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: HFS256G39MND-230
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A5768815-48AF-468F-9953-E3026E6F572B
First LBA: 34
Last LBA: 500118158
Alternative LBA: 500118191
Partition entries LBA: 2
Allocated partition entries: 128

Dispositivo     Start      Fine   Settori Type-UUID                            UUID                                 Nome                Attrs
/dev/sda1        2048    534527    532480 C12A7328-F81F-11D2-BA4B-00A0C93EC93B E01F44BA-0EF8-4818-B47D-80BF6B4A6B7C EFI system partition
                                                                                                                                        
/dev/sda2      534528    567295     32768 E3C9E316-0B5C-4DB8-817D-F92DF00215AE 5EE8930D-6642-4B08-9A36-380010958732 Microsoft reserved partition
                                                                                                                                        
/dev/sda3      567296 158642467 158075172 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 0D76CD43-0519-4C28-BB75-CEDF4401BF27 Basic data partition
                                                                                                                                        
/dev/sda4   158644224 159821823   1177600 DE94BBA4-06D1-4D40-A16A-BFD50179D6AC D8FED24C-247D-4346-B36F-60BF9DFA4C1C                     RequiredPartition GUID:63
/dev/sda5   159823872 499095551 339271680 0FC63DAF-8483-4772-8E79-3D69D8477DE4 A7FF8847-F9E3-46EF-8F0D-A9183B0D1D3F ArchRootSSD         
/dev/sda6   499095552 500117503   1021952 0FC63DAF-8483-4772-8E79-3D69D8477DE4 B1DB6544-BEFA-6947-9EB0-476F3D9442DC                     NoBlockIOProtocol LegacyBIOSBootable GUID:49,52,53,63

As you can see the GUID type of /dev/sda6 is not bc13c2ff-59e6-4262-a352-b275fd6f7172 and it is an ext4 partition.
I suppose I've to change it to fat32 and use the correct GUID. Is it correct?
If so can I simply copy file and folders which are in /boot in a tmp folder and then write them back into the newly reformatted /boot modyfing fstab accordngly?

Last edited by Xwang (2021-02-16 19:01:31)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#35 2021-02-16 21:21:57

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Xwang wrote:

As you can see the GUID type of /dev/sda6 is not bc13c2ff-59e6-4262-a352-b275fd6f7172 and it is an ext4 partition.
I suppose I've to change it to fat32 and use the correct GUID. Is it correct?

Yes.

Xwang wrote:

If so can I simply copy file and folders which are in /boot in a tmp folder and then write them back into the newly reformatted /boot modyfing fstab accordngly?

Yes. You could also just re-install the kernel (pacman -S linux). This would also confirm correct file placement and there shouldn't be any surprises on next kernel update.

Don't forget about the recovery option (usb-stick or 2nd system). Good luck! smile

Last edited by Maniaxx (2021-02-16 21:33:20)


sys2064

Offline

#36 2021-02-17 18:23:39

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

I've just redone the process I've made one month ago (see https://bbs.archlinux.org/viewtopic.php?id=262654) to cahnge the boot partition from ext4 to vfat so that to be able to use as XBOOTLDR with systemd-boot.
this is my fstab:

# 
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda5 UUID=74296c4e-84df-4eda-87a1-09be9d8e114b LABEL=ArchRootSSD 
UUID=74296c4e-84df-4eda-87a1-09be9d8e114b       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sdc1 UUID=dca8b900-5a1a-4d64-b193-9194d4b214ff LABEL=ArchDataSSD
UUID=dca8b900-5a1a-4d64-b193-9194d4b214ff       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sdb1 UUID=91e93ef5-a6c7-45c9-94a9-90497f48754d LABEL=ArchDataHDD
UUID=91e93ef5-a6c7-45c9-94a9-90497f48754d       /dataBackup     ext4            rw,relatime,data=ordered        0 2

# /dev/sda1 UUID=F0D6-7769                            LABEL=SYSTEM
UUID=F0D6-7769                                  /efi            vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda6 UIDD=0C8C-E451                            LABEL=XBOOTLDR
UUID=0C8C-E451                                  /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

/swapfile none swap defaults 0 0

This is the output of lsblk -f

NAME   FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                 
├─sda1 vfat   FAT32 SYSTEM      F0D6-7769                             229,8M    10% /efi
├─sda2                                                                              
├─sda3 ntfs         OS          9A7CDA157CD9EC4F                                    
├─sda4 ntfs                     12D2C4E3D2C4CBE3                                    
├─sda5 ext4   1.0   ArchRootSSD 74296c4e-84df-4eda-87a1-09be9d8e114b   81,8G    43% /
└─sda6 vfat   FAT32 XBOOTLDR    0C8C-E451                             221,1M    56% /boot
sdb                                                                                 
└─sdb1 ext4   1.0   ArchDataHDD 91e93ef5-a6c7-45c9-94a9-90497f48754d  162,8G    77% /dataBackup
sdc                                                                                 
└─sdc1 ext4   1.0   ArchDataSSD dca8b900-5a1a-4d64-b193-9194d4b214ff  191,2G    74% /home

I've reinstalled grub using this command

sudo grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB --boot-directory=/boot

I've reinstalled intel-ucode, linux, linux-lts and linux-zen and then I've executed

sudo grub-mkconfig -o /boot/grub/grub.cfg

Then I've rebooted the pc to check if grub with fat32 still was working before continuing and it has booted correclty, but once I entered the DE I've discovered that the /boot partition was completely empty!!!
So now I've executed again the commands to reinstall grub, kernels and configure grunb in boot, but before trying to reboot again I'm wondering if I've done something wrongly and why the /boot partition has been emptied.
I've still to install systemd-boot, change the XBOOTLDR partition GUID type and do all the configuration to have systemd-boot working, but before doing that I want to have a working GRUB.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#37 2021-02-17 19:33:40

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Check with 'mount' if /boot is mounted at all. It could be overmounted by systemd or something. Otherwise mount /boot manually to take a look if data is there. Eventually check the efi partition for kernel and initramfs. Maybe check the logs for what happened to /boot.

Last edited by Maniaxx (2021-02-17 19:38:33)


sys2064

Offline

#38 2021-02-17 22:28:29

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

This is the output of mount and it seems correct:

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=8117640k,nr_inodes=2029410,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3256828k,nr_inodes=819200,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
/dev/sda5 on / type ext4 (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=774)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=8142064k,nr_inodes=409600,inode64)
/dev/sda6 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda1 on /efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sdb1 on /dataBackup type ext4 (rw,relatime,data=ordered)
/dev/sdc1 on /home type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1628412k,nr_inodes=407103,mode=700,uid=1000,gid=1000,inode64)

/dev/sda6 was mounted on /boot but it was empty and neither journalctl nor dmesg contain anything related.

EDIT: I have rebooted after having repopulated the boot directory and the file inside /boot aare still present. Is it possible that the issue was related with the errors=remount-ro option of the /boot partition (I've copied the options from the efi one and generally speaking I think that my fstab is a result of what was suggested years ago when I installed the system on this pc. Should I change something?)

Last edited by Xwang (2021-02-17 23:11:05)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#39 2021-02-18 10:57:15

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

What about rEFInd instead of systemd-boot?
It seems simpler to configure (with the ability to automatically create menu entries for the installed kernels, much like grub).
I'm still not so sure how to create them for systemd-boot considering that I have to use the XBOOTLDR partition because the EPS one is too small and surrounded by windows reserved partitions which I do not want to resize/move at all.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#40 2021-02-18 12:14:23

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Sure, you can also try rEFInd. Or even better try both.

I would try to investigate why /boot was empty and it still booted. Maybe there's another bootloader on a different hdd. Or the kernel/initramfs is on ESP.
It's also possible that the SSD is corrupt playing tricks on you (files vanish, won't get stored).

Last edited by Maniaxx (2021-02-18 12:16:44)


sys2064

Offline

#41 2021-02-18 12:20:36

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Maniaxx wrote:

Sure, you can also try rEFInd. Or even better try both.

I would try to investigate why /boot was empty and it still booted. Maybe there's another bootloader on a different hdd. Or the kernel/initramfs is on ESP.

Neither of the two.
The strange thing is that PC was able to boot and then the /boot partition became empty somehow.
Before booting a loading initial ramdisk happened.
So maybe the fat32 went corrupted and lost all of its contents, but in such a case it would have not been able to reboot at all.
It is one of the strangest thing which have happened to me since I use linux.
In the journactl I've seen that just after that boot a fstrim "Started Discard unused blocks once a week." was executed, but I doubt it has anything to do with that.

Last edited by Xwang (2021-02-18 12:26:11)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#42 2021-02-18 12:36:34

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

If I run genfstab -U I get the following:

# /dev/sda5 LABEL=ArchRootSSD
UUID=74296c4e-84df-4eda-87a1-09be9d8e114b       /               ext4            rw,relatime     0 1

# tracefs
tracefs                 /sys/kernel/tracing     tracefs         rw,nosuid,nodev,noexec  0 0

# /dev/sdc1 LABEL=ArchDataSSD
UUID=dca8b900-5a1a-4d64-b193-9194d4b214ff       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sda6 LABEL=XBOOTLDR
UUID=0C8C-E451          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/sda1 LABEL=SYSTEM
UUID=F0D6-7769          /efi            vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/sdb1 LABEL=ArchDataHDD
UUID=91e93ef5-a6c7-45c9-94a9-90497f48754d       /dataBackup     ext4            rw,relatime,data=ordered        0 2

/swapfile               none            swap            defaults        0 0

that is the same as mine except for the order in which partitions are written (is it important?), the tracefs which is not present in mine and the lack of data=ordered for the root
Is it better to use this instead of mine?


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#43 2021-02-18 13:13:46

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

I don't think it's important.


sys2064

Offline

#44 2021-02-18 18:54:52

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

So I'0ve installed refind

This is the refind_linux.conf which is in the /boot folder with kernle images, initramfs and inte_ucode.img and which I've modified adding the initrd=intel-ucode.img initrd=initramfs-%v.img

"Boot with standard options"  "root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw earlyprintk=vga,keep loglevel=7 rd.systemd.show_status=auto rd.udev.log_priority=3 mitigations=auto,nosmt nvidia-drm.modeset=1 initrd=intel-ucode.img initrd=initramfs-%v.img"
"Boot using fallback initramfs"  "root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw earlyprintk=vga,keep loglevel=7 rd.systemd.show_status=auto rd.udev.log_priority=3 mitigations=auto,nosmt nvidia-drm.modeset=1 initrd=intel-ucode.img initrd=initramfs-%v-fallback.img"

Below there is the refind.conf
What I do not understand is if it is all I've to do to have it working and see my three kernels (linux-zen, linux and linux-lts), their fallbacks and windows 10.
When does refind read these configurations? at runtime or I've to execute refind_install so that it use them at next boot?
Is it possible to add an entry for grub so that to use it in case refind ones do not work?
I fear I've made mistakes and to find myself stuck without being able to boot nothing

#
# refind.conf
# Configuration file for the rEFInd boot menu
#

# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout). Setting it to -1 causes
# an immediate boot to the default OS *UNLESS* a keypress is in the buffer
# when rEFInd launches, in which case that keypress is interpreted as a
# shortcut key. If no matching shortcut is found, rEFInd displays its
# menu with no timeout.
#
timeout 5

# Normally, when the timeout period has passed, rEFInd boots the
# default_selection. If the following option is uncommented, though,
# rEFInd will instead attempt to shut down the computer.
# CAUTION: MANY COMPUTERS WILL INSTEAD HANG OR REBOOT! Macs and more
# recent UEFI-based PCs are most likely to work with this feature.
# Default value is true
#
#shutdown_after_timeout

# Whether to store rEFInd's rEFInd-specific variables in NVRAM (1, true,
# or on) or in files in the "vars" subdirectory of rEFInd's directory on
# disk (0, false, or off). Using NVRAM works well with most computers;
# however, it increases wear on the motherboard's NVRAM, and if the EFI
# is buggy or the NVRAM is old and worn out, it may not work at all.
# Storing variables on disk is a viable alternative in such cases, or
# if you want to minimize wear and tear on the NVRAM; however, it won't
# work if rEFInd is stored on a filesystem that's read-only to the EFI
# (such as an HFS+ volume), and it increases the risk of filesystem
# damage. Note that this option affects ONLY rEFInd's own variables,
# such as the PreviousBoot, HiddenTags, HiddenTools, and HiddenLegacy
# variables. It does NOT affect Secure Boot or other non-rEFInd
# variables.
# Default is true
#
#use_nvram false

# Screen saver timeout; the screen blanks after the specified number of
# seconds with no keyboard input. The screen returns after most keypresses
# (unfortunately, not including modifier keys such as Shift, Control, Alt,
# or Option). Setting a value of "-1" causes rEFInd to start up with its
# screen saver active. The default is 0, which disables the screen saver.
#
#screensaver 300

# Hide user interface elements for personal preference or to increase
# security:
#  banner      - the rEFInd title banner (built-in or loaded via "banner")
#  label       - boot option text label in the menu
#  singleuser  - remove the submenu options to boot macOS in single-user
#                or verbose modes; affects ONLY macOS
#  safemode    - remove the submenu option to boot macOS in "safe mode"
#  hwtest      - the submenu option to run Apple's hardware test
#  arrows      - scroll arrows on the OS selection tag line
#  hints       - brief command summary in the menu
#  editor      - the options editor (+, F2, or Insert on boot options menu)
#  badges      - device-type badges for boot options
#  all         - all of the above
# Default is none of these (all elements active)
#
#hideui singleuser
#hideui all

# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Icon files may be in any supported format -- ICNS (*.icns), BMP (*.bmp),
# PNG (*.png), or JPEG (*.jpg or *.jpeg); however, rEFInd's BMP and JPEG
# implementations do not support transparency, which is highly desirable
# in icons.
# Default is "icons".
#
#icons_dir myicons
#icons_dir icons/snowy

# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG and JPEG
# images. (ICNS images can also be used, but ICNS has limitations that
# make it a poor choice for this purpose.) PNG and JPEG support is
# limited by the underlying libraries; some files, like progressive JPEGs,
# will not work.
#
#banner hostname.bmp
#banner mybanner.jpg
#banner icons/snowy/banner-snowy.png

# Specify how to handle banners that aren't exactly the same as the screen
# size:
#  noscale     - Crop if too big, show with border if too small
#  fillscreen  - Fill the screen
# Default is noscale
#
#banner_scale fillscreen

# Icon sizes. All icons are square, so just one value is specified. The
# big icons are used for OS selectors in the first row and the small
# icons are used for tools on the second row. Drive-type badges are 1/4
# the size of the big icons. Legal values are 32 and above. If the icon
# files do not hold icons of the proper size, the icons are scaled to
# the specified size. The default values are 48 and 128 for small and
# big icons, respectively.
#
#small_icon_size 96
#big_icon_size 256

# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons. If an image other
# than the optimal size is specified, it will be scaled in a way that may
# be ugly.
#
# Like the banner option above, these options take a filename of an
# uncompressed BMP, PNG, JPEG, or ICNS image file with a color depth of
# 24, 8, 4, or 1 bits. The PNG or ICNS format is required if you need
# transparency support (to let you "see through" to a full-screen banner).
#
#selection_big   selection-big.bmp
#selection_small selection-small.bmp

# Set the font to be used for all textual displays in graphics mode.
# For best results, the font must be a PNG file with alpha channel
# transparency. It must contain ASCII characters 32-126 (space through
# tilde), inclusive, plus a glyph to be displayed in place of characters
# outside of this range, for a total of 96 glyphs. Only monospaced fonts
# are supported. Fonts may be of any size, although large fonts can
# produce display irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#
#font myfont.png

# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#
textonly

# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#
textmode 2

# Set the screen's video resolution. Pass this option one of the following:
#  * two integer values, corresponding to the X and Y resolutions
#  * one integer value, corresponding to a GOP (UEFI) video mode
#  * the string "max", which sets the maximum available resolution
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
#resolution 1024 768
#resolution 1440 900
#resolution 3
#resolution max

# Enable touch screen support. If active, this feature enables use of
# touch screen controls (as on tablets). Note, however, that not all
# tablets' EFIs provide the necessary underlying support, so this
# feature may not work for you. If it does work, you should be able
# to launch an OS or tool by touching it. In a submenu, touching
# anywhere launches the currently-selection item; there is, at present,
# no way to select a specific submenu item. This feature is mutually
# exclusive with the enable_mouse feature. If both are uncommented,
# the one read most recently takes precedence.
#
#enable_touch

# Enable mouse support. If active, this feature enables use of the
# computer's mouse. Note, however, that not all computers' EFIs
# provide the necessary underlying support, so this feature may not
# work for you. If it does work, you should be able to launch an
# OS or tool by clicking it with the mouse pointer. This feature
# is mutually exclusive with the enable_touch feature. If both
# are uncommented, the one read most recently takes precedence.
#
#enable_mouse

# Size of the mouse pointer, in pixels, per side.
# Default is 16
#
#mouse_size 16

# Speed of mouse tracking. Higher numbers equate to faster
# mouse movement. This option requires that enable_mouse be
# uncommented.
# Legal values are between 1 and 32. Default is 4.
#
#mouse_speed 4

# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except macOS. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
#   osx     - macOS
#   linux   - A Linux kernel with EFI stub loader
#   elilo   - The ELILO boot loader
#   grub    - The GRUB (Legacy or 2) boot loader
#   windows - Microsoft Windows
# Default value: osx
#
#use_graphics_for osx,linux

# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
#  shell            - the EFI shell (requires external program; see rEFInd
#                     documentation for details)
#  memtest          - the memtest86 program, in EFI/tools, EFI/memtest86,
#                     EFI/memtest, EFI/tools/memtest86, or EFI/tools/memtest
#  gptsync          - the (dangerous) gptsync.efi utility (requires external
#                     program; see rEFInd documentation for details)
#  gdisk            - the gdisk partitioning program
#  apple_recovery   - boots the Apple Recovery HD partition, if present
#  windows_recovery - boots an OEM Windows recovery tool, if present
#                     (see also the windows_recovery_files option)
#  mok_tool         - makes available the Machine Owner Key (MOK) maintenance
#                     tool, MokManager.efi, used on Secure Boot systems
#  csr_rotate       - adjusts Apple System Integrity Protection (SIP)
#                     policy. Requires "csr_values" to be set.
#  install          - an option to install rEFInd from the current location
#                     to another ESP
#  bootorder        - adjust the EFI's (NOT rEFInd's) boot order
#  about            - an "about this program" option
#  hidden_tags      - manage hidden tags
#  exit             - a tag to exit from rEFInd
#  shutdown         - shuts down the computer (a bug causes this to reboot
#                     many UEFI systems)
#  reboot           - a tag to reboot the computer
#  firmware         - a tag to reboot the computer into the firmware's
#                     user interface (ignored on older computers)
#  fwupdate         - a tag to update the firmware; launches the fwupx64.efi
#                     (or similar) program
#  netboot          - launch the ipxe.efi tool for network (PXE) booting
# Default is shell,memtest,gdisk,apple_recovery,windows_recovery,mok_tool,about,hidden_tags,shutdown,reboot,firmware,fwupdate
#
#showtools shell, bootorder, gdisk, memtest, mok_tool, apple_recovery, windows_recovery, about, hidden_tags, reboot, exit, firmware, fwupdate

# Tool binaries to be excluded from the tools line, even if the
# general class is specified in showtools. This enables trimming an
# overabundance of tools, as when you see multiple mok_tool entries
# after installing multiple Linux distributions.
# Just as with dont_scan_files, you can specify a filename alone, a
# full pathname, or a volume identifier (filesystem label, partition
# name, or partition GUID) and a full pathname.
# Default is an empty list (nothing is excluded)
#
#dont_scan_tools ESP2:/EFI/ubuntu/mmx64.efi,gptsync_x64.efi

# Boot loaders that can launch a Windows restore or emergency system.
# These tend to be OEM-specific.
# Default is LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi
#
#windows_recovery_files LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi

# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#
#scan_driver_dirs EFI/tools/drivers,drivers

# Which types of boot loaders to search, and in what order to display them:
#  internal      - internal EFI disk-based boot loaders
#  external      - external EFI disk-based boot loaders
#  optical       - EFI optical discs (CD, DVD, etc.)
#  netboot       - EFI network (PXE) boot options
#  hdbios        - BIOS disk-based boot loaders
#  biosexternal  - BIOS external boot loaders (USB, eSATA, etc.)
#  cd            - BIOS optical-disc boot loaders
#  manual        - use stanzas later in this configuration file
#  firmware      - boot EFI programs set in the firmware's NVRAM
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# The netboot option is experimental and relies on the ipxe.efi and
# ipxe_discover.efi program files.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#
#scanfor internal,external,optical,manual,firmware

# By default, rEFInd relies on the UEFI firmware to detect BIOS-mode boot
# devices. This sometimes doesn't detect all the available devices, though.
# For these cases, uefi_deep_legacy_scan results in a forced scan and
# modification of NVRAM variables on each boot. Adding "0", "off", or
# "false" resets to the default value. This token has no effect on Macs or
# when no BIOS-mode options are set via scanfor.
# Default is unset (or "uefi_deep_legacy_scan false")
#
#uefi_deep_legacy_scan

# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#
#scan_delay 5

# When scanning volumes for EFI boot loaders, rEFInd always looks for
# macOS's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#
#also_scan_dirs boot,ESP2:EFI/linux/kernels

# Partitions (or whole disks, for legacy-mode boots) to omit from scans.
# For EFI-mode scans, you normally specify a volume by its label, which you
# can obtain in an EFI shell by typing "vol", from Linux by typing
# "blkid /dev/{devicename}", or by examining the disk's label in various
# OSes' file browsers. It's also possible to identify a partition by its
# unique GUID (aka its "PARTUUID" in Linux parlance). (Note that this is
# NOT the partition TYPE CODE GUID.) This identifier can be obtained via
# "blkid" in Linux or "diskutil info {partition-id}" in macOS.
# For legacy-mode scans, you can specify any subset of the boot loader
# description shown when you highlight the option in rEFInd.
# The default is "LRS_ESP".
#
#dont_scan_volumes "Recovery HD"

# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory, the EFI/tools directory, the
# EFI/memtest directory, the EFI/memtest86 directory, or the
# com.apple.recovery.boot directory. Using the dont_scan_dirs option
# enables you to "blacklist" other directories; but be sure to use "+"
# as the first element if you want to continue blacklisting existing
# directories. You might use this token to keep EFI/boot/bootx64.efi out
# of the menu if that's a duplicate of another boot loader or to exclude
# a directory that holds drivers or non-bootloader utilities provided by
# a hardware manufacturer. If a directory is listed both here and in
# also_scan_dirs, dont_scan_dirs takes precedence. Note that this
# blacklist applies to ALL the filesystems that rEFInd scans, not just
# the ESP, unless you precede the directory name by a filesystem name or
# partition unique GUID, as in "myvol:EFI/somedir" to exclude EFI/somedir
# from the scan on the myvol volume but not on other volumes.
#
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell,EFI/memtest86

# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, various Secure Boot and recovery
# tools are present in this list, but may appear as second-row
# items.
# The file may be specified as a bare name (e.g., "notme.efi"), as
# a complete pathname (e.g., "/EFI/somedir/notme.efi"), or as a
# complete pathname with volume (e.g., "SOMEDISK:/EFI/somedir/notme.efi"
# or 2C17D5ED-850D-4F76-BA31-47A561740082:/EFI/somedir/notme.efi").
# OS tags hidden via the Delete or '-' key in the rEFInd menu are
# added to this list, but stored in NVRAM.
# The default is shim.efi,shim-fedora.efi,shimx64.efi,PreLoader.efi,
# TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,
# HashTool-signed.efi,bootmgr.efi,fb{arch}.efi
# (where "{arch}" is the architecture code, like "x64").
# If you want to keep these defaults but add to them, be sure to
# specify "+" as the first item in the new list; if you don't, then
# items from the default list are likely to appear.
#
#dont_scan_files shim.efi,MokManager.efi

# EFI NVRAM Boot#### variables that should NOT be presented as loaders
# when "firmware" is an option to "scanfor". The comma-separated list
# presented here contains strings that are matched against the
# description field -- if a value here is a case-insensitive substring
# of the boot option description, then it will be excluded from the
# boot list. To specify a string that includes a space, enclose it
# in quotes. Specifying "shell" will counteract the automatic
# inclusion of built-in EFI shells.
#
#dont_scan_firmware HARDDISK,shell,"Removable Device"

# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When set to "1", "true", or "on", this
# option causes all files in scanned directories with names that begin with
# "vmlinuz", "bzImage", or "kernel" to be included as loaders, even if they
# lack ".efi" extensions. Passing this option a "0", "false", or "off" value
# causes kernels without ".efi" extensions to NOT be scanned.
# Default is "true" -- to scan for kernels without ".efi" extensions.
#
#scan_all_linux_kernels false

# Combine all Linux kernels in a given directory into a single entry.
# When so set, the kernel with the most recent time stamp will be launched
# by default, and its filename will appear in the entry's description.
# To launch other kernels, the user must press F2 or Insert; alternate
# kernels then appear as options on the sub-menu.
# Default is "true" -- kernels are "folded" into a single menu entry.
#
fold_linux_kernels false

# Comma-delimited list of strings to treat as if they were numbers for the
# purpose of kernel version number detection. These strings are matched on a
# first-found basis; that is, if you want to treat both "linux-lts" and
# "linux" as version strings, they MUST be specified as "linux-lts,linux",
# since if you specify it the other way, both vmlinuz-linux and
# vmlinuz-linux-lts will return with "linux" as the "version string," which
# is not what you'd want. Also, if the kernel or initrd file includes both a
# specified string and digits, the "version string" includes both. For
# instance, "vmlinuz-linux-4.8" would yield a version string of "linux-4.8".
# This option is intended for Arch and other distributions that don't include
# version numbers in their kernel filenames, but may provide other uniquely
# identifying strings for multiple kernels. If this feature causes problems
# (say, if your kernel filename includes "linux" but the initrd filename
# doesn't), be sure this is set to an empty string
# (extra_kernel_version_strings "") or comment out the option to disable it.
# Default is no extra version strings
#
extra_kernel_version_strings linux-zen,linux-lts,linux

# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#
#max_tags 0

# Set the default menu selection.  The available arguments match the
# keyboard accelerators available within rEFInd.  You may select the
# default loader using:
#  - A digit between 1 and 9, in which case the Nth loader in the menu
#    will be the default.
#  - A "+" symbol at the start of the string, which refers to the most
#    recently booted loader.
#  - Any substring that corresponds to a portion of the loader's title
#    (usually the OS's name, boot loader's path, or a volume or
#    filesystem title).
# You may also specify multiple selectors by separating them with commas
# and enclosing the list in quotes. (The "+" option is only meaningful in
# this context.)
# If you follow the selector(s) with two times, in 24-hour format, the
# default will apply only between those times. The times are in the
# motherboard's time standard, whether that's UTC or local time, so if
# you use UTC, you'll need to adjust this from local time manually.
# Times may span midnight as in "23:30 00:30", which applies to 11:30 PM
# to 12:30 AM. You may specify multiple default_selection lines, in which
# case the last one to match takes precedence. Thus, you can set a main
# option without a time followed by one or more that include times to
# set different defaults for different times of day.
# The default behavior is to boot the previously-booted OS.
#
#default_selection 1
#default_selection Microsoft
#default_selection "+,bzImage,vmlinuz"
#default_selection Maintenance 23:30 2:00
#default_selection "Maintenance,macOS" 1:00 2:30

# Enable VMX bit and lock the CPU MSR if unlocked.
# On some Intel Apple computers, the firmware does not lock the MSR 0x3A.
# The symptom on Windows is Hyper-V not working even if the CPU
# meets the minimum requirements (HW assisted virtualization and SLAT)
# DO NOT SET THIS EXCEPT ON INTEL CPUs THAT SUPPORT VMX! See
# http://www.thomas-krenn.com/en/wiki/Activating_the_Intel_VT_Virtualization_Feature
# for more on this subject.
# The default is false: Don't try to enable and lock the MSR.
#
#enable_and_lock_vmx false

# Tell a Mac's EFI that macOS is about to be launched, even when it's not.
# This option causes some Macs to initialize their hardware differently than
# when a third-party OS is launched normally. In some cases (particularly on
# Macs with multiple video cards), using this option can cause hardware to
# work that would not otherwise work. On the other hand, using this option
# when it is not necessary can cause hardware (such as keyboards and mice) to
# become inaccessible. Therefore, you should not enable this option if your
# non-Apple OSes work correctly; enable it only if you have problems with
# some hardware devices. When needed, a value of "10.9" usually works, but
# you can experiment with other values. This feature has no effect on
# non-Apple computers.
# The default is inactive (no macOS spoofing is done).
#
#spoof_osx_version 10.9

# Set the CSR values for Apple's System Integrity Protection (SIP) feature.
# Values are two-byte (four-character) hexadecimal numbers. These values
# define which specific security features are enabled. Below are the codes
# for what the values mean. Add them up (in hexadecimal!) to set new values.
# Apple's "csrutil enable" and "csrutil disable" commands set values of 10
# and 877, respectively.
#   CSR_ALLOW_UNTRUSTED_KEXTS            0x0001
#   CSR_ALLOW_UNRESTRICTED_FS            0x0002
#   CSR_ALLOW_TASK_FOR_PID               0x0004
#   CSR_ALLOW_KERNEL_DEBUGGER            0x0008
#   CSR_ALLOW_APPLE_INTERNAL             0x0010
#   CSR_ALLOW_UNRESTRICTED_DTRACE        0x0020
#   CSR_ALLOW_UNRESTRICTED_NVRAM         0x0040
#   CSR_ALLOW_DEVICE_CONFIGURATION       0x0080
#   CSR_ALLOW_ANY_RECOVERY_OS            0x0100
#   CSR_ALLOW_UNAPPROVED_KEXTS           0x0200
#   CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE 0x0400
#   CSR_ALLOW_UNAUTHENTICATED_ROOT       0x0800
#csr_values 10,877

# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#
#include manual.conf

# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
#
#  volume    - identifies the filesystem from which subsequent files
#              are loaded. You can specify the volume by filesystem
#              label, by partition label, or by partition GUID number
#              (but NOT yet by filesystem UUID number).
#  loader    - identifies the boot loader file
#  initrd    - Specifies an initial RAM disk file
#  icon      - specifies a custom boot loader icon
#  ostype    - OS type code to determine boot options available by
#              pressing Insert. Valid values are "MacOS", "Linux",
#              "Windows", and "XOM". Case-sensitive.
#  graphics  - set to "on" to enable graphics-mode boot (useful
#              mainly for MacOS) or "off" for text-mode boot.
#              Default is auto-detected from loader filename.
#  options   - sets options to be passed to the boot loader; use
#              quotes if more than one option should be passed or
#              if any options use characters that might be changed
#              by rEFInd parsing procedures (=, /, #, or tab).
#  disabled  - use alone or set to "yes" to disable this entry.
#
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.

# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.

# A sample entry for a Linux 3.13 kernel with EFI boot stub support
# on a partition with a GUID of 904404F8-B481-440C-A1E3-11A5A954E601.
# This entry includes Linux-specific boot options and specification
# of an initial RAM disk. Note uses of Linux-style forward slashes.
# Also note that a leading slash is optional in file specifications.
menuentry Linux {
    icon EFI/refind/icons/os_linux.png
    volume 904404F8-B481-440C-A1E3-11A5A954E601
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
}

# Below is a more complex Linux example, specifically for Arch Linux.
# This example MUST be modified for your specific installation; if nothing
# else, the PARTUUID code must be changed for your disk. Because Arch Linux
# does not include version numbers in its kernel and initrd filenames, you
# may need to use manual boot stanzas when using fallback initrds or
# multiple kernels with Arch. This example is modified from one in the Arch
# wiki page on rEFInd (https://wiki.archlinux.org/index.php/rEFInd).
menuentry "Arch Linux" {
    icon     /EFI/refind/icons/os_arch.png
    volume   "Arch Linux"
    loader   /boot/vmlinuz-linux
    initrd   /boot/initramfs-linux.img
    options  "root=PARTUUID=5028fa50-0079-4c40-b240-abfaf28693ea rw add_efi_memmap"
    submenuentry "Boot using fallback initramfs" {
        initrd /boot/initramfs-linux-fallback.img
    }
    submenuentry "Boot to terminal" {
        add_options "systemd.unit=multi-user.target"
    }
    disabled
}

# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refind/icons/os_linux.png
    disabled
}

# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
}

# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
}

# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.png
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
}

# MacOS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My macOS" {
    icon \EFI\refind\icons\os_mac.png
    volume "macOS boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
}

# The firmware_bootnum token takes a HEXADECIMAL value as an option
# and sets that value using the EFI's BootNext variable and then
# reboots the computer. This then causes a one-time boot of the
# computer using this EFI boot option. It can be used for various
# purposes, but one that's likely to interest some rEFInd users is
# that some Macs with HiDPI displays produce lower-resolution
# desktops when booted through rEFInd than when booted via Apple's
# own boot manager. Booting using the firmware_bootnum option
# produces the better resolution. Note that no loader option is
# used in this type of configuration.
menuentry "macOS via BootNext" {
    icon /EFI/refind/icons/os_mac.png
    firmware_bootnum 80
    disabled
}

I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#45 2021-02-18 19:45:39

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Xwang wrote:

Is it possible to add an entry for grub so that to use it in case refind ones do not work?

I've never done that but i think on EFI it should be possible as long as no files are colliding.

Xwang wrote:

I fear I've made mistakes and to find myself stuck without being able to boot nothing

You can always boot from USB-stick and chroot into your system.


sys2064

Offline

#46 2021-02-18 20:00:58

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,065

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

I strongly belief this is going in the wrong direction, you are technically loading the ramdisk, and if it happens to work with a specific reboot cycle then the general loading mechanism of UEFI isn't the issue but something else and I consider it unlikely to be fixed by swapping bootloaders around.

Much more likely are firmware issues (... check whether there's an UEFI update) or random entropy during early boot (add random.trust_cpu=on to the kernel parametrs to use the CPU's RNG for seeding)

Offline

#47 2021-02-18 21:14:53

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

V1del wrote:

you are technically loading the ramdisk, and if it happens to work with a specific reboot cycle then the general loading mechanism of UEFI isn't the issue but something else and I consider it unlikely to be fixed by swapping bootloaders around.

As far as i know the bootloader is loading, allocating and passing over the ramdisk/memory to the kernel. That might be a critical (and maybe not always bug free) process that could be handled different on other bootloaders. GRUB2 might be much more bloated/complex (and thus more error prone) than the more slick systemd-boot.

But yes, actually it was intended as a "quick test" only indeed.

Last edited by Maniaxx (2021-02-18 21:19:57)


sys2064

Offline

#48 2021-02-18 22:31:43

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

I can confirm that with refind too the freeze still happens randomly.
So I've uninstalled refind and went back to using GRUB.
I've added the kernel parameter random.trust_cpu=on, but also with taht every 3 or 4 reboot the freeze has happened.
Then I've uninstalled intel-ucode and reinstalled linux, linux-lts and linux-zen and updated grub.cfg to avoid loading itel-ucode and then I was able to do about 20 reboots without issue.
I know that intel-ucode is important, but it seems to be the suspect.

For the sake of safety I've reinstalled intel-ucode (and after 2 reboots the freeze has happened again).
On Asus site there is no uefi update available, the last BIOS (303) is the one I already have and dates back to 2019.
Should I try to use older versions of intel-ucode?

More generally speaking Windows 10 does not have this issue and as far as I know the intel-ucode is used also in Windows (even thought in a different way) every time I use it, so it seems as if the mechanism Microsoft uses is more reliable (at least on this PC). I suppose that the code base of intel-ucode is the same for both operating systems, but then maybe it is loaded in a different way? Is there anywhere an explanation on how microcode is handled by linux and windows? Just to say that it is not an hardware/firmware issue since windows 10 do not shows the same symptom.

EDIT
I've just tried to reboot in windows more than 10 times without issue.
In windows the CPU revision (which as far as I know should be related to the ucode version installed) is reported as "cc" whereas under linux it says "microcode updated early to revision 0xe2, date = 2020-07-14".
Is there a way to know which version of intel-ucode contains the cc revision for my CPU?

EDIT2
Here https://support.microsoft.com/en-us/top … aa76daa07a says that on the 1st September 2020 the  Skylake H 6th Generation Intel® Core™ Processor Family Intel® Core™ Processor i7-6700HQ CPUID 506E3 will get with the update the microcode version 0xCC, bu cc was released the 1st april 2019
So I've tried to go back to previous versions of intel-ucode till the one which used th cc revision, but still the random freeze was present even if with a different frequency. So I went back to the latest one.

EDIT3
I've tried different reboot= kernel parameters:
reboot=bios is not able to shutdown or restart the pc
reboot=efi completely turns off the pc for 5 seconds when rebooting and randomly freezes loading initial ramdisk
reboot=cold randomly freeze loading initial ramdisk and when it happens it keeps freezing so I had to change the kernel parameter from the grub editor
reboot=acpi reboot in a way very similar to what windows too (meaning the power led remains on and the keyboad light is cycled when the asus logo appears before grub, but it still randomly freezes loading initial ramdisk

what else can I do?

Last edited by Xwang (2021-02-19 19:54:05)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#49 2021-02-19 20:33:16

Xwang
Member
Registered: 2012-05-14
Posts: 321

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Adding these parameters:

 initcall_debug earlycon=efifb

the initial phase of the booting takes more time (7 seconds instead of half a second or less, but a lot of early messages are displayed and when it freezes these are the last lines:
https://i.postimg.cc/qMsvcZ34/IMG-20210219-210353.jpg
I hope it helps understand what is happening when it freezes

Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code

EDIT:
Today I 've changed the kernel parameters so that journalctl is able to log some of the initial messages and this is the output of cat /proc/cmdline:

BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw initcall_debug ignore_loglevel=1 earlycon=efifb reboot=acpi random.trust_cpu=on earlyprintk=vga,keep rd.systemd.show_status=auto rd.udev.log_priority=3 mitigations=auto,nosmt nvidia-drm.modeset=1

This is  what happens when the boot works correctly:

feb 20 12:23:30 archlinux systemd-journald[159]: Missed 201 kernel messages
feb 20 12:23:30 archlinux kernel: spurious 8259A interrupt: IRQ7.
feb 20 12:23:30 archlinux kernel: calling  con_init+0x0/0x25e @ 0
feb 20 12:23:30 archlinux kernel: Console: colour dummy device 80x25
feb 20 12:23:30 archlinux kernel: printk: console [tty0] enabled
feb 20 12:23:30 archlinux kernel: printk: bootconsole [efifb0] disabled
feb 20 12:23:30 archlinux kernel: initcall con_init+0x0/0x25e returned 0 after 0 usecs
feb 20 12:23:30 archlinux kernel: calling  hvc_console_init+0x0/0x14 @ 0
feb 20 12:23:30 archlinux kernel: initcall hvc_console_init+0x0/0x14 returned 0 after 0 usecs
feb 20 12:23:30 archlinux kernel: calling  xen_cons_init+0x0/0x50 @ 0
feb 20 12:23:30 archlinux kernel: initcall xen_cons_init+0x0/0x50 returned 0 after 0 usecs
feb 20 12:23:30 archlinux kernel: calling  univ8250_console_init+0x0/0x27 @ 0
feb 20 12:23:30 archlinux kernel: initcall univ8250_console_init+0x0/0x27 returned 0 after 0 usecs
feb 20 12:23:30 archlinux kernel: ACPI: Core revision 20200925
feb 20 12:23:30 archlinux kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
feb 20 12:23:30 archlinux kernel: APIC: Switch to symmetric I/O mode setup
feb 20 12:23:30 archlinux kernel: DMAR: Host address width 39
feb 20 12:23:30 archlinux kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
feb 20 12:23:30 archlinux kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0501e
feb 20 12:23:30 archlinux kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
feb 20 12:23:30 archlinux kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
feb 20 12:23:30 archlinux kernel: DMAR: RMRR base: 0x00000075fa2000 end: 0x00000075fc1fff
feb 20 12:23:30 archlinux kernel: DMAR: RMRR base: 0x00000078800000 end: 0x0000007affffff
feb 20 12:23:30 archlinux kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x000000007affffff], contact BIOS vendor for fixes
feb 20 12:23:30 archlinux kernel: DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x0000000078800000-0x000000007affffff]
                                  BIOS vendor: American Megatrends Inc.; Ver: N752VX.303; Product Version: 1.0       
feb 20 12:23:30 archlinux kernel: DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
feb 20 12:23:30 archlinux kernel: DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
feb 20 12:23:30 archlinux kernel: DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
feb 20 12:23:30 archlinux kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
feb 20 12:23:30 archlinux kernel: DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
feb 20 12:23:30 archlinux kernel: DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
feb 20 12:23:30 archlinux kernel: DMAR-IR: Enabled IRQ remapping in xapic mode
feb 20 12:23:30 archlinux kernel: x2apic: IRQ remapping doesn't support X2APIC mode
feb 20 12:23:30 archlinux kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
feb 20 12:23:30 archlinux kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
feb 20 12:23:30 archlinux kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=2599992)
feb 20 12:23:30 archlinux kernel: pid_max: default: 32768 minimum: 301
feb 20 12:23:30 archlinux kernel: LSM: Security Framework initializing
feb 20 12:23:30 archlinux kernel: Yama: becoming mindful.
feb 20 12:23:30 archlinux kernel: LSM support for eBPF active
feb 20 12:23:30 archlinux kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
feb 20 12:23:30 archlinux kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
feb 20 12:23:30 archlinux kernel: mce: CPU0: Thermal monitoring enabled (TM1)
feb 20 12:23:30 archlinux kernel: process: using mwait in idle threads
feb 20 12:23:30 archlinux kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
feb 20 12:23:30 archlinux kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4

by compiring with what happens when it freezes in the image it seems as if it freezes between these two lines:

feb 20 12:23:30 archlinux kernel: printk: bootconsole [efifb0] disabled
feb 20 12:23:30 archlinux kernel: initcall con_init+0x0/0x25e returned 0 after 0 usecs

Last edited by Xwang (2021-02-20 11:36:06)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#50 2021-02-20 14:29:27

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 460

Re: [SOLVED] Frequent freezes on "Loading initial ramdisk ..."

Did you try systemd-boot as well? I rather think ucodes are a red herring (unless you find other ppl with same problems). Did you check general stability with memtest yet?
Those laptops are a mess indeed with all the custom proprietary embedded controllers, Ring -2 security hypervisors and so on.

Maybe try to tweak grub to load ucodes/ramdisk/kernel "different" (if that's possible). I don't know... maybe something with alternative free space enumeration, different memory allocation, etc.. Not sure what's possible here.

Or look up the BIOS itself for any features to shut down. I've seen (for example) somewhere in your logs something about EC security driver. All this business DRM security spyware crap no one wants could be a potential interfering low-level error candidate.

That the ucodes itself are buggy is rather unlikely i think. And yes, this all is already beyond rational bug hunting.

Last edited by Maniaxx (2021-02-20 14:45:33)


sys2064

Offline

Board footer

Powered by FluxBB