LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   >>Strange bootup message? (http://www.linuxquestions.org/questions/slackware-14/strange-bootup-message-581701/)

muttdawg 09-02-2007 03:09 PM

>>Strange bootup message?
 
When booting Slack 12.0 I get the following message:

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
=======================
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
=======================
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned by kernel)

I'm using the stock kernel. It's displayed this message since I first rebooted into the new system. I don't know enough to be concerned. Nevertheless I'm curious.

Alien Bob 09-02-2007 03:21 PM

No need to be concerned.
You are booting with a "huge" kernel which has a great many of kernel drivers built into the kernel. You also installed the kernel-modules package which has a lot of the above drivers as kernel modules (to be used primarily with one of the "generic" kernels which are smaller than the "huge" kernels because they use drivers compiled as modules).

Your hardware hotplugging system (UDEV) finds hardware during boot and tries to load the appropriate drivers for it (the kernel modules) but when these modules load, the kernel complains because these drivers are already part of the kernel (part of the "huge" kernel).
The messages you see are thus harmless but annoying to see. You can solve this by reconfiguring lilo so that it will boot a "generic" kernel. In this case you will need to create an initrd (initial ramdisk) which contains the filesystem drivers for your root partition... the "generic" kernel does not contain any filesystem driver itself.
Read the information in /boot/README.initrd if you have doubts about how to create an initrd for your Slackware and how to configure lilo for it.

Eric

muttdawg 09-02-2007 05:25 PM

Eric,

"You can solve this by reconfiguring lilo so that it will boot a "generic" kernel. In this case you will need to create an initrd (initial ramdisk) which contains the filesystem drivers for your root partition... the "generic" kernel does not contain any filesystem driver itself."

Sounds like fun. I recall doing something like that back in 10.x days when wanting to go with a 2.6 as opposed to the stock 2.4. (If I remember correctly). I missed all the 11.x releases. Looks like I've got some catching up to do.

Thanks for your help/advice.


All times are GMT -5. The time now is 08:48 PM.