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

2006-12-18 Thread Ingo Molnar
* Jiri Slaby <[EMAIL PROTECTED]> wrote: > Ingo Molnar wrote: > > * Jiri Slaby <[EMAIL PROTECTED]> 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 l

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

2006-12-18 Thread Jiri Slaby
Ingo Molnar wrote: > * Jiri Slaby <[EMAIL PROTECTED]> 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. > > cur

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

2006-12-18 Thread Jiri Slaby
Ingo Molnar wrote: > * Jiri Slaby <[EMAIL PROTECTED]> 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. > > cur

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

2006-12-18 Thread Ingo Molnar
* Jiri Slaby <[EMAIL PROTECTED]> 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 -

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

2006-12-18 Thread Jiri Slaby
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() > kobje