Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
Hi Johannes,
Sorry for the late reply, I was travelling around the world ...
I have now tested the =2 and =4 settings at home, with the following
outcome:
On Do, 12 Jul 2012, Johannes Berg wrote:
> With the latest, I've extended 11n_disable to have more bits.
>
> 11n_disable=1 will disable HT completely
> 11n_disable=2 will disable TX aggregation
> 11n_disable=4 will disable RX aggregation
11n_disabled=2:
lots of messages
Open BA session requested for 00:0a:79:eb:56:10 tid 0
BA request denied - HW unavailable for tid 0
and
Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
Rx A-MPDU request on tid 0 result 0
Connection is stable for quite some time, but after 1-2 hours I got
a bad hang, grinding to a halt. pings to kernel.org gives 26%
packet loss, but the rest of the packets are fast 130ms
(Isn't that a strange thing - 25+% packet loss and all others are fast?)
I assume the packaet loss is related to the above messages.
11n_disabled=4:
lots of messages
Rx A-MPDU request on tid 0 result -22
and at some point ping timeouts of 80+ secs (!) and then total hang
(as far as I remember)
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
PERRANZABULOE (n.)
One of those spray things used to wet ironing with.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
Hi Johannes,
Sorry for the late reply, I was travelling around the world ...
I have now tested the =2 and =4 settings at home, with the following
outcome:
On Do, 12 Jul 2012, Johannes Berg wrote:
With the latest, I've extended 11n_disable to have more bits.
11n_disable=1 will disable HT completely
11n_disable=2 will disable TX aggregation
11n_disable=4 will disable RX aggregation
11n_disabled=2:
lots of messages
Open BA session requested for 00:0a:79:eb:56:10 tid 0
BA request denied - HW unavailable for tid 0
and
Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
Rx A-MPDU request on tid 0 result 0
Connection is stable for quite some time, but after 1-2 hours I got
a bad hang, grinding to a halt. pings to kernel.org gives 26%
packet loss, but the rest of the packets are fast 130ms
(Isn't that a strange thing - 25+% packet loss and all others are fast?)
I assume the packaet loss is related to the above messages.
11n_disabled=4:
lots of messages
Rx A-MPDU request on tid 0 result -22
and at some point ping timeouts of 80+ secs (!) and then total hang
(as far as I remember)
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
PERRANZABULOE (n.)
One of those spray things used to wet ironing with.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
On Thu, 2012-07-12 at 17:14 +0900, Norbert Preining wrote: > > I can actually work now wirelessly, and in case of hangs an rfkill block > > rfkill unblock practically always, and mostly is not needed. > > Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the > iwlwifi module with > 11n_disable=1 > > Now, latest git from today, I though, let us try to enable 11n again, > and there we go, boot from cold machine and after short time everything > is dead without reaction. Dmesg gives many many funny messages: > > [ 30.047943] iwlwifi :06:00.0: L1 Enabled; Disabling L0S > [ 30.051933] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 > [ 30.164836] iwlwifi :06:00.0: L1 Enabled; Disabling L0S > [ 30.167876] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 > [ 37.533619] wlan0: authenticate with 00:0a:79:eb:56:10 > [ 37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3) > [ 37.538241] wlan0: authenticated > [ 37.538391] wlan0: associating with AP with corrupt beacon That might be an indication of things already going wrong with your AP ... :-( [snip log] Mostly from the log it seems that there's a lot of spurious aggregation setup/teardown, some of it seems to originate from the AP. > At that point I removed the iwlwifi module, and reloaded it with > 11n_disable=1 again, otherwise nothing would work at all... With the latest, I've extended 11n_disable to have more bits. 11n_disable=1 will disable HT completely 11n_disable=2 will disable TX aggregation 11n_disable=4 will disable RX aggregation It'd be interesting to see what happens for you with 11n_disable=2/4/6. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
In preach for decent iwl driver ... On Do, 28 Jun 2012, Norbert Preining wrote: > > You seem to be on 3.5.0-rc now, is that really no different from 3.4? > > The feeling is that it is definitely better. > > I can actually work now wirelessly, and in case of hangs an rfkill block > rfkill unblock practically always, and mostly is not needed. Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the iwlwifi module with 11n_disable=1 Now, latest git from today, I though, let us try to enable 11n again, and there we go, boot from cold machine and after short time everything is dead without reaction. Dmesg gives many many funny messages: [ 30.047943] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.051933] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 30.164836] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.167876] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 37.533619] wlan0: authenticate with 00:0a:79:eb:56:10 [ 37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3) [ 37.538241] wlan0: authenticated [ 37.538391] wlan0: associating with AP with corrupt beacon [ 37.540056] wlan0: associate with 00:0a:79:eb:56:10 (try 1/3) [ 37.543844] wlan0: RX AssocResp from 00:0a:79:eb:56:10 (capab=0x411 status=0 aid=3) [ 37.543848] wlan0: associated [ 37.547219] cfg80211: Calling CRDA for country: JP [ 37.551474] cfg80211: Regulatory domain changed to country: JP [ 37.551477] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 37.551479] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551481] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (N/A, 2000 mBm) [ 37.551483] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm) [ 37.551485] cfg80211: (491 KHz - 493 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551486] cfg80211: (491 KHz - 499 KHz @ 4 KHz), (N/A, 2300 mBm) [ 37.551488] cfg80211: (493 KHz - 495 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551490] cfg80211: (503 KHz - 5045000 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551492] cfg80211: (503 KHz - 509 KHz @ 4 KHz), (N/A, 2300 mBm) [ 37.551494] cfg80211: (505 KHz - 506 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551495] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551497] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551499] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2300 mBm) [ 39.526929] Rx A-MPDU request on tid 0 result 0 [ 46.907606] type=1305 audit(1342079160.633:43563): auid=4294967295 ses=4294967295 op="remove rule" key=(null) list=4 res=1 [ 46.907619] type=1305 audit(1342079160.633:43564): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1 [ 49.372661] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 49.392528] activated addBA response timer on tid 0 [ 49.394760] switched off addBA timer for tid 0 [ 49.394769] Aggregation is on for tid 0 [ 52.416068] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416081] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416089] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416096] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416103] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416110] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416117] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416124] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416131] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416138] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 69.252057] tx session timer expired on tid 0 [ 69.252125] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0 [ 69.272673] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0 [ 99.933558] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 99.952530] activated addBA response timer on tid 0 [ 99.954667] switched off addBA timer for tid 0 [ 99.954676] Aggregation is on for tid 0 [ 115.075768] net_ratelimit: 25 callbacks suppressed [ 115.075783] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0 [ 122.721571] Rx A-MPDU request on tid 0 result 0 [ 132.008042] tx session timer expired on tid 0 [ 132.008099] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0 [ 132.028663] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0 [ 150.396166] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 150.416568] activated addBA response timer on tid 0 [ 150.418855] switched off addBA timer for tid 0 [ 150.418864] Aggregation is on for tid 0
Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
In preach for decent iwl driver ... On Do, 28 Jun 2012, Norbert Preining wrote: You seem to be on 3.5.0-rc now, is that really no different from 3.4? The feeling is that it is definitely better. I can actually work now wirelessly, and in case of hangs an rfkill block rfkill unblock practically always, and mostly is not needed. Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the iwlwifi module with 11n_disable=1 Now, latest git from today, I though, let us try to enable 11n again, and there we go, boot from cold machine and after short time everything is dead without reaction. Dmesg gives many many funny messages: [ 30.047943] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.051933] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 30.164836] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.167876] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 37.533619] wlan0: authenticate with 00:0a:79:eb:56:10 [ 37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3) [ 37.538241] wlan0: authenticated [ 37.538391] wlan0: associating with AP with corrupt beacon [ 37.540056] wlan0: associate with 00:0a:79:eb:56:10 (try 1/3) [ 37.543844] wlan0: RX AssocResp from 00:0a:79:eb:56:10 (capab=0x411 status=0 aid=3) [ 37.543848] wlan0: associated [ 37.547219] cfg80211: Calling CRDA for country: JP [ 37.551474] cfg80211: Regulatory domain changed to country: JP [ 37.551477] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 37.551479] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551481] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (N/A, 2000 mBm) [ 37.551483] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm) [ 37.551485] cfg80211: (491 KHz - 493 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551486] cfg80211: (491 KHz - 499 KHz @ 4 KHz), (N/A, 2300 mBm) [ 37.551488] cfg80211: (493 KHz - 495 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551490] cfg80211: (503 KHz - 5045000 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551492] cfg80211: (503 KHz - 509 KHz @ 4 KHz), (N/A, 2300 mBm) [ 37.551494] cfg80211: (505 KHz - 506 KHz @ 1 KHz), (N/A, 2300 mBm) [ 37.551495] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551497] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 37.551499] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2300 mBm) [ 39.526929] Rx A-MPDU request on tid 0 result 0 [ 46.907606] type=1305 audit(1342079160.633:43563): auid=4294967295 ses=4294967295 op=remove rule key=(null) list=4 res=1 [ 46.907619] type=1305 audit(1342079160.633:43564): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1 [ 49.372661] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 49.392528] activated addBA response timer on tid 0 [ 49.394760] switched off addBA timer for tid 0 [ 49.394769] Aggregation is on for tid 0 [ 52.416068] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416081] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416089] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416096] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416103] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416110] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416117] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416124] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416131] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 52.416138] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames [ 69.252057] tx session timer expired on tid 0 [ 69.252125] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0 [ 69.272673] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0 [ 99.933558] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 99.952530] activated addBA response timer on tid 0 [ 99.954667] switched off addBA timer for tid 0 [ 99.954676] Aggregation is on for tid 0 [ 115.075768] net_ratelimit: 25 callbacks suppressed [ 115.075783] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0 [ 122.721571] Rx A-MPDU request on tid 0 result 0 [ 132.008042] tx session timer expired on tid 0 [ 132.008099] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0 [ 132.028663] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0 [ 150.396166] Open BA session requested for 00:0a:79:eb:56:10 tid 0 [ 150.416568] activated addBA response timer on tid 0 [ 150.418855] switched off addBA timer for tid 0 [ 150.418864] Aggregation is on for tid 0 [
Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
On Thu, 2012-07-12 at 17:14 +0900, Norbert Preining wrote: I can actually work now wirelessly, and in case of hangs an rfkill block rfkill unblock practically always, and mostly is not needed. Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the iwlwifi module with 11n_disable=1 Now, latest git from today, I though, let us try to enable 11n again, and there we go, boot from cold machine and after short time everything is dead without reaction. Dmesg gives many many funny messages: [ 30.047943] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.051933] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 30.164836] iwlwifi :06:00.0: L1 Enabled; Disabling L0S [ 30.167876] iwlwifi :06:00.0: Radio type=0x1-0x2-0x0 [ 37.533619] wlan0: authenticate with 00:0a:79:eb:56:10 [ 37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3) [ 37.538241] wlan0: authenticated [ 37.538391] wlan0: associating with AP with corrupt beacon That might be an indication of things already going wrong with your AP ... :-( [snip log] Mostly from the log it seems that there's a lot of spurious aggregation setup/teardown, some of it seems to originate from the AP. At that point I removed the iwlwifi module, and reloaded it with 11n_disable=1 again, otherwise nothing would work at all... With the latest, I've extended 11n_disable to have more bits. 11n_disable=1 will disable HT completely 11n_disable=2 will disable TX aggregation 11n_disable=4 will disable RX aggregation It'd be interesting to see what happens for you with 11n_disable=2/4/6. johannes -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
