[Kernel-packages] [Bug 1845323] Re: Trying to online dasd drive results in invalid input/output from the kernel on z/VM

2019-09-27 Thread Christian Borntraeger 
We are working on a fix. Can you give this testpatch a spin?

** Patch added: "testpatch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5291775/+files/0001-s390-dasd-Fix-error-handling-during-online-processin.patch

-- 
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/1845323

Title:
  Trying to online dasd drive results in invalid input/output from the
  kernel on z/VM

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Trying to online dasd drive results in invalid input/output from the
  kernel on z/VM

  [Fix]

  * ? TODO - hopefully patch attached ?

  [Test Case]

  * Ubuntu on z/VM guest installation and selecting at least one DASD
  device (that's not defined as dedicated).

  * Alternatively doing an Ubuntu on z/VM guest installation on
  zFCP/SCSI disk and manually activating a DASD device post-install with
  'chzdev -e '.

  [Regression Potential]

  * The kernel (aka DASD module) currently just fails on activating a
  (non dedicated) DASD.

  * But regressions might be introduced in the DASD stack so that is
  fails later on LPAR installation, too - but this can easily be tested
  (and will be).

  * The chance that zFCP/SCSI disks are harmed by accident is quite low,
  since this is a very different stack.

  [Other Info]

  * This is a regression that was introduced with the thin dasd provisioning 
feature that landed upstream with kernel 5.2/5.3, so affects Eoan only.
  __

  Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed
  Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file 
/sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error
  Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active 
configuration only
  Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed 
with error code 1
  Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed.
  Sep 25 12:06:39 kernel: [  137.472853] dasd-eckd.401b68: 0.0.0200: A channel 
path to the device has become operational
  Sep 25 12:06:39 kernel: [  137.473914] dasd-eckd.6b7759: 0.0.0200: Reading 
the volume storage information failed with rc=-5
  Sep 25 12:06:39 kernel: [  137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD 
online with discipline ECKD failed with rc=-5
  Sep 25 12:06:39 kernel: [  137.473918] [ cut here ]
  Sep 25 12:06:39 kernel: [  137.473943] WARNING: CPU: 0 PID: 4638 at 
kernel/module.c:1137 module_put.part.0+0xe2/0xe8
  Sep 25 12:06:39 kernel: [  137.473944] Modules linked in: lcs ctcm fsm zfcp 
scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey 
crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt
  Sep 25 12:06:39 kernel: [  137.473953] CPU: 0 PID: 4638 Comm: chzdev Not 
tainted 5.3.0-10-generic #11-Ubuntu
  Sep 25 12:06:39 kernel: [  137.473954] Hardware name: IBM 2964 N63 400 (z/VM 
6.4.0)
  Sep 25 12:06:39 kernel: [  137.473955] Krnl PSW : 0704c0018000 
2b2c3372 (module_put.part.0+0xe2/0xe8)
  Sep 25 12:06:39 kernel: [  137.473958]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
  Sep 25 12:06:39 kernel: [  137.473959] Krnl GPRS: 0004 
0006 0024 0007
  Sep 25 12:06:39 kernel: [  137.473960]0007 
7f2ce800 fffb 03ff80151578
  Sep 25 12:06:39 kernel: [  137.473961]fffb 
03ff80074df8 03ff80151900 78105800
  Sep 25 12:06:39 kernel: [  137.473962]7e17e600 
0bf8 2b2c336e 03e000c5fb08
  Sep 25 12:06:39 kernel: [  137.473969] Krnl Code: 2b2c3362: 
c0200048859a  larl%r2,2bbd3e96
  Sep 25 12:06:39 kernel: [  137.473969]2b2c3368: 
c0e5fffe16a4  brasl   %r14,2b2860b0
  Sep 25 12:06:39 kernel: [  137.473969]   #2b2c336e: a7f40001  
brc 15,2b2c3370
  Sep 25 12:06:39 kernel: [  137.473969]   >2b2c3372: a7f4ffb1  
brc 15,2b2c32d4
  Sep 25 12:06:39 kernel: [  137.473969]2b2c3376: 0707  
bcr 0,%r7
  Sep 25 12:06:39 kernel: [  137.473969]2b2c3378: 
c004  brcl0,2b2c3378
  Sep 25 12:06:39 kernel: [  137.473969]2b2c337e: 
ec280006007c  cgij%r2,0,8,2b2c338a
  Sep 25 12:06:39 kernel: [  137.473969]2b2c3384: 
c0f4ff86  brcl15,2b2c3290
  Sep 25 12:06:39 kernel: [  137.473980] Call Trace:
  Sep 25 12:06:39 kernel: [  137.473982] ([<2b2c336e>] 
module_put.part.0+0xde/0xe8)
  Sep 25 12:06:39 kernel: [  137.473994]  [<03ff80074df8>] 
dasd_generic_free_discipline+0x68/0x80 [dasd_mod]
  Sep 25 12:06:39 kernel: [

[Kernel-packages] [Bug 1533646] Re: Could you set vm.allocate_pgste = 1 by default?

2016-01-21 Thread Christian Borntraeger 
My modprobe.conf solution might not work in all cases, as the kvm module might 
be loaded on demand by a process accessing /dev/kvm. That process then already 
has 2k page tables.
 So I agree with Viktor: If we want to support KVM, maybe set  
vm.allocate_pgste = 1 unconditionally.

-- 
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/1533646

Title:
  Could you set vm.allocate_pgste = 1 by default?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  to use qemu one needs  vm.allocate_pgste = 1, on kernels that support that 
setting e.g. s390x.
  I'm now setting it with a sysctl.d snippet in procps package, however I was 
wondering if it could be set by default.

  Or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533646/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1533646] Re: Could you set vm.allocate_pgste = 1 by default?

2016-01-21 Thread Christian Borntraeger 
ok, kvm builtin certainly makes sense if you plan to use it regularly.
So in essence its a question about: do we expect a number of users to use KVM 
in Ubuntu or not?

-- 
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/1533646

Title:
  Could you set vm.allocate_pgste = 1 by default?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  to use qemu one needs  vm.allocate_pgste = 1, on kernels that support that 
setting e.g. s390x.
  I'm now setting it with a sysctl.d snippet in procps package, however I was 
wondering if it could be set by default.

  Or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533646/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1533646] Re: Could you set vm.allocate_pgste = 1 by default?

2016-01-20 Thread Christian Borntraeger 
the TCG emulation of QEMU does work without allocatr_pgste. 
vm.allocate_pgste=1 is necessary to use the KVM kernel module (which is used by 
qemu in kvm mode)

The main difference is that this uses 4k page tables instead of 2k page
tables on s390. So enabling pgstes will increase the page table
overhead. The difference is usually pretty small, but might become
noticeable when you have things like a big database with hundreds of
processes accessing a big area of shared memory.

Maybe something like
# cat /etc/modprobe.d/99-kvm.conf 
install kvm /sbin/sysctl vm.allocate_pgste=1; /sbin/modprobe --ignore-install 
kvm
remove kvm /sbin/sysctl vm.allocate_pgste=0; /sbin/modprobe -r --ignore-remove 
kvm

would be good enough?

-- 
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/1533646

Title:
  Could you set vm.allocate_pgste = 1 by default?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  to use qemu one needs  vm.allocate_pgste = 1, on kernels that support that 
setting e.g. s390x.
  I'm now setting it with a sysctl.d snippet in procps package, however I was 
wondering if it could be set by default.

  Or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533646/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp