linux-kernel - Re: bcm43xx regression in 2.6.24 (with patch)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200802290012.56654.s.L-H@gmx.de>
Date:	Fri, 29 Feb 2008 00:12:55 +0100
From:	Stefan Lippers-Hollmann <s.L-H@....de>
To:	"Alexey Zaytsev" <alexey.zaytsev@...il.com>
Cc:	"Michael Buesch" <mb@...sch.de>,
	"John W. Linville" <linville@...driver.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Alexey Zaytsev" <zaytsev.a@...tei.ru>, "Greg KH" <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Re: bcm43xx regression in 2.6.24 (with patch)

Hi

On Donnerstag, 28. Februar 2008, Alexey Zaytsev wrote:
> On Fri, Feb 29, 2008 at 1:03 AM, Michael Buesch <mb@...sch.de> wrote:
> > On Tuesday 26 February 2008 23:41:55 Michael Buesch wrote:
> >  > On Tuesday 26 February 2008 23:12:32 Alexey Zaytsev wrote:
> >  > > >  Yeah, seems so. But if you are willing to test an adjusted version, I can
> >  > > >  probably do a backported version of this patch.
> >  > > >  This patch is well tested and does the right thing, so I'm willing to sign
> >  > > >  off a backported version of this.
> >  > > >  First need to find the place in the old phy.c code that matches the new wa.c code.
> >  > > >
> >  > > I'll do the testing.
> >  >
[...]
> >
> >  So are you actually going to do this anytime soon?
> >
> 
> Sorry for the delay. Yes, it worked fine.
> 
> Btw, when booting the system with the b43 driver, I get a
> ~30 socond delay after the boot scripts report
> "Waiting for /dev to be fully populated" and all the modules
> get loaded. Is this something expected?

That is most likely udev related, which doesn't really like module names 
and default interface names changing for a known MAC address, depending on 
your distribution (the following example assumes debian sid, udev 0.114-2) 
you might have something like /etc/udev/rules.d/z25_persistent-net.rules 
(which lists MAC addresses and the associated persistent interface name), 
removing the corresponding stanza for your Broadcom wireless card (or 
removing the whole file alltogether and letting udev (or rather 
z45_persistent-net-generator.rules) recreate it during the next boot will 
most likely fix it. 

This issue is in no way b43 related, it happens with "every" networking 
devices with changing module names (at least for every legacy wireless 
module being replaced by a new mac80211 based driver).

Regards
	Stefan Lippers-Hollmann

Download attachment "signature.asc " of type "application/pgp-signature" (190 bytes)