Linux

62508 readers

415 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Laptop randomly freezes. How to debug it? (feddit.dk)

submitted 1 day ago by drillepind42@feddit.dk to c/linux@lemmy.ml

29 comments fedilink hide all child comments

Hi all, sorry if I post this the wrong place.

I have a laptop running mint with qtile which sometimes freezes. To the point where nothing responds and I need to kill it. I've tried: sudo journalctl But I don't get any information which helps me.

Can anyone help to debug it?

you are viewing a single comment's thread
view the rest of the comments

[–] A_norny_mousse@piefed.zip 2 points 1 day ago (6 children)

Since you specifically mention qtile you should undo your customizations and see if that fixes your problem?

If not, you should look at the journal after reboot:

journalctl -b

But you'll need to filter it.

Try journalctl -b | grep -v rtkit-daemon, which will remove the masses of entries you bemoaned in another comment (AFAICS all syslog entries should also be in the journal anyhow).

Very important:
Please make note of when the problem happened, and if your journal entries even go that far in time.

[–] drillepind42@feddit.dk 1 points 1 day ago (2 children)

journalctl -b | grep -v rtkit-daemon

I just got the following freeze that it recovered from by itself (rarely happens). After filtering the log a bit I get the following from around the time it happened.

Feb 07 00:00:58 tuxedo systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Feb 07 00:00:58 tuxedo systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Feb 07 00:00:58 tuxedo systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Feb 07 00:00:58 tuxedo systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Feb 07 00:58:35 tuxedo kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=780519, emitted seq=780521
Feb 07 00:58:35 tuxedo kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process floorp pid 1548 thread floorp:cs0 pid 1606
Feb 07 00:58:35 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: GPU reset begin!
Feb 07 00:58:35 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:35 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:35 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:35 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:36 tuxedo kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 07 00:58:36 tuxedo kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 07 00:58:37 tuxedo kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: MODE2 reset
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: GPU reset succeeded, trying to resume
Feb 07 00:58:37 tuxedo kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: SMU is resuming...
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: SMU is resumed successfully!
Feb 07 00:58:37 tuxedo kernel: [drm] DMUB hardware initialized: version=0x08000500
Feb 07 00:58:37 tuxedo kernel: [drm] DPIA AUX failed on 0x600(1), error 7
Feb 07 00:58:37 tuxedo kernel: [drm] DPIA AUX failed on 0x600(1), error 7
...
Feb 07 00:58:37 tuxedo kernel: [drm] DPIA AUX failed on 0x600(1), error 7
Feb 07 00:58:37 tuxedo kernel: [drm] DPIA AUX failed on 0x600(1), error 7
Feb 07 00:58:37 tuxedo kernel: [drm] kiq ring mec 3 pipe 1 q 0
Feb 07 00:58:37 tuxedo kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 1
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 1
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: recover vram bo from shadow start
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: recover vram bo from shadow done
Feb 07 00:58:37 tuxedo kernel: [drm] ring gfx_32775.1.1 was added
Feb 07 00:58:37 tuxedo kernel: [drm] ring compute_32775.2.2 was added
Feb 07 00:58:37 tuxedo kernel: [drm] ring sdma_32775.3.3 was added
Feb 07 00:58:37 tuxedo kernel: [drm] ring gfx_32775.1.1 test pass
Feb 07 00:58:37 tuxedo kernel: [drm] ring gfx_32775.1.1 ib test pass
Feb 07 00:58:37 tuxedo kernel: [drm] ring compute_32775.2.2 test pass
Feb 07 00:58:37 tuxedo kernel: [drm] ring compute_32775.2.2 ib test pass
Feb 07 00:58:37 tuxedo kernel: [drm] ring sdma_32775.3.3 test pass
Feb 07 00:58:37 tuxedo kernel: [drm] ring sdma_32775.3.3 ib test pass
Feb 07 00:58:37 tuxedo kernel: amdgpu 0000:65:00.0: amdgpu: GPU reset(2) succeeded!
``'

[–] A_norny_mousse@piefed.zip 3 points 21 hours ago (1 children)

Nice, that looks pretty obvious.

In addition to the other reply, you should search around your distro* having problems with (certain) AMD gpus; maybe all you need is a backported kernel.

* I don't think you ever mentioned. If it's Ubuntu-based, search for Ubuntu.

[–] drillepind42@feddit.dk 2 points 20 hours ago (1 children)

I use linux mint debian edition (LMDE)

[–] unwillingsomnambulist@midwest.social 1 points 8 hours ago

Could it be a CPU/iGPU too new for the kernel LMDE is running? I haven’t used LMDE in a while, so I imagine that if it’s still based on bookworm the in-kernel drivers could be too old. If it’s trixie-based that probably isn’t the problem though.

[–] FishFace@piefed.social 2 points 1 day ago

Looks like the chipset/graphics driver is crashing. That can be because of the driver or the hardware.

It will be hard to diagnose, but you can search for the most detailed of those log lines together with your laptop model and see if that yields anything. There problem is that it's never possible to know whether you have a software issue or a hardware issue that is exposed by particular software.

You can try installing a completely different os (i.e windows) to see if the same problem occurs - if it does you can be fairly sure it's hardware.

load more comments (3 replies)