Ubuntu

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

Bug #881164 reported by Arul on 2011-10-25

This bug affects 5 people

Affects

Status

Importance

Assigned to

Milestone

Ubuntu

Fix Released

Undecided

Unassigned

You need to log in to change this bug's status.

Affecting:	Ubuntu
Filed here by:	Arul
When:	2011-10-25
Confirmed:	2011-10-26
Started work:	2013-11-17
Completed:	2013-11-17

Target

Distribution
Package	(Find…)
Project	(Find…)

Status	Importance
	Undecided

Assigned to

	Nobody
	Me

Comment on this change (optional)

Email me about changes to this bug report

(?)

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: Edit Tag help

Arul (aselvan) wrote on 2011-10-25:

output of lspci,lsusb & lshw Edit (6.6 KiB, text/plain)

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

Launchpad Janitor (janitor) wrote on 2011-10-26:

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

Changed in ubuntu:
status:	New → Confirmed

Frank (frank-scriptzone) wrote on 2011-10-26:

lshw Edit (28.2 KiB, text/plain)

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"

Frank (frank-scriptzone) wrote on 2011-10-26:

lshw lspci lsusb Edit (32.0 KiB, text/plain)

To be complete:

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

Arul (aselvan) wrote on 2011-11-01:

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.

Huang Ying (ying-huang) wrote on 2011-11-15:

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

acpidump > acpi.dump

Frank (frank-scriptzone) wrote on 2011-11-15:

acpidump output Edit (95.3 KiB, text/plain)

Sure :)

Arul (aselvan) wrote on 2011-11-15:

output of "acpidump >acpi.dump 2>&1" Edit (106.6 KiB, text/plain)

Here is mine as well.

Huang Ying (ying-huang) wrote on 2011-11-16:

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

Frank (frank-scriptzone) wrote on 2011-11-16:

#10

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.

Arul (aselvan) wrote on 2011-11-16:

#11

Mine is 32bit

Huang Ying (ying-huang) wrote on 2011-11-17:

#12

Hi, Frank,

Do you still have the bug after moving to x64?

Best Regards,
Huang Ying

Huang Ying (ying-huang) wrote on 2011-11-17:

#13

fix_readq.patch Edit (493 bytes, text/plain)

Please try the patch attached.

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2011-11-17:

#14

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

Frank (frank-scriptzone) wrote on 2011-11-17:

#15

In reply to #12 :

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

Arul (aselvan) wrote on 2011-11-29:

#16

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!.

Huang Ying (ying-huang) wrote on 2011-11-30:

#17

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

ghes.disable= works on my system.

Federico Stirparo (fstirparo) wrote on 2012-01-07:

#18

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!

Federico Stirparo (fstirparo) wrote on 2012-01-07:

#19