https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
dieterich@gmail.com changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #23 from dieterich@gmail.com ---
(In reply to Hiren Panchasara from comment #22)
(In reply to dieterich.joh from comment #21)
(In reply to Adrian Chadd from comment #17)
Also, please test out with the latest -HEAD and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
Lars Engels l...@freebsd.org changed:
What|Removed |Added
CC||l...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #19 from Adrian Chadd adr...@freebsd.org ---
wlandebug +rate
what happens?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #20 from Hiren Panchasara hi...@freebsd.org ---
18:55 hiren Sep 6 18:55:10 flymockour-l7 kernel: wlan0: [dc:9f:db:6a:3e:9e]
AMRR: current rate 0, txcnt=11, retrycnt=14
18:55 hiren Sep 6 18:55:15 flymockour-l7 kernel: wlan0:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #21 from dieterich@gmail.com ---
(In reply to Adrian Chadd from comment #17)
Also, please test out with the latest -HEAD and see if it behaves better for
you.
Just installed r271215 and can confirm that the situation is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #15 from Adrian Chadd adr...@freebsd.org ---
The problem seems to be a lack of correct feedback to the AMRR rate control
code. It doesn't get informed of the correct number of transmissions, failures
and retries, leading to it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #3 from Hiren Panchasara hi...@freebsd.org ---
I did a simple iperf test where I ran client on wifi laptop and server on a
machine connected to lan in my network. I am seeing 3mbps/sec average.
% ifconfig wlan0
wlan0:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #6 from Hiren Panchasara hi...@freebsd.org ---
Created attachment 146235
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146235action=edit
wifi debug 1
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #7 from Hiren Panchasara hi...@freebsd.org ---
Created attachment 146236
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146236action=edit
wifi debug 2
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #9 from Adrian Chadd adr...@freebsd.org ---
(In reply to Hiren Panchasara from comment #6)
Created attachment 146235 [details]
wifi debug 1
Hm, so it drops all the way to MCS0 and then never tries a higher rate. I
wonder why.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #11 from Hiren Panchasara hi...@freebsd.org ---
where exactly should I be looking for to know the rate?
I see following:
Aug 24 15:43:44 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 2 len 56 nsegs 2
rate 0083 plcp 0x4103
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #12 from Hiren Panchasara hi...@freebsd.org ---
Tried to follow the rabbit-hole to see where rate is coming from:
Index: if_iwn.c
===
--- if_iwn.c(revision
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950
--- Comment #14 from Adrian Chadd adr...@freebsd.org ---
Hi,
So the tx path grabs the rate from the net80211 ratectl code.
The link_quality table controls which rates are tried in which order, and I
think it's _after_ the rate that is
14 matches
Mail list logo
