laptop keeps crashing

abderrahm3n · 2023-07-14 00:06:51

out of nowhere and without any indices .
i tried to find the cause ,first i thought it was bc of heat (it was very hot when that happened and it was first time)
after that it did it multiple times so i went on this forum and saw that i am not the only one ,there is a post in laptop issues that suggested to update but mine is good in terms of bios [https://bbs.archlinux.org/viewtopic.php?id=286932]
and yeah a week ago it was working perfectly (for me)
journelctl shows this as the last secondes before the forced shutdown by me

Jul 14 00:51:18 archlinux systemd[409]: Created slice User Application Slice.
Jul 14 00:51:18 archlinux systemd[409]: Reached target Paths.
Jul 14 00:51:18 archlinux systemd[409]: Reached target Timers.
Jul 14 00:51:18 archlinux systemd[409]: Starting D-Bus User Message Bus Socket...
Jul 14 00:51:18 archlinux systemd[409]: Listening on GnuPG network certificate management daemon.
Jul 14 00:51:18 archlinux systemd[409]: Listening on GCR ssh-agent wrapper.
Jul 14 00:51:18 archlinux systemd[409]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 14 00:51:18 archlinux systemd[409]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 14 00:51:18 archlinux systemd[409]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 14 00:51:18 archlinux systemd[409]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 14 00:51:18 archlinux systemd[409]: Listening on p11-kit server.
Jul 14 00:51:18 archlinux systemd[409]: Listening on PipeWire PulseAudio.
Jul 14 00:51:18 archlinux systemd[409]: Listening on PipeWire Multimedia System Socket.
Jul 14 00:51:18 archlinux systemd[409]: Listening on D-Bus User Message Bus Socket.
Jul 14 00:51:18 archlinux systemd[409]: Reached target Sockets.
Jul 14 00:51:18 archlinux systemd[409]: Reached target Basic System.
Jul 14 00:51:18 archlinux systemd[409]: Reached target Main User Target.
Jul 14 00:51:18 archlinux systemd[409]: Startup finished in 924ms.
Jul 14 00:51:18 archlinux systemd[1]: Started User Manager for UID 1000.
Jul 14 00:51:18 archlinux systemd[1]: Started Session 1 of User abderrahm3n.
Jul 14 00:51:23 archlinux kernel: [drm] PCIE gen 2 link speeds already enabled
Jul 14 00:51:23 archlinux kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000162000).
Jul 14 00:51:23 archlinux kernel: radeon 0000:01:00.0: WB enabled
Jul 14 00:51:23 archlinux kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
Jul 14 00:51:23 archlinux kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
Jul 14 00:51:23 archlinux kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118
Jul 14 00:51:23 archlinux kernel: debugfs: File 'radeon_ring_gfx' in directory '1' already present!
Jul 14 00:51:23 archlinux kernel: debugfs: File 'radeon_ring_dma1' in directory '1' already present!
Jul 14 00:51:23 archlinux kernel: [drm] ring test on 0 succeeded in 2 usecs
Jul 14 00:51:23 archlinux kernel: [drm] ring test on 3 succeeded in 6 usecs
Jul 14 00:51:23 archlinux kernel: debugfs: File 'radeon_ring_uvd' in directory '1' already present!
Jul 14 00:51:23 archlinux kernel: [drm] ring test on 5 succeeded in 2 usecs
Jul 14 00:51:23 archlinux kernel: [drm] UVD initialized successfully.
Jul 14 00:51:23 archlinux kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Jul 14 00:51:23 archlinux kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Jul 14 00:51:24 archlinux kernel: [drm] ib test on ring 5 succeeded
Jul 14 00:51:29 archlinux systemd-timesyncd[317]: Contacted time server 196.10.52.57:123 (2.arch.pool.ntp.org).
Jul 14 00:51:29 archlinux systemd-timesyncd[317]: Initial clock synchronization to Fri 2023-07-14 00:51:29.079378 CET.
Jul 14 00:51:31 archlinux systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jul 14 00:51:33 archlinux systemd[409]: Created slice User Core Session Slice.
Jul 14 00:51:33 archlinux systemd[409]: Starting D-Bus User Message Bus...
Jul 14 00:51:33 archlinux systemd[409]: Started D-Bus User Message Bus.
Jul 14 00:51:40 archlinux dbus-daemon[479]: [session uid=1000 pid=479] Activating via systemd: service name='org.a11y.Bus' unit='at-spi>
Jul 14 00:51:40 archlinux systemd[409]: Starting Accessibility services bus...
Jul 14 00:51:41 archlinux dbus-daemon[479]: [session uid=1000 pid=479] Successfully activated service 'org.a11y.Bus'
Jul 14 00:51:41 archlinux systemd[409]: Started Accessibility services bus.
Jul 14 00:51:42 archlinux dbus-daemon[322]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.ser>
Jul 14 00:51:42 archlinux systemd[1]: Starting Authorization Manager...
Jul 14 00:51:42 archlinux polkitd[548]: Started polkitd version 122
Jul 14 00:51:42 archlinux polkitd[548]: Loading rules from directory /etc/polkit-1/rules.d
Jul 14 00:51:42 archlinux polkitd[548]: Loading rules from directory /usr/share/polkit-1/rules.d
Jul 14 00:51:42 archlinux polkitd[548]: Finished loading, compiling and executing 2 rules
Jul 14 00:51:42 archlinux dbus-daemon[322]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 14 00:51:42 archlinux systemd[1]: Started Authorization Manager.
Jul 14 00:51:42 archlinux polkitd[548]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jul 14 00:51:42 archlinux NetworkManager[387]: <info>  [1689292302.7483] agent-manager: agent[67726a5fe1bc56b5,:1.14/org.freedesktop.nm>
Jul 14 00:51:42 archlinux at-spi-bus-launcher[514]: dbus-daemon[514]: Activating service name='org.a11y.atspi.Registry' requested by ':>
Jul 14 00:51:42 archlinux at-spi-bus-launcher[514]: dbus-daemon[514]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 14 00:51:42 archlinux at-spi-bus-launcher[578]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 14 00:53:39 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:39 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:39 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:39 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:39 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:39 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:40 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:40 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:40 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:40 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:40 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:41 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:41 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:41 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:41 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:41 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:43 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:43 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:43 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:43 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:43 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
Jul 14 00:53:44 archlinux kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/>
Jul 14 00:53:44 archlinux kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
Jul 14 00:53:44 archlinux kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known

any help is appreciated .

seth · 2023-07-14 06:40:08

journelctl shows this as the last secondes before the forced shutdown by me

Does it (if you look at the timestamps)?
This seems to be only 2 minutes into the boot and if you "forced shutdown" with the power button, most of the journal won't be preserved.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'f:1=<-' ix.io

If you boot some live distro (grml, knoppix, ubuntu, whatever), does it suffer from the same "crash"?
What what are the actual symptoms of the "crash"?

abderrahm3n · 2023-07-17 09:53:26

i apologize for the late reply .
anyway ,when the pc crash,I literally cant do a single thing like no mouse no keyboard the only thing i can do is the forced shutdown (note that i tried to wait if it does solve itself but no )
now i dont know when the crash happens but the last time it didnt crashed so the cmd u gave me showed nothing
i will however when the crash happens next time ,
and i appreciate ur reply.

seth · 2023-07-17 13:32:05

seth wrote:

If you boot some live distro (grml, knoppix, ubuntu, whatever), does it suffer from the same "crash"?

I literally cant do a single thing like no mouse no keyboard the only thing i can do is the forced shutdown

Try https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

the last time it didnt crashed so the cmd u gave me showed nothing

The command will show a url that you'll please post to provide a general idea about the system.

abderrahm3n · 2023-07-19 17:23:42

hello
finally as i was trying to set up a connection between my laptop and my phone it crashed
https://pastebin.com/gRLUi0YM
here is the command u provided gave me

seth · 2023-07-19 21:10:33

Sorry, this was under the assumption you could draw it from the crashing boot.
If you had to reboot, you need to post the journal of the previous boot

sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io

(increasing "-1" to "-2"… will allow you to go back further if you rebooted multiple times since)

abderrahm3n · 2023-07-20 03:27:20

waiting for the next crash to happen then.

abderrahm3n · 2023-07-21 22:12:12

yoo i think the error is from the hdd that i am using since when i go to BIOS and run test on the disc i get an error so yeah
https://pastebin.com/6kHtasMN

seth · 2023-07-21 22:17:27

https://wiki.archlinux.org/title/SMART

sudo smartctl -a /dev/…

and probably run a long test.

The posted journal ends at

Jul 21 23:05:59 archlinux systemd-journald[195]: Time spent on flushing

so no meaningful journal for the boot was synced to disc.

abderrahm3n · 2023-07-21 22:36:06

here it is https://pastebin.com/WbbzfwCj
and i started the long test and it says 110 mn so yeah

seth · 2023-07-21 22:54:33

40 51 00 00 60 60 e0  Error: UNC at LBA = 0x00606000 = 6316032

197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       6

See whether the test failed at the same LBA, then https://wiki.archlinux.org/title/Badblocks
It is probably advisable to have backups of any personal data at this point.

abderrahm3n · 2023-07-21 22:56:43

so it is the hdd?

seth · 2023-07-21 23:02:27

There're indications for an issue w/ the HDD that warrent caution.
Whether the disk is toast and/or the cause of your crashes is to be seen.
First backup your personal data, then wait for the result of the selftest, post it.
Then you should run badblocks to clear the pending sectors and see how bad the situation actually is.

abderrahm3n · 2023-07-21 23:05:19

if i would to format it ,would it be good thing and just solve everything?

seth · 2023-07-21 23:10:33

That's akin t running badblocks in the destructive mode. ("format" in that sense isn't a thing anf mkfs doesn't write a lot to the disk)
It'll tell you how bad it is - if there're only 6 bad sectors and those get re-allocated you can test whether the disk stabilizes afterwards. But there's no way to predict that.
If the drive is falling apart, it's falling apart - no software will do anything about that.

* backups
* BACKUPS
* wait for the test to finish
* check smartctl -a again for the result
* run badblocks
* check smartctl -a again for the result

abderrahm3n · 2023-07-21 23:12:52

aaa now i understand appreciate it ,waiting for the test to finish and i dont really have that much of info on it wish is why i suggest formatting it .
thnx anyway appreciate it .

Arch Linux

#1 2023-07-14 00:06:51

laptop keeps crashing

#2 2023-07-14 06:40:08

Re: laptop keeps crashing

#3 2023-07-17 09:53:26

Re: laptop keeps crashing

#4 2023-07-17 13:32:05

Re: laptop keeps crashing

#5 2023-07-19 17:23:42

Re: laptop keeps crashing

#6 2023-07-19 21:10:33

Re: laptop keeps crashing

#7 2023-07-20 03:27:20

Re: laptop keeps crashing

#8 2023-07-21 22:12:12

Re: laptop keeps crashing

#9 2023-07-21 22:17:27

Re: laptop keeps crashing

#10 2023-07-21 22:36:06

Re: laptop keeps crashing

#11 2023-07-21 22:54:33

Re: laptop keeps crashing

#12 2023-07-21 22:56:43

Re: laptop keeps crashing

#13 2023-07-21 23:02:27

Re: laptop keeps crashing

#14 2023-07-21 23:05:19

Re: laptop keeps crashing

#15 2023-07-21 23:10:33

Re: laptop keeps crashing

#16 2023-07-21 23:12:52

Re: laptop keeps crashing

Board footer