On 4/19/19 12:45 AM, Jon deps wrote:
> On 4/13/19 8:01 PM, Michael Siepmann wrote:
>>  
>> On 4/13/19 12:28 PM, Chris wrote:
>>> Hello Michael,
>>>
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Friday, April 12, 2019 3:24 PM, Michael Siepmann
>>> <[email protected]> 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.
>>>>
>>>
>>> I had this problem which was due to Intel AMT Control being enabled in
>>> the BIOS. Since turning this off my system has not rebooted.
>>>
>>> Regards,
>>>
>>> Chris
>>>
>>> -
>>> Chris Willard
>>> [email protected]
>>> <mailto:[email protected]>
>>
>>
>> Thanks for the suggestion, Chris. I appreciate it. I checked and Intel
>> AMT was already disabled so I guess something else must be causing it in
>> my case.
>>
>>
>
> and what does
> #journalctl -r   say if anything ?
>
In a dom0 terminal if I type "journalctl -r" I see a lot of info.
Anything in particular I should look for?


-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c725a9e8-3151-af72-b688-5bb4e4b7bf45%40TechDesignPsych.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to