linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: prahal@yahoo.com
Cc: John Linville <linville@tuxdriver.com>,
	rt2x00 Users List <users@rt2x00.serialmonkey.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Ivo van Doorn <ivdoorn@gmail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: [PATCH 1/2] rt2x00 : hw support txdone implementation. (without fallback change)
Date: Thu, 25 Feb 2010 15:21:58 -0500	[thread overview]
Message-ID: <1267129318.16176.15.camel@mj> (raw)
In-Reply-To: <4B86D0BD.3000803@yahoo.com>

On Thu, 2010-02-25 at 20:34 +0100, Alban Browaeys wrote:

> > wpa_supplicant worked most of the time.  I believe the occasional
> > failures are due to a preexisting memory corruption issue (I reported
> > earlier that addr3 can be corrupted in probe requests).

That's what I'm referring to:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/46727

> Really interesting. I had access to an Access Point that leading to
> such state of affait a week ago (but not for long enough to decipher the 
> issue).
> All I could tell is the rt2x00mac_config was constantly called and as 
> this function kills
> RX well I ended up with RX off all the time after a few initial pings.
> Does any message comes out with mac80211 and rt2x00 debug on ?
> As I cannot reproduce with both of my 3 different access points I am 
> kind of interested
> by such a setup that break.

There are no kernel messages, but ping stops working after 11 packets
every time.  Wireshark shows that no more pings are sent.

> Does 
> http://git.popipo.fr/?p=rt2x00.git;a=commitdiff;h=f82ab894fdac70954a50507921947facce8d8321 
> helps ?

It's already in the kernel.

This patch should help, but it was criticized and we are waiting for a
better version:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/46713

> >> +		rt2x00_desc_read(txwi, 1,&word);
> >> +		tx_wcid = rt2x00_get_field32(word, TXWI_W1_WIRELESS_CLI_ID);
> >> +		tx_ack  = rt2x00_get_field32(word, TXWI_W1_ACK);
> >> +		tx_pid  = rt2x00_get_field32(word, TXWI_W1_PACKETID);
> >> +
> >> +		if ((wcid != tx_wcid) || (ack != tx_ack) || (pid != tx_pid))
> >> +			WARNING(rt2x00dev, "invalid TX_STA_FIFO content\n");
> >>      
> > Can we make this sanity check optional?
> >
> >    
> Is this a showstopper ? Do you mean only enabling this message telling 
> something totally
> unexpected happened in debug mode ? The sanity of the queue is pretty 
> critical for operation.

I'm not a maintainer, I'm just trying to help with the driver, so I
cannot declare anything a showstopper.  It was just an idea.  We can
make it optional later.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-02-25 20:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  4:19 [PATCH 1/2] rt2x00 : hw support txdone implementation. (without fallback change) Alban Browaeys
2010-02-25 17:22 ` Gertjan van Wingerde
2010-02-25 18:54   ` Alban Browaeys
2010-02-25 17:48 ` Pavel Roskin
2010-02-25 19:34   ` Alban Browaeys
2010-02-25 20:21     ` Pavel Roskin [this message]
2010-02-25 23:56       ` Alban Browaeys
2010-02-25 20:46     ` Ivo van Doorn
2010-02-25 20:53       ` Josef Bacik
2010-02-26  1:21         ` Alban Browaeys
2010-02-25 23:37       ` Alban Browaeys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1267129318.16176.15.camel@mj \
    --to=proski@gnu.org \
    --cc=gwingerde@gmail.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=prahal@yahoo.com \
    --cc=users@rt2x00.serialmonkey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).