Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VP6670 - overheating #777

Closed
pkubaj opened this issue Apr 5, 2024 · 5 comments
Closed

VP6670 - overheating #777

pkubaj opened this issue Apr 5, 2024 · 5 comments
Labels

Comments

@pkubaj
Copy link

pkubaj commented Apr 5, 2024

Component

Dasharo firmware

Device

Protectli VP6670

Dasharo version

0.9.0rc2

Dasharo Tools Suite version

No response

Brief summary

overheating VP6670

How reproducible

No response

How to reproduce

unknown

Expected behavior

temperature should be below 82C.

Actual behavior

Current temperature: 89.0°C

Screenshots

No response

Additional context

No response

Solutions you've tried

No response

@pkubaj pkubaj added the bug Something isn't working label Apr 5, 2024
@mkopec
Copy link
Member

mkopec commented Apr 8, 2024

Doesn't look like TCC offset is defined anywhere in the devicetree: https://github.com/Dasharo/coreboot/blob/dasharo/src/mainboard/protectli/vault_adl_p/devicetree.cb

so the CPU is free to boost up to 100 degC (Tjunction)

@miczyg1
Copy link
Contributor

miczyg1 commented Apr 8, 2024

Dasharo/coreboot#478

@pkubaj
Copy link
Author

pkubaj commented Apr 25, 2024

'87.0 < 82' should be true.

@pkubaj
Copy link
Author

pkubaj commented Apr 25, 2024

        Version: Dasharo (coreboot+UEFI) v0.9.0-rc3
        Release Date: 04/16/2024

@macpijan
Copy link
Contributor

We have concluded that the test case should be more sophisticated, allowing for a very short temperature spikes, which is not a real problem. The problem is if this higher temperature persists for a longer period.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants