I ran this but it seems to be either doing nothing or taking a very long time to do something after inxi -Fxzz. It’s yet to spit out a response
should not take much time. This may be another symptom of a hardware fault.
God that would really suck… Everything was working fine earlier this week on Windows 11, could I have busted something in the process of migrating to Linux?
Unlikely - software doesn’t tend to cause hardware issues as a rule. More than likely just bad luck.
Can you show us the journalctl -b 0 --no-hostname --no-pager | tail -n 50 if it’ll run.
rin@rinux:~$ journalctl -b 0 --no-hostname --no-pager | tail -n 50
Jul 03 17:40:30 PackageKit[19529]: daemon quit
Jul 03 17:40:30 systemd[1]: packagekit.service: Deactivated successfully.
Jul 03 17:40:30 systemd[1]: packagekit.service: Consumed 1.245s CPU time over 5min 6.150s wall clock time, 168.9M memory peak.
Jul 03 17:40:30 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 17:41:58 audit: BPF prog-id=188 op=LOAD
Jul 03 17:41:58 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 03 17:41:58 systemd[1]: Starting systemd-zram-setup@zram0.service - Create swap on /dev/zram0...
Jul 03 17:41:58 zram-generator[19830]: Error: Failed to configure disk size into /sys/block/zram0/disksize
Jul 03 17:41:58 zram-generator[19830]: Caused by:
Jul 03 17:41:58 zram-generator[19830]: Device or resource busy (os error 16)
Jul 03 17:41:58 systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 17:41:58 kernel: zram: Cannot change disksize for initialized device
Jul 03 17:41:58 systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'exit-code'.
Jul 03 17:41:58 systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Jul 03 17:41:58 systemd[1]: Dependency failed for dev-zram0.swap - Compressed Swap on /dev/zram0.
Jul 03 17:41:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 17:41:58 systemd[1]: dev-zram0.swap: Job dev-zram0.swap/start failed with result 'dependency'.
Jul 03 17:41:58 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jul 03 17:41:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 17:42:00 audit[19827]: AUDIT1100 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix acct="rin" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 audit[19827]: AUDIT1101 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix acct="rin" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 sudo[19827]: rin : TTY=pts/1 ; PWD=/home/rin ; USER=root ; COMMAND=/usr/sbin/cat /var/cache/akmods/nvidia/.last.log
Jul 03 17:42:00 audit[19827]: AUDIT1123 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/rin" cmd=636174202F7661722F63616368652F616B6D6F64732F6E76696469612F2E6C6173742E6C6F67 exe="/usr/bin/sudo" terminal=pts/1 res=success'
Jul 03 17:42:00 audit[19827]: AUDIT1110 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 systemd-logind[1119]: Existing logind session ID 3 used by new audit session, ignoring.
Jul 03 17:42:00 systemd-logind[1119]: New session 'c18' of user 'root' with class 'user-early' and type 'tty'.
Jul 03 17:42:00 systemd[1]: Started session-c18.scope - Session c18 of User root.
Jul 03 17:42:00 systemd[1]: Starting systemd-zram-setup@zram0.service - Create swap on /dev/zram0...
Jul 03 17:42:00 sudo[19827]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
Jul 03 17:42:00 audit[19827]: AUDIT1105 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 sudo[19827]: pam_unix(sudo:session): session opened for user root(uid=0) by rin(uid=1000)
Jul 03 17:42:00 sudo[19827]: pam_unix(sudo:session): session closed for user root
Jul 03 17:42:00 audit[19827]: AUDIT1106 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 audit[19827]: AUDIT1104 pid=19827 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo" hostname=rinux addr=? terminal=/dev/pts/1 res=success'
Jul 03 17:42:00 systemd[1]: session-c18.scope: Deactivated successfully.
Jul 03 17:42:00 zram-generator[19842]: Error: Failed to configure disk size into /sys/block/zram0/disksize
Jul 03 17:42:00 zram-generator[19842]: Caused by:
Jul 03 17:42:00 zram-generator[19842]: Device or resource busy (os error 16)
Jul 03 17:42:00 systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 17:42:00 systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'exit-code'.
Jul 03 17:42:00 kernel: zram: Cannot change disksize for initialized device
Jul 03 17:42:00 systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Jul 03 17:42:00 systemd[1]: Dependency failed for dev-zram0.swap - Compressed Swap on /dev/zram0.
Jul 03 17:42:00 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 03 17:42:00 systemd[1]: dev-zram0.swap: Job dev-zram0.swap/start failed with result 'dependency'.
Jul 03 17:42:00 systemd-logind[1119]: Session c18 logged out. Waiting for processes to exit.
Jul 03 17:42:00 systemd-logind[1119]: Removed session c18.
Jul 03 17:42:28 systemd[1]: fprintd.service: Deactivated successfully.
Jul 03 17:42:28 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 03 17:42:28 audit: BPF prog-id=188 op=UNLOAD
You could try inxi -Fxxz --debug 3 which should at least give an idea of where it’s getting stuck.
rin@rinux:~$ inxi -Fxxz --debug 3
Start: Function: CheckTools::set
Args:
Elapsed: 0.01369
Start: Function: main::grabber
Args: /sbin/dmidecode -t chassis -t baseboard -t processor 2>&1;
Elapsed: 0.020845
Elapsed: 0.022258
End: Function: main::grabber
Elapsed: 0.029594
End: Function: CheckTools::set
Start: Function: main::set_colors
Args:
Elapsed: 0.029691
Start: Function: main::set_color_scheme
Args: 2;
Elapsed: 0.029745
Start: Function: main::get_color_scheme
Args: 2;
Elapsed: 0.029807
Elapsed: 0.02991
End: Function: main::get_color_scheme
Elapsed: 0.029949
End: Function: main::set_color_scheme
Elapsed: 0.02998
End: Function: main::set_colors
Start: Function: OutputGenerator::generate
Args:
Elapsed: 0.030033
Start: Function: PsData::set
Args:
Elapsed: 0.030079
Start: Function: main::grabber
Args: /sbin/ps wwaux 2>/dev/null; ; strip; ref;
Elapsed: 0.03013
smells like a RAM issue from this:
Jul 03 17:42:00 zram-generator[19842]: Error: Failed to configure disk size into /sys/block/zram0/disksize
Jul 03 17:42:00 zram-generator[19842]: Caused by:
Jul 03 17:42:00 zram-generator[19842]: Device or resource busy (os error 16)
Jul 03 17:42:00 systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 17:42:00 systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'exit-code'.
Jul 03 17:42:00 kernel: zram: Cannot change disksize for initialized device
Jul 03 17:42:00 systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Jul 03 17:42:00 systemd[1]: Dependency failed for dev-zram0.swap - Compressed Swap on /dev/zram0.
When you reset the BIOS did you set the RAM back to is correct XMP profile?
I’d also look at running memtest86 on this machine, jsut to rule the ram either good or bad. If you have a bad stick you’re going to get all kinds of weird stuff happening…
Does this command hang if you run it alone? Normally it should output a list of running processes pretty quickly.
I have to be honest I’m not sure what an XMP profile is, what should I be looking for with that?
I’ll also run memtest86 when I can, I’m about to head out for the evening and I’ve not got time to figure out how to do that, but I’ll be back at this tomorrow and be able to give it my full attention.
Thanks again for all the help, I do appreciate it.
It’ll be in the BIOS page for ram settings. It’ll say something like XMP Profile 2.0 or words to that effect. It tends to default to the lowest possible setting which just means your ram runs slightly slower than this could potentially do, so I’d not expect it to cause an issue if you didn’t change it.
Given that you had over clocked the CPU I wondered if you were overclocking the ram too.
It would also be handy if you could perform a fresh boot and then execute a journalctl -b -0 --no-hostname --no-pager | fpaste so we can see the entire boot process from start to finish in case there’s a smoking gun in there.
It does seem to hang
Try another reboot. Changing settings within the bios setup menus sometimes requires a full reboot and not just continuing to boot the OS.