Date: Tue, 30 Apr 2013 19:04:37 GMT From: Stephen Sanders <stephen.sanders@riverbed.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/178267: USB causing interrupt storm on irq16 Message-ID: <201304301904.r3UJ4bvV090009@red.freebsd.org> Resent-Message-ID: <201304301910.r3UJA0XT011277@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 178267 >Category: kern >Synopsis: USB causing interrupt storm on irq16 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 30 19:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Stephen Sanders >Release: FreeBSD 8.1 >Organization: Riverbed >Environment: FreeBSD bd5000-34.lab.opnet.com 8.1-RELEASE FreeBSD 8.1-RELEASE #1: Wed Jun 6 13:41:00 PDT 2012 jtoung@focus8.networkphysics.com:/u1/builds/8.6/ALKernel.jt/src/sys/amd64/compile/NPBAB8 amd64 >Description: USB hub controller seems to be generating a large number of interrupts per second. This seems to be in effect whether something is attached to the USB ports or not. The mother board is an Intel S5520HC with 48GB RAM . "vmstat -i | grep irq16" yields irq16: uhci3 uhci4* 87743 923 Very often,the number of interrupts is above 1200. Altering the usb quirks sysctl's didn't have any effect. There seems to be no BIOS setting that effects this problem either. "sysctl hw.usb.ehci.debug=15 ; sleep 5 ; sysctl hw.usb.ehci.debug=0" yielded the following in /var/log/message : Apr 30 14:44:39 bd5000-34 kernel: ehci_roothub_exec: get port status i=1 Apr 30 14:44:39 bd5000-34 kernel: ehci_roothub_exec: get port status i=1 Apr 30 14:44:39 bd5000-34 kernel: Apr 30 14:44:59 bd5000-34 kernel: ehci_set_hw_power: ehci_set_hw_power: Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0001 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0001 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=1 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=1 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0002 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0002 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=2 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=2 Apr 30 14:44:59 bd5000-34 kernel: Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0003 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0003 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=3 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=3 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0004 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0004 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=4 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=4 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x3000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0005 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0005 Apr 30 14:44:59 bd5000-34 kernel: Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=5 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: get port status i=5 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x1000 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: port status=0x3000 Apr 30 14:44:59 bd5000-34 kernel: Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x0006 Apr 30 14:44:59 bd5000-34 kernel: ehci_roothub_exec: type=0xa3 request=0x00 wLen=0x0004 wValue=0x00 00 wIndex=0x000 >How-To-Repeat: Boot 8.1 on an Intel S5520HC board. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304301904.r3UJ4bvV090009>