[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-12-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #9 from Jim Pirzyk  ---
(In reply to Yuri Victorovich from comment #8)

So far seems to.

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-12-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #8 from Yuri Victorovich  ---
(In reply to Jim Pirzyk from comment #7)

Does Atheros AR9460 work well?

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-12-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #7 from Jim Pirzyk  ---
FYI the card also times out on 12.1-RELEASE-p1.

I have swapped out the card for an Atheros AR9460 card and won't be able to do
more testing.

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-10-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #6 from Jim Pirzyk  ---
Here's another debug output, this time with all flags enabled:

Oct  7 19:14:05  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:06  zephyr kernel: run0: debug reg 0401
Oct  7 19:14:06  zephyr kernel: run0: tx stat 0x400301a8
Oct  7 19:14:06  zephyr kernel: run0: count=0
Oct  7 19:14:06  zephyr kernel: run0: ridx=0
Oct  7 19:14:06  zephyr kernel: run0: retrycnt=0 txcnt=0 success=0
Oct  7 19:14:06  zephyr kernel: run0: ridx=7
Oct  7 19:14:07  zephyr kernel: run0: rx done, actlen=680
Oct  7 19:14:07  zephyr kernel: run0: received RT2860_RX_L2PAD frame
Oct  7 19:14:07  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:07  zephyr kernel: run0: cmdq_store=12
Oct  7 19:14:07  zephyr kernel: run0: cmdq_exec=12 pending=1
Oct  7 19:14:07  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:07  zephyr kernel: run0: cmdq_store=13
Oct  7 19:14:07  zephyr kernel: run0: cmdq_exec=13 pending=1
Oct  7 19:14:07  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:07  zephyr kernel: run0: debug reg 0401
Oct  7 19:14:07  zephyr kernel: run0: tx stat 0x400301a8
Oct  7 19:14:07  zephyr kernel: run0: count=0
Oct  7 19:14:07  zephyr kernel: run0: ridx=0
Oct  7 19:14:07  zephyr kernel: run0: retrycnt=0 txcnt=0 success=0
Oct  7 19:14:07  zephyr kernel: run0: ridx=7
Oct  7 19:14:08  zephyr kernel: run0: rx done, actlen=132
Oct  7 19:14:08  zephyr kernel: run0: cmdq_store=14
Oct  7 19:14:08  zephyr kernel: run0: cmdq_exec=14 pending=1
Oct  7 19:14:08  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:08  zephyr kernel: run0: cmdq_store=15
Oct  7 19:14:08  zephyr kernel: run0: cmdq_exec=15 pending=1
Oct  7 19:14:08  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:08  zephyr kernel: run0: debug reg 0401
Oct  7 19:14:08  zephyr kernel: run0: tx stat 0x400301a8
Oct  7 19:14:08  zephyr kernel: run0: count=0
Oct  7 19:14:08  zephyr kernel: run0: ridx=0
Oct  7 19:14:08  zephyr kernel: run0: retrycnt=0 txcnt=0 success=0
Oct  7 19:14:08  zephyr kernel: run0: ridx=7
Oct  7 19:14:09  zephyr kernel: run0: rx done, actlen=144
Oct  7 19:14:09  zephyr kernel: run0: received RT2860_RX_L2PAD frame
Oct  7 19:14:09  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:09  zephyr syslogd: last message repeated 1 times
Oct  7 19:14:09  zephyr kernel: run0: debug reg 0401
Oct  7 19:14:09  zephyr kernel: run0: tx stat 0x400301a8
Oct  7 19:14:09  zephyr kernel: run0: count=0
Oct  7 19:14:09  zephyr kernel: run0: ridx=0
Oct  7 19:14:09  zephyr kernel: run0: retrycnt=0 txcnt=0 success=0
Oct  7 19:14:09  zephyr kernel: run0: ridx=7
Oct  7 19:14:10  zephyr kernel: run0: rx done, actlen=632
Oct  7 19:14:10  zephyr kernel: run0: received RT2860_RX_L2PAD frame
Oct  7 19:14:10  zephyr kernel: run0: rx done, actlen=48
Oct  7 19:14:10  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  7 19:14:10  zephyr kernel: run0: device timeout

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-10-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #5 from Jim Pirzyk  ---
No I have yet to discover a specific cause.  Most of the time I see the device
timeouts are in the middle of the night.  But sometimes (like just within the
hour) it will happen while I am using wireless, browsing web, slack, etc.

I turned on the hw.usb.run.debug=0x40 (USB_ERR_TIMEOUT) and this is what I see:

Oct  3 12:34:30  zephyr kernel: transfer complete: 488 bytes @ index
1
Oct  3 12:34:30  zephyr kernel: run0: sending frame len=132/160 @
index 1
Oct  3 12:34:35  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  3 12:34:35  zephyr kernel: run0: device timeout
Oct  3 12:34:35  zephyr kernel: run0: cmdq_store=5
Oct  3 12:34:35  zephyr kernel: run0: sending frame len=389/420 @
index 1
Oct  3 12:34:35  zephyr kernel: run0: transfer complete: 420 bytes @
index 1
Oct  3 12:34:35  zephyr kernel: run0: sending frame len=1536/1564 @
index 1
Oct  3 12:34:37  zephyr kernel: run0: sending frame len=126/156 @
index 0
Oct  3 12:34:37  zephyr kernel: run0: transfer complete: 156 bytes @
index 0
Oct  3 12:34:37  zephyr kernel: run0: sending frame len=126/156 @
index 0
Oct  3 12:34:37  zephyr kernel: run0: transfer complete: 156 bytes @
index 0
Oct  3 12:34:40  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  3 12:34:40  zephyr kernel: run0: device timeout
Oct  3 12:34:40  zephyr kernel: run0: cmdq_store=2
Oct  3 12:34:40  zephyr kernel: run0: sending frame len=1536/1564 @
index 1
Oct  3 12:34:45  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  3 12:34:45  zephyr kernel: run0: device timeout
Oct  3 12:34:45  zephyr kernel: run0: 
Oct  3 12:34:45  zephyr kernel: cmdq_store=11
Oct  3 12:34:45  zephyr kernel: run0: sending frame len=1536/1564 @
index 1
Oct  3 12:34:47  zephyr kernel: run0: sending frame len=126/156 @
index 0
Oct  3 12:34:50  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  3 12:34:50  zephyr kernel: run0: device timeout
Oct  3 12:34:50  zephyr kernel: run0: cmdq_store=12
...
Oct  3 12:54:41  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:41  zephyr kernel: run0: transfer complete: 56 bytes @
index 0
Oct  3 12:54:41  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:41  zephyr kernel: run0: transfer complete: 56 bytes @
index 0
Oct  3 12:54:41  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:46  zephyr kernel: run0: USB transfer error,
USB_ERR_TIMEOUT
Oct  3 12:54:46  zephyr kernel: run0: device timeout
Oct  3 12:54:46  zephyr kernel: run0: cmdq_store=13
Oct  3 12:54:46  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:46  zephyr kernel: run0: transfer complete: 56 bytes @
index 0
Oct  3 12:54:46  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:46  zephyr kernel: run0: transfer complete: 56 bytes @
index 0
Oct  3 12:54:46  zephyr kernel: run0: sending frame len=26/56 @
index 0
Oct  3 12:54:48  zephyr kernel: run0: USB transfer error,
USB_ERR_CANCELLED
Oct  3 12:54:53  zephyr kernel: run0: firmware RT2870 ver. 0.33
loaded

I belive the USB_ERR_CANCELLED is when I downed the interface.

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-09-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

Ashish Gupta  changed:

   What|Removed |Added

 CC||lrx...@gmail.com

--- Comment #4 from Ashish Gupta  ---
(In reply to Jim Pirzyk from comment #2)

Hi!

I'd like to reproduce this issue on my setup. I have an AP which forwards my
traffic to/from another wireless interface on the same machine. Do you see
these device timeouts when doing something specific (like watching an HD video
/ downloading large files, etc)?

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-09-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #3 from Jim Pirzyk  ---
Forgot to add the hardware info:

run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address Y:Y:Y:Y:Y:Y

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-09-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

Jim Pirzyk  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
 CC||pir...@freebsd.org

--- Comment #2 from Jim Pirzyk  ---
I have been seeing this issue in the last day as I just started using the
interface as an AP.

158>uname -a
FreeBSD zephyr 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC  amd64

159>ifconfig wlan0
wlan0: flags=8843 metric 0 mtu 1500
ether Y:Y:Y:Y:Y:Y
inet X.X.X.X netmask 0xff00 broadcast X.X.X.255 
groups: wlan 
ssid HOSTID channel 1 (2412 MHz 11g) bssid Y:Y:Y:Y:Y:Y
regdomain FCC country US authmode WPA2/802.11i privacy MIXED
deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit txpower 30 scanvalid 60
protmode CTS wme hidessid dtimperiod 1 -dfs
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
status: running
nd6 options=29

and it lasts for a bit:

Sep 11 18:08:11  zephyr kernel: run0: device timeout
Sep 11 18:08:46  zephyr syslogd: last message repeated 7 times
Sep 11 18:10:50  zephyr syslogd: last message repeated 25 times
Sep 11 18:11:59  zephyr syslogd: last message repeated 14 times
...
Sep 11 18:14:35  zephyr kernel: run0: firmware RT2870 ver. 0.33
loaded

Sep 11 22:57:22  zephyr kernel: run0: device timeout
Sep 11 22:57:57  zephyr syslogd: last message repeated 10 times
Sep 11 22:58:30  zephyr syslogd: last message repeated 13 times

At the 18:11:59 time, I forced the interface down and back up to get it to
reload.  I am not sure when the issue cleared after 22:57.

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2019-02-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

Yuri Victorovich  changed:

   What|Removed |Added

 CC||wirel...@freebsd.org

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2018-11-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

--- Comment #1 from Yuri Victorovich  ---
Internet connection freezes for a while when this happens, and it comes back in
a few minutes.

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


[Bug 233226] run(4) WiFi card fails periodically: run0: device timeout

2018-11-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226

Bug ID: 233226
   Summary: run(4) WiFi card fails periodically: run0: device
timeout
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: wirel...@freebsd.org
  Reporter: y...@freebsd.org

I don't think this is a regression, this has been happening for a long time.

> $ grep timeout /var/log/messages
> Nov 11 19:52:57 xx kernel: run0: device timeout
> Nov 13 14:10:37 xx kernel: run0: device timeout
> Nov 13 15:05:14 xx kernel: run0: device timeout
> Nov 14 09:08:59 xx kernel: run0: device timeout

FreeBSD xx 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 #2 r338897M: Sun Sep 23 23:36:22 PDT
2018 sw@sw:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

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