The log in comment #7 seems to show a controlled shutdown, no "hard reboot".
But gnome-shell does seem to have crashed with signal 11 again so maybe that's
the main issue. Please follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received
** Description changed:
[ Impact ]
When running fio on a NVME on an AWS test instance with 5.19 kernel, IOs
get stuck and fio never ends
fio command:
sudo fio --name=read_iops_test --filename=/dev/nvme1n1 --filesize=50G
--time_based --ramp_time=2s --runtime=1m
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/444376
--
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/1836694
Title:
memcg_test_3
I don't understand how is it possible that this bug went out to users?
The build at
https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.33-0ubuntu2 passed
for armhf and MTR/CI did not fail. Why is it failing for users then?
--
You received this bug notification because you are a member of Kernel
I'm seeing this on a brand new Dell Precision 5570 running Ubuntu 22.04
with X11 (not Wayland):
> ucsi_acpi USBC000:00: failed to re-enable notifications (-110)
See details of my attempted fixes and settings here:
https://askubuntu.com/a/1471585/327339
--
You received this bug notification
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2015972
Title:
Dell: Enable speaker mute hotkey
All autopkgtests for the newly accepted linux-meta-raspi (5.19.0.1020.19) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.8-1~ubuntu22.10.0 (arm64, armhf)
lxc/unknown (arm64)
With this fix, does kdump/kexec work with
CONFIG_SECURITY_LOCKDOWN_LSM=y?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2008523
Title:
Make kexec work by default on secureboot
I added the noload mount option and now the mount succeeds with no
error. Not sure if the described issue is expected behaviour (with the
noload/norecovery mount option expected to be used) or if it is still an
issue (I lean towards the latter).
--
You received this bug notification because you
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 directly
** Changed in: linux (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/2020390
Title:
Focal update: v5.4.236 upstream stable
** Changed in: linux (Ubuntu Kinetic)
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/2020599
Title:
Kinetic update: upstream stable patchset
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/2013390
Title:
CPU Lockup related to xhci/DMA
Status in linux-signed-hwe-5.13 package in Ubuntu:
** Changed in: linux (Ubuntu Jammy)
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/2023328
Title:
Jammy update: v5.15.108 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2020387
Title:
Jammy update: v5.15.100 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2020391
Title:
Jammy update: v5.15.101 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2020393
Title:
Jammy update: v5.15.102 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2023224
Title:
Jammy update: v5.15.103 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2023225
Title:
Jammy update: v5.15.104 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2023230
Title:
Jammy update: v5.15.105 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2023233
Title:
Jammy update: v5.15.106 upstream stable
** Changed in: linux (Ubuntu Jammy)
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/2023320
Title:
Jammy update: v5.15.107 upstream stable
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 directly
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.19
(5.19.0.1027.28~22.04.13) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64)
Please visit the excuses page
All autopkgtests for the newly accepted linux-meta-hwe-5.4
(5.4.0.152.169~18.04.123) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/1.1.0-4 (ppc64el, s390x)
asic0x/1.0.1-1 (s390x)
kpatch/0.5.0-0ubuntu1.1 (amd64)
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
The plan is to upstream this patch once the XDP framework has matured,
and once XDP meta data is supported.
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => Triaged
** Changed in:
Public bug reported:
This is a public version of https://bugs.launchpad.net/bugs/2021543
This is to add another patch to encounter the reverting patches effect
in this bug list : https://bugs.launchpad.net/ubuntu-kernel-
tests/+bug/2008085
Hi,
I would like to add one patch to correct the
All autopkgtests for the newly accepted linux-meta-gkeop (5.15.0.1022.21) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.9 (amd64)
Please visit the excuses page listed below and investigate the failures,
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/2017801
Title:
Azure: keys: Do not cache key in
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 directly
Here's the final patch from
https://bugzilla.kernel.org/show_bug.cgi?id=217242. I've applied, built
and tested it on the master-next branch of the Ubuntu Jammy repository
and it fixes this bug.
** Patch added:
"0001-xhci-Fix-incorrect-tracking-of-free-space-on-transfe.patch"
Here's the output without drm.debug=0xe. I was able to repro by putting
the GPU under stress with a bunch of WebGL aquarium windows using the
Chromium hwaccel beta snap. Reproduced using the HDMI unplug method.
Would you like me to re-do all the logs this way or just this one?
** Attachment
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2017600
Title:
Move CONFIG_NF_CONNTRACK to
** Description changed:
GCP is asking for a backport of the patch "iommu/amd: Add
- map/unmap_pages() iommu_domain_ops callback support" to the 5.19
- (kinetic) gcp kernel
+ map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2
+ to the 5.19 (kinetic) gcp kernel
+
+ The
Public bug reported:
GCP is asking for a backport of the patch "iommu/amd: Add
map/unmap_pages() iommu_domain_ops callback support" to the 5.19
(kinetic) gcp kernel
The following two patches are pre-requisites:
6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement
map_pages
on ubuntu 20.04 (focal) with BCM43142 wifi
After updating the system, specifically the kernel from version 5.15.0-73 to
5.15.0-74, the wifi stopped functioning correctly. The network is detected, but
it cannot connect. When loading the previous kernel 5.15.0-73, everything works
as before.
ps
Public bug reported:
SRU Justification
[Impact]
MSFT has requested the inclusion of commit
e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64: efi: Recover from
synchronous exceptions occurring in firmware'). It looks generic enough
to apply to the master kernel.
Unlike x86, which has machinery
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in linux-allwinner package in Ubuntu:
Fix Released
Status in
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 2019203
and then change the status of the bug to 'Confirmed'.
If, due to the
Marking this as affecting the kernel, with glibc as Invalid, as it
doesn't seem like something we can do much about on our end.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu Focal)
Status: New => Invalid
** Changed in: glibc
separately it was discussed that our nezha/licheerv do not have any sort
of meta or config package installed (like we have on raspi, or
concept-x13s images).
and that some may not use or have installed u-boot-nezha, because they
have a custom u-boot. Meaning it is not safe to introduce a
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678646/+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
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678644/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678645/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678643/+files/ProcEnviron.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678642/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This affects kernel >= v5.19.
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678648/+files/acpidump.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/2023307/+attachment/5678647/+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: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678641/+files/PaInfo.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-v.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678640/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678639/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678638/+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/2023307
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678637/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678636/+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/2023307
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678635/+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
** Tags added: apport-collected jammy
** Description changed:
[Summary]
1. System hang on starting checkbox test.
2. Hang on collecting device information during start Auto and Stress test.
3. This issue exist on GPU with W7500 & W7600.
[Steps to reproduce]
1.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2023307/+attachment/5678634/+files/CRDA.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/2023307
Test with linux-nvidia-5.19/5.19.0-1014.14 are ok.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2016269
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 2023307
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Summary]
1. System hang on starting checkbox test.
2. Hang on collecting device information during start Auto and Stress test.
3. This issue exist on GPU with W7500 & W7600.
[Steps to reproduce]
1. Boot into OS
2. Start Auto test or Stress test(checkbox-cli run
All autopkgtests for the newly accepted linux-meta (5.19.0.45.41) for kinetic
have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.8-1~ubuntu22.10.0 (amd64, arm64, armhf, ppc64el,
s390x)
Please visit the excuses page listed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-riscv (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: u-boot-nezha (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
Dear Dimitri,
it is unclear to me why U-Boot should have any influence on the
(non-)inclusion of a driver in the initramfs. Could you, please, add the
missing information.
There is no guarantee that any update of U-Boot runs after the kernel
change. A user can choose only to update the kernel.
My understanding is that nothing needs to be done for systemd. Please
re-open if I am mistaken.
** Changed in: systemd (Ubuntu Lunar)
Status: Confirmed => Invalid
--
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: systemd (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Patch added: "linux-meta-riscv.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1975592/+attachment/5678616/+files/linux-meta-riscv.patch
** Description changed:
[Impact]
integrate linux-allwinner patches into linux-riscv kernel
[Test]
* Newly built images
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in linux-allwinner package in Ubuntu:
Fix Released
Status in linux-riscv package in
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in linux-allwinner package in Ubuntu:
Fix Released
Status in linux-riscv package in
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in linux-allwinner package in Ubuntu:
Fix Released
Status in linux-riscv package in
** Tags removed: verification-done-jammy
** Patch added: "u-boot-nezha.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1975592/+attachment/5678611/+files/u-boot-nezha.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: linux-allwinner (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-allwinner (Ubuntu)
Status: New => Fix Released
** Changed in: linux-riscv (Ubuntu)
Status: Fix Committed => New
** Description changed:
[Impact]
- Enable the Allwinner D1
** Merge proposal linked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/444376
--
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/1836694
Title:
memcg_test_3
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.19
(5.19.0.1026.27~22.04.12) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64)
Please visit the excuses page
** Merge proposal linked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812194
Title:
rtnetlink.sh in
** Merge proposal linked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1932549
Title:
seltests/net:
Hello Olga, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.2 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Olga, or anyone else affected,
Accepted linux-firmware into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220923.gitf09bebf3-0ubuntu1.7 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Merge proposal linked:
https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/444370
--
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/1977827
Title:
ftrace in
Hello Olga, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.14 in a few hours, and then in
the -proposed repository.
Please help us by testing
I have hit this bug in the ADT testing part of the linux-aws 5.19.0-1027.28
release:
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/s/systemd/20230525_124201_d6c4e@/log.gz
This bug was fixed in the package linux-gke - 5.15.0-1035.40
---
linux-gke (5.15.0-1035.40) jammy; urgency=medium
* jammy/linux-gke: 5.15.0-1035.40 -proposed tracker (LP: #2022105)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Severe NFS
This bug was fixed in the package linux-gke - 5.4.0-1101.108
---
linux-gke (5.4.0-1101.108) focal; urgency=medium
* focal/linux-gke: 5.4.0-1101.108 -proposed tracker (LP: #2022106)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Severe NFS
1 - 100 of 106 matches
Mail list logo
