[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANUX_P3XSCsWUJ9M55qeaK-DuPEMXODFPJiNk+BgnHN-=WECqw@mail.gmail.com>
Date: Thu, 26 Jan 2012 13:13:05 -0800
From: Emmanuel Grumbach <egrumbach@...il.com>
To: Norbert Preining <preining@...ic.at>
Cc: linux-kernel@...r.kernel.org, ipw3945-devel@...ts.sourceforge.net,
"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>,
Johannes Berg <johannes@...solutions.net>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
Dave Jones <davej@...hat.com>
Subject: Re: iwlagn is getting even worse with 3.3-rc1
Hey Dave,
Can you please try to patch attached to this thread. You and Norbert
are suffering from the same issue. I am merging the mail threads here.
On Wed, Jan 25, 2012 at 21:49, Emmanuel Grumbach <egrumbach@...il.com> wrote:
> Hi Norbert,
>
>>
>> syslog output is at http://www.logic.at/people/preining/syslog.log
>> this is after a suspend and resume.
>>
>> first connection after resume succeeded at around kernel time 378.859794
>> then it worked for say 20sec or so, hard to say when exactely it dropped,
>> but defeinitely at kernel time 451 it was finished.
>>
>> After that nothing went out or in again.
>>
>> Hope you can make something out of that.
>>
>
> Unfortunately, not really. I can see you are hitting PASSIVE_NO_RX,
> meaning that the uCode complains that you are trying to Tx on a
> passive channel on which it hasn't heard any beacon yet. But then we
> finally get a beacon there, and open the queue again.
>
> Anyway, can you try the attached patch ?
> Note that I have no real way to test it (I have to admit I haven't
> even compiled... I am not in my office).
> I hope it might help.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists