@kaihengfeng - It is unclear where the issue lies. If it turns out to be
a driver bug, and we find an SRUable fix, then I'd like to see it SRU'd.
The issue is still reproducible with latest upstream kernels.
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
**
Updating the statuses. This is Fix Released in groovy (patches were
later applied, per Comment #2), and marking Focal as NEW as some patches
are coming into focal/master-next via stable after the initial "Won't
Fix" decision. It needs to be investigated whether that unblocks the
remaining patches.
** Attachment added: "focal-mce-auto-reboot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+attachment/5443914/+files/focal-mce-auto-reboot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "reboot-mce-hang.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+attachment/5443915/+files/reboot-mce-hang.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
[Impact]
When rebooting with the focal kernel, my system always MCEs. Installing an
nvidia driver - or simply blacklisting the nouveau driver - avoids the issue.
Sometimes it hard hangs the system, requiring a manual power cycle:
[ OK ] Reached target Reboot.
[
Public bug reported:
I noticed that the Built-Using control field is no longer being
generated for linux-modules-nvidia- packages... well, except for the aws
ones, which still have it.
For example:
$ apt show linux-modules-nvidia-440-5.3.0-51-generic | grep Built-Using
Built-Using:
them. Issues could
include kernel oopses, corruption, etc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu
ACK, I'll go ahead and close this bug then, but still happy to help if I can :)
I'd suggest adding some debugging command line arguments (debug,
initcall_debug, etc) to see if you can get any more info about where it's
hanging.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
It works fine for me:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.14.211 #3 SMP Wed Dec 9 00:40:44 UTC 2020 x86_64 x86_64 x86_64
GNU/Linux
I kept the default initramfs.conf w/ COMPRESS=lz4. I started with a
defconfig and added what I needed to boot my (EFI-based) VM.
ubuntu@ubuntu:~$ sudo file
Note that we did switch to lz4 compression starting in 19.10. This is
configurable via /etc/initramfs-tools/initramfs.conf, so you could
workaround it by returning to gzip. Why 4.14.y would be a snowflake here
isn't clear.
--
You received this bug notification because you are a member of Kernel
What's the symptom?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1907156
Title:
Unable to run 4.14 stable kernel in 20.04 user space
Status in linux package in Ubuntu:
Incomplete
Verification:
ubuntu@bestovius:~$ lsmod | grep sha
sha2_ce16384 0
sha1_ce16384 0
ubuntu@bestovius:~$ cat /proc/version
Linux version 4.4.0-197-generic (buildd@bos02-arm64-056) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12) ) #229-Ubuntu SMP
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
The sha{1,2}_ce modules no longer load on arm64, preventing the use of the
ha
Reported upstream:
https://www.spinics.net/lists/stable/msg429412.html
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
**
Public bug reported:
[Impact]
The sha{1,2}_ce modules no longer load on arm64, preventing the use of the
hardware accelerated ARMv8 crypto extensions for SHA1, SHA-224/SHA-256.
[Test Case]
sudo modprobe sha1_ce
Currently fails:
[ 33.838295] module sha1_ce: unsupported RELA relocation: 275
= xenial verification -
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-195-generic
root=UUID=6f35ed47-31af-4f66-b33f-5863971f8df0 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags
= bionic verification =
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-125-generic
root=UUID=9e45081a-7e2b-4294-8b2f-4ccb8139ed67 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags
= groovy verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.8.0-30-generic (buildd@lgw01-amd64-009) (gcc (Ubuntu
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #32-Ubuntu
SMP Mon Nov 9 21:03:15 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars | grep FOO
= focal verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.4.0-55-generic (buildd@lcy01-amd64-013) (gcc version 9.3.0
(Ubuntu 9.3.0-17ubuntu1~20.04)) #61-Ubuntu SMP Mon Nov 9 20:49:56 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
xenial verification
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 4.4.0-195.227
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 715 kB
Provides:
bionic verification:
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 4.15.0-125.128
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 730 kB
Depends:
focal verification:
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 5.4.0-55.61
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 618 kB
Depends:
** Description changed:
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
Split out of bug 1894217.
[Test Case]
$ ls /sys/firmware/efi/efivars | grep ^Boot
ls: reading directory '/sys/firmware/efi/efivars': Input/output error
Boot
** Description changed:
+ [Impact]
+ MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
+
Split out of bug 1894217.
- We're seeing a situation where curtin fails when the variable
- BootCurrent references does not exist.
+ [Test Case]
+ $ ls
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Xenial)
St
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Gro
Patch backport to stable:
https://www.spinics.net/lists/stable/msg423555.html
** Changed in: curtin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
With the above patch applied, we can see the culprit directories:
$ sudo find /sys/firmware/efi/vars/ -type d | grep \!
/sys/firmware/efi/vars/Pwr!Perf Profiles-7683c190-9523-4402-81ff-a11e93dc389c
/sys/firmware/efi/vars/Intel(R) VT for Directed I!O
(VT-d)-7683c190-9523-4402-81ff-a11e93dc389c
Ah:
commit 336af6a4686d885a067ecea8c3c3dd129ba4fc75 (refs/bisect/bad)
Author: Michael Schaller
Date: Fri Sep 25 09:45:02 2020 +0200
efivarfs: Replace invalid slashes with exclamation marks in dentries.
Without this patch efivarfs_alloc_dentry creates dentries with slashes in
I tried to prove whether or not this is a firmware issue or, perhaps, a
bug in efibootmgr or curtin's calling of it. I deployed an affected
system w/ MAAS w/ init=/bin/bash on the cmdline, and was surprised to
see that efibootmgr showed the full expected set of Boot variables.
However, if I ssh'd
** Description changed:
linux-modules-nvidia-450-server-generic appears to be uninstallable on
- bionic currently:
+ bionic currently. I hit this on actual hardware, but here's a
+ reproduction in lxd for a clean-room demonstration:
ubuntu@blanka:~$ lxc launch ubuntu:bionic 450srv
Public bug reported:
linux-modules-nvidia-450-server-generic appears to be uninstallable on
bionic currently:
ubuntu@blanka:~$ lxc launch ubuntu:bionic 450srv
Creating 450srv
Error: Failed instance creation: Invalid instance name: Name must not be a
number
ubuntu@blanka:~$ lxc launch
Perhaps we need to enable CONFIG_ARM_MODULE_PLTS ?
https://www.spinics.net/lists/arm-kernel/msg813310.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899519
Title:
booting
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898909
Title:
Installing hwe linux-tools does not provide /usr/bin
Public bug reported:
I have a test script that requires /usr/bin/cpupower. Before calling it,
I 'apt install linux-tools-$(uname -r)' to make sure it is available.
For GA kernels, this works fine as there is a dependency chain on linux-
tools-common which provides them. For HWE (tested on
Confirmed => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazie
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete =>
Public bug reported:
$ apt show linux-tools-common
Description: Linux kernel version specific tools for version 4.15.0
This package provides the architecture independent parts for kernel
version locked tools (such as perf and x86_energy_perf_policy) for
version PGKVER.
^^
Seems
Upstream proposed a fix that works for me:
https://lists.freedesktop.org/archives/nouveau/2020-October/037069.html
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received th
Reported upstream:
http://lkml.iu.edu/hypermail/linux/kernel/2010.0/02256.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
oops in nvkm_udevice_info() [nouveau]
focal didn't have this problem, so I bisected v5.4..v5.8 to discover
when it was introduced and hit:
commit 24d5ff40a732633dceab68c6559ba723784f4a68
Author: Karol Herbst
Date: Tue Apr 28 18:54:02 2020 +0200
drm/nouveau/device: rework mmio mapping code to get rid of second map
Also impacts latest upstream:
[ 213.131657] nouveau :07:00.0: unknown chipset (17a1)
[ 213.138547] nouveau :07:00.0: unknown chipset (17a1)
[ 213.144938] BUG: kernel NULL pointer dereference, address:
[ 213.152704] #PF: supervisor read access in kernel mode
[
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416354/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416358/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416357/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Description changed:
The 5.8.0-20.21 reliably trips an Oops on startup when initializing the
nouveau driver.
+
+ [ 221.032875] nouveau :07:00.0: unknown chipset (17a1)
+ [ 221.039893] nouveau :07:00.0: unknown chipset (17a1)
+ [ 221.046328] BUG:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416350/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898130
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416356/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416351/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416353/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416348/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898130
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416352/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416355/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416347/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416349/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416359/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
The 5.8.0-20.21 reliably trips an Oops on startup when initializing the
nouveau driver.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: groovy
** Attachment added: "dmesg.out"
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu
overrides the GNOME default of auto-suspending, but that override only
takes effect if you have the ubuntu-settings package installed. I tested
this out on a Saber system, and I can confirm that it does seem to only
happen
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862559
Title:
ubuntu 19.10: unresponsive/freezes on ThunderX2 if
@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
*** 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
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 Kernel
Packages, which is subscribed to linux
@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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
@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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877620
Title:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877620
Title:
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 Kernel
Packages, which
** 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)
** 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
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851446
Title:
Backport MPLS
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,
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
= 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
sorry s/Juery/Juerg/!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860013
Title:
[thunderx] Synchronous External Abort: synchronous parity or ECC error
Status in linux package in
@Juery: I have no reason to believe this is related to the boot
regression we fixed (bug 1857074). I haven't re-tested lately, but as of
4.15.0-76 it was still reproducible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
bionic verification:
ubuntu@crash-bionic:~/crash-7.2.8$ sudo sh ./debian/tests/live
Adding linux-image debug symbols.
Executing: /tmp/apt-key-gpghome.vuS9jI2yc6/gpg.1.sh --keyserver
keyserver.ubuntu.com --recv-keys C8CAB6595FDFF622
gpg: key C8CAB6595FDFF622: 5 signatures not checked due to
eoan verification:
ubuntu@crash-eoan:~/crash-7.2.8$ sudo sh ./debian/tests/live
Adding linux-image debug symbols.
Executing: /tmp/apt-key-gpghome.7LWILREpSP/gpg.1.sh --keyserver
keyserver.ubuntu.com --recv-keys C8CAB6595FDFF622
gpg: key C8CAB6595FDFF622: 5 signatures not checked due to missing
I tried installing ubuntu-desktop on a sabre, but I was still unable to
reproduce. That's still my best hypothesis (Comment #4), but I think
we're stuck here w/o more info from Naresh.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
= linux/eoan verification =
I created a multi-zone array on current eoan, then upgraded to the -proposed
kernel:
[4.021562] md/raid0:md0: !!! DEFAULTING TO ALTERNATE LAYOUT !!!
[4.021563] md/raid0: Please set raid0.default_layout to 1 or 2
[4.021564] md/raid0: Read the following page
** Tags removed: verification-done verification-done-bionic
verification-done-disco verification-done-eoan
** Tags added: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-eoan
** Tags removed: block-proposed-bionic block-proposed-disco block-
Do you happen to have a desktop installation? If so, it does appear that GNOME
now defaults to auto-suspending the system after ~20 minutes of inactivity:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #22
I also could not reproduce, even with the same kernel version the
submitter used (5.3.0-26.28). What firmware are you using? My system
(dualla) reports:
BIOS Date: 03/19/2019 14:27:32 Ver: 0ACKL026
Please also attach the apport info requested in Comment #1.
--
You received this bug
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
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
** Changed in: linux (Ubuntu Disco)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860013
Title:
[thunderx] Synchronous External Abort: synchronous
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 Kernel
Packages, which is subscribed to linux in
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
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
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776654
Title:
systemd upstream sysusers tests fails
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)
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
** 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
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 Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
nee: (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 => In Progr
301 - 400 of 1621 matches
Mail list logo
