XServe Persists in Crashing with 3188

Hello All,

My XServe still seems to 'unexpectedly restart' even after installing the latest stable build. I have attached a few logs if anyone has insight on the issue. I just reported it to Parallels.

panic(cpu 0 caller 0x68F18CC4): Uncorrectable Fbd memory error detected. ferr = 20000000 , nerr == 00000000, fErrFat = 20000000 nErrFat == 00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x108cd8 : 0x128d08 (0x3cb134 0x108cfc 0x131de5 0x0)
0x108d18 : 0x68f18cc4 (0x68f1af1c 0x20000000 0x0 0x20000000)
0x108da8 : 0x68f18f58 (0x8297400 0x8297400 0x2 0x820044)
0x108e38 : 0x59732712 (0x8297400 0x0 0x7f62000 0x0)
0x108e68 : 0x5973259b (0x7f33c00 0x0 0x0 0x1c)
0x108e88 : 0x597459be (0x1c 0x108ef8 0x8 0x597474be)
0x108eb8 : 0x59745b68 (0x7f2eb1c 0x17 0x7f33b4a 0x7e43120)
0x108f18 : 0x59752743 (0x7f30ea8 0x0 0xea2827de 0x9240)
0x108f38 : 0x599004fb (0x7f30ea8 0x0 0x7d16c80 0x0)
0x108f68 : 0x5973853f (0x7e10b00 0x0 0x7effb00 0x49)
0x108f88 : 0x59731c1f (0x7d93600 0x0 0x7effb00 0x49)
0x108fa8 : 0x3bb95a (0x7f06a80 0x0 0x7f06c00 0x49)
0x108fe8 : 0x19aef0 (0x49723c90 0x49723c90 0x19bf46 0x57e000)
0x49723d28 : 0x135676 (0x1 0x7d31d40 0x0 0x0)
0x49723d78 : 0x135819 (0x11f576 0x0 0x0 0x19e23a)
0x49723d98 : 0x11ff83 (0x11f576 0x4b1480 0x0 0x2) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleMCEDriver(1.1.2f1)@0x68f15000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x596dc000
com.apple.driver.AppleAPIC(1.2.0)@0x598ff000
com.apple.driver.AppleACPIPlatform(1.0.8)@0x59730000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x596c6000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x596dc000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

Model: Xserve1,1, BootROM XS11.0080.B00, 4 processors, Dual-Core Intel Xeon, 2 GHz, 5 GB
Graphics: ATI Radeon X1300, ATY,RadeonX1300, PCIe, 64 MB
Memory Module: BRANCH 0 CHANNEL 0/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: BRANCH 0 CHANNEL 1/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: BRANCH 1 CHANNEL 0/DIMM 3, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: BRANCH 1 CHANNEL 1/DIMM 4, 2 GB, DDR2 FB-DIMM, 667 MHz
Network Service: Built-in Ethernet 1, Ethernet, en0
Network Service: Built-in Ethernet 2, Ethernet, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
PCI Card: ATY,RadeonX1300, Display, Mezzanine
Parallel ATA Device: MATSHITADVD-R UJ-85J
USB Device: Frontpanel Controller, Apple Computer, Up to 12 Mb/sec, 500 mA
FireWire Device: built-in_hub, unknown_value, Unknown

View attachment panic.log.txt

 

Hello,

Did it start happening since installing Parallels Desktop or since installing latest 3188 build?
Do you have a good sequence of actions to repro the problem?

Having a quick look at the trace log, I don't see any Parallels Desktop drivers on top of the stack. Can you please run memtest on your xServe to make sure it is not faulty memory that causes the crash? A good number of such crashes are caused exactly by faulty memory.

I would appreciate a chance to dig deeper into the issue. Can you send me your email address into private messages?

 

It started happening after installing Parallels Desktop for the first time. (I think I started with Build 1970) This was within thirty days of receiving the server though, for all that means. My sequence of actions is to let it sit... I know it sounds strange, but that is all I do. The XServe runs XP Pro w/SP2 running MSSQL Lite which up to 6 people are accessing at a time... And that is the extent to which we touch anything. The XServe is running a variety of other services, but those all are configured and just run. Even when the XServe restarts I rarely even go in as it gets fully up and running again on its own.

I will give you the result of the memtest shortly.

I have to thank you for the fast response.

 

Hello again, Tim.

I just 'tried' running the memory test... It crashed my Server. I guess I know what our issue is then... I'm still somewhat green when it comes to the hardware side of things... Are you able to tell by the log which stick of memory is causing my most comfortable of headaches?

 

Great news! You're just a step away from fixing the problem.

Unfortunately, it is not possible to locate the faulty stick via logs - they just tell that something is wrong on software layer and don't provide any idea of what is wrong on hardware one I'm afraid your only option now is old good "replace one - check what happens" method.

 

I'll get moving on this issue with Apple. Thanks a bunch for looking at this!

Parallels is a great product, and it seems to be working for the most part now... I just have to go see if the Palm Treo 700p on our iMac issue now works with this new build now...