Ubuntu
linux package

zram02 from kernel_misc test suite in LTP failed

Bug #1829992 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

startup='Wed May 22 07:02:20 2019'
zram02 1 TINFO: create '1' zram device(s)
zram02 1 TFAIL: unexpected num of devices: 4
zram02 2 TINFO: zram cleanup
tag=zram02 stime=1558508540 dur=0 exit=exited stat=1 core=no cu=1 cs=0

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-20-generic 4.18.0-20.21
ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 22 06:28 seq
 crw-rw---- 1 root audio 116, 33 May 22 06:28 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Wed May 22 07:52:48 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-20-generic N/A
 linux-backports-modules-4.18.0-20-generic N/A
 linux-firmware 1.175.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1829992

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 Cosmic):
status: New → Incomplete
Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu Cosmic):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in ubuntu-kernel-tests:
status: New → Confirmed
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-ltp
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This is probably caused by the unsuccessful zram01 test, which will create 4 devices.

no longer affects: linux (Ubuntu Cosmic)
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: Confirmed → Triaged
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Failed on B-hwe-edge 5.3 (zram01 passed) i386, with:

 tag=zram02 stime=1569014511 dur=0 exit=exited stat=33 core=no cu=0 cs=1
 startup='Fri Sep 20 21:21:51 2019'
 zram02 1 TINFO: create '1' zram device(s)
 zram02 1 TPASS: test succeeded
 zram02 2 TCONF: The device attribute max_comp_streams was introduced in kernel 3.15 and deprecated in 4.7
 zram02 3 TINFO: set disk size to zram device(s)
 sh: echo: I/O error
 zram02 3 TFAIL: can't set '107374182400' to /sys/block/zram0/disksize
 zram02 4 TINFO: zram cleanup
 sh: echo: I/O error

tags: added: sru-20190902
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

On Bionic, it's still failing with i386 but passed with other arches.

Sean Feole (sfeole)
tags: added: arm64
tags: added: eoan
removed: cosmic
tags: added: arm64-aws
Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
assignee: Po-Hsu Lin (cypressyew) → nobody
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: Triaged → Won't Fix
status: Won't Fix → Triaged
tags: added: sru-20200106
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Failed with B-i386

tags: added: sru-20200316
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This is still reproducible on B-hwe-5.3 on i386 node pepe (works with other arches)

 startup='Fri May 8 23:50:43 2020'
 zram02 1 TINFO: timeout per run is 0h 5m 0s
 zram02 1 TINFO: create '1' zram device(s)
 zram02 1 TPASS: test succeeded
 zram02 1 TCONF: The device attribute max_comp_streams was introduced in kernel 3.15 and deprecated in 4.7
 zram02 2 TINFO: set disk size to zram device(s)
 sh: echo: I/O error
 zram02 2 TFAIL: can't set '107374182400' to /sys/block/zram0/disksize
 sh: echo: I/O error
 zram02 2 TINFO: AppArmor enabled, this may affect test results
 zram02 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
 zram02 2 TINFO: loaded AppArmor profiles: none

 Summary:
 passed 1
 failed 1
 skipped 1
 warnings 0
 tag=zram02 stime=1588981843 dur=0 exit=exited stat=1 core=no cu=2 cs=1

tags: added: sru-20200427
tags: added: 5.3 bionic
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue on i386 is a different one, this bug should be closed.

Changed in ubuntu-kernel-tests:
status: Triaged → Fix Released
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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