[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

2020-09-17 Thread dann frazier
** Changed in: gdm3 (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/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle

[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

2020-09-15 Thread dann frazier
@Naresh: see my comment #4, asking if you are running Ubuntu Desktop. dmesg doesn't tell me that - but an sosreport would, if you can attach that. We've recently hit this on an x86 server, and did tie that back to the system having a desktop installed (Nvidia CUDA 11 somehow brings in gdm as a

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-26 Thread dann frazier
sbsigntool w/ "Breaks: secureboot-db (<< 1.7~)" now uploaded to groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892797 Title: sbkeysync fails to return non-zero on error To manage

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-26 Thread dann frazier
Sure thing, I'll prepare one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892797 Title: sbkeysync fails to return non-zero on error To manage notifications about this bug go to:

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-26 Thread dann frazier
Fair enough, I suppose I should think more about a way to let a user know that the db update failed - and the consequences of it - that do not involve failing a systemd unit. No objections to rejected the SRUs. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-25 Thread dann frazier
** Description changed: [Impact] sbkeysync may exit with exitcode 0 even if it failed to update keys. The secureboot-db service will report no error in this case. This can lead a user to believe they have protected themselves against known insecure bootloaders when they have not. An

[Bug 1892797] [NEW] sbkeysync fails to return non-zero on error

2020-08-24 Thread dann frazier
Public bug reported: [Impact] sbkeysync may exit with exitcode 0 even if it failed to update keys. The secureboot-db service will report no error in this case. This can lead a user to believe they have protected themselves against known insecure bootloaders when they have not. An example of

[Bug 1892792] [NEW] Causes grub-install to segfault

2020-08-24 Thread dann frazier
Public bug reported: After updating one of my VMs from 37-2ubuntu4 to 37-4ubuntu1, grub- install began to segfault: $ sudo grub-install Installing for x86_64-efi platform. Segmentation fault gdb shows the backtrace in parse_acpi_root(): (gdb) bt #0 __strlen_avx2 () at

[Bug 1892347] Re: HiSilicon HNS3 ethernet broken

2020-08-24 Thread dann frazier
*** This bug is a duplicate of bug 1859756 *** https://bugs.launchpad.net/bugs/1859756 TLDR; ignore in-tree driver version strings, they don't really mean anything. I have no idea what the proprietary driver is or how it is versioned, so I can't speak to that. I can say that version strings

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2020-08-24 Thread dann frazier
** Bug watch added: Debian Bug tracker #963475 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475 ** Also affects: efivar (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1891718] Re: [Regression] breaks GRUB install on an nvme device

2020-08-15 Thread dann frazier
** Bug watch added: github.com/rhboot/efivar/issues #157 https://github.com/rhboot/efivar/issues/157 ** Also affects: efivar via https://github.com/rhboot/efivar/issues/157 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of

[Bug 1891718] [NEW] [Regression] breaks GRUB install on an nvme device

2020-08-14 Thread dann frazier
Public bug reported: After upgrading a system from bionic to focal, grub-install began to fail: $ sudo /usr/sbin/grub-install Installing for x86_64-efi platform. /usr/sbin/grub-install: warning: Internal error. /usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-08-14 Thread dann frazier
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Triaged => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04 Status: Triaged => Fix Committed ** Changed in: kunpeng920 Status: Triaged => Fix Committed -- You received this bug notification because you are a member of

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-08-13 Thread dann frazier
This build log shows tests running for ~40s: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/e/edk2/20200807_201106_d36d2@/log.gz This provides the evidence I was looking for in Comment #6 that the tests can take longer

[Bug 1888423] Re: ras-mc-ctl doesn't provide BDF for PCIe errors

2020-08-11 Thread dann frazier
Verification: ubuntu@akis:~$ cat einj.sh #!/bin/bash D="/sys/kernel/debug/apei/einj" # supported errors for injection listed in ${D}/available_error_types # magic numbers from ACPI 6.3 18.6.3 table 18-409 ERROR_TYPE="0x40" # PCIe SBDF - ACPI 6.3 18.6.3 table 18-410 # Byte 3 – PCIe Segment

[Bug 1888423] Re: ras-mc-ctl doesn't provide BDF for PCIe errors

2020-08-11 Thread dann frazier
Note that the "DBD::SQLite::db prepare failed:" message in the last comment also occurs pre-upgrade, so it is not a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888423 Title:

[Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch

2020-08-10 Thread dann frazier
Marking as impacting subiquity, because being unable to mount root is unlikely a problem with the kernel itself. ** Also affects: subiquity Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-08-07 Thread dann frazier
Verified w/ over 500 successful iterations on a m6g.metal instance, and over 300 in an armhf chroot on the same. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a

Re: [Bug 1890646] [NEW] ovmf builds lack TPM support

2020-08-06 Thread dann frazier
On Thu, Aug 6, 2020 at 12:05 PM Dimitri John Ledkov <1890...@bugs.launchpad.net> wrote: > > Public bug reported: > > ovmf builds lack TPM support in groovy, yet it was present in focal. > > I wonder what is missing from making TPM support work, for bios / > firmware measurements to work with

[Bug 1885662] Re: please provide 4MB firmware builds

2020-08-03 Thread dann frazier
ug/1885662/+attachment/5398518/+files/edk2_2020.05-2ubuntu1_2020.05-2ubuntu1+4M.2.debdiff ** Changed in: edk2 (Ubuntu Groovy) Status: New => In Progress ** Changed in: edk2 (Ubuntu Groovy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notifica

[Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread dann frazier
@Milan: I don't doubt that there maybe also be a driver issue, but that wasn't the root cause of this issue. @All: It might be helpful to know, for each of these cases, if what you are seeing is also correlated with the patch we reverted (and are planning to reintroduce) in older releases. To

[Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread dann frazier
fyi, the system for which I originally filed this bug was conclusively determined to have an out-of-spec USB cable, for which the manufacturer is providing replacements. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1873914] Re: initramfs clevis no carrier after 1s, no retry

2020-07-22 Thread dann frazier
Hi @Thorsten! This sounds like an issue we've been discussing upstream[1], and I think I have an approach that might work for you. It requires changes to both clevis and initramfs-tools. I've prepared test packages in a PPA[2]. Would it be possible for you to test these? Note that you will need

[Bug 1888423] Re: ras-mc-ctl doesn't provide BDF for PCIe errors

2020-07-22 Thread dann frazier
possible that a user has some + code to parse the output that would be confused by the additional + content. ** Changed in: rasdaemon (Ubuntu Focal) Status: New => In Progress ** Changed in: rasdaemon (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) ** Description c

[Bug 1888423] Re: ras-mc-ctl doesn't provide BDF for PCIe errors

2020-07-21 Thread dann frazier
** Description changed: - The ras-mc-ctl tool will extract and display PCIe AER events from the - database, but it fails to identify the associated PCIe device. - This information is stored in the database (has been since 0.6.5), - so we just need to update ras-mc-ctl to include it. + [Impact] +

[Bug 1888423] Re: ras-mc-ctl doesn't provide BDF for PCIe errors

2020-07-21 Thread dann frazier
** Changed in: rasdaemon (Ubuntu) Status: New => In Progress ** Changed in: rasdaemon (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

[Bug 1888423] [NEW] ras-mc-ctl doesn't provide BDF for PCIe errors

2020-07-21 Thread dann frazier
Public bug reported: The ras-mc-ctl tool will extract and display PCIe AER events from the database, but it fails to identify the associated PCIe device. This information is stored in the database (has been since 0.6.5), so we just need to update ras-mc-ctl to include it. I've recently had a

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-07-15 Thread dann frazier
I ran the new PPA build (1:2.11+dfsg-1ubuntu7.29~ppa01) on both a ThunderX2 system and a Hi1620 system overnight, and both survived (6574 & 12919 iterations, respectively). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1884788] Re: Update bionic/eoan to the fwupd 1.2.13 release

2020-07-10 Thread dann frazier
The current upload has the line: * Don't cleanup /var/cache/fwupdate anymore (LP: #1858590) But bug #1858590 is about fwupaa64.efi crashing on arm64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-06-26 Thread dann frazier
The initial autopkgtest results after bumping the timeout to 60s passed, but each test ran within a time length that may have passed even with the previous 30s timeout (longest case I see was 32s). Before (low- impact) SRU'ing this back, ideally we'd be able to point to a test that clearly blew

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-06-25 Thread dann frazier
** Description changed: - Recently edk2 autopkgtests fail intermittently - but the frequency has - increased quite a bit recently. The autopkgtests run QEMU to boot to an - EFI prompt, and then power off. The run for each of the supported archs + edk2 autopkgtests fail intermittently - but the

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-06-25 Thread dann frazier
The failures don't appear to follow an Ubuntu release, a host architecture, or the guest architecture being tested. So did something change externally? Looking at the data: Prior to June 2020, we only saw a 2.7% failure rate (3/112). Starting in June, that's grown to 25% (8/32). This is across

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-06-25 Thread dann frazier
It's not clear to me what the pattern is here, so I wrote a script to generate a csv file of the failures, including how long each test took and which ones timed out. ** Attachment added: "edk2-autopkgtest-times.py"

[Bug 1885186] Re: autopkgtests sometimes timeout

2020-06-25 Thread dann frazier
And here's the resulting csv from that script. ** Attachment added: "times.csv" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1885186/+attachment/5387225/+files/times.csv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1885186] [NEW] autopkgtests sometimes timeout

2020-06-25 Thread dann frazier
Public bug reported: Recently edk2 autopkgtests fail intermittently - but the frequency has increased quite a bit recently. The autopkgtests run QEMU to boot to an EFI prompt, and then power off. The run for each of the supported archs (ARM, AARCH64 & X64). The failure symptom is that 1 or more

[Bug 1883023] Re: clevis-luks-bind fails in non-interactive mode

2020-06-11 Thread dann frazier
** Also affects: clevis (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: clevis (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: clevis (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: clevis (Ubuntu Focal)

[Bug 1881947] [NEW] Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.

2020-06-03 Thread dann frazier
Public bug reported: Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz [...] PASS: test-journal-enum ==

[Bug 682445] Re: configure_networking doesn't wait for udev to populate available nics

2020-06-03 Thread dann frazier
This was fixed long ago. initramfs-tools (0.100) unstable; urgency=low Release "singing in the snow ☃☃☃" [...] [ Alkis Georgopoulos ] * [b938c7e] configure_networking() wait for udev to populate available nics (LP: #682445) [...] -- Michael Prokop Tue, 14 Feb 2012 14:42:23 +0100

[Bug 1872463] Re: Duplicate marker files will make chainload fail to launch subiquity

2020-05-26 Thread dann frazier
@Dimitri - is the significant difference there that $prefix can and should be trusted to uniquely point to the boot disk and only fallback to the .disk/info search? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch

2020-05-21 Thread dann frazier
@Ike: it looks like that patch depends on this other patch set, which is currently in linux-next: https://www.spinics.net/lists/linux-crypto/msg46951.html To avoid backporting that, perhaps you could drop the qm_list assignment. That said, I don't see a valid SRU justification for any of

[Bug 1875984] Re: console noise when / is not bound

2020-05-19 Thread dann frazier
Also regression tested by unbinding and manually entering a passphrase to unlock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875984 Title: console noise when / is not bound To manage

[Bug 1877620] Re: Backport of Patch "ata: ahci: Add shutdown to freeze hardware resources of ahci"

2020-05-08 Thread dann frazier
Patch was included in bionic in Ubuntu-4.15.0-97.98 ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1877620 Title: Backport

[Bug 1877620] Re: Backport of Patch "ata: ahci: Add shutdown to freeze hardware resources of ahci"

2020-05-08 Thread dann frazier
Path was included in eoan in Ubuntu-5.3.0-47.39 ** Changed in: linux (Ubuntu Eoan) Status: New => 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/1877620 Title: Backport of

[Bug 1877620] Re: Backport of Patch "ata: ahci: Add shutdown to freeze hardware resources of ahci"

2020-05-08 Thread dann frazier
Patch was included in focal/groovy in Ubuntu-5.4.0-18.22 ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1877620] Re: Backport of Patch "ata: ahci: Add shutdown to freeze hardware resources of ahci"

2020-05-08 Thread dann frazier
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal)

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-07 Thread dann frazier
Ike's backport in https://launchpad.net/~ikepanhc/+archive/ubuntu/lp1805256 tests well for me on Cavium Sabre. One minor note is that the function in_aio_context_home_thread() is being called in aio-win32.c, but that function didn't exist in 2.11. We probably want to change that to

[Bug 1872832] Re: initramfs-tools support

2020-05-07 Thread dann frazier
= Verification = == eoan == === dracut package contents haven't changed === $ mkdir 11-2 $ mkdir 11-2ubuntu0.1 $ dpkg-deb -x clevis-dracut_11-2_all.deb 11-2 $ dpkg-deb -x clevis-dracut_11-2ubuntu0.1_all.deb 11-2ubuntu0.1 $ diff -urpN 11-2 11-2ubuntu0.1 diff:

[Bug 1872846] Re: FTBFS when bash-completion installed

2020-05-07 Thread dann frazier
= Verification = Since this only impacts the source package, my pre-upload verification should suffice here. It also built successfully in -proposed, though that wasn't impacted as the builders don't appear to have bash-completion installed. ** Tags removed: verification-needed

[Bug 1875984] Re: console noise when / is not bound

2020-05-07 Thread dann frazier
= Verification = Note that the ip: errors are not a regression and I believe are due to my specific network config. But the /proc/$pid/environ errors are now gone: --- Begin: Running /scripts/init-premount ... ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or

[Bug 1875984] Re: console noise when / is not bound

2020-05-07 Thread dann frazier
Note that the riscv64 build in focal-proposed currently FTBFS. That's due to a regression related to the LP riscv64 builders that is causing our tests to run ~50% slower, which exceeds the default timeouts. wgrant has been looking into that. In groovy, I worked around those by increasing the

[Bug 1877270] Re: Devlink - add RoCE disable kernel support

2020-05-07 Thread dann frazier
** Also affects: linux (Ubuntu Groovy) Importance: Medium Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are

[Bug 1872832] Re: initramfs-tools support

2020-05-07 Thread dann frazier
Thanks for reviewing Łukasz! I believe dracut support has never worked - see bug 1814460, which we resolved by adding initramfs-tools support in focal. I will include a demonstration that the clevis-dracut package has not changed as part of verification, thanks for that suggestion. I hear you

[Bug 1872832] Re: initramfs-tools support

2020-05-06 Thread dann frazier
** Also affects: clevis (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: clevis (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-06 Thread dann frazier
On Wed, May 6, 2020 at 1:20 PM Philippe Mathieu-Daudé <1805...@bugs.launchpad.net> wrote: > > Isn't this fixed by commit 5710a3e09f9? See comment #43. The discussions hence are about testing/integration of that fix. -dann -- You received this bug notification because you are a member of

[Bug 1875984] Re: console noise when / is not bound

2020-05-06 Thread dann frazier
** Also affects: clevis (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: clevis (Ubuntu Focal) Status: New => In Progress ** Changed in: clevis (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: clevis (Ubuntu) As

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-06 Thread dann frazier
** Description changed: [Impact] * QEMU locking primitives might face a race condition in QEMU Async I/O bottom halves scheduling. This leads to a dead lock making either QEMU or one of its tools to hang indefinitely. [Test Case] * qemu-img convert -f qcow2 -O qcow2

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-05 Thread dann frazier
fyi, I backported that fix also to focal/groovy and eoan, and with those builds. On my test systems the hang reliable occurs within 20 iterations. After the fix, they have survived > 500 iterations thus far. I'll leave running overnight just to be sure. -- You received this bug notification

[Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15

2020-05-01 Thread dann frazier
@Mohammed: Can you also test the official build and set the verification tag as appropriate per comment #18? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from

[Bug 1875984] [NEW] console noise when / is not bound

2020-04-29 Thread dann frazier
Public bug reported: [Impact] There's a race condition in the clevis initramfs-hook that can cause noisy errors on the console. This is 100% reproducible when / is a dm_crypt device that is *not* bound to clevis, but seems like timing could cause it to happen when bound as well. [Test Case]

[Bug 1820764] Re: CVE-2018-12178 CVE-2018-12180 CVE-2018-12181

2020-04-17 Thread dann frazier
** Changed in: edk2 (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: edk2 (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed modules

2020-04-15 Thread dann frazier
The ubuntu-drivers-common task here appears to be to change it to prefer the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS counterparts. I'd recommend at that point that we start seeding linux- modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS counterparts,

[Bug 1871965] Re: new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-15 Thread dann frazier
= bionic verification = == AMD EPYC == # dmesg [ 631.470101] mce: [Hardware Error]: Machine check events logged [ 631.470104] [Hardware Error]: Deferred error, no action required. [ 631.470153] [Hardware Error]: CPU:0 (17:31:0) MC0_STATUS[-|-|MiscV|AddrV|-|-|SyndV|UECC|Deferred|-|-]:

[Bug 1871965] Re: new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-15 Thread dann frazier
= eoan verification = == AMD EPYC == # dmesg [ 2188.007718] mce: [Hardware Error]: Machine check events logged [ 2188.007722] [Hardware Error]: Deferred error, no action required. [ 2188.009446] [Hardware Error]: CPU:0 (17:31:0) MC0_STATUS[-|-|MiscV|AddrV|-|-|SyndV|UECC|Deferred|-|-]:

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-04-15 Thread dann frazier
Agreed, marked both tasks Won't Fix. ** Changed in: edk2 (Ubuntu Eoan) Status: Confirmed => Won't Fix ** Changed in: libvirt (Ubuntu Bionic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1872832] Re: initramfs-tools support

2020-04-14 Thread dann frazier
** Description changed: [Impact] clevis <= 12 did not integrate with initramfs-tools. This meant that if users wanted to automatically decrypt a luks volume for /, they had to use dracut, which is poorly supported in Ubuntu (see bug 1814460). [Test Case] sudo apt install clevis-luks

[Bug 1872832] Re: initramfs-tools support

2020-04-14 Thread dann frazier
** Description changed: [Impact] clevis <= 12 did not integrate with initramfs-tools. This meant that if users wanted to automatically decrypt a luks volume for /, they had to use dracut, which is poorly supported in Ubuntu (see bug 1814460). [Test Case] sudo apt install clevis-luks

[Bug 1872832] Re: initramfs-tools support

2020-04-14 Thread dann frazier
** Description changed: [Impact] clevis <= 12 did not integrate with initramfs-tools. This meant that if users wanted to automatically decrypt a luks volume for /, they had to use dracut, which is poorly supported in Ubuntu (see bug 1814460). [Test Case] sudo apt install clevis-luks

[Bug 1872846] [NEW] FTBFS when bash-completion installed

2020-04-14 Thread dann frazier
any specific regression risk here. ** Affects: clevis (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: clevis (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: clevis (Ubuntu Eoan) Import

[Bug 1872832] [NEW] initramfs-tools support

2020-04-14 Thread dann frazier
Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: clevis (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: clevis (Ubuntu Bionic) Importance: Undecided Status: New ** Also

[Bug 1871965] Re: new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-13 Thread dann frazier
** Description changed: [Impact] rasdaemon does not know how to decode MCE events from various new platforms, making it difficult to interpret errors reported up from the platform. [Test Case] On an AMD SMCA-capable system: #!/bin/bash modprobe mce-inject

[Bug 1871965] Re: new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-13 Thread dann frazier
** Description changed: [Impact] rasdaemon does not know how to decode MCE events from various new platforms, making it difficult to interpret errors reported up from the platform. [Test Case] + On an AMD SMCA-capable system: + #!/bin/bash + modprobe mce-inject - [Fix] +

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-13 Thread dann frazier
** Description changed: [Impact] This release contains both bug-fixes, new hardware support, and new features for users of Mellanox network controllers. The notable ones are:    * bug 1864475 - Add RoCE disable support [Test Case] The following development and SRU process will be

[Bug 1866319] Re: [focal] fail to reboot when installing focal daily live iso (200227)

2020-04-10 Thread dann frazier
Definitely looks like a kernel bug, assigning to linux. @Tai: do you have the version of the kernel that this version of the installer was running? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [focal] fail to reboot when installing focal

[Bug 1864475] Re: Mstflint package - add RoCE disable support

2020-04-10 Thread dann frazier
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864475 Title: Mstflint package - add RoCE disable support To manage

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-04-10 Thread dann frazier
One other comment about bionic - this would require a default config file change, so I believe every bionic user who has modified /etc/libvirt/qemu.conf would then get prompted about differences there. In my mind this tips the scales more towards "leave it alone". -- You received this bug

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-04-10 Thread dann frazier
This is now addressed in focal, so now let's discuss what we should do for eoan/bionic. = eoan = At a high level the issue here is that cosmic/disco behaved a certain way, eoan's behavior changed, and we've now restored the cosmic/disco behavior in focal. Detail: the behavior change concerns

[Bug 1869423] Re: Restore kernel control of PCIe DPC via option

2020-04-09 Thread dann frazier
= eoan verification = ubuntu@akis:~$ ls /sys/bus/pci_express/drivers/dpc/ :2d:00.0:pcie208 :50:10.0:pcie208 :bb:04.0:pcie208 :2d:01.0:pcie208 :56:00.0:pcie208 :bb:10.0:pcie208 :2d:02.0:pcie208 :56:04.0:pcie208 :d9:00.0:pcie208 :2d:03.0:pcie208

[Bug 1871965] Re: new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-09 Thread dann frazier
** Changed in: rasdaemon (Ubuntu Eoan) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: rasdaemon (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1871965] [NEW] new platform support: Intel SkyLake, AMD Scalable MCA

2020-04-09 Thread dann frazier
Public bug reported: [Impact] rasdaemon does not know how to decode MCE events from various new platforms, making it difficult to interpret errors reported up from the platform. [Test Case] [Fix] [Regression Risk] ** Affects: rasdaemon (Ubuntu) Importance: Undecided Status: Fix

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-03 Thread dann frazier
Thanks Jim - given that, I've marked the command line portion of the testing complete. ** Description changed: [Impact] This release contains both bug-fixes, new hardware support, and new features for users of Mellanox network controllers. The notable ones are:    * bug 1864475 - Add

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-04-03 Thread dann frazier
** Changed in: libvirt (Ubuntu) Status: In Progress => Invalid ** Changed in: libvirt (Ubuntu Eoan) Status: Confirmed => Invalid ** Changed in: edk2 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
= Command usage analysis = Summary - the -proposed usage statements all describe a superset of the commands/arguments in the previous version, with one exception. In bionic, mstflint's -qq argument used to say it affected both the burn and query commands - but the -proposed version only claims

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
** Patch added: "bionic-usages.diff" https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1869441/+attachment/5345231/+files/bionic-usages.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
** Patch added: "eoan-usages.diff" https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1869441/+attachment/5345230/+files/eoan-usages.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869441

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
= Command usage() regression checks = Here's how I'm comparing the usage output of each command to make sure no flags were dropped/changed: $ mkdir cur proposed $ dpkg -L mstflint | grep ^/usr/bin/ > mstflint.commands $ for cmd in $(< mstflint.commands); do $cmd -h > cur/$(basename $cmd).usage;

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
= Clean upgrade verifications = == eoan == ubuntu@mstflint-eoan:~$ sudo apt install mstflint -y Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-04-02 Thread dann frazier
I used the attached script to compare the contents of the existing & proposed versions of this package in eoan and bionic. The output for each follows. The set of utilities in -proposed is a superset of the existing version in each release, so I'll check that off in the validation checklist.

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-31 Thread dann frazier
I've just uploaded the following changes to Debian: https://salsa.debian.org/qemu-team/edk2/-/commit/1698e2a07e5c8a07ff0d772d2a9377ebe577d544 https://salsa.debian.org/qemu-team/edk2/-/commit/a08b306955cfde78b39028ae8bad44922e0c8e1b

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-31 Thread dann frazier
** Changed in: edk2 (Ubuntu Bionic) Status: New => Invalid ** Changed in: edk2 (Ubuntu) Status: New => In Progress ** Changed in: edk2 (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-30 Thread dann frazier
After digging into this today, I'm thinking that I may not be using OVMF_CODE.secboot.fd as intended. While I initially assumed that specifying OVMF_CODE.secboot.fd would give you a system with Secure Boot *active* - it actually just gives you a system where Secure Boot *could* be activated, if

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-30 Thread dann frazier
** Also affects: edk2 (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/1864532 Title: Incorrect nvram template for secboot firmware To manage

[Bug 1864535] Re: What is OVMF_CODE.ms.fd for?

2020-03-30 Thread dann frazier
** Description changed: In the ovmf package, /usr/share/OVMF/OVMF_CODE.ms.fd is a symlink to OVMF_CODE.fd, which is a build of OVMF that does *not* support Secure Boot. I assume the "ms" stands for Microsoft, whose signing keys are included in the OVMF_VARS.ms.fd nvram template. If so,

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-30 Thread dann frazier
** Changed in: libvirt (Ubuntu Eoan) Status: New => Confirmed ** Changed in: libvirt (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: libvirt (Ubuntu) Status: Confirmed => In Progress ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => dann fr

[Bug 1864532] Re: Incorrect nvram template for secboot firmware

2020-03-30 Thread dann frazier
** Also affects: libvirt (Ubuntu Eoan) 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/1864532 Title: Incorrect nvram template for secboot firmware To

[Bug 1869441] Re: Update to upstream version 4.13.3-2

2020-03-27 Thread dann frazier
) => dann frazier (dannf) ** Changed in: mstflint (Ubuntu Eoan) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869441 Title: Update to upstream v

[Bug 1864475] Re: Mstflint package - add RoCE disable support

2020-03-27 Thread dann frazier
While we are seeking to fix this in bionic/eoan by backporting a new upstream version (bug 1869441), note that it would have also been possible to backport the mstreg command (and supporting infrastructure) to bionic's 4.8 version. See:

[Bug 1869441] [NEW] Update to upstream version 4.13.3-2

2020-03-27 Thread dann frazier
Public bug reported: [Impact] This release contains both bug-fixes, new hardware support, and new features for users of Mellanox network controllers. The notable ones are: * bug 1864475 - Add RoCE disable support [Test Case] The following development and SRU process will be followed:

[Bug 1868174] Re: [FFe] mstflint: enable mstreg command

2020-03-24 Thread dann frazier
Thanks Stéphane! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868174 Title: [FFe] mstflint: enable mstreg command To manage notifications about this bug go to:

[Bug 1868323] Re: [FFe] clevis 12 adds initramfs support & tpm2-tools compat

2020-03-20 Thread dann frazier
Upgrade log (clevis-initramfs is a new package): dannf@focal:~$ sudo apt install clevis clevis-luks clevis-initramfs Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: bc

[Bug 1868323] Re: [FFe] clevis 12 adds initramfs support & tpm2-tools compat

2020-03-20 Thread dann frazier
Testing - binding a luks device and demo that it boots w/o user input: dannf@focal:~$ sudo clevis luks bind -d /dev/vda3 tang '{"url": "http://192.168.1.186"}' The advertisement contains the following signing keys: DQSThDmKDhD2GQIDSIYLWGc8Tjc Do you wish to trust these keys? [ynYN] y Enter

  1   2   3   4   5   6   7   8   9   10   >