Actually the second is in 6.11 already.
> git describe --contains bf5641eccf71bcd13a849930e190563c3a19815d
v6.11-rc2~2^2~4
This is just an ask for 6.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
I see the same message on 0x60. Please pull in the this commit too.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bf5641eccf71bcd13a849930e190563c3a19815d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
> I don't know why i use dkms
When you installed the packaged version of ROCm you can use arguments to
decide whether or not to build the DKMS package. I don't expect you
really need it with this kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I am tending to agree with Juerg, this is not Ubuntu's bug. They picked
up a stable update that fixed a problem, but it just so happens this
DKMS doesn't compile anymore.
I think the DKMS package will need to be re-spun due to this change.
I suggest reporting it here: https://gitlab.freedesktop.o
This definitely isn't an Ubuntu kernel bug, I will reject it as such.
You can file an issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues if you have problems
stemming from that script.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
> That's an unsupported DKMS, not a kernel problem. Is there any reason
why you don't use the kernel's amdgpu driver?
The DKMS driver takes an upstream snapshot of amdgpu for use with older
kernel versions. As I notice that in the above error log the DKMS
driver is from "6.8.5-2009582.24.04" you
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Ubuntu
Fwupd only reports the security of the firmware that it can measure.
It's not a fwupd bug if there is a problem.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
This appears to be a different problem even if it leads to same symptom.
Please open a separate issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: S
> But building a new kernel and switching to it without deeper
experience and a fallback would be too hard for me.
No need to build a new kernel. There are binaries in the link that was
posted above. You can grab some of those to try. Just note that you
need to turn off secure boot if you have i
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to exit 'fwupd' install excution via
That regression isn't real. Looks like an infra problem.
0s autopkgtest [15:16:00]: starting date and time: 2024-08-23 15:16:00+
0s autopkgtest [15:16:00]: git checkout: fd3bed09 nova: allow more retries
for quota issues
0s autopkgtest [15:16:00]: host
juju-7f2275-prod-proposed-migratio
Verified that ESP is still being identified properly on my test systems.
❯ sudo fwupdtool esp-list
Loading… [ ]15:24:50.821
FuHistoryLoading…
[** ]
Selected volume: /org/freedesk
KC - Yes, I've already uploaded it to unapproved queue. It's waiting
for SRU team member review (see comment #8).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hard
Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs? There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.
Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loa
As this is really a development effort not a bug I've also filed it at
https://github.com/canonical/ubuntu-desktop-provision/issues/800.
** Bug watch added: github.com/canonical/ubuntu-desktop-provision/issues #800
https://github.com/canonical/ubuntu-desktop-provision/issues/800
--
You receiv
** Description changed:
- Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
+ [Impact]
+ Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
* https://github.com/fwupd/fwupd/issues/7593
And following
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hardware system in mediatek_scalar
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to exit 'fwupd' instal
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077553
Title:
ESP detection failures
To manage notifications about
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065874
Title:
Can't update firmware on TPM-backed FDE systems
To manage notificatio
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072612
Title:
Lenovo touchpad intermittently stops working with i2c_designware
err
FWIW I don't feel this is likely a kernel regression but rather a
platform firmware problem.
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=219101
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
** Also affects: fwupd via
https://github.com/fwupd/fwupd/issues/7520
Importance: Unknown
Status: Unknown
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Orac
fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hardware system in mediatek_scalar p
This is fixed in both main and 1_9_X branches upstream and will be part
of the fwupd 1.9.24 release. When that's released this will be updated
in Ubuntu.
** Changed in: fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Changed in: fwupd (Ubuntu
user manually names their ESP using anything in the heuristics list
it will no longer be identified properly.
** Affects: fwupd
Importance: Unknown
Status: Unknown
** Affects: fwupd (Ubuntu)
Importance: High
Assignee: Mario Limonciello (superm1)
Status: Triaged
** Af
** Also affects: ubuntu-desktop-provision
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064023
Title:
Installer should detect small ESP in a dual boot
T
** Changed in: fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to e
fwupd has an exception in SRU process and is supposed to be updated to
upstream point releases for SRU.
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate
https://wiki.ubuntu.com/firmware-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There are going to be a few things Dell needs too on 1.9.24. I suggest
once it's released an update happens for both reasons.
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Oracular)
Importance: Undecided
Status: New
**
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspend hangs syst
I feel it should also backport to jammy since 6.8 kernel will be in
jammy too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
sddm/simpledrm race conditions leads to frequent black dis
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071889
Title:
a critical typo in the code managing the ASPM settings for PCI
Express devices
To manage notificatio
I do have a theory.
Maybe it's bug 2071889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system
To manage notifications about this bug
*** This bug is a duplicate of bug 2071889 ***
https://bugs.launchpad.net/bugs/2071889
** This bug has been marked a duplicate of bug 2071889
a critical typo in the code managing the ASPM settings for PCI Express
devices
--
You received this bug notification because you are a member of
Matthew, Chris,
Maybe one of you guys can add a kernel with that revert for people to
use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longer working after upgrade f
It sure sounds like there are some other patches in Ubuntu's kernel
causing problems.
Could you check mainline v6.9 and v6.9.7? I know they backported some
ASPM patches. Maybe those cause issues for some of these machines?
If those are fine then what I suggest doing is bisecting Ubuntu's kernel
If I was to guess it's one of these patches that causes it.
965f593401bd PCI/ASPM: Update save_state when configuration changes
c12dda119c7a PCI/ASPM: Disable L1 before configuring L1 Substates
7fe5ec02955e PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state()
014516361233 PCI/ASPM: Save
Canonical 6.5 series seems to have picked up at least one bad commit
that was reverted upstream.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.la
I don't know if it's the same issue; but there is another relatively
similar issue that occurred very recently: bug #2070096
As I mentioned there, this commit is at least PART of the problem:
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
And that commit did go back to stable:
https://git.kernel.org/stable/c/6266b3a312b7f69c883c2d7c82d85772464421d2
So I guess Canonical team missed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20700
Here's at least part of the problem.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.launchpad.net/bugs/2059068
commit 3a0fa3bc245ef92838a82
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066275
Title:
[SRU] Fix bla
BTW - Several commits are in your list twice as different IDs. You
should double check that nothing landed twice...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longe
Of that list b47f813e0303 does look suspicious to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
To manage no
We never saw a report upstream on any of the stable kernels like this.
To me; I suspect this is a case that a commit back ported to Canonical
6.5 without a matching dependency, but a bisect will be really helpful
to understand it.
--
You received this bug notification because you are a member of
I also think it should target Jammy because eventually the 6.8 kernels
will backport there and introduce this bug to even more people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066275
Title:
[S
I do think it makes sense to pull in the change you're doing for now,
but I do want to mention this is tech debt to pick up that approach to
avoid this issue as that isn't merged and there isn't really line of
sight to a proper fix:
https://github.com/sddm/sddm/pull/1924
--
You received this bug
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
** This bug has been marked a duplicate of bug 2070020
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression
** Tags removed: regression
** Tags added: regression-update
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
** This bug has been marked a duplicate of bug 2070020
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
--
You received this bug notification because you are a member of Ubuntu
Bugs
I read on that link that mainline 6.9.3 is fine. So there is some bad
backport.
Can you handle building a kernel? If so; it would probably be best to
find the cause by bisecting [1].
You would clone the Ubuntu kernel tree [2] that has these tags and use them for
your start and end.
Ubuntu-6.5.
That's a BIOS bug with VCN not a GPU F/W bug. We can reproduce it on
the same BIOS as you, and updating to a newer BIOS it goes away.
You can workaround it by masking the VCN IP block like this:
amdgpu.ip_block_mask=0xfcff
--
You received this bug notification because you are a member of U
Please try 6.8.5 mainline and 6.8.12 mainline. There are binary builds
created here:
https://kernel.ubuntu.com/mainline/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt &
#46:
That's this bug:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2063143
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after ins
#19/#20.
Your issue is not that one that you linked. 6.8.0-38.38 picks up the
fix for #2064595. So if that helps, your issue is a duplicate of
#2064595. If that doesn't help, you have a different issue. You should
open up your own issue for triage in this case.
--
You received this bug notif
The GUI button triggers the lock action and dpms. Grab a newer kernel or
backport that patch linked in the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067945
Title:
Restart after resume from
I can explain your result. The issue is specifically a race condition
with the lock screen triggering after the suspend sequence starts. The
driver change that helps it flushes content during the suspend sequence
to ensure engines are not running when suspend starts.
By using pm utils you don't t
** Summary changed:
- S2idle regression
+ AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspend
> Command "sudo pm-suspend" does not work properly on my notebook, just
blank screen but without going to sleep mode - hard restart needed.
FYI pm-utils is orphaned and outdated. You should be using `systemctl
suspend` to suspend from CLI.
> Yes, CPU on my ASUS notebook is AMD Ryzen 7 6800H, so
If this is AMD Rembrandt, it's probably this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067945
Title:
Restart after res
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 2069357 ***
https://bugs.launchpad.net/bugs/2069357
** This bug has been marked a duplicate of bug 2069357
Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
Thunderbolt 3 Gen 2 USB-C dock
--
You received this bug notification because you
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's
the fix (IIRC).
https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/
Try applying that to your 5.15 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's
the fix (IIRC).
https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/
Try applying that to your 5.15 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Should be a duplicate of that. It was fixed in upstream 6.8.5, Ubuntu's
6.8.0-35 is still on 6.8.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067997
Title:
Lenovo T14 Gen3 AMD laptop freezes s
I posted some idea over to the systemd bug on a way to approach this
from systemd instead of each greeter.
https://github.com/systemd/systemd/issues/32509#issuecomment-2134152084
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
The discussion upstream on dri-devel has mostly settled upon userspace greeters
need to support hot-unplug.
https://lore.kernel.org/dri-devel/ZkyZCmMU86nUV4TO@phenom.ffwll.local/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Can someone with an affected system raise a bug report upstream to lightdm?
There was a very similar bug that occurred in GDM last year:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2909
And there is a similar report opened with SDDM:
https://github.com/sddm/sddm/issues/1917
** Summary changed:
** Summary changed:
- Frequent boot to black display
+ sddm/lightdm race conditions leads to frequent black display on bootup
** Summary changed:
- sddm/lightdm race conditions leads to frequent black display on bootup
+ sddm/simpledrm race conditions leads to frequent black display on bootup
-
** Package changed: linux (Ubuntu) => lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143
** This bug has been marked a duplicate of bug 2063143
Frequent boot to black display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This should be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595
The fix is
https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Do you have secure boot enabled? if so, turn it off and hopefully the
kernel you built should be bootadble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838
Title:
System crash on resume from
As the firmware is on it's own stable and by the time this hardware is
in market that kernel fix should be picked up adding verification done
tag.
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Internal team tested this SRU against current generic and OEM kernel and
it fails on both because they're missing the fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066233.
After adding in that fix it works.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Status: New => Invalid
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065839
Title:
UBSAN: array-index-out-of-bounds
To ma
Save the below as a patch file and then apply using "patch -p1 < FILE".
Build your kernel and see if it has helped.
diff --git a/drivers/acpi/acpica/exregion.c b/drivers/acpi/acpica/exregion.c
index 8907b8bf4267..ca060ec6936e 100644
--- a/drivers/acpi/acpica/exregion.c
+++ b/drivers/acpi/acpica/ex
Yes since you didn't clone using git you can't use git revert.
Once you can successfully build and test that kernel I'll post you a
revert patch' with explanation how to use it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Yeah I know they're different symptoms but the reason for that revert might
have a similar root cause.
I'm saying this because I've got a different system that fails to boot up that
reverting that helps.
In terms of specific instructions, I'd start with this:
https://itsfoss.com/compile-linux-k
As a random guess; could this be the same as
https://bugzilla.kernel.org/show_bug.cgi?id=218849?
Try reverting d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs.
Your kernel is fine."")
** Bug watch added: Linux Kernel Bug Tracker #218849
https://bugzilla.kernel.org/show_bug.cgi?id=21
Fixed upstream.
https://github.com/fwupd/fwupd/pull/7264
** Changed in: fwupd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065948
Title:
fwupdmgr enab
This is the original bug for deb fwupd:
https://github.com/canonical/ubuntu-desktop-installer/issues/2371
This is the original bug for snap fwupd:
https://github.com/fwupd/fwupd/issues/6264
The problem is that fwupd (both deb and snap) don't understand the
layout that TPM FDE uses.
As mentioned
It's saying the same thing the GUI does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616
Title:
Settings Power says high hardware temperature
To manage notifications about this bug go to:
htt
How about the command line tool (powerprofilesctl)? Can you switch
using that? If it really is a pure GCC bug then you can file it here:
https://launchpad.net/ubuntu/+source/gnome-control-center for Ubuntu and
here: https://gitlab.gnome.org/GNOME/gnome-control-center for upstream.
--
You receiv
You can file it here:
https://bugzilla.kernel.org/
Mention your reproduction using a mainline kernel and add your logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616
Title:
Settings Power
This sure sounds like an intel-pstate bug. If you can reproduce it with
the latest mainline kernel you should file a bug with the intel-pstate
maintainers.
You can find some kernel binaries for mainline kernel here:
https://kernel.ubuntu.com/mainline/
--
You received this bug notification becau
This is certainly a false negative. This firmware only affects DCN 3.5
which isn't available for arm64 or armhf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002
Title:
Add support for DCN 3.5
I just tested on a Phoenix based laptop and tested video playback on
OEM-6.5 (1022) with VP9 content in mpv and things look good to me.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143
** This bug has been marked a duplicate of bug 2063143
Frequent boot to black display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143
** This bug is no longer a duplicate of bug 2064815
Always black screen on first reboot after fresh install 24.04, Intel and AMD
GPU
** This bug has been marked a duplicate of bug 2063143
Frequent boo
The issue here is the same one that happened in gdm last year where the
startup would race with the load of DRM graphics drivers.
GDM fixed it by essentially running the equivalent of 'udevadm settle'.
The same kind of fix needs to be ported to sddm or systemd needs to be
modified to not emit CanG
1 - 100 of 6814 matches
Mail list logo