Thinkpad T410: resume broken
John Baldwin
jhb at freebsd.org
Fri May 23 14:08:29 UTC 2014
On Wednesday, May 21, 2014 3:43:49 pm 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.
> >
> > 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
These are probably not related. These man that your BIOS explicitly told the
OS to power down these devices (PEG_ is probably your GPU, and EXP[1-5] are
probably PCI-PCI bridges that represent the downstream ports of your PCI-e
root complex) in the D2 state when suspending, but the devices don't actually
support D2 (most PCI devices only support D0 (full on) and D3 (full off)).
--
John Baldwin
More information about the freebsd-mobile
mailing list