From: Ivan Bulatovic <combuster@gmx.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Satish Eerpini <eerpini@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl3945 bug in 2.6.34
Date: Mon, 31 May 2010 15:06:16 +0200 [thread overview]
Message-ID: <1275311176.3329.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1274830187.2091.17034.camel@rchatre-DESK>
On Tue, 2010-05-25 at 16:29 -0700, reinette chatre wrote:
> Hi Satish,
>
> On Mon, 2010-05-24 at 15:08 -0700, reinette chatre wrote:
> > On Mon, 2010-05-24 at 11:33 -0700, reinette chatre wrote:
> > > On Sat, 2010-05-22 at 23:25 -0700, Satish Eerpini wrote:
> > >
> > > > No probe response from AP 00:1b:da:2a:a1:53 after 500ms, disconnecting.
> > > > iwl3945 0000:10:00.0: Error sending REPLY_RXON: time out after 500ms.
> > > > iwl3945 0000:10:00.0: Error setting new configuration (-110).
> > > > iwl3945 0000:10:00.0: Error sending REPLY_RXON: time out after 500ms.
> > > > iwl3945 0000:10:00.0: Error setting new configuration (-110).
> > >
> > > This did not use to be an issue with 3945 and unfortunately we do not
> > > know what is triggering it now. Please try the "Enable stuck queue
> > > detection on 3945" patch that is attached to
> > > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1834 as a
> > > workaround.
> >
> > Actually, sorry, but that patch will not work on 2.6.34 since the
> > feature it enables is not present there - it will be in 2.6.35 though.
> > To enable the feature in 2.6.34 will take some more backporting effort
> > that I'm looking into now.
>
> Please try the attached two patches.
>
> Reinette
>
I didn't have a problem with 2.6.34 but with 2.6.35-rc1 while obtaing IP
address with dhcpcd it bails out with reason 3 and gets timed out. I've
tried to increase timeout to 100 but the result is the same. I can't
apply this patches because base is somewhat different, as I can see the
first patch is already applied but the second one isn't. Any
suggestions ? Thanks. In the meantime I will try to get some more debug
information.
next prev parent reply other threads:[~2010-05-31 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 6:25 iwl3945 bug in 2.6.34 Satish Eerpini
2010-05-24 18:03 ` John W. Linville
2010-05-24 18:33 ` reinette chatre
2010-05-24 22:08 ` reinette chatre
[not found] ` <AANLkTinFt5yiINXrc9-fnUl7NiyzN42eUotFnZdcxbas@mail.gmail.com>
2010-05-25 2:21 ` Satish Eerpini
2010-05-25 23:29 ` reinette chatre
2010-05-31 13:06 ` Ivan Bulatovic [this message]
2010-06-03 21:32 ` reinette chatre
2010-06-10 18:49 ` Satish Eerpini
2010-06-11 11:39 ` Satish Eerpini
2010-06-11 16:27 ` reinette chatre
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=1275311176.3329.3.camel@localhost.localdomain \
--to=combuster@gmx.com \
--cc=eerpini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).