** Description changed:
[Impact]
We need to backport dynamic boost control into OEM-6.5 kernel. This
request is to backport the ccp changes.
Here are the commits necessary to backport to OEM-6.5 kernel from kernel
6.6:
b58276372182 crypto: ccp - Rename macro for security attri
Try amdgpu.mcbp=0 on your kernel command line.
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in linux package in Ubuntu
I don't think we should close it, if you reproduce a hang in Ubuntu it should
be fixed in Ubuntu.
The patch should come in mesa. I already know what patch should fix it in mesa
(it's mentioned in https://gitlab.freedesktop.org/drm/amd/-/issues/2971)
If I build you a PPA to test, can you see if
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
**
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrad
** Bug watch added: Linux Kernel Bug Tracker #217993
https://bugzilla.kernel.org/show_bug.cgi?id=217993
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=217993
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Summary changed:
- Mantic reboot loop before splash screen is displayed
+ VT6307 IEEE1394 card causes reboot loop
--
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/2043905
Title:
VT6307
Can you please try to reproduce using a mainline upstream build?
https://kernel.ubuntu.com/mainline/v6.7-rc2/
If you can reproduce please share a new kernel log from a boot it
occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
--
You received this
Just a little extra context for this.
Some systems this manifests as described because they don't use _BTP for
notifying when battery has crossed a critical threshold but instead
notify the OS of every battery level change.
Systems that use _BTP still will have the issue manifest with other ACPI
> Anyway, I still don't get why upgrading the wifi-cards firmware to a
> more recent version fixes the problem.
> Would you mind to elaborate on this a bit more?
When the system is in the hardware sleep state it can be woken up from
either a GPIO or a GPE. Any of those ACPI events I mentioned wil
The commit is in linux-firmware upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=c7a57ef688f7d99d8338a5d8edddc8836ff0e6de
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ub
** 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/bugs/2015297
Title:
Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue
Status in HWE Next:
> Tainted: G
In the two upstream bugs it was noted that there was an amdgpu dkms
package in place. I believe that's where this issue likely was. Commit
63a9ab264a8c came in 6.3-rc1 and the commit it fixes was also in 6.3-rc1
(b1a9557a7d00).
So at least one of the issues is probably invalid in U
** Changed in: linux (Ubuntu Kinetic)
Status: Invalid => 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/2018470
Title:
Linux 5.19 amdgpu: NULL pointer on GCN2 and inval
This commit from 6.4-rc1 fixes the S/G mode issue.
https://github.com/torvalds/linux/commit/08da182175db4c7f80850354849d95f2670e8cd9
It's CC to stable.
--
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
** Also affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a me
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Fix Released
--
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/2011403
Title:
Jammy update: v6.1.1 upstream stable releas
OK here are the fixes for this identified upstream:
Mantic (6.3+):
* UBSAN issue fixed by
https://gitlab.freedesktop.org/agd5f/linux/-/commit/3a5fb036af0a18436209fbb16e331edd26a07b3d
Kinetic (5.19):
* UBSAN issue fixed by
https://gitlab.freedesktop.org/agd5f/linux/-/commit/3a5fb036af0a1843620
** 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/1994076
Title:
Kinetic update: v5.19.14 upstream stable release
** 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/1994068
Title:
Kinetic update: v5.19.9 upstream stable release
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Stat
This issue has been fixed in later kernels and s2idle is supported now.
Suggest to use LTS 5.15 or LTS 6.1 kernels.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
[ Impact ]
* Selecting certain resolutions causes hangs when an AMD GPU is
connected to a display that supports FreeSync
[ Test Plan ]
* Verify display with freesync doesn't hang anymore
[ Where problems could occur ]
* AMD GPU could stop displaying
[ Other Info ]
*
Here is the request to take it back to stable:
https://lore.kernel.org/stable/20230515150426.2197413-1-alexander.deuc...@amd.com/T/#u
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
*
5.4.243:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y&id=d60f15682a5ce51e8119c1b9ff522494554e33b5
5.15.112:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=0788273bd0a6bbfb3c65ec77b52ebee504713925
6.1.29:
https:/
Public bug reported:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
I include tasks for Jammy because 6.2-HWE kernel will backport soon and
expose this issue in Jammy.
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affec
For reference, current version of linux-firmware
(20220329.git681281e4-0ubuntu3.14) contains following versions:
Rembrandt: 0x422
Phoenix: 0x8000e00
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bug
Upstream linux-firmware has a tag that includes these firmware
(20230625) so perhaps mantic task can be closed by syncing to that tag.
--
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/bug
Thanks, I see mantic has migrated as well, closing the mantic task.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.la
mantic has linux-firmware 20230629.gitee91452d-0ubuntu1, closing that
task.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => Triaged
** Cha
> Not entirely sure if this is the exact logging you are looking for,
but this is the result from my testing.
Thanks for having a try.
> ➜ ~ sudo python Downloads/psr.py
> DRI device 0 DMCUB F/W version: 0x043c
> ○ PSR 2 with Y coordinates (eDP 1.4a) [3]
> ○ Sink OUI: Parade
> ○ resv_40f: 01
Under stress testing it was reported that the system will sometimes fail
to wake from S3.
This firmware version has been run heavily under Q/A on various 6.1.y
kernel and those issues don't occur after taking this runtime firmware
update.
--
You received this bug notification because you are a m
Ah, in that case I would say it shouldn't be a cherry pick. Just pick
the file.
IE We don't need the whole commit for either, just
amdgpu/yellow_carp_dmcub.bin (For RMB) and amdgpu/dcn_3_1_4_dmcub.bin
(for PHX).
--
You received this bug notification because you are a member of Kernel
Packages,
I've verified the PHX jammy update (which jumped up to 0x8001b00) with a
non-problematic panel doesn't cause any additional regressions with
display or suspend on both 6.4-rc1 or with 6.1-OEM 1015.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Changed in: linux-firmware (Ubuntu)
Status: Fix Committed => Fix Released
--
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/bugs/2015297
Title:
Update GPU F/W for DCN 3.1.4 pr
Just to clarify Renjith tested on a Phoenix machine.
Based on Renjith's test result though, this is a fail and an extra change is
needed.
It turns out that this linux-firmware commit should come too:
1c513ec7 ("amdgpu: Update GC 11.0.1 and 11.0.4")
This is because of kernel commit
616843d5a11b
60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release
31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release
introduced a regression on 11.0.1/11.0.4, which is why specifically
requested (https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2024427/comments/16) below c
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kern
Confirmed on a Phoenix laptop no longer see the fallback path with 6.1
1016-OEM kernel. marking verified.
** 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.launc
** 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/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
** Tags removed: verification-failed-jammy
** 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/bugs/2024427
Title:
potential S3 issue for amdgpu Nav
OEM-6.1 1018 picks up this patch which was accidentally introduced even
though reverted upstream.
- drm/amd/display: edp do not add non-edid timings
This breaks mirror mode. It's already reverted in 6.5 and being
reverted in 6.1.42.
Can you please revert in OEM 6.1 1018 as well?
--
You re
Something that I notice in both logs:
/etc/udev/rules.d/70-amdgpu.rules:1 Invalid operator for GROUP.
Where did this file come from and what's in it?
Also; is it possible you're just missing the matching linux-
modules-6.2.0-25-generic/linux-modules-6.2.0-26-generic?
--
You received this bug n
I don't see the full logs for your failure in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+attachment/5695799/+files/journalctl-b0-20230829.log,
I'm interested in the stuff outside of the trace itself.
But I /suspect/ from that trace alone that you were out of memory at
suspend ti
Can you just manually fetch the journal from the failed boot and attach
that?
--
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/2033327
Title:
Desktop cannot resume after suspend: screen no
I don't know if launchpad messed it up, but I'm not seeing anything past
the 28th.
--
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/2033327
Title:
Desktop cannot resume after suspend: scre
I'm adding a task for gdm to this bug. The reason is that if simpledrm
is used, we've found race conditions that occur where the transition
from simpledrm to the proper KMS driver may race with gdm starting up
the login screen.
When gdm loses the race you end up with a black screen. So please ma
** Also affects: gdm (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu M
Got it; so what happened is there is a separate malloc call elsewhere in
the amdgpu display code that failed due to the low memory situation. Is
this a "one time thing" or is this a regular occurrence that you can
reproduce in how you use your machine? I would have to look at context
to see if it
I believe this likely needs the VCN fixes from
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728
** Also affects: mesa (Ubuntu)
Importance: Undecided
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu
> WARNING
This is dGPU with GC 11.0.3 right?
The warnings themselves you posted are harmless; they are missing backports in
the 6.2 kernel. I believe they're fixed in OEM-6.1 already and as you
mentioned in 6.5 kernel.
> hotplug blank screen problem
By hotplug you mean single display hotplug,
> It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2029396 .
I don't believe these to be related. That issue is specifically with
navi3x dGPU, your system has a much older dGPU.
Your 6.3 and 6.5 logs both appear to crash similarly; Do you have a
point in time t
> [5.134271] kernel: [drm:detect_link_and_local_sink [amdgpu]] *ERROR* No
> EDID read.
> [5.322247] kernel: [drm:detect_link_and_local_sink [amdgpu]] *ERROR* No
> EDID read.
> [5.510230] kernel: [drm:detect_link_and_local_sink [amdgpu]] *ERROR* No
> EDID read.
Is this connected to a
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is
still open.
** Changed in: gdm3 (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Description changed:
- The fbdev subsystem has been deprecated for a long time. We should drop
- it in favour of using simpledrm with fbdev emulation layer.
+ [ Impact ]
+ The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev emulat
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036742
Title:
amdgpu crash on Mantic
Status in linux package in Ubun
ng for matching changes landing in OEM-6.5, or HWE-6.5.
** Changed in: gdm3 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: gdm3 (Ubuntu Jammy)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Description changed:
- [ Impact ]
+ [ Impact ]
The fbd
The kernel part yes. The bug fix in GDM to prepare for whenever the
kernel part happens I would think not.
--
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/1965303
Title:
Migrate from fbde
> dmesg-ip-block-mask
[6.150330] kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper
[amdgpu]] *ERROR* ring vce0 test failed (-110)
[6.150581] kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of
IP block failed -110
[6.150726] kernel: amdgpu :01:00.0: amdgpu: a
FYI - one of those commits has reverted in 6.1 due to regressions.
See this commit:
5632e2beaf9d5 ("Revert "PCI: Distribute available resources for root buses,
too"")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubun
b60e31bf18a70 ("thunderbolt: Add DP OUT resource when DP tunnel is
discovered")
--
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/1983143
Title:
AMD Rembrandt: DP tunneling fails w
As an FYI, Kalle is also sending this fix to 6.1-rc with a CC to stable.
So this will eventually drop off the Ubuntu kernels as SAUCE.
https://patchwork.kernel.org/project/linux-
wireless/patch/20221102114803.13485-1-kv...@kernel.org/
--
You received this bug notification because you are a membe
With manually placing firmware in /lib/firmware (since SRU not started
for that) and using 5.14 kernel confirmed that mesa looks good. Since
we don't have linux-firmware SRU package yet and they are combined on
this bug report I will not add "verification-done-focal".
# glxinfo | grep "OpenGL ren
I checked this on YC and it works properly.
** 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/194438
Verified on YC with the following combination all from -proposed:
# dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0."
ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3
amd64free implementation of the EGL API -- Mesa vendor li
Checked on correct system
$ cat /proc/cpuinfo | grep "model\|family" | head -n 2
cpu family : 23
model : 160
$ dpkg -l | grep linux-firmware
ii linux-firmware
20220329.git681281e4-0ubuntu3.5 all Firmware for Linux kernel
drivers
Ran a few cycles
As dependency bug 1969091 was covered by v5.15.33 this is really just
two patches, and the more important one is 5.15.y already. The other
one is just messaging: f316ba0a8814f4c91e80a435da3421baf0ddd24c.
# git describe --contains 9e53c25f326604c838d528b430b8e603944b9e28
v5.15.46~190
It's landed
** Changed in: linux (Ubuntu Focal)
Status: Invalid => Fix Released
--
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/1950062
Title:
Unable to access CPU i2c interfaces with
Here is the kernel bug report.
https://bugzilla.kernel.org/show_bug.cgi?id=216460
** Bug watch added: Linux Kernel Bug Tracker #216460
https://bugzilla.kernel.org/show_bug.cgi?id=216460
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notif
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=216460
Importance: Unknown
Status: Unknown
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification bec
** 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/1987670
Title:
Add support for AMD PMF
Status in HWE Next:
New
Status in linux package in Ubuntu:
Here is the fix that has been queued up:
https://lore.kernel.org/linux-
ide/20220926183718.480950-1-niklas.cas...@wdc.com/
--
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/1968155
Title:
The kernel patch solution for #1968155 I don't believe will cover "HL-
DT-ST BDDVDRW GGC-H20L".
If you're comfortable building your own kernel to test it you can try to
add a new entry for your drive to replicate the solution for #1968155
(https://lore.kernel.org/linux-
ide/20220926183718.480950-1
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981364
Title:
ALSA: hda/realtek: Enable 4-speaker output for Dell XPS
Public bug reported:
[Impact]
Certain Rembrandt designs use LPDDR memory and current firmware in
linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on
DC power with it.
Some sample designs affected by the failure are Thinkpad X13, Z13, Z16.
This failure doesn't affect r
Here is a sample assertion in the wild that making just this fix helps
the problem:
https://www.reddit.com/r/thinkpad/comments/voxsr0/thinkpad_t14_gen_3_amd_first_impression_final/ightdbq/?context=8&depth=9
** Changed in: linux-firmware (Ubuntu Impish)
Status: New => Won't Fix
** Tags add
Just FYI - Lenovo hasn't certified this hardware yet, they're still
working on some Linux issues.
> Jul 18 14:34:03 thinkpad kernel: [11523.159593] [Hardware Error]: Corrected
> error, no action required.
> Jul 18 14:34:03 thinkpad kernel: [11523.159598] [Hardware Error]: CPU:0
> (19:44:1) MC15_
I'd suggest adding logs for the two other kernel tests for confirm it
really is the same 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/1982524
Title:
QCNFA765 in Lenovo Z16 fails a
Thanks Aaron! @josh if https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.3/+build/24103899/+files/linux-
firmware_20220329.git681281e4-0ubuntu3.3_all.deb solves it we should
mark this as a duplicate of #1972806 for you.
--
You received this bug notification becau
*** This bug is a duplicate of bug 1972806 ***
https://bugs.launchpad.net/bugs/1972806
You're just a little ahead of the curve using this machine before it's
certified and ready to go. You'll keep getting updates, that package
was just in progress (In the "proposed" repo). It will promote to
** 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/bugs/1972806
Title:
[SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
Status i
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1972134
Title:
AMD APU s2idle is broken after the ASIC rese
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1798552
Title:
Enable keyboard wakeup for S2Idle laptops
Status i
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1961739
Title:
PS/2 Keyboard wakeup from s2idle not fun
Here is the fixed firmware binary upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/ath12k/WCN7850/hw2.0?id=34d181d737527d903ebb363de6b2e3b1dcd42683
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu)
Status: New => 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/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 /
Can you check that? Was this maybe when the snap refreshed silently in
background? Or try a version without snap so you could use the host
mesa?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Possibly the same issue as fixed in mesa 24.1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
Please uprev mesa in the snap and see if it helps.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11138
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
--
You receiv
> but the GPU restarts are failing and the driver apparently deadlocks
or something (quite a bunch of mutex backtraces).
Yes; poor clean up/recovery should be tracked as a separate bug report
at https://gitlab.freedesktop.org/drm/amd/-/issues
--
You received this bug notification because you are
(From the log you can see that you switched modes but then the kernel
changed it right back)
--
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/2084971
Title:
Unable to change power modes fr
This appears to be a kernel driver or platform firmware bug. If it's new
to this kernel upgrade then it's more likely a kernel bug.
You should report it against the Thinkpad ACPI driver upstream.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: power-pro
Oh this is a Dell system? I thought it was a Thinkpad sorry.
Can you please try to blacklist dell-laptop and restart your system?
Does it still reproduce?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
It still appears loaded. Or something else is providing the platform
profile.
--
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/2084971
Title:
Unable to change power modes from balanced
St
Did you rebuild your initramfs after blacklist? Or maybe it's
"dell_laptop"?
--
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/2084971
Title:
Unable to change power modes from balanced
Sta
Are you sure it's kernel? Or that's just a first guess? This could
easily be the systemd bugs.
https://github.com/systemd/systemd/issues/33626
https://github.com/systemd/systemd/issues/33462
You could try SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false to see if it
helps.
** Bug watch added: github.c
> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
This is the assertion yo
501 - 600 of 624 matches
Mail list logo
