RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1581197 - plymouthd crashes on boot
Summary: plymouthd crashes on boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: plymouth
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 7.8
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1727111
TreeView+ depends on / blocked
 
Reported: 2018-05-22 10:40 UTC by Deepu K S
Modified: 2021-05-21 10:34 UTC (History)
6 users (show)

Fixed In Version: plymouth-0.8.9-0.33.20140113.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:06:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 91590 0 None None None 2018-05-22 10:41:37 UTC
Red Hat Product Errata RHBA-2020:1140 0 None None None 2020-03-31 20:06:09 UTC

Description Deepu K S 2018-05-22 10:40:36 UTC
Description of problem:
[abrt] plymouth: plymouthd killed by SIGSEGV
reason:         plymouthd killed by SIGSEGV
package:        plymouth-0.8.9-0.28.20140113.el7
pkg_vendor:     Red Hat, Inc.
cmdline:        @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session
executable:     /usr/sbin/plymouthd

Core was generated by `@usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-se'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f80179ed82c in ply_boot_splash_update_progress (splash=0x55a86040dbb0) at ply-boot-splash.c:448
448	  if (splash->plugin_interface->on_boot_progress != NULL)
(gdb) bt
#0  0x00007f80179ed82c in ply_boot_splash_update_progress (splash=0x55a86040dbb0) at ply-boot-splash.c:448
#1  0x00007f8017bfc632 in ply_event_loop_handle_timeouts (loop=0x55a860402150) at ply-event-loop.c:1234
#2  ply_event_loop_process_pending_events (loop=loop@entry=0x55a860402150) at ply-event-loop.c:1303
#3  0x00007f8017bfcf90 in ply_event_loop_run (loop=0x55a860402150) at ply-event-loop.c:1368
#4  0x000055a85fab64d5 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2443
(gdb) l
443	    {
444	      percentage = ply_progress_get_percentage(splash->progress);
445	      time = ply_progress_get_time(splash->progress);
446	    }
447	
448	  if (splash->plugin_interface->on_boot_progress != NULL)
449	    splash->plugin_interface->on_boot_progress (splash->plugin,
450	                                                time,
451	                                                percentage);
452	
(gdb) p *splash
$1 = {loop = 0x7f80172c97b8 <main_arena+88>, module_handle = 0x55a860407ef0, plugin_interface = 0x0, plugin = 0x0, mode = PLY_BOOT_SPLASH_MODE_BOOT_UP, boot_buffer = 0x55a860404de0, idle_trigger = 0x0, 
  keyboard = 0x0, pixel_displays = 0x55a86040dc80, text_displays = 0x55a86040dca0, theme_path = 0x55a86040dc40 "\360\334@`\250U", plugin_dir = 0x55a86040dc60 "0\334@`\250U", status = 0x0, 
  progress = 0x55a860407760, idle_handler = 0x0, idle_handler_user_data = 0x0, is_loaded = 0, should_force_text_mode = 0}
(gdb)
(gdb) p splash->plugin_interface
$2 = (const ply_boot_splash_plugin_interface_t *) 0x0
(gdb)

splash->plugin_interface is seen as a NULL pointer.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.4
plymouth-0.8.9-0.28.20140113.el7.x86_64

$ lspci | grep -i VGA\ 
00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller])

How reproducible:
Happened only once and not able to reproduce.

Steps to Reproduce:
1. Plymouthd crashed once at boot.
2.
3.

Actual results:
Apr 24 13:11:25 localhost systemd[1]: Received SIGRTMIN+21 from PID 264 (plymouthd).
Apr 24 13:11:26 localhost abrt-hook-ccpp[1911]: File '/usr/sbin/plymouthd' seems to be deleted
Apr 24 13:11:26 localhost abrt-hook-ccpp[1911]: Process 264 (plymouthd) of user 0 killed by SIGSEGV - dumping core
Apr 24 13:11:26 localhost systemd[1]: plymouth-start.service: main process exited, code=dumped, status=11/SEGV
Apr 24 13:11:26 localhost systemd[1]: Unit plymouth-start.service entered failed state.
Apr 24 13:11:26 localhost systemd[1]: plymouth-start.service failed.
Apr 24 13:11:26 localhost systemd[1]: Started Wait for Plymouth Boot Screen to Quit.

Expected results:
No plymouthd crashes.

Additional info:
This seems to be https://bugs.freedesktop.org/show_bug.cgi?id=91590

Comment 7 Pavlin Georgiev 2019-09-04 14:32:51 UTC
TEST SETUP
KVM based VM
Distro: RHEL 7.4
Component version: plymouth-0.8.9-0.28.20140113.el7

Graphics card: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04)


TEST PROCEDURE
1. Install RHEL 7.4 on a VM by using ISO file.
2. Boot the system.
3. Check for the problem in the system journal.
4. Reboot.
5. Repeat 2 times from step 2.


RESULT
I cannot reproduce the bug on that testing VM.

Comment 8 Pavlin Georgiev 2019-09-04 14:33:50 UTC
TEST SETUP 2
Hardware: PC HP xw4600 Workstation
Distro: RHEL 7.4
Component version: plymouth-0.8.9-0.28.20140113.el7

Graphics card: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2)


TEST PROCEDURE 2
Repeat the last testing procedure.


RESULT 2
I cannot reproduce the bug on that testing system.

Comment 9 Pavlin Georgiev 2019-09-04 15:14:24 UTC
TEST SETUP 3
Hardware: PC HP Z400 Workstation
Distro: RHEL 7.4
Component version: plymouth-0.8.9-0.28.20140113.el7

Graphics card: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)


TEST PROCEDURE 3
Repeat the last testing procedure.


RESULT 3
I cannot reproduce the bug on that testing system.

Comment 10 Pavlin Georgiev 2019-09-04 15:27:00 UTC
TEST SETUP 4
Distro: RHEL 7.4
Component version: plymouth-0.8.9-0.28.20140113.el7

Graphics card: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02)


TEST PROCEDURE 4
Repeat the last testing procedure.


RESULT 4
I cannot reproduce the bug on that testing system.

Comment 11 Pavlin Georgiev 2019-09-04 15:36:17 UTC
TEST SETUP 5
Hardware: PC Dell Inspiron 660s
Distro: RHEL 7.4
Component version: plymouth-0.8.9-0.28.20140113.el7

Graphics card: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)


TEST PROCEDURE 5
Repeat the last testing procedure.


RESULT 5
I cannot reproduce the bug on that testing system.

Comment 12 Tomas Pelka 2019-09-05 07:16:20 UTC
Deepu as we are not able to reproduce in house can you provide https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=958367 to customer.

Comment 13 Tomas Pelka 2019-09-20 14:16:12 UTC
(In reply to Tomas Pelka from comment #12)
> Deepu as we are not able to reproduce in house can you provide
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=958367 to
> customer.

Any feedback?

Thanks
-Tom

Comment 14 Deepu K S 2019-10-28 15:19:10 UTC
(In reply to Tomas Pelka from comment #13)
> (In reply to Tomas Pelka from comment #12)
> > Deepu as we are not able to reproduce in house can you provide
> > https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=958367 to
> > customer.
> 
> Any feedback?
> 
> Thanks
> -Tom

Finally got sometime to test the fix.

I updated plymouth to plymouth-0.8.9-0.33.20140113.el7.x86_64.rpm and haven't seen any crashes.
# abrt-cli list; is clean.

Thanks.

Comment 17 errata-xmlrpc 2020-03-31 20:06:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1140


Note You need to log in before you can comment on or make changes to this bug.