[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#628444: iwlagn - "MAC is in deep sleep", cannot restore wifi operation




Hi Moritz,

I have not seen this problem or any of the other iwl instabilities in a long time, however, I have been running with these option lines disabling 11n functionality in order to achieve that stability:

    options iwlagn 11n_disable50=1
    options iwlwifi 11n_disable=1

since I am no longer running kernels which use iwlagn (currently running 3.2.xx), I can't really speak to the original issue anymore. Of course iwlwifi has had 11n related stability issues as well, however, I have never seen the:

  "MAC is in deep sleep"

bug (as far as I can recall) while running a newer kernel with iwlwifi instead of iwlagn. Not sure how much code (if any) is common between iwlwifi and the older iwlagn module.

I suppose I should try enabling 11n again to see what happens (I had forgotten it was disabled).

The upgrade to wheezy is most notable for much shorter times required to make wireless connections, though I am not sure if it is the driver or network-manager responsible for that improvement.

FWIW.

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


On Thu, 15 Aug 2013, Moritz Muehlenhoff wrote:

reassign 628444 src:linux
thanks

On Wed, Mar 14, 2012 at 08:37:17PM -0700, Shannon Dealy wrote:


Like others, the problems seemed to start around 2.6.39.

Thought I should note here, my system showed this problem with 2.6.36
through 2.6.39.  It seems to have stopped showing the problem (possibly
due to a memory upgrade many months ago), but it still has chronic
instability of the connection (drops out for varying intervals), and
often, network-manager doesn't seem aware of the failure - reloading the
driver isn't a reliable solution (sometimes appears to work, often does
not)

Does this bug still occur with more recent kernels/firmware, e.g. Wheezy?

Cheers,
       Moritz



Reply to: