Peter Osterlund <[EMAIL PROTECTED]> writes: > Michael Buesch <[EMAIL PROTECTED]> writes: > > > On Friday 04 August 2006 01:31, Peter Osterlund wrote: > > > "Ivan Matveich" <[EMAIL PROTECTED]> writes: > > > > > > > [interface works fine for a few hours, then this spontaneously happens] > > > > [note: the computer does nothing but compile stuff, etc during this > > > > time] > > > > > > > > NETDEV WATCHDOG: wireless: transmit timed out > > > > bcm43xx: Controller RESET (TX timeout) ... > > > > bcm43xx: select_wireless_core: cleanup > > > > bcm43xx: Radio turned off > > > > bcm43xx: DMA 0x0200 (RX) max used slots: 1/64 > > > > bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 > > > > bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 > > > > bcm43xx: DMA 0x0220 (TX) max used slots: 70/512 > > > > bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 > > > > bcm43xx: Radio turned on > > > > bcm43xx: Chip initialized > > > > bcm43xx: DMA initialized > > > > bcm43xx: Keys cleared > > > > bcm43xx: Selected 802.11 core (phytype 2) > > > > bcm43xx: Controller restarted > > > > > > > > [now the interface stops working: pings no longer go through] > > > > > > I've seen this too and I also use a preemptable kernel. In my case the > > > problem goes away if I increase BADNESS_LIMIT to 20 in bcm43xx_main.c. > > > Therefore, my guess is that the new locking strategy isn't > > > preempt-safe. (I haven't tested a non-preemptable kernel though.) > > > > That might be wrong guesswork. ... > > To verify: Does it also go away, if you stay away from BADNESS_LIMIT > > and disable preemption? To do that, you must disable CONFIG_PREEMPT > > and make the function bcm43xx_voluntary_preempt() in bcm43xx_phy.c > > a NOP (return early). > > I just booted a linville wireless git tree kernel with these changes. > Now I'll just have to wait a few hours to see what happens.
This version also stopped working after about 2.5 hours of uptime. It doesn't lock up the system, but instead ksoftirqd starts using 100% CPU time, and the only way to stop that seems to be a reboot. I use wpa_supplicant. From /var/log/messages: Aug 5 02:24:23 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 Aug 5 03:31:49 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 Aug 5 03:31:49 r3000 kernel: NETDEV WATCHDOG: eth1: transmit timed out Aug 5 03:31:49 r3000 kernel: bcm43xx: Controller RESET (TX timeout) ... Aug 5 03:31:49 r3000 kernel: bcm43xx: select_wireless_core: cleanup Aug 5 03:31:49 r3000 kernel: bcm43xx: Radio turned off Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA 0x0200 (RX) max used slots: 2/64 Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA 0x0220 (TX) max used slots: 5/512 Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 Aug 5 03:31:49 r3000 kernel: bcm43xx: Radio turned on Aug 5 03:31:49 r3000 kernel: bcm43xx: Chip initialized Aug 5 03:31:49 r3000 kernel: bcm43xx: DMA initialized Aug 5 03:31:49 r3000 kernel: bcm43xx: Keys cleared Aug 5 03:31:49 r3000 kernel: bcm43xx: Selected 802.11 core (phytype 2) Aug 5 03:31:49 r3000 kernel: bcm43xx: Controller restarted Aug 5 03:34:26 r3000 kernel: bcm43xx: Radio turned off Aug 5 03:34:26 r3000 kernel: bcm43xx: DMA 0x0200 (RX) max used slots: 0/64 Aug 5 03:34:26 r3000 kernel: bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 Aug 5 03:34:26 r3000 kernel: bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 Aug 5 03:34:26 r3000 kernel: bcm43xx: DMA 0x0220 (TX) max used slots: 13/512 Aug 5 03:34:26 r3000 kernel: bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 Aug 5 03:34:26 r3000 avahi-daemon[3105]: Interface eth1.IPv4 no longer relevant for mDNS. Aug 5 03:34:26 r3000 avahi-daemon[3105]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.9. Aug 5 03:34:26 r3000 avahi-daemon[3105]: Withdrawing address record for 192.168.1.9 on eth1. Aug 5 03:34:27 r3000 nmbd[3063]: [2006/08/05 03:34:27, 0] libsmb/nmblib.c:send_udp(791) Aug 5 03:34:27 r3000 nmbd[3063]: Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable Aug 5 03:34:27 r3000 nmbd[3063]: [2006/08/05 03:34:27, 0] nmbd/nmbd_packets.c:retransmit_or_expire_response_records(1611) Aug 5 03:34:27 r3000 nmbd[3063]: retransmit_or_expire_response_records: Failed to resend packet id 23105 to IP 192.168.1.255 on subnet 192.168.1.9 Aug 5 03:34:28 r3000 nmbd[3063]: [2006/08/05 03:34:28, 0] libsmb/nmblib.c:send_udp(791) Aug 5 03:34:28 r3000 nmbd[3063]: Packet send failed to 192.168.1.255(137) ERRNO=Network is unreachable Aug 5 03:34:28 r3000 nmbd[3063]: [2006/08/05 03:34:28, 0] nmbd/nmbd_packets.c:send_netbios_packet(163) Aug 5 03:34:28 r3000 nmbd[3063]: send_netbios_packet: send_packet() to IP 192.168.1.255 port 137 failed Aug 5 03:34:28 r3000 nmbd[3063]: [2006/08/05 03:34:28, 0] nmbd/nmbd_nameregister.c:register_name(512) Aug 5 03:34:28 r3000 nmbd[3063]: register_name: Failed to send packet trying to register name HEMMA<1d> -- Peter Osterlund - [EMAIL PROTECTED] http://web.telia.com/~u89404340 _______________________________________________ Bcm43xx-dev mailing list [email protected] http://bat.berlios.de/mailman/listinfo/bcm43xx-dev
