http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c1 --- Comment #1 from Klaus Kämpf --- Created attachment 744232 --> http://bugzilla.suse.com/attachment.cgi?id=744232&action=edit startx log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c3 --- Comment #3 from Klaus Kämpf --- Scratch the lspci info from the last comment, this one's better:

lspci 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05a4 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f7800000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c5 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkaempf@suse.com, | |msrb@suse.com Assignee|xorg-maintainer-bugs@forge. |msrb@suse.com |provo.novell.com | Flags| |needinfo?(kkaempf@suse.com) --- Comment #5 from Michal Srb ---

From the stacktrace it looks like it could be some problem with PRIME (multi GPU support). From the X log it looks like you also have some AMD card in your computer: PCI: (0:0:2:0) 8086:0412:1028:05a4 rev 6, Mem @ 0xf7800000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64 PCI:*(0:1:0:0) 1002:6611:1028:210b rev 0, Mem @ 0xe0000000/268435456, 0xf7c00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072

Is there also AMD GPU in the computer? (In reply to Klaus Kämpf from comment #2)

...

rpm -qf /usr/bin/X xorg-x11-server-1.19.3-5.1.x86_64

The newest version in Tumbleweed is 1.19.4. I don't see any related fixes in 1.19.4, but it is worth trying.

...

rpm -q xf86-video-intel xf86-video-intel-2.99.917+git781.c8990575-1.1.x86_64

Strange that it is installed, but X server is failing to find it. There seem to be some other discrepancies between versions: [ 68920.106] (II) Module modesetting: vendor="X.Org Foundation" [ 68920.106] compiled for 1.19.4, module version = 1.19.4 ^^^^^^ Please make sure you have up-to-date X server and all drivers. If the crash still happens, please attach coredump as well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c7 --- Comment #7 from Klaus Kämpf --- (In reply to Klaus Kämpf from comment #6)

...

There seem to be some other discrepancies between versions: [ 68920.106] (II) Module modesetting: vendor="X.Org Foundation" [ 68920.106] compiled for 1.19.4, module version = 1.19.4 ^^^^^^

Huh ? Shouldn't package dependencies prevent this ?

Argh, my bad. Again, I confused remote with local. Remote system is now up to date with

rpm -q xorg-x11-server xorg-x11-server-1.19.4-1.1.x86_64

And the crash is with the AMD GPU

rpm -q xf86-video-amdgpu xf86-video-amdgpu-1.4.0-1.1.x86_64

Background: I used to run with multiple graphics cards and multiple monitors. This setup was running fine with Tumbleweed until Jun/Aug timeframe. Since then, only one card was functioning but not both together. Since last week (Tumbleweed 20171004) X completely refused to start. Just yesterday I detected the core dumps :-/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c9 --- Comment #9 from Michal Srb --- (In reply to Klaus Kämpf from comment #6)

Huh ? Shouldn't package dependencies prevent this ?

Well in theory the different versions should work together as long as they have the same ABI_VIDEODRV_VERSION (they have in this case). Package dependencies only make sure that ABI_VIDEODRV_VERSION of the drivers match the one of X server. But something is broken, so it is worth checking every option, maybe upstream made some changes and forgot to bump ABI_VIDEODRV_VERSION. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c11 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Flags| |needinfo?(kkaempf@suse.com) --- Comment #11 from Michal Srb --- Thank you for the coredump. It seems that fbdev is used for the AMD card and modesetting for the Intel card. When setting up the Intel card, it crashes because the Intel card does not have master set. Afaik it should not even try to set it up that way. This is a bug and I will look into it, but it should not be using those two drivers in the first place. X server is trying to load the proper drivers - intel and ati, but fails to find their files. The drivers come from xf86-video-intel and xf86-video-ati packages. You said that you have xf86-video-intel installed, do you have xf86-video-ati as well? Can you please verify that their files are OK? (rpm -qV xf86-video-intel xf86-video-ati) If the files are there, could you record strace of X server so we know why is it failing to find their files? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c13 --- Comment #13 from Klaus Kämpf --- (In reply to Stefan Dirsch from comment #12)

Also, we had a regression in 1.19.4, which has been addressed again in 1.19.5. Klaus has installed the -amdgpu driver for unknown reasons. It appears to be the wrong driver. Should be -ati instead.

I had no idea which one to install. I did some experiments of installing only one of -amdgpu, -ati, or -intel in the past. To no avail. Also installing xf86-video-ati (alongside xf86-video-intel) lead to the same crash. To be continued next week ... thanks a lot so far ! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c15 --- Comment #15 from Klaus Kämpf --- Looking further (gdb) print pScreen->isGPU $2 = 1 => rrGetScrPriv() returns NULL -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c17 --- Comment #17 from Klaus Kämpf --- (In reply to Michal Srb from comment #16)

That's why I asked you to:

(In reply to Michal Srb from comment #11)

...

Can you please verify that their files are OK? (rpm -qV xf86-video-intel xf86-video-ati)

If the files are there, could you record strace of X server so we know why is it failing to find their files?

Sorry, I missed this comment. (rpm -qV xf86-video-intel xf86-video-ati) does not return any output. Both packages were re-installed by me after the last TW update. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c19 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kkaempf@suse.com) --- Comment #19 from Stefan Dirsch --- The strace output is a mess, which hardly is readable. Can you please also provide a regular Xorg.0.log with xf86-video-intel xf86-video-ati packages installed? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #744837|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c22 --- Comment #22 from Klaus Kämpf --- Created attachment 744911 --> http://bugzilla.suse.com/attachment.cgi?id=744911&action=edit Xorg.0.log after removal of xf86-video-vesa Hmm, "no screens found" if I remove xf86-video-vesa. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #744911|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c25 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kkaempf@suse.com) | --- Comment #25 from Klaus Kämpf --- Created attachment 744927 --> http://bugzilla.suse.com/attachment.cgi?id=744927&action=edit lsmod -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c27 --- Comment #27 from Stefan Dirsch --- (In reply to Klaus Kämpf from comment #24)

(In reply to Michal Srb from comment #23)

...

Alright, now the situation looks bit different. Both the strace and the logs in comment 20 and comment 22 show that the xf86-video-ati is found and loaded. However, it fails to initialize and in case of comment 20 it fallbacks to VESA, in case of comment 22 it has no options left and terminates.

Why doesn't it fall back to the intel card ?

Good question. It's yet another bug I would say. But please let's concentrate now on why radeon KMS support isn't working, please. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c29 --- Comment #29 from Stefan Dirsch --- Our kernel config for openSUSE:Factory [...] CONFIG_DRM_AMDGPU_SI=y [...] This explains a lot! I want this change reverted! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c31 --- Comment #31 from Stefan Dirsch --- Klaus, can you confirm, that this kernel option is also set on your system? zcat /proc/config.gz | grep DRM_AMDGPU_SI -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c33 --- Comment #33 from Klaus Kämpf --- (In reply to Stefan Dirsch from comment #28)

For some reason amdgpu instead of radeon KMS driver is loaded and apparently does not work, not even with generic modesetting X driver it seems. Please try these kernel options.

radeon.si_support=1 amdgpu.si_support=0

No, this does not improve the situation. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c35 --- Comment #35 from Klaus Kämpf --- When I re-install xf86-video-vesa, I'm back at the segfault in RRSetChanged() -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c36 --- Comment #36 from Michal Srb --- I think the "radeon.si_support=1 amdgpu.si_support=0" options are the default. These lines are in the kernel log: amdgpu 0000:01:00.0: enabling device (0000 -> 0003) amdgpu 0000:01:00.0: SI support provided by radeon. amdgpu 0000:01:00.0: Use radeon.si_support=0 amdgpu.si_support=1 to override. They come from the amdgpu_driver_load_kms function. They get printed out if amdgpu detected that the card is too old and should be handled by radeon driver. It then returns -ENODEV and the amdgpu driver is not used. It suggests the opposite parameters that would disable radeon and enable amdgpu for this card, but that is experimental and we don't want that. I think that disabling the CONFIG_DRM_AMDGPU_SI will just remove the option to opt-in for this experimental support. It seems to me that amdgpu puts its hands away from the card correctly. What I don't understand is why the radeon driver doesn't get used for it after that. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c38 --- Comment #38 from Klaus Kämpf --- Created attachment 744955 --> http://bugzilla.suse.com/attachment.cgi?id=744955&action=edit dmesg "before" (no additional kernel parameters) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c40 --- Comment #40 from Klaus Kämpf --- Created attachment 744959 --> http://bugzilla.suse.com/attachment.cgi?id=744959&action=edit Xorg.0.log With the radeon module loaded, startx succeeds (amd card only). Xorg.0.log attached. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c42 --- Comment #42 from Klaus Kämpf --- Well, X starts, but it's unusable (horrible flickering) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c43 --- Comment #43 from Stefan Dirsch --- (In reply to Klaus Kämpf from comment #39)

Created attachment 744956 [details] dmesg "after" (no additional kernel parameters)

[ 105.932494] radeon 0000:01:00.0: Invalid PCI ROM data signature: expecting 0x52494350, got 0xe808aa55 [...] [ 106.123771] radeon 0000:01:00.0: failed VCE resume (-110). Hmm. Something sounds wrong here. Maybe kernel-firmware is not installed or outdated or whatever. Or even hardware is broken. Could you verify, that the graphics card's fan is still rotating? ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c45 --- Comment #45 from Klaus Kämpf --- (In reply to Stefan Dirsch from comment #44)

Honestly, if it's possible in Firmware/BIOS to disable Intel card, I would like to know whether the radeon cards works during boot.

Yes, actually both cards work during boot and show boot log messages (first the ati card, then kernel logging switches to the intel card surprisingly). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c47 --- Comment #47 from Klaus Kämpf --- (In reply to Stefan Dirsch from comment #44)

Honestly, if it's possible in Firmware/BIOS to disable Intel card, I would like to know whether the radeon cards works during boot.

I can't disable a card, but I can configure the primary display in the BIOS. If I choose the ATI card, kernel messages appear on the ATI displays (2 monitors are attached to the ATI card) during boot up to a specific point where the kernel switches message output to the Intel display. The GDM login appears on the ATI displays. But it's unusable due to flickering. If I choose the Intel card, all kernel messages appear on the Intel card. The ATI displays stay completely dark. Running "startx" provides a GNOME desktop on the Intel display. But it's unusable due to flickering. ==> Both cards work separately. I can choose the card via BIOS setting. The actual desktop is broken for both cards (excessive flickering) though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c49 --- Comment #49 from Klaus Kämpf --- Also, X/GDM stays unusable due to excessive flickering. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|msrb@suse.com |xorg-maintainer-bugs@forge. | |provo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1063139 http://bugzilla.suse.com/show_bug.cgi?id=1063139#c54 --- Comment #54 from Klaus Kämpf --- (In reply to Stefan Dirsch from comment #53)

Klaus, is this still an issue with curent TW?

No, this seems fixed. Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.