syslog errors (after install)

czezz · 02-06-2008, 07:04 AM

I have just installed Slackware 12 with huge-smp kernel.
What I found in syslog after first boot is that:

Code:

Feb  5 23:47:42 general kernel: kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Feb  5 23:47:42 general kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Feb  5 23:47:42 general kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Feb  5 23:47:42 general kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Feb  5 23:47:42 general kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Feb  5 23:47:42 general kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Feb  5 23:47:42 general kernel:  =======================
Feb  5 23:47:42 general kernel: kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Feb  5 23:47:42 general kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Feb  5 23:47:42 general kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Feb  5 23:47:42 general kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Feb  5 23:47:42 general kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Feb  5 23:47:42 general kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Feb  5 23:47:42 general kernel:  =======================
Feb  5 23:47:42 general kernel: kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Feb  5 23:47:42 general kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Feb  5 23:47:42 general kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Feb  5 23:47:42 general kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Feb  5 23:47:42 general kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Feb  5 23:47:42 general kernel:  =======================
Feb  5 23:47:42 general kernel: kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Feb  5 23:47:42 general kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Feb  5 23:47:42 general kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Feb  5 23:47:42 general kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Feb  5 23:47:42 general kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Feb  5 23:47:42 general kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Feb  5 23:47:42 general kernel:  =======================
Feb  5 23:47:42 general kernel: kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Feb  5 23:47:42 general kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Feb  5 23:47:42 general kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Feb  5 23:47:42 general kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Feb  5 23:47:42 general kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Feb  5 23:47:42 general kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Feb  5 23:47:42 general kernel:  =======================

And I got no point what does it mean and what is wrong ?
Basically system looks stable...
Thanks for any hints

MS3FGX · 02-06-2008, 08:04 AM

This is a issue in the latest Slackware release when using the huge kernels. Basically, the huge kernel already has USB support built in, but udev will still try and load the modules anyway.

It is not anything you need to worry about, and won't impact the system in any negative way. However, it is recommended to use the generic kernels for everyday use over the huge kernels. The huge line is really just for the installer or "safe mode" type situations, where the kernel needs to have as much hardware support as possible. But for your day to day activities, it is needlessly bloated up.

The best option is really to compile your own kernel if you need support for something that the generic kernel doesn't offer.