All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: timeout udevd too hort
Date: Thu, 01 Apr 2004 06:40:56 +0000	[thread overview]
Message-ID: <20040401064055.GC11655@kroah.com> (raw)
In-Reply-To: <20040401010726.GC13247@vrfy.org>

On Thu, Apr 01, 2004 at 03:07:26AM +0200, Kay Sievers wrote:
> Bahh, I thought we introduced a bug in udevd with the recent changes,
> but it seems I have a really slow device here.
> 
> We currently have a event timeout of 5 seconds to wait for a missing
> event. I can catch it by activating my Thinkpad's builtin bluetooth
> hardware. Sometimes the kernel needs 6 seconds to submit all the
> hotplug events for this device.

Ouch, that log trail was pretty bad.  It's nice to see we can duplicate
out-of-order messages :)

> Should we increase it to 10 seconds?

I don't have a problem with doing that.  Anyone else?

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      reply	other threads:[~2004-04-01  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  1:07 timeout udevd too hort Kay Sievers
2004-04-01  6:40 ` Greg KH [this message]

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=20040401064055.GC11655@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.