linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Malthe Borch <mborch@gmail.com>
To: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Sternberg, Jay E" <jay.e.sternberg@intel.com>
Subject: Re: Intel Wireless: Microcode SW error detected.
Date: Sun, 1 Aug 2010 19:56:28 -0400	[thread overview]
Message-ID: <AANLkTi=urmiEPXN+Bpk-6_KwcqSgFuqKc1LK0njNd5E_@mail.gmail.com> (raw)
In-Reply-To: <E9954878DD1FB34FAE5187FB88C58A350122DF3C44@orsmsx506.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

Attached is the additional logging output I get when I load the drivers using:

  modprobe iwlagn debug=0x43fff

\malthe

On 27 July 2010 10:40, Guy, Wey-Yi W <wey-yi.w.guy@intel.com> wrote:
> Add Jay to the thread,
>
> Jay, could you help to take a look at it. Thanks
>
> Wey-Yi Guy
> Intel Corporation
> 2111 N.E. 25th Avenue  M/S JF3-308
> Hillsboro OR 97124-5961
> USA
> Work Phone: 503-264-6023 (OR)
> Cell Phone: 503-329-8410
> Email: wey-yi.w.guy@intel.com
>
>
> -----Original Message-----
> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Malthe Borch
> Sent: Monday, July 26, 2010 2:19 PM
> To: linux-wireless@vger.kernel.org
> Subject: Intel Wireless: Microcode SW error detected.
>
> I get this with the latest and greatest Intel firmware 9.221.4.1 build 25532.
>
> Ultimately enabling the device fails with: "uCode did not respond OK."
>

[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 1794 bytes --]

ieee80211 phy0: I iwl_print_rx_config_cmd RX CONFIG:
iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
iwl data: 00000010: 00 00 00 00 00 00 00 00 00 00 0e 24 00 00 00 00  ...........$....
iwl data: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
iwl data: 00000030: 00 00                                            ..
ieee80211 phy0: I iwl_print_rx_config_cmd u16 channel: 0x0
ieee80211 phy0: I iwl_print_rx_config_cmd u32 flags: 0x00000000
ieee80211 phy0: I iwl_print_rx_config_cmd u32 filter_flags: 0x00000000
ieee80211 phy0: I iwl_print_rx_config_cmd u8 dev_type: 0x0
ieee80211 phy0: I iwl_print_rx_config_cmd u8 ofdm_basic_rates: 0x00
ieee80211 phy0: I iwl_print_rx_config_cmd u8 cck_basic_rates: 0x00
ieee80211 phy0: I iwl_print_rx_config_cmd u8[6] node_addr: 00:00:00:00:00:00
ieee80211 phy0: I iwl_print_rx_config_cmd u8[6] bssid_addr: 00:00:00:00:00:00
ieee80211 phy0: I iwl_print_rx_config_cmd u16 assoc_id: 0x0
ieee80211 phy0: I iwl_irq_handle_error Restarting adapter due to uCode error.
ieee80211 phy0: I iwl_rx_reply_alive Alive ucode status 0x00000000 revision 0x1 0x0
ieee80211 phy0: I iwl_rx_reply_alive Runtime Alive received.
iwlagn 0000:02:00.0: uCode did not respond OK.
ieee80211 phy0: U __iwl_down iwlagn is going down
ieee80211 phy0: U iwl_clear_ucode_stations Clearing ucode stations in driver
ieee80211 phy0: U iwl_clear_ucode_stations No active stations found to be cleared
ieee80211 phy0: U iwl_apm_stop Stop card, put in low power state
ieee80211 phy0: U iwl_apm_stop_master stop master
ieee80211 phy0: U iwl_clear_free_frames 0 frames on pre-allocated heap on clear.
iwlagn 0000:02:00.0: START_ALIVE timeout after 4000ms.
ieee80211 phy0: U iwl_configure_filter Enter: changed: 0x0, total: 0x80000000

  reply	other threads:[~2010-08-01 23:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:19 Intel Wireless: Microcode SW error detected Malthe Borch
2010-07-27 14:40 ` Guy, Wey-Yi W
2010-08-01 23:56   ` Malthe Borch [this message]
2010-08-26 11:46     ` Saurav Barik
2010-08-26 15:48       ` Guy, Wey-Yi

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='AANLkTi=urmiEPXN+Bpk-6_KwcqSgFuqKc1LK0njNd5E_@mail.gmail.com' \
    --to=mborch@gmail.com \
    --cc=jay.e.sternberg@intel.com \
    --cc=linux-wireless@vger.kernel.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).