Open SebastianCzapla opened 4 weeks ago
Can you also upload the outputs of sensors-detect
and full dmesg
here?
[sudo] password for ubuntu:
# sensors-detect version 3.6.0
# System: Notebook V5xTNC_TND_TNE [V540TNx] (laptop)
# Kernel: 6.11.0-8-generic x86_64
# Processor: Intel(R) Core(TM) Ultra 7 155H (6/170/4)
Running in automatic mode, default answers to all questions
are assumed.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... Yes
Found unknown chip with ID 0x5570
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Found unknown SMBus adapter 8086:7e22 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-3)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: SMBus I801 adapter at efa0 (i2c-4)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x48
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP435'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
Client found at address 0x50
Handled by driver `spd5118' (already loaded), chip type `spd5118'
(note: this is probably NOT a sensor chip!)
Next adapter: i915 gmbus dpa (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus dpb (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus dpd (i2c-8)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus dpe (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus tc1 (i2c-10)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus tc2 (i2c-11)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus tc3 (i2c-12)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus tc4 (i2c-13)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AUX A/DDI A/PHY A (i2c-14)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AUX USBC1/DDI TC1/PHY TC1 (i2c-15)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AUX USBC2/DDI TC2/PHY TC2 (i2c-16)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AUX USBC3/DDI TC3/PHY TC3 (i2c-17)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AUX USBC4/DDI TC4/PHY TC4 (i2c-18)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-19)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 3 at 1:00.0 (i2c-20)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-21)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-22)
Do you want to scan it? (yes/NO/selectively):
Now follows a summary of the probes I have just done.
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)
Identical behavior present within v0.9.1-rc8, on newest, Ubuntu 24.10, on kernel 6.11
Component
Dasharo firmware
Device
NovaCustom V54 14th Gen
Dasharo version
v0.9.1-rc7
Dasharo Tools Suite version
No response
Test case ID
FAN001.001
Brief summary
dmesg spammed with timeout messages
How reproducible
100%
How to reproduce
Run FAN001.001, during sensors-detect phase, dmesg is flooded with messages, on kernel 6.11
Expected behavior
sensors-detect works without causing message flood
Actual behavior
dmesg does not show unneeded prints
Screenshots
Additional context
Might be missing driver from 6.11 kernel, and in the end, might be not an issue related to dasharo at all.
Solutions you've tried
No response