Cannot suspend HP ProLiant SE316M1R2

[Vincas Dargis]

pm-suspend does not work on HP ProLiant SE316M1R2 system.

I am not sure if hardware actually supports that though, but there is kernel crash (see syslog.txt attached with Call Trace) which maybe is the cause.

Monitor goes off for few seconds but after that system resumes and works as before.

Also, some interesting lines:

May 7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
May 7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): pci_pm_freeze+0x0/0xe0 returns -38
May 7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device 0000:06:00.0 failed to freeze async: error -38s2disks

These lines also appears when using s2disk.

s2ram gives:

KMS graphics driver is in use, skipping quirks.
s2ram_do: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.21.22
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Sat May 7 20:55:52 2016
HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
InstallationDate: Installed on 2015-10-12 (208 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: HP ProLiant SE316M1R2
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
dmi.bios.date: 07/02/2013
dmi.bios.vendor: HP
dmi.bios.version: R02
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant SE316M1R2
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-wily/

[Vincas Dargis (talkless)]

Issue was the same with 15.10 before upgrade.

I'll try upstream kernel when I get access to this server after some time.

Thanks.

[Vincas Dargis (talkless)]

I've installed latest kernel (final release, not rc):
Linux tomashp-server 4.6.0-040600-generic #201605151930 SMP Sun May 15 23:32:59 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Strangely, pm-suspend outputs:
$ sudo pm-suspend
sudo: unable to resolve host tomashp-server

And nothing happens.

pm-hybernate does not produce backtrace, but -XY errors still occurs:

$ tail -n0 -f /var/log/kern.log
May 22 17:34:35 tomashp-server kernel: [ 368.519903] Syncing filesystems ... done.
May 22 17:34:35 tomashp-server kernel: [ 368.520521] Freezing user space processes ... (elapsed 0.001 seconds) done.
May 22 17:34:35 tomashp-server kernel: [ 368.522671] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
May 22 17:34:35 tomashp-server kernel: [ 368.522674] PM: Marking nosave pages: [mem 0x00097000-0x000fffff]
May 22 17:34:35 tomashp-server kernel: [ 368.522677] PM: Marking nosave pages: [mem 0xe7622000-0xe762bfff]
May 22 17:34:35 tomashp-server kernel: [ 368.522678] PM: Marking nosave pages: [mem 0xe762d000-0xffffffff]
May 22 17:34:35 tomashp-server kernel: [ 368.522905] PM: Basic memory bitmaps created
May 22 17:34:35 tomashp-server kernel: [ 368.522983] PM: Preallocating image memory... done (allocated 471506 pages)
May 22 17:34:35 tomashp-server kernel: [ 369.200798] PM: Allocated 1886024 kbytes in 0.67 seconds (2814.96 MB/s)
May 22 17:34:35 tomashp-server kernel: [ 369.200801] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
May 22 17:34:35 tomashp-server kernel: [ 369.202586] Suspending console(s) (use no_console_suspend to debug)
May 22 17:34:35 tomashp-server kernel: [ 369.203015] serial 00:03: disabled
May 22 17:34:35 tomashp-server kernel: [ 369.204049] pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
May 22 17:34:35 tomashp-server kernel: [ 369.204056] dpm_run_callback(): pci_pm_freeze+0x0/0xe0 returns -38
May 22 17:34:35 tomashp-server kernel: [ 369.204057] PM: Device 0000:06:00.0 failed to freeze async: error -38
May 22 17:34:35 tomashp-server kernel: [ 370.353902] power_meter ACPI000D:00: Found ACPI power meter.
May 22 17:34:35 tomashp-server kernel: [ 370.354124] serial 00:03: activated
May 22 17:34:35 tomashp-server kernel: [ 370.354128] rtc_cmos 00:04: System wakeup disabled by ACPI
May 22 17:34:35 tomashp-server kernel: [ 370.671883] ata3: SATA link down (SStatus 0 SControl 300)
May 22 17:34:35 tomashp-server kernel: [ 370.682559] ata4: SATA link down (SStatus 0 SControl 300)
May 22 17:34:35 tomashp-server kernel: [ 370.736637] [drm] PCI GART of 512M enabled (table at 0x0000000035500000).
May 22 17:34:35 tomashp-server kernel: [ 370.736640] radeon 0000:01:03.0: WB disabled
May 22 17:34:35 tomashp-server kernel: [ 370.736643] radeon 0000:01:03.0: fence driver on ring 0 use gpu addr 0x00000000d0000000 and cpu addr 0xffff880035488000
May 22 17:34:35 tomashp-server kernel: [ 370.736765] [drm] radeon: ring at 0x00000000D0001000
May 22 17:34:35 tomashp-server kernel: [ 370.736790] [drm] ring test succeeded in 1 usecs
May 22 17:34:35 tomashp-server kernel: [ 370.985315] ata1.00: SATA link down (SStatus 0 SControl 300)
May 22 17:34:35 tomashp-server kernel: [ 370.985326] ata1.01: SATA ...

[penalvch (penalvch)]

Vincas Dargis:
1) Could you please provide the serial number so one may look it up via https://www.hpe.com/us/en/support.html ?
2) Regarding suspend only (not hibernate) could you please test the latest mainline kernel (4.7-rc1) and advise to the results?

[Vincas Dargis (talkless)]

Serial is CZ3224LWY3, though it does not help, support page does not find that...

I'll try 4.7 within week or two.

[penalvch (penalvch)]

Vincas Dargis, regarding 1), yhe lookup tool noted it as:
Product: HP SE1120-006913-AX Srvr
Product number: BR711A

which as one may try, doesn't bring up anything conclusive. However, using http://partsurfer.hpe.com/search.aspx , it indicates it as a HP ProLiant DL160 G6 Server under the hood:
http://h20565.www2.hpe.com/portal/site/hpsc/public/psi/home/?sp4ts.oid=3884343

[Vincas Dargis (talkless)]

Yea, looking at photo found here http://www.newegg.com/Product/Product.aspx?Item=9SIA5DJ1UN3138 it looks like it.

An now how cant it help solving this issue?

[penalvch (penalvch)]

Vincas Dargis:
>"An now how cant it help solving this issue?"

Provide the results of testing 4.7-rc2.

[Vincas Dargis (talkless)]

OK so I just installed 4.7 rc4:
$ uname -a
Linux tomashp-server 4.7.0-040700rc4-generic #201606201235 SMP Mon Jun 20 16:38:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

again, pm-suspend does absolutely nothing. I'll attach strace output. Interestingly, there are errors as such:

stat("/sbin/do_suspend", 0x7ffecd046e80) = -1 ENOENT (No such file or directory)
stat("/usr/sbin/do_suspend", 0x7ffecd046e80) = -1 ENOENT (No such file or directory)
stat("/bin/do_suspend", 0x7ffecd046e80) = -1 ENOENT (No such file or directory)
stat("/usr/bin/do_suspend", 0x7ffecd046e80) = -1 ENOENT (No such file or directory)
stat("/usr/lib/pm-utils/bin/do_suspend", 0x7ffecd046e80) = -1 ENOENT (No such file or directory)

pm-hybernate and pm-suspend-hybrid again produces -38 errors.

[Vincas Dargis (talkless)]

Clicking Suspend on XFCE produces much more verbose output in syslog. Screen goes dark, mouse cursor is visible as rectangle with some junk pixels. Had to REISUB.

[penalvch (penalvch)]

Vincas Dargis, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Vincas Dargis (talkless)]

These "echo SOMETHING > /sys/power/pm_test" doesn't do anything.

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" produces only these lines:

Jul 22 22:02:32 tomashp-server kernel: [ 972.420095] PM: Enabling pm_trace changes system date and time during resume.
Jul 22 22:02:32 tomashp-server kernel: [ 972.420095] PM: Correct system time has to be restored manually after resume.

There was no actual suspend, as if it resumes without even suspending.

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-hibernate" does produce more output, but I guess the same as earlyer, with -38 errors. Attaching output.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[András Korn (kornandras)]

In case anyone finds this bug report when googling for this error: the problem is that the hpsa driver (which drives many HP RAID controllers) just doesn't support suspend.

The code (even in Linux 5.0.13) reads:

```
static int hpsa_suspend(__attribute__((unused)) struct pci_dev *pdev,
        __attribute__((unused)) pm_message_t state)
{
        return -ENOSYS;
}

static int hpsa_resume(__attribute__((unused)) struct pci_dev *pdev)
{
        return -ENOSYS;
}

static struct pci_driver hpsa_pci_driver = {
        .name = HPSA,
        .probe = hpsa_init_one,
        .remove = hpsa_remove_one,
        .id_table = hpsa_pci_device_id, /* id_table */
        .shutdown = hpsa_shutdown,
        .suspend = hpsa_suspend,
        .resume = hpsa_resume,
};
```

[Vincas Dargis (talkless)]

Thanks for the info!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

So it's not something fixable...