I built voyage kernel inside voyage-current (with gcc 4.3.2) and all the previous problems I mentioned almost disappeared. With the kernel (and madwifi modules) built with gcc 4.1.2 , I had hundreds of messages per hour in the dmesg. Now, after 10 hours running the new kernel, I only have two such messages.<br>
wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)<br><br>So the situation improved very much, but is not yet perfect. Next I'll try with newer madwifi version (the 3772 that voyage/lenny ships is from 15th of July 2008 - quite old). Latest is 3952.<br>
<br><br><div class="gmail_quote">On Mon, Feb 16, 2009 at 12:23 AM, Panagiotis Malakoudis <span dir="ltr"><<a href="mailto:malakudi@gmail.com">malakudi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I updated one of my ALIX 2D3 systems with voyage-current (lenny) and I keep getting messages like:<br>wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)<br>or<br>wifi0: ath_rxorn_tasklet: Receive FIFO overrun; resetting.<br>
and even this some times<br>NETDEV WATCHDOG: wifi0: transmit timed out<br>------------[ cut here ]------------<br>WARNING: at net/sched/sch_generic.c:223 dev_watchdog+0x8a/0xe2()<br> [<c0113530>] warn_on_slowpath+0x40/0x65<br>
[<c0128b17>] tick_handle_periodic+0xc/0x55<br> [<d0922b9c>] zz00050ae3+0xdc/0xf0 [ath_hal]<br> [<d09a11b1>] ath_set_ack_bitrate+0x161/0x168 [ath_pci]<br> [<d0989c13>] ath_reset+0x223/0x263 [ath_pci]<br>
[<c025872a>] dev_watchdog+0x0/0xe2<br> [<c025872a>] dev_watchdog+0x0/0xe2<br> [<c02587b4>] dev_watchdog+0x8a/0xe2<br> [<c0119f2c>] run_timer_softirq+0xfc/0x15d<br> [<c0116f73>] __do_softirq+0x35/0x75<br>
[<c0116fd5>] do_softirq+0x22/0x26<br> [<c011713b>] irq_exit+0x25/0x5d<br> [<c0104f35>] do_IRQ+0x50/0x60<br> [<c0103973>] common_interrupt+0x23/0x30<br><br>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.<br>
I run my CM9 atheros card as an Access Point bridged with eth0, with WPA2-PSK.<br><br>I never had any such problems with voyage 0.5.2 in this configuration.<br><br>
</blockquote></div><br>