Dell E1410 Cpu Error
Contents |
by: [ date ] [ thread ] [ subject ] [ author ] We had similar problem on a dell e1410 system fatal error PE2900-III, although not completely identical. We found out, through trial and
Dell R710 E1410 Error
error, that the problem was the onboard SATA controller. I don't know if it is the hardware or
Cpu 1 Machine Check Error Detected
the drivers for the onboard SATA in RHEL/CentOS, but the onboard SATA controller would lock-up, then cause a fault on the PCI-E bus, which then caused faults on both
A Bus Fatal Error Was Detected On A Component At Bus 0 Device 0 Function 0.
CPUs resulting in instantaneous reboot of the entire server. We finally disabled the onboard SATA completely in the BIOS (switched to IDE based optical drive) and the server has been completely stable since. At the time (this past April), Dell tech support was not aware of this issue and they said we were the first to report on it. dell poweredge 2950 e1410 system fatal error -B. Masuda > -----Original Message----- > From: linux-poweredge-bounces at lists.us.dell.com [mailto:linux- > poweredge-bounces at lists.us.dell.com] On Behalf Of Larsen, Peter > Sent: Friday, August 14, 2009 3:24 PM > To: Tom Cowin; Linux-PowerEdge at lists.us.dell.com > Subject: RE: E1410 CPU IERR on 2950 III > > http://bugs.centos.org/view.php?id=2619 > > That may give you a few answers? > > -- > Peter H. Larsen > Technical Architect > > -----Original Message----- > From: linux-poweredge-bounces at lists.us.dell.com [mailto:linux- > poweredge-bounces at lists.us.dell.com] On Behalf Of Tom Cowin > Sent: Friday, August 14, 2009 2:08 PM > To: Linux-PowerEdge at lists.us.dell.com > Subject: E1410 CPU IERR on 2950 III > > Has anyone gotten this error on a 2950? My server continues to crash > hard, with this error on the front - on both CPUs. The best I can get > from tech support is that this is probably a software configuration > issue - given that CentOS and VMWare is not a "supported" > configuration - although it has been running fine for 18 mon
Issues Roadmap View Issue Details[Jump to Notes] [Issue History] [Print] IDProjectCategoryView StatusDate SubmittedLast Update0003034CentOS-5-OTHERpublic2008-08-07 00:332009-02-18 17:12ReportersteevithakPrioritynormalSeveritycrashReproducibilityalwaysStatusresolvedResolutionfixedProduct Version5.2Target VersionFixed in Version5.2Summary0003034: DELL PowerEdge 1950 - E1410 CPU1 intel cpu ierr IERR E1410 CPU2 IERRDescriptionI'm attempting to install CentOS 5.2 on a new processor 1 has failed with ierr Dell 1950 with two quad-core Xeon CPUs. The install completes but during subsequent boots, the machine dies. Screen ierr spokane goes black, the flashing orange hardware failure light on the back of the server comes on, and the front panel LCD displays "E1410 CPU1 IERR E1410 CPU2 IERR" I should http://lists.us.dell.com/pipermail/linux-poweredge/2009-August/039974.html note that running CentOS 5.0 runs fine on this server, so it appears to be a problem with 5.2. My guess would be faulty Intel microcode or a kernel bug of some sort but I'm not sure how to narrow it down.Additional InformationI noticed a similar bug was reported by a user attempting to run CentOS 4.3 on a Dell https://bugs.centos.org/view.php?id=3034 1950: http://bugs.centos.org/view.php?id=2619 I also spotted a similar crash report from a user running OpenSuse 11 on a Dell 1950 (the reporter suspected a connection to a Xen bug but I'm not running Xen on my server so this one may not be related): http://forums.opensuse.org/install-boot-login/390004-opensuse-11-x86_64-xen-dell-2950-a.html TagsNo tags attached.Attached Files Relationships Relationships Notes ~0007808 smooge (reporter) 2008-08-07 01:01 The Dell site says the problem may occur from bad CPU's or bad PCI cards. Was the CentOS-5.0 box getting updates regularly? If it was then the system would have been running 5.2 via updates.. Also microcode is not updated until microcode_ctl is run. If the system is dieing before it gets to that.. then it is more likely a hardware fault. ~0007811 steevithak (reporter) 2008-08-07 15:59 No, this is a new Dell 1950. We received it with no OS installed. I initially installed CentOS 5.2. When that resulted in crashes on boot, I tried an old set of CentOS 5.0 CDs. CentOS 5.0 works fine but CentOS 5.2 crashes on boot. I burned a new set of CentOS 5.2 CDs today
Issues Roadmap View Issue Details[Jump to Notes] [Issue History] [Print] IDProjectCategoryView StatusDate SubmittedLast https://bugs.centos.org/view.php?id=2619 Update0002619CentOS-44Suitepublic2008-01-23 02:592008-01-23 10:18Reporteroli_rajaPrioritynormalSeveritymajorReproducibilitysometimesStatusclosedResolutionfixedProduct Version4.3 - i386Target VersionFixed in VersionSummary0002619: DELL PowerEdge 1950 - E1410 CPU1 IERR E1410 CPU2 IERRDescriptionHi Community, I have successfully installed 4.3 final (i386) on dell poweredge 1950. The system were working fine for few days/week. Then, system hang suddenly and the LCD fatal error panel displays "E1410 CPU1 IERR E1410 CPU2 IERR". According to Dell, the meaning of the error follows... -------------------------------------------------------------------------------- Intel CPU IERR Filtering Algorithm and Fault Isolation Methodology CPU's manufactured by Intel Corporation have an internal error or IERR signal that is usually tied to an interrupt line e1410 system fatal or to an external monitor. The original purpose of this signal was to indicate an internal, unrecoverable CPU error. The normal procedure is to replace any CPU that signals an IERR. More recently, the IERR signal is also triggered by non-CPU faults. Bus time-out's, forward progress stalls in multi-processor configurations, evaluation versions of Windows operating systems and other non-hardware fault triggers have been identified that result in an active IERR signal. On occasion, two or more CPU's signal an IERR simultaneously. Experiences in the laboratory have shown that the CPU(s) can be restarted and the IERR often does not re-occur. In the field, the result is that non-faulty CPU's are replaced first and the real source of the IERR is discovered only after multiple IERR events and one or more CPU replacements. The IERR Filtering Algorithm and Fault Isolati