sadaszewski

sadaszewski

Member Since 9 years ago

Experience Points
12
follower
Lessons Completed
0
follow
Lessons Completed
2
stars
Best Reply Awards
45
repos

394 contributions in the last year

Pinned
⚡ Focker is a FreeBSD image/jail orchestration tool in the vein of Docker.
⚡ C++ port of mapbox's JS concaveman, with a Python wrapper
⚡ Qt-based Flow/Vector Field Editor
⚡ Astrophotography Utilities
⚡ My Blender Add-ons
⚡ Minimalistic Python version of the Linux VERBS API for Infiniband
Activity
Nov
26
1 week ago
Nov
25
1 week ago
push

sadaszewski push sadaszewski/freebsd-src

sadaszewski
sadaszewski

Tpm2PolicyPCR requires debugging, error in parameter 2 - pcrs

commit sha: 13f14a58dbf3ae1652fe38fc61033a2981724625

push time in 1 week ago
Nov
24
1 week ago
Nov
18
2 weeks ago
Activity icon
created branch

sadaszewski in sadaszewski/freebsd-src create branch tpm-support-in-stand

createdAt 2 weeks ago
Nov
17
2 weeks ago
pull request

sadaszewski pull request freebsd/freebsd-src

sadaszewski
sadaszewski

Coretemp prochot is not critical

According to the Intel manual the Thermal Status (0) and Thermal Status Log (1) bits report only a high temperature on the CPU, not a critical temperature as suggested in the coretemp driver. I would remove the warning or check for the actual Critical Temperature Log (5) bit. Looking at the Log bit might be better than Critical Temperature Status (4), as AFAIK the critical temperature waives guarantees of correct function, therefore the CPU could have for example written some wrong values into memory at that point and the OS should be stopped ASAP as the state is no longer reliable.

pull request

sadaszewski pull request sadaszewski/freebsd-src

sadaszewski
sadaszewski

Update coretemp.c

According to the Intel manual the Thermal Status (0) and Thermal Status Log (1) bits report only a high temperature on the CPU, not a critical temperature as suggested in the coretemp driver. I would remove the warning or check for the actual Critical Temperature Log (5) bit. Looking at the Log bit might be better than Critical Temperature Status (4), as AFAIK the critical temperature waives guarantees of correct function, therefore the CPU could have for example written some wrong values into memory at that point and the OS should be stopped ASAP as the state is no longer reliable.

pull request

sadaszewski pull request sadaszewski/freebsd-src

sadaszewski
sadaszewski

Update coretemp.c

According to the Intel manual the Thermal Status (0) and Thermal Status Log (1) bits report only a high temperature on the CPU, not a critical temperature as suggested in the coretemp driver. I would remove the warning or check for the actual Critical Temperature Log (5) bit. Looking at the Log bit might be better than Critical Temperature Status (4), as AFAIK the critical temperature waives guarantees of correct function, therefore the CPU could have for example written some wrong values into memory at that point and the OS should be stopped ASAP as the state is no longer reliable.

Activity icon
created branch

sadaszewski in sadaszewski/freebsd-src create branch coretemp-prochot-is-not-critical

createdAt 2 weeks ago
Activity icon
fork

sadaszewski forked freebsd/freebsd-src

⚡ FreeBSD src tree (read-only mirror)
sadaszewski Updated
fork time in 2 weeks ago
Nov
16
3 weeks ago
Nov
15
3 weeks ago
push

sadaszewski push sadaszewski/focker

sadaszewski
sadaszewski

Add test20_jls_not_running_raise.

commit sha: 921791bfbde42db269d6706729646294e47439d5

push time in 3 weeks ago
Activity icon
issue

sadaszewski issue sadaszewski/focker

sadaszewski
sadaszewski

listing is slow due to multiple process launches

need to optimize by providing cache to the datasets obtained from listings

push

sadaszewski push sadaszewski/focker

sadaszewski
sadaszewski

JailConfCache leave as it was.

commit sha: aceba012c007949742031bb8bb71a3b9c4e8c2a7

push time in 3 weeks ago