Claudio Kuenzler writes:
On Wed, Jun 30, 2021 at 9:51 AM Paul Wise wrote:
Claudio Kuenzler wrote:
> I currently suspect a Kernel bug in 5.10.
Thanks to everyone for hints and suggestions!
At the end it turned out to be an issue with the hpwdt module. After
blacklisting this module,
On Wed, Jun 30, 2021 at 9:51 AM Paul Wise wrote:
> Claudio Kuenzler wrote:
>
> > I currently suspect a Kernel bug in 5.10.
>
Thanks to everyone for hints and suggestions!
At the end it turned out to be an issue with the hpwdt module. After
blacklisting this module, no boot or stability issues wi
Claudio Kuenzler wrote:
> I currently suspect a Kernel bug in 5.10.
You could try booting a bullseye install with the buster kernel,
if that works then it sounds like you need a kernel git bisect.
https://wiki.debian.org/DebianKernel/GitBisect
--
bye,
pabs
https://wiki.debian.org/PaulWise
s
I tend to suspect it's unrelated, but if you add "nomodeset nofb" to
> your boot command line it will turn off the graphics drivers.
>
Yes, I guess it is indeed unrelated. With buster I can see the same
messages during boot:
- *ERROR* Failed to load firmware! on drm
- pcc_cpufreq_init: Too many CP
On Tue, Jun 29, 2021 at 11:08:09AM +0200, Claudio Kuenzler wrote:
This line catches my attention:
[ 62.953082] systemd[1]: modprobe@drm.service: Succeeded.
This is missing (doesn't show) when the freeze happens.
I tend to suspect it's unrelated, but if you add "nomodeset nofb" to
your boot
>
> Trace dump suggests that crash occurs while executing cpuidle module.
> Try to boot with "intel_pstate=force" kernel parameter [1] to force
> different CPU driver (if CPU supports it) and\or "cpuidle.off=1" to disable
> cpuidle subsystem.
>
>
Thank you Alexander and Georgi (thanks for the link!
On 6/29/21 1:29 PM, Claudio Kuenzler wrote:
> Hi Georgi
>
> I noticed that kernel logs you posted are between 62nd - 64th second
> after kernel loading. Why is the boot process so slow?
>
>
> Due to a disabled SATA device in BIOS, the kernel tries to do an ERST
> and SRST and does this u
On 29.06.2021 15:29, Claudio Kuenzler wrote:
Hi Georgi
I noticed that kernel logs you posted are between 62nd - 64th second
after kernel loading. Why is the boot process so slow?
Due to a disabled SATA device in BIOS, the kernel tries to do an ERST
and SRST and does this until 60s aft
Hi Georgi
I noticed that kernel logs you posted are between 62nd - 64th second
> after kernel loading. Why is the boot process so slow?
>
Due to a disabled SATA device in BIOS, the kernel tries to do an ERST and
SRST and does this until 60s after boot.
That's OK, it's been the same on Buster, too
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.923
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.
Meanwhile I was able to identify more by removing "quiet" from the grub
loader.
The pcc_cpufreq_init does not seem to hurt the booting - these are just
warnings popping up.
The following messages appear on the console before the server freezes:
[ OK ] Finished Load Kernel Module fuse.
[ 62.887855
Hello!
Currently testing the new Bullseye release (using
firmware-bullseye-DI-rc2-amd64-netinst.iso) and see a strange phenomenon on
a HP Proliant DL380 G7 server.
During boot, the following messages show up in the console:
[63.063844] pcc_cpufreq_init: Too many CPUs, dynamic performance scaling
13 matches
Mail list logo
