LinuxQuestions.org - Getting Kernel[Hardware] message in Mandriva. Need help with it please.

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Getting Kernel[Hardware] message in Mandriva. Need help with it please. (https://www.linuxquestions.org/questions/linux-hardware-18/getting-kernel%5Bhardware%5D-message-in-mandriva-need-help-with-it-please-921758/)

Getting Kernel[Hardware] message in Mandriva. Need help with it please.

This seems to only occur in Mandriva or any fork from them like PCLinuxOS but I've not dealt with this before. For whatever unusual reason either in a Live mode or after installation this message pops up nonstop it seems :

Message from syslog@localhost
Kernel [Hardware Error] : Run the message through 'mcelog --ascii' to decode

and only sometimes it says "No Human Interface for this CPU."

From the little research I've found its a text editor thing like maybe I need Midnight Commander in KDE? Anyone know how to fix or what this means?

Thanks.

Quote:

Originally Posted by barnac1e (Post 4564552)

Message from syslog@localhost
Kernel [Hardware Error] : Run the message through 'mcelog --ascii' to decode

read the mcelog man page. It gives a good explanation.

And could you perhaps guide towards that please
?

Hi,
Welcome to LQ!

Quote:

Originally Posted by barnac1e (Post 4564920)

And could you perhaps guide towards that please
?

On line 'man mcelog' or you could open a terminal an do 'man mcelog.

Just a few links to aid you to gaining some understanding;

  1 Linux Documentation Project 
2 Rute Tutorial & Exposition 
3 Linux Command Guide  
4 Bash Beginners Guide 
5 Bash Reference Manual 
6 Advanced Bash-Scripting Guide 
7 Linux Newbie Admin Guide 
8 LinuxSelfHelp 
9 Utimate Linux Newbie Guide
10 Linux Home Networking
11 Virtualization- Top 10

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

I am editing this because it turns out this issue is not solved and I made an additional post following this one. Thanks

Thanks but still...

Hi,

I appreciate you guys' answers you gave but those links are a thousand pages long, first of all.

Secondly, when I run those commands the BASH script can't even generate output because the error repeats itself there.

Can someone "hold my hand" :cry: here and guide me into the depths of the files to wherever this config file file is that needs "decoding"? I mean I prefer to continue on enjoying all of my new distro installation without an annoying info popup disrupting me ever 20 seconds in the KDE info widget, you know?

Thank you to anyone and much obliged.

Hi,

Quote:

excerpt from ''man mcelog';
X86 CPUs report errors detected by the CPU as machine check events (MCEs). These can be data corruption detected in the CPU caches, in main memory by an integrated memory controller, data transfer errors on the front side bus or CPU interconnect or other internal errors. Possible causes can be cosmic radiation, instable power supplies, cooling problems, broken hardware, or bad luck.
Most errors can be corrected by the CPU by internal error correction mechanisms. Uncorrected errors cause machine check exceptions which may panic the machine.

From the above excerpt you can look at 'dmesg' to see if any other errors are being logged. If not then look at potential problems with CPU cooling, PSU issues or other hardware problems.

You might consider running diagnostics from Tools, Recovery, Diagnostic, Emergency section of Slackware®-Links;

UBCD Ultimate Boot CD <- 'UBCD allows users to run floppy-based diagnostic tools from most CDROM drives on Intel-compatible machines, no operating system required. The cd includes many diagnostic utilities.'

Or;

SystemRescueCd <- 'is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system utilities (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools).' + 'Online-Manual

Run 'memtest86+' to validate the memory. You will find it on the above LiveCDs'.
memtest86+ is a memory tester which is based on memtest86 v3.0, and provides an up-to-date version of this useful tool, which aims to be as reliable as the original. It has been fixed to work on AMD64 systems, and also properly detects all current CPUs and motherboard chipsets. The project supports ECC polling for AMD64, i875P, and E7205, and displays some useful settings for the most popular chipsets'

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson

Yes that is what it is. I have to edit dmesg with mcelog --ascii but it is a read only file. I need to create a new log file and append that to dmesg in a terminal as root. But what is the command to direct dmesg to that new file to add it?

Hi,

Just open a terminal or from console do;

Code:

dmesg >mydmesg

This will direct the output to file 'mydmesg'. Why are you attempting to append the 'mcelog' to 'dmesg'?

Quote:

X86 CPUs report errors detected by the CPU as machine check events (MCEs).

Which states that this will be in mcelog. 'dmesg' should provide additional information for errors or system info.

Thanks. I did a google search with the human interface error on Mandriva 2011 i586 and I found this was some bug and back in the test phase I guess they had some some link to a patch but it doesnt exist anymore. But one one of the links it had on one of the sites I saw a developer say you could also run a code on the terminal 'mcelog --ascii > file' but doing that gave a bash error so I was looking for where a text file with kernel errors were lusted. I found a dmesg.log file I was going to manual paste the text to and save it for the CPU to read on bootup so it could deal with it then.