Matthias, I have been able to reproduce this with the following steps (wait a couple of seconds between the steps):
1. Enable hotspot mode
2. Disabled hotspot mode
3. Press/release power button to turn off screen
4. Press/release power button to turn on screen
You may need to repeat the sequence a few times before this fails. The failure actually occurs in step (3) (e.g. that's the point where syslog starts to get spammed), but it's at point (4) that the user notices because they can't turn on the screen, due to repowerd being blocked waiting in vain for suspend to happen.
I have found it makes no difference if usb is plugged in and there is an active ssh connection (e.g. with the phablet-shell tool).
Matthias, I have been able to reproduce this with the following steps (wait a couple of seconds between the steps):
1. Enable hotspot mode
2. Disabled hotspot mode
3. Press/release power button to turn off screen
4. Press/release power button to turn on screen
You may need to repeat the sequence a few times before this fails. The failure actually occurs in step (3) (e.g. that's the point where syslog starts to get spammed), but it's at point (4) that the user notices because they can't turn on the screen, due to repowerd being blocked waiting in vain for suspend to happen.
I have found it makes no difference if usb is plugged in and there is an active ssh connection (e.g. with the phablet-shell tool).