On 05/06/2017 10:22 PM, H wrote:> On 05/03/2017 07:47 AM, mark wrote:
>> On 05/02/17 21:49, H wrote:
>>> On 05/02/2017 08:01 AM, mark wrote:
>>>> On 05/02/17 06:56, Steven Tardy wrote:
>>>>>
>>>>>> On May 1, 2017, at 8:49 PM, H <agents at
meddatainc.com> wrote:
>>>>>>
>>>>>> the computer locks up at random intervals
>>>>>
>>>>> Anything in /var/log/mcelog?
>>>>> Is the "edac" module running?
>>>>> Does that model support bundle include any Intel MCA files?
>>>>
>>>> systemctl start ipmi
>>>> ipmitool sel list
>>>>
>>> 'Failed to start ipmi.service: Unit not found'
>>
>> yum install OpenIPMI ipmitool
>>
>> Then systemctl enable ipmi and systemctl start ipmi, then run ipmitool
sel list.
>>
>> Um... I just had a thought - this is a server, right, not a desktop?
>>
>> mark
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>
> It is a server model but I am using it as a desktop. I tried to reply to
this message and include a screenshot of a couple of error messages on the
display before it spontaneously reboots but it seems the message never went
through, nor did I receive an error message.
>
> The error messages were:
>
> [Firmware bug]: The BIOS has corruped hw-PMU resources (MSR 38d is b0)
>
> nouveau 0000:07:00.0: priv: HUB0: 085014 ffffffff (1f70820b)
>
> ERST: Failed to get Error Log Address Range.i_dj_raw_event: inval
>
> mce: Unable to init device /dev/mcelog (rc:-5)
>
> logitech-djreceiver 00003:046D:C52B.0003: logi_dj_raw_event: invalid device
index:0
>
> After which the reboot where it asks me for my LUKS passphrase.
>
> When I looked I could not find any messages i /var/logs/messages.
>
> Suggestions appreciated.
>
> Thank you.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
I finally decided to give the native nvidia driver a shot and installed it
following instructions by T Helmsley I found on the web.
Surprise, surprise! No more lockups, no more spontaneous reboots and no more
error messages from the Logitech mouse! Not only that, the nvidia configuration
program seems to offer settings I could not easily find for the nouveau driver.
Last, but not least, now both monitors go to sleep at the right time (using the
nouveau driver only one of the monitors went to sleep.)
The error message about "Failed to get log error address range"
remains but I gather that has something to do with a BIOS incompatibility that
HP and RHEL have been pointing fingers at each other over for some time.