From: Alex Chiang <achiang@hp.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci <linux-pci@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
willy@linux.intel.com
Subject: Re: [PATCH] PCI: create function symlinks in /sys/bus/pci/slots/N/
Date: Mon, 22 Mar 2010 12:17:30 -0600 [thread overview]
Message-ID: <20100322181730.GA6310@ldl.fc.hp.com> (raw)
In-Reply-To: <86802c441003201052taa660c0n2098e3ced56d2f1d@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org>:
> On Fri, Mar 19, 2010 at 2:46 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > On Mon, 8 Mar 2010 10:24:29 -0700
> > Alex Chiang <achiang@hp.com> wrote:
> >
> >> Create convenience symlinks in sysfs, linking slots to device
> >> functions, and vice versa. These links make it easier for users to
> >> figure out which devices actually live in what slots.
> >>
> >> For example:
> >
> > Applied to linux-next, thanks.
>
> looks this one cause
>
> [ 225.210695] calling pci_sysfs_init+0x0/0x51 @ 1
> [ 225.224774] ------------[ cut here ]------------
> [ 225.228913] WARNING: at fs/sysfs/dir.c:451 sysfs_add_one+0xd9/0xf3()
> [ 225.245349] Hardware name: Sun Fire x4800
> [ 225.247894] sysfs: cannot create duplicate filename
> '/devices/pci0000:00/0000:00:03.0/0000:02:00.0/slot'
That's really not supposed to happen.
It means that somehow, a single pci_dev is associated with
multiple slots.
There are dev_dbg statements in pci_create_slot() that should
display which slots are getting associated with which pci_dev
during initialization.
Can you please turn those debug statements on and send the
output?
Thanks,
/ac
prev parent reply other threads:[~2010-03-22 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 17:24 [PATCH] PCI: create function symlinks in /sys/bus/pci/slots/N/ Alex Chiang
2010-03-09 1:16 ` Kenji Kaneshige
2010-03-10 18:15 ` Alex Chiang
2010-03-19 21:46 ` Jesse Barnes
2010-03-20 17:52 ` Yinghai Lu
2010-03-20 18:22 ` Yinghai Lu
2010-03-22 18:17 ` Alex Chiang [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=20100322181730.GA6310@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=willy@linux.intel.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox