CF-29 (and others) halt on suspend issue under linux

Hi. I've been trying to get linux working on my cf-29 mk4. My machine has celeron m 1.6ghz, 1.5gb ram, a touchscreen (totally dead) and intel 2915bg wifi. I currently have a 40gb hard disk in it which I swapped from my cf-18. The issue is, as the title says, the halt on suspend issue. I have been searching on and off for a few years how to solve this issue but I have found only 1 other cf-29 owner with the same issue but was unable to contact him. My googling and my own experience (cf-w7 i think) seems to suggest this issue is overall quite rare but affects multiple models with intel 9xx chipset.

I have tried many versions of ubuntu, debian, centos, backtrack, crunchbang, etc with kernels 2.4 through 3.x. Exerything works, including compiz (take that, windows aero!), except suspend.

When I close the lid, the power stays on but the screen goes blank. Opening the lid, the system is completely unresponsive and has to be hard shutdown. About 5 years ago I found a thread suggesting that the issue might be related to graphics or wifi holding back suspend but I never managed to get anything useful from my logs.

I know the hotkeys sometimes need manual configuration, and in some distributions suspend simply doesnt exist until a suspend script is created. I can figure that out later. What I need help with is this freezing issue. Thanks in advance. Long time panasonic user but new to the forums.

***Correction: my wifi card is intel 3945bg, not 2915.

 

Welcome, I am not experienced enough in Linux to be of much help.
I am sure one of the other members will be along shortly to assist.

 

i do not own a '29 ... have you tried mint 9 , 13 or 17 ?

 

I will send one of the Linux guru's this way later on.

 

I have tried Mint 9 and 10.

Thanks. I should mention that this issue does not affect windows for me. I have actually had a pair of W7's in the past with only one of them misbehaving under linux. I never figured that out either.

 

I'll check into it and get back to you.

What is your preferred OS right now?

 

I use kali linux a lot for work. Personally any 'modern enough' ubuntu based distro would be fine but I would like to avoid mint because of their security issues. I only need 1 xp machine, and my cf-18 is doing that job fine. Best case scenario is someone has a workaround that can be applied to several different linux distros.

 

What happens if you type sudo systemctl suspend

 

I dont have the systemctl command available in backtrack 5, which is currently installed. I'll see if its available on any of the bootable CDs I have. Does suspend work properly on your cf-29 mk5?

 

I haven't used it in a while, but it did. I don't have hard drives loaded in either of my 29's at the moment but I ran Debian or Kali on them at one time or another.

Backtrack 5 is a bit old and it uses SysV init, so no systemd for you. It probably wouldn't hurt to upgrade to Kali or something else a bit more up to date.

I'd try

Code:

pm-suspend

or

Code:

pmi action suspend

and see how your system reacts.

 

Generally distros that are new enough to have systemd have other issue on old machines, so I havent used them. I've tried "pm-suspend" many times and the result is always a hard freeze with blank screen but power still on. I havent tried "pmi action suspend" before though.

 

i have noticed that many (most all ?) of the newer versions simply will not load correctly or even "run" if one gets past loading them .
in some cases an older machine can be bricked while attempting to load an 'nix OS ...
i found out that toshiba machines seem to enjoy a higher than average rate/fate when it comes to this matter .

 

In that case

It's good that you can recreate the bug with pm-suspend because now you can troubleshoot by adding arguments to the command as well as add a few config vars in a file in /etc/pm/config.d

Read the man page for pm-suspend!

For the config file, create /etc/pm/config.d/suspend.conf then check the man page's section on configuration variables to stick in the file. If you think wifi is the culprit, there's a variable for unloading modules before suspend that could be a workaround, like SUSPEND_MODULES = mac80211 or something.

 

OP I have messed with this for a bit. What I found.....

1. Mint 18 suspend no workie on MK4. (29)
2. Mint 18 suspend works on MK2. (29) Same drive as above.
3. Mint 17.1 to 17.3 suspend works. Ummm these were CF-30, 31 and 53.

I won't try to say what it means. Info only.

 

Double post different topic so I approve it.

Here is sample early MX-14 on a 29MK2....a portion of dmesg. I don't use IPv6 so ignore the errors.

EDIT: SUSPEND WORKS! END EDIT

25.844510] Bluetooth: BNEP socket layer initialized
[ 29.792843] 8139too 0000:02:02.0 eth2: link down
[ 29.792938] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 31.172626] lib80211_crypt: registered algorithm 'TKIP'
[ 40.382338] fuse init (API version 7.22)
[ 99.867657] PM: Syncing filesystems ... done.
[ 100.049125] PM: Preparing system for mem sleep
[ 100.049270] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 100.050507] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 100.051603] PM: Entering mem sleep
[ 100.051626] Suspending console(s) (use no_console_suspend to debug)
[ 100.051932] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 100.080238] parport_pc 00:09: disabled
[ 100.083395] serial 00:08: disabled
[ 100.083460] eth3: Going into suspend...
[ 100.083720] sd 0:0:0:0: [sda] Stopping disk
[ 100.569501] PM: suspend of devices complete after 517.699 msecs
[ 100.569602] PM: late suspend of devices complete after 0.096 msecs
[ 100.584141] PM: noirq suspend of devices complete after 14.535 msecs
[ 100.584376] ACPI: Preparing to enter system sleep state S3
[ 100.820783] PM: Saving platform NVS memory
[ 100.820783] ACPI: Low-level resume complete
[ 100.820783] PM: Restoring platform NVS memory
[ 100.820960] ACPI: Waking up from system sleep state S3
[ 101.592100] yenta_cardbus 0000:02:00.0: proprietary Ricoh MMC controller disabled (via cardbus function)
[ 101.592103] yenta_cardbus 0000:02:00.0: MMC cards are now supported by standard SDHCI controller
[ 101.608335] PM: noirq resume of devices complete after 563.295 msecs
[ 101.608436] PM: early resume of devices complete after 0.060 msecs
[ 101.608536] i915 0000:00:02.0: setting latency timer to 64
[ 101.623781] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 101.623804] usb usb1: root hub lost power or was reset
[ 101.623853] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 101.623872] usb usb2: root hub

 

Thank you all for your own prodding at the issue. I must have missed the alerts over the weekend. I have been trying to get results myself but its a long process of trial and error unfortunately. I am assuming suspend works a bit different with a live image so I have been installing. For this week (and maybe a little longer) I am slightly more interested in tracking down the issue and producing a log which might help others. I will post whatever I discover here.