From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Cahill, Ben M" <ben.m.cahill@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: RE: [ipw3945-devel] iwl3945 dies on module reload
Date: Tue, 24 Nov 2009 01:54:28 +0200 [thread overview]
Message-ID: <1259020468.16650.0.camel@maxim-laptop> (raw)
In-Reply-To: <02B3067C068D0549A8CCFCB17D4D318B4E6032E5@orsmsx502.amr.corp.intel.com>
On Mon, 2009-11-23 at 15:24 -0800, Cahill, Ben M wrote:
>
> >-----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.
I use -git tip of wireless-testing
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2009-11-23 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 9:28 RFKILL related oops on iwl3945 reload Maxim Levitsky
2009-11-23 10:27 ` [PATCH 2.6.32] rfkill: fix miscdev ops Johannes Berg
2009-11-23 10:44 ` Maxim Levitsky
2009-11-23 10:49 ` Johannes Berg
2009-11-23 14:12 ` Maxim Levitsky
2009-11-23 16:00 ` Johannes Berg
2009-11-23 17:16 ` iwl3945 dies on module reload Maxim Levitsky
2009-11-23 23:24 ` [ipw3945-devel] " Cahill, Ben M
2009-11-23 23:54 ` Maxim Levitsky [this message]
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=1259020468.16650.0.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ben.m.cahill@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).