Created attachment 13262 [details]
dmesg

Created attachment 13263 [details]
lspci

Reply-To: akpm@linux-foundation.org

On Wed, 24 Oct 2007 08:01:19 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9218
> 
>            Summary: sysfs: duplicate filename 'bInterfaceNumber' can not be
>                     created
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.24-rc1
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: no.hope@gmail.com
> 
> 
> Most recent kernel where this bug did not occur: 2.6.23.1
> Distribution: Gentoo
> Hardware Environment: x86_64 Intel(R) Core(TM)2, Intel USB UHCI, EHCI
> Software Environment: gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-rc1 x86_64
> Problem Description: Scary message during boot (below). Everything seems to
> work fine though.
> 
> hub 7-0:1.0: USB hub found
> hub 7-0:1.0: 2 ports detected
> sysfs: duplicate filename 'bInterfaceNumber' can not be created
> WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> 
> Call Trace:
>  [<ffffffff802b9b58>] sysfs_add_one+0x54/0xbd
>  [<ffffffff802b9644>] sysfs_add_file+0x50/0x81
>  [<ffffffff802bafe3>] sysfs_create_group+0x9a/0xf7
>  [<ffffffff80443490>] usb_create_sysfs_intf_files+0x3a/0xc8
>  [<ffffffff8043feeb>] usb_set_configuration+0x4bb/0x4fe
>  [<ffffffff80446fbd>] generic_probe+0x53/0x92
>  [<ffffffff803e921e>] __device_attach+0x0/0x5
>  [<ffffffff803e9195>] driver_probe_device+0xf6/0x17f
>  [<ffffffff803e921e>] __device_attach+0x0/0x5
>  [<ffffffff803e8441>] bus_for_each_drv+0x3d/0x6c
>  [<ffffffff803e92a9>] device_attach+0x63/0x7a
>  [<ffffffff803e83b8>] bus_attach_device+0x2a/0x76
>  [<ffffffff803e72e9>] device_add+0x391/0x604
>  [<ffffffff8043b5a6>] usb_new_device+0x45/0x7e
>  [<ffffffff8043ca2e>] hub_thread+0x728/0xb92
>  [<ffffffff8024572c>] autoremove_wake_function+0x0/0x2e
>  [<ffffffff8043c306>] hub_thread+0x0/0xb92
>  [<ffffffff8024561a>] kthread+0x47/0x75
>  [<ffffffff8020cc18>] child_rip+0xa/0x12
>  [<ffffffff802455d3>] kthread+0x0/0x75
>  [<ffffffff8020cc0e>] child_rip+0x0/0x12
> 
> Steps to reproduce: boot
> 
> 

FYI- this breaks suspend-to-ram here.

Also, this bisects to: efefc6eb38d43b8e5daef482f575d767b002004e

There's a patch to fix this problem here:

http://marc.info/?l=linux-usb-devel&m=119280459503731&w=2

Apparently Greg KH hasn't merged this patch into his development tree yet.

I actually tried that patch, it didn't work here, though I admittedly make many mistakes :) Anyone else had success?

Yes.  The person who reported this bug before you found that the patch fixed it.

Are you sure that you installed the patched driver correctly?  Some distributions load the usbcore module in an initramfs image during boot-up; if you don't rebuild that image then you would still be using the original driver.

Whoops, I guess only I can screw up such a small patch. Yes the fix worked. Thanks

Okay, you can go ahead and close this bug report.  Mark it as PATCH ALREADY AVAILABLE.