[Bug] Jolla Tablet randomly shuts down
The tablet is randomly shutting down after the recent update - 2.0.1.7. Even when the battery is full. This never happend before the update.
Edit:
Here are some observations regarding this bug which were already discussed on TMO:
How to reproduce
- Turn on the Tablet without the USB cable connected
- Turn on WLAN and let it go to standby or just lock it
- Wait some hours without using and touching it/ using ssh/ connecting the USB cable or pinging the tablet
- After several hours (there is no defined time period since it varies all the time, sometimes also after half an hour) you won't be able to unlock the tablet since it is kind of turned off. Only pushing the power button for a longer time period than on a normal startup process or connecting the charger will turn on the tablet again
Observations
- This bug seems to not correlate with the battery percentage
- This issue only occurs if the tablet is in standby mode AND the charger is not connected
- In quite all shutdown cases (caused by this issue) the bootlog is missing this shutdown
- Even with persistent journalctl logging the logs will be vanished/ destroyed on most cases
- This issue could also correlate with this issue (constant high CPU usage without connected charger and in standby mode, possibly caused by the WIFI chip and a 'kworker' process AND/OR inability of reaching deep-sleep mode)
- It seems to be caused by the Intel CPU (source):
[root@Jolla nemo]# journalctl --no-pager | grep "shut"
Mar 17 23:58:56 Jolla kernel: dollar_cove_pwrsrc dollar_cove_pwrsrc: Last shutdown caused by SOC initiated cold off
Mar 18 00:11:52 Jolla kernel: dollar_cove_pwrsrc dollar_cove_pwrsrc: Last shutdown caused by SOC initiated cold off
did you check the btrfs status?
tad ( 2016-02-09 13:04:00 +0200 )editThe tablet isn't btrfs, afaik.
lispy ( 2016-02-09 15:12:15 +0200 )editTablet is EXT4 IIRC
jollailija ( 2016-02-09 19:52:58 +0200 )editI can confirm this. I also got my (genuine) tablet a while ago and seems like that even with the earlier update (1.1.9.30) this bug is present. Also, it might be just me, but it seems to happen more often with 2.0.1.7. This is hard to debug as recovering from this requires hard poweroff and most logs are lost. Probably something to do with deep sleep?
irah ( 2016-03-07 20:46:41 +0200 )edit