Bug 234595 - Suspend/resume issues with PCI bus on ThinkPad T420 on 12.0-RELEASE
Summary: Suspend/resume issues with PCI bus on ThinkPad T420 on 12.0-RELEASE
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.0-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2019-01-03 16:57 UTC by Kevin Zheng
Modified: 2019-02-10 10:57 UTC (History)
1 user (show)

See Also:


Attachments
dmesg output (14.75 KB, text/plain)
2019-01-03 16:57 UTC, Kevin Zheng
no flags Details
T420 ASL (515.93 KB, text/plain)
2019-01-03 17:05 UTC, Kevin Zheng
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Zheng 2019-01-03 16:57:50 UTC
Created attachment 200741 [details]
dmesg output

Issuing:

# zzz

On a ThinkPad T420, either with CSM or UEFI boot, gives:

pci0: failed to set ACPI power state D3 on \134_SB_.PCI0.VID_: AE_BAD_PARAMETER
pcib0: failed to set ACPI power state D2 on \134_SB_.PCI0: AE_BAD_PARAMETER
acpi0: cleared fixed power button status

Then, either after the screen goes blank, or on resume, some things on the PCI bus end up broken. For me, it's the ehci controller and ethernet (em) controller.

ehci_interrupt: unrecoverable error, controller halted
cmd=0xffffffff
...
sts=0xffffffff
...
ien=0xffffffff
frindex=0xffffffff ctrdsegm=0xffffffff periodic=0xffffffff async=0xffffffff
port 1 status=0xffffffff
port 2 status=0xffffffff
port 3 status=0xffffffff
...
ehci_interrupt: blocking interrupts 0x10

em does not give any dmesg output, continues to show up in ifconfig, but does not seem to work.

Suspend/resume worked on this machine in 11.2-RELEASE. I suspect something broke with the ACPI upgrade, but will keep investigating.
Comment 1 Kevin Zheng 2019-01-03 17:05:51 UTC
Created attachment 200743 [details]
T420 ASL
Comment 2 miguel.barao 2019-02-08 15:42:02 UTC
Also affects Thinkpad X220.
Comment 3 Andriy Gapon freebsd_committer 2019-02-10 10:57:16 UTC
Can you try 12.0-STABLE or CURRENT ?