Patch landed in Ubuntu-5.4.0-55.61 (or newer) and since we are currently at:
linux-generic | 5.4.0.56.59 | focal-updates| s390x
the patch is included and rolled out (via -updates).
Hence updating focal entry to Fix Released.
--
You received this bug notification because you are a mem
Checking the focal git tree this is included in the Ubuntu kernels:
Ubuntu-5.4.0-55.61
Ubuntu-5.4.0-56.62
Ubuntu-5.4.0-57.63
And Ubuntu-5.4.0-56 just migrated to updates:
linux-generic | 5.4.0.56.59 | focal-updates| s390x
hence I'm updating this (focal) to Fix Released.
** Changed in
No, the issue is not yet fixed and rolled out with 20.04 updates.
It means that the issue is handled for focal/20.04 by the LP bug 1900624 and
that is just Fix Committed (and not yet Fix Released).
The status and plan is (as of today) that the commit 709192d531e5 ("s390/dasd:
Fix zero write for F
The focal part of this ticket is addressed by:
"Focal update: v5.4.69 upstream stable release"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900624
And LP 1900624 is Fix Committed and the patches are already applied to focal
master-next.
Hence aligning the status of this ticket to LP 19006
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Status: Expired => In Progress
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-tea
I just 'found' that it's included in upstream stable update 5.4.69:
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.69
So it will find it's way into focal via this route.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Ican see that this patch was brought upstream on 20200923 and was picked up
with v5.9-rc7,
hence it's first of all not in stock 5.4 or 5.8.
Digging a bit deeper into this I found that it already landed in groovy
(Ubuntu-5.8.0-21.22) via:
"Groovy update: v5.8.13 upstream stable release"
https://bu
[Expired for Ubuntu on IBM z Systems because there has been no activity
for 60 days.]
** Changed in: ubuntu-z-systems
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
Title:
dasd_fba io error and kernel panic
To manage notificat
I tried to re-create the situation over here.
I have a z/VM 6.4:
q cplevel
z/VM Version 6 Release 4.0, service level 1901 (64-bit)
Generated at 06/14/19 14:15:49 UTC
and there is a VM guest running from the time I did 18.04.4 regression testing,
hence it's up since quite some time:
buntu@zbox:~$
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
Title:
dasd_fba io error and kernel panic
To manage notifications
11 matches
Mail list logo
