zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4

Bug #1757937 reported by Po-Hsu Lin on 2018-03-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Po-Hsu Lin
Artful
Medium
Po-Hsu Lin
Bionic
Medium
Po-Hsu Lin

Bug Description

The zram smoke test failed due to the absence of the zram module.

modprobe: FATAL: Module zram not found in directory /lib/modules/4.13.0-1012-gcp

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1757937

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Changed in linux (Ubuntu Artful):
status: New → Triaged
importance: Undecided → Medium
tags: added: artful kernel-da-key

This issue can be spotted on AWS Bionic kernel as well:
20:30:46 DEBUG| modprobe: FATAL: Module zram not found in directory /lib/modules/4.15.0-1002-aws
20:30:46 DEBUG| modprobe: FATAL: Module zram not found in directory /lib/modules/4.15.0-1002-aws

summary: - zram smoke test failed on GCP 4.13
+ zram smoke test failed on GCP 4.13 / AWS 4.15
Po-Hsu Lin (cypressyew) wrote :

Affecting Xenial AWS kernel as well 4.4.0-1053.62

tags: added: xenial
summary: - zram smoke test failed on GCP 4.13 / AWS 4.15
+ zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4
Khaled El Mously (kmously) wrote :

@Po-Hsu Lin When I build this kernel tag, I see linux-image-extra is built and it has the zram module inside it.

How can I reproduce this issue myself?

Po-Hsu Lin (cypressyew) wrote :

For the GCP kernel, yes it's missing the linux-image-extra-4.13.0-1012-gcp package, this issue will gone with that package installed.

However as this package was not installed by default (when the instance got deployed), we had a similar issue for aufs.ko for s390x before:
https://lists.ubuntu.com/archives/kernel-team/2017-March/082978.html

This can be fixed from the test suite or just doing the same thing above.

For the AWS kernel, there is no extra package available.
$ apt-cache search extra| grep linux
linux-image-extra-4.15.0-1001-gcp - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
linux-image-extra-4.15.0-1002-azure - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
linux-image-extra-4.15.0-13-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
linux-image-extra-virtual - Extra drivers for Virtual Linux kernel image
ganglia-modules-linux - Ganglia extra modules for Linux (IO, filesystems, multicpu)
linux-image-extra-4.15.0-1003-azure - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP

Po-Hsu Lin (cypressyew) wrote :
Changed in linux (Ubuntu Artful):
status: Triaged → Fix Released
Changed in linux (Ubuntu Bionic):
status: Triaged → Fix Released
Changed in linux (Ubuntu Artful):
assignee: nobody → Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu Bionic):
assignee: nobody → Po-Hsu Lin (cypressyew)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers