libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x zVM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Won't Fix
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Steps:
1. sudo apt-get install git python-minimal -y
2. git clone --depth=1 git://kernel.
3. git clone --depth=1 git://kernel.
4. rm -fr autotest/
5. ln -sf ~/autotest-
6. AUTOTEST_
It will failed with the following python code piece when trying to access /proc/sys/
utils.write_
With error message:
[Errno 95] Operation not supported
For Xenial, the error message is:
[Errno 524] Unknown error 524
This issue is not a regression.
Full error log:
$ AUTOTEST_
07:20:37 INFO | Writing results to /home/ubuntu/
07:20:37 DEBUG| Initializing the state engine
07:20:37 DEBUG| Persistent state client.steps now set to []
07:20:37 DEBUG| Persistent option harness now set to None
07:20:37 DEBUG| Persistent option harness_args now set to None
07:20:37 DEBUG| Selected harness: standalone
07:20:48 INFO | START ---- ---- timestamp=
07:20:48 DEBUG| Persistent state client.
07:20:48 INFO | START libhugetlbfs libhugetlbfs timestamp=
07:20:48 DEBUG| Persistent state client.
07:20:48 DEBUG| Persistent state client.
07:20:49 DEBUG| Running 'apt-get install --yes --force-yes build-essential git gcc'
07:20:50 DEBUG| [stdout] Reading package lists...
07:20:50 DEBUG| [stdout] Building dependency tree...
07:20:50 DEBUG| [stdout] Reading state information...
07:20:50 DEBUG| [stdout] build-essential is already the newest version (12.4ubuntu1).
07:20:50 DEBUG| [stdout] gcc is already the newest version (4:7.2.0-1ubuntu1).
07:20:50 DEBUG| [stdout] git is already the newest version (1:2.14.
07:20:50 DEBUG| [stdout] The following packages were automatically installed and are no longer required:
07:20:50 DEBUG| [stdout] containerd linux-headers-
07:20:50 DEBUG| [stdout] linux-image-
07:20:50 DEBUG| [stdout] Use 'sudo apt autoremove' to remove them.
07:20:50 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
07:20:50 ERROR| [stderr] W: --force-yes is deprecated, use one of the options starting with --allow instead.
07:20:50 DEBUG| Running 'which gcc'
07:20:50 DEBUG| [stdout] /usr/bin/gcc
07:20:53 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/
_cherry_
File "/home/
return func(*p_args, **p_dargs)
File "/home/
str(
File "/home/
open_
File "/home/
f.close()
IOError: [Errno 95] Operation not supported
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-
ProcVersionSign
Uname: Linux 4.13.0-16-generic s390x
NonfreeKernelMo
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu3
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Thu Nov 2 07:18:00 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/
RelatedPackageV
linux-
linux-
linux-firmware 1.169
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in linux (Ubuntu): | |
status: | Incomplete → In Progress |
description: | updated |
description: | updated |
description: | updated |
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 1729510
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.