-
Notifications
You must be signed in to change notification settings - Fork 58
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
Sudden restart #70
Comments
I have never experienced sudden restarts so far. Let's watch this. |
Might also want to try 13-CURRENT based builds for comparison (once they become available again). |
Thanks. If a kernel panic does occur, should I expect a 'drop out' to a command line? Where |
Incidentally re: ncw/stressdisk#14 there's the possibility of a drive firmware issue affecting s/n With an earlier helloSystem image, the same drive featured in a non-reported boot failure (I/O errors, IIRC) with the drive in one of the rear ports of the Ergo Vista 631. For the incident at #70 (comment) above I recall beginning (or aiming) to experiment with the global menu for Falkon very shortly before the blackout, so for what it's worth, I wondered about a DRM issue. Rewind to a few minutes earlier, I recall trying to get Spectacle to recognise Filer as a handler to open the location of a saved screenshot. |
When a kernel panic occurs, then I think the system restarts. |
No other panic observed, with any medium. |
hello-12.1-RELEASE-0a2ed28-amd64.iso
(202012301349)Sudden blackout and restart not long after taking the screenshot at #23 (comment)
Should I assume a kernel panic?
I half-expected an opportunity to
bt
(but not a core dump).Environment
HW probe of HP EliteBook 8570p #60d9540d35
Booted from Verbatim STORE N GO s/n
17071802004381
After the event (with a non-helloSystem):
The text was updated successfully, but these errors were encountered: