[SOLVED] Upgraded to 14.3, suspend, hibernate now lock up hard
Suspending to ram resumes w/screen ok, but everything frozen and locked up hard (must powercycle). This ocurrs using either pm-suspend or echo mem >/sys/power/state. Nothing is logged to /var/log/messages.
Back to top |
|||||
If you have systemd, and journalctl, and if you have set journalctl to not reset every boot, as root journalctl may have more data. Note that default debian has journalctl dump its data every reboot, so you have to change that prior to the crash.
If you hate systemd and refuse to use it, well, lol, hats off. Also, inxi -bxxx would help damentz out to see your system specs. Back to top |
|||||
I do not have systemd (sysvinit). Nothing else updated except kernel from 4.13 to 4.14. Hereis the inxi (HP Elitebook 8440p, intel graphics:
:: Code ::
System: Host: roadrunner Kernel: 4.12.0-14.3-liquorix-amd64 x86_64 bits: 64 gcc: 6.4.0 Desktop: AfterStep 2.2.12 dm: slim Distro: antiX-16.2_x64-base Berta Cáceres 15 June 2017 Machine: Device: laptop System: Hewlett-Packard product: HP EliteBook 8440p serial: N/A Mobo: Hewlett-Packard model: 172A v: KBC Version 30.31 serial: N/A BIOS: Hewlett-Packard v: 68CCU Ver. F.11 date: 11/25/2010 Chassis: type: 10 serial: N/A Battery BAT0: charge: 26.0 Wh 95.9% condition: 27.1/27.1 Wh (100%) volts: 12.3/10.8 model: Hewlett-Packard Primary Li-ion serial: 07744 2011/03/26 status: N/A cycles: 0 CPU: Dual core Intel Core i5 M 520 (-HT-MCP-) arch: Nehalem rev.5 speed/max: 1199/2400 MHz Graphics: Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0046 Display Server: X.Org 1.19.5 driver: intel Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel Ironlake Mobile version: 2.1 Mesa 17.2.5 Direct Render: Yes Network: Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 5020 bus-ID: 00:19.0 chip-ID: 8086:10ea Card-2: Intel Centrino Advanced-N 6200 bus-ID: 43:00.0 chip-ID: 8086:4239 Drives: HDD Total Size: 250.1GB (35.0% used) Info: Processes: 152 Uptime: 3:46 Memory: 884.6/7777.3MB Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 7.2.0 alt: 4.9/6 Client: Shell (bash 4.4.121 running in aterm) inxi: 2.3.43 Back to top |
|||||
Have you tried updating your BIOS? It looks like the version on your laptop doesn't even exist in the revision history for HP's site here:
support.hp.com/us-en/drivers/selfservice/hp-elitebook-8440p-notebook-pc/4095872 Specifically, the last update was in 2015: support.hp.com/us-en/drivers/selfservice/swdetails/hp-elitebook-8440p-notebook-pc/4095872/swItemId/ob-157352-1 Also, on the driver site, there's a intel management engine security update if you're interested, it's been all over the news. Back to top |
|||||
I've always been somewhat scared to do that, especially since everything's been workin' fine (until now)!
Back to top |
|||||
Me too, but it is necessary nowadays. Especially with that backdoor called "management engine" present on your system. It's bad enough that Intel can remotely access your system without your authorization, but you wouldn't want everybody else to be able to do that too.
Back to top |
|||||
If that's the case, I'd suspect that the "upgraded" spy-engine pbly gives 'em even MORE/easier/better access to your 'puter?! The only "BIOS"-related issues I appear to have is the "_OSC failed (AE_NOT_FOUND); disabling ASPM" msg that's been around forever on all boxes here. Don't know if upgrading might "fix" that and give Linux control over ASPM on the pci bus, but since I run docked all the time, doube it'd really buy me anything for the RISK of upgrading the bios all the way from .15 to .60 (a massive upgrade), which could, from what I understand from research, introduce NEW pbms!
Anyway, after further testing, it's not this box and it's not Liquorix. I tested my latest distro 4.14 and it fails too, and then tested on another box and it fails the same way there too. For now, will wait for later releases. Thanks for the research and advice though! Back to top |
|||||
As a counter to the upgrade bios, the last time I tried upgrading a lenovo bios, I think that was a bios, not uefi, it bricked it.
However, I did make a serious error there and run the bios upgrade tool from inside its windows install (was a laptop someone gave me), and that failed. Now, in a nice world, if a company writes the software that bricks your laptop, they'd politely replace it, but sadly, we don't live in that world, so I ended up with a brick. I believe the boot usb/cd methods for linux bios upgrades are far safer, but I have bricked more than one device doing firmware or bios upgrades now, and in neither case did I do anything wrong. Back to top |
|||||
Are you using antiX 16, but tracking Debian Sid with it? That what it looks like from the versions of some packages, such as Mesa. Things can break...
All I can say it that the Jessie-based MX 16 and backported Liquorix kernels up to 4.14.-3 have been suspending and recovering from s2ram and s2disk very well on my laptop: :: Code :: System: Host: mx1 Kernel: 4.14.0-2.3-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-16_x64 Metamorphosis 12 December 2016 Machine: Device: laptop System: Acer product: Aspire E5-575G v: V1.27 serial: N/A Mobo: Acer model: Ironman_SK v: V1.27 serial: N/A UEFI: Insyde v: V1.27 date: 05/26/2017 Back to top |
|||||
No, I'm using the "testing" repositories, only "sid" one is the Liquorix kernel repo.
Back to top |
|||||
All times are GMT - 8 Hours
|