[Bug 1012142] New: SEGV (11) on plymouthd
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142 Bug ID: 1012142 Summary: SEGV (11) on plymouthd Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mikhail.kasimov@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 703694 --> http://bugzilla.opensuse.org/attachment.cgi?id=703694&action=edit plymouthd core dump Hello! [1] k_mikhail@linux-mk500:~> coredumpctl list | grep ply ========================================================================= Срд 2016-11-23 14:17:39 EET 234 0 0 11 * /usr/sbin/plymouthd Чтв 2016-11-24 01:36:18 EET 259 0 0 11 * /usr/sbin/plymouthd Чтв 2016-11-24 23:54:12 EET 263 0 0 11 * /usr/sbin/plymouthd Чтв 2016-11-24 23:59:41 EET 269 0 0 11 * /usr/sbin/plymouthd ========================================================================= [2] k_mikhail@linux-mk500:~> coredumpctl dump plymouthd ========================================================================= k_mikhail@linux-mk500:~> coredumpctl dump plymouthd PID: 269 (plymouthd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Чтв 2016-11-24 23:59:41 EET (14min ago) Command Line: @usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session Executable: /usr/sbin/plymouthd Control Group: /system.slice/plymouth-start.service Unit: plymouth-start.service Slice: system.slice Boot ID: 3298e61885dc48229ffef7bde5d0b220 Machine ID: 4664bc7cba6aee90fe1efc7f571cbf28 Hostname: linux-mk500 Coredump: /var/lib/systemd/coredump/core.plymouthd.0.3298e61885dc48229ffef7bde5d0b220.269.1480024781000000.xz Message: Process 269 (plymouthd) of user 0 dumped core. Refusing to dump core to tty. ========================================================================= -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c1
--- Comment #1 from Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c3
Fabian Vogt
same here:
# coredumpctl gdb plymouthd [...] (gdb) bt #0 ply_event_loop_get_destination_from_fd_watch (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:449 #1 0x00007f756771b1db in ply_event_loop_stop_watching_fd (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:750 #2 0x00007f756750784c in ply_terminal_close () from /usr/lib64/libply-splash-core.so.4
This is extremely weird. watch is a pointer and 0x21 is way too low to be valid. It is likely the result of taking the address of a member of a struct at NULL, but that can't possibly happen as watch comes straight from calloc. I have no idea what's going on here.
#3 0x00007f756771ec33 in ply_hashtable_foreach (hashtable=0xd1c8e0, func=0x7f75675077c0
, user_data=0xd1cf20) at ply-hashtable.c:268 #4 0x000000000040c1e8 in quit_splash (state=state@entry=0x7ffec1e4e580) at main.c:1064 #5 0x000000000040d8cf in on_boot_splash_idle (state=0x7ffec1e4e580) at main.c:1196 #6 0x00007f756771bd02 in ply_event_loop_handle_timeouts (loop=0xd17150) at ply-event-loop.c:1192 #7 ply_event_loop_process_pending_events (loop=loop@entry=0xd17150) at ply-event-loop.c:1251 #8 0x00007f756771c2f0 in ply_event_loop_run (loop=0xd17150) at ply-event-loop.c:1310 #9 0x00000000004055bf in main (argc=<optimized out>, argv=<optimized out>) at main.c:2236 (gdb) l 444 { 445 ply_event_destination_t *destination; 446 447 assert (loop != NULL); 448 assert (watch != NULL); 449 assert (watch->destination != NULL); 450 451 destination = watch->destination; 452 453 return destination; (gdb)
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
Mischa Salle
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c4
--- Comment #4 from Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c5
Fabian Vogt
've tried to reproduce with all needed -debug packages (possibly, it'll help):
That's the usual crash that gets triggered by the broken patch that is now removed in TW and Base:System. Can you confirm that it works with plymouth from http://download.opensuse.org/repositories/home:/Vogtinator:/branches:/Base:/... ? (Never tested that package, it might be broken in other ways) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c6
--- Comment #6 from Mikhail Kasimov
(In reply to Mikhail Kasimov from comment #4)
've tried to reproduce with all needed -debug packages (possibly, it'll help):
That's the usual crash that gets triggered by the broken patch that is now removed in TW and Base:System. Can you confirm that it works with plymouth from http://download.opensuse.org/repositories/home:/Vogtinator:/branches:/Base:/ System/openSUSE_Leap_42.2 ?
(Never tested that package, it might be broken in other ways)
Failed again, but this time -- without segfaults: [1] ========================================================================= k_mikhail@linux-mk500:~> systemctl status -l plymouth-start.service ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Чтв 2017-02-02 22:45:55 EET; 5min ago Process: 665 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=1/FAILURE) Process: 555 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS) Main PID: 654 (code=exited, status=127) Фев 02 22:45:54 linux-mk500 systemd[1]: Starting Show Plymouth Boot Screen... Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Main process exited, code=exited, status=127/n/a Фев 02 22:45:55 linux-mk500 systemd[1]: Failed to start Show Plymouth Boot Screen. Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Unit entered failed state. Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Failed with result 'exit-code'. ========================================================================= [2] Previous fail with core-dump (on 42.2 release branch) and current fail (after reinstalling plymouth from http://download.opensuse.org/repositories/home:/Vogtinator:/branches:/Base:/...) ================================================================================================== k_mikhail@linux-mk500:~> journalctl -u plymouth-start.service --since=today -- Logs begin at Срд 2016-11-23 13:48:54 EET, end at Чтв 2017-02-02 22:51:59 EET. -- Фев 02 21:06:50 linux-mk500 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Фев 02 21:06:50 linux-mk500 systemd[1]: plymouth-start.service: Unit entered failed state. Фев 02 21:06:50 linux-mk500 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. Фев 02 21:06:53 linux-mk500 systemd-coredump[1422]: Process 283 (plymouthd) of user 0 dumped core. -- Reboot -- Фев 02 22:45:54 linux-mk500 systemd[1]: Starting Show Plymouth Boot Screen... Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Main process exited, code=exited, status=127/n/a Фев 02 22:45:55 linux-mk500 systemd[1]: Failed to start Show Plymouth Boot Screen. Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Unit entered failed state. Фев 02 22:45:55 linux-mk500 systemd[1]: plymouth-start.service: Failed with result 'exit-code'. ================================================================================================== -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
Nico Kruber
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c8
--- Comment #8 from Mikhail Kasimov
Mikhail Kasimov:
Since I can't reproduce this in my machine with openSUSE Leap 42.2, Could you please show me your /etc/os-release file, please.
======================================================= k_mikhail@linux-mk500:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="42.2" ID=opensuse ID_LIKE="suse" VERSION_ID="42.2" PRETTY_NAME="openSUSE Leap 42.2" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.2" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" k_mikhail@linux-mk500:~> ======================================================= -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c19
--- Comment #19 from Zhao Qiang 赵强
(In reply to Zhao Qiang 赵强 from comment #16)
(In reply to Mikhail Kasimov from comment #14)
(In reply to Zhao Qiang 赵强 from comment #13)
Have you try to upgrade dracut and reboot ?
I have only what system gets on its update from oss repo. =========================================== k_mikhail@linux-mk500:~> dracut --version getopt: неизвестный ключ «--version» Usage: /usr/bin/dracut [OPTION]... [<initramfs> [<kernel-version>]]
Version: 044-14.1
... ===========================================
Sorry, it's a misleading. I'm not mean dracut rpm package, but to run "sudo dracut --force" in command line.
========================================= k_mikhail@linux-mk500:~> sudo dracut --force
You mean even after this update and system reboot, your plymouth still core dump right ? Is this core dump appear 100% when system boot? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c20
--- Comment #20 from Mikhail Kasimov
(In reply to Mikhail Kasimov from comment #18)
(In reply to Zhao Qiang 赵强 from comment #16)
(In reply to Mikhail Kasimov from comment #14)
(In reply to Zhao Qiang 赵强 from comment #13)
Have you try to upgrade dracut and reboot ?
I have only what system gets on its update from oss repo. =========================================== k_mikhail@linux-mk500:~> dracut --version getopt: неизвестный ключ «--version» Usage: /usr/bin/dracut [OPTION]... [<initramfs> [<kernel-version>]]
Version: 044-14.1
... ===========================================
Sorry, it's a misleading. I'm not mean dracut rpm package, but to run "sudo dracut --force" in command line.
========================================= k_mikhail@linux-mk500:~> sudo dracut --force
You mean even after this update and system reboot, your plymouth still core dump right ?
Is this core dump appear 100% when system boot?
Yes. Just put 'sudo dracut --force && sudo systemctl reboot' coomand and, after system has been rebooted: [1] k_mikhail@linux-mk500:~> systemctl --failed ========================================================================== UNIT LOAD ACTIVE SUB DESCRIPTION ● plymouth-start.service loaded failed failed Show Plymouth Boot Screen LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ========================================================================== [2] k_mikhail@linux-mk500:~> journalctl -e -u plymouth-start.service ========================================================================== -- Reboot -- Фев 13 14:16:11 linux-mk500 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Фев 13 14:16:11 linux-mk500 systemd[1]: plymouth-start.service: Unit entered failed state. Фев 13 14:16:11 linux-mk500 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. Фев 13 14:16:13 linux-mk500 systemd-coredump[1303]: Process 282 (plymouthd) of user 0 dumped core. ========================================================================== Фев (ru) = Feb (en). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c22
Andrei Borzenkov
This problem is happened in a real machine or a virtual machine ?
I have it VM: qemu-system-x86_64 -m 768 -device virtio-scsi-pci -drive file=$HOME/vm/leap/hd0.qcow2,if=none,id=hd0,discard=on,format=qcow2 -device scsi-hd,drive=hd0 -net user -net nic,model=virtio -enable-kvm -virtfs local,path=$HOME,security_model=none,mount_tag=home -drive file=$HOME/vm/leap/hd1.qcow2,if=none,id=hd1,discard=on,format=qcow2 -device scsi-hd,drive=hd1 100% reproducible. The first core preserved here is from 2016-11-19. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c23
R Silverman
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c24
--- Comment #24 from Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c25
--- Comment #25 from Mischa Salle
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142
http://bugzilla.opensuse.org/show_bug.cgi?id=1012142#c26
--- Comment #26 from R Silverman
participants (1)
-
bugzilla_noreply@novell.com