[Bug 191090] New: rsu panics when reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090

Bug ID: 191090
   Summary: rsu panics when reboot
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: dcha...@freebsd.org

Mon Jun 16 10:01:48 MSK 2014

FreeBSD dchagin.static.corbina.net 11.0-CURRENT FreeBSD 11.0-CURRENT #5
r267493+5636483(lemul): Mon Jun 16 09:18:14 MSK 2014
r...@dchagin.static.corbina.net:/home/dchagin/garbage/obj/home/dchagin/head/sys/YOY
 amd64

panic:

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
<118>Jun 16 09:47:26 dchagin reboot: rebooted by root
<118>Jun 16 09:47:26 dchagin syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...7 2 2 1 0 0 0 0 done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
All buffers synced.
lock order reversal:
 1st 0xf8001128e5f0 ufs (ufs) @
/home/dchagin/head/sys/kern/vfs_mount.c:1237
 2nd 0xf800114d2d50 devfs (devfs) @
/home/dchagin/head/sys/ufs/ffs/ffs_vfsops.c:1412
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe033d1e4380
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe033d1e4430
witness_checkorder() at witness_checkorder+0xdc2/frame 0xfe033d1e44c0
__lockmgr_args() at __lockmgr_args+0xdca/frame 0xfe033d1e4600
vop_stdlock() at vop_stdlock+0x3c/frame 0xfe033d1e4620
VOP_LOCK1_APV() at VOP_LOCK1_APV+0x14a/frame 0xfe033d1e4670
_vn_lock() at _vn_lock+0xaa/frame 0xfe033d1e46e0
ffs_flushfiles() at ffs_flushfiles+0x88/frame 0xfe033d1e4740
softdep_flushfiles() at softdep_flushfiles+0x1e3/frame 0xfe033d1e47a0
ffs_unmount() at ffs_unmount+0x152/frame 0xfe033d1e4800
dounmount() at dounmount+0x445/frame 0xfe033d1e4890
vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfe033d1e48e0
kern_reboot() at kern_reboot+0x5d0/frame 0xfe033d1e4960
sys_reboot() at sys_reboot+0x41/frame 0xfe033d1e4980
amd64_syscall() at amd64_syscall+0x27d/frame 0xfe033d1e4ab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe033d1e4ab0
--- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x80086380c, rsp =
0x7fffe9d8, rbp = 0x7fffeb40 ---
lock order reversal:
 1st 0xf8001128e5f0 ufs (ufs) @
/home/dchagin/head/sys/kern/vfs_mount.c:1237
 2nd 0x80feefb8 GEOM topology (GEOM topology) @
/home/dchagin/head/sys/ufs/ffs/ffs_vfsops.c:1302
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe033d1e4600
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe033d1e46b0
witness_checkorder() at witness_checkorder+0xdc2/frame 0xfe033d1e4740
_sx_xlock() at _sx_xlock+0x78/frame 0xfe033d1e47a0
ffs_unmount() at ffs_unmount+0x306/frame 0xfe033d1e4800
dounmount() at dounmount+0x445/frame 0xfe033d1e4890
vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfe033d1e48e0
kern_reboot() at kern_reboot+0x5d0/frame 0xfe033d1e4960
sys_reboot() at sys_reboot+0x41/frame 0xfe033d1e4980
amd64_syscall() at amd64_syscall+0x27d/frame 0xfe033d1e4ab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe033d1e4ab0
--- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x80086380c, rsp =
0x7fffe9d8, rbp = 0x7fffeb40 ---
lock order reversal:
 1st 0xf800111f67c8 ufs (ufs) @
/home/dchagin/head/sys/kern/vfs_mount.c:1237
 2nd 0x810090b0 allproc (allproc) @
/home/dchagin/head/sys/kern/kern_descrip.c:2790
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe033d1e4610
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe033d1e46c0
witness_checkorder() at witness_checkorder+0xdc2/frame 0xfe033d1e4750
_sx_slock() at _sx_slock+0x79/frame 0xfe033d1e47b0
mountcheckdirs() at mountcheckdirs+0x47/frame 0xfe033d1e4800
dounmount() at dounmount+0x390/frame 0xfe033d1e4890
vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfe033d1e48e0
kern_reboot() at kern_reboot+0x5d0/frame 0xfe033d1e4960
sys_reboot() at sys_reboot+0x41/frame 0xfe033d1e4980
amd64_syscall() at amd64_syscall+0x27d/frame 0xfe033d1e4ab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe033d1e4ab0
--- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x80086380c, rsp =
0x7fffe9d8, rbp = 0x7fffeb40 ---
Uptime: 26m18s


Fatal trap 9: general p

[Bug 191090] rsu panics when reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090

vidwer+fbsdb...@gmail.com changed:

   What|Removed |Added

 CC||vidwer+fbsdb...@gmail.com

--- Comment #1 from vidwer+fbsdb...@gmail.com ---
Can you tell more about the hardware: what is the commercial name of the
adapter, how is attached: to usb 2.0 or 3.0, etcetera?

How does your 'YOY' kernel configuration look like?

When does the panic happen, is it plugged in while rebooting? Does your machine
panic when removing the USB device?

Can you reproduce the panic with 10-STABLE?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 191090] rsu panics when reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090

--- Comment #2 from Dmitry Chagin  ---
Created attachment 143861
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143861&action=edit
YOY kernel config

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 191090] rsu panics when reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090

--- Comment #3 from Dmitry Chagin  ---
According to a trap trace i do not think what panic is hw specific...
Nonetheless, it is a asus usb-n10 adapter.
usbus2 on ehci1 which is Intel Lynx Point USB 2.0 controller,
panic occurs when adapter plugged in.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 191090] rsu panics when reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090

--- Comment #4 from Dmitry Chagin  ---
yet another panic, when removing rsu:

rsu0:  on
usbus2
rsu0: MAC/BB RTL8712 cut 3
wlan1: Ethernet address: 50:46:5d:76:ef:15
ugen2.3:  at usbus2 (disconnected)
rsu0: at uhub3, port 3, addr 3 (disconnected)
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex rsu0 (network driver) r = 0 (0xfe0002c330a0) locked @
/home/dchagin/head/sys/dev/usb/usb_util.c:146
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe033d2292e0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe033d229390
witness_warn() at witness_warn+0x4b5/frame 0xfe033d229450
trap_pfault() at trap_pfault+0x59/frame 0xfe033d2294f0
trap() at trap+0x752/frame 0xfe033d229840
calltrap() at calltrap+0x8/frame 0xfe033d229840
--- trap 0xc, rip = 0x804358fe, rsp = 0xfe033d229900, rbp =
0xfe033d229980 ---
rsu_init_locked() at rsu_init_locked+0x19ce/frame 0xfe033d229980
rsu_ioctl() at rsu_ioctl+0xa6/frame 0xfe033d2299b0
taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfe033d229a10
taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfe033d229a40
fork_exit() at fork_exit+0xd9/frame 0xfe033d229ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe033d229ab0
--- trap 0, rip = 0, rsp = 0xfe033d229b70, rbp = 0 ---


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address= 0x0
fault code= supervisor read data, page not present
instruction pointer= 0x20:0x804358fe
stack pointer= 0x28:0xfe033d229900
frame pointer= 0x28:0xfe033d229980
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process= 0 (rsu0 net80211 taskq)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 184692] [iwi] [panic] kernel panic in iwi0 driver

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184692

h...@sendmail.cz changed:

   What|Removed |Added

 Status|In Discussion   |Issue Resolved
 Resolution|--- |DUPLICATE

--- Comment #3 from h...@sendmail.cz ---


*** This bug has been marked as a duplicate of bug 185025 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 185025] [iwi] [panic] iwi driver panic on 10.0rc2

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185025

--- Comment #2 from h...@sendmail.cz ---
*** Bug 184692 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 189405] [run] [wlan] hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189405

Gabor Simon  changed:

   What|Removed |Added

 CC||gabor.simo...@gmail.com

--- Comment #2 from Gabor Simon  ---
Created attachment 144753
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144753&action=edit
Proposed patch to prevent kernel panic in hostap mode.

rvp->beacon_mbuf was NULL in run_update_beacon

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192057] New: Wi-Fi Broadcom BCM43224 doesn`t work and etc.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192057

Bug ID: 192057
   Summary: Wi-Fi Broadcom BCM43224 doesn`t work and etc.
   Product: Base System
   Version: 10.0-STABLE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: p...@imail.ru

Created attachment 144903
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144903&action=edit
Diagnostic

Wi-Fi Broadcom Corporation BCM43224 802.11a/b/g/n doesn`t work.

Sound IDT 92HD81B1X (Analog 2.0+HP/2.0) (pcm) found and works only in Sound
Configuration Test sound from PC-BSD Control Panel, it is inactive in other
places.

System fan permanently on high speed.

OS version 10.0.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192057] Sound doesn't work, fan on high, Wi-Fi Broadcom BCM43224 doesn't work

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192057

Gavin Atkinson  changed:

   What|Removed |Added

 Status|Needs Triage|Open
Summary|Wi-Fi Broadcom BCM43224 |Sound doesn't work, fan on
   |doesn`t work and etc.   |high, Wi-Fi Broadcom
   ||BCM43224 doesn't work

--- Comment #1 from Gavin Atkinson  ---
Hi,

Unfortunately, we do not have a driver for the BCM43224 WiFi chipset - this
chipset is entirely undocumented, making it hard to support.

For the sound issue, it looks like your system actually has four different
sound interfaces, and my guess is that we're defaulting to the wrong interface.
 In a root shell, can you try:

sysctl hw.snd.default_unit=0

and then try playing sound.  If that doesn't work, try setting it to 1, 2 and
then 3, each time stopping and restarting playing audio each time.  I suspect
one setting will make audio work (note that it is possible that PC-BSD provides
a "proper" interface to do this, however I'm afraid that I don't know what that
would be.

It's not clear from the debug output you gave what the issue could be with the
fan being stuck on high speed.  Could you show the output of "vmstat -i; sleep
10; vmstat -i" when the fan is running at high speed on an otherwise idle
system?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192057] Sound doesn't work, fan on high, Wi-Fi Broadcom BCM43224 doesn't work

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192057

Gavin Atkinson  changed:

   What|Removed |Added

   Assignee|freebsd-wirel...@freebsd.or |freebsd-b...@freebsd.org
   |g   |

--- Comment #2 from Gavin Atkinson  ---
Over to -bugs, multiple bugs in one report (and the non-wireless ones are more
easily fixed)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 189405] [run] [wlan] hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189405

j...@feith.com changed:

   What|Removed |Added

 CC||j...@feith.com

--- Comment #3 from j...@feith.com ---
I also ran into this after migrating 9.2 to 10.0 via src build (the wifi
was working fine on 9.2). The supplied patch appears to fix the problem 
on my machine.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192415] New: [ath] AR933x power save causes the AR9331 to stop DMA

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415

Bug ID: 192415
   Summary: [ath] AR933x power save causes the AR9331 to stop DMA
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

The current powersave code in the ath(4) driver / HAL is causing issues on the
AR9331.

Even if powersave is disabled, the chip is put into powersave mode when no VAPs
are in use. This seems to lock up the DMA side of things.

Symptoms:

* lots of "disable rx dma failed" messages
* no packets being transmitted/received
* TX/RX interrupt counts don't increase
* if AH_INTERRUPT_DEBUGGING is defined, then sync interrupts are posted - 0x200
and 0x40.

Now, I'm not sure yet what those bits are. I guess it's similar to the AR9340
ones - AR9340_INTR_SYNC_MAC_SLEEP_ACCESS (0x40). That meant that it was
configured whilst the MAC was asleep. Ugh.

If i disable the power save code in if_ath.c (ie, make all the
ath_hal_setpowermode() calls to HAL_PM_AWAKE) then things work fine.

So, figure out what is being programmed whilst the MAC is asleep, or what is
currently not shut down correctly before the MAC is put to sleep.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192416] New: [ath] TSFOOR interrupt firing on AR9331

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192416

Bug ID: 192416
   Summary: [ath] TSFOOR interrupt firing on AR9331
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

The TSFOOR interrupt is triggering with the AR9331 in station mode.

take a look to see what's going on:

* is it not RX'ing beacons;
* is the beacon timer programming all fucked up;
* is calibration interfering;
* something else.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192416] [ath] TSFOOR interrupt firing on AR9331

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192416

--- Comment #1 from Glen Barber  ---
Also happens on AR9485, but has not happened for me recently.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] New: FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

Bug ID: 192423
   Summary: FreeBSD-10 with AR9220, console spam and reboot with
both hostap and client wlan-s on the same ath0
   Product: Base System
   Version: 10.0-STABLE
  Hardware: i386
OS: Any
Status: Needs Triage
  Severity: Affects Some People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: nde...@gmail.com

I have a Soekris Net5501 on which I've recently installed an AR9220 based
mini-PCI card (MikroTik R52Hn) with both antenna ports used.

I'm trying to use it to both connect to an AP, and at the same time setup as a
AP.

The AP I'm connecting to is 802.11g, while I'm setting up the AP wlan as
802.11n (not sure if this is relevant).

And at the moment both wlan0 and wlan1 are enabled the machine slows down,
possibly due to excessive kernel printfs like these :

  ath0: ath_rate_findrate: currates != sc_currates!

And eventually reboots (possibly due to watchdog kicking in).

rc.conf :

  wlans_ath0="wlan0 wlan1"
  ifconfig_ath0="up"
  ifconfig_wlan0="ssid WISP wepkey 1:0xdeadbeef weptxkey 1 wepmode on deftxkey
1 DHCP"
  create_args_wlan1="wlanmode hostap"
  ifconfig_wlan1="mode 11ng channel 9:ht/40"
  ifconfig_bridge0="addm wlan1 addm vr0"

hostapd.conf :
  interface=wlan1
  logger_syslog=-1
  logger_syslog_level=0
  logger_stdout=-1
  logger_stdout_level=0
  debug=3
  dump_file=/tmp/hostapd.dump
  ctrl_interface=/var/run/hostapd
  ctrl_interface_group=wheel
  ssid=my-home-wi-fi
  macaddr_acl=0
  auth_algs=1
  ieee8021x=0
  wpa=2
  wpa_passphrase=
  wpa_key_mgmt=WPA-PSK
  wpa_pairwise=CCMP

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

--- Comment #1 from nde...@gmail.com ---
OS is : FreeBSD mars 10.0-STABLE FreeBSD 10.0-STABLE #20 r262664: Mon Mar  3
02:24:37 UTC 2014 root@mars:/usr/obj/usr/src/sys/MARS  i386

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #2 from Adrian Chadd  ---
What channel is it associating on?

Typically when that happens it's because the rate control code found that the
rate table was changing very frequently from underneath it and a lot of the
wifi driver code assumed the rate table wouldn't change that frequently.

Is ath0 the AP or STA?

So there's two parts:

* figure out why your rate table keeps changing;
* figure out a better way to handle that in the rate table code.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192424] New: [ath] Port over AR9331 fixes from qca-wifi git repository

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192424

Bug ID: 192424
   Summary: [ath] Port over AR9331 fixes from qca-wifi git
repository
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

There's a few things that should be ported over from the qca-wifi (public) git
repository. I'll add to this ticket as I find things to port.

* there's some hornet (AR9331) specific otp initialisation code which I _think_
is setting up various thermal / regulator parameters.
* there's a WAR in ar9300_set_reset() for the AR9331 which asks the SoC to get
involved if it's a cold reset. Ie, it actually does a full wireless
mac/phy/radio reset via the SoC path rather than a straight cold reset via the
normal MAC/RTC path.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 188576] [ath] traffic hangs in station mode when downgrading from AMPDU TX or reassociating

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188576

Adrian Chadd  changed:

   What|Removed |Added

 Status|In Discussion   |Issue Resolved
 Resolution|--- |FIXED

--- Comment #2 from Adrian Chadd  ---
I believe this is fixed in FreeBSD-HEAD.

I found and squished these until I had it constantly doing AMPDU
upgrade/downgrade due to high packet loss whilst doing constant traffic.

I'll re-open this if it pops up again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

--- Comment #3 from nde...@gmail.com ---
Both wlan0 and wlan1 are on the same ath0 device.

So, wlan0 is STA, associated on channel 9 (2452 MHz 11g).
Currently is at DS/11Mbps, however it fluctuates a lot between DS1/Mbps,
5.5Mbps,
sometimes it goes as high as OFDM/48Mbps.

wlan1 is the AP wlan, it is now configured on Channel 6, however I've tried to
start it also on channel 9 with the same result.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192415] [ath] AR933x power save causes the AR9331 to stop DMA

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415

--- Comment #1 from Adrian Chadd  ---
Specifically:

root@freebsd-carambola2:/home/adrian # sysctl dev.ath.0.stats.sync_intr | grep
-v ': 0$'
dev.ath.0.stats.sync_intr.10: 52
dev.ath.0.stats.sync_intr.13: 52

The bits from ar9300reg.h:

AR9300_INTR_SYNC_RADM_CPL_TLP_ABORT = 0x0400,
AR9300_INTR_SYNC_LOCAL_TIMEOUT  = 0x2000,

.. now, the former is not entirely right - those bits are PCIe host interface
specific. The latter bit is likely valid for the AR9331.

I'll have to get a hold of the AR9331 host interface description from Atheros
to figure out what the sync interrupt bits actually mean here.

I do think that a register was programmed whilst the NIC was in network or full
sleep. I'll have to figure out why my debugging code isn't picking up on that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 176104] [iwn] iwn0: iwn_intr: fatal firmware error

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176104

Rene Ladan  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #10 from Rene Ladan  ---
I'm seeing the same (or quite similar) fatal firmware errors on my Acer 7738G
with this chip:
iwn0:  mem 0xf520-0xf5201fff irq 17 at device 0.0 on
pci3

This is on 10.0-RELEASE amd64, with firmware version iwlwifi-5150-8.24.2.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192567] New: [ath] AR9331 regulator programming is checking OTP but reading garbage

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192567

Bug ID: 192567
   Summary: [ath] AR9331 regulator programming is checking OTP but
reading garbage
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

The AR9331 HAL is programming the regulator during reset. However, it's reading
values from the OTP which seems to (a) read correctly from the OTP, but (b)
read 0xbadc0ffe. I'm not sure why that is yet (eg is the OTP hardware off?)

Now, on the AR9331 boards I have (eg carambola 2) the calibration data is in
the NOR flash rather than OTP.  So, this won't .. work. I'm not sure which
boards will use OTP in this instance.

But the code seems to check and use the OTP value. Ie:

ar9300_internal_regulator_apply():
...
if ((reg_val & 0x80) == 0x80){
usb_valid = 1;
reg_usb = reg_val & 0x00ff;
}
...
if ((reg_val & 0x8000) == 0x8000){
pmu_valid = 1;
reg_pmu = (reg_val & 0xff00) >> 24;
}

... 0xbadc0ffe has both of those bits set!

ath9k doesn't bother checking the OTP here. It just uses some local values to
program in.

So, what should be done?

* Is the code correct but OTP isn't on for some reason?
* Should I be checking the in-flash calibration data?
* should I just ignore OTP and use hard-coded values like ath9k?



-a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192415] [ath] AR933x power save causes the AR9331 to stop DMA

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415

Adrian Chadd  changed:

   What|Removed |Added

 Status|Needs Triage|Issue Resolved
 Resolution|--- |FIXED

--- Comment #2 from Adrian Chadd  ---
This has been fixed in r269748.

Well, "fixed" - it just cold resets the NIC as appropriately rather than trying
to figure out why it's failing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

--- Comment #4 from Nikolay Denev  ---
So, just for the experiment, I've commented out the "currrates != sc_currates!"
device_printf line and recompiled.

Now, when I crete both wlan devices one, AP one STA, they seem to work, but
after a while (a few minutes) of iperf traffic over wlan1 (the AP) I see a lot
of these on the console and
wifi clients lose IP connectivity while still show "associated":

Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fbbc0: seqno
2434: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eaef0: seqno
2435: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e9f00: seqno
2436: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ecdc0: seqno
2437: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f4d40: seqno
2438: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f0d80: seqno
2439: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e8e00: seqno
2440: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e7150: seqno
2441: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fa790: seqno
2442: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e0820: seqno
2443: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eb660: seqno
2444: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e89c0: seqno
2445: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e8470: seqno
2446: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f8f20: seqno
2447: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f21b0: seqno
2428: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f01d0: seqno
2453: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39da550: seqno
2454: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ea780: seqno
2455: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eeeb0: seqno
2456: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eced0: seqno
2458: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e3c30: seqno
2459: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dda70: seqno
2460: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39ea670: seqno
2461: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f6170: seqno
2462: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f5f50: seqno
2463: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dffa0: seqno
2464: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f1930: seqno
2465: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dc860: seqno
2466: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f23d0: seqno
2467: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f78d0: seqno
2468: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f02e0: seqno
2469: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f4e50: seqno
2470: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f14f0: seqno
2471: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39eea70: seqno
2472: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e4180: seqno
2473: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e3190: seqno
2474: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39edec0: seqno
2475: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39e26f0: seqno
2476: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39f3f70: seqno
2477: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39dca80: seqno
2478: bf_next not NULL!
Aug 11 07:33:25 mars kernel: ath0: ath_tx_default_comp: bf 0xc39fa9b0: seqno
2479: bf_next not NULL!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

--- Comment #5 from Nikolay Denev  ---
So, I'm absolutely not familiar with the inner workings of the 80211 layer,
but if the ""currrates != sc_currates!"" condition is not something really
weird in my case, maybe I can try to turn this into a counter, so that the
console is not spammed to a livelock of the machine. (offtopic, but ideally
kernel printf should have had some rate limiting)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

Adrian Chadd  changed:

   What|Removed |Added

 Status|Needs Triage|In Discussion

--- Comment #6 from Adrian Chadd  ---
Ah, I only noticed just now that you're using it as STA and AP.

So, the only supported (read: tested) setup with a STA + AP VAP on the same
device is when running it as a wireless extension using WDS.

Also, I think I fixed that bf_next issue in -HEAD. Would you consider running
that instead for ath+11n?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423

--- Comment #7 from Nikolay Denev  ---
I will give it a try (running CURRENT) if time permits, as the full rebuild
will take me some time (I don't have a separate build env setup correctly, and
rebuilding on the Soekris itslef takes a few days :D )

Anyways, I've just tried a shortcut and manually applied a bf_next fix I've
found : http://svnweb.freebsd.org/base?view=revision&revision=264710
And not I no longer see these messages.
Apart from having to do a "ifconfig wlan1 down && ifconfig wlan1 up" after
reboot[1] it seems to work and I just pushed a 60 secs of iperf over the AP
wlan :

[  5] local 10.0.0.1 port 5001 connected with 10.0.0.173 port 61317
[  5]  0.0-60.0 sec   615 MBytes  86.0 Mbits/sec


[1]: after reboot I see wlan1 as "no carrier", while it is UP and hostapd is
runing. If I do down/up if starts working.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192641] New: [iwn] panic in AMPDU tx code "ni: no node"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192641

Bug ID: 192641
   Summary: [iwn] panic in AMPDU tx code "ni: no node"
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

(kgdb) bt
#0  doadump (textdump=-1059352868) at pcpu.h:233
#1  0xc04f92cd in db_fncall (dummy1=-332454048, dummy2=0, dummy3=-951087536,
dummy4=0xec2f274c "�&R��\216��") at
/usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:578
#2  0xc04f8fab in db_command (cmd_table=) at
/usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:449
#3  0xc04f8cf0 in db_command_loop () at
/usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:502
#4  0xc04fb640 in db_trap (type=, code=) at /usr/home/adrian/work/freebsd/head/src/sys/ddb/db_main.c:231
#5  0xc06c2bf4 in kdb_trap (type=, code=, tf=) at
/usr/home/adrian/work/freebsd/head/src/sys/kern/subr_kdb.c:654
#6  0xc093df67 in trap (frame=) at
/usr/home/adrian/work/freebsd/head/src/sys/i386/i386/trap.c:693
#7  0xc0926a7c in calltrap () at
/usr/home/adrian/work/freebsd/head/src/sys/i386/i386/exception.s:169
#8  0xc06c247d in kdb_enter (why=0xc09ba864 "panic", msg=)
at cpufunc.h:71
#9  0xc0687f61 in vpanic (fmt=, ap=)
at /usr/home/adrian/work/freebsd/head/src/sys/kern/kern_shutdown.c:739
#10 0xc0687e13 in kassert_panic (fmt=) at
/usr/home/adrian/work/freebsd/head/src/sys/kern/kern_shutdown.c:634
#11 0xc8f14751 in iwn_ampdu_tx_done (sc=0xc8f21000, qid=10, idx=, nframes=1, stat=) at
/usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3613
#12 0xc8f13eb5 in iwn5000_tx_done (sc=, desc=, data=) at
/usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3411
#13 0xc8f0b9ff in iwn_notif_intr (sc=0xc8f21000) at
/usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3696
#14 0xc8f0b2e0 in iwn_intr (arg=0xc8f21000) at
/usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3995
#15 0xc0655913 in intr_event_execute_handlers (ie=) at
/usr/home/adrian/work/freebsd/head/src/sys/kern/kern_intr.c:1252
#16 0xc0656213 in ithread_loop (arg=0xc85e6ee0) at
/usr/home/adrian/work/freebsd/head/src/sys/kern/kern_intr.c:1265
#17 0xc0652e2f in fork_exit (callout=0xc0656180 ) at
/usr/home/adrian/work/freebsd/head/src/sys/kern/kern_fork.c:977
#18 0xc0926b24 in fork_trampoline () at
/usr/home/adrian/work/freebsd/head/src/sys/i386/i386/exception.s:278
Current language:  auto; currently minimal
(kgdb) frame 11
#11 0xc8f14751 in iwn_ampdu_tx_done (sc=0xc8f21000, qid=10, idx=, nframes=1, stat=) at
/usr/home/adrian/work/freebsd/head/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3613
3613KASSERT(ni != NULL, ("no node"));
(kgdb) print ni
$1 = 
(kgdb) 

.. and leading up to it:

Unread portion of the kernel message buffer:
iwn0: iwn_tx_data: m=0xc9572900: seqno (53004) (12) != ring index (0) !
iwn0: iwn_tx_data: m=0xc896f200: seqno (53005) (13) != ring index (1) !
panic: no node
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper(c09bf552,ec2f29b8,fc,1000,0,...) at
db_trace_self_wrapper+0x2d/frame 0xec2f29a0
kdb_backtrace(c09fc9a7,1,c8f18b78,ec2f2a8c,ec2f2a30,...) at
kdb_backtrace+0x30/frame 0xec2f2a08
vpanic(c0af9f18,100,c8f18b78,ec2f2a8c,4000ace,...) at vpanic+0x11d/frame
0xec2f2a44
kassert_panic(c8f18b78,5,cdd25c00,cdd25c00,c8d6dc00,...) at
kassert_panic+0x153/frame 0xec2f2a80
iwn_ampdu_tx_done(0,1,cae8f028,c0671aa1,c8f2100c,...) at
iwn_ampdu_tx_done+0x251/frame 0xec2f2adc
iwn5000_tx_done(c8f21000,cae8f000,c8f3a934,bd2,c8f0dea0,...) at
iwn5000_tx_done+0xe5/frame 0xec2f2b20
iwn_notif_intr(c8f2101c,0,c8f18029,f5a,c0b07b80,...) at
iwn_notif_intr+0x4bf/frame 0xec2f2bd0
iwn_intr(c8f21000,c09b3975,4e0,c09b3b43,c09b3b68,...) at iwn_intr+0x7c0/frame
0xec2f2c3c
intr_event_execute_handlers(c7492bc0,c86c6480,c09b3975,55a,3c9,...) at
intr_event_execute_handlers+0xe3/frame 0xec2f2c80
ithread_loop(c85e6ee0,ec2f2d08,c09b367a,3c9,0,...) at ithread_loop+0x93/frame
0xec2f2ccc
fork_exit(c0656180,c85e6ee0,ec2f2d08) at fork_exit+0x7f/frame 0xec2f2cf4
fork_trampoline() at fork_trampoline+0x8/frame 0xec2f2cf4
--- trap 0, eip = 0, esp = 0xec2f2d40, ebp = 0 ---
KDB: enter: panic

.. so something went a little pear shaped and we didn't handle it right.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 185478] [iwi] [panic] panic in iwi0 driver

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185478

brea...@gmail.com changed:

   What|Removed |Added

 CC||brea...@gmail.com

--- Comment #2 from brea...@gmail.com ---
I, too, am having this issue.

Unread portion of the kernel message buffer:
wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost
panic: vm_fault: fault on nofault entry, addr: c8032000
cpuid = 0
KDB: stack backtrace:
#0 0xc0b3a082 at kdb_backtrace+0x52
#1 0xc0afce11 at panic+0x121
#2 0xc0d9863a at vm_fault_hold+0x1a4a
#3 0xc0d96bb2 at vm_fault+0x82
#4 0xc0ff36bb at trap_pfault+0x1bb
#5 0xc0ff2f07 at trap+0x677
#6 0xc0fdca4c at calltrap+0x6
#7 0xc07636fe at iwi_auth_and_assoc+0x4be
#8 0xc076304b at iwi_newstate+0x15b
#9 0xc0c112c5 at ieee80211_newstate_cb+0x175
#10 0xc0b482da at taskqueue_run_locked+0xea
#11 0xc0b48e77 at taskqueue_thread_loop+0xc7
#12 0xc0acbef3 at fork_exit+0xa3
#13 0xc0fdcaf4 at fork_trampoline+0x8
Uptime: 7h14m2s
Physical memory: 2014 MB
Dumping 156 MB: 141 125 109 93 77 61 45 29 13

Reading symbols from /boot/kernel/aio.ko.symbols...done.
Loaded symbols for /boot/kernel/aio.ko.symbols
Reading symbols from /boot/kernel/acpi_video.ko.symbols...done.
Loaded symbols for /boot/kernel/acpi_video.ko.symbols
Reading symbols from /boot/kernel/sem.ko.symbols...done.
Loaded symbols for /boot/kernel/sem.ko.symbols
Reading symbols from /boot/kernel/i915kms.ko.symbols...done.
Loaded symbols for /boot/kernel/i915kms.ko.symbols
Reading symbols from /boot/kernel/iicbb.ko.symbols...done.
Loaded symbols for /boot/kernel/iicbb.ko.symbols
Reading symbols from /boot/kernel/iicbus.ko.symbols...done.
Loaded symbols for /boot/kernel/iicbus.ko.symbols
Reading symbols from /boot/kernel/iic.ko.symbols...done.
Loaded symbols for /boot/kernel/iic.ko.symbols
Reading symbols from /boot/kernel/drm2.ko.symbols...done.
Loaded symbols for /boot/kernel/drm2.ko.symbols
Reading symbols from /boot/kernel/apm_saver.ko.symbols...done.
Loaded symbols for /boot/kernel/apm_saver.ko.symbols
Reading symbols from /boot/kernel/apm.ko.symbols...done.
Loaded symbols for /boot/kernel/apm.ko.symbols
Reading symbols from /boot/kernel/fdescfs.ko.symbols...done.
Loaded symbols for /boot/kernel/fdescfs.ko.symbols
Reading symbols from /boot/kernel/iwi_bss.ko.symbols...done.
Loaded symbols for /boot/kernel/iwi_bss.ko.symbols
Reading symbols from /boot/kernel/ums.ko.symbols...done.
Loaded symbols for /boot/kernel/ums.ko.symbols
Reading symbols from /boot/kernel/uhid.ko.symbols...done.
Loaded symbols for /boot/kernel/uhid.ko.symbols
#0  doadump (textdump=-957650816) at pcpu.h:233
233 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) #0  doadump (textdump=-957650816) at pcpu.h:233
#1  0xc0afca89 in kern_reboot (howto=260) at kern_shutdown.c:452
#2  0xc0afce4f in panic (fmt=) at kern_shutdown.c:759
#3  0xc0d9863a in vm_fault_hold (vaddr=3242895516, fault_type=1 '\001', 
fault_flags=, m_hold=)
at vm_fault.c:283
#4  0xc0d96bb2 in vm_fault (map=0xc1ec1000, vaddr=, 
fault_type=0 '\0', fault_flags=) at vm_fault.c:224
#5  0xc0ff36bb in trap_pfault (frame=, usermode=0, 
eva=3243337188) at trap.c:914
#6  0xc0ff2f07 in trap (frame=0xeb166ad8) at trap.c:532
#7  0xc0fdca4c in calltrap () at /usr/src/sys/i386/i386/exception.s:170
#8  0xc0c06786 in node_getrssi (ni=0xc8032000) at ieee80211_node.c:1100
#9  0xc07636fe in iwi_auth_and_assoc () at if_iwi.c:2910
#10 0xc076304b in iwi_newstate (vap=, 
nstate=) at if_iwi.c:997
#11 0xc0c112c5 in ieee80211_newstate_cb (xvap=0xc7e5d000, npending=1)
at ieee80211_proto.c:1756
#12 0xc0b482da in taskqueue_run_locked (queue=0xc7ad2480)
at subr_taskqueue.c:342
#13 0xc0b48e77 in taskqueue_thread_loop (arg=0xc7ad50a4)
at subr_taskqueue.c:563
#14 0xc0acbef3 in fork_exit (callout=0xc0b48db0 )
at kern_fork.c:995
#15 0xc0fdcaf4 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:279
Current language:  auto; currently minimal

FreeBSD keyhole 10.0-STABLE FreeBSD 10.0-STABLE #0 r269844: Tue Aug 12 15:30:35
CDT 2014 root@keyhole:/usr/obj/usr/src/sys/GENERIC  i386

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] New: [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

Bug ID: 192950
   Summary: [iwn] Centrino Advanced-N 6205 slow on 11n, better on
11g
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: dieterich@gmail.com

Above mentioned WLAN NIC only manages a maximum upload of 900 kB/s on an 11n
network on the 2.4 GHz band in my tests. By recommendation of adrian@, removing
ht and falling back to 11g mode improves the upload speed to 1.9 MB/s and
download to 2.9 MB/s.

Please see the thread on freebsd-wireless at
http://lists.freebsd.org/pipermail/freebsd-wireless/2014-August/004907.html for
a more detailed description of the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #1 from Adrian Chadd  ---
Ok, I'll start adding some more debugging to iwn(4) in HEAD and let you know
when I'm ready to debug this.

If I forget / move onto something else, here's what I'm going to look at (in
order):

* RXON config - antennas, MIMO, etc;
* TX config - link quality setup, PLCP antenna config;

There's other mismatches I've found in the way the antennas are setup and ..
well, it's still a mess. Sigh.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #2 from Hiren Panchasara  ---
(In reply to Adrian Chadd from comment #1)
> Ok, I'll start adding some more debugging to iwn(4) in HEAD and let you know
> when I'm ready to debug this.

I also have 6205:
iwn0@pci0:3:0:0:class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34
hdr=0x00
vendor = 'Intel Corporation'
device = 'Centrino Advanced-N 6205 [Taylor Peak]'
class  = network

> 
> If I forget / move onto something else, here's what I'm going to look at (in
> order):
> 
> * RXON config - antennas, MIMO, etc;
> * TX config - link quality setup, PLCP antenna config;

If possible, can you please share how are you going to debug these?

> 
> There's other mismatches I've found in the way the antennas are setup and ..
> well, it's still a mess. Sigh.

I'd like to follow how you debug this and would like to document it.

Thanks a lot in advance.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #3 from Hiren Panchasara  ---
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: flags=8843 metric 0 mtu 1500
ether 08:11:96:f9:b2:ec
inet 192.168.1.116 netmask 0xff00 broadcast 192.168.1.255 
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid Point100 channel 1 (2412 MHz 11g ht/20) bssid dc:9f:db:6a:3e:9e
country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF
TKIP 2:128-bit TKIP 3:128-bit txpower 11 bmiss 10 scanvalid 60 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS
ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme
roaming MANUAL

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #4 from Hiren Panchasara  ---
(In reply to Hiren Panchasara from comment #3)
> 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.
> 

Okay, experiment above was wifi(laptop) to ethernet(freebsd router) on the same
n/w.

When I installed iperf on my android and did the same experiment, I am barely
getting 500kbps. 

 % ifconfig wlan0 list sta 
ADDR   AID CHAN RATE RSSI IDLE  TXSEQ  RXSEQ CAPS FLAG   
dc:9f:db:6a:3e:9e31   7M 25.00  15443   6288 EPS  AQEHTRS RSN WME
HTCAP ATH

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #5 from Adrian Chadd  ---
Hiren - oh you went iperf from STA -> AP -> STA? That's going to suck for lots
of reasons.

You should get more than 3mbit/sec iperfing STA->AP->ethernet.

Do this:

* add IWN_DEBUG and IEEE80211_DEBUG to kernel, recompile
* sysctl dev.iwn.0.debug=1
* wlandebug +rate
* log some stuff
* post it here



-a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #6 from Hiren Panchasara  ---
Created attachment 146235
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146235&action=edit
wifi debug 1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #7 from Hiren Panchasara  ---
Created attachment 146236
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146236&action=edit
wifi debug 2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #8 from Hiren Panchasara  ---
(In reply to Adrian Chadd from comment #5)
> Hiren - oh you went iperf from STA -> AP -> STA? That's going to suck for
> lots of reasons.
> 
> You should get more than 3mbit/sec iperfing STA->AP->ethernet.
> 
> Do this:
> 
> * add IWN_DEBUG and IEEE80211_DEBUG to kernel, recompile
> * sysctl dev.iwn.0.debug=1
> * wlandebug +rate
> * log some stuff
> * post it here

On my freebsd router on lan:
hirenp@entry:~ % iperf -s -u -i1

and on the laptop on wifi:
flymockour-l7% iperf -c 192.168.1.1 -u -i1 -l1300 -b110m -t10

I see about 3Mbps.

Logs attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #9 from Adrian Chadd  ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #10 from Hiren Panchasara  ---
(In reply to Adrian Chadd from comment #9)
> (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.

Are you talking about following portion of logs?

Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: 1stream
antenna=0x01, 2stream antenna=0x03, ntxstreams=2
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=0, txrate=7,
rate=0x87
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=1, txrate=6,
rate=0x86
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=2, txrate=5,
rate=0x85
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=3, txrate=4,
rate=0x84
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=4, txrate=3,
rate=0x83
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=5, txrate=2,
rate=0x82
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=6, txrate=1,
rate=0x81
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=7, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=8, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=9, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=10, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=11, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=12, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=13, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=14, txrate=0,
rate=0x80
Aug 24 15:43:42 flymockour-l7 kernel: iwn_set_link_quality: i=15, txrate=0,
rate=0x80

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #11 from Hiren Panchasara  ---
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
Aug 24 15:43:44 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 2 retries 6
nkill 0 rate 80004103 duration 1280 status 201

So, is 80004103 the rate its selecting to send?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #12 from Hiren Panchasara  ---
Tried to follow the rabbit-hole to see where rate is coming from:

Index: if_iwn.c
===
--- if_iwn.c(revision 269621)
+++ if_iwn.c(working copy)
@@ -4281,6 +4281,8 @@
rate = ni->ni_txrate;
}

+   DPRINTF(sc, IWN_DEBUG_XMIT, "tx rate is: %d in %s \n", rate, __func__);
+
/* Encrypt the frame if need be. */
if (wh->i_fc[1] & IEEE80211_FC1_PROTECTED) {
/* Retrieve key for TX. */

via this codepath:

ieee80211_set_basic_htrates() 
ieee80211_add_htinfo_body()
amrr_rate()
.ir_rate
ieee80211_ratectl_rate()
iwn_tx_data()

In the logs, I get:

Aug 24 16:59:35 flymockour-l7 kernel: tx rate is: 128 in iwn_tx_data

Which I think is:
807 #define IEEE80211_RATE_BASIC0x80

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #13 from Hiren Panchasara  ---
Adrian,

I still couldn't find out where the "step up" in rates should happen and how it
should look like. i.e. is there an array of speeds it should step up to?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #14 from Adrian Chadd  ---
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 specified by the rate control code - but
again, I can't be sure, because I haven't really sat down and figured out what
the rate code does.

Ie, if you do this:

* link quality table has MCS0-7 in it;
* you set a rate of MCS8 in the TX frame, btu also say "do link quality
retries"

then what happens.

The default rate module for iwn is amrr. It's in net80211. That's what should
be outputting debugging when you enable wlandebug +rate.


-a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #15 from Adrian Chadd  ---
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 believing the correct thing to do is continue
bumping up the rate.

If you enable IEEE80211_DEBUG in your kernel config, rebuild, then enable
debugging via 'wlandebug +rate', you'll likely see the MCS rate continue
climbing towards MCS7 or MCS15. This only works in a very clean environment -
definitely not with 2GHz.

If you compile with IWN_DEBUG, then sysctl dev.iwn.0.debug=0x1, you'll see
information about transmissions and transmit completions. You'll likely see the
TX PLCP climb to MCS rate 0xf (MCS15) - with the retry and duration counts will
be very high.

I'm not sure if there's a quick fix. I think I'm going to have to add some 11n
awareness to the ratectl API (ie, so we can tell it how many retries, how many
successes, how many failures, the transmit duration) and then ensure it really
is being called upon completion of each sent frame - aggregate or otherwise.

As for the driver - there seems to be multiple places where frame transmisson
completes and the rate control code gets called. I'll have to audit these to
ensure it's, well, "right".

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] New: wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

Bug ID: 193044
   Summary: wpi driver keeps switching between 2.4 Ghz and 5 Ghz
band
   Product: Base System
   Version: 10.0-RELEASE
  Hardware: amd64
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: chris.vansteenla...@telenet.be

Using a Intel 3945ABG Wireless chip inside a Sony Vaio laptop.
My wireless router is configured as dualband for my ssid.

The driver finds the ssid. If it's on the 2.4 GHz band, it stays connected for
a while but than disconnects and switches to the 5GHz band, which is not
supported by Intel 3945ABG, so it disconnects, connects back to the 2.4 Ghz
band and so fort ...

Link to discussion I had with the developer via the wireless mailing list :



-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

Hiren Panchasara  changed:

   What|Removed |Added

 CC||hi...@freebsd.org

--- Comment #1 from Hiren Panchasara  ---
I see similar behavior on iwn 6205 too.

It keeps trying 5GHz and only goes to 2.4Ghz when I do "ifconfig wlan0 channel
1:ht/20"

It should at least try 2.4 after X number of unsuccessful retries on 5Ghz.

Aug 26 09:53:15 flymockour-l7 kernel: iwn0: 
mem 0xf510-0xf5101fff irq 17 at device 0.0 on pci3
Aug 26 09:53:26 flymockour-l7 kernel: ifa_del_loopback_route: deletion failed:
48
Aug 26 09:53:27 flymockour-l7 wpa_supplicant[43306]: Successfully initialized
wpa_supplicant
Aug 26 09:53:27 flymockour-l7 kernel: wlan0: Ethernet address:
08:11:96:f9:b2:ec
Aug 26 09:53:27 flymockour-l7 kernel: iwn0: iwn_read_firmware: ucode
rev=0x12a80601
Aug 26 09:53:30 flymockour-l7 wpa_supplicant[43307]: wlan0: Trying to associate
with 6c:f3:7f:67:ac:57 SSID='Y!Office' freq=5805 MHz)
Aug 26 09:53:38 flymockour-l7 hirenp: /etc/rc.d/dhclient: WARNING: failed to
start dhclient
Aug 26 09:53:40 flymockour-l7 wpa_supplicant[43307]: wlan0: Authentication with
6c:f3:7f:67:ac:57 timed out.
Aug 26 09:53:40 flymockour-l7 wpa_supplicant[43307]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:67:ac:57 reason=3 locally_generated=1
Aug 26 09:53:43 flymockour-l7 wpa_supplicant[43307]: wlan0: Trying to associate
with 6c:f3:7f:4d:89:37 (SSID='Y!Office' freq=5745 MHz)
Aug 26 09:53:53 flymockour-l7 wpa_supplicant[43307]: wlan0: Authentication with
6c:f3:7f:4d:89:37 timed out.
Aug 26 09:53:53 flymockour-l7 wpa_supplicant[43307]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:4d:89:37 reason=3 locally_generated=1
Aug 26 09:53:56 flymockour-l7 wpa_supplicant[43307]: wlan0: Trying to associate
with 6c:f3:7f:67:ac:47 (SSID='Y!Office' freq=2462 MHz)
Aug 26 09:54:06 flymockour-l7 wpa_supplicant[43307]: wlan0: Authentication with
6c:f3:7f:67:ac:47 timed out.
Aug 26 09:54:06 flymockour-l7 wpa_supplicant[43307]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:67:ac:47 reason=3 locally_generated=1
Aug 26 09:54:09 flymockour-l7 wpa_supplicant[43307]: wlan0: Trying to associate
with 6c:f3:7f:4d:89:17 (SSID='Y!Office' freq=5220 MHz)
Aug 26 09:54:19 flymockour-l7 wpa_supplicant[43307]: wlan0: Authentication with
6c:f3:7f:4d:89:17 timed out.
Aug 26 09:54:19 flymockour-l7 wpa_supplicant[43307]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:4d:89:17 reason=3 locally_generated=1
Aug 26 09:54:19 flymockour-l7 wpa_supplicant[43307]: wlan0: Trying to associate
with 6c:f3:7f:4f:a4:a7 (SSID='Y!Office' freq=2412 MHz)
Aug 26 09:54:19 flymockour-l7 wpa_supplicant[43307]: wlan0: Associated with
6c:f3:7f:4f:a4:a7

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #2 from Adrian Chadd  ---
It's supported by the 3945ABG, but the driver isn't entirely correct.

The driver needs to buffer frames until the firmware says "yup, I've heard a
beacon" and then retry them.

iwn has the same problem with 5ghz.

-a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

--- Comment #3 from Hiren Panchasara  ---
(In reply to Adrian Chadd from comment #2)
> It's supported by the 3945ABG, but the driver isn't entirely correct.
> 
> The driver needs to buffer frames until the firmware says "yup, I've heard a
> beacon" and then retry them.
> 
> iwn has the same problem with 5ghz.

Agree. it should not jump around as being reported in this bug, right?

IMO by default, it should try 5GHz first and if that doesn't work, try 2.4 GHz
and stick to it till the session life-time. And should not jump back and forth. 

Please correct me if that's a wrong expectation.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

--- Comment #4 from Adrian Chadd  ---
Right; I have no idea why the wpi firmware keeps disassociating.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

--- Comment #5 from chris.vansteenla...@telenet.be ---
I do not know if this is related but the associating/disassociating also takes
place when you limit the interface to one band. By doing a 'ifconfig wlan0 mode
11g', my wireless only looks for the 2.4 Ghz. It associates correctly, then
disconnects, reconnects and so on. This happens about every 2 minutes in my
case.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193044] wpi driver keeps switching between 2.4 Ghz and 5 Ghz band

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193044

--- Comment #6 from Adrian Chadd  ---
Well, we need to figure out why the firmware is disconnecting in the first
place. I'll see if I can find one of these NICs in my collection.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193087] New: [iwn] port over the rate control and antenna selection bits from Linux for the various bluetooth coexistence code

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193087

Bug ID: 193087
   Summary: [iwn] port over the rate control and antenna selection
bits from Linux for the various bluetooth coexistence
code
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

The Linux intel driver (iwlwifi) has a bunch of code to limit the antenna
selection when bluetooth coexistence is configured.

All of that needs to be ported/debugged.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193402] New: [ath] AR9227 hang: ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193402

Bug ID: 193402
   Summary: [ath] AR9227 hang: ar5416PerCalibrationN: NF
calibration didn't finish; delaying CCA
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: alex.dei...@gmail.com

FreeBSD 11.0-CURRENT r270733M amd64, PCI / Atheros 9227, 802.11n hostap mode
Time to time network traffic between clients and AP stops:

Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
off, 1 sta's in ps mode
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] ath_rate_findrate:
switching quickly..
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd]
ath_rate_tx_complete: size 1600 (519 bytes) OK rate/short/long 7 MCS/0/1
nframes/nbad [1/0]
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
on, 2 sta's in ps mode
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
off, 1 sta's in ps mode
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
on, 2 sta's in ps mode
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
off, 1 sta's in ps mode
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] ath_rate_findrate:
switching quickly..
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd]
ath_rate_tx_complete: size 1600 (305 bytes) OK rate/short/long 7 MCS/0/1
nframes/nbad [1/0]
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] ath_rate_findrate:
switching quickly..
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd]
ath_rate_tx_complete: size 250 (114 bytes) OK rate/short/long 4 MCS/0/1
nframes/nbad [1/0]
Sep  5 16:18:31 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
on, 2 sta's in ps mode
Sep  5 16:18:32 blackbird kernel: wlan0: [84:7a:88:70:c6:cd] power save mode
off, 1 sta's in ps mode

it is the same case with all clients: android, windows, FreeBSD.
Workaround - reboot AP system :-(


athstats:
317346   data frames received
432914   data frames transmit
543  tx frames with an alternate rate
29708short on-chip tx retries
41739long on-chip tx retries
5700 tx failed 'cuz too many retries
17   stuck beacon conditions
MCS4 current transmit rate
3tx stopped 'cuz no xmit buffer
209  tx failed 'cuz destination filtered
2061 tx frames with no ack marked
421765   tx frames with short preamble
13990rx failed 'cuz of bad CRC
1rx failed 'cuz frame too short
1rx failed 'cuz of PHY err
1illegal service
162287   beacons transmitted
554  periodic calibrations
-0/+0TDMA slot adjust (usecs, smoothed)
50   rssi of last ack
33   avg recv rssi
-96  rx noise floor
9348 tx frames through raw api
205506   A-MPDU sub-frames received
120913   Half-GI frames received
751  CRC errors for non-last A-MPDU subframes
172  CRC errors for last subframe in an A-MPDU
1Frames received w/ STBC encoding
97566Frames transmitted with HT Protection
6407 Number of frames retransmitted in software
336  Number of frames exceeding software retry
178990   A-MPDU sub-frame TX attempt success
5884 A-MPDU sub-frame TX attempt failures
900  A-MPDU TX frame failures
1514 cabq frames transmitted
137  cabq xmit overflowed beacon interval
1OFDM weak signal detect
189  listen time
33   ANI disabled OFDM weak signal detect
741238   cumulative OFDM phy error count
346722   cumulative CCK phy error count
677  ANI forced listen time to zero
35612missing ACK's
50495RTS without CTS
73359successful RTS
19322bad FCS
21   average rssi (beacons only)
Antenna profile:
[0] tx   277449 rx 7401
[1] tx0 rx   309945

wlan interface hang with messages:

Sep  6 13:26:19 blackbird kernel: ar5416PerCalibrationN: NF calibration
didn't finish; delaying CCA
Sep  6 13:26:49 blackbird kernel: ar5416PerCalibrationN: NF calibration
didn't finish; delaying CCA
Sep  6 13:27:19 blackbird kernel: ar5416PerCalibrationN: NF calibration
didn't finish; delaying CCA
Sep  6 13:27:49 blackbird kernel: ar5416PerCalibrationN: NF calibration
didn't finish; delaying CCA

and clients can not connect.

sysctl dev.ath.0.txagg=1 output:

Sep  6 13:29:28 blackbird kernel: no tx bufs (empty list): 0
Sep  6 13:29:28 blackbird kernel: no tx bufs (was busy): 0
Sep  6 13:29:28 blackbird kernel: aggr single packet: 159053
Sep  6 13:29:28 blackbird kernel: aggr single packet w/ BAW closed: 4291
Sep  6 13:29:28 blackbird kernel

[Bug 193402] [ath] AR9227 hang: ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193402

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #1 from Adrian Chadd  ---
I think that calibration hang means the baseband has gone RX deaf.

I wonder if a full chip reset will fix it, rather than a warm chip reset. I'll
have to go experiment.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #17 from Adrian Chadd  ---
Also, please test out with the latest -HEAD and see if it behaves better for
you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #16 from Adrian Chadd  ---
r270738 fixed some antenna stuff.
r270742 fixed AMPDU completion notification to AMRR.

This _should_ be better (and it is for me!) but Hiren still reports oddness.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #18 from Hiren Panchasara  ---
Noticing only 400kbps on ssh from laptop to desktop on wifi.

root@flymockour-l7:/home/hirenp/head/sys/net80211 # sysctl dev.iwn.0.debug=0xff
dev.iwn.0.debug: 0 -> 255
root@flymockour-l7:/home/hirenp/head/sys/net80211 # wlandebug +rate
net.wlan.0.debug: 0x0 => 0x20

I see the rate is stuck at 0x0080.

Here are logs to send packet no: 1614 to 1616 - just for example.

I've added following printf to see if on successful transfer, ratectl code is
getting trigger to ++ the rate. It seems to be firing but not doing the right
thing.

Index: if_iwn.c
===
--- if_iwn.c(revision 270821)
+++ if_iwn.c(working copy)
@@ -3500,10 +3500,12 @@
 */
if (status & IWN_TX_FAIL) {
ifp->if_oerrors++;
+   DPRINTF(sc, IWN_DEBUG_XMIT, "->%s Not updating rate control
if_opackets: %lu\n", __func__, ifp->if_opackets);
ieee80211_ratectl_tx_complete(vap, ni,
IEEE80211_RATECTL_TX_FAILURE, &ackfailcnt, NULL);
} else {
ifp->if_opackets++;
+   DPRINTF(sc, IWN_DEBUG_XMIT, "->%s updating rate control if_opackets:
%lu\n", __func__, ifp->if_opackets);
ieee80211_ratectl_tx_complete(vap, ni,
IEEE80211_RATECTL_TX_SUCCESS, &ackfailcnt, NULL);
}

Logs:

64190 Sep  6 18:27:57 flymockour-l7 kernel: ->iwn_tx_done updating rate control
if_opackets: 1613
64191 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=63; qid 6 idx
154 flags 0 type 192(RX_PHY) len 68
64192 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=0; qid 6 idx
155 flags 0 type 193(MPDU_RX_DONE) len 168
64193 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 55 rssi 9766
11051 0 result -56
64194 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=1; qid 6 idx
156 flags 0 type 192(RX_PHY) len 68
64195 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=2; qid 6 idx
157 flags 0 type 193(MPDU_RX_DONE) len 336
64196 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 29 rssi 4884
5399 0 result -50
64197 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=3; qid 6 idx
158 flags 0 type 157(BEACON_STATS) len 528
64198 Sep  6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta:
102; cck=48, ofdm=2, ht=0, total=152, thresh=5100
64199 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=4; qid 9 idx 1
flags 0 type 168(IWN_CMD_SET_SENSITIVITY) len 4
64200 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=5; qid 6 idx
159 flags 0 type 192(RX_PHY) len 68
64201 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=6; qid 6 idx
160 flags 0 type 193(MPDU_RX_DONE) len 120
64202 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 56 rssi 10023
11308 0 result -56
64203 Sep  6 18:27:57 flymockour-l7 kernel: iwn_start_locked: called
64204 Sep  6 18:27:57 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 63 len 80
nsegs 2 flags 0x00100018 rate 0x0080 plcp 0x4100
64205 Sep  6 18:27:57 flymockour-l7 kernel: iwn_start_locked: done
64206 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=7; qid 0 idx 63
flags 0 type 28(TX_DONE) len 44
64207 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 63
retries 0 nkill 0 rate 80004100 duration 296 status 201
64208 Sep  6 18:27:57 flymockour-l7 kernel: ->iwn_tx_done updating rate control
if_opackets: 1614
64209 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=8; qid 6 idx
172 flags 0 type 192(RX_PHY) len 68
64210 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=9; qid 6 idx
173 flags 0 type 193(MPDU_RX_DONE) len 336
64211 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 28 rssi 4627
5399 0 result -49
64212 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=10; qid 6 idx
174 flags 0 type 157(BEACON_STATS) len 528
64213 Sep  6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta:
102; cck=11, ofdm=0, ht=0, total=113, thresh=5100
64214 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=11; qid 6 idx
183 flags 0 type 192(RX_PHY) len 68
64215 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=12; qid 6 idx
184 flags 0 type 193(MPDU_RX_DONE) len 336
64216 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 30 rssi 3858
5398 0 result -52
64217 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=13; qid 6 idx
185 flags 0 type 157(BEACON_STATS) len 528
64218 Sep  6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta:
103; cck=36, ofdm=0, ht=0, total=139, thresh=5150
64219 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=14; qid 6 idx
188 flags 0 type 192(RX_PHY) len 68
64220 Sep  6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=15; qid 6 idx
189 flags 0 type 193(MPDU_RX_DONE) len 120
64221 Sep  6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 55 rssi 9765
11051

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #19 from Adrian Chadd  ---
wlandebug +rate

what happens?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #20 from Hiren Panchasara  ---
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: [dc:9f:db:6a:3e:9e]
AMRR: current rate 0, txcnt=11, retrycnt=20
18:55 < hiren> Sep  6 18:55:20 flymockour-l7 kernel: wlan0: [dc:9f:db:6a:3e:9e]
AMRR: current rate 0, txcnt=11, retrycnt=21

I guess because of this much retries rate is not going up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

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 much improved.
Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I can
run more detailed tests if you wish, but I am more than happy with the status
as is.

Thanks so much for your work on this! :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #22 from Hiren Panchasara  ---
(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 see if it behaves better for
> > you.
> Just installed r271215 and can confirm that the situation is much improved.
> Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I
> can run more detailed tests if you wish, but I am more than happy with the
> status as is.

Are you connecting at 11g? Can you paste ifconfig o/p? 
It'd be nice to see what rate does it go up to? (with wlandebug +rate)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

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 see if it behaves better 
> > > for
> > > you.
> > Just installed r271215 and can confirm that the situation is much improved.
> > Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I
> > can run more detailed tests if you wish, but I am more than happy with the
> > status as is.
> 
> Are you connecting at 11g? Can you paste ifconfig o/p? 
> It'd be nice to see what rate does it go up to? (with wlandebug +rate)
No, this should be 11n (on the 2.4 GHz band and w/ only 20 MHz channel width,
though) as I explicitly configured the access point to not support anything but
11n.

ifconfig:
wlan0: flags=8843 metric 0 mtu 1500
ether XX
inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255 
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid XX channel 10 (2457 MHz 11g ht/20) bssid XXX
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
TKIP 2:128-bit TKIP 3:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS
ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme
roaming MANUAL

wlandebug + rate:
Sep  7 13:51:54  kernel: wlan0: [] AMRR: current rate 15, txcnt=36, retrycnt=11
Sep  7 13:51:54  kernel: wlan0: [] AMRR: current rate 15, txcnt=37, retrycnt=2
Sep  7 13:51:55  kernel: wlan0: [] AMRR: current rate 15, txcnt=37, retrycnt=6
Sep  7 13:51:55  kernel: wlan0: [] AMRR: current rate 15, txcnt=34, retrycnt=1
Sep  7 13:51:56  kernel: wlan0: [] AMRR: current rate 15, txcnt=38, retrycnt=8
Sep  7 13:51:56  kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=2
Sep  7 13:51:57  kernel: wlan0: [] AMRR: current rate 15, txcnt=39, retrycnt=5
Sep  7 13:51:57  kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=10
Sep  7 13:51:58  kernel: wlan0: [] AMRR: current rate 15, txcnt=38, retrycnt=20
Sep  7 13:51:58  kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=38
retrycnt=20)
Sep  7 13:51:58  kernel: wlan0: [] AMRR: current rate 14, txcnt=38, retrycnt=5
Sep  7 13:51:59  kernel: wlan0: [] AMRR: current rate 14, txcnt=35, retrycnt=4
Sep  7 13:51:59  kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6
Sep  7 13:52:00  kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=1
Sep  7 13:52:00  kernel: wlan0: [] AMRR increasing rate 15 (txcnt=32
retrycnt=1)
Sep  7 13:52:00  kernel: wlan0: [] AMRR: current rate 15, txcnt=31, retrycnt=12
Sep  7 13:52:00  kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=31
retrycnt=12)
Sep  7 13:52:01  kernel: wlan0: [] AMRR: current rate 14, txcnt=36, retrycnt=3
Sep  7 13:52:01  kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6
Sep  7 13:52:02  kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=5
Sep  7 13:52:02  kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6
Sep  7 13:52:03  kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=5
Sep  7 13:52:03  kernel: wlan0: [] AMRR: current rate 14, txcnt=35, retrycnt=8
Sep  7 13:52:04  kernel: wlan0: [] AMRR: current rate 14, txcnt=30, retrycnt=6
Sep  7 13:52:04  kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=0
Sep  7 13:52:04  kernel: wlan0: [] AMRR increasing rate 15 (txcnt=33
retrycnt=0)
Sep  7 13:52:05  kernel: wlan0: [] AMRR: current rate 15, txcnt=26, retrycnt=5
Sep  7 13:52:05  kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=12
Sep  7 13:52:05  kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=33
retrycnt=12)
Sep  7 13:52:06  kernel: wlan0: [] AMRR: current rate 14, txcnt=30, retrycnt=8
Sep  7 13:52:06  kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=5
Sep  7 13:52:07  kernel: wlan0: [] AMRR: current rate 14, txcnt=27, retrycnt=2
Sep  7 13:52:07  kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=9
Sep  7 13:52:08  kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=3
Sep  7 13:52:09  kernel: wlan0: [] AMRR: current rate 14, txcnt=27, retrycnt=1
Sep  7 13:52:09  kernel: wlan0: [] AMRR increasing rate 15 (txcnt=27
retrycnt=1)
Sep  7 13:52:09  kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=9
Sep  7 13:52:10  kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=8
Sep  7 13:52:10  kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=7
Sep  7 13:52:11  kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=8
Sep  7 13:52:11  kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=11
Sep  7 13:52:12  kernel: wlan0: [] AMRR: current rate 15, txcnt=31, retrycnt=11
Sep  7 13:52:12  kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=31
retrycnt=11)
Sep  7 13:52:12  kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retry

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

Lars Engels  changed:

   What|Removed |Added

 CC||l...@freebsd.org

--- Comment #24 from Lars Engels  ---
To jump in: I'm not having problems on yesterday's HEAD using an 6205:

ubuntu-14.04.1-server-amd64.iso 6.4 MB/s - 195 MB of 572 MB, 59 secs left


wlan0: flags=8843 metric 0 mtu 1500
ether 60:67:20:xx:xx:xx
inet 192.168.0.11 netmask 0xff00 broadcast 192.168.0.255 
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid hafenkneipe24GHz channel 1 (2412 MHz 11g ht/20) bssid
c4:27:95:xx:xx:xx
regdomain ETSI country DE authmode WPA2/802.11i privacy ON
deftxkey UNDEF TKIP 2:128-bit txpower 50 bmiss 10 scanvalid 60 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS
ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme
roaming MANUAL

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

--- Comment #25 from Hiren Panchasara  ---
wow, I so envy you guys :-)

I've a similar setting but not getting anything more than 400kbps. So weird.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193458] New: can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458

Bug ID: 193458
   Summary: can not connect reliable to Wifi AP with WPA-PSK /
WPA-EAP
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: i386
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: g...@unixarea.de

$ uname -a
FreeBSD tiny-r269739 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r269739M: Fri Aug 15
18:07:41 CEST 2014 guru@vm-tiny-r269739:/usr/obj/usr/src/sys/GENERIC  i386

Wifi NIC:

urtwn0:  on
usbus4
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
wlan0: Ethernet address: 80:1f:02:ee:16:37

# cat /etc/wpa_supplicant.conf
#
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1

# Hotel Wieserhof
#
network={
ssid="Naturhotel Wieserhof"
scan_ssid=1
# key_mgmt=WPA-PSK WPA-EAP IEEE8021X
key_mgmt=WPA-PSK
# key_mgmt=WPA-PSK WPA-EAP
psk="N@tur%Wieser"
# key_mgmt=NONE
# wep_tx_keyidx=0
# wep_key0="N@tur%Wieser"
}

note: credentials have been was by local hotel management staff as:
Wi-Fi: Naturhotel Wieserhof
Password: N@tur%Wieser
i.e. the credentials are correct and the SSID was visible with ifconfig wlan0
list scan


WPA started as:

# /usr/sbin/wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf -D bsd

connection (associating, IP by DHCP) was only sometimes possible far away from
the AP (in the hotel room, where the staff said it is not supposed to work),
and was never possible near the AP (in the lobby, where it was supposed to
work);

I tested the various combinations, the best was what is visible above as aktive
lines;

I will attach log files;

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193458] can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458

--- Comment #1 from Matthias Apitz  ---
Created attachment 147057
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147057&action=edit
wpa debug log

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193458] can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458

--- Comment #2 from Matthias Apitz  ---
Created attachment 147058
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147058&action=edit
wpa debug log (2)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193512] New: ath0: bb hang detected (0x1), resetting for AR9287

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193512

Bug ID: 193512
   Summary: ath0: bb hang detected (0x1), resetting for AR9287
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: artyom.mirgorod...@gmail.com

Sometime I receive this message on one of access point:
ath0: bb hang detected (0x1), resetting
After that connection restored only if I turn off wifi by hard button and turn
on again.

ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR9287 mac 384.2 RF5133 phy 15.15
ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950

dieterich@gmail.com changed:

   What|Removed |Added

 Status|Needs Triage|Issue Resolved
 Resolution|--- |FIXED

--- Comment #26 from dieterich@gmail.com ---
Is fixed for me, trying to clean up. Please (@hiren) reopen if you feel that is
required.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193569] New: [iwn] [wpi] 5GHz association fails on passive channels

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193569

Bug ID: 193569
   Summary: [iwn] [wpi] 5GHz association fails on passive channels
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

The TL;DR is this:

* 5GHz passive channels require the station to hear a beacon from an AP doing
DFS before it transmits anything;
* so net80211 does this;
* then it tries to associate;
* .. and iwn/wpi will just issue a new RXON to associate, clearing the firmware
state
* which includes that it's seen beacons;
* so then it transmits a frame (association request);
* and the firmware immediately fails it with some status code (IWN_TX_*) that
says "nope, need to see a beacon first."

I forget the status code but it's pretty easy to see with 'sysctl
dev.iwn.0.debug=0x1' when associating on a 5GHz channel.

What the linux iwlwifi driver does - and what I think we should do - is this:

* have a per-vap buffer of temporarily failed frames;
* (not per-node; it's not required for this NIC);
* if we see a TX fail for this reason, don't free the mbuf - just append it to
the vap retry queue - and set some flag + channel number;
* upon receiving a beacon notification - if it's for a beacon on the currently
associated channel then schedule a taskqueue to flush that queue;
* .. then flush this queue as appropriate in iwn_newstate().
* .. and make sure the taskqueue is cancelled during state changes,
suspend/resume, etc.

the flush may get complicated - we should flush it if we transition away from
RUN. Just make sure it works. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193588] New: [PATCH] Staged malo(4) firmware module

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588

Bug ID: 193588
   Summary: [PATCH] Staged malo(4) firmware module
   Product: Base System
   Version: 10.0-RELEASE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: lis...@club.fr

Created attachment 147248
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147248&action=edit
Staging patch for Makefile

Installing the malo(4) firmware kernel module fails with:

===>   Registering installation for malo-firmware-kmod-3.0.0.39_1
pkg-static: lstat(/root/malo-firmware-1.4/work/stage/boot/modules/malofw.ko):
No suuh file or directory
*** Error code 74

Please find attached patch for staging this port and resolving the issue.

The original port was downloaded, as for malo(4) manual, from:
http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz

NOTE: I’m far from understanding throughly how this (or any other) Makefile
works, but the proposed patch works in my set up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193588] [PATCH] Staged malo(4) firmware module

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org
  Component|wireless|Individual Port(s)
Version|10.0-RELEASE|Latest
   Assignee|freebsd-wirel...@freebsd.or |freebsd-ports-bugs@FreeBSD.
   |g   |org
Product|Base System |Ports Tree

--- Comment #1 from Adrian Chadd  ---
Hi!

This is a ports thing! I'd like some help!

Thanks!

-a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[FreeBSD Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193628] Marvell 88W8335 wireless NIC not enabled by malo(4) or ndis(4)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193628

Carlos Jacobo Puga Medina  changed:

   What|Removed |Added

 CC||freebsd-wirel...@freebsd.or
   ||g

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193588] [PATCH] Staged malo(4) firmware module

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588

Carlos Jacobo Puga Medina  changed:

   What|Removed |Added

 CC||freebsd-wirel...@freebsd.or
   ||g

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Problem reports for freebsd-wireless@FreeBSD.org that need special attention

[bugzilla-noreply]

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+-
Needs MFC   |140567 | [ath] [patch] ath is not worked on my notebook  
Needs MFC   |154598 | [ath] Atheros 5424/2424 can't connect to WPA ne 
Needs MFC   |163312 | [panic] [ath] kernel panic: page fault with ath 
Needs MFC   |166190 | [ath] TX hangs and frames stuck in TX queue 
Needs MFC   |166357 | [ath] 802.11n TX stall when the first frame in  
Needs MFC   |166642 | [ieee80211] [patch] in 802.11n mode for FreeBSD 
Needs MFC   |169362 | [ath] AR5416: radar pulse PHY errors sometimes  

7 problems total for which you should take action.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193788] New: Intel WiFi Dual Band 7260 NIC not supported

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193788

Bug ID: 193788
   Summary: Intel WiFi Dual Band 7260 NIC not supported
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: ohart...@zedat.fu-berlin.de

The Intel DualBand WiFi 7260 NIC is not supported by most recent CURRENT:

none2@pci0:4:0:0:   class=0x028000 card=0x42628086 chip=0x08b28086 rev=0x73
hdr=0x00
vendor = 'Intel Corporation'
class  = network
bar   [10] = type Memory, range 64, base 0xf0c0, size 8192, enabled
cap 01[c8] = powerspec 3  supports D0 D3  current D0
cap 05[d0] = MSI supports 1 message, 64 bit 
cap 10[40] = PCI-Express 2 endpoint max data 128(128) FLR link x1(x1)
 speed 2.5(2.5) ASPM L1(L0s/L1)
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
ecap 0003[140] = Serial 1 ac7ba1a06fd6
ecap 0018[14c] = LTR 1
ecap 000b[154] = Vendor 1 ID 51966

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Problem reports for freebsd-wireless@FreeBSD.org that need special attention

[bugzilla-noreply]

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+-
Needs MFC   |140567 | [ath] [patch] ath is not worked on my notebook  
Needs MFC   |154598 | [ath] Atheros 5424/2424 can't connect to WPA ne 
Needs MFC   |163312 | [panic] [ath] kernel panic: page fault with ath 
Needs MFC   |166190 | [ath] TX hangs and frames stuck in TX queue 
Needs MFC   |166357 | [ath] 802.11n TX stall when the first frame in  
Needs MFC   |166642 | [ieee80211] [patch] in 802.11n mode for FreeBSD 
Needs MFC   |169362 | [ath] AR5416: radar pulse PHY errors sometimes  

7 problems total for which you should take action.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193826] New: iwn does not scan channels

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193826

Bug ID: 193826
   Summary: iwn does not scan channels
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: Needs Triage
  Severity: Affects Some People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: henry.hu...@gmail.com

I'm trying to use DTrace to trace a problem I'm seeing from time to time.
After some time, iwn can't get any scan result. ifconfig says:

wlan0: flags=8c43 metric 0 mtu
1500
ether c4:85:08:82:da:5c
inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng (autoselect)
status: no carrier
ssid "" channel 1 (2412 MHz 11g ht/20)
country US authmode WPA1+WPA2/802.11i privacy MIXED deftxkey UNDEF
txpower 11 bmiss 10 scanvalid 60 protmode CTS ht20 ampdulimit 8k
-amsdutx amsdurx shortgi wme roaming MANUAL

and ifconfig wlan0 scan returns no results, neither do wpa_cli scan_results

With wlandebug +scan, I see these messages:

Sep 21 00:40:52 pepsi kernel: wlan0: ieee80211_scanreq: flags 0x20052 duration
0x7fff mindwell 0 maxdwell 0 nssid 1
Sep 21 00:40:52 pepsi kernel: wlan0: ieee80211_check_scan: active scan, append,
nojoin, once
Sep 21 00:40:52 pepsi kernel: wlan0: start_scan_locked: active scan, duration
2147483647 mindwell 0 maxdwell 0, desired mode 11ng, append, nojoin, once
Sep 21 00:40:52 pepsi kernel: wlan0: scan set  dwell min 20ms max 200ms
Sep 21 00:40:52 pepsi kernel: wlan0: scan_task: no channels to scan
Sep 21 00:40:52 pepsi kernel: wlan0: notify scan done

it seems like that the channel list to scan is empty.

By using dtrace to print some information in makescanlist() in
ieee80211_scan_sta.c, I find that:
vap->iv_des_mode = 9 (IEEE80211_MODE_11NG)
everything in table[] has mode = 1 or 2 (IEEE80211_MODE_11A / 11B)
According to logic in makescanlist,
if (vap->iv_des_mode != IEEE80211_MODE_AUTO) {
/*
 * If a desired mode was specified, scan only
 * channels that satisfy that constraint.
 */
if (vap->iv_des_mode != mode) {
/*
 * The scan table marks 2.4Ghz channels as b
 * so if the desired mode is 11g, then use
 * the 11b channel list but upgrade the mode.
 */
if (vap->iv_des_mode != IEEE80211_MODE_11G ||
mode != IEEE80211_MODE_11B)
continue;
This would skip all the channels.

Later it calls sweepchannels(). In this function, we have these channels in
ieee80211com.ic_channels:
freq / flags / ieee number / state / ht ext channel
chan: 2412 a0 1 0 0
chan: 2412 480 1 0 0
chan: 2412 10480 1 0 0
chan: 2412 20480 1 0 5
chan: 2417 a0 2 0 0
chan: 2417 480 2 0 0
chan: 2417 10480 2 0 0
chan: 2417 20480 2 0 6


so for each freq, we have
CCK | 2G = a0
DYN | 2G = 480
HT20 | DYN | 2G = 10480
HT40 | DYN | 2G = 20480

In sweepchannels(), it says
for (i = 0; i < ic->ic_nchans; i++) {
if (ss->ss_last >= IEEE80211_SCAN_MAX)
break;

c = &ic->ic_channels[i];
/*
 * Ignore dynamic turbo channels; we scan them
 * in normal mode (i.e. not boosted).  Likewise
 * for HT channels, they get scanned using
 * legacy rates.
 */
if (IEEE80211_IS_CHAN_DTURBO(c) || IEEE80211_IS_CHAN_HT(c))
continue;
// here, HT20 and HT40 channels are filtered out
/*
 * If a desired mode was specified, scan only
 * channels that satisfy that constraint.
 */
if (vap->iv_des_mode != IEEE80211_MODE_AUTO &&
vap->iv_des_mode != ieee80211_chan2mode(c))
continue;
// iv_des_mode = 11NG, chan2mode(DYN | 2G) = 11G, chan2mode(CCK | 2G) = 11B, so
other channels are filtered out

as a result, no channels are prepared for scan.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[FreeBSD Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (7 bugs)

Bug 140567:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] [patch] ath is not worked on my notebook PC
Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193628] Marvell 88W8335 wireless NIC not enabled by malo(4) or ndis(4)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193628

Tilman Keskinoz  changed:

   What|Removed |Added

 CC||ar...@freebsd.org
  Component|Individual Port(s)  |wireless
Version|Latest  |11.0-CURRENT
   Assignee|freebsd-ports-bugs@FreeBSD. |freebsd-b...@freebsd.org
   |org |
Product|Ports Tree  |Base System

--- Comment #6 from Tilman Keskinoz  ---
wrong component. Move to basesystem

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 140567] [ath] [patch] ath is not worked on my notebook PC

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567

Adrian Chadd  changed:

   What|Removed |Added

 Status|Needs MFC   |Issue Resolved
 CC||adr...@freebsd.org
 Resolution|--- |FIXED

--- Comment #8 from Adrian Chadd  ---
i'm not going to mfc this to -7. :(

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 193907] New: [ath] in HT40 mode set the final rate table entry to be 20MHz, just in case HT40 reception is terrible.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193907

Bug ID: 193907
   Summary: [ath] in HT40 mode set the final rate table entry to
be 20MHz, just in case HT40 reception is terrible.
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: adr...@freebsd.org

It may be that transmitting 40MHz rates (eg in HT40 2GHz mode) performs really
crappy due to adjacent channel interference.

So:

* teach ath_rate_sample to set the 20MHz flag for the final rate in the rate
table, so there's at least a good fallback
* .. and then maybe have it track how good 20/40 rates are and if too many
fallbacks to 20MHz is done, just fallback to transmitting on 20MHz for a while.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Problem reports for freebsd-wireless@FreeBSD.org that need special attention

[bugzilla-noreply]

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+-
Needs MFC   |154598 | [ath] Atheros 5424/2424 can't connect to WPA ne 
Needs MFC   |163312 | [panic] [ath] kernel panic: page fault with ath 
Needs MFC   |166190 | [ath] TX hangs and frames stuck in TX queue 
Needs MFC   |166357 | [ath] 802.11n TX stall when the first frame in  
Needs MFC   |166642 | [ieee80211] [patch] in 802.11n mode for FreeBSD 
Needs MFC   |169362 | [ath] AR5416: radar pulse PHY errors sometimes  

6 problems total for which you should take action.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[FreeBSD Bugzilla] Commit Needs MFC

[bugzilla-noreply]

Hi,

You have a bug in the "Needs MFC" state which has not been touched in 7 or more 
days. This email serves as a reminder that you may want to MFC this bug or 
marked it as completed.

In the event you have a longer MFC timeout you may update this bug with a 
comment and I won't remind you again for 7 days.

This reminder is only sent on Mondays.  Please file a bug about concerns you 
may have.

  This search was scheduled by ead...@freebsd.org.


 (6 bugs)

Bug 154598:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] Atheros 5424/2424 can't connect to WPA network
Bug 163312:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [panic] [ath] kernel panic: page fault with ath0 taskq
Bug 166190:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] TX hangs and frames stuck in TX queue
Bug 166357:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the 
software queue
Bug 166642:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a 
station in powersave cripples AP TX.
Bug 169362:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362
Severity: Affects Only Me
Priority: Normal
Hardware: Any
Assignee: freebsd-wireless@FreeBSD.org
  Status: Needs MFC
  Resolution: 
 Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC 
Error bit set as well as the PHY errors

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"