From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Jiri Slaby <jirislaby@gmail.com>
Subject: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
Date: Mon, 18 Dec 2006 16:57:15 +0100 [thread overview]
Message-ID: <20061218155714.GA21823@elte.hu> (raw)
allyesconfig bzImage bootup produced 33 warning messages, of which the
first couple are attached below.
Ingo
--------------->
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
[<c05f97fa>] tty_register_driver+0x202/0x21e
[<c0628fa3>] isicom_setup+0x24a/0x315
[<c0100567>] init+0x178/0x451
[<c0105feb>] kernel_thread_helper+0x7/0x10
=======================
kobject_add failed for ttyM1 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
[<c05f97fa>] tty_register_driver+0x202/0x21e
[<c0628fa3>] isicom_setup+0x24a/0x315
[<c0100567>] init+0x178/0x451
[<c0105feb>] kernel_thread_helper+0x7/0x10
=======================
kobject_add failed for ttyM2 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
[<c05f97fa>] tty_register_driver+0x202/0x21e
[<c0628fa3>] isicom_setup+0x24a/0x315
[<c0100567>] init+0x178/0x451
[<c0105feb>] kernel_thread_helper+0x7/0x10
=======================
kobject_add failed for ttyM3 with -EEXIST, don't try to register things with the same name in the same directory.
next reply other threads:[~2006-12-18 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 15:57 Ingo Molnar [this message]
2006-12-18 16:57 ` bug: isicom: kobject_add failed for ttyM0 with -EEXIST Jiri Slaby
2006-12-18 20:00 ` Ingo Molnar
2006-12-18 20:04 ` Jiri Slaby
2006-12-18 20:31 ` Jiri Slaby
2006-12-18 20:40 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061218155714.GA21823@elte.hu \
--to=mingo@elte.hu \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.