From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Xavier Bestel" <xavier.bestel@free.fr>
Cc: linux-kernel@vger.kernel.org, "Adam Belay" <ambx1@neo.rr.com>
Subject: Re: PnP: WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
Date: Thu, 3 Apr 2008 17:19:23 +0200 [thread overview]
Message-ID: <3ae72650804030819n2b26cf13na9b30eed18df3d2c@mail.gmail.com> (raw)
In-Reply-To: <1207230993.3438.4.camel@skunk.anacadf.mentorg.com>
On Thu, Apr 3, 2008 at 3:56 PM, Xavier Bestel <xavier.bestel@free.fr> wrote:
> it's a debian 2.6.24-5
> On Thu, 2008-04-03 at 15:54 +0200, Xavier Bestel wrote:
> > I know some of these have been reported, but I couldn't find one in the
> > PnP subsystem.
> >
> >
> > Linux Plug and Play Support v0.97 (c) Adam Belay
> > pnp: PnP ACPI init
> > ACPI: bus type pnp registered
> > pnp: PnP ACPI: found 15 devices
> > ACPI: ACPI bus type pnp unregistered
> > PnPBIOS: Disabled by ACPI PNP
> > PCI: Probing PCI hardware
> > sysfs: duplicate filename 'bridge' can not be created
> > WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> > Pid: 1, comm: swapper Not tainted 2.6.24-1-686 #1
> > [<c01b12f8>] sysfs_add_one+0x54/0xb8
> > [<c01b1ee2>] sysfs_create_link+0xaf/0xfd
> > [<c01e7070>] pci_bus_add_devices+0xba/0xff
> > [<c0253589>] pcibios_scan_root+0x25/0x80
> > [<c01251d5>] printk+0x1b/0x1f
> > [<c0394d9c>] pci_legacy_init+0x53/0xe1
> > [<c0377497>] kernel_init+0x153/0x2c6
> > [<c0103d92>] ret_from_fork+0x6/0x1c
> > [<c0377344>] kernel_init+0x0/0x2c6
> > [<c0377344>] kernel_init+0x0/0x2c6
> > [<c0104b0f>] kernel_thread_helper+0x7/0x10
> > =======================
> > pci 0000:00:01.0: Error creating sysfs bridge symlink, continuing...
I guess, this fixes it:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=cc74d96f47b0d916840f92092595e3be9731e047
Kay
prev parent reply other threads:[~2008-04-03 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:54 Xavier Bestel
2008-04-03 13:56 ` Xavier Bestel
2008-04-03 15:19 ` Kay Sievers [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=3ae72650804030819n2b26cf13na9b30eed18df3d2c@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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
all inboxes | Powered by JetHome®