public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udev: udevd shall inform us abot trouble
Date: Sat, 11 Sep 2004 10:48:24 -0700	[thread overview]
Message-ID: <41433A68.7090403@backtobasicsmgmt.com> (raw)
In-Reply-To: <200409111943.21225.vda@port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:

> Well, I lied a bit. These lines are from my home box, which is not
> udev'ified yet. At the job, I sit on i815 box, and there amixer
> fails to set volume. It happens 100% of the time. Adding "sleep 1"
> after modprobing helps. With devfs it worked without sleep.

This is correct; with devfs, creation of device nodes during module 
loading was synchronous, so it was always (or nearly always) complete 
before modprobe returned. With udev, creation of device nodes is 
completely asynchronous, and may happen at _any_ time after the module 
has been loaded.

The real solution here is for people to re-think their system startup 
processes; if you need mixer settings applied at startup, then build a 
small script somewhere in /etc/hotplug.d or /etc/dev.d that applies them 
to the mixer _when it appears_.

  reply	other threads:[~2004-09-11 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08  7:18 [PATCH] udev: udevd shall inform us abot trouble Denis Vlasenko
2004-09-10 20:30 ` Greg KH
2004-09-11 16:43   ` Denis Vlasenko
2004-09-11 17:48     ` Kevin P. Fleming [this message]
2004-09-11 18:22       ` Denis Vlasenko
2004-09-11 19:59         ` Kevin P. Fleming
2004-09-12 16:58         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41433A68.7090403@backtobasicsmgmt.com \
    --to=kpfleming@backtobasicsmgmt.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox