Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSystem spontaneously reboots #1681
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
edwintorok
Jan 23, 2016
Reproduced. This is related to KDE/OpenGL: #1680 (comment), so closing this bug in favour of the other one.
edwintorok
commented
Jan 23, 2016
|
Reproduced. This is related to KDE/OpenGL: #1680 (comment), so closing this bug in favour of the other one. |
edwintorok
closed this
Jan 23, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
edwintorok commentedJan 23, 2016
I understand that AMD based systems may not be supported by Qubes as well as Intel systems, but I thought to report this nonetheless, just in case its a bug that would affect something else too.
IIRC this was the 2nd boot after install (see #1680), I started/stopped a few VMs (for example I stopped the whonix VM and the sys-whonix one), tried to run qubes-dom0update but it failed due to a missing
repomd.xmlfile, updated some template VMs.Then I started a VM from the menu (note that Qubes VM manager was already not working at this point, see #1680), I got the notification that the VM is booting and then the machine just rebooted by itself.
No error messages, no high CPU usage (fan wasn't audible), no panic messages, it just rebooted.
The system has 12 GiB of RAM so its unlikely it would've run out of memory so soon.
I tried to recreate the situations by booting/stopping some VMs, but I couldn't.
The /var/log/messages from the 2nd boot are here, are there any other logs that could contain hints on why it rebooted?
Is there some setting in Xen or Qubes to tell it to show a panic message instead of rebooting?
BTW I've been running 4.1, 4.2 and 4.3 kernels from Debian jessie+backports with sysvinit and KVM without problems for years on this machine, although I haven't tried running Xen with IOMMU for an extended period of time, so this might be a Xen problem, but then it might also be a dom0 issue (or even a systemd issue).
If dom0 crashes would it be expected to have the system spontaneously reboot?
Here is some system information and hypervisor logs that I collected now (obviously not before the reboot bug): https://gist.github.com/edwintorok/64e6473c0fa1191a1bc2