On Wed, May 21, 2014 at 12:43 PM, Jan Henrik Sylvester <m...@janh.de> wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote: > > On 05/21/14 21:16, Jan Henrik Sylvester wrote: > >> Unfortunately, my USB mouse does not work anymore: After the first > >> resume, it took a few seconds until it worked again (the build in > >> touchpad was back immediately). After the second resume, it would not > >> work anymore at all, even after reconnecting it to a different EHCI > >> port. It does work at a XHCI, though, until the next resume. Anyhow, > >> this is obviously not related to the original problem. > > > > Hi, > > > > USB controller are being reset at resume, so I think this indicates a > > more fundamental PCI/BUS problem. > > Looking through dmesg, it seems that other USB devices (build-in) are > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after > resume, just not the mouse. > > Are these lines likely related? > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_: > AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1: > AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2: > AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP4: > AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5: > AE_BAD_PARAMETER > > Thanks, > Jan Henrik > Could this be another face of the problems that requires kbdmux to keep the USB keyboard working correctly with vt(4)? -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"