On 4/13/19 7:56 AM, unman wrote: > On Sat, Apr 13, 2019 at 08:36:19AM +0200, David Hobach wrote: >> On 4/12/19 5:24 PM, Michael Siepmann wrote: >>> On 8/10/18 12:37 PM, Kelly Dean wrote: >>> >>>> Am I the only one having a problem with Qubes spontaneously rebooting on >>>> Intel hardware? Only other reports I see are about AMD problems, but I'm >>>> using an Intel Core i3. >>>> >>>> Happens every few weeks. Sometimes just 1 or 2 weeks, sometimes 5 or 6. >>>> Got it on Qubes 3.2, and now 4.0 too (new installation, not upgrade), >>>> multiple times. >>>> >>>> Unlikely to be a hardware problem. The system passed both memtest86 and a >>>> multi-day mersenne prime stress test. And other OSes tested on this >>>> hardware before I switched to Qubes, including Debian and Windows, never >>>> had a problem. >>>> >>>> The rebooting seems completely random. No apparent trigger, and no >>>> warning. Acts like an instant hard reset. Sometimes even when the system >>>> is idle, and I haven't touched the console for hours. >>>> >>>> It's wearingly inevitable enough that I don't even bother intentionally >>>> rebooting after system updates anymore, in order to minimize how many >>>> reboots I have to deal with (setting my workspace back up is an ordeal), >>>> because I know the system will end up spontaneously rebooting a week or >>>> two later anyway. >>> I'm having this problem too. I hadn't had it for a while but in the past >>> week or so it's happened a few times. I have a Lenovo ThinkPad T440p >>> with Intel Core i7, and Qubes 4.0 which I keep updated. >> Same here, but only since 4.0 and since coreboot & ME-cleaner on a T530. >> >> I've always suspected that it's related to memory kills (there was an OOM >> issue on github), but there's absolutely nothing in the journal after such a >> "forced" reboot. >> > I dont see this on any machine, including long running desktops. > Is it possible that you are suffering from over-heating? That would > account for symptoms.
I'm now monitoring temperatures with the "sensors" command in a dom0 terminal and although the problem hasn't yet happened again, the temperatures I'm seeing are often getting close to or even reaching "Critical": coretemp-isa-0000 Adapter: ISA adapter Package id 0: +100.0°C (high = +84.0°C, crit = +100.0°C) Core 0: +99.0°C (high = +84.0°C, crit = +100.0°C) Core 1: +100.0°C (high = +84.0°C, crit = +100.0°C) acpitz-virtual-0 Adapter: Virtual device temp1: +99.0°C (crit = +200.0°C) thinkpad-isa-0000 Adapter: ISA adapter fan1: 4788 RPM If over-heating is the cause, does that suggest a hardware problem, or is there something I can do to configure Qubes differently to stop it from getting so hot? Thanks! -- 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/5ed85497-3b60-757f-c74a-0b7cc20bb5bb%40TechDesignPsych.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature