From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: IWL3945 problems in 2.6.35-rc1
Date: Fri, 18 Jun 2010 13:40:57 +0300 [thread overview]
Message-ID: <1276857657.19036.0.camel@maxim-laptop> (raw)
In-Reply-To: <1276857009.3638.20.camel@jlt3.sipsolutions.net>
On Fri, 2010-06-18 at 12:30 +0200, Johannes Berg wrote:
> Maxim,
>
> Thanks for the quick reply!
>
> > > 1) with the patch reverted, which is what presumably you're running
> > > now, can you try
> > > ifconfig wlan0 allmulti
> > > ifconfig wlan0 -allmulti
> > >
> > > I think this will *break* the driver right now.
> >
> > I didn't exactly understand how this supposed to break it.
>
> Ok this needs some more explaining.
>
> The old code did:
>
> if (allmulti changed)
> "set grp-filter in hw according to allmulti"
>
> the new code just did
>
> "set grp-filter in hw according to allmulti"
>
>
> During normal operation the "allmulti changed" condition is never true.
> Therefore, the old code, despite being incorrect, never broke things.
> The above would make the condition true, and lead to it being broken
> because it would change to on/off and then the grp-filter in hw would be
> off, although it's required to be on.
>
> Thus the real bug was there before my change, but it never triggered,
> and when I "optimised away" the condition I broke it.
Got it.
>
> > > 2) with the patch *not* reverted, apply the patch below and see if that
> > > fixes the problem as well (if it gets mangled, just remove the one
> > > CHK() line manually)
> > >
> > > Actually, (2) is obviously more important to me, but (1) would indicate
> > > that my guess is correct wrt. what's causing the problem
>
> > I tested (2) and it works.
>
> Thank you. I'll submit this patch instead.
>
> johannes
>
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2010-06-18 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 12:25 IWL3945 problems in 2.6.35-rc1 Maxim Levitsky
2010-06-01 14:57 ` Maxim Levitsky
2010-06-01 15:21 ` Sedat Dilek
2010-06-01 18:12 ` Maxim Levitsky
2010-06-02 16:53 ` Maxim Levitsky
2010-06-02 18:01 ` Sedat Dilek
2010-06-01 19:03 ` Abhijeet Kolekar
2010-06-01 19:59 ` Maxim Levitsky
2010-06-02 8:35 ` Sedat Dilek
2010-06-03 6:00 ` reinette chatre
2010-06-03 9:18 ` Sedat Dilek
2010-06-03 15:55 ` reinette chatre
2010-06-18 9:28 ` Johannes Berg
2010-06-18 10:19 ` Maxim Levitsky
2010-06-18 10:30 ` Johannes Berg
2010-06-18 10:40 ` Maxim Levitsky [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=1276857657.19036.0.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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).