From: Andrej Gelenberg <andrej.gelenberg@udo.edu>
To: wwguy <wey-yi.w.guy@intel.com>
Cc: Udo Steinberg <udo@hypervisor.org>,
Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iwlagn regression in v3.1.5
Date: Sun, 11 Dec 2011 20:05:20 +0100 [thread overview]
Message-ID: <4EE4FEF0.1090107@udo.edu> (raw)
In-Reply-To: <1323627815.1806.19.camel@wwguy-ubuntu>
Hi,
i haven't experienced firmware crushes, but after that commit i don't
get any networking with my wlan card. I added some lspci and dmesg
output to the patch. There was no strange output in my dmesg. dhcpcd
says in logs, that carrier lost after about 30 seconds. How can i
reproduce the HT40 bug?
Regards,
Andrej
On 12/11/2011 07:23 PM, wwguy wrote:
> On Sun, 2011-12-11 at 08:58 -0800, Andrej Gelenberg wrote:
>> Hi,
>>
>> this is pretty mean regression for the stable kernel. You may the fix
>> only for cards, which need it and not for all of them.
>
> Could you elaborate more on the failure case and setup. this patch is to
> address HT40 related problem which cause the iwlwifi firmware crash.
>
> Thanks
> Wey
>>>
>
>
next prev parent reply other threads:[~2011-12-11 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 13:24 iwlagn regression in v3.1.5 Andrej Gelenberg
2011-12-11 16:33 ` Andrej Gelenberg
2011-12-11 16:41 ` Udo Steinberg
2011-12-11 16:58 ` Andrej Gelenberg
2011-12-11 18:23 ` wwguy
2011-12-11 19:05 ` Andrej Gelenberg [this message]
2011-12-11 19:20 ` Andrej Gelenberg
2011-12-12 1:35 ` wwguy
2011-12-12 17:15 ` Andrej Gelenberg
2011-12-13 20:15 ` wwguy
2011-12-13 21:08 ` Andrej Gelenberg
2011-12-13 22:04 ` Udo Steinberg
2011-12-13 23:20 ` wwguy
2011-12-15 22:12 ` Arkadiusz Miśkiewicz
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=4EE4FEF0.1090107@udo.edu \
--to=andrej.gelenberg@udo.edu \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=udo@hypervisor.org \
--cc=wey-yi.w.guy@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).