http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 Ismail Donmez changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|idonmez@suse.com |sreeves@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c4 --- Comment #4 from Donald Curtis --- Created attachment 700884 --> http://bugzilla.opensuse.org/attachment.cgi?id=700884&action=edit Plymouth core dump 2016-11-07 -- Kernel 4.4.27-1-default Haven't yet rebooted to install the new Kernel from this mornings update. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c8 --- Comment #8 from Donald Curtis --- (In reply to Zhao Qiang 赵强 from comment #7)

Created attachment 704509 [details] Screen shot

openSUSE Leap 42.2 has updated to GM, the bug can't reproduce in this edition. I think we can set the bug as INVALID.

I disagree: the attachment 702688 is a core dump from production Leap 42.2 running on AMD based hardware -- NOT IN A VM -- and NOT A RELEASE CANDIDATE VERSION!!!! The hardware where the Plymouth of (production) Leap 42.2 dumps core is: an AMD A10-5750M APU with Radeon(tm) HD Graphics (Lenovo G505s Laptop). I'll drop another coredumpctl output into this Bug Report later today. -------------------------------------------------------------------- Please be aware that, that part of the community who are using production Leap 42.2 on AMD based hardware are suffering continual issue not only with Plymouth but, also with KDE Plasma Segment Faults. Very few developers are responsive to the Bug Reports and Crash Dumps presumably, because they're using ** Intel ** based hardware . . . -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c10 --- Comment #10 from Donald Curtis --- Created attachment 704584 --> http://bugzilla.opensuse.org/attachment.cgi?id=704584&action=edit Plymouth core dump 2016-12-01 -- production Leap 42.2 Not a Release Candidate. Not running in a VM. Running native on an AMD A10-5750M APU with Radeon(tm) HD Graphics (Lenovo G505s Laptop). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c12 --- Comment #12 from Donald Curtis --- Created attachment 704659 --> http://bugzilla.opensuse.org/attachment.cgi?id=704659&action=edit Plymouth core dump 2016-11-30 -- production Leap 42.2 -- debug symbols Repeat of the earlier attachment -- this time with more debug symbols included. Running native on an AMD A10-5750M APU with Radeon(tm) HD Graphics (Lenovo G505s Laptop). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c14 Ignacio Taranto changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |itaranto7@gmail.com --- Comment #14 from Ignacio Taranto --- I could reproduce the issue on a Laptop Dell E6440 with Intel graphics (Core i7-4610M) in production Leap 42.2. Reproduction rate 100%. Should I attach the coredump of plymouthd? If so, do I need to provide the debug symbols as well? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 Mischa Salle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mischa.salle@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c17 Fernando Acero Martin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |facemar@gmail.com --- Comment #17 from Fernando Acero Martin --- I have the same problem with OpenSuse Tumbleweed: Linux linux-2k24 4.10.4-1-default #1 SMP PREEMPT Sat Mar 18 12:29:57 UTC 2017 (e2ef894) x86_64 x86_64 x86_64 GNU/Linux Sat 2017-03-25 09:20:54 CET 256 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 09:33:55 CET 4014 0 0 6 present /usr/sbin/snapperd Sat 2017-03-25 10:10:46 CET 278 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 10:36:04 CET 276 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 10:47:15 CET 312 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 10:49:12 CET 282 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 11:09:15 CET 267 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 12:23:18 CET 697 0 0 11 present /usr/sbin/plymouthd Sat 2017-03-25 12:23:23 CET 1134 0 0 11 present /usr/sbin/plymouthd Sat 2017-03-25 12:38:03 CET 284 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 12:42:19 CET 278 0 0 6 present /usr/sbin/plymouthd Sat 2017-03-25 12:49:26 CET 274 0 0 6 present /usr/sbin/plymouthd mar 25 12:49:19 linux-2k24 systemd[1]: Starting Show Plymouth Boot Screen... mar 25 12:49:19 linux-2k24 systemd[1]: Started Show Plymouth Boot Screen. mar 25 12:49:19 linux-2k24 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. mar 25 12:49:21 linux-2k24 systemd[1]: Starting Plymouth switch root service... mar 25 12:49:21 linux-2k24 systemd[1]: Started Plymouth switch root service. mar 25 12:49:25 linux-2k24 systemd[1]: Received SIGRTMIN+20 from PID 274 (plymouthd). mar 25 12:49:25 linux-2k24 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT mar 25 12:49:25 linux-2k24 systemd[1]: plymouth-start.service: Unit entered failed state. mar 25 12:49:25 linux-2k24 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. mar 25 12:49:26 linux-2k24 systemd-coredump[493]: Process 274 (plymouthd) of user 0 dumped core. mar 25 12:49:30 linux-2k24 systemd[1]: Starting Show Plymouth Boot Screen... mar 25 12:49:30 linux-2k24 systemd[1]: Started Show Plymouth Boot Screen. mar 25 12:49:31 linux-2k24 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... mar 25 12:49:31 linux-2k24 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. mar 25 12:49:35 linux-2k24 systemd[1]: Received SIGRTMIN+20 from PID 1170 (plymouthd). mar 25 12:49:37 linux-2k24 systemd[1]: Received SIGRTMIN+21 from PID 1170 (plymouthd). linux-2k24 description: Notebook product: HP ProBook 450 G3 (L6L07AV) vendor: HP serial: 5CD616615T width: 4294967295 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: administrator_password=disabled boot=normal chassis=notebook family=103C_5336AN G=N L=BUS B=HP S=PRO frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=L6L07AV uuid=CAA8B48A-D109-E611-BDC2-2CACB90080E8 *-core description: Motherboard product: 8101 vendor: HP physical id: 0 version: KBC Version 40.62 serial: PFMKU048J220PC *-firmware description: BIOS vendor: HP physical id: b version: N78 Ver. 01.14 date: 08/08/2016 size: 64KiB capacity: 15MiB capabilities: pci pcmcia upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi *-cpu description: CPU product: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz serial: To Be Filled By O.E.M. slot: U3E1 size: 500MHz capacity: 4005MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq configuration: cores=2 enabledcores=2 threads=4 Best regards -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c19 Stuart Rogers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stuart@stella-maris.org.uk --- Comment #19 from Stuart Rogers --- I have had this issue on Tumbleweed for some months now on every boot up. My system is an AMD quad core processor running AMD graphics. On every boot I see Apr 22 11:29:27 Tumbleweed.crowhill plymouth[23437]: error: unexpectedly disconnected from boot status daemon Apr 22 11:29:27 Tumbleweed.crowhill systemd[1]: plymouth-reboot.service: Main process exited, code=dumped, status=11/SEGV Apr 22 11:29:27 Tumbleweed.crowhill systemd[1]: plymouth-reboot.service: Unit entered failed state. Apr 22 11:29:27 Tumbleweed.crowhill systemd[1]: plymouth-reboot.service: Failed with result 'core-dump'. Apr 22 11:29:59 Tumbleweed systemd[1]: Received SIGRTMIN+20 from PID 261 (plymouthd). Apr 22 11:29:59 Tumbleweed systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT Apr 22 11:29:59 Tumbleweed systemd[1]: plymouth-start.service: Unit entered failed state. Apr 22 11:29:59 Tumbleweed systemd[1]: plymouth-start.service: Failed with result 'core-dump'. Apr 22 11:30:01 Tumbleweed systemd-coredump[575]: Process 261 (plymouthd) of user 0 dumped core. Nothing I have tried changes the situation, although the system boot up OK. It is some what annoying to say the least. If any more information is needed please let me know what it is. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c21 M Vermeiden changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@vermeiden.net --- Comment #21 from M Vermeiden --- It seems there is a fix, see https://build.opensuse.org/package/show/Base:System/plymouth. For version 0.9.2+git20170424.6fd5c6b: "This fixes plymouth-start.service failure at startup for me." -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1008489 http://bugzilla.opensuse.org/show_bug.cgi?id=1008489#c23 Aleksey Kontsevich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |akontsevich@gmail.com --- Comment #23 from Aleksey Kontsevich --- I have same issue on latest openSUSE Tumbleweed: Aug 25 12:09:40 localhost systemd[1]: Received SIGRTMIN+21 from PID 531 (plymouthd). After installing nvidia drivers splash on boot disappeared and I see only blinking screen with cursor during boot: https://forums.opensuse.org/showthread.php/526739-Splash-screen-on-boot-disa... Is it Plymouth bug or nvidia? Seems works fine with noveau. -- You are receiving this mail because: You are on the CC list for the bug.