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
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
Ok the patch fixes the problem! I can see a stack trace still but it's
probably related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/comments/13
?
Thanks!
** Attachment added: "dmesg-mantic-6.5.3-patched"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachm
** Tags added: patch
--
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
Bug description:
[Impact]
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
With `amdgpu.aspm=0` it works fine.
** Attachment added: "dmesg-focal-5.14-rc2-aspm0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5711750/+files/dmesg-focal-5.14-rc2-aspm0
--
You received this bug notification because you are a member of Kernel
Packages, which is
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
I can't install Jammy because I can't see the installer, so I did the
test on Focal.
5.13.19 works, 5.14-rc2 fails (same for 5.14.0). Dmesg attached.
** Attachment added: "dmesg-focal-mainline.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5711667/+files/dmesg-f
> 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.
the firmware on mantic is zstd compressed, so mainline builds from the
past can't load the firmware..
--
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
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
Here’s an example of what happens when I start using Brave browser in
the attachment.
With X it crashes and then restarts the gdm and brings me to the login screen.
in any case it’s unusable as it crashes maybe 10 seconds into opening any app.
** Attachment added: "example of what happens when I
I think I have the same issue but I'm not sure. Please advise if I can
test anything and how?
GPU: AMD Radeon RX Vega 64 Liquid
CPU: AMD Threadripper 1900x
DS: Wayland
With the new installer:
The new installer crashes the entire session when it opens the “Connectivity”
screen.
-
On Focal, it also works with 5.14.0-1059. dmesg attached.
** Attachment added: "dmesg-5.14oem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5709895/+files/dmesg-5.14oem
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
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
> 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?
Unfortunately still no luck. I booted Focal with 5.10 OEM and then
rebooted to Mantic with 5.15.134. The screen freezes at
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
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.
> Can you see if it keeps working with latest 5.10 OEM? 1057 it looks
like is newest.
Yes, it still works with that version.
** Attachment added: "dmesg-5.10.0-1057"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/570/+files/dmesg-5.10.0-1057
--
You received thi
> 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 setup involves a custom KVM indeed, I'll attach the EDID file
involved in this setup.
I tested everything as requested, no luck unfortunately. The working
configuration, which I've now replicated, is involving the OEM image for
Ubuntu 20.04 with which the device has been certified.
Please fin
** 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
Yes it's a KVM of sorts, using Zapper. But apparently this did work
before, so a rough bisect with mainline builds will be conducted.
--
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
> [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
UBSAN warnings could be a red herring. They've added a compiler flag
that complains about flexible arrays if they're declared incorrectly
(false positive). Will take a look tomorrow.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
> 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
[4.918050] kernel: UBSAN: array-index-out-of-bounds in /build/linux-
IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
is not good
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-23.10
--
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/2036742
Title:
amdgpu crash on Mantic
Status in linux-
** Description changed:
[Impact]
- Booting from USB the latest Mantic Desktop canary image (2023-09-19),
+ Booting from USB the latest Mantic Desktop daily image (2023-09-20),
just after the initial logs, nothing is displayed on screen. The system
is still alive since _autoinstall_ works
30 matches
Mail list logo
