linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* bug: isicom: kobject_add failed for ttyM0 with -EEXIST
@ 2006-12-18 15:57 Ingo Molnar
  2006-12-18 16:57 ` Jiri Slaby
  0 siblings, 1 reply; 6+ messages in thread
From: Ingo Molnar @ 2006-12-18 15:57 UTC (permalink / raw)
  To: linux-kernel; +Cc: Jiri Slaby


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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
  2006-12-18 15:57 bug: isicom: kobject_add failed for ttyM0 with -EEXIST Ingo Molnar
@ 2006-12-18 16:57 ` Jiri Slaby
  2006-12-18 20:00   ` Ingo Molnar
  0 siblings, 1 reply; 6+ messages in thread
From: Jiri Slaby @ 2006-12-18 16:57 UTC (permalink / raw)
  To: Ingo Molnar; +Cc: linux-kernel

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.


> --------------->
> 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
>  =======================
[...]

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
  2006-12-18 16:57 ` Jiri Slaby
@ 2006-12-18 20:00   ` Ingo Molnar
  2006-12-18 20:04     ` Jiri Slaby
  2006-12-18 20:31     ` Jiri Slaby
  0 siblings, 2 replies; 6+ messages in thread
From: Ingo Molnar @ 2006-12-18 20:00 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: linux-kernel


* 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.

	Ingo

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
  2006-12-18 20:00   ` Ingo Molnar
@ 2006-12-18 20:04     ` Jiri Slaby
  2006-12-18 20:31     ` Jiri Slaby
  1 sibling, 0 replies; 6+ messages in thread
From: Jiri Slaby @ 2006-12-18 20:04 UTC (permalink / raw)
  To: Ingo Molnar; +Cc: linux-kernel

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.

Ok, thanks, I'll check it,
-- 
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Jiri Slaby @ 2006-12-18 20:31 UTC (permalink / raw)
  To: Ingo Molnar; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST
  2006-12-18 20:31     ` Jiri Slaby
@ 2006-12-18 20:40       ` Ingo Molnar
  0 siblings, 0 replies; 6+ messages in thread
From: Ingo Molnar @ 2006-12-18 20:40 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: linux-kernel


* Jiri Slaby <jirislaby@gmail.com> wrote:

> 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)?

indeed it was a v2.6.19 base - sorry! I'll re-report if there's any 
problem left.

	Ingo


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-12-18 20:42 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-18 15:57 bug: isicom: kobject_add failed for ttyM0 with -EEXIST Ingo Molnar
2006-12-18 16:57 ` 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).