ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] kernel panic with ath9k
Date: Wed, 15 Feb 2012 13:06:09 -0500	[thread overview]
Message-ID: <20120215130609.476e4e0e@mj> (raw)
In-Reply-To: <CAD2nsn2XR22E5r-Xs4BE3LxBxCNbbO7hz21F2nvOHVuDrVAZnQ@mail.gmail.com>

On Wed, 15 Feb 2012 21:18:36 +0530
Mohammed Shafi <shafi.wireless@gmail.com> wrote:

> if we refer rate_control_get_rate in rate.c of mac80211
> 
> for (i = 0; i < IEEE80211_TX_MAX_RATES; i++) {
> 		info->control.rates[i].idx = -1;
> 		info->control.rates[i].flags = 0;
> 		info->control.rates[i].count = 1;
> 	}

Thanks for finding this code!  That's another sign that my patch is not
hiding an underlying problem, such as memory corruption.

> why count = 1 not 0 ? if count has to be 0 then we should fix in
> mac80211 also. though the doc in mac80211 says idx -1 means invalid
> rate, did not say if count =0 invalid
> but anyway the rate is tried once ?
> 
> *now  the drivers assumption of count=0 for invalid is not correct i
> think ministrel checks for both index and count in
> 'minstrel_ht_txstat_valid' while ath9k does not before your patch

We should remove the checks for count=0 eventually.  But it's not a
change for stable kernels.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2012-02-15 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04  8:26 [ath9k-devel] kernel panic with ath9k Olivier Keshavjee
2012-02-04 15:48 ` Pavel Roskin
2012-02-07 22:00   ` Pavel Roskin
2012-02-08 19:10     ` Adrian Chadd
2012-02-08 19:27       ` Felix Fietkau
2012-02-08 22:54         ` Pavel Roskin
2012-02-10  6:05           ` Mohammed Shafi
2012-02-11  4:06             ` Pavel Roskin
2012-02-13  7:36               ` Mohammed Shafi
2012-02-15 14:23                 ` Pavel Roskin
2012-02-15 15:48                   ` Mohammed Shafi
2012-02-15 18:06                     ` Pavel Roskin [this message]

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=20120215130609.476e4e0e@mj \
    --to=proski@gnu.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /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).