Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST

[Jiri Slaby <jirislaby@gmail.com>]

Ingo Molnar wrote:
> * Jiri Slaby <jirislaby@gmail.com> wrote:
> 
>> Ingo Molnar wrote:
>>> allyesconfig bzImage bootup produced 33 warning messages, of which the 
>>> first couple are attached below.
>> With which kernel? mxser had ttyM for a long time, it should be fixed 
>> in 2.6.20-rc1.
> 
> current -git.

It's rather impossible. Aren't you seeked somewhere (I'm in
825020c3866e7312947e17a0caa9dd1a5622bafc now)?

Calling initcall 0xc0628d59: isicom_setup+0x0/0x315()
kobject_add failed for ttyM0 with -EEXIST, don't try to register things with the
same name in the same directory.
 [<c0106273>] show_trace_log_lvl+0x34/0x4a
 [<c01063a9>] show_trace+0x2c/0x2e
 [<c01063d6>] dump_stack+0x2b/0x2d
 [<c04f06a3>] kobject_add+0x15f/0x187
 [<c06e3421>] class_device_add+0xb5/0x45c
 [<c06e37e5>] class_device_register+0x1d/0x21
 [<c06e3892>] class_device_create+0xa9/0xcc
 [<c05f8a5c>] tty_register_device+0xe3/0xea

Can't be called from tty_register_driver, since
!(driver->flags & TTY_DRIVER_DYNAMIC_DEV) is false in
http://www.linux-m32r.org/lxr/http/source/drivers/char/tty_io.c#L3756

 [<c05f97fa>] tty_register_driver+0x202/0x21e
 [<c0628fa3>] isicom_setup+0x24a/0x315

Is no longer in the isicom driver.

 [<c0100567>] init+0x178/0x451
 [<c0105feb>] kernel_thread_helper+0x7/0x10
 =======================

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/