I've got Rawhide running on an SMP PentiunIII machine, and up until the
post 2.6.17 kernel things had been very stable on the machine. The
development kernels leading to 2.6.18 have not been nearly as reliable
as many others on the list have observed. In my particular case,
the machine continues to lock up during network activity as that done
for 'yum update' or browsing with Firefox.
What I'm vexed about is how to try and debug the problem I'm seeing. A
bugzilla report saying 'Kernel locks up during network activity' is just
to vague to be of any use. Also, the lock ups are not consistent - I can
do somethings like 'git pull' or updates with cvs/svn and more often
than not the machine hums along. But then that one event happens and
things lock up solid requiring a reboot. The 'yum update' I try and do
daily is almost always guaranteed to cause a lockup at least one out of
two times I try to get the latest packages.
In an effort to try and get the latest Rawhide packages, this morning I
booted off an FC5 install disc with 'linux rescue', and with a bit of
chroot magic I was able to get many of the updates available this
morning with some exceptions due to dependency issues which I'm sure
will be resolved shortly. I'd also run 'memtest86' on the machine for a
day or two and it ran without errors.
Given my description above, just what sort of steps can people recommend
so that I can try and narrow down the problem? I'd like to try and dig
in a bit so that I can possibly fix things or at least make a useful bug
report. I'd hoped that the post 2.6.18-rc2 kernels would have fixed
things as a variety of networking bugs have been patched but that has
not happened. Suggestions welcomed.
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
I dual-boot Fedora with WinXP on my laptop. A couple of years ago I got
swsusp2 (Software Suspend) going with FC3 (I think) and it worked pretty
well. I could keep Fedora and XP in hibernated states and select the one
I wanted from the GRUB menu.
With hibernate on FC6 I don't get the GRUB menu - although it briefly
mentions GRUB at startup - so after hibernating Fedora I can only go
back to Fedora. If I want XP I have to de-hibernate Fedora, then shut
the computer down, then start Windows.
Could it be changed so the GRUB menu appears so the required OS is
started? Or is there a good reason for doing it this way?
Thanks in advance,
After messing up my install to the point where it was no longer worth
fighting, I made a new install of Test1 last night and tried to run update.
It fails with the message that 'autofs conflicts with kernel < 2.6.17' - but
I had already seen that message and installed the new kernel. I am running
-----BEGIN PGP SIGNED MESSAGE-----
Any idea why X is using so much RAM on Rawhide?
I have Composite Enabled and I am using compiz as the Window Manager.
That just seems like a lot of memory.
Apps I have running
gaim, firefox, thunderbird and anjuta
- From top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2285 root 15 0 546m 120m 11m S 6.6 12.1 11:27.51 Xorg
Get my public GnuPG key from
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
this is also tricky with
rpm --setugids <packages>
rpm --setperms ...
the order is important here!, isn't it ?
rpm --setperms coreutils-5.97-1.1
rpm --setugids ...
i noticed this after an "unprofessional" move of an partition
Jim Cornette <fct-cornette(a)insight.rr.com> wrote:
> Would the driver for radeon (ati) be causing this error?
I've got an nVidia chip here, using the xorg driver.
> code? Mesa-libGL? A combination of these or something else?
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513