Livelock on recent current
Thomas Mueller
mueller6722 at twc.com
Wed Sep 9 10:01:00 UTC 2020
> I am seeing a problem since I moved to current on my laptop this week. It's
> odd as it is linked to the keyboard. As long as the keyboard is active,
> everything is fine, but if the keyboard is not used, after a few minutes,
> it locks up and gets very hot. The system may be busy or idle. The system
> seems completely locked. It does not respond in the network and the
> display, X or just vt is frozen. The only factor is use of the keyboard.
> I'm not sure what information I might collect.
> The system is a ThinkPad L15 with 4GN of DRAMM (more on order) .
> FreeBSD 13.0-CURRENT #2 r365481M: Tue Sep 8 20:16:02 PDT 2020
> root at ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64
> FreeBSD ptavv 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365481M: Tue Sep 8
20:16:02 PDT 2020
> root at ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
amd64
> Intel(R) Core(TM) i5-10210U CPU (Crystal Lake)
> Kevin Oberman, Part time kid herder and retired Network Engineer
Overheating, maybe?
I can see CPU temperature with "envstat" (NetBSD) or
sysctl -a | grep "temperature" (FreeBSD) :
don't know how Linux does it.
Is there any way you could run
sysctl -a | grep "temperature"
at one- or two-minute intervals, perhaps on a different virtual terminal?
I've heard of laptops getting hot, but that was not specifically connected to keyboard inactivity.
Tom
More information about the freebsd-current
mailing list