|
8 kobject_add failed reports from dmesg
Operating System:Slackware Version 12.0.0
Motherboard:abit IP35 Pro Socket 775 Chipset:Intel P35/ICH9R Command uname -r reports:2.6.21.5-smp Command uname -m reports:i686 Command uname -p reports:Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz /var/log/dmesg reports troublemakers 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 ehci_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 ======================= i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned by kernel) 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 ======================= ACPI: PCI Interrupt 0000:00:1f.3[b] -> GSI 18 (level, low) -> IRQ 20 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 ======================= ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22 PCI: Setting latency timer of device 0000:00:1b.0 to 64 kobject_add failed for ehci_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 ======================= 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 ======================= usbhid: exports duplicate symbol hiddev_hid_event (owned by kernel) usbhid: exports duplicate symbol hiddev_hid_event (owned by kernel) 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 Question: What will be the path to stop/get these troublemakers out of my machine ? If more infomation is needed please report in kind. |
There is a reason that some of us spend time writing documentation.
Please read over CHANGES_AND_HINTS.TXT on your installation cd. |
This is covered in other threads as well. Hint: try not using the huge kernel.
|
To:rworkman
Quote:
Note: If this statement is mint to be arrogant or nasty on your part and we were physically four feet apart your arrogance and nastiness would stop in less than a Detroit second. Also, in regard to your first statement are you the author of CHANGES_AND_HINTS_TXT or are you speaking on behalf of someone other than yourself ? The CHANGES_AND_HINTS.TXT documention is instructions for upgrading to Slackware 12.0 I did not upgrade to Slackware 12.0 Any more advice big mouth ? |
That file is meant for more then just upgrading, and yes, it's format can be a bit misleading. The information referred to is actually inside the section dedicated to upgrading from 11.0 (a few paragraphs after the 13 steps), so it's quite easy to miss. That section contains good general information information about slackware.
|
AFAIK, Robby maintained those file and send the updates to Patrick, so yes, he's one of the author of that file
CHANGES_AND_HINTS are not merely instructions for upgrading to 12.0, but also a list to see what has been changed since the development of Slackware 12.0 started and giving you some HINTS when you have problems using 12.0 due to big changes introduced in 12.0 compared to 11.0 (mainly kernel issues) |
MCMM, people (including rworkman) are very friendly on these forums, even to newbies. However, this particular question has been addressed many many times on these forums even though it is in the official documentation (although you may not have thought to read it). If you read rworkman's other posts, he really isn't a nasty guy. It's just that it seems these documents get written for no reason, plus this topic has been covered many times. A simple search for 'kobject' in the Slackware forum turned up a few unrelated and a few related threads, most of which address the problem. One thread that was brought up was "kobject_add failed for error using 2.6.21.1-smp", which seems pretty on the nose -- and all I did was search for kobject. All we ask for at these forums (and I'm assuming a collective "we", despite being one of the lesser beings here) is that you do a simple search before asking the question. No hard feelings though, and don't hold it against rworkman or others at these forums -- sometimes it's easier to write RTFM than to fully answer a repetitive question many times.
NOTE: The worst thing you could do next is ask why you're getting a "A security policy in place prevents this sender from sending this message to this recipient..." error when trying to automount something...check the HAL sticky thread at the top of the forums if you do. ;) |
Nice post, T3slider.
|
Quote:
Quote:
Quote:
Quote:
It just so happens that in 12.0, they're essentially the same thing, as there's no good way to separate the two. Quote:
Quote:
|
Quote:
[1] for random values of most |
rworkman, it'll be pretty hard to convince MCMM you're not a nasty guy now. ;) (Nice responses though -- had me laughing)
|
MCMM read the documentation first, and after you have/haven't read the documentation, search for the problem here or through Google, Then ask. A simple yet effective way to keep from getting on the nerves of people... especially the person that wrote the explanation and fix for it.
Just a suggestion. By the way, nice hat. |
How long is a Detroit second?
|
OK all, fun's over, back to the bear pit. I think MCMM has been jumped on enough now. The correct answer is to read the two .TXT files referred to above (and thanks to Robby for writing them). MCMM, if the answers given here/in the .TXT files aren't enough to fix the problem, post back here with the error messages you receive.
The post which pointed out the search terms is good advice - with over 300,000 members now, many questions have already been asked (more than once in some cases and interminably in others :)) and despite the speed of responses here it can be the speediest way to get an answer. And a Detroit second is slightly shorter than a real second, it's also around 2 feet taller. |
Here's the relevant bit from CHANGES_AND_HINTS.TXT:
Quote:
|
| All times are GMT -5. The time now is 02:13 PM. |