From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: "reinette chatre" <reinette.chatre@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn interrupt problem
Date: Thu, 11 Dec 2008 18:48:52 +0500 [thread overview]
Message-ID: <c072ca310812110548s64612ac7icd6e9187aa4af75a@mail.gmail.com> (raw)
In-Reply-To: <1228929548.18730.21.camel@rc-desk>
2008/12/10 reinette chatre <reinette.chatre@intel.com>:
> The messages you refer to are printed because a user space app
> (wpa_supplicant or network manager) brings the wireless interface down
> and up. Interrupts are disabled when interface is brought down and
> reenabled when interface is brought up.
OK.
> The unresponsiveness is due to a bug that was fixed recently. The
> patches have been merged into wireless-testing repo and will be included
> in 2.6.29. If you want to try
> the individual patches, please try:
> http://marc.info/?l=linux-wireless&m=122824886623698&w=2
> http://marc.info/?l=linux-wireless&m=122849275528102&w=2
These individual patches don't apply to 2.6.27.6, so I installed
today's compat-wireless-2.6, and it seems to work. Thanks!
OTOH, are these patches a material for backporting into -stable?
--
Alexander E. Patrakov
next prev parent reply other threads:[~2008-12-11 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c072ca310812100638k6c15473brb89632a9c175a028@mail.gmail.com>
2008-12-10 15:10 ` Alexander E. Patrakov
2008-12-10 17:19 ` reinette chatre
2008-12-11 13:48 ` Alexander E. Patrakov [this message]
2008-12-11 17:14 ` reinette chatre
2008-12-12 10:59 ` Zdenek Kabelac
[not found] ` <c072ca310812120323r2c92420di5a138ae6265d567f@mail.gmail.com>
2008-12-12 11:31 ` Zdenek Kabelac
2008-12-12 11:39 ` Alexander E. Patrakov
2008-12-12 13:03 ` Dan Williams
2008-12-12 14:04 ` Zdenek Kabelac
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=c072ca310812110548s64612ac7icd6e9187aa4af75a@mail.gmail.com \
--to=patrakov@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
all inboxes | Powered by JetHome®