Re: Errata: OpenBSD 7.5: high temperature spotted different times
Correction: CPU: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz, 06-45-01, patch 0026 (year 2014) Dan wrote: > Hello, > > In my OpenBSD 7.5 stable temperature incrises timtotime remaining on > 64-65°C; an old quad cores I5 cpu. > > Thanks, > > -dan
OpenBSD 7.5: high temperature spotted different times
Hello, In my OpenBSD 7.5 stable temperature incrises timtotime remaining on 64-65°C; an old quad cores I5 cpu. Thanks, -dan
High cpu temperature moment (unexpect bugget :-)
Hello, Guessing#1 it will be hard to grasp anything useful from my report due to the lack of info I collected at the moment of this "bugget" happening. Guessing#2 it could be a problem of Badwolf that it was already showing some symptoms in its last version under 7.4 stable but I neither exclude phpfpm within hw.smt=1. I just experienced a continuous period of high cpu temperature on 7.4 stable, with the browser becoming very unresponsive, while I was working within the following environment: grep hw.smt /etc/sysctl.conf: hw.smt=1 hw.ncpufound=4 hw.ncpuonline=2 hw.sensors.cpu0.temp0=62 degC (;;53.00 degC normal temperature) Excerpt from dmesg: cpu1: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz, 1696.10 MHz, 06-45-01, patch 0026 Running software: xfce-4.18p6 parole-4.18.0p0 (playing great music!) php-8.1.25 (using phpfpm!) memcached-1.6.15p0 (two instances!) nginx-1.24.0p0 badwolf-1.2.2p2 unbound (running!) System was syspatched till 009 I promptly reverted to hw.smt=1 and patched till 012 Thanks, good day to everyone! > N0\/\/@r€Z > -- > /\/\@rk€T
Re: lm(4) temperature
>> OK, with expectations adjusted, >> does anyone know what the three numbers >> are _supposed_ to be? >> I guess you are talking about those numbers: > dev/ic/lm78var.h talks about Temperature 1, 2, 3; The 1,2,3 are the corresponding ports from the chip itself, there are 3 ports for temperature reading, numbered from 1 to 3, so the programmer kept the numbering and duplicated it in the actual C code variables names. > > > but man lm(4) only says > > > > > > Temp uK Motherboard Temperature The manual says this: "The original LM78 hardware monitor ..." That is _NOT_ your case, since your sensor is reported as: > > > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 > > > lm1 at wbsio0 port 0x290/8: W83627HF LM78=/=W83627HF. It has been included in the lm driver, maybe to avoid another extra work and code duplication for a new driver, something like CD_ROMs put on scsi drivers or something like this. > Yes. Temperature readings from multiple places on the motherboard. Not quite in this case, only the first is a temperature reading, the rest are bogus since the pins are not connected (i.e. floating, reading whatever EMI is throwing to them). Again, what you read on your specific hardware is the CPU die temperature as the first temperature reported, the remaining 2 readings on temperature are bogus, they have no real meaning since the pins have no sensors connected on them. At least this is if you read the ALIX schematics.
Re: lm(4) temperature
Am Sat, Nov 27, 2021 at 03:35:05PM +0100 schrieb Jan Stary: > > > This is current/i386 on an ALIX.1E (dmesg below). > > > I am trying to monitor the CPU temperature with > > > > > > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 > > > lm1 at wbsio0 port 0x290/8: W83627HF > > > > > > $ sysctl hw.sensors.lm1 > > > hw.sensors.lm1.temp0=69.00 degC > > > hw.sensors.lm1.temp1=57.00 degC > > > hw.sensors.lm1.temp2=49.00 degC > > > hw.sensors.lm1.volt0=1.26 VDC (VCore A) > > > hw.sensors.lm1.volt1=2.64 VDC (VCore B) > > > hw.sensors.lm1.volt2=3.42 VDC (+3.3V) > > > hw.sensors.lm1.volt3=5.11 VDC (+5V) > > > hw.sensors.lm1.volt4=0.00 VDC (+12V) > > > hw.sensors.lm1.volt5=-14.91 VDC (-12V) > > > hw.sensors.lm1.volt6=-7.71 VDC (-5V) > > > hw.sensors.lm1.volt7=5.07 VDC (5VSB) > > > hw.sensors.lm1.volt8=0.00 VDC (VBAT) > > > > > > There are three temperatures reported, > > > and dev/ic/lm78var.h talks about Temperature 1, 2, 3; > > > but man lm(4) only says > > > > > > Temp uK Motherboard Temperature > > > > > > Does anyone know what exactly they are? > > > > > > There is a chip in the machine. > > It has pins. > > Those pins are monitored by the driver, as specific registers. > > > > The pins wired to who the hell knows where by each board manufacturer. > > > > Sometimes the chips need special registers and capacitors > > > > Quite often, the board engineer sent to add this part to the board > > choose the wrong registers and capacitors, and sometimes they compensate > > for these errors with private tables in the BIOS or various monitoring > > programs which move around machine to machine. > > > > > > We monitor registers. We assume the vendor did the right thing. > > > > No that I've described what a shitshow it is, I hope you can adjust your > > expectations. > > OK, with expectations adjusted, > does anyone know what the three numbers > are _supposed_ to be? > Yes. Temperature readings from multiple places on the motherboard.
Re: lm(4) temperature
> > This is current/i386 on an ALIX.1E (dmesg below). > > I am trying to monitor the CPU temperature with > > > > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 > > lm1 at wbsio0 port 0x290/8: W83627HF > > > > $ sysctl hw.sensors.lm1 > > hw.sensors.lm1.temp0=69.00 degC > > hw.sensors.lm1.temp1=57.00 degC > > hw.sensors.lm1.temp2=49.00 degC > > hw.sensors.lm1.volt0=1.26 VDC (VCore A) > > hw.sensors.lm1.volt1=2.64 VDC (VCore B) > > hw.sensors.lm1.volt2=3.42 VDC (+3.3V) > > hw.sensors.lm1.volt3=5.11 VDC (+5V) > > hw.sensors.lm1.volt4=0.00 VDC (+12V) > > hw.sensors.lm1.volt5=-14.91 VDC (-12V) > > hw.sensors.lm1.volt6=-7.71 VDC (-5V) > > hw.sensors.lm1.volt7=5.07 VDC (5VSB) > > hw.sensors.lm1.volt8=0.00 VDC (VBAT) > > > > There are three temperatures reported, > > and dev/ic/lm78var.h talks about Temperature 1, 2, 3; > > but man lm(4) only says > > > > Temp uK Motherboard Temperature > > > > Does anyone know what exactly they are? > > > There is a chip in the machine. > It has pins. > Those pins are monitored by the driver, as specific registers. > > The pins wired to who the hell knows where by each board manufacturer. > > Sometimes the chips need special registers and capacitors > > Quite often, the board engineer sent to add this part to the board > choose the wrong registers and capacitors, and sometimes they compensate > for these errors with private tables in the BIOS or various monitoring > programs which move around machine to machine. > > > We monitor registers. We assume the vendor did the right thing. > > No that I've described what a shitshow it is, I hope you can adjust your > expectations. OK, with expectations adjusted, does anyone know what the three numbers are _supposed_ to be?
Re: lm(4) temperature
> it looks like it goes to the LX memory controller. So it must be the temperature of the board itself, more or less. Looking at the LX Geode processor specs, the memory controller is integrated in the CPU. So looking again at the pins names (AL17, AK17), it looks like there is a diode inside the CPU die. So you have the CPU die temperature.
Re: lm(4) temperature
ALIX.1E has schematics available. W83627HF has specifications available too. >From the W83627HF one can see there are 3 ports for temperature monitoring: PIN# | PURPOSE | FUNCTION 102 | VTIN3 | Temperature sensor 3 input (used for CPU2 temperature) 103 | VTIN2 | Temperature sensor 2 input (used for CPU1 temperature) 104 | VTIN1 | Temperature sensor 1 input (used for system temperature) >From the ALIX.1E schematics, page 10, there is only PIN# 104 connected, from those enumerated, the rest are not. Unless they are using another way to measure temperatures (which i didn't checked on schematics), there is only one temperature monitored. As for the place the input is connected, it looks like it goes to the LX memory controller. So it must be the temperature of the board itself, more or less. Same goes for voltages. I think you can address this issue to pcengines support, they are generally very responsive.
Re: lm(4) temperature
On 11/20/21 2:42 PM, Theo de Raadt wrote: Jan Stary wrote: This is current/i386 on an ALIX.1E (dmesg below). I am trying to monitor the CPU temperature with wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 lm1 at wbsio0 port 0x290/8: W83627HF $ sysctl hw.sensors.lm1 hw.sensors.lm1.temp0=69.00 degC hw.sensors.lm1.temp1=57.00 degC hw.sensors.lm1.temp2=49.00 degC hw.sensors.lm1.volt0=1.26 VDC (VCore A) hw.sensors.lm1.volt1=2.64 VDC (VCore B) hw.sensors.lm1.volt2=3.42 VDC (+3.3V) hw.sensors.lm1.volt3=5.11 VDC (+5V) hw.sensors.lm1.volt4=0.00 VDC (+12V) hw.sensors.lm1.volt5=-14.91 VDC (-12V) hw.sensors.lm1.volt6=-7.71 VDC (-5V) hw.sensors.lm1.volt7=5.07 VDC (5VSB) hw.sensors.lm1.volt8=0.00 VDC (VBAT) There are three temperatures reported, and dev/ic/lm78var.h talks about Temperature 1, 2, 3; but man lm(4) only says Temp uK Motherboard Temperature Does anyone know what exactly they are? There is a chip in the machine. It has pins. Those pins are monitored by the driver, as specific registers. The pins wired to who the hell knows where by each board manufacturer. Sometimes the chips need special registers and capacitors Quite often, the board engineer sent to add this part to the board choose the wrong registers and capacitors, and sometimes they compensate for these errors with private tables in the BIOS or various monitoring programs which move around machine to machine. We monitor registers. We assume the vendor did the right thing. No that I've described what a shitshow it is, I hope you can adjust your expectations. Otherwise, maybe it is time to give up and delete these sensor drivers.. Boot the machine to startup BIOS. Search for a hardware monitor screen. Write down what it says - values and descriptions. Any correlation between that and what sysctl.hw.sensors says is purely in the mind of the viewer.
Re: lm(4) temperature
Jan Stary wrote: > This is current/i386 on an ALIX.1E (dmesg below). > I am trying to monitor the CPU temperature with > > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 > lm1 at wbsio0 port 0x290/8: W83627HF > > $ sysctl hw.sensors.lm1 > hw.sensors.lm1.temp0=69.00 degC > hw.sensors.lm1.temp1=57.00 degC > hw.sensors.lm1.temp2=49.00 degC > hw.sensors.lm1.volt0=1.26 VDC (VCore A) > hw.sensors.lm1.volt1=2.64 VDC (VCore B) > hw.sensors.lm1.volt2=3.42 VDC (+3.3V) > hw.sensors.lm1.volt3=5.11 VDC (+5V) > hw.sensors.lm1.volt4=0.00 VDC (+12V) > hw.sensors.lm1.volt5=-14.91 VDC (-12V) > hw.sensors.lm1.volt6=-7.71 VDC (-5V) > hw.sensors.lm1.volt7=5.07 VDC (5VSB) > hw.sensors.lm1.volt8=0.00 VDC (VBAT) > > There are three temperatures reported, > and dev/ic/lm78var.h talks about Temperature 1, 2, 3; > but man lm(4) only says > > Temp uK Motherboard Temperature > > Does anyone know what exactly they are? There is a chip in the machine. It has pins. Those pins are monitored by the driver, as specific registers. The pins wired to who the hell knows where by each board manufacturer. Sometimes the chips need special registers and capacitors Quite often, the board engineer sent to add this part to the board choose the wrong registers and capacitors, and sometimes they compensate for these errors with private tables in the BIOS or various monitoring programs which move around machine to machine. We monitor registers. We assume the vendor did the right thing. No that I've described what a shitshow it is, I hope you can adjust your expectations. Otherwise, maybe it is time to give up and delete these sensor drivers..
lm(4) temperature
This is current/i386 on an ALIX.1E (dmesg below).
I am trying to monitor the CPU temperature with
wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41
lm1 at wbsio0 port 0x290/8: W83627HF
$ sysctl hw.sensors.lm1
hw.sensors.lm1.temp0=69.00 degC
hw.sensors.lm1.temp1=57.00 degC
hw.sensors.lm1.temp2=49.00 degC
hw.sensors.lm1.volt0=1.26 VDC (VCore A)
hw.sensors.lm1.volt1=2.64 VDC (VCore B)
hw.sensors.lm1.volt2=3.42 VDC (+3.3V)
hw.sensors.lm1.volt3=5.11 VDC (+5V)
hw.sensors.lm1.volt4=0.00 VDC (+12V)
hw.sensors.lm1.volt5=-14.91 VDC (-12V)
hw.sensors.lm1.volt6=-7.71 VDC (-5V)
hw.sensors.lm1.volt7=5.07 VDC (5VSB)
hw.sensors.lm1.volt8=0.00 VDC (VBAT)
There are three temperatures reported,
and dev/ic/lm78var.h talks about Temperature 1, 2, 3;
but man lm(4) only says
Temp uK Motherboard Temperature
Does anyone know what exactly they are?
Jan
OpenBSD 7.0-current (GENERIC) #276: Wed Nov 10 11:36:02 MST 2021
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 259207168 (247MB)
avail mem = 238137344 (227MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/19/10, BIOS32 rev. 0 @ 0xfa950
apm0 at bios0: Power Management spec V1.2 (slowidle)
pcibios0 at bios0: rev 2.1 @ 0xf/0xdfb4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/128 (6 entries)
pcibios0: PCI Exclusive IRQs: 5 10 11
pcibios0: no compatible PCI ICU found: ICU vendor 0x1022 product 0x2090
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0xa800 0xef000/0x1000!
cpu0 at mainbus0: (uniprocessor)
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 499
MHz, 05-0a-02
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
mtrr: K6-family MTRR support (2 registers)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
vga1 at pci0 dev 1 function 1 "AMD Geode LX Video" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 13 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:0d:b9:0e:9e:f4
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
auglx0 at pci0 dev 15 function 3 "AMD CS5536 Audio" rev 0x01: irq 11, CS5536
AC97
ac97: codec id 0x414c4770 (Avance Logic ALC203 rev 0)
ac97: codec features headphone, 20 bit DAC, 18 bit ADC, No 3D Stereo
audio0 at auglx0
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 5, version 1.0,
legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 5
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00
addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41
lm1 at wbsio0 port 0x290/8: W83627HF
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00
addr 1
dt: 445 probes
umass0 at uhub0 port 4 configuration 1 interface 0 "JMicron USB to ATA/ATAPI
bridge" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0:
serial.152d2329801130168383
sd0: 228936MB, 512 bytes/sector, 468862128 sectors
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (cfeae50a002d1e1d.a) swap on wd0b dump on wd0b
Re: Thinkpad T400 temperature sensors
On Fri, Nov 19, 2021 at 01:58:20PM +0100, Jan Stary wrote: > This is current/amd64 on a Thinkpad T400 > (full dmesg and sysctl hw below). > > It provides various sensors reporting temperatures, > but I don't really know what temperatures these are. > > $ sysctl hw | grep temp > > hw.sensors.cpu0.temp0=39.00 degC > hw.sensors.acpithinkpad0.temp0=48.00 degC > hw.sensors.acpithinkpad0.temp1=41.00 degC > hw.sensors.acpithinkpad0.temp2=34.00 degC > hw.sensors.acpithinkpad0.temp4=25.00 degC > hw.sensors.acpithinkpad0.temp6=25.00 degC > hw.sensors.acpitz0.temp0=48.00 degC (zone temperature) > hw.sensors.acpitz1.temp0=44.00 degC (zone temperature) > hw.sensors.aps0.temp0=255.00 degC > hw.sensors.aps0.temp1=255.00 degC > ... Hi Jan, There is some (emperically derived) info. about the hardware here: https://www.thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_T400 And: https://www.sthu.org/misc/t400.html E.g. Index in "thermal" Location 1CPU neighbourhood (also via ACPI THM0) 2Ultrabay 3Express card 4ATI graphics module 5Main battery (always around 50°C) 6n/a (probably ultrabay battery) 7Main Battery (fits about the value reported by smapi) 8n/a (probably ultrabay battery) 9Hard disc 10 Intel graphics module 11 Heatsink? Those numbers are the indicies into the Linux thinkpad_acpi kernel module, made available via '/proc/acpi/ibm/thermal' Maybe that helps. Cheers, Robb.
Thinkpad T400 temperature sensors
This is current/amd64 on a Thinkpad T400 (full dmesg and sysctl hw below). It provides various sensors reporting temperatures, but I don't really know what temperatures these are. $ sysctl hw | grep temp hw.sensors.cpu0.temp0=39.00 degC hw.sensors.acpithinkpad0.temp0=48.00 degC hw.sensors.acpithinkpad0.temp1=41.00 degC hw.sensors.acpithinkpad0.temp2=34.00 degC hw.sensors.acpithinkpad0.temp4=25.00 degC hw.sensors.acpithinkpad0.temp6=25.00 degC hw.sensors.acpitz0.temp0=48.00 degC (zone temperature) hw.sensors.acpitz1.temp0=44.00 degC (zone temperature) hw.sensors.aps0.temp0=255.00 degC hw.sensors.aps0.temp1=255.00 degC By cpu(4), the hw.sensors.cpu0.temp0 is the CPU temperatue (duh). Is there some documentation of what exactly the others are? acpitz(4) and acpithinkpad(4) don't really say. (The aps(4) temperatures are "unused".) Jan OpenBSD 7.0-current (GENERIC.MP) #104: Thu Nov 18 09:10:05 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8461684736 (8069MB) avail mem = 8189267968 (7809MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012 bios0: LENOVO 64741EG acpi0 at bios0: ACPI 3.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.33 MHz, 06-17-06 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 MHz, 06-17-06 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 tpm0 at acpi0 TPM_ 1.2 (TIS) addr 0xfed4/0x5000, device 0x10208086 rev 0x6 acpibat0 at acpi0: BAT0 model "92P1137" serial57 type LION oem "SANYO" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0: version 1.0 "PNP0C14" at acpi0 not configured acpicpu0 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: apic 1 int 16, GM45, gen 4 "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:9b:0a:23 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03:
Re: laptop cpu high temperature while idle
"Due to the way in which thermal information is reported on Intel processors, the temperature may be off by exactly +/-15 degrees C." man 4 cpu http://man.openbsd.org/cpu#BUGS This must be my case. Thanks for participating to Stefan Hagen and John aka j. Topic closed. Sadly, temperature output is not accompanied by warning of known bugs. That would add clarity and save time for users, e.g. it was not obvious to me that man 4 cpu http://man.openbsd.org/cpu#BUGS needs to be read. Although that would add complexity to the code and take time from developers, sadly.
Re: laptop cpu high temperature while idle
o...@mailo.com wrote: $ sysctl hw.sensors | grep temp hw.sensors.cpu0.temp0=95.00 degC hw.sensors.acpitz0.temp0=79.00 degC (zone temperature) I have an old (of course) IBM/Lenovo X60 with a similar issue. Once it gets to 80 or 90C, the CPU goes into thermal runaway, emits a "exceeded 128C" syslog error and autoshuts down. I tried replacing the CPU paste, with little effect. So now it has: $ cat /etc/sysctl.conf hw.setperf=1 and the cpu runs at 1GHz instead of 1.6GHz and seems to stay cool even when working the CPU and graphics hard. John
Re: laptop cpu high temperature while idle
>> $ sysctl hw.sensors | grep temp >> hw.sensors.cpu0.temp0=95.00 degC >> hw.sensors.acpitz0.temp0=79.00 degC (zone temperature) > This seems hot for doing nothing. Does it run cooler on Linux? 1. Linux live usb, right after reboot from OpenBSD: $ sensors coretemp-isa- Adapter: ISA adapter Core 0: +79.0°C (high = +85.0°C, crit = +85.0°C) Core 1: +78.0°C (high = +85.0°C, crit = +85.0°C) acpitz-virtual-0 Adapter: Virtual device temp1:+76.0°C (crit = +119.0°C) nouveau-pci-0100 Adapter: PCI adapter GPU core: +0.90 V (min = +0.90 V, max = +1.17 V) temp1:+85.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +2.0°C) (emerg = +110.0°C, hyst = +5.0°C) 2. Linux live usb, soon after reboot from OpenBSD: $ sensors coretemp-isa- Adapter: ISA adapter Core 0: +75.0°C (high = +85.0°C, crit = +85.0°C) Core 1: +75.0°C (high = +85.0°C, crit = +85.0°C) acpitz-virtual-0 Adapter: Virtual device temp1:+73.0°C (crit = +119.0°C) nouveau-pci-0100 Adapter: PCI adapter GPU core: +0.90 V (min = +0.90 V, max = +1.17 V) temp1:+81.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +2.0°C) (emerg = +110.0°C, hyst = +5.0°C) 3. Linux live usb, idle for longer time: $ sensors coretemp-isa- Adapter: ISA adapter Core 0: +72.0°C (high = +85.0°C, crit = +85.0°C) Core 1: +72.0°C (high = +85.0°C, crit = +85.0°C) acpitz-virtual-0 Adapter: Virtual device temp1:+70.0°C (crit = +119.0°C) nouveau-pci-0100 Adapter: PCI adapter GPU core: +0.90 V (min = +0.90 V, max = +1.17 V) temp1:+78.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +2.0°C) (emerg = +110.0°C, hyst = +5.0°C) 4. Linux live usb, idle for long time, outdoors: $ sensors coretemp-isa- Adapter: ISA adapter Core 0: +63.0°C (high = +85.0°C, crit = +85.0°C) Core 1: +64.0°C (high = +85.0°C, crit = +85.0°C) acpitz-virtual-0 Adapter: Virtual device temp1:+62.0°C (crit = +119.0°C) nouveau-pci-0100 Adapter: PCI adapter GPU core: +0.90 V (min = +0.90 V, max = +1.17 V) temp1:+69.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +2.0°C) (emerg = +110.0°C, hyst = +5.0°C) > I also wonder if the reading is correct. Does the fan speed up further > than under linux? If the CPU has 95 degrees, you should be able to feel > a pretty hot airflow and hear the fan spinning high. I can not definitely confirm that OpenBSD fan airflow is hotter than Linux one, maybe yes, but it is within the margin of error of my sense of touch and I am not equipped with a meter. In both cases airflow is hot. I also can not definitely confirm that fan speed is further. I have been using this laptop for months with Linux and fan behavior seems indistinguishable, whatever load is. I suppose, it is always at its max. > Did you enable automatic frequency scaling? I had enabled apmd but had not set the -A flag. After your reply I added -A and rebooted, result: 91 degC - log in temperature 87 degC - after a while, and not dropping screenshot: https://i.postimg.cc/rpVF1QSx/IMG-20200811-163108.jpg >> Also, it takes several seconds for xterm to redraw itself >> from top to bottom on my 1280x800 display. >> Is it because of NVIDIA graphics? > Stay away from Nvidia if possible (disable it in the BIOS if you have > hybrid graphics). Nvidia cards will be driven by the vesa / framebuffer > module, which is pretty slow on any hardware. Only discrete NVIDIA is installed, no hybrid-graphics, so if the reading is correct, this is another reason why I am unfortunate to be incapable of running an OpenBSD desktop on this laptop... > If the machine has never been serviced and the temperature seems to be > high on any OS, then cleaning the heat sink and replacing the thermal > compound may help. It certainly has to be done. Thank you, Stefan. Current summary: OpenBSD is still too hot - 87 degC cpu temperature while idle
Re: laptop cpu high temperature while idle
o...@mailo.com wrote: > CPU: 100% idle > load averages: 0.04, 0.06, 0.04 100% idle means "100% doing nothing". This is normal for a CPU that does nothing. > $ sysctl hw.sensors | grep temp > hw.sensors.cpu0.temp0=95.00 degC > hw.sensors.acpitz0.temp0=79.00 degC (zone temperature) This seems hot for doing nothing. Does it run cooler on Linux? I also wonder if the reading is correct. Does the fan speed up further than under linux? If the CPU has 95 degrees, you should be able to feel a pretty hot airflow and hear the fan spinning high. If this is not the case, I assume the reading is not correct. Did you enable automatic frequency scaling? $ cat /etc/rc.conf.local apmd_flags=-A > Also, it takes several seconds for xterm to redraw itself > from top to bottom on my 1280x800 display. > Is it because of NVIDIA graphics? Stay away from Nvidia if possible (disable it in the BIOS if you have hybrid graphics). Nvidia cards will be driven by the vesa / framebuffer module, which is pretty slow on any hardware. > Has it something to do with high temperature? No. If the machine has never been serviced and the temperature seems to be high on any OS, then cleaning the heat sink and replacing the thermal compound may help. Best Regards, Stefan
laptop cpu high temperature while idle
Fresh install of OpenBSD/6.7/amd64/install67.fs on Lenovo 3000 G530 laptop, 2008 manufacture year. Straight from the start, just after log in: CPU: 100% idle load averages: 0.04, 0.06, 0.04 $ sysctl hw.sensors | grep temp hw.sensors.cpu0.temp0=95.00 degC hw.sensors.acpitz0.temp0=79.00 degC (zone temperature) and growed by 1 degC in 3 minutes of inactivity. Found: https://www.reddit.com/r/openbsd/comments/gmmh98/has_high_cpuheat_issue_been_fixed_in_67/ which has also this link: https://old.reddit.com/r/openbsd/comments/e6qf3m/66_t420_heat/ but: 1. no solution there; 2. there temperature average is higher by a few degC, or rises inadequately under some particular load, mine - is constantly inadequate under no load. Also, it takes several seconds for xterm to redraw itself from top to bottom on my 1280x800 display. Is it because of NVIDIA graphics? Has it something to do with high temperature? I have not tried OpenBSD/6.5 mentioned in the above links - I am a new-comer. I have not syspatch'ed - I am afraid of keeping my machine running at a-little-below-water-boiling temperature. Anyway, both https://www.openbsd.org/errata67.html https://www.openbsd.org/plus.html seem to me to not contain temperature fixes. screenshot of hot while idle: https://i.postimg.cc/9fj29RHN/IMG-20200810-212534.jpg https://i.postimg.cc/2698nkwb/IMG-20200810-212848.jpg screenshots of dmesg: https://i.postimg.cc/sD7GCWmT/IMG-20200810-212954.jpg https://i.postimg.cc/kGRYwsxN/IMG-20200810-213019.jpg https://i.postimg.cc/zG3BXRFm/IMG-20200810-213036.jpg dmesg from Linux live usb: https://hastebin.com/raw/evokawoxuz Any hints?
Re: inteldrm changes cause high temperature / fan speeds
Hi, Alex Karle wrote on 25.2.2020 6.51: Hi Tero, Apologies if this breaks the threading -- I wasn't subscribed to misc@ at the time the original was sent. Have you (or any others) dug any deeper into this? My problem was more or less "solved" when the power supply from my Optiplex died. Instead of fixing the supply, I simply recycled the device and bought PC Engines APU2. I still have another slightly newer Optiplex (running Linux), but not sure when I will have time to test the latest OpenBSD on it (might take many months). Yours, Tero
Re: inteldrm changes cause high temperature / fan speeds
Hi Tero, Apologies if this breaks the threading -- I wasn't subscribed to misc@ at the time the original was sent. Have you (or any others) dug any deeper into this? I've spent a good few hours reading different related threads, but haven't found any solutions, and you seem to have come closest to narrowing down the search space for the root cause. I am also experiencing a similar heat problem on my X220. When idling, I am consistently seeing ~50deg Celcius for the CPU. I've seen this with a fresh install of 6.6 and more recently on -current. I downgraded to 6.5 and the issue disappeared (with idle CPU's at mid thirties or so). I should note that these temperatures hold for just idling in the console (no X11). Based on my symptoms, and your description, I have a hunch I might be seeing the same issue you described. In particular, the other reports of heat seem to have been solved by tweaking the BIOS settings [1], but I tried all the mentioned settings and more without any luck. If anyone has any pointers on where to look as next steps (what part of the 250k line diff might be problematic, troubleshooting steps, etc), that would be very welcome too! Thanks all for your time and help, Alex [1]: https://marc.info/?t=15738333783 dmesg: OpenBSD 6.6-current (GENERIC.MP) #653: Thu Feb 20 21:40:37 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4156157952 (3963MB) avail mem = 4017606656 (3831MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries) bios0: vendor LENOVO version "8DET76WW (1.46 )" date 06/21/2018 bios0: LENOVO 4286CTO acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 797.55 MHz, 06-2a-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 797.42 MHz, 06-2a-07 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus 14 (EXP7) acpicpu0 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpicpu1 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 halt), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 tpm0 at acpi0: TPM_ addr 0xfed4/0x5000, device 0x104a rev 0x4e acpibat0 at acpi0: BAT0 model "42T4940" serial 5067 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0: version 1.0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 797 MHz: speeds: 2701, 2700, 2400, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi "Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04
Re: inteldrm changes cause high temperature / fan speeds
Ted Unangst wrote on 13.11.2019 8.52: Tero Koskinen wrote: Eventually I pinned the problem down to April 14/15: FAULTY 091f8f6587f dlg Mon Apr 15 02:59:41 2019 + the myx_cmd FAULTY 1bbcb699ab8 dlg Mon Apr 15 00:28:29 2019 + there's a bunch PROBLEM! 7f4dd37977d jsg Sun Apr 14 10:14:50 2019 + Update shared drm code OK 505701c75b3 visa Sun Apr 14 08:51:31 2019 + Add lock I must admit that I don't have yet any idea how to fix the problematic commit (or what is actually wrong there). This is not too surprising. It's still a bit of a mystery what's different between machines that behave fine and those that don't. I have the same machine, and it's never been problematic. I note I'm at the same old bios I had when I first purchased it. bios0: vendor LENOVO version "N23ET61W (1.36 )" date 01/17/2019 Note that my device is a desktop computer (Dell Optiplex 990) with ultra small form factor (USFF) case - not Thinkpad or other laptop. Otherwise I don't mind if fan or cpu is running at 100%, but I am worried about the temperature. Idle 70C and 80+ C in use temperatures will kill the device sooner or later (small case, not so good ventilation). Otto Moerbeek wrote on 13.11.2019 8.25: > > If you run top -S, do you see any process taking lots of CPU? Nothing suspicious. I have some daemons, but they are mostly idle. load averages: 0.06, 0.03, 0.00 gurb.koti 16:45:10 104 processes: 102 idle, 2 on processor up 0:28 CPU0 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle CPU1 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle CPU2 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle CPU3 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle Memory: Real: 322M/1296M act/tot Free: 2542M Cache: 587M Swap: 0K/8189M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 24353 root -2200K 11M sleep/3 -28:19 0.00% idle3 38595 root -2200K 11M sleep/2 -28:15 0.00% idle2 28685 root -2200K 11M sleep/1 -28:13 0.00% idle1 29534 root -2200K 11M sleep/0 -28:12 0.00% idle0 43437 _gitea100 129M 73M onproc/3 thrslee 0:04 0.00% gitea 20526 root 1000K 11M sleep/0 bored 0:01 0.00% softnet 0 root -1800K 11M sleep/0 schedul 0:01 0.00% swapper 93389 root -2200K 11M sleep/0 bored 0:01 0.00% softclock 66152 root 1000K 11M sleep/2 bored 0:01 0.00% systqmp 1 root 100 476K 444K idle wait 0:01 0.00% init 83453 root 1000K 11M idle bored 0:01 0.00% drmwq 49657 root 1000K 11M idle bored 0:01 0.00% drmwq 61541 root 1000K 11M idle usbatsk 0:01 0.00% usbatsk 51529 root 1000K 11M idle bored 0:01 0.00% drmlwq 9367 root 1000K 11M idle bored 0:01 0.00% drmubwq 64175 root -1800K 11M idle bored 0:01 0.00% smr 2195 root 1000K 11M idle bored 0:01 0.00% crynlk 7 root 1000K 11M idle bored 0:01 0.00% drmtskl 2429 root 1000K 11M idle bored 0:01 0.00% drmlwq 38115 root 1000K 11M idle bored 0:01 0.00% drmubwq 40710 root -1800K 11M sleep/1 reaper0:01 0.00% reaper 58981 root 68 200K 11M idle pgzero0:01 0.00% zerothread 18061 www20 22M 27M sleep/1 select0:01 0.00% python2.7 29049 tkoskine 280 1504K 3624K onproc/0 - 0:00 0.00% top 77959 _unbound 20 33M 26M sleep/1 kqread0:00 0.00% unbound 2955 www20 17M 21M sleep/0 select0:00 0.00% python2.7 45267 www20 13M 17M sleep/0 select0:00 0.00% python2.7 5164 tkoskine 20 2128K 3068K sleep/0 kqread0:00 0.00% tmux 63466 root 20 1456K 4152K idle poll 0:00 0.00% sshd 63357 _nsd 20 99M 83M idle kqread0:00 0.00% nsd 92852 root 1800K 11M sleep/0 syncer0:00 0.00% update 48008 root 20 1616K 2044K sleep/0 poll 0:00 0.00% smbd 25978 root 20 800K 600K idle kqread0:00 0.00% slaacd 95670 _nsd 20 32M 32M idle poll 0:00 0.00% nsd 36212 root 1000K 11M idle bored 0:00 0.00% i915 75047 root -2200K 11M idle schto 0:00 0.00% i915/signal:2 53280 root -2200K 11M idle schto 0:00 0.00% i915/signal:1 28187 root 1000K 11M idle bored 0:00 0.00% i915-userptr-acq 78907 root -2200K 11M idle
Re: inteldrm changes cause high temperature / fan speeds (was: Downgrade 6.6 to 6.5)
Tero Koskinen wrote: > Eventually I pinned the problem down to April 14/15: > > FAULTY 091f8f6587f dlg Mon Apr 15 02:59:41 2019 + the myx_cmd > FAULTY 1bbcb699ab8 dlg Mon Apr 15 00:28:29 2019 + there's a bunch > PROBLEM! 7f4dd37977d jsg Sun Apr 14 10:14:50 2019 + Update shared > drm code > OK 505701c75b3 visa Sun Apr 14 08:51:31 2019 + Add lock > > I must admit that I don't have yet any idea how to fix > the problematic commit (or what is actually wrong there). This is not too surprising. It's still a bit of a mystery what's different between machines that behave fine and those that don't. I have the same machine, and it's never been problematic. I note I'm at the same old bios I had when I first purchased it. bios0: vendor LENOVO version "N23ET61W (1.36 )" date 01/17/2019 And there are some other bios options, regarding bios/efi and thunderbolt and suspend that can be set one way or the other. I have everything turned down to whatever the "oldest" settings are. CMS boot, etc.
Re: inteldrm changes cause high temperature / fan speeds (was: Downgrade 6.6 to 6.5)
On Wed, Nov 13, 2019 at 08:19:15AM +0200, Tero Koskinen wrote: > Hi, > > Sorry if someone gets this twice. My first version didn't go to the list. > > cho...@jtan.com wrote on 6.11.2019 19.52: > > Theo de Raadt writes: > >> I have some sort of X1rev6 and I don't see the problem. > >> > >> The situation is you have the hardware, and you also have the sourcecode, > >> and the repository to traverse investigate the problem. > >> > >> That sounds hard, until you give it a try. > > > > To be fair, it *is* hard. > > I have same problem on my Dell Optiplex 990 (running in "headless" mode, > no monitor attached!). > > After upgrade from 6.5-stable to 6.6-current, CPU temperature > increased from 50C to 70C..80C and the fans are running at full speed. > > So, I went and cloned OpenBSD src tree from https://github.com/openbsd/src/ > > Then I started bisecting kernel commits from 6.5-release to 6.6-current: > > ls -1 kernels > bsd.apr10.a72c25aac8e43fe > bsd.apr14.505701c75b30a46033a8 > bsd.apr23.53d03815630664 > bsd.apr27.c1f77a6b17d5a799d322 > bsd.apr29.47170b90f4a74 > bsd.apr5.b2516e1f98d4a5f7757 > bsd.jul31.ddc1a6c2c17 > bsd.jun.b2a28ec4ea > bsd.jun1.535cf6c2b > bsd.may1.4a0e86bfb04cce9 > bsd.may19.01b2b04ad452620a32 > > > > (Note the list isn't complete. I noticed that kernel became backwards > incompatible at some point in April and I had to create a temporary > 6.5 installation on another disk.) > > Eventually I pinned the problem down to April 14/15: > > FAULTY 091f8f6587f dlg Mon Apr 15 02:59:41 2019 + the myx_cmd > FAULTY 1bbcb699ab8 dlg Mon Apr 15 00:28:29 2019 + there's a bunch > PROBLEM! 7f4dd37977d jsg Sun Apr 14 10:14:50 2019 + Update shared > drm code > OK 505701c75b3 visa Sun Apr 14 08:51:31 2019 + Add lock > > I must admit that I don't have yet any idea how to fix > the problematic commit (or what is actually wrong there). > > Reverting 7f4dd37977d didn't work for latest 6.6-current as there > have been too many changes after that. > > I also tried to check the latest changes from linux-4.19.y, > but didn't spot anything useful. > > Yours, > Tero If you run top -S, do you see any process taking lots of CPU? -Otto > > > dmesg: > OpenBSD 6.6-current (GENERIC.MP) #452: Mon Nov 11 19:08:23 MST 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4153880576 (3961MB) > avail mem = 4015665152 (3829MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf2650 (71 entries) > bios0: vendor Dell Inc. version "A19" date 08/26/2015 > bios0: Dell Inc. OptiPlex 990 > acpi0 at bios0: ACPI 4.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC TCPA SSDT MCFG HPET BOOT SSDT SSDT DMAR SLIC > acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S4) GLAN(S4) RP01(S4) > PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) > PXSX(S4) RP06(S4) PXSX(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.69 MHz, 06-2a-07 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.35 MHz, 06-2a-07 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.35 MHz, 06-2a-07 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,
inteldrm changes cause high temperature / fan speeds (was: Downgrade 6.6 to 6.5)
Hi, Sorry if someone gets this twice. My first version didn't go to the list. cho...@jtan.com wrote on 6.11.2019 19.52: > Theo de Raadt writes: >> I have some sort of X1rev6 and I don't see the problem. >> >> The situation is you have the hardware, and you also have the sourcecode, >> and the repository to traverse investigate the problem. >> >> That sounds hard, until you give it a try. > > To be fair, it *is* hard. I have same problem on my Dell Optiplex 990 (running in "headless" mode, no monitor attached!). After upgrade from 6.5-stable to 6.6-current, CPU temperature increased from 50C to 70C..80C and the fans are running at full speed. So, I went and cloned OpenBSD src tree from https://github.com/openbsd/src/ Then I started bisecting kernel commits from 6.5-release to 6.6-current: > ls -1 kernels bsd.apr10.a72c25aac8e43fe bsd.apr14.505701c75b30a46033a8 bsd.apr23.53d03815630664 bsd.apr27.c1f77a6b17d5a799d322 bsd.apr29.47170b90f4a74 bsd.apr5.b2516e1f98d4a5f7757 bsd.jul31.ddc1a6c2c17 bsd.jun.b2a28ec4ea bsd.jun1.535cf6c2b bsd.may1.4a0e86bfb04cce9 bsd.may19.01b2b04ad452620a32 > (Note the list isn't complete. I noticed that kernel became backwards incompatible at some point in April and I had to create a temporary 6.5 installation on another disk.) Eventually I pinned the problem down to April 14/15: FAULTY 091f8f6587f dlg Mon Apr 15 02:59:41 2019 + the myx_cmd FAULTY 1bbcb699ab8 dlg Mon Apr 15 00:28:29 2019 + there's a bunch PROBLEM! 7f4dd37977d jsg Sun Apr 14 10:14:50 2019 + Update shared drm code OK 505701c75b3 visa Sun Apr 14 08:51:31 2019 + Add lock I must admit that I don't have yet any idea how to fix the problematic commit (or what is actually wrong there). Reverting 7f4dd37977d didn't work for latest 6.6-current as there have been too many changes after that. I also tried to check the latest changes from linux-4.19.y, but didn't spot anything useful. Yours, Tero dmesg: OpenBSD 6.6-current (GENERIC.MP) #452: Mon Nov 11 19:08:23 MST 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4153880576 (3961MB) avail mem = 4015665152 (3829MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf2650 (71 entries) bios0: vendor Dell Inc. version "A19" date 08/26/2015 bios0: Dell Inc. OptiPlex 990 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC TCPA SSDT MCFG HPET BOOT SSDT SSDT DMAR SLIC acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S4) GLAN(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.69 MHz, 06-2a-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.35 MHz, 06-2a-07 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.35 MHz, 06-2a-07 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2494.35 MHz, 06-2a-07 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IB
Re: OT: Temperature sensors suggestions?
http://man.openbsd.org/onewire http://man.openbsd.org/uow.4 http://man.openbsd.org/owtemp.4
Re: OT: Temperature sensors suggestions?
On 5/19/2018 4:52 AM, Hiltjo Posthuma wrote: > On Fri, May 18, 2018 at 04:42:01PM -0400, Daniel Ouellet wrote: >> Does anyone have a decent temperature sensors that can connect to an >> OpenBSD server and be reliable and give any decent reading via either >> USB or Serial port or even stand alone via Ethernet? >> [snip] > > I use PCsensors TEMPer-based USB device and the ugold(4) driver. > It works well. > For a simple temperature sensor setup, the TEMPer-based sensor works very well. I just plugged it into the USB port via a short USB extension cable, and started to monitor the temperature via OpenBSD's sensor framework. # sysctl hw.sensors.cpu0.temp0 hw.sensors.cpu0.temp0=23.00 degC
Re: OT: Temperature sensors suggestions?
I would suggest bme280 sensor. If you have a spare VGA port you can use the d2c bus as i2c and plug directly into it with a modified VGA cable. Other wise yeah esp8266 module + bme280 for 5$ is going to give you the best result. On Fri., 18 May 2018, 4:01 pm Base Pr1me, <tlemery5...@gmail.com> wrote: > I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming > involved. > Good hardware though, if that's what you're looking for. > > On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet <dan...@presscom.net> > wrote: > > > Does anyone have a decent temperature sensors that can connect to an > > OpenBSD server and be reliable and give any decent reading via either > > USB or Serial port or even stand alone via Ethernet? > > > > I asked because yes I can use the sensors on some servers, but I got a > > pretty expensive router blowing up because an AC unit stop working and > > in a few hours the router was history and I need something reliable so I > > can graph the changes in temperature to keep track of things. > > > > I got lucky this time as that using was providing 192 VoIP channels and > > I had just moved them from PRI to full SIP like a month earlier. If I > > haven't done that it would have been a disaster for me! > > > > So, I need more then just servers sensors so I can place these at > > various location to get a better idea of what's going on. > > > > I don't understand why it is so difficult to have decent AC technician > > keep AC units working properly. It's not like brain surgery, but that's > > always a problem. > > > > Anything you know or use that is reliable that you can recommend would > > be very much appreciated. > > > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > > no proprietary shit or Windows crap like I found tonnes of them. I have > > NO Windows systems for 20+ years already and I am sure hell not going to > > install any either. I try to keep it simple. Even snmp reading is find. > > Simpler the better. I can grab the reading and save to a database to > > graph later and what not. I got two self standing units in the pass, > > nice but they get hacked and not useful obviously, so add-on to OpenBSD > > is better to me. I trust that way more then all the self standing units, > > records proving it... > > > > If that's no interest for the list fell free to reply off line as well, > > but I guess some might like to know too. > > > > Thanks in advance for any suggestions... > > > > Daniel > > > > >
Re: OT: Temperature sensors suggestions?
I do not remember where I bought my ugold(4) back then (maybe soekris?), but this one looks the same: https://www.amazon.de/Thermometer-Temperatur-Sensor-Rekord-F%C3%BCr-PC-Maschine/dp/B00C0OW4OE Since it says on the inside: "pcsensor.com" this might be the origin: http://pcsensor.com/usb-thermometers/gold-temper.html With it I get: hw.sensors.ugold0.temp0=29.12 degC (inner) It's not super correct, my tests seemed to show that the deviation depends on the current temperatur range. Marcus dan...@presscom.net (Daniel Ouellet), 2018.05.18 (Fri) 22:42 (CEST): > Does anyone have a decent temperature sensors that can connect to an > OpenBSD server and be reliable and give any decent reading via either > USB or Serial port or even stand alone via Ethernet? > > I asked because yes I can use the sensors on some servers, but I got a > pretty expensive router blowing up because an AC unit stop working and > in a few hours the router was history and I need something reliable so I > can graph the changes in temperature to keep track of things. > > I got lucky this time as that using was providing 192 VoIP channels and > I had just moved them from PRI to full SIP like a month earlier. If I > haven't done that it would have been a disaster for me! > > So, I need more then just servers sensors so I can place these at > various location to get a better idea of what's going on. > > I don't understand why it is so difficult to have decent AC technician > keep AC units working properly. It's not like brain surgery, but that's > always a problem. > > Anything you know or use that is reliable that you can recommend would > be very much appreciated. > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > no proprietary shit or Windows crap like I found tonnes of them. I have > NO Windows systems for 20+ years already and I am sure hell not going to > install any either. I try to keep it simple. Even snmp reading is find. > Simpler the better. I can grab the reading and save to a database to > graph later and what not. I got two self standing units in the pass, > nice but they get hacked and not useful obviously, so add-on to OpenBSD > is better to me. I trust that way more then all the self standing units, > records proving it... > > If that's no interest for the list fell free to reply off line as well, > but I guess some might like to know too. > > Thanks in advance for any suggestions... > > Daniel >
Re : Temperature sensors suggestions?
Hello, For production environment, You may give a try to mosquitto package and to industrial modules which support mqtt 3.1 or 3.1.1. As far as i remember there's some which support standard rtd sensor like pt100/pt1000 and publish their data over wifi or ethernet. (Try adam 6015 series for example). It usually fits on a DIN rail... Eric.
Re: OT: Temperature sensors suggestions?
On Fri, May 18, 2018 at 04:42:01PM -0400, Daniel Ouellet wrote: > Does anyone have a decent temperature sensors that can connect to an > OpenBSD server and be reliable and give any decent reading via either > USB or Serial port or even stand alone via Ethernet? > > I asked because yes I can use the sensors on some servers, but I got a > pretty expensive router blowing up because an AC unit stop working and > in a few hours the router was history and I need something reliable so I > can graph the changes in temperature to keep track of things. > > I got lucky this time as that using was providing 192 VoIP channels and > I had just moved them from PRI to full SIP like a month earlier. If I > haven't done that it would have been a disaster for me! > > So, I need more then just servers sensors so I can place these at > various location to get a better idea of what's going on. > > I don't understand why it is so difficult to have decent AC technician > keep AC units working properly. It's not like brain surgery, but that's > always a problem. > > Anything you know or use that is reliable that you can recommend would > be very much appreciated. > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > no proprietary shit or Windows crap like I found tonnes of them. I have > NO Windows systems for 20+ years already and I am sure hell not going to > install any either. I try to keep it simple. Even snmp reading is find. > Simpler the better. I can grab the reading and save to a database to > graph later and what not. I got two self standing units in the pass, > nice but they get hacked and not useful obviously, so add-on to OpenBSD > is better to me. I trust that way more then all the self standing units, > records proving it... > > If that's no interest for the list fell free to reply off line as well, > but I guess some might like to know too. > > Thanks in advance for any suggestions... > > Daniel > I use PCsensors TEMPer-based USB device and the ugold(4) driver. It works well. -- Kind regards, Hiltjo
Re: OT: Temperature sensors suggestions?
If you want, i'd be happy to discuss my setup offline. I've got lots of code in GitHub already, that you could modify. There are other temp only i2c sensors that would work too. On May 18, 2018 16:38, "Daniel Ouellet" <dan...@presscom.net> wrote: Thanks, That look interesting. I wonder how the wifi works on this ESP8266 module. It's so cheap that it's nothing lost to try. (; Will see if I get other suggestions, but that's interesting and may well be fun to program a driver for the SHT31-D too. (; Daniel. On 5/18/18 5:53 PM, Base Pr1me wrote: > I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming > involved. > Good hardware though, if that's what you're looking for. > > On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet <dan...@presscom.net> wrote: > >> Does anyone have a decent temperature sensors that can connect to an >> OpenBSD server and be reliable and give any decent reading via either >> USB or Serial port or even stand alone via Ethernet? >> >> I asked because yes I can use the sensors on some servers, but I got a >> pretty expensive router blowing up because an AC unit stop working and >> in a few hours the router was history and I need something reliable so I >> can graph the changes in temperature to keep track of things. >> >> I got lucky this time as that using was providing 192 VoIP channels and >> I had just moved them from PRI to full SIP like a month earlier. If I >> haven't done that it would have been a disaster for me! >> >> So, I need more then just servers sensors so I can place these at >> various location to get a better idea of what's going on. >> >> I don't understand why it is so difficult to have decent AC technician >> keep AC units working properly. It's not like brain surgery, but that's >> always a problem. >> >> Anything you know or use that is reliable that you can recommend would >> be very much appreciated. >> >> I am trying to keep it simple, so using base tools in OpenBSD is a must, >> no proprietary shit or Windows crap like I found tonnes of them. I have >> NO Windows systems for 20+ years already and I am sure hell not going to >> install any either. I try to keep it simple. Even snmp reading is find. >> Simpler the better. I can grab the reading and save to a database to >> graph later and what not. I got two self standing units in the pass, >> nice but they get hacked and not useful obviously, so add-on to OpenBSD >> is better to me. I trust that way more then all the self standing units, >> records proving it... >> >> If that's no interest for the list fell free to reply off line as well, >> but I guess some might like to know too. >> >> Thanks in advance for any suggestions... >> >> Daniel >> >>
Re: OT: Temperature sensors suggestions?
Thanks, That look interesting. I wonder how the wifi works on this ESP8266 module. It's so cheap that it's nothing lost to try. (; Will see if I get other suggestions, but that's interesting and may well be fun to program a driver for the SHT31-D too. (; Daniel. On 5/18/18 5:53 PM, Base Pr1me wrote: > I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming > involved. > Good hardware though, if that's what you're looking for. > > On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet <dan...@presscom.net> wrote: > >> Does anyone have a decent temperature sensors that can connect to an >> OpenBSD server and be reliable and give any decent reading via either >> USB or Serial port or even stand alone via Ethernet? >> >> I asked because yes I can use the sensors on some servers, but I got a >> pretty expensive router blowing up because an AC unit stop working and >> in a few hours the router was history and I need something reliable so I >> can graph the changes in temperature to keep track of things. >> >> I got lucky this time as that using was providing 192 VoIP channels and >> I had just moved them from PRI to full SIP like a month earlier. If I >> haven't done that it would have been a disaster for me! >> >> So, I need more then just servers sensors so I can place these at >> various location to get a better idea of what's going on. >> >> I don't understand why it is so difficult to have decent AC technician >> keep AC units working properly. It's not like brain surgery, but that's >> always a problem. >> >> Anything you know or use that is reliable that you can recommend would >> be very much appreciated. >> >> I am trying to keep it simple, so using base tools in OpenBSD is a must, >> no proprietary shit or Windows crap like I found tonnes of them. I have >> NO Windows systems for 20+ years already and I am sure hell not going to >> install any either. I try to keep it simple. Even snmp reading is find. >> Simpler the better. I can grab the reading and save to a database to >> graph later and what not. I got two self standing units in the pass, >> nice but they get hacked and not useful obviously, so add-on to OpenBSD >> is better to me. I trust that way more then all the self standing units, >> records proving it... >> >> If that's no interest for the list fell free to reply off line as well, >> but I guess some might like to know too. >> >> Thanks in advance for any suggestions... >> >> Daniel >> >>
Re: OT: Temperature sensors suggestions?
I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming involved. Good hardware though, if that's what you're looking for. On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet <dan...@presscom.net> wrote: > Does anyone have a decent temperature sensors that can connect to an > OpenBSD server and be reliable and give any decent reading via either > USB or Serial port or even stand alone via Ethernet? > > I asked because yes I can use the sensors on some servers, but I got a > pretty expensive router blowing up because an AC unit stop working and > in a few hours the router was history and I need something reliable so I > can graph the changes in temperature to keep track of things. > > I got lucky this time as that using was providing 192 VoIP channels and > I had just moved them from PRI to full SIP like a month earlier. If I > haven't done that it would have been a disaster for me! > > So, I need more then just servers sensors so I can place these at > various location to get a better idea of what's going on. > > I don't understand why it is so difficult to have decent AC technician > keep AC units working properly. It's not like brain surgery, but that's > always a problem. > > Anything you know or use that is reliable that you can recommend would > be very much appreciated. > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > no proprietary shit or Windows crap like I found tonnes of them. I have > NO Windows systems for 20+ years already and I am sure hell not going to > install any either. I try to keep it simple. Even snmp reading is find. > Simpler the better. I can grab the reading and save to a database to > graph later and what not. I got two self standing units in the pass, > nice but they get hacked and not useful obviously, so add-on to OpenBSD > is better to me. I trust that way more then all the self standing units, > records proving it... > > If that's no interest for the list fell free to reply off line as well, > but I guess some might like to know too. > > Thanks in advance for any suggestions... > > Daniel > >
OT: Temperature sensors suggestions?
Does anyone have a decent temperature sensors that can connect to an OpenBSD server and be reliable and give any decent reading via either USB or Serial port or even stand alone via Ethernet? I asked because yes I can use the sensors on some servers, but I got a pretty expensive router blowing up because an AC unit stop working and in a few hours the router was history and I need something reliable so I can graph the changes in temperature to keep track of things. I got lucky this time as that using was providing 192 VoIP channels and I had just moved them from PRI to full SIP like a month earlier. If I haven't done that it would have been a disaster for me! So, I need more then just servers sensors so I can place these at various location to get a better idea of what's going on. I don't understand why it is so difficult to have decent AC technician keep AC units working properly. It's not like brain surgery, but that's always a problem. Anything you know or use that is reliable that you can recommend would be very much appreciated. I am trying to keep it simple, so using base tools in OpenBSD is a must, no proprietary shit or Windows crap like I found tonnes of them. I have NO Windows systems for 20+ years already and I am sure hell not going to install any either. I try to keep it simple. Even snmp reading is find. Simpler the better. I can grab the reading and save to a database to graph later and what not. I got two self standing units in the pass, nice but they get hacked and not useful obviously, so add-on to OpenBSD is better to me. I trust that way more then all the self standing units, records proving it... If that's no interest for the list fell free to reply off line as well, but I guess some might like to know too. Thanks in advance for any suggestions... Daniel
Re: adt(4) on Sun W1100z OpenBSD6.0-stable returns weird(?) temperature and RPM
> I've noticed that the ADT driver correctly attaches, but reports weird > (excessive?) > temperature and RPM. Is adt7467 supported? > > ### > adt0 at iic0 addr 0x2e: adt7467 rev 0x71 > > $ sysctl -a | grep -e degC -e RPM > hw.sensors.acpitz0.temp0=45.00 degC (zone temperature) > hw.sensors.adt0.temp0=109.00 degC (Remote) > hw.sensors.adt0.temp1=109.00 degC (Internal) > hw.sensors.adt0.temp2=0.00 degC (Remote) > hw.sensors.adt0.fan0=675000 RPM > hw.sensors.adt0.fan2=675000 RPM > hw.sensors.kate0.temp2=63.00 degC Early sensor devices were rather annoying. Registers indicate a value which needs to be scaled using per-device tables. Assuming the device has been properly wired externally with registers and capacitors. If that wiring diagram was changed, the vendor who put them into the machine would know but we wouldn't. We've even seen chips with some of the sensors pins left floating or tied to ground. These drivers were best effort.
adt(4) on Sun W1100z OpenBSD6.0-stable returns weird(?) temperature and RPM
Hello openbsd-misc, I've got a legacy "Sun Microsystems W1100z" running 6.0-stable AMD64 I've noticed that the ADT driver correctly attaches, but reports weird (excessive?) temperature and RPM. Is adt7467 supported? ### adt0 at iic0 addr 0x2e: adt7467 rev 0x71 $ sysctl -a | grep -e degC -e RPM hw.sensors.acpitz0.temp0=45.00 degC (zone temperature) hw.sensors.adt0.temp0=109.00 degC (Remote) hw.sensors.adt0.temp1=109.00 degC (Internal) hw.sensors.adt0.temp2=0.00 degC (Remote) hw.sensors.adt0.fan0=675000 RPM hw.sensors.adt0.fan2=675000 RPM hw.sensors.kate0.temp2=63.00 degC ### Full `dmesg' and full `sysctl -a' follows. (sections divided by ###) I've changed kern.hostname to in sysctl output to protect the guilty... Thank you for your time, Jan Vlach ### DMESG OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2130051072 (2031MB) avail mem = 2061082624 (1965MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.33 @ 0xefeb0 (37 entries) bios0: vendor Sun Microsystems version "R01-B5 S0" date 03/17/2006 bios0: Sun Microsystems W1100z/2100z acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SRAT APIC SSDT acpi0: wakeup devices USB0(S1) USB1(S1) Z009(S1) Z00A(S1) Z00B(S1) G0PA(S4) G0PB(S4) G1PA(S4) G1PB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Opteron(tm) Processor 144, 1795.16 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: AMD errata 89, 97, 101 present, BIOS upgrade may be required mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins ioapic1 at mainbus0: apid 2 pa 0xe800, version 11, 4 pins ioapic2 at mainbus0: apid 3 pa 0xe801, version 11, 4 pins ioapic3 at mainbus0: apid 4 pa 0xe850, version 11, 4 pins ioapic4 at mainbus0: apid 5 pa 0xe851, version 11, 4 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (TP2P) acpiprt2 at acpi0: bus 2 (G0PA) acpiprt3 at acpi0: bus 3 (G0PB) acpiprt4 at acpi0: bus 9 (Z00D) acpiprt5 at acpi0: bus 14 (G1PA) acpiprt6 at acpi0: bus 19 (G1PB) acpicpu0 at acpi0: C1(@1 halt!), PSS acpitz0 at acpi0: critical temperature is 65 degC acpibtn0 at acpi0: PWRB "PNP0A05" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0501" at acpi0 not configured cpu0: Cool'n'Quiet K8 1795 MHz: speeds: 1800 1000 MHz pci0 at mainbus0 bus 0 ppb0 at pci0 dev 6 function 0 "AMD 8111" rev 0x07 pci1 at ppb0 bus 1 pciide0 at pci1 dev 2 function 0 "CMD Technology SiI3512 SATA" rev 0x01: DMA pciide0: using apic 1 int 17 for native-PCI interrupt ohci0 at pci1 dev 3 function 0 "NEC USB" rev 0x43: apic 1 int 18, version 1.0, legacy support ohci1 at pci1 dev 3 function 1 "NEC USB" rev 0x43: apic 1 int 19, version 1.0, legacy support ehci0 at pci1 dev 3 function 2 "NEC USB" rev 0x04: apic 1 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 "NEC OHCI root hub" rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1 amdpcib0 at pci0 dev 7 function 0 "AMD 8111 LPC" rev 0x05 pciide1 at pci0 dev 7 function 1 "AMD 8111 IDE" rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide1 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 78533MB, 160836480 sectors wd1 at pciide1 channel 0 drive 1: wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5 wd2 at pciide1 channel 1 drive 0: wd2: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 amdiic0 at pci0 dev 7 function 2 "AMD 8111 SMBus" rev 0x02: SCI iic0 at amdiic0 adt0 at iic0 addr 0x2e: adt7467 rev 0x71 amdpm0 at pci0 dev 7 function 3 "AMD 8111 Power" rev 0x05 ppb1 at pci0 dev 10 function 0 "AMD 8131 PCIX" rev 0x12 pci2 at ppb1 bus 2 aapic0 at pci0 dev 10 function 1 "AMD 8131 PCIX IOAPIC" rev 0x01 ppb2 at pci0 dev 11 function 0 "AMD 8131 PCIX" rev 0x12 pci3 at ppb2 bus 3 bge0 at pci3 dev 2 function 0 "Broadcom BCM5703X" rev 0x02, BCM5702/5703 A2 (0x1002): a
Re: Temperature
On 2014-11-14 19:59, patrick keshishian wrote: As I say, I never have had this issue with x120e, which I've been using for over 3 years with OpenBSD, mainly following snapshots. Thanks for the info. Clearly, I need to open the beast for inspection. Cheers! -- Étienne
Re: Temperature
On Fri, Nov 14, 2014 at 06:27:10PM +, Etienne wrote: [...] (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80??C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. [...] So running on another OS for a longer time has the temperature of your laptop staying at around 80C? That sounds awfully high. Maybe you just need to clean out the fans and airways inside the laptop and the timing is just a coincidence. Just make sure the fan does not turn (by blocking it with a toothpick or the like) when blowing compressed air through the case or vacuuming out dustbunnies so the bearing does not get damaged. -- Gregor Best
Temperature
Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80°C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100°C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? Cheers! -- Ãtienne OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-3 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PB5_) acpiprt2 at acpi0: bus 4 (P2P_) acpiprt3 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature is 92 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model 42T4787 serial 626 oem SONY acpibtn2 at acpi0: LID_ cpu0: PowerNow! K8 1597 MHz: speeds: 1600 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD RS780 Host rev 0x00 ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 5 function 0 ATI Radeon HD 3200 rev 0x00 drm0 at radeondrm0 radeondrm0: apic 2 int 18 ppb1 at pci0 dev 5 function 0 AMD RS780 PCIE rev 0x00: msi pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), msi, address c8:0a:a9:6a:6c:6b rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb2 at pci0 dev 6 function 0 AMD RS780 PCIE rev 0x00: msi pci3 at ppb2 bus 3 Realtek 8192SE rev 0x10 at pci3 dev 0 function 0 not configured ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 22, AHCI 1.1 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, ST9250315AS, 0020 SCSI3 0/direct fixed naa.5000c50022882f8c sd0: 238475MB, 512 bytes/sector, 488397168 sectors ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 16, version 1.0, legacy
Re: Temperature
On 11/14/14 13:27, Etienne wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80°C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100°C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? I'm running OpenBSD -current on my X120e. Temperature is around 68-72C unless I'm doing something very CPU intensive (but then it never gets up higher than around 82C). Not sure what to tell you to diagnose it. Cheers! -- Étienne OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-3 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PB5_) acpiprt2 at acpi0: bus 4 (P2P_) acpiprt3 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature is 92 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model 42T4787 serial 626 oem SONY acpibtn2 at acpi0: LID_ cpu0: PowerNow! K8 1597 MHz: speeds: 1600 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD RS780 Host rev 0x00 ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 5 function 0 ATI Radeon HD 3200 rev 0x00 drm0 at radeondrm0 radeondrm0: apic 2 int 18 ppb1 at pci0 dev 5 function 0 AMD RS780 PCIE rev 0x00: msi pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), msi, address c8:0a:a9:6a:6c:6b rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb2 at pci0 dev 6 function 0 AMD RS780 PCIE rev 0x00: msi pci3 at ppb2 bus 3 Realtek 8192SE rev 0x10 at pci3 dev 0 function 0 not configured ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 22, AHCI 1.1 scsibus1
Re: Temperature
Etienne etienne.m...@magickarpet.org wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80??C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100??C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? Cheers! I have no trouble running 5.6 and had no trouble running 5.5 on my x120e. Is your computer actually getting up to 92 degC? I do run with apmd -L, which helps to reduce temperature, but that's still insane. -- Martin OpenBSD 5.6 (GENERIC.MP) #2: Tue Oct 28 11:13:59 CET 2014 r...@stable-56-amd64.mtier.org:/binpatchng/work-binpatch56-amd64/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16736387072 (15961MB) avail mem = 16282083328 (15527MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf9ba0 (60 entries) bios0: vendor LENOVO version 8FET27WW (1.11 ) date 03/24/2011 bios0: LENOVO 0596CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC HPET APIC MCFG UEFI UEFI SSDT SSDT UEFI acpi0: wakeup devices PB4_(S4) PB5_(S4) PB6_(S4) PB7_(S4) OHC1(S3) EHC1(S3) OHC2(S3) EHC2(S3) OHC3(S3) EHC3(S3) OHC4(S3) SBAZ(S4) GEC_(S4) P2P_(S5) SPB0(S4) SPB1(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD E-350 Processor, 41193.33 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD E-350 Processor, 1596.60 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpimcfg0 at acpi0 addr 0xf800, bus 0-31 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB4_) acpiprt2 at acpi0: bus -1 (PB5_) acpiprt3 at acpi0: bus 1 (PB6_) acpiprt4 at acpi0: bus -1 (PB7_) acpiprt5 at acpi0: bus 2 (P2P_) acpiprt6 at acpi0: bus 3 (SPB0) acpiprt7 at acpi0: bus -1 (SPB1) acpiprt8 at acpi0: bus -1 (SPB2) acpiprt9 at acpi0: bus -1 (SPB3) acpiec0 at acpi0 acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpitz0 at acpi0: critical temperature is 92 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model 42T4785 serial 223 type LION oem SANYO acpibtn2 at acpi0: LID_ cpu0: 41193 MHz: speeds: 1600 1280 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00 radeondrm0 at pci0 dev 1 function 0 ATI Radeon HD 6310 rev 0x00 drm0 at radeondrm0 radeondrm0: msi azalia0 at pci0 dev 1 function 1 ATI Radeon HD 6310 HD
Re: Temperature
On 2014-11-14 18:27, Etienne wrote: Hello list, Sorry for answering to myself, that was my first post and I didn't expect the attachements to be concatenated after my message. Please let me reformat: x100e# dmesg OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-3 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PB5_) acpiprt2 at acpi0: bus 4 (P2P_) acpiprt3 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature is 92 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model 42T4787 serial 626 oem SONY acpibtn2 at acpi0: LID_ cpu0: PowerNow! K8 1597 MHz: speeds: 1600 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD RS780 Host rev 0x00 ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 5 function 0 ATI Radeon HD 3200 rev 0x00 drm0 at radeondrm0 radeondrm0: apic 2 int 18 ppb1 at pci0 dev 5 function 0 AMD RS780 PCIE rev 0x00: msi pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), msi, address c8:0a:a9:6a:6c:6b rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb2 at pci0 dev 6 function 0 AMD RS780 PCIE rev 0x00: msi pci3 at ppb2 bus 3 Realtek 8192SE rev 0x10 at pci3 dev 0 function 0 not configured ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 22, AHCI 1.1 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, ST9250315AS, 0020 SCSI3 0/direct fixed naa.5000c50022882f8c sd0: 238475MB, 512 bytes/sector, 488397168 sectors ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 16, version 1.0, legacy support ohci1 at pci0 dev 18 function 1 ATI SB700 USB rev 0x00: apic 2 int 16, version 1.0, legacy support ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1 ohci2 at pci0 dev 19 function 0 ATI SB700 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ehci1 at pci0 dev 19 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 19 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 ATI EHCI root hub rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 ATI SBx00 SMBus rev 0x3c: SMI iic0 at piixpm0 spdmem0 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM azalia0 at pci0 dev 20 function 2 ATI SBx00 HD Audio rev 0x00: apic 2 int 16 azalia0: codecs: Conexant/0x5066 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 ATI SB700 ISA rev 0x00 ppb3 at pci0 dev 20 function 4 ATI SB600 PCI rev 0x00 pci4 at ppb3 bus 4 pchb1 at pci0 dev 24 function 0 AMD AMD64 0Fh HyperTransport rev 0x00 pchb2 at pci0 dev 24 function 1 AMD AMD64 0Fh Address Map rev 0x00 pchb3 at pci0 dev 24 function 2 AMD AMD64 0Fh DRAM Cfg rev 0x00 kate0 at pci0 dev 24 function 3 AMD AMD64 0Fh Misc Cfg rev 0x00: core rev BH-G2 usb2 at ohci0: USB revision 1.0 uhub2
Re: Temperature
Did a fan die? Or are you blocking the vent somehow? I killed a laptop like that once by putting it on my lap. Turned out the fan vent was on the bottom and the laptop needed to be on a flat surface. Usually called a desk. So I don't know why it was classified as a laptop. :) Tim.
Re: Temperature
On 2014-11-14 18:56, Gregor Best wrote: (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80??C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. [...] So running on another OS for a longer time has the temperature of your laptop staying at around 80C? That sounds awfully high. Maybe you just need to clean out the fans and airways inside the laptop and the timing is just a coincidence. Just make sure the fan does not turn (by blocking it with a toothpick or the like) when blowing compressed air through the case or vacuuming out dustbunnies so the bearing does not get damaged. Thanks everybody for the feedback and advices. I think it's fair to conclude my machine has a unique problem not related to the model (I bought it as a used machine, maybe the previous owner messed something). I'm still surprised by the 20°C difference between OpenBSD and Linux, and by the fact it was apparently working fine on 5.4. I'll see how much I can clean it up/change the paste before trying anything else. Cheers! -- Étienne
Re: Temperature
Hi, On 11/14/14, Etienne etienne.m...@magickarpet.org wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 I don't believe I have ever seen the issue you describe with my x120e. hw.vendor=LENOVO hw.version=ThinkPad X120e hw.sensors.acpitz0.temp0=75.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=75.00 degC hw.sensors.acpithinkpad0.temp1=0.00 degC hw.sensors.acpithinkpad0.temp2=75.00 degC hw.sensors.acpithinkpad0.temp3=0.00 degC hw.sensors.acpithinkpad0.temp4=0.00 degC hw.sensors.acpithinkpad0.temp5=0.00 degC hw.sensors.acpithinkpad0.temp6=27.00 degC hw.sensors.acpithinkpad0.temp7=0.00 degC hw.sensors.km0.temp0=75.88 degC hw.sensors.acpithinkpad0.fan0=441 RPM (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80°C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. That may be a hint that something may be wrong with your cooling. Dust blockage, etc. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100°C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? As I say, I never have had this issue with x120e, which I've been using for over 3 years with OpenBSD, mainly following snapshots. Running older snapshot atm: $ sysctl kern.version kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep 9 00:28:20 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I have a Gateway LT31 (?) that used to have similar issue as you describe. After first cold boot, it would immediately shutdown because of temperature warning. Next boot, it would be fine. However, since the last snapshot I put on it, from Sep. It hasn't exhibited this behavior. Then again, the Gateway isn't used much; so it could be that I've been lucky. --patrick Cheers! -- Étienne OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-3 acpihpet0
Re: Temperature
On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote: Hi, On 11/14/14, Etienne etienne.m...@magickarpet.org wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 I don't believe I have ever seen the issue you describe with my x120e. hw.vendor=LENOVO hw.version=ThinkPad X120e hw.sensors.acpitz0.temp0=75.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=75.00 degC hw.sensors.acpithinkpad0.temp1=0.00 degC hw.sensors.acpithinkpad0.temp2=75.00 degC hw.sensors.acpithinkpad0.temp3=0.00 degC hw.sensors.acpithinkpad0.temp4=0.00 degC hw.sensors.acpithinkpad0.temp5=0.00 degC hw.sensors.acpithinkpad0.temp6=27.00 degC hw.sensors.acpithinkpad0.temp7=0.00 degC hw.sensors.km0.temp0=75.88 degC hw.sensors.acpithinkpad0.fan0=441 RPM (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80?C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. That may be a hint that something may be wrong with your cooling. Dust blockage, etc. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100?C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? As I say, I never have had this issue with x120e, which I've been using for over 3 years with OpenBSD, mainly following snapshots. Running older snapshot atm: $ sysctl kern.version kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep 9 00:28:20 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I have a Gateway LT31 (?) that used to have similar issue as you describe. After first cold boot, it would immediately shutdown because of temperature warning. Next boot, it would be fine. However, since the last snapshot I put on it, from Sep. It hasn't exhibited this behavior. Then again, the Gateway isn't used much; so it could be that I've been lucky. I fixed the bogus shutdowns at the last hackathon (the ones where acpitz(4) would return temperatures in the 4000-5000K range). -ml --patrick Cheers! -- ?tienne OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2
Re: Temperature
On 11/14/14, Mike Larkin mlar...@azathoth.net wrote: On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote: Hi, On 11/14/14, Etienne etienne.m...@magickarpet.org wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 I don't believe I have ever seen the issue you describe with my x120e. hw.vendor=LENOVO hw.version=ThinkPad X120e hw.sensors.acpitz0.temp0=75.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=75.00 degC hw.sensors.acpithinkpad0.temp1=0.00 degC hw.sensors.acpithinkpad0.temp2=75.00 degC hw.sensors.acpithinkpad0.temp3=0.00 degC hw.sensors.acpithinkpad0.temp4=0.00 degC hw.sensors.acpithinkpad0.temp5=0.00 degC hw.sensors.acpithinkpad0.temp6=27.00 degC hw.sensors.acpithinkpad0.temp7=0.00 degC hw.sensors.km0.temp0=75.88 degC hw.sensors.acpithinkpad0.fan0=441 RPM (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80?C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. That may be a hint that something may be wrong with your cooling. Dust blockage, etc. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100?C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? As I say, I never have had this issue with x120e, which I've been using for over 3 years with OpenBSD, mainly following snapshots. Running older snapshot atm: $ sysctl kern.version kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep 9 00:28:20 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I have a Gateway LT31 (?) that used to have similar issue as you describe. After first cold boot, it would immediately shutdown because of temperature warning. Next boot, it would be fine. However, since the last snapshot I put on it, from Sep. It hasn't exhibited this behavior. Then again, the Gateway isn't used much; so it could be that I've been lucky. I fixed the bogus shutdowns at the last hackathon (the ones where acpitz(4) would return temperatures in the 4000-5000K range). Nice! --patrick
Re: thinkpad temperature climbs after resume
David Hoskin, 24 Sep 2014 12:18: On 9/24/14, frantisek holop min...@obiit.org wrote: there seems to be a problem with my thinkpad X60s after resume: the cpu temperature keeps going up gradually, no matter that the machine is idle. I've experienced this sometimes for the past couple of months on my Thinkpad T420. As a workaround, $ apm -H $ apm -C after resume seems to cure it. yes, this seems to be working, thanks. so i guess this goes into /etc/apm/resume -f -- some people fall for everything and stand for nothing.
Re: thinkpad temperature climbs after resume
frantisek holop, 25 Sep 2014 11:18: David Hoskin, 24 Sep 2014 12:18: On 9/24/14, frantisek holop min...@obiit.org wrote: there seems to be a problem with my thinkpad X60s after resume: the cpu temperature keeps going up gradually, no matter that the machine is idle. I've experienced this sometimes for the past couple of months on my Thinkpad T420. As a workaround, $ apm -H $ apm -C after resume seems to cure it. yes, this seems to be working, thanks. so i guess this goes into /etc/apm/resume but what is making the temperature rise? the machine is idle, load is 0.0, setperf=0, cpuspeed is the lowest. -f -- it has been discovered: research causes cancer in rats.
thinkpad temperature climbs after resume
there seems to be a problem with my thinkpad X60s after resume: the cpu temperature keeps going up gradually, no matter that the machine is idle. normal operating temperature is around 50-55C. however after a resume, quite quickly the temperature starts to climb and the whole notebook is becoming noticably hot on the outside. a reboot restores the correct temperature again. $ grep apmd /etc/rc.conf.local apmd_flags=-C disabling acpitz does not help. normal operation: hw.sensors.acpitz0.temp0=52.00 degC (zone temperature) hw.sensors.acpitz1.temp0=51.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=52.00 degC hw.sensors.acpithinkpad0.temp1=54.00 degC hw.sensors.acpithinkpad0.temp3=49.00 degC hw.sensors.acpithinkpad0.temp4=32.00 degC hw.sensors.acpithinkpad0.temp6=31.00 degC hw.sensors.acpithinkpad0.fan0=3102 RPM hw.sensors.cpu0.temp0=51.00 degC hw.sensors.aps0.temp0=54.00 degC hw.sensors.aps0.temp1=54.00 degC after resume it starts to climb: hw.sensors.acpitz0.temp0=59.00 degC (zone temperature) hw.sensors.acpitz1.temp0=75.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=59.00 degC hw.sensors.acpithinkpad0.temp1=51.00 degC hw.sensors.acpithinkpad0.temp3=61.00 degC hw.sensors.acpithinkpad0.temp4=22.00 degC hw.sensors.acpithinkpad0.temp6=22.00 degC hw.sensors.acpithinkpad0.fan0=3115 RPM hw.sensors.cpu0.temp0=75.00 degC hw.sensors.aps0.temp0=51.00 degC hw.sensors.aps0.temp1=51.00 degC OpenBSD 5.6-current (GENERIC.MP) #338: Wed Sep 10 17:55:18 MDT 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137354240 (2038MB) avail mem = 2090008576 (1993MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/18/07, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7BETC9WW (2.10 ) date 04/18/2007 bios0: LENOVO 1705CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4629 serial 327 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 0xd/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, 0x/0x, using Analog Devices AD1981HD audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 pci1 at ppb0 bus 2 em0 at pci1 dev 0 function 0 Intel 82573L rev 0x00: msi, address 00:16:d3:b6:19:57 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1
Re: thinkpad temperature climbs after resume
On 9/24/14, frantisek holop min...@obiit.org wrote: there seems to be a problem with my thinkpad X60s after resume: the cpu temperature keeps going up gradually, no matter that the machine is idle. I've experienced this sometimes for the past couple of months on my Thinkpad T420. As a workaround, $ apm -H $ apm -C after resume seems to cure it. -- David
Video card fan speed temperature
Hello, is it possible to show/change the current fan speed, temperature and clock of my video card? (ATI Radeon HD7770) `sysctl hw` shows sensors of my cpu and north bridge which seem correct. I'm using the 5.5 release. I'm asking because i want to control the fan speed, which is much lower with the proprietary driver for example on linux. Regards
Re: Video card fan speed temperature
On Sat, Jun 21, 2014 at 06:19:51PM +0200, Julian Andrej wrote: Hello, is it possible to show/change the current fan speed, temperature and clock of my video card? (ATI Radeon HD7770) `sysctl hw` shows sensors of my cpu and north bridge which seem correct. I'm using the 5.5 release. I'm asking because i want to control the fan speed, which is much lower with the proprietary driver for example on linux. There is a temperature sensor on some models but it isn't exposed via the sensors framework at the moment. The code has a notion of profiles as mentioned here: http://xorg.freedesktop.org/wiki/RadeonFeature/#index3h2 The choice of profile isn't exposed to userland currently. Newer upstream versions of the radeon code default to dynamic power control managed by the hardware (dpm) which apparently helps reduce noise quite a bit but that will have to wait until we have newer drm code.
Re: Video card fan speed temperature
Do you mind telling me where to find the power profile in the sources? Or is it not possible at the moment even with changing and recompiling the kernel? On 21 June 2014 19:03, Jonathan Gray j...@jsg.id.au wrote: On Sat, Jun 21, 2014 at 06:19:51PM +0200, Julian Andrej wrote: Hello, is it possible to show/change the current fan speed, temperature and clock of my video card? (ATI Radeon HD7770) `sysctl hw` shows sensors of my cpu and north bridge which seem correct. I'm using the 5.5 release. I'm asking because i want to control the fan speed, which is much lower with the proprietary driver for example on linux. There is a temperature sensor on some models but it isn't exposed via the sensors framework at the moment. The code has a notion of profiles as mentioned here: http://xorg.freedesktop.org/wiki/RadeonFeature/#index3h2 The choice of profile isn't exposed to userland currently. Newer upstream versions of the radeon code default to dynamic power control managed by the hardware (dpm) which apparently helps reduce noise quite a bit but that will have to wait until we have newer drm code.
Re: Video card fan speed temperature
You'd have to build a new kernel to modify the profile at the moment. I believe what we have currently is the profile where the clocks are left untouched from what the bios sets them to on boot. In terms of code it is sys/dev/pci/drm/radeon/radeon_pm.c adding something like the the following to the end of radeon_pm_init() might be enough to set a different profile but I've not tested it. rw_enter_write(rdev-pm.rwlock); rdev-pm.profile = PM_PROFILE_LOW; radeon_pm_update_profile(rdev); radeon_pm_set_clocks(rdev); rw_exit_write(rdev-pm.rwlock) On Sat, Jun 21, 2014 at 08:08:33PM +0200, Julian Andrej wrote: Do you mind telling me where to find the power profile in the sources? Or is it not possible at the moment even with changing and recompiling the kernel? On 21 June 2014 19:03, Jonathan Gray j...@jsg.id.au wrote: On Sat, Jun 21, 2014 at 06:19:51PM +0200, Julian Andrej wrote: Hello, is it possible to show/change the current fan speed, temperature and clock of my video card? (ATI Radeon HD7770) `sysctl hw` shows sensors of my cpu and north bridge which seem correct. I'm using the 5.5 release. I'm asking because i want to control the fan speed, which is much lower with the proprietary driver for example on linux. There is a temperature sensor on some models but it isn't exposed via the sensors framework at the moment. The code has a notion of profiles as mentioned here: http://xorg.freedesktop.org/wiki/RadeonFeature/#index3h2 The choice of profile isn't exposed to userland currently. Newer upstream versions of the radeon code default to dynamic power control managed by the hardware (dpm) which apparently helps reduce noise quite a bit but that will have to wait until we have newer drm code.
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
previously on this list Steve Quinn contributed: The acpitz3 shutdown issue remains. I haven't tried the latest patch however I have an nc6220 with the issue but whilst I don't use this laptop daily personally I believe it has never occurred if you remove the battery and power before each boot, we also don't use suspend currently and so I actually encourage users to remove the battery anyway via a message when shutting down. I don't mind testing any patches and let me know if you want me to get the hw.sensors and dmesg from a patched kernel when the bug fires. When the bug is triggered the console says: acpitz2: critical temperature exceeded 3632C, shutting down and sysctl hw.sensors grabbed via rc.local says -662.57 Full dmesg at bottom and diff of a boot with the bug showing and without above it, note the screwed up date on the acpibat0 and stating AC as offline on the boot with the bug present even though the power was plugged in. --- /mnt/usb0/acpi2/hw.sensors Tue Apr 15 22:56:24 2014 +++ /mnt/usb0/acpi3/hw.sensors.bugpresent(nobattremoval)Tue Apr 15 23:06:50 2014 @@ -1,14 +1,14 @@ hw.sensors.acpitz0.temp0=45.00 degC (zone temperature) -hw.sensors.acpitz1.temp0=40.00 degC (zone temperature) -hw.sensors.acpitz2.temp0=23.10 degC (zone temperature) -hw.sensors.acpitz3.temp0=20.00 degC (zone temperature) -hw.sensors.acpibat0.volt0=10.80 VDC (voltage) -hw.sensors.acpibat0.volt1=12.50 VDC (current voltage) -hw.sensors.acpibat0.current0=0.00 A (rate) -hw.sensors.acpibat0.amphour0=3.57 Ah (last full capacity) -hw.sensors.acpibat0.amphour1=0.18 Ah (warning capacity) -hw.sensors.acpibat0.amphour2=0.04 Ah (low capacity) -hw.sensors.acpibat0.amphour3=3.53 Ah (remaining capacity), OK +hw.sensors.acpitz1.temp0=41.00 degC (zone temperature) +hw.sensors.acpitz2.temp0=-662.57 degC (zone temperature) +hw.sensors.acpitz3.temp0=100.00 degC (zone temperature) +hw.sensors.acpibat0.volt0=12.43 VDC (voltage) +hw.sensors.acpibat0.volt1=53.90 VDC (current voltage) +hw.sensors.acpibat0.current0=0.14 A (rate) +hw.sensors.acpibat0.amphour0=62.10 Ah (last full capacity) +hw.sensors.acpibat0.amphour1=3.10 Ah (warning capacity) +hw.sensors.acpibat0.amphour2=0.62 Ah (low capacity) +hw.sensors.acpibat0.amphour3=52.37 Ah (remaining capacity), OK hw.sensors.acpibat0.raw0=0 (battery idle), OK -hw.sensors.acpiac0.indicator0=On (power supply) +hw.sensors.acpiac0.indicator0=Off (power supply) hw.sensors.acpibtn1.indicator0=On (lid open) --- /mnt/usb0/dmesg-nc6220 Tue Apr 15 22:38:34 2014 +++ /mnt/usb0/acpi3/dmesg-bugpresent(nobattremoval) Tue Apr 15 23:06:40 2014 @@ -41,9 +41,9 @@ acpitz1 at acpi0: critical temperature is 103 degC acpitz2 at acpi0: critical temperature is 105 degC acpitz3 at acpi0: critical temperature is 110 degC -acpibat0 at acpi0: C177 model Primary serial 01099 2007/10/19 type LIon oem Hewlett-Packard +acpibat0 at acpi0: C177 model Primary serial 19344 2021/12/16 type LIon oem Hewlett-Packard acpibat1 at acpi0: C176 not present -acpiac0 at acpi0: AC unit online +acpiac0 at acpi0: AC unit offline acpibtn0 at acpi0: C1F1 acpibtn1 at acpi0: C1F2 acpivideo0 at acpi0: C05A @@ -120,41 +120,11 @@ pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 +acpitz2: critical temperature exceeded 3632C, shutting down vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on wd0a (616804515c82c3c2.a) swap on wd0b dump on wd0b -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp -umass0 at uhub0 port 3 configuration 1 interface 0 USB 2.0 Flash Disk rev 2.00/1.00 addr 2 -umass0: using SCSI over Bulk-Only -scsibus4 at umass0: 2 targets, initiator 0 -sd0 at scsibus4 targ 1 lun 0: USB 2.0, Flash Disk, 5.00 SCSI2 0/direct removable serial.020460252400260AF313 -sd0: 1010MB, 512 bytes/sector, 2068480 sectors -acpitz3: TZ4_: failed to read _TMP -acpitz3: TZ4_: failed to read temp +Process (pid 1) got signal 31 +acpitz2: critical temperature exceeded 3632C, shutting down
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
Hi Folks Sorry about the delay. Heartbleed conversations took much time away :-) The acpitz3 shutdown issue remains. It's no big deal because I'm witnessing more OpenBSD awesomeness. I have two dmesg's for those interested Please don't flame me too much for any goof up's. I'm really taking it slow, learning and reading as I go. dmesg-55-amd64-snapshot-fresh 5.5 amd64 PXE booted cd55.iso fetching from /pub/OpenBSD/snapshots/amd64/ dmesg-55-amd64-snapshot-cvscurrent-diff 5.5 amd64 as above, CVS -current last night patched with the diff supplied by Paul Irofti Steve On Sat, Apr 12, 2014 at 11:36 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: On Sat, Apr 12, 2014 at 4:22 AM, Steve Quinn letter2st...@gmail.com wrote: On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: Using -current is easy, just start with latest snapshot from mirror and use snapshot path for packages in PKG_PATH as well. From that time on easy like with regular system. Plus is you have binary upgrades to new snapshot mostly everyday (if you want to) - man sysmerge - checking current.html page IF some manual intervention needed - pkg_add -u . All of that takes like 15 minutes or so, depends on speed of your network and interval how often you will update between snapshots. Generally more stable then some so called stable/lts/whatever distros and you have latest fixes. My gosh Tomas, you are so incredibly helpful thank you. I now have an avenue to supply a laptop to a Dev :-) In parallel though, I'll still be taking this opportunity to learn -current and other shiny new (to me) things You're welcome. You will find it quickly very easy. Especially for desktop/workstation/laptop not much reasons to be on release/stable. I don't say that there are not use cases, but very small amount of those. For BIOS I meant if there's something related to ACPI in fixes from vendor. Oh, right, sorry. I will check Steve [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg-55-amd64-snapshot-fresh] [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg-55-amd64-snapshot-cvscurrent-diff]
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
Steve,
can you test this diff for me and tell me if it fixes anything for you.
I'll also be attending BSDCan to give a talk, see you there!
Index: dsdt.c
===
RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
retrieving revision 1.205
diff -u -p -r1.205 dsdt.c
--- dsdt.c 12 Dec 2013 20:56:01 - 1.205
+++ dsdt.c 12 Apr 2014 10:45:02 -
@@ -736,72 +736,58 @@ static long global_lock_count = 0;
void
acpi_glk_enter(void)
{
- acpi_acquire_glk(acpi_softc-sc_facs-global_lock);
-}
-
-void
-acpi_glk_leave(void)
-{
- int x;
-
- if (acpi_release_glk(acpi_softc-sc_facs-global_lock)) {
- /*
-* If pending, notify the BIOS that the lock was released
-* by the OSPM. No locking is needed because nobody outside
-* the ACPI thread is touching this register.
-*/
- x = acpi_read_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0);
- x |= ACPI_PM1_GBL_RLS;
- acpi_write_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0, x);
- }
-}
-
-void
-aml_lockfield(struct aml_scope *scope, struct aml_value *field)
-{
int st = 0;
- if (AML_FIELD_LOCK(field-v_field.flags) != AML_FIELD_LOCK_ON)
- return;
-
- /* If lock is already ours, just continue */
+ /* If lock is already ours, just continue. */
if (global_lock_count++)
return;
- /* Spin to acquire lock */
+ /* Spin to acquire the lock. */
while (!st) {
st = acpi_acquire_glk(acpi_softc-sc_facs-global_lock);
/* XXX - yield/delay? */
}
-
- return;
}
void
-aml_unlockfield(struct aml_scope *scope, struct aml_value *field)
+acpi_glk_leave(void)
{
- int st, x, s;
+ int st, x;
- if (AML_FIELD_LOCK(field-v_field.flags) != AML_FIELD_LOCK_ON)
- return;
-
- /* If we are the last ones, turn out the lights */
+ /* If we are the last one, turn out the lights. */
if (--global_lock_count)
return;
- /* Release lock */
st = acpi_release_glk(acpi_softc-sc_facs-global_lock);
if (!st)
return;
- /* Signal others if someone waiting */
- s = spltty();
+ /*
+* If pending, notify the BIOS that the lock was released by
+* OSPM. No locking is needed because nobody outside the ACPI
+* thread is supposed to touch this register.
+*/
x = acpi_read_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0);
x |= ACPI_PM1_GBL_RLS;
acpi_write_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0, x);
- splx(s);
+}
+
+void
+aml_lockfield(struct aml_scope *scope, struct aml_value *field)
+{
+ if (AML_FIELD_LOCK(field-v_field.flags) != AML_FIELD_LOCK_ON)
+ return;
+
+ acpi_glk_enter();
+}
+
+void
+aml_unlockfield(struct aml_scope *scope, struct aml_value *field)
+{
+ if (AML_FIELD_LOCK(field-v_field.flags) != AML_FIELD_LOCK_ON)
+ return;
- return;
+ acpi_glk_leave();
}
/*
Index: acpiec.c
===
RCS file: /cvs/src/sys/dev/acpi/acpiec.c,v
retrieving revision 1.48
diff -u -p -r1.48 acpiec.c
--- acpiec.c2 Jul 2013 18:37:47 - 1.48
+++ acpiec.c12 Apr 2014 10:45:03 -
@@ -34,6 +34,7 @@
intacpiec_match(struct device *, void *, void *);
void acpiec_attach(struct device *, struct device *, void *);
+intacpiec_activate(struct device *, int);
u_int8_t acpiec_status(struct acpiec_softc *);
u_int8_t acpiec_read_data(struct acpiec_softc *);
@@ -54,6 +55,7 @@ int acpiec_getregister(const u_int8_t *
void acpiec_wait(struct acpiec_softc *, u_int8_t, u_int8_t);
void acpiec_sci_event(struct acpiec_softc *);
+void acpiec_clear_events(struct acpiec_softc *);
void acpiec_get_events(struct acpiec_softc *);
@@ -82,7 +84,8 @@ void acpiec_unlock(struct acpiec_softc
intacpiec_reg(struct acpiec_softc *);
struct cfattach acpiec_ca = {
- sizeof(struct acpiec_softc), acpiec_match, acpiec_attach
+ sizeof(struct acpiec_softc), acpiec_match, acpiec_attach,
+ NULL, acpiec_activate
};
struct cfdriver acpiec_cd = {
@@ -296,6 +299,8 @@ acpiec_attach(struct device *parent, str
acpi_set_gpehandler(sc-sc_acpi, sc-sc_gpe, acpiec_gpehandler,
sc, 1);
#endif
+
+ acpiec_clear_events(sc);
if (aml_evalname(sc-sc_acpi, sc-sc_devnode, _GLK, 0, NULL, res))
sc-sc_glk = 0;
@@ -307,6 +312,20 @@ acpiec_attach(struct device *parent, str
printf(\n);
}
+int
+acpiec_activate(struct device *self, int act)
+{
+ struct acpiec_softc *sc = (struct acpiec_softc *)self;
+
+
+ switch (act) {
+ case DVACT_RESUME:
+
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Sat, Apr 12, 2014 at 9:04 AM, Paul Irofti p...@irofti.net wrote: can you test this diff for me and tell me if it fixes anything for you. Cool, yes, thank you I'll also be attending BSDCan to give a talk, see you there! Sweet, D-Link DSR, interesting. 3 Scheduled Talk Tracks and only 1 me. I need to clone myself. Steve
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Sat, Apr 12, 2014 at 4:22 AM, Steve Quinn letter2st...@gmail.com wrote: On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: Using -current is easy, just start with latest snapshot from mirror and use snapshot path for packages in PKG_PATH as well. From that time on easy like with regular system. Plus is you have binary upgrades to new snapshot mostly everyday (if you want to) - man sysmerge - checking current.html page IF some manual intervention needed - pkg_add -u . All of that takes like 15 minutes or so, depends on speed of your network and interval how often you will update between snapshots. Generally more stable then some so called stable/lts/whatever distros and you have latest fixes. My gosh Tomas, you are so incredibly helpful thank you. I now have an avenue to supply a laptop to a Dev :-) In parallel though, I'll still be taking this opportunity to learn -current and other shiny new (to me) things You're welcome. You will find it quickly very easy. Especially for desktop/workstation/laptop not much reasons to be on release/stable. I don't say that there are not use cases, but very small amount of those. For BIOS I meant if there's something related to ACPI in fixes from vendor. Oh, right, sorry. I will check Steve
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: Using -current is easy, just start with latest snapshot from mirror and use snapshot path for packages in PKG_PATH as well. From that time on easy like with regular system. Plus is you have binary upgrades to new snapshot mostly everyday (if you want to) - man sysmerge - checking current.html page IF some manual intervention needed - pkg_add -u . All of that takes like 15 minutes or so, depends on speed of your network and interval how often you will update between snapshots. Generally more stable then some so called stable/lts/whatever distros and you have latest fixes. My gosh Tomas, you are so incredibly helpful thank you. I now have an avenue to supply a laptop to a Dev :-) In parallel though, I'll still be taking this opportunity to learn -current and other shiny new (to me) things For BIOS I meant if there's something related to ACPI in fixes from vendor. Oh, right, sorry. I will check Steve
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
Hi, Steve Quinn wrote: I have been recently playing with OpenBSD. I am very impressed with the whole experience, great job people !! I am using an HP nc6320 Laptop. Quite often, I get an error similar to this with amd64 5.4 and 5.5 acpitz3: critical temperature exceeded 3786C, shutting down If that temperature were to be correct, your Silicon would be liquid or possibly even gaseous :) I had a nc6120 and there was an ACPI bug very similar to this, solved with 5.3, if I remember correctly. Sadly, my hardware broke, so I cannot verify if it surfaced again. Riccardo
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Thu, Apr 10, 2014 at 12:37 AM, Steve Quinn letter2st...@gmail.comwrote: Hi folks I have been recently playing with OpenBSD. I am very impressed with the whole experience, great job people !! Just one side note. Most (or all?) major operating systems are using implementation of ACPI from Intel, but OpenBSD has own implementation http://www.openbsd.org/cgi-bin/man.cgi?query=acpisektion=4apropos=0manpath=OpenBSD+Currentarch=i386, which may be sometimes problematic, but generally fixes are available very quickly compared to that general implementation. I am using an HP nc6320 Laptop. Quite often, I get an error similar to this with amd64 5.4 and 5.5 acpitz3: critical temperature exceeded 3786C, shutting down For me it was a nice error to get, because it introduced me to the coolness of using boot -c and config -e I have no problems working around the issue. I did some digging and see others with the same issue on similar hardware http://comments.gmane.org/gmane.os.openbsd.misc/176044 http://comments.gmane.org/gmane.os.openbsd.misc/205033 I'd like to offer the use of my HP nc6320 if a Developer would like to play directly with the hardware to assist others in the community with the issue. I'll be at BSDCan 2014 and can bring it along. Otherwise, please let me know if/how I can be of any help. Good quick start is to send dmesg output from latest -current (both i386 and amd64 IF there's some difference) and something which you probably already checked ; BIOS versions Take care Steve Quinn
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Thu, Apr 10, 2014 at 3:53 AM, Riccardo Mottola riccardo.mott...@libero.it wrote: If that temperature were to be correct, your Silicon would be liquid or possibly even gaseous :) :-) I noticed it would even boil a Titanium case ! http://www.chemicalelements.com/elements/ti.html I had a nc6120 and there was an ACPI bug very similar to this, solved with 5.3, if I remember correctly. Interesting, I'll try that out if necessary Sadly, my hardware broke, so I cannot verify if it surfaced again. Bummer. Thanks for sharing your experience with the issue Steve Quinn
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
I had the same issue a couple of weeks ago with my Sager laptop. An update to a newer snapshot seemed to solve it. Sorry, I can't really offer any advice as the issue seemed to resolve on its own after the update and hasn't surfaced on any snapshots since then. Mike On Apr 9, 2014 4:37 PM, Steve Quinn letter2st...@gmail.com wrote: Hi folks I have been recently playing with OpenBSD. I am very impressed with the whole experience, great job people !! I am using an HP nc6320 Laptop. Quite often, I get an error similar to this with amd64 5.4 and 5.5 acpitz3: critical temperature exceeded 3786C, shutting down For me it was a nice error to get, because it introduced me to the coolness of using boot -c and config -e I have no problems working around the issue. I did some digging and see others with the same issue on similar hardware http://comments.gmane.org/gmane.os.openbsd.misc/176044 http://comments.gmane.org/gmane.os.openbsd.misc/205033 I'd like to offer the use of my HP nc6320 if a Developer would like to play directly with the hardware to assist others in the community with the issue. I'll be at BSDCan 2014 and can bring it along. Otherwise, please let me know if/how I can be of any help. Take care Steve Quinn
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
I had the same issue a couple of weeks ago with my Sager laptop. An update to a newer snapshot seemed to solve it. From time to time we have to explain this one. There is unknown and not yet understood bug, which we think is related to acpi EC handling. It seems to affect HP laptops more than others. It's been there since the beginning, so that would be 5+ years. There have been numerous efforts to fix it. For some reason it wanders around a bit. We've never actually managed to get one of the affected laptops into the hands of a serious developer who would hunt it down.
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Thu, Apr 10, 2014 at 7:31 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: Just one side note. Most (or all?) major operating systems are using implementation of ACPI from Intel, but OpenBSD has own implementation http://www.openbsd.org/cgi-bin/man.cgi?query=acpisektion=4apropos=0manpath=OpenBSD+Currentarch=i386 , which may be sometimes problematic, but generally fixes are available very quickly compared to that general implementation. Wow, thanks for the great reference Good quick start is to send dmesg output from latest -current (both i386 and amd64 IF there's some difference) and something which you probably already checked ; BIOS versions Ok. Sounds great, thank you. I've yet to install -current and want to do it properly so it will be a few days until I have a dmesg to share Regarding the BIOS version, I will triple check but I'm usually quite anal about these things :-) Steve
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Thu, Apr 10, 2014 at 9:16 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: I had the same issue a couple of weeks ago with my Sager laptop. An update to a newer snapshot seemed to solve it. From time to time we have to explain this one. There is unknown and not yet understood bug, which we think is related to acpi EC handling. It seems to affect HP laptops more than others. It's been there since the beginning, so that would be 5+ years. There have been numerous efforts to fix it. For some reason it wanders around a bit. We've never actually managed to get one of the affected laptops into the hands of a serious developer who would hunt it down. Hi Theo I'd like to help in any way I can and hopefully get this bug squashed for good I have access to several of these HP models and can test locally, provide remote access or ship one if required Again, I'm from the Toronto area and am hitting my first BSDCan in May if that helps. Take care Steve Quinn
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
I have access to several of these HP models and can test locally, provide remote access or ship one if required Again, I'm from the Toronto area and am hitting my first BSDCan in May if that helps. A very helpful approach would be: 1. Find a few cheap machines that are 100% confirmed to have this issue repeatable. 2. Flood the ACPI subsystem developer community with them, by ninja action where you suddenly handcuff it to them at some conference, other evento, or even a pub. But please, I am exempt from this.
Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop
On Fri, Apr 11, 2014 at 3:18 AM, Steve Quinn letter2st...@gmail.com wrote: On Thu, Apr 10, 2014 at 7:31 AM, Tomas Bodzar tomas.bod...@gmail.com wrote: Just one side note. Most (or all?) major operating systems are using implementation of ACPI from Intel, but OpenBSD has own implementation http://www.openbsd.org/cgi-bin/man.cgi?query=acpisektion=4apropos=0manpath=OpenBSD+Currentarch=i386 , which may be sometimes problematic, but generally fixes are available very quickly compared to that general implementation. Wow, thanks for the great reference One correction I did not have single issue with ACPI over the years on Dell or Lenovo HW with OpenBSD, but had number of those with other BSDs, OpenSolaris or Linux with their Intel implementation. Especially cheaper consumer models from HP, Toshiba, Sony and similar has very interesting workarounds implemented to get it working at least somewhat even on Windows and Linux so these are often very funny :-) Good quick start is to send dmesg output from latest -current (both i386 and amd64 IF there's some difference) and something which you probably already checked ; BIOS versions Ok. Sounds great, thank you. I've yet to install -current and want to do it properly so it will be a few days until I have a dmesg to share Regarding the BIOS version, I will triple check but I'm usually quite anal about these things :-) Using -current is easy, just start with latest snapshot from mirror and use snapshot path for packages in PKG_PATH as well. From that time on easy like with regular system. Plus is you have binary upgrades to new snapshot mostly everyday (if you want to) - man sysmerge - checking current.html page IF some manual intervention needed - pkg_add -u . All of that takes like 15 minutes or so, depends on speed of your network and interval how often you will update between snapshots. Generally more stable then some so called stable/lts/whatever distros and you have latest fixes. For BIOS I meant if there's something related to ACPI in fixes from vendor. Steve
acpitz3: critical temperature exceeded with HP nc6320 Laptop
Hi folks I have been recently playing with OpenBSD. I am very impressed with the whole experience, great job people !! I am using an HP nc6320 Laptop. Quite often, I get an error similar to this with amd64 5.4 and 5.5 acpitz3: critical temperature exceeded 3786C, shutting down For me it was a nice error to get, because it introduced me to the coolness of using boot -c and config -e I have no problems working around the issue. I did some digging and see others with the same issue on similar hardware http://comments.gmane.org/gmane.os.openbsd.misc/176044 http://comments.gmane.org/gmane.os.openbsd.misc/205033 I'd like to offer the use of my HP nc6320 if a Developer would like to play directly with the hardware to assist others in the community with the issue. I'll be at BSDCan 2014 and can bring it along. Otherwise, please let me know if/how I can be of any help. Take care Steve Quinn
HIgh temperature Asus k52F
Hello, I got an Asus K52F recently. I repair it, because the keyboard and battery were dead. I also cleaned the dust and reapplied thermal grease. On the dark side, on Linux, the temperature is at 45c at idle, on load at 55c. On OpenBSD is near 64c idle and on load up to 85c. With the acpi everything is working: brightness, volume, suspend, hotkeys. These are idle temps # sysctl hw.sensors hw.sensors.cpu0.temp0=65.00 degC hw.sensors.cpu1.temp0=65.00 degC hw.sensors.cpu2.temp0=65.00 degC hw.sensors.cpu3.temp0=65.00 degC hw.sensors.acpitz0.temp0=57.00 degC (zone temperature) hw.sensors.acpiac0.indicator0=Off (power supply) hw.sensors.acpibat0.volt0=10.80 VDC (voltage) hw.sensors.acpibat0.volt1=10.65 VDC (current voltage) hw.sensors.acpibat0.power0=25.95 W (rate) hw.sensors.acpibat0.watthour0=48.39 Wh (last full capacity) hw.sensors.acpibat0.watthour1=4.84 Wh (warning capacity) hw.sensors.acpibat0.watthour2=0.48 Wh (low capacity) hw.sensors.acpibat0.watthour3=23.33 Wh (remaining capacity), OK hw.sensors.acpibat0.raw0=1 (battery discharging), OK hw.sensors.acpibtn0.indicator0=On (lid open) hw.sensors.itherm0.temp1=54.05 degC (Core 1) hw.sensors.itherm0.temp4=57.00 degC (CPU/GPU Max temp) hw.sensors.itherm0.temp9=57.00 degC (GPU/Memory controller abs.) hw.sensors.itherm0.temp10=59.00 degC (PCH abs.) hw.sensors.itherm0.power0=5.00 W (CPU power consumption) # apm Battery state: low, 47% remaining, 52 minutes life estimate A/C adapter state: not connected Performance adjustment mode: manual (933 MHz) # sysctl hw.setperf hw.setperf=0 # dmesg OpenBSD 5.4-current (GENERIC.MP) #59: Tue Sep 17 08:43:41 MDT 2013 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3050057728 (2908MB) avail mem = 2960818176 (2823MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xec3d0 (77 entries) bios0: vendor American Megatrends Inc. version K52F.218 date 07/12/2011 bios0: ASUSTeK Computer Inc. K52F acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC DBGP ECDT SLIC MCFG HPET SSDT acpi0: wakeup devices PEG4(S4) PEG5(S4) PEG6(S4) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) HDEF(S4) RP01(S4) RP02(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2394.35 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 4 (application processor) cpu1: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2393.99 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 2, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2393.99 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 5 (application processor) cpu3: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2393.99 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 2, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG1) acpiprt2 at acpi0: bus -1 (PEG3) acpiprt3 at acpi0: bus -1 (PEG5) acpiprt4 at acpi0: bus 5 (P0P1) acpiprt5 at acpi0: bus 1 (RP01) acpiprt6 at acpi0: bus 2 (RP02) acpiprt7 at acpi0: bus -1 (RP04) acpiprt8 at acpi0: bus -1 (RP05) acpiprt9 at acpi0: bus 4 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiprt12 at acpi0: bus 3 (RP03) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpitz0 at acpi0: critical temperature is 93 degC acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT0 model K52F-44 serial type LIon oem ASUSTek acpiasus at acpi0 not configured acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2399, 2266, 2133, 1999
Re: USB temperature sensors
On 2013-06-19, rafaello konfekte peleekaiskardina...@gmail.com wrote: Hello, Thanks Barry, this was exactly what I was looking for. Been using it now for a couple of days with TEMPer sensor on both 5.3 stable and current by using this patch written by SASANO Takayoshi: http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130331/20130331.diff Any ideas when this could go into source tree? http://marc.info/?l=openbsd-techm=136472023131435w=2 http://marc.info/?l=openbsd-techm=136762807930749w=2 There is a newer version here, http://www.uaa.org.uk/gomitext/2013/20130513/20130513.diff mpi found a few more issues to fix, I have an additional diff to go over the top of the above which fixes some but not all of these: http://junkpile.org/ugold-20130513-patches.diff Though even with the issues it is still more reliable than uthum.
Re: USB temperature sensors
Hello, Thanks Barry, this was exactly what I was looking for. Been using it now for a couple of days with TEMPer sensor on both 5.3 stable and current by using this patch written by SASANO Takayoshi: http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130331/20130331.diff Any ideas when this could go into source tree? http://marc.info/?l=openbsd-techm=136472023131435w=2 http://marc.info/?l=openbsd-techm=136762807930749w=2
Re: USB temperature sensors
On 2013-05-10, Christian Weisgerber na...@mips.inka.de wrote: Stuart Henderson s...@spacehopper.org wrote: TemperNTC (http://www.pcsensor.com/index.php?_a=productproduct_id=7) uses uthum(4) but has a problem where the sensor drops out occasionally; diff I posted to tech@ improves (but doesn't totally fix) this. This seems specific to TemperNTC, I don't have any other uthum(4) devices myself but it seems e.g. TemperHUM is more reliable. My TEMPerHUM also drops out occasionally. As far as the readings are concerned, the temperature it reports is consistently some 1.5 .. 2.0 degC higher than what an alcohol thermometer in the same room shows, i.e., the measurements are reproducible if somewhat miscalibrated. I doubt that the humidity readings are any good, but I haven't checked. I've just got a ugold to play with locally (rather than my other one which is in a remote server room), all three of these are in pretty much the same location next to my laptop: hw.sensors.ugold1.temp0=22.75 degC (inner) hw.sensors.uthum1.temp0=19.00 degC (inner) hw.sensors.uthum1.temp1=22.99 degC (outer/ntc) I don't have an alcohol/Hg thermometer to compare with though. Maybe I'll try the NTC in a cup of iced water to see how that looks (the ugold and uthum's inner sensors are somewhat harder to check in that way :)
Re: USB temperature sensors
Stuart Henderson s...@spacehopper.org wrote: TemperNTC (http://www.pcsensor.com/index.php?_a=productproduct_id=7) uses uthum(4) but has a problem where the sensor drops out occasionally; diff I posted to tech@ improves (but doesn't totally fix) this. This seems specific to TemperNTC, I don't have any other uthum(4) devices myself but it seems e.g. TemperHUM is more reliable. My TEMPerHUM also drops out occasionally. As far as the readings are concerned, the temperature it reports is consistently some 1.5 .. 2.0 degC higher than what an alcohol thermometer in the same room shows, i.e., the measurements are reproducible if somewhat miscalibrated. I doubt that the humidity readings are any good, but I haven't checked. -- Christian naddy Weisgerber na...@mips.inka.de
USB temperature sensors
Hello, Could you share your experience with USB temperature sensors? I'm looking for something cheap for my server room. Only one temperature sensor would be fine, but internal + external temperature sensor and maybe even humidity sensor would be even better. I'm looking for something that is supported by OpenBSD sensors framework as that would be most convenient. Thanks!
Re: USB temperature sensors
I never tryed on OpenBSD but mFi from Ubnt is cheap and the software is compatible with Unix. Michel *De: *rafaello konfekte *Envoyé: *jeudi 9 mai 2013 07 h 30 min 18 s EDT *À: *misc@openbsd.org *Répondre à: *rafaello konfekte *Objet: *USB temperature sensors Hello, Could you share your experience with USB temperature sensors? I'm looking for something cheap for my server room. Only one temperature sensor would be fine, but internal + external temperature sensor and maybe even humidity sensor would be even better. I'm looking for something that is supported by OpenBSD sensors framework as that would be most convenient. Thanks!
Re: USB temperature sensors
On Thu, May 9, 2013 at 4:19 AM, rafaello konfekte peleekaiskardina...@gmail.com wrote: Hello, Could you share your experience with USB temperature sensors? I'm looking for something cheap for my server room. Only one temperature sensor would be fine, but internal + external temperature sensor and maybe even humidity sensor would be even better. I'm looking for something that is supported by OpenBSD sensors framework as that would be most convenient. Thanks! man 4 onewire
Re: USB temperature sensors
If you're willing/able to test some new code, you may be interested in two recent threads on tech@ http://marc.info/?l=openbsd-techm=136472023131435w=2 http://marc.info/?l=openbsd-techm=136762807930749w=2 On Thu, May 9, 2013 at 4:19 AM, rafaello konfekte peleekaiskardina...@gmail.com wrote: Hello, Could you share your experience with USB temperature sensors? I'm looking for something cheap for my server room. Only one temperature sensor would be fine, but internal + external temperature sensor and maybe even humidity sensor would be even better. I'm looking for something that is supported by OpenBSD sensors framework as that would be most convenient. Thanks!
Re: USB temperature sensors
On 2013-05-09, rafaello konfekte peleekaiskardina...@gmail.com wrote: Hello, Could you share your experience with USB temperature sensors? I'm looking for something cheap for my server room. Only one temperature sensor would be fine, but internal + external temperature sensor and maybe even humidity sensor would be even better. I'm looking for something that is supported by OpenBSD sensors framework as that would be most convenient. Thanks! man -k sensor will show you various options. man -k sensor | grep ^u for the directly USB-connected ones. The Toradex uoak* ones are now an open hardware design and Toradex no longer produce them themselves. 1-Wire sensors can also be connected to USB via uow(4), these may be a better bet if you want a larger number of sensors. At the moment most of the ebay vendors that I'm seeing have either ugold(4) or the TemperNTC version of uthum(4) devices. TemperNTC (http://www.pcsensor.com/index.php?_a=productproduct_id=7) uses uthum(4) but has a problem where the sensor drops out occasionally; diff I posted to tech@ improves (but doesn't totally fix) this. This seems specific to TemperNTC, I don't have any other uthum(4) devices myself but it seems e.g. TemperHUM is more reliable. ugold(4) has not been committed yet, see recent tech@ posts. (http://www.pcsensor.com/index.php?_a=productproduct_id=41) There are some possible races in the driver though in practice it seems to work well (better than the above TemperNTC). If you have something running, there are various ways to get graphs etc (snmpd in base exports sensor data; symon is another option), or for simple alerting you can just run sensorsd - I have it log to a separate file in syslog.conf: !sensorsd *.* /var/log/sensors and tell newsyslog to rotate the file without log turned over markers, and to send alerts: /var/log/sensors644 7 *168 ZMB root and uncomment the send log file notifications in root's crontab.
Re: ACPI hack for temperature control
2013/5/2 STeve Andre' and...@msu.edu Can someone point me to the proper patch for ACPI so I don't reboot any more? Thanks. Do you mean disabling acpitz(4) when it does the Wrong Thing, or ThinkPad-specific patch I was posting some time ago (and still want to incorporate but after 64-bit time_t)? -- WBR, Vadim Zhukov
Re: ACPI hack for temperature control
On 05/02/13 02:40, Vadim Zhukov wrote: 2013/5/2 STeve Andre' and...@msu.edu mailto:and...@msu.edu Can someone point me to the proper patch for ACPI so I don't reboot any more? Thanks. Do you mean disabling acpitz(4) when it does the Wrong Thing, or ThinkPad-specific patch I was posting some time ago (and still want to incorporate but after 64-bit time_t)? -- WBR, Vadim Zhukov Sorry -- I mean the acpitz(4) hack to let my W500 get past 79C without rebooting. Time_t I can wait for. ;-) Thanks, STeve Andre'
ACPI hack for temperature control
Can someone point me to the proper patch for ACPI so I don't reboot any more? Thanks. --STeve Andre'
Re: Absurdly high temperature reading - system shutdown
HP 8530w OpenBSD 5.1 AMD64 GENERIC MP
Got this message almost every time I boot:
acpitz2: critical temperature exceeded 5424C (56976K), shutting down
Applied the patch mentioned here and the message disappeared:
http://old.nabble.com/acpiec-madness-%28HP-laptop-people-pay-attention-to-thi
s-one%29-to29872059.html#a29872059
dmesg after applying patch attached
- Original meddelelse -
Fra: Theo de Raadt dera...@cvs.openbsd.org
Til: pablo caballero pdcv...@gmail.com
Cc: misc@openbsd.org
Dato: Fre, 17. jun 2011 06:15
Emne: Re: Absurdly high temperature reading - system shutdown
On Thu, Jun 16, 2011 at 3:33 PM, Michal Mazurek
akf...@jasminek.net wrote:
After moving my old laptop around I got home, booted it and got a
very
distressing message:
messages.2.gz:Jun 14 22:40:09 hopek /bsd: acpitz2: Critical
temperature
4938C (52112K), shutting down
Perhaps some dust moved around, or a cable disconnected.
Unfortunately, the system shut down before it booted. I booted
bsd.rd,
read some manpages and booted with -c 'disable acpitz' -
everything
worked fine. I attach a diff to only shutdown if the temperature
is
below 2000C. If it's above then it's too late to shut down anyway
:)
BTW, for no apparent reason my laptop started working fine again.
Index: acpitz.c
===
RCS file: /cvs/src/sys/dev/acpi/acpitz.c,v
retrieving revision 1.43
diff -u -r1.43 acpitz.c
--- acpitz.c 15 Jun 2011 00:15:54 - 1.43
+++ acpitz.c 16 Jun 2011 15:09:14 -
@@ -326,11 +326,17 @@
}
/* critical trip points */
if (sc-sc_crt != -1 sc-sc_crt = sc-sc_tmp) {
- /* do critical shutdown */
- printf(%s: critical temperature exceeded %dC (%dK),
shutting
- down\n,
- DEVNAME(sc), KTOC(sc-sc_tmp), sc-sc_tmp);
- psignal(initproc, SIGUSR2);
+ if (KTOC(sc-sc_tmp) 2000) {
+ printf(%s: absurdly high temperature %dC (%dK),
+ doing nothing\n,
+ DEVNAME(sc), KTOC(sc-sc_tmp), sc-sc_tmp);
+ } else {
+ /* do critical shutdown */
+ printf(%s: critical temperature exceeded %dC (%dK),
+ shutting down\n,
+ DEVNAME(sc), KTOC(sc-sc_tmp), sc-sc_tmp);
+ psignal(initproc, SIGUSR2);
+ }
}
if (sc-sc_hot != -1 sc-sc_hot = sc-sc_tmp) {
printf(%s: _HOT temperature\n, DEVNAME(sc));
--
Michal Mazurek
I had noticed the following behaviour (maybe related or maybe not)
in my
laptop:
- When the batt goes low the system shutdown with the same message.
The temp is always (not 100% sure) 110C. This is 100% reproducible
(every time batt goes low -- system shutdown).
I was trying to figure myself what is happening to introduce myself
to
kernel code but if someone want to test something I'll glad to
help.
This diff you are writing is a workaround. It is not fixing the bug.
Somewhere higher, some acpi, aml, bios, or EC behaviour has provided
bad data, which has propogated up to the acpitz driver.
We will kind of needs these workarounds until the real bugs are
found,
though, perhaps...
OpenBSD 5.1 (GENERIC.MP) #4: Mon Aug 13 01:48:12 CEST 2012
r...@foo.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
bfclock_battery,config_unit,memory_size,fixed_disk,invalid_time
real mem = 8484552704 (8091MB)
avail mem = 8244531200 (7862MB)
User Kernel Config
UKC timezone /120\^H \^H\^H \^H\^H \^H\^H \^H-120
timezone = -120, dst = 0
UKC exit
Continuing...
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xbdec4000 (22 entries)
bios0: vendor Hewlett-Packard version 68PDV Ver. F.12 date 06/08/2010
bios0: Hewlett-Packard HP EliteBook 8530w
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG TCPA SSDT SLIC SSDT DMAR ASF! SSDT SSDT
SSDT
acpi0: wakeup devices LANC(S5) HDEF(S4) RP02(S5) WNIC(S5) RP03(S5) ECF0(S5)
RP05(S5) ECF0(S5) RP06(S5) NIC_(S5) USB1(S3) USB2(S3) USB3(S3) USB4(S3)
USB5(S3) USB6(S3) U6RM(S3) EHC1(S3) EHC2(S3) PCIB(S5) HST1(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.42 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF
cpu0: 6MB 64b/line 16-way L2 cache
cpu0: apic clock running at 266MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF
cpu1: 6MB 64b/line 16-way L2 cache
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0
Re: Absurdly high temperature reading - system shutdown
* ba...@mail.dk ba...@mail.dk [120814 19:50]: HP 8530w OpenBSD 5.1 AMD64 GENERIC MP Got this message almost every time I boot: acpitz2: critical temperature exceeded 5424C (56976K), shutting down Applied the patch mentioned here and the message disappeared: http://old.nabble.com/acpiec-madness-%28HP-laptop-people-pay-attention-to-thi s-one%29-to29872059.html#a29872059 Wow. This patch does wonders. With it applied my HP 6910 boots with keyboard and touchpad working four times out of five, and suspend works.
Re: acpitz critical temperature is too high
Another idea I forgot to mention is to use syslog, and pipe to scripts. This would pretty much solve any issues with temperature and battery monitoring... run every syslog of sensorsd and apmd through a script, and forget using sensorsd for event commands.
Re: acpitz critical temperature is too high
On Mon, Jun 18, 2012 at 05:54:31PM -0700, Robert Connolly wrote: I want to initiate a shutdown if the temperature gets too high. I have been This already happens if the temperature gets too high. See recent threads on misc@ about this. using sensorsd(8), but sensorsd(8) only reacts once to the high (or low) event, leaving it up to the program/script to run timers to keep checking if the temperature gets worse. For my satisfaction, the timers would have to keep running until the system cooled down below the high temperature, so that sensorsd(8) will pick up the monitoring from there. When the temperature gets to a warning level, I would like sensorsd(8) to notify logged in users (me), mail root, step down the CPU with apm -L, and then let the kernel do a shutdown, with acpitz(4), if the temperature continues to rise to critical. This would be easier and more simple for me than using sensorsd(8) alone (no timers). You want to continue to run your machine after its reached critical temperature? Critical means just that ... shut down I checked this out a little bit today. Some laptop manufacturers release Windows programs to control these temperature settings. I don't know if the setting is permanent/saved in BIOS, but if it is then I could run it from a Windows Livecd to reset the critical temperature. Another idea was installing Coreboot (free-bios), but I doubt my mainboard is supported, and it could brick my system. Or, configure the OpenBSD kernel to ignore the BIOS setting, and use my hard coded temperature instead. Or, use sensorsd(8) and a script. Good luck with this. On Mon, Jun 18, 2012 at 9:35 AM, Mike Larkin mlar...@azathoth.net wrote: On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: acpitz critical temperature is too high
I think one problem with using syslog triggers is opening op the risk for DOS attack if someuser or some internet connection into a service finds a way to trick syslog to print strings, to.. shutdown a server. On Mon, Jun 18, 2012 at 11:36:46PM -0700, Robert Connolly wrote: Another idea I forgot to mention is to use syslog, and pipe to scripts. This would pretty much solve any issues with temperature and battery monitoring... run every syslog of sensorsd and apmd through a script, and forget using sensorsd for event commands.
Re: acpitz critical temperature is too high
2012/6/19 Robert Connolly robertconnolly1...@gmail.com sensorsd(8)'s low goes in the other direction. If I set low to 60C, it will go off if the CPU is running at 50C. Sensorsd(8) isn't made for such fine control as some of us would like. If the battery is low, we want the sensor to alert us. If the temperature is low, we do not want to be alerted. So a medium setting simply wouldn't work with the way sensorsd(8) works. Furthermore, I checked out Windows and Acer software, and I don't see a way of resetting the BIOS critical temperature. They use daemons, and so my kernel hack option to take advantage of acpitz(4) looks like a good idea. On Mon, Jun 18, 2012 at 8:05 PM, Artturi Alm artturi@gmail.comwrote: How about setting low to the warning level, and high to the shutdown level? That way you should be able to handle all 3 states w/o timers. below being normal, within where it notifies and steps down CPU and above where it does shutdown. I don't see the problem with that. Those three states should be enough, given that the 'warning zone' has reasonable limits, where you feel confident that it doesn't hurt running even in the long run. Ie. you've got this in your sensorsd.conf: hw.sensors.cpu0.temp0:low=50C:high=55C:command=/etc/sensorsd/temp %l and /etc/sensorsd/temp looks like this: #!/bin/sh case $1 in below) apm -A ;; within) apm -C echo 'Running HOT' | wall ;; above) shutdown -h now ;; esac Or did I miss the point?
Re: acpitz critical temperature is too high
It didn't occur to me to set up sensorsd(8) this way, although it makes perfect sense now. This would also work well for battery monitoring. Thank you On Tue, Jun 19, 2012 at 7:11 AM, Artturi Alm artturi@gmail.com wrote: 2012/6/19 Robert Connolly robertconnolly1...@gmail.com sensorsd(8)'s low goes in the other direction. If I set low to 60C, it will go off if the CPU is running at 50C. Sensorsd(8) isn't made for such fine control as some of us would like. If the battery is low, we want the sensor to alert us. If the temperature is low, we do not want to be alerted. So a medium setting simply wouldn't work with the way sensorsd(8) works. Furthermore, I checked out Windows and Acer software, and I don't see a way of resetting the BIOS critical temperature. They use daemons, and so my kernel hack option to take advantage of acpitz(4) looks like a good idea. On Mon, Jun 18, 2012 at 8:05 PM, Artturi Alm artturi@gmail.comwrote: How about setting low to the warning level, and high to the shutdown level? That way you should be able to handle all 3 states w/o timers. below being normal, within where it notifies and steps down CPU and above where it does shutdown. I don't see the problem with that. Those three states should be enough, given that the 'warning zone' has reasonable limits, where you feel confident that it doesn't hurt running even in the long run. Ie. you've got this in your sensorsd.conf: hw.sensors.cpu0.temp0:low=50C:high=55C:command=/etc/sensorsd/temp %l and /etc/sensorsd/temp looks like this: #!/bin/sh case $1 in below) apm -A ;; within) apm -C echo 'Running HOT' | wall ;; above) shutdown -h now ;; esac Or did I miss the point?
Temperature script for sensorsd(8)
Hello. I'm not a proficient shell script writer, so I would like advice and criticism for my sensorsd(8) temperature script. In particular, I would like the above email to root to include helpful information that would help explain why the temperature went to critical. Anything else that I may be missing would be nice to know too, including scripting style. $ cat /etc/sensorsd/temp.sh #!/bin/sh case $1 in below) # Normal operation. apm -A ;; within) # We hit the warning threshold. Step down the CPU. apm -L # Write the warning to syslog, so we know why the CPU was stepped down. logger -t $0 Reached warning temperature. Stepping down CPU. # Tell root. echo Stepping down CPU due to high temperature | mail -s $0 root@`hostname` # Tell users: echo Stepping down CPU due to high temperature | wall ;; above) # Mail message for root, with hopefully helpful information. message= The system was shut down due to excessive temperature. The system hardware may need maintenance. System information: `date` `uptime` `who -u` `sysctl hw.sensors` `sysctl hw.cpuspeed` `sysctl hw.setperf` `ps auxw` # Mail root. echo $message | mail -s $0 root@`hostname` # Halt and power down. shutdown -h -p now Reached critical temperature. Halting system from $0 ;; esac
acpitz critical temperature is too high
Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks
Re: acpitz critical temperature is too high
On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: acpitz critical temperature is too high
I want to initiate a shutdown if the temperature gets too high. I have been using sensorsd(8), but sensorsd(8) only reacts once to the high (or low) event, leaving it up to the program/script to run timers to keep checking if the temperature gets worse. For my satisfaction, the timers would have to keep running until the system cooled down below the high temperature, so that sensorsd(8) will pick up the monitoring from there. When the temperature gets to a warning level, I would like sensorsd(8) to notify logged in users (me), mail root, step down the CPU with apm -L, and then let the kernel do a shutdown, with acpitz(4), if the temperature continues to rise to critical. This would be easier and more simple for me than using sensorsd(8) alone (no timers). I checked this out a little bit today. Some laptop manufacturers release Windows programs to control these temperature settings. I don't know if the setting is permanent/saved in BIOS, but if it is then I could run it from a Windows Livecd to reset the critical temperature. Another idea was installing Coreboot (free-bios), but I doubt my mainboard is supported, and it could brick my system. Or, configure the OpenBSD kernel to ignore the BIOS setting, and use my hard coded temperature instead. Or, use sensorsd(8) and a script. On Mon, Jun 18, 2012 at 9:35 AM, Mike Larkin mlar...@azathoth.net wrote: On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: acpitz critical temperature is too high
How about setting low to the warning level, and high to the shutdown level? That way you should be able to handle all 3 states w/o timers. below being normal, within where it notifies and steps down CPU and above where it does shutdown. 2012/6/19 Robert Connolly robertconnolly1...@gmail.com I want to initiate a shutdown if the temperature gets too high. I have been using sensorsd(8), but sensorsd(8) only reacts once to the high (or low) event, leaving it up to the program/script to run timers to keep checking if the temperature gets worse. For my satisfaction, the timers would have to keep running until the system cooled down below the high temperature, so that sensorsd(8) will pick up the monitoring from there. When the temperature gets to a warning level, I would like sensorsd(8) to notify logged in users (me), mail root, step down the CPU with apm -L, and then let the kernel do a shutdown, with acpitz(4), if the temperature continues to rise to critical. This would be easier and more simple for me than using sensorsd(8) alone (no timers). I checked this out a little bit today. Some laptop manufacturers release Windows programs to control these temperature settings. I don't know if the setting is permanent/saved in BIOS, but if it is then I could run it from a Windows Livecd to reset the critical temperature. Another idea was installing Coreboot (free-bios), but I doubt my mainboard is supported, and it could brick my system. Or, configure the OpenBSD kernel to ignore the BIOS setting, and use my hard coded temperature instead. Or, use sensorsd(8) and a script. On Mon, Jun 18, 2012 at 9:35 AM, Mike Larkin mlar...@azathoth.net wrote: On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: acpitz critical temperature is too high
sensorsd(8)'s low goes in the other direction. If I set low to 60C, it will go off if the CPU is running at 50C. Sensorsd(8) isn't made for such fine control as some of us would like. If the battery is low, we want the sensor to alert us. If the temperature is low, we do not want to be alerted. So a medium setting simply wouldn't work with the way sensorsd(8) works. Furthermore, I checked out Windows and Acer software, and I don't see a way of resetting the BIOS critical temperature. They use daemons, and so my kernel hack option to take advantage of acpitz(4) looks like a good idea. On Mon, Jun 18, 2012 at 8:05 PM, Artturi Alm artturi@gmail.com wrote: How about setting low to the warning level, and high to the shutdown level? That way you should be able to handle all 3 states w/o timers. below being normal, within where it notifies and steps down CPU and above where it does shutdown.
critical temperature exceeded
5.1/current @ HP EliteBook 8530w. Sometimes during boot, acpitz says acpitz2: critical temperature exceeded 5424C (56976K), shutting down and at the end of the booting sequence, Process (pid 1) got signal 31 It seems to happen more often when running on battery. The temperature numbers must somehow be absurdly wrong, unless there really is 5424 degrees. Also, 5424C is not 56976K. Also, it continues to run fine: it does not shut down even though it decided to. The acpidump is available at http://stare.cz/dmesg/hp-elitebook-8530w.tar.gz Is there something I should specifically test? Jan OpenBSD 5.1-current (GENERIC) #230: Mon Jun 11 12:10:30 MDT 2012 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC RTC BIOS diagnostic error bbclock_battery,config_unit,memory_size,fixed_disk cpu0: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,LAHF real mem = 2125709312 (2027MB) avail mem = 2080153600 (1983MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/10/08, SMBIOS rev. 2.4 @ 0x7edbf000 (21 entries) bios0: vendor Hewlett-Packard version 68PDV Ver. F.06 date 12/15/2008 bios0: Hewlett-Packard HP EliteBook 8530w acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG TCPA SSDT SLIC SSDT DMAR ASF! SSDT SSDT SSDT SSDT acpi0: wakeup devices LANC(S5) HDEF(S4) RP02(S5) WNIC(S5) RP03(S5) ECF0(S5) RP05(S5) ECF0(S5) RP06(S5) NIC_(S5) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) U6RM(S3) EHC1(S3) EHC2(S3) PCIB(S5) HST1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 1 (PEGP) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP02) acpiprt3 at acpi0: bus 4 (RP03) acpiprt4 at acpi0: bus 69 (RP05) acpiprt5 at acpi0: bus 134 (PCIB) acpiprt6 at acpi0: bus 0 (PCI0) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: APPR acpipwrres1 at acpi0: COMP acpipwrres2 at acpi0: LPP_ acpipwrres3 at acpi0: PGF0 acpitz0 at acpi0: critical temperature is 115 degC acpitz1 at acpi0: critical temperature is 105 degC acpitz2 at acpi0: critical temperature is 112 degC acpitz3 at acpi0: critical temperature is 112 degC acpitz4 at acpi0: critical temperature is 90 degC acpitz5 at acpi0: critical temperature is 112 degC acpibat0 at acpi0: BAT0 model Primary serial 34704 2002/12/16 type LIon oem Hewlett-Packard acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: LID_ acpivideo0 at acpi0: DGFX acpivout0 at acpivideo0: LCD_ bios0: ROM list: 0xc/0xe200 0xce800/0x1000 0xcf800/0x1000 cpu0: Enhanced SpeedStep 2528 MHz: speeds: 2534, 2533, 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 ppb0 at pci0 dev 1 function 0 Intel GM45 PCIE rev 0x07: apic 1 int 16 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x065c rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel GM45 PT IDER rev 0x07: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) puc0 at pci0 dev 3 function 3 Intel GM45 KT rev 0x07: ports: 1 com com3 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com3: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: msi, address 00:23:7d:e7:ac:60 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 17 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 18 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: msi azalia0: codecs: Analog Devices AD1984A, 0x/0x, using Analog Devices AD1984A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: apic 1 int 16 pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: apic 1 int 17 pci3 at ppb2 bus 3 iwn0 at pci3 dev
Re: critical temperature exceeded
On Fri, Jun 15, 2012 at 7:40 PM, Jan Stary h...@stare.cz wrote: 5.1/current @ HP EliteBook 8530w. Sometimes during boot, acpitz says acpitz2: critical temperature exceeded 5424C (56976K), shutting down and at the end of the booting sequence, Process (pid 1) got signal 31 It seems to happen more often when running on battery. The temperature numbers must somehow be absurdly wrong, unless there really is 5424 degrees. Also, 5424C is not 56976K. Also, it continues to run fine: it does not shut down even though it decided to. The acpidump is available at http://stare.cz/dmesg/hp-elitebook-8530w.tar.gz Is there something I should specifically test? See here http://marc.info/?l=openbsd-miscw=2r=1s=critical+temperature+exceededq=b . Most probably message from Theo and some previous email with patch, but was not working for some people. There's some workaround tested as well - removing battery and running with apmd -C Jan OpenBSD 5.1-current (GENERIC) #230: Mon Jun 11 12:10:30 MDT 2012 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC RTC BIOS diagnostic error bbclock_battery,config_unit,memory_size,fixed_disk cpu0: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,SMX,EST, TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,LAHF real mem = 2125709312 (2027MB) avail mem = 2080153600 (1983MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/10/08, SMBIOS rev. 2.4 @ 0x7edbf000 (21 entries) bios0: vendor Hewlett-Packard version 68PDV Ver. F.06 date 12/15/2008 bios0: Hewlett-Packard HP EliteBook 8530w acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG TCPA SSDT SLIC SSDT DMAR ASF! SSDT SSDT SSDT SSDT acpi0: wakeup devices LANC(S5) HDEF(S4) RP02(S5) WNIC(S5) RP03(S5) ECF0(S5) RP05(S5) ECF0(S5) RP06(S5) NIC_(S5) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) U6RM(S3) EHC1(S3) EHC2(S3) PCIB(S5) HST1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 1 (PEGP) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP02) acpiprt3 at acpi0: bus 4 (RP03) acpiprt4 at acpi0: bus 69 (RP05) acpiprt5 at acpi0: bus 134 (PCIB) acpiprt6 at acpi0: bus 0 (PCI0) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: APPR acpipwrres1 at acpi0: COMP acpipwrres2 at acpi0: LPP_ acpipwrres3 at acpi0: PGF0 acpitz0 at acpi0: critical temperature is 115 degC acpitz1 at acpi0: critical temperature is 105 degC acpitz2 at acpi0: critical temperature is 112 degC acpitz3 at acpi0: critical temperature is 112 degC acpitz4 at acpi0: critical temperature is 90 degC acpitz5 at acpi0: critical temperature is 112 degC acpibat0 at acpi0: BAT0 model Primary serial 34704 2002/12/16 type LIon oem Hewlett-Packard acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: LID_ acpivideo0 at acpi0: DGFX acpivout0 at acpivideo0: LCD_ bios0: ROM list: 0xc/0xe200 0xce800/0x1000 0xcf800/0x1000 cpu0: Enhanced SpeedStep 2528 MHz: speeds: 2534, 2533, 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 ppb0 at pci0 dev 1 function 0 Intel GM45 PCIE rev 0x07: apic 1 int 16 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x065c rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel GM45 PT IDER rev 0x07: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) puc0 at pci0 dev 3 function 3 Intel GM45 KT rev 0x07: ports: 1 com com3 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com3: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: msi, address 00:23:7d:e7:ac:60 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 17 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 18 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0
Re: EeePC, 5.0: acpitz gets wrong temperature
Hi Henri, Le mercredi 2 C 20:48, Henri Kemppainen a C)crit : I just installed a snapshot (dated Oct 19) of -current on a new EeePC 1001PXD. The installation itself went fine. However, on the first boot, even before I can see the login prompt, acpitz decides to shutdown the machine: acpitz0: critical temperature exceeded 255C (5282K), shutting down `dmesg' with this patch is at: http://tar-jx.bz/stuff/dmesg.lapin-5.0-nohaltoncrit From your dmesg: acpiec _REG failed, broken BIOS ASUS has a BIOS update (0702; 2011.04.13) with the this description: Update EC firmware I'd try that. Tell me if it fixes the problem. Thanks for the suggestion. I updated the BIOS. The only relevant difference I see in dmesg is the new version number of the BIOS; I still have the message about a broken BIOS and acpitz finding the temperature too high. For the record: http://tar-jx.bz/stuff/dmesg.lapin-5.0-nohaltoncrit-newbios I've been paying closer attention to the dmesg from Linux and FreeBSD, and indeed, in both cases, I see messages about flaky things in the BIOS. However, both Linux and FreeBSD are able to see the correct temperature. For instanace, under FreeBSD: # sysctl -a ... hw.acpi.thermal.tz0.temperature: 57.0C http://tar-jx.bz/stuff/dmesg.lapin-freebsd9rc1 http://tar-jx.bz/stuff/sysctl-a.lapin-freebsd9rc1 Linux: http://tar-jx.bz/stuff/dmesg.lapin-linux [0.168433] ACPI: EC: EC description table is found, configuring boot EC (I don't know if the EC table was available before the BIOS update; all I know is that Linux was able to get the correct temperature/) [0.249652] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored ... [0.272921] pci:00: Requesting ACPI _OSC control (0x1d) [0.272930] pci:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d Please do tell me if there is more relevant info I can provide. I am far from an expert in ACPI; I have no idea what an EC table is, for instance, and maybe I'm missing something obvious. -- Fred
