On Mon, Sep 22, 2014 at 08:10:51PM +0200, Louis Lagendijk wrote:
> On Mon, 2014-09-22 at 08:43 +0100, Ian Malone wrote:
> > On 22 September 2014 03:37, Chris Murphy <li...@colorremedies.com> wrote:
> > >
> > > On Sep 19, 2014, at 3:08 PM, David A. De Graaf <d...@datix.us> wrote:
> > >
> > >>>
> > >>> On Fri, Sep 19, 2014 at 11:51 AM, Chris Murphy
> > >>> <li...@colorremedies.com> wrote:
> > >>>>
> > >>>> On Sep 19, 2014, at 10:18 AM, David A. De Graaf <d...@datix.us> wrote:
> > >>>>>
> > >>>>> When the system freezes, if X is lit (not screen-saved) the LCD
> > >>>>> monitor looks as if it had been hit a sharp blow on the right edge so
> > >>>>> that all the pixels have been shaken loose.
> > >>>>
> > >>>> Sounds like a bad motherboard. It's managing to corrupt memory in such
> > >>>> a way that you're getting video artifacts.
> > >>>>
> > >> Chris, I agree. Which is why the first thing I tried was to buy a
> > >> new different motherboard (to replace the almost new motherboard).
> > >> The two mobo's have onboard video that appears to be different, yet the
> > >> display during freeze is indistinguishable.
> > >
> > > OK but when you say different motherboard, how different? Same make and
> > > model? It could still be from the same batch; either the logic board
> > > itself, or the components.
> > >
> >
> > From David De Graaf's original email:
> > "Originally, I had used a Gigabyte 78MT-USB3 mobo, but replaced it with
> > an ASRock 960M/U3S3 FX mobo in a futile attempt to fix the problem."
> >
> > If I had to take a guess, and with PSU issues ruled out (I'm assuming
> > "I did also change the power supply but forgot to list that with all
> > the other things that didn't work." means "to a larger capacity
> > one".), the other common factor is the hard drive. Possibly it's doing
> > something that SATA3 ignores or handles better, either because of
> > different controller chips or some difference in the driver software.
> > Any log errors recorded when it crashes? Might be one for a kernel
> > bug. Increasing frequency of the problem could indicate something in
> > the drive electronics that's failing.
> Did the OP try a different SATA cable? If replaqcing the power supply
> nor the Mobo solves the issue, the SATA cable may be the issue....
>
As the OP (that's me) I am terribly embarrassed to say that my fix
fixes nothing. After tediously testing all four of the SATA 2 sockets
to verify that all produce freezes, imagine my dismay to find that the
system now also freezes with the SATA cable plugged into either of the
SATA 3 sockets.
Now Louis Lagendijk suggests changing the SATA cable. That's just weird!
But with nothing else left to try, I've done so, and the system has been
running for over 20 hours. That's good, but not yet conclusive.
I'm off on a trip for a few days. Let's see if it's still running when
I get back. I'll let you know.
Meanwhile, thanks to everyone for thinking and suggesting and writing.
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
d...@datix.us www.datix.us
Government's view of the economy could be summed up in a few short phrases:
If it moves, tax it.
If it keeps moving, regulate it.
And if it stops moving, subsidize it.
- Ronald Reagan
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
