Pci Ue Error
Contents |
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM edac error Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < handling mce memory error Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries
Edac-util: Error: No Memory Controller Data Found.
VoIP_News Inside-ERP MacProTX Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Craig Borysowich Locutus Dennis Stevenson DukeGanote Richard iudithm mircea_luca Clinton Jones bracke Nikki Klein AbhaiTripathi Iqbalyk Adrian_Grigoriu
Ce Memory Read Error
bluesguyAZ59 numbersguyPA COMPANIES Wave Direct Avaya Pivotal CRM SendGrid View All Topics View All Members View All Companies Toolbox for IT Topics UNIX Groups Ask a New Question Solaris The Solaris group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance. Home | Invite edac sbridge lost memory errors Peers | More UNIX Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Fatal PCI UE Error kenny Thomas asked Jun 19, 2012 | Replies (4) I have a Netra 240 that is not booting. This is the error being reported, has anyone encountered this error and possible solution. ereport.io.pci.sta ena=10970e208600401 detector=[ version=0 scheme="dev" device-path="/pci@1c,600000" ] pci-status=aa0 pci-command=146 pci-pa=0 ereport.io.tom.ecc.drue ena=10970e208600401 detector=[ version=0 scheme="dev" device-path="/pci@1c" ] ecc-afsr=400000001c000000 ecc-afar=1050a46000 ecc-ctrl=e000000000000000 ecc-syndrome=0 ecc-err-type="U" ecc-err-disposition= 0 mem-resource=[ version=0 scheme="mem" unum="MB/P1/B0: B0/D0 B0/D1" ] ereport.cpu.ultraSPARC-IIIi.fru ena=10970db1d800401 detector=[ version=1 scheme="cpu" cpuid=1 cpumask=34 serial="16BDBCF1469" ] afsr=8001806 afar-status=0 afar=7c600000800 pc=1042178 tl=0 tt=63 privileged=1 multiple=0 syndrome-status=1 syndrome=6 e
it out completely. Thanks to Surender Dinkar, Gene Beaird, Bill Voight, Kevin Buterbaugh, Jay Lessert and Joe Fletcher for their help. In short: 1) it is a cpu fault, or at least of
Edac Vs Mcelog
the memory mounted on the cpu board and 2) apparently Sun's world-wide policy is edac mc0 to sit it out. If a panic happens twice in a short period (< 1 year) on the same CPU, Sun will edac wiki replace the module. Several people pointed to the cache, which they say uses parity rather than ECC memory. A fully patched box (such as ours) should have a workaround installed, which reduces the incidence, but http://unix.ittoolbox.com/groups/technical-functional/solaris-l/fatal-pci-ue-error-4819783 does not eliminate it. Gene, Bill and Kevin suggested to re-seat the memory banks and cpu-boards, as this helps sometimes. Unfortunately, under our maintenance contract we are not allowed to physically touch the box and Sun did not want to send an engeneer to do even that... it would introduce new unknown variables. We can do nothing but wait for the inevitable it seems... Nobody had an answer to the http://osdir.com/ml/os.solaris.managers.summaries/2004-02/msg00059.html differences between UE errors with different Syndromes. As said the references I found referred to Syndrome 0x03, whereas our error showed Syndrome 0x77. Surender sent a summary posted to this list in April 2002, with an excellent discussion of the E-Cache error and the Sun CTO and Sombrero modules, by Buddy Limpkin. The subject of that summary however was an EDP error rather than an UE error. I guess the question remains: does anybody know what the different syndromes mean, if anything. As to the qla error messages in the log, Kevin reinforced my opinion that forceloading the drivers is not necessary. None of these devices contain boot partitions. In the mean time we have been able to trace at least some of those to a faulty UPS that the storage array is plugged into (the panicky server is not plugged in there, though). Cheers, -- Tony van Lingen Technical Consultant The original question follows. ============================== Dear All, Last monday we've experienced an unexplaned panic that seems to be due to a memory fault. We've reported it to Sun Support, who basically advise us to sit back and hope it won't happen again Obviously this is not a nice prospect, since it is on our main intranet and mail server.
Close Products Mobile Skip to Next Menu Mobile Cell Phones Discover the LG V20 Discover the LG G5 Discover LG Mobile Promotions Enterprise Mobile Solutions All Phones AT&T Phones http://www.lg.com/us/support/product-help/CT00000305-1394563702295-ue Sprint Phones T-Mobile Phones Verizon Phones Unlocked Phones X Series Tablets Smart Watches https://blogs.oracle.com/olympus/entry/fault_management_coordination_between_solaris LG Friends Bluetooth Headsets & Headphones Discover LG TONE Mobile Accessories All Mobile Accessories Cases & Covers Batteries Chargers Keyboards Mounts Docks Portable Photo Printers Clearly Capture Life in Motion Discover the LG V20 Close TV/Audio/Video Skip to Next Menu TV/Audio/Video Home Entertainment TVs All TVs OLED TVs Super UHD TVs memory error 4K Ultra HD TVs LED TVs LG Promotions Home Audio All Home Audio Wireless Speakers Sound Bars & SoundPlates Shelf Stereo Systems Portable Bluetooth Speakers Docking Stations Home Theater Systems Home Video Blu-ray Players DVD Players Projectors TV Audio Video Accessories Magic Remote TV Wall Mounts 3D Glasses Not a New TV. A New Category of Television. Discover LG OLED Close Appliances Skip to Next pci ue error Menu Appliances LG Promotions Kitchen Appliances Refrigerators All Refrigerators French Door Side-by-Side Bottom Freezer Top Freezer Door-in-Door® Cooking Appliances All Cooking Appliances Ranges & Ovens Wall Ovens Cooktops Microwave Ovens LG Studio Dishwashers Top Control Dishwashers Front Control Dishwashers Kitchen Accessories All Kitchen Accessories Refrigerator Filters Replacement Oven Knobs Laundry Washers All Washers Front Load Washers TWIN Load Washers SideKick™ Pedestal Washers Top Load Washers Washer Dryer Combos Dryers Steam Clothing Care System LG Styler Laundry Accessories SmartThinQ® Connected Appliances Rest of Home Air Conditioners Air Care Solutions Vacuum Cleaners Robot Vacuum Cleaners LED Lights Home Appliance Accessories For Small Loads That Are a Big Deal Discover LG SideKick™ Close Computers Skip to Next Menu Computers LG Promotions Consumer Monitors All Monitors Gaming Monitors 4K UHD Monitors 21:9 UltraWide® Monitors IPS Monitors LED Monitors Commercial Monitors Desktop Monitors 21:9 UltraWide Monitors Laptops Desktop & All In One Computers Burners & Drives All Burners & Drives Blu-ray Burners and Drives DVD Burners and Drives Get Seriously Professional Experience 21:9 UltraWide® Monitors Close Previous Next Support Skip to Next Menu Support Register a Product Repair Request a Repair Track Repair Locate Repair Provider LG Di
Coordination Between Solaris and SCF By Bob Hueston on Jan 09, 2008 Accurately diagnosing faults on a large and complex system like a Sun SPARC Enterprise M-class server is critical to maintaining server availability. But fault diagnosis is complicated by the fact that Solaris sees a limited view of the universe, while the service processor (SP) sees a different, limited view. In the M-class server line, things are further complicated because two Solaris instances may be sharing the same hardware, and as a result, seeing different errors due to the same hardware fault. Solaris basically sees three types of hardware: CPUs, memory and I/O devices. A real machine, though, is composed of many more components: interconnect ASICs, cables and connectors, power supplies and voltage regulators, and fans, to name just a few. The SP sees these other components. A fault may manifest itself as different errors depending no one's point of view. For example, a fault in an ASIC that connects a CPU to memory might be seen by the SP as protocol errors on the data interconnect, while the effect that Solaris sees is an uncorrectable memory error. Accurate diagnosis and recovery requires the SP and Solaris to coordinate. In the M-class family of servers, the SP/Solaris coordination basically comes in three areas: Memory, I/O and CPU. Memory Errors For the most part, Solaris handles correctable errors in memory. Single-bit, correctable errors in DIMMs are a natural result of physics of dynamic RAMs, and does not, in general, reflect faulty hardware. A stray cosmic ray may hit the device and flip a bit. Thanks to ECC (error correction code) bits, the single-bit error is corrected, and the data is rewritten to memory. There are, however, several memory errors that may imply faulty hardware: Multi-bit uncorrectable errors (UEs). Permanent correctable errors (also called PCEs, or "Sticky" CEs). These are correctable errors that are not cleared by rewriting to memory. They typically represent a stuck bit. Excessive correctable errors in a short period of time, which could indicate a faulty DIMM. Solaris detects all of these errors, and handles each slightly differently. When a UE is detected, the memory controller notifies Solaris and the SCF at the same time. The Solaris Fault Management Architecture (FMA) will retire the page containing the UE, to avoid hitting the same error i