On 21.05.2014 21:43, Jan Henrik Sylvester 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.
>> 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.
I can confirm this behavior. It already happened on 9.x.
Devices plugged into the USB ports are not even powered. It's not just
mouse, also USB hard disks for instance.
> Are these lines likely related?
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_:
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1:
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2:
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP4:
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5:
I don't remember seeing these lines in 9.x. That doesn't necessarily
mean they are not related.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"