Help with Errors

General system Newbie
1

Hi, So I’ve been using EndOs for couple off days now and have a pretty good feeling that i’m gonna settle for this. But I need your help here.
So I was just checking the Jornal ctl logs for any errors and came across these what are all those errors and why doesn’t it shows me beyond line 1-17. Please help me fix this. I don’t want to reinstall everything from beginning.

[kundan@EndeavourPC ~]$ journalctl -p 3 -b
Apr 29 02:46:12 EndeavourPC kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Apr 29 02:46:15 EndeavourPC kernel: [drm:r600_ring_test [radeon]] *ERROR* radeo>
Apr 29 02:46:15 EndeavourPC kernel: radeon 0000:01:00.0: disabling GPU accelera>
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus>
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus>
Apr 29 02:46:30 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCI>
Apr 29 02:46:30 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* eve>
Apr 29 02:46:41 EndeavourPC gdm-password][1120]: gkr-pam: unable to locate daem>
Apr 29 02:46:53 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCI>
Apr 29 02:46:53 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* eve>
Apr 29 02:46:54 EndeavourPC gdm-launch-environment][818]: GLib-GObject: g_objec>
Apr 29 02:47:02 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCI>
Apr 29 02:47:02 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* eve>
Apr 29 02:48:20 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCI>
Apr 29 02:48:20 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* eve>
Apr 29 02:48:55 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCI>
Apr 29 02:48:55 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* eve>
lines 1-17/17 (END)...skipping...
Apr 29 02:46:12 EndeavourPC kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Apr 29 02:46:15 EndeavourPC kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Apr 29 02:46:15 EndeavourPC kernel: radeon 0000:01:00.0: disabling GPU acceleration
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 29 02:46:30 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:46:30 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:46:41 EndeavourPC gdm-password][1120]: gkr-pam: unable to locate daemon control file
Apr 29 02:46:53 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:46:53 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:46:54 EndeavourPC gdm-launch-environment][818]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 29 02:47:02 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:47:02 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:48:20 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:48:20 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:48:55 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:48:55 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-17/17 (END)






































Apr 29 02:46:12 EndeavourPC kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Apr 29 02:46:15 EndeavourPC kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Apr 29 02:46:15 EndeavourPC kernel: radeon 0000:01:00.0: disabling GPU acceleration
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 29 02:46:27 EndeavourPC gnome-session-binary[873]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 29 02:46:30 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:46:30 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:46:41 EndeavourPC gdm-password][1120]: gkr-pam: unable to locate daemon control file
Apr 29 02:46:53 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:46:53 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:46:54 EndeavourPC gdm-launch-environment][818]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 29 02:47:02 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:47:02 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:48:20 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:48:20 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Apr 29 02:48:55 EndeavourPC kernel: radeon 0000:01:00.0: No VRAM object for PCIE GART.
Apr 29 02:48:55 EndeavourPC kernel: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-17/17 (END)
2

This is normally where you pick one and search the Web for the text. It’s not really fair to expect someone to pick through a wall of log output and explain each line in turn?

There are no lines beyond line 17. That is the last line of output.

These lines are truncated so are much less useful anyway.

These lines are not truncated and so are more useful - and have text that is eminently searchable.

Help us, help you.

Why would you do that if everything is working? :thinking:

6 Likes
3

Sorry but I did a check on that but what I found is

radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Found this
https://bugzilla.kernel.org/show_bug.cgi?id=196197

radeon 0000:01:00.0: disabling GPU acceleration
https://bbs.archlinux.org/viewtopic.php?id=139716

and similarly for others too but only If I’d knew and understood what has to be done with that would have followed the article and not been asking for help here. I’m complete newbie to Linux and still learning I don’t know what exactly to look for to solve this. So thanks anyways

4

If your system is working fine, what do you need to solve?
Or is there any issue with your system?

1 Like
5

My system is working fine. But I was reading a maintenance post where I found to check journalctl for logs errors and to get it solved or it would pile up or something and complicate things later.

See exactly that’s what I’m trying to understand here that If those errors shown are something to be worried about or can be ignored and How it works.

6

I check for journalctl only when I have error. I don’t know about others.

7

I do have error and have created a separate post (regarding wifi issues) for that coz can’t post multiple issues in one post. So while troubleshooting that I came across this and checked and found Journlctl logs errors. Also fixed some of them myself like one caused by TLP and had to reinstall and restart the service. And only asked for few which I didn’t knew if that is something to ignore or to be solved.

8

Ignore it; If it ain’t broke, don’t try to fix it :wink:

btw, @Kundan welcome aboard :enos: and enjoy!

1 Like
9

OK Thanks.

1 Like
10

Here is my journal https://clbin.com/heooG Everythng works. Gnome 42 has to patch a few thngs, but everythng works.

1 Like
11

Thanks for helping out It’s just that I’m pretty new to this stuff and recently switched to Linux so still learning so that’s why I’m not aware what can be ignored and whats an actual error.

12

Congratulations :partying_face: You won’t look back on your decision.

1 Like
13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.