| Summary: | why plymouth dependency on shutdown? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Harald Reindl <h.reindl> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | johannbg, metherid, mschmidt, notting, plautrba, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-24 11:30:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Harald Reindl
2012-01-23 04:00:05 UTC
Please describe as exactly as possible how to reproduce the hang at shutdown. It is definitely possible to avoid plymouth. I have just tested it by: cd /lib/systemd/system systemctl mask plymouth* and adding the "rd.plymouth=0" boot parameter. systemd in rawhide seems to be totally broken found something in the mailinglist today BTW: /var/log/boot.log is empty currently in F15 and what does the DHCP messages in boot.log? [root@srv-rhsoft:~]$ rpm -qa | grep systemd systemd-26-14.fc15.x86_64 systemd-sysv-26-14.fc15.x86_64 systemd-units-26-14.fc15.x86_64 [root@srv-rhsoft:~]$ uname -r 2.6.41.10-2.fc15.x86_64 #1 SMP Thu Jan 19 02:27:37 UTC 2012 [root@srv-rhsoft:~]$ cat /var/log/boot.log Jan 22 05:37:03 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.7 from 00:90:3e:c8:d0:3c via br0 Jan 22 05:37:03 srv-rhsoft dhcpd: DHCPACK on 192.168.1.7 to 00:90:3e:c8:d0:3c via br0 Jan 22 06:25:49 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.15 from 00:0e:08:dd:9c:fd via br0 Jan 22 06:25:49 srv-rhsoft dhcpd: DHCPACK on 192.168.1.15 to 00:0e:08:dd:9c:fd via br0 Jan 22 10:51:04 srv-rhsoft dhcpd: DHCPDISCOVER from 00:90:3e:c8:d0:3c via br0 Jan 22 10:51:04 srv-rhsoft dhcpd: DHCPOFFER on 192.168.1.7 to 00:90:3e:c8:d0:3c via br0 Jan 22 10:51:04 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.7 (192.168.1.2) from 00:90:3e:c8:d0:3c via br0 Jan 22 10:51:04 srv-rhsoft dhcpd: DHCPACK on 192.168.1.7 to 00:90:3e:c8:d0:3c via br0 Jan 22 18:25:48 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.15 from 00:0e:08:dd:9c:fd via br0 Jan 22 18:25:48 srv-rhsoft dhcpd: DHCPACK on 192.168.1.15 to 00:0e:08:dd:9c:fd via br0 Jan 22 22:51:05 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.7 from 00:90:3e:c8:d0:3c via br0 Jan 22 22:51:05 srv-rhsoft dhcpd: DHCPACK on 192.168.1.7 to 00:90:3e:c8:d0:3c via br0 Jan 23 03:00:19 srv-rhsoft dhcpd: DHCPDISCOVER from 90:21:55:e4:a5:0a via br0 Jan 23 03:00:20 srv-rhsoft dhcpd: DHCPOFFER on 192.168.1.16 to 90:21:55:e4:a5:0a via br0 Jan 23 03:00:20 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.16 (192.168.1.2) from 90:21:55:e4:a5:0a via br0 Jan 23 03:00:20 srv-rhsoft dhcpd: DHCPACK on 192.168.1.16 to 90:21:55:e4:a5:0a via br0 Jan 23 06:25:47 srv-rhsoft dhcpd: DHCPREQUEST for 192.168.1.15 from 00:0e:08:dd:9c:fd via br0 Jan 23 06:25:47 srv-rhsoft dhcpd: DHCPACK on 192.168.1.15 to 00:0e:08:dd:9c:fd via br0 (In reply to comment #2) > systemd in rawhide seems to be totally broken > found something in the mailinglist today That's very vague and it does not seem related to the original report about shutdown in F16. systemd in Rawhide works for me, BTW. > BTW: > /var/log/boot.log is empty currently in F15 /var/log/boot.log is written out by plymouth, which you're trying to get rid of. Could this be the reason? Also, firstly the report was about F16, then Rawhide, now entirely something else in F15. Let's not conflate several issues in one BZ please. > and what does the DHCP messages in boot.log? As far as I know, boot.log is created by plymouth scraping the text from the console and saving it. >> systemd in rawhide seems to be totally broken >> found something in the mailinglist today > That's very vague and it does not seem related to the original report about > shutdown in F16. > systemd in Rawhide works for me, BTW. i do not know exactly why me rawhide-VM does no longer shutdown maybe the plymouth messages was only a assumption > i do not know exactly why me rawhide-VM does no longer shutdown bug 781657 maybe yes, this is it and with the version before it hung with the plymouth messages from above Is there anything left to fix in this BZ, or can we close it now? can be closed sorry, was a wrong assumption what is happening in my Rawhide-VM |