[iwl4965] Microcode SW error detected

[iwl4965] Microcode SW error detected

[Paul Bolle]

0) Since I started running (release candidates of) kernel v2.6.39 errors
like these show up in my log, every now and then:

iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x82000000.
iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
iwl4965 0000:03:00.0: Start IWL Error Log Dump:
iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
iwl4965 0000:03:00.0: Desc                                  Time       data1      data2      line
iwl4965 0000:03:00.0: FH_ERROR                     (0x000C) 1821446380 0x00000008 0x03130000 208 
iwl4965 0000:03:00.0: pc      blink1  blink2  ilink1  ilink2  hcmd
iwl4965 0000:03:00.0: 0x0046C 0x04A46 0x004C2 0x006DA 0x04A46 0x4C700A8
iwl4965 0000:03:00.0: FH register values:
iwl4965 0000:03:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X132a9b00
iwl4965 0000:03:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X01329ed0
iwl4965 0000:03:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X000000d8
iwl4965 0000:03:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819000
iwl4965 0000:03:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X0000003c
iwl4965 0000:03:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X03130000
iwl4965 0000:03:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
iwl4965 0000:03:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0002
iwl4965 0000:03:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
iwl4965 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
iwl4965 0000:03:00.0: EVT_LOGT:1821445332:0x00000000:1352
iwl4965 0000:03:00.0: EVT_LOGT:1821445332:0x00000001:1353
iwl4965 0000:03:00.0: EVT_LOGT:1821445336:0x0000000c:0357
iwl4965 0000:03:00.0: EVT_LOGT:1821445533:0x00000107:0106
iwl4965 0000:03:00.0: EVT_LOGT:1821445534:0x00000000:0302
iwl4965 0000:03:00.0: EVT_LOGT:1821445574:0x000000d4:0321
iwl4965 0000:03:00.0: EVT_LOGT:1821445575:0x00000000:1350
iwl4965 0000:03:00.0: EVT_LOGT:1821445576:0x00000000:1351
iwl4965 0000:03:00.0: EVT_LOGT:1821445576:0x00000000:1352
iwl4965 0000:03:00.0: EVT_LOGT:1821445577:0x00000001:1353
iwl4965 0000:03:00.0: EVT_LOGT:1821445581:0x0000000d:0357
iwl4965 0000:03:00.0: EVT_LOGT:1821446327:0x00000107:0106
iwl4965 0000:03:00.0: EVT_LOGT:1821446328:0x00000000:0302
iwl4965 0000:03:00.0: EVT_LOGT:1821446368:0x000000d4:0321
iwl4965 0000:03:00.0: EVT_LOGT:1821446369:0x00000000:1350
iwl4965 0000:03:00.0: EVT_LOGT:1821446370:0x00000000:1351
iwl4965 0000:03:00.0: EVT_LOGT:1821446370:0x00000000:1352
iwl4965 0000:03:00.0: EVT_LOGT:1821446371:0x00000001:1353
iwl4965 0000:03:00.0: EVT_LOGT:1821446375:0x0000000e:0357
iwl4965 0000:03:00.0: EVT_LOGT:1821446383:0x00000000:0125
ieee80211 phy0: Hardware restart was requested

1) Is there anything I'm supposed to do to (help) make these errors go
away?


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Mon, May 23, 2011 at 01:45:06PM +0200, Paul Bolle wrote:
> 0) Since I started running (release candidates of) kernel v2.6.39 errors
> like these show up in my log, every now and then:
>
> iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x82000000.
[snip]
> 1) Is there anything I'm supposed to do to (help) make these errors go
> away?

Does it also happen on 2.6.39-rc1 ? What is your configuration (mode,
encryption, do you use wpa_supplicant or NetworkManager, which version,
etc ...)? I will try to reproduce locally. If I'll be not able to reproduce,
I'll ask you for debug logs on broken, and working (i.e. 2.6.38) version
for compare. 

Thanks
Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> Does it also happen on 2.6.39-rc1 ?

My logs do not go back anymore to the (short) period I was actually
running 2.6.39-rc1. Is this important enough for you that I should
reinstall 2.6.39-rc1 and try to see whether I can reproduce this error
with that release candidate?


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Tue, May 24, 2011 at 05:54:05PM +0200, Paul Bolle wrote:
> On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> > Does it also happen on 2.6.39-rc1 ?
> 
> My logs do not go back anymore to the (short) period I was actually
> running 2.6.39-rc1. Is this important enough for you that I should
> reinstall 2.6.39-rc1 and try to see whether I can reproduce this error
> with that release candidate?

It's not so important at that point, it could be if we would not find
remedy other way. Currently I would more like to know how to reproduce
the problem.

Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> What is your configuration (mode,
> encryption, do you use wpa_supplicant or NetworkManager, which version,
> etc ...)?

0) Mode as is displayed in iwconfig output? That is "Managed".

1) Encryption is wep (so, no wpa_supplicant).

2) Currently using NetworkManager-0.8.4-1.fc14.x86_64.

> I will try to reproduce locally. If I'll be not able to reproduce,
> I'll ask you for debug logs on broken, and working (i.e. 2.6.38) version
> for compare.

3) Sure, no problem. But isn't 2.6.38 from before the iwlegacy split?


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Tue, May 24, 2011 at 06:50:53PM +0200, Paul Bolle wrote:
> On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> > What is your configuration (mode,
> > encryption, do you use wpa_supplicant or NetworkManager, which version,
> > etc ...)?
> 
> 0) Mode as is displayed in iwconfig output? That is "Managed".
> 
> 1) Encryption is wep (so, no wpa_supplicant).
> 
> 2) Currently using NetworkManager-0.8.4-1.fc14.x86_64.

I try to use WEP with one AP, no microcode errors. However with different
NetworkManager version, not sure if it is important. I'll try lately on F-14. 
What channel do you use? Is network 11n or 11g or mixed ? WEP is 40 bits or
other?

> > I will try to reproduce locally. If I'll be not able to reproduce,
> > I'll ask you for debug logs on broken, and working (i.e. 2.6.38) version
> > for compare.
> 
> 3) Sure, no problem. But isn't 2.6.38 from before the iwlegacy split?
Yes, it is. If the problem was introduced during driver split (that
happen in 2.6.39), one way to find a fix would be compare driver
behaviour before the split and after.

Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Wed, 2011-05-25 at 15:11 +0200, Stanislaw Gruszka wrote:

> What channel do you use?
11, 2.462 GHz (according to my basestation)

> Is network 11n or 11g or mixed ?
Network is mixed 11b and 11g (according to my basestation)

> WEP is 40 bits or other?
128 bits, 26 hex digits (again, according to my basestation)


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Wed, May 25, 2011 at 03:31:53PM +0200, Paul Bolle wrote:
> On Wed, 2011-05-25 at 15:11 +0200, Stanislaw Gruszka wrote:
> 
> > What channel do you use?
> 11, 2.462 GHz (according to my basestation)
> 
> > Is network 11n or 11g or mixed ?
> Network is mixed 11b and 11g (according to my basestation)
> 
> > WEP is 40 bits or other?
> 128 bits, 26 hex digits (again, according to my basestation)

My all attempts of reproduce the problem was unsuccessful. Please
send me (off list since this could be quite big) dmesg output from 
loading module to first microcode error, when using verbose debug eg:

$ modprobe -r iwl4965
$ modprobe iwl4965 debug=0x47ffffff  

Note: driver have to be compiled with CONFIG_IWLWIFI_LEGACY_DEBUG.
Also dmesg circular buffer can be too small to contain all requested
messages. In such case, you will have to configure syslog like described
here:
https://bugzilla.kernel.org/show_bug.cgi?id=35932#c2

Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Tue, 2011-05-31 at 15:37 +0200, Stanislaw Gruszka wrote:
> My all attempts of reproduce the problem was unsuccessful. Please
> send me (off list since this could be quite big) dmesg output from 
> loading module to first microcode error, when using verbose debug eg:
> 
> $ modprobe -r iwl4965
> $ modprobe iwl4965 debug=0x47ffffff  
> 
> Note: driver have to be compiled with CONFIG_IWLWIFI_LEGACY_DEBUG.
> Also dmesg circular buffer can be too small to contain all requested
> messages. In such case, you will have to configure syslog like described
> here:
> https://bugzilla.kernel.org/show_bug.cgi?id=35932#c2

0) I have not yet done that, but I do hope to do it shortly.

1) This Microcode SW error pops up only every now and then, so I'm
afraid I might find myself logging debug messages for quite some time.
What is the average volume of those messages? If it's no more than, say,
10 MB/min I can still run in verbose debug mode for hours on end without
worrying about running out of disk space.  


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Mon, Jun 06, 2011 at 10:58:42AM +0200, Paul Bolle wrote:
> On Tue, 2011-05-31 at 15:37 +0200, Stanislaw Gruszka wrote:
> > My all attempts of reproduce the problem was unsuccessful. Please
> > send me (off list since this could be quite big) dmesg output from 
> > loading module to first microcode error, when using verbose debug eg:
> > 
> > $ modprobe -r iwl4965
> > $ modprobe iwl4965 debug=0x47ffffff  
> > 
> > Note: driver have to be compiled with CONFIG_IWLWIFI_LEGACY_DEBUG.
> > Also dmesg circular buffer can be too small to contain all requested
> > messages. In such case, you will have to configure syslog like described
> > here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=35932#c2
> 
> 0) I have not yet done that, but I do hope to do it shortly.
> 
> 1) This Microcode SW error pops up only every now and then, so I'm
> afraid I might find myself logging debug messages for quite some time.

Hmm, perhaps there is some way to reproduce a error?

> What is the average volume of those messages? If it's no more than, say,
> 10 MB/min I can still run in verbose debug mode for hours on end without
> worrying about running out of disk space.  

I don't know how fast verbose logging will eat disk space, perhaps
you can check that? :-) Maybe logger could be configured to do not
log date, hostname and component, that would decrease size of logs
vastly. If not, less verbose logging could be used, let say
debug=0x00375fff, that will miss some information, but maybe would be
enough to figure out where the bug is.

Thanks
Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Mon, 2011-06-06 at 13:36 +0200, Stanislaw Gruszka wrote:
> Hmm, perhaps there is some way to reproduce a error?

My current logs show no obvious - to me - pattern for this error, so I'm
afraid we must scan the debug output for some hints for
reproducibility ...


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Dan Williams]

On Wed, 2011-05-25 at 15:11 +0200, Stanislaw Gruszka wrote:
> On Tue, May 24, 2011 at 06:50:53PM +0200, Paul Bolle wrote:
> > On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> > > What is your configuration (mode,
> > > encryption, do you use wpa_supplicant or NetworkManager, which version,
> > > etc ...)?
> > 
> > 0) Mode as is displayed in iwconfig output? That is "Managed".
> > 
> > 1) Encryption is wep (so, no wpa_supplicant).
> > 
> > 2) Currently using NetworkManager-0.8.4-1.fc14.x86_64.
> 
> I try to use WEP with one AP, no microcode errors. However with different
> NetworkManager version, not sure if it is important. I'll try lately on F-14. 
> What channel do you use? Is network 11n or 11g or mixed ? WEP is 40 bits or
> other?

If it makes a difference, NM 0.8.x uses only the 'wext' supplicant
driver and uses wpa_supplicant 0.6.x.  NM still requests periodic scans
about every 2 minutes as usual.

(F15+, ie NM 0.9, uses "nl80211,wext" and supplicant 0.7.3+git)

Dan

> > > I will try to reproduce locally. If I'll be not able to reproduce,
> > > I'll ask you for debug logs on broken, and working (i.e. 2.6.38) version
> > > for compare.
> > 
> > 3) Sure, no problem. But isn't 2.6.38 from before the iwlegacy split?
> Yes, it is. If the problem was introduced during driver split (that
> happen in 2.6.39), one way to find a fix would be compare driver
> behaviour before the split and after.
> 
> Stanislaw
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [iwl4965] Microcode SW error detected

[Bernhard Schmidt]

On Monday, May 23, 2011 13:45:06 Paul Bolle wrote:
> 0) Since I started running (release candidates of) kernel v2.6.39 errors
> like these show up in my log, every now and then:
> 
> iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x82000000.
> iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
> iwl4965 0000:03:00.0: Start IWL Error Log Dump:
> iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
> iwl4965 0000:03:00.0: Desc                                  Time       data1      data2      line
> iwl4965 0000:03:00.0: FH_ERROR                     (0x000C) 1821446380 0x00000008 0x03130000 208 

On a unrelated site note, I have a case where I can trigger a
FH_ERROR at this line 100% reliably. Not on Linux though..
While being associated to a 5GHz BSS doing a scan chan by chan
(instead of all at once) is enough to trigger it. A workaround
is too not send probe requests for 2GHz channels at 1Mbps (CCK
flag) but at 6Mbps instead.

Maybe this bug report [1] is related too?

[1] http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1965

-- 
Bernhard

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Tue, Jun 07, 2011 at 08:32:48AM +0200, Bernhard Schmidt wrote:
> On Monday, May 23, 2011 13:45:06 Paul Bolle wrote:
> > 0) Since I started running (release candidates of) kernel v2.6.39 errors
> > like these show up in my log, every now and then:
> > 
> > iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x82000000.
> > iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
> > iwl4965 0000:03:00.0: Start IWL Error Log Dump:
> > iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
> > iwl4965 0000:03:00.0: Desc                                  Time       data1      data2      line
> > iwl4965 0000:03:00.0: FH_ERROR                     (0x000C) 1821446380 0x00000008 0x03130000 208 
> 
> On a unrelated site note, I have a case where I can trigger a
> FH_ERROR at this line 100% reliably. Not on Linux though..
> While being associated to a 5GHz BSS doing a scan chan by chan
> (instead of all at once) is enough to trigger it.
That could be useful hint, we do not scan chan by chan, but we
have thing called "plcp check health", which "restart radio"
by requesting one channel scan. So perhaps disabling that could
help.

> A workaround
> is too not send probe requests for 2GHz channels at 1Mbps (CCK
> flag) but at 6Mbps instead.
> 
> Maybe this bug report [1] is related too?
> 
> [1] http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1965

Hard to tell.

Thanks
Stanislaw

diff --git a/drivers/net/wireless/iwlegacy/iwl-rx.c b/drivers/net/wireless/iwlegacy/iwl-rx.c
index 654cf23..6062da0 100644
--- a/drivers/net/wireless/iwlegacy/iwl-rx.c
+++ b/drivers/net/wireless/iwlegacy/iwl-rx.c
@@ -230,6 +230,8 @@ EXPORT_SYMBOL(iwl_legacy_rx_spectrum_measure_notif);
 void iwl_legacy_recover_from_statistics(struct iwl_priv *priv,
 				struct iwl_rx_packet *pkt)
 {
+	return;
+
 	if (test_bit(STATUS_EXIT_PENDING, &priv->status))
 		return;
 	if (iwl_legacy_is_any_associated(priv)) {

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:
> That could be useful hint, we do not scan chan by chan, but we
> have thing called "plcp check health", which "restart radio"
> by requesting one channel scan. So perhaps disabling that could
> help.

At this moment I'm interested in something (a script, some sequence of
actions, whatever) that (somewhat) reliably triggers this error. Because
right now I have no clue what triggers it.

Is your patch in that category or is it a (crude) fix? If it's a fix,
I'm not sure it is of much help at this stage.



Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Tue, Jun 07, 2011 at 09:23:00PM +0200, Paul Bolle wrote:
> On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:
> > That could be useful hint, we do not scan chan by chan, but we
> > have thing called "plcp check health", which "restart radio"
> > by requesting one channel scan. So perhaps disabling that could
> > help.
> 
> At this moment I'm interested in something (a script, some sequence of
> actions, whatever) that (somewhat) reliably triggers this error. Because
> right now I have no clue what triggers it.

Having reliable reproducer will be definitely something that is
nice to have. But bug could be some kind of race condition that happen
in code flow  once per 10000000000 cases ...  

> Is your patch in that category or is it a (crude) fix? If it's a fix,
> I'm not sure it is of much help at this stage.

It could be possible fix. Why you can not simply patch and see if errors
are still there? If after a week or so there will be no errors, we could
consider bug fixed, otherwise well ... still will need looking around
for fix.

I just posted patch that remove these "plcp health check" and related
code on -next anyway, because I don't think this is something that we
need.

Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Wed, 2011-06-08 at 15:47 +0200, Stanislaw Gruszka wrote:
> It could be possible fix. Why you can not simply patch and see if errors
> are still there? If after a week or so there will be no errors, we could
> consider bug fixed, otherwise well ... still will need looking around
> for fix.
> 
> I just posted patch that remove these "plcp health check" and related
> code on -next anyway, because I don't think this is something that we
> need.

0) This is just to note that I haven't yet tried to see if you're small
patch helps. I still hope to do that as I have not given up on this
issue. Feel free to prod me if I again disappear for too long and you
loose your patience.

1) By the way, I still see this error (every now and then) in my logs.
Most recently while running v3.0.1, so it appears not to be fixed by
recent updates for iwl4965 (if any).


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:
> That could be useful hint, we do not scan chan by chan, but we
> have thing called "plcp check health", which "restart radio"
> by requesting one channel scan. So perhaps disabling that could
> help.
> 
> [...]
>
> diff --git a/drivers/net/wireless/iwlegacy/iwl-rx.c b/drivers/net/wireless/iwlegacy/iwl-rx.c
> index 654cf23..6062da0 100644
> --- a/drivers/net/wireless/iwlegacy/iwl-rx.c
> +++ b/drivers/net/wireless/iwlegacy/iwl-rx.c
> @@ -230,6 +230,8 @@ EXPORT_SYMBOL(iwl_legacy_rx_spectrum_measure_notif);
>  void iwl_legacy_recover_from_statistics(struct iwl_priv *priv,
>  				struct iwl_rx_packet *pkt)
>  {
> +	return;
> +
>  	if (test_bit(STATUS_EXIT_PENDING, &priv->status))
>  		return;
>  	if (iwl_legacy_is_any_associated(priv)) {

0) I finally got around to applying this patch (to v3.0.4).

1) After a few days of normal usage (with quite a bit of suspend and
resume cycles) this error was again triggered. So avoiding
check_plcp_health() doesn't seem to help.

2) I never send you the debug output (ie, output after doing "modprobe
iwl4965 debug=0x47ffffff"), did I?


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Sun, Sep 04, 2011 at 10:28:35AM +0200, Paul Bolle wrote:
> On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:
> > That could be useful hint, we do not scan chan by chan, but we
> > have thing called "plcp check health", which "restart radio"
> > by requesting one channel scan. So perhaps disabling that could
> > help.
> > 
> > [...]
> >
> > diff --git a/drivers/net/wireless/iwlegacy/iwl-rx.c b/drivers/net/wireless/iwlegacy/iwl-rx.c
> > index 654cf23..6062da0 100644
> > --- a/drivers/net/wireless/iwlegacy/iwl-rx.c
> > +++ b/drivers/net/wireless/iwlegacy/iwl-rx.c
> > @@ -230,6 +230,8 @@ EXPORT_SYMBOL(iwl_legacy_rx_spectrum_measure_notif);
> >  void iwl_legacy_recover_from_statistics(struct iwl_priv *priv,
> >  				struct iwl_rx_packet *pkt)
> >  {
> > +	return;
> > +
> >  	if (test_bit(STATUS_EXIT_PENDING, &priv->status))
> >  		return;
> >  	if (iwl_legacy_is_any_associated(priv)) {
> 
> 0) I finally got around to applying this patch (to v3.0.4).
> 
> 1) After a few days of normal usage (with quite a bit of suspend and
> resume cycles) this error was again triggered. So avoiding
> check_plcp_health() doesn't seem to help.
> 
> 2) I never send you the debug output (ie, output after doing "modprobe
> iwl4965 debug=0x47ffffff"), did I?

No, but if error show up after few days, gathering and analyzing few
days of debug logs in impractical. Does wifi stop working after an
error, or there is some other negative impact? Or only that messages
are printed and driver recover itself?

Stanislaw

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Mon, 2011-09-05 at 11:33 +0200, Stanislaw Gruszka wrote:
> On Sun, Sep 04, 2011 at 10:28:35AM +0200, Paul Bolle wrote:
> > 1) After a few days of normal usage (with quite a bit of suspend and
> > resume cycles) this error was again triggered. So avoiding
> > check_plcp_health() doesn't seem to help.
> > 
> > 2) I never send you the debug output (ie, output after doing "modprobe
> > iwl4965 debug=0x47ffffff"), did I?
> 
> No, but if error show up after few days, gathering and analyzing few
> days of debug logs in impractical.

I see.

> Does wifi stop working after an
> error, or there is some other negative impact? Or only that messages
> are printed and driver recover itself?

There doesn't seem to be any impact (ie, it might have some impact but
I'm too insensitive to notice). The driver does recover itself and I do
not have to mess with rfkill or "modprobe -r" or whatever. I actually
discovered this because I tend to regularly do
    dmesg -r |  grep "^<[123]>"

to keep myself informed of any kernel errors (or worse). And then these
few dozen lines can't go unnoticed.


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Mon, 2011-09-05 at 12:32 +0200, Paul Bolle wrote:
> On Mon, 2011-09-05 at 11:33 +0200, Stanislaw Gruszka wrote:
> > Does wifi stop working after an
> > error, or there is some other negative impact? Or only that messages
> > are printed and driver recover itself?
> 
> There doesn't seem to be any impact (ie, it might have some impact but
> I'm too insensitive to notice). The driver does recover itself and I do
> not have to mess with rfkill or "modprobe -r" or whatever. I actually
> discovered this because I tend to regularly do
>     dmesg -r |  grep "^<[123]>"
> 
> to keep myself informed of any kernel errors (or worse). And then these
> few dozen lines can't go unnoticed.

0) It's one year later now and this Microcode SW error again showed up
in the logs. I recently upgraded and I haven't kept any logs, but my
guess would be that I have run into that error once every week. (This
laptop is now running a v3.5.3 based kernel as shipped for Fedora 17.)

1) Would you have any suggestions how to pinpoint the cause of this
error? It is mainly annoying, and I managed to ignore it since my
previous message, but I still would like to free the logs from the noise
it makes.


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Paul Bolle]

On Fri, 2012-09-14 at 14:17 +0200, Paul Bolle wrote:
> 0) It's one year later now and this Microcode SW error again showed up
> in the logs. I recently upgraded and I haven't kept any logs, but my
> guess would be that I have run into that error once every week. (This
> laptop is now running a v3.5.3 based kernel as shipped for Fedora 17.)
> 
> 1) Would you have any suggestions how to pinpoint the cause of this
> error? It is mainly annoying, and I managed to ignore it since my
> previous message, but I still would like to free the logs from the noise
> it makes.

0) I ported the "iwlegacy_tracing" patch from
https://bugzilla.kernel.org/show_bug.cgi?id=42766 to v3.6-rc7 and to
iwl4965. I've been running iwl4965 with tracing enabled ever since (that
is on: v3.6-rc7, v3.6, v3.6.1, and v3.6.2). Finally, after only three
weeks I hit our Microcode SW error again.

1) So now I've got a 600+k line (or 65 MB) trace dump. What should I do
with it?


Paul Bolle

Re: [iwl4965] Microcode SW error detected

[Stanislaw Gruszka]

On Mon, Oct 15, 2012 at 04:51:00PM +0200, Paul Bolle wrote:
> On Fri, 2012-09-14 at 14:17 +0200, Paul Bolle wrote:
> > 0) It's one year later now and this Microcode SW error again showed up
> > in the logs. I recently upgraded and I haven't kept any logs, but my
> > guess would be that I have run into that error once every week. (This
> > laptop is now running a v3.5.3 based kernel as shipped for Fedora 17.)
> > 
> > 1) Would you have any suggestions how to pinpoint the cause of this
> > error? It is mainly annoying, and I managed to ignore it since my
> > previous message, but I still would like to free the logs from the noise
> > it makes.
> 
> 0) I ported the "iwlegacy_tracing" patch from
> https://bugzilla.kernel.org/show_bug.cgi?id=42766 to v3.6-rc7 and to
> iwl4965. I've been running iwl4965 with tracing enabled ever since (that
> is on: v3.6-rc7, v3.6, v3.6.1, and v3.6.2). Finally, after only three
> weeks I hit our Microcode SW error again.
> 
> 1) So now I've got a 600+k line (or 65 MB) trace dump. What should I do
> with it?

Just post me privately let say last 10MB of it...

Stanislaw