Hi Ben,
After a few days monitoring this issue, I can confirm that the problem
disappeared since new RAM
modules were installed.
So, feel free to close this bug report under your own criteria.
Thanks a lot for your help.
Regards,
--
Dario Minnucci mid...@debian.org
Phone: +34 902884117
Hi again,
I've found a reference to this error [0] providing and a possible patch is
provided.
Regards,
[0] https://patchwork.kernel.org/patch/67658/
--
Dario Minnucci mid...@debian.org
Phone: +34 902884117 | Fax: +34 902024417 | Support: (+34) 80745
Key fingerprint = BAA1 7AAF B21D
Hi Dario,
Dario Minnucci wrote:
I've being configuring a new server for a couple of days now, and
suddenly today I've started being flooded with this message at the
console.
Don't know if this is a clue but this message triggered while I was
making a tarball from a mounted disk a while ago
Hi Jonathan,
Thanks you and Ben for the quick reply!
The most useful thing you can try to track this down is swapping out
the RAM and seeing if the errors go away.
I'll open a ticket at the provider asking for a RAM test and|or RAM replacement.
See
On Wed, 2011-06-15 at 07:50 +0200, Dario Minnucci wrote:
Hi again,
I've found a reference to this error [0] providing and a possible patch is
provided.
Regards,
[0] https://patchwork.kernel.org/patch/67658/
I've reopened the bug and will check how it got fixed in mainline Linux
(not
Hi Ben,
On 06/15/2011 09:13 PM, Ben Hutchings wrote:
On Wed, 2011-06-15 at 07:50 +0200, Dario Minnucci wrote:
Hi again,
I've found a reference to this error [0] providing and a possible patch is
provided.
Regards,
[0] https://patchwork.kernel.org/patch/67658/
I've reopened the bug
On Wed, 2011-06-15 at 21:38 +0200, Dario Minnucci wrote:
Hi Ben,
On 06/15/2011 09:13 PM, Ben Hutchings wrote:
On Wed, 2011-06-15 at 07:50 +0200, Dario Minnucci wrote:
Hi again,
I've found a reference to this error [0] providing and a possible patch is
provided.
Regards,
Hi again Ben,
I've got me RAM replaced a while ago and no sign og the flloding yet, so I
guess no further testing
will be posible on my side. :(
So we don't know whether those were genuine ECC error reports...?
These are the only references reported by dmesg now so, I guess (as you
8 matches
Mail list logo
