** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
To manage
This bug was fixed in the package linux - 4.15.0-144.148
---
linux (4.15.0-144.148) bionic; urgency=medium
* bionic/linux: 4.15.0-144.148 -proposed tracker (LP: #1927648)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-ve
Using verification steps from bug 1916485
ubuntu@test-s390x:~$ uname -a
Linux test-s390x 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:16:31 UTC
2021 s390x s390x s390x GNU/Linux
ubuntu@test-s390x:~$ mkdir h
ubuntu@test-s390x:~$ cd h
ubuntu@test-s390x:~/h$ sudo tar xf ../hirsute-server-cloudimg
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 'verifica
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Ti
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
SRU Justification
+
+ Note: I marked this as affecting bionic as well, as discovered in bug
+ 1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit,
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
T
This bug was fixed in the package linux - 5.4.0-66.74
---
linux (5.4.0-66.74) focal; urgency=medium
* focal/linux: 5.4.0-66.74 -proposed tracker (LP: #1913152)
* Add support for selective build of special drivers (LP: #1912789)
- [Packaging] Add support for ODM drivers
-
Verified with 5.4.0-65 kernel, upgrading to the latest upstream systemd
hangs trying to restart services and hangs at boot.
Upgrading to the 5.4.0-66 kernel and then upgrading to the latest
upstream systemd does not hang and (re)boots successfully.
** Tags removed: verification-needed-focal
** Ta
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
I facing a whole load of odd issues in recent Hirsute LXD containers on s390x.
Only s390x, only Hirsute - The guests didn't complete systemd initialization,
some processes hang around, journal didn't start ...
ddstreet was so kind to recognize this on IRC and gave me a hint to this bug.
I was fom
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Fix Committed
** Tags added: s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Dan St
This also is blocking migration of upstream systemd CI from bionic to focal (on
s390x), as the system will hang at boot due to this problem when using upstream
systemd code on focal with the latest 5.4 ubuntu kernel. Test systemd build is
available at:
https://launchpad.net/~ddstreet/+archive/ub
specifically, this bug was introduced by the commit
69ba0dbfabf6c1ccd88eabd2ac3959b3ee08 introduced from stable series
bug 1885942, first included in version Ubuntu-5.4.0-43.47.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This needs to be backported to our 5.4 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
To manage notifications about
18 matches
Mail list logo