I am running the latest updated version of CentOS on a HP DL160 G6 server as a workstation with the Mate desktop, not Gnome. The only expansion card I have installed is a MSI Geforce GT710 graphics card driving two monitors.
Unfortunately the computer locks up at random intervals: neither the mouse nor the keyboard work and I lose the SSH connection to the computer I have used to see if the entire computer locks up or only the desktop. If I leave the computer in this state it eventually reboots.
Any suggestions on where to begin researching this?
Thank you.
On 2017-05-02 02:49, H wrote:
I am running the latest updated version of CentOS on a HP DL160 G6 server as a workstation with the Mate desktop, not Gnome. The only expansion card I have installed is a MSI Geforce GT710 graphics card driving two monitors.
Unfortunately the computer locks up at random intervals: neither the mouse nor the keyboard work and I lose the SSH connection to the computer I have used to see if the entire computer locks up or only the desktop. If I leave the computer in this state it eventually reboots.
Any suggestions on where to begin researching this?
Thank you.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
dmesg
CentOS 6: less /var/log/messages
CentOS 7: journalctl -xe
It looks like a HW error, maybe CPU or RAM, so I would recommend running memtest and some CPU bench tool as well.
//Zdenek
On 5/1/2017 5:49 PM, H wrote:
Any suggestions on where to begin researching this?
in addition to Zdenek's suggestions, I'd consider running it with the graphics disabled, on centos 6 set /etc/inittab to start at runlevel 3, then reboot. not sure how you do it on c 7.
while its running without graphics, exercise it via ssh connections, running as much stuff as you can. download a linux kernel and compile it with `make clean && make -j 8` over and over, that sort of thing.
On May 1, 2017, at 8:49 PM, H agents@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?
On 05/02/17 06:56, Steven Tardy wrote:
On May 1, 2017, at 8:49 PM, H agents@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
mark
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@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
mark
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
'Failed to start ipmi.service: Unit not found'
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@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
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@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@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.
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@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@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@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.
On 05/02/2017 06:56 AM, Steven Tardy wrote:
On May 1, 2017, at 8:49 PM, H agents@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? _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
mcelog does not exist - should it? I am not familiar with edac.
-
H -
John R Pierce -
mark -
Steven Tardy -
Zdenek Sedlak