Comment 3 for bug 1882455

Revision history for this message
Ivan Hu (ivan.hu) wrote :

for the high failures from comment#1
 dmicheck: Out of range value 0xfb0a (range allowed 0x0000..0x8000) while accessing entry 'Temperature Probe (Type 28)' @ 0x000e0b3c, field 'Minimum Value', offset 0x08
 dmicheck: Out of range value 0xfb0a (range allowed 0x0000..0x8000) while accessing entry 'Temperature Probe (Type 28)' @ 0x000e0b5d, field 'Minimum Value', offset 0x08
 dmicheck: Out of range value 0xfb0a (range allowed 0x0000..0x8000) while accessing entry 'Temperature Probe (Type 28)' @ 0x000e0b81, field 'Minimum Value', offset 0x08
 dmicheck: Out of range value 0xfb0a (range allowed 0x0000..0x8000) while accessing entry 'Temperature Probe (Type 28)' @ 0x000e0ba6, field 'Minimum Value', offset 0x08
 method: \_SB_.PCI0.RP05._S0W returned value 4 but range allowed is 0..3 .
 method: \_SB_.PCI0.RP09._S0W returned value 4 but range allowed is 0..3 .
 method: \_SB_.PCI0.I2C0.TPL0._S0W returned value 4 but range allowed is 0..3 .
 method: \_SB_.PCI0.I2C2.TPL1._S0W returned value 4 but range allowed is 0..3 .
 method: \_SB_.PCI0.I2C3.TPL1._S0W returned value 4 but range allowed is 0..3 .

It seems all firmware issues on smbios and Acpi tables,
all are out of range from specification defined.

Maybe you can attach the acpidump log for further investigation,
by #sudo acpidump > acpidump.log