Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
this is done in eoan I believe, but I haven't rebuild my image of eoan
yet; nor started daily focal aarch64 laptops.
--
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/1850731
Title:
Make
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in
I have simmilar issue, but linked to nautilus. Cannot find what caused
it, might be user swithcing also.:
org.gnome.Nautilus[10750]: [7f6e9001c640] vdpau_chroma filter error:
video mixer attributes failure: An invalid handle value was provided.
--
You received this bug notification because
If it's any bit of helpful information, I occasionally have this issue
(on 18.04) and it is fixed by a proper shutdown and boot. It seems to
happen for me when one of the servers that I sshfs to crashes/becomes
unavailable (or something else server side) and the issue persists past
the time in
The concern I have is for other file systems that also don't populate
the UUID - this seems to be a general problem for overlayfs. Perhaps a
UUID can be autogenerated based on the superblock rather than file
system specific UUID magic if the UUID is zero.
--
You received this bug notification
Adding a uuid into the superblock on squashfs seems to resolve the
issue. Since squashfs does not have UUID support, my hack below
generates one based on some squashfs superblock metadata that provides a
good enough UUID for our purposes.
diff --git a/fs/squashfs/super.c b/fs/squashfs/super.c
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
Public bug reported:
[Impact]
"debian.gcp/configs/annotations" is used to ensure the basic config
options the custom kernel are kept unchanged. Unfortunately there's a
typo in this file (ENFORCE instead of ENFORCED) which are making this
check to be ignored.
[Test Case]
Changing one of the
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
A couple of comments on the suggested path:
> Imho the sequency of commands should be:
> * take flock on the device, to neutralise udev
+1 on this approach. Do you know if the flock will block
systemd's inotify write watch on the block device which triggers
udevd? This is the typical race we
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
@ Cloud init team, do we want to try changing cloud-utils to use a lock?
And like have a canary "only use locked codepath on this region" such
that we can assert through testing that this no longer happens with new
code, but does with old code.
--
You received this bug notification because you
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1849027
Title:
xenial/linux-azure:
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848989
Title:
disco/linux-azure:
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848987
Title:
bionic/linux-azure:
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1849026
Title:
trusty/linux-azure:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Reported upstream
https://bugs.freedesktop.org/show_bug.cgi?id=112221
** Bug watch added: freedesktop.org Bugzilla #112221
https://bugs.freedesktop.org/show_bug.cgi?id=112221
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Does someone know when the fix will be ported to the Ubuntu arm64 image?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1848790
Title:
USB not working under arm64 on Pi4
Status
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- linux-oem: -proposed tracker
+ bionic/linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Comparing the previous debug with 2 squashfs overlayfs lowers with the
*same* data on ext4 as the 2 overlayfs lowers we have:
[ 56.257691] repro-nosquashf (1038): drop_caches: 3
[ 56.265075] ovl_get_fh: 112 dentry: etc/.pwd.lock name:
trusted.overlay.origin
[ 56.265077] ovl_get_fh: 115:
Strange. I now tried different Kernels and I just can't get those keys to
function.
They just don't create the corresponding ACPI Events...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You
I ordered a brand new, "premium" Roswell HDMI cable from Newegg and the
problem occurs with that cable as well.
Now that the problem has occurred with three different cables, two of
them new, with no adapters in the middle, I hope we can agree that it is
unlikely that this is a cable issue.
--
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
**
The problem is rather the opposite; the aufs in the kernel is newer than
the synced aufs-tools. And I just recently found out that aufs for 5.x
kernels is hosted in a different git repository, which explains why we
haven't been seeing any tags for 5.x kernels (and thus the version is
still
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug:
Public bug reported:
[Impact]
Intel GLK systems may overheat and trigger a shutdown when doing CPU stress
test. It's because the CPU thermal zone is missing.
[Fix]
Add missing ID to let int340x device work.
[Test]
With the patch, the thermal zone "TCPU" is corretly created. In conjunction
** Tags added: oem-priority originate-from-1850248 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1851506
Title:
Add GeminiLake support on Intel int340x thermal device
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1851506
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug affects me. Severely. It's more than once per day.
shakespeare@RYZEN:~$ uname -r
5.0.0-33-generic
--
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/1776887
Title:
Critical
** Attachment added: "Output of `journalctl -b -1 -k` after successful
suspend/resume"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+attachment/5303250/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
In case it could help, here's the output of the same command after a
successful suspend/resume.
--
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/1846214
Title:
Freezes instead of
Commit c616cbee97ae fixes ffe81d45322c ("blk-mq: fix corruption with
direct issue") that is not present. Are you sure c616cbee97ae is really
need in xenial:linux-azure?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
Fair enough. Thanks for the detailed explanation!
--
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/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
the included snapcraft.yaml means i need to have the whole tree locally
on disk, as someone who maintains a ton of community images for
UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk
is only cluttered during build. along with that i am trying to build the
eoan tree for the
This failure still can be found on B-hwe 5.0 PowerPC:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851488
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1843327
Title:
What's wrong with using the provided/included snapcraft.yaml?
So can this case be closed?
--
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/1851233
Title:
building a snap from the eoan
https://lists.ubuntu.com/archives/kernel-team/2019-November/105243.html
** Description changed:
== Justification ==
- In the ubuntu_kernel_selftests, the skipped test will uses return code 4
(KSFT_SKIP).
+ In the ubuntu_kernel_selftests, the skipped test will uses return code 4
+ (KSFT_SKIP).
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1851486
and then change the status of the bug to 'Confirmed'.
If, due to the
Xenial will require more work, I will split the test report here (see
bug 1851486 for X)
** Summary changed:
- Handle the skip return code in kernel_selftests
+ Handle the skip return code in kernel_selftests on Bionic
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
**
Public bug reported:
Like bug 1812352
In the ubuntu_kernel_selftests, the skipped test will uses return code 4
(KSFT_SKIP).
However the code to handle this non-zero return code was not implemented
in the kselftest framework. And this will generate some false-positives
results as those skipped
well, as a user/customer building my own kernel i'd kind of expect the
defconfig for a flavour to not be a debug config.
but indeed you are correct, i should have taken a look at the included
snapcraft.yaml which, despite being for the wrong flavour (generic/pc-
kernel), indeed contains
Test result for B-4.15 after this patch set.
** Attachment added: "B-client.DEBUG-patched"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812352/+attachment/5303236/+files/B-client.DEBUG-patched
** Description changed:
== Justification ==
In the ubuntu_kernel_selftests, the
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Test result for B-4.15 before this patch set.
** Description changed:
+ == Justification ==
+ In the ubuntu_kernel_selftests, the skipped test will uses return code 4
(KSFT_SKIP).
+
+ However the code to handle this non-zero return code was not implemented
+ in the kselftest framework. And
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
kern.log when the bug triggers
** Attachment added: "kern.log when bug triggers"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851470/+attachment/5303216/+files/kern.log-cephfs-5.0.0-32.bug
--
You received this bug notification because you are a member of Kernel
Packages, which is
The machine is hanging when the bug has been triggered, so I cannot use
apport.
** 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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
The kernel has built successfully, which was the point of the fix, so
marking it verified.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
DEBUG_INFO=y is perfectly fine and required. We build all the blobs with
debug info and then strip them for the 'regular' kernel wo/ debug
symbols.
Potentially relevant: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1851469
DEBUG_INFO *needs* to be overridden in any snapcraft.yaml
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1851470
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
As reported on the ceph-users mailing list, the latest HWE kernel for
ubuntu 18.04 (and the current kernel for disco 19.04) has a problem with
cephfs mounts when you write to it. (kernel version 5.0.0-32)
We are using cephfs to write backups to with amanda (virtual tapes)
** Description changed:
[Impact]
The current snapcraft.yaml file on the raspi2 branch is the one from the
main/master kernel and not the raspi2 version.
[Test Case]
Compare snapcraft.yaml from the affected series with the version from
bionic:linux-raspi2.
+ Try to snap the
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1849011
Title:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Also affects: linux-raspi2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug
101 - 167 of 167 matches
Mail list logo
