LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 06-09-2008, 12:37 PM   #1
dark*
Member
 
Registered: Jan 2006
Distribution: slackware 12.0
Posts: 42

Rep: Reputation: 15
Unhappy kobject_add failed for uhci_hcd with -EEXIST


I have been watching this message from kernel (slack 12 hugesmp) at booting, ever since I installed it (I even had it on my previous system but didnt bother to ask).

kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
sd 2:0:0:0: Attached scsi generic sg0 type 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================


Whats the meaning of this, i didnt change anything (like a new kernel or driver). how to get rid of it? its not hindering any functionality but its looks like something is wrong.
 
Old 06-09-2008, 12:45 PM   #2
Uncle_Theodore
Member
 
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 60
Quote:
Originally Posted by dark* View Post
I have been watching this message from kernel (slack 12 hugesmp) at booting, ever since I installed it (I even had it on my previous system but didnt bother to ask).

kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
sd 2:0:0:0: Attached scsi generic sg0 type 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================


Whats the meaning of this, i didnt change anything (like a new kernel or driver). how to get rid of it? its not hindering any functionality but its looks like something is wrong.
It's described in CHANGES_AND_HINTS.TXT ftp://carroll.cac.psu.edu/pub/linux/..._AND_HINTS.TXT

It's not really a problem, just a consequence of using the huge kernel. Switch to generic (you'll need an initrd), it'll go away.
 
Old 06-09-2008, 10:57 PM   #3
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,327

Rep: Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760
Please read all, or at least most, of the relevant text files included with your Slackware installation, particularly CHANGES_AND_HINTS.TXT and UPGRADE.TXT (even if you are not upgrading). CHANGES_AND_HINTS.TXT is the most quoted piece of official documentation that goes unread, even though it contains the answers to 90% of the problems asked.
 
Old 06-09-2008, 11:48 PM   #4
fibster
Member
 
Registered: Feb 2006
Location: Washington State
Distribution: Slackware
Posts: 40

Rep: Reputation: 16
Wow

Quote:
Originally Posted by T3slider View Post
Please read all, or at least most, of the relevant text files included with your Slackware installation, particularly CHANGES_AND_HINTS.TXTCHANGES_AND_HINTS.TXT and UPGRADE.TXT (even if you are not upgrading). CHANGES_AND_HINTS.TXT is the most quoted piece of official documentation that goes unread, even though it contains the answers to 90% of the problems asked.
Yes the CHANGES_AND_HINTS is always a good wager.

Last edited by fibster; 06-10-2008 at 12:18 AM.
 
Old 06-10-2008, 03:07 AM   #5
dark*
Member
 
Registered: Jan 2006
Distribution: slackware 12.0
Posts: 42

Original Poster
Rep: Reputation: 15
Thanks, i'll definitely look it.
 
Old 06-10-2008, 07:03 AM   #6
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,283
Blog Entries: 55

Rep: Reputation: Disabled
If you do change to the generic kernel, you can use Eric's script to give you the right command to enter to create an initrd:

http://www.slackware.com/~alien/tool...d_generator.sh
 
Old 06-22-2009, 10:34 PM   #7
semiRocket
LQ Newbie
 
Registered: Apr 2009
Location: Rijeka, Croatia
Distribution: Slackware 12.2
Posts: 16

Rep: Reputation: 0
I have similar errors in my system start, so I decided to do change to generic kernel.

I did everything from README.initrd except the compiling line which I changed a bit to suite my situation:
Code:
mkinitrd -c -k 2.6.27.7-smp -m mbcache:jbd:ext3 -f ext3 -r /dev/sda6
After I compiled initrd.gz I changed lilo.conf:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-2.6.27.7-smp  # Default vmlinuz
  initrd = /boot/initrd.gz      # Default without the whole line
  root = /dev/sda6
  label = Slack
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
I have run the lilo command which ran whithout errors. After I have restarted it was given me error that it can't find init and that it may indicate of mounting problems. And that I have been given a chance to fix it mannualy with some sort of a command line. (If you need the exact sequence, just tell me I can make a photo)

From lsmod -vnn I've found out that my SATA controller use kernel driver via_sata, but all I've found was /usr/src/linux-2.6.27.7/drivers/ata/sata_via.c, so I think that the controller is build into kernel.

What I've did wrong?

Last edited by semiRocket; 06-22-2009 at 10:41 PM.
 
Old 06-23-2009, 12:03 AM   #8
C-Sniper
Member
 
Registered: Dec 2006
Distribution: Slackware
Posts: 507

Rep: Reputation: 33
Beside the ancient thread revival did you read the CHANGES_AND_HINTS.TXT?
 
Old 06-23-2009, 12:18 AM   #9
semiRocket
LQ Newbie
 
Registered: Apr 2009
Location: Rijeka, Croatia
Distribution: Slackware 12.2
Posts: 16

Rep: Reputation: 0
Sorry about that but I have read CHANGES_AND_HINTS.TXT on the original dvd and it's saying see /boot/README.initrd for instructions, Which I did.

It's also saying something about udev but I can' understand if it's related to my situation.

I'm no expert

EDIT:
Here's the photo: http://i43.tinypic.com/2uikz9y.jpg
It is saying also that cannot find kernel modules but I all packages all installed, I did Full install

What does this mean?

Last edited by semiRocket; 06-23-2009 at 01:12 AM. Reason: Photo
 
Old 06-23-2009, 05:07 AM   #10
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,283
Blog Entries: 55

Rep: Reputation: Disabled
Is there an initrd.gz in /boot? Did you cd to /boot before running the mkinitrd command?
 
Old 06-23-2009, 07:24 AM   #11
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
It is saying also that cannot find kernel modules but I all packages all installed, I did Full install

What does this mean?
This is being reported by the loading of the initial ram disk. It can't find any modules (which it stores in the ramdisk itself). The ramdisk doesn't look to your main system at this point so the fact you did a full install has nothing to do with it.

You can have a look at the /boot/initrd-tree directory to see how this works. This is a temporary storage that is built into the ramdisk.

As it has been said it looks like something has gone wrong with creating the initial ramdisk (initrd.gz). Note that whenever you recreate the initrd you will have to rerun lilo to install it.
 
Old 06-23-2009, 09:56 AM   #12
semiRocket
LQ Newbie
 
Registered: Apr 2009
Location: Rijeka, Croatia
Distribution: Slackware 12.2
Posts: 16

Rep: Reputation: 0
Solved

Thank you guys I'm not sure what exactly went wrong, but I did what you told me and it worked

@brianL yes I have checked many times before the mkinitrd command created /boot/initrd-tree & initrd.gz. I don't remember if I went to /boot before compiling, but I thought it doesn't matter because it always creates those files in /boot.

@bgeddy I didn't know that, thank you
I think the missing modules in initrd was the cause
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
8 kobject_add failed reports from dmesg MCMM Slackware 18 06-01-2010 01:39 PM
please explain kobject_add failed DIGITAL39 Slackware 6 08-20-2007 10:49 PM
kobject_add failed for error using 2.6.21.1-smp davimint Slackware 9 06-14-2007 12:37 PM
kernel without uhci_hcd gives slow video. firedance Linux - Newbie 1 10-04-2005 01:58 AM


All times are GMT -5. The time now is 05:49 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration