[Bug 1968258] Re: Data corruption in qemu_rbd_co_block_status

[Markus Schade]

Hi Christian,

thanks you very much for getting this out of the door so fast!
I can confirm that new version with the patches resolves the issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968258

Title:
  Data corruption in qemu_rbd_co_block_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1968258/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968258] [NEW] Data corruption in qemu_rbd_co_block_status

[Markus Schade]

Public bug reported:

Hi Christian,

we have started testing jammy and triggered a qemu bug which has already
been fixed upstream.

The qemu 6.2 in jammy has currently a buggy implementation of 
.bdrv_co_block_status in block/rbd.
This can result in data corruption and/or crash of the instance.

https://tracker.ceph.com/issues/53784

Please consider backporting the following patches into qemu jammy before
the release:

https://git.qemu.org/?p=qemu.git;a=patch;h=9e302f64bb407a9bb097b626da97228c2654cfee
https://git.qemu.org/?p=qemu.git;a=patch;h=fc176116cdea816ceb8dd969080b2b95f58edbc0

A repoducer is in the Ceph tracker. Trying to create a qcow2 snapshot
from a running rbd-backed  virtual machine will lead to a crash of the
virtual machine, e.g.

# virsh snapshot-create-as --domain vm-123 --no-metadata --disk-only
--diskspec sda,file=/var/lib/libvirt/qemu/snapshot/disk-123.qcow2

Resulting core dump:

#0  0x7fbaee61f18b in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbaee5fe859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fbaee5fe729 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x7fbaee60ff36 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7fbaed64663f in qemu_rbd_co_block_status (bs=, 
want_zero=, offset=4259840, bytes=12288, pnum=0x7fba27bfb980, 
map=, file=0x7fba27bfb6c8) at ../../block/rbd.c:1355
#5  0x5566ab8f574c in bdrv_co_block_status (bs=0x5566ac468220, 
want_zero=want_zero@entry=false, offset=4259840, bytes=12288, 
pnum=pnum@entry=0x7fba27bfb980, map=map@entry=0x7fba27bfb770, 
file=0x7fba27bfb778) at ../../block/io.c:2489
#6  0x5566ab8f582b in bdrv_co_block_status (bs=bs@entry=0x5566ac62ffd0, 
want_zero=want_zero@entry=false, offset=offset@entry=4259840, 
bytes=bytes@entry=12288, pnum=pnum@entry=0x7fba27bfb980, map=map@entry=0x0, 
file=0x0) at ../../block/io.c:2557
#7  0x5566ab8f8589 in bdrv_co_common_block_status_above 
(bs=bs@entry=0x5566acdf0400, base=base@entry=0x0, 
include_base=include_base@entry=false, want_zero=want_zero@entry=false, 
offset=offset@entry=4259840, bytes=bytes@entry=12288, pnum=0x7fba27bfb980, 
map=0x0, file=0x0, depth=0x7fba27bfb824) at ../../block/io.c:2667
#8  0x5566ab8c975a in bdrv_common_block_status_above (bs=0x5566acdf0400, 
base=base@entry=0x0, include_base=include_base@entry=false, 
want_zero=want_zero@entry=false, offset=4259840, bytes=bytes@entry=12288, 
pnum=0x7fba27bfb980, map=0x0, file=0x0, depth=0x0) at block/block-gen.c:444
#9  0x5566ab8f8920 in bdrv_co_is_zero_fast (bs=bs@entry=0x5566acdf0400, 
offset=, bytes=12288) at ../../block/io.c:2755
#10 0x5566ab91c924 in is_zero_cow (m=0x5566ac938660, bs=0x5566acdf0400) at 
../../block/qcow2.c:2477
#11 handle_alloc_space (l2meta=, bs=0x5566acdf0400) at 
../../block/qcow2.c:2477
#12 qcow2_co_pwritev_task (l2meta=, qiov_offset=, 
qiov=0x5566ad374160, bytes=, offset=, 
host_offset=, bs=0x5566acdf0400) at ../../block/qcow2.c:2550
#13 qcow2_co_pwritev_task_entry (task=) at 
../../block/qcow2.c:2594
#14 0x5566ab919866 in qcow2_add_task (bs=bs@entry=0x5566acdf0400, 
pool=pool@entry=0x0, func=func@entry=0x5566ab91c640 
, 
subcluster_type=subcluster_type@entry=QCOW2_SUBCLUSTER_UNALLOCATED_PLAIN, 
host_offset=471040, offset=offset@entry=4272128, bytes=4096, 
qiov=0x5566ad374160, qiov_offset=0, l2meta=0x5566ac938660) at 
../../block/qcow2.c:2249
#15 0x5566ab919fe7 in qcow2_co_pwritev_part (bs=0x5566acdf0400, 
offset=4272128, bytes=4096, qiov=0x5566ad374160, qiov_offset=0, 
flags=) at ../../block/qcow2.c:2645
#16 0x5566ab8f9099 in bdrv_driver_pwritev (bs=bs@entry=0x5566acdf0400, 
offset=offset@entry=4272128, bytes=bytes@entry=4096, 
qiov=qiov@entry=0x5566ad374160, qiov_offset=qiov_offset@entry=0, 
flags=flags@entry=0) at ../../block/io.c:1252
#17 0x5566ab8fb15f in bdrv_aligned_pwritev (child=0x5566ac6271e0, 
req=0x7fba27bfbe00, offset=4272128, bytes=4096, align=, 
qiov=0x5566ad374160, qiov_offset=0, flags=0) at ../../block/io.c:2126
#18 0x5566ab8fbba8 in bdrv_co_pwritev_part (child=0x5566ac6271e0, 
offset=, offset@entry=4272128, bytes=, 
bytes@entry=4096, qiov=, qiov@entry=0x5566ad374160, 
qiov_offset=, qiov_offset@entry=0, flags=flags@entry=0) at 
../../block/io.c:2314
#19 0x5566ab8ec21d in blk_co_do_pwritev_part (blk=0x5566ad94e410, 
offset=4272128, bytes=4096, qiov=0x5566ad374160, 
qiov_offset=qiov_offset@entry=0, flags=0) at ../../block/block-backend.c:1283
#20 0x5566ab8ec38f in blk_aio_write_entry (opaque=0x5566adfeefc0) at 
../../block/block-backend.c:1467
#21 0x5566ab9ddaa3 in coroutine_trampoline (i0=, 
i1=) at ../../util/coroutine-ucontext.c:173
#22 0x7fbaee637660 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#23 0x7ffc5fa8c270 in ?? ()
#24 0x in ?? ()

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968258

[Bug 1913421] Re: Load of pre-upgrade qemu modules needs to avoid noexec

[Markus Schade]

As this has bitten us more than once in the past, we had to find a solution 
that would work for us while this issue was discussed. Adding a mount unit 
without noexec for /run/qemu was the obvious and most straightforward solution. 
We have on average at least one qemu update between reboots, so having a 
reliable and trackable mount unit would be the preferred solution. 
But I do acknowledge that the DH acrobatics are a bit ugly. :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913421

Title:
  Load of pre-upgrade qemu modules needs to avoid noexec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913421] Re: Load of pre-upgrade qemu modules needs to avoid noexec

[Markus Schade]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913421

Title:
  Load of pre-upgrade qemu modules needs to avoid noexec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913866] Re: intel-microcode 20210216 bump request

[Markus Schade]

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 bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913866

Title:
  intel-microcode 20210216 bump request

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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 EPYC-v2 AMD EPYC Processor (with IBPB)
x86 EPYC-v3 AMD EPYC Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


After:

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-Milan (alias configured by machine type)
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome Processor
x86 EPYC-Rome-v2 AMD EPYC-Rome Processor
x86 EPYC-v1 AMD EPYC Processor
x86 EPYC-v2 AMD EPYC Processor (with IBPB)
x86 EPYC-v3 AMD EPYC Processor


  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Still working as expected


** 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/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


After:

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-Milan(alias configured by machine type)  
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-Rome-v2  AMD EPYC-Rome Processor 
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor   


  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Still working as expected

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


New:
# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-Rome-v2  AMD EPYC-Rome Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Instance with ibrs flag can now be run

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 23
model   : 49
model name  : AMD EPYC-Rome Processor
stepping: 0
microcode   : 0x165
cpu MHz : 2495.312
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor 
lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw 
topoext perfctr_core ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 
rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero 
xsaveerptr wbnoinvd arat npt nrip_save umip rdpid
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4990.62
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:


Migration of guest (e.g. with EPYC-IBPB or EPYC-Rome) from previous version to 
proposed still works.

Migration of guest (EPYC-Rome with ibrs) to previous version doesn't (as
expected)

** 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/1921754

Title:
  Add missing cpu feature bits in EPYC-Rome model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922907] Re: Unable to use Skylake capability on Cascadelake server

[Markus Schade]

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
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


On Xeon 5218 (CascadeLake)

Before/After (no change):


  Cascadelake-Server
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907

Title:
  Unable to use Skylake capability on Cascadelake server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1922907/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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 Processor

# virsh domcapabilities
...

  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

...


Launching a guest with with EPYC-Milan works:

# cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 25
model   : 1
model name  : AMD EPYC-Milan Processor
stepping: 1
microcode   : 0x165
cpu MHz : 2445.404
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand 
hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 
3dnowprefetch osvw topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp 
vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt 
clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr wbnoinvd arat npt 
nrip_save umip pku ospke rdpid fsrm
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4890.80
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:


** 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/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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 Processor 

After installing proposed for qemu/libvirt:

# virsh domcapabilities 

  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)

x86 EPYC-Rome-v1  AMD EPYC-Rome Processor   

x86 EPYC-Rome-v2  AMD EPYC-Rome Processor

Starting focal instance with:

  
EPYC-Rome



  

# grep -P 'ssbd|ibrs' /proc/cpuinfo 
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor 
lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw 
topoext perfctr_core ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 
rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero 
xsaveerptr wbnoinvd arat npt nrip_save umip rdpid

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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 to Ubuntu.
https://bugs.launchpad.net/bugs/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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 still has the other error (RDMSR from 
0xda0).

So right now, I am using our build with the ibrs flag to get rid of the
MSR 0x48 error on all distros, even though it's gone with 5.4.0-72 in
the guest (and host).

The missing "erms" on my 7713 seems to stem from a buggy BIOS, I will
recheck once I have an update from the vendor. The 7763 are on a
different platform and the ones we have in production. Those work just
fine and don't have any "scary" ECC errors ;-)

I am more than happy to do further testing with/for you.

-- 
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-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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+0x6e/0x93
 early_identify_cpu.constprop.0+0x112/0x144
 early_cpu_init+0x77/0x7c
 setup_arch+0xc9/0x8cc
 ? lockdown_lsm_init+0x21/0x25
 start_kernel+0x67/0x4a2
 ? copy_bootdata+0x1d/0x5d
 x86_64_start_reservations+0x24/0x26
 x86_64_start_kernel+0x8b/0x8f
 secondary_startup_64_no_verify+0xc2/0xcb

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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 the EPYC model.
Anyway the MSR error got me on the path that this is related to the missing 
IBRS flag, which after trying it with the patch, the MSR error was gone. So 
yes, this is related to LP#1915063 and as you already concluded with this 
backport, it would be resolved as well.

I don't think only the kernel commit will resolve this. I have seen a
similar/same MSR error without IBRS on a Fedora 33 guest which has
kernel 5.11.x.

So I if I have time, I test the mainline ppa kernel to confirm this.

For reference, this is the MSR error on the focal guest with 5.4.0-70 on
both host and guest:

unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0006) 
at rIP: 0x89a73594 (native_write_msr+0x4/0x30)
Call Trace:
 ? __switch_to_xtra+0x1ae/0x5e0
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 __switch_to+0x3b0/0x470
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 __schedule+0x2e3/0x740
 preempt_schedule_common+0x18/0x30
 _cond_resched+0x22/0x30
 stop_one_cpu+0x69/0xa0
 ? sched_ttwu_pending+0xe0/0xe0
 sched_exec+0x92/0xc0
 __do_execve_file.isra.0+0x1fc/0x840
 ? strncpy_from_user+0x4c/0x150
 __x64_sys_execve+0x39/0x50
 do_syscall_64+0x57/0x190
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f31e09ef2fb
Code: 41 89 01 eb da 66 2e 0f 1f 84 00 00 00 00 00 f7 d8 64 41 89 01 eb d6 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa b8 3b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d 65 4b 10 00 f7 d8 64 89 01 48
RSP: 002b:7fff1cfd3b48 EFLAGS: 0246 ORIG_RAX: 003b
RAX: ffda RBX: 55713f000370 RCX: 7f31e09ef2fb
RDX: 55713f0d5010 RSI: 55713f069690 RDI: 55713f006070
RBP: 7fff1cfd3d50 R08: 55713f057cd0 R09: 
R10: 55713efe9980 R11: 0246 R12: 
R13: 55713f0d0f50 R14:  R15: 55713f069690

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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~focalppa1

# virsh domcapabilities | grep EPYC
  EPYC-Milan
  EPYC-Rome
  EPYC-Milan
  EPYC-IBPB
  EPYC

which is expected given that we are missing:

  
  
  
  

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-Milan(alias configured by machine type)  
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-Rome-v2  AMD EPYC-Rome Processor 
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor


Running a focal instance (5.4.0-70-generic) on the "before" system with the 
EPYC-Rome type on a Milan CPU results in the following error. This is due to 
the missing IBRS flag, which is one of the reasons, I'd like to see this 
backported ;-)

unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0006) 
at rIP: 0x89a73594 (native_write_msr+0x4/0x30)
Call Trace:
 ? __switch_to_xtra+0x1ae/0x5e0
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 __switch_to+0x3b0/0x470
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 __schedule+0x2e3/0x740
 preempt_schedule_common+0x18/0x30
 _cond_resched+0x22/0x30
 stop_one_cpu+0x69/0xa0
 ? sched_ttwu_pending+0xe0/0xe0
 sched_exec+0x92/0xc0
 __do_execve_file.isra.0+0x1fc/0x840
 ? strncpy_from_user+0x4c/0x150
 __x64_sys_execve+0x39/0x50
 do_syscall_64+0x57/0x190
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f31e09ef2fb
Code: 41 89 01 eb da 66 2e 0f 1f 84 00 00 00 00 00 f7 d8 64 41 89 01 eb d6 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa b8 3b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d 65 4b 10 00 f7 d8 64 89 01 48
RSP: 002b:7fff1cfd3b48 EFLAGS: 0246 ORIG_RAX: 003b
RAX: ffda RBX: 55713f000370 RCX: 7f31e09ef2fb
RDX: 55713f0d5010 RSI: 55713f069690 RDI: 55713f006070
RBP: 7fff1cfd3d50 R08: 55713f057cd0 R09: 
R10: 55713efe9980 R11: 0246 R12: 
R13: 55713f0d0f50 R14:  R15: 55713f069690

Live migration of such an instance from a "before" system to an "after"
system went without problems.

Starting the same instance (now with the ibrs flag added), resolves the
the above MSR error and pretty much works just like my own build. So
live migrating back and forth showed no problems.


Trying to start an instance with EPYC-Milan on my 7713 system results in the 
following libvirt error:

error: the CPU is incompatible with host CPU: Host CPU does not provide
required features: erms, fsrm

Now the fsrm is expected, but the erms flag is only missing on the host
with the 7713, but present on all my 7763 systems. I haven't got a
second 7713 to confirm, but I can say it's present on multiple 7763.
Not sure if this is due to it being an early sample or because it is not
present on all SKUs.

7713:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush 
mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc 
rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor 
ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand 
lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch 
osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc 
mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate sme ssbd mba sev ibrs ibpb 
stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid cqm rdt_a rdseed adx smap 
clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc 
cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd arat npt lbrv 
svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter 
pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq rdpid 
overflow_recov succor smca

7763:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush 
mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc 
rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor 
ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand 
lahf_lm cmp_legacy svm extapic 

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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-backports repo would be great.

Mid-term I think it would still makes sense to get it into focal proper.
Icelake is there and it hasn't even launched, yet. AMD is the more
attractive platform these days, so having good support is more than just
nice to have. But I defer this judgement to the server-team and you.

-- 
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-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

[Markus Schade]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] [NEW] Add EPYC-Milan model

[Markus Schade]

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 and fsrm (which is already in qemu)

fsrm
https://gitlab.com/libvirt/libvirt/-/commit/8c5c660b99101544d8cfcb8edbe48688c04bee25
svme-addr-chk (later patch fixed spelling)
https://gitlab.com/libvirt/libvirt/-/commit/5ac6ab2fde63881d3c5cc7372a0d0e59618feb55
ibrs
https://gitlab.com/libvirt/libvirt/-/commit/5c17a7ba41670f3182186c06e621995b5d03fc95
EPYC-Milan model
https://gitlab.com/libvirt/libvirt/-/commit/f321a4822e9fa6542e48a78611989ecd9acaa83a
https://gitlab.com/libvirt/libvirt/-/commit/d3de79dbfc20dc4dfc19154b16079861c542b71e
spelling fix for svme-addr-chk
https://gitlab.com/libvirt/libvirt/-/commit/b5abf9a192248b1005f63a7102d2627375d70fe5

Please consider adding/backporting these.

Of course there are a number of kernel commits, some/most listed in the
qemu commit, that would need to be backported to enable all features.
But even without them, this already works for the most part (tested on
focal kernel 5.4.0-70).

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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 feature bits in EPYC-Rome model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] [NEW] Add missing cpu feature bits in EPYC-Rome model

[Markus Schade]

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 on the IBRS and AMD SSBD definitions that were added
as part of the EPYC-Milan patch:

https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg03370.html


diff --git a/target/i386/cpu.h b/target/i386/cpu.h
index 8d599bb5b8..888c3a59e2 100644
--- a/target/i386/cpu.h
+++ b/target/i386/cpu.h
@@ -816,8 +816,12 @@ typedef uint64_t FeatureWordArray[FEATURE_WORDS];
 #define CPUID_8000_0008_EBX_WBNOINVD(1U << 9)
 /* Indirect Branch Prediction Barrier */
 #define CPUID_8000_0008_EBX_IBPB(1U << 12)
+/* Indirect Branch Restricted Speculation */
+#define CPUID_8000_0008_EBX_IBRS(1U << 14)
 /* Single Thread Indirect Branch Predictors */
 #define CPUID_8000_0008_EBX_STIBP   (1U << 15)
+/* Speculative Store Bypass Disable */
+#define CPUID_8000_0008_EBX_AMD_SSBD(1U << 24)

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 not sure I would still call it a regression and it is certainly an
annoying, but it can be workarounded.

-- 
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/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations

[Markus Schade]

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.0-54-generic and hope we can provide a simple reproducer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578

Title:
  raid10: Block discard is very slow, causing severe delays for mkfs and
  fstrim operations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905599] Re: sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and Groovy

[Markus Schade]

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
  Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904823] [NEW] device-mapper: btree spine: node_check failed: csum

[Markus Schade]

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 drivers/md/persistent-data/dm-btree-spine.c:34!
invalid opcode:  [#1] SMP PTI
CPU: 42 PID: 2175930 Comm: kworker/42:1 Not tainted 5.4.0-51-generic #56-Ubuntu
Hardware name: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-1G), 
BIOS 3B17.Q302 08/12/2020
Workqueue: dm_bufio_cache work_fn [dm_bufio]
RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data]
Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 
e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 
00 00 00 00 00 66 90 0f 1f 44 00 00 55 48
RSP: 0018:98b9f539fd08 EFLAGS: 00010286
RAX: ffac RBX: 8bce38b4f000 RCX: 
RDX:  RSI: 8bc580e978c8 RDI: 8bc580e978c8
RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001
R10: 0095 R11: 6b300095 R12: 8bc451e18d20
R13: 1000 R14: c0416550 R15: 8bc451e18d20
FS:  () GS:8bc580e8() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
PKRU: 5554
Call Trace:
 ? le64_inc+0x20/0x20 [dm_persistent_data] 
 dm_block_manager_write_callback+0x42/0x50 [dm_persistent_data]
 submit_io+0x1ad/0x230 [dm_bufio]
 __flush_write_list+0x81/0xc0 [dm_bufio]
 work_fn+0x1c8/0x1f0 [dm_bufio]
 process_one_work+0x1eb/0x3b0
 worker_thread+0x4d/0x400
 kthread+0x104/0x140
 ? process_one_work+0x3b0/0x3b0
 ? kthread_park+0x90/0x90
 ret_from_fork+0x35/0x40
Modules linked in: dm_snapshot vhost_net vhost tap ip6table_raw tcp_diag 
udp_diag inet_diag overlay veth dummy bridge nf_tables netconsole sch_ingress 
vxlan ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout openvswitch nsh 
nf_conncount ip6table_filter ip6_tables xt_CT iptable_raw iptable_mangle 
intel_rapl_msr intel_rapl_common xt_set xt_tcpudp isst_if_common skx_edac 
xt_state nfit xt_conntrack x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_pclmul ghash_clmulni_intel iptable_filter aesni_intel ipmi_ssif 
bpfilter kvm_intel crypto_simd cryptd glue_helper rapl kvm intel_cstate 
drm_vram_helper ttm drm_kms_helper i2c_algo_bit fb_sys_fops syscopyarea 
sysfillrect sysimgblt ioatdma ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter acpi_pad mac_hid ip_set_hash_net ip_set nfnetlink sch_fq_codel 
nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp 
nf_conntrack_pptp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tcp_htcp 
8021q garp mrp stp llc bonding drm
 ip_tables x_tables autofs4 btrfs zstd_compress raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c raid10 raid1 
crc32_pclmul ixgbe xfrm_algo dca mdio nvme nvme_core ahci i2c_i801 lpc_ich 
libahci wmi
---[ end trace 7e896cfa4fcf1285 ]---
RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data]
Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 
e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 
00 00 00 00 00 66 90 0f 1f 44 00 00 55 48
RSP: 0018:98b9f539fd08 EFLAGS: 00010286
RAX: ffac RBX: 8bce38b4f000 RCX: 
RDX:  RSI: 8bc580e978c8 RDI: 8bc580e978c8
RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001
R10: 0095 R11: 6b300095 R12: 8bc451e18d20
R13: 1000 R14: c0416550 R15: 8bc451e18d20
FS:  () GS:8bc580e8() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
PKRU: 5554
[ cut here ]

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904823

Title:
  device-mapper: btree spine: node_check failed: csum

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 using EPYC or EPYC-IBPB CPU models 
started with libvirt versions prior to this one because the instance on the 
target host has these extra flags

-- 
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/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885527] Re: cloud-init regenerating ssh-keys

[Markus Schade]

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 about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1885527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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.launchpad.net/bugs/1887490

Title:
  [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885527] Re: cloud-init regenerating ssh-keys

[Markus Schade]

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://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885527] Re: cloud-init regenerating ssh-keys

[Markus Schade]

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 already configured
instance from being reconfigured in case the metadata server does not
respond properly.

-- 
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://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885527] Re: cloud-init regenerating ssh-keys

[Markus Schade]

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/1885527

Title:
  cloud-init regenerating ssh-keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 EPYC-Rome model via libvirt. Also the new flags
like npt/nrip-save are present when svm is enabled.

-- 
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/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor 
lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw 
topoext perfctr_core ssbd ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 
rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero 
xsaveerptr wbnoinvd arat npt nrip_save umip rdpid

Patches for libvirt are submitted upstream
https://www.redhat.com/archives/libvir-list/2020-October/msg8.html

A version fitting for the focal version is attached

** Patch added: "Add-EPYC-ROME-x86-CPU-model.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887490/+attachment/5416509/+files/Add-EPYC-ROME-x86-CPU-model.patch

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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-Rome CPU model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

[Markus Schade]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896751

Title:
  Guest hang on reboot after migration from bionic to focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1896751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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-mc-no-bit-in-IA32_ARCH_CAPABILITIES-MSR.patch
Request-test-files-update-when-adding-x86-features.patch
Add-missing-x86-features-in-0x7-CPUID-leaf.patch
Add-missing-x86-features-in-0x8008-CPUID-leaf.patch
Add-missing-AMD-SVM-features.patch

Plus the patch adding the EPYC-Rome model. I'll try to get it upstream,
but it will take some time. From my side, it's totally fine from my side
to go ahead with the update without it.

My patch queue for qemu also has 2 more patches, reported as LP#1896751
and LP#1896751

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896751] [NEW] Guest hang on reboot after migration from bionic to focal

[Markus Schade]

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/5073b5d3ea303d37f4a8e2ea451d7a2eb1817448

https://bugzilla.redhat.com/show_bug.cgi?id=1809380

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896751

Title:
  Guest hang on reboot after migration from bionic to focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1896751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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

https://github.com/libvirt/libvirt/commit/3944f6855b9d4df73754bb6e5c8023d77399879b

that you have partially applied.

I would howver not add the CooperLake patches because focal qemu does
not have the required patches (yet).

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

Is there anything I can do, regarding the backport of 52297436199d into
focal kernel?

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869815] Re: package nsd (not installed) failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1

[Markus Schade]

** 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
  package post-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1869815/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880795] Re: package nsd 4.1.26-1build1 failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1

[Markus Schade]

** 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 post-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1880795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781705] Re: Memory leaks fixed in 4.1.21

[Markus Schade]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1781705/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880795] Re: package nsd 4.1.26-1build1 failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1

[Markus Schade]

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 defaults.

-- 
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 post-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1880795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869815] Re: package nsd (not installed) failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1

[Markus Schade]

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 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
  package post-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1869815/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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 enable support for 
all CPU flags currently supported by focal qemu and for the additional AMD 
flags from the mentioned patched.
I currently run a private build in production with the following patches added:

https://github.com/libvirt/libvirt/commits/master/src/cpu_map:

- cpu_map: Distinguish Cascadelake-Server from Skylake-Server (unrelated, but 
recommended)
- cpu_map: Add pschange-mc-no bit in IA32_ARCH_CAPABILITIES MSR
- cpu_map: Request test files update when adding x86 features 
- cpu_map: Add missing x86 features in 0x7 CPUID leaf
- cpu_map: Add missing x86 features in 0x8008 CPUID leaf

Plus the attached patch which defines an EPYC-Rome type (without any
tests), so not quite ready for upstream

** Attachment added: "Add-EPYC-ROME-x86-CPU-model"
   
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887490/+attachment/5398119/+files/Add-EPYC-ROME-x86-CPU-model

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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.

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887490] [NEW] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

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/143c30d4d346831a09e59e9af45afdca0331e819

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  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
- #diff-c8f550847b733f46aaf5cedfce0b6f90
  
  https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819
- #diff-c8f550847b733f46aaf5cedfce0b6f90

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834875] Re: cloud-init growpart race with udev

[Markus Schade]

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.

Removing cloud-initramfs-growroot provides a working focal image.


Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [2.261862] Btrfs loaded, 
crc32c=crc32c-intel
Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.34
[/usr/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 32500/188048 files, 340923/751616 blocks
done.
[2.397086] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
done.
Begin: Running /scripts/local-bottom ... [2.723549]  sda: sda1 sda14 sda15
GROWROOT: CHANGED: partition=1 start=129024 old: size=6012928 end=6141952 new: 
size=39872479 end=40001503
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev 
failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6) multi-call binary.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875

Title:
  cloud-init growpart race with udev

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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://bugs.launchpad.net/bugs/1777398

Title:
  dm thin block allocation failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

Patch has been backported to all stable kernel releases, e.g. 4.19:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=1fac9f574cd2536abcdd645ee23d35c0e819d7ec

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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=4feaef830de7ffdd8352e1fe14ad3bf13c9688f8
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=e9f8ca0ae7b7bc9a032b429929431c626a69dd5e

Since we had also peformance regressions with bionics 4.15 due to
https://lore.kernel.org/lkml/20180321175453.gg4...@bombadil.infradead.org/T/
we have moved to the eoan hwe kernel.

We have been running that with this patch so far without triggering the
condition again.

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-2), 
BIOS 3A13.Q402 11/16/2018
Workqueue: dm-thin do_worker [dm_thin_pool]
RIP: 0010:sm_disk_new_block+0x92/0xa0 [dm_persistent_data]
Code: 55 e4 48 83 c0 01 48 89 83 20 22 00 00 49 8b 34 24 e8 82 f7 ff ff 85 c0 
75 c4 83 7d e4 01 75 0a 48 83 83 28 22 00 00 01 eb b4 <0f> 0b e8 97 b4 dd c7 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89
RSP: 0018:b647bb06fca8 EFLAGS: 00010297
RAX:  RBX: 95dc1d9a4000 RCX: 
RDX:  RSI:  RDI: 95dc347a9a00
RBP: b647bb06fcc8 R08:  R09: b647bb06fa38
R10: f6c3d4ca9080 R11: 0001 R12: b647bb06fd70
R13: b647bb06fd70 R14: 9593a3d6f000 R15: 957adcb455b0
FS:  () GS:9593efd4() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 00c4202d2318 CR3: 0079b7c0e002 CR4: 007626e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
PKRU: 5554
Call Trace:
 dm_pool_alloc_data_block+0x3c/0x60 [dm_thin_pool]
 alloc_data_block.isra.61+0x6c/0x1a0 [dm_thin_pool]
 process_cell+0x2cd/0x4f0 [dm_thin_pool]
 ? _cond_resched+0x19/0x30
 ? u32_swap+0x10/0x10
 ? sort+0x13b/0x220
 ? u32_swap+0x10/0x10
 do_worker+0x27c/0x900 [dm_thin_pool]
 ? __switch_to_asm+0x40/0x70
 process_one_work+0x20f/0x410
 worker_thread+0x34/0x400
 kthread+0x120/0x140
 ? process_one_work+0x410/0x410
 ? __kthread_parkme+0x70/0x70
 ret_from_fork+0x35/0x40
Modules linked in: dm_snapshot xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 veth 
dummy bridge ip6table_filter ip6_tables iptable_mangle xt_CT iptable_raw 
xt_tcpudp xt_conntrack iptable_filter ip_tables x_tables bpfilter vhost_net 
vhost tap dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio intel_rapl 
skx_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ioatdma ipmi_ssif 
intel_rapl_perf lpc_ich dca acpi_power_meter acpi_pad mac_hid ipmi_si 
ipmi_devintf ipmi_msghandler nf_nat_ftp nf_conntrack_ftp nf_nat_sip 
nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat nf_conntrack_proto_gre 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tcp_htcp 8021q garp mrp stp llc 
bonding autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear 
raid10 raid1 i2c_algo_bit ttm
 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm i40e nvme 
ahci nvme_core libahci wmi
---[ end trace 678c665ac774d0d4 ]---
RIP: 0010:sm_disk_new_block+0x92/0xa0 [dm_persistent_data]
Code: 55 e4 48 83 c0 01 48 89 83 20 22 00 00 49 8b 34 24 e8 82 f7 ff ff 85 c0 
75 c4 83 7d e4 01 75 0a 48 83 83 28 22 00 00 01 eb b4 <0f> 0b e8 97 b4 dd c7 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89
RSP: 0018:b647bb06fca8 EFLAGS: 00010297
RAX:  RBX: 95dc1d9a4000 RCX: 
RDX:  RSI:  RDI: 95dc347a9a00
RBP: b647bb06fcc8 R08:  R09: b647bb06fa38
R10: f6c3d4ca9080 R11: 0001 R12: b647bb06fd70
R13: b647bb06fd70 R14: 9593a3d6f000 R15: 957adcb455b0
FS:  () GS:9593efd4() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 00c4202d2318 CR3: 0079b7c0e002 CR4: 007626e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
PKRU: 5554

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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)
   Status: Expired => 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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 iptable_mangle 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter 
ip_tables x_tables vhost_net vhost tap dm_thin_pool dm_persistent_data 
intel_rapl dm_bio_prison skx_edac dm_bufio x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc ipmi_ssif aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich shpchp ioatdma dca 
acpi_power_meter acpi_pad mac_hid ipmi_si ipmi_devintf ipmi_msghandler 
nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp 
nf_conntrack_pptp nf_nat_proto_gre
kernel: [1120717.623364]  nf_nat nf_conntrack_proto_gre nf_conntrack tcp_htcp 
8021q garp mrp stp llc bonding autofs4 btrfs zstd_compress raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid0 multipath linear raid1 raid10 i2c_algo_bit ttm drm_kms_helper 
i40e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci nvme pps_core drm 
nvme_core libahci wmi
kernel: [1120717.623739] CPU: 40 PID: 1269520 Comm: kworker/u128:2 Not tainted 
4.15.0-47-generic #50~16.04.1-Ubuntu
kernel: [1120717.623881] Hardware name: Quanta Cloud Technology Inc. QuantaGrid 
D52B-1U/S5B-MB (LBG-2), BIOS 3A13.Q402 11/16/2018
kernel: [1120717.624035] Workqueue: dm-thin do_worker [dm_thin_pool]
kernel: [1120717.624142] RIP: 0010:sm_disk_new_block+0xa1/0xb0 
[dm_persistent_data]
kernel: [1120717.624245] RSP: 0018:a467364d7c68 EFLAGS: 00010297
kernel: [1120717.624347] RAX:  RBX: 89285e3f8000 RCX: 

kernel: [1120717.624481] RDX: 890b51e68000 RSI: 0282 RDI: 
8970be770600
kernel: [1120717.624614] RBP: a467364d7c90 R08:  R09: 
a467364d79f0
kernel: [1120717.624747] R10: a467364d78f8 R11: a467364d7b48 R12: 

kernel: [1120717.624880] R13: a467364d7d40 R14: a467364d7d40 R15: 
8921d2ac9460
kernel: [1120717.625015] FS:  () GS:89287040() 
knlGS:
kernel: [1120717.625149] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [1120717.625249] CR2: 7f864a646000 CR3: 00806a40a002 CR4: 
007626e0
kernel: [1120717.625384] DR0:  DR1:  DR2: 

kernel: [1120717.625517] DR3:  DR6: fffe0ff0 DR7: 
0400
kernel: [1120717.625649] PKRU: 5554
kernel: [1120717.625739] Call Trace:
kernel: [1120717.625839]  dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool]
kernel: [1120717.625948]  alloc_data_block.isra.56+0x6f/0x180 [dm_thin_pool]
kernel: [1120717.626053]  process_cell+0x2cf/0x4d0 [dm_thin_pool]
kernel: [1120717.626157]  ? sort+0x165/0x250
kernel: [1120717.626250]  do_worker+0x25c/0x8b0 [dm_thin_pool]
kernel: [1120717.626351]  process_one_work+0x14d/0x410
kernel: [1120717.626451]  ? process_discard_cell_passdown+0x1e0/0x1e0 
[dm_thin_pool]
kernel: [1120717.626557]  ? process_one_work+0x14d/0x410
kernel: [1120717.626655]  worker_thread+0x4b/0x460
kernel: [1120717.626755]  kthread+0x105/0x140
kernel: [1120717.626849]  ? process_one_work+0x410/0x410
kernel: [1120717.626947]  ? kthread_destroy_worker+0x50/0x50
kernel: [1120717.627050]  ret_from_fork+0x35/0x40
kernel: [1120717.627142] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 
ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb 
aa <0f> 0b e8 a8 34 98 f0 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 
kernel: [1120717.627428] RIP: sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] 
RSP: a467364d7c68

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813266] [NEW] udhcpd: not dying on SIGTERM

[Markus Schade]

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 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813266

Title:
  udhcpd: not dying on SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1813266/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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 
/build/linux-hwe-okqLve/linux-hwe-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178!
kernel: [8860597.921579] invalid opcode:  [#1] SMP PTI
kernel: [8860597.921640] Modules linked in: cpuid cmac arc4 md4 nls_utf8 cifs 
ccm fscache dm_snapshot dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
iptable_mangle xt_CT iptable_raw veth dummy nf_conntrack_ipv4 nf_defrag_ipv4 
bridge iptable_filter ip_tables xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 
xt_conntrack ip6table_filter ip6_tables x_tables vhost_net vhost tap intel_rapl 
skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp dm_thin_pool kvm_intel 
dm_persistent_data dm_bio_prison kvm dm_bufio irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd 
ipmi_ssif glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich shpchp 
ioatdma dca acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_devintf
kernel: [8860597.921973]  ipmi_msghandler nf_nat_ftp nf_conntrack_ftp 
nf_nat_sip nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre 
nf_nat nf_conntrack_proto_gre nf_conntrack tcp_htcp 8021q garp mrp stp llc 
bonding autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
raid10 i40e i2c_algo_bit ttm ptp drm_kms_helper pps_core syscopyarea nvme 
sysfillrect sysimgblt fb_sys_fops nvme_core drm ahci libahci wmi
kernel: [8860597.922282] CPU: 38 PID: 1917945 Comm: kworker/u128:2 Not tainted 
4.15.0-31-generic #33~16.04.1-Ubuntu
kernel: [8860597.922413] Hardware name: Quanta Cloud Technology Inc. QuantaGrid 
D52B-1U/S5B-MB (LBG-4), BIOS 3A10.10 02/12/2018
kernel: [8860597.922554] Workqueue: dm-thin do_worker [dm_thin_pool]
kernel: [8860597.922650] RIP: 0010:sm_disk_new_block+0xa1/0xb0 
[dm_persistent_data]
kernel: [8860597.922747] RSP: 0018:bfa19dc7fc68 EFLAGS: 00010297
kernel: [8860597.922839] RAX:  RBX: 9e6c63f0c000 RCX: 

kernel: [8860597.922962] RDX: 9e6c3768d940 RSI: 0282 RDI: 
9eb4dc4f3400
kernel: [8860597.923086] RBP: bfa19dc7fc90 R08:  R09: 
bfa19dc7f9f0
kernel: [8860597.923211] R10: bfa19dc7f8f8 R11: bfa19dc7fb48 R12: 

kernel: [8860597.923335] R13: bfa19dc7fd40 R14: bfa19dc7fd40 R15: 
9e47cb3460e0
kernel: [8860597.923460] FS:  () GS:9e6cb038() 
knlGS:
kernel: [8860597.923587] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [8860597.923678] CR2: 009cfd20 CR3: 008d2400a003 CR4: 
007626e0
kernel: [8860597.923802] DR0:  DR1:  DR2: 

kernel: [8860597.923926] DR3:  DR6: fffe0ff0 DR7: 
0400
kernel: [8860597.924049] PKRU: 5554
kernel: [8860597.924130] Call Trace:
kernel: [8860597.924217]  dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool]
kernel: [8860597.924310]  alloc_data_block.isra.53+0x6f/0x180 [dm_thin_pool]
kernel: [8860597.924404]  process_cell+0x2cf/0x4d0 [dm_thin_pool]
kernel: [8860597.924498]  ? mempool_alloc_slab+0x15/0x20
kernel: [8860597.924585]  ? mempool_alloc+0x73/0x180
kernel: [8860597.924671]  ? process_prepared+0x8d/0xc0 [dm_thin_pool]
kernel: [8860597.924762]  do_worker+0x25c/0x8b0 [dm_thin_pool]
kernel: [8860597.924855]  process_one_work+0x14d/0x410
kernel: [8860597.924942]  ? process_discard_cell_passdown+0x1e0/0x1e0 
[dm_thin_pool]
kernel: [8860597.925037]  ? process_one_work+0x14d/0x410
kernel: [8860597.925124]  worker_thread+0x4b/0x460
kernel: [8860597.925210]  kthread+0x105/0x140
kernel: [8860597.925294]  ? process_one_work+0x410/0x410
kernel: [8860597.925381]  ? kthread_associate_blkcg+0xa0/0xa0
kernel: [8860597.925473]  ret_from_fork+0x35/0x40
kernel: [8860597.925558] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 
ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb 
aa <0f> 0b e8 08 0c bf d0 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55.
kernel: [8860597.925779] RIP: sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] 
RSP: bfa19dc7fc68
kernel: [8860597.925961] ---[ end trace dfde9f8a30119f50 ]---

** Changed in: linux (Ubuntu)
   Status: Expired => New

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1788563] Re: L1TF mitigation not effective in some CPU and RAM combinations

[Markus Schade]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778475] Re: i40e: restore workaround for removing default MAC filter

[Markus Schade]

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://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788563] Re: L1TF mitigation not effective in some CPU and RAM combinations

[Markus Schade]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1789834] Re: off-by-one bug in L1TF mitigation

[Markus Schade]

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 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 go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789834/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1789834] Re: off-by-one bug in L1TF mitigation

[Markus Schade]

** 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 go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789834/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1789834] [NEW] off-by-one bug in L1TF mitigation

[Markus Schade]

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
happens with the latest trusty kernel (3.13.0-157-generic)

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=b0a182f875689647b014bc01d36b340217792852

The following patch increases the memory limit for the mitigation on
these systems in general:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  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 
happens
- with the latest trusty kernel (3.13.0-157-generic)
+ Originally this was reported in OpenSUSE, but I can confirm this is also
+ happens with the latest trusty kernel (3.13.0-157-generic)
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=b0a182f875689647b014bc01d36b340217792852
  
  The following patch increases the memory limit for the mitigation on
  these systems in general:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789834/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787126] Re: Update microcode to 20180807 version

[Markus Schade]

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/1787126

Title:
   Update microcode to 20180807 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1787126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783385] Re: intel-microcode: update to 20180703 drop

[Markus Schade]

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://bugs.launchpad.net/bugs/1783385

Title:
  intel-microcode: update to 20180703 drop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1783385/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Markus Schade]

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/1778486

Title:
  x86/kvm: fix LAPIC timer drift when guest uses periodic mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778486/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787126] [NEW] Update microcode to 20180807 version

[Markus Schade]

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 should release an update shortly.

Please consider packaging this version to enable mitigations.

** Affects: intel-microcode (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: needs-debian-merge upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787126

Title:
   Update microcode to 20180807 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1787126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783385] Re: intel-microcode: update to 20180703 drop

[Markus Schade]

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/1783385

Title:
  intel-microcode: update to 20180703 drop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1783385/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Markus Schade]

** 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 periodic mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778486/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783385] Re: intel-microcode: update to 20180703 drop

[Markus Schade]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783385

Title:
  intel-microcode: update to 20180703 drop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1783385/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780399] Re: Update microcode to 20180703 version

[Markus Schade]

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 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1780399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780399] [NEW] Update microcode to 20180703 version

[Markus Schade]

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.
Please sync with unstable and backport it to all still supported releases.

** Affects: intel-microcode (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: upgrade-software-version

-- 
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 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1780399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Markus Schade]

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 LAPIC timer drift when guest uses periodic mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778486/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778475] Re: i40e: restore workaround for removing default MAC filter

[Markus Schade]

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.0-041800rc2-generic #201806241430 SMP Sun Jun 24 14:33:07 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

# dmesg:
[Thu Jun 28 08:08:45 2018] i40e :3d:00.1: Error I40E_AQ_RC_EINVAL adding RX 
filters on PF, promiscuous mode forced on
[Thu Jun 28 08:08:45 2018] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX 
filters on PF, promiscuous mode forced on

# lspci -nn | grep -i eth
3d:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 
for 10GbE SFP+ [8086:37d3] (rev 08)
3d:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 
for 10GbE SFP+ [8086:37d3] (rev 08)

-- 
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://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778486] [NEW] x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Markus Schade]

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)
 Importance: Undecided
 Status: New

-- 
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 periodic mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778486/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778475] [NEW] i40e: restore workaround for removing default MAC filter

[Markus Schade]

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:

https://patchwork.ozlabs.org/patch/692499/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777398

Title:
  dm thin block allocation failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

** 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777398] Re: dm thin block allocation failure

[Markus Schade]

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.803986] invalid opcode:  [#1] SMP PTI
kernel: [450194.804101] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm 
fscache dm_snapshot dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_CT iptable_raw 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter veth 
dummy bridge iptable_mangle ip_tables x_tables vhost_net vhost tap intel_rapl 
skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp dm_thin_pool 
dm_persistent_data dm_bio_prison kvm_intel dm_bufio kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ipmi_ssif aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich 
shpchp ioatdma dca acpi_power_meter acpi_pad mac_hid ipmi_si ipmi_devintf 
ipmi_msghandler
kernel: [450194.804489]  nf_nat_ftp nf_conntrack_ftp nf_nat_sip 
nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_nat 
nf_conntrack_proto_gre nf_conntrack tcp_htcp 8021q garp mrp stp llc bonding 
autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 
i2c_algo_bit ttm i40e drm_kms_helper ptp syscopyarea pps_core sysfillrect nvme 
sysimgblt fb_sys_fops nvme_core drm ahci libahci wmi
kernel: [450194.804763] CPU: 4 PID: 1788072 Comm: kworker/u128:1 Not tainted 
4.15.0-23-generic #25~16.04.1-Ubuntu 
kernel: [450194.804898] Hardware name: Quanta Cloud Technology Inc. QuantaGrid 
D52B-1U/S5B-MB (LBG-4), BIOS 3A10.03 11/17/2017
kernel: [450194.805037] Workqueue: dm-thin do_worker [dm_thin_pool]
kernel: [450194.805132] RIP: 0010:sm_disk_new_block+0xa1/0xb0 
[dm_persistent_data]
kernel: [450194.805225] RSP: 0018:bd5c00d3fc68 EFLAGS: 00010297
kernel: [450194.805315] RAX:  RBX: 98ff57aa RCX: 

kernel: [450194.805437] RDX: 9948019ebc00 RSI: 0282 RDI: 
98ff99bf4a00
kernel: [450194.805561] RBP: bd5c00d3fc90 R08:  R09: 
bd5c00d3f9f0
kernel: [450194.805685] R10: bd5c00d3f8f8 R11: bd5c00d3fb48 R12: 

kernel: [450194.805808] R13: bd5c00d3fd40 R14: bd5c00d3fd40 R15: 
98dc797fcce0
kernel: [450194.805934] FS:  () GS:98ffaff0() 
knlGS: 
kernel: [450194.806061] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [450194.806152] CR2: 00c420224000 CR3: 00544820a003 CR4: 
007626e0
kernel: [450194.806275] DR0:  DR1:  DR2: 

kernel: [450194.806399] DR3:  DR6: fffe0ff0 DR7: 
0400
kernel: [450194.806522] PKRU: 5554
kernel: [450194.806604] Call Trace:
kernel: [450194.806690]  dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool]
kernel: [450194.806783]  alloc_data_block.isra.53+0x6f/0x180 [dm_thin_pool]
kernel: [450194.806876]  process_cell+0x2cf/0x4d0 [dm_thin_pool]
kernel: [450194.806966]  ? mempool_alloc_slab+0x15/0x20
kernel: [450194.807052]  ? mempool_alloc+0x73/0x180
kernel: [450194.807138]  do_worker+0x25c/0x8b0 [dm_thin_pool]
kernel: [450194.807227]  process_one_work+0x14d/0x410
kernel: [450194.807313]  ? process_discard_cell_passdown+0x1e0/0x1e0 
[dm_thin_pool]
kernel: [450194.807407]  ? process_one_work+0x14d/0x410
kernel: [450194.807493]  worker_thread+0x4b/0x460
kernel: [450194.807578]  kthread+0x105/0x140
kernel: [450194.807661]  ? process_one_work+0x410/0x410
kernel: [450194.807747]  ? kthread_associate_blkcg+0xa0/0xa0
kernel: [450194.807835]  ? do_syscall_64+0x73/0x130
kernel: [450194.807921]  ? SyS_exit+0x17/0x20
kernel: [450194.808007]  ret_from_fork+0x35/0x40
kernel: [450194.808091] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 
ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb 
aa <0f> 0b e8 08 cc 3c e3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55  
kernel: [450194.808310] RIP: sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] 
RSP: bd5c00d3fc68
kernel: [450194.808582] ---[ end trace 7980ced76a1091db ]---

** Description changed:

+ 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-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178!
  kernel: [146487.421435] invalid opcode:  [#1] SMP PTI
  kernel: [146487.421528] Modules linked in: dm_snapshot cmac arc4 md4 nls_utf8 
cifs ccm fscache 

[Bug 1777398] [NEW] dm thin block allocation failure

[Markus Schade]

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-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178!
kernel: [146487.421435] invalid opcode:  [#1] SMP PTI
kernel: [146487.421528] Modules linked in: dm_snapshot cmac arc4 md4 nls_utf8 
cifs ccm fscache dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter veth dummy bridge 
iptable_mangle xt_CT iptable_raw ip_tables x_tables vhost_net vhost tap 
ipmi_ssif dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio intel_rapl 
skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich ioatdma 
shpchp dca acpi_power_meter acpi_pad mac_hid ipmi_si ipmi_devintf 
ipmi_msghandler
kernel: [146487.421859]  nf_nat_ftp nf_conntrack_ftp nf_nat_sip 
nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_nat 
nf_conntrack_proto_gre nf_conntrack tcp_htcp 8021q garp mrp stp llc bonding 
autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 
i2c_algo_bit ttm i40e drm_kms_helper syscopyarea ptp sysfillrect pps_core 
sysimgblt fb_sys_fops nvme ahci drm nvme_core libahci wmi
kernel: [146487.422080] CPU: 13 PID: 2274450 Comm: kworker/u576:1 Not tainted 
4.15.0-22-generic #24~16.04.1-Ubuntu
kernel: [146487.422211] Hardware name: Quanta Cloud Technology Inc. QuantaGrid 
D52B-1U/S5B-MB (LBG-4), BIOS 3A10.03 11/17/2017
kernel: [146487.422349] Workqueue: dm-thin do_worker [dm_thin_pool]
kernel: [146487.422443] RIP: 0010:sm_disk_new_block+0xa1/0xb0 
[dm_persistent_data]
kernel: [146487.422536] RSP: 0018:9efc5e4d3c68 EFLAGS: 00010297
kernel: [146487.422626] RAX:  RBX: 88b122d34000 RCX: 

kernel: [146487.422749] RDX: 8868d8631e00 RSI: 0282 RDI: 
88b137691200
kernel: [146487.422872] RBP: 9efc5e4d3c90 R08:  R09: 
9efc5e4d39f0
kernel: [146487.422994] R10: 9efc5e4d38f8 R11: 9efc5e4d3b48 R12: 

kernel: [146487.423117] R13: 9efc5e4d3d40 R14: 9efc5e4d3d40 R15: 
882de1769fa0
kernel: [146487.423240] FS:  () GS:8868ee54() 
knlGS:
kernel: [146487.423366] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [146487.423457] CR2: 7f0f30b083c0 CR3: 002ab260a004 CR4: 
007626e0
kernel: [146487.423580] DR0:  DR1:  DR2: 

kernel: [146487.423703] DR3:  DR6: fffe0ff0 DR7: 
0400
kernel: [146487.423826] PKRU: 5554
kernel: [146487.423906] Call Trace:
kernel: [146487.423989]  dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool]
kernel: [146487.424082]  alloc_data_block.isra.53+0x6f/0x180 [dm_thin_pool]
kernel: [146487.424175]  process_cell+0x2cf/0x4d0 [dm_thin_pool]
kernel: [146487.424267]  ? mempool_alloc_slab+0x15/0x20
kernel: [146487.424354]  ? mempool_alloc+0x73/0x180
kernel: [146487.424440]  ? process_prepared+0x8d/0xc0 [dm_thin_pool]
kernel: [146487.424531]  do_worker+0x25c/0x8b0 [dm_thin_pool]
kernel: [146487.424621]  process_one_work+0x14d/0x410
kernel: [146487.424708]  ? process_discard_cell_passdown+0x1e0/0x1e0 
[dm_thin_pool]
kernel: [146487.424802]  ? process_one_work+0x14d/0x410
kernel: [146487.424888]  worker_thread+0x4b/0x460
kernel: [146487.424973]  kthread+0x105/0x140
kernel: [146487.425055]  ? process_one_work+0x410/0x410
kernel: [146487.425142]  ? kthread_associate_blkcg+0xa0/0xa0
kernel: [146487.425230]  ? do_syscall_64+0x73/0x130
kernel: [146487.425315]  ? SyS_exit_group+0x14/0x20
kernel: [146487.425401]  ret_from_fork+0x35/0x40
kernel: [146487.425485] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 
ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb 
aa <0f> 0b e8 e8 1b cf d2 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55
kernel: [146487.425703] RIP: sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] 
RSP: 9efc5e4d3c68
kernel: [146487.425869] ---[ end trace 76985d9f3818cc3d ]---

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 bug go to:

[Bug 1744244] Re: linux: 4.4.0-112.135 -proposed tracker

[Markus Schade]

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 this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1744244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

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 notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

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   carrier unmanaged 
  2 eth0 ether  carrier configuring
  3 eth1 ether  carrier configuring
  4 bond0ether  routableconfigured
  5 bond0.200ether  routableconfigured

# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 9000 qdisc mq master bond0 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 9000 qdisc mq master bond0 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
4: bond0:  mtu 9000 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
5: bond0.200@bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff

interfaces(.d) and netplan are empty and unused/disabled

/etc/systemd/network:

# cat eth1.network 
[Match]
Name=eth1

[Network]
Bond=bond0

# cat eth0.network 
[Match]
Name=eth0

[Network]
Bond=bond0

# cat bond0.netdev 
[NetDev]
Name=bond0
Kind=bond

[Bond]
Mode=802.3ad
MIIMonitorSec=0.1s
LACPTransmitRate=fast
UpDelaySec=0.2s
DownDelaySec=0.2s

# cat bond0.network 
[Match]
Name=bond0

[Address]
Address=192.168.1.100/24

[Route]
Gateway=192.168.1.1

[Network]
VLAN=bond0.200

[Link]
MTUBytes=9000

# cat bond0.200.netdev 
[NetDev]
Name=bond0.200
Kind=vlan

[VLAN]
Id=200

# cat bond0.200.network 
[Match]
Name=bond0.200

[Address]
Address=10.10.0.100/16

[Route]
Gateway=10.10.0.1

[Link]
MTUBytes=9000

After upgrade:

# networkctl 
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 eth0 ether  carrier configuring
  3 eth1 ether  carrier configuring
  4 bond0ether  routableconfigured
  5 bond0.200ether  routableconfigured

However, the link of eth0, eth1 and the bond and vlan interface changes
to NOARP

# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
4: bond0:  mtu 9000 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
5: bond0.200@bond0:  mtu 1500 qdisc 
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff


** Bug watch added: github.com/systemd/systemd/issues #6184
   https://github.com/systemd/systemd/issues/6184

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727301] [NEW] 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

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 Link section of a .network file does not
work.

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 Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: regression-updates

** Description changed:

+ this breaks existing configurations with bonding on upgrading from
+ 229-4ubuntu19 to 229-4ubuntu20 on xenial
  
- 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.
+ 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 file does not
  work.
  
  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 Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1709135] Re: add bond primary parameter

[Markus Schade]

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 Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
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.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1709135] Re: add bond primary parameter

[Markus Schade]

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.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1709135] Re: add bond primary parameter

[Markus Schade]

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 file does not
work.

-- 
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.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1411350] Re: routing table does not show dynamic routes

[Markus Schade]

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.launchpad.net/bugs/1411350

Title:
  routing table does not show dynamic routes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Markus Schade]

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 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Markus Schade]

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 task_numa_migrate - handle_mm_fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Markus Schade]

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 there is any
difference.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Markus Schade]

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 iptable_nat nf_nat_ipv4 xt_NFQUEUE xt_CLASSIFY 
ip6table_mangle sch_sfq sch_htb veth dccp_diag dccp tcp_diag udp_diag inet_diag 
unix_diag af_packet_diag netlink_diag ebtable_filter ebtables nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables iptable_mangle xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter xt_CT iptable_raw 
ip_tables x_tables dummy bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd 
grace sunrpc fscache ipmi_ssif ipmi_devintf x86_pkg_temp_thermal 
intel_powerclamp coretemp dcdbas kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
joydev input_leds sb_edac edac_core cdc_ether nf_nat_ftp usbnet mii 
nf_conntrack_ftp nf_nat_pptp lpc_ich nf_conntrack_pptp nf_nat_proto_gre 
nf_nat_sip nf_nat nf_conntrack_sip ioa
 tdma ipmi_si shpchp ipmi_msghandler 8250_fintek nf_conntrack_proto_gre wmi 
acpi_pad nf_conntrack acpi_power_meter mac_hid bonding lp parport tcp_htcp xfs 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor hid_generic usbhid hid ixgbe igb raid6_pq vxlan i2c_algo_bit libcrc32c ahci 
ip6_udp_tunnel dca udp_tunnel libahci raid1 ptp pps_core megaraid_sas raid0 
mdio multipath fjes linear
Apr 14 00:34:43 cnode17 kernel: [204922.476423] CPU: 2 PID: 5905 Comm: ceph-osd 
Not tainted 4.4.0-19-generic #35
Apr 14 00:34:43 cnode17 kernel: [204922.476469] Hardware name: Dell Inc. 
PowerEdge R720/0W7JN5, BIOS 2.5.2 01/28/2015
Apr 14 00:34:43 cnode17 kernel: [204922.476538] task: 8822ea962940 ti: 
8822eab44000 task.ti: 8822eab44000
Apr 14 00:34:43 cnode17 kernel: [204922.476606] RIP: 0010:[]  
[] task_numa_find_cpu+0x23c/0x710
Apr 14 00:34:43 cnode17 kernel: [204922.476682] RSP: :8822eab47bd8  
EFLAGS: 00010206
Apr 14 00:34:43 cnode17 kernel: [204922.476723] RAX:  RBX: 
8822eab47c78 RCX: 
Apr 14 00:34:43 cnode17 kernel: [204922.476789] RDX:  RSI: 
88239f84 RDI: 8823847efa00
Apr 14 00:34:43 cnode17 kernel: [204922.476856] RBP: 8822eab47c40 R08: 
0001030c9163 R09: 0262
Apr 14 00:34:43 cnode17 kernel: [204922.476923] R10: 0185 R11: 
0001b936 R12: 88470dcf6e00
Apr 14 00:34:43 cnode17 kernel: [204922.477086] R13: 000d R14: 
0089 R15: 0166
Apr 14 00:34:43 cnode17 kernel: [204922.477153] FS:  7f86a7caa700() 
GS:88239f84() knlGS:
Apr 14 00:34:43 cnode17 kernel: [204922.477222] CS:  0010 DS:  ES:  
CR0: 80050033
Apr 14 00:34:43 cnode17 kernel: [204922.477265] CR2: 21ba73f0 CR3: 
002384352000 CR4: 001426e0
Apr 14 00:34:43 cnode17 kernel: [204922.477331] Stack:
Apr 14 00:34:43 cnode17 kernel: [204922.477364]  8847706be600 
88479f016d70 002619b8 8822ea962940
Apr 14 00:34:43 cnode17 kernel: [204922.477450]  0089 
ffc5 00016d00 0089
Apr 14 00:34:43 cnode17 kernel: [204922.477535]  8822ea962940 
8822eab47c78 0211 01af
Apr 14 00:34:43 cnode17 kernel: [204922.477621] Call Trace:
Apr 14 00:34:43 cnode17 kernel: [204922.477660]  [] 
task_numa_migrate+0x43e/0x9b0
Apr 14 00:34:43 cnode17 kernel: [204922.477706]  [] 
numa_migrate_preferred+0x79/0x80
Apr 14 00:34:43 cnode17 kernel: [204922.477751]  [] 
task_numa_fault+0x7f4/0xd40
Apr 14 00:34:43 cnode17 kernel: [204922.477795]  [] ? 
should_numa_migrate_memory+0x55/0x130
Apr 14 00:34:43 cnode17 kernel: [204922.477845]  [] 
handle_mm_fault+0xbc0/0x1820
Apr 14 00:34:43 cnode17 kernel: [204922.477890]  [] ? 
SYSC_recvfrom+0x144/0x160
Apr 14 00:34:43 cnode17 kernel: [204922.477936]  [] 
__do_page_fault+0x197/0x400
Apr 14 00:34:43 cnode17 kernel: [204922.477980]  [] 
do_page_fault+0x22/0x30
Apr 14 00:34:43 cnode17 kernel: [204922.478025]  [] 
page_fault+0x28/0x30
Apr 14 00:34:43 cnode17 kernel: [204922.478066] Code: 55 b0 4c 89 f7 e8 f5 c9 
ff ff 48 8b 55 b0 49 8b 4e 78 48 8b 82 d8 01 00 00 48 83 c1 01 31 d2 49 0f af 
86 b0 00 00 00 4c 8b 73 78 <48> f7 f1 48 8b 4b 20 49 89 c0 48 29 c1 48 8b 45 d0 
4c 03 43 48 
Apr 14 00:34:43 cnode17 kernel: [204922.478513] RIP  [] 
task_numa_find_cpu+0x23c/0x710
Apr 14 00:34:43 cnode17 kernel: [204922.478561]  RSP 
Apr 14 00:34:43 cnode17 kernel: [204922.479210] ---[ end trace 7acc418f42a233b0 
]---

-- 
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 notifications about this bug go to:

[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Markus Schade]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs