On Wed, Jan 21, 2015 at 11:42 PM, trondd <tro...@gmail.com> wrote:
> Check 'sysctl hw.sensors' and see if you have some temp sensors in
> there and what they're telling you.
>
> Tim.

Now that you mention it, yeah, that command does tell the temperature and such.

Right now:

hw.sensors.acpitz0.temp0=38.50 degC (zone temperature)
hw.sensors.lm1.temp0=21.00 degC
hw.sensors.lm1.temp1=38.50 degC
hw.sensors.lm1.fan0=3668 RPM
hw.sensors.lm1.fan1=2596 RPM
hw.sensors.lm1.volt0=1.55 VDC (VCore)
hw.sensors.lm1.volt1=3.31 VDC (+3.3V)
hw.sensors.lm1.volt2=5.03 VDC (+5V)
hw.sensors.lm1.volt3=11.61 VDC (+12V)
hw.sensors.lm1.volt4=-11.87 VDC (-12V)
hw.sensors.lm1.volt5=-4.80 VDC (-5V)
hw.sensors.lm1.volt6=4.87 VDC (5VSB)
hw.sensors.lm1.volt7=3.30 VDC (VBAT)

To my eye, that all looks withing range. I'll have to try replicating
the load and checking the temperature. (I had google mail, a wikipedia
page or two open and some candy-making pages for my wife, but that was
all at the time. All browser stuff. I was thinking less about load and
more about firefox dying and taking the system with it. Firefox 26.0
from the openbsd 5.5 packages. Google even keeps telling me the
browser is no longer supported by them. Need to upgrade to obsd 5.6
this weekend if I can make the time.)

On Wed, Jan 21, 2015 at 11:11 PM, Matt M <cmorrow...@gmail.com> wrote:
> Sudden power offs are often indicative of heat issues, especially on
> laptops. Does it power right back on and stay on for a long time? If not I
> would suspect heat. If it does stay on, it may be a power management bug, a
> bad power source or possibly a failing power supply in the machine.
>  If it won't power back on right away, or won't stay on till it sits for a
> while, try cleaning the cpu fan - they collect a lot of dust.

I think it's getting close to time for spring cleaning with the vacuum
cleaner. Dust is definitely a possibility.

> On Wednesday, January 21, 2015, Joel Rees <joel.r...@gmail.com> wrote:
>>
>> I'm looking under /var/log, but not seeing any logfiles to give me any
>> clues.
>>
>> What information should I post? I have /var/log/messages from the
>> moment of the crash, but it's about 36K.
>>
>> dmesg:
>> ---------------
>> [See prior post in thread.]

-- 
Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.

Reply via email to