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


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

Re: Journaling problem

From Haines Brown <haines@histomat.net>
Newsgroups comp.os.linux.hardware
Subject Re: Journaling problem
References <87lhmsgyvu.fsf@bach.histomat.net> <wwvppc45nng.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid> <87h9xfhaks.fsf@bach.histomat.net> <wwviohv5gx8.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid>
Date 2014-12-02 10:09 -0500
Message-ID <87d282gkal.fsf@bach.histomat.net> (permalink)

Show all headers | View raw


Richard Kettlewell <rjk@greenend.org.uk> writes:

> Haines Brown <haines@histomat.net> writes:
>> Richard Kettlewell <rjk@greenend.org.uk> writes:

> The BIOS can run at any time, not just during boot.  In particular it is
> likely to run when certain hardware problems are detected.  See
> https://en.wikipedia.org/wiki/System_Management_Mode for more
> information.
>
> Beeping is a common way for the BIOS to report errors.  I don’t know of
> anything else that uses this particular strategy.

The BIOS is an American Megatrends F3, and I don't see that it allows me
to set acceptable ranges for fan speeds, temperature, voltage, etc. DRAM
latency values set a bit higher (for example, 11 vs 9) than recommended
by the manufacturer (Skill), but I suppose this only means I'm getting
a little more stability at the cost of performance. 

The DRAM passed memtest OK, the power supply voltage is correct. The CPU
is running cool, case fans all seem to be spinning up to speed. Although
the hang followed by beeps suggests hardware problems, I suspect that
the hang is of X not getting along with systemd in the testing version
of my linux distribution. I ran the hardware two weeks without systemd
and there were no problems; I could well be wrong, but the beeps seem
quieter than BIOS warning or code beeps, about as if do DEL at a
terminal prompt.

I will now try to do a fsck on the hard disk. If it passes, I'll install
my old distribution that lacked systemd. If after a week or two there is
no freeze, I'll conclude that problem not hardware, but if there is a
freeze, then I'll know what has to be done next.

My HD manufacturer (Seagate) has a diagnostic utility that I'll trying
to run on the drive.   

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


Thread

Journaling problem Haines Brown <haines@histomat.net> - 2014-11-30 16:30 -0500
  Re: Journaling problem Marc Haber <mh+usenetspam1118@zugschl.us> - 2014-11-30 22:55 +0100
  Re: Journaling problem philo  <philo@privacy.net> - 2014-11-30 16:11 -0600
  Re: Journaling problem Richard Kettlewell <rjk@greenend.org.uk> - 2014-11-30 22:28 +0000
    Re: Journaling problem Haines Brown <haines@histomat.net> - 2014-12-01 06:29 -0500
      Re: Journaling problem Richard Kettlewell <rjk@greenend.org.uk> - 2014-12-01 19:05 +0000
        Re: Journaling problem Haines Brown <haines@histomat.net> - 2014-12-02 10:09 -0500
          Re: Journaling problem Thomas Richter <thor@math.tu-berlin.de> - 2014-12-02 16:48 +0100
            Re: Journaling problem Haines Brown <haines@histomat.net> - 2014-12-02 16:44 -0500

csiph-web