Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
available for download from
http://intellinuxwireless.org/?n=Downloads
Changes:
-- More graceful handling of Rx hangs (NMI)
-- More reliable scanning
-- Wait 10 seconds after association before power down
-- Reset receiver via retune after missing beacons
-- Disable TGK measurement when receiving packet
-- More reliable Tx of ACK/BA/CTS
Reinette
Hi John,
On Mon, 2009-07-13 at 12:52 -0700, John Ranson wrote:
> Reinette,
>
> On Mon, Jul 13, 2009 at 11:56 AM, reinette
> chatre<[email protected]> wrote:
> > John,
> >
> > On Mon, 2009-07-13 at 11:43 -0700, John Ranson wrote:
> >> I am also seeing frequent loss of association and firmware restarts
> >> with the new firmware. On occasion, I can't recover even when I
> >> reload the driver. Admittedly, I am using an old driver right now
> >> (2.6.29, I think).
> >
> > The better restart work was added in 2.6.31 I think, so it is only in
> > the recent driver that you will have a smooth recovery after a failure.
> > You may thus be seeing the same problem as Helmut, with him running the
> > recent restart code.
>
> Can I also get this with the latest compat wireless release and
> 2.6.30.1? I don't usually switch to a new kernel until it's been
> stable for a while.
yes - compat wireless contains all the latest code, which includes this
restart work.
>
> >
> >>
> >> I'm going to upgrade to 2.6.30.1 with the latest compat-wireless. I'll
> >> file a bug if things continue as they are.
> >
> > Even if the restart code gets you up and running smoothly after a
> > failure, please do submit a bug report so that we can look into this.
>
> I'll be sure to file a bug.
Thank you very much
Reinette
W dniu 10 lipca 2009 01:26 użytkownik reinette chatre
<[email protected]> napisał:
>> Can you reveal some plans of upgrading 5100/5300/5350 uCode? Any
>> estimate would be nice to known. This month? This year?
>
> I am not aware of any scheduled date for a new release. Are there
> critical issues that you are aware of that requires a new uCode?
I noticed new bug report about firmware failure on scp (using new
firmware). I use ssh/sftp/scp a lot, so it doesn't sound nice to me.
Moreover it seems to be quite reproductable, so I'm scared of hittint
it quite often.
--
Rafał Miłecki
Reinette,
On Mon, Jul 13, 2009 at 11:56 AM, reinette
chatre<[email protected]> wrote:
> John,
>
> On Mon, 2009-07-13 at 11:43 -0700, John Ranson wrote:
>> I am also seeing frequent loss of association and firmware restarts
>> with the new firmware. ?On occasion, I can't recover even when I
>> reload the driver. Admittedly, I am using an old driver right now
>> (2.6.29, I think).
>
> The better restart work was added in 2.6.31 I think, so it is only in
> the recent driver that you will have a smooth recovery after a failure.
> You may thus be seeing the same problem as Helmut, with him running the
> recent restart code.
Can I also get this with the latest compat wireless release and
2.6.30.1? I don't usually switch to a new kernel until it's been
stable for a while.
>
>>
>> I'm going to upgrade to 2.6.30.1 with the latest compat-wireless. I'll
>> file a bug if things continue as they are.
>
> Even if the restart code gets you up and running smoothly after a
> failure, please do submit a bug report so that we can look into this.
I'll be sure to file a bug.
John
Am Donnerstag, 9. Juli 2009 schrieb reinette chatre:
> Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> available for download from
> http://intellinuxwireless.org/?n=Downloads
The new ucode seems to cause fw restarts every now and then (together
with wireless-testing).
iwlagn 0000:10:00.0: Microcode SW error detected. Restarting 0x82000000.
I couldn't figure out how to reproduce this but it happened a few times
now since I switched to the new ucode.
Should I load iwlagn with some special debug flags?
Helmut
W dniu 13 lipca 2009 22:30 użytkownik Rafał Miłecki <[email protected]> napisał:
> W dniu 10 lipca 2009 01:26 użytkownik reinette chatre
> <[email protected]> napisał:
>>> Can you reveal some plans of upgrading 5100/5300/5350 uCode? Any
>>> estimate would be nice to known. This month? This year?
>>
>> I am not aware of any scheduled date for a new release. Are there
>> critical issues that you are aware of that requires a new uCode?
>
> I noticed new bug report about firmware failure on scp (using new
> firmware). I use ssh/sftp/scp a lot, so it doesn't sound nice to me.
>
> Moreover it seems to be quite reproductable, so I'm scared of hittint
> it quite often.
Probably I really should post link to bug report:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004
--
Rafał Miłecki
On Mon, 2009-07-13 at 13:32 -0700, Rafał Miłecki wrote:
> W dniu 13 lipca 2009 22:30 użytkownik Rafał Miłecki <[email protected]> napisał:
> > W dniu 10 lipca 2009 01:26 użytkownik reinette chatre
> > <[email protected]> napisał:
> >>> Can you reveal some plans of upgrading 5100/5300/5350 uCode? Any
> >>> estimate would be nice to known. This month? This year?
> >>
> >> I am not aware of any scheduled date for a new release. Are there
> >> critical issues that you are aware of that requires a new uCode?
> >
> > I noticed new bug report about firmware failure on scp (using new
> > firmware). I use ssh/sftp/scp a lot, so it doesn't sound nice to me.
> >
> > Moreover it seems to be quite reproductable, so I'm scared of hittint
> > it quite often.
>
> Probably I really should post link to bug report:
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004
This bug was reported against 5100 series hardware and is not present in
4965. Even so, this bug was fixed in the driver and the patch has
already been pushed upstream.
Reinette
On Mon, 2009-07-13 at 13:43 -0700, Rafał Miłecki wrote:
> W dniu 13 lipca 2009 22:38 użytkownik reinette chatre
> <[email protected]> napisał:
> >> Probably I really should post link to bug report:
> >> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004
> >
> > This bug was reported against 5100 series hardware and is not present in
> > 4965. Even so, this bug was fixed in the driver and the patch has
> > already been pushed upstream.
>
> Great, thanks for clarifying. It was reported on 5100, reproduced on
> 5300, so I was afraid also with my 4965 :)
>
> If I may suggest something, it would be nice to keep current status in
> bug report. I was waiting to see any commend about fixing driver of
> resolving report by updating firmware.
I think the information you are asking for is captured in comments 16
and 17.
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004#c16
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004#c17
Reinette
W dniu 13 lipca 2009 22:48 użytkownik reinette chatre
<[email protected]> napisał:
> I think the information you are asking for is captured in comments 16
> and 17.
>
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004#c16
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004#c17
Ups, I totally failed in my reading skills :/
--
Rafał Miłecki
W dniu 13 lipca 2009 22:38 użytkownik reinette chatre
<[email protected]> napisał:
>> Probably I really should post link to bug report:
>> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2004
>
> This bug was reported against 5100 series hardware and is not present in
> 4965. Even so, this bug was fixed in the driver and the patch has
> already been pushed upstream.
Great, thanks for clarifying. It was reported on 5100, reproduced on
5300, so I was afraid also with my 4965 :)
If I may suggest something, it would be nice to keep current status in
bug report. I was waiting to see any commend about fixing driver of
resolving report by updating firmware.
--
Rafał Miłecki
Am Montag, 13. Juli 2009 schrieb reinette chatre:
> On Sun, 2009-07-12 at 05:45 -0700, Helmut Schaa wrote:
> > Am Donnerstag, 9. Juli 2009 schrieb reinette chatre:
> > > Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> > > available for download from
> > > http://intellinuxwireless.org/?n=Downloads
> >
> > The new ucode seems to cause fw restarts every now and then (together
> > with wireless-testing).
>
> oh no ...
>
> >
> > iwlagn 0000:10:00.0: Microcode SW error detected. Restarting 0x82000000.
>
> What is the status when such an error occurs? Can it recover on its own
> or do you need to take action? What action is needed?
It recovers automatically, no action required. Not sure if it has any
negative impact on the connection. At least I did not notice anything yet.
> > I couldn't figure out how to reproduce this but it happened a few times
> > now since I switched to the new ucode.
> >
> > Should I load iwlagn with some special debug flags?
>
> If your driver is compiled with CONFIG_IWLWIFI_DEBUG then you can pass a
> debug flag to the module that will print a ucode event log when it
> encounters a problem like this. As it will only print out the event log
> when this error occurs you can safely turn this debugging on permanently
> without risking a clutter of your logs. Later, if you know how to
> reproduce is you can increase debugging to get more details about what
> the driver is actually doing. The debug flag for _just_ the ucode event
> log is 0x40000 (like "modprobe iwlagn debug=0x40000"). The 0x43fff is a
> more general debug flag that helps with obtaining more information.
>
> When you have this data - could you please submit a bug at
> intellinuxwireless.org/bugzilla for us to be able to track it?
Will do as soon as I find a way to reproduce it.
Helmut
John,
On Mon, 2009-07-13 at 11:43 -0700, John Ranson wrote:
> I am also seeing frequent loss of association and firmware restarts
> with the new firmware. On occasion, I can't recover even when I
> reload the driver. Admittedly, I am using an old driver right now
> (2.6.29, I think).
The better restart work was added in 2.6.31 I think, so it is only in
the recent driver that you will have a smooth recovery after a failure.
You may thus be seeing the same problem as Helmut, with him running the
recent restart code.
>
> I'm going to upgrade to 2.6.30.1 with the latest compat-wireless. I'll
> file a bug if things continue as they are.
Even if the restart code gets you up and running smoothly after a
failure, please do submit a bug report so that we can look into this.
> Thank you very much for getting the new firmware out!
Reinette
2009/7/9 reinette chatre <[email protected]>:
> Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> available for download from
> http://intellinuxwireless.org/?n=Downloads
>
> Changes:
>
> -- More graceful handling of Rx hangs (NMI)
> -- More reliable scanning
> -- Wait 10 seconds after association before power down
> -- Reset receiver via retune after missing beacons
> -- Disable TGK measurement when receiving packet
> -- More reliable Tx of ACK/BA/CTS
Nice work, AFAICU this should fix a few annoying issues, right?
Can you reveal some plans of upgrading 5100/5300/5350 uCode? Any
estimate would be nice to known. This month? This year?
--
Rafał Miłecki
Hi Helmut,
On Sun, 2009-07-12 at 05:45 -0700, Helmut Schaa wrote:
> Am Donnerstag, 9. Juli 2009 schrieb reinette chatre:
> > Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> > available for download from
> > http://intellinuxwireless.org/?n=Downloads
>
> The new ucode seems to cause fw restarts every now and then (together
> with wireless-testing).
oh no ...
>
> iwlagn 0000:10:00.0: Microcode SW error detected. Restarting 0x82000000.
What is the status when such an error occurs? Can it recover on its own
or do you need to take action? What action is needed?
>
> I couldn't figure out how to reproduce this but it happened a few times
> now since I switched to the new ucode.
>
> Should I load iwlagn with some special debug flags?
If your driver is compiled with CONFIG_IWLWIFI_DEBUG then you can pass a
debug flag to the module that will print a ucode event log when it
encounters a problem like this. As it will only print out the event log
when this error occurs you can safely turn this debugging on permanently
without risking a clutter of your logs. Later, if you know how to
reproduce is you can increase debugging to get more details about what
the driver is actually doing. The debug flag for _just_ the ucode event
log is 0x40000 (like "modprobe iwlagn debug=0x40000"). The 0x43fff is a
more general debug flag that helps with obtaining more information.
When you have this data - could you please submit a bug at
intellinuxwireless.org/bugzilla for us to be able to track it?
Thank you very much
Reinette
I am also seeing frequent loss of association and firmware restarts
with the new firmware. On occasion, I can't recover even when I
reload the driver. Admittedly, I am using an old driver right now
(2.6.29, I think).
I'm going to upgrade to 2.6.30.1 with the latest compat-wireless. I'll
file a bug if things continue as they are.
Thank you very much for getting the new firmware out!
Cheers,
John
On Mon, Jul 13, 2009 at 8:46 AM, reinette
chatre<[email protected]> wrote:
> Hi Helmut,
>
> On Sun, 2009-07-12 at 05:45 -0700, Helmut Schaa wrote:
>> Am Donnerstag, 9. Juli 2009 schrieb reinette chatre:
>> > Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
>> > available for download from
>> > http://intellinuxwireless.org/?n=Downloads
>>
>> The new ucode seems to cause fw restarts every now and then (together
>> with wireless-testing).
>
> oh no ...
>
>>
>> iwlagn 0000:10:00.0: Microcode SW error detected. ?Restarting 0x82000000.
>
> What is the status when such an error occurs? Can it recover on its own
> or do you need to take action? What action is needed?
>
>>
>> I couldn't figure out how to reproduce this but it happened a few times
>> now since I switched to the new ucode.
>>
>> Should I load iwlagn with some special debug flags?
>
> If your driver is compiled with CONFIG_IWLWIFI_DEBUG then you can pass a
> debug flag to the module that will print a ucode event log when it
> encounters a problem like this. As it will only print out the event log
> when this error occurs you can safely turn this debugging on permanently
> without risking a clutter of your logs. Later, if you know how to
> reproduce is you can increase debugging to get more details about what
> the driver is actually doing. The debug flag for _just_ the ucode event
> log is 0x40000 (like "modprobe iwlagn debug=0x40000"). The 0x43fff is a
> more general debug flag that helps with obtaining more information.
>
> When you have this data - could you please submit a bug at
> intellinuxwireless.org/bugzilla for us to be able to track it?
>
> Thank you very much
>
> Reinette
>
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Ipw3945-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw3945-devel
>
On Thu, 2009-07-09 at 16:13 -0700, Rafał Miłecki wrote:
> 2009/7/9 reinette chatre <[email protected]>:
> > Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> > available for download from
> > http://intellinuxwireless.org/?n=Downloads
> >
> > Changes:
> >
> > -- More graceful handling of Rx hangs (NMI)
> > -- More reliable scanning
> > -- Wait 10 seconds after association before power down
> > -- Reset receiver via retune after missing beacons
> > -- Disable TGK measurement when receiving packet
> > -- More reliable Tx of ACK/BA/CTS
>
> Nice work, AFAICU this should fix a few annoying issues, right?
We hope so.
> Can you reveal some plans of upgrading 5100/5300/5350 uCode? Any
> estimate would be nice to known. This month? This year?
I am not aware of any scheduled date for a new release. Are there
critical issues that you are aware of that requires a new uCode?
Reinette