Hang Problem With 10.3 X86_64?

Has anyone noticed a hang problem with 10.3 on x86_64 platforms? I have a dual core Turion x64 that has 10.1, 10.2, and 10.3 installed on it. Only 10.3 hangs unpredictably - most often when gaming, but also when the system is heavily loaded (KDE can hang). I thought maybe it was the install, but I just reinstalled and it hung the first time I played ut2004 - haven't had it installed long enough to see if it will hang in KDE on this install... I haven't seen a hang with 10.1 or 10.2 on this machine (nVidia 7300 video, sata+pata drives, 2GB RAM, Turion4400+, BioStarT-series Mobo) so the hardware is basically OK. Could it have anything to do with the relabeling of drives? (In 10.2 PATA drives were called hdaX whereas not they're called sdaX just like SATA drives.)

Patti

Has anyone noticed a hang problem with 10.3 on x86_64 platforms? I have a dual core Turion x64 that has 10.1, 10.2, and 10.3 installed on it. Only 10.3 hangs unpredictably - most often when gaming, but also when the system is heavily loaded (KDE can hang). I thought maybe it was the install, but I just reinstalled and it hung the first time I played ut2004 - haven't had it installed long enough to see if it will hang in KDE on this install... I haven't seen a hang with 10.1 or 10.2 on this machine (nVidia 7300 video, sata+pata drives, 2GB RAM, Turion4400+, BioStarT-series Mobo) so the hardware is basically OK. Could it have anything to do with the relabeling of drives? (In 10.2 PATA drives were called hdaX whereas not they're called sdaX just like SATA drives.)

Patti
[/b]

Yes, I have the same thing happening. After a heavy load it hangs.

Bakerue

Same problem here. I can't find any source for the hang - nothing in the log and it crashes in random situations

My config:
Asus P5K motherboard
Intel C2 Duo E6750
Asus EN8800 GTS 320MB
4X1 GB KINGSTON HyperX DDR2-800 Mhz
Fortron Bluestorm II 500 W
OpenSuse 10.3 x86_64 with the updated kernel 2.6.22.13 with atl1 driver from 2.6.23, because I found I topic stating that the old driver can cause system crash when network is under heavy load

Same problem here with system hangs on x86_64 install of opensuse 10.3

mobo is Asus M2A-VM with AMD Athon X2 64 +4000. The HCL shows the mobo is works w/ 10.3. Not sure what the problem is and it even hangs when trying to perform the online update! I hope there's a fix.

Has anyone noticed a hang problem with 10.3 on x86_64 platforms? I have a dual core Turion x64 that has 10.1, 10.2, and 10.3 installed on it. Only 10.3 hangs unpredictably - most often when gaming, but also when the system is heavily loaded (KDE can hang). I thought maybe it was the install, but I just reinstalled and it hung the first time I played ut2004 - haven't had it installed long enough to see if it will hang in KDE on this install... I haven't seen a hang with 10.1 or 10.2 on this machine (nVidia 7300 video, sata+pata drives, 2GB RAM, Turion4400+, BioStarT-series Mobo) so the hardware is basically OK. Could it have anything to do with the relabeling of drives? (In 10.2 PATA drives were called hdaX whereas not they're called sdaX just like SATA drives.)

Patti
[/b]

Similar problem here with the MSI board. It is infrequent and hard to identify.

I have some problems with my NTFS partitions, so they are not currently mounted by NTFS - 3G and OpenSuse haven't crash for two or three days. Does any of you guys use NTFS - 3G and does OpenSuse crash when you are using some files from NTFS partiton(or a background task doing this - in my case KTorrent)?

I have noticed it too especially when i try to run amarok!!!! the system hung and becomes very edgy!! i have a laptop with AMD turionx2 TL-50 2g of ram kingstone 533 mzh and 120g
HDD

Update the bios to the latest version. Do a memory-check.

I also have just installed Suse 10.3 x86_64 on an AMD +3000 (2ghz) 1Gig Mem, ATI Radeon 9250 256MB

I can reproduce this 'TOTAL HANG' usually just by launching Firefox.

The X server pegs the CPU @ 99.9%

I run Solaris 10/Sparc on my home network, and I can ssh into the SUSE box, run commands at the command line, but on the SUSE PC, it's 100% locked up.

Here's the output of the top command

top - 16:23:28 up 33 min, 3 users, load average: 1.00, 1.01, 0.88
Tasks: 72 total, 3 running, 69 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us,100.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1028772k total, 444088k used, 584684k free, 20092k buffers
Swap: 2104472k total, 0k used, 2104472k free, 317992k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2677 root 25 0 255m 24m 11m R 99.8 2.4 22:08.00 X

# ps -ef | grep X
root 2677 2648 74 15:50 tty7 00:31:08 /usr/bin/X :0 -audit 0 -br -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
# pkill -9 X
# pkill -9 X
# kill -9 2677
# kill -9 2677
# kill -9 2677
# kill -9 2677
ps -ef | grep X
root 2677 2648 74 15:50 tty7 00:31:08 /usr/bin/X :0 -audit 0 -br -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7


[edit] Tried to kill gdm also, no difference, still locked up

I can not kill the X server, even with a -9. My only recourse is to reboot, this really sukz!

I tried
# init 2
And still, the system is totally locked up, only remote access is available.

Me thinks SUSE 10.4 x86_64 will be needed very very soon! Time to free up that partition space for something else

Funny, I run 10.3 almost from the day it came out, and I never had problems like this. Must be something special with your installation, not a general problem with 10.3.

Edit: I don't have an ATI-card. Maybe it's something wrong with this.