Ok, that _CANNOT_ be yum's problem, some other part of your system is
flaky. Either Hard Disk, or HDD drivers, or RAM, or CPU, or kernel
drivers for one of the above. But it is _NOT_ yum. It can't be. Yum may
be the most likely to trigger it, but that doesn't make it it's problem.
It just isn't possible (no program can freeze the machine under linux, if
a program does freeze the machine, then either there's a bug in the
kernel, a hardware error or the program is running with ioport priveledges
(which yum doesn't use)). Again, try running memtest86 and mprime on it -
verify that the systems CPU and RAM are stable, then try running some disk
intensive tasks, then try running them concurrent to mprime. But it's
99.99% guaranteed that you either have flaky hardware or flaky kernel
drivers.
Cheers,
MaZe.
On Thu, 8 Sep 2005, Dave Gutteridge wrote:
>
>> but as far as I can see you don't have a specific
>> problem per se, just that yum is slow which has been addressed
>>
> Um... I guess I didn't convey the problem. Yum isn't just slow, it freezes my
> machine. It halts the system to the point where the mouse and keyboard are
> unresponsive, and the only way I can regain control of my system is to do a
> hard reset. Yum is the only program on my system which causes this to happen.
>
> If I run Yum immediately after a reboot, it's usually safe. This is how I've
> managed to keep up to date.
>
> But, if I have been using my computer for a while, and then I run Yum, it is
> just as likely as not to freeze my computer. Or, if I run Yum more than once,
> it may freeze my computer on the second, or third time.
>
> If Yum was just slow, I wouldn't mind so much. But having to hard reset is a
> pretty big issue.
>
> Dave
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
