System hang during boot and dracut-pre-mount-hooks processing
by George R Goffe
Hi,
I just installed a current kernel (6.1.0-0.rc1.20221018gitbb1a1146467a.16). This kernel will not boot. It appears to hang near the execution of dracut-pre-mount processing. This process seems to be looking for a disk by uuid but it NEVER completes. I let it go for over an hour but the system was still effectively hung.
My fallback kernel is the release 5.18.0-0.rc7.54.fc37.x86_64. This situation happened during early releases of this kernel series but thien it just started working.
I have no ability (that I know of) to get a log of the boot attempt.
Is this a known problem? Is there a workaround?
Please help.
Best regards,
George...
3 months, 1 week
Re: Thoughts welcome: interface between automated test gating and
the "critical path"
by Adam Williamson
On Fri, 2022-09-02 at 08:37 +0000, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > Now, because I glued openQA to the critpath because it was handy, there
> > are two sets of consequences to a package being in critical path:
> >
> > 1. Tighter Bodhi requirements
> > 2. openQA tests are run, and results gate the update (except Rawhide)
> >
> > So, one of the implicit questions here is, is it OK to keep twinning
> > these two sets of consequences, or should we split them up? Splitting
> > them up kinda implies answer 2) from my original mail: "Keep the
> > current "critical path" concept but define a broader group
> > of "gated packages" somewhere". Because we would then need some new
> > concept that isn't "critical path". As I said, that's more *work* -
> > it'd require us to write new code in several places[0]. Even if we
> > decide it'd be nice to do this, is it nice *enough* to be worth doing
> > that work?
>
> I'd still vote for keeping a single critpath list and using it as
> "the list of packages that require extra care and testing".
>
> As you describe, the original meaning of critpath has shifted, but
> it's because the way we do updates and QA has also shifted. Doing
> gating tests for a package seems much more useful than just keeping
> it longer in 'updates-testing' in hope that somebody discovers an
> important regresion in the second week.
Well, there's a caveat there - openQA doesn't test everything. On the
whole we cover quite a lot with the set of tests that gets run on
updates, but there's certainly lots of potential for there to be
important bugs it misses, that a human tester might catch. So I think
there is still a case for the higher karma requirements too.
>
> So yeah, I don't think it makes sense to do the extra work to split
> the concepts. Also because we have way too many concepts and processes
> in Fedora already.
On the whole, though, I agree with you. I just don't trust my own
opinion because it's obviously biased by what's convenient for me. :D
> > If we don't think it's worth doing that work, then we're kinda stuck
> > with openQA glomming onto the critpath definition to decide which
> > updates to test and gate, because I don't have any other current viable
> > choices for that, really. And we'd have to figure out a critpath
> > definition that's as viable as possible for both purposes.
> >
> >
> > BTW, one other thought I've had in relation to all this is that we
> > could enhance the current critpath definition somewhat. Right now, it's
> > built out of package groups in comps which are kinda topic-separated:
> > there's a critpath-kde, a critpath-gnome, a critpath-server, and so on.
> > But the generated critical path package list is a monolith: it doesn't
> > distinguish between a package that's on the GNOME critpath and a
> > package that's on the KDE critpath, you just get a big list of all
> > critpath packages. It might be nice if we actually did distinguish
> > between those - the critpath definition could keep track of which
> > critpath topic(s) a package is included in, and Bodhi could display
> > that information in the web UI and provide it via the API. That way
> > manual testers could get a bit more info on why a package is critpath
> > and what areas to test, and openQA could potentially target its test
> > runs to conserve resources a bit, though this might require a bit more
> > coding work on the gating stuff now I think about it.
>
> That sounds useful. We only need a volunteer to figure out the details
> and do the work ;)
I actually did a huge rewrite of the thing that generates the critpath
data this week, and it probably wouldn't be tooooo much work, honestly.
The most annoying bit would be the Bodhi frontend stuff, but that's
because I'm bad at frontend dev in general. :P But yeah, this is
definitely off in sky-castle land. I'll add it to my ever-growing list
of sky-castle projects to do when I get a couple of years of spare
time...
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
3 months, 2 weeks
Video issue
by pmkellly＠frontier.com
This is something I first saw at first branch and I have continued
monitoring it since. There has been no change.
The problem is that MP4, and AVI videos will not play on Totem. This is
probably not a blocker based on the current criteria. I doubt that a bug
report is even a proper thing to do. However this seems likely to cause
some discontent and commentary.
My current clean install is from Fedora-WS-Live-37-20221013-n-0. It is
fully updated. I have also loaded the Free video codecs from
RPMFusion.org. In Software --> Codecs when I try to install the the
gstreamer-libav Software says it's not available. So it can't be
installed. I've looked for it on RPMFusion.org with no luck. I found
gstreamer1-plugin-libav in the fedora repo then installed in and did a
reboot. This solved the problem. MP4, and AVI videos now play in totem.
Software --> Codecs still says that gstreamer-libav is not available.
I think this either needs to be installed by default and remove it from
Software --> Codecs or put it back in RPMFusion.org where it can be
installed the way users are used to. For now I'll just add it to my
install script.
Have a Great Day!
Pat (tablepc)
3 months, 2 weeks
Fedora 37 Final status update
by Adam Williamson
Hi, folks! Just wanted to make sure everyone's aware of the current
status with regards to the Fedora 37 release.
We are waiting on a couple of key things to build a release candidate:
a new glibc build for
https://bugzilla.redhat.com/show_bug.cgi?id=2129358 , and improved
upstream fixes for the gnome-calendar recurring event bugs. Both of
those are being actively worked on and I'm hoping they'll arrive today
or tomorrow; as soon as they do, I'll request a candidate compose.
In the mean time, it'd be great if folks can test and karma the pending
updates for blocker and FE bugs, which are listed on blockerbugs:
https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist
especially it'd be great to have as much testing as possible of the
kernel update. It'd also be great if folks can help fill out the
validation matrices for the current compose:
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20221012.n...
even though we won't ship that compose, it's pretty similar to what we
will ship, and it'd be very good to have the tricky tests like Active
Directory, unusual storage, and Cloud tests run now just in case there
are any lurking issues. And if necessary, we'll be able to transfer
results forward to the RC for tests that shouldn't be affected by
anything changed in it.
Thanks a lot, folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
3 months, 2 weeks
Fedora-Minimal-37-20221014.n.0.aarch64 report bug
by wang_chen
download Fedora-Minimal-37-20221014.n.0.aarch64.raw.xz and install to raspberry pi 3b+,
start display: 5.924021] kernel BUG at lib/list_debug.c:62!
[ 5.924021] kernel BUG at lib/list_debug.c:62!
3 months, 3 weeks
F37 GPU thread crash on Ryzen 6000 iGPU: GL_OUT_OF_MEMORY in
glReadPixels
by Leon White
Hello, first time posting here.
I have an Ryzen 6000 with iGPU (Radeon 680M) hardware compatibility bug that I can reproduce under Fedora 37, as well as 36 a number of other distros. To reproduce, install Fedora, install VS Code (or any other Electron app such as Slack or Spotify) and go to fullscreen or attempt to resize the window diagonally for a few seconds, or attempt to wake from sleep. This will result in a GPU thread crash (visible with `sudo journalctl _UID=1000`) and kernel core dump (`sudo dmesg`). In some cases the system can recover, but stability is poor until the system is rebooted. Using the dGPU results in some improvement, but still crashes when waking from sleep.
Fedora 37 Beta (all updates installed)
Kernel: 5.19.11
Gnome: 43.0
Hardware: Lenovo Z16 Gen 1 (UEFI 1.22)
amdgpu issue thread: https://gitlab.freedesktop.org/drm/amd/-/issues/2149
video of the issue recorded for Lenovo support: https://www.loom.com/share/a474ff44a09c422698cb588a8e206a15
inxi:
Graphics:
Device-1: AMD Navi 24 [Radeon RX 6400 / 6500 XT] vendor: Lenovo
driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16
bus-ID: 03:00.0 chip-ID: 1002:743f
Device-2: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu
v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: eDP-1
empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7 bus-ID: 67:00.0
chip-ID: 1002:1681
Device-3: Chicony Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-4:2 chip-ID: 04f2:b78b
Device-4: Chicony Integrated IR Camera type: USB driver: N/A
bus-ID: 5-1:2 chip-ID: 04f2:b78c
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.3
compositor: gnome-shell v: 43.0 driver: gpu: amdgpu display-ID: 0
Monitor-1: eDP-1 model: Samsung 0x4165 res: 3840x2400 dpi: 284
diag: 406mm (16")
OpenGL: renderer: REMBRANDT (rembrandt LLVM 15.0.0 DRM 3.47
5.19.11-300.fc37.x86_64) v: 4.6 Mesa 22.2.0 direct render: Yes
journalctl:
Sep 28 16:07:29 fedora gnome-shell[7910]: Failed to scan out client buffer: drmModeAtomicCommit: Cannot allocate memory
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 37683200 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[7910]: Failed to scan out client buffer: drmModeAtomicCommit: Cannot allocate memory
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38928384 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38928384 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6
Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Failed to allocate 3844x2340 FBO due to GL_OUT_OF_MEMORY.
Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Expect reduced performance.
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: EE ../src/gallium/drivers/radeonsi/si_texture.c:1917 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glReadPixels
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE)
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) Backtrace:
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 0: /usr/bin/Xwayland (0x5655542ed000+0x16d1b2) [0x56555445a1b2]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 1: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x1151ea) [0x7fd6c1c0e1ea]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 2: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fdbb6) [0x7fd6c1df6bb6]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 3: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x33ce42) [0x7fd6c1e35e42]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 4: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fe7a1) [0x7fd6c1df77a1]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 5: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fea36) [0x7fd6c1df7a36]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 6: /usr/bin/Xwayland (0x5655542ed000+0x69c4e) [0x565554356c4e]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 7: /usr/bin/Xwayland (0x5655542ed000+0x5896f) [0x56555434596f]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 8: /usr/bin/Xwayland (0x5655542ed000+0x5924d) [0x56555434624d]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 9: /usr/bin/Xwayland (0x5655542ed000+0x1abc63) [0x565554498c63]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 10: /usr/bin/Xwayland (0x5655542ed000+0x1ac3ce) [0x5655544993ce]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 11: /usr/bin/Xwayland (0x5655542ed000+0x53526) [0x565554340526]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 12: /usr/bin/Xwayland (0x5655542ed000+0xf49bf) [0x5655543e19bf]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 13: /usr/bin/Xwayland (0x5655542ed000+0xd21e9) [0x5655543bf1e9]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 14: /usr/bin/Xwayland (0x5655542ed000+0xf7345) [0x5655543e4345]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 15: /usr/bin/Xwayland (0x5655542ed000+0x94a4e) [0x565554381a4e]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 16: /usr/bin/Xwayland (0x5655542ed000+0x4c046) [0x565554339046]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 17: /usr/bin/Xwayland (0x5655542ed000+0xd1d82) [0x5655543bed82]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 18: /usr/bin/Xwayland (0x5655542ed000+0xd4d03) [0x5655543c1d03]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 19: /usr/bin/Xwayland (0x5655542ed000+0xa2980) [0x56555438f980]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 20: /usr/bin/Xwayland (0x5655542ed000+0xab6a8) [0x5655543986a8]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 21: /usr/bin/Xwayland (0x5655542ed000+0x38bd1) [0x565554325bd1]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 22: /lib64/libc.so.6 (0x7fd6c3e75000+0x23510) [0x7fd6c3e98510]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 23: /lib64/libc.so.6 (__libc_start_main+0x89) [0x7fd6c3e985c9]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 24: /usr/bin/Xwayland (0x5655542ed000+0x3a3f5) [0x5655543273f5]
Sep 28 16:07:29 fedora gnome-shell[9533]: (EE)
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Failed to allocate 36864000 bytes PBO due to GL_OUT_OF_MEMORY.
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: domains : 2
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: flags : 0
Sep 28 16:07:30 fedora gnome-shell[9533]: EE ../src/gallium/drivers/radeonsi/si_texture.c:1917 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glReadPixels
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE)
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) Backtrace:
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 0: /usr/bin/Xwayland (0x5655542ed000+0x16d1b2) [0x56555445a1b2]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 1: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x1151ea) [0x7fd6c1c0e1ea]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 2: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fdbb6) [0x7fd6c1df6bb6]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 3: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x33ce42) [0x7fd6c1e35e42]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 4: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fe7a1) [0x7fd6c1df77a1]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 5: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fea36) [0x7fd6c1df7a36]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 6: /usr/bin/Xwayland (0x5655542ed000+0x69c4e) [0x565554356c4e]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 7: /usr/bin/Xwayland (0x5655542ed000+0x5e99f) [0x56555434b99f]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 8: /usr/bin/Xwayland (0x5655542ed000+0x628bb) [0x56555434f8bb]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 9: /usr/bin/Xwayland (0x5655542ed000+0x63ab2) [0x565554350ab2]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 10: /usr/bin/Xwayland (0x5655542ed000+0xf7fd0) [0x5655543e4fd0]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 11: /usr/bin/Xwayland (0x5655542ed000+0xe183a) [0x5655543ce83a]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 12: /usr/bin/Xwayland (0x5655542ed000+0xe16d8) [0x5655543ce6d8]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 13: /usr/bin/Xwayland (0x5655542ed000+0xe16d8) [0x5655543ce6d8]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 14: /usr/bin/Xwayland (0x5655542ed000+0xda2dc) [0x5655543c72dc]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 15: /usr/bin/Xwayland (0x5655542ed000+0xaab3f) [0x565554397b3f]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 16: /usr/bin/Xwayland (0x5655542ed000+0x38bd1) [0x565554325bd1]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 17: /lib64/libc.so.6 (0x7fd6c3e75000+0x23510) [0x7fd6c3e98510]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 18: /lib64/libc.so.6 (__libc_start_main+0x89) [0x7fd6c3e985c9]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 19: /usr/bin/Xwayland (0x5655542ed000+0x3a3f5) [0x5655543273f5]
Sep 28 16:07:30 fedora gnome-shell[9533]: (EE)
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer:
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: size : 37683200 bytes
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: domains : 4
Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: flags : 6
dmesg:
[ 143.221178] code: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0
[ 143.221189] CPU: 1 PID: 9613 Comm: code Not tainted 5.19.11-300.fc37.x86_64 #1
[ 143.221192] Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022
[ 143.221193] Call Trace:
[ 143.221196] <TASK>
[ 143.221201] dump_stack_lvl+0x44/0x5c
[ 143.221206] warn_alloc+0xfb/0x120
[ 143.221210] ? psi_task_change+0x85/0x110
[ 143.221214] __alloc_pages_slowpath.constprop.0+0xcfe/0xd60
[ 143.221217] __alloc_pages+0x201/0x220
[ 143.221220] ttm_pool_alloc+0x2af/0x5a0 [ttm]
[ 143.221227] amdgpu_ttm_tt_populate+0x35/0x90 [amdgpu]
[ 143.221327] ttm_tt_populate+0x9d/0x140 [ttm]
[ 143.221330] ttm_bo_handle_move_mem+0x1ac/0x1c0 [ttm]
[ 143.221334] ttm_bo_validate+0xb5/0xf0 [ttm]
[ 143.221337] ? drm_vma_offset_add+0x59/0x60
[ 143.221340] ? drm_vma_offset_add+0x2f/0x60
[ 143.221342] ttm_bo_init_reserved+0x178/0x250 [ttm]
[ 143.221345] amdgpu_bo_create+0x1b2/0x460 [amdgpu]
[ 143.221421] ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
[ 143.221495] ? unix_stream_recvmsg+0x68/0x80
[ 143.221499] amdgpu_bo_create_user+0x24/0x40 [amdgpu]
[ 143.221576] amdgpu_gem_create_ioctl+0x121/0x360 [amdgpu]
[ 143.221652] ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
[ 143.221727] ? amdgpu_gem_force_release+0x130/0x130 [amdgpu]
[ 143.221802] drm_ioctl_kernel+0xa1/0x150
[ 143.221807] drm_ioctl+0x21f/0x420
[ 143.221809] ? amdgpu_gem_force_release+0x130/0x130 [amdgpu]
[ 143.221884] ? ioctl_has_perm.constprop.0.isra.0+0xaa/0xf0
[ 143.221887] ? ktime_get_ts64+0x4c/0xf0
[ 143.221891] amdgpu_drm_ioctl+0x4a/0x80 [amdgpu]
[ 143.221964] __x64_sys_ioctl+0x90/0xd0
[ 143.221968] do_syscall_64+0x5b/0x80
[ 143.221971] ? syscall_exit_to_user_mode+0x17/0x40
[ 143.221973] ? do_syscall_64+0x67/0x80
[ 143.221974] ? syscall_exit_to_user_mode+0x17/0x40
[ 143.221976] ? do_syscall_64+0x67/0x80
[ 143.221977] ? syscall_exit_to_user_mode+0x17/0x40
[ 143.221979] ? do_syscall_64+0x67/0x80
[ 143.221980] ? syscall_exit_to_user_mode+0x17/0x40
[ 143.221981] ? do_syscall_64+0x67/0x80
[ 143.221983] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 143.221986] RIP: 0033:0x7fe50730a87f
[ 143.222023] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[ 143.222024] RSP: 002b:00007ffc99411fc0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 143.222026] RAX: ffffffffffffffda RBX: 000039e003da3700 RCX: 00007fe50730a87f
[ 143.222027] RDX: 00007ffc99412060 RSI: 00000000c0206440 RDI: 0000000000000017
[ 143.222028] RBP: 00007ffc99412060 R08: 000039e003da3700 R09: 00000000000000a0
[ 143.222029] R10: 000039e000265a08 R11: 0000000000000246 R12: 00000000c0206440
[ 143.222029] R13: 0000000000000017 R14: 000000000087e000 R15: 0000000000000013
[ 143.222033] </TASK>
[ 143.222034] Mem-Info:
[ 143.222036] active_anon:3974 inactive_anon:1176507 isolated_anon:0
active_file:367429 inactive_file:1097328 isolated_file:0
unevictable:1768 dirty:387 writeback:0
slab_reclaimable:47631 slab_unreclaimable:73611
mapped:391973 shmem:22515 pagetables:30639 bounce:0
kernel_misc_reclaimable:0
free:4682330 free_pcp:56 free_cma:0
[ 143.222039] Node 0 active_anon:15896kB inactive_anon:4706028kB active_file:1469716kB inactive_file:4389312kB unevictable:7072kB isolated(anon):0kB isolated(file):0kB mapped:1567892kB dirty:1548kB writeback:0kB shmem:90060kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 2048kB writeback_tmp:0kB kernel_stack:50256kB pagetables:122556kB all_unreclaimable? no
[ 143.222043] Node 0 DMA free:6880kB boost:0kB min:32kB low:44kB high:56kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15996kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[ 143.222046] lowmem_reserve[]: 0 1713 31287 31287 31287
[ 143.222049] Node 0 DMA32 free:3556kB boost:0kB min:3696kB low:5448kB high:7200kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:1869324kB managed:1801348kB mlocked:0kB bounce:0kB free_pcp:224kB local_pcp:0kB free_cma:0kB
[ 143.222051] lowmem_reserve[]: 0 0 29574 29574 29574
[ 143.222054] Node 0 Normal free:18718884kB boost:0kB min:63852kB low:94132kB high:124412kB reserved_highatomic:0KB active_anon:15896kB inactive_anon:4706028kB active_file:1469716kB inactive_file:4389312kB unevictable:7072kB writepending:1548kB present:30903296kB managed:30291884kB mlocked:7072kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[ 143.222057] lowmem_reserve[]: 0 0 0 0 0
[ 143.222059] Node 0 DMA: 0*4kB 0*8kB 0*16kB 1*32kB (U) 1*64kB (U) 1*128kB (U) 0*256kB 1*512kB (U) 0*1024kB 1*2048kB (M) 1*4096kB (M) = 6880kB
[ 143.222105] Node 0 DMA32: 29*4kB (U) 62*8kB (U) 0*16kB 0*32kB 0*64kB 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 1*2048kB (U) 0*4096kB = 3556kB
[ 143.222115] Node 0 Normal: 9843*4kB (UME) 8861*8kB (UME) 2839*16kB (UME) 1770*32kB (UME) 835*64kB (UME) 420*128kB (UME) 214*256kB (UME) 71*512kB (ME) 36*1024kB (UME) 14*2048kB (UME) 4454*4096kB (ME) = 18719780kB
[ 143.222124] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[ 143.222125] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[ 143.222126] 1215680 total pagecache pages
[ 143.222127] 0 pages in swap cache
[ 143.222127] Swap cache stats: add 0, delete 0, find 0/0
[ 143.222128] Free swap = 8388604kB
[ 143.222129] Total swap = 8388604kB
[ 143.222129] 8197154 pages RAM
[ 143.222130] 0 pages HighMem/MovableOnly
[ 143.222130] 170006 pages reserved
[ 143.222131] 0 pages cma reserved
[ 143.222131] 0 pages hwpoisoned
[ 143.292958] amdgpu 0000:67:00.0: amdgpu: 000000009d692800 pin failed
[ 143.292964] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12
[ 143.396867] amdgpu 0000:67:00.0: amdgpu: 00000000d10f4251 pin failed
[ 143.396873] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12
3 months, 3 weeks
Epiphany doesn't play webm ?
by Frederic Muller
Hi!
As the title says. I tried opening the direct link to the video and it
kind of opened, though I have mainly the sound as the video doesn't seem
to move.
I looked for more details online, install all the rpmfusion video
packages, it doesn't seem to have changed anything.
Any further idea?
Thank you.
Fred
3 months, 4 weeks
Chromium doesn't respond to clicks or typing in 1 external monitor
by Frederic Muller
Hi!
This one is really weird and probably too specific:
I start chromium and move it to my lower left monitor (I have 4
screens). I can do nothing with it.
I move it back to either center (the primary display) or even the upper
left monitor and can type or click. I then move it to the lower left
monitor back and then it's working.
As I said this really is weird. But if anyone is interested I can file a
bug and do further testing.
Thank you.
Fred
4 months
