The notebook does not run very stable and robust: on console no reaction with yay - what to do now?

General system Kernel, boot, graphics & hardware
1

dear friends

the notebook does not run very stable and robust: on console no reaction with yay - what to do now?

which options do we have.

in fact: if i add yay in console - nothing happens!

look forward to hear from you

btw: if i am trying to restart - i get the following

image
image1599×899 124 KB

the system does not want to shut down…

i just tried to start the system with another option -

note we ve got three lines in the start menu
one is with “so called” “initframes” - i used this opton to start the system

while doing so - i am able to do a update with yay

i will have a closer llook what happens - i iwll keep you posted

2

aah…THE NOTEBOOK!
:crystal_ball:

Yes yes, i see…i see complete and total lack of any info on it! :rofl:
How about some of this? :upside_down_face:

inxi -Faz

P.S. but still just wait a bit, maybe it will finish :man_shrugging: if not and you have none of that [Tip] Enable Magic SysRq Key (REISUB) (which you should) - then hard reset and try to boot again to share you info…as well as try to do full system update.

If it fails - you may boot from live USB or something…

Also see:

journalctl -p3 -xb

As well as previous boot:

journalctl -p3 -xb -1
1 Like
3

note - i did some furhter investigations and currently i am updating
i will come back and keep you informed

4

did an update - see here

5

Ok now try to reboot and see if issue is still there

2 Likes
6

well to be frank - if i try to do a newstart
i have the same behaviour in the shutdown process - see the last line in the image above

a stop-job is running for network manager - this alternates with
a stop-job is running for WPA Supplicant

this is very weird - i cannot run down - or restart… without pressing the power button!?

7

What about journal?

1 Like
8

i will stop the notebook and restart - then i will run these comands in in the terminal

just wait

9

Yeah and next time you boot - please do REISUB, hard reset ain’t best thing do…It’s safe way to restart when something (always) go wrong :upside_down_face:

10

well hopefully

i hope that we can get the thing up and running again…

11

Link i have before, read it - do it.

This way you won’t hurt your system while doing hard resets, just enable it and press sequence of those keys if you need to shutdown / reboot in some extra-ordinary case like that.

1 Like
12

That network stuff ain’t lookin’ good…
Maybe @dalto or @joekamprad could help?

1 Like
13

looks a bit like a network device driver went nuts and causing hung and block…

inxi -Naz | eos-sendlog please @otrott

14

now i run your command

jst wait


`inxi -Naz | eos-sendlog`

hi there good day dear Joe - see first of all the journal
and i will run your command right now

[heike@tp14 ~]$ journalctl -p3 -xb
Dez 15 22:05:02 tp14 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.WMI6], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 15 22:05:02 tp14 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 15 22:05:03 tp14 kernel: ACPI Error: No handler for Region [ECSI] (000000002ca11a62) [EmbeddedControl] (20230628/evregion-130)
Dez 15 22:05:03 tp14 kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261)
Dez 15 22:05:03 tp14 kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 15 22:05:03 tp14 kernel: ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 15 22:05:03 tp14 kernel: ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
Dez 15 22:05:10 tp14 wpa_supplicant[585]: bgscan simple: Failed to enable signal strength monitoring
Dez 15 22:05:54 tp14 wpa_supplicant[585]: bgscan simple: Failed to enable signal strength monitoring
[heike@tp14 ~]$ journalctl -p3 -xb -1
Dez 15 21:28:28 tp14 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.WMI6], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 15 21:28:28 tp14 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 15 21:28:29 tp14 kernel: ACPI Error: No handler for Region [ECSI] (00000000c6714492) [EmbeddedControl] (20230628/evregion-130)
Dez 15 21:28:29 tp14 kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261)
Dez 15 21:28:29 tp14 kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 15 21:28:29 tp14 kernel: ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 15 21:28:29 tp14 kernel: ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
Dez 15 21:28:35 tp14 wpa_supplicant[564]: bgscan simple: Failed to enable signal strength monitoring
Dez 15 21:48:55 tp14 kernel: INFO: task NetworkManager:478 blocked for more than 122 seconds.
Dez 15 21:48:55 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:48:55 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:48:55 tp14 kernel: INFO: task wpa_supplicant:564 blocked for more than 122 seconds.
Dez 15 21:48:55 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:48:55 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:50:57 tp14 kernel: INFO: task kworker/9:1:124 blocked for more than 122 seconds.
Dez 15 21:50:58 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:50:58 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:50:58 tp14 kernel: INFO: task NetworkManager:478 blocked for more than 245 seconds.
Dez 15 21:50:58 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:50:58 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:50:58 tp14 kernel: INFO: task wpa_supplicant:564 blocked for more than 245 seconds.
Dez 15 21:50:58 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:50:58 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:50:58 tp14 kernel: INFO: task kworker/u24:1:7365 blocked for more than 122 seconds.
Dez 15 21:50:58 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:50:58 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:50:58 tp14 kernel: INFO: task kworker/6:0:7905 blocked for more than 122 seconds.
Dez 15 21:50:58 tp14 kernel:       Not tainted 6.6.5-arch1-1 #1
Dez 15 21:50:58 tp14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 15 21:52:40 tp14 kernel: watchdog: watchdog0: watchdog did not stop!
[heike@tp14 ~]$

and now i run your command - just wait and see in some seconds

16

see this output

[heike@tp14 ~]$ inxi -Naz | eos-sendlog 
https://0x0.st/HYcf.txt
[heike@tp14 ~]$

what can i do now - should i run more commands

17

system also not fully updated… shows outdated kernel in the log.

Heikes notebook … not good :wink:

Is it using wireless or wired connection to Network?
A s it shows Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet

1 Like
18

hi it uses wireless

should i run some extra commands!?