Hello,
I have an issue on FC3, as following:
after few hours the system become extremely slow in responding and eventually will hang. The time interval for this to happen is usually 4-5 hours. I tried on several configuration, all Intel based, on i865 and i875 chipsets, with video and audio incorporated, on both PATA and SATA. I also installed FC3 with and without SELinux, as well as fresh install or upgrading from FC2.
Does anyone have any ideea how to work this out?
Thank you
Calin Cosma
-----------------------------------------------------------------------
Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. -- Antoine de Saint-Exupery
Hi Calin
Please attach: the output of 'lspci -v' dmesg tail -n 500 /var/log/messages, after a hang Xorg.0.log lsmod /etc/modprobe.conf
Hi Marius
Sorry for being so late in my response, but I've just upgraded my hw configuration. Still the issue appears. You may find below the messages you asked. Please note that FC2 runs without any problem (no hangs, no slow response, no desktop freezing) and I've updated FC3 with the latest updates avaliable.
Thank you.
On Mon, 2004-11-22 at 08:05, Marius Andreiana wrote:
Hi Calin
Please attach: the output of 'lspci -v' dmesg tail -n 500 /var/log/messages, after a hang Xorg.0.log lsmod /etc/modprobe.conf
-- Marius Andreiana Galuna - Solutii Linux in Romania http://www.galuna.ro
On Tue, 2004-11-30 at 17:12 -0500, calin wrote:
Sorry for being so late in my response, but I've just upgraded my hw configuration. Still the issue appears.
what did you replaced completely? (to see what's left unchanged)
You may find below the messages you asked.
nothing weird in them :(
Please note that FC2 runs without any problem (no hangs, no slow response, no desktop freezing) and I've updated FC3 with the latest updates avaliable.
could you please leave the workstation in a night booted with fc3 install CD and running "linux memtest" ? But as fc2 works, it doesn't seem to be a hardware problem
i started using a kernel from kernel.org because i hoped it would help me get rid of some problems i was having with the kernel (which, since then, i realize are in those kernels too) but since i have that kernel so well configured for my system, i wish i could keep using it.
it works great. all my devices are in perfect working order, every module is being loaded, it's perfect. the problem isn't with the kernel.
when i use this kernel (and it doesn't seem to matter if it's one of linus' or morton's (i haven't tried any others, it's too inconvenient on dial up)), haldaemon doesn't seem to want to work correctly. it doesn't seem to be haldaemon's fault. it's just that the kernel does sysfs a little differently...
sorry, this is getting hard to explain. let me be a little more specific. i have a couple of USB mass storage devices. they work in both kernels perfectly. the devices are created (even following my custom udev rules so the naming and symlinking is persistent). i can mount them myself. but automatic mount points aren't being created like they should !
i spent a really long time trying to figure out the problem, and i think it's with sysfs. with a _Fedora_ kernel, HAL finds info about each storage volume under a path like this (this would be for my USB CD-RW):
linux.sysfs_path_device = '/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:2.0/host0/0:0:0:0'
and the same USB CD-RW's info in a vanilla kernel seems to be in THIS path:
/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:2.0/host1/target0:0:0/0:0:0:0
and HAL doesn't seem to be able to figure that out. is that indeed what the problem is ? is HAL not looking in the right place ? it's unaware of the existence of these storage volumes even though they exist. i don't know how to make HAL look in the right place or if i need and updated version or if i'm going in a totally wrong direction. is anybody else using a vanilla kernel with USB storage and not getting automatic mountpoints ?
udev figures this out (which i can see from "udevinfo -a -p `udevinfo -q path -n /dev/sr0`") !! why not HAL ?
On Mon, 2004-11-22 at 12:22 -0500, Emily Brantley wrote:
i started using a kernel from kernel.org because i hoped it would help me get rid of some problems i was having with the kernel (which, since then, i realize are in those kernels too) but since i have that kernel so well configured for my system, i wish i could keep using it.
it works great. all my devices are in perfect working order, every module is being loaded, it's perfect. the problem isn't with the kernel.
when i use this kernel (and it doesn't seem to matter if it's one of linus' or morton's (i haven't tried any others, it's too inconvenient on dial up)), haldaemon doesn't seem to want to work correctly. it doesn't seem to be haldaemon's fault. it's just that the kernel does sysfs a little differently...
sorry, this is getting hard to explain. let me be a little more specific. i have a couple of USB mass storage devices. they work in both kernels perfectly. the devices are created (even following my custom udev rules so the naming and symlinking is persistent). i can mount them myself. but automatic mount points aren't being created like they should !
i spent a really long time trying to figure out the problem, and i think it's with sysfs. with a _Fedora_ kernel, HAL finds info about each storage volume under a path like this (this would be for my USB CD-RW):
linux.sysfs_path_device = '/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:2.0/host0/0:0:0:0'
and the same USB CD-RW's info in a vanilla kernel seems to be in THIS path:
/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:2.0/host1/target0:0:0/0:0:0:0
and HAL doesn't seem to be able to figure that out. is that indeed what the problem is ? is HAL not looking in the right place ? it's unaware of the existence of these storage volumes even though they exist. i don't know how to make HAL look in the right place or if i need and updated version or if i'm going in a totally wrong direction. is anybody else using a vanilla kernel with USB storage and not getting automatic mountpoints ?
udev figures this out (which i can see from "udevinfo -a -p `udevinfo -q path -n /dev/sr0`") !! why not HAL ? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
and oops. didn't mean to reply to that guy's email. should i repost or leave it alone ?
-
calin -
Emily Brantley -
Marius Andreiana