Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #2176 > unrolled thread

Did something on my old Debian/Linux stable box crash and mess up my CMOS?

Back to article view | Back to comp.os.linux.hardware

Contents

  Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 11:23 -0800
    Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-10 13:58 -0600
      Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 12:17 -0800
        Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-10 14:37 -0600
          Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 12:54 -0800
            Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-10 15:20 -0600
              Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 14:01 -0800
                Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-10 18:52 -0600
                  Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 17:43 -0800
                    Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-10 19:59 -0600
                      Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-11 01:24 -0800
                        Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? philo  <philo@privacy.net> - 2014-01-11 08:18 -0600
    Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? John Dulak <Johnd@Booogus.com> - 2014-01-10 16:38 -0500
      Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-10 13:59 -0800
        Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? "Rod Speed" <rod.speed.aaa@gmail.com> - 2014-01-11 15:09 +1100
          Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-11 01:21 -0800
        Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Arno <me@privacy.net> - 2014-01-11 12:52 +0000
          Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-11 08:07 -0800
            Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? "Rod Speed" <rod.speed.aaa@gmail.com> - 2014-01-12 05:26 +1100
              Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-11 13:50 -0800
                Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? "Rod Speed" <rod.speed.aaa@gmail.com> - 2014-01-13 05:23 +1100
                  Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-12 10:56 -0800
            Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Arno <me@privacy.net> - 2014-01-13 01:05 +0000
              Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-13 00:50 -0800
    Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Johann Klammer <klammerj@NOSPAM.a1.net> - 2014-01-11 12:01 +0100
      Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS? Ant <ant@zimage.comANT> - 2014-01-11 08:08 -0800

Page 1 of 2  [1] 2  Next page →

#2176 — Did something on my old Debian/Linux stable box crash and mess up my CMOS?

[Multipart message — attachments visible in raw view] — view raw

... I woke up before 6:15 AM PST and noticed my old box wasn't 
responding (e.g., SSH2's text terminal commands not recognizing) 
correctly and its BitchX v1.2 client's clock said 2:xx PM PST when I was 
using it briefly and remotely (PuTTY) late last night before I passed 
out at about 10:32 PM PST. /var/log/'s log files showed the box working 
up to 3:17:01 AM PST from what I can tell.

Anyways, I rebooted and Grub couldn't find blah blah. Then, I noticed it 
was trying to boot up my former old Seagate 80 GB PATA HDD which isn't 
supposed to do (it is just an storage drive). I did a manual boot (F11) 
and saw all of my drives. I booted to my Corsair SSD, and it was fine. I 
rebooted into my CMOS and its boot order seems to be messed up (should 
be booting to Corsair SSD first and all else disabled!). So, I fixed it 
and it worked fine.

What the frak happened? Did my motherboard forget everything and 
resetted? Something else? I assume both of my drives are OK (ran 
smartctrl command's long tests and attached their results for reviews 
just in case)?

Thank you in advance. :)
-- 
"... Hey. Could we do that again? I know we haven't met, but I don't 
want to be an ant. You know? I mean, it's like we go through life with 
our antennae bouncing off one another, continously on ant autopilot, 
with nothing really human required of us. 'Stop.' 'Go.' 'Walk here.' 
'Drive there.' All action basically for survival. All communication 
simply to keep this ant colony buzzing along in an efficient, polite 
manner. 'Here's your change.' 'Paper or plastic?' 'Credit or debit?"' 
'You want ketchup with that' I don't want a straw. I want real human 
moments. I want to see you. I want you to see me. I don't want to give 
that up. I don't want to be ant, you know?" "Yeah... yeah I know. I 
don't want to be an ant either. Thanks for kinda, like, josteling me 
there... I've been kinda on zombie autopilot lately. I don't feel like 
an ant in my head, but I guess I probably look like one..." --Waking 
Life movie
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [next] | [standalone]

#2177

On 01/10/2014 01:23 PM, Ant wrote:
> ... I woke up before 6:15 AM PST and noticed my old box wasn't
> responding (e.g., SSH2's text terminal commands not recognizing)
> correctly and its BitchX v1.2 client's clock said 2:xx PM PST when I was
> using it briefly and remotely (PuTTY) late last night before I passed
> out at about 10:32 PM PST. /var/log/'s log files showed the box working
> up to 3:17:01 AM PST from what I can tell.
>
X


If your system is not on a UPS it could have been a power surge that 
locked up your machine and scrambled your CMOS.


Also: A good possibility that it's as simple as a dead CMOS battery...
I'd replace it...it's probably a good precaution anyway.

[toc] | [prev] | [next] | [standalone]

#2178

On 1/10/2014 11:58 AM PT, philo  typed:

> If your system is not on a UPS it could have been a power surge that
> locked up your machine and scrambled your CMOS.

I do have an UPS:
$ /sbin/apcaccess
APC      : 001,036,0904
DATE     : 2014-01-10 12:12:22 -0800
HOSTNAME : MyBox
VERSION  : 3.14.10 (13 September 2011) debian
UPSNAME  : MyBox
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2014-01-10 06:41:30 -0800
MODEL    : Back-UPS XS 1500G
STATUS   : ONLINE
LINEV    : 119.0 Volts
LOADPCT  :  38.0 Percent Load Capacity
BCHARGE  : 100.0 Percent
TIMELEFT :  16.2 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
SENSE    : Medium
LOTRANS  : 088.0 Volts
HITRANS  : 139.0 Volts
ALARMDEL : No alarm
BATTV    : 27.0 Volts
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
SELFTEST : NO
STATFLAG : 0x07000008 Status Flag
SERIALNO : 4B1220P27574
BATTDATE : 2012-05-17
NOMINV   : 120 Volts
NOMBATTV :  24.0 Volts
NOMPOWER : 865 Watts
FIRMWARE : 866.L6 .D USB FW:L6
END APC  : 2014-01-10 12:12:33 -0800

Nothing unusual in /var/log/apcupsd.events file.


> Also: A good possibility that it's as simple as a dead CMOS battery...
> I'd replace it...it's probably a good precaution anyway.

Even if my PC is powered on 24/7? When I powered off and booted up a few 
times this morning, CMOS never told me about low battery like my older 
desktop PCs at work and personal desktop PCs in the past. Is there a way 
to check in Linux? I rarely reboot (only for Kernel upgrades) and shut 
down (usually for hardware maintenances, but haven't done that for 
almost a year).
-- 
"I have to sit up with a sick ant." --unknown
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2179

On 01/10/2014 02:17 PM, Ant wrote:
> On 1/10/2014 11:58 AM PT, philo  typed:
>
>> If your system is not on a UPS it could have been a power surge that
>> locked up your machine and scrambled your CMOS.
>
>

<snip>

>> Also: A good possibility that it's as simple as a dead CMOS battery...
>> I'd replace it...it's probably a good precaution anyway.
>
> Even if my PC is powered on 24/7? When I powered off and booted up a few
> times this morning, CMOS never told me about low battery like my older
> desktop PCs at work and personal desktop PCs in the past. Is there a way
> to check in Linux? I rarely reboot (only for Kernel upgrades) and shut
> down (usually for hardware maintenances, but haven't done that for
> almost a year).


Agreed but...
here is what I'd do:


Turn your machine off and unplug it from the UPS.


Plug a lamp into your UPS and turn it on.

Now pull the AC plug from the UPS and see if the lamp stays lit.

If it goes out pretty fast...your UPS batteries are dead.

If so, they should be replaced...but check the charging portion to 
confirm that's it's good. A 12V lead acid battery should "float" around 
13.5 volts unless the charging circuit employs hysteresis loop charging.
(HLC    v= 12.75 to 13.9  OK )


Also...if when you turn your machine back on...if the CMOS is scrambled 
again...almost for sure the CMOS battery is bad.

[toc] | [prev] | [next] | [standalone]

#2180

On 1/10/2014 12:37 PM PT, philo  typed:
...
 > Now pull the AC plug from the UPS and see if the lamp stays lit.

I only unplugged my UPS's AC plug from the house room's wall for about 
15 seconds since I was pretty sure my "not that old" UPS still works (a 
good test to do).


> If it goes out pretty fast...your UPS batteries are dead.

It was fine for old 19" 5:4 LCD monitor and two old desktop PCs 
connected to it (didn't hear any beeps, but did hear UPS' fan spin up). 
Here is what my e-mail notification said during my fake power outage:
APC      : 001,037,0928
DATE     : 2014-01-10 12:44:16 -0800
HOSTNAME : MyBox
VERSION  : 3.14.10 (13 September 2011) debian
UPSNAME  : MyBox
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2014-01-10 06:41:30 -0800
MODEL    : Back-UPS XS 1500G
STATUS   : ONBATT
LINEV    : 000.0 Volts
LOADPCT  :  36.0 Percent Load Capacity
BCHARGE  : 100.0 Percent
TIMELEFT :  17.2 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
SENSE    : Medium
LOTRANS  : 088.0 Volts
HITRANS  : 139.0 Volts
ALARMDEL : No alarm
BATTV    : 23.6 Volts
LASTXFER : Low line voltage
NUMXFERS : 1
XONBATT  : 2014-01-10 12:44:11 -0800
TONBATT  : 6 seconds
CUMONBATT: 6 seconds
XOFFBATT : N/A
SELFTEST : NO
STATFLAG : 0x07060010 Status Flag
SERIALNO : 4B1220P27574
BATTDATE : 2012-05-17
NOMINV   : 120 Volts
NOMBATTV :  24.0 Volts
NOMPOWER : 865 Watts
FIRMWARE : 866.L6 .D USB FW:L6
END APC  : 2014-01-10 12:44:17 -0800


> Also...if when you turn your machine back on...if the CMOS is scrambled
> again...almost for sure the CMOS battery is bad.

I will keep that in mind then even though I did have it off for a few 
minutes this morning to see if my PC would boot up again before I 
checked and fixed my CMOS. Also, I never saw any message that my CMOS' 
settings were set back to defaults like my previous older PCs like at work.
-- 
"It's kind of an insane case ... 6,000 ants dressed up as rice and 
robbed a Chinese restaurant." --Steven Wright
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2181

On 01/10/2014 02:54 PM, Ant wrote:
> On 1/10/2014 12:37 PM PT, philo  typed:
> ...
>  > Now pull the AC plug from the UPS and see if the lamp stays lit.
>
> I only unplugged my UPS's AC plug from the house room's wall for about
> 15 seconds since I was pretty sure my "not that old" UPS still works (a
> good test to do).
>


If your computers were on at the time and it held for 15 seconds then 
you know at least it would hold up for any momentary power failure.

[toc] | [prev] | [next] | [standalone]

#2184

On 1/10/2014 1:20 PM PT, philo  typed:

>> ...
>>> Now pull the AC plug from the UPS and see if the lamp stays lit.
>>
>> I only unplugged my UPS's AC plug from the house room's wall for about
>> 15 seconds since I was pretty sure my "not that old" UPS still works (a
>> good test to do).
>
> If your computers were on at the time and it held for 15 seconds then
> you know at least it would hold up for any momentary power failure.

Yep, everything survived from that 15 seconds. Someone suggested it 
could be the old 600 watts SeaSonic S12 PSU from 2005/2006? I wished I 
could easily reproduce this to test.
-- 
"Although you're a little ant, I won't bully you." --Sai Yuk from The 
Legend of Fong Sai Yuk movie (English subtitles)
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2185

On 01/10/2014 04:01 PM, Ant wrote:
> On 1/10/2014 1:20 PM PT, philo  typed:
>
>>> ...
>>>> Now pull the AC plug from the UPS and see if the lamp stays lit.
>>>
>>> I only unplugged my UPS's AC plug from the house room's wall for about
>>> 15 seconds since I was pretty sure my "not that old" UPS still works (a
>>> good test to do).
>>
>> If your computers were on at the time and it held for 15 seconds then
>> you know at least it would hold up for any momentary power failure.
>
> Yep, everything survived from that 15 seconds. Someone suggested it
> could be the old 600 watts SeaSonic S12 PSU from 2005/2006? I wished I
> could easily reproduce this to test.



It really sounds like a voltage surge. Even though a UPS should protect 
for that ...most lower priced UPS's are the standby type that will 
rapidly "switch on" in the event of a power failure. It's not impossible 
for them to pass on some amount of "noise".


The more expensive types employ a ferroresonant transformer which is 
pulse-width modulated and it's virtually impossible for one to pass on a 
voltage spike.

[toc] | [prev] | [next] | [standalone]

#2186

> It really sounds like a voltage surge. Even though a UPS should protect
> for that ...most lower priced UPS's are the standby type that will
> rapidly "switch on" in the event of a power failure. It's not impossible
> for them to pass on some amount of "noise".
>
> The more expensive types employ a ferroresonant transformer which is
> pulse-width modulated and it's virtually impossible for one to pass on a
> voltage spike.

Even if it was a voltage issue, my other connected PC would get hit. 
Right? FYI on my Debian/Linux box that crashed this morning with its 
current sensors):

$ sensors -f
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +129.2°F  (high = +176.0°F, crit = +212.0°F)
Core 1:      +125.6°F  (high = +176.0°F, crit = +212.0°F)
Core 2:      +125.6°F  (high = +176.0°F, crit = +212.0°F)
Core 3:      +132.8°F  (high = +176.0°F, crit = +212.0°F)

f71882fg-isa-0a00
Adapter: ISA adapter
+3.3V:        +3.28 V
in1:          +1.14 V  (max =  +2.04 V)
in2:          +0.86 V
in3:          +0.94 V
in4:          +1.09 V
in5:          +0.89 V
in6:          +0.72 V
3VSB:         +3.30 V
Vbat:         +3.20 V
fan1:        1095 RPM
fan2:        1038 RPM
fan3:           0 RPM  ALARM
fan4:           0 RPM  ALARM
temp1:        +87.8°F  (high = +185.0°F, hyst = +177.8°F)
                        (crit = +122.0°F, hyst = +114.8°F)  sensor = 
transistor
temp2:       +100.4°F  (high = +185.0°F, hyst = +177.8°F)
                        (crit = +212.0°F, hyst = +204.8°F)  sensor = 
transistor
temp3:          FAULT  (high = +158.0°F, hyst = +154.4°F)
                        (crit = +185.0°F, hyst = +181.4°F)  sensor = 
transistor

adt7473-i2c-4-2e
Adapter: NVIDIA i2c adapter 2 at 5:00.0
in1:          +3.00 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:        +3.25 V  (min =  +0.00 V, max =  +4.39 V)
fan1:        2920 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =  164 RPM)  ALARM
temp1:       +158.0°F  (low  = +149.0°F, high = +185.0°F)
                        (crit = +212.0°F, hyst = +208.4°F)
Board Temp:  +140.9°F  (low  = +68.0°F, high = +140.0°F)
                        (crit = +212.0°F, hyst = +204.8°F)
temp3:       +157.5°F  (low  = +176.0°F, high = +221.0°F)  ALARM
                        (crit = +242.6°F, hyst = +235.4°F)

I use cpufreq so voltages might look weird/odd?

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
stepping        : 7
microcode       : 0x705
cpu MHz         : 2003.000
cache size      : 2048 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 
lahf_lm dtherm
bogomips        : 4678.61
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
stepping        : 7
microcode       : 0x705
cpu MHz         : 2003.000
cache size      : 2048 KB
physical id     : 0
siblings        : 4
core id         : 1
cpu cores       : 4
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 
lahf_lm dtherm
bogomips        : 4678.28
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
stepping        : 7
microcode       : 0x705
cpu MHz         : 2003.000
cache size      : 2048 KB
physical id     : 0
siblings        : 4
core id         : 2
cpu cores       : 4
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 
lahf_lm dtherm
bogomips        : 4678.29
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
stepping        : 7
microcode       : 0x705
cpu MHz         : 2003.000
cache size      : 2048 KB
physical id     : 0
siblings        : 4
core id         : 3
cpu cores       : 4
apicid          : 3
initial apicid  : 3
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 
lahf_lm dtherm
bogomips        : 4678.30
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

I hope that helps?
-- 
"It is certain that there may be extraordinary mental activity with an 
extremely small absolute mass of nervous matter: thus the wonderfully 
diversified instincts, mental powers, and affections of ants are 
notorious, yet their cerebral ganglia are not so large as the quarter of 
a small pin's head. Under this point of view, the brain of an ant is one 
of the most marvelous atoms of matter in the world, perhaps more so than 
the brain of a man." --Charles Darwin (from The Origin of Species, 1859)
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2187

On 01/10/2014 07:43 PM, Ant wrote:
>> It really sounds like a voltage surge. Even though a UPS should protect
>> for that ...most lower priced UPS's are the standby type that will
>> rapidly "switch on" in the event of a power failure. It's not impossible
>> for them to pass on some amount of "noise".
>>
>> The more expensive types employ a ferroresonant transformer which is
>> pulse-width modulated and it's virtually impossible for one to pass on a
>> voltage spike.
>
> Even if it was a voltage issue, my other connected PC would get hit.
> Right? FYI on my Debian/Linux box that crashed this morning with its
> current sensors):



Not necessarily.



I have seen problems on rare occasions with the power connector.  Unplug 
your power connector(s) that go from your power supply to the 
motherboard and inspect the pins (both on the power supply and the 
motherboard) for tarnish or burn marks. If all OK...
plug and unplug a few times...then finally plug in securely.

A few times I've seen problems and traced it to burned pins...
and a few times I've seen problems that went away after the power 
connector was removed then reseated.


Looking below I did see one reading marked "FAULT"

It could be a bad sensor...or it could be a bad connection.




> $ sensors -f
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +129.2°F  (high = +176.0°F, crit = +212.0°F)
> Core 1:      +125.6°F  (high = +176.0°F, crit = +212.0°F)
> Core 2:      +125.6°F  (high = +176.0°F, crit = +212.0°F)
> Core 3:      +132.8°F  (high = +176.0°F, crit = +212.0°F)
>
> f71882fg-isa-0a00
> Adapter: ISA adapter
> +3.3V:        +3.28 V
> in1:          +1.14 V  (max =  +2.04 V)
> in2:          +0.86 V
> in3:          +0.94 V
> in4:          +1.09 V
> in5:          +0.89 V
> in6:          +0.72 V
> 3VSB:         +3.30 V
> Vbat:         +3.20 V
> fan1:        1095 RPM
> fan2:        1038 RPM
> fan3:           0 RPM  ALARM
> fan4:           0 RPM  ALARM
> temp1:        +87.8°F  (high = +185.0°F, hyst = +177.8°F)
>                         (crit = +122.0°F, hyst = +114.8°F)  sensor =
> transistor
> temp2:       +100.4°F  (high = +185.0°F, hyst = +177.8°F)
>                         (crit = +212.0°F, hyst = +204.8°F)  sensor =
> transistor
> temp3:          FAULT  (high = +158.0°F, hyst = +154.4°F)
>                         (crit = +185.0°F, hyst = +181.4°F)  sensor =
> transistor
>
> adt7473-i2c-4-2e
> Adapter: NVIDIA i2c adapter 2 at 5:00.0
> in1:          +3.00 V  (min =  +0.00 V, max =  +2.99 V)
> +3.3V:        +3.25 V  (min =  +0.00 V, max =  +4.39 V)
> fan1:        2920 RPM  (min =    0 RPM)
> fan2:           0 RPM  (min =    0 RPM)
> fan3:           0 RPM  (min =  164 RPM)  ALARM
> temp1:       +158.0°F  (low  = +149.0°F, high = +185.0°F)
>                         (crit = +212.0°F, hyst = +208.4°F)
> Board Temp:  +140.9°F  (low  = +68.0°F, high = +140.0°F)
>                         (crit = +212.0°F, hyst = +204.8°F)
> temp3:       +157.5°F  (low  = +176.0°F, high = +221.0°F)  ALARM
>                         (crit = +242.6°F, hyst = +235.4°F)
>
> I use cpufreq so voltages might look weird/odd?
>
> $ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 23
> model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
> stepping        : 7
> microcode       : 0x705
> cpu MHz         : 2003.000
> cache size      : 2048 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 4
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
> aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1
> lahf_lm dtherm
> bogomips        : 4678.61
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 23
> model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
> stepping        : 7
> microcode       : 0x705
> cpu MHz         : 2003.000
> cache size      : 2048 KB
> physical id     : 0
> siblings        : 4
> core id         : 1
> cpu cores       : 4
> apicid          : 1
> initial apicid  : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
> aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1
> lahf_lm dtherm
> bogomips        : 4678.28
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> processor       : 2
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 23
> model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
> stepping        : 7
> microcode       : 0x705
> cpu MHz         : 2003.000
> cache size      : 2048 KB
> physical id     : 0
> siblings        : 4
> core id         : 2
> cpu cores       : 4
> apicid          : 2
> initial apicid  : 2
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
> aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1
> lahf_lm dtherm
> bogomips        : 4678.29
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> processor       : 3
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 23
> model name      : Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
> stepping        : 7
> microcode       : 0x705
> cpu MHz         : 2003.000
> cache size      : 2048 KB
> physical id     : 0
> siblings        : 4
> core id         : 3
> cpu cores       : 4
> apicid          : 3
> initial apicid  : 3
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
> aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1
> lahf_lm dtherm
> bogomips        : 4678.30
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> I hope that helps?

[toc] | [prev] | [next] | [standalone]

#2190

> Looking below I did see one reading marked "FAULT"
>
> It could be a bad sensor...or it could be a bad connection.

I have had since day one/1. I doubt that is the cause of it. :/
-- 
"At high tide the fish eat ants; at low tide the ants eat fish." --Thai 
Proverb
    /\___/\ Leveled Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2193

On 01/11/2014 03:24 AM, Ant wrote:
>> Looking below I did see one reading marked "FAULT"
>>
>> It could be a bad sensor...or it could be a bad connection.
>
> I have had since day one/1. I doubt that is the cause of it. :/



More important would be the zeroth day. <g>


At any rate if it were my machine not only would I check the cmos 
battery  I'd inspect the PSU connectors.

[toc] | [prev] | [next] | [standalone]

#2182

On 1/10/2014 2:23 PM, Ant wrote:
> ... I woke up before 6:15 AM PST and noticed my old box wasn't
> responding (e.g., SSH2's text terminal commands not recognizing)
> correctly and its BitchX v1.2 client's clock said 2:xx PM PST when I
> was using it briefly and remotely (PuTTY) late last night before I
> passed out at about 10:32 PM PST. /var/log/'s log files showed the box
> working up to 3:17:01 AM PST from what I can tell.
>
> Anyways, I rebooted and Grub couldn't find blah blah. Then, I noticed
> it was trying to boot up my former old Seagate 80 GB PATA HDD which
> isn't supposed to do (it is just an storage drive). I did a manual
> boot (F11) and saw all of my drives. I booted to my Corsair SSD, and
> it was fine. I rebooted into my CMOS and its boot order seems to be
> messed up (should be booting to Corsair SSD first and all else
> disabled!). So, I fixed it and it worked fine.
>
> What the frak happened? Did my motherboard forget everything and
> resetted? Something else? I assume both of my drives are OK (ran
> smartctrl command's long tests and attached their results for reviews
> just in case)?
>
> Thank you in advance. :)

Ant:

CMOS battery failing, Power supply failing, Stray cosmic ray?

John

-- 
                          \\\||///
------------------o000----(o)(o)----000o----------------
----------------------------()--------------------------
'' Madness takes its toll - Please have exact change. ''

John Dulak - 40.4888ºN,79.899ºW - http://tinyurl.com/3lvoh2n

[toc] | [prev] | [next] | [standalone]

#2183

On 1/10/2014 1:38 PM PT, John Dulak typed:

> CMOS battery failing, Power supply failing, Stray cosmic ray?

I didn't get any messages about low CMOS battery during the boot ups. 
600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006. 
It and my PC still work? How can I check to see if it was from it? Stray 
cosmic ray? Wouldn't that affect my other machines and electronics too? :P
-- 
"Even the ant has his (her) bite." --Turkish
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2188

Ant <ant@zimage.comANT> wrote
> John Dulak wrote

>> CMOS battery failing, Power supply failing, Stray cosmic ray?

> I didn't get any messages about low CMOS battery during the boot ups.

You can get that with a poor connection to the cmos battery.

> 600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006. It 
> and my PC still work? How can I check to see if it was from it?

By swapping it with a good one if you see it happen again and
see if that stops it happening. Unlikely to reset the cmos tho.

> Stray cosmic ray? Wouldn't that affect my other machines and electronics 
> too? :P

Yes, that's why you had that short circuit between your ears. 

[toc] | [prev] | [next] | [standalone]

#2189

On 1/10/2014 8:09 PM PT, Rod Speed typed:

>> 600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006.
>> It and my PC still work? How can I check to see if it was from it?
>
> By swapping it with a good one if you see it happen again and
> see if that stops it happening. Unlikely to reset the cmos tho.

I will try that if my box crashes again and lose my CMOS' boot settings. 
I did notice the date and time were correct in Linux/Debian, but I think 
it was too late since NTP synchronized those already online. I should 
have checked them in CMOS like I did with the drives' boot order. So 
far, no new incidents.


>> Stray cosmic ray? Wouldn't that affect my other machines and
>> electronics too? :P
>
> Yes, that's why you had that short circuit between your ears.

Uh... I don't get it but then it is 1:20 AM PST. |(
-- 
"At high tide the fish eat ants; at low tide the ants eat fish." --Thai 
Proverb
    /\___/\ Leveled Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2192

In comp.sys.ibm.pc.hardware.storage Ant <ant@zimage.comant> wrote:
> On 1/10/2014 1:38 PM PT, John Dulak typed:

>> CMOS battery failing, Power supply failing, Stray cosmic ray?

> I didn't get any messages about low CMOS battery during the boot ups. 
> 600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006. 
> It and my PC still work? How can I check to see if it was from it? Stray 
> cosmic ray? Wouldn't that affect my other machines and electronics too? :P

Not all computers warn you and some do not even have a sensor 
for it (some Lenovo Laptops from the last 3-5 years, e.g.).
I guess they expect the thing not to be in use logn enough
for the battery to die.

The clock being wrong is a dead giveaway for a dying battery 
though. It is usually a CR2032 litium battery these days.

Arno

[toc] | [prev] | [next] | [standalone]

#2194

On 1/11/2014 4:52 AM PT, Arno typed:
...
>> I didn't get any messages about low CMOS battery during the boot ups.
>> 600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006.
>> It and my PC still work? How can I check to see if it was from it? Stray
>> cosmic ray? Wouldn't that affect my other machines and electronics too? :P
>
> Not all computers warn you and some do not even have a sensor
> for it (some Lenovo Laptops from the last 3-5 years, e.g.).
> I guess they expect the thing not to be in use logn enough
> for the battery to die.
>
> The clock being wrong is a dead giveaway for a dying battery
> though. It is usually a CR2032 litium battery these days.

The time was wrong before I did the reboot. My PC is on 24/7. So, that 
is still caused by a dead/weak battery? So far, no problems since 
yesterday morning. I thought CMOS batteries were only saving settings 
when PC is not connected to power AC.
-- 
"At high tide the fish eat ants; at low tide the ants eat fish." --Thai 
Proverb
    /\___/\   +1 to Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.

[toc] | [prev] | [next] | [standalone]

#2196

Ant <ant@zimage.comANT> wrote
> Arno wrote

>>> I didn't get any messages about low CMOS battery during the boot ups.
>>> 600 watts SeaSonic S12 PSU could be it since I had it since 2005/2006.
>>> It and my PC still work? How can I check to see if it was from it? Stray
>>> cosmic ray? Wouldn't that affect my other machines and electronics too? 
>>> :P

>> Not all computers warn you and some do not even have a sensor
>> for it (some Lenovo Laptops from the last 3-5 years, e.g.).
>> I guess they expect the thing not to be in use logn enough
>> for the battery to die.

>> The clock being wrong is a dead giveaway for a dying battery
>> though. It is usually a CR2032 litium battery these days.

> The time was wrong before I did the reboot. My PC is on 24/7. So, that is 
> still caused by a dead/weak battery?

Yes, that normally happens before you see cmos values lost.

> So far, no problems since yesterday morning. I thought CMOS batteries were 
> only saving settings when PC is not connected to power AC.

That's true in the sense that its powered from
the power supply when its connected to the mains. 

[toc] | [prev] | [next] | [standalone]

#2197

On 1/11/2014 10:26 AM PT, Rod Speed typed:

>> The time was wrong before I did the reboot. My PC is on 24/7. So, that
>> is still caused by a dead/weak battery?
>
> Yes, that normally happens before you see cmos values lost.

Hmm. I remember it said 2 or something PM PST. I was using PC until 
10:32 PM PST. If my computer's CMOS went bust, then it should have 
happened after 3:17 AM PST. Or maybe my BitchX's time got jacked off too 
from the crash and CMOS's boot drive order mess up.
-- 
"At high tide the fish eat ants; at low tide the ants eat fish." --Thai 
Proverb
    /\___/\   +1 to Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.hardware

csiph-web