Oleksij Rempel wrote:
Can you try this patch ?
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 6d643ca..a638f3a 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -850,8 +850,9 @@
Sujith Manoharan wrote:
seems to be fixed with this change. thank you :)
Thanks for testing, I'll post a more complete patch.
Just to confirm, can you test this patch on a clean tree
(without the earlier fix) and make sure that the debug message
is seen when the issue happens ?
Thanks !
Am 08.01.2014 11:58, schrieb Sujith Manoharan:
Oleksij Rempel wrote:
Can you try this patch ?
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 6d643ca..a638f3a 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++
Oleksij Rempel wrote:
Can you try this patch ?
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 6d643ca..a638f3a 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -850,8 +850,9 @@
Oleksij Rempel wrote:
Can you see if this patch makes a difference ?
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index 47c6285..b3e1d5e 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -2480,7
Am 08.01.2014 12:18, schrieb Sujith Manoharan:
Sujith Manoharan wrote:
seems to be fixed with this change. thank you :)
Thanks for testing, I'll post a more complete patch.
Just to confirm, can you test this patch on a clean tree
(without the earlier fix) and make sure that the debug
Oleksij Rempel wrote:
Does this happen a lot ?
It depends on how intensively WiFi is used.
See attachment
[ 657.383048] ath: phy0: unsupported hw bitrate detected 0x1b using 1 Mbit
[ 657.703201] ath: phy0: unsupported hw bitrate detected 0x1b using 1 Mbit
Can you load the driver
Oleksij Rempel wrote:
Am 07.01.2014 17:26, schrieb Sujith Manoharan:
Oleksij Rempel wrote:
Does this happen a lot ?
It depends on how intensively WiFi is used.
See attachment
[ 657.383048] ath: phy0: unsupported hw bitrate detected 0x1b using 1 Mbit
[ 657.703201] ath: phy0:
Oleksij Rempel wrote:
looks like happens at scan time:
[ 3161.475583] ath: phy3: Reset to 2442 MHz, HT40: 0 fastcc: 1
[ 3161.540259] ath: phy3: Set channel: 5180 MHz width: 2
[ 3161.540394] ath: phy3: unsupported hw bitrate detected 0x1b using 1 Mbit
[ 3161.540414] ath: phy3: Reset to 5180
Oleksij Rempel wrote:
Hello all,
my kernel log spammed with this message:
ath: phy0: unsupported hw bitrate detected 0x1b using 1 Mbit
Does this happen a lot ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
Am 19.12.2013 04:14, schrieb Sujith Manoharan:
Oleksij Rempel wrote:
Hello all,
my kernel log spammed with this message:
ath: phy0: unsupported hw bitrate detected 0x1b using 1 Mbit
Does this happen a lot ?
It depends on how intensively WiFi is used.
See attachment
--
Regards,
Oleksij
11 matches
Mail list logo