public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: sarcarsh@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: Boot time module loading problem
Date: Sun, 23 Dec 2007 20:54:00 -0800	[thread overview]
Message-ID: <476F3B68.9040702@lwfinger.net> (raw)
In-Reply-To: <476F11EE.7070204@gmail.com>

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

      reply	other threads:[~2007-12-24  4:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=476F3B68.9040702@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sarcarsh@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox