Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #71255 > unrolled thread

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2021-05-08 15:00 +0200
Last post2021-05-08 21:00 +0200
Articles 5 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99 Salvatore Bonaccorso <carnil@debian.org> - 2021-05-08 15:00 +0200
    Processed: Re: Bug#959170: linux: at boot: Process  '/usr/sbin/alsactl ... restore 0' failed with exit code 99 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-08 15:00 +0200
    Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99 Vincent Lefevre <vincent@vinc17.net> - 2021-05-08 18:20 +0200
      Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99 Vincent Lefevre <vincent@vinc17.net> - 2021-05-08 18:40 +0200
      Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99 Salvatore Bonaccorso <carnil@debian.org> - 2021-05-08 21:00 +0200

#71255 — Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-05-08 15:00 +0200
SubjectBug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99
Message-ID<CcuIN-72v-1@gated-at.bofh.it>
Control: tags -1 + moreinfo

On Thu, Apr 30, 2020 at 12:38:26PM +0200, Vincent Lefevre wrote:
> Source: linux
> Version: 5.6.7-1
> Severity: minor
> 
> With the 5.6.0-1-amd64 Linux kernel at least, I get the following
> error at boot (shown by journalctl):
> 
> Apr 30 11:57:16 zira systemd-udevd[489]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> 
> This apparently comes from /lib/systemd/system/alsa-restore.service,
> which has:
> 
> ExecStart=-/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore
> 
> It seems that the first time I got a similar error was in October:
> 
> Oct 22 10:07:58 zira systemd-udevd[500]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
> 
> Then in November:
> 
> Nov 10 02:40:42 zira systemd-udevd[513]: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> 
> /etc/alsa/conf.d contains:
> 
> lrwxrwxrwx 1 root root  44 2020-02-29 17:15:54 10-rate-lav.conf -> /usr/share/alsa/alsa.conf.d/10-rate-lav.conf
> lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 10-samplerate.conf -> /usr/share/alsa/alsa.conf.d/10-samplerate.conf
> lrwxrwxrwx 1 root root  45 2020-02-29 17:15:54 10-speexrate.conf -> /usr/share/alsa/alsa.conf.d/10-speexrate.conf
> lrwxrwxrwx 1 root root  48 2020-02-29 17:15:54 50-arcam-av-ctl.conf -> /usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
> lrwxrwxrwx 1 root root  40 2020-02-29 17:15:54 50-jack.conf -> /usr/share/alsa/alsa.conf.d/50-jack.conf
> lrwxrwxrwx 1 root root  39 2020-02-29 17:15:54 50-oss.conf -> /usr/share/alsa/alsa.conf.d/50-oss.conf
> lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 50-pulseaudio.conf -> /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
> lrwxrwxrwx 1 root root  47 2020-02-29 17:15:54 60-a52-encoder.conf -> /usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
> lrwxrwxrwx 1 root root  41 2020-02-29 17:15:54 60-upmix.conf -> /usr/share/alsa/alsa.conf.d/60-upmix.conf
> lrwxrwxrwx 1 root root  44 2020-02-29 17:15:54 60-vdownmix.conf -> /usr/share/alsa/alsa.conf.d/60-vdownmix.conf
> lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 98-usb-stream.conf -> /usr/share/alsa/alsa.conf.d/98-usb-stream.conf
> lrwxrwxrwx 1 root root  38 2020-02-06 03:06:41 99-pulse.conf -> /usr/share/alsa/alsa.conf.d/pulse.conf
> -rw-r--r-- 1 root root 201 2018-11-03 00:35:24 99-pulseaudio-default.conf.example
> 
> (I haven't changed anything there.)

Is this still something you are able to reproduce and have more
insights since then? If you are not able to reproduce it anymore,
should we otherwise close the issue?

Regards,
Salvatore

[toc] | [next] | [standalone]

#71258 — Processed: Re: Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-05-08 15:00 +0200
SubjectProcessed: Re: Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99
Message-ID<CcuIO-72v-15@gated-at.bofh.it>
In reply to#71255
Processing control commands:

> tags -1 + moreinfo
Bug #959170 [src:linux] linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99
Added tag(s) moreinfo.

-- 
959170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#71311

FromVincent Lefevre <vincent@vinc17.net>
Date2021-05-08 18:20 +0200
Message-ID<CcxQl-Rz-5@gated-at.bofh.it>
In reply to#71255
On 2021-05-08 14:54:58 +0200, Salvatore Bonaccorso wrote:
> Is this still something you are able to reproduce and have more
> insights since then? If you are not able to reproduce it anymore,
> should we otherwise close the issue?

zira:~> journalctl | grep 'failed with exit code 99'
May 18 14:40:58 zira systemd-udevd[461]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
May 18 14:43:03 zira systemd-udevd[488]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 17 14:44:13 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 18 11:22:05 zira systemd-udevd[464]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Sep 24 10:54:58 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 24 11:01:26 zira systemd-udevd[432]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 24 11:07:31 zira systemd-udevd[456]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 24 11:09:43 zira systemd-udevd[444]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 24 11:29:22 zira systemd-udevd[449]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Sep 24 11:30:50 zira systemd-udevd[450]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Oct 18 23:19:30 zira systemd-udevd[462]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Oct 18 23:20:28 zira systemd-udevd[450]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Oct 29 02:51:50 zira systemd-udevd[452]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Nov 30 02:44:43 zira systemd-udevd[451]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Jan 04 21:21:29 zira systemd-udevd[458]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Jan 22 19:54:32 zira systemd-udevd[468]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.

So this failure hasn't occurred for a few months, but this was already
the case between 2020-05-18 and 2020-09-17. Thus there may still be
some possibility that it occurs again in a few weeks.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#71313

FromVincent Lefevre <vincent@vinc17.net>
Date2021-05-08 18:40 +0200
Message-ID<Ccy9I-12I-9@gated-at.bofh.it>
In reply to#71311
FYI, other users got the same error:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848395
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772
  https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1624435
  https://bugs.gentoo.org/578138

In Debian bug 848395: as said by the alsactl(1) man page:

    init tries to initialize all devices to a default state.
    If device is not known, error code 99 is returned.

I can see 2 possibilities:

1. For some reason, the device is not always initialized by the
   kernel.

2. There is a race condition: alsactl is run too soon, while the
   device has not been initialized yet by the kernel.

(2) would explain why this isn't always reproducible.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#71321

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-05-08 21:00 +0200
Message-ID<CcAlb-2nP-1@gated-at.bofh.it>
In reply to#71311
Hi Vincent,

On Sat, May 08, 2021 at 06:13:09PM +0200, Vincent Lefevre wrote:
> On 2021-05-08 14:54:58 +0200, Salvatore Bonaccorso wrote:
> > Is this still something you are able to reproduce and have more
> > insights since then? If you are not able to reproduce it anymore,
> > should we otherwise close the issue?
> 
> zira:~> journalctl | grep 'failed with exit code 99'
> May 18 14:40:58 zira systemd-udevd[461]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> May 18 14:43:03 zira systemd-udevd[488]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 17 14:44:13 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 18 11:22:05 zira systemd-udevd[464]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> Sep 24 10:54:58 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 24 11:01:26 zira systemd-udevd[432]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 24 11:07:31 zira systemd-udevd[456]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 24 11:09:43 zira systemd-udevd[444]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 24 11:29:22 zira systemd-udevd[449]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Sep 24 11:30:50 zira systemd-udevd[450]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Oct 18 23:19:30 zira systemd-udevd[462]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> Oct 18 23:20:28 zira systemd-udevd[450]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> Oct 29 02:51:50 zira systemd-udevd[452]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> Nov 30 02:44:43 zira systemd-udevd[451]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
> Jan 04 21:21:29 zira systemd-udevd[458]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> Jan 22 19:54:32 zira systemd-udevd[468]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
> 
> So this failure hasn't occurred for a few months, but this was already
> the case between 2020-05-18 and 2020-09-17. Thus there may still be
> some possibility that it occurs again in a few weeks.

Okay and thanks for quickly report back, much appreciated.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web