User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101
Firefox/115.0
Build Identifier: 

Every time I do:

USS-Liberty:~ # mount -t cifs //192.168.99.78/elements -o username=hattons
/mnt/elements
Password for hattons@//192.168.99.78/elements:

followed by ‘ls /mnt’, I get

2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][    C0]
watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764]

etc.

I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to
get stuck on other processes. I haven’t been using Linux for several years, but
in the good old days, this wasn’t supposed to happen.

Reproducible: Always

Steps to Reproduce:
1. # mount -t cifs //192.168.99.78/<share> -o username=<user> /mnt/<mount
point>
2. ‘ls /mnt’
3. 
Actual Results:  
I get repeated messages of the form

2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][    C0]
watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764]

I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to
get stuck on other processes.

Expected Results:  
Expected the remote share to either be mounted an ls to show me the contents of
/mnt, or receive an error indicating a failure of the mount and/or ls commands.

This is very deterministic.  I have nothing to compare it to because it is my
first Linux install in years, and I don't have a second machine to test with. 
There is, however, this:

https://forums.opensuse.org/t/mount-t-cifs-then-ls-mnt-causes-soft-lockup-cpu-0-stuck-cant-kill-9-nor-init-s-etc/176343/3

Unfortunately, I did a reinstall since I last crashed the machine, so I don't
have logs.  If you can't reproduce the result, I will try again.