Le 02/08/2018 à 16:30, alberto a écrit : > I just substituted my stolen thinkpad x250 with a x270.
Sorry for your loss. I experienced that myself in late 2012, this is a terrible experience. Fortunately, mine was fully encrypted, and I had a recent (less than one week) full backup. I hope you took the same precautions. > Despite that tlp-stat reports correctly that the power source is AC, tlp > always starts the suspend process after some inactivity even if I configured > PM (through xfce GUI) not to suspend on AC. > > This is the log: > > Aug 2 11:20:26 <host> systemd[1]: Starting TLP suspend/resume... > Aug 2 11:20:26 <host> systemd[1]: Started TLP suspend/resume. > Aug 2 11:20:26 <host> systemd[1]: Reached target Sleep. > Aug 2 11:20:26 <host> systemd[1]: Starting Restart Syncthing after resume... > Aug 2 11:20:26 <host> systemd[1]: Starting Suspend... > Aug 2 11:20:26 <host> systemd[1]: Started Restart Syncthing after resume. > Aug 2 11:20:26 <host> systemd-sleep[11509]: Suspending system... > Aug 2 11:20:26 <host> kernel: [ 1685.988411] PM: suspend entry (deep) > > Note that this never happened with the x250. > > BTW, I tried to perform some diagnostics but I could not find anything. > I do not even find a proper setting to avoid this (tried searching into > /etc/default/tlp). Are you positively sure that it's not something triggered by XFCE ? AFAIK, TLP doesn't activate suspend at all (hence the lack of such a setting in the configuration file). You may have been mislead by the log messages showing "TLP suspend/resume", which merely indicate that TLP's pre/post suspend hooks are being run. I don't know XFCE very well, so I'll ask you to double-check every setting even remotely related to power management. Also, if you want to be absolutely sure, try to purge TLP, and see if your computer still exhibits the same behavior. > I don't know if this is relevant but I found other stuffs related to > thinkpad in syslog: > > Aug 2 15:57:13 <host> kernel: [ 7848.767292] thinkpad_ec: > thinkpad_ec_request_row: arg0 rejected: (0x01:0x00)->0x00 > Aug 2 15:57:13 <host> kernel: [ 7848.767298] thinkpad_ec: > thinkpad_ec_read_row: failed requesting row: (0x01:0x00)->0xfffffffb > Aug 2 15:57:13 <host> kernel: [ 7848.767305] thinkpad_ec: initial ec test > failed > > In addition, tlp-stat says: > +++ ThinkPad Battery Features > tp-smapi = inactive (unsupported hardware) > tpacpi-bat = active > > and, actually, I can use tlp BAT settings even without smapi. That's perfectly normal. Lenovo discarded the SMAPI interface starting with the X230 (read [1]). Newer models must use tpacpi-bat (which uses acpi-call) to set the battery (dis)charge thresholds. This also explains your error messages emanating from thinkpad_ec : it can't find the interface it's looking for. Normally, on your X270, you shouldn't install tp-smapi-dkms, but acpi-call-dkms instead. I'm not sure about the improved hdaps driver, though, but I guess you got an SSD with your new X270, so you shouldn't need it anyway. [1] http://www.thinkwiki.org/wiki/Tp_smapi Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
