Re: EISA & sysfs.

Greg KH
2004-02-18T18:44:10Z

On Wed, Feb 18, 2004 at 03:53:17PM +0000, Dave Jones wrote:
>
> ok, that stops it hanging at least, it now barfs a little failure
> message, and a calltrace. This seems awfully verbose for a failure
> path that isn't unreasonable IMO.
>
> kernel: kobject_register failed for hp100 (-17)
> kernel: Call Trace:
> kernel: [<c01d3662>] kobject_register+0x31/0x39
> kernel: [<c0221d0c>] bus_add_driver+0x2e/0x83
> kernel: [<c01db6db>] pci_register_driver+0x6b/0x87
> kernel: [<c78078ad>] hp100_module_init+0x12/0x22 [hp100]
> kernel: [<c013c0fc>] sys_init_module+0x14e/0x25e
> kernel: [<c010b697>] syscall_call+0x7/0xb

It's not "unresonable", it just means that someone messed up and we are
now letting the user/developer know. It's normally because someone
named their driver the same name as another one.

Actually, it's nice to see this message get printed out, and not the
"normal" oops that happens around this area for this case. Something
must be working correctly :)

I'll go fix that printk to put the proper KERN_ level on it...

thanks,

greg k-h