This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
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/1913442
Title:
[Ubuntu 20.04] Problem leading IUCV service
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable
I could validate this, didn't noticed any 'usercopy' messages - same
behavior like impish, hence updating tags...
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug is awaiting verification that the linux/5.4.0-97.110 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
Hi Karsten, no, nothing needed on top.
It's in status "Fix Committed", hence it's already available from the
-proposed pocket of the Ubuntu archive, and will be migrated to -release with
the next kernel update (which is a matter of days).
(What I just didn't understood was
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
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/1913442
Title:
[Ubuntu 20.04] Problem leading IUCV service
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1913442
Title:
[Ubuntu 20.04] Problem leading IUCV service
Hi Harald, well, I'm a bit confused - probably because I don't see the entire
discussion that you may have in bugzilla.
I guess you are talking about the new/add issue that was mentioned in LP
comment #7 ?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913442/comments/7
Well, since this
Hello Frank
hm, the output shows absolutely no relationship with AP bus or zcrypt device
driver code.
Neither the kernel callstack nor the userspace iucvserv application has any
relations to
my patch series.
--
You received this bug notification because you are a member of Kernel
Packages,
Patch request submitted for focal:
https://lists.ubuntu.com/archives/kernel-team/2021-October/thread.html#124589
changing status to 'In Progress' for focal.
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: ubuntu-z-systems
Status: Incomplete =>
191691 has not been mirrored to launchpad, thus Ubuntu developers cannot
see any of that details.
Note that Ubuntu does not have access to the LTC bugzilla, instead
bugproxy mirrors reports to Launchpad as needed. Please check with hws
if 191691 should be mirrored across, or not.
--
You
--- Comment From kgr...@de.ibm.com 2021-03-16 07:39 EDT---
(In reply to comment #24)
> In the console log I see the following error message:
>
> 5.836326? zvmguestconfigure619?: Successfully removed device 0.0.1000
> (enc1000)
> 9.973839? zvmguestconfigure652?: Scanning for network
Is it now a znetconf issue or still a kernel issue?
Can you manually enable the device by directly echo-ing to the sysfs entry?
(I guess the device is not in the cio ignore list or so.)
Did you also tried chzdev to enable it? (ideally with '--verbose')
(I was once told that this is the strategic
Yes, the two kernel are on the same level - I did a rebuild since the
above patch is common code and the kernel needed to be build on all
significant architectures - that's what I did based on the PPA.
So looks like the messages/warning are gone, but that there is another issue.
I'm changing the
A kernel test build (binary-debs) from s390x can be found here:
https://people.canonical.com/~fheimes/lp1913442/
Cross-arch. builds (for amd64, arm64, ppc64el and amd64) can be found in this
PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1913442
--
You received this bug notification
A PPA with a patched kernel is available for further testing:
https://people.canonical.com/~fheimes/lp1913442/
--
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/1913442
Title:
[Ubuntu
** Patch added: "backport of upstream commit 49f2d2419d60 to focal 5.4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is
Checking the Ubuntu kernel git trees for H, G and F, this patch is only needed
for focal.
(It became upstream accepted with 5.8).
Hence marking only focal as affected.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Assignee:
21 matches
Mail list logo
