Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nodeagent: clarifies reboot reason message #4089

Merged
merged 1 commit into from
Jul 17, 2024

Conversation

rouming
Copy link
Contributor

@rouming rouming commented Jul 15, 2024

SMART power cycle counter does not expose much and stays same (previous counter and current counter) if system was reset, rebooted or paniced. Previous quite pessimistic reboot message said "kernel crash", which is not always the case and confuses our support and customers. More clear message should be "system reset, reboot or kernel panic due to watchdog or kernel bug (no kdump)".

SMART power cycle counter does not expose much and stays same
(previous counter and current counter) if system was reset,
rebooted or paniced. Previous quite pessimistic reboot message
said "kernel crash", which was not always the case and confused
our support and customers. More clear message should be
"system reset, reboot or kernel panic due to watchdog or kernel
bug (no kdump)".

Signed-off-by: Roman Penyaev <r.peniaev@gmail.com>
@shjala
Copy link
Member

shjala commented Jul 15, 2024

This is still confusing "system reset, reboot or kernel panic", which one is it?

@rouming
Copy link
Contributor Author

rouming commented Jul 15, 2024

We can't tell exactly, unfortunately. We use SMART power cycle counters to make a decision, but what they say is that a machine was powered cycled and this is another message: "device powered off". In all other cases anything can happen from the list I mentioned, the message seems to be more comforting for the user, because it does not insist that this is kernel crash. It might be, yes, but also reset, watchdog, etc. etc.

@rouming rouming merged commit c998eec into lf-edge:master Jul 17, 2024
20 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants