I suggest starting out with a mainline kernel build for 6.12-rc7.
* If you can reproduce the issue still there then you should check if
it's on the AMD bug tracker
(https://gitlab.freedesktop.org/drm/amd/-/issues). If it's not you
should raise an issue there.
* If you can't reproduce it on 6.12-
** No longer affects: amd
** Project changed: xf86-video-amd => linux
** Also affects: linux (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.launchpad.net
Your bad log seems to be showing the following problems.
Nov 10 22:38:42 Silencio kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Nov 10 22:41:17 Silencio kernel: [drm:drm_crtc_commit_wait [drm]] *ERROR*
flip_done timed out
Nov 10
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I need to find the
cause for that and report another bug :(
Maybe this:
https://gitlab.gnome.org/GNOM
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
> 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 Kernel
Packages,
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 Kernel
Packages, which is subscribed to li
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** 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.
htt
Did you happen to change the power adapter state over the suspend
sequence when this reproduced? There may be a problem with the firmware
handling of that event.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Can you tell me how many times you unplugged and plugged power adapter
during that log?
I see that hardware left s0i3 state 4 times over the one suspend cycle:
> 2024-11-19 21:47:42,898 INFO: ○ Hardware sleep cycle count: 4
I'm wondering if it's 1:1 mapping that it woke up and went back to
hardw
> sorry, I don't understand question. How do I change power adapter
state over the suspend sequence?
I'm meaning do either of these scenarios (specifically) trigger it:
1) You start your suspend sequence with it unplugged and then plug in and then
resume and the issue happens.
2) You start your
>From the trace this is triggered from a userspace IOCTL to remove a
framebuffer. This causes drm core to process atomic_remove_fb() as
work, and this will use the drm driver to do atomic modesets.
One of the things that happens for this is going to be recalculating MST
DSC configs (if appropriat
> I clearly dont have time to play with (1) and rebuilding/maintaining a
kernel in the hope of a non reproduction ; especially since I dont have
clear STR so it means making this my daily driver.
I'm not suggesting you to keep using/maintaining such a kernel, it's a
debugging data point to prove w
>From your log this looks like a nouveau kernel problem to me that is
tickled by fwupd using the DPCD reading interface.
If you don't use that GPU you can try modprobe.blacklist=nouveau or you
can try another kernel like OEM 6.11 or HWE 6.11.
** Package changed: fwupd (Ubuntu) => linux (Ubuntu)
2025-02-16T00:08:02.549345+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
kernel: [ cut here ]
2025-02-16T00:08:02.549359+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
kernel: WARNING: CPU: 13 PID: 1192141 at
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:192
r535_gsp_c
Can you please experiment with modprobe.blacklist=nouveau?
--
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/2098668
Title:
fwupd daemon hangs for a while during TPM access
Status in fwupd
> According to the answer of this question, "fwupd scans for all dpaux
devices and probes them". Hence there might be no plugin that I could
disable to bypass this bug.
That's correct.
> Unfortunately, no. The ASUS TUF Gaming laptop may need it to run the
display. I suspect that because long ago
> 2. Once it is up and running, starting the firmware-updater.firmware-notifier
> service produced this message:
> 15:55:12.499 FuPluginLinuxLockdown failed to ensure attribute fix flags:
> missing executable grubby in PATH
This message is to be expected; Ubuntu doesn't use grubby.
> 1. For som
** Changed in: fwupd (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/2098668
Title:
nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN
S
Public bug reported:
OEM-6.14 and mainline 6.14 kernel include AMD XDNA NPU kernel module.
Without matching NPU firmware the kernel will show an error about
failing to load on many platforms. This firmware should be SRU'ed into
Noble linux-firmware package to prevent this problem.
https://git.ke
Plucky already rebased to new enough linux-firmware, so only need task
for noble.
--
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/2098979
Title:
[SRU] Add amdnpu firmware
Status
I don't draw that same conclusion as you. I feel you have two separate
issues that can cause severe problems.
If accessing the DPCD sysfs file provided by nouveau crashes in a way
that is enough to taint it there is certainly a nouveau bug (the
original one you filed here).
For this particular b
> Unfortunately, I can't replicate this as I have no idea how to easily
trigger a GPU reset
On AMD systems You can use debugfs file you can do it with. For example
on my system:
# cat /sys/kernel/debug/dri/0/amdgpu_gpu_recover
--
You received this bug notification because you are a member of Ke
601 - 624 of 624 matches
Mail list logo
