* Re: pull-request: iwlwifi-fixes 2013-10-18
From: John W. Linville @ 2013-10-18 17:35 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1382105527.14393.3.camel@jlt4.sipsolutions.net>
On Fri, Oct 18, 2013 at 04:12:07PM +0200, Johannes Berg wrote:
> John,
>
> Before you travel to Edinburgh, I hope to get in another pull request.
> Or maybe when you are there? :-)
>
> I have a few fixes for warnings/issues: one from Alex, fixing scan
> timings, one from Emmanuel fixing a WARN_ON in the DVM driver, one from
> Stanislaw removing a trigger-happy WARN_ON in the MVM driver and a
> change from myself to try to recover when the device isn't processing
> commands quickly.
>
> Please let me know if there's any issue.
>
> johannes
>
>
> The following changes since commit 5a3e9f7f8c8768b5f7df81100c684e4cd00a6eb5:
>
> iwlwifi: mvm: call ieee80211_scan_completed when needed (2013-10-02 11:25:50 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git for-john
>
> for you to fetch changes up to f6b129527ca15bae29ffb9417ddaa1c9d99ffc5d:
>
> iwlwifi: dvm: don't override mac80211's queue setting (2013-10-18 16:03:14 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: pull-request: mac80211 2013-10-18
From: John W. Linville @ 2013-10-18 17:36 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1382105667.14393.5.camel@jlt4.sipsolutions.net>
On Fri, Oct 18, 2013 at 04:14:27PM +0200, Johannes Berg wrote:
> John,
>
> I'm flushing out patches ... one more for mac80211.
>
> This time I have two fixes for P2P (which requires not using CCK rates)
> and a workaround for APs with broken WMM information.
>
> Let me know if there's any problem.
>
> johannes
>
>
> The following changes since commit d86aa4f8ca58898ec6a94c0635da20b948171ed7:
>
> mac80211: fix crash if bitrate calculation goes wrong (2013-10-14 09:47:08 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git for-john
>
> for you to fetch changes up to 095d81cee742fc31e1218077ca6ca8f0df07c613:
>
> mac80211: disable WMM with invalid parameters (2013-10-17 15:38:22 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: pull-request: iwlwifi-next 2013-10-18
From: John W. Linville @ 2013-10-18 17:58 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1382106086.14393.10.camel@jlt4.sipsolutions.net>
On Fri, Oct 18, 2013 at 04:21:26PM +0200, Johannes Berg wrote:
> John,
>
> And for iwlwifi-next ... This is bigger. I guess -next stuff can wait
> until after KS though. Also, I think there might be a merge conflict
> hidden here, don't really remember.
>
> For this round, I have a lot of changes:
> * power management improvements
> * BT coexistence improvements/updates
> * new device support
> * VHT support
> * IBSS support (though due to a small bug it requires new firmware)
> * various other fixes/improvements.
>
> Sorry to concentrate it all into one pull request, I was holding for a
> small bugfix that turned out to be much more difficult than I expected,
> but also not needed yet (so this code has a known bug with -8 firmware,
> but we'll fix it before the driver gets updated to use that firmware.)
>
> Let me know if there's any problem.
>
> johannes
>
>
> The following changes since commit e25aa82a89db9e3b09d02b5481aa375c7712a10d:
>
> rt2x00: rt2800lib: fix VGC adjustment for RT3572 and RT3593 (2013-10-10 13:53:07 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git for-john
>
> for you to fetch changes up to 246dd9922e859768aa522daa6c1c601785e57e0c:
>
> iwlwifi: mvm: fix operator precedence (2013-10-18 16:02:38 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: pull request: bluetooth-next 2013-10-14
From: John W. Linville @ 2013-10-18 17:56 UTC (permalink / raw)
To: Gustavo Padovan, linux-wireless, linux-bluetooth, linux-kernel
In-Reply-To: <20131014235218.GE2305@joana>
On Mon, Oct 14, 2013 at 08:52:18PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> More patches for 3.12, busy times for Bluetooth. More than a 100 commits since
> the last pull. The bulk of work comes from Johan and Marcel, they are doing
> fixes and improvements all over the Bluetooth subsystem, as the diffstat can
> show.
>
> Please pull or let me know of any problems! Thanks.
>
> Gustavo
> --
> The following changes since commit 4f3e219d95a3c31b916dcd5e2631c4e440736f79:
>
> Bluetooth: Only one command per L2CAP LE signalling is supported (2013-10-03 16:09:59 +0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next for-upstream
>
> for you to fetch changes up to 4b836f393bd8ed111857a6ee1865e44627266ec6:
>
> Bluetooth: Read current IAC LAP on controller setup (2013-10-14 19:31:18 -0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: Pull request: ath 20131017
From: John W. Linville @ 2013-10-18 17:57 UTC (permalink / raw)
To: Kalle Valo; +Cc: linux-wireless, ath10k, ath6kl-devel
In-Reply-To: <87mwm82rmu.fsf@kamboji.qca.qualcomm.com>
On Thu, Oct 17, 2013 at 12:06:33PM +0300, Kalle Valo wrote:
> Hi John,
>
> here's a pull request for ath6kl and ath10k. Notable changes:
>
> Bartosz added support to ath10k for our 10.x AP firmware branch, which
> gives us AP specific features and fixes. We still support the main
> firmware branch as well just like before, ath10k detects runtime what
> firmware is used. Unfortunately the firmware interface in 10.x branch is
> somewhat different so there was quite a lot of changes in ath10k for
> this.
>
> Michal and Sujith did some performance improvements in ath10k. Vladimir
> fixed a compiler warning and Fengguang removed an extra semicolon.
>
> Please let me know if there are any problems.
>
> Kalle
>
> The following changes since commit 6e712d427cb0542afdd5220edb6e4f4f8a5b952d:
>
> ath10k: replenish HTT RX buffers in a tasklet (2013-09-26 17:22:54 +0300)
>
> are available in the git repository at:
>
> git://github.com/kvalo/ath.git for-linville
>
> for you to fetch changes up to 56b84287d14aa74823a9c290d0c5839d38365110:
>
> ath10k: add might_sleep() to ath10k_wmi_cmd_send() (2013-10-16 15:44:47 +0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [GIT] [3.13] NFC updates
From: John W. Linville @ 2013-10-18 18:00 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: Linux Wireless, Linux NFC
In-Reply-To: <20131015161917.GF30191@zurbaran>
On Tue, Oct 15, 2013 at 06:19:17PM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the first NFC pull request for the 3.13 kernel.
>
> It's a fairly big one, with the following highlights:
>
> - NFC digital layer implementation: Most NFC chipsets implement the NFC
> digital layer in firmware, but others have more basic functionalities
> and expect the host to implement the digital layer. This layer sits
> below the NFC core.
>
> - Sony's port100 support: This is "soft" NFC USB dongle that expects the
> digital layer to be implemented on the host. This is the first user of
> our NFC digital stack implementation.
>
> - Secure element API: We now provide a netlink API for enabling,
> disabling and discovering NFC attached (embedded or UICC ones) secure
> elements. With some userspace help, this allows us to support NFC
> payments.
> Only the pn544 driver currently supports that API.
>
> - NCI SPI fixes and improvements: In order to support NCI devices over
> SPI, we fixed and improved our NCI/SPI implementation. The currently
> most deployed NFC NCI chipset, Broadcom's bcm2079x, supports that mode
> and we're planning to use our NCI/SPI framework to implement a
> driver for it.
>
> - pn533 fragmentation support in target mode: This was the only missing
> feature from our pn533 impementation. We now support fragmentation in
> both Tx and Rx modes, in target mode.
>
> The following changes since commit b75ff5e84bb6c2d43a8ec39b240c80f0543821f0:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-09-19 13:57:28 -0500)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next.git tags/nfc-next-3.13-1
>
> for you to fetch changes up to ddc1a70b5f2a07a932ed31f989d63937bb813439:
>
> NFC: Fix SE API related sparse warning (2013-10-07 14:18:44 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [PATCH 1/6] cfg80211: export reg_initiator_name()
From: John W. Linville @ 2013-10-18 18:01 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: johannes, linux-wireless
In-Reply-To: <1381797731-2454-2-git-send-email-mcgrof@do-not-panic.com>
I'm going to merge this series, including the cfg80211.h change...FYI!
On Mon, Oct 14, 2013 at 05:42:06PM -0700, Luis R. Rodriguez wrote:
> Drivers can now use this to parse the regulatory request and
> be more verbose when needed.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
> ---
> include/net/cfg80211.h | 9 +++++++++
> net/wireless/reg.c | 27 +++++++++++++++++----------
> 2 files changed, 26 insertions(+), 10 deletions(-)
>
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 45f6bf5..419202c 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -3483,6 +3483,15 @@ void wiphy_apply_custom_regulatory(struct wiphy *wiphy,
> const struct ieee80211_reg_rule *freq_reg_info(struct wiphy *wiphy,
> u32 center_freq);
>
> +/**
> + * reg_initiator_name - map regulatory request initiator enum to name
> + * @initiator: the regulatory request initiator
> + *
> + * You can use this to map the regulatory request initiator enum to a
> + * proper string representation.
> + */
> +const char *reg_initiator_name(enum nl80211_reg_initiator initiator);
> +
> /*
> * callbacks for asynchronous cfg80211 methods, notification
> * functions and BSS handling helpers
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index edb2ba4e..9851a2b 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -768,23 +768,25 @@ const struct ieee80211_reg_rule *freq_reg_info(struct wiphy *wiphy,
> }
> EXPORT_SYMBOL(freq_reg_info);
>
> -#ifdef CONFIG_CFG80211_REG_DEBUG
> -static const char *reg_initiator_name(enum nl80211_reg_initiator initiator)
> +const char *reg_initiator_name(enum nl80211_reg_initiator initiator)
> {
> switch (initiator) {
> case NL80211_REGDOM_SET_BY_CORE:
> - return "Set by core";
> + return "core";
> case NL80211_REGDOM_SET_BY_USER:
> - return "Set by user";
> + return "user";
> case NL80211_REGDOM_SET_BY_DRIVER:
> - return "Set by driver";
> + return "driver";
> case NL80211_REGDOM_SET_BY_COUNTRY_IE:
> - return "Set by country IE";
> + return "country IE";
> default:
> WARN_ON(1);
> - return "Set by bug";
> + return "bug";
> }
> }
> +EXPORT_SYMBOL(reg_initiator_name);
> +
> +#ifdef CONFIG_CFG80211_REG_DEBUG
>
> static void chan_reg_rule_print_dbg(struct ieee80211_channel *chan,
> const struct ieee80211_reg_rule *reg_rule)
> @@ -986,14 +988,17 @@ static bool ignore_reg_update(struct wiphy *wiphy,
> struct regulatory_request *lr = get_last_request();
>
> if (!lr) {
> - REG_DBG_PRINT("Ignoring regulatory request %s since last_request is not set\n",
> + REG_DBG_PRINT("Ignoring regulatory request set by %s "
> + "since last_request is not set\n",
> reg_initiator_name(initiator));
> return true;
> }
>
> if (initiator == NL80211_REGDOM_SET_BY_CORE &&
> wiphy->flags & WIPHY_FLAG_CUSTOM_REGULATORY) {
> - REG_DBG_PRINT("Ignoring regulatory request %s since the driver uses its own custom regulatory domain\n",
> + REG_DBG_PRINT("Ignoring regulatory request set by %s "
> + "since the driver uses its own custom "
> + "regulatory domain\n",
> reg_initiator_name(initiator));
> return true;
> }
> @@ -1005,7 +1010,9 @@ static bool ignore_reg_update(struct wiphy *wiphy,
> if (wiphy_strict_alpha2_regd(wiphy) && !wiphy->regd &&
> initiator != NL80211_REGDOM_SET_BY_COUNTRY_IE &&
> !is_world_regdom(lr->alpha2)) {
> - REG_DBG_PRINT("Ignoring regulatory request %s since the driver requires its own regulatory domain to be set first\n",
> + REG_DBG_PRINT("Ignoring regulatory request set by %s "
> + "since the driver requires its own regulatory "
> + "domain to be set first\n",
> reg_initiator_name(initiator));
> return true;
> }
> --
> 1.8.4.rc3
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [PATCH 1/6] cfg80211: export reg_initiator_name()
From: Johannes Berg @ 2013-10-18 18:21 UTC (permalink / raw)
To: John W. Linville; +Cc: Luis R. Rodriguez, linux-wireless
In-Reply-To: <20131018180107.GG28130@tuxdriver.com>
On Fri, 2013-10-18 at 14:01 -0400, John W. Linville wrote:
> I'm going to merge this series, including the cfg80211.h change...FYI!
I already have this patch though, hmm.
johannes
^ permalink raw reply
* bug
From: squadrato @ 2013-10-18 18:53 UTC (permalink / raw)
To: linux-wireless
Hello i own a Fujitsu ah512 laptop. As described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159690
I cannot switch the wireless with fn + f5, even in the last ubuntu version,
released yesterday.
grretings
^ permalink raw reply
* [PATCH] mac80211: fix uninitialized variable
From: Michal Kazior @ 2013-10-18 21:57 UTC (permalink / raw)
To: johannes; +Cc: linux-wireless, Michal Kazior
CSA completion could call in a driver
bss_info_changed() with a garbled `changed` flag
leading to all sorts of problems.
Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
---
net/mac80211/cfg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c
index 629dee7..fd1f6d1 100644
--- a/net/mac80211/cfg.c
+++ b/net/mac80211/cfg.c
@@ -2860,7 +2860,7 @@ void ieee80211_csa_finalize_work(struct work_struct *work)
container_of(work, struct ieee80211_sub_if_data,
csa_finalize_work);
struct ieee80211_local *local = sdata->local;
- int err, changed;
+ int err, changed = 0;
if (!ieee80211_sdata_running(sdata))
return;
--
1.8.4.rc3
^ permalink raw reply related
* [PATCH 1/1] drivers: net: wireless: rtlwifi: Fix wrong assignment
From: Felipe Pena @ 2013-10-18 22:15 UTC (permalink / raw)
To: Larry Finger, Chaoming Li, John W. Linville
Cc: linux-wireless, netdev, linux-kernel, Felipe Pena
There is a typo in the struct member name on assignment when checking
rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
for bound limit and uses pwrgroup_ht20 when assigning instead.
Signed-off-by: Felipe Pena <felipensp@gmail.com>
---
drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
index 5061f1d..92d38ab 100644
--- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
+++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
@@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
rtlefuse->pwrgroup_ht40
[RF90_PATH_A][chnl - 1]) {
pwrdiff_limit[i] =
- rtlefuse->pwrgroup_ht20
+ rtlefuse->pwrgroup_ht40
[RF90_PATH_A][chnl - 1];
}
} else {
--
1.7.10.4
^ permalink raw reply related
* Re: [PATCH 1/1] drivers: net: wireless: rtlwifi: Fix wrong assignment
From: Larry Finger @ 2013-10-18 22:27 UTC (permalink / raw)
To: Felipe Pena, Chaoming Li, John W. Linville
Cc: linux-wireless, netdev, linux-kernel
In-Reply-To: <1382134538-3719-1-git-send-email-felipensp@gmail.com>
On 10/18/2013 05:15 PM, Felipe Pena wrote:
> There is a typo in the struct member name on assignment when checking
> rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
> for bound limit and uses pwrgroup_ht20 when assigning instead.
>
> Signed-off-by: Felipe Pena <felipensp@gmail.com>
> ---
> drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> index 5061f1d..92d38ab 100644
> --- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> +++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> @@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
> rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1]) {
> pwrdiff_limit[i] =
> - rtlefuse->pwrgroup_ht20
> + rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1];
> }
> } else {
Good catch. There is only one problem - by convention we skip
drivers/net/wireless in the subject. That would probably be OK, but you are
missing the rtl8192se part, which needs to be there. I suggest that you use the
subject "rtlwifi: rtl8192de: Fix wrong assignment".
Larry
^ permalink raw reply
* Re: [PATCH 1/1] drivers: net: wireless: rtlwifi: Fix wrong assignment
From: Felipe Pena @ 2013-10-18 22:43 UTC (permalink / raw)
To: Larry Finger
Cc: Chaoming Li, John W. Linville, linux-wireless, netdev,
linux-kernel
In-Reply-To: <5261B5D6.2020002@lwfinger.net>
On Fri, Oct 18, 2013 at 7:27 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> On 10/18/2013 05:15 PM, Felipe Pena wrote:
>>
>> There is a typo in the struct member name on assignment when checking
>> rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses
>> pwrgroup_ht40
>> for bound limit and uses pwrgroup_ht20 when assigning instead.
>>
>> Signed-off-by: Felipe Pena <felipensp@gmail.com>
>> ---
>> drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> index 5061f1d..92d38ab 100644
>> --- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> +++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> @@ -265,7 +265,7 @@ static void
>> _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
>> rtlefuse->pwrgroup_ht40
>> [RF90_PATH_A][chnl - 1]) {
>> pwrdiff_limit[i] =
>> - rtlefuse->pwrgroup_ht20
>> + rtlefuse->pwrgroup_ht40
>> [RF90_PATH_A][chnl - 1];
>> }
>> } else {
>
>
> Good catch. There is only one problem - by convention we skip
> drivers/net/wireless in the subject. That would probably be OK, but you are
> missing the rtl8192se part, which needs to be there. I suggest that you use
> the subject "rtlwifi: rtl8192de: Fix wrong assignment".
>
> Larry
>
>
Thanks for the reply. I'll re-send it with the suggested subject.
--
Regards,
Felipe Pena
^ permalink raw reply
* [PATCH] wireless: rt2800lib: Fix typo on checking
From: Felipe Pena @ 2013-10-19 0:20 UTC (permalink / raw)
To: Ivo van Doorn, Gertjan van Wingerde, Helmut Schaa,
John W. Linville
Cc: linux-wireless, users, netdev, linux-kernel, Felipe Pena
On rt2800_config_channel_rf53xx function the member default_power1 is checked
for bound limit, but default_power2 is used instead.
Signed-off-by: Felipe Pena <felipensp@gmail.com>
---
drivers/net/wireless/rt2x00/rt2800lib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
index 88ce656..1c2ce93 100644
--- a/drivers/net/wireless/rt2x00/rt2800lib.c
+++ b/drivers/net/wireless/rt2x00/rt2800lib.c
@@ -2650,7 +2650,7 @@ static void rt2800_config_channel_rf53xx(struct rt2x00_dev *rt2x00dev,
if (rt2x00_rt(rt2x00dev, RT5392)) {
rt2800_rfcsr_read(rt2x00dev, 50, &rfcsr);
- if (info->default_power1 > POWER_BOUND)
+ if (info->default_power2 > POWER_BOUND)
rt2x00_set_field8(&rfcsr, RFCSR50_TX, POWER_BOUND);
else
rt2x00_set_field8(&rfcsr, RFCSR50_TX,
--
1.7.10.4
^ permalink raw reply related
* [PATCH] rtlwifi: rtl8192se: Fix wrong assignment
From: Felipe Pena @ 2013-10-19 0:52 UTC (permalink / raw)
To: Larry Finger, Chaoming Li, John W. Linville
Cc: linux-wireless, netdev, linux-kernel, Felipe Pena
There is a typo in the struct member name on assignment when checking
rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
for bound limit and uses pwrgroup_ht20 when assigning instead.
Signed-off-by: Felipe Pena <felipensp@gmail.com>
---
drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
index 5061f1d..92d38ab 100644
--- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
+++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
@@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
rtlefuse->pwrgroup_ht40
[RF90_PATH_A][chnl - 1]) {
pwrdiff_limit[i] =
- rtlefuse->pwrgroup_ht20
+ rtlefuse->pwrgroup_ht40
[RF90_PATH_A][chnl - 1];
}
} else {
--
1.7.10.4
^ permalink raw reply related
* Re: [PATCH] rtlwifi: rtl8192se: Fix wrong assignment
From: Joe Perches @ 2013-10-19 1:05 UTC (permalink / raw)
To: Felipe Pena
Cc: Larry Finger, Chaoming Li, John W. Linville, linux-wireless,
netdev, linux-kernel
In-Reply-To: <1382143960-4594-1-git-send-email-felipensp@gmail.com>
On Fri, 2013-10-18 at 21:52 -0300, Felipe Pena wrote:
> There is a typo in the struct member name on assignment when checking
> rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
> for bound limit and uses pwrgroup_ht20 when assigning instead.
>
> Signed-off-by: Felipe Pena <felipensp@gmail.com>
> ---
> drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> index 5061f1d..92d38ab 100644
> --- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> +++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> @@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
> rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1]) {
> pwrdiff_limit[i] =
> - rtlefuse->pwrgroup_ht20
> + rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1];
> }
Using min could help minimize typos
pwrdiff_limit[i] = min(pwrdiff_limit[i],
rtlefuse->pwrgroup_ht40[RF90_PATH_A][chnl - 1]);
^ permalink raw reply
* Re: [PATCH] rtlwifi: rtl8192se: Fix wrong assignment
From: Larry Finger @ 2013-10-19 1:33 UTC (permalink / raw)
To: Joe Perches, Felipe Pena
Cc: Chaoming Li, John W. Linville, linux-wireless, netdev,
linux-kernel
In-Reply-To: <1382144748.2041.16.camel@joe-AO722>
On 10/18/2013 08:05 PM, Joe Perches wrote:
> On Fri, 2013-10-18 at 21:52 -0300, Felipe Pena wrote:
>> There is a typo in the struct member name on assignment when checking
>> rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
>> for bound limit and uses pwrgroup_ht20 when assigning instead.
>>
>> Signed-off-by: Felipe Pena <felipensp@gmail.com>
>> ---
>> drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> index 5061f1d..92d38ab 100644
>> --- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> +++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
>> @@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
>> rtlefuse->pwrgroup_ht40
>> [RF90_PATH_A][chnl - 1]) {
>> pwrdiff_limit[i] =
>> - rtlefuse->pwrgroup_ht20
>> + rtlefuse->pwrgroup_ht40
>> [RF90_PATH_A][chnl - 1];
>> }
>
> Using min could help minimize typos
>
> pwrdiff_limit[i] = min(pwrdiff_limit[i],
> rtlefuse->pwrgroup_ht40[RF90_PATH_A][chnl - 1]);
In the initial driver, that would have been true; however, at this point, I
prefer the patch as submitted. There is less churning of the source.
Larry
^ permalink raw reply
* Re: [PATCH] rtlwifi: rtl8192se: Fix wrong assignment
From: Larry Finger @ 2013-10-19 1:35 UTC (permalink / raw)
To: Felipe Pena, Chaoming Li, John W. Linville
Cc: linux-wireless, netdev, linux-kernel
In-Reply-To: <1382143960-4594-1-git-send-email-felipensp@gmail.com>
On 10/18/2013 07:52 PM, Felipe Pena wrote:
> There is a typo in the struct member name on assignment when checking
> rtlphy->current_chan_bw == HT_CHANNEL_WIDTH_20_40, the check uses pwrgroup_ht40
> for bound limit and uses pwrgroup_ht20 when assigning instead.
>
> Signed-off-by: Felipe Pena <felipensp@gmail.com>
> ---
> drivers/net/wireless/rtlwifi/rtl8192se/rf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> index 5061f1d..92d38ab 100644
> --- a/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> +++ b/drivers/net/wireless/rtlwifi/rtl8192se/rf.c
> @@ -265,7 +265,7 @@ static void _rtl92s_get_txpower_writeval_byregulatory(struct ieee80211_hw *hw,
> rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1]) {
> pwrdiff_limit[i] =
> - rtlefuse->pwrgroup_ht20
> + rtlefuse->pwrgroup_ht40
> [RF90_PATH_A][chnl - 1];
> }
> } else {
> --
Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
John: I forgot to mention this earlier, but when you add your s-o-b, please add
a Cc for Stable [3.0 +].
Thanks,
Larry
^ permalink raw reply
* Log added
From: Mark Wu @ 2013-10-19 6:02 UTC (permalink / raw)
To: linux-wireless
I'm added log on bug tracker:
https://bugzilla.kernel.org/show_bug.cgi?id=63221
^ permalink raw reply
* Fwd: iwlwifi issues with Ultimate 6300-N card in laptop
From: Michael Saunders @ 2013-10-19 8:15 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <CAPnY58pLZNQ4=V92upcaOGVwvNryyPZ7sV6WwB3_6LrzCWx5NA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3146 bytes --]
This was rejected due to not being text/plain content. I've forwarded
the original and changed the content to text/plain.
Also, I should have mentioned in the original- thank you for taking
the time to read this e-mail.
Cheers,
Michael
---------- Forwarded message ----------
From: Michael Saunders <mick.saunders@gmail.com>
Date: Sat, Oct 19, 2013 at 5:42 PM
Subject: iwlwifi issues with Ultimate 6300-N card in laptop
To: ilw@linux.intel.com, linux-wireless@vger.kernel.org
Hi,
Firstly apologies for e-mailing this, but I'm unsure where to report
this now as the bugzilla.intellinuxwireless appears to be offline.
I've been experiencing wireless issues with my laptop that runs an
Intel Ultimate 6300-N card with the iwlwifi drivers for a couple of
years now. I'd seen numerous bug reports on many different
distributions incl. bugzilla for kernel.org reporting similar issues,
but not always exactly the same type of issue as mine and was always
hopeful that a fix would be forthcoming.
The issue:
I experience occasional packet loss and extremely poor latency when
doing any activity over my wireless network. I experience this no
matter which AP I am connected to, and I have tried various iwlwifi
module options (11n_disable=1 or 2) and these can improve the
situation but are not a solution.
I've attached a few log files that help detail my setup, and show some
of the errors found in dmesg during transfers and also a log of
latency results of a ping to a system on my local network (e.g. I'd
expect replies around the 1-2ms mark, not up to 12000ms like I
occasionally have)
I run ArchLinux, and have done for a couple of years, and I'm almost
certain I've had wireless issues since install around when the kernel
3.0 series began.
Logfiles attached:
ping.log -- shows the extremely poor latencies I get when doing
transfers over wireless
lsmod.log -- lsmod of drivers running
dmesg.out.log -- errors seen in dmesg during the wireless transfers
iwlwifi.firmware.1.log -- ls of /lib/firmware/ directory to show
version of firmware
iwlwifi.firmware.2.md5s.log -- md5s of said firmware
lshw.log -- sudo lshw to detail hardware
date.log -- just the date this was all done (to ascertain approximate
package versions if needed due to rolling nature of ArchLinux)
uname.log -- current kernel version.
modinfo.iwlwifi.log -- iwlwifi info
modinfo.iwldvm.log -- iwldvm info
iwconfig.out -- iwconfig output showing large TX excessive retries and
invalid misc
I'm disappointed in how long this card has had issues under Linux, and
it reflects poorly on Intel products and their driver support in
Linux. As it is, this product is faulty when used under linux, even
though it is stated as being supported by Intel.
I would really like to obtain a fix for this. If I can assist in any
way (running custom firmware/kernels/drivers, providing more info,
perhaps step-by-step explanations for debugging, or even potentially
providing SSH access to a liveCD instance running on this system) then
please let me know.
If there's an official intel wireless bugzilla somewhere, please point
me at it if I need to log this there.
Regards.
Michael
[-- Attachment #2: ping.log --]
[-- Type: application/octet-stream, Size: 8842 bytes --]
## ping while at the same time doing downloads from remote server with:
# ssh msaun@192.168.4.1 'dd if=/dev/zero | cat - ' | cat - >/dev/null
[msaun@neptune Downloads]$ ping 192.168.4.1
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
64 bytes from 192.168.4.1: icmp_seq=1 ttl=64 time=102 ms
64 bytes from 192.168.4.1: icmp_seq=2 ttl=64 time=1957 ms
64 bytes from 192.168.4.1: icmp_seq=3 ttl=64 time=957 ms
64 bytes from 192.168.4.1: icmp_seq=4 ttl=64 time=2060 ms
64 bytes from 192.168.4.1: icmp_seq=5 ttl=64 time=1059 ms
64 bytes from 192.168.4.1: icmp_seq=6 ttl=64 time=106 ms
64 bytes from 192.168.4.1: icmp_seq=7 ttl=64 time=599 ms
64 bytes from 192.168.4.1: icmp_seq=8 ttl=64 time=672 ms
64 bytes from 192.168.4.1: icmp_seq=9 ttl=64 time=614 ms
64 bytes from 192.168.4.1: icmp_seq=10 ttl=64 time=8158 ms
64 bytes from 192.168.4.1: icmp_seq=11 ttl=64 time=7149 ms
64 bytes from 192.168.4.1: icmp_seq=12 ttl=64 time=6149 ms
64 bytes from 192.168.4.1: icmp_seq=13 ttl=64 time=5149 ms
64 bytes from 192.168.4.1: icmp_seq=14 ttl=64 time=4149 ms
64 bytes from 192.168.4.1: icmp_seq=15 ttl=64 time=3149 ms
64 bytes from 192.168.4.1: icmp_seq=16 ttl=64 time=2149 ms
64 bytes from 192.168.4.1: icmp_seq=17 ttl=64 time=1149 ms
64 bytes from 192.168.4.1: icmp_seq=18 ttl=64 time=2548 ms
64 bytes from 192.168.4.1: icmp_seq=19 ttl=64 time=1651 ms
64 bytes from 192.168.4.1: icmp_seq=20 ttl=64 time=643 ms
64 bytes from 192.168.4.1: icmp_seq=21 ttl=64 time=307 ms
64 bytes from 192.168.4.1: icmp_seq=22 ttl=64 time=124 ms
64 bytes from 192.168.4.1: icmp_seq=23 ttl=64 time=217 ms
64 bytes from 192.168.4.1: icmp_seq=24 ttl=64 time=81.0 ms
64 bytes from 192.168.4.1: icmp_seq=25 ttl=64 time=30.3 ms
64 bytes from 192.168.4.1: icmp_seq=26 ttl=64 time=8911 ms
64 bytes from 192.168.4.1: icmp_seq=27 ttl=64 time=7912 ms
64 bytes from 192.168.4.1: icmp_seq=28 ttl=64 time=6912 ms
64 bytes from 192.168.4.1: icmp_seq=29 ttl=64 time=5912 ms
64 bytes from 192.168.4.1: icmp_seq=30 ttl=64 time=4912 ms
64 bytes from 192.168.4.1: icmp_seq=31 ttl=64 time=3912 ms
64 bytes from 192.168.4.1: icmp_seq=32 ttl=64 time=2912 ms
64 bytes from 192.168.4.1: icmp_seq=33 ttl=64 time=1912 ms
64 bytes from 192.168.4.1: icmp_seq=34 ttl=64 time=912 ms
64 bytes from 192.168.4.1: icmp_seq=35 ttl=64 time=3394 ms
64 bytes from 192.168.4.1: icmp_seq=36 ttl=64 time=2781 ms
64 bytes from 192.168.4.1: icmp_seq=37 ttl=64 time=1781 ms
64 bytes from 192.168.4.1: icmp_seq=38 ttl=64 time=781 ms
64 bytes from 192.168.4.1: icmp_seq=39 ttl=64 time=71.1 ms
64 bytes from 192.168.4.1: icmp_seq=40 ttl=64 time=702 ms
64 bytes from 192.168.4.1: icmp_seq=41 ttl=64 time=261 ms
64 bytes from 192.168.4.1: icmp_seq=42 ttl=64 time=12466 ms
64 bytes from 192.168.4.1: icmp_seq=43 ttl=64 time=11848 ms
64 bytes from 192.168.4.1: icmp_seq=44 ttl=64 time=10848 ms
64 bytes from 192.168.4.1: icmp_seq=45 ttl=64 time=9848 ms
64 bytes from 192.168.4.1: icmp_seq=46 ttl=64 time=8848 ms
64 bytes from 192.168.4.1: icmp_seq=47 ttl=64 time=7848 ms
64 bytes from 192.168.4.1: icmp_seq=48 ttl=64 time=6848 ms
64 bytes from 192.168.4.1: icmp_seq=49 ttl=64 time=5848 ms
64 bytes from 192.168.4.1: icmp_seq=50 ttl=64 time=4848 ms
64 bytes from 192.168.4.1: icmp_seq=51 ttl=64 time=3848 ms
64 bytes from 192.168.4.1: icmp_seq=52 ttl=64 time=2848 ms
64 bytes from 192.168.4.1: icmp_seq=53 ttl=64 time=1848 ms
64 bytes from 192.168.4.1: icmp_seq=54 ttl=64 time=1079 ms
64 bytes from 192.168.4.1: icmp_seq=55 ttl=64 time=79.5 ms
64 bytes from 192.168.4.1: icmp_seq=56 ttl=64 time=61.4 ms
64 bytes from 192.168.4.1: icmp_seq=57 ttl=64 time=115 ms
64 bytes from 192.168.4.1: icmp_seq=58 ttl=64 time=165 ms
64 bytes from 192.168.4.1: icmp_seq=59 ttl=64 time=3587 ms
64 bytes from 192.168.4.1: icmp_seq=60 ttl=64 time=2579 ms
64 bytes from 192.168.4.1: icmp_seq=61 ttl=64 time=1580 ms
64 bytes from 192.168.4.1: icmp_seq=62 ttl=64 time=580 ms
64 bytes from 192.168.4.1: icmp_seq=63 ttl=64 time=71.8 ms
64 bytes from 192.168.4.1: icmp_seq=64 ttl=64 time=52.5 ms
64 bytes from 192.168.4.1: icmp_seq=65 ttl=64 time=4418 ms
64 bytes from 192.168.4.1: icmp_seq=66 ttl=64 time=3420 ms
64 bytes from 192.168.4.1: icmp_seq=67 ttl=64 time=2746 ms
64 bytes from 192.168.4.1: icmp_seq=68 ttl=64 time=1748 ms
64 bytes from 192.168.4.1: icmp_seq=69 ttl=64 time=758 ms
64 bytes from 192.168.4.1: icmp_seq=70 ttl=64 time=305 ms
64 bytes from 192.168.4.1: icmp_seq=71 ttl=64 time=182 ms
64 bytes from 192.168.4.1: icmp_seq=72 ttl=64 time=4232 ms
64 bytes from 192.168.4.1: icmp_seq=73 ttl=64 time=3708 ms
64 bytes from 192.168.4.1: icmp_seq=74 ttl=64 time=2868 ms
64 bytes from 192.168.4.1: icmp_seq=75 ttl=64 time=1878 ms
64 bytes from 192.168.4.1: icmp_seq=76 ttl=64 time=893 ms
64 bytes from 192.168.4.1: icmp_seq=77 ttl=64 time=600 ms
64 bytes from 192.168.4.1: icmp_seq=78 ttl=64 time=196 ms
64 bytes from 192.168.4.1: icmp_seq=80 ttl=64 time=5385 ms
64 bytes from 192.168.4.1: icmp_seq=81 ttl=64 time=4411 ms
64 bytes from 192.168.4.1: icmp_seq=82 ttl=64 time=3412 ms
64 bytes from 192.168.4.1: icmp_seq=83 ttl=64 time=2584 ms
64 bytes from 192.168.4.1: icmp_seq=84 ttl=64 time=1621 ms
64 bytes from 192.168.4.1: icmp_seq=85 ttl=64 time=622 ms
64 bytes from 192.168.4.1: icmp_seq=86 ttl=64 time=184 ms
64 bytes from 192.168.4.1: icmp_seq=87 ttl=64 time=393 ms
64 bytes from 192.168.4.1: icmp_seq=88 ttl=64 time=5411 ms
64 bytes from 192.168.4.1: icmp_seq=89 ttl=64 time=5230 ms
64 bytes from 192.168.4.1: icmp_seq=90 ttl=64 time=4882 ms
64 bytes from 192.168.4.1: icmp_seq=91 ttl=64 time=3915 ms
64 bytes from 192.168.4.1: icmp_seq=92 ttl=64 time=2916 ms
64 bytes from 192.168.4.1: icmp_seq=93 ttl=64 time=1916 ms
64 bytes from 192.168.4.1: icmp_seq=94 ttl=64 time=945 ms
64 bytes from 192.168.4.1: icmp_seq=95 ttl=64 time=178 ms
64 bytes from 192.168.4.1: icmp_seq=96 ttl=64 time=320 ms
64 bytes from 192.168.4.1: icmp_seq=97 ttl=64 time=6433 ms
64 bytes from 192.168.4.1: icmp_seq=98 ttl=64 time=5569 ms
64 bytes from 192.168.4.1: icmp_seq=99 ttl=64 time=4757 ms
64 bytes from 192.168.4.1: icmp_seq=100 ttl=64 time=3757 ms
64 bytes from 192.168.4.1: icmp_seq=101 ttl=64 time=2757 ms
64 bytes from 192.168.4.1: icmp_seq=102 ttl=64 time=1757 ms
64 bytes from 192.168.4.1: icmp_seq=103 ttl=64 time=757 ms
64 bytes from 192.168.4.1: icmp_seq=104 ttl=64 time=141 ms
64 bytes from 192.168.4.1: icmp_seq=105 ttl=64 time=115 ms
64 bytes from 192.168.4.1: icmp_seq=106 ttl=64 time=2393 ms
64 bytes from 192.168.4.1: icmp_seq=107 ttl=64 time=1395 ms
64 bytes from 192.168.4.1: icmp_seq=108 ttl=64 time=395 ms
64 bytes from 192.168.4.1: icmp_seq=109 ttl=64 time=482 ms
64 bytes from 192.168.4.1: icmp_seq=110 ttl=64 time=375 ms
64 bytes from 192.168.4.1: icmp_seq=111 ttl=64 time=140 ms
64 bytes from 192.168.4.1: icmp_seq=112 ttl=64 time=220 ms
64 bytes from 192.168.4.1: icmp_seq=113 ttl=64 time=1365 ms
64 bytes from 192.168.4.1: icmp_seq=114 ttl=64 time=356 ms
64 bytes from 192.168.4.1: icmp_seq=115 ttl=64 time=138 ms
64 bytes from 192.168.4.1: icmp_seq=116 ttl=64 time=66.2 ms
64 bytes from 192.168.4.1: icmp_seq=117 ttl=64 time=99.7 ms
64 bytes from 192.168.4.1: icmp_seq=118 ttl=64 time=151 ms
64 bytes from 192.168.4.1: icmp_seq=119 ttl=64 time=1661 ms
64 bytes from 192.168.4.1: icmp_seq=120 ttl=64 time=652 ms
64 bytes from 192.168.4.1: icmp_seq=121 ttl=64 time=125 ms
64 bytes from 192.168.4.1: icmp_seq=122 ttl=64 time=163 ms
64 bytes from 192.168.4.1: icmp_seq=123 ttl=64 time=256 ms
64 bytes from 192.168.4.1: icmp_seq=124 ttl=64 time=137 ms
64 bytes from 192.168.4.1: icmp_seq=125 ttl=64 time=1712 ms
64 bytes from 192.168.4.1: icmp_seq=126 ttl=64 time=705 ms
64 bytes from 192.168.4.1: icmp_seq=127 ttl=64 time=2090 ms
64 bytes from 192.168.4.1: icmp_seq=128 ttl=64 time=1090 ms
64 bytes from 192.168.4.1: icmp_seq=129 ttl=64 time=165 ms
64 bytes from 192.168.4.1: icmp_seq=130 ttl=64 time=167 ms
64 bytes from 192.168.4.1: icmp_seq=131 ttl=64 time=594 ms
64 bytes from 192.168.4.1: icmp_seq=132 ttl=64 time=326 ms
64 bytes from 192.168.4.1: icmp_seq=133 ttl=64 time=5552 ms
64 bytes from 192.168.4.1: icmp_seq=134 ttl=64 time=4582 ms
64 bytes from 192.168.4.1: icmp_seq=135 ttl=64 time=3582 ms
64 bytes from 192.168.4.1: icmp_seq=136 ttl=64 time=2582 ms
64 bytes from 192.168.4.1: icmp_seq=137 ttl=64 time=1583 ms
64 bytes from 192.168.4.1: icmp_seq=138 ttl=64 time=582 ms
64 bytes from 192.168.4.1: icmp_seq=139 ttl=64 time=9.50 ms
64 bytes from 192.168.4.1: icmp_seq=140 ttl=64 time=3.64 ms
64 bytes from 192.168.4.1: icmp_seq=141 ttl=64 time=3.24 ms
64 bytes from 192.168.4.1: icmp_seq=142 ttl=64 time=3.23 ms
64 bytes from 192.168.4.1: icmp_seq=143 ttl=64 time=6.00 ms
64 bytes from 192.168.4.1: icmp_seq=144 ttl=64 time=4.32 ms
^C
--- 192.168.4.1 ping statistics ---
144 packets transmitted, 143 received, 0% packet loss, time 144162ms
rtt min/avg/max/mdev = 3.237/2356.317/12466.972/2686.351 ms, pipe 12
[-- Attachment #3: lsmod.log --]
[-- Type: application/octet-stream, Size: 4141 bytes --]
Module Size Used by
iwldvm 172354 0
iwlwifi 137145 1 iwldvm
fuse 74829 5
x86_pkg_temp_thermal 6959 0
intel_powerclamp 8642 0
btrfs 784577 1
coretemp 6326 0
kvm_intel 129393 0
uvcvideo 72804 0
kvm 379255 1 kvm_intel
videobuf2_vmalloc 3272 1 uvcvideo
raid6_pq 91142 1 btrfs
libcrc32c 1002 1 btrfs
videobuf2_memops 2335 1 videobuf2_vmalloc
zlib_deflate 20476 1 btrfs
xor 11824 1 btrfs
videobuf2_core 27797 1 uvcvideo
crc32_pclmul 3019 0
crc32c_intel 14249 1
ghash_clmulni_intel 4501 0
aesni_intel 46124 1
aes_x86_64 7399 1 aesni_intel
nvidia 9323793 51
videodev 110188 2 uvcvideo,videobuf2_core
media 11591 2 uvcvideo,videodev
lrw 3565 1 aesni_intel
snd_hda_codec_hdmi 30616 4
gf128mul 5858 1 lrw
arc4 2000 2
glue_helper 4609 1 aesni_intel
mac80211 453784 1 iwldvm
snd_hda_codec_realtek 37032 1
ablk_helper 1972 1 aesni_intel
cryptd 8473 3 ghash_clmulni_intel,aesni_intel,ablk_helper
snd_hda_intel 36520 4
snd_hda_codec 148129 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6332 1 snd_hda_codec
joydev 9663 0
iTCO_wdt 5407 0
cfg80211 402729 3 iwlwifi,mac80211,iwldvm
iTCO_vendor_support 1929 1 iTCO_wdt
snd_pcm 77765 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
evdev 10693 13
drm 236092 2 nvidia
jme 35657 0
snd_page_alloc 7234 2 snd_pcm,snd_hda_intel
snd_timer 18718 1 snd_pcm
snd 59141 15 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
rfkill 15698 2 cfg80211
soundcore 5450 1 snd
mii 4027 1 jme
mei_me 9296 0
jmb38x_ms 11240 0
memstick 7440 1 jmb38x_ms
mei 62003 1 mei_me
psmouse 85356 0
i2c_i801 11269 0
wmi 8347 0
lpc_ich 13112 0
serio_raw 5041 0
shpchp 25457 0
i2c_core 23720 4 drm,i2c_i801,nvidia,videodev
thermal 8620 0
battery 6925 0
ac 3324 0
video 11380 0
button 4669 0
mperf 1267 0
pcspkr 2027 0
microcode 15024 0
processor 25077 0
vboxnetadp 18355 0
vboxnetflt 17612 0
vboxdrv 1823232 2 vboxnetadp,vboxnetflt
nfs 145226 0
lockd 76942 1 nfs
sunrpc 221106 2 nfs,lockd
fscache 46003 1 nfs
vhba 10616 0
ext4 470156 3
crc16 1359 1 ext4
mbcache 5866 1 ext4
jbd2 83376 1 ext4
sr_mod 14898 0
sd_mod 30739 4
cdrom 34848 1 sr_mod
ahci 22888 3
libahci 21393 1 ahci
libata 171318 2 ahci,libahci
ehci_pci 4120 0
firewire_ohci 31869 0
sdhci_pci 12138 0
xhci_hcd 91389 0
ehci_hcd 48084 1 ehci_pci
scsi_mod 128695 4 vhba,libata,sd_mod,sr_mod
sdhci 29076 1 sdhci_pci
firewire_core 52227 1 firewire_ohci
crc_itu_t 1363 1 firewire_core
mmc_core 95506 2 sdhci,sdhci_pci
usbcore 178119 4 uvcvideo,ehci_hcd,ehci_pci,xhci_hcd
usb_common 1648 1 usbcore
dm_mod 72673 12
[-- Attachment #4: dmesg.out.log --]
[-- Type: application/octet-stream, Size: 3778 bytes --]
[ 208.572956] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
[ 208.579618] iwlwifi 0000:04:00.0: Radio type=0x0-0x3-0x1
[ 208.672142] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 215.075452] wlan0: authenticate with 10:0d:7f:74:f6:c3
[ 215.135774] wlan0: send auth to 10:0d:7f:74:f6:c3 (try 1/3)
[ 215.140245] wlan0: authenticated
[ 215.141107] wlan0: associate with 10:0d:7f:74:f6:c3 (try 1/3)
[ 215.173852] wlan0: associate with 10:0d:7f:74:f6:c3 (try 2/3)
[ 215.177554] wlan0: RX AssocResp from 10:0d:7f:74:f6:c3 (capab=0x411 status=0 aid=4)
[ 215.185088] wlan0: associated
[ 215.185152] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1609.768495] iwlwifi 0000:04:00.0: fail to flush all tx fifo queues Q 2
[ 1609.768506] iwlwifi 0000:04:00.0: Current SW read_ptr 160 write_ptr 164
[ 1609.768558] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 1609.768595] iwlwifi 0000:04:00.0: FH TRBs(0) = 0x00000000
[ 1609.768631] iwlwifi 0000:04:00.0: FH TRBs(1) = 0xc010b084
[ 1609.768668] iwlwifi 0000:04:00.0: FH TRBs(2) = 0x00000000
[ 1609.768704] iwlwifi 0000:04:00.0: FH TRBs(3) = 0x8030001a
[ 1609.768741] iwlwifi 0000:04:00.0: FH TRBs(4) = 0x00000000
[ 1609.768777] iwlwifi 0000:04:00.0: FH TRBs(5) = 0x00000000
[ 1609.768814] iwlwifi 0000:04:00.0: FH TRBs(6) = 0x00000000
[ 1609.768851] iwlwifi 0000:04:00.0: FH TRBs(7) = 0x00704076
[ 1609.768930] iwlwifi 0000:04:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [27,27]
[ 1609.769009] iwlwifi 0000:04:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
[ 1609.769087] iwlwifi 0000:04:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [160,164]
[ 1609.769165] iwlwifi 0000:04:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769244] iwlwifi 0000:04:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [119,119]
[ 1609.769322] iwlwifi 0000:04:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769400] iwlwifi 0000:04:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769478] iwlwifi 0000:04:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769557] iwlwifi 0000:04:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769635] iwlwifi 0000:04:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769713] iwlwifi 0000:04:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769792] iwlwifi 0000:04:00.0: Q 11 is active and mapped to fifo 1 ra_tid 0x0000 [117,197]
[ 1609.769870] iwlwifi 0000:04:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.769948] iwlwifi 0000:04:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770026] iwlwifi 0000:04:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770104] iwlwifi 0000:04:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770182] iwlwifi 0000:04:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770260] iwlwifi 0000:04:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770339] iwlwifi 0000:04:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1609.770417] iwlwifi 0000:04:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 2087.320917] cfg80211: Calling CRDA to update world regulatory domain
[ 2090.642746] wlan0: authenticate with 10:0d:7f:74:f6:c3
[ 2090.659776] wlan0: send auth to 10:0d:7f:74:f6:c3 (try 1/3)
[ 2090.663675] wlan0: authenticated
[ 2090.666615] wlan0: associate with 10:0d:7f:74:f6:c3 (try 1/3)
[ 2090.706213] wlan0: associate with 10:0d:7f:74:f6:c3 (try 2/3)
[ 2090.719434] wlan0: RX AssocResp from 10:0d:7f:74:f6:c3 (capab=0x411 status=0 aid=4)
[ 2090.725648] wlan0: associated
[-- Attachment #5: iwlwifi.firmware.2.md5s.log --]
[-- Type: application/octet-stream, Size: 495 bytes --]
feea228ed059c3a998c12031313242b8 /lib/firmware/iwlwifi-6000-4.ucode
c66b20f9d5ac307ccae24989c5719fef /lib/firmware/iwlwifi-6000g2a-5.ucode
4b47db024c8a0cba872c3e98e907a378 /lib/firmware/iwlwifi-6000g2a-6.ucode
0117445b398883258811bfbb3852f1a8 /lib/firmware/iwlwifi-6000g2b-5.ucode
1f1763dfd472a487c3d61eac0a12b766 /lib/firmware/iwlwifi-6000g2b-6.ucode
2520eeeb638f22811e50d2d1912ef807 /lib/firmware/iwlwifi-6050-4.ucode
47cea8c3c90eeddf3d527685c05e5567 /lib/firmware/iwlwifi-6050-5.ucode
[-- Attachment #6: iwlwifi.firmware.1.log --]
[-- Type: application/octet-stream, Size: 558 bytes --]
-rw-r--r-- 1 root root 454608 Sep 4 04:36 /lib/firmware/iwlwifi-6000-4.ucode
-rw-r--r-- 1 root root 444128 Sep 4 04:36 /lib/firmware/iwlwifi-6000g2a-5.ucode
-rw-r--r-- 1 root root 677296 Sep 4 04:36 /lib/firmware/iwlwifi-6000g2a-6.ucode
-rw-r--r-- 1 root root 460236 Sep 4 04:36 /lib/firmware/iwlwifi-6000g2b-5.ucode
-rw-r--r-- 1 root root 679436 Sep 4 04:36 /lib/firmware/iwlwifi-6000g2b-6.ucode
-rw-r--r-- 1 root root 463692 Sep 4 04:36 /lib/firmware/iwlwifi-6050-4.ucode
-rw-r--r-- 1 root root 469780 Sep 4 04:36 /lib/firmware/iwlwifi-6050-5.ucode
[-- Attachment #7: lshw.log --]
[-- Type: application/octet-stream, Size: 18346 bytes --]
neptune
description: Notebook
product: P150HMx (Not Applicable)
vendor: CLEVO
version: Not Applicable
serial: Not Applicable
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 vsyscall32
configuration: boot=normal chassis=notebook family=Not Applicable sku=Not Applicable uuid=0090F5BE-CB40-0000-0000-000000000000
*-core
description: Motherboard
product: P150HMx
vendor: CLEVO
physical id: 0
version: Not Applicable
serial: Not Applicable
slot: Not Applicable
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 4.6.4
date: 07/06/2011
size: 64KiB
capacity: 1984KiB
capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
*-cache:0
description: L1 cache
physical id: 4
size: 256KiB
capacity: 256KiB
capabilities: internal varies
*-cache:1
description: L2 cache
physical id: 5
size: 1MiB
capacity: 1MiB
capabilities: internal varies unified
*-cache:2
description: L3 cache
physical id: 6
size: 6MiB
capacity: 6MiB
capabilities: internal varies unified
*-memory
description: System Memory
physical id: 7
slot: System board or motherboard
size: 8GiB
*-bank:0
description: SODIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: 9905428-040.A00LF
vendor: Kingston
physical id: 0
serial: 5705A96D
slot: ChannelA-DIMM0
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:1
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 1
serial: [Empty]
slot: ChannelA-DIMM1
*-bank:2
description: SODIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: 9905428-040.A00LF
vendor: Kingston
physical id: 2
serial: 5805AE6D
slot: ChannelB-DIMM0
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:3
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 3
serial: [Empty]
slot: ChannelB-DIMM1
*-cpu
description: CPU
product: Core i7
vendor: Intel Corp.
physical id: 4f
bus info: cpu@0
version: Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
slot: SOCKET 0
size: 2200MHz
capacity: 3300MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid cpufreq
configuration: cores=4 enabledcores=4 threads=8
*-pci
description: Host bridge
product: 2nd Generation Core Processor Family DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 09
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 09
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:41 ioport:e000(size=4096) memory:f4000000-f60fffff ioport:e8000000(size=201326592)
*-display
description: VGA compatible controller
product: GF114M [GeForce GTX 580M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:55 memory:f4000000-f5ffffff memory:e8000000-efffffff memory:f0000000-f3ffffff ioport:e000(size=128) memory:f6000000-f607ffff
*-multimedia
description: Audio device
product: GF114 HDMI Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@0000:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:f6080000-f6083fff
*-communication
description: Communication controller
product: 6 Series/C200 Series Chipset Family MEI Controller #1
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:51 memory:f650a000-f650a00f
*-usb:0
description: USB controller
product: 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:16 memory:f6508000-f65083ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 3.11.5-1-ARCH ehci_hcd
physical id: 1
bus info: usb@3
logical name: usb3
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@3:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=6 speed=480Mbit/s
*-multimedia
description: Audio device
product: 6 Series/C200 Series Chipset Family High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: 05
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:52 memory:f6500000-f6503fff
*-pci:1
description: PCI bridge
product: 6 Series/C200 Series Chipset Family PCI Express Root Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 memory:f6400000-f64fffff
*-usb
description: USB controller
product: uPD720200 USB 3.0 Host Controller
vendor: NEC Corporation
physical id: 0
bus info: pci@0000:02:00.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:16 memory:f6400000-f6401fff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 3.11.5-1-ARCH xhci_hcd
physical id: 0
bus info: usb@2
logical name: usb2
version: 3.11
capabilities: usb-3.00
configuration: driver=hub slots=2 speed=5000Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 3.11.5-1-ARCH xhci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-pci:2
description: PCI bridge
product: 6 Series/C200 Series Chipset Family PCI Express Root Port 2
vendor: Intel Corporation
physical id: 1c.1
bus info: pci@0000:00:1c.1
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:17 ioport:d000(size=4096) memory:f6300000-f63fffff
*-network
description: Ethernet interface
product: JMC250 PCI Express Gigabit Ethernet Controller
vendor: JMicron Technology Corp.
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 05
serial: 00:90:f5:be:cb:40
size: 10Mbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msix msi bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=jme driverversion=1.0.8 duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:54 memory:f6320000-f6323fff ioport:d100(size=128) ioport:d000(size=256) memory:f6310000-f631ffff memory:f6300000-f630ffff
*-generic:0
description: System peripheral
product: SD/MMC Host Controller
vendor: JMicron Technology Corp.
physical id: 0.1
bus info: pci@0000:03:00.1
version: 90
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
configuration: driver=sdhci-pci latency=0
resources: irq:18 memory:f6326000-f63260ff
*-generic:1 UNCLAIMED
description: SD Host controller
product: Standard SD Host Controller
vendor: JMicron Technology Corp.
physical id: 0.2
bus info: pci@0000:03:00.2
version: 90
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi cap_list
configuration: latency=0
resources: memory:f6325000-f63250ff
*-generic:2
description: System peripheral
product: MS Host Controller
vendor: JMicron Technology Corp.
physical id: 0.3
bus info: pci@0000:03:00.3
version: 90
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
configuration: driver=jmb38x_ms latency=0
resources: irq:18 memory:f6324000-f63240ff
*-pci:3
description: PCI bridge
product: 6 Series/C200 Series Chipset Family PCI Express Root Port 3
vendor: Intel Corporation
physical id: 1c.2
bus info: pci@0000:00:1c.2
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:18 memory:f6200000-f62fffff
*-network
description: Wireless interface
product: Centrino Ultimate-N 6300
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 35
serial: 00:24:d7:25:63:c0
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.11.5-1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.4.166 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
resources: irq:53 memory:f6200000-f6201fff
*-pci:4
description: PCI bridge
product: 6 Series/C200 Series Chipset Family PCI Express Root Port 4
vendor: Intel Corporation
physical id: 1c.3
bus info: pci@0000:00:1c.3
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:19 memory:f6100000-f61fffff
*-firewire
description: FireWire (IEEE 1394)
product: IEEE 1394 Host Controller
vendor: JMicron Technology Corp.
physical id: 0
bus info: pci@0000:05:00.0
version: 30
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi ohci bus_master cap_list
configuration: driver=firewire_ohci latency=0
resources: irq:19 memory:f6101000-f61017ff memory:f6100000-f61000ff
*-usb:1
description: USB controller
product: 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:23 memory:f6507000-f65073ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 3.11.5-1-ARCH ehci_hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@4:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=6 speed=480Mbit/s
*-usb
description: Video
product: BisonCam, NB Pro
vendor: BisonCam, NB Pro
physical id: 6
bus info: usb@4:1.6
version: 6.04
capabilities: usb-2.00
configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s
*-isa
description: ISA bridge
product: HM65 Express Chipset Family LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-storage
description: SATA controller
product: 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 05
width: 32 bits
clock: 66MHz
capabilities: storage msi pm ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:50 ioport:f070(size=8) ioport:f060(size=4) ioport:f050(size=8) ioport:f040(size=4) ioport:f020(size=32) memory:f6506000-f65067ff
*-serial UNCLAIMED
description: SMBus
product: 6 Series/C200 Series Chipset Family SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 05
width: 64 bits
clock: 33MHz
configuration: latency=0
resources: memory:f6505000-f65050ff ioport:f000(size=32)
*-power UNCLAIMED
description: To Be Filled By O.E.M.
product: To Be Filled By O.E.M.
vendor: To Be Filled By O.E.M.
physical id: 1
version: To Be Filled By O.E.M.
serial: To Be Filled By O.E.M.
capacity: 32768mWh
[-- Attachment #8: date.log --]
[-- Type: application/octet-stream, Size: 29 bytes --]
Sat Oct 19 17:11:42 CST 2013
[-- Attachment #9: uname.log --]
[-- Type: application/octet-stream, Size: 90 bytes --]
Linux neptune 3.11.5-1-ARCH #1 SMP PREEMPT Mon Oct 14 08:31:43 CEST 2013 x86_64 GNU/Linux
[-- Attachment #10: modinfo.iwldvm.log --]
[-- Type: application/octet-stream, Size: 451 bytes --]
filename: /lib/modules/3.11.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/dvm/iwldvm.ko.gz
license: GPL
author: Copyright(c) 2003-2013 Intel Corporation <ilw@linux.intel.com>
version: in-tree:
description: Intel(R) Wireless WiFi Link AGN driver for Linux
srcversion: F61A6DFF16236AFE6FB3E3B
depends: iwlwifi,mac80211,cfg80211
intree: Y
vermagic: 3.11.5-1-ARCH SMP preempt mod_unload modversions
[-- Attachment #11: modinfo.iwlwifi.log --]
[-- Type: application/octet-stream, Size: 13283 bytes --]
filename: /lib/modules/3.11.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz
license: GPL
author: Copyright(c) 2003-2013 Intel Corporation <ilw@linux.intel.com>
version: in-tree:
description: Intel(R) Wireless WiFi driver for Linux
firmware: iwlwifi-100-5.ucode
firmware: iwlwifi-1000-5.ucode
firmware: iwlwifi-135-6.ucode
firmware: iwlwifi-105-6.ucode
firmware: iwlwifi-2030-6.ucode
firmware: iwlwifi-2000-6.ucode
firmware: iwlwifi-5150-2.ucode
firmware: iwlwifi-5000-5.ucode
firmware: iwlwifi-6000g2b-6.ucode
firmware: iwlwifi-6000g2a-5.ucode
firmware: iwlwifi-6050-5.ucode
firmware: iwlwifi-6000-4.ucode
firmware: iwlwifi-3160-7.ucode
firmware: iwlwifi-7260-7.ucode
srcversion: B3EF32124305F5D1F6E94A5
alias: pci:v00008086d000008B3sv*sd00008470bc*sc*i*
alias: pci:v00008086d000008B4sv*sd00008270bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00008062bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00008060bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00008170bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00008070bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00000470bc*sc*i*
alias: pci:v00008086d000008B4sv*sd00000270bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00000062bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00000060bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00000170bc*sc*i*
alias: pci:v00008086d000008B3sv*sd00000070bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C420bc*sc*i*
alias: pci:v00008086d000008B2sv*sd0000C220bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C020bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C462bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C460bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C470bc*sc*i*
alias: pci:v00008086d000008B2sv*sd0000C262bc*sc*i*
alias: pci:v00008086d000008B2sv*sd0000C260bc*sc*i*
alias: pci:v00008086d000008B2sv*sd0000C270bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C162bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C062bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C160bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C060bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C170bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000C070bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004420bc*sc*i*
alias: pci:v00008086d000008B2sv*sd00004220bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004020bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004A6Cbc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004A6Ebc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004A70bc*sc*i*
alias: pci:v00008086d000008B1sv*sd0000486Ebc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004870bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004462bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004460bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004470bc*sc*i*
alias: pci:v00008086d000008B2sv*sd00004262bc*sc*i*
alias: pci:v00008086d000008B2sv*sd00004260bc*sc*i*
alias: pci:v00008086d000008B2sv*sd00004270bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004162bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004062bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004160bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004060bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004170bc*sc*i*
alias: pci:v00008086d000008B1sv*sd00004070bc*sc*i*
alias: pci:v00008086d00000892sv*sd00000462bc*sc*i*
alias: pci:v00008086d00000893sv*sd00000262bc*sc*i*
alias: pci:v00008086d00000892sv*sd00000062bc*sc*i*
alias: pci:v00008086d00000894sv*sd00000822bc*sc*i*
alias: pci:v00008086d00000894sv*sd00000422bc*sc*i*
alias: pci:v00008086d00000895sv*sd00000222bc*sc*i*
alias: pci:v00008086d00000894sv*sd00000022bc*sc*i*
alias: pci:v00008086d0000088Fsv*sd00005260bc*sc*i*
alias: pci:v00008086d0000088Esv*sd00004860bc*sc*i*
alias: pci:v00008086d0000088Esv*sd00004460bc*sc*i*
alias: pci:v00008086d0000088Fsv*sd00004260bc*sc*i*
alias: pci:v00008086d0000088Esv*sd00004060bc*sc*i*
alias: pci:v00008086d00000887sv*sd00004462bc*sc*i*
alias: pci:v00008086d00000888sv*sd00004262bc*sc*i*
alias: pci:v00008086d00000887sv*sd00004062bc*sc*i*
alias: pci:v00008086d00000890sv*sd00004822bc*sc*i*
alias: pci:v00008086d00000890sv*sd00004422bc*sc*i*
alias: pci:v00008086d00000891sv*sd00004222bc*sc*i*
alias: pci:v00008086d00000890sv*sd00004022bc*sc*i*
alias: pci:v00008086d00000896sv*sd00005027bc*sc*i*
alias: pci:v00008086d00000896sv*sd00005025bc*sc*i*
alias: pci:v00008086d00000897sv*sd00005017bc*sc*i*
alias: pci:v00008086d00000897sv*sd00005015bc*sc*i*
alias: pci:v00008086d00000896sv*sd00005007bc*sc*i*
alias: pci:v00008086d00000896sv*sd00005005bc*sc*i*
alias: pci:v00008086d000008AEsv*sd00001027bc*sc*i*
alias: pci:v00008086d000008AEsv*sd00001025bc*sc*i*
alias: pci:v00008086d000008AFsv*sd00001017bc*sc*i*
alias: pci:v00008086d000008AFsv*sd00001015bc*sc*i*
alias: pci:v00008086d000008AEsv*sd00001007bc*sc*i*
alias: pci:v00008086d000008AEsv*sd00001005bc*sc*i*
alias: pci:v00008086d00000084sv*sd00001316bc*sc*i*
alias: pci:v00008086d00000084sv*sd00001216bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001326bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001226bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001306bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001206bc*sc*i*
alias: pci:v00008086d00000084sv*sd00001315bc*sc*i*
alias: pci:v00008086d00000084sv*sd00001215bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001325bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001225bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001305bc*sc*i*
alias: pci:v00008086d00000083sv*sd00001205bc*sc*i*
alias: pci:v00008086d00000886sv*sd00001317bc*sc*i*
alias: pci:v00008086d00000886sv*sd00001315bc*sc*i*
alias: pci:v00008086d00000885sv*sd00001327bc*sc*i*
alias: pci:v00008086d00000885sv*sd00001325bc*sc*i*
alias: pci:v00008086d00000885sv*sd00001307bc*sc*i*
alias: pci:v00008086d00000885sv*sd00001305bc*sc*i*
alias: pci:v00008086d00000089sv*sd00001316bc*sc*i*
alias: pci:v00008086d00000089sv*sd00001311bc*sc*i*
alias: pci:v00008086d00000087sv*sd00001326bc*sc*i*
alias: pci:v00008086d00000087sv*sd00001321bc*sc*i*
alias: pci:v00008086d00000087sv*sd00001306bc*sc*i*
alias: pci:v00008086d00000087sv*sd00001301bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005226bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005225bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005221bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005207bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005206bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005205bc*sc*i*
alias: pci:v00008086d00000091sv*sd00005201bc*sc*i*
alias: pci:v00008086d00000090sv*sd00005216bc*sc*i*
alias: pci:v00008086d00000090sv*sd00005215bc*sc*i*
alias: pci:v00008086d00000090sv*sd00005211bc*sc*i*
alias: pci:v00008086d0000008Bsv*sd00005317bc*sc*i*
alias: pci:v00008086d0000008Bsv*sd00005315bc*sc*i*
alias: pci:v00008086d0000008Asv*sd00005327bc*sc*i*
alias: pci:v00008086d0000008Asv*sd00005325bc*sc*i*
alias: pci:v00008086d0000008Asv*sd00005307bc*sc*i*
alias: pci:v00008086d0000008Asv*sd00005305bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001305bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001304bc*sc*i*
alias: pci:v00008086d00000082sv*sd00004820bc*sc*i*
alias: pci:v00008086d00000085sv*sd0000C220bc*sc*i*
alias: pci:v00008086d00000082sv*sd0000C020bc*sc*i*
alias: pci:v00008086d00000085sv*sd00001316bc*sc*i*
alias: pci:v00008086d00000085sv*sd00001311bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001326bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001321bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001307bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001306bc*sc*i*
alias: pci:v00008086d00000082sv*sd00001301bc*sc*i*
alias: pci:v00008086d00004239sv*sd00001316bc*sc*i*
alias: pci:v00008086d00004239sv*sd00001311bc*sc*i*
alias: pci:v00008086d00004238sv*sd00001111bc*sc*i*
alias: pci:v00008086d0000422Csv*sd00001326bc*sc*i*
alias: pci:v00008086d0000422Csv*sd00001321bc*sc*i*
alias: pci:v00008086d0000422Csv*sd00001307bc*sc*i*
alias: pci:v00008086d0000422Csv*sd00001306bc*sc*i*
alias: pci:v00008086d0000422Csv*sd00001301bc*sc*i*
alias: pci:v00008086d0000422Bsv*sd00001121bc*sc*i*
alias: pci:v00008086d0000422Bsv*sd00001101bc*sc*i*
alias: pci:v00008086d0000423Dsv*sd00001316bc*sc*i*
alias: pci:v00008086d0000423Dsv*sd00001216bc*sc*i*
alias: pci:v00008086d0000423Dsv*sd00001311bc*sc*i*
alias: pci:v00008086d0000423Dsv*sd00001211bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001326bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001321bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001221bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001306bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001206bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001301bc*sc*i*
alias: pci:v00008086d0000423Csv*sd00001201bc*sc*i*
alias: pci:v00008086d0000423Bsv*sd00001011bc*sc*i*
alias: pci:v00008086d0000423Asv*sd00001021bc*sc*i*
alias: pci:v00008086d0000423Asv*sd00001001bc*sc*i*
alias: pci:v00008086d00004236sv*sd00001114bc*sc*i*
alias: pci:v00008086d00004236sv*sd00001014bc*sc*i*
alias: pci:v00008086d00004236sv*sd00001111bc*sc*i*
alias: pci:v00008086d00004236sv*sd00001011bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001104bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001004bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001101bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001001bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001124bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001024bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001121bc*sc*i*
alias: pci:v00008086d00004235sv*sd00001021bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001316bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001216bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001315bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001215bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001314bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001214bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001311bc*sc*i*
alias: pci:v00008086d00004237sv*sd00001211bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001326bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001226bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001325bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001225bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001324bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001224bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001321bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001221bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001306bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001206bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001305bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001205bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001304bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001204bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001301bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001201bc*sc*i*
depends: cfg80211
intree: Y
vermagic: 3.11.5-1-ARCH SMP preempt mod_unload modversions
parm: swcrypto:using crypto in software (default 0 [hardware]) (int)
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: agg TX, 4: agg RX (uint)
parm: amsdu_size_8K:enable 8K amsdu size (default 0) (int)
parm: fw_restart:restart firmware in case of error (default true) (bool)
parm: antenna_coupling:specify antenna coupling in dB (defualt: 0 dB) (int)
parm: wd_disable:Disable stuck queue watchdog timer 0=system default, 1=disable, 2=enable (default: 0) (int)
parm: nvm_file:NVM file name (charp)
parm: bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm: led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm: power_save:enable WiFi power management (default: disable) (bool)
parm: power_level:default power save level (range from 1 - 5, default: 1) (int)
[-- Attachment #12: iwconfig.out --]
[-- Type: application/octet-stream, Size: 564 bytes --]
[msaun@neptune ~]$ iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11abgn ESSID:"Kamikaze-24"
Mode:Managed Frequency:2.462 GHz Access Point: 10:0D:7F:74:F6:C3
Bit Rate=60 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=41/70 Signal level=-69 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:21869 Invalid misc:814 Missed beacon:0
^ permalink raw reply
* Re: [PATCH] wireless: rt2800lib: Fix typo on checking
From: Gertjan van Wingerde @ 2013-10-19 8:31 UTC (permalink / raw)
To: Felipe Pena, John W. Linville
Cc: Ivo van Doorn, Helmut Schaa, linux-wireless, users, netdev,
linux-kernel
In-Reply-To: <1382142042-4463-1-git-send-email-felipensp@gmail.com>
On 10/19/13 02:20, Felipe Pena wrote:
> On rt2800_config_channel_rf53xx function the member default_power1 is checked
> for bound limit, but default_power2 is used instead.
>
> Signed-off-by: Felipe Pena <felipensp@gmail.com>
Good catch.
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800lib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
> index 88ce656..1c2ce93 100644
> --- a/drivers/net/wireless/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/rt2x00/rt2800lib.c
> @@ -2650,7 +2650,7 @@ static void rt2800_config_channel_rf53xx(struct rt2x00_dev *rt2x00dev,
>
> if (rt2x00_rt(rt2x00dev, RT5392)) {
> rt2800_rfcsr_read(rt2x00dev, 50, &rfcsr);
> - if (info->default_power1 > POWER_BOUND)
> + if (info->default_power2 > POWER_BOUND)
> rt2x00_set_field8(&rfcsr, RFCSR50_TX, POWER_BOUND);
> else
> rt2x00_set_field8(&rfcsr, RFCSR50_TX,
> --
> 1.7.10.4
>
--
---
Gertjan
^ permalink raw reply
* Re: [PATCH 3.12] rt2800usb: slow down TX status polling
From: Gertjan van Wingerde @ 2013-10-19 8:33 UTC (permalink / raw)
To: Stanislaw Gruszka, Larry Finger; +Cc: linux-wireless, users
In-Reply-To: <20131018094238.GA7506@redhat.com>
On 10/18/13 11:42, Stanislaw Gruszka wrote:
> On Thu, Oct 17, 2013 at 09:39:06AM -0500, Larry Finger wrote:
>> I suggest getting rid of the magic numbers as long as you are making
>> this change. A single define could handle the delay time for the two
>> cases.
>
> Thanks for sugestion Larry, though I do not see clear benefit of
> introduce define since those magic numbers are just time values
> expressed in nano seconds. Anyway patch with define added below.
> John can pick it, if he thinks it is better.
>
> Stanislaw
> ---
> From 813e0bde7340bad7d3401c6aa2a3f8635ec49597 Mon Sep 17 00:00:00 2001
> From: Stanislaw Gruszka <sgruszka@redhat.com>
> Date: Fri, 18 Oct 2013 11:36:54 +0200
> Subject: [PATCH] rt2800usb: slow down TX status polling
>
> Polling TX statuses too frequently has two negative effects. First is
> randomly peek CPU usage, causing overall system functioning delays.
> Second bad effect is that device is not able to fill TX statuses in
> H/W register on some workloads and we get lot of timeouts like below:
>
> ieee80211 phy4: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
> ieee80211 phy4: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
> ieee80211 phy4: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
>
> This not only cause flood of messages in dmesg, but also bad throughput,
> since rate scaling algorithm can not work optimally.
>
> In the future, we should probably make polling interval be adjusted
> automatically, but for now just increase values, this make mentioned
> problems gone.
>
> Resolve:
> https://bugzilla.kernel.org/show_bug.cgi?id=62781
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
I don't care which version gets picked. In both cases:
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800usb.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c b/drivers/net/wireless/rt2x00/rt2800usb.c
> index 96677ce5..997df03 100644
> --- a/drivers/net/wireless/rt2x00/rt2800usb.c
> +++ b/drivers/net/wireless/rt2x00/rt2800usb.c
> @@ -148,6 +148,8 @@ static bool rt2800usb_txstatus_timeout(struct rt2x00_dev *rt2x00dev)
> return false;
> }
>
> +#define TXSTATUS_READ_INTERVAL 1000000
> +
> static bool rt2800usb_tx_sta_fifo_read_completed(struct rt2x00_dev *rt2x00dev,
> int urb_status, u32 tx_status)
> {
> @@ -176,8 +178,9 @@ static bool rt2800usb_tx_sta_fifo_read_completed(struct rt2x00_dev *rt2x00dev,
> queue_work(rt2x00dev->workqueue, &rt2x00dev->txdone_work);
>
> if (rt2800usb_txstatus_pending(rt2x00dev)) {
> - /* Read register after 250 us */
> - hrtimer_start(&rt2x00dev->txstatus_timer, ktime_set(0, 250000),
> + /* Read register after 1 ms */
> + hrtimer_start(&rt2x00dev->txstatus_timer,
> + ktime_set(0, TXSTATUS_READ_INTERVAL),
> HRTIMER_MODE_REL);
> return false;
> }
> @@ -202,8 +205,9 @@ static void rt2800usb_async_read_tx_status(struct rt2x00_dev *rt2x00dev)
> if (test_and_set_bit(TX_STATUS_READING, &rt2x00dev->flags))
> return;
>
> - /* Read TX_STA_FIFO register after 500 us */
> - hrtimer_start(&rt2x00dev->txstatus_timer, ktime_set(0, 500000),
> + /* Read TX_STA_FIFO register after 2 ms */
> + hrtimer_start(&rt2x00dev->txstatus_timer,
> + ktime_set(0, 2*TXSTATUS_READ_INTERVAL),
> HRTIMER_MODE_REL);
> }
>
>
--
---
Gertjan
^ permalink raw reply
* Re: ar5523 Gigaset USB Adapter 108 issue
From: Yannik Völker @ 2013-10-19 12:18 UTC (permalink / raw)
To: Oleksij Rempel; +Cc: Pontus Fuchs, linux-wireless
In-Reply-To: <52616CD0.2000203@rempel-privat.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 18.10.2013 19:16, schrieb Oleksij Rempel:
> Am 18.10.2013 18:33, schrieb Yannik Völker:
>> Am 18.10.2013 18:16, schrieb Oleksij Rempel:
>>> Am 18.10.2013 17:38, schrieb Yannik Völker:
>>>> Am 18.10.2013 17:07, schrieb Oleksij Rempel:
>>>>> Am 18.10.2013 16:49, schrieb Alan Stern:
>>>>>> Yannik, you should always use Reply-To-All so that your
>>>>>> messages get sent to the mailing list and not just to
>>>>>> me.
>>>>>>
>>>>>> On Thu, 17 Oct 2013, Yannik Völker wrote:
>>>>>>
>>>>>>> Am 07.08.2013 19:34, schrieb Alan Stern:
>>>>>>>> Please post two usbmon traces, one showing the
>>>>>>>> failure on your current system and the other showing
>>>>>>>> the adapter running correctly under a 32-bit kernel.
>>>>>>>> Instructions for usbmon are in the kernel source
>>>>>>>> file Documentation/usb/usbmon.txt.
>>>>>>> I never got it to work under a 32-bit kernel, i was
>>>>>>> just able to utilize a windows32 driver using
>>>>>>> ndiswrapper.
>>>>>>>
>>>>>>> Now i got it to "work". I randomly found out that the
>>>>>>> ar5523 driver actually works when you load it after
>>>>>>> you unload ndiswrapper so the following steps make it
>>>>>>> work: 1. modprobe ndiswrapper 2. plug in device 3.
>>>>>>> connect to wlan using ndiswrapper and disconnect again
>>>>>>> (might be optional) 4. modprobe -r ndiswrapper 5.
>>>>>>> modprobe ar5523 6. connect to wlan log for that is
>>>>>>> attatched as wlanthennative2.log
>>>>
>>>>
>>>>> It sounds like linux driver didn't recognised usb id and
>>>>> didn't uploaded firmware, or there was no firmware to
>>>>> upload.
>>>> there is firmware (/lib/firmware/ar5523.bin exists) but it
>>>> does not even get touched (i renamed the file and the error
>>>> did not change at all)
>>
>>> find first usbid of your adapter (it will be changed after
>>> firmware upload). And try to force driver to use this id:
>>> modprobe -v ar5523 echo 07d1 3a0d >
>>> /sys/bus/usb/drivers/ar5523/new_id
>>
>>> instead of "07d1 3a0d" use your id.
>>
>>
>> # lsusb … Bus 003 Device 011: ID 129b:160c CyberTAN Technology
>> Siemens S30853-S1038-R351 802.11g Wireless Adapter [Atheros
>> AR5523] …
>>
>> # modprobe ar5523 # echo 129b 160c >
>> /sys/bus/usb/drivers/ar5523/new_id <plugging device in> syslog:
>> Oct 18 18:27:47 yannik-desktop kernel: [ 8751.447784] usbcore:
>> registered new interface driver ar5523 Oct 18 18:28:25
>> yannik-desktop kernel: [ 8789.036912] usb 3-14: new high-speed
>> USB device number 12 using xhci_hcd Oct 18 18:28:25
>> yannik-desktop kernel: [ 8789.053995] usb 3-14: New USB device
>> found, idVendor=129b, idProduct=160c Oct 18 18:28:25
>> yannik-desktop kernel: [ 8789.054005] usb 3-14: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3 Oct 18 18:28:25
>> yannik-desktop kernel: [ 8789.054010] usb 3-14: Product: AR5523
>> Oct 18 18:28:25 yannik-desktop kernel: [ 8789.054015] usb 3-14:
>> Manufacturer: Atheros Communications Inc Oct 18 18:28:25
>> yannik-desktop kernel: [ 8789.054019] usb 3-14: SerialNumber:
>> 1.0 Oct 18 18:28:27 yannik-desktop kernel: [ 8791.052313] usb
>> 3-14: timeout waiting for command 01 reply Oct 18 18:28:27
>> yannik-desktop kernel: [ 8791.052323] usb 3-14: could not
>> initialize adapter Oct 18 18:28:27 yannik-desktop kernel: [
>> 8791.052359] usb 3-14: RX USB error -2. Oct 18 18:28:27
>> yannik-desktop kernel: [ 8791.052378] usb 3-14: error -1 when
>> submitting rx urb Oct 18 18:28:27 yannik-desktop kernel: [
>> 8791.052504] ar5523: probe of 3-14:1.0 failed with error -110
>>
>>> Besidy, what kernel version are you using? May be it is too
>>> old..
>>
>> 3.11.0-12-generic it is my understanding that the ar5523 driver
>> was included from 3.8 on.
>
> please test attached patch.
Stopped the error from appearing but it looks like it would not even try
to upload the firmware to me:
[ 708.193488] cfg80211: Calling CRDA to update world regulatory domain
[ 708.492120] usbcore: registered new interface driver ar5523
[ 708.509819] cfg80211: World regulatory domain updated:
[ 708.509822] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 708.509823] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 708.509824] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 708.509825] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[ 708.509826] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 708.509827] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 720.232697] usb 3-14: USB disconnect, device number 8
[ 721.721980] usb 3-14: new high-speed USB device number 9 using xhci_hcd
[ 721.739153] usb 3-14: New USB device found, idVendor=129b,
idProduct=160c
[ 721.739163] usb 3-14: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 721.739168] usb 3-14: Product: AR5523
[ 721.739174] usb 3-14: Manufacturer: Atheros Communications Inc
[ 721.739178] usb 3-14: SerialNumber: 1.0
mtp-probe: checking bus 3, device 9:
"/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14"
mtp-probe: bus: 3, device: 9 was not an MTP device
also it did not load the module on plugging in.
- --
Yannik Völker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBAgAGBQJSYnidAAoJEDqk81AiCyXKT1cP/3U/UvcXmhIHrxioZsM+WDcA
eEbC6zyEdGeLR10kkD9bnsTa0pwk4Bvj7ciuNKYYRn1kDpt+KIgmJoam0ljbF0Gb
jE/hG6ZzVdZEHWbEy2yz1+ns8hyQ7hCcc96zHI+5LQsPvqajRFgiclIOK9J1TbR4
Vc6xV0mJAAhLpokUZ+lD7cPlmBcpmMVkJrWRkyZW7W/jp4myitxmnROJrEVhZM51
sdglrDWq0tsEWgL8T5M10ZVwbBRZo94qYGWr3CVcDqEdAzx+vujtST7XWzmv1p85
6C9P+CmcEIS8GiCeZrQmPu74L2nXl5fT8xkrI9XrYd71q9HArl9Arr6w268nYw4N
urheXF88bg/Os4L/npm5yy9SGl+Iz/LJcsayrDP3MrwgNGZ8WGQ82mlxkk25X+l1
igu6A2OhB7fGfGoAuWpfRl1WBG33A1IuYyA1GWr5OrVShD831g8PLv8cFOBBHeFC
SLfh4hKPtctQk5NOlhe623wtOGI4lN2wXnRJIKABCdnIlzIkem7ZK1rmT4oXzNj3
cKzMf1mFOt5G1ow4iE0JDuH0RyUbkOa0CweyrXaJnyh1mQ6j3Y9XI6QMjk+dbt1f
E4RYKpL8IhTL2aWTDjSkyrbRNDpvtGa8h3yDvpZ3MartwOokUE6TTirxz3WfvLC0
8Poh/Wb6C2znRN/kfY6Q
=+njK
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: [PATCH] mac80211_hwsim: Add iface comb for DFS
From: Janusz Dziedzic @ 2013-10-19 12:39 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1382017495.14410.4.camel@jlt4.sipsolutions.net>
On 17 October 2013 15:44, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Mon, 2013-10-14 at 19:51 +0200, Janusz Dziedzic wrote:
>> Add iface combination that allow DFS support.
>> Add also debugfs dfs_simulate_radar file that
>> can be used to simulate radar event.
>> This could be usefull for mac80211/cfg80211/
>
> typo: useful
>
>> @@ -1714,6 +1716,7 @@ static void mac80211_hwsim_free(void)
>>
>> list_for_each_entry_safe(data, tmpdata, &tmplist, list) {
>> debugfs_remove(data->debugfs_group);
>> + debugfs_remove(data->debugfs_radar);
>
> I think it would be good to convert to debugfs_remove_recursive first -
> that avoids the need for the new dentry pointer as well as the remove
> here. Can you do that (as a separate patch)?
>
Sure, I will prepare patch.
>> +static int hwsim_write_simulate_radar(void *dat, u64 val)
>> +{
>> + struct mac80211_hwsim_data *data = dat;
>> +
>> + ieee80211_radar_detected(data->hw);
>> +
>> + return 0;
>> +}
>> +
>> +DEFINE_SIMPLE_ATTRIBUTE(hwsim_simulate_radar, NULL,
>> + hwsim_write_simulate_radar, "%llu\n");
>
> Does the u64 make sense? Probably doesn't matter much, but seems weird
> to be so specific for a file that really doesn't care about the value?
Yes this doesn't matter much. I am not sure what put there.
BR
Janusz
^ permalink raw reply
* Re: ar5523 Gigaset USB Adapter 108 issue
From: Oleksij Rempel @ 2013-10-19 15:30 UTC (permalink / raw)
To: Yannik Völker; +Cc: Pontus Fuchs, linux-wireless
In-Reply-To: <5262789D.8030704@yahoo.de>
Am 19.10.2013 14:18, schrieb Yannik Völker:
> Am 18.10.2013 19:16, schrieb Oleksij Rempel:
>> Am 18.10.2013 18:33, schrieb Yannik Völker:
>>> Am 18.10.2013 18:16, schrieb Oleksij Rempel:
>>>> Am 18.10.2013 17:38, schrieb Yannik Völker:
>>>>> Am 18.10.2013 17:07, schrieb Oleksij Rempel:
>>>>>> Am 18.10.2013 16:49, schrieb Alan Stern:
>>>>>>> Yannik, you should always use Reply-To-All so that your
>>>>>>> messages get sent to the mailing list and not just to
>>>>>>> me.
>>>>>>>
>>>>>>> On Thu, 17 Oct 2013, Yannik Völker wrote:
>>>>>>>
>>>>>>>> Am 07.08.2013 19:34, schrieb Alan Stern:
>>>>>>>>> Please post two usbmon traces, one showing the
>>>>>>>>> failure on your current system and the other showing
>>>>>>>>> the adapter running correctly under a 32-bit kernel.
>>>>>>>>> Instructions for usbmon are in the kernel source
>>>>>>>>> file Documentation/usb/usbmon.txt.
>>>>>>>> I never got it to work under a 32-bit kernel, i was
>>>>>>>> just able to utilize a windows32 driver using
>>>>>>>> ndiswrapper.
>>>>>>>>
>>>>>>>> Now i got it to "work". I randomly found out that the
>>>>>>>> ar5523 driver actually works when you load it after
>>>>>>>> you unload ndiswrapper so the following steps make it
>>>>>>>> work: 1. modprobe ndiswrapper 2. plug in device 3.
>>>>>>>> connect to wlan using ndiswrapper and disconnect again
>>>>>>>> (might be optional) 4. modprobe -r ndiswrapper 5.
>>>>>>>> modprobe ar5523 6. connect to wlan log for that is
>>>>>>>> attatched as wlanthennative2.log
>>>>>
>>>>>
>>>>>> It sounds like linux driver didn't recognised usb id and
>>>>>> didn't uploaded firmware, or there was no firmware to
>>>>>> upload.
>>>>> there is firmware (/lib/firmware/ar5523.bin exists) but it
>>>>> does not even get touched (i renamed the file and the error
>>>>> did not change at all)
>>>
>>>> find first usbid of your adapter (it will be changed after
>>>> firmware upload). And try to force driver to use this id:
>>>> modprobe -v ar5523 echo 07d1 3a0d >
>>>> /sys/bus/usb/drivers/ar5523/new_id
>>>
>>>> instead of "07d1 3a0d" use your id.
>>>
>>>
>>> # lsusb … Bus 003 Device 011: ID 129b:160c CyberTAN Technology
>>> Siemens S30853-S1038-R351 802.11g Wireless Adapter [Atheros
>>> AR5523] …
>>>
>>> # modprobe ar5523 # echo 129b 160c >
>>> /sys/bus/usb/drivers/ar5523/new_id <plugging device in> syslog:
>>> Oct 18 18:27:47 yannik-desktop kernel: [ 8751.447784] usbcore:
>>> registered new interface driver ar5523 Oct 18 18:28:25
>>> yannik-desktop kernel: [ 8789.036912] usb 3-14: new high-speed
>>> USB device number 12 using xhci_hcd Oct 18 18:28:25
>>> yannik-desktop kernel: [ 8789.053995] usb 3-14: New USB device
>>> found, idVendor=129b, idProduct=160c Oct 18 18:28:25
>>> yannik-desktop kernel: [ 8789.054005] usb 3-14: New USB device
>>> strings: Mfr=1, Product=2, SerialNumber=3 Oct 18 18:28:25
>>> yannik-desktop kernel: [ 8789.054010] usb 3-14: Product: AR5523
>>> Oct 18 18:28:25 yannik-desktop kernel: [ 8789.054015] usb 3-14:
>>> Manufacturer: Atheros Communications Inc Oct 18 18:28:25
>>> yannik-desktop kernel: [ 8789.054019] usb 3-14: SerialNumber:
>>> 1.0 Oct 18 18:28:27 yannik-desktop kernel: [ 8791.052313] usb
>>> 3-14: timeout waiting for command 01 reply Oct 18 18:28:27
>>> yannik-desktop kernel: [ 8791.052323] usb 3-14: could not
>>> initialize adapter Oct 18 18:28:27 yannik-desktop kernel: [
>>> 8791.052359] usb 3-14: RX USB error -2. Oct 18 18:28:27
>>> yannik-desktop kernel: [ 8791.052378] usb 3-14: error -1 when
>>> submitting rx urb Oct 18 18:28:27 yannik-desktop kernel: [
>>> 8791.052504] ar5523: probe of 3-14:1.0 failed with error -110
>>>
>>>> Besidy, what kernel version are you using? May be it is too
>>>> old..
>>>
>>> 3.11.0-12-generic it is my understanding that the ar5523 driver
>>> was included from 3.8 on.
>
>> please test attached patch.
> Stopped the error from appearing but it looks like it would not even try
> to upload the firmware to me:
>
> [ 708.193488] cfg80211: Calling CRDA to update world regulatory domain
>
>
> [ 708.492120] usbcore: registered new interface driver ar5523
>
>
> [ 708.509819] cfg80211: World regulatory domain updated:
>
>
> [ 708.509822] cfg80211: (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
>
> [ 708.509823] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
> mBi, 2000 mBm)
> [ 708.509824] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300
> mBi, 2000 mBm)
> [ 708.509825] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
> mBi, 2000 mBm)
> [ 708.509826] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
> mBi, 2000 mBm)
> [ 708.509827] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
> mBi, 2000 mBm)
> [ 720.232697] usb 3-14: USB disconnect, device number 8
> [ 721.721980] usb 3-14: new high-speed USB device number 9 using xhci_hcd
> [ 721.739153] usb 3-14: New USB device found, idVendor=129b,
> idProduct=160c
> [ 721.739163] usb 3-14: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 721.739168] usb 3-14: Product: AR5523
> [ 721.739174] usb 3-14: Manufacturer: Atheros Communications Inc
> [ 721.739178] usb 3-14: SerialNumber: 1.0
> mtp-probe: checking bus 3, device 9:
> "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14"
> mtp-probe: bus: 3, device: 9 was not an MTP device
>
> also it did not load the module on plugging in.
does not looks like it is complete log. Please attach your dmesg.
--
Regards,
Oleksij
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox