The patchset was originally based on another GPE fix series.
The fix has been discussed for more than 3 months, and didn't get merged.
So my environment is a bit different from yours.
You may suffer from a dead lock during suspending without the fix.
In order to make this patchset working for "system suspend" without the fix, the gpe-handle21.patch workaround is required.
For this test:
4. Using linux-pm/linux-next+ec-flush{1,2,3,4,5,6}.patch+updated ec-flush7.patch, can you perform a suspend/resume test?
It should be updated as:
4. Using linux-pm/linux-next+gpe-handle21.patch+ec-flush{1,2,3,4,5,6}.patch+updated ec-flush7.patch, can you perform a suspend/resume test?
linux-pm/linux-next maintainer has merged the regression fixes, so if you have synchronized the branch, you need to:
1. git revert 79149001
2. git revert df9ff918
3. git am gpe-handle21.patch (attachment 156591)
4. git am ec-flush1.patch (attachment 155351)
5. git am ec-flush2.patch (attachment 155371)
6. git am ec-flush3.patch (attachment 155381)
7. git am ec-flush4.patch (attachment 155391)
8. git am ec-flush5.patch (attachment 155411)
9. git am ec-flush6.patch (attachment 155421)
10.git am ec-flush7.patch (use updated attachment 155851, do not use attachment 155431)
11. rebuild and boot the kernel.
12. try the suspend/resume test again.
For this test:
5. Then what's the actual test result of linux-pm/linux-next +ec-flush{1,2,3,4,5,6,7}.patch after a suspend/resume test?
It also should be updated as:
5. Then what's the actual test result of linux-pm/linux-next +gpe-handle21.patch+ec-flush{1,2,3,4,5,6}.patch+updated ec-flush7.patch after a suspend/resume test?
Hi, Ortwin:
Sorry for the inconvenience.
The patchset was originally based on another GPE fix series.
The fix has been discussed for more than 3 months, and didn't get merged.
So my environment is a bit different from yours.
You may suffer from a dead lock during suspending without the fix.
In order to make this patchset working for "system suspend" without the fix, the gpe-handle21.patch workaround is required.
For this test: linux-next+ ec-flush{ 1,2,3,4, 5,6}.patch+ updated ec-flush7.patch, can you perform a suspend/resume test? linux-next+ gpe-handle21. patch+ec- flush{1, 2,3,4,5, 6}.patch+ updated ec-flush7.patch, can you perform a suspend/resume test?
4. Using linux-pm/
It should be updated as:
4. Using linux-pm/
linux-pm/linux-next maintainer has merged the regression fixes, so if you have synchronized the branch, you need to:
1. git revert 79149001
2. git revert df9ff918
3. git am gpe-handle21.patch (attachment 156591)
4. git am ec-flush1.patch (attachment 155351)
5. git am ec-flush2.patch (attachment 155371)
6. git am ec-flush3.patch (attachment 155381)
7. git am ec-flush4.patch (attachment 155391)
8. git am ec-flush5.patch (attachment 155411)
9. git am ec-flush6.patch (attachment 155421)
10.git am ec-flush7.patch (use updated attachment 155851, do not use attachment 155431)
11. rebuild and boot the kernel.
12. try the suspend/resume test again.
For this test: 1,2,3,4, 5,6,7}. patch after a suspend/resume test? patch+ec- flush{1, 2,3,4,5, 6}.patch+ updated ec-flush7.patch after a suspend/resume test?
5. Then what's the actual test result of linux-pm/linux-next +ec-flush{
It also should be updated as:
5. Then what's the actual test result of linux-pm/linux-next +gpe-handle21.
Sorry again.
Thanks and best regards