I ran a journalctl -p 3 -xb command and found many errors

AWSUMWarrior · 2021-03-03 16:03:16

Hello, I installed Arch Linux about few weeks ago, and I am using NViDia as my default graphics card. My friend told me to run this journalctl -p 3 -xb command, and I found many errors. I was wondering if you guys could help me fix them.

Here is the output:

-- Journal begins at Thu 2021-02-18 15:21:17 CST, ends at Wed 2021-03-03 09:51:30 CST. --
Mar 03 09:41:15 mohorog kernel: x86/cpu: SGX disabled by BIOS
Mar 03 09:41:15 mohorog kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._E4A], AE_ALREADY_EXISTS (20201113/dswload2-326)
Mar 03 09:41:15 mohorog kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-220)
Mar 03 09:41:15 mohorog kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._E47], AE_ALREADY_EXISTS (20201113/dswload2-326)
Mar 03 09:41:15 mohorog kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20201113/psobject-220)
Mar 03 09:41:15 mohorog kernel: 
Mar 03 09:41:17 mohorog kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Mar 03 09:41:17 mohorog kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Mar 03 09:41:17 mohorog kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Mar 03 09:41:19 mohorog systemd-coredump[571]: Process 513 (Xorg) of user 0 dumped core.
                                               
                                               Stack trace of thread 513:
                                               #0  0x00007f31cb13cef5 raise (libc.so.6 + 0x3cef5)
                                               #1  0x00007f31cb126862 abort (libc.so.6 + 0x26862)
                                               #2  0x000055b1578a86ea OsAbort (Xorg + 0x14a6ea)
                                               #3  0x000055b1578aa1b1 FatalError (Xorg + 0x14c1b1)
                                               #4  0x000055b1578afe09 n/a (Xorg + 0x151e09)
                                               #5  0x00007f31cb13cf80 __restore_rt (libc.so.6 + 0x3cf80)
                                               #6  0x00007f31cb13cef5 raise (libc.so.6 + 0x3cef5)
                                               #7  0x00007f31cb126862 abort (libc.so.6 + 0x26862)
                                               #8  0x00007f31cb126747 __assert_fail_base.cold (libc.so.6 + 0x26747)
                                               #9  0x00007f31cb135646 __assert_fail (libc.so.6 + 0x35646)
                                               #10 0x000055b1577f3870 n/a (Xorg + 0x95870)
                                               #11 0x00007f31c5fddfb9 glamor_init (libglamoregl.so + 0xcfb9)
                                               #12 0x00007f31c61710fd n/a (modesetting_drv.so + 0x140fd)
                                               #13 0x000055b1577d740e AddGPUScreen (Xorg + 0x7940e)
                                               #14 0x000055b1578e3eb9 n/a (Xorg + 0x185eb9)
                                               #15 0x000055b157919288 n/a (Xorg + 0x1bb288)
                                               #16 0x000055b15791952b n/a (Xorg + 0x1bb52b)
                                               #17 0x000055b1578c9435 InitInput (Xorg + 0x16b435)
                                               #18 0x000055b157797798 n/a (Xorg + 0x39798)
                                               #19 0x00007f31cb127b25 __libc_start_main (libc.so.6 + 0x27b25)
                                               #20 0x000055b1577985de _start (Xorg + 0x3a5de)
                                               
                                               Stack trace of thread 567:
                                               #0  0x00007f31caffa9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                                               #1  0x00007f31caff4260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                                               #2  0x00007f31c4b84cec n/a (iris_dri.so + 0x4edcec)
                                               #3  0x00007f31c4b834c8 n/a (iris_dri.so + 0x4ec4c8)
                                               #4  0x00007f31cafee299 start_thread (libpthread.so.0 + 0x9299)
                                               #5  0x00007f31cb1ff053 __clone (libc.so.6 + 0xff053)
                                               
                                               Stack trace of thread 568:
                                               #0  0x00007f31caffa9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                                               #1  0x00007f31caff4260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                                               #2  0x00007f31c4b84cec n/a (iris_dri.so + 0x4edcec)
                                               #3  0x00007f31c4b834c8 n/a (iris_dri.so + 0x4ec4c8)
                                               #4  0x00007f31cafee299 start_thread (libpthread.so.0 + 0x9299)
                                               #5  0x00007f31cb1ff053 __clone (libc.so.6 + 0xff053)
                                               
                                               Stack trace of thread 566:
                                               #0  0x00007f31caffa9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                                               #1  0x00007f31caff4260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                                               #2  0x00007f31c4b84cec n/a (iris_dri.so + 0x4edcec)
                                               #3  0x00007f31c4b834c8 n/a (iris_dri.so + 0x4ec4c8)
                                               #4  0x00007f31cafee299 start_thread (libpthread.so.0 + 0x9299)
                                               #5  0x00007f31cb1ff053 __clone (libc.so.6 + 0xff053)
                                               
                                               Stack trace of thread 569:
                                               #0  0x00007f31caffa9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                                               #1  0x00007f31caff4260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                                               #2  0x00007f31c4b84cec n/a (iris_dri.so + 0x4edcec)
                                               #3  0x00007f31c4b834c8 n/a (iris_dri.so + 0x4ec4c8)
                                               #4  0x00007f31cafee299 start_thread (libpthread.so.0 + 0x9299)
                                               #5  0x00007f31cb1ff053 __clone (libc.so.6 + 0xff053)
░░ Subject: Process 513 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
░░ Documentation: man:core(5)
░░ 
░░ Process 513 (Xorg) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Mar 03 09:41:19 mohorog sddm[505]: Failed to read display number from pipe
lines 21-76/76 (END)

Last edited by AWSUMWarrior (2021-03-03 16:26:47)

V1del · 2021-03-03 16:06:44

Please wrap outputs in

[code]code tags[/code]

everything other than the xorg dump is normal and harmless, What effect did the xorg dump have? Do you have trouble starting xorg or was this a one off occurrence?

AWSUMWarrior · 2021-03-03 16:35:00

V1del wrote:

Please wrap outputs in
[code]code tags[/code]
everything other than the xorg dump is normal and harmless, What effect did the xorg dump have? Do you have trouble starting xorg or was this a one off occurrence?

I am using Plasma for my Arch Linux. I have no trouble using Linux when I try booting it in. I have tried this command, and the errors are always there, so it is not a one off thing. There is one issue I do have with a display. Whenever I leave my laptop idle, the display becomes black and I can't access anything. That is the only display issue I have.

seth · 2021-03-03 19:59:48

The backtrace is in the modesetting driver while the server also deals with the intel chip, so this is most likely an optimus setup.
=> How did you configure it?

Please post
a) your xorg log, https://wiki.archlinux.org/index.php/Xorg#General
b) the complete system journal for the boot (sudo journalctl -b)

the journal excerpt wrote:

Mar 03 09:41:17 mohorog kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000

https://bbs.archlinux.org/viewtopic.php … 7#p1932897

AWSUMWarrior · 2021-03-06 01:39:08

seth wrote:

The backtrace is in the modesetting driver while the server also deals with the intel chip, so this is most likely an optimus setup.
=> How did you configure it?
Please post
a) your xorg log, https://wiki.archlinux.org/index.php/Xorg#General
b) the complete system journal for the boot (sudo journalctl -b)
the journal excerpt wrote:
Mar 03 09:41:17 mohorog kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
https://bbs.archlinux.org/viewtopic.php … 7#p1932897

This is the xorg log: http://ix.io/2RPP

I configured it to be NVIDIA only. I am using the NVIDIA proprietary drivers. I follow the steps from this page from the Arch WIki:

https://wiki.archlinux.org/index.php/NV … phics_only

Here is the output of the sudo journal -b:

http://sprunge.us/KSoEfy

seth · 2021-03-06 07:14:17

You're using the intel chip as crtc since no output is wired directly to the nvidia one.

The only coredumps in the provided journal are from minecraft, so it does not reflect the coredump in the OP.

Arch Linux

#1 2021-03-03 16:03:16

I ran a journalctl -p 3 -xb command and found many errors

#2 2021-03-03 16:06:44

Re: I ran a journalctl -p 3 -xb command and found many errors

#3 2021-03-03 16:35:00

Re: I ran a journalctl -p 3 -xb command and found many errors

#4 2021-03-03 19:59:48

Re: I ran a journalctl -p 3 -xb command and found many errors

#5 2021-03-06 01:39:08

Re: I ran a journalctl -p 3 -xb command and found many errors

#6 2021-03-06 07:14:17

Re: I ran a journalctl -p 3 -xb command and found many errors

Board footer