linux-kernel - Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer

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: <200712172345.20710.mb@bu3sch.de>
Date:	Mon, 17 Dec 2007 23:45:19 +0100
From:	Michael Buesch <mb@...sch.de>
To:	mvtodevnull@...il.com
Cc:	"Larry Finger" <larry.finger@...inger.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Daniel Walker" <dwalker@...sta.com>,
	"Ray Lee" <ray-lk@...rabbit.org>,
	"Simon Holm Thøgersen" <odie@...aau.dk>,
	matthias.kaehlcke@...il.com, linux-kernel@...r.kernel.org,
	linux@...mer.net, "Ingo Molnar" <mingo@...e.hu>,
	kjwinchester@...il.com, jonathan@...masters.org,
	akpm@...ux-foundation.org, bcm43xx-dev@...ts.berlios.de
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex

On Monday 17 December 2007 23:04:37 mvtodevnull@...il.com wrote:
> On Dec 17, 2007 5:35 AM,  <mvtodevnull@...il.com> wrote:
> > If this is a mac80211 related problem, then other systems connecting
> > to the same ap and using mac80211 would also be affected? Like I said
> > earlier, there are five machines connecting to this ap, and I just
> > realized one of them has a ralink card that uses the rt2x00 driver,
> > which I believe is mac80211. That system doesn't have this problem,
> > which leads me to believe it may not be mac80211 after all, although I
> > wouldn't rule it out.
> >
> 
> This also doesn't seem to be related to firmware version. I forced my
> device to use b43legacy, and the results were identical with the
> version 3 firmware.

Ehm, excuse me.
What are you doing exactly? In this thread you told me you have
a device which requires b43:

> I don't know what happened before, but after a reboot, I can't repeat
> the 200 kB/s speed. It's back down to 40 kB/s, just like originally. I
> didn't move the laptop, or the ap, the only thing I can think of that
> might have changed is the noise level. FWIW, link quality is
> consistently the same or better with b43.

How the hell can you now "force it to use b43legacy"??

-- 
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/