On Mon, 9 Oct 2000, John Koyle wrote:
> A friend and I just upgraded our workstations from RH6.2 to 7.0. We did
> a full re-install however, not the upgrade off the CD. We are both
> having a lot of problems where the system will hang. I've had it hang
> in the middle of moving my mouse across the screen and doing nothing at
> all. It's been installed for about a week, and there hasn't been a
> single morning yet where I've come into work to find the machine still
> on.
...
> 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
