Issue #121 has been updated by Anastasios Koutian.
The freezes have been quite random for me, sometimes happening within minutes
of booting, sometimes hours, and sometimes days.
It is possible that there are two separate issues that have the same symptom.
You mentioned that using mrc.bin seems
Issue #121 has been updated by Patrick Rudolph.
My X220 is stable for more than 48h, which wasn't possible before as it would
crash within a couple of hours.
Since the issue doesn't appear any more I must assume it's fixed on my device.
There might be other settings causing a similar problem,
Issue #121 has been updated by Anastasios Koutian.
Anastasios Koutian wrote in #note-90:
> Patrick Rudolph wrote in #note-89:
> > I checked the vendor BIOS for (X220, T420 and T420s) and it hard-codes PSI2
> > and PSI3 values to 0 in PowerManagment2.efi.
> > The X230 vendor BIOS does not
Issue #121 has been updated by Patrick Rudolph.
Jun Muta wrote in #note-91:
> Patrick Rudolph wrote in #note-89:
> > I checked the vendor BIOS for (X220, T420 and T420s) and it hard-codes PSI2
> > and PSI3 values to 0 in PowerManagment2.efi.
> > The X230 vendor BIOS does not hard-code those
Issue #121 has been updated by Jun Muta.
Patrick Rudolph wrote in #note-89:
> I checked the vendor BIOS for (X220, T420 and T420s) and it hard-codes PSI2
> and PSI3 values to 0 in PowerManagment2.efi.
> The X230 vendor BIOS does not hard-code those values in PowerManagment2.efi.
> Thus this is
Issue #121 has been updated by Anastasios Koutian.
Patrick Rudolph wrote in #note-89:
> I checked the vendor BIOS for (X220, T420 and T420s) and it hard-codes PSI2
> and PSI3 values to 0 in PowerManagment2.efi.
> The X230 vendor BIOS does not hard-code those values in PowerManagment2.efi.
>
Issue #121 has been updated by Patrick Rudolph.
I checked the vendor BIOS for (X220, T420 and T420s) and it hard-codes PSI2 and
PSI3 values to 0 in PowerManagment2.efi.
The X230 vendor BIOS does not hard-code those values in PowerManagment2.efi.
Thus this is likely a bug in the voltage
Issue #121 has been updated by Patrick Rudolph.
I made good progress with https://review.coreboot.org/c/coreboot/+/81597
It allows to configure the VR12-compatible regulator adjusting the CPU core
voltage.
Especially the PSI state are from interest, since those are using in Package C3
or
Issue #121 has been updated by Patrick Rudolph.
I compared the vendor ACPI code for T520 and T530:
- The T520 is missing _CST entries, thus the C-states are reported in FADT. I
couldn't find a firmware dump that has a FADT.
- The T530 has _CST, but the latencies are higher: For C3 148usec, vs
Issue #121 has been updated by Patrick Rudolph.
Does limiting the max C-state in MSR MSR_PKG_CST_CONFIG_CONTROL also work
around the issue?
What setting is being used on vendor firmware for MSR
MSR_PKG_CST_CONFIG_CONTROL?
Currently the code doesn't check if the processor supports C6/C3 sleep
Issue #121 has been updated by Anastasios Koutian.
File defconfig added
The issue is resolved for me after doing the following:
a) Change motherboards from FRU 04W2049 (dGPU + iGPU) to FRU 04W2045 (iGPU).
b) Update coreboot to 4.21 with EDK II (defconfig is attached).
System has been stable
Issue #121 has been updated by Evgeny Zinoviev.
On my x230 with gentoo, with recent kernel the situation has worsened
significally. If on 5.x kernels it worked somewhat stable (I had crashes maybe
once in a month or so and maybe it wasn't even coreboot related), now I after
upgrade to
Issue #121 has been updated by Anastasios Koutian.
File defconfig added
Andrey A. wrote in #note-70:
> T420 and IVB cpu here again.
> After 9 months with intel_idle.max_cstate=4 (and last kernel and coreboot) I
> get a full stable system without a freeze.
I have a similar setup:
Mainboard:
13 matches
Mail list logo
