Hi Mauricio,
So, after my disks checks, I've installed:
linux-image-5.4.0-110-generic
linux-modules-5.4.0-110-generic
linux-modules-extra-5.4.0-110-generic
I restarted a raid check (echo check > /sys/block/md0/md/sync_action) and
copied/moved/removed a 5GB file and I didn't encounter the driver
** No longer affects: linux-raspi (Ubuntu Bionic)
** No longer affects: linux-raspi2 (Ubuntu Focal)
** Also affects: linux-raspi-5.4 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-raspi2 (Ubuntu Bionic)
** Also affects: linux-raspi2 (Ubuntu Bionic)
Importanc
Please ignore the commit ids provided in the last comment.
Below patches/commit ids are sitting in Linux SCSI repo:
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/ (branch
5.19/scsi-staging)
f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0
7dbd0dd8cde3 scsi: mpi3mr: Ad
Public bug reported:
Bluetooth devices do not connect. Or better: they connect, disconnect,
connect, then finally disconnect.
It is the same using graphical tools or cli.
It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35
Hello @metze,
The Impish kernel with the patches for this issue is currently in
-proposed. Could you please test this kernel to check whether it's
fixed? Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
*** This bug is a duplicate of bug 1968875 ***
https://bugs.launchpad.net/bugs/1968875
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1968875, so it is being marked as such. Please look
Can you identify other common factors among the non-working and working distros?
- Kernel version
- BlueZ version
- Intermediate software like gnome-bluetooth
- Bluetooth firmware version reported in the kernel log, currently:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
--
You received this b
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1968875
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1035.38
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-focal' to 'verification-done-focal'. If the
problem still exist
is there a bug reported upstream yet?
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
seems this just needs a config change? from the private bug:
"This is due to the patch "[patch] integrity: Do not load MOK and MOKx when
secure boot be disabled" was added to check if secureboot enabled for trusting
the MOK key,
https://lore.kernel.org/lkml/9b93e099fc6ee2a56d70ed338cd79f2c1ddcff
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 1969432
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Description changed:
+ [Workaround/Fix]
+
+ 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe
+ graphics)' from the boot menu.
+
+ 2. During installation be sure to check the third-party software option
+ in order to get the right Nvidia driver installed.
+
+ [Original
** Changed in: linux-raspi-5.4 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux-raspi-5.4 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-raspi2 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux-raspi2 (Ubuntu Bionic)
Sta
Public bug reported:
apt upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-510 510.60.02-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm zfs zunicode zavl
Public bug reported:
[Impact]
New hardware being enabled needs the firmware for DMC and GuC, freshly
merged to upstream git.
[Fix]
Merge the files from upstream git.
[Test case]
Boot a machine with DG2 using oem-5.17 kernel plus a dkms, check that
both firmware get loaded and i915.ko is used
I'm having the same experience on my X1 Yoga 1st Gen (i7-6600u).
there are a lot of similar reports here
https://askubuntu.com/questions/1404856/not-waking-up-from-suspend-
ubuntu-22-04
I haven't tested with xorg, but with wayland (both gnome and kde) it
goes to sleep an can't resume.
As an asid
** 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/1971493
Title:
Focal update: v5.4.187 upstream stable relea
** 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/1971496
Title:
Focal update: v5.4.188 upstream stable relea
Thanks @mfo! That is correct, the crash was seen there, but they
determined it was generic and are pushing this to all the Linux OSVs.
Also of note, that patch set is a general driver update and not all of those
are relevant to this bug, I've asked them to pinpoint the patches that resolve
this
git log1 v5.14.20..v5.14.21
545728d9e085937 (tag: v5.14.21, stable/linux-5.14.y) Linux 5.14.21
999805aaf925594 Revert "ACPI: scan: Release PM resources blocked by unused
objects"
0750f769b95841b thermal: Fix NULL pointer dereferences in of_thermal_ functions
50812034d105b81 perf/core: Avoid put_pa
** 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/1971497
Title:
Focal update: v5.4.189 upstream stable relea
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I know, same for bug 1965882. But still a regression in 5.14.21.
--
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/1971146
Title:
[radeon] Pictures including wallpaper not showing in kernel
Is there an easy way to diff the configs used between:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.20/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.21/
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Public bug reported:
Closing the notebook results in the system going to sleep/hibernate.
Since upgrading to 22.04, the system is unable to wake up. No buttons pressed
register, even the power button does not work as a wake-up call.
Only way out seems to be a hard reset.
I am not alone with this
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1939052
Title:
No sound on Lenovo laptop models Legion 15IMHG05,
Closing as per comment #6
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1825638
Title:
Lenovo Legion Y530-15ICH does
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1550704
Title:
Type Cover (3) touchpad not working on Surface Pro 3
S
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1971551
Title:
Hibernate wake up does not wor
Video with the flickering, currently testing kernel 5.15.0-27-generic
** Attachment added: "20220504_113918.mp4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+attachment/5586600/+files/20220504_113918.mp4
--
You received this bug notification because you are a member of Kerne
pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 4 18:09:29 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-
more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-27
InstallationDate: Installed on 2022-05-04 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-met
ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-27
InstallationDate: Installed on 2022-05-04 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: linux-meta-oem-5.17
UpgradeStatus: No
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-27
InstallationDate: Installed on 2022-05-04 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType:
-jammy-amd64-20220504-27
InstallationDate: Installed on 2022-05-04 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: linux-meta-oem-5.17
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notificat
also worth mentioning, on the kernels of ubuntu 20.04 i never had this
flickering
--
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/1958191
Title:
Flickering and disforming booting into des
Public bug reported:
After upgrading Lenovo Thinkpad X260 from 21.10 to 22.04, following
error shows at boot:
[4.830657] tpm tpm0: Operation Timed out
[ 11.654699] tpm tpm0: Operation Timed out
[ 11.654718] tpm_crb: probe of MSFT0101:00 failed with error -62
Notable consequence is that t
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1971567
Title:
TPM breaks resume from standby
Tagging as verification-done-impish based on comment #12. Thank you!
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bug
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1968475
Title:
Fix broken HDMI audio on AMD PRO
Same as Bas Janssen here, Dell XPS 13 with i915. No devices attached. It
is a fresh install, not an upgrade.
--
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/1971428
Title:
CPU pipe A FIFO
I can confim the bug is in the latest drm-tip kernel
Regards,
Mick
On 04/05/2022 06:08, Daniel van Vugt wrote:
> Nice work, thanks!
>
> The only remaining thing to do is to try the latest drm-tip kernel:
>
>https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/amd64/
>
> That wil
hello.
In order to operate the Mediatek M80 5G device normally, I installed the
linux-oem-5.17 - 5.17.0-9003.3+exp.11 package attached to the link
below.
- https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel/+packages
However, after installing the kernel, the following
Public bug reported:
SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
version 5.4.0-109-generic", but it works on earlier version of " Linux
version 5.4.0-42-generic"
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug noti
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 1971576
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Thank you. Frankly I cannot continue to provide information on that bug.
In the meantime I have upgraded to 22.04. And this particular issue
vanished for me.
As far as I am concerned the issue does not exist any more. It still
occurs at my computer at work, but there I have the Debian 11, and I
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
This issue seems to appear when we have multiple connection to this
server. It appears randomy and connection drops by losing gateway. When
we are trying to put manually the
For 5.4.0-109 kernel, if "rescan-scsi-bus" after plug in, it can find
disk.
--
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/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asu
5. un-plugin sata disk; restart system
6. restart and boot into 5.4.0-109 kernel
7. login and monitor kernel log like sudo tail -f /var/log/syslog
8. plug in sata disk, there no similar log and no disk was found.
--
You received this bug notification because you are a member of Kernel
Packages,
reproduce method
1. On Ubuntu 20.04, install both 5.4.0-42 and 5.4.0-109 kernel
2. restart and boot into 5.4.0-42 kernel via grub menu
3. login and monitor kernel log like sudo tail -f /var/log/syslog
4. plug in sata disk, the log showed disk was dected like below:
---
May 4 05:5
The resume after suspend works with Ubuntu mainline kernel 5.14.16. So
the issue occurs with 5.15.x kernels.
--
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/1971437
Title:
linux-image-5.1
In fact, the issue occurs with all kernels starting from 5.15.x and
newer versions. 5.16.x, 5.17.x too.
--
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/1971437
Title:
linux-image-5.15.0-2
*** This bug is a duplicate of bug 1966803 ***
https://bugs.launchpad.net/bugs/1966803
Hey Nemir,
That's great news; thanks for testing!
I'll set this bug as a dup of 1966803.
** This bug has been marked a duplicate of bug 1966803
xfs: Fix deadlock between AGI and AGF when target_ip exis
I thought this problem had solved itself somehow since I could resume
from suspend but around 2 weeks ago, the problem resurfaced again.
About your solutions:
Here's the thing, I can't see the login screen post resume. The whole screen is
blank. There's no way to send an input to the computer (e.
Below is full sosreports of our test. Test and log please refer to last
2 boot (42 and 109 kernel)
May 4 05:49:11 rd1 kernel: [0.00] Linux version
5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu
9.3.0-10ubuntu2)) #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 (Ubuntu
5.4
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs
Hi Byron,
Thanks for reporting this bug.
Looking at the attached files, they don't seem to have a kernel stack
trace to provide insight about the crash; let's try to get it.
Do you see kernel messages in your monitor when the issue happens, that
you could take a picture and upload?
That might b
apport information
** Tags added: apport-collected jammy uec-images
** Description changed:
I got this error after a fresh install of Ubuntu 22.4
The server is a Gen8 Microserver. I moved from Fedora 35 to Ubuntu.
Everything was working before the format and reinstall.
- Unfortunately,
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586691/+files/Lspci-vt.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/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586690/+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/1971505
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586693/+files/Lsusb-t.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/1971
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586697/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586692/+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/1971505
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586696/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586694/+files/Lsusb-v.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/1971
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586695/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586699/+files/UdevDb.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/1971505
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586698/+files/ProcModules.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/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586700/+files/WifiSyslog.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/bug
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1971505/+attachment/5586701/+files/acpidump.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/19
Hi Michael,
Thanks for reporting this bug.
We'd need some kernel messages to understand where it's coming from.
It looks like the Gen8 Microserver has iLO / serial console support.
Can you please check whether you can setup a serial console on it?
Then you might need linux kernel option 'consol
All autopkgtests for the newly accepted linux-meta (5.15.0.28.31) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
oss4/4.2-build2010-5ubuntu9 (amd64)
network-manager/1.36.4-2ubuntu1 (ppc64el, arm64, amd64)
Please visit the excuses
Your attachments came through after I sent last comment.
You could get to a shell in order to run the commands?
CurrentDmesg.txt does show an interesting error (but
it starts in the middle of the flood) going to ext4/
scsi/ata/intel DMA, which is the DMAR handler/thing.
Having messages from befo
Public bug reported:
Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members
before initialization") attempted to fix a race condition that lead to a
NULL pointer, but in the process caused a regression for _AEI/_EVT
declared GPIOs.
This manifests in messages showing deferred probing
This bug is awaiting verification that the linux/5.15.0-29.30 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 exists, change t
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 1971597
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1971597
Title:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to
Commit 06fb4ecfeac7 ("gpio: Request interrupts after IRQ is
initialized") in v5.18-rc4 fixes this issue and has been CC stable to
v5.17.5, v5.15.37.
Affected kernels are v5.17.3, v5.16.20, v5.15.35, or:
* Ubuntu-unstable-5.17.0-8.8
* Ubuntu-hwe-5.17-5.17.0-8.8_22.04.2
* Ubuntu-oem-5.17-5.17.0-1004
It happens also on my laptop:
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Also note that the bug tags says wayland, but I am running Ubuntu Mate
under Xorg (no Wayland).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: amd oem-priority originate-from-1971572
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
S
Yes I have the same CPU as mentioned earlier, and I'm also using X as it
is default with Kubuntu 22.04.
--
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/1970426
Title:
[i915] screen sudden
Public bug reported:
E: linux-image-5.15.0-27-generic: installed linux-
image-5.15.0-27-generic package post-removal script subprocess returned
error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-29-generic 5.15.0-29.30
ProcVersionSignature: Ubuntu 5.1
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1971598
Title:
package linux-image-5.15.0-29-
Marking verification done for the master kernel. The circumstance that
triggers the bug that this patch fixes requires an Azure CVM instance
with swiotlb=force.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are
pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 4 18:22:39 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-202205
Verified that inside-secure firmware is provided by linux-firmware
20220329.git681281e4-0ubuntu3.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/
** Changed in: linux-azure (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1970468
Title:
linux-azure: Patch Set for ARM64
** Changed in: linux-azure (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux-azure (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-azure in Ub
You have been subscribed to a public bug:
After IBM z16 has been announced, we need to add the new s390 platform
in glibc.
S390: Add new s390 platform z16.
https://sourceware.org/git/?p=glibc.git;a=commit;h=2376944b9e5c0364b9fb473e4d8dabca31b57167
Backport to glibc 2.35 release branch:
https://s
You have been subscribed to a public bug:
I had a 20.04 system I "upgraded" to 22.04.
> do-release-upgrade -d
The upgrade went well except after reboot the system never came back up.
Searching the web I found quite a few others having the same/similar
problem.
Troubleshooting
I booted a LiveC
1 - 100 of 168 matches
Mail list logo
