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 FBA devices") landed in Ubuntu's focal master-next git tree.
And according to 'kernel.ubuntu.com' an new binary kernel will be build and
made available for testing in '-proposed' around 13-Nov. And if the "Bug
verification & Regression testing" doesn't show any problems, this kernel will
then be released to '-updates' around 30-Nov.
All kernel updates are usually processed by 3-weekly 'kernel SRU' cycles that
are posted here: https://kernel.ubuntu.com/
But due to internal rearrangements and changes one SRU cycle is skipped this
time ("There will be no SRU cycle from October 12 through November 8.").
But the fix is already included in Ubuntu 20.10, which was released just
yesterday!
To shorten the time a bit until it get's released for focal/20.04, I
just compile a kernel based on the current master-next (that should have
the fix in) and made it available for testing here:
https://people.canonical.com/~fheimes/lp1867118/
--
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/1867118
Title:
dasd_fba io error and kernel panic
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Bug description:
Generated I/O errors every hour in syslog and caused kernel panic with
workloads running
---uname output---
Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC
2020 s390x s390x s390x GNU/Linux
---Patches Installed---
distro provided. up-to-date from Ubuntu18.04.
Machine Type = z15
---System Hang---
The hourly generated I/O errors didn't impact the system up and running.
When there are workloads on it, it will cause kernel panic and rebooted the
server.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
After migrated from 16.04 to 18.04, will see the i/o errors.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
Device driver error code:
[52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and
failed
[52297.898244] dasd(fba): I/O status report for device 0.0.0100:
dasd(fba): in req: 000000002e142bcd CS: 0x20 DS: 0x0C
dasd(fba): device 0.0.0100: Failing CCW: 00000000a84f6c9f
dasd(fba): SORRY - NO VALID SENSE AVAILABLE
[52297.898255] dasd(fba): Related CP in req: 000000002e142bcd
dasd(fba): CCW 00000000d15f44d3: 63400010 7FE2BBA0 DAT:
00000200 008150F2 00000000 00000017
dasd(fba): CCW 00000000b09ad76e: 43400008 7FE2BBB0 DAT:
05000006 00000000
dasd(fba): CCW 00000000c44dfb20: 41600C00 F3600000 DAT:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
dasd(fba): CCW 00000000a84f6c9f: 43400008 7FE2BBB8 DAT:
05000010 00000006
dasd(fba): CCW 0000000022dac88c: 41600000 00000000 DAT:
dasd(fba): CCW 0000000069686544: 43400008 7FE2BBC0 DAT:
05000002 00000016
dasd(fba): CCW 000000007bb6a17c: 41200400 F3600000 DAT:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
*Additional Instructions for [email protected]:
-Attach sysctl -a output output to the bug.
[reply] [?]
Internal Only
Comment 1 QI YE 2020-03-12 02:29:20 CDT
The z/VM version 6.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+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
