[opensuse-factory] Command failed (Tumbleweed)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I should note that I removed "splash=silent" from the boot command line, so I am seeing startup and shutdown messages instead of the Plymouth splash screen. When I shutdown (or reboot) Tumbleweed, I am seeing around 40 lines of "Command failed" or similar wording. The 40 is a guess. It happens too rapidly to count, but it does fill more than one screen. After that, there is a line "Read failed ...". It disappears too quickly to read the full line. All of this happens after "target shutdown reached". I'm not at all surprised that commands are failing after shutdown, or that files cannot be read after shutdown. But it seems to me that something is wrong, that it is even attempting to run commands and read files after shutdown. I'll note that this is not actually causing problems. But I thought I should report it. I don't think it is possible to catch any data on this, so I have not reported a bug. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZSyQIAAoJEGSXLIzRJwiFVRgH/jkvljEPX2vlMgGFh6jYn69F r9oPmF3Y/Sp/Nr3qE9aWLMmxG8d/IO2SYsHmC9/Xk7bW0yQGXiRXXKSEKTNku4dX 839N7bSK1fEAayv2ecK6eRs4nb34bBY2N7PynN0bR4EROUUJkcGCY4QNX9fXEPjz wqzeDQ3/kPxuyYv8LFZjLlqJTu8WhhflqcUy18Yn4ujRkSrj3FfPzJjxxPPR6r3H 9Qb9DG6SG2NRZQUSQlQZMexcr3vT/v31JCnwWO+lrKbygzXbhf30z6D40zRvpOlr f++Insv2h8tKQzDMyHBcO4nTi1YoHpzfPGONVpBNwhB3YWgwHxTM/oJ1RXuEvxw= =LDYQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Neil Rickert composed on 2017-06-21 20:57 (UTC-0500): .
I should note that I removed "splash=silent" from the boot command line, so I am seeing startup and shutdown messages instead of the Plymouth splash screen. . When I shutdown (or reboot) Tumbleweed, I am seeing around 40 lines of "Command failed" or similar wording. The 40 is a guess. It happens too rapidly to count, but it does fill more than one screen. . After that, there is a line "Read failed ...". It disappears too quickly to read the full line. . All of this happens after "target shutdown reached". . I'm not at all surprised that commands are failing after shutdown, or that files cannot be read after shutdown. But it seems to me that something is wrong, that it is even attempting to run commands and read files after shutdown. . I'll note that this is not actually causing problems. But I thought I should report it. I don't think it is possible to catch any data on this, so I have not reported a bug. . I always boot with no splash=<anything> and no quiet. To me, not seeing boot messages is anathema to Linux not being Windows.
Are you seeing failure messages at boot, maybe not perceptible during boot, but in the journal? If yes, don't be surprised to see corresponding failures at shutdown. Systemd routinely tries to stop units at shutdown that failed to start during init. Numerous things that never started cannot be successfully stopped. ;-) Some that systemd tries to stop can cause long shutdown delays, sometimes even unlimited, and not unusually 90 seconds. IIRC, common ones here seem to be various non-critical networking connections, e.g. NTP, NFS, ?MB. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-06-22 03:57, Neil Rickert wrote:
I should note that I removed "splash=silent" from the boot command line, so I am seeing startup and shutdown messages instead of the Plymouth splash screen.
I use "splash=verbose" and uninstall Plymouth. I get all the beautiful text messages.
When I shutdown (or reboot) Tumbleweed, I am seeing around 40 lines of "Command failed" or similar wording. The 40 is a guess. It happens too rapidly to count, but it does fill more than one screen.
Not when you boot?
After that, there is a line "Read failed ...". It disappears too quickly to read the full line.
All of this happens after "target shutdown reached".
I'm not at all surprised that commands are failing after shutdown, or that files cannot be read after shutdown. But it seems to me that something is wrong, that it is even attempting to run commands and read files after shutdown.
I'll note that this is not actually causing problems. But I thought I should report it. I don't think it is possible to catch any data on this, so I have not reported a bug.
It delays things. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2017-06-22 12:38 (UTC+0200):
I use "splash=verbose" and uninstall Plymouth. I get all the beautiful text messages. . I uninstall Plymouth, quiet and splash=verbose. The following are equivalent ways to have verbose messages during init:
"" "splash=0" "splash=none" "splash=verbose" IOW, the default kernel behavior is verbose boot messages. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 22-06-2017 a las 10:21, Felix Miata escribió:
I uninstall Plymouth, quiet and splash=verbose. The following are equivalent ways to have verbose messages during init:
"" "splash=0" "splash=none" "splash=verbose"
JFYI: The kernel does not parse this option at all. CONFIG_BOOTSPLASH patches are long gone. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez composed on 2017-06-22 20:51 (UTC-0400): .
I uninstall Plymouth, quiet and splash=verbose. The following are equivalent ways to have verbose messages during init: . "" "splash=0" "splash=none" "splash=verbose" . JFYI: The kernel does not parse this option at all. CONFIG_BOOTSPLASH
Felix Miata composed: . patches are long gone. . To be clear: 1-All variations of splash= on cmdline are inert with current & recent releases? 2-Patches refers to all kernels, or only openSUSE kernels? 3-How long is long? OS 13.x? OS 12.x? OS 11.x? Longer? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 22-06-2017 a las 23:36, Felix Miata escribió:
To be clear: 1-All variations of splash= on cmdline are inert with current & recent releases?
Yes. if this works, some other userspace component is parsing it and adjusting the verbosity level.
2-Patches refers to all kernels, or only openSUSE kernels?
the openSUSE kernels..in any case bootsplash patches never made it into upstream.
3-How long is long? OS 13.x? OS 12.x? OS 11.x? Longer?
since kernel 3.10-rc1 according to the log. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-06-23 18:15, Cristian Rodríguez wrote:
El 22-06-2017 a las 23:36, Felix Miata escribió:
To be clear: 1-All variations of splash= on cmdline are inert with current & recent releases?
Yes. if this works, some other userspace component is parsing it and adjusting the verbosity level.
2-Patches refers to all kernels, or only openSUSE kernels?
the openSUSE kernels..in any case bootsplash patches never made it into upstream.
3-How long is long? OS 13.x? OS 12.x? OS 11.x? Longer?
since kernel 3.10-rc1 according to the log.
Thanks :-) Now I'll have to adjust my boot lines on several computers and see... ;-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2017-06-23 20:21 (UTC+0200): .
Cristian Rodríguez wrote: .
since kernel 3.10-rc1 according to the log.. 12.1 was 3.10.0. . Now I'll have to adjust my boot lines on several computers and see... ;-) . I started removing them last February, but only going back to 13.1. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Jun 23, 2017 at 02:38:36PM -0400, Felix Miata wrote:
Cristian Rodríguez wrote:
since kernel 3.10-rc1 according to the log.. 12.1 was 3.10.0.
Not true, 12.1 had 3.1, not 3.10. Version 3.10 falls between 12.3 (kernel 3.7) and 13.1 (kernel 3.11). (see e.g. https://en.wikipedia.org/wiki/OpenSUSE#Releases ) Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-06-23 at 23:00 +0200, Michal Kubecek wrote:
On Fri, Jun 23, 2017 at 02:38:36PM -0400, Felix Miata wrote:
Cristian Rodríguez wrote:
since kernel 3.10-rc1 according to the log.. 12.1 was 3.10.0.
Not true, 12.1 had 3.1, not 3.10. Version 3.10 falls between 12.3 (kernel 3.7) and 13.1 (kernel 3.11).
(see e.g. https://en.wikipedia.org/wiki/OpenSUSE#Releases )
Michal Kubeček
Default kernel line in 42.3 Build0289 is has: splash=silent quiet showopts Also, "showopts" is obsolete, it does not work on grub2. - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAllTjL8ACgkQtTMYHG2NR9W7UACfag8yTcNGwWpBcaaCwbQgdj0h d2UAnjAkL7II8y/1iVGCTtPmpClSfkbQ =Z/Ms -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/22/2017 05:38 AM, Carlos E. R. wrote:
On 2017-06-22 03:57, Neil Rickert wrote:
I'm replying to both Carlos and Felix here. They both asked similar questions.
Not when you boot?
The only failures that I see during boot, are failure to start plymouth and failure to switch plymouth to a different mode.
I'll note that this is not actually causing problems. But I thought I should report it. I don't think it is possible to catch any data on this, so I have not reported a bug.
It delays things.
Not noticeably. Shutdown is still pretty fast. The "Command failed" messages go by very quickly, and then the screen blanks as the system boots or shuts down. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZTBwsAAoJEGSXLIzRJwiFiEYIAIm2krwuBhDr5v5SZ+/z/C2i N2KEgP8etGG3EBqWlAW18BeGK66O/afwSa1nj7u0MC7tgR/XM2WXHNyWe0XTaxGg 4Ka9hHac8+U5Uu49MiDES9P2Uz8uuzxwJ/5UGbbxixZaPpSeuu9ds4k5CINRFZ7U N+KPzpuHCRDUJm51P6ezu+aMpd9+60YnZXlYXMfpjkXAYGt71bEsba7WJJbLfANH 0Wioja/IZRx9iRGGQyiZ7QAdbLhWw4Q+Wm0/wpWpnOX9306PRza4hEbkLnWQBFNq mzoLyZRO0CyatWq7AjpcGfxNgDdhPS19WFnPx9FtYjW/H+kLIApysZJ2+182suY= =6OZn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-06-22 21:36, Neil Rickert wrote:
On 06/22/2017 05:38 AM, Carlos E. R. wrote:
It delays things.
Not noticeably. Shutdown is still pretty fast. The "Command failed" messages go by very quickly, and then the screen blanks as the system boots or shuts down.
The traditional way to debug these was to send the messages to a real RS232 port and log them on another computer. Needs such a port on the machine being investigated (real hardware, not faked), and I don't know how to make this under systemd. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Jun 22 2017, "Carlos E. R."
The traditional way to debug these was to send the messages to a real RS232 port and log them on another computer.
You can also use netconsole. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-06-26 08:56, Andreas Schwab wrote:
On Jun 22 2017, "Carlos E. R." <> wrote:
The traditional way to debug these was to send the messages to a real RS232 port and log them on another computer.
You can also use netconsole.
Ah, yes, I have used that one, yet I forgot. However, I think it dies earlier in the shutdown process. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (6)
-
Andreas Schwab -
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Michal Kubecek -
Neil Rickert