[qubes-users] Random sudden reboots
I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in the last few hours, often around the time I start a VM. I do not see anything in the log. P.S: I've been running Citrix XenServer for two years on this machine with no issues. Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed for user root Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? Nov 26 22:36:38 dom0 kernel: audit: type=1106 audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi Nov 26 22:36:38 dom0 kernel: audit: type=1104 audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: balance_when_enough_memory(xen_free_memory=97794733, total_mem_pref=5101760998.4, total_available_memory=60546306417.6) Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: left_memory=24233992215 acceptors_count=1 -- Reboot -- Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Nov 26 22:38:00 dom0 kernel: Linux version 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 Nov 26 22:38:00 dom0 kernel: Command line: placeholder root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. Nov 26 22:38:00 dom0 kernel: Released 0 page(s) Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x-0x0009bfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0009c800-0x000f] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0010-0x67e1] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e2-0x67e20fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e21000-0x67e6afff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e6b000-0x67ebcfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67ebd000-0x68bedfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x68bee000-0x6ee48fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ee49000-0x6f7adfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6f7ae000-0x6ff99fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ff9a000-0x6fffefff] ACPI data Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6000-0x6fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x7000-0x77ff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xe000-0xefff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfe00-0xfe010fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfec0-0xfec00fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfed9-0xfed91fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfee0-0xfeef] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xff00-0x] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0001-0x000191f95fff] usable -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9959bd62-686c-4cd2-8d27-03f6f1b70478%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Random sudden reboots
On 11/27/2017 07:47 AM, Wael Nasreddine wrote: I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in the last few hours, often around the time I start a VM. I do not see anything in the log. P.S: I've been running Citrix XenServer for two years on this machine with no issues. Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed for user root Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? Nov 26 22:36:38 dom0 kernel: audit: type=1106 audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi Nov 26 22:36:38 dom0 kernel: audit: type=1104 audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: balance_when_enough_memory(xen_free_memory=97794733, total_mem_pref=5101760998.4, total_available_memory=60546306417.6) Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: left_memory=24233992215 acceptors_count=1 -- Reboot -- Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Nov 26 22:38:00 dom0 kernel: Linux version 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 Nov 26 22:38:00 dom0 kernel: Command line: placeholder root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. Nov 26 22:38:00 dom0 kernel: Released 0 page(s) Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x-0x0009bfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0009c800-0x000f] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0010-0x67e1] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e2-0x67e20fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e21000-0x67e6afff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e6b000-0x67ebcfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67ebd000-0x68bedfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x68bee000-0x6ee48fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ee49000-0x6f7adfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6f7ae000-0x6ff99fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ff9a000-0x6fffefff] ACPI data Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6000-0x6fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x7000-0x77ff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xe000-0xefff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfe00-0xfe010fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfec0-0xfec00fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfed9-0xfed91fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfee0-0xfeef] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xff00-0x] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0001-0x000191f95fff] usable Yes, I can confirm that issue (except for the "around the time I start a VM"). Didn't find anything yet neither, my log looks similar. Some memory balancing tends to be the last entry. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a6230b5d-52ee-89de-bf71-3d182194564b%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. smime.p7s Description: S/MIME Cryptographic Signature
Re: [qubes-users] Random sudden reboots
On 11/27/2017 07:57 PM, David Hobach wrote: On 11/27/2017 07:47 AM, Wael Nasreddine wrote: I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in the last few hours, often around the time I start a VM. I do not see anything in the log. P.S: I've been running Citrix XenServer for two years on this machine with no issues. Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed for user root Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? Nov 26 22:36:38 dom0 kernel: audit: type=1106 audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi Nov 26 22:36:38 dom0 kernel: audit: type=1104 audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: balance_when_enough_memory(xen_free_memory=97794733, total_mem_pref=5101760998.4, total_available_memory=60546306417.6) Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: left_memory=24233992215 acceptors_count=1 -- Reboot -- Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Nov 26 22:38:00 dom0 kernel: Linux version 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 Nov 26 22:38:00 dom0 kernel: Command line: placeholder root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. Nov 26 22:38:00 dom0 kernel: Released 0 page(s) Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x-0x0009bfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0009c800-0x000f] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0010-0x67e1] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e2-0x67e20fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e21000-0x67e6afff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e6b000-0x67ebcfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67ebd000-0x68bedfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x68bee000-0x6ee48fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ee49000-0x6f7adfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6f7ae000-0x6ff99fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ff9a000-0x6fffefff] ACPI data Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6000-0x6fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x7000-0x77ff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xe000-0xefff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfe00-0xfe010fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfec0-0xfec00fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfed9-0xfed91fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfee0-0xfeef] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xff00-0x] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0001-0x000191f95fff] usable Yes, I can confirm that issue (except for the "around the time I start a VM"). Didn't find anything yet neither, my log looks similar. Some memory balancing tends to be the last entry. P.S.: I run a T530 with coreboot, some i5, ME cleaned. I'm not sure whether it's a heat issue, but I'd guess not as I had tested it until ~95 Celsius and it tends to run at max 80 with Qubes. I think it reboots at ~100 Celsius. But yes, it tends to happen at relatively high load. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to th
Re: [qubes-users] Random sudden reboots
On Monday, November 27, 2017 at 11:09:12 AM UTC-8, David Hobach wrote: > On 11/27/2017 07:57 PM, David Hobach wrote: > > On 11/27/2017 07:47 AM, Wael Nasreddine wrote: > >> I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard > >> reboots in the last few hours, often around the time I start a VM. I > >> do not see anything in the log. > >> > >> P.S: I've been running Citrix XenServer for two years on this machine > >> with no issues. > >> > >> Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed > >> for user root > >> Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:session_close > >> grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ > >> Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" > >> exe="/usr/bin/sudo" hostname=? addr=? > >> Nov 26 22:36:38 dom0 kernel: audit: type=1106 > >> audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi > >> Nov 26 22:36:38 dom0 kernel: audit: type=1104 > >> audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> balance_when_enough_memory(xen_free_memory=97794733, > >> total_mem_pref=5101760998.4, total_available_memory=60546306417.6) > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> left_memory=24233992215 acceptors_count=1 > >> -- Reboot -- > >> Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal > >> (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. > >> Nov 26 22:38:00 dom0 kernel: Linux version > >> 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 > >> 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 > >> Nov 26 22:38:00 dom0 kernel: Command line: placeholder > >> root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro > >> rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: > >> 'x87 floating point registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: > >> 'SSE registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: > >> 'AVX registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, > >> xstate_sizes[2]: 256 > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, > >> context size is 832 bytes, using 'standard' format. > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. > >> Nov 26 22:38:00 dom0 kernel: Released 0 page(s) > >> Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x-0x0009bfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0009c800-0x000f] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0010-0x67e1] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e2-0x67e20fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e21000-0x67e6afff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e6b000-0x67ebcfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67ebd000-0x68bedfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x68bee000-0x6ee48fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ee49000-0x6f7adfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6f7ae000-0x6ff99fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ff9a000-0x6fffefff] ACPI data > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6000-0x6fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x7000-0x77ff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xe000-0xefff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfe00-0xfe010fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfec0-0xfec00fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfed9-0xfed91fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfee0-0xfeef] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xff00-0x] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0001-0x000191f95fff] usable > > > > > > Yes, I can confirm that issue (except for the "around the time I start a > > VM"). Didn't find anything yet neither, my log looks similar. Some > > memory balancing tends to be the last entry.
Re: [qubes-users] Random sudden reboots
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-11-27 13:37, Wael Nasreddine wrote: > On Monday, November 27, 2017 at 11:09:12 AM UTC-8, David Hobach > wrote: >> On 11/27/2017 07:57 PM, David Hobach wrote: >>> On 11/27/2017 07:47 AM, Wael Nasreddine wrote: I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in the last few hours, often around the time I start a VM. I do not see anything in the log. P.S: I've been running Citrix XenServer for two years on this machine with no issues. [...] >>> >>> Yes, I can confirm that issue (except for the "around the time >>> I start a VM"). Didn't find anything yet neither, my log looks >>> similar. Some memory balancing tends to be the last entry. >> >> P.S.: I run a T530 with coreboot, some i5, ME cleaned. >> >> I'm not sure whether it's a heat issue, but I'd guess not as I >> had tested it until ~95 Celsius and it tends to run at max 80 >> with Qubes. I think it reboots at ~100 Celsius. >> >> But yes, it tends to happen at relatively high load. > > It happened to me regardless of load, I had only essential VMs with > one Firefox opened the last time it happened, also I was not trying > to start up a VM. > It looks like you may be encountering this known bug: https://github.com/QubesOS/qubes-issues/issues/3079 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJaHMkhAAoJENtN07w5UDAwpiIP/AmiSKhNwhmQaCF2RCOiTvvy eZ/JgtgKGn04fRELNHp5ban71hHOt5ra5Z0r91UUX1ClR1gGpRm3Nmnq6Bb2wmTe u8GpgP2n6AWzw9GR/sl2iCgTisC7tBErsdI61lmkN+YvOhdrAeWyiWDssEna/0qV KN9QEIxcIytblAXf+daaYF6dLbia1InShkZ5EaCf8JAlADSPkGC2+dfcCquO3Klv Gp4JZFsEKWKkqdjGtMAjPzdqApABUQjUHgd8/vWpCvbygtw3aBbNfAXeiYdOwDj9 ixMrUTglDkidn3NBhHpjZcPA99plnKSB3YFIclKBd8TC7vKW6mF1r/aDK/T85waz HN6tgIWRmLmdbDpFkHEVwOgxQkq6KPMqK4dEF77fLDU+uEHaCRrRxPxtw4PQXqeu uU5ctJn3hp4DlchJptq8m5qViMYspUj/9G3zByk50EKTMluqn/vJsbAvwkeFsE1x wvmaMMtwSQM55hxV2giggAjCeoMsux6xuMzlNyIISDAWfRS0Pbj5QxAYnKmCasd1 JNywt8n3KDsJ70KQNgVOGmKoybOxbM6uxtLZp1M9r1g1gvnFn+CXfC7yH0OTlIRO vEkmx7068WqUl0TBECvx8gT+fbpg24yUiSdgDWvHeegLdwJ+EZAZL34Pjey1vpec EHi/3jR4SRlv4ERPGrdB =J39y -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/54c50a9e-8d57-fc34-f515-f02f7353b330%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Random sudden reboots
On Monday, November 27, 2017 at 6:25:58 PM UTC-8, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-11-27 13:37, Wael Nasreddine wrote: > > On Monday, November 27, 2017 at 11:09:12 AM UTC-8, David Hobach > > wrote: > >> On 11/27/2017 07:57 PM, David Hobach wrote: > >>> On 11/27/2017 07:47 AM, Wael Nasreddine wrote: > I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got > two hard reboots in the last few hours, often around the time > I start a VM. I do not see anything in the log. > > P.S: I've been running Citrix XenServer for two years on this > machine with no issues. > > [...] > >>> > >>> Yes, I can confirm that issue (except for the "around the time > >>> I start a VM"). Didn't find anything yet neither, my log looks > >>> similar. Some memory balancing tends to be the last entry. > >> > >> P.S.: I run a T530 with coreboot, some i5, ME cleaned. > >> > >> I'm not sure whether it's a heat issue, but I'd guess not as I > >> had tested it until ~95 Celsius and it tends to run at max 80 > >> with Qubes. I think it reboots at ~100 Celsius. > >> > >> But yes, it tends to happen at relatively high load. > > > > It happened to me regardless of load, I had only essential VMs with > > one Firefox opened the last time it happened, also I was not trying > > to start up a VM. > > > > It looks like you may be encountering this known bug: > > https://github.com/QubesOS/qubes-issues/issues/3079 > Not sure that it is, #3079 is about kernel killing X due to OOM, but my issue is that the entire server reboots, so the screen goes black and a few seconds later I'm greeted by the bios boot. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7b7ad5ef-e92a-475f-ac91-1e7671d7fb7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Random sudden reboots
On Monday, November 27, 2017 at 2:09:12 PM UTC-5, David Hobach wrote: > On 11/27/2017 07:57 PM, David Hobach wrote: > > On 11/27/2017 07:47 AM, Wael Nasreddine wrote: > >> I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard > >> reboots in the last few hours, often around the time I start a VM. I > >> do not see anything in the log. > >> > >> P.S: I've been running Citrix XenServer for two years on this machine > >> with no issues. > >> > >> Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed > >> for user root > >> Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:session_close > >> grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ > >> Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" > >> exe="/usr/bin/sudo" hostname=? addr=? > >> Nov 26 22:36:38 dom0 kernel: audit: type=1106 > >> audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi > >> Nov 26 22:36:38 dom0 kernel: audit: type=1104 > >> audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> balance_when_enough_memory(xen_free_memory=97794733, > >> total_mem_pref=5101760998.4, total_available_memory=60546306417.6) > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> left_memory=24233992215 acceptors_count=1 > >> -- Reboot -- > >> Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal > >> (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. > >> Nov 26 22:38:00 dom0 kernel: Linux version > >> 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 > >> 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 > >> Nov 26 22:38:00 dom0 kernel: Command line: placeholder > >> root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro > >> rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: > >> 'x87 floating point registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: > >> 'SSE registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: > >> 'AVX registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, > >> xstate_sizes[2]: 256 > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, > >> context size is 832 bytes, using 'standard' format. > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. > >> Nov 26 22:38:00 dom0 kernel: Released 0 page(s) > >> Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x-0x0009bfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0009c800-0x000f] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0010-0x67e1] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e2-0x67e20fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e21000-0x67e6afff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e6b000-0x67ebcfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67ebd000-0x68bedfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x68bee000-0x6ee48fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ee49000-0x6f7adfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6f7ae000-0x6ff99fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ff9a000-0x6fffefff] ACPI data > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6000-0x6fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x7000-0x77ff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xe000-0xefff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfe00-0xfe010fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfec0-0xfec00fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfed9-0xfed91fff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xfee0-0xfeef] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xff00-0x] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0001-0x000191f95fff] usable > > > > > > Yes, I can confirm that issue (except for the "around the time I start a > > VM"). Didn't find anything yet neither, my log looks similar. Some > > memory balancing tends to be the last entry.