Return-path: Received: from mga11.intel.com ([192.55.52.93]:11940 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756087AbZKWXYL convert rfc822-to-8bit (ORCPT ); Mon, 23 Nov 2009 18:24:11 -0500 From: "Cahill, Ben M" To: Maxim Levitsky , Johannes Berg CC: linux-wireless , iwlwifi maling list Date: Mon, 23 Nov 2009 15:24:13 -0800 Subject: RE: [ipw3945-devel] iwl3945 dies on module reload Message-ID: <02B3067C068D0549A8CCFCB17D4D318B4E6032E5@orsmsx502.amr.corp.intel.com> References: <1258968499.3271.5.camel@maxim-laptop> <1258972050.7094.140.camel@johannes.local> <1258973082.3675.0.camel@maxim-laptop> <1258973362.7094.151.camel@johannes.local> <1258996575.9727.2.camel@maxim-laptop> In-Reply-To: <1258996575.9727.2.camel@maxim-laptop> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: >-----Original Message----- >From: Maxim Levitsky [mailto:maximlevitsky@gmail.com] >Sent: Monday, November 23, 2009 12:16 PM >To: Johannes Berg >Cc: linux-wireless; iwlwifi maling list >Subject: [ipw3945-devel] iwl3945 dies on module reload > >When reloading the iwl3945 driver I often get this: > > >[ 830.333386] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG >Network Connection driver for Linux, 1.2.26kds >[ 830.333407] iwl3945: Copyright(c) 2003-2009 Intel Corporation >[ 830.333536] iwl3945 0000:06:00.0: PCI INT A -> GSI 19 >(level, low) -> IRQ 19 >[ 830.374979] iwl3945 0000:06:00.0: Tunable channels: 13 >802.11bg, 0 802.11a channels >[ 830.374995] iwl3945 0000:06:00.0: Detected Intel Wireless >WiFi Link 3945BG >[ 830.375163] iwl3945 0000:06:00.0: irq 32 for MSI/MSI-X >[ 830.376859] phy0: Selected rate control algorithm 'iwl-3945-rs' >[ 830.427214] iwl3945 0000:06:00.0: firmware: requesting >iwlwifi-3945-2.ucode >[ 830.526945] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9 >[ 830.544236] CE: hpet increasing min_delta_ns to 15000 nsec >[ 830.575694] iwl3945 0000:06:00.0: BSM uCode verification >failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 >[ 830.578862] iwl3945 0000:06:00.0: Hardware error detected. >Restarting. >[ 832.570133] iwl3945 0000:06:00.0: Wait for START_ALIVE >timeout after 2000ms. >[ 832.622676] iwl3945 0000:06:00.0: BSM uCode verification >failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 >[ 832.625839] iwl3945 0000:06:00.0: Hardware error detected. >Restarting. >[ 834.620132] iwl3945 0000:06:00.0: Wait for START_ALIVE >timeout after 2000ms. The 0xa5a5a5a2 signature indicates that the device is powered up and the PCI Express link is working, but somehow the device internals have not been powered up / initialized. Are you using a very recent version of the driver? I've done some work in this area in the past couple of months. -- Ben -- > > >Note that I used antenna=2 parameter to experiment with >quality of reception of both antennas >(this feature strangely works just fine....) > >I disabled this option, so next time I feel like rebooting my >system, I see if this option was the cause. >(unlikely) > > >Best regards, > Maxim Levitsky > > > > > > >--------------------------------------------------------------- >--------------- >Let Crystal Reports handle the reporting - Free Crystal >Reports 2008 30-Day >trial. Simplify your report design, integration and deployment >- and focus on >what you do best, core application coding. Discover what's new with >Crystal Reports now. http://p.sf.net/sfu/bobj-july >_______________________________________________ >Ipw3945-devel mailing list >Ipw3945-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/ipw3945-devel >