[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Giving up on Linux...

Hash: SHA1

On Sunday 22 February 2004 16:02, xyzzy hotpop com wrote:

> Look at bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109497
> which has been open since November and is ending up with the consensus that
> it is a problem with the Fedora stock kernels....  People with this bug
> report that if they run 2.4.24 from kernel.org, they have uptimes of over a
> week without problems.

I had mixed success with sticking stuff in Bugzilla.  A problem that was my 
fault with turning off cupsd was nailed down efficiently by a RH guy that 
way.  But some other things just got ignored.  It would be better to have a 
bug closed as "you're an idiot" than nothing.

I wouldn't necessarily trawl Bugzilla to collect the temperature of Fedora 
stability.  All large apps have many problems that may only occur with 
certain environmental factors.  If you look at the canonical list of all 
problems under all circumstances you're going to be alarmed be it Fedora or 
be it Windows.  Generally, people on the list (including me) are telling you 
that under normal circumstances Fedora is pretty good.

If this particular thing turns out to be an issue for you, it looks like 
running a stock kernel is enough to keep you going.

> I was also leaning towards trying the 2.6 kernel but that is a major hassle
> for me if I can't get X up at all due to the seg fault I had from updating
> the Intel graphics driver.

My advice would be to try to remove X from the equation under 2.4 as 
suggested.  Then, if your disease is present without X on 2.4, you can test 
if 2.6 helped without having to bring up X in 2.6.  FWIW the X driver "vesa" 
is really very compatible with most everything I ever ran Linux on.

Thinking about what "slow" could mean, I would definitely be looking hard 
at /var/log/messages, and also things like /proc/interrupts.  ACPI can also 
be the problem, try acpi=off on the kernel commandline 
in /boot/grub/grub.conf, it can change the way Interrupts are deal with.

You didn't mention if you checked for BIOS updates, too.  If the heart fo the 
problem is some BIOS messup that can easily go away with an update.

- -Andy

- -- 
Find your answer without waiting for replies....
Searchable list archives at 
Version: GnuPG v1.2.3 (GNU/Linux)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]