Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-09-17 Thread maximilian attems
On Wed, 14 Sep 2011, Shannon Dealy wrote:

 On Tue, 13 Sep 2011, maximilian attems wrote:
 
 tags 628444 moreinfo
 stop
 
 This bug actually applies to all Debian kernels I have tried including
 2.6.36, 2.6.37, 2.6.38, and 2.6,39
 
 Did you try since newer 3.0 images, how are they performing?
 
 thank you
 
 I wasn't aware that the 3.0 kernels were out until you sent this
 message. Unfortunately, since this bug takes time to manifest, it
 will require that I run with 3.0 as my default kernel, this means I
 have to get vmware to run with it (since I use it heavily), and that
 is usually a problem for bleeding edge kernels.  I will look into
 it, but it may be a week or so before I can even try running a 3.0
 kernel.

bleeding edge would be against linux-next, 3.1-rcX is in experimental.
that would be next target if problem persists.

Anyway according to your description you are loading binary blobs
into your OS, so you just voided our support and this bug report
can be closed away unless you can reproduce without.

-- 
maks



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-09-17 Thread Shannon Dealy

On Sat, 17 Sep 2011, maximilian attems wrote:


I wasn't aware that the 3.0 kernels were out until you sent this
message. Unfortunately, since this bug takes time to manifest, it
will require that I run with 3.0 as my default kernel, this means I
have to get vmware to run with it (since I use it heavily), and that
is usually a problem for bleeding edge kernels.  I will look into
it, but it may be a week or so before I can even try running a 3.0
kernel.


bleeding edge would be against linux-next, 3.1-rcX is in experimental.
that would be next target if problem persists.


Bleeding edge is anything which hasn't been in use long enough that there 
is still significant potential for major bugs.   Having had very long 
experience with the Linux kernel (and having fixed the bugs myself on 
several occasions), the 3.x kernels qualify.



Anyway according to your description you are loading binary blobs
into your OS, so you just voided our support and this bug report
can be closed away unless you can reproduce without.


1- Actually, VMWare provides the source code for their kernel interface
   code which uses loadable modules, but usually someone has to work up a
   source code patch for the latest versions of the kernel ( 6-9 months
   old) and then users have to patch and rebuild the kernel interface.  I
   have worked up patches myself on a few occasions, but I don't really
   have the time.

2- I wasn't running VMWare at the time I reported these problems, I use
   it only for customer software development and there weren't any
   customers back then.  Now I am rather busy.

So no, this bug report cannot be closed on that basis and as I stated 
before, even a cursory scan of the internet shows this is a common 
problem for people running similar hardware, so even if I were running 
binary blobs, the bug should remain open.


NOTE: If one were to assume that VMWare were in any way relevant to this 
problem, then the bug should move from machine to machine as I migrate my 
development environment.  Instead, the bug showed up when I moved to a new 
machine with different hardware and device drivers, but the same kernel.

I upgraded to a variety of different kernels in the hope that one of them
would work and have settled on the current one I am running because it 
seems to have the problem less often.


Shannon C. Dealy  |   DeaTech Research Inc.
de...@deatech.com |  - Custom Software Development -
Phone: (800) 467-5820 |  - Natural Building Instruction -
   or: (541) 929-4089 |  www.deatech.com



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-09-17 Thread Shannon Dealy


A developer at Intel contacted me regarding this bug the other day (he 
was following up on a similar bug report from another source) and I 
am working with him on the problem (currently doing a debug build of the 
module to collect data on what is happening).


Shannon C. Dealy  |   DeaTech Research Inc.
de...@deatech.com |  - Custom Software Development -
Phone: (800) 467-5820 |  - Natural Building Instruction -
   or: (541) 929-4089 |  www.deatech.com



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-09-15 Thread Shannon Dealy

On Tue, 13 Sep 2011, maximilian attems wrote:


tags 628444 moreinfo
stop


This bug actually applies to all Debian kernels I have tried including
2.6.36, 2.6.37, 2.6.38, and 2.6,39


Did you try since newer 3.0 images, how are they performing?

thank you


I wasn't aware that the 3.0 kernels were out until you sent this message. 
Unfortunately, since this bug takes time to manifest, it will require that 
I run with 3.0 as my default kernel, this means I have to get vmware to 
run with it (since I use it heavily), and that is usually a problem for 
bleeding edge kernels.  I will look into it, but it may be a week or so 
before I can even try running a 3.0 kernel.


Shannon C. Dealy  |   DeaTech Research Inc.
de...@deatech.com |  - Custom Software Development -
Phone: (800) 467-5820 |  - Natural Building Instruction -
   or: (541) 929-4089 |  www.deatech.com



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-09-13 Thread maximilian attems
tags 628444 moreinfo
stop

 This bug actually applies to all Debian kernels I have tried including
 2.6.36, 2.6.37, 2.6.38, and 2.6,39 

Did you try since newer 3.0 images, how are they performing?

thank you



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation

2011-05-28 Thread Shannon Dealy
Package: linux-2.6
Version: 2.6.39-1
Severity: important


After some arbitrary period of use, wifi fails and errors show up in syslog
indicating MAC is in deep sleep after which nothing can be done to restore
wifi functionality other than rebooting the system.  In most (possibly all)
cases, the failure occurs after the laptop has been suspended and resumed
at least once, though the actual occurance may not be immediately after
resuming, it often occurs within a few minutes after resume.

Unloading and reloading the iwlagn driver and the drivers it relies on have
no effect.

Speculation:
   there is a mechanical switch on the side of the laptop which
   cuts power to both bluetooth and wifi on this machine.  Unloading iwlagn
   turning off the switch waiting ten seconds, then turning it on and reloading 
   iwlagn also has no effect.  Assuming this switch actually is a hardware
   power off of the devices, this should reset the device and a reload of
   the driver should restore functionality.  Since this does not occur, I
   see only two possibilities, either the power switch does not completely
   power off the device, or the kernel is retaining some bogus information
   (possibly placed there by iwlagn) about the device in spite of the driver
   being unloaded and reloaded.  Even if it doesn't prevent the problem,
   simply curing this issue so the device can be restarted without rebooting
   would be a major improvement.

I have tried a number of different versions of the firmware as well as
different kernels, all combinations have the problem, though some seem to
be more stable than others.  In some combinations it make take one to two
weeks of usage with perhaps a dozen suspend resume cycles per day, in others
it seems to happen every day.

I have noted in my search of the net that Lenovo laptops seem to be most
(possibly all, I wasn't paying close attention) of the cases where this
bug occurs.

My system is a Lenovo x201i, the wifi adapter was listed as an:

Intel Centrino Advanced-N 6200 (2x2 AGN)


This bug actually applies to all Debian kernels I have tried including 2.6.36,
2.6.37, 2.6.38, and 2.6,39 (various versions of each and I think it included
earlier ones, but I don't remember which ones and no longer have them
installed).

NOTE: this appears to be the same as closed bug 589383 which was closed
upstream and tagged unreproducible.  Even the most cursory search of 
the net shows there are lots of people having no problems reproducing it.
It strikes me as inappropriate to close a bug as unreproducible when it
is quite clear that many people are seeing it.


May 28 15:19:12 nashapur kernel: [16275.165421] iwlagn :02:00.0: Error 
sending REPLY_ADD_STA: time out after 500ms.
May 28 15:19:12 nashapur kernel: [16275.165428] HW problem - can not stop rx 
aggregation for tid 0
May 28 15:19:12 nashapur ifd[1923]: executing: 
'/usr/share/laptop-net/link-change wlan0 unmanaged up,running,connected 
up,running,disconnected'
May 28 15:19:12 nashapur kernel: [16275.664639] iwlagn :02:00.0: Error 
sending REPLY_QOS_PARAM: time out after 500ms.
May 28 15:19:12 nashapur kernel: [16275.664644] iwlagn :02:00.0: Failed to 
update QoS
May 28 15:19:12 nashapur kernel: [16275.748419] iwlagn :02:00.0: Queue 2 
stuck for 2000 ms.
May 28 15:19:12 nashapur kernel: [16275.748429] iwlagn :02:00.0: On demand 
firmware reload
May 28 15:19:13 nashapur kernel: [16276.163702] iwlagn :02:00.0: Error 
sending REPLY_RXON: time out after 500ms.
May 28 15:19:13 nashapur kernel: [16276.163709] iwlagn :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
May 28 15:19:13 nashapur kernel: [16276.180377] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.196983] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.213584] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.230200] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.246801] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.263411] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.280011] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.296612] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.313214] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.329830] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.346433] iwlagn :02:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0x
May 28 15:19:13 nashapur kernel: [16276.363037] iwlagn