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

Groups > comp.os.linux.hardware > #2187

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

From philo  <philo@privacy.net>
Newsgroups comp.os.linux.hardware
Subject Re: Did something on my old Debian/Linux stable box crash and mess up my CMOS?
Date 2014-01-10 19:59 -0600
Organization A noiseless patient Spider
Message-ID <laq8hl$3v0$1@dont-email.me> (permalink)
References (4 earlier) <b5GdndcHvZGNw03PnZ2dnUVZ_uednZ2d@earthlink.com> <lapo69$au8$1@dont-email.me> <voKdnfZmv8Mn8E3PnZ2dnUVZ_sqdnZ2d@earthlink.com> <laq4k5$ist$1@dont-email.me> <A8-dnT1rFIUlPE3PnZ2dnUVZ_rudnZ2d@earthlink.com>

Show all headers | View raw

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?

Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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

csiph-web