| Summary: | trying to enable desktop effects freezes computer | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Defunct user <m.foulkes> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | m.foulkes, nathan.thomas |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Xorg.0.log.old | ||
|
Description
Defunct user
2009-05-28 21:50:07 UTC
in general if X freezes it's an X bug, not a kwin. The fact that it works with Compiz does not say anything as it seems that driver developers test only with Compiz. It would be useful to have a crash report or output of /var/log/Xorg.*.log if there is something useful. If possible: are you able to ssh to the freezed system and collect some information? Created attachment 34085 [details]
Xorg.0.log.old
As I said in my original report, I cannot ssh in to the frozen machine;
I cannot even ping it. The whole machine is dead.
Here is the Xorg.0.log.old file immediately after the reboot following the
freeze. There doesn't seem to be much there, unfortunately. The other log
files are also uninformative.
If you tell me how to get a crash report from a frozen machine I'll try.
I thought this might be an X problem, but the Debian KDE maintainer who
answered my original bug report asked me to report it to the KDE bug
tracking system.
(In reply to comment #2) > Here is the Xorg.0.log.old file immediately after the reboot following the > freeze. There doesn't seem to be much there, unfortunately. The other log > files are also uninformative. > > If you tell me how to get a crash report from a frozen machine I'll try. That will be difficult. But I can't see how we will be able to find anything useful to solve this bug or even to decide if it is a kwin bug (which I doubt). as kwin and compiz use different implementations, thus likely different GL and maybe Render calls it's not /that/ strange. still a bug.
this however sounds like a kernel halt -> i just blame ati kernel module ;-)
did you try the other driver(s) - like fglrx and radeonhd or whatever is the amd/ati choice de toujours?
(it might stumble on concurrent GL and XRender calls that try to operate on the same HW)
last resort:
does alt+sysreq + "busier" work**? (sysreq is most likely the "print" key, and DON'T FORGET: busier is to be typed backwards, "REISUB", and wait some seconds between the keystrokes)
if not: many distros enable it on "kernel.sysrq = 1" in /etc/sysctl.conf
this should allow you to get a coredump ('c', like restart kexec and crashdump, rather than 'b' reBooot)
if you don't know what this is at all, google* first and better be no absolute n00b ;-)
*or just read this:
http://en.wikipedia.org/wiki/System_request
and
http://en.wikipedia.org/wiki/Magic_SysRq_key
you want to print the second page - like on PAPER (or have a second machine...)
**kids: don't do that at home =P
I am using the X.org radeon driver, which as far as I know is the only option for Radeon 9200 cards. The radeonhd driver only supports newer hardware (R500 and above). Recent versions of the proprietary fglrx driver no longer support the 9200. I had already tried "Alt-SysRq reisub", but tested it again just to make sure. When the machine is running normally it causes a reboot as expected, but it has no effect when the machine is frozen. The kernel seems completely dead. Is there anything else I can do? (In reply to comment #5) > I had already tried "Alt-SysRq reisub", but tested it again just to make sure. > When the machine is running normally it causes a reboot as expected, but it has > no effect when the machine is frozen. The kernel seems completely dead. hmmm. maybe just the usb subsystem? can you try replacing the (usb?) keyboard with a ps/2 one? (iff you still have such io ports) i don't however know if this could help anything. (just guessing around) > Is there anything else I can do? file a bug to ati/amd or the radeon(hd) kernel/X11 driver devs. userspace procs are not supposed to do such on your kernel. ever. you could also run kwin in gdb, set a breakpoint on the composite check and step on, but that's not precisely your job... last: google suggested to lower the agp speed to 4x, but again: that's just some random guessing :-( The computer has a ps/2 port but I don't have a ps/2 keyboard. I doubt ATI/AMD will be able to help, but some time within the next few days I'll file a bug with the X.org radeon driver developers. They'll probably blame KDE. Debugging kwin with gdb is beyond me. I have already tried changing the AGP speed and aperture, but it didn't help. There may be a magic combination of BIOS and xorg.conf settings that works, but there were too many combinations to try. Crashing my main work computer again and again cannot be good for it. I guess I'll have to live without desktop effects. I wouldn't mind if I could figure out how to switch desktops using only the keyboard. Any hints? ctrl+F[1-n] (by default) and iff the kernel halts (and in particular in a certain module), that's /not/ any userspace apps problem, and even more /not/ the one of a highly abstracted one like kwin i.e. calling glWhatever() or XRenderWhatever() should not be able even to just segfault X11, and certainly not the kernel - guess what it would mean if every app had to care about: "please do not call this and that together on ati cards - it's ok on intel and nvidia, though - where (on intel) you might not call that and those combination while on nvidia (but just in case of a > G92 chip) you must not call over there... waaaAAhhhHH! =D I also encounter this bug on my iBook G4 PowerPc laptop. Like Matthew I am also running KDE 4.2.2 on Debian testing, and also use an ATI graphics card (though mine's a Mobility Radeon 9550). Not only does enabling the desktop effects crash the system, but the screen also goes a nice shade of purple with vertical lines. Again, the system will not respond to keyboard input: hard reboot is the only option. If other Debian testing users aren't affected by this bug, I'm guessing it must be a problem with the radeon driver and/or older radeon graphics cards. Nathan This bug has been fixed: I discovered yesterday that kde desktop effects now work on my machine, as long as the firmware-linux package is installed. If firmware-linux is not installed KDE refuses to use compositing and does not explain why, but the machine no longer freezes. I do not know which of the many debian testing updates since May cured the problem (and it would be hard to find out), but guess it was the switch to kde 4.3 or xorg 7.4. As far as I am concerned this bug is now closed. (In reply to comment #10) > As far as I am concerned this bug is now closed. Seems to be fixed, if it occurs again please reopen |