dmesg output:
[ 61.741644] Hardware name: IBM 2964 N63 400 (LPAR)
[ 61.741645] Krnl PSW : 00000000d4fd3f9b 000000008aabe5b8
(__alloc_pages_nodemask+0xe96/0x1068)
[ 61.741649] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0
RI:0 EA:3
[ 61.741650] Krnl GPRS: 0000000000000000 00000000006000c1 00000000006000c1
0000000000000000
[ 61.741651] 0000000000000000 000000006fff3700 0000000000000000
000003ff8117c800
[ 61.741652] 0000000000b39000 000003ff8117ca50 000003ff8117f000
0000000000000000
[ 61.741653] 0000000000000000 0000000000901b00 00000000002e56e8
000000005c18f9b8
[ 61.741661] Krnl Code: 00000000002e645a: a7110200 tmll %r1,512
00000000002e645e: a774f94a brc 7,2e56f2
#00000000002e6462: a7f40001 brc
15,2e6464
>00000000002e6466: a7f4f946 brc
15,2e56f2
00000000002e646a: e31003380004 lg %r1,824
00000000002e6470: d503f15819c0 clc
344(4,%r15),2496(%r1)
00000000002e6476: a784febc brc 8,2e61ee
00000000002e647a: a7f4fa73 brc
15,2e5960
[ 61.741674] Call Trace:
[ 61.741676] ([<00000000002e56e8>] __alloc_pages_nodemask+0x118/0x1068)
[ 61.741677] [<00000000002e0bca>] __get_free_pages+0x2a/0x60
[ 61.741680] [<000003ff8117a2e0>] hmcdrv_cache_startup+0x68/0xd0 [hmcdrv]
[ 61.741682] [<000003ff8117f03e>] hmcdrv_mod_init+0x3e/0x1000 [hmcdrv]
[ 61.741684] [<0000000000100878>] do_one_initcall+0x48/0x1d0
[ 61.741687] [<0000000000216f52>] do_init_module+0x7a/0x260
[ 61.741688] [<00000000002196e6>] load_module+0x16ee/0x1968
[ 61.741689] [<0000000000219bce>] sys_finit_module+0xb6/0xf8
[ 61.741693] [<00000000008f0dc0>] system_call+0xdc/0x2c8
[ 61.741693] Last Breaking-Event-Address:
[ 61.741695] [<00000000002e6462>] __alloc_pages_nodemask+0xe92/0x1068
[ 61.741696] ---[ end trace 3870bf3953e53424 ]---
[ 61.741697] hmcdrv.a3150c: Allocating the requested cache size of 134217728
bytes failed
[ 108.285532] hmcdrv.a3150c: Allocating the requested cache size of 67108864
bytes failed
[ 120.229043] hmcdrv.a3150c: Allocating the requested cache size of 33554432
bytes failed
[ 130.020224] hmcdrv.a3150c: Allocating the requested cache size of 16777216
bytes failed
[ 143.255667] hmcdrv.a3150c: Allocating the requested cache size of 8388608
bytes failed
[ 155.345222] hmcdrv.a3150c: Allocating the requested cache size of 4194304
bytes failed
[ 165.291445] hmcdrv.a3150c: Allocating the requested cache size of 2097152
bytes failed
[ 173.740144] hmcdrv.a3150c: Allocating the requested cache size of 2097152
bytes failed
[ 279.595926] hmcdrv: `1G' invalid for parameter `cachesize'
[ 285.847067] hmcdrv: `512M' invalid for parameter `cachesize'
[ 708.461429] hmcdrv.a3150c: Allocating the requested cache size of 1050624
bytes failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806115
Title:
cannot set hmcdrv cachesize to 1GB
Status in linux package in Ubuntu:
Confirmed
Bug description:
On an LPAR, execute Customize/Delete Activation Profile. Customize
profile. In security section, tick "Input/Output (I/O) configuration
control". Save. Ok. Close.
Execute Deactivate task.
Execute Activate task.
ssh into lpar.
Try to modprobe hmcdrv module, whilst setting cachesize to 1GiB. Going
down to the smallest permissible value.
First, observe that suffixes do not appear to be accepted, despite the
documentation stating that it should be supported:
ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=1G
modprobe: ERROR: could not insert 'hmcdrv': Invalid argument
ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=512M
modprobe: ERROR: could not insert 'hmcdrv': Invalid argument
Next try to request largish amounts of cache, and note how those calls fail:
$ sudo modprobe hmcdrv cachesize=134217728
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=67108864
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=33554432
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=16777216
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=8388608
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=4194304
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=2097152
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=2097152
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
# 1MiB + 2048 bytes
$ sudo modprobe hmcdrv cachesize=1050624
modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory
$ sudo modprobe hmcdrv cachesize=1048576
$ echo $?
0
The LPAR in question is configured with 2000MB of storage
(RAM/memory), thus imho should be able to handle more than 1MiB
cachesize, when there are more than 900MiB of free storage:
$ free -h
total used free shared buff/cache
available
Mem: 1.7Gi 348Mi 913Mi 0.0Ki 459Mi
1.3Gi
Swap: 1.9Gi 0B 1.9Gi
Is 1MiB some kind of a cachesize limit of the hmcdrv module? Can it be fixed
and/or bumped to be unlimited? I'm looking forward to be able to use a 1GiB
cachesize.
---
ProblemType: Bug
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.10-0ubuntu14
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.
DistroRelease: Ubuntu 19.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=0972d5df-b2f2-499e-a787-9fb90b7ebf00
crashkernel=256M break=bottom BOOT_IMAGE=1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
RelatedPackageVersions:
linux-restricted-modules-4.18.0-11-generic N/A
linux-backports-modules-4.18.0-11-generic N/A
linux-firmware 1.176
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: disco
Uname: Linux 4.18.0-11-generic s390x
UpgradeStatus: Upgraded to disco on 2018-11-20 (10 days ago)
UserGroups: adm cdrom cpacfstats dip kvm libvirt lpadmin lxd plugdev
sambashare sbuild sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806115/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
