Created attachment 106533 [details] dmesg ==System Environment== -------------------------- Regression: No. This is first time test this byt machine. And I fail to find a good commit. Non-working platforms: Baytrail ==kernel== -------------------------- -nightly: 3e5e5913a80f593aa8f67784220eac2658034c6c (fails) drm-intel-nightly: 2014y-09m-17d-16h-09m-44s UTC integration manifest -queued: de6a03dbc12c72e8ddd936071936fe96633c9d05 (test fails in the same way) drm/i915: Clarify mmio_flip_lock locking -fixes: d72985765e986f45a28f87d75f3f0ece489b04cc (test fails with bla) drm/i915: Add limited color range readout for HDMI/DP ports on g4x/vlv/chv ==Bug detailed description== ----------------------------- run S3 ERROR message: [ 968.223195] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2. [ 968.376369] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2. [ 968.817419] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3. [ 968.890744] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3. ==Reproduce steps== ---------------------------- 1.S3
What's the exact problem here? What I can see from the log is that suspend/resume succeeds, with USB emitting some error messages. Is the display/machine alive after resume?
(In reply to comment #1) > What's the exact problem here? What I can see from the log is that > suspend/resume succeeds, with USB emitting some error messages. Is the > display/machine alive after resume? Yes, the machine is alive after resume. Just display output some ERROR message. Like bug description.
This is not a problem in the graphics stack (xhci_hcd is the SATA driver). Closing.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.