FS#7230 - Xorg 7.2 freezes

Attached to Project: Arch Linux
Opened by sinister99 (sinister99) - Monday, 21 May 2007, 21:11 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 05 September 2007, 09:28 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Alexander Baldeck (kth5)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Xorg 7.2 freezes on my computer 2-3 times per day. The task "X" is using 100% of my processor. I can move the mouse, and the display continues to update (time, superkaramba, open im windows), but clicking on anything doesn't do anything, and no windows can be opened even with keyboard shortcuts. It always starts when I am away from the computer, it has never begun while I was working.

I can still SSH into the computer, and I can usually restart X and it works fine. X did work fine for a while, but this issue started in the last month or so, and has gotten more frequent to the point it is a hassle to use the computer.

Processor: Intel Core 2 Duo e6600
Video: Nvidia 6600GT (using nvidia driver)

The computer runs cool, so that is not an issue.
   xorg.conf (14.9 KiB)
   Xorg.0.log (22.6 KiB)
   dmesg (23 KiB)
   lspci (1.5 KiB)
This task depends upon

Closed by  Alexander Baldeck (kth5)
Wednesday, 05 September 2007, 09:28 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#7513 
Comment by Jan de Groot (JGC) - Tuesday, 22 May 2007, 10:47 GMT
Hmm, 2.6.20-ck. Did you try kernel26? Does it freeze with that one?
Comment by Roman Kyrylych (Romashka) - Tuesday, 22 May 2007, 10:57 GMT
I don't know if my issue is related, but:
such freezes happen to me sometimes with no clear reasons (no HDD activity or hard CPU tasks) but only for few seconds (and while I'm working on PC, not when I'm away).
I'm using Beryl on Nvidia on kernel26.
Comment by sinister99 (sinister99) - Tuesday, 22 May 2007, 13:06 GMT
This happens with kernel26 and kernel26ck, this was the original reason I tried ck.
Comment by Alexander Baldeck (kth5) - Tuesday, 22 May 2007, 13:17 GMT
do you run a 32bit system on a 64bit machine? i see you have a "core 2" cpu in your system.
Comment by sinister99 (sinister99) - Tuesday, 22 May 2007, 13:21 GMT
32 bit
Comment by Roman Kyrylych (Romashka) - Tuesday, 22 May 2007, 13:21 GMT
@Alexander: there is Architecture i686 on the left
Comment by Alexander Baldeck (kth5) - Tuesday, 22 May 2007, 13:28 GMT
@Roman: yes but i think the cpu in that system is a Core 2 Duo according to dmesg.
Comment by Roman Kyrylych (Romashka) - Tuesday, 22 May 2007, 13:39 GMT
I don't understand... I don't know how dmesg of i686 and x86_64 systems with Core 2 Duo differ.
I assumed that if i686 is stated then it is i686 on Core 2 Duo. *shrugs*
Comment by sinister99 (sinister99) - Tuesday, 22 May 2007, 13:42 GMT
I could run 64 bit on the Core 2 Duo, but I am using 32 bit at the moment
Comment by sinister99 (sinister99) - Tuesday, 22 May 2007, 17:22 GMT
There was a power surge and my os hard drive got fried despite my surge protector...I don't need this resolved anymore, but I can answer more questions if anyone wants to still follow it...
Comment by Shahar (sweiss) - Wednesday, 23 May 2007, 10:40 GMT
I am having the exact same problem as you describe.
I use a P4 HT cpu.

How did you solve it?
Comment by sinister99 (sinister99) - Thursday, 24 May 2007, 13:55 GMT
I am now running a fresh install of arch on the same computer, and it is still doing the same thing
Comment by Shahar (sweiss) - Friday, 01 June 2007, 07:27 GMT
Well, any ideas for a useful debug output? This bug is driving me nuts..
Comment by Shahar (sweiss) - Friday, 01 June 2007, 07:33 GMT
Some more details:
I've a GeForce FX5200 128mb, and I'm using the proprietary NVidia driver.

My xorg.conf is pretty basic as you can see.
I've basically commented out every option to test if it solves it, without any luck.

I'm using a 32bit Pentium 4 HT Presscot 3.2ghz

If you could use anything else, please let me know.
   xorg.conf (2.7 KiB)
   dmesg.txt (19.1 KiB)
   lspci.txt (1 KiB)
   Xorg.0.log (19.9 KiB)
Comment by sinister99 (sinister99) - Sunday, 03 June 2007, 13:57 GMT
I just tried upgrading to xorg-server 1.3, and I am still having this issue.
Comment by sinister99 (sinister99) - Monday, 18 June 2007, 12:09 GMT
I spoke with NVIDIA
Comment by sinister99 (sinister99) - Monday, 18 June 2007, 12:11 GMT
about this problem, and they told me to do a bunch of stuff. Nothing worked including their beta driver, which is apparently the only driver they support. I think I may just be SOL. I'm going to try the nv driver now.
Comment by Urs Wolfer (uwolfer) - Friday, 29 June 2007, 08:24 GMT
See also this issue:
http://bugs.archlinux.org/task/7513
Comment by Greg Meyer (oggb4mp3) - Monday, 30 July 2007, 12:53 GMT
I completely worked around this problem by not using superkaramba. I don't think it is so much a superkaramba bug as it is superkaramba triggering a bug in xorg/xorg-server/video drivers. I know it is not a fix, but I needed to get a stable desktop again.
Comment by sinister99 (sinister99) - Monday, 30 July 2007, 13:30 GMT
I have had this problem without using superkaramba
Comment by sinister99 (sinister99) - Monday, 30 July 2007, 22:24 GMT
I have had this problem without using superkaramba