Re: kernel oops with extended serial stuff turned on...

[Greg KH <greg@kroah.com>]

On Wed, Oct 18, 2006 at 05:35:17PM -0500, Kilau, Scott wrote:
> Hi Greg,
> 
> > 
> > I don't understand, what problem is occuring here?  Who is trying to
> > register with sysfs twice?
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> The original warning/error he gets is:
> 
> > kobject_add failed for ttyM0 with -EEXIST, don't try to register
> things
> > with the same name in the same directory.
> 
> Presumably this means that "ttyM0" was already registered with
> sysfs/udev already...

Yes (sysfs, not udev, there is no kernel portion of udev, sorry).

> In my out-of-tree driver's case, I used to use "TTY_DRIVER_NO_DEVFS" as
> a flag.
> 
> When that flag went away, I did not put in "TTY_DRIVER_DYNAMIC_DEV" by
> mistake,
> and I got the same error as Greg C.
> I had to push in "TTY_DRIVER_DYNAMIC_DEV" to fix my problem...

What other driver is using the ttyM0 name?

> I don't know much (anything) about the isicom.c driver, so maybe I am
> reading
> something into that error that shouldn't be read into it...

Any pointer to your driver's code so I can see if you are doing
something odd here?  Any reason it's just not in the main kernel tree so
I would have fixed it up at the time I did the other fixes?

thanks,

greg k-h