massive syslog entries (GHES: Failed ...) after upgrade to oneiric

Bug #881164 reported by Arul
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

After the upgrade of my natty (server version) to oneiric, my syslog is flooded with massive amount (6 or 7 of these messages below per second) of the messages shown below. I had to filter out this message in my rsyslog configuration to err level to avoid this flooding.

Oct 24 08:26:11 gorilla kernel: [67636.418784] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49376.
Oct 24 08:26:11 gorilla kernel: [67636.418790] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49377.
Oct 24 08:26:11 gorilla kernel: [67636.418794] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49378.

Machine/Model: Dell PowerEdge T110
root@gorilla:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"

Tags: patch syslog
Revision history for this message
Arul (aselvan) wrote :

Additional details of the system components from lspci, lshw, and lsusb.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Frank (frank-scriptzone) wrote :

I can confirm this issue.

user@nightly:~/debug$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"

Revision history for this message
Frank (frank-scriptzone) wrote :

To be complete:

This involves (for me) an Dell PowerEdge R210 running Ubuntu Server (32bit)

Revision history for this message
Arul (aselvan) wrote :

This is affecting several (possibly all) PowerEdge models, can this issue be assigned to someone to take a look?. I'd be glad to provide any further details.

Revision history for this message
Huang Ying (ying-huang) wrote :

Can you provide the acpidump of your machine? That can be gotten via:

acpidump > acpi.dump

Revision history for this message
Frank (frank-scriptzone) wrote :

Sure :)

Revision history for this message
Arul (aselvan) wrote :

Here is mine as well.

Revision history for this message
Huang Ying (ying-huang) wrote :

Do you use the 32 bit system on the machine? That can be checked via "uname -a".

Revision history for this message
Frank (frank-scriptzone) wrote :

I was when I opened this bug.
Moved to x64 some time after that.

Now I think of it, the acpi output was done on x64.

Revision history for this message
Arul (aselvan) wrote :

Mine is 32bit

Revision history for this message
Huang Ying (ying-huang) wrote :

Hi, Frank,

Do you still have the bug after moving to x64?

Best Regards,
Huang Ying

Revision history for this message
Huang Ying (ying-huang) wrote :

Please try the patch attached.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "fix_readq.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
Frank (frank-scriptzone) wrote :

In reply to #12 :

Seems like I can not reproduce this on x64.
At least not on the current version.

Revision history for this message
Arul (aselvan) wrote :

This is still a problem on 32bit, is this patch going to be included in the next kernel update?, if so when?.

For now, I disabled GHES using "ghes.disable=1" to the kernel boot options. Though, I see a log message "ghes: Unknown parameter 'disable'", the spewing of messages are gone!.

Revision history for this message
Huang Ying (ying-huang) wrote :

If someone can test the patch on 32bit, I can try to push it into kernel.

ghes.disable= works on my system.

Revision history for this message
Federico Stirparo (fstirparo) wrote :

Huang, thanks for your help.
I'm having the same problem and my system is a DELL PowerEdge R210 running Oneric 32bit.

I can test the patch, but since it's a production server and I'm not an expert, I would like to have clear instructions on how to apply the patch you posted.

Thanks in advance!

Revision history for this message
Federico Stirparo (fstirparo) wrote :

Some additional information:

root@myserver:/# uname -a
Linux myserver 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 i686 i386 GNU/Linux

Revision history for this message
Arul (aselvan) wrote :

Finally, this problem is fixed in quantal (Ubuntu 12.10)

Revision history for this message
Juan L. Negron (negronjl) wrote :

Reviewing this now.

-Juan

Revision history for this message
Juan L. Negron (negronjl) wrote :

... I posted a comment in this bug by mistake ... please ignore.

-Juan

Arul (aselvan)
Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.