From: Zhu Yi <yi.zhu@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: Microcode SW error detected. Restarting 0x2000000
Date: Tue, 06 Jan 2009 09:13:40 +0800 [thread overview]
Message-ID: <1231204420.11581.24.camel@debian> (raw)
In-Reply-To: <1231197048.4858.9.camel@californication>
On Tue, 2009-01-06 at 07:10 +0800, Marcel Holtmann wrote:
> iwlagn 0000:03:00.0: PCI INT A disabled
> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k
> iwlagn: Copyright(c) 2003-2008 Intel Corporation
> vendor=8086 device=2841
> iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlagn 0000:03:00.0: setting latency timer to 64
> iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
> iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
> wmaster0 (iwlagn): not using net_device_ops yet
> phy1: Selected rate control algorithm 'iwl-agn-rs'
> wlan0 (iwlagn): not using net_device_ops yet
> vendor=8086 device=2841
> iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode
> iwlagn loaded firmware version 228.57.2.23
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> iwlagn: Microcode SW error detected. Restarting 0x2000000.
>
> It renders the wireless device useless and module unload/reload
> doesn't
> help either. Is this the AMT issue again or something totally
> different with the latest ucode?
Not sure. Marcel, please load iwlagn with debug=0x43fff. We can then
track the uCode failure.
Thanks,
-yi
next prev parent reply other threads:[~2009-01-06 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 23:10 iwlagn: Microcode SW error detected. Restarting 0x2000000 Marcel Holtmann
2009-01-06 1:13 ` Zhu Yi [this message]
2009-01-06 2:18 ` Marcel Holtmann
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=1231204420.11581.24.camel@debian \
--to=yi.zhu@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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).