At 08:34 12-6-2001 -0500, Steve Lord wrote:
> > Well, check the Linux mailing lists -- reading those, and having battled
> > with a Tyan Tiger 133 for ages now, I would be extremely hesistant depend
> > on anything with a VIA chip set onboard. I'm sure that they'll get it
> > right at some point, but at the moment, stability and reliability still
> > seems to equal Intel, and then preferably a 440BX chip set.
>
> well I certainly can't replace the motherboard. Unless things *really*
get
> bad and that's the only possible solution.
There is nothing about XFS which should be directly affected by the particular
type of motherboard you have. XFS may stress the system in different manners,
and expose kernel/bios/hardware bugs that ext2 would not. However, if a
board works
without problems on Linux normally, but is crashing with XFS then I would say
the most likely explaination is that you have an I/O load which is
triggering a
bug in XFS. Without some form of oops message (decoded) or a stack backtrace
from kdb, there is not much we can do to diagnose the problem. There is a good
chance that running the latest kernel will make the problem 'go away' since
we have fixed a lot of problems. However, your situation with being so far
from
the machine does not make it easy to do experiments with different kernels.
See http://kt.zork.net/kernel-traffic/kt20010611_121.html#5 This explains
the problems people are seeing on VIA boards. These are general not XFS
related issues. It's just that the 2.4.2 1.0 misses a lot of updates to
handle the VIA chipsets.
Cheers
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.
|