From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com
Subject: sysfs: duplicate filename 'bInterfaceNumber' can not be created
Date: Tue, 16 Oct 2007 15:06:58 +0200 [thread overview]
Message-ID: <20071016130658.GG5263@kernel.dk> (raw)
Hi,
I get this on booting git as of this morning, HEAD is at
65a6ec0d72a07f16719e9b7a96e1c4bae044b591.
sysfs: duplicate filename 'bInterfaceNumber' can not be created
WARNING: at fs/sysfs/dir.c:425 sysfs_add_one()
Call Trace:
[<ffffffff802bd786>] sysfs_add_one+0x5c/0xc9
[<ffffffff802bd21a>] sysfs_add_file+0x59/0x8d
[<ffffffff802bed57>] sysfs_create_group+0x9c/0xf5
[<ffffffff8803b1db>] :usbcore:usb_create_sysfs_intf_files+0x35/0xd6
[<ffffffff88037a39>] :usbcore:usb_set_configuration+0x49d/0x4bf
[<ffffffff8803bb35>] :usbcore:usb_create_ep_files+0x290/0x2df
[<ffffffff8803ed11>] :usbcore:generic_probe+0x5d/0xa0
[<ffffffff8803902d>] :usbcore:usb_probe_device+0x39/0x3b
[<ffffffff803ec13e>] driver_probe_device+0xde/0x165
[<ffffffff803ec1c5>] __device_attach+0x0/0xb
[<ffffffff803ec1ce>] __device_attach+0x9/0xb
[<ffffffff803eb33d>] bus_for_each_drv+0x4b/0x82
[<ffffffff803ec258>] device_attach+0x64/0x7c
[<ffffffff803eb2a6>] bus_attach_device+0x2d/0x79
[<ffffffff803ea092>] device_add+0x38c/0x60d
[<ffffffff88032f1e>] :usbcore:usb_new_device+0x51/0x91
[<ffffffff88033b5f>] :usbcore:hub_thread+0x7a0/0xbae
[<ffffffff80247770>] autoremove_wake_function+0x0/0x38
[<ffffffff880333bf>] :usbcore:hub_thread+0x0/0xbae
[<ffffffff80247641>] kthread+0x49/0x78
[<ffffffff8020c658>] child_rip+0xa/0x12
[<ffffffff802475f8>] kthread+0x0/0x78
[<ffffffff8020c64e>] child_rip+0x0/0x12
--
Jens Axboe
next reply other threads:[~2007-10-16 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:06 Jens Axboe [this message]
2007-10-16 13:38 ` sysfs: duplicate filename 'bInterfaceNumber' can not be created Kamalesh Babulal
2007-10-16 14:26 ` sysfs: duplicate filename 'bInterfaceNumber' can not be created & different places Kamalesh Babulal
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=20071016130658.GG5263@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=greg@kroah.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