You are not logged in.

#1 2020-09-23 22:38:39

samobot
Member
Registered: 2020-09-03
Posts: 6

System crashing under normal use

This is my first post on the forums

After having installed arch for about a week I noticed that it would sometimes completely crash.  After a crash I cannot access virtual console or even send sysrequests.

I have had it installed now for about 2 months

My Specs are
CPU - Ryzen 5 2400g
GPU - Nvidia gtx 1060
RAM - 16gb

While researching I saw that disabling c-states fixed random crashes for some Ryzen users, but this was of no avail for me.  The crashes seem to be more prone under some software, in my case Android Studio and using online video calling services like Microsoft Teams or Google Meets, however I have had crashes under any set of software that I use.

I tried to use journalctl to see logs but I can't figure out what parameters to use to see the right information.

Any help is appreciated!

Last edited by samobot (2020-09-23 22:41:28)

Offline

#2 2020-09-23 22:46:10

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: System crashing under normal use

What options did you try for journalctl?

Offline

#3 2020-09-23 23:07:04

samobot
Member
Registered: 2020-09-03
Posts: 6

Re: System crashing under normal use

After a crash I did journalctl -b -1 -p err

it's output was

Sep 23 09:19:08 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.SMIC], AE_ALREADY_EXISTS (20200528/dswload2-326)
Sep 23 09:19:08 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
Sep 23 09:19:08 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.SMIB], AE_ALREADY_EXISTS (20200528/dsfield-637)
Sep 23 09:19:08 arch kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.AFN7], AE_NOT_FOUND (20200528/psargs-330)
Sep 23 09:19:08 arch kernel: ACPI Error: Aborting method \AFN7 due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
Sep 23 09:19:08 arch kernel: ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
Sep 23 09:19:08 arch kernel: ACPI Error: Evaluating _BCM failed (20200528/video-357)
Sep 23 09:19:11 arch kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Sep 23 09:19:11 arch kernel: usb 3-2: 3:1: cannot get freq at ep 0x86
Sep 23 09:19:12 arch kernel: usb 3-2: 3:2: cannot get freq at ep 0x86
Sep 23 09:19:12 arch kernel: usb 3-2: 3:3: cannot get freq at ep 0x86
Sep 23 09:19:48 arch gdm-password][743]: gkr-pam: unable to locate daemon control file
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000061:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x8000000a:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000020:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000020:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000020:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000009:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000007:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000007:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000000:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000000:0x0, last cmd=0x1f000a
Sep 23 12:01:42 arch kernel: snd_hda_intel 0000:10:00.1: azx_get_response timeout, switching to single_cmd mode: last cmd=0x001f000b
Sep 23 12:02:43 arch systemd-coredump[5129]: Process 3251 (qemu-system-x86) of user 1000 dumped core.
                                             
                                             Stack trace of thread 3859:
                                             #0  0x00007f7ac956f743 n/a (n/a + 0x0)
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xaa0000
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xaa0000
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x11:0x0, last cmd=0xaa0000
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa24011
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x4011:0x0, last cmd=0xaa0000
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa24015
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x4015:0x0, last cmd=0xaa0000
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa24017
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x3:0x0, last cmd=0xa72402
Sep 23 12:05:05 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa72402
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x3:0x0, last cmd=0x573500
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0x5f0700
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x40:0x0, last cmd=0x570700
Sep 23 12:05:11 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0x570700
Sep 23 13:03:03 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000000:0x0, last cmd=0x4f0900
Sep 23 13:03:03 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000000:0x0, last cmd=0x5f0900
Sep 23 13:03:03 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0x4f0900
Sep 23 13:03:03 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0x5f0900
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0xc0000000:0x0, last cmd=0x5f0015
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x3:0x0, last cmd=0x573500
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x0:0x0, last cmd=0x5f2e08
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x5f:0x0, last cmd=0x5f2f00
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000010:0x0, last cmd=0x5f2f01
Sep 23 13:13:52 arch kernel: snd_hda_intel 0000:10:00.1: spurious response 0x80000000:0x0, last cmd=0x5f2f02

Last edited by samobot (2020-09-24 02:23:10)

Offline

#4 2020-09-23 23:12:03

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: System crashing under normal use

Please use code tags for commands and their outputs.  Filtering by priority removes context.
Please post the output of ` journalctl -b -1` assuming the last boot was one with a crash.  If it is too big for code tags see the tip box from pastebin to pipe the output to a pastebin.

Offline

#5 2020-09-23 23:24:51

samobot
Member
Registered: 2020-09-03
Posts: 6

Re: System crashing under normal use

http://sprunge.us/XSYDIm here is a pastebin with the log, also how do you use code tags?

Offline

#6 2020-09-23 23:28:49

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: System crashing under normal use

See the bbcode link below every post box.
Edit:
Nothing in the journal from the hang.

Last edited by loqs (2020-09-23 23:30:06)

Offline

Board footer

Powered by FluxBB