From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: Chris Clayton <chris2553@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-usb@vger.kernel.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: 2,6.26-rc4-git2 - long pause during boot
Date: Wed, 11 Jun 2008 14:24:42 -0500 [thread overview]
Message-ID: <1213212282.3461.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20080611191533.GA6189@kroah.com>
On Wed, 2008-06-11 at 12:15 -0700, Greg KH wrote:
> On Wed, Jun 11, 2008 at 06:58:05PM +0000, Chris Clayton wrote:
> > Jun 11 17:48:13 upstairs udevd-event[1457]: wait_for_sysfs: wait for '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:0a.2/usb11/11-2/11-2:1.0/host4/ioerr_cnt' for 20 mseconds
> > Jun 11 17:48:18 upstairs last message repeated 236 times
>
> This doesn't look good. It looks like a udev rule in your system is
> looking for a file that will never show up. That's a short way to a
> long delay time :)
>
> Try commenting out the rule that does this and see if things are fixed.
Actually, there's something seriously wrong here: ioerr_cnt is a
property of the device, not of the host (as in it will never appear
under .../host4 but under .../host4/targetX:X:X/4:X:X:X/ioerr_cnt).
Perhaps an investigation of why udevd-event is looking under host4/ is
in order.
James
next prev parent reply other threads:[~2008-06-11 19:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 4:15 2,6.26-rc4-git2 - long pause during boot Chris Clayton
2008-06-06 5:17 ` Andrew Morton
2008-06-06 6:07 ` Chris Clayton
2008-06-06 6:21 ` Andrew Morton
2008-06-06 6:25 ` Andrew Morton
2008-06-06 15:22 ` James Bottomley
2008-06-06 18:03 ` Andrew Morton
2008-06-06 18:40 ` James Bottomley
2008-06-07 5:16 ` Chris Clayton
2008-06-08 6:19 ` Chris Clayton
2008-06-08 18:37 ` James Bottomley
2008-06-09 23:07 ` Greg KH
2008-06-10 18:49 ` Chris Clayton
2008-06-10 22:06 ` Chris Clayton
2008-06-10 22:19 ` Alan Stern
2008-06-11 18:58 ` Chris Clayton
2008-06-11 19:15 ` Greg KH
2008-06-11 19:24 ` James Bottomley [this message]
2008-06-11 19:29 ` Stefan Richter
2008-06-11 19:36 ` James Bottomley
2008-06-13 6:56 ` Chris Clayton
2008-06-13 14:12 ` James Bottomley
2008-06-11 19:33 ` Greg KH
2008-06-11 19:51 ` Chris Clayton
2008-06-11 21:04 ` Stefan Richter
2008-06-11 21:46 ` Stefan Richter
2008-06-11 22:03 ` Stefan Richter
2008-06-14 6:03 ` Chris Clayton
2008-06-09 14:46 ` Alan Stern
2008-06-09 19:10 ` Stefan Richter
2008-06-09 19:40 ` Alan Stern
2008-06-09 21:35 ` Chris Clayton
2008-06-10 19:00 ` Chris Clayton
2008-06-10 19:38 ` Stefan Richter
2008-06-06 14:11 ` James Bottomley
2008-06-06 14:42 ` Rafael J. Wysocki
2008-06-06 17:42 ` Chris Clayton
2008-06-06 17:35 ` Chris Clayton
2008-06-09 4:51 ` Grant Grundler
2008-06-10 18:46 ` Chris Clayton
2008-06-06 10:45 ` Rafael J. Wysocki
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=1213212282.3461.9.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=chris2553@googlemail.com \
--cc=greg@kroah.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stefanr@s5r6.in-berlin.de \
/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