From: Chris Clayton <chris2553@googlemail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Greg KH <greg@kroah.com>,
James Bottomley <James.Bottomley@hansenpartnership.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
Subject: Re: 2,6.26-rc4-git2 - long pause during boot
Date: Sat, 14 Jun 2008 06:03:59 +0000 [thread overview]
Message-ID: <200806140603.59061.chris2553@googlemail.com> (raw)
In-Reply-To: <48504B94.9050100@s5r6.in-berlin.de>
On Wednesday 11 June 2008, Stefan Richter wrote:
> I wrote:
> > /etc/udev/rules.d/05-udev-early.rules:ACTION=="add",
> > KERNEL=="[0-9]*:[0-9]*", SUBSYSTEM=="scsi", WAIT_FOR_SYSFS="ioerr_cnt"
> >
> > Whatever this rule is good for... Maybe the pattern should be
> > "[0-9]+(:[0-9]+){3}" to match logical units only.
>
> Actually no; looks like these are just glob(7) patterns. Then the
> pattern might already be OK since host devices' and target devices'
> names don't start with decimal numbers.
For Slackware 12.0.0, the rule is:
ACTION=="add", KERNEL=="[0-9]*:[0-9]*", SUBSYSTEM=="scsi",
WAIT_FOR_SYSFS="ioerr_cnt"
Using that rule instaed of the old one in the Slackware rules file included with
udev appears to result in the same behaviour as with the old rule and kernel <
2.6.26.
Unless someone warns me otherwise, I think I'll go with that on my (homebrewed)
system, so thanks to everyone for your help.
Chris
--
Beauty is in the eye of the beerholder.
next prev parent reply other threads:[~2008-06-14 6:06 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
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 [this message]
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=200806140603.59061.chris2553@googlemail.com \
--to=chris2553@googlemail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--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