Achim Gratz composed on 2015-05-19 20:00 (UTC+0200):

With the latest update from Tumbleweed the machine crashes in drm_radeon or drm_kvm_helper (if I could glean these correctly) with a recursive page fault when the boot process tries to initialize the radeon module. This happened before systemd switched the journal to disk, so I can't look at any logs. I can still boot with the 4.0.1 kernel on that installation although I'm currently having trouble getting a stable X display past the kdm screen. That happened before with this card, an RV350, and seems to be related to the pixel clock PLL not locking.

I've had multiple ATI cards from that era go bad. You might have a hardware failure in progress that manifests only when previously un- or little-used functionality is put to use. Why kernel-pae instead of kernel-desktop? I have two rv370 cards working normally in TW with kernel-desktop-4.0.3, a Radeon X600 on 64 bit and KDE5, and a FireGL on 32 bit and KDE 5. On both I have compositing disabled globally. Maybe disabling compositing would be telling for you. Here's how I do it: /etc/X11/xorg.conf.d/70-extensions.conf: Section "Extensions" Option "Composite" "Disable" EndSection -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Tue, 19 May 2015 20:00:19 +0200 Achim Gratz пишет:

With the latest update from Tumbleweed the machine crashes in drm_radeon or drm_kvm_helper (if I could glean these correctly) with a recursive page fault when the boot process tries to initialize the radeon module.

You can blacklist module and load it manually later, after boot is finished.

This happened before systemd switched the journal to disk, so I can't look at any logs. I can still boot with the 4.0.1 kernel on that installation although I'm currently having trouble getting a stable X display past the kdm screen. That happened before with this card, an RV350, and seems to be related to the pixel clock PLL not locking.

Regards, Achim.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 19.05.2015 um 20:00 schrieb Achim Gratz:

With the latest update from Tumbleweed the machine crashes in drm_radeon or drm_kvm_helper (if I could glean these correctly) with a recursive page fault when the boot process tries to initialize the radeon module.

This is a kernel problem => openSUSE kernel. Since you see "4.0.3 crashing, 4.0.1 working", it should be pretty easy to: * clone the stable kernel git repo * build your own 4.0.3 kernel with SUSE config * see it crash * git bisect and find the offending commit. I also have a machine with such a card at home, but building kernels on an 1.8GHz Dothan machine is not funny, and my interest in this bugfix is not very high :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org