From: Xavier Bestel <xavier.bestel@free.fr>
To: linux-kernel@vger.kernel.org
Cc: Adam Belay <ambx1@neo.rr.com>
Subject: PnP: WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
Date: Thu, 03 Apr 2008 15:54:56 +0200 [thread overview]
Message-ID: <1207230896.3438.1.camel@skunk.anacadf.mentorg.com> (raw)
Hi,
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...
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
[<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:1c.0: Error creating sysfs bridge symlink, continuing...
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
[<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:1c.4: Error creating sysfs bridge symlink, continuing...
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
[<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:1c.5: Error creating sysfs bridge symlink, continuing...
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
[<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:1e.0: Error creating sysfs bridge symlink, continuing...
next reply other threads:[~2008-04-03 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:54 Xavier Bestel [this message]
2008-04-03 13:56 ` Xavier Bestel
2008-04-03 15:19 ` Kay Sievers
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=1207230896.3438.1.camel@skunk.anacadf.mentorg.com \
--to=xavier.bestel@free.fr \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®