Return-path: Received: from blaine.gmane.org ([80.91.229.8]:35134 "EHLO hugh.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758638AbYLLOFI (ORCPT ); Fri, 12 Dec 2008 09:05:08 -0500 Received: from public by hugh.gmane.org with local (Exim 4.63) (envelope-from ) id 1LB8dd-0007DX-MQ for linux-wireless@vger.kernel.org; Fri, 12 Dec 2008 15:05:05 +0100 Message-ID: <49426F6B.3040109@redhat.com> (sfid-20081212_150515_763763_BF411CFE) Date: Fri, 12 Dec 2008 15:04:27 +0100 From: Zdenek Kabelac MIME-Version: 1.0 To: Dan Williams CC: "Alexander E. Patrakov" , reinette chatre , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" Subject: Re: iwlagn interrupt problem References: <1228929548.18730.21.camel@rc-desk> <49424419.1090103@redhat.com> <49424B7A.9060700@redhat.com> <1229086999.32038.6.camel@localhost.localdomain> In-Reply-To: <1229086999.32038.6.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: Dan Williams napsal(a): > On Fri, 2008-12-12 at 12:31 +0100, Zdenek Kabelac wrote: >> Alexander E. Patrakov napsal(a): >>> 2008/12/12 Zdenek Kabelac : >>>> I assume that this backtrace I've got with 2.6.28-rc7 is the same issue ? >>> No, this is different. My issue is with unacceptable latency when >>> bringing the interface down. In your dmesg, the interface was never >>> brought up or down. >>> >> Hmm - it was something like an hour after resume when the problem started, >> >> Here is timed part of the same backtrace: >> >> [65627.782972] wlan0: associate with AP 00:11:d8:da:65:40 >> [65627.785569] wlan0: RX ReassocResp from 00:11:d8:da:65:40 (capab=0x401 >> status=0 aid=8) >> [65627.785576] wlan0: associated >> [69541.209873] wlan0: No ProbeResp from current AP 00:11:d8:da:65:40 - assume >> out of range >> [69541.810104] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms. >> [69542.309861] iwl3945: Error sending REPLY_RXON_ASSOC: time out after 500ms. >> >> >> The begging of my trace looked similar. >> >> Should I open new bugzilla separately ? > > If you can reproduce this, it sounds more like a firmware problem, so > Reinette is probably going to want you to enable firmware debugging in > the driver. Try removing the iwl3945 module with rmmod, then "modprobe > iwl3945 debug=0x43fff", reproduce this command timeout, and attach the > logs to whatever bug report you file. > Unfortunately I do not have a reproducing case and it happened just once on Wednesday after resume. But when (if) it will repeat I'll try to reinsert module with debug - I think without this my bug is not resolvable right ? Zdenek