https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c2 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|trenn@suse.com |tittiatcoke@gmail.com --- Comment #2 from Stefan Dirsch 2012-06-28 12:32:14 UTC --- Looking at the library deps of plymouth it seems to talk to libdrm directly. Reassigning to maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c4 --- Comment #4 from Thomas Renninger 2012-06-28 13:09:10 UTC --- I can still log into the machine via ssh. I tried i915_modeset=0, removed splash=silent boot options, without luck. As soon as graphics are tried to get initialized, the screen stays black. Please ping me and I can provide ssh login for someone to debug this (company internal only of course). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c6 --- Comment #6 from Stefan Dirsch 2012-06-28 13:11:53 UTC --- Yes, please give me ssh access. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c9 --- Comment #9 from Stefan Dirsch 2012-06-28 15:53:36 UTC --- I don't see such an assertion when running plymouthd on this machine with this kernel running. I didn't try to boot the original 12.2 kernel, since I'm not familiar with configuring grub2. :-( There seem to be different renderers available for plymouth: drm, fb and text. Maybe we should use fb also for drm drivers since they provide also a generic fb interface. Just an idea, if we can't really debug that issue and it's easily and reliably fixed that way. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c11 --- Comment #11 from Stefan Dirsch 2012-06-28 16:39:31 UTC --- Indeed. That would perfectly match! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c13 --- Comment #13 from Stefan Dirsch 2012-06-28 19:06:34 UTC --- I need to confirm what Takashi has written on any Ivybridge laptop I've tried so far. Just that I couldn't find out that Plymouth is the culprit here. So besides from adding the libdrm patch back to my proposal of comment #9? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c15 --- Comment #15 from Takashi Iwai 2012-06-29 10:04:13 UTC --- OK, below is xorg.log. The highlight is: [ 313.536] drmOpenDevice: node name is /dev/dri/card0 [ 313.536] drmOpenDevice: open result is 9, (OK) [ 313.536] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 313.536] drmOpenDevice: node name is /dev/dri/card0 [ 313.536] drmOpenDevice: open result is 9, (OK) [ 313.536] drmOpenByBusid: drmOpenMinor returns 9 [ 313.536] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [ 313.536] drmOpenByBusid: drmGetBusid reports [ 313.536] drmOpenDevice: node name is /dev/dri/card1 [ 313.540] drmOpenByBusid: drmOpenMinor returns -1 [ 313.540] drmOpenDevice: node name is /dev/dri/card2 [ 313.544] drmOpenByBusid: drmOpenMinor returns -1 [ 313.544] drmOpenDevice: node name is /dev/dri/card3 [ 313.548] drmOpenByBusid: drmOpenMinor returns -1 [ 313.548] drmOpenDevice: node name is /dev/dri/card4 [ 313.552] drmOpenByBusid: drmOpenMinor returns -1 [ 313.552] drmOpenDevice: node name is /dev/dri/card5 [ 313.556] drmOpenByBusid: drmOpenMinor returns -1 [ 313.556] drmOpenDevice: node name is /dev/dri/card6 [ 313.560] drmOpenByBusid: drmOpenMinor returns -1 [ 313.560] drmOpenDevice: node name is /dev/dri/card7 [ 313.564] drmOpenByBusid: drmOpenMinor returns -1 [ 313.564] drmOpenDevice: node name is /dev/dri/card8 [ 313.568] drmOpenByBusid: drmOpenMinor returns -1 [ 313.568] drmOpenDevice: node name is /dev/dri/card9 [ 313.572] drmOpenByBusid: drmOpenMinor returns -1 [ 313.572] drmOpenDevice: node name is /dev/dri/card10 [ 313.576] drmOpenByBusid: drmOpenMinor returns -1 [ 313.576] drmOpenDevice: node name is /dev/dri/card11 [ 313.580] drmOpenByBusid: drmOpenMinor returns -1 [ 313.580] drmOpenDevice: node name is /dev/dri/card12 [ 313.584] drmOpenByBusid: drmOpenMinor returns -1 [ 313.584] drmOpenDevice: node name is /dev/dri/card13 [ 313.587] drmOpenByBusid: drmOpenMinor returns -1 [ 313.587] drmOpenDevice: node name is /dev/dri/card14 [ 313.591] drmOpenByBusid: drmOpenMinor returns -1 [ 313.591] drmOpenDevice: node name is /dev/dri/card15 [ 313.594] drmOpenByBusid: drmOpenMinor returns -1 [ 313.594] drmOpenDevice: node name is /dev/dri/card0 [ 313.594] drmOpenDevice: open result is 9, (OK) [ 313.594] drmOpenDevice: node name is /dev/dri/card0 [ 313.594] drmOpenDevice: open result is 9, (OK) [ 313.594] drmGetBusid returned '' [ 313.594] (EE) intel(0): [drm] failed to set drm interface version. [ 313.594] (EE) intel(0): Failed to become DRM master. [ 313.594] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 313.594] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 313.594] (==) intel(0): RGB weight 888 [ 313.594] (==) intel(0): Default visual is TrueColor [ 313.594] (II) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2) [ 313.594] (--) intel(0): Chipset: "Ivybridge Mobile (GT2)" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c17 --- Comment #17 from Takashi Iwai 2012-06-29 10:54:26 UTC --- It seems that the hang up on my test machine isn't directly related with drm (although the error messages above look scary). When you start X manually while plymouth is showing a splash, it could be started well. However, if you do "chvt 1; chvt 7", then it returns back to plymouth splash screen instead of X. Then, even after you hide the plymouth screen or kill plymouthd, X never gets back to the normal state. (Following "kill -HUP X" restores the visual but the inputs are gone.) So, there could be an issue with VT handling in addition. I guess we should test the newer version of plymouth at this moment instead of wasting too many efforts for debugging the old version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c19 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@suse.com --- Comment #19 from Thomas Renninger 2012-06-29 11:07:34 UTC ---

In the meantime we have version 0.8.5.1 available, but I am not sure if Coolo would allow any version update for 12.2. Adding him. Most interesting comments: #12, #13. Eh this is plymouth version, but the libdrm is broken as well?

The fact that HW has to be whitelisted or otherwise the installation will hang sounds like a serious design issue. Is there any workaround to get around the HW dependencies? Can I get things working with some kind of userspace program or kernel parameter or whatsoever quick fix (without recompiling/packaging)? I tried plymouth-0.8.5.1 and thanks to Stefan I could give a patches libdrm version a try: plymouth 0.8.5.1: fixes: splash screen working early (did not before) with and without i915_modeset=0 (didn't work at all before) fixed libdrm version from Stefan: X comes up (does not with old or new plymouth version (X also throughs the assert failure message shown in the title like: X: intel_bufmgr_gem.c:2783: drm_intel_bufmgr_gem_init: Assertion `0' failed. Summary: At least two bugs in different packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c21 --- Comment #21 from Raymond Wooninck 2012-06-29 11:41:16 UTC --- Thomas, In Base:System we have now two packages that provide the same files. Initially the plymouth integration came from systemd and was provided with systemd-plymouth. With the latest version of plymouth, the integration with systemd has been moved to the plymouth package itself. Therefore I packaged this temporarily in plymouth-systemd. This package has some provides/obsoletes on the systemd-plymouth package. I guess for the moment, the best way would be to delete the systemd integration inside plymouth and to keep it where it is now. Unfortunately fcrozat is not online in IRC, but this way we would prevent changes to systemd as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c23 --- Comment #23 from Thomas Renninger 2012-06-29 12:16:37 UTC ---

I guess for the moment, the best way would be to delete the systemd integration inside plymouth and to keep it where it is now. If still anyhow possible I would add the plymouth's systemd files into plymouth and remove them from systemd. This is how things should look like later, right?

Now you can still do that. Once 12.2 is released, one has to take a lot extra care to check the update case 12.2 -> 12.X if systemd plymouth files should get moved to where (I expect) they belong to (plymouth package). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c25 --- Comment #25 from Takashi Iwai 2012-06-29 12:28:17 UTC --- I tried plymouth-0.8.5 from Base:System, but the hang still occurs at the same place. systemd-plymouth isn't updated. Before update: # rpm -qa | grep plymouth plymouth-plugin-label-0.8.4-11.1.x86_64 plymouth-scripts-0.8.4-11.1.noarch plymouth-plugin-script-0.8.4-11.1.x86_64 plymouth-0.8.4-11.1.x86_64 systemd-plymouth-44-8.1.x86_64 plymouth-branding-openSUSE-0.8.4-11.1.noarch After upadate: # rpm -qa | grep plymouth plymouth-0.8.5.1-75.1.x86_64 plymouth-plugin-label-0.8.5.1-75.1.x86_64 plymouth-scripts-0.8.5.1-75.1.noarch systemd-plymouth-44-8.1.x86_64 plymouth-branding-openSUSE-0.8.5.1-75.1.noarch plymouth-plugin-script-0.8.5.1-75.1.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c27 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|sndirsch@suse.com | --- Comment #27 from Takashi Iwai 2012-06-29 12:39:36 UTC --- (In reply to comment #26)

Takashi,

Updating plymouth alone does not resolve the issue described here. The systemd-plymouth package doesn't require to be updated as that this has nothing to do with starting plymouth (as this is done within the initrd).

I assume that you are missing the patches for libdrm.

No, you miss the point that plymouth itself is always working (showing splash) on my machines. Although it's IvyBridge, but it's a different chip variant. The problem on all of my test installations is that X hangs up when plymouth is running. It's a different problem from libdrm. Possibly some VT-handling issue. The problem happens even if you remove drm rendering plugin from plymouth. Actually I also updated libdrm now, but the problem still remains. So, there are basically three things we are facing: 1. IVY-S GT2 is missing in libdrm Already fixed in OBS X11:XOrg, and submitted via SRID 126602. (This is the answer to comment 24) 2. plymouth splash doesn't appear on IVY (bnc#769397) Updating plymouth to 0.8.5 fixed on Thomas' machine 3. X hangs up due to plymouth Updating plymouth 0.8.5 doesn't help. Maybe better to open another bug to track the issue 3? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c29 --- Comment #29 from Takashi Iwai 2012-06-29 13:31:53 UTC --- Looks like Ubuntu has the same issue about X and plymouth race (issue 3 in comment 27): https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c31 --- Comment #31 from Bernhard Wiedemann 2012-06-29 16:00:15 CEST --- This is an autogenerated message for OBS integration: This bug (769209) was mentioned in https://build.opensuse.org/request/show/126628 Factory / libdrm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c33 --- Comment #33 from Takashi Iwai 2012-06-29 14:07:51 UTC --- Created an attachment (id=496958) --> (http://bugzilla.novell.com/attachment.cgi?id=496958) Patch to quit plymouth properly before starting DM -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c35 --- Comment #35 from Takashi Iwai 2012-06-29 14:18:30 UTC --- It seems that --retain-splash option doesn't give any better result, so better to omit the option. I got some weird VT behavior when I tested this option a few times. Not sure whether it's related with it, though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c37 --- Comment #37 from Bernhard Wiedemann 2012-06-29 21:02:21 CEST --- This is an autogenerated message for OBS integration: This bug (769209) was mentioned in https://build.opensuse.org/request/show/126666 Factory / xdm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c39 --- Comment #39 from Takashi Iwai 2012-06-29 19:28:45 UTC --- OK, that explains a lot. FWIW, I've tested xdm and XFCE. It's really a design flaw in plymouth. It should have been integrated better in the session management. Otherwise it breaks X so badly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c41 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #41 from Stefan Dirsch 2012-07-02 13:49:53 UTC --- *** Bug 769416 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=769416 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c43 --- Comment #43 from Takashi Iwai 2012-07-02 14:10:20 UTC --- The KDM/GDM check was already added in FACTORY xdm. Yes, it's possible to fix in /usr/lib/X11/displaymanager/*, but in that case, you must add "plymouth quit" to each entry. If you forget it, you'll lose the game -- X hangs up, and you cannot see even why, if you have no remote access. Thus I think it's safer to take a white-list approach. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c45 --- Comment #45 from Michal Marek 2012-07-02 14:12:01 UTC --- (In reply to comment #44)

That would require each (new) displaymanager script to have it's own plymouth handling. [...]

This was answer to Frederic's comment 42. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769209 https://bugzilla.novell.com/show_bug.cgi?id=769209#c47 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #47 from Takashi Iwai 2012-07-17 13:36:54 UTC --- xdm package already contains the fix and no longer hang is seen. Let's close the bug now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.