https://bugzilla.kernel.org/show_bug.cgi?id=207629 --- Comment #20 from Rafael J. Wysocki (rjw@xxxxxxxxxxxxx) --- (In reply to Abhishek Pandit-Subedi from comment #14) > Ok -- this one is not a systemic problem as I predicted. This looks to be > the controller not responding to a specific command. In the logs below, the > controller is responding to everything except for 0x2042 and even that is > intermittent (responds to some 0x2042 but not others). > > So this is increasingly starting to look like a controller firmware problem. Which totally doesn't matter. Evidently, there are multiple cases in which the controller stops responding and that must not be a reason for failing the system suspend (that may mean refusing to suspend after a user has closed a laptop lid or similar). The controller may not be able to suspend cleanly, but that doesn't matter. There still is time to recover during system resume and if that fails, it will just not work going forward and so be it. Failing system suspend is not an option. You can do that only in critical situations. -- You are receiving this mail because: You are the assignee for the bug.
