Incorrect temperature readings were observed. The reported temperature spikes to 491°C before dropping back to normal.
It's unclear what is causing these spikes or why the readings fluctuate so significantly. I performed several pulls a few seconds apart, and the issue was reproducible.
First pull: 491 degrees.
sensors -u
mt7915_phy1-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 491.000
temp1_max: 120.000
temp1_crit: 110.000
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:
temp1_input: 56.522
mt7915_phy2-isa-18000000
Adapter: ISA adapter
temp1:
temp1_input: 42.000
temp1_max: 120.000
temp1_crit: 110.000
mt7915_phy0-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 491.000
temp1_max: 120.000
temp1_crit: 110.000
Second pull:
sensors -u
mt7915_phy1-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 0.000
temp1_max: 120.000
temp1_crit: 110.000
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:
temp1_input: 56.824
mt7915_phy2-isa-18000000
Adapter: ISA adapter
temp1:
temp1_input: 42.000
temp1_max: 120.000
temp1_crit: 110.000
mt7915_phy0-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 0.000
temp1_max: 120.000
temp1_crit: 110.000
third pull, back to 491:
sensors -u
mt7915_phy1-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 491.000
temp1_max: 120.000
temp1_crit: 110.000
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:
temp1_input: 56.824
mt7915_phy2-isa-18000000
Adapter: ISA adapter
temp1:
temp1_input: 42.000
temp1_max: 120.000
temp1_crit: 110.000
mt7915_phy0-pci-0100
Adapter: PCI adapter
temp1:
temp1_input: 491.000
temp1_max: 120.000
temp1_crit: 110.000
System info:
ubus call system board-a
{
"kernel": "6.12.87",
"hostname": "mesh-main-node",
"system": "ARMv8 Processor rev 4",
"model": "Acer Connect Vero W6m",
"board_name": "acer,vero-w6m",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "25.12.4",
"firmware_url": "https://downloads.openwrt.org/",
"revision": "r32933-4ccb782af7",
"target": "mediatek/filogic",
"description": "OpenWrt 25.12.4 r32933-4ccb782af7",
"builddate": "1778712129"
}
}
uname -a
Linux hostnamehere 6.12.87 #0 SMP Wed May 13 22:42:09 2026 aarch64 GNU/Linux
Should this be reported as a bug?