Bug 152103 - booting error message: "run_program: exec of program '/usr/sbin/alsactl' failed"
Summary: booting error message: "run_program: exec of program '/usr/sbin/alsactl' failed"
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 4
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Kay Sievers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-19 17:05 UTC by Jon Nelson
Modified: 2006-04-13 09:34 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Nelson 2006-02-19 17:05:46 UTC
While booting I get the following message:

booting error message: "run_program: exec of program '/usr/sbin/alsactl' failed"

I get it around the time serial ports are being configured and swap devices are being activated.

It /may/ be preceted by 'udevd-event[1494]: ' and does appear /before/ "Starting udevd".

/usr/sbin is not available yet and that is likely why - udevd should wait until /usr/sbin is available before trying to use alsactl, or, alsactl should be moved to /sbin so that it is available for booting.
Comment 1 Takashi Iwai 2006-02-20 11:30:11 UTC
Is /usr mounted via nfs?
Comment 2 Jon Nelson 2006-02-20 14:52:37 UTC
/usr is not mounted via nfs.
/usr is a logical volume provided by LVM
Comment 3 Kay Sievers 2006-02-21 17:31:45 UTC
That happens cause all tools to configure devices by udev are expected to be on the root filesystem and not on /usr. This is usually not a problem, cause the failing events will be applied later after all local filesystems are mounted.
Comment 4 Jon Nelson 2006-02-21 18:12:49 UTC
So is the solution to use one of my suggestions:

1. wait until /usr/sbin is available (or /path/to/program/but/not/program/itself) is available

2. move alsactl to /sbin

I guess I'd prefer [1] which would result in deferral(s) and/or eventual error?
Comment 5 Kay Sievers 2006-04-13 09:34:27 UTC
There is no need to wait, as the failing events are recorded and retried by /etc/init.d/boot.udev_retry.