** 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
This should be a different issue than the mutter issue; please open it
up separately for investigation.
--
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/2034619
Title:
[amdgpu] gnome-shell
*** This bug is a duplicate of bug 2042867 ***
https://bugs.launchpad.net/bugs/2042867
** This bug has been marked a duplicate of bug 2042867
Changing display resolution leads into black screen
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
*** This bug is a duplicate of bug 2043197 ***
https://bugs.launchpad.net/bugs/2043197
** This bug has been marked a duplicate of bug 2043197
USB bus error after upgrading to proposed kernel on lunar and jammy
--
You received this bug notification because you are a member of Kernel
Packag
Open a new bug at kernel bugzilla and attach kernel log, acpidump and
dmidecode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working i
Btw - That commit is in 5.15.132.
--
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/2043197
Title:
USB bus error after upgrading to proposed kernel on lunar and jammy
Status in linux packa
Should be fixed with
https://github.com/torvalds/linux/commit/59cf445754566984fd55af19ba7146c76e6627bc
then I would expect.
--
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/2043197
Title:
Each page you'll need the following binaries:
Linux image unsigned
Linux modules
Linux modules extra
Download those 3 and install them with dpkg.
Note: none of these are signed for secure boot. If you have that
enabled, disable it for this experiment.
--
You received this bug notification becau
OK thanks. Nothing was obvious in the log differences. We need to
narrow down intermediate kernel releases to identify what's changed to
cause this regression.
Can you please test these binaries from those. Capture the journals for
each and note if they worked or didn't. Hopefully we'll get clo
This issue is fixed in 6.6-rc3: 2de19022c5d7 ("drm/amd/display: fix the
ability to use lower resolution modes on eDP")
It's backported to stable 6.5.6 as 79aec38ba852 ("drm/amd/display: fix
the ability to use lower resolution modes on eDP").
Canonical needs to pull the fix into their kernel.
**
Please add kernel log from both your old kernel and new kernel.
** 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/2042713
Title
Your "good" journal is with nomodeset. Can I see the log from a good
journal without adding a module parameter? Like an older kernel that
worked?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Changed in: linux (Ubuntu Noble)
Status: New => Triaged
** Changed in: linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: linux (Ubuntu Lunar)
Status: New => Triaged
** Changed in: linux (Ubuntu Jammy)
Status: New => Triaged
** Changed in: linux-oem-6.5 (
From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You received
Can you please share the kernel log from a failed kernel? To get it:
1) Boot the failed kernel and reproduce failure
2) Boot a good kernel
3) run "journalctl -k -b-1 > journal_bad.txt"
4) run "journalctl -k > journal_good.txt"
Then attach both of those to this bug.
** Changed in: linux (Ubuntu)
> amd_gpio AMDI0030 0: Invalid config param 0014
This is fixed by this patch:
https://github.com/torvalds/linux/commit/87b549efcb0f7934b0916d2a00607a878b6f1e0f
Canonical needs to backport that to applicable kernels.
> 10/31/23 12:11 PM WARNING CPU: 2 PID: 3763 at
drivers/gpu/drm/amd/amdgpu
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
https://gitlab.free
These fixes all landed in 6.5-rc2, mantic and noble have them for sure, closing
those tasks.
I'd expect backporting to be done for Lunar and Jammy if necessary.
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Mantic)
Stat
It's in lvfs-testing.
https://fwupd.org/lvfs/devices/work.frame.Laptop.Ryzen7040.BIOS.firmware
** 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://b
#166
Canonicals' kernel team needs to apply it. When they do there would be
notification to this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and
Here's the fix in Linus' tree.
https://github.com/torvalds/linux/commit/128b0c9781c9f2651bea163cb85e52a6c7be0f9e
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Ke
Sorry for delay looking at this. I might have not been clear. That
script needs to be run after the error has occurred. I don't see the
error in this kernel log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
h
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working in New Lenovo
Please also take this fix at the same time for this same laptop. It
will fix s2idle for it.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes&id=3bde7ec13c971445faade32172cb0b4370b841d9
** Changed in: libinput (Ubuntu)
Status: Confirmed => Inv
Here is the upstream patch for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218003
Importance: Unknown
Status: Unknown
-
Here's the mainline commit with the fix for your issue:
https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f
--
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/203
#75
You can turn on proposed and then use ppa-purge command to remove my
PPA.
--
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/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd when lock
Can you please share your kernel log from jammy when the failure has
occurred?
We did test XTX working, suspect a separate issue.
--
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/20
conflict since they will be different binaries.
Please reject the *ubuntu4 version from the mantic-proposed queue and
accept the *ubuntu3.1 version (if it looks good).
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notific
#17
This issue is specific to AMD Navi3x dGPU; please open separate issue for your
problem.
--
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/2038745
Title:
NV31 XTX cannot boot i
/+packages
I've also uploaded the mutter package into the proposed queue for SRU
team to look at.
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Mantic)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
I'd say let's track the out of bounds stuff in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039926
** Summary changed:
- amdgpu crash on Mantic
+ VI dGPU fails to initialize on Intel platforms w/ 5.14+
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2874
https://gitlab.freedesktop.org/drm/amd/-/issues/2874
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2874
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=217947
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/
Great! Thanks I've posted it for review.
https://lore.kernel.org/amd-
gfx/20231023134514.144863-1-mario.limoncie...@amd.com/T/#u
Yes the "UBSAN: array-index-out-of-bounds" traces are to be fixed in
6.7. If you want to pull those patches early I can point you at them.
--
You received this bug
resume after suspend: screen not detected
+ dGPU suspend fails under memory pressure
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2362
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed
Also reported at #2036742
It's caused by the use of flexible size arrays.
Here's the fixes from linux-next that should help it.
https://cgit.freedesktop.org/drm/drm/commit/drivers/gpu/drm/amd/pm/powerplay/hwmgr?id=0f0e59075b5c22f1e871fbd508d6e4f495048356
https://cgit.freedesktop.org/drm/drm/commi
Great, thanks! Let me know if the patch works 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/2036742
Title:
amdgpu crash on Mantic
Status in linux package in Ubuntu:
Confirmed
If amdgpu.aspm=0 helps the issue, then can you please test this patch
against Mantic? If it helps I'll submit it.
** Patch added: "Disable ASPM for VI on all Intel systems"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5711749/+files/0001-drm-amd-Disable-ASPM-for-VI
To explain some of the differences in the logs:
* UVD is the IP block that fails to init (so no "UVD and UVD ENC initialized
successfully").
* Once an IP block fails, next one isn't even tried (so no "VCE initialized
successfully")
* kfd doesn't initialize because amdgpu_amdkfd_device_init() won
For Framework please upgrade to bios 3.03. There is a very crucial bug
in 3.02 that can lead to stuff like this.
--
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/2039819
Title:
amdgpu cras
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
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/2039868
Title:
amdgpu reset during usage of
This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
I was just checking a Lenovo X13 for another issue and reproduced the
same thing. This is a duplicate of that other bug.
** This bug has been marked a duplicate of bug 2034619
[amdgpu] gnome-shell gets
> the firmware on mantic is zstd compressed, so mainline builds from the
past can't load the firmware..
As a hack then maybe just clone https://gitlab.com/kernel-
firmware/linux-firmware and put everything (uncompressed) in
/lib/firmware/updates/ to get by that.
Or run the check on Jammy instead.
I've split up the GDM for Jammy change into
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757
** No longer affects: gdm3 (Ubuntu 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/
> Oh, wait. You are just fixing the race condition?
Yeah; I see the confusion. This issue got caught up by making sure the
GDM race condition was fixed at the same as when this feature is
enabled.
Perhaps it's better to split the GDM part of it off to it's own bug
instead then.
> In that case,
The problem is specifically when 24.04's kernel backports to 22.04 it
will expose the race condition to GDM. If that kernel will never
backport then it won't be a problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
This seems like a different bug to me. Can you please open a different
report and attach the relevant logs from the journal to it?
--
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
T
Something is really fishy here - the 5.15 test is again missing firmware
for both i915, amdgpu and ath10k:
[2.345119] kernel: i915 :00:02.0: Direct firmware load for
i915/rkl_dmc_ver2_03.bin failed with error -2
[2.345122] kernel: i915 :00:02.0: [drm] Failed to load DMC firmware
Please share a kernel log of the failure after you've upgraded.
--
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/2038745
Title:
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop wi
*** This bug is a duplicate of bug 2038745 ***
https://bugs.launchpad.net/bugs/2038745
** This bug has been marked a duplicate of bug 2038745
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver
installed
--
You received this bug notification because you are a mem
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Ne
Can you please share your kernel log from a boot that had the failure, and
without that parameter in place share the output of this script?
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
--
You received this bug notification because you are a member of Kernel
Packages, which
Internal team has tested the Jammy update
(20220329.git681281e4-0ubuntu3.21) as well on NV31 XTX card and it looks
good there as well.
** Changed in: linux-firmware (Ubuntu Lunar)
Status: Fix Released => Fix Committed
** Tags added: verification-done-jammy
--
You received this bug notifi
** Tags added: verification-done-lunar
--
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/2038745
Title:
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
driv
@Juerg:
Internal team looked at it, VP with Navi31 XTX boards, VNP with the others.
So the testing with OEM-6.1/OEM-6.5 on other Navi31 from earlier bug is
accurate.
Confirmed that upgrading SMU binary (just dropped into
/lib/firmware/updates/amdgpu) fixes the issue.
Considering the regression
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => Critical
** Changed in: linux-firmware (Ubuntu Lunar)
Importance:
Let's track the regression in
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
I believe the same thing should be done for Navi33 at same time, it
upgraded IMU as well. So these two commits are needed in Jammy and
Lunar:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd
http
Instead of reverting the IMU binary can you please upgrade the SMU
binary from the same 5.5 release ?
Navi31:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd
Navi33:
https://git.kernel.org/pub/scm
Thanks, let me check with others on Monday if that's the right action
for your issue.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ub
Can you please upload your journal from the failure?
Also can you please experiment with rolling back to this one version of
this one firmware binary:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/gc_11_0_0_imu.bin?id=e32209f07556427c9b0b841bfb76ca71e8
I don't expect it helps your boot issue, but the UBSAN issue will be
fixed by this commit.
https://lore.kernel.org/amd-
gfx/78abc334-44ed-4632-8796-6bbe9c432...@amd.com/T/#me31ff6b88640b03be1a8edfc6fc8878ac78ca6bb
Please redo the test with 5.15.
--
You received this bug notification because you
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
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/2037641
Title:
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You r
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
AMD internal team has tested this updated firmware package against
Navi31 and Navi33 dGPUs on both OEM-6.1 and OEM-6.5 kernels. No new
problems introduced.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance: Undec
Thanks for checking. So good to know it hasn't regressed from stable in
5.10. Can you redo your 5.15 test with the firmware in place so we can
see if we're OK there or not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> 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
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
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
** 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
** 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
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
> [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
> 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
> 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,
** 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
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
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
** 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
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
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
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 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
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
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
** 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
** 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:
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
** 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
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
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
** 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
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
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,
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
101 - 200 of 590 matches
Mail list logo
