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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1860523 Title: Fix misleading error message: Configuring the VNIC characteristics failed Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Triaged Bug description: SRU Justification: ------------------ [Impact] * For devices that don't support the 'INVISIBLE' characteristic (ie. OSA), the resulting IO failure raises the noisy error message "Configuring the VNIC characteristics failed" * The INVISIBLE characteristic unconditionally gets switched off, which is reverted with this patch. * For Internal Queued Direct communication (IQD) 'INVISIBLE' is off by default. * Hence the INVISIBLE characteristic case is unnecessary. [Fix] * 68c57bfd52836e31bff33e5e1fc64029749d2c35 68c57bf "s390/qeth: fix false reporting of VNIC CHAR config failure" * Upstream accepted with v5.5-rc5, but backport for 4.19-stable and 5.4-stable here: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git [Test Case] * Configure an IBM z15 for LinuxONE III machine with at least one OSA adapter. * Check dmsg for message "Configuring the VNIC characteristics failed" while setting an OSA device online. [Regression Potential] * The regression potential is low, since the patch is limited to a single line * again limited to the s390x architecture and once again limited to the qeth network driver * and on z15 hardware only. [Other Info] * This bug was identified at IBM while testing and is now rolled out to several different kernels. * Once the patch got applied to the Ubuntu kernel(s) and a verification is required, * this needs to be done by IBM, since Canonical doesn't have the needed machine generation. __________ The patch titled s390/qeth: fix false reporting of VNIC CHAR config failure has been added to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: s390-qeth-fix-false-reporting-of-vnic- char-config-failure.patch and it can be found in the queue-4.19 subdirectory. Same for the the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable- queue.git;a=summary The filename of the patch is: s390-qeth-fix-vnicc_is_in_use-if- rx_bcast-not-set.patch and it can be found in the queue-5.4 subdirectory. s390/qeth: fix false reporting of VNIC CHAR config failure commit 68c57bfd52836e31bff33e5e1fc64029749d2c35 upstream. Request: Please provide that fix also for Ubuntu 18.04 . Many thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860523/+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
