Search Linux Wireless

Re: brcmsmac: Unknown symbol backport_cordic_calc_iq (err 0)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 28, 2013 at 2:56 AM, Camaleón <noelamac@xxxxxxxxx> wrote:
> 2013/3/28 Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxx>:
>> On Thu, Mar 28, 2013 at 2:02 AM, Camaleón <noelamac@xxxxxxxxx> wrote:
>
> (...)
>
>>> Now, as soon as I proceed to load "brcmsmac" I get a long and
>>> uninterruptible "beeeeep", system hard-freezes (no mouse nor caps lock
>>> led reaction) and only restart is possible.
>>>
>>> Any clue?
>>
>> You are on 3.9.0-rc2, so there is nothing for us to backport on these
>> linux-next based releases except the delta between v3.9 and what is
>> not yet on Linus' tree, in other worlds just the development delta for
>> the 802.11 subsystem.
>
> I have two sets of kernels installed in this system: Debian's stock
> kernel (3.2.39-2) and another one I get from kernel.org (3.9.0-rc2).
>
> Now, what happens is that the compat-driver freezes with kernel 3.9
> and I get this message with kernel 3.2:
>
> [  684.589268] Compat-drivers backport release: compat-drivers-2013-03-26-u
> [  684.589279] Backport based on linux-next.git next-20130326
> [  684.589285] compat.git: linux-next.git
> [  684.609187] cfg80211: Unknown symbol
> backport_netdev_set_default_ethtool_ops (err 0)
>
> This driver is "driving" me nuts :-)

I have a fix for this, mind you, this is a Debian thing, that is --
debian cherry picked some code from a future kernel on their own
kernel. The new LINUX_BACKPORT() macro will rescue these. I'll post a
new release tomorrow, but I'm working on backporting some other
collateral evolutions right now.

>> We have yet to require any backport work between 3.9 and what we assume will be
>> 3.10. My bet is this is a real driver bug, not backport bug.
>
> Curious is that brcmsmac module loads fine from the common kernel
> module, I mean, the stock one.

What do you mean? Have you tried the stock driver from 3.9-rc2?

>> Can you
>>
>> git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
>>
>> and use your .config, and build and test that kernel ? If it fails to
>> boot / crash then you know its the driver.
>
> I'm not using git (don't even have it installed in my system), I'm
> used to compile kernels/modules in the old fashion way. Sorry, I don't
> know how git works.

make localmodconfig
make
make install

>> Has brcmsmac ever worked for you?
>
> Well, yes (this is a long story¹ with many helpful people doing their
> best). It stopped from working since kernel 2.38 or so, but even
> though the driver is giving me some headaches, it never froze the
> system like is doing now.
>
> ¹ http://marc.info/?t=136359599600001&r=1&w=2

Sorry to hear that, if its a driver issue I hope the maintainers will
jump in as they are Cc'd.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux