Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 596656 - [abrt] plymouth-0.8.3-3.el6: raise: Process /sbin/plymouthd was killed by signal 6 (SIGABRT)
[abrt] plymouth-0.8.3-3.el6: raise: Process /sbin/plymouthd was killed by sig...
Status: CLOSED DUPLICATE of bug 601745
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: plymouth (Show other bugs)
6.0
s390x Linux
low Severity medium
: rc
: ---
Assigned To: Ray Strode [halfline]
desktop-bugs@redhat.com
abrt_hash:f28321061560ee02104654a6e28...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-27 05:12 EDT by Michal Nowak
Modified: 2013-03-07 21:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-15 15:03:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (10.05 KB, text/plain)
2010-05-27 05:12 EDT, Michal Nowak
no flags Details

  None (edit)
Description Michal Nowak 2010-05-27 05:12:02 EDT
abrt version: 1.1.4
architecture: s390x
Attached file: backtrace
cmdline: /sbin/plymouthd --mode=shutdown
component: plymouth
crash_function: raise
executable: /sbin/plymouthd
global_uuid: f28321061560ee02104654a6e28d0bc1a37d311a
kernel: 2.6.32-28.el6.s390x
package: plymouth-0.8.3-3.el6
rating: 4
reason: Process /sbin/plymouthd was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Server release 6.0 Beta (Santiago)
Comment 1 Michal Nowak 2010-05-27 05:12:04 EDT
Created attachment 417156 [details]
File: backtrace
Comment 3 Bill Nottingham 2010-05-27 11:19:19 EDT
How reproducible is this?
Comment 4 RHEL Product and Program Management 2010-05-27 11:35:52 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 5 Michal Nowak 2010-05-28 05:00:55 EDT
No idea. Just found it after S/390x restart. I could have been the first restart after May 21 Plymouth update.
Comment 6 Ray Strode [halfline] 2010-06-01 10:43:17 EDT
next time you reboot can you add plymouth:debug to the kernel command line?
Comment 7 Michal Nowak 2010-06-02 06:39:01 EDT
So... It happens on shutdown after plymouth update.

[...]
Jun  2 06:26:05 auto-s390-001 yum: Updated: plymouth-theme-spinfinity-0.8.3-3.el6.s390x
Jun  2 06:26:05 auto-s390-001 yum: Updated: plymouth-theme-glow-0.8.3-3.el6.s390x
Jun  2 06:26:06 auto-s390-001 yum: Updated: plymouth-debuginfo-0.8.3-3.el6.s390x
Jun  2 06:26:12 auto-s390-001 abrtd: Getting crash infos...
Jun  2 06:26:16 auto-s390-001 init: tty (/dev/console) main process (2480) killed by TERM signal
Jun  2 06:26:16 auto-s390-001 abrt[2579]: saved core dump of pid 2572 (/sbin/plymouthd) to /var/spool/abrt/ccpp-1275474376-2572.new/coredump (1064960 bytes)
Jun  2 06:26:16 auto-s390-001 abrtd: Directory 'ccpp-1275474376-2572' creation detected
Jun  2 06:26:16 auto-s390-001 init: plymouth-shutdown main process (2570) terminated with status 2
Jun  2 06:26:16 auto-s390-001 init: splash-manager main process (2566) terminated with status 1
[...]

I added "plymouth:debug" to zipl.conf and updated it via `zipl`, however I don't see anything more in logs regarding plymouth. Where should I see those debug messages?
Comment 8 Ray Strode [halfline] 2010-06-02 08:54:31 EDT
oh sorry.  The log file is in /var/log/plymouth-debug.log

Of course, it will be for your boot up (which succeeds) not your shutdown (which fails).  It's still useful, though.

One thing I'm interested in is the output of /proc/cmdline, but that should be in the plymouth-debug.log
Comment 9 Michal Nowak 2010-06-02 10:10:54 EDT
(In reply to comment #8)
> oh sorry.  The log file is in /var/log/plymouth-debug.log

No such file, I am afraid.

> Of course, it will be for your boot up (which succeeds) not your shutdown
> (which fails).  It's still useful, though.
> 
> One thing I'm interested in is the output of /proc/cmdline, but that should be
> in the plymouth-debug.log    

[root@auto-s390-002 ~]# cat /proc/cmdline
root=/dev/mapper/vg_autos390002-lv_root rd_DASD=0.0.206e,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.216e,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.226e,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.236e,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.206f,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.216f,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.226f,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.236f,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.2070,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.2170,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.2270,use_diag=0,readonly=0,erplog=0,failfast=0 rd_DASD=0.0.2370,use_diag=0,readonly=0,erplog=0,failfast=0 rd_LVM_LV=vg_autos390002/lv_root rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 crashkernel=auto plymouth:debug BOOT_IMAGE


Tried both "plymouth:debug" and "plymouth=debug". With plymouth-0.8.3-1.el6.s390x.
Comment 10 Ray Strode [halfline] 2010-06-15 15:03:47 EDT

*** This bug has been marked as a duplicate of bug 601745 ***

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