From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 80E7F138CBE for ; Sat, 21 Mar 2015 17:28:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9F945E0A5A; Sat, 21 Mar 2015 17:27:46 +0000 (UTC) Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 80724E0941 for ; Sat, 21 Mar 2015 17:27:45 +0000 (UTC) Received: by igbud6 with SMTP id ud6so12161031igb.1 for ; Sat, 21 Mar 2015 10:27:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=5ITOkp80zcoL1oBW4XANnq563xO0+e6xV/iRRyifUSM=; b=kK/FL7m2Mg4l7jMCjJ08pjSd/QngRUefvUDYVAfvSRWz9utlv87K0vv53WRMPfeu8N 4vmbUSyiGW8jNu9MlGqzcVXF6PLYph9h0qBHeW1ov1+dw7fSvEE+PTZGMUOHBp0B33Ef 69srgaGLb7Ot7nSueG0JInAY8dpHGsUEzaL3i62Uk2z3C7RnvTjBZHHNVQrapr3gCYRS v++wGjdz+w8bfvTh6erTC6ZvYTTg+gI0ILPk1dSDqZSt7oxmq1QHErCafCCBArycoIHd brbiKKLCcwXs6W49tcCYIJyj3Tpk0y4D0l/9tCY4CGb1GUmyfb0voDPxVYfvw8JmIw7+ rcsw== X-Received: by 10.107.14.141 with SMTP id 135mr86761402ioo.15.1426958864927; Sat, 21 Mar 2015 10:27:44 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.149.149 with HTTP; Sat, 21 Mar 2015 10:27:24 -0700 (PDT) In-Reply-To: <550DA889.30000@gmail.com> References: <550DA889.30000@gmail.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Sat, 21 Mar 2015 11:27:24 -0600 Message-ID: Subject: Re: [gentoo-user] OK, so not everything works properly with systemd To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a113fefc240d3260511cfc0a4 X-Archives-Salt: a77abad6-0f6d-46d2-bce8-00a3f18840da X-Archives-Hash: 60c226eb2914c78f8cc81be0b7918fcd --001a113fefc240d3260511cfc0a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Mar 21, 2015 at 11:21 AM, Daniel Frey wrote: > Hi list, Hi. > In one of my earlier posts I mentioned I wasn't having any issues with > systemd. Well, I guess I lied, although I didn't know about it at the time. > > My laptop works fine, no issues. > > My desktop, however, has an issue, but only while rebooting. I use mdadm > to access my IMSM raid, and during the reboot process, the last message > I see is (from memory, so it's not exact): > > "Stopping mdmon..." > > And it hangs there. > > The journal shows this: > =3D=3D=3D=3D=3D > -- Reboot -- > Mar 18 20:48:42 osoikaze systemd-journal[485]: Journal stopped > Mar 18 20:48:42 osoikaze systemd-shutdown[1]: Sending SIGTERM to > remaining processes... > Mar 18 20:48:41 osoikaze systemd[1]: Shutting down. > > =3D=3D=3D=3D=3D > > mdmon is normally stopped right at the end, so it should be a part of > 'Sending SIGTERM to remaining processes'. The Journal stops, then from > what I gather, it hangs on the next one, which is mdmon. I have left it > for a half an hour and it doesn't do anything. > > When rebooting: > > =3D=3D=3D=3D=3D > Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out of 4 > devices > Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: not clean -- starting > background reconstruction > Mar 18 20:49:39 osoikaze kernel: md: bind > Mar 18 20:49:39 osoikaze kernel: md: bind > Mar 18 20:49:39 osoikaze kernel: md: bind > Mar 18 20:49:39 osoikaze kernel: md: bind > Mar 18 20:49:39 osoikaze kernel: md: bind > Mar 18 20:49:39 osoikaze kernel: md: bind > =3D=3D=3D=3D=3D > > Indicating that mdmon was not stopped properly. (The array starts a > rebuild.) Checking /proc/mdstat confirms this. > > Now this is the odd thing: `systemctl poweroff` works fine! It shuts > everything down, and turns my workstation off without corrupting the > RAID array! > > So why does `systemctl reboot` not want to work? I'm a little confused. What kind of initramfs are you using? Supposedly, the only difference between poweroff and reboot is that the former turns off the machine and reboot does a reset. In either case, systemd pivots back to the initramfs before umounting everything, so perhaps there lies the problem. > I also noticed this in the USE flags for systemd: > - - sysv-utils : Install sysvinit compatibility > symlinks and manpages for init, telinit, halt, poweroff, reboot, > runlevel, and shutdown > > Should I enable that USE flag? No. In Gentoo in particular the SysV compatibility is completely useless. > (By the way, KDE shows the same behaviour. If I shutdown with the K > Menu, it works. Reboot from the K Menu hangs.) KDE (as GNOME, Xfce, and everything else) uses logind, so it's equivalent to do "systemctl poweroff" or click "Power Off" in your DE. I would bet on the initramfs. Regards. -- Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico --001a113fefc240d3260511cfc0a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Mar 21, 2015 at 11:21 AM, Daniel Frey <djqfrey@gmail.com> wrote:
> Hi l= ist,

Hi.

> In one of my earlier posts I mentioned I wasn&#= 39;t having any issues with
> systemd. Well, I guess I lied, although= I didn't know about it at the time.
>
> My laptop works fi= ne, no issues.
>
> My desktop, however, has an issue, but only = while rebooting. I use mdadm
> to access my IMSM raid, and during the= reboot process, the last message
> I see is (from memory, so it'= s not exact):
>
> "Stopping mdmon..."
>
>= And it hangs there.
>
> The journal shows this:
> =3D=3D= =3D=3D=3D
> -- Reboot --
> Mar 18 20:48:42 osoikaze systemd-jou= rnal[485]: Journal stopped
> Mar 18 20:48:42 osoikaze systemd-shutdow= n[1]: Sending SIGTERM to
> remaining processes...
> Mar 18 20:4= 8:41 osoikaze systemd[1]: Shutting down.
>
> =3D=3D=3D=3D=3D>
> mdmon is normally stopped right at the end, so it should be a= part of
> 'Sending SIGTERM to remaining processes'. The Jour= nal stops, then from
> what I gather, it hangs on the next one, which= is mdmon. I have left it
> for a half an hour and it doesn't do = anything.
>
> When rebooting:
>
> =3D=3D=3D=3D=3D> Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out = of 4
> devices
> Mar 18 20:49:39 osoikaze kernel: md/raid10:md1= 26: not clean -- starting
> background reconstruction
> Mar 18 = 20:49:39 osoikaze kernel: md: bind<sdi>
> Mar 18 20:49:39 osoik= aze kernel: md: bind<sdh>
> Mar 18 20:49:39 osoikaze kernel: md= : bind<sdg>
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdf&= gt;
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdi>
> Ma= r 18 20:49:39 osoikaze kernel: md: bind<sdg>
> =3D=3D=3D=3D=3D<= br>>
> Indicating that mdmon was not stopped properly. (The array = starts a
> rebuild.) Checking /proc/mdstat confirms this.
>
= > Now this is the odd thing: `systemctl poweroff` works fine! It shuts> everything down, and turns my workstation off without corrupting the=
> RAID array!
>
> So why does `systemctl reboot` not wan= t to work? I'm a little confused.

What kind of initramfs are you= using?=C2=A0 Supposedly, the only difference between poweroff and reboot i= s that the former turns off the machine and reboot does a reset. In either = case, systemd pivots back to the initramfs before umounting everything, so = perhaps there lies the problem.

> I also noticed this in the USE = flags for systemd:
> - - sysv-utils =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Install sysvinit compatibility
= > symlinks and manpages for init, telinit, halt, poweroff, reboot,
&g= t; runlevel, and shutdown
>
> Should I enable that USE flag?
No. In Gentoo in particular the SysV compatibility is completely usele= ss.

> (By the way, KDE shows the same behaviour. If I shutdown wi= th the K
> Menu, it works. Reboot from the K Menu hangs.)

KDE = (as GNOME, Xfce, and everything else) uses logind, so it's equivalent t= o do "systemctl poweroff" or click "Power Off" in your = DE.

I would bet on the initramfs.

Regards.
--<= br>Canek Pel=C3=A1ez Vald=C3=A9s
Profesor de asignatura, Facultad de Cie= ncias
Universidad Nacional Aut=C3=B3noma de M=C3=A9xico
--001a113fefc240d3260511cfc0a4--