Comments on: DELL E1420 CPU BUS PERR ERROR on front LCD

By: admin

admin — Wed, 29 Oct 2008 14:53:33 +0000

So I believe it is okay to say that the redhat fix was successful. As far as Dell/Microsoft setup, 1950s and 2950s are still having the problem.

I’m running on the 2970 with Hyper-V now, for well over a month, not a single problem.

By: David

David — Thu, 16 Oct 2008 22:20:50 +0000

Hi Shank,
Great, I think that the problem has been solved.
David

By: shank

shank — Thu, 16 Oct 2008 21:22:01 +0000

Hi david,

How’s it looking today?

By: David

David — Wed, 15 Oct 2008 15:35:40 +0000

Shank,
Still no issues so far.
Thanks
David

By: shank

shank — Wed, 15 Oct 2008 13:41:09 +0000

Hi david.
yes it is an upgrade, but I think you figured that out. Good to hear that the error seems to be gone.

Keep me posted on what happens. I emailed a Dell tech I was working with a few days ago to find out if there were any updates on the Linux end, and of course for the windows site. Still waiting for a response from them.

By: David

David — Wed, 15 Oct 2008 08:15:04 +0000

Shank, after the kernel upgrade the error seems to be gone …finger crossed!

By: David

David — Tue, 14 Oct 2008 09:43:39 +0000

Hi Shank,
Thanks a lot for the info, the situation matches completely with ours.We are updating the kernel but while compiling it to the updated version we are having crashes when accessing the storage due to multipath(other issues).
The link you are referring to is the link to the new kernel or a patch to fix this problem?if it is a fix will be great to quickly test it if not…we need to keep on working…:-(
Thanks again for your help…
David

By: shank

shank — Mon, 13 Oct 2008 14:15:57 +0000

http://kbase.redhat.com/faq/FAQ_85_11695

^ That link may help, that’s what I found in my emails.

Still looking for the actual update link.

By: David

David — Mon, 13 Oct 2008 08:07:44 +0000

Thanks Shank,
I know they are different but because they released a new BIOS to address that CPU errors I though it will be fixed also.
The bad news is that with the new BIOS still messaging and crashing the machine sometimes. This started again when they put LUSTRE filesystem on preproduction again…the machines have been previously fully tested (CPU stressing and memtest) with no errors without Lustre filesystem.
So there must be something linked to the filesystem or the kernel patched for LUSTRE filesystem.
This kind of fix for RH would be a great help to see what have been addressed within the kernel.
Thanks again
David

By: shank

shank — Fri, 10 Oct 2008 14:49:25 +0000

Hello.

Now the IERR and PERR are totally different errors. I had the IERR on another 2950 of mine. The exact message was:

CPU1 Status: Processor sensor for CPU1, IERR was asserted
CPU2 Status: Processor sensor for CPU2 IERR was asserted

Did you have this error? Dell asked me to reseat everything, which made no sense to me. Without reseating, anda simple reboot, the machine ran fine, and still has.

Let me take a look into the RedHat fix for you.