megaraid_sas fails after rtcwake

Bug #1860313 reported by Tommy Giesler
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

It appears that in recent Kernel versions the megaraid_sas cannot properly handle suspend to RAM (rtcwake -m mem -s 30).

After the system wakes up, the megaraid_sas driver reports multiple errors and I/O to disks fails completely. A reset is required to make the machine work again.

----------------->%-----------------
Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: megaraid_sas 0000:18:00.0: Failed to register IRQ for vector 64.
Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -19
Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: PM: Device 0000:18:00.0 failed to resume async: error -19
-----------------%<-----------------

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Mon Jan 20 09:03:49 2020
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tommy Giesler (guardion) wrote :
Revision history for this message
Tommy Giesler (guardion) wrote :

bug also present in 5.5.0-050500rc7-generic #202001192030

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe (Ubuntu):
status: New → Confirmed
Revision history for this message
Tommy Giesler (guardion) wrote :

bug not present in 18.04 original kernel tree 4.15.0-74

Revision history for this message
Terry Rudd (terrykrudd) wrote :

Have you tested the latest 5.3.0-29 kernel to see if this is resolved

Revision history for this message
Khaled El Mously (kmously) wrote :

@Tommy Giesler: Could you please test with the latest kernels in -proposed to confirm that this bug isn't already resolved? Thanks

Revision history for this message
Tommy Giesler (guardion) wrote :

Sorry I was out of office until today. Please find the logs attached.

bug still present in 5.5.0-050500-generic #202001262030

Revision history for this message
Tommy Giesler (guardion) wrote :

latest kernel in proposed for bionic I could find: 5.3.0-28-generic #30~18.04.1-Ubuntu

bug still present.

Revision history for this message
Tommy Giesler (guardion) wrote :

I also tried 5.3.0-29 by downloading the eoan packages:
5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17 17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Tommy Giesler (guardion) wrote :

The issue appears to be fixed in Mainline Kernel 5.6.6.

So far, I have not done further research, when this fix was implemented excatly. If needed, I can do further mainline or -rc tests.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.