Dawning Sky wrote:
On 7/22/07, Hansen <mht@xxxxxxxxxxx> wrote:
On Sun, 2007-07-22 at 14:17 -0700, Dawning Sky wrote:
> I'm experiencing this freeze too. I've disabled irqbalance, put
> "noirqbalance" in the kernel parameters, removed compiz. But my F7
> system still freezes a few times a day.
>
> It appears related to the desktop environment. I can leave it there
> for weeks, with server processes running. But if I sit there and
> using the desktop environment, it then freezes frequently. Nothing in
> the log files.
OK, I saw this happen 22 days ago. I made sure I had all updates, then
rebooted and added kernel parameters to log the boot/console to serial
port. I capture this with another machine running f7 {minicom}.
Last night I noticed the kernel update, so I have updated the machine,
and now running 2.6.22 release. The machine stayed up for 21 days until
I told it to reboot with the newer kernel package.
During this time I have had at least 15 gnome-terminal, azureus
bittorrent {sharing Fedora-7-i386 dvd - total uploads 180 GB}, short
periods of limewire, 7 tabs in firefox, another 10-15 tabs in another
firefox, doing a lot of nautilus file sorting/moving, some python/django
development / web server testing, all shared between 4x desktops,
vncviewer sessions going to a local server for a week at a time,
thunderbird email with a zillion fedora-list emails, ssh sessions to
work, and clients, xmms music playback, xine dvd and dvb tuner recording
and playback, mplayer playback, having my many partitions fill up,
deleting stuff, moving stuff around, moving 150 GB from amongst 3xdisks
to an external usb drive, gparted, removing partitions of one of the
disks, repartitioning, and running system-config-lvm to make an lvm
volume, and then copying all the information back - slightly better sorted.
All I'm saying is that it definitely can be reliable in my configuration:
AMD Athlon XP 2600+, nvidia fx5600, nv driver.
> I'm running F7 x86_64, with AMD X2 and the latest nVidia driver. I've
> run memtest for hours
2 be sure: overnight or whole weekend.
I'm experience with this too but at very rare occurrence, but that
usually about X server that push CPU to almost 100% working. The machine
still available trough ssh and I must kill the X server and gdm bring
back again.
I think the freeze usually is about the kernel or X server. Maybe you
can try with nv driver for video and if still freeze you can check your
computer availability from network for searching who's the cause
freezing.
What I'm experiencing is not just X server freeze. It's something
more serious. I cannot ssh to it. Cannot even ping it. Have to do a
hard reset.
If you can manage a 3x wire DB9F-DB9F serial crossover cable, and put
the console commands to the grub kernel line, then a second computer may
just catch what goes wrong {in my case it then performed flawlessly for
21 days}.
DaveT.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
