Problem Shutting Down and Restarting

If none of the more specific forums is the right place to ask

Problem Shutting Down and Restarting

Postby nickettke » 2020-01-20 12:23

I just installed debian two days ago and I can't reboot nor do anything to switch off my pc. At first it said something like 'watchdog lockup cpu#3 stuck for 23s'. After waiting a while I used the power button on my laptop to shut it down. Then after booting again into it, I googled about it and found something and did all that(I dont know what I did). After doing all that, I tried to shut it down again and it said this 'rcu_shed detected stalls on CPUs/tasks' and said that a stop job was running(no watchdog this time). Again after waiting a while I had to force shut down. The next time i tried to shut down it just showed a black screen for 25min. I am dual booting debian over windows 10.

P.S. i dont know much about computers
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-20 12:27

Are you overclocking? Is your power supply adequate?

If you enable persistent logging:
Code: Select all
# mkdir -p /var/log/journal

Then you can reboot and use this to examine the journal contents from the previous boot:
Code: Select all
journalctl -b -1

That may have some more clues.
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-01-20 13:01

I'm not overclocking and I think my power supply is adequate(I plug in while I use),
I did as you told and it gave me this
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.

This time while rebooting, the black screen appeared for some time and the fans started kicking. I force shut it down after a few minutes.
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-20 13:10

nickettke wrote:I did as you told and it gave me this

The message does tell you how to solve that, consider it a challenge :mrgreen:

nickettke wrote:I force shut it down after a few minutes.

If you keep doing that then you might corrupt your filesystem.

http://blog.kember.net/articles/reisub- ... x-restart/

https://unix.stackexchange.com/question ... -on-debian
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-01-20 13:31

I'm sorry sir but I have no clue whatsoever(sorry for being this dumb).

Head_on_a_Stick wrote:If you keep doing that then you might corrupt your filesystem.

How else can I shut down or reboot?
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-20 13:47

Please don't call me "sir", it makes me nervous.

To access the journal either run the command as root or add your user to the systemd-journal group:
Code: Select all
sudo gpasswd -a $USER systemd-journal

Then log out & back in again.

nickette wrote:
Head_on_a_Stick wrote:If you keep doing that then you might corrupt your filesystem.

How else can I shut down or reboot?

Read the two links I provided, they explain how to use REISUB in Debian.
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-01-26 16:34

Okay, I still have not fixed the problem. But I'm using the REISUB to shut down. Hope it doesn't break my system in the long run.

And I can't seem to get the journal thing to work.

Typing this
Code: Select all
journalctl -b -1
gives
Code: Select all
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.


And Typing this
Code: Select all
sudo journalctl -b -1
gives this
Code: Select all
Specifying boot ID or boot offset has no effect, no persistent journal was found.


Tried restarting my system a bunch of times
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-26 16:43

nickettke wrote:
Code: Select all
Specifying boot ID or boot offset has no effect, no persistent journal was found.

I wrote:
Code: Select all
# mkdir -p /var/log/journal

viewtopic.php?p=714159#p714159

Alternatively, edit /etc/systemd/journald.conf, remove the # symbol from the start of the "Storage=" line and change the setting to "persistent".

For more on this read
Code: Select all
man journald.conf
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-01-26 17:36

Head_on_a_Stick wrote:
Code: Select all
# mkdir -p /var/log/journal

Did it.

Did this
Head_on_a_Stick wrote:Alternatively, edit /etc/systemd/journald.conf, remove the # symbol from the start of the "Storage=" line and change the setting to "persistent".
and ran this
Code: Select all
sudo journalctl -b -1
. The output was
Code: Select all
Data from the specified boot (-1) is not available: No such boot ID in journal
. But ran this
Code: Select all
 sudo journalctl
and it gave me a thousand line or more of stuff.
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-26 18:12

You have to reboot after changing the setting, old logs can't be summoned back out of the ether.
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-01-28 15:57

I'm sorry.

Code: Select all
sudo journalctl -b -1
This now shows a lot of stuff. So what should I do next?
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby Head_on_a_Stick » 2020-01-28 18:28

nickettke wrote:This now shows a lot of stuff. So what should I do next?

Read the stuff and enter any errors into a search engine to see if there are any solutions.
User avatar
Head_on_a_Stick
 
Posts: 11114
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Problem Shutting Down and Restarting

Postby sunrat » 2020-01-28 21:38

Head_on_a_Stick wrote:
nickettke wrote:This now shows a lot of stuff. So what should I do next?

Read the stuff and enter any errors into a search engine to see if there are any solutions.


And read the man page for journalctl. You will find you can limit the "stuff" to warnings and/or errors by setting priority. This is what I usually start with:
Code: Select all
journalctl -b -1 -p 3

The man will tell you what the numbers mean and what happens if you use different numbers.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2956
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Problem Shutting Down and Restarting

Postby nickettke » 2020-02-05 11:05

Sorry for posting late...

But I guess I found a solution! I found this vid on youtube and did as the guy said https://www.youtube.com/watch?v=nPprHes-K_Y&t=61s. I'll still tell what I did.
1) While the grub menu appears, I clicked 'e'.
2) Then I added
Code: Select all
nouveau.modeset=0
to the end of the linux line.

Then when I booted and tried shutting down, it worked!
But the next time I boot into, this edit I made is gone and I'm unable to shut it down normally.

So can someone tell me how I can make the edit to be permanent?
nickettke
 
Posts: 16
Joined: 2020-01-20 12:05

Re: Problem Shutting Down and Restarting

Postby sunrat » 2020-02-05 11:54

Edit (as root or sudo) the file /etc/default/grub and add it to the line GRUB_CMDLINE_LINUX_DEFAULT between the double quotes. It will have something like
Code: Select all
"quiet splash"

so change it to
Code: Select all
"quiet splash nouveau.modeset=0"

and save. Then do
Code: Select all
update-grub

and reboot.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2956
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Next

Return to General Questions

Who is online

Users browsing this forum: No registered users and 13 guests

fashionable