Messages in this thread |  | | Date | Mon, 20 Nov 2006 09:27:33 -0800 | From | Greg KH <> | Subject | Re: kobject_add failed with -EEXIST |
| |
On Mon, Nov 20, 2006 at 06:14:56PM +0100, Jiri Slaby wrote: > Hi! > > Does anybody have some clue, what's wrong with the attached module? > Kernel complains when the module is insmoded second time (DRIVER_DEBUG enabled): > > > cls_init FIRST TIME > device class 'cls_class': registering > DEV: registering device: ID = 'cls_device' > PM: Adding info for No Bus:cls_device > DEV: Unregistering device. ID = 'cls_device' > PM: Removing info for No Bus:cls_device > device_create_release called for cls_device > device class 'cls_class': unregistering > class 'cls_class': release. > class_create_release called for cls_class > cls_exit
What does sysfs look like at this point in time? Does /sys/class/cls_class exist?
Also, which kernel version are you using here?
thanks,
greg k-h - 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/
|  |