** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Hirsute)
** No longer affects: udev (Ubuntu)
** No longer affects: udev (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
To unblock the SRU process for this bug I'm updating the tag from
verification-needed-focal to verification-done-focal, however this
ticket does not affect focal and it was never marked as affecting focal
(see title and bug description), hence I think this tag should not have
occurred here.
** Tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
With that we can close the entire bug, since hirsute / 5.11 is now Fix
Released (#34), groovy / 5.8 is not affected (#17) and the patches are
upstream with 5.13 (#33), hence will end up sooner or later in impish.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Chan
This bug was fixed in the package linux - 5.11.0-18.19
---
linux (5.11.0-18.19) hirsute; urgency=medium
* hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the 465 driver series, fabric
Just as a heads up: The upstream stable update 5.11.20 for hirsute un-reverts
- "s390/cio: remove pm support from ccw bus driver"
and adds
- "s390/cio: remove invalid condition on IO_SCH_UNREG"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Testing former status with 5.11.0-17-generic
Journal:
Add:
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3,
anc=0, erc=4, rsid=5
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3,
anc=0, erc=4, rsid=0
May 17 05:56:26 h kernel: virtio_blk
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verifi
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in Hirsute
** Changed in: linux (Ubuntu Hirsute)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in H
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ Hot removal of disks under kvm on s390 does not result in the kernel
+ removing the block device, which can lead to hung tasks and other
+ issues.
+
+ [Test Plan]
+
+ See steps to reproduce the bug in the original description below.
The condition for css_sch_device_unregister(sch) also caught my eye,
calling it unconditionally is probably closer to right because it was
called in the !cdev case before, and in the attached patch it would no
longer be called in this case. However I think in the short term the
revert is the safest
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in Hirsute on
s390x
To manage notifications about this bug
** Tags added: architecture-s39064 bugnameltc-192463 severity-high
targetmilestone-inin2104
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devic
I was wondering if I could trigger the same issue on an lpar as it would
raise the severity IMHO. I have no claim on completeness of these tests
in regard to all that could happen. I tried what I considered low
hanging fruits in regard to this cross check.
Pre-condition each time
- a dasd attache
Yes, !resuming always evaluates to true because obviously the hot-unplug
test was not done in any system PM operations.
I am also unsure whether cdev can be NULL in that context so I left it
there. Other functions have similar cdev check too. I think IBM devs
will have more insights on this.
--
Hi Kaihenfeng,
Thanks for your patch suggestion! I'm semantically not sure it is the right
thing - to clarify your theory is that before it checked !resuming and before
had the check for !cdev maybe just to avoid a deference error. And now you
assume that instead of !cdev it should check if ther
Thanks Frank for adding the mirror request to this, because either way
we sooner or later want a discussion with the s390x developers on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Tit
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
** Tags added: reverse-proxy-bugzilla
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The check was for resuming flag, but now it's inverted. Please test this
patch.
** Patch added: "lp1925211.patch"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1925211/+attachment/5490454/+files/lp1925211.patch
--
You received this bug notification because you are a member of Ubuntu
Bu
Thanks Seth.
I have verified 5.11.0-16-generic #17+lp1925211v202104201520 from the PPA and
can confirm that the issue is gone.
=> The revert works as a fix \o/
For the severity/urgency at least we now know that it is s390x only (not "good"
but reduces the amount of affected people).
I'll later (
** Summary changed:
- Hot-unplug of disks leaves broken block devices around in Hirsute
+ Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Changed in: linux (Ubuntu Hirsute)
Milestone: None => hirsute-updates
--
You received this bug notification because you are
The commit reverts cleanly. We need to confirm that reverting the commit
does fix the issue. I put a test build here, please test.
https://people.canonical.com/~sforshee/lp1925211/
I doubt we can get a new kernel into the release. If it's extremely
urgent we can consider a day 0 SRU kernel for hi
But it makes sense in regard to the broken use case and explains why we
see it only on s390x.
@sforshee - what should we do about it now that we know which commit it
was - just revert it asap or are there bad dependencies to it?
--
You received this bug notification because you are a member of U
commit 8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
Author: Vineeth Vijayan
Date: Fri Nov 20 09:36:38 2020 +0100
s390/cio: remove pm support from ccw bus driver
As part of removing broken pm-support from s390 arch, remove
the pm callbacks from ccw-bus driver.The power-management fu
Ok build env set up and tested the starting points.
>From that I also see:
v5.10 - working
v5.11 - failing
So from here I think I can try a bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925211
I was trying mainline builds [1] to pinpoint the kernel change (if any).
I had a few totally failing ones which stalled me a bit, but eventually I can
show
this helpful list:
v5.8 - working
v5.10 - working
v5.10.31 - working
v5.11 - failing
v5.11.15 - failing
v5.12-rc8 - failing
So it isn't a >5
FYI
[15:43] cpaelzer, this may be related
https://github.com/systemd/systemd/blob/4d484e14bb9864cef1d124885e625f33bf31e91c/NEWS#L5
And indeed it is an interesting read, but for now the question is why only with
5.11@s390x then? Maybe there is something small to get this back in line? No
one i
** Also affects: udev (Ubuntu Hirsute)
Importance: Critical
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
You received this bug notification
Hirsute - udevadm
# attach
KERNEL[319.020043] add /devices/css0/0.0.0005 (css)
KERNEL[319.020088] add /devices/css0/0.0.0005/0.0.0005 (ccw)
KERNEL[319.020103] bind /devices/css0/0.0.0005/0.0.0005 (ccw)
UDEV [319.022297] add /devices/css0/0.0.0005 (css)
UDEV [319.022802] add
Hirsute - dmesg
# attach
[ 264.065866] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0,
erc=4, rsid=5
[ 264.065906] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0,
erc=4, rsid=0
[ 264.099347] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197
kB/193 KiB)
# detac
This even happens with the most common image-file backed disks which
further simplifies the repro:
$ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
$ virsh detach-disk h vdc
** Description changed:
Repro:
- # P
32 matches
Mail list logo
