How to log system messages from unexpected poweroffRandom ShutdownsHow do I get my power indicator to reliably warn me before shutting off my laptop?system does not power off on “poweroff”, just haltsSchedule the system to poweroffUbuntu doesn't fully power down machine
What would be the effect of a giant magical fireball burning in the ocean?
How can I learn to write better questions to test for conceptual understanding?
A man condemned to serve his sentence in other times
BV-217 Antler bottom bracket service or replacement
What are the branches of statistics?
Does Darwin owe a debt to Hegel?
90's/00's anime about 3 girls who travel between the real world and a fantasy world
Is it safe to pay bills over satellite internet?
Could an American state survive nuclear war?
When to use the gestalt principle of common region?
Where does the upgrade to macOS Catalina move root "/" directory files?
Generating sequential alphanumeric values that match a certain pattern
Can we not simply connect a battery to a RAM to prevent data loss during power cuts?
Encountering former, abusive advisor at a conference
What's that funny "illo" I keep hearing in Southern Spain?
If I did not sign promotion bonus document, my career would be over. Is this duress?
Demod as a neologism
Christmas party at employers home
What could possibly power an Alcubierre drive?
Easy way of generating a 50-150W load @12V
Does the US require a House vote to begin an impeachment inquiry?
Idiom for a situation or event that makes one poor or even poorer?
Why is technology bad for children?
How should I understand FPGA architecture?
How to log system messages from unexpected poweroff
Random ShutdownsHow do I get my power indicator to reliably warn me before shutting off my laptop?system does not power off on “poweroff”, just haltsSchedule the system to poweroffUbuntu doesn't fully power down machine
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
My laptop powers off unexpectedly sometimes. There is a warning before that happens, the fans start to spin loudly. I can trigger the shutdown by putting the laptop on heavy load, by trying to build lineageOS. However there are other times when the laptop is under low load, for example during boot (either pre or just after log in) when the fans spin up warning me that it is about to shutdown on it's own.
I have installed a package lm-sensors to check cpu temperatures but I never saw anything above 80, that would justify the laptop powering off on it's own immediately. The expected behaviour if the cpu is on heavy load is to throttle, right?
I would like to capture or access whatever relevant system logs, just before the unexpected poweroff so that I can see, after I reboot, what happened and how it was triggered. The goal is to find out what is the cause of those unexpected power offs. I 'm guessing the kernel or systemd would be creating some logs
I have unscrewed my laptop and used an air blower to remove any dust, even though there wasn't much - so I don't think this is a cooling problem. My laptop uses Ubuntu Mate 18.04.2 fully updated, without HWE so 4.15 kernel series. Hardware wise it has an i5-7300hq cpu and an nvidia 1050Ti. The gpu shouldn't matter as I 've been using the laptop on iGPU mode exclusively before this happened, nvidia's drivers are installed though.
Update:
I run journalctl -b -1 -e and the result was:
May 14 00:34:23 shade smartd[900]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 68
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session opened for user root by (uid=0)
May 14 00:35:01 shade CRON[25666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session closed for user root
I don't think any of those messages relates to why the laptop shut down on it's own. I also looked at /var/log/syslog and the messages there were the same. Does the motherboard's/CPU's firmware store logs anywhere else that may show something when they tell the laptop to shut down?
shutdown temperature
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
add a comment
|
My laptop powers off unexpectedly sometimes. There is a warning before that happens, the fans start to spin loudly. I can trigger the shutdown by putting the laptop on heavy load, by trying to build lineageOS. However there are other times when the laptop is under low load, for example during boot (either pre or just after log in) when the fans spin up warning me that it is about to shutdown on it's own.
I have installed a package lm-sensors to check cpu temperatures but I never saw anything above 80, that would justify the laptop powering off on it's own immediately. The expected behaviour if the cpu is on heavy load is to throttle, right?
I would like to capture or access whatever relevant system logs, just before the unexpected poweroff so that I can see, after I reboot, what happened and how it was triggered. The goal is to find out what is the cause of those unexpected power offs. I 'm guessing the kernel or systemd would be creating some logs
I have unscrewed my laptop and used an air blower to remove any dust, even though there wasn't much - so I don't think this is a cooling problem. My laptop uses Ubuntu Mate 18.04.2 fully updated, without HWE so 4.15 kernel series. Hardware wise it has an i5-7300hq cpu and an nvidia 1050Ti. The gpu shouldn't matter as I 've been using the laptop on iGPU mode exclusively before this happened, nvidia's drivers are installed though.
Update:
I run journalctl -b -1 -e and the result was:
May 14 00:34:23 shade smartd[900]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 68
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session opened for user root by (uid=0)
May 14 00:35:01 shade CRON[25666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session closed for user root
I don't think any of those messages relates to why the laptop shut down on it's own. I also looked at /var/log/syslog and the messages there were the same. Does the motherboard's/CPU's firmware store logs anywhere else that may show something when they tell the laptop to shut down?
shutdown temperature
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
2
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
3
The commandjournalctl -b -1 -ewill show the last messages logged at the previous boot. Replacing-b -1with-b -2,...will show earlier boots.journalctl --list-bootsandman journalctlare also interesting.
– waltinator
May 13 at 18:11
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08
add a comment
|
My laptop powers off unexpectedly sometimes. There is a warning before that happens, the fans start to spin loudly. I can trigger the shutdown by putting the laptop on heavy load, by trying to build lineageOS. However there are other times when the laptop is under low load, for example during boot (either pre or just after log in) when the fans spin up warning me that it is about to shutdown on it's own.
I have installed a package lm-sensors to check cpu temperatures but I never saw anything above 80, that would justify the laptop powering off on it's own immediately. The expected behaviour if the cpu is on heavy load is to throttle, right?
I would like to capture or access whatever relevant system logs, just before the unexpected poweroff so that I can see, after I reboot, what happened and how it was triggered. The goal is to find out what is the cause of those unexpected power offs. I 'm guessing the kernel or systemd would be creating some logs
I have unscrewed my laptop and used an air blower to remove any dust, even though there wasn't much - so I don't think this is a cooling problem. My laptop uses Ubuntu Mate 18.04.2 fully updated, without HWE so 4.15 kernel series. Hardware wise it has an i5-7300hq cpu and an nvidia 1050Ti. The gpu shouldn't matter as I 've been using the laptop on iGPU mode exclusively before this happened, nvidia's drivers are installed though.
Update:
I run journalctl -b -1 -e and the result was:
May 14 00:34:23 shade smartd[900]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 68
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session opened for user root by (uid=0)
May 14 00:35:01 shade CRON[25666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session closed for user root
I don't think any of those messages relates to why the laptop shut down on it's own. I also looked at /var/log/syslog and the messages there were the same. Does the motherboard's/CPU's firmware store logs anywhere else that may show something when they tell the laptop to shut down?
shutdown temperature
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
My laptop powers off unexpectedly sometimes. There is a warning before that happens, the fans start to spin loudly. I can trigger the shutdown by putting the laptop on heavy load, by trying to build lineageOS. However there are other times when the laptop is under low load, for example during boot (either pre or just after log in) when the fans spin up warning me that it is about to shutdown on it's own.
I have installed a package lm-sensors to check cpu temperatures but I never saw anything above 80, that would justify the laptop powering off on it's own immediately. The expected behaviour if the cpu is on heavy load is to throttle, right?
I would like to capture or access whatever relevant system logs, just before the unexpected poweroff so that I can see, after I reboot, what happened and how it was triggered. The goal is to find out what is the cause of those unexpected power offs. I 'm guessing the kernel or systemd would be creating some logs
I have unscrewed my laptop and used an air blower to remove any dust, even though there wasn't much - so I don't think this is a cooling problem. My laptop uses Ubuntu Mate 18.04.2 fully updated, without HWE so 4.15 kernel series. Hardware wise it has an i5-7300hq cpu and an nvidia 1050Ti. The gpu shouldn't matter as I 've been using the laptop on iGPU mode exclusively before this happened, nvidia's drivers are installed though.
Update:
I run journalctl -b -1 -e and the result was:
May 14 00:34:23 shade smartd[900]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 68
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:34:36 shade brisk-menu[19830]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session opened for user root by (uid=0)
May 14 00:35:01 shade CRON[25666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 14 00:35:01 shade CRON[25665]: pam_unix(cron:session): session closed for user root
I don't think any of those messages relates to why the laptop shut down on it's own. I also looked at /var/log/syslog and the messages there were the same. Does the motherboard's/CPU's firmware store logs anywhere else that may show something when they tell the laptop to shut down?
shutdown temperature
shutdown temperature
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
edited May 14 at 22:47
Karsus
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
asked May 13 at 17:54
KarsusKarsus
6352 gold badges8 silver badges26 bronze badges
6352 gold badges8 silver badges26 bronze badges
2
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
3
The commandjournalctl -b -1 -ewill show the last messages logged at the previous boot. Replacing-b -1with-b -2,...will show earlier boots.journalctl --list-bootsandman journalctlare also interesting.
– waltinator
May 13 at 18:11
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08
add a comment
|
2
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
3
The commandjournalctl -b -1 -ewill show the last messages logged at the previous boot. Replacing-b -1with-b -2,...will show earlier boots.journalctl --list-bootsandman journalctlare also interesting.
– waltinator
May 13 at 18:11
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08
2
2
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
3
3
The command
journalctl -b -1 -e will show the last messages logged at the previous boot. Replacing -b -1 with -b -2, ... will show earlier boots. journalctl --list-boots and man journalctl are also interesting.– waltinator
May 13 at 18:11
The command
journalctl -b -1 -e will show the last messages logged at the previous boot. Replacing -b -1 with -b -2, ... will show earlier boots. journalctl --list-boots and man journalctl are also interesting.– waltinator
May 13 at 18:11
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08
add a comment
|
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1142936%2fhow-to-log-system-messages-from-unexpected-poweroff%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1142936%2fhow-to-log-system-messages-from-unexpected-poweroff%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Overloading the Intel Graphics is a bad idea. You should be using the Nvidia for demanding tasks. I wonder if that's the reason for the shutdowns...
– GabrielaGarcia
May 13 at 18:07
3
The command
journalctl -b -1 -ewill show the last messages logged at the previous boot. Replacing-b -1with-b -2,...will show earlier boots.journalctl --list-bootsandman journalctlare also interesting.– waltinator
May 13 at 18:11
@GabrielaGarcia most likely
– Rinzwind
May 13 at 18:37
@GabrielaGarcia I don't believe I am overloading the Intel graphics. Building LineageOS is a CPU intensive task. Moreover I was doing it on the laptop for ~6 months while this problem showed up a month or so ago.
– Karsus
May 13 at 21:08