Search Linux Wireless

RE: [ipw3945-devel] iwl3945 dies on module reload

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2009-11-23 at 15:24 -0800, Cahill, Ben M wrote: 
> 
> >-----Original Message-----
> >From: Maxim Levitsky [mailto:maximlevitsky@xxxxxxxxx] 
> >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

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux