Are there any plans to go forward with any of the above mentioned solutions?
Currently I either have to migrate off all guests before a qemu upgrade or set
up a tmpfs mount with exec on /run/qemu.
Happy to help testing.
--
You received this bug notification because you are a member of Ubuntu
Bu
I have retested with kernel 5.4.0-72 and qemu 1:4.2-3ubuntu6.15
With 5.4.0-72 on the host and 5.4.0-70 the MSR error (WRMSR to 0x48) is
consistently there. After updating the instance to 5.4.0-72 the MSR error is
gone without the need for the ibrs flag.
Booting mainline 5.11.14-051114-generic st
That should have said:
With 5.4.0-72 on the host and 5.4.0-70 in the guest the MSR error (WRMSR to
0x48) is consistently there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880
Title:
Add EPYC
I have an update regarding the missing "erms". This is apparently a bug
in the Milan 1.0.0.1 AGESA, which should be resolved with the next
update. Systems with Milan AGESA 1.0.0.0 are not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Before testing with linux 5.11.0-16-generic, qemu 1:5.2+dfsg-9ubuntu2,
libvirt 7.0.0-2ubuntu1:
# virsh domcapabilities |grep Milan
# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome P
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754
Title:
Add missing cpu feature bits in EPYC-Rome model
To
Before state as in LP#1921754 (linux 5.11.0-16-generic, qemu 1:5.2
+dfsg-9ubuntu2, libvirt 7.0.0-2ubuntu1)
With proposed:
# qemu-system-x86_64 -cpu ? | grep EPYC-Milan
x86 EPYC-Milan(alias configured by machine type)
x86 EPYC-Milan-v1 AMD EPYC-Milan P
Testing before with libvirt 6.0.0-0ubuntu8.8 on Xeon 6130 (Skylake):
Cascadelake-Server
Intel
With 6.0.0-0ubuntu8.9
Skylake-Server-IBRS
Old:
qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8
# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome Processor
# virsh domcapabilities
EPYC-Rome
AMD
focal: qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8
# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-Rome (alias configured by machi
focal: qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8
# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome Processor
x86 EPYC-v1 AMD EPYC Processor
x86
Please consider importing the 20210216 update from Debian where it has
been available since February. It contains fixes for INTEL-SA-00381 on
Skylake and CascadeLake systems.
** Summary changed:
- intel-microcode 20201118 bump request
+ intel-microcode 20210216 bump request
--
You received this
It seems one of the patches also introduced a regression:
* lp-1887490-cpu_map-Add-missing-AMD-SVM-features.patch
adds various SVM-related flags. Specifically npt and nrip-save are now expected
to be present by default as shown in the updated testdata.
This however breaks migration from instances
Public bug reported:
While I have found previous reports of this check failing, they are all
resolved years ago.
So I guess this is something for upstream.
device-mapper: btree spine: node_check failed: csum 544691913 != wanted
1983069109
[ cut here ]
kernel BUG at drive
Verified with xenial, bionic and focal images on Hetzner Cloud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905599
Title:
sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and
Groo
On focal (5.4.0-56-generic) we are starting to see massive file system
corruptions on systems updated to this kernel version.
These systems are using LVM with discards and thin provisioning on 6 or 8 NVMe
drives in a RAID10 near configuration. We are currently downgrading all systems
back to 5.4
Apparently not, but this was the only mentioning of this bug and the it
can be reproduced just the same way (bonding + vlan)
But after trying the mainline 4.18rc2 kernel, the bug is still present
their. So it needs to be fixed upstream first (again).
For reference:
# uname -a
Linux hostname 4.18
Thanks Joseph.
I tested the kernel with OpenBSD and FreeBSD virtual machines and this
patch seems to fix the timing issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
x86/kvm: fix
This happens pretty much on all Ubuntu kernels with the initial L1TF
implementation, so xenial, bionic and cosmic are also affected.
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.154
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.18.6
--
You received this bug notification
kernel from #7 resolves this on trusty as well (according to sysfs)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
To ma
still unresolved in 4.19rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778475
Title:
i40e: restore workaround for removing default MAC filter
To manage notifications about this bug go to:
https
This issue is still present. Possibly fixed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=a685557fbbc3122ed11e8ad3fa63a11ebc5de8c3
https://www.redhat.com/archives/dm-devel/2018-April/msg00022.html
kernel: [8860597.921484] kernel BUG at
proposed kernel for trusty still resolves this like test-kernel from #7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
T
Public bug reported:
udhcpd in bionic does not stop on SIGTERM due to an upstream change.
This was corrected by the following patch:
https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084
Please apply and backport/SRU this change to bionic.
** Affects: busybox (Ubun
The patch is merged upstream and will be in 5.6.
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.6&id=4feaef830de7ffdd8352e1fe14ad3bf13c9688f8
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=e9f8ca0ae7b7bc9a032b42992
Patch posted at
https://www.redhat.com/archives/dm-devel/2020-January/msg00021.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
To manage notificat
Since upgrading to 16.04 I have not seen this problem again. So I would
consider this issue resolved.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Unfortunately still present in mainline 5.0.13 kernel:
[ cut here ]
kernel BUG at drivers/md/persistent-data/dm-space-map-disk.c:178!
invalid opcode: [#1] SMP PTI
CPU: 5 PID: 1675751 Comm: kworker/u128:1 Not tainted 5.0.13-050013-generic
#201905051330
Hardware name: Q
Note the fixup patch removing monitor flag:
https://gitlab.com/libvirt/libvirt/-/commit/3bf6f9fe22dfbd3c1dcc614b31f2f4fe8b71a2f2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
[FFe/SR
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
To manage
With the 5.4.0-49 from focal-proposed the xsaves flag can now be passed
into instances.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
To
Thanks for the update. It looks like your libvirt build fails.
Most likely due to the following patch missing:
https://github.com/libvirt/libvirt/commit/58691208e2063285d981a620873d48ddf8df8be5
That patch adds the CooperLake test data (wrongly as CascadeLake-
Server), which is later fixed in
ht
Public bug reported:
When migrating a guest from a bionic host to a focal host, the guest may
hang during reboot. This is due to an upstream optimization that skips
ROM reset on incoming migrations.
Full details and patch in:
https://github.com/qemu/qemu/commit/5073b5d3ea303d37f4a8e2ea451d7a2eb1
The second one is: https://bugs.launchpad.net/qemu/+bug/1849644
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
To manage notifications abo
Actually no. It builds and does not have any downsides, but does not
resolve the issue. Sorry for that. When I looked at the history of
cpu_map and this patch, I did not see that it would require further
patches to actually make it work.
So that would leave it at these four patches:
Add-pschange-m
That's pretty much it. We triggered this fairly reliable as the qemu
versions in bionic and focal pretty much match the ones in the original
bug report. They were gone after we added the mentioned patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Thanks. It does not look like the "regression" preventing proposed
migration is caused by the qemu changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC
The new qemu version works as expected together with 5.4.0-49 kernel
required for xsaves
# grep -e 'model name' -e 'flags' /proc/cpuinfo
model name : AMD EPYC-Rome Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 h
Hi Juul,
these two flags are only present when SVM is enabled (which is unfortunately
default in Ubuntu).
We worked around this issue by modifying the target domain XML in live
migration to disable both flags if they are not present on the source side
(e.g. host running with older kernel).
I am
Plain qemu with the EPYC-Rome model works without any problems. I
already get xsave, xsaveopt, xsavec and xsaveerptr with the current
focal kernel, which also means that gcc finally uses znver1 (for v3) and
znver2 (for Rome) optimizations.
Libvirt would require cherrypicking a number of commits to
NSD will automatically start and bind itself to all available
interfaces. If you run systemd-resolved (the focal default), this will
fail. If you want to keep systemd-resolved, you must explicitly specify
the interfaces and/or IP addresses that NSD should listen on.
--
You received this bug notif
Without any configuration NSD will automatically start and binds itself
to port 53 on all available interfaces/ip addresses. It does not
actually conflict with systemd-resolved if both services are configured
explicitly. As a universe packages coming directly from Debian, its not
tuned to Ubuntu de
This is a universe package imported from Debian. It does not get support
from Canonical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781705
Title:
Memory leaks fixed in 4.1.21
To manage notifica
** Changed in: nsd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869815
Title:
package nsd (not installed) failed to install/upgrade: installed nsd
pa
** Changed in: nsd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880795
Title:
package nsd 4.1.26-1build1 failed to install/upgrade: installed nsd
package p
Well, for me it's more or less a noop because we have been running a
version with these patches for some time now. But nevertheless I haven't
encountered any problems using your build/patch series. Host
capabilities are correctly detected as EPYC-Rome and I can (still) start
an instance with the EP
Hetzner also provides instance ID via DMI information (system-serial-
number). So this could be used as a fallback should the metadata service
not respond
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I co-wrote the datasource. ;-)
I will prepare a MR to add the following to our DS:
def check_instance_id(self, sys_cfg):
return sources.instance_id_matches_system_uuid(
self.get_instance_id(), 'system-serial-number')
That should take care of those cases and prevent an alr
https://github.com/canonical/cloud-init/pull/630
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885527
Title:
cloud-init regenerating ssh-keys
To manage notifications about this bug go to:
https://
Same tests as above. Still working as intended
** Tags removed: patch verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
New images with the patched datasource have been rolled out on the
platform.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885527
Title:
cloud-init regenerating ssh-keys
To manage notifications ab
Public bug reported:
The EPYC-Rome model is missing the IBRS and SSBD flags due to an
oversight
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg07378.html
They have been added as a EPYC-Rome-v2 in
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01020.html
This patch depends o
Libvirt support for IBRS
https://gitlab.com/libvirt/libvirt/-/commit/5c17a7ba41670f3182186c06e621995b5d03fc95.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754
Title:
Add missing cpu feat
Public bug reported:
QEMU added a separate model for EPYC-Milan in
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg03370.html
On the qemu side most bits are already present as far back as focal. The
only things missing are the ibrs and svme-addr-chk flag.
On the libvirt side the same a
Hi Christian,
thanks for picking this up. No rush, we run with our build in the meantime.
I can also do tests for you on a Milan system, no problem.
I will also try to gather the missing tests and submit them to upstream
libvirt.
--
You received this bug notification because you are a member of
Again, thanks for putting so much thought into this. Yes, the Rome-v2
hasn't been merged, yet. But is trivial, so I expect no problems.
As for the Ubuntu integration, targeting this for 21.10 makes sense. By
then most things should be in place. In the meantime having a PPA or in
the server-backpor
Testing is done on EPYC 7763 and EPYC 7713 systems
Before: linux 5.4.0-70-generic, libvirt 6.0.0-0ubuntu8.8, qemu
1:4.2-3ubuntu6.14:
# virsh domcapabilities | grep EPYC
EPYC-Rome
EPYC-Rome
EPYC-IBPB
EPYC
After: libvirt 6.0.0-0ubuntu8.9~focalppa1, qemu
1:4.2-3ubuntu6.16~fo
As mentioned in LP#1921880 I get an unchecked MSR access when running a focal
guest with the EPYC-Rome model on a Milan CPU, but it did not crash. So if you
have access to a P620, which is pretty much a Milan CPU, you should be able to
reproduce this. It does not happen, if the guest has just th
With 5.11.12-051112-generic in the guest error changes to:
unchecked MSR access error: WRMSR to 0xda0 (tried to write 0x)
at rIP: 0x9587fa54 (native_write_msr+0x4/0x30)
Call Trace:
? fpu__init_cpu_xstate+0xb8/0xf0
fpu__init_system_xstate+0x143/0x354
fpu__init_system+0x6
fix was included in 4.4.0-177.207 (xenial), 4.15.0-92.93 (bionic),
5.3.0-46.38 (eoan), 5.4.0-15.18 (focal)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
It seems that the changes to cloud-initramfs-growroot have a side effect
that was not present before focal.
After initially provisioning an image, the root partition is resized in
initramfs, but cannot be mounted afterwards. A second boot to the now
resized disk works then without problems.
Remov
Public bug reported:
Qemu in focal has already support for most (except amd-stibp) flags of
this model.
Please backport the following patches:
https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c
https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e81
Hi Rafael,
thanks for the feedback. I would consider the patches to be non-
invasive, but important enough to justify an SRU. There are a similar
set of patches to add the missing bits to libvirt as well, except for
the EPYC-Rome model. I'll try to submit a patch upstream to add this
model.
--
Y
Still present in 4.15.0-47-generic even though a number of dm/thin fixes
have been backported
kernel: [1120717.622665] Modules linked in: cpuid xt_CHECKSUM xt_nat
iptable_nat nf_nat_ipv4 dm_snapshot veth dummy bridge nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables xt_CT iptable_raw i
Currently testing 5.0.10 as we think the issue is related to thin trying
to reallocate a discarded block not working correctly
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=cffd425b90147296c627dfb13f7ea8f361d962b2
** Changed in: linux (Ubuntu)
Sta
Intel has reverted the problematic licensing and Henrique has just
released the updated Debian package. Please merge and updated the Ubuntu
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/178712
Public bug reported:
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still
vulnerable
is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems
with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789834
Title:
off-by-one bug in L1TF mitigation
To manage notifications about this bug g
Since the L1TF has been disclosed yesterday, the update has become even
more urgent. The MCU also contains the necessary mitigations for SGX as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17833
Public bug reported:
Intel has released a new microcode version which includes updates for
further CPU models providing the necessary code for SSBD as well as the
recently disclosed L1TF vulnerability
https://downloadcenter.intel.com/download/28039/Linux-Processor-
Microcode-Data-File
Debian sho
If I'm not mistaken, the fix has been released with the latest kernel
update that was pushed for the L1TF issue. So this bug should be "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/17784
As the 20180807 MCU can currently not be distributed due to licensing
issues, this update is even more important as it at least provides the
SSBD and L1TF fixes for server CPUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
When using the bionic kernel (hwe-edge) on xenial we randomly trigger a
kernel bug when creating or querying a thin provisioned lvm volume.
kernel: [146487.421278] [ cut here ]
kernel: [146487.421281] kernel BUG at
/build/linux-hwe-edge-eBL7So/linux-
Also present in HWE kernel 4.15.0-23-generic #25~16.04.1-Ubuntu for
xenial
kernel: [450194.803852] [ cut here ]
kernel: [450194.803855] kernel BUG at
/build/linux-hwe-edge-ew4Cb4/linux-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178!
kernel: [450194.803
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
To manage notifications about this
Hi Joseph,
sure, but running an rc- kernel is not ideal for production systems, so I can
only give this limited exposure on a few canary systems.
I hope we can find a way to deterministically trigger this, to confirm a fix.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
results in forced promiscous mode when adding a vlan.
[ 10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on
PF, promiscuous mode forced on
Steps to reproduce and patch here:
http
Public bug reported:
OpenBSD guests encounter timing issues when running under bionic kernel.
This issue is actually present since 4.10 and is fixed by:
https://patchwork.kernel.org/patch/10411125/
See also
https://www.spinics.net/lists/kvm/msg161311.html
** Affects: linux (Ubuntu)
Impor
We have been running this microcode on Xenial in production for the last
month on a few hundred SNB, IVB, HSW, BDW and SKL systems without seeing
any regression.
Seems like Intel has gotten it right this time on the first try.
--
You received this bug notification because you are a member of Ubu
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
x86/kvm: fix LAPIC timer drift when guest uses period
Public bug reported:
Intel has released a new microcode version which includes the prerequisites
for SSBD patches
https://downloadcenter.intel.com/download/27945/Linux-Processor-
Microcode-Data-File
This enables Spetre v4 and 3a mitigations. The new version is already available
in Debian.
Plea
Is there anything I could do to help with this issue? Debian has now
also backports to jessie and stretch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780399
Title:
Update microcode to 20180703 v
fix confirmed spec-ctrl cpu flag is now visible inside kvm guest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744244
Title:
linux: 4.4.0-112.135 -proposed tracker
To manage notifications about th
The ppa package works for my use case. Maybe add this test-case to QA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
the updates-proposed build works in my case as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
To manage notifica
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20
as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network fil
Actually there is. Before this update, bond interfaces (specifically
802.3ad) were defaulting to ARP enabled. After the upgrade, they are
created with NOARP set on the link.
pre-upgrade:
eth0:
eth1:
bond0:
post-upgrade:
eth0:
eth1:
bond0:
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP
I opened LP #1727301 to track this further
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709135
Title:
add bond primary parameter
To manage notifications about this bug go to:
https://bugs.launchp
Public bug reported:
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial
as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the
the networking is configured via systemd-networkd.
bonding module is loaded with 'max_bonds=0' to address upcoming systemd change
https://github.com/systemd/systemd/issues/6184
pre-upgrade:
# networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback
I have been running the -29 kernel from
http://people.canonical.com/~smb/lp1568729/ for about two weeks now, so
far without triggering the bug. With the kernel from Tim, the bug could
still be triggered. So it seems there were different patches.
I'll try the -33 kernel from ppa as well, to see if
But that is not the -31 from the PPA. Could you please try the kernel
from the PPA that Stefan has posted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in
The -31 Kernel from Stefan's PPA with the patch has been running stable
for 2 weeks and the previous version based on -29 for 3 weeks. So if
that patch will make its way into Ubuntu kernel via the 4.4.16 stable
series update, the bug can be closed from my side at that point
--
You received this b
Public bug reported:
While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1 the
host system has crashed (load > 200) 3 times in the last 3 days.
Always with this stack trace:
Apr 9 19:01:09 cnode9.0 kernel: [197071.195577] divide error: [#1] SMP
Apr 9 19:01:09 cnode9.0 kerne
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - handle_mm_fault
Thanks. Will test and report back in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - handle_mm_fault
To manage notificati
Unfortunately, the issue is still present.
Apr 14 00:34:43 cnode17 kernel: [204922.475156] divide error: [#1] SMP
Apr 14 00:34:43 cnode17 kernel: [204922.475185] Modules linked in: cpuid arc4
md4 nls_utf8 cifs vhost_net vhost macvtap macvlan nfnetlink_queue nfnetlink
xt_CHECKSUM xt_nat ipt
the overflow bug, I mentioned, is this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/805341
which is fixed in 2.6.32-38.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/809313
Title:
mcel
We always do a burn in and memory test before putting systems in production.
Should a system exhibit multiple crashes, we revert back to a know stable
kernel version. If that doesn't solve the problem, we move the virtual machines
off and re-test the hardware. We are also talking about dozens of
We have traced most of the 2.6.32-40 crashes to memory errors, but I will wait
a couple of days to be sure.
Also we are slowly moving towards the -oneiric-backports kernel in preparation
for the precise release, the 3.0.0-17 kernels has almost definitely
introduced a regression (mce error in c
1 - 100 of 152 matches
Mail list logo
