[Voyage-linux] Problems with alix 2d3 and madwifi on voyage-current (lenny)

[Panagiotis Malakoudis]

I updated one of my ALIX 2D3 systems with voyage-current (lenny) and I keep
getting messages like:
wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
or
wifi0: ath_rxorn_tasklet: Receive FIFO overrun; resetting.
and even this some times
NETDEV WATCHDOG: wifi0: transmit timed out
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:223 dev_watchdog+0x8a/0xe2()
 [<c0113530>] warn_on_slowpath+0x40/0x65
 [<c0128b17>] tick_handle_periodic+0xc/0x55
 [<d0922b9c>] zz00050ae3+0xdc/0xf0 [ath_hal]
 [<d09a11b1>] ath_set_ack_bitrate+0x161/0x168 [ath_pci]
 [<d0989c13>] ath_reset+0x223/0x263 [ath_pci]
 [<c025872a>] dev_watchdog+0x0/0xe2
 [<c025872a>] dev_watchdog+0x0/0xe2
 [<c02587b4>] dev_watchdog+0x8a/0xe2
 [<c0119f2c>] run_timer_softirq+0xfc/0x15d
 [<c0116f73>] __do_softirq+0x35/0x75
 [<c0116fd5>] do_softirq+0x22/0x26
 [<c011713b>] irq_exit+0x25/0x5d
 [<c0104f35>] do_IRQ+0x50/0x60
 [<c0103973>] common_interrupt+0x23/0x30

I've read in some fora that this might be fixed if you build kernel and
madwifi tools with latest gcc - 4.3.2 (it seems that current voyage kernel
is built with gcc 4.1.2), so I am going to try that, but I first would like
to know if any other people experience such kind of problems.
I run my CM9 atheros card as an Access Point bridged with eth0, with
WPA2-PSK.

I never had any such problems with voyage 0.5.2 in this configuration.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20090216/9c15525a/attachment-0001.html>