Date: Thu, 03 Oct 2019 18:00:33 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 233226] run(4) WiFi card fails periodically: run0: device timeout Message-ID: <bug-233226-21060-xa32oxtXVj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233226-21060@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233226 --- Comment #5 from Jim Pirzyk <pirzyk@FreeBSD.org> --- 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 <kern.crit> zephyr kernel: transfer complete: 488 bytes @ index 1 Oct 3 12:34:30 <kern.crit> zephyr kernel: run0: sending frame len=132/160 @ index 1 Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_TIMEOUT Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: device timeout Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: cmdq_store=5 Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: sending frame len=389/420 @ index 1 Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: transfer complete: 420 bytes @ index 1 Oct 3 12:34:35 <kern.crit> zephyr kernel: run0: sending frame len=1536/1564 @ index 1 Oct 3 12:34:37 <kern.crit> zephyr kernel: run0: sending frame len=126/156 @ index 0 Oct 3 12:34:37 <kern.crit> zephyr kernel: run0: transfer complete: 156 bytes @ index 0 Oct 3 12:34:37 <kern.crit> zephyr kernel: run0: sending frame len=126/156 @ index 0 Oct 3 12:34:37 <kern.crit> zephyr kernel: run0: transfer complete: 156 bytes @ index 0 Oct 3 12:34:40 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_TIMEOUT Oct 3 12:34:40 <kern.crit> zephyr kernel: run0: device timeout Oct 3 12:34:40 <kern.crit> zephyr kernel: run0: cmdq_store=2 Oct 3 12:34:40 <kern.crit> zephyr kernel: run0: sending frame len=1536/1564 @ index 1 Oct 3 12:34:45 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_TIMEOUT Oct 3 12:34:45 <kern.crit> zephyr kernel: run0: device timeout Oct 3 12:34:45 <kern.crit> zephyr kernel: run0: Oct 3 12:34:45 <kern.crit> zephyr kernel: cmdq_store=11 Oct 3 12:34:45 <kern.crit> zephyr kernel: run0: sending frame len=1536/1564 @ index 1 Oct 3 12:34:47 <kern.crit> zephyr kernel: run0: sending frame len=126/156 @ index 0 Oct 3 12:34:50 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_TIMEOUT Oct 3 12:34:50 <kern.crit> zephyr kernel: run0: device timeout Oct 3 12:34:50 <kern.crit> zephyr kernel: run0: cmdq_store=12 ... Oct 3 12:54:41 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:41 <kern.crit> zephyr kernel: run0: transfer complete: 56 bytes @ index 0 Oct 3 12:54:41 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:41 <kern.crit> zephyr kernel: run0: transfer complete: 56 bytes @ index 0 Oct 3 12:54:41 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_TIMEOUT Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: device timeout Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: cmdq_store=13 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: transfer complete: 56 bytes @ index 0 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: transfer complete: 56 bytes @ index 0 Oct 3 12:54:46 <kern.crit> zephyr kernel: run0: sending frame len=26/56 @ index 0 Oct 3 12:54:48 <kern.crit> zephyr kernel: run0: USB transfer error, USB_ERR_CANCELLED Oct 3 12:54:53 <kern.crit> 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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233226-21060-xa32oxtXVj>