I also do a kernel compile loop burn in test on my machines (first
sugested to me by the honorable Donald Becker oncE :) )
I have used the same g400 in two machines, both able to compile the kernel
with -j4 for days. As an aside, on one of these machines I actually forgot
I was compiling the kernel for a few days as she still performed well :).
The card worked fine for several months under 6.2 XFree86 3.x. Once I
upgraded the first machine to 7.0 and played around tiht XFree86 4.0 and
dual-headed (perhaps the real problem there) It started locking up. Even
when I went back to single headed, and the original mga driver it
continued to lockup. It is not locking up now with an ATI card.
I did some brief testing on a new machine (but with the same card) and it
locked up after leaving it overnight. This could very well have been an
apmd issue since I hadn't completed configuring the box. I will be redoing
the burn in test when I get it back, and will report on it's stability
too.
But, I do see something common amongst these machines (with
lockups). They are all athlons. this may be pure coincidence.
My "old" system:
Microstar MB
Athlon 500
Adaptec 2940U2W
2 x IBM 9GB LVD drives
Matrox G400 32MB
lynksys or netgear thernet
SB 64 sound (i think)
My new system:
Asus K7M MB
Athlon 800 (only reported 550 so I sent her back)
Adaptec 29160
Seagate 160 drive 18GB
Matrox G400 32MB (same card as above)
3com nic
some built in sound - not configured
charles
On Mon, 9 Oct 2000, Gordon Messmer wrote:
> On Mon, 9 Oct 2000, John Koyle wrote:
> > System info:
> > Microstar MB
> > Athlon 700
> > Adaptec 29160
> > Seagate 160 drive
> > Matrox G200 8MB
> > Intel Etherexpress 100
> > ES1371 soundcard
> >
> > My friend has the some config only with a 2940 controller and UW drive.
>
> In light of other reports of problems with Matrox cards, I thought I'd
> through in my system config.
>
> I also have Red Hat 7.0 installed, though I'm using a kernel that I
> compiled previously for LVM support.
>
> I have:
> Intel DK440LX dual CPU MB
> 2x Intel PII 300Mhz
> Adaptec 2940 (AIC-7895) :: aic7xxx
> Matrox G400 32MB :: mga XF4.0
> Intel Etherexpress 100 :: eepro100
> Crystal sound? onboard :: ALSA snd-card-cs4236
> PS/2 keyboard and MicroSoft USB Intellimouse
>
> My system has been totally stable. I've left myself logged in to X for 13
> days until this morning, when I installed the glibc errata from Red Hat
> and rebooted the system.
>
> When I test hardware, I usually take the following steps:
>
> download the latest copy of memtest86 (find it on freshmeat) and run it
> for at least 8 hours.
>
> boot linux into single user mode, remove any modules you don't need, and
> start compiling kernels in a loop:
> #!/bin/sh
> cd /usr/src/linux
> while: ; do
> if ( make bzImage >/dev/null ) ; then
> echo "GOOD kernel compile at `date`" >> /tmp/compile.log
> else
> echo "BAD kernel compile at `date`" >> /tmp/compile.log
> fi
> if ( make modules >/dev/null ) ; then
> echo "GOOD modules compile at `date`" >> /tmp/compile.log
> else
> echo "BAD modules compile at `date`" >> /tmp/compile.log
> fi
> done
>
> That should run for about 24 hours. give or take a length of
> patience. If either of those tests produce ANY errors, you have hardware
> issues, and you should take the issue up with your manufacturer/place of
> purchase.
>
> If they turn up no errors, then your scsi controller is probably good, as
> is your drive, processor, motherboard and RAM. That leaves your video
> card, sound card, NIC, or peripherals as possible problems. Testing that
> shouldn't be too difficult if you machine locks up reliable every
> day. Just start switching cards out for other brands of cards until it
> stops ;)
>
> I'd be interested in what you learn.
>
> MSG
>
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
