The patch I highlighted in Comment #9 appears to be unrelated -
4.15.0-76 still fails even though it has the patch. A test build of
4.15.0-76 w/ the patch reverted also fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Correction for the previous comment: version should be 1:4.0+dfsg-
0ubuntu9.2. To be clear, neither the current QEMU in eoan-updates (.2),
nor the one in eoan-proposed (.3) fails my reproducer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
qemu/eoan (1:4.0+dfsg-0ubuntu9.3) does not seem to be impacted by this
issue - at least, my reproducer doesn't trigger it. However, I've tested
the package from -proposed, and it continues to pass the test, so I'll
mark eoan verified.
** Tags removed: verification-needed verification-needed-eoan
*
I think I've figured out how to simulate the OVMF PXE -> iPXE chaining
you are doing, which had me confused in Comment #14. I also see the
problem being introduced between the versions you identified, and was
able to bisect it down to the following commit:
# first bad commit: [6e5e544f227f031d0b45
Looking at the git log - I wonder if this could be related?
commit 94bb804e1e6f0a9a77acf20d7c70ea141c6c821e
Author: Pavel Tatashin
Date: Tue Nov 19 17:10:06 2019 -0500
arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess
fault
It's interesting because ThunderX is somewhat un
I attempted to bisect this, using the following process:
- Run the kernel-build-reboot-loop test on 3 machines in parallel
I used 2 CRB1S systems (anuchin, bestovius) and 1 R120-T33 (seidel)
- If any machine crashes w/ the parity error message, consider it failed
- If all machines survive
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857074
Title
My $0.02 is that we should mark this Invalid. We appear to have
intentionally changed the governor, and that new governor does not
expose the attributes that the old one did. @Gavin: is this causing any
issue for you, or is it just something your testing noticed?
** Changed in: linux-snapdragon (U
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776654
Title:
systemd upstream sysusers tests fails
To manage notifi
Verified, using test case described in Description.
** 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/1859527
Title:
ystemd (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notific
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
** Bug watch added: github.com/systemd/systemd/issues #8880
https://github.com/systemd/systemd/issues/8880
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859527
Title:
vring_get_region_caches: As
On Mon, Jan 27, 2020 at 1:25 PM Ubuntu SRU Bot
<1859...@bugs.launchpad.net> wrote:
>
> All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.22) for
> bionic have finished running.
> The following regressions have been reported in tests triggered by the
> package:
>
> systemd/237-3ub
Notice in the log in comment #6 that the unexpected error we are seeing
for "unhappy-2" is the expected error for "unhappy-1".
I wonder if there's a race here:
# tests for error conditions
for f in unhappy-*.input; do
echo "*** Running test $f"
rm -
Another instance:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/s/systemd/20200127_181441_fb524@/log.gz
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubunt
** Also affects: distro-info-data (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: distro-info-data (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: distro-info-data (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects:
Public bug reported:
[Impact]
The debian-distro-info command reports out of date information. I noticed this
when debugging a vagrant-mutate autopkgtest failure (which ended up being
unrelated).
[Test Case]
$ debian-distro-info --stable
stretch
After update:
$ debian-distro-info --stable
bust
** Also affects: dmidecode (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: dmidecode (Ubuntu Xenial)
Status: New => In Progress
** Changed in: dmidecode (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notifi
** Description changed:
- Device: Inforce 6640
-
https://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-820-inforce-6640-sbc
- SoC: Snapdragon 820
+ [Impact]
+ Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to
crash/reboot. cloud-init apparently
Actually, I realized I can reproduce this on a dragonboard I have here.
I've verified the PPA fix myself, so I'll go ahead and SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmide
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: dmidecode (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: dmidecode (Ubuntu Eoan)
Status: New => In Progress
** Changed in: dmidecode (Ubuntu Bionic)
Status: New => I
We carry this patch in focal - do we just need to backport it to bionic?
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
I uploaded a test fix to ppa:dannf/test. Could someone w/ hw access
verify that?
--
You received this bug notification b
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855958
Title:
scsi: hisi_sas: Return directly if init hardware f
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854550
Title:
[scsi-1130]scsi: scsi_transport_sas: Fix memory le
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855952
Title:
scsi: hisi_sas: Check sas_port before using it
To
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc3 hpre patchs
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853999
Title:
[sas-1126]scsi: hisi_sas: use wait_for_completion_
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854549
Title:
[acc-1130]sync mainline kernel 5.5rc1 acc patchse
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854000
Title:
[sas-1126]scsi: hisi_sas: Replace in_softirq() che
For fwupd-signed, I verified it by copying the fwupdx64.efi.signed over
the grubx64.efi binary on a SecureBoot-enabled system and verified that
it was able to be exec'd. (I'm not sure how to force shim to execute it
any other way).
** Tags removed: verification-needed verification-needed-eoan
** T
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858590
Title:
fwupaa64.efi crashes on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Changed in: fwupd (Ubuntu)
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/1860536
Title:
fwupd-signed 1.2.10-1ubuntu4 not available in eoan-proposed
To manage n
@djgalloway: If you haven't removed your previously working older
kernel, you should be able to boot into it from the GRUB menu. Another
suggestion would be to boot into rescue mode from an Ubuntu 18.04.3 ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1057.62 has them, 1058.64 does not.
I noticed that 1057.62 has only the performance governor built-in, and
1058.64 only has the on-demand governor built-in.
ubuntu@dragon410c:~$ grep CPU_FREQ_DEFAULT_GOV
/boot/config-4.15.0-1057-snapdragon /boot/config-4.15.0-1058-snapdragon
/boot/config-4.15.0
Correction: that should be 4.15.0-1070.73.
4.15.0-1053.57, which appears to be the oldest one in the archive,
*does* have those files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860527
Title:
s
I can reproduce on 4.15.0-107.73, the current -updates kernel:
ubuntu@dragon410c:~$ ls /sys/devices/system/cpu/cpufreq/
ubuntu@dragon410c:~$
So this is not a regression with current -proposed.
With 4.15.0-45.48 (the one from the ppisati image):
ubuntu@dragon410c:~$ ls /sys/devices/system/cpu/cpufr
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
** Description changed:
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system
which is configured (via BIOS) as a single NUMA domain.
[Test Case]
+
+ uvt-kvm create test
+ uvt-kvm wait test
+ uvt-kvm ssh test sudo poweroff
+
+ virsh edit test
+
+ # chang
Thx. fwupd-signed is in the SRU queue but needs to be approved before
this goes out. I'll add the block-proposed tag here until then.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
fwupd-signed is pending in the SRU queue. I've added block-proposed to
bug 1858590 to prevent fwupd from being promulgated until fwupd-signed
is available as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Also affects: fwupd-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fwupd-signed (Ubuntu Bionic)
Status: New => In Progress
** Changed in: fwupd-signed (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: fwupd-signed (
The 4.15.0-76 kernel has survived several iterations on 2 nodes, so
marking verified.
** 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.lau
** Attachment added: "dmidecode_-t_memory.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321215/+files/dmidecode_-t_memory.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Attachment added: "dmidecode_-t_bios.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321214/+files/dmidecode_-t_bios.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "Full console log of host seidel oops w/ error 5.0.0-37.40"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321212/+files/seidel.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Attachment added: "dmidecode_-t_processor.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321213/+files/dmidecode_-t_processor.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321216/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860013
Title:
[t
eoan verification:
FS0:\efi\> fwupdaa64.efi
WARNING: No updates to process. Called in error?
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@Timo: Is that true even when the subsequent proposed upload merges all
changes into the same package version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab and
All 3 of my machines survived overnight testing on the 5.5-rc6 mainline
build[*].
Next step is to try 5.3. 5.3 mainline doesn't boot on these systems, so I'll
use Ubuntu's 5.3.0-24.
[*] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc6/
--
You received this bug notification because you a
Also reproducible w/ the 5.0.0-37.40 kernel. I'll try a mainline 5.5-rc6
build next.
[ 602.796765] Internal error: synchronous parity or ECC error: 9618 [#1]
SMP
[ 602.803994] Modules linked in: nls_iso8859_1 cavium_rng_vf ipmi_ssif
ipmi_devintf input_leds joydev ipmi_msghandler thunderx_e
** Summary changed:
- Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)
+ Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Summary changed:
- Cavium ThunderX CN88XX Panic : Unknown reason
+ Cavium ThunderX CN88XX crashes on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857074
Title:
Cavium ThunderX CN88XX cras
On Wed, Jan 15, 2020 at 11:28 PM Juerg Haefliger
wrote:
>
> On Thu, 16 Jan 2020 02:14:16 -0000
> dann frazier wrote:
>
> > I built a kernel with the proposed patches[*] and ran a reboot/kernel
> > compile test on 4 systems. The tests survived 46 total iterations
&
Public bug reported:
[Impact]
Under load, ThunderX systems eventually fail with:
[ 282.360376] Synchronous External Abort: synchronous parity or ECC error
(0x9618) at 0xa6eb7000
[ 282.372351] Internal error: : 9618 [#1] SMP
[ 282.379152] Modules linked in: nls_iso8859_1 thunde
The description shows 2 Oops messages - one in IPMI, and one in ext4. I
had marked this as a duplicate of bug 1857074 because the ext4 symptom
is in both. But, per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/comments/18
, the IPMI issue exists even with the fix for LP: #1857074. So
I've now seen an occurrence of the the SEA/ECC issue on a system w/ the
4.15.0-70 kernel, so I think we can safely assume this is not a
regression related to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I built a kernel with the proposed patches[*] and ran a reboot/kernel
compile test on 4 systems. The tests survived 46 total iterations
(~12/system) before I interrupted. Two systems failed with "Synchronous
External Abort: synchronous parity or ECC error" errors.
I've reverted the systems back to
We reverted the offending patch while we continue to work towards root
causing the failure. The revert will cause this bug to be resolved, so
I've opened bug 1859873 to track fixing and reapplying the patch (+ any
fixes). I suggest we move further technical discussion there.
** Description changed
Public bug reported:
This bug tracks the reapplication of "usb: handle warm-reset port
requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from
the Ubuntu kernels due to a regression it introduced (bug 1856608).
However, that patch did fix an issue for a user
On Tue, Jan 14, 2020 at 8:35 AM Juerg Haefliger
<1857...@bugs.launchpad.net> wrote:
>
> We certainly want this:
>
> commit 71c751f2a43fa03fae3cf5f0067ed3001a397013
> Author: Mark Rutland
> Date: Mon Apr 23 11:41:33 2018 +0100
>
> arm64: add sentinel to kpti_safe_list
Agreed, nice catch. Unf
** Patch added: "lp1858590-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1858590/+attachment/5320128/+files/lp1858590-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I've uploaded a new fwupd for eoan with an additional fix (for bug
1858590), as well as an fwupd-signed that covers both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856896
Title:
Only check the
v4.14.151 upstream fails as well - but with a different symptom (see
below). v4.14.150 seems fine, so I'll try and bisect between the two. Of
course, that's really just a shot in the dark, as we know this issue is
finicky..
[ 34.896151] Unable to handle kernel paging request at virtual address
** Changed in: qemu (Ubuntu Bionic)
Status: New => In Progress
** Changed in: qemu (Ubuntu Bionic)
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.launchp
Thread 1 (Thread 0x7f2a00963640 (LWP 15030)):
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x7f29fabdd801 in __GI_abort () at abort.c:79
#2 0x7f29fabcd39a in __assert_fail_base (fmt=0x7f29fad547d8 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=asse
Public bug reported:
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system
which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
[Regression Risk]
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu (Ub
** Attachment added: "4.14.164.config"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5319910/+files/4.14.164.config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857074
fyi, I was able to reproduce this w/ upstream 4.14.164, built w/ an
Ubuntu-based config.
** Attachment added: "4.14.164.dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5319909/+files/4.14.164.dmesg
--
You received this bug notification because you are a member
in: binutils (Ubuntu)
Status: New => Fix Committed
** Changed in: binutils (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: crash (Ubuntu)
Status: New => In Progress
** Changed in: crash (Ubuntu)
Assignee: (unassigned) => dann frazier (dan
This appears to fix it for me:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commitdiff;h=8cd0e5e93145699736a370b271ff03f3f41670b0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859226
** Also affects: crash (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/1859226
Title:
crash reports Illegal instruction w/ newer binutils
To manag
Public bug reported:
crash 7.2.6-1ubuntu1 now fails on arm64 w/ an Illegal instruction:
$ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) /proc/kcore
Illegal instruction
The previous version of crash was 7.2.6-1build1. While there are no
differences in the source code (just an autopkgtest
18892/+files/recht-console.log
** Changed in: linux (Ubuntu Focal)
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-po
Public bug reported:
crash autopkgtests have began to fail on arm64, as seen here:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/arm64/c/crash/20191223_190616_50c73@/log.gz
The significant difference between this test and the l
*** This bug is a duplicate of bug 1857074 ***
https://bugs.launchpad.net/bugs/1857074
** This bug has been marked a duplicate of bug 1857074
Cavium ThunderX CN88XX Panic : Unknown reason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "'dmesg | grep -e usb -e xhci -e hub' w/ usbcore.dyndbg=+p"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+attachment/5318666/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@kaihengfeng - sorry for the delay over the US holidays. I don't have
physical access to the system myself, but I've made the request to a
user who does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Tagging verification-failed due to bug 1857074.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853485
Title:
Bi
Marking verification failed, as that is blocked by bug 1857074.
** Description changed:
We reverted a couple changes in 4.15.0-72.81 because they were causing a
regression (bug 1853326) that was not understood at press time:
b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hv
** Changed in: linux (Ubuntu Bionic)
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/1857074
Title:
Cavium ThunderX CN88XX Panic : Unknown reason
To manage notificatio
Fixed packages are staged here:
https://launchpad.net/~dannf/+archive/ubuntu/fwupd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858590
Title:
fwupaa64.efi crashes on startup
To manage notificat
Public bug reported:
[Impact]
fwupdaa64.efi crashes on startup
[Test Case]
FS0:\EFI\BOOT\> fwupdaa64.efi
Synchronous Exception at 0x000438759658
Synchronous Exception at 0x000438759658
[Fix]
https://github.com/fwupd/fwupd/commit/8b044c6cb3d007803bd67ca5e6527ed89d5ecb62
[Regression R
** Attachment added: "anuchin-4.15.0-74.84-bionic-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317960/+files/anuchin-4.15.0-74.84-bionic-oops.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "seidel-4.15.0-74.84-xenial-no-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317963/+files/seidel-4.15.0-74.84-xenial-no-oops.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Our testing found the same issue on 2 other CN88XX systems (seidel &
anuchin), I'll attach the logs here. Interestingly, while both systems
hit the oops when booting the bionic 4.15.0-74.84, neither system had a
problem with the xenial hwe 4.15.0-74.84.
--
You received this bug notification becau
** Attachment added: "anuchin-4.15.0-74.84-xenial-no-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317961/+files/anuchin-4.15.0-74.84-xenial-no-oops.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "seidel-4.15.0-74.84-bionic-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317962/+files/seidel-4.15.0-74.84-bionic-oops.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sbuild-launchpad-chroot (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: sbuild-launchpad-chroot (Ubuntu Disco)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
[Impact]
s-l-c is unable to consume LP chroots. Launchpad appears to have changed the
extension of stored chroots, presumably in
https://git.launchpad.net/launchpad/commit/?id=3d107db183c22f6653412291bf1d66c3a2edf984
[Test Case]
Current bionic (0.14):
$ sudo sbuild-launchp
** Changed in: linux (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/1854207
Title:
Unrevert "arm64: Use firmware to detect CPUs that are not affected by
Running upstream 5.5-rc2 mainline build:
$ dmesg | grep -e usb -e xhci -e hub
[ 13.482690] usbcore: registered new interface driver usbfs
[ 13.486685] usbcore: registered new interface driver hub
[ 13.490894] usbcore: registered new device driver usb
[ 20.767117] xhci_hcd :00:14.0: xHC
** Description changed:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
+
+ Kernel emits messages like:
+ usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[Test Case]
dme
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
git bisect reports:
0b6a70743beacb15516ef9572b40c93b8b3892d3 is the first bad commit
commit 0b6a70743beacb15516ef9572b40c93b8b3892d3
Author: Jan-Marek Glogowski
Date: Fri Feb 1 13:52:31 2019 +0100
usb: handle warm-reset port requests on hub resume
--
You received this bug notification because
fyi, what I tested in Comment #35 was upstream QEMU (@ aceeaa69d2) with
a port of the patch in Comment #34 applied. I've attached that patch
here. While it did avoid the issue in my testing, I agree with Rafael's
Comment #36 that it does not appear to address the root cause (as I
understand it), an
I tested the patch in Comment #34, and it was able to pass 500
iterations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805256
Title:
qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Public bug reported:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
[Test Case]
dmesg | grep "Cannot enable"
[Fix]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
801 - 900 of 3385 matches
Mail list logo
