| Summary: | mageia2b2, shutdown very long time | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | episteme promeneur <epistemepromeneur> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemd | CVE: | |
| Status comment: | |||
|
Description
episteme promeneur
2012-03-23 09:13:28 CET
at least can you boot in verbose mode and shtudown the computer and report what you see ? Confirmed. CC:
(none) =>
thierry.vignaud (In reply to comment #1) > at least can you boot in verbose mode and shtudown the computer and report what > you see ? how to boot in verbose mode ? At the grub prompt, you need to remove the "splash=silent" or "splash" and "quiet" arguments if they appear. Then boot as normal. Hopefully it'll tell you something interesting. during shutdown process pauses just after diplaying "Detaching DM Devices" also there is a pb during boot process. process pauses a long time just after displaying "waiting for hotplugged network up" (i am not sure this is the exact message) during boot process the exact message is "waiting for the hot plugged network to be up" Is this still a problem with latest Cauldron? i wait for the beta 3 because my b2 with last update is completely out of order mageia 2 beta 3 now - startup is fast - shutdown is still long i can't see any message because the "escape" control does not display the messages we stay veiwing the mageia picture Please remove the options "quiet" and "splash" from your kernel command line line when you boot. This should stop the images showing up and let you read what is taking time on shutdown. process pauses just after diplaying "Detaching DM Devices" about 45 s Before shutting down, can you grab the output of "mount" (or cat /proc/mounts) and attach it. Do you have any network filesystems or any RAID/LVM/Crypt stuff? >> Do you have any network filesystems or any RAID/LVM/Crypt stuff?
no
[root@localhost ~]# cat /proc/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,relatime,size=2504636k,nr_inodes=626159,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
/dev/sda8 / ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
systemd-1 /proc/bus/usb autofs rw,relatime,fd=38,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
/dev/sda10 /home ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
usbfs /proc/bus/usb usbfs rw,relatime,devgid=43,devmode=664 0 0
[root@localhost ~]#
OK next step: Can you boot as before (i.e. without the quiet and slash args) but also add the following to the command line: "systemd.log_level= debug systemd.log_target=console" Then, rather than shutting down as normal, issue the following command (as root): systemctl halt Your machine should not power off by itself and you should get to see the messages displayed on shutdown. Hopefully after the 45s wait, it will print out some more messages after the "Detaching DM Devices" message. Hopefully that will hold some clues. When you are done copying down the details, you'll have to use the power button to turn off the machine. Thanks :) there is only one message after 45 s, after "detaching DM devices" [200.130.498] system halted addendum: i made several tests with systemd options in kernel command and with standard kernel command result : one or two time no 45 s delay thus fast shutdown ! it is a random and rare phenomenon then i can say 99 % of case shutdown takes a long time I'm struggling to work out why this is, but I'm guessing that it's in some way related to unmounting filesystems or killing processes. What messages preceed the "detatching DM devices" message. There should be "Unmounting file systems" and "Disabling swaps" etc. Do these all happen without any errors etc.? there are the expected messages : shutdown sigterm sigkill unmounting disabling detaching all without no error message my conf (bios order) : first disk : pata, several os to test (for example mageia 2), many partitions(ext4, swap) second disk : sata, mandriva 2010.2 (my every day system), 3 partitions (ext4, swap) third disk : sata, backup and store with last update 28/02/2012 i assume update of : - kernel - udev - udisk there is no more pb Status:
NEW =>
RESOLVED |