Not-fatal errors related to EDAC

[fuy]

Hello,

I have a Supermicro X7DVL-E setup which runs great using Ubuntu 7.10 - but Hardy Alpha 5 does not want to startup.

The last message I can see is,

[ 97.156228] EDAC MCO: Giving out device to 'i5000_edac.c' 'I5000' : DEV 0000:00:10.0

I also attached a screenshot of the messages during starting Hardy Alpha 5.

Please let me know what I can do to add more information to this problem.

Regards,
Frederik.

[James Westby (james-w)]

Hi,

Here is where the last message is printed:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/edac/edac_mc.c;h=063a1bffe38b026ba7005ee0b105a4e956baf6e9;hb=HEAD#l519

There was a bunch of work done on this file 2007-07,
giving the following diff

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdiff;f=drivers/edac/edac_mc.c;h=063a1bffe38b026ba7005ee0b105a4e956baf6e9;hp=7b622300d0e58f2c4ef43fe4e6d99022688f2600;hb=HEAD;hpb=9794f33ddedd878dd92fcf8b4834391840366919

Thanks,

James

[fuy (frederikuyttersprot)]

James,

Anything I should do with that as this is close to Chinese for me.
Are these changes in the current kernel that is used by Hardy or not?

Regards,
Frederik.

[James Westby (james-w)]

Hi Freferik,

I also do not understand the changes, I was just
adding some information for someone else to look
at when they consider your report.

I think they are changes from gutsy to hardy, yes.

However, it is also possible that the failure is not actually
in this area, it is in the next step that the kernel tries
to do.

Thanks,

James

[fuy (frederikuyttersprot)]

FYI.

I have the same (or at least similar issue) with openSUSE 11.0 Alpha 2. My rerpot,
https://bugzilla.novell.com/show_bug.cgi?id=367109

I hope someone picks this up.

Regards,
Frederik.

[Leann Ogasawara (leannogasawara)]

Hi fuy,

Care to test Alpha6 and verify this is still an issue? http://cdimage.ubuntu.com/releases/hardy/alpha-6/ You should be able to test via the LiveCd. Please let us know your results. Thanks.

[fuy (frederikuyttersprot)]

Leann,

Similar result. Last message is also about EDAC. Then nothing anymore.
I'm using the AMD64 ISO image (as I'm using it for 7.10). The keyboard is "dead" also.

See attached screen shot.

As a side note, I won't be online the coming week. I can help again from Monday 17the of march again.

R.

[fuy (frederikuyttersprot)]

A small update.

Besides Ubuntu 7.10, openSUSE 10.3 has no problems with the system.
Nobody from Ubuntu team that is interested in this problem?

I'll test again with the next release (beta 1 I suppose).

Regards,
Frederik.

[James Westby (james-w)]

Setting to New, as it was tested on alpha6.

Thanks,

James

[fuy (frederikuyttersprot)]

Report on Ubuntu 8.04 beta 1. The system is able to start the live cd ! Yah Yah.

I do still get messages (errors ?) from EDAC. Not sure what they mean,

[ 126.013760] EDAC MC0: Giving out device to 'i5000_edac.c' 'I5000': DEV 0000:00:10.0
[ 126.192000] EDAC PCI0: Giving out device to module 'i5000_edac' controller 'EDAC PCI controller': DEV '0000:00:10.0' (POLLED)

and quite a lot of messages like (I hope someone knows what those mean),

[ 127.057184] EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x2000
[ 127.057188] EDAC MC0: CE row 2, channel 1, label "": (Branch=0 DRAM-Bank=1 RDWR=Read RAS=0 CAS=0, CE Err=0x2000)

I will attach the dmesg log message. The system is quite slow once it's fully loaded.
I also get an error from the GNOME Settings Deamon (I'll add a screenshot). This is probably another bug but I prefer to focus on this one for now.

Regards,
Frederik.

[fuy (frederikuyttersprot)]

A quick Google for the NON-FATAL ERRORS only gave one hit,

http://forums.fedoraforum.org/archive/index.php/t-175116.html

Regards,
Frederik.

[fuy (frederikuyttersprot)]

I've done some more investigations. I have the following setting in the BIOS of the motherboard,

SERR Signal Condition
This setting species the ECC Error conditions that an SERR# is to be asserted.
The options are None, Single Bit, Multiple Bit, and Both.

When I use None or Single Bit the system can boot but as mentioned above shows a LOT of non-fatal errors.
When I use Multiple or Both the system does not boot as it was before beta 1.

I've run memtest (v2.01, http://www.memtest.org/) with and without ECC during a night (+8 hours) and it found no errors.
Besides that, the system has been running fine for almost a year on Ubuntu 7.10.

I really hope someone is looking into to this (if so please give me some feedback).

Regards,
Frederik.

[fuy (frederikuyttersprot)]

Just for the record.

The release of Ubuntu 8.04 LTS works great. Boots fine and quickly.
I still do have a lot of 'non-fatal' messages but the system is stable and everything works up to now (expect my screen resolution - but that's another topic :-)).

I mentioned my 'issues' on the EDAC mailing list also.

Thanks for listening. Keep up to the good work.

Frederik.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[fuy (frederikuyttersprot)]

Hello,

I don't have the same hardware at this moment as I had at the time of the
alpha's & beta's of 8.04.
I will see what I can do but I can't promise anything.

R.

On Thu, Aug 28, 2008 at 7:49 PM, Leann Ogasawara <email address hidden> wrote:

> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to test:
>
> 1) If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves the
> bug reported here or if the issue remains. More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel. Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> Not-fatal errors related to EDAC
> https://bugs.launchpad.net/bugs/198122
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[James Westby (james-w)]

Hi,

I don't think there's a need to test, as you reported
that the problem was fixed with 8.04, I just missed that
and left the bug open.

Thanks,

James

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.