Re: Livelock on recent current

On 2020-09-12 01:24, Kevin Oberman wrote:

> I'm happy to see that I am not crazy!
> 
> This is mostly anecdotal. The freezes have occurred regularly, without
> question, but the details are not statistically verified. This is based 
> on
> my perceptions. The only things I am really sure of is that the system 
> is
> unusable on head and runs well on 12.1-Release. This system has a 
> rather
> new Intel GPU, the Comet Lake, and is only supported on head with
> drm-devel-kmod, so moving back to 12.1 is not an option. I am curious 
> what
> processor is on the T490. I am using the default keyboard layout.
> On terminal sessions (vt), when the keyboard is idle. I have had the 
> system
> run for a couple of hours or longer with no problems. To get bigger 
> ports
> to build, I usually switch to another vty and keep that one fairly 
> busy. It
> will freeze when no vty is active, but as long as any is active every
> minute or less. I have had freezes in under a minute, but rarely.
> 
> Moving on to other possibly related (or not) issues:
> When running on X (MATE), it may freeze whether the keyboard is active 
> or
> not. OTOH, it seems to freeze less often. I've had X lock up mid-word 
> but
> also run for 15 or more minutes. It eventually does freeze, but I don't
> think I've ever gone more than 10 minutes on an idle keyboard without a
> freeze without X running.
> 
> Switching to a vty and keeping it fairly active still seems to keep the
> system alive while X is being used. X is performing very poorly. If the
> processors are busy, say by building a port, screen updates are very 
> slow,
> often pausing for several seconds. Expose events seem to often redraw 
> all
> windows which is very annoying. Several times I thought the system was
> frozen only to suddenly have the screen update and everything be 
> normal,
> again.

I also have this issue on a Carbon X1 7th Gen (type 20QDCTO1WW) on 
recent -CURRENT snapshots.
I'll try 12-STABLE for now since the system is totally unreliable on 
-CURRENT.
I used the default English kb layout but that didn't resolve anything.

The longest I've been able to just let the live cd run (running top) 
when on AC before my system completely freezes is roughly about 7 hours.
Then again, I've also seen even the live cd from the memstick.img freeze 
after a couple of seconds after login (did a tail -f on 
/var/log/messages and it almost immediately froze right after that).
When it freezes the fan ramps up at a fairly high rpm.
Unless I forcibly power down the high rpm just continues.
Power mode for AC is set to max performance.
Adaptive thermal management scheme for AC also set to max performance.

I've tried booting both using UEFI and also legacy BIOS but in both 
cases I've experienced the same behaviour.

Any specific settings in BIOS to perhaps avoid?

I bought this ThinkPad based on the info listed on 
https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon

I just made the following BIOS changes:

config -> power -> adaptive thermal management > scheme for AC : 
balanced (was : maximize performance)
config -> power -> sleep state : Linux (was: windows 10)
config -> intel AMT > intel AMT control : disabled (was : enabled)
security -> security chip > security chip : Off (was : On) <-- security 
chip type : TPM 2.0

Hasn't improved anything i'm afraid.

User Duffyx on the forums mentioned
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659

So consider this an official 'me too'