Real interrupt: frindex=0x000012f6 ctrdsegm=0x00000000 periodic=0xda3cf000 async=0xda3d1000 port 1 status=0x00001005 port 2 status=0x00001000 ehci_interrupt: real interrupt cmd=0x00010031 EHCI_CMD_ITC_1 EHCI_CMD_ASE EHCI_CMD_PSE EHCI_CMD_RS sts=0x0000c008 EHCI_STS_ASS EHCI_STS_PSS EHCI_STS_FLR ien=0x00000037
-adrian On 10 January 2015 at 03:52, Hans Petter Selasky <h...@selasky.org> wrote: > On 01/10/15 00:37, Daniel Kolesa wrote: >> >> 2015-01-09 23:26 GMT+00:00 Daniel Kolesa <quake...@gmail.com>: >>> >>> 2015-01-09 20:24 GMT+00:00 Adrian Chadd <adr...@freebsd.org>: >>>> >>>> hi, >>>> >>>> I have a haswell desktop box at home: >>>> >>>> CPU: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (3192.67-MHz K8-class CPU) >>>> >>>> With lynx point USB: >>> >>> >>> Also Haswell here, but with H97 chipset, which means Wildcat Point >>> USB. Not getting the issue. >>> >>>> >>>> adrian@test-2:~ % dmesg | grep ehci >>>> ehci0: <Intel Lynx Point USB 2.0 controller USB-B> mem >>>> 0xf7f1c000-0xf7f1c3ff irq 16 at device 26.0 on pci0 >>>> usbus1 on ehci0 >>>> ehci1: <Intel Lynx Point USB 2.0 controller USB-A> mem >>>> 0xf7f1b000-0xf7f1b3ff irq 23 at device 29.0 on pci0 >>>> usbus2 on ehci1 >>>> > > Hi, > > You can easily check who's generating the interrupts by setting: > > hw.usb.ehci.debug=16 > hw.usb.xhci.debug=16 > > If the interrupt status is all-zero, then it is a bug somewhere else! > > --HPS > _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"