public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Boot time module loading problem
       [not found]             ` <476E3D6D.1010203@gmail.com>
@ 2007-12-23 19:39               ` Larry Finger
  2007-12-23 20:05                 ` Johannes Berg
                                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Larry Finger @ 2007-12-23 19:39 UTC (permalink / raw)
  To: LKML; +Cc: sarcarsh, Johannes Berg, bcm43xx-dev

With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43 module, which should be loaded by
the ssb module, fails with the following type of message:

ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
b43: disagrees about version of symbol ssb_device_is_enabled
b43: Unknown symbol ssb_device_is_enabled
b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
b43: disagrees about version of symbol ssb_bus_may_powerdown
b43: Unknown symbol ssb_bus_may_powerdown

< and more similar lines....>

If the user issues the commands

rmmod ssb; modprobe b43

then the modules are loaded correctly and the wireless device works.

What could be causing such a problem?

Larry


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Boot time module loading problem
  2007-12-23 19:39               ` Boot time module loading problem Larry Finger
@ 2007-12-23 20:05                 ` Johannes Berg
  2007-12-23 21:25                 ` Michael Buesch
  2007-12-24  1:57                 ` Shourya Sarcar
  2 siblings, 0 replies; 5+ messages in thread
From: Johannes Berg @ 2007-12-23 20:05 UTC (permalink / raw)
  To: Larry Finger; +Cc: LKML, bcm43xx-dev

[-- Attachment #1: Type: text/plain, Size: 166 bytes --]


> What could be causing such a problem?

I would guess that user has "ssb" loaded from his initrd for some reason
and upgraded the modules by hand.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Boot time module loading problem
  2007-12-23 19:39               ` Boot time module loading problem Larry Finger
  2007-12-23 20:05                 ` Johannes Berg
@ 2007-12-23 21:25                 ` Michael Buesch
  2007-12-24  1:57                 ` Shourya Sarcar
  2 siblings, 0 replies; 5+ messages in thread
From: Michael Buesch @ 2007-12-23 21:25 UTC (permalink / raw)
  To: bcm43xx-dev; +Cc: Larry Finger, LKML, Johannes Berg

On Sunday 23 December 2007 20:39:18 Larry Finger wrote:
> With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43 module, which should be loaded by
> the ssb module, fails with the following type of message:
> 
> ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
> b43: disagrees about version of symbol ssb_device_is_enabled
> b43: Unknown symbol ssb_device_is_enabled
> b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
> b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
> b43: disagrees about version of symbol ssb_bus_may_powerdown
> b43: Unknown symbol ssb_bus_may_powerdown

This is a module versioning warning.
I think it's caused by a b43 compiled against a different
kernel tree than the currently running ssb module.
Different may mean that only a tiny little thing was changed, which
might not affect the API at all. modversion will complain then.

I don't use module versioning, so I can't help you how to fix this.
I'd simply suggest turning off module versioning.

-- 
Greetings Michael.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Boot time module loading problem
  2007-12-23 19:39               ` Boot time module loading problem Larry Finger
  2007-12-23 20:05                 ` Johannes Berg
  2007-12-23 21:25                 ` Michael Buesch
@ 2007-12-24  1:57                 ` Shourya Sarcar
  2007-12-24  4:54                   ` Larry Finger
  2 siblings, 1 reply; 5+ messages in thread
From: Shourya Sarcar @ 2007-12-24  1:57 UTC (permalink / raw)
  To: Larry Finger; +Cc: LKML, Johannes Berg, bcm43xx-dev

Larry Finger wrote:
> With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43
> module, which should be loaded by the ssb module, fails with the
> following type of message:
> 
> ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0 b43:
> disagrees about version of symbol ssb_device_is_enabled b43: Unknown
> symbol ssb_device_is_enabled b43: disagrees about version of symbol
> ssb_pcicore_dev_irqvecs_enable b43: Unknown symbol
> ssb_pcicore_dev_irqvecs_enable b43: disagrees about version of symbol
> ssb_bus_may_powerdown b43: Unknown symbol ssb_bus_may_powerdown
> 
> < and more similar lines....>
> 
> If the user issues the commands
> 
> rmmod ssb; modprobe b43
> 
> then the modules are loaded correctly and the wireless device works.
> 
> What could be causing such a problem?
> 
> Larry
> 

Larry, thanks for pursuing this. I upgraded to 2.6.24-rc6 last night and
I don't see this issue anymore. One might think that the clean remake
solved the problem (which I am pretty sure I did with rc5 as well); but 
still does not explain with 2.6.24-rc5, the module would not load on 
first attempt but then load after the manual:

# rmmod ssb;modprobe b43

Best regards,
Shourya





^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Boot time module loading problem
  2007-12-24  1:57                 ` Shourya Sarcar
@ 2007-12-24  4:54                   ` Larry Finger
  0 siblings, 0 replies; 5+ messages in thread
From: Larry Finger @ 2007-12-24  4:54 UTC (permalink / raw)
  To: sarcarsh; +Cc: LKML, Johannes Berg, bcm43xx-dev

Shourya Sarcar wrote:
> Larry Finger wrote:
>> With 2.6.24-rc5, a b43 user reports a problem at bootup. The b43
>> module, which should be loaded by the ssb module, fails with the
>> following type of message:
>>
>> ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0 b43:
>> disagrees about version of symbol ssb_device_is_enabled b43: Unknown
>> symbol ssb_device_is_enabled b43: disagrees about version of symbol
>> ssb_pcicore_dev_irqvecs_enable b43: Unknown symbol
>> ssb_pcicore_dev_irqvecs_enable b43: disagrees about version of symbol
>> ssb_bus_may_powerdown b43: Unknown symbol ssb_bus_may_powerdown
>>
>> < and more similar lines....>
>>
>> If the user issues the commands
>>
>> rmmod ssb; modprobe b43
>>
>> then the modules are loaded correctly and the wireless device works.
>>
>> What could be causing such a problem?
>>
>> Larry
>>
> 
> Larry, thanks for pursuing this. I upgraded to 2.6.24-rc6 last night and
> I don't see this issue anymore. One might think that the clean remake
> solved the problem (which I am pretty sure I did with rc5 as well); but
> still does not explain with 2.6.24-rc5, the module would not load on
> first attempt but then load after the manual:
> 
> # rmmod ssb;modprobe b43

Johannes may have been right and that you had a stale initrd. I was going to have you try a 'sudo
mkinitrd', but it is now fixed.

Larry

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-12-24  4:54 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <476D38F9.4090802@gmail.com>
     [not found] ` <476D567D.3020401@lwfinger.net>
     [not found]   ` <476DE108.6030306@gmail.com>
     [not found]     ` <476DFC95.9010904@lwfinger.net>
     [not found]       ` <476E2A19.1080205@gmail.com>
     [not found]         ` <1198402827.4058.0.camel@johannes.berg>
     [not found]           ` <1198404567.4058.2.camel@johannes.berg>
     [not found]             ` <476E3D6D.1010203@gmail.com>
2007-12-23 19:39               ` Boot time module loading problem Larry Finger
2007-12-23 20:05                 ` Johannes Berg
2007-12-23 21:25                 ` Michael Buesch
2007-12-24  1:57                 ` Shourya Sarcar
2007-12-24  4:54                   ` Larry Finger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox