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

Spontaneous weird reboot (with logs, surprisingly) #2613

Open
tonsimple opened this Issue Jan 31, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@tonsimple

tonsimple commented Jan 31, 2017

Qubes OS version (e.g., R3.2):

3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

dom0 (presumably)


Expected behavior:

System on a non-overclocked and well-cooled box remains stable for >48 hours

Actual behavior:

Occasional spontaneous reboots due to unknown cause, relatively rare.

Steps to reproduce the behavior:

Unfortunately, only running qubes and waiting

General notes:

Despite the crash-like random occurrence, the reboot turns out to be "graceful" enough to leave a seemingly unambiguous log (the -- Reboot -- is present where the reboot took place).

Here it is
weirdreboot.txt

trails of asterisks a-la ** indicate either my comment added later, or redaction (I redacted some VM names ;-) )

Look for
**(****ANCHOR****comment - I didn't ask for this reboot!)**

that's exactly where the reboot takes place.

Do note that -- Reboot -- statement is preceded by a copious "normal qubes activity" log.

I can't quite determine from this log alone what caused reboot, but I'm not a professional. Hope it provides enough info to figure out what's going on.

P.S.:
I was not even working with qubes when the reboot happened, I went afk for a bit and was on the other side of the room when I suddenly heard typical "reboot noises"


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 1, 2017

Member

Did you apply dom0 updates without rebooting?

Member

andrewdavidwong commented Feb 1, 2017

Did you apply dom0 updates without rebooting?

@tonsimple

This comment has been minimized.

Show comment
Hide comment
@tonsimple

tonsimple Feb 1, 2017

@andrewdavidwong no, I applied updates several days before, and made a planned reboot afterwards.

No updates were installed to dom0 on 31 January

tonsimple commented Feb 1, 2017

@andrewdavidwong no, I applied updates several days before, and made a planned reboot afterwards.

No updates were installed to dom0 on 31 January

@0spinboson

This comment has been minimized.

Show comment
Hide comment
@0spinboson

0spinboson Feb 1, 2017

I'm also seeing unexpected reboots, though without any journal entries that seem relevant. First occurrence was on jan 30th, 3 so far. All occurred while I was AFK for an extended period of time.
Only recent update I've seen is the domU pulseaudio and mesa stuff, the former from current-testing, would have to check which were the latest dom0 updates.
Additional info: I'm running all current dom0 updates in current-testing and security-testing, 4.8.12 kernel (since the day Marek uploaded it in december)

I'm also seeing unexpected reboots, though without any journal entries that seem relevant. First occurrence was on jan 30th, 3 so far. All occurred while I was AFK for an extended period of time.
Only recent update I've seen is the domU pulseaudio and mesa stuff, the former from current-testing, would have to check which were the latest dom0 updates.
Additional info: I'm running all current dom0 updates in current-testing and security-testing, 4.8.12 kernel (since the day Marek uploaded it in december)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment