I accidentally noticed this error written to the warn log on my Dell R200's when the machines booted up after latest kernel update. Google doesn't have this exact error, only a few with differently named devices, but all seem to have to do with USB. Could this be a bug? Didn't see this error on other machines with more than one USB port, though.
Jun 26 22:59:07 c4 kernel: kobject_add failed for usbdev1.2_ep81 with - EEXIST, don't try to register things with the same name in the same directory. Jun 26 22:59:07 c4 kernel: Jun 26 22:59:07 c4 kernel: Call Trace: Jun 26 22:59:07 c4 kernel: [<ffffffff803457a0>] kobject_add+0x166/0x191 Jun 26 22:59:07 c4 kernel: [<ffffffff803af893>] device_add+0x85/0x372 Jun 26 22:59:07 c4 kernel: [<ffffffff803f03f6>] usb_create_ep_files+0x137/0x19a Jun 26 22:59:07 c4 kernel: [<ffffffff80478406>] klist_add_tail+0x35/0x42 Jun 26 22:59:07 c4 kernel: [<ffffffff803efe92>] usb_create_sysfs_intf_files+0x80/0x93 Jun 26 22:59:07 c4 kernel: [<ffffffff803ed710>] usb_set_configuration+0x3aa/0x3d9 Jun 26 22:59:07 c4 kernel: [<ffffffff803e9408>] usb_new_device+0x253/0x2c4 Jun 26 22:59:07 c4 kernel: [<ffffffff803ea554>] hub_thread+0x74e/0xb11 Jun 26 22:59:07 c4 kernel: [<ffffffff8029e04c>] autoremove_wake_function+0x0/0x2e Jun 26 22:59:07 c4 kernel: [<ffffffff803e9e06>] hub_thread+0x0/0xb11 Jun 26 22:59:07 c4 kernel: [<ffffffff8029de34>] keventd_create_kthread+0x0/0xc4 Jun 26 22:59:07 c4 kernel: [<ffffffff80233dee>] kthread+0xfe/0x132 Jun 26 22:59:07 c4 kernel: [<ffffffff80260b2c>] child_rip+0xa/0x12 Jun 26 22:59:07 c4 kernel: [<ffffffff8029de34>] keventd_create_kthread+0x0/0xc4 Jun 26 22:59:07 c4 kernel: [<ffffffff80233cf0>] kthread+0x0/0x132 Jun 26 22:59:07 c4 kernel: [<ffffffff80260b22>] child_rip+0x0/0x12
Kai
Kai Schaetzl wrote:
I accidentally noticed this error written to the warn log on my Dell R200's when the machines booted up after latest kernel update. Google doesn't have this exact error, only a few with differently named devices, but all seem to have to do with USB. Could this be a bug? Didn't see this error on other machines with more than one USB port, though.
Jun 26 22:59:07 c4 kernel: kobject_add failed for usbdev1.2_ep81 with - EEXIST, don't try to register things with the same name in the same directory. Jun 26 22:59:07 c4 kernel: Jun 26 22:59:07 c4 kernel: Call Trace: Jun 26 22:59:07 c4 kernel: [<ffffffff803457a0>] kobject_add+0x166/0x191 Jun 26 22:59:07 c4 kernel: [<ffffffff803af893>] device_add+0x85/0x372 Jun 26 22:59:07 c4 kernel: [<ffffffff803f03f6>] usb_create_ep_files+0x137/0x19a Jun 26 22:59:07 c4 kernel: [<ffffffff80478406>] klist_add_tail+0x35/0x42 Jun 26 22:59:07 c4 kernel: [<ffffffff803efe92>] usb_create_sysfs_intf_files+0x80/0x93 Jun 26 22:59:07 c4 kernel: [<ffffffff803ed710>] usb_set_configuration+0x3aa/0x3d9 Jun 26 22:59:07 c4 kernel: [<ffffffff803e9408>] usb_new_device+0x253/0x2c4 Jun 26 22:59:07 c4 kernel: [<ffffffff803ea554>] hub_thread+0x74e/0xb11 Jun 26 22:59:07 c4 kernel: [<ffffffff8029e04c>] autoremove_wake_function+0x0/0x2e Jun 26 22:59:07 c4 kernel: [<ffffffff803e9e06>] hub_thread+0x0/0xb11 Jun 26 22:59:07 c4 kernel: [<ffffffff8029de34>] keventd_create_kthread+0x0/0xc4 Jun 26 22:59:07 c4 kernel: [<ffffffff80233dee>] kthread+0xfe/0x132 Jun 26 22:59:07 c4 kernel: [<ffffffff80260b2c>] child_rip+0xa/0x12 Jun 26 22:59:07 c4 kernel: [<ffffffff8029de34>] keventd_create_kthread+0x0/0xc4 Jun 26 22:59:07 c4 kernel: [<ffffffff80233cf0>] kthread+0x0/0x132 Jun 26 22:59:07 c4 kernel: [<ffffffff80260b22>] child_rip+0x0/0x12
Kai
You failed to mention that this is CentOS 4 kernel, am I correct it is C4? Adding as much info as possible is always advised.
Ljubomir
Ljubomir Ljubojevic wrote on Mon, 27 Jun 2011 08:28:43 +0200:
You failed to mention that this is CentOS 4 kernel, am I correct it is C4?
No, c4 is a host numbering scheme. This is the latest series 5 kernel. 2.6.18-238.12.1.el5xen. What I didn't mention is that it is the xen kernel on x64.
Kai
On Mon, Jun 27, 2011 at 7:10 AM, Kai Schaetzl maillists@conactive.comwrote:
Ljubomir Ljubojevic wrote on Mon, 27 Jun 2011 08:28:43 +0200:
You failed to mention that this is CentOS 4 kernel, am I correct it is C4?
No, c4 is a host numbering scheme. This is the latest series 5 kernel. 2.6.18-238.12.1.el5xen. What I didn't mention is that it is the xen kernel on x64.
Most of the errors on Google seems to account for bugs in drivers failing to keep track of how many objects they've added to sysfs.
http://www.google.com/search?q= "EEXIST%2C+don't+try+to+register+things+with+the+same+name+in+the+same+directory"
RH Bugzilla: http://bit.ly/jQHbXa
I wouldn't be too worried, it just seems to be repeating something it has already done.
I'm not too familiar on how such thing should be reported. Should a bug be created in the CentOS bug database?
Giovanni Tirloni wrote on Mon, 27 Jun 2011 08:04:26 -0300:
I'm not too familiar on how such thing should be reported. Should a bug be created in the CentOS bug database?
There's another bug mentioned on the bugzilla page you referred to, 703084, which is supposed to be exactly about this one. I added a comment on 505284 as I can't view 703084. So, this should be sufficient. Thanks for finding the bugzilla entry!
Kai
-
Giovanni Tirloni -
Kai Schaetzl -
Ljubomir Ljubojevic