desktop freeze with kwin desktop effects on Radeon X600 and X1600

Bug #368461 reported by 3ntix
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Expired
Low
Unassigned

Bug Description

I've a fresh install of Kubuntu 9.04. I use kubuntu almost on default settings (desktop effects activated) and sometimes the desktop becomes black (the LCD backlight switch off!!!) and I've to reset the pc.
I use a notebook, Toshiba M50-140 and I've attacched the lspci -vv.
I don't found anything interesting in the log, just too much lines at the end of Xorg.0.log.old (the old when pc freeze):
...............
(II) PS/2 Mouse: Found 3 mouse buttons
(II) PS/2 Mouse: Found x and y relative axes
(II) PS/2 Mouse: Configuring as mouse
(**) PS/2 Mouse: YAxisMapping: buttons 4 and 5
(**) PS/2 Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) PS/2 Mouse: (accel) keeping acceleration scheme 1
(**) PS/2 Mouse: (accel) filter chain progression: 2.00
(**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms
(**) PS/2 Mouse: (accel) set acceleration profile 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 0
Unhandled monitor type 0
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 0
(II) RADEON(0): Added native panel mode: 1280x768
(II) RADEON(0): Output: S-video, Detected Monitor Type: 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 0
Unhandled monitor type 0
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 0
(II) RADEON(0): Added native panel mode: 1280x768
(II) RADEON(0): Output: S-video, Detected Monitor Type: 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 0
Unhandled monitor type 0
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 0
(II) RADEON(0): Added native panel mode: 1280x768
(II) RADEON(0): Output: S-video, Detected Monitor Type: 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 0
Unhandled monitor type 0
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 0
(II) RADEON(0): Added native panel mode: 1280x768
(II) RADEON(0): Output: S-video, Detected Monitor Type: 0

[lspci]
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
     Subsystem: Toshiba America Info Systems Device ff00
01:00.0 VGA compatible controller: ATI Technologies Inc M24 [Radeon Mobility X600]
     Subsystem: Toshiba America Info Systems Device ff05

Tags: jaunty kubuntu
Revision history for this message
3ntix (francesco-3ntini) wrote :
Revision history for this message
aya (aya-mega-anime) wrote :

The same thing here on kubuntu 9.04 with desktop effects on (Radeon Mobility X1600).
Sometimes it hangs while loading kde, sometimes after 30 minutes, sometimes after 1 hour...

I had the screen going black and I also had the screen freezing without going black. PC locks completely, so it is not possible to switch to console. The only way out is hard reboot.

The system itself is working. I can ssh to it from another PC.

I am using opensource xserver-xorg-video-radeon since fglrx became unavailable for my card.

Revision history for this message
jtholmes (jtholmes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Unfortunately, we can't fix it because your description didn't include enough information.

Next time this happens, can you switch to a text console by hitting
CTRL + ALT + F1, login there, and then run
sudo apport-collect -l linux 368461
then run
sudo killall kdm
and see if the window manager starts back

If the window manager does not come back then
you will have to manually power down and boot again.
thanks

jtholmes (jtholmes)
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
aya (aya-mega-anime) wrote :

The problem is that it is NOT possible to switch to console as I wrote in my previous message. The keyboard would not respond after screen freeze, and CTRL + ALT + F1 would not work. This is of course the first thing I tried after the freeze, but no luck...

Revision history for this message
aya (aya-mega-anime) wrote :

jtholmes, I have just tried to enable the Desktop Effects again, when I click Apply the screen goes to the default b/w wallpaper (the one seen after the login screen). After some time the screen just goes black. Keyboard does not work and network was down too (I could not connect via ssh from another machine).
Please, let me know if you need more logs.

summary: - desktop freeze with kwin desktop effects on Radeon X600
+ desktop freeze with kwin desktop effects on Radeon X600 and X1600
Revision history for this message
aya (aya-mega-anime) wrote : apport-collect data

Architecture: i386
DistroRelease: Ubuntu 9.04
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
aya (aya-mega-anime) wrote :

FYI:
sudo apport-collect -l linux 368461 does not work
apport-collect: error: no such option: -l
So I did it without this option (I don't think that this is the thing you need though...)

A way to reproduce the black screen:

1. Before logging in switch to console CTRL + ALT + F1
2. While in console enable the desktop effects. Edit the file ~/.kde/share/config/kwinrc. In the section [Compositing] make sure that Enabled=true
3. Switch back to graphic screen CTRL + ALT + F7
4. Log in
5. Run skype
6. Without logging in to skype right-click on the skype icon and choose Options
At this place my screen goes black immediately - this worked two times for me but on the third I could open Options dialog without screen freezing. However, when I tried to type in my skype password the screen froze again.

Revision history for this message
jtholmes (jtholmes) wrote :

Could you please take time to file out the following
information and add it to the bug report.

If something does not apply leave it blank.
Some are yes/no (ex: using wireless).
For instance if you are using Wirless and answer
yes, then ignore wired, etc.

kernel version:
Graphics Chip Mfgr:
Graphics Chip Model:
File System Type for /:
Is this problem on a Laptop:
Laptop mfgr:
Laptop model:

Is this problem on a Desktop:
Desktop mobo mfgr:
Desktop mobo model:

using wireless:
ethernet card driver:

using wired:
ethernet card driver:

bios mfgr:
using Compiz:
using Kde:
using Gnome (metacity):

Much of the above information can be obtained from the command
   lspci -vvv

Thanks in advance

Revision history for this message
aya (aya-mega-anime) wrote :

Here you go:

kernel version: 2.6.28-11-generic #42-Ubuntu SMP
Graphics Chip Mfgr: ATI Technologies Inc
Graphics Chip Model: M56P [Radeon Mobility X1600]
File System Type for /: ext4
Is this problem on a Laptop: yes
Laptop mfgr: HP Compaq
Laptop model: nx9420

using wireless: no

using wired: yes
ethernet card driver: tg3

bios mfgr: Hewlett-Packard
using Compiz: No
using Kde: Yes (Compositing)
using Gnome (metacity): No

The full output of lspci -vvv is attached for your reference. Thank you
Please, let me know if you need any more info.

Revision history for this message
jtholmes (jtholmes) wrote :

Excellent reply, thank you.
The developers are working on this to try and find the problem..

thanks again

Revision history for this message
3ntix (francesco-3ntini) wrote :

The same is for me: I couldn't collect data because the pc become unavailable at all.
This is my data:

kernel version: 2.6.28-11-generic
Graphics Chip Mfgr: ATI
Graphics Chip Model: Radeon X600 Mobility (RV380)
File System Type for /: ext3
Is this problem on a Laptop: Yes
Laptop mfgr: Toshiba
Laptop model: M50-148

Is this problem on a Desktop: No
Desktop mobo mfgr:
Desktop mobo model:

using wireless: Yes
ethernet card driver: ipw2200

using wired: No
ethernet card driver:

bios mfgr: phoenix (not sure)
using Compiz: No
using Kde: Yes (Compositing active)
using Gnome (metacity): No

Here is the lspci -vvv
Thanks a lot

Revision history for this message
3ntix (francesco-3ntini) wrote :

New crash. But this time X-org had been restarted to kdm login. This time I've found something interesting in the kdm.log (maybe).
Here it is and the Xorg.log and Xorg.log.old...

Revision history for this message
3ntix (francesco-3ntini) wrote :
Revision history for this message
3ntix (francesco-3ntini) wrote :
Revision history for this message
3ntix (francesco-3ntini) wrote :
Revision history for this message
aya (aya-mega-anime) wrote :

Yes, "Unhandled monitor type 0" is quite familiar to me also. My errors are exactly the same.

The crashes are quite sporadic. But I noticed that when the screen goes black the network goes down too, however when the screen just freezes, I can still ssh from another machine and reboot the box safely.

But in both cases the keyboard does not respond.

Revision history for this message
aya (aya-mega-anime) wrote :

I think this bug is most likely the duplicate of #348332 and #351990.

After I installed kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.2/ all problems with compositing are gone. It has been 4 hours since I enabled Desktop effects and so far so good.

Revision history for this message
3ntix (francesco-3ntini) wrote :

In my experience I've see tree types of freeze:
(1) system freeze, the screen propose the last seeing, the mouse can move, pc don't respond with keyboad, ssh on (and safely reboot). This behaviour is related to bug #351990
(2) the screen become black and the pc don't respond at all: no mouse, no keyboard, no ssh (hard reboot). This is related to bug this bug
(3) just a crash of kdm. Then I can login into kdm-login-interface and the pc is up. As I've reported before, on kdm.log I've found this backtrace:
*** glibc detected *** /usr/bin/X: realloc(): invalid pointer: 0x0c2b29e0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7c94604]
/lib/tls/i686/cmov/libc.so.6(realloc+0x242)[0xb7c99022]
/usr/bin/X(Xrealloc+0x32)[0x8139182]
/usr/bin/X(dixAllocatePrivate+0x103)[0x8072d23]
/usr/bin/X(dixLookupPrivateAddr+0x44)[0x8072e44]
/usr/bin/X[0x817f61f]
/usr/lib/xorg/modules/extensions//libextmod.so[0xb7a04018]
/usr/bin/X(dixDestroyPixmap+0x15)[0x8086d35]
/usr/bin/X(FreeResource+0x10c)[0x8074c3c]
/usr/bin/X(ProcFreePixmap+0x93)[0x8088663]
/usr/bin/X(Dispatch+0x33f)[0x808d57f]
/usr/bin/X(main+0x3bd)[0x80722ed]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7c3b775]
/usr/bin/X[0x80717a1]
======= Memory map: ========
[.....................]

Yesterday I've update my ubuntu with the last updates. I don't see nothing bugfix that could be related to this bug, but at this moment I've no more crash.

Revision history for this message
3ntix (francesco-3ntini) wrote : Fwd: [Bug 368461] Re: desktop freeze with kwin desktop effects on Radeon X600 and X1600

As I speek...
Just when I click to send...freeze :-)
This time the freeze is similar to type (1) but with the difference
that I can switch to the console. I've copied all /var/log/.
I want just to note that sometimes, after the crash, in the dmesg add
some message "[drm] Num pipes: 1" as you can see in kern.log.
I forgot to write that, yesterday I also have installed the
libgl1-mesa-dri-dbg libc6-dbg xserver-xorg-core-dbg
xserver-xorg-video-ati-dbg packages (I don't know how use that
packages, I've just installed) but I haven't found any backtrace...

Revision history for this message
3ntix (francesco-3ntini) wrote : [Bug 368461] Re: desktop freeze with kwin desktop effects on Radeon X600 and X1600
  • kdm.log Edit (947 bytes, application/octet-stream; name="kdm.log")
  • kern.log Edit (470.0 KiB, application/octet-stream; name="kern.log")
  • Xorg.0.log Edit (36.1 KiB, application/octet-stream; name="Xorg.0.log")
  • syslog Edit (2.7 KiB, application/octet-stream; name=syslog)
Revision history for this message
jtholmes (jtholmes) wrote :

two different reporters have confirmed this problem

Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
aya (aya-mega-anime) wrote :

3ntix, I had (1) and (2) types of freezes as you describe them, but never (3).
It has been 2 days since I installed the new kernel, and no freezes for me anymore.

Revision history for this message
aya (aya-mega-anime) wrote :

I had kdm crashing on me just now.

Revision history for this message
Wolfgang Jeltsch (4cqncnl7) wrote :

I have a different kind of crash with KDE. Everything that is displayed disappears (screen goes black) and immediately reappears. So there is just a short flicker. Then the mouse pointer cannot be moved anymore and the system doesn’t respond to key presses.

Revision history for this message
Tomasz Czapiewski (xeros) wrote :

@3ntix,
Yes, I've experienced all three types of crash you've reported and thanks for list them here.

I've got jaunty-proposed and jaunty-backports repos enabled.

I don't remember when I saw the first one last time - it's been mostly reproductable for me by using gnome/gtk or kde3 apps and wine and I could do few crashes in few minutes then but now I use only kde4 apps (with the exception for kde3 k3b) and haven't experienced this bug for a week or so.

For the second bug I haven't experienced more time than the first one (something more than a week (maybe two)).

The third is does occur frequently (something like once a day or once a two days). It's experienced mostly by my wife (she uses firefox, thunderbird, sometimes tvtime - everything on kde 4.2.2 on kubuntu with default enabled desktop effects).

My card is Radeon 9600 AGP 256MB (RV350).

Revision history for this message
Hannu Pulli (h-pulli) wrote :

I have also encountered this problem with fresh install of Kubuntu 9.04 (with updates). The first time the system froze it took some time after enabling desktop effects (about 30 minutes or so) and before that everything worked well. The second time I tried to enable the desktop effects the screen went black instantly with the "no signal" error message flashing back every time the monitor shuts off automatically (normally it just shows the message once and shuts off if there is no signal). As with others the system doesn't respond to keyboard at all after the freeze so no chance of accessing console.

The card is Radeon 9600 AGP 128MB with a DVI monitor.

Revision history for this message
3ntix (francesco-3ntini) wrote :

@Hannu Pulli
This seems to be the feeze type (2) (see my previous post to understand what I talking about). Can you attach your /var/log/Xorg.log, /var/log/Xorg.log.old and /var/log/kern.log on the first reboot just after the crash?
Can you also attach your $lspci -vv and put the output of those command:
- $ dpkg -l xserver-xorg-video-ati
- $ dpkg -l libglu1-mesa
At last, do you have enabled proposed updates?

Revision history for this message
Hannu Pulli (h-pulli) wrote :

Only have the security and recommended updates enabled.

Revision history for this message
Tomasz Czapiewski (xeros) wrote :

I've get yesterday (1) type of freeze (kernel 2.6.28-11-generic and mesa 7.4-0buntu3)
and today (2) type of freeze (on new kernel 2.6.28-12-generic '#43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686 GNU/Linux' and mesa 7.4-0ubuntu3.1 from jaunty-proposed) - today is some minutes since reboot after the upgrade. I was in menu of amarok 2.0.90 (2.1 beta 1 - installed from kubuntu-experimental ppa) - just after choosing 'Sound system configuration'. Now I've done the same thing in amarok and my system didn't freeze.

ATI Radeon 9600 AGP 256MB RV350 on xserver-xorg-video-ati_6.12.1-0ubuntu2

Now I've disabled "DontZap" option in xorg.conf, installed openssh-server and get ready the second machine to try to backtrace on next freezes.

Revision history for this message
Tomasz Czapiewski (xeros) wrote :

And this (2) freeze happened on KDE 4.2.3 from kubuntu-ppa repository so KDE 4.2.3 is not the fix for it either.

Revision history for this message
Scott Emmons (lscotte) wrote :

I've been seeing type (3) X crashes ever since upgrading to 9.04. kdm.log in each case looks like:

*** glibc detected *** /usr/bin/X: realloc(): invalid pointer: 0x0cd1b100 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7cf2604]
/lib/tls/i686/cmov/libc.so.6(realloc+0x242)[0xb7cf7022]
/usr/bin/X(Xrealloc+0x32)[0x8139182]
/usr/bin/X(dixAllocatePrivate+0x103)[0x8072d23]
/usr/bin/X(dixLookupPrivate+0x44)[0x8072ea4]
/usr/lib/xorg/modules//libexa.so(exaPixmapSave+0x37)[0xb7785167]
/usr/lib/xorg/modules//libexa.so[0xb7785d6e]
/usr/lib/xorg/modules//libexa.so(exaOffscreenAlloc+0x22e)[0xb778624e]
/usr/lib/xorg/modules//libexa.so[0xb7785380]
/usr/lib/xorg/modules//libexa.so(exaDoMigration+0x652)[0xb7785ac2]
/usr/lib/xorg/modules//libexa.so[0xb778093b]
/usr/lib/xorg/modules//libexa.so[0xb7782312]

I attached full kdm.log...

Revision history for this message
3ntix (francesco-3ntini) wrote :

Just a new crash of type (1). And nothing reported in Xorg.0.log. There are any news from ubuntu team?

Revision history for this message
jakubcjusz (jakubcjusz) wrote :

I have the same problem on Ati Mobility Radeon Fire GL T2. (On 8.10 works great). The problem is that I can't use any programs that use 3D graphic (for example games). Any chances for a patch?

affects: ubuntu → xserver-xorg-video-ati (Ubuntu)
Bryce Harrington (bryce)
tags: added: kubuntu
Bryce Harrington (bryce)
description: updated
bugbot (bugbot)
tags: added: jaunty
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

3ntix, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-video-ati REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xserver-xorg-video-ati (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers