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

Panagiotis Malakoudis (spam-protected)
Sat Feb 21 23:58:38 HKT 2009 

Which of the options discussed in this article solved your problems?

I was aware of this article, however the madwifi team should acknoledge that
this problem started somewhere after the 2.6.23 kernel and they should track
down the problem in their madwifi source instead of trying to convince users
it's their problem, motherboard problem etc etc. To me it seems there is a
problem to how linux kernel handles irqs and dma transfers after 2.6.23 in
relation to madwifi.


On Sat, Feb 21, 2009 at 2:35 PM, Juergen Adolph <ja at coffeecrew.net> wrote:

> Hi Punky,
>
> many thanks for this info! now, it works fine for me.
>
> Regards,
> Juergen
>
> ----- "Punky Tse" <punkytse at punknix.com> schrieb:
>
> > Hi,
> >
> > For your leisure reading, please find this in-depth information on
> > stuck
> > beacon problem:
> >
> >     http://madwifi-project.org/wiki/StuckBeacon
> >
> > Regards,
> > Punky
> >
> >
> > Juergen Adolph wrote:
> > > Hi Panky,
> > >
> > > first thanks for the 0.6.1 and recompiling the kernel with gcc
> > 4.3.2,
> > > but does not work for me!
> > >
> > > dmesg:
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > > wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
> > count: 11)
> > >
> > >
> > > any clue?
> > >
> > >
> > > -ja
> > >
> > > ----- "Punky Tse" <punkytse at punknix.com> schrieb:
> > >
> > >
> > >> Hi,
> > >>
> > >> Voyage kernel in 0.6.1 is now compiled under Lenny, hence it make
> > use
> > >> if
> > >> gcc 4.3.2 now.
> > >>
> > >> - Punky
> > >>
> > >>
> > >> Panagiotis Malakoudis wrote:
> > >>
> > >>> As I said in my follow up message, building the linux voyage
> > kernel
> > >>>
> > >>> inside voyage-current (thus making use of lenny's gcc 4.3.2)
> > almost
> > >>>
> > >>> eliminates the problem. After 24 hours uptime, I only got five
> > >>>
> > >> "stuck
> > >>
> > >>> beacon" lines in my dmesg, and the performance is great. I
> > haven't
> > >>>
> > >> yet
> > >>
> > >>> tried any newer version of madwifi.
> > >>>
> > >>> I would suggest the voyage team to build the voyage kernel under a
> >
> > >>> voyage-current (lenny) environment on the 0.6.1 release.
> > >>>
> > >>>
> > >>> On Mon, Feb 16, 2009 at 8:23 PM, Ward Vandewege <ward at pong.be
> > >>> <mailto:ward at pong.be>> wrote:
> > >>>
> > >>>     On Mon, Feb 16, 2009 at 07:17:51PM +0100, Juergen Adolph
> > wrote:
> > >>>     > Hello,
> > >>>     >
> > >>>     > accurately the same hardware/config. accurately the same
> > >>>
> > >> problem!
> > >>
> > >>>     I'm seeing the same problem on alix 2c3 with madwifi and
> > >>>     voyage-current.
> > >>>
> > >>>     Thanks,
> > >>>     Ward.
> > >>>
> > >>>     > ----- "Panagiotis Malakoudis" <malakudi at gmail.com
> > >>>     <mailto:malakudi at gmail.com>> schrieb:
> > >>>     >
> > >>>     > > 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.
> > >>>     > >
> > >>>     > >
> > >>>     > > _______________________________________________
> > >>>     > > Voyage-linux mailing list
> > >>>     > > Voyage-linux at list.voyage.hk
> > >>>
> > >> <mailto:Voyage-linux at list.voyage.hk>
> > >>
> > >>>     > > http://list.voyage.hk/mailman/listinfo/voyage-linux
> > >>>     >
> > >>>     > --
> > >>>     > Juergen Adolph
> > >>>     >
> > >>>
> > >>>
> > >>
> >
> ----------------------------------------------------------------------------
> > >>
> > >>>     > PGP-KeyID: 0x4A77083A
> > >>>     >
> > >>>     > _______________________________________________
> > >>>     > Voyage-linux mailing list
> > >>>     > Voyage-linux at list.voyage.hk
> > >>>
> > >> <mailto:Voyage-linux at list.voyage.hk>
> > >>
> > >>>     > http://list.voyage.hk/mailman/listinfo/voyage-linux
> > >>>     >
> > >>>     >
> > >>>     > !DSPAM:4999ae25123311804284693!
> > >>>     >
> > >>>
> > >>>     Ward Vandewege.
> > >>>
> > >>>     --
> > >>>     Pong.be         -(           "HTML needs a rant tag" - Alan
> > Cox
> > >>>
> > >>>              )-
> > >>>     Virtual hosting -(
> >
> > >>>
> > >>
> > >>
> > >>>             )-
> > >>>     http://pong.be  -(
> >
> > >>>
> > >>
> > >>
> > >>>             )-
> > >>>     GnuPG public key: http://pgp.mit.edu
> > >>>
> > >>>     _______________________________________________
> > >>>     Voyage-linux mailing list
> > >>>     Voyage-linux at list.voyage.hk
> > >>>
> > >> <mailto:Voyage-linux at list.voyage.hk>
> > >>
> > >>>     http://list.voyage.hk/mailman/listinfo/voyage-linux
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > ------------------------------------------------------------------------
> > >>
> > >>> _______________________________________________
> > >>> Voyage-linux mailing list
> > >>> Voyage-linux at list.voyage.hk
> > >>> http://list.voyage.hk/mailman/listinfo/voyage-linux
> > >>>
> > >>>
> > >> _______________________________________________
> > >> Voyage-linux mailing list
> > >> Voyage-linux at list.voyage.hk
> > >> http://list.voyage.hk/mailman/listinfo/voyage-linux
> > >>
> > >
> > >
>
> --
> Juergen Adolph
>
> ----------------------------------------------------------------------------
> PGP-KeyID: 0x4A77083A
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20090221/7aed0393/attachment.html>

More information about the Voyage-linux mailing list