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

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



Shannon Dealy <dealy@deatech.com> writes:

> I created a file "/etc/modprobe.d/iwlagn.conf" and placed the
> following line in it:
>
>   options iwlagn 11n_disable=1 11n_disable50=1

Note that the 11n_disable50 options was removed in 3.0 and the iwlagn
module was renamed to iwlwifi in 3.2.

Which makes this workaround pretty much irrelevant to any current Debian
kernel as noone(?) has seen the bug in 2.6.32.  Are you still using the
2.6.39-1 kernel you originally opened this bug against?

FWIW, I enabled power_save a few days ago (was previously at default)
after the nice summary from Meenakshi, just to see if I could replicate
this issue.  My module parameters are now:

bjorn@nemi:~$ grep . /sys/module/iwlwifi/parameters/*
/sys/module/iwlwifi/parameters/11n_disable:0
/sys/module/iwlwifi/parameters/ack_check:N
/sys/module/iwlwifi/parameters/amsdu_size_8K:1
/sys/module/iwlwifi/parameters/antenna_coupling:0
/sys/module/iwlwifi/parameters/auto_agg:Y
/sys/module/iwlwifi/parameters/bt_ch_inhibition:Y
/sys/module/iwlwifi/parameters/bt_coex_active:Y
/sys/module/iwlwifi/parameters/fw_restart:1
/sys/module/iwlwifi/parameters/led_mode:0
/sys/module/iwlwifi/parameters/no_sleep_autoadjust:Y
/sys/module/iwlwifi/parameters/plcp_check:Y
/sys/module/iwlwifi/parameters/power_level:0
/sys/module/iwlwifi/parameters/power_save:Y
/sys/module/iwlwifi/parameters/queues_num:0
/sys/module/iwlwifi/parameters/swcrypto:0
/sys/module/iwlwifi/parameters/ucode_alternative:1
/sys/module/iwlwifi/parameters/wd_disable:0


And I am often using 802.11n at 5GHz.  Still haven't seen the issue.

But I wonder about Juha's observation about this difference between my
setup: 

  [   12.611061] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S

and his:

  [245082.407512] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S

This looks extremely suspicious to me in light of Meenakshi's comment on
known issues with L1 on these devices and that Intel therefore use L0S
by default.

How come Juha end up with L1 enabled, then?  And is that the case for
everyone seeing this bug?



Bjørn



Reply to: