| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 25 Nov 2011 14:33:51 -0600 From: Bob Tracy <rct@...rkin.frus.com> To: linux-kernel@...r.kernel.org Cc: airlied@...ux.ie Subject: [BUG] 3.2-rcX radeon KMS system freeze I've been trying to get KDE4 running on an Alpha, and I have things to the point where FreeNX (non-KMS) KDE4 sessions work just fine. When I try a KDE4 session on the console with 3.2-rc[1-2] kernels and KMS enabled, the KDE4 splash screen appears, and the expected left-to-right fade-in of the five startup progress icons happens. As soon as the fifth icon (the big "K") is done appearing, I assume plasma-desktop starts, and that's where the system locks-up solid. Can't switch virtual consoles, can't login remotely, etc.: system doesn't even respond to pings. Have to hit the reset switch to recover. After rebooting, there's nothing to be found in any of the X11 and/or syslog files as far as "Oops" messages or other errors. Similar bad things happen when I try to test Gnome-3 sessions (KMS required for non-fallback mode). With FreeNX, the best I can do is test Gnome-3 fallback mode (Gnome-2). Apologies for the less-than-useful bug report. If there's anything I can do to generate/capture more diagnostic info, please don't hesitate to let me know. I'll be able to try a 3.2-rc3 kernel later today. --Bob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists