From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Microcode SW error detected on current wireless-testing
Date: Tue, 30 Nov 2010 14:01:49 +0100 [thread overview]
Message-ID: <20101130130148.GA3074@redhat.com> (raw)
Hi
Today pull on wireless testing caused this on my 4965 device (100%
reproducible on my system, yesterday w-t does not have this).
iwlagn 0000:40:00.0: Microcode SW error detected. Restarting 0x82000000.
iwlagn 0000:40:00.0: Loaded firmware version: 228.61.2.24
iwlagn 0000:40:00.0: Start IWL Error Log Dump:
iwlagn 0000:40:00.0: Status: 0x0002B3E4, count: 5
iwlagn 0000:40:00.0: Desc Time data1 data2 line
iwlagn 0000:40:00.0: SYSASSERT (0x0005) 0000851408 0x000000FF 0x00000000 578
iwlagn 0000:40:00.0: pc blink1 blink2 ilink1 ilink2 hcmd
iwlagn 0000:40:00.0: 0x13AC0 0x13A36 0x13AD6 0x006DE 0x00000 0x44140080
iwlagn 0000:40:00.0: FH register values:
iwlagn 0000:40:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X11a7cd00
iwlagn 0000:40:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0119e720
iwlagn 0000:40:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000060
iwlagn 0000:40:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819004
iwlagn 0000:40:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X0000003c
iwlagn 0000:40:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
iwlagn 0000:40:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
iwlagn 0000:40:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0002
iwlagn 0000:40:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
iwlagn 0000:40:00.0: Start IWL Event Log Dump: display last 20 entries
iwlagn 0000:40:00.0: EVT_LOGT:0000851099:0x781c3b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851103:0x7c233b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851105:0x7c1b3b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851109:0x80223b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851111:0x801b3b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851115:0x84213b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851117:0x841b3b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851121:0x88223b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851123:0x881a3b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851128:0x8c213b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851130:0x8c193b6e:0450
iwlagn 0000:40:00.0: EVT_LOGT:0000851132:0x0000007f:0601
iwlagn 0000:40:00.0: EVT_LOGT:0000851138:0x00000100:0706
iwlagn 0000:40:00.0: EVT_LOGT:0000851140:0x00000000:0708
iwlagn 0000:40:00.0: EVT_LOGT:0000851143:0x01000300:0706
iwlagn 0000:40:00.0: EVT_LOGT:0000851145:0x01000300:0725
iwlagn 0000:40:00.0: EVT_LOGT:0000851146:0x00000000:0710
iwlagn 0000:40:00.0: EVT_LOGT:0000851148:0x00000024:0729
iwlagn 0000:40:00.0: EVT_LOGT:0000851149:0x000cfccc:0729
iwlagn 0000:40:00.0: EVT_LOGT:0000851411:0x00000000:0125
iwlagn 0000:40:00.0: Command REPLY_SCAN_CMD failed: FW Error
Is Intel aware of that problem? Should I bisect it?
Stanislaw
next reply other threads:[~2010-11-30 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 13:01 Stanislaw Gruszka [this message]
2010-11-30 13:16 ` Microcode SW error detected on current wireless-testing Johannes Berg
2010-11-30 13:49 ` Stanislaw Gruszka
2010-11-30 14:09 ` Johannes Berg
2010-11-30 14:33 ` [PATCH w-t] iwlagn: fix microcode error on 4965 Stanislaw Gruszka
2010-11-30 14:36 ` Johannes Berg
2010-11-30 15:38 ` 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=20101130130148.GA3074@redhat.com \
--to=sgruszka@redhat.com \
--cc=ilw@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.