LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   kobject_add failed for error using 2.6.21.1-smp (https://www.linuxquestions.org/questions/slackware-14/kobject_add-failed-for-error-using-2-6-21-1-smp-555274/)

davimint 05-19-2007 09:19 PM
kobject_add failed for error using 2.6.21.1-smp
 
How do you go about fixing this problem. I built current using this kernel and had this error so I though it was something I wasn't catching following the instructions so I build current again and had the same problem. Then I downloaded alien bob's ISO and installed and had the same problem.

Help, Help, Help.....

Example of dmesg error:
Code:
ohci1394: exports duplicate symbol ohci1394_unregister_iso_tasklet (owned by kernel)
kobject_add failed for usb_storage with -EEXIST, don't try to register things with the same name in the same directory.
 [<c03b4b17>] kobject_shadow_add+0x117/0x1a0
 [<c013a404>] mod_sysfs_setup+0x24/0xb0
 [<c013bcb8>] sys_init_module+0x1648/0x1940
 [<c0102ae8>] syscall_call+0x7/0xb
 =======================

KStorm 05-19-2007 10:06 PM
See this post:

http://www.linuxquestions.org/questi...46#post2741446

I have the same kobject errors, but Slackware -current is running fine.

davimint 05-19-2007 10:37 PM
KStorm,
Need more help, don't get it... I already seen your post and didn't get it... To little info for me..

KStorm 05-20-2007 06:05 AM
Well then...a previous changelog explained the error messages. My apologies.

davimint 05-20-2007 11:23 PM
Ok, never did find out why Pat V's build caused these errors or if they actually mean anything but I did solve the problem. I rebuilt current today with a custom kernel so I could tweak my system and installed all the new packages. I thought that if I removed the rw permission on the slackbuilt kernels they would not install but they did anyway. So, I removed those packages and rebuilt my kernel due to the fact it was removed by the install scrips ( for some reason ). So guess what, all that junk was gone. Now I've got current going with a tweaked kernel and everything is great again without those silly errors.

davimint 06-01-2007 05:47 PM
On the "Changes & Hints text" today I found the information that had been removed by Pat which explains this error.

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.
It's nice to see that back in their becuase I search everywhere for the answer on this.

rworkman 06-02-2007 12:10 AM
Sorry about that - we don't know how that information got removed.
I guess it must have gotten removed accidentally when we were rearranging the contents.

KStorm 06-03-2007 12:06 PM
Quote:
Originally Posted by rworkman
Sorry about that - we don't know how that information got removed.
I guess it must have gotten removed accidentally when we were rearranging the contents.
Thanks for bringing it back. How would I go about, aside from installing a new kernel (I'm running -current), having these kobject errors removed during boot-up?

rworkman 06-03-2007 06:33 PM
Quote:
Originally Posted by KStorm
Thanks for bringing it back. How would I go about, aside from installing a new kernel (I'm running -current), having these kobject errors removed during boot-up?
Use either the generic or generic SMP kernel and create an initrd or perhaps blacklist (see /etc/modprobe.d/blacklist) the relevant modules. Just be sure to remove them from the blacklist if you ever decide to use one of the generic kernels.

KStorm 06-14-2007 11:37 AM
Quote:
Originally Posted by rworkman
Use either the generic or generic SMP kernel and create an initrd or perhaps blacklist (see /etc/modprobe.d/blacklist) the relevant modules. Just be sure to remove them from the blacklist if you ever decide to use one of the generic kernels.
I blacklisted the relevant modules and it's all good now. Thanks a bunch!


All times are GMT -5. The time now is 02:03 PM.