On 9/22/06, Larry Finger <[email protected]> wrote:
When we found the cause of NETDEV watchdog timeouts in the wireless-2.6 code,
I knew that the 2.6.18 release code would cause a serious regression.
I don't know if this is the lockup you're trying to address, but
2.6.18's bcm43xx has definitely regressed for me versus 2.6.17.x.
2.6.18 vanilla and 2.6.18 with your patch both lock my system hard
with bcm43xx. I've got an HP/Compaq nx6125 laptop. Symptoms are that
it will associate fine on its own and send traffic to/fro upon ifup,
but when I do an iwconfig, ifdown, ifup to change the access point,
the system locks (somewhat randomly) during one of those operations.
Well, the iwconfig or the ifup, actually.
lspci -v:
02:02.0 Network controller: Broadcom Corporation BCM4309 802.11a/b/g (rev 03)
Subsystem: Hewlett-Packard Company Unknown device 12f9
Flags: bus master, fast devsel, latency 64, IRQ 11
Memory at d0010000 (32-bit, non-prefetchable) [size=8K]
./bcm43xx-fwcutter -i BCMWL5.SYS
filename : bcmwl5.sys
version : 4.10.40.1
MD5 : 69f940672be0ecee5bd1e905706ba8ce
Wireless tools are Version: 28-1ubuntu2.
I've got multiple access points in view of the laptop, a g (54Mb), and
a b (11Mb). Neither with encryption enabled, if that makes a
difference (we live in the boonies).
It's 2.6.18 + your patch, compiled for x86_64, ubuntu devel.
Any suggestions or requests for tests?
Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
