please explain kobject_add failed

DIGITAL39 · 08-20-2007, 02:46 PM

This is on Slackware 12.0, I never had any problems with 11.0.. Can someone explain what is going wrong here?

Code:

kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 344k freed
Linux agpgart interface v0.102 (c) Dave Jones
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03cb591>] kobject_shadow_add+0x101/0x1a0
 [<c01375a8>] mod_sysfs_setup+0x18/0xb0
 [<c0138907>] sys_init_module+0x1147/0x15d0
 [<c0103ec0>] syscall_call+0x7/0xb
 =======================
agpgart: Detected an Intel 855PM Chipset.
agpgart: AGP aperture is 128M @ 0xe0000000
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03cb591>] kobject_shadow_add+0x101/0x1a0
 [<c01375a8>] mod_sysfs_setup+0x18/0xb0
 [<c0138907>] sys_init_module+0x1147/0x15d0
 [<c0103ec0>] syscall_call+0x7/0xb
 [<c06f0000>] auth_unix_lookup+0x70/0x90
 =======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03cb591>] kobject_shadow_add+0x101/0x1a0
 [<c01375a8>] mod_sysfs_setup+0x18/0xb0
 [<c0138907>] sys_init_module+0x1147/0x15d0
 [<c0103ec0>] syscall_call+0x7/0xb
 [<c06f0000>] auth_unix_lookup+0x70/0x90
 =======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03cb591>] kobject_shadow_add+0x101/0x1a0
 [<c01375a8>] mod_sysfs_setup+0x18/0xb0
 [<c0138907>] sys_init_module+0x1147/0x15d0
 [<c0103ec0>] syscall_call+0x7/0xb
 [<c06f0000>] auth_unix_lookup+0x70/0x90
 =======================

dennisk · 08-20-2007, 03:05 PM

I see similar messages and don't think they are important. Remember the stock "huge" kernels will try to load drivers for hardware that might not be there. It has no way of knowing until it tries.

Bottom line - nothing to worry about. You'll need to compile a custom kernel to get rid of them.

And as Robby Workman points out below, spending quality time with the various READMEs that come with each new Slackware release before installing is time well spent. I, too, had forget that this was mentioned in one of them.

Dennisk

aquilolumen · 08-20-2007, 05:21 PM

yeah, when i compiled a custom kernel, those blocks of text went away. yay.

rworkman · 08-20-2007, 07:22 PM

Yay?? The only "yay" should be for reading http://slackware.osuosl.org/slackwar..._AND_HINTS.TXT, which explains it quite nicely:

Code:

  As stated earlier, it is recommended that you use one of the generic kernels
  rather than the huge kernels; the huge kernel is primarily intended as 
  an "installer" and "emergency" kernel in case you forget to make an initrd.
  However, if you do use one of the huge kernels, you will likely encounter 
  errors like this:
    kobject_add failed for uhci_hcd with -EEXIST, don't try to register
  These occur because the respective drivers are compiled statically into the
  huge kernels but udev tries to load them anyway.  These errors should be safe
  to ignore, but if you really don't want them to appear, you can blacklist the
  modules that try to load in /etc/modprobe.d/blacklist.  However, make sure you
  remove them from the blacklist if you ever decide to use the (recommended)
  generic kernels.

Since that file is mentioned in the Release Notes, and everyone is expected to read the Release Notes, everyone is expected to read CHANGES_AND_HINTS.TXT. :-)

aquilolumen · 08-20-2007, 08:47 PM

well, i don't remember all the details of all the docs that i've read. thanks for belittling my success as a newb...

rworkman · 08-20-2007, 09:16 PM

Thanks for ignoring the Slackware team's hard work on writing documentation to answer frequently asked questions.

Maybe I'm just weird like this -- BUT -- if a problem "goes away," I like to know why. Pardon me for thinking that other Slackware users also want to know why. Saying that "compiling a new kernel made them go away" is functionally not much different than saying "I rebooted my Windows box and it's okay now."

Anyway, you will note that there was a smiley at the end of my post - those things mean that I wasn't intending to belittle anyone. Even so, I have to ask: do you want someone who will make you feel all warm and fuzzy while feeding you worthless information, or do you want someone to give you useful information (even though you might get "belittled" in the process)? As for me, the choice is easy, but to each his own. [EDIT: Note that I am *NOT* suggesting that the other posts in the thread are worthless - I'm simply asking a question]

aquilolumen · 08-20-2007, 09:49 PM

i really do appreciate all the documentation on slackware that is out there and people who have helped me my own problems -- no need to accuse me of being ungrateful and ignorant. i simply don't remember every detail that is provided for slackware users on the internet. in my case, i learned the "why" after, and not before -- it just worked out that way for me. that is all.

fyi, i picked slackware for a reason.