2006-02-09 14:47:51

by Meelis Roos

Subject: megaraid bug in kobject_register when no device is present

Loading megaraid modules when no actual cards are present yields this in
dmesg. 2.6.16-rc2+git.

megasas: 00.00.02.02 Mon Jan 23 14:09:01 PST 2006
megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
megaraid: 2.20.4.7 (Release Date: Mon Nov 14 12:27:22 EST 2005)
kobject_register failed for megaraid (-17)
[<b01b0fa1>] kobject_register+0x43/0x5f
[<b020b5ad>] bus_add_driver+0x51/0xa8
[<b01bc812>] __pci_register_driver+0x5e/0x89
[<b011ca7c>] printk+0x17/0x1b
[<f0e89070>] megaraid_init+0x70/0x98 [megaraid_mbox]
[<b0136759>] sys_init_module+0x128/0x1bd
[<b01029a7>] sysenter_past_esp+0x54/0x75
megaraid: could not register hotplug support.

--
Meelis Roos ([email protected])

2006-02-09 16:25:44

by Greg KH

Subject: Re: megaraid bug in kobject_register when no device is present

On Thu, Feb 09, 2006 at 04:47:49PM +0200, Meelis Roos wrote:
> Loading megaraid modules when no actual cards are present yields this in
> dmesg. 2.6.16-rc2+git.
>
> megasas: 00.00.02.02 Mon Jan 23 14:09:01 PST 2006
> megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
> megaraid: 2.20.4.7 (Release Date: Mon Nov 14 12:27:22 EST 2005)
> kobject_register failed for megaraid (-17)

This means that the driver is trying to register with the same name as
another driver on the same bus.

Nice to see we at least recover from it and don't kill the kernel :)

thanks,

greg k-h

2006-02-09 19:14:20

by Ju, Seokmann

Subject: RE: megaraid bug in kobject_register when no device is present

Hi,

On Thursday, February 09, 2006 11:26 AM Greg KH wrote:
> This means that the driver is trying to register with the same name as
> another driver on the same bus.
It has been duplicated and made change in megaraid legacy driver.
The module name for the driver will be 'megaraid_legacy' from 'megaraid'.
Patch will be followed soon.

Thank you,

Seokmann