On Fri, Oct 11, 2019 at 08:30:02AM +, Jan Glauber wrote:
> On Fri, Oct 11, 2019 at 10:18:18AM +0200, Paolo Bonzini wrote:
> > On 11/10/19 08:05, Jan Glauber wrote:
> > > On Wed, Oct 09, 2019 at 11:15:04AM +0200, Paolo Bonzini wrote:
> > >>> ...but if I bump notify_me size to uint64_t the issue
** Changed in: kunpeng920/ubuntu-19.04
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/1845355
Title:
Support Hi1620 zip hw accelerator
To manage notifica
** Also affects: gdb (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Also affects: gdb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gdb (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: gdb (Ubuntu Disco)
Importance:
I have a test fix building here, could one of you verify it?
https://launchpad.net/~dannf/+archive/ubuntu/lp1848200
** Changed in: gdb (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gdb (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
You receive
** Description changed:
- After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
- stop on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
+ [Impact]
+ After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
+ on breakpoint when running a 32-bit
** 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
** 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/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/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/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/1855958
Title:
scsi: hisi_sas: Return directly if init hardware f
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
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
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
** 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
** 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
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: 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:
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
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 -
hing was out of
sync at the time. I retried the test and it passed.
-dann
--
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: Assertion `caches != NULL' fai
** 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
** 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)
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
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:
** 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
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: 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
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
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 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
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
*
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
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
** Changed in: linux (Ubuntu Disco)
Status: Triaged => Won't Fix
--
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:
[thunderx] Synchronous External Abort: synchronous parity or ECC
Dropping block-proposed-{bionic,eoan} tags as fixes have now landed in
focal.
** Tags removed: block-proposed-bionic block-proposed-eoan
** Changed in: qemu (Ubuntu Bionic)
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member
Public bug reported:
I tested out the new shim-signed (1.41+15+1552672080.a4a1fbe-0ubuntu1)
on arm64 today. Unfortunately, I was unable to boot a kernel. I tried
manually running commands in the GRUB shell to try and get more info,
and here's the error I get:
grub> insmod gzio
grub> linux (hd0,gp
Public bug reported:
I noticed that systemd-machined was failing to start on an arm64 box.
This box had armhf enabled, and turns out systemd had been cross-graded
over to systemd:armhf[*]. It still had systemd-container:arm64
installed, so now I had an arm64 /lib/systemd/systemd-machine, but an
ar
Verified:
ubuntu@dannf-bionic:~$ sudo dpkg -i
sbuild-launchpad-chroot_0.14ubuntu0.18.04.1_all.deb
(Reading database ... 54978 files and directories currently installed.)
Preparing to unpack sbuild-launchpad-chroot_0.14ubuntu0.18.04.1_all.deb ...
Unpacking sbuild-launchpad-chroot (0.14ubuntu0.18.
** Changed in: ibm-java71 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861984
Title:
[Comm] IBM JDK 8.0.6.5 integration into Ubuntu
To manage notificati
Uploaded to xenial-proposed. btw, should we now request copying to
focal?
** Changed in: ibm-java71 (Ubuntu)
Assignee: dann frazier (dannf) => Ubuntu Package Archive Administrators
(ubuntu-archive)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
e/b/x all verified on a dragonboard 410c
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
Both crmsh autopkgtest failures could be explained by a flaky network
connection. The eoan one is certainly that - it's unable to connect to
the archive. The error from the bionic case is masked - but the test is
trying to apt install vim. That could obviously also be an archive
connectivity issue.
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
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
** 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
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
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
** 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
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
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
** 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/
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
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
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
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
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
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
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
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
&
** 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
** 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
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
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
@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
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
** 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
** 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: "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
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
** 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 (
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.
** 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
** 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
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
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
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
@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
** 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
** 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
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
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
** Changed in: kunpeng920/ubuntu-19.10
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.la
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
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/
a258 -e a259
ubuntu@segers:~$
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Eoan)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linu
Public bug reported:
[Impact]
The 5.4 introduced a regression that could potentially lead to a crash during
resume.
[Test Case]
Regression tested only.
[Fix]
547fde8b5a192 scsi: hisi_sas: Return directly if init hardware failed
[Regression Risk]
Code change is restricted to the hisi_sas driver
atus: New => In Progress
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notificatio
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of
** Also 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/1853999
Title:
[sas-1126]scsi: hisi_sas: use wait_for_completion_timeout() w
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (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
** Changed in: linux (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.net/bugs/1855958
Title:
scsi: hisi_sas: Return directly if init hardw
*** This bug is a duplicate of bug 1855059 ***
https://bugs.launchpad.net/bugs/1855059
** This bug has been marked a duplicate of bug 1855059
[Regression] 4.15.0-73.82 Can not boot ThunderX
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: kunpeng920/ubuntu-19.10
Assignee: Ike Panhc (ikepanhc) => 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/1855952
Title:
scsi: hisi_sas: Check sas_port bef
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
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/1854207
** Changed in: kunpeng920/ubuntu-20.04
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920/ubuntu-18.04-hwe
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920
Status: New => In Progress
--
You received this bug notificatio
** Changed in: kunpeng920
Status: New => Triaged
--
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 manage notifications about thi
401 - 500 of 3463 matches
Mail list logo
