Re: Bullseye (mostly) not booting on Proliant DL380 G7
On 6/29/21 12:08 PM, Claudio Kuenzler wrote:
> Sorry for auto-responding all the time ;-)
> I was just able to catch a "freeze" followed by a successful boot
> afterwards.
>
> The successful boot continues with these lines:
>
> [ 62.922169] systemd[1]: Finished Create System Users.
> [ 62.923633] systemd[1]: Starting Create Static Device Nodes in /dev...
> [ 62.941753] systemd[1]: Finished Create Static Device Nodes in /dev.
> [ 62.944691] systemd[1]: Starting Rule-based Manager for Device Events
> and Files...
> [ 62.953082] systemd[1]: modprobe@drm.service: Succeeded.
> [ 62.953539] systemd[1]: Finished Load Kernel Module drm.
> [ 62.983630] systemd[1]: Started Rule-based Manager for Device Events
> and Files.
> [ 62.991307] systemd[1]: Finished Set the console keyboard layout.
> [ 63.015898] input: Power Button as
> /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
> [ 63.016490] systemd[1]: Finished Coldplug All udev Devices.
> [ 63.018250] systemd[1]: Starting Helper to synchronize boot up for
> ifupdown...
> [ 63.020119] power_meter ACPI000D:00: Found ACPI power meter.
> [ 63.020214] power_meter ACPI000D:00: Ignoring unsafe software power cap!
> [ 63.020280] power_meter ACPI000D:00: hwmon_device_register() is
> deprecated. Please convert the driver to use
> hwmon_device_register_with_info().
> [ 63.029971] systemd[1]: Finished Monitoring of LVM2 mirrors,
> snapshots etc. using dmeventd or progress polling.
> [ 63.030392] systemd[1]: Reached target Local File Systems (Pre).
> [ 63.031784] IPMI message handler: version 39.2
> [ 63.035060] ipmi device interface
> [ 63.036149] ACPI: Power Button [PWRF]
> [ 63.038539] EDAC MC1: Giving out device to module i7core_edac.c
> controller i7 core #1: DEV 0000:3e:03.0 (INTERRUPT)
> [ 63.038670] EDAC PCI0: Giving out device to module i7core_edac
> controller EDAC PCI controller: DEV 0000:3e:03.0 (POLLED)
> [ 63.039204] EDAC MC0: Giving out device to module i7core_edac.c
> controller i7 core #0: DEV 0000:3f:03.0 (INTERRUPT)
> [ 63.039315] EDAC PCI1: Giving out device to module i7core_edac
> controller EDAC PCI controller: DEV 0000:3f:03.0 (POLLED)
> [ 63.039405] EDAC i7core: Driver loaded, 2 memory controller(s) found.
> [ 63.044910] ipmi_si: IPMI System Interface driver
> [ 63.044996] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS
> [ 63.045059] ipmi_platform: ipmi_si: SMBIOS: io 0xca2 regsize 1
> spacing 1 irq 0
> [ 63.045134] ipmi_si: Adding SMBIOS-specified kcs state machine
> [ 63.045263] ipmi_si IPI0001:00: ipmi_platform: probing via ACPI
> [ 63.045393] ipmi_si IPI0001:00: ipmi_platform: [io 0x0ca2-0x0ca3]
> regsize 1 spacing 1 irq 0
> [ 63.045652] iTCO_vendor_support: vendor-support=0
> [ 63.046504] hpwdt 0000:02:00.0: HPE Watchdog Timer Driver: NMI
> decoding initialized
> This line catches my attention:
>
> [ 62.953082] systemd[1]: modprobe@drm.service: Succeeded.
>
> This is missing (doesn't show) when the freeze happens.
>
Hi Claudio,
I noticed that kernel logs you posted are between 62nd - 64th second
after kernel loading. Why is the boot process so slow?
If you think that video driver can be an issue then you can try to
configure the system not to use framebuffer (if the system
doesn't use GUI).
Kind regards
Georgi
Reply to: