From: Kay Sievers <kay.sievers@vrfy.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: jim owens <jowens@hp.com>, Martin Knoblauch <knobi@knobisoft.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Andrew Morton <akpm@linux-foundation.org>,
efault@gmx.de, viro@zeniv.linux.org.uk, rjw@sisk.pl,
linux-kernel@vger.kernel.org, shemminger@vyatta.com,
mike.miller@hp.com, linux-pci@vger.kernel.org
Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
Date: Sat, 20 Jun 2009 20:36:25 +0200 [thread overview]
Message-ID: <ac3eb2510906201136v4c6eac1bwffd2aed3e38c6ae1@mail.gmail.com> (raw)
In-Reply-To: <20090620182617.GM19977@parisc-linux.org>
On Sat, Jun 20, 2009 at 20:26, Matthew Wilcox<matthew@wil.cx> wrote:
> On Sat, Jun 20, 2009 at 08:19:43PM +0200, Kay Sievers wrote:
>> On Sat, Jun 20, 2009 at 18:58, Matthew Wilcox<matthew@wil.cx> wrote:
>>
>> > but I don't know what udev is doing. ??The udev source doesn't seem to
>> > read PCI vpd itself:
>> >
>> > udev-0.141$ find -type f |xargs grep -il vpd
>> > ./extras/volume_id/lib/adaptec_raid.c
>> > ./extras/scsi_id/scsi_id.8
>> > ./extras/scsi_id/scsi.h
>> > ./extras/scsi_id/scsi_id.config
>> > ./extras/scsi_id/scsi_serial.c
>> >
>> > so there must be some script that it's invoking which is doing that.
>> > Anyone familiar with udev?
>>
>> scsi_id is usually also called for cciss devices:
>> KERNEL=="cciss*", ..., IMPORT{program}="scsi_id ...
>
> yes, but it's getting SCSI VPD (by asking for mode pages from the SCSI
> device). This problem is with PCI VPD which is totally different.
Ah, I see. There is no tool around udev, I know of, which does this.
Maybe someone is still using the broken-by-design libsysfs, which
opens _every_ file it can find in /sys, even when not asked for
anything specific.
Thanks,
Kay
next prev parent reply other threads:[~2009-06-20 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 11:25 Martin Knoblauch
2009-05-27 20:31 ` Andrew Morton
2009-05-27 20:56 ` Kay Sievers
2009-05-28 9:14 ` Martin Knoblauch
2009-06-16 19:25 ` Jesse Barnes
2009-06-17 8:35 ` Martin Knoblauch
2009-06-20 16:37 ` jim owens
2009-06-20 16:58 ` Matthew Wilcox
2009-06-20 18:19 ` Kay Sievers
2009-06-20 18:26 ` Matthew Wilcox
2009-06-20 18:36 ` Kay Sievers [this message]
2009-06-20 19:06 ` Matthew Wilcox
2009-06-20 21:17 ` jim owens
2009-06-21 10:57 ` Martin Knoblauch
2009-06-21 13:50 ` jim owens
2009-06-21 10:54 ` Martin Knoblauch
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 11:01 Martin Knoblauch
2009-04-24 12:45 Analyzed/Solved: " Martin Knoblauch
2009-04-29 1:28 ` Andrew Morton
2009-04-29 3:51 ` Mike Galbraith
2009-04-29 8:17 ` Andrew Morton
2009-04-29 12:08 ` Al Viro
2009-04-29 14:18 ` Mike Galbraith
2009-05-05 22:49 ` Andrew Morton
2009-05-06 4:45 ` Mike Galbraith
2009-05-06 7:55 ` Martin Knoblauch
2009-05-06 8:37 ` Mike Galbraith
2009-05-20 10:22 ` Analyzed/Solved/Bisected: " Martin Knoblauch
2009-05-27 6:31 ` Andrew Morton
2009-05-27 9:14 ` Martin Knoblauch
2009-05-27 11:21 ` Matthew Wilcox
2009-05-27 11:53 ` Martin Knoblauch
2009-05-27 18:07 ` jim owens
2009-05-27 18:18 ` Miller, Mike (OS Dev)
2009-05-27 20:12 ` jim owens
2009-05-27 21:18 ` Miller, Mike (OS Dev)
2009-05-28 8:59 ` Martin Knoblauch
2009-05-28 19:01 ` Miller, Mike (OS Dev)
2009-05-28 20:48 ` Martin Knoblauch
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=ac3eb2510906201136v4c6eac1bwffd2aed3e38c6ae1@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=jbarnes@virtuousgeek.org \
--cc=jowens@hp.com \
--cc=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mike.miller@hp.com \
--cc=rjw@sisk.pl \
--cc=shemminger@vyatta.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome