Public bug reported:
Some newer Dell systems (I experienced this on an Optiplex 7000) include
an Intel I219-LM NIC that is not supported by the 5.4.0 kernel. Later
versions of the HWE kernel do support this NIC.
That makes it impossible to use these systems with the FIPS kernel.
Since our imaging
The Xenial system that I installed the binary packages from the proposed
Bionic repository on has been running properly and stable since the 7th.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
I installed the proposed Bionic packages on my Xenial system and have
confirmed that basic functionality is working properly. If the system
remains stable for >24h, I will consider the issue to be fixed in this
kernel.
--
You received this bug notification because you are a member of Kernel
Packa
My Xenial system is still stable after almost two days with the kernel
package I built from the proposed Bionic kernel's source.
--
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/1871688
Titl
I built and installed the package on one of my Xenial systems from the
source available here:
https://launchpad.net/ubuntu/+source/linux/4.15.0-100.101
If the system is still stable a day from now, is it okay for me to set
the 'verification-done-bionic' tag, even though I'm testing on Xenial?
--
The only machines I've reproduced this bug on are running Xenial. For
the past few months, I've been applying these patches to the Xenial HWE
kernels and building packages for my dev/test systems.
These systems frequently add and remove targets (around 125 per hour)
with separate initiators connec
** Tags added: bionic focal
** Description changed:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when
** Attachment added: "contents of /proc/version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349844/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Attachment added: "output of `lspci -vvnn`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Attachment added: "dmesg output shortly after booting"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349845/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Public bug reported:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when a "targetcli iscsi/iqn.../tpg1 disable" co
11 matches
Mail list logo