Linux hangs what to do

Linux Mint Forums

Welcome to the Linux Mint forums!

(Solved) Linux Mint 19.1 hangs at shutdown and restart

(Solved) Linux Mint 19.1 hangs at shutdown and restart

Post by lechatnoir » Sun Apr 07, 2019 1:31 am

Good morning everybody,
i’m having a hard time trying to troubleshoot my shutdown problems with Linux Mint 19.1
It just hangs at the linux mint logo, if i try to press ESC nothing happen and i have to use the shutdown button.
I have already tried to change the GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash» line to GRUB_CMDLINE_LINUX_DEFAULT=»acpi=force reboot=acpi quiet splash» in the /etc/default/grub file, save it, sudo update-grub and reboot, but that did not work.
Same thing happen when i boot from the live USB.
Secure boot is disabled.
What else can i do to solve this issue?
Below is my inxi -Fxz command output.
Thanks.

System:
Host: Commander2 Kernel: 4.15.0-47-generic x86_64 bits: 64 compiler: gcc
v: 7.3.0 Desktop: Xfce 4.12.3 Distro: Linux Mint 19.1 Tessa
base: Ubuntu 18.04 bionic
Machine:
Type: Laptop Mobo: Eurocom model: Commander 2 serial:
UEFI: INSYDE v: 1.07.05TEU date: 08/14/2018
CPU:
Topology: 6-Core model: Intel Core i7-8700 bits: 64 type: MT MCP
arch: Kaby Lake rev: A L2 cache: 12.0 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 76608
Speed: 4517 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 4501 2: 4469
3: 4439 4: 4444 5: 4452 6: 4498 7: 4500 8: 4459 9: 4499 10: 4437 11: 4450
12: 4500
Graphics:
Device-1: Intel vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa
resolution: 3840×2160

60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3×8 GT2)
v: 4.5 Mesa 18.2.8 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k4.15.0-47-generic
Network:
Device-1: Intel Ethernet I219-LM vendor: CLEVO/KAPOK driver: e1000e
v: 3.2.6-k port: 4040 bus ID: 00:1f.6
IF: enp0s31f6 state: down mac:
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 4040
bus ID: 6c:00.0
IF: wlp108s0 state: up mac:
Drives:
Local Storage: total: 1.36 TiB used: 178.27 GiB (12.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
Partition:
ID-1: / size: 456.96 GiB used: 21.07 GiB (4.6%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 55.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 280 Uptime: 14m Memory: 31.11 GiB used: 1.48 GiB (4.7%)
Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 Shell: bash v: 4.4.19
inxi: 3.0.27

Источник

What to do when your Linux hangs?

Por Rodrigo Ramirez

Linux, despite “popular belief”, does crash (hangs or jams). Sometimes it is one or two applications per deadlock and everything can be resolved with a kill -9 to the application hanging from the terminal, this only if it is possible to change the terminal with ctrl + alt + 1, or ctrl + alt + 2, or or doing a Ctrl + Alt + Backspace (if you have it enabled) to restart the X; But if after they have already tried all of the above and still nothing could be achieved, many of us or those of us who do not know this, what we do is press our power button to turn it off and this causes our disk to start to fail Lasted.

What should we do when Hangs?

Magic SysRq key is a key combination in the Linux kernel that allows the user to execute various low-level commands regardless of the system state. This means that, even if your computer hangs on all sides and seems not to respond, this set of keys will give you a better solution than the “power off” one, allowing you, among other things, to synchronize the hard drives so that you do not lose everything. what you have been doing.

How does it work? Easy. The standard combination is as follows: ALT + Sysrq (print screen) + command, where Sysrq is the key that appears on current keyboards as Print screen and Sys Request (System Request). One of the most famous combinations is REISUB:
Alt + SysRq+:

▸R: Puts the keyboard in XLATE mode (ASCII mode, NOT UNICODE)

▸E: Terminates (term) all processes (except init).

▸I: Forces the “cascaded” processes to end, so that the files in use can be written to disk.

▸S: You empty the disk caches, finalizing all disk writes.

▸U: Reassemble all filesystems as read-only, so that nothing can be accidentally written just before the reset.

▸B: Reset the system.

If, for whatever reason, the Sysrq key doesn’t work for you, write the following: echo command> / proc / sysrq-trigger

Where command is any letter you want Sysrq to make.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] What To Do When Mint Crashes / Hangs / Freezes?

[SOLVED] What To Do When Mint Crashes / Hangs / Freezes?

Post by Ow That Hurts » Tue Feb 16, 2016 6:54 pm

EDIT: See Cosmo’s posts below for solution

I am sure this has been asked and answered before, but I am having a stupid moment here, so please bear with me.

What do you do (instead of ctrl-alt-delete) when Linux Mint freezes?

Using 17.3 Cinnamon desktop

I had one «crash» where after logging out (in order to switch users), I came to a mostly black screen with just a blinking cursor in the top left hand corner.

Did not know how to get out of it.

Thanks in advance, and sorry if this has been covered ad nauseum. For some reason, Mr. Google has not been kind to me lately every time I look for an answer.

Re: What To Do When Mint Crashes / Hangs / Freezes?

Post by Old Ruler » Tue Feb 16, 2016 8:37 pm

First thing I’d do is check if I can get a virtual terminal by pressing CTRL+ALT+F1 (or 2,3,4,5,6 can do different things on each one if you want) and log in. Probably just reboot from there. I use ‘shutdown -r now’, but only because I’ve always used that. ‘reboot’ works just as well iiuc.

If I’m interested in why it crashed, I might look in /var/log files for clues, or check if process has gone wild with ‘top’.

Those virtual terminals have been available in every Linux desktop I’ve used, but I haven’t tried them all.

I hardly ever get that sort of trouble, so I’m no expert.

Источник

Linux kernel hang at crng init done #306

Comments

Rusack commented Sep 13, 2018

I’m trying to install OP-TEE and TF-A on the Raspberry Pi 3 (model B), therefore I used the manifest file for the rpi3 and the repo command (Didn’t specify the release or anything, just took the last one). The build went fine, I then installed the result on the micro SD following instructions of the make img-help output. My problem is appearing at the linux kernel boot, it hangs forever after random : `crng init done , I’m connected by UART.
I’m joining the build log as well as the boot log.
build.log
boot.log

The text was updated successfully, but these errors were encountered:

gkarop commented Sep 13, 2018

I have a similar issue. I’m using a Raspberry Pi 3 (model B, V 1.2, 2015) and release branch 3.2 ( -b 3.2.0 ). I also had no problems with build, installed OP-TEE following the instructions on make img-help and I get the output to the screen through HDMI. The first time I boot Pi it is stuck in crng init done as @Rusack mentioned previously; see the screenshot below:

If I power off and then power on again the Pi it is stuck in the following screen (every time apart from the first boot it is stuck in the following screen):

I also tried rootfs.cpio.gz that @jbech-linaro provided here:
#276 (comment)
but the result was exactly the same as above.

jbech-linaro commented Sep 13, 2018

And from the comments in #276 we haven’t done anything with the RPi3 B+ model (I still only have the old RPi3). So, I wouldn’t be surprised if it’s (still) an RPi3 B+ issue.

igoropaniuk commented Sep 13, 2018

@gkarop Seems the dhcp-client is the reason of this hang. Try to connect RPi3 to ethernet and see what happens next (I did have a similar issue)

Rusack commented Sep 13, 2018 •

I’m using a Rpi 3 model B v1.2 2015, that’s what is written on it.

Edit : It’s v1.2 actually

gkarop commented Sep 14, 2018

And from the comments in #276 we haven’t done anything with the RPi3 B+ model (I still only have the old RPi3). So, I wouldn’t be surprised if it’s (still) an RPi3 B+ issue.

@jbech-linaro In the past I tried in a RPi3 B+ where indeed it does not boot. Currently I’m using an RPi3 B model (the screenshots above are from the B one). Could it be something with the different versions? Mine is model B v1.2.

@gkarop Seems the dhcp-client is the reason of this hang. Try to connect RPi3 to ethernet and see what happens next (I did have a similar issue)

@igoropaniuk I tried with ethernet with no success; compared to the screenshots above I only get one more message saying «Link up» and then it is stuck there.

Is there a way to disable dhcp?

jforissier commented Sep 14, 2018 •

Is there a way to disable dhcp?

Quick and dirty way: delete this line in common.mk :

Edit: For a better fix, perhaps we should make this line conditional, default enabled for QEMU at least. But first try to understand why this udhcp thing is a problem for RPi3: shouldn’t the script just fail quickly if there is no network device or no DHCP server on the network?

gkarop commented Sep 14, 2018

Nothing changed. In my common.mk file it is already conditional so probably it was never called anyway:

jforissier commented Sep 14, 2018

@gkarop sorry I failed to notice you’re on 3.2.0. Current master does not have QEMU_USERNET_ENABLE anymore.

gkarop commented Sep 17, 2018

I have tried many different things in order to disable udhcpc but it always starts during boot. Any ideas? In which configuration files I should search in particular?

dmeignan commented Oct 30, 2018

Any news with this issue, I have the same problem with a Rpi 3 model B v1.2 2015.

jforissier commented Oct 30, 2018

@dmeignan should be fixed by #316

jedichen121 commented Oct 31, 2018

I just tried the build yesterday and I’m still hanging at the crng init done . I checked my local code and found that the changes in the newest commit were there. I’m also using Rpi3 and I’m not using UART but connected directly with HDMI. The following code in the #316 is not in my version of common.mk. Should I add it and try make again?

jbech-linaro commented Nov 1, 2018 •

So to summarize things that needs to be addressed and looked at into in the future.

1. The core team doesn’t have any RPi3 model B+, we only have the first RPi3 revision (B).
   1.1 People are seeing various errors using RPi3 model B+. Most of them seems to be that it hangs during boot and crng init done is the final message seen.
2. Using the first RPi3 revision, the core team have no issues building, booting nor running test.

To address «1», we (core team) need to buy a RPi3 model B and start debugging. We can do that, but we have the roadmap planned for several months a head of us with other things and features, which means that it could take a while until we have time to do proper debugging and testing with the newer RPi3 revision. So a faster way forward would be to help users having the issue to narrow down the problem (basically what we’ve tried in this thread).

Related, if and when I find time, I’ve planned to add the RPi3 to the automatic build, boot, test cycle initiated by GitHub commits (basically add a config for IBART). But with recent changes to the RPi3 boot (doing a more proper boot), it has become harder to deploy the files automatically. I think it still id doable, but just a bit more tricky. If I ever get to work on this, we should hopefully be able to rule out problems like this.

Regarding «2», we can re-test again to ensure that the first RPi3 revision still works. As mentioned yesterday in #296 (comment) 3.2.0 was tested OK by two independent developers and 3.3.0 released

2 weeks ago was also tested OK also, see OP-TEE/optee_os#2552 (comment)).

Источник

2E0PGS / linux-usb-file-copy-fix.md

If your running a x64 bit Ubuntu or other Linux and find USB transfers hang at the end apply this fix:

I suggest you edit your /etc/rc.local file to make this change persistant across reboots.

sudo nano /etc/rc.local

Go to the bottom of the file and leave a space then paste in those two lines.

Save the file with ctrl + x then press y.

To revert the changes enter this in console and remove the lines in /etc/rc.local

This comment has been minimized.

Copy link Quote reply

jorgeribeiro commented Oct 24, 2018

It worked just fine, thank you so much!

After searching a lot in different sources, this was the only answer to actually work.
I use Linux Mint 18.

This comment has been minimized.

Copy link Quote reply

Oldbuntu commented Jan 24, 2019

Thank’s this really work for Ubuntu 18.04.Thank one’s again

This comment has been minimized.

Copy link Quote reply

Rockburner commented Feb 20, 2019 •

I tried entering these lines into the file, but now a 1Gb file that previously took less than a minute to copy, after which ‘files’ would hang for over an hour, is taking up to an hour to copy at something like 255kB/sec.
For reference the machine is an I5 with 16GbRAM running ubuntu 18.04. The USB stick is a new 256Gb SanDisk.
Are there some better byte values I can try to get a better balance between the latency and the hanging?

I can’t use the lines directly in the terminal either — I just get ‘Permission Denied’, even using sudo.

Источник