prahn Posted July 28, 2010 Report Share Posted July 28, 2010 Hi! I just updated today from version 8.1 to version 8.2, hoping that finally most bugs are fixed, that I have to work with for almost a year now... :-( Just when I startet the Retrospect Console on the server, I got a Kernel Panic! So I restarted the machine and did not touch any Retrospect stuff anymore the whole day. This evening, when all working people went home, I started the Console on a client machine. Console started, no problems. But after connecting to the server, the server once again did a Kernel Panic!! So after booting up the server again I tried to stop the Retrospect Engine, but from the GUI, stopping was not successful. After using "kill" in the CLI I finally stopped the Engine. So what can I do now?? Any suggestions? I am really uncertain with my server now!! The Retrospect Engine is running on an Intel XServe with Mac OS X Server 10.5.8 here (2,8 GHz Quadcore, 4 GB RAM, Hardware RAID). Please help me!! Quote Link to comment Share on other sites More sharing options...
Maser Posted July 28, 2010 Report Share Posted July 28, 2010 Did you update both the engine and the console to 8.2? You might try stopping the engine (use the GUI -- but wait a full 10 minutes for it to stop), then move your "config80.dat" and "config80.bak" files to the desktop and restart the engine. (Files are located in /Library/Application Support/Retrospect) This will start the engine clean (no scripts/no sources/no licenses) -- but the console should still try to connect to the engine so you can add your license code, etc... If you are KP'ing with a clean config80.dat file, then something else is wrong somewhere else. If you aren't KP'ing with the clean config80.dat file, then something might be corrupt with your old config80.dat file. I believe you can always *downgrade* to 8.1, too, if you want to see if that addresses the KP. But I'd first see what happens with a clean config80.dat file. Quote Link to comment Share on other sites More sharing options...
prahn Posted July 30, 2010 Author Report Share Posted July 30, 2010 Hi! Thank you for the quick response. So, I did what you suggested, and after moving the config files, I could connect to the Engine without a Kernel Panic. I started re-configuration, but right after adding an SMB network share to a Media Set I got another Kernel Panic!! This is really disappointing. :-( Bugs are not good, but they are reality. But how can a server backup software crashes a server (!), just when setting up some basic configuration. Is there a money-back possibility? I am using Retrospect since Mac OS 8, I was so happy when the new version came out. But after buying this license I had to wait one year for solving a bug, which did not let me backup my local disk. Now, this bug should have been fixed, but now this version is doing one Kernel Panics... really sad, but this could not be true... Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 2, 2010 Report Share Posted August 2, 2010 The Retrospect Engine is running on an Intel XServe with Mac OS X Server 10.5.8 here (2,8 GHz Quadcore, 4 GB RAM, Hardware RAID). "Hardware RAID" In another thread, you describe it as "Apple Hardware RAID". Can you please describe it more thoroughly? - What bus does the RAID use to connect? - Is there a host bus adapter involved? - What is the make, model and firmware of any HBA being used? Quote Link to comment Share on other sites More sharing options...
prahn Posted August 2, 2010 Author Report Share Posted August 2, 2010 Hi! We use the RAID-Card from Apple, which replaces the Original HD Controller. There are two SATA 1 TB drives connected to it, used as a RAID-1 with two partitions on it. Is that all you need? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 2, 2010 Report Share Posted August 2, 2010 Is that all you need? Well, I don't need anything, as I'm not having any difficulties with Retrospect. So if "the RAID-Card from Apple" is as specific as you want to get, I'm not going to try and pry any additional information from you. Now you _could_ visit System Profiler and report the specific model/version of the hardware you're using. But that would be up to you. Is it a "controller?" Or is it simply a SCSI HBA using some software RAID-1 configuration. Who knows? Not us readers... Dave Quote Link to comment Share on other sites More sharing options...
prahn Posted August 2, 2010 Author Report Share Posted August 2, 2010 Hi! Sorry, but I really don't know what information I could give you. I have big trouble using the new Retrospect version and I am searching for some help here. If you don't want to help me solve my problems, I guess you would not answer to my post...?!?! When looking at the System Profiler I read about a "Xserve RAID-Card" as a "Hardware RAID". Hardware Version 1.0 with Firmware M-2.0.5.5. At the Section "SAS" I read under "SAS Domain 0": Apple RAID Card, Version 312E3030. The Xserve itseld identifies as "Xserve 2,1". Quote Link to comment Share on other sites More sharing options...
rhwalker Posted August 2, 2010 Report Share Posted August 2, 2010 So if "the RAID-Card from Apple" is as specific as you want to get, I'm not going to try and pry any additional information from you. Now you _could_ visit System Profiler and report the specific model/version of the hardware you're using. But that would be up to you. Dave, It's a circuit board inside the xServe (recent Intel xServes only, such as this poster has), not a card in any PCI-X or PCI-e slot, as with the older Apple Hardware RAID card (PCI-X) for the xServe G5 (rebranded LSI Logic "Megaraid" card, with firmware bugs). This oddly-shaped circuit board replaces the similarly-shaped drive module connector board above the three drive modules, and it's a build-to-order option. See (scroll down, just below the internal picture of the xServe): Fast, powerful hardware RAID option The particular circuit board differs by Intel xServe vintage, but see, for example: Apple manual for Apple Hardware RAID, 2008 xServe The poster has provided all information possible. Sorry, I don't know the answer to this. Russ Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 3, 2010 Report Share Posted August 3, 2010 Given that, I'd suggest putting a call into Roxio support, telling them you don't want to pay and that you're getting kernel panic on big iron server hardware. There should also be a panic log written after the crash; can you post that here? And ok, I'm sorry for being a douche about it. Dave Quote Link to comment Share on other sites More sharing options...
hippy Posted August 3, 2010 Report Share Posted August 3, 2010 I also get panics having upgraded to 8.2. I upgraded both the console & engine yesterday, ran a couple of test backups these were OK. Over last night my server panic'ed 16 times! all appear to be related to the RetroEngine, and at least 1/2 of them occurred on system startup it appears. I've managed to disable the engine startup, and things appear to be stable again Hardware: Mac Pro 2 x 3Ghz Dual-core 4Gb 667 DDR2 Raid Card OSX 10.5.8 Last Panic, (all others can be provided) ---------------------------------------- Tue Aug 3 08:00:26 2010 panic(cpu 0 caller 0x001AB0FE): Kernel trap at 0x0017f403, type 14=page fault, registers: CR0: 0x80010033, CR2: 0x0b17c18d, CR3: 0x270cb000, CR4: 0x00000660 EAX: 0x00000001, EBX: 0x0b17c179, ECX: 0x09019b58, EDX: 0x07d49460 CR2: 0x0b17c18d, EBP: 0x5c63fde8, ESI: 0x005c1000, EDI: 0x00000000 EFL: 0x00010202, EIP: 0x0017f403, CS: 0x00000008, DS: 0x001a0010 Error code: 0x00000000 Backtrace (CPU 0), Frame : Return Address (4 potential args on stack) 0x5c63fbe8 : 0x12b4c6 (0x45f91c 0x5c63fc1c 0x13355c 0x0) 0x5c63fc38 : 0x1ab0fe (0x469a98 0x17f403 0xe 0x469248) 0x5c63fd18 : 0x1a1713 (0x5c63fd30 0x6d714d4 0x5c63fde8 0x17f403) 0x5c63fd28 : 0x17f403 (0xe 0x7f00048 0x5c630010 0x5c630010) 0x5c63fde8 : 0x162d9a (0x7d49460 0x5c1000 0x0 0x5) 0x5c63ff58 : 0x1ab39c (0x780507c 0x533000 0x1 0x5) 0x5c63ffc8 : 0x1a160d (0x9148a84 0x0 0x1a40b5 0x9148a84) Backtrace terminated-invalid frame pointer 0x4164390 BSD process name corresponding to current thread: RetroEngine Mac OS version: 9L34 Kernel version: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 System model name: MacPro1,1 (Mac-F4208DC8) System uptime in nanoseconds: 142511980650 unloaded kexts: (none) loaded kexts: com.vmware.kext.vmnet 3.0.0 com.vmware.kext.vmioplug 3.0.0 com.vmware.kext.vmci 3.0.0 com.vmware.kext.vmx86 3.0.0 com.sophos.kext.sav 7.1.1 com.belkin.driver.n52te 1.0.2 com.apple.filesystems.afpfs 9.0.2 - last loaded 140025428663 com.apple.nke.asp_tcp 4.7.1 com.apple.filesystems.autofs 2.0.2 com.apple.driver.AppleHDAPlatformDriver 1.7.1a2 com.apple.driver.AppleHDAHardwareConfigDriver 1.7.1a2 com.apple.driver.AppleUpstreamUserClient 2.7.5 com.apple.driver.AppleHDA 1.7.1a2 com.apple.kext.ATY_Alopias 5.4.8 com.apple.driver.AppleHWSensor 1.9d0 com.apple.Dont_Steal_Mac_OS_X 6.0.3 com.apple.driver.AppleTyMCEDriver 1.0.0d28 com.apple.driver.AppleHDAController 1.7.1a2 com.apple.iokit.IOFireWireIP 1.7.7 com.apple.driver.AudioIPCDriver 1.0.6 com.apple.ATIRadeonX1000 5.4.8 com.apple.driver.AppleUSBAudio 2.6.4b17 com.apple.driver.AppleMCEDriver 1.1.7 com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a17 com.apple.driver.AppleLPC 1.3.1 com.apple.driver.XsanFilter 2.7.91 com.apple.driver.iTunesPhoneDriver 1.0 com.apple.driver.AppleHIDKeyboard 1.0.9b4 com.apple.driver.AppleUSBMergeNub 3.5.2 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1 com.apple.iokit.SCSITaskUserClient 2.1.1 com.apple.iokit.IOATAPIProtocolTransport 1.5.3 com.apple.driver.AppleLSIFusionMPT 2.0.3 com.apple.driver.AppleFWOHCI 3.9.7 com.apple.driver.AppleFileSystemDriver 1.1.0 com.apple.driver.AppleUSBHub 3.4.9 com.apple.driver.AppleAHCIPort 1.7.0 com.apple.driver.AppleIntelPIIXATA 2.0.1 com.apple.driver.AppleRAIDCard 70 com.apple.iokit.IOUSBUserClient 3.5.2 com.apple.driver.AppleIntel8254XEthernet 2.1.2b1 com.apple.driver.AppleUSBEHCI 3.4.6 com.apple.driver.AppleUSBUHCI 3.5.2 com.apple.driver.AppleEFINVRAM 1.2.0 com.apple.driver.AppleACPIButtons 1.2.5 com.apple.driver.AppleRTC 1.2.3 com.apple.driver.AppleHPET 1.4 com.apple.driver.AppleACPIPCI 1.2.5 com.apple.driver.AppleSMBIOS 1.4 com.apple.driver.AppleACPIEC 1.2.5 com.apple.driver.AppleAPIC 1.4 com.apple.security.seatbelt 107.12 com.apple.nke.applicationfirewall 1.8.77 com.apple.security.TMSafetyNet 3 com.apple.driver.AppleIntelCPUPowerManagement 76.2.0 com.apple.driver.DiskImages 199 com.apple.BootCache 30.4 com.apple.driver.DspFuncLib 1.7.1a2 com.apple.iokit.IOHDAFamily 1.7.1a2 com.apple.iokit.IONDRVSupport 1.7.3 com.apple.iokit.IOGraphicsFamily 1.7.3 com.apple.iokit.IOAudioFamily 1.6.9fc5 com.apple.kext.OSvKernDSPLib 1.1 com.apple.driver.IOPlatformPluginFamily 3.4.0a17 com.apple.driver.AppleSMC 2.3.1d1 com.apple.iokit.IOUSBHIDDriver 3.4.6 com.apple.driver.AppleUSBComposite 3.2.0 com.apple.iokit.IOBDStorageFamily 1.5 com.apple.iokit.IODVDStorageFamily 1.5 com.apple.iokit.IOCDStorageFamily 1.5 com.apple.iokit.IOFireWireFamily 3.4.9 com.apple.iokit.IOAHCIFamily 1.5.0 com.apple.iokit.IOATAFamily 2.0.1 com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1 com.apple.iokit.IOSCSIParallelFamily 1.5.2 com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1 com.apple.iokit.IONetworkingFamily 1.6.1 com.apple.iokit.IOUSBFamily 3.5.2 com.apple.driver.AppleEFIRuntime 1.2.0 com.apple.iokit.IOSMBusFamily 1.1 com.apple.iokit.IOStorageFamily 1.5.6 com.apple.iokit.IOHIDFamily 1.5.5 com.apple.driver.AppleACPIPlatform 1.2.5 com.apple.iokit.IOPCIFamily 2.6 com.apple.iokit.IOACPIFamily 1.2.0 Quote Link to comment Share on other sites More sharing options...
sleitner Posted August 3, 2010 Report Share Posted August 3, 2010 I have this bug in Beta 2 and in the final version: http://forums.dantz.com/showtopic.php?tid/34333/post/new/#NEW When wil be the next patch version released? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 3, 2010 Report Share Posted August 3, 2010 I have this bug in Beta 2 and in the final version Why would you post that in a thread about an entirely different matter? Especially since Robin has confirmed an open bug for what you're experiencing? If the Apple XServe RAID Card is the common factor among the panic reports, that's important information to mine. Has anyone seen this sort of behavior _without_ the APPLE installed XServe RAID board? Quote Link to comment Share on other sites More sharing options...
maesu Posted August 4, 2010 Report Share Posted August 4, 2010 Same problem here, we are using also a Apple hardware raid card from the beginning. Retro 8.1.x was running without kernel panic. Maybe a bad code in the 64bit version 8.2? BTW. Kernel panic on a server is one of the last things you can use as admin.... we need a quick fix or a downgrade. is a downgrade possible? Quote Link to comment Share on other sites More sharing options...
prahn Posted August 4, 2010 Author Report Share Posted August 4, 2010 @CallMeDave: Should we also make a post in the forum called "Retrospect 8 bug reports" to get this bug fixed? Or do you hand this problem over to the right persons? I also opened a case at Roxio Support in the meantime, but I received no interesting feedback so far! Regards, prahn Quote Link to comment Share on other sites More sharing options...
Mayoff Posted August 4, 2010 Report Share Posted August 4, 2010 I have never seen a software program cause a Kernel Panic. These things always have an underlying hardware problem or operating system corruption to make them happen. Do you have any type of Crash crash reporter logs? Quote Link to comment Share on other sites More sharing options...
rhwalker Posted August 4, 2010 Report Share Posted August 4, 2010 I have never seen a software program cause a Kernel Panic. These things always have an underlying hardware problem or operating system corruption to make them happen. Sorry, Robin, that's just not correct. In a perfect world, it would be right, and yes, the OS and its drivers should be more defensive and prevent this. However, just as Retrospect has numerous bugs, the Mac OS and drivers have bugs, too. Some are bad. It might be that Retrospect passes some bad parameter into a syscall that causes the disk driver to scribble all over the OS, etc., and that this particular issue never arose in testing. We live in an imperfect world. I respectfully suggest that the Retrospect dev team pay a visit to Apple and test on an Intel xServe with a Hardware RAID card, configured similarly to those customers who are seeing the kernel panic. This doesn't seem to be an isolated incident. Russ Quote Link to comment Share on other sites More sharing options...
prahn Posted August 4, 2010 Author Report Share Posted August 4, 2010 Our Xserve runs here without any Kernel Panic for some years now, very stable and rock solid. Of course we had some software issues with mail server and other stuff, but only after the install of Retrospect we had 3 Kernel Panics, all when starting the Retrospect Console, or using it to configure the Engine. These KPs always made my heart beating faster, because this machine is a central point for our whole company!! I looked in the OS X Console and found 2 interesting entrys: 1. under Crash Reporter the are 3 entries for Retrospect 2. Under Panic Reporter I see 3 entries with the date of the Kernel Panics. Below are the contents: CrashReporter Process: Retrospect [27187] Path: /Applications/Retrospect 6.1/Retrospect.app/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect Identifier: Retrospect Version: ??? (???) Code Type: PPC (Translated) Parent Process: launchd [1] Date/Time: 2010-07-30 20:26:08.520 +0200 OS Version: Mac OS X Server 10.5.8 (9L34) Report Version: 6 Anonymous UUID: 0AEDA1D4-640B-42E3-B1B7-2742E3140FEA Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000342000 Crashed Thread: 0 Thread 0 Crashed: 0 translate 0xb816030d CallPPCFunctionAtAddressInt + 25769 1 translate 0xb816ce24 CallPPCFunctionAtAddressInt + 77760 2 translate 0xb80dfb0b 0xb8000000 + 916235 3 ??? 0x817171da 0 + 2171695578 Thread 1: 0 ??? 0x800bc286 0 + 2148254342 1 ??? 0x800c3a7c 0 + 2148285052 2 translate 0xb818b6ea CallPPCFunctionAtAddressInt + 202886 3 ??? 0x800ed155 0 + 2148454741 4 ??? 0x800ed012 0 + 2148454418 Thread 2: 0 translate 0xb8152b34 spin_lock_wrapper + 91256 1 translate 0xb8167dce CallPPCFunctionAtAddressInt + 57194 2 translate 0xb80bdb8b 0xb8000000 + 777099 3 translate 0xb80b7007 0xb8000000 + 749575 4 translate 0xb80d49c0 0xb8000000 + 870848 5 translate 0xb813d75f spin_lock_wrapper + 4259 6 translate 0xb8011b64 0xb8000000 + 72548 Thread 3: 0 translate 0xb8152c24 spin_lock_wrapper + 91496 1 translate 0xb816c825 CallPPCFunctionAtAddressInt + 76225 2 translate 0xb80bdb8b 0xb8000000 + 777099 3 translate 0xb80b7007 0xb8000000 + 749575 4 translate 0xb80d49c0 0xb8000000 + 870848 5 translate 0xb813d75f spin_lock_wrapper + 4259 6 translate 0xb8011b64 0xb8000000 + 72548 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00010000 ebx: 0xb81601b0 ecx: 0x00195780 edx: 0x00341ffc edi: 0x00341fd0 esi: 0x00341ff0 ebp: 0xb7fffa28 esp: 0xb7fff9f0 ss: 0x0000001f efl: 0x00010292 eip: 0xb816030d cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00342000 Binary Images: 0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate Translated Code Information: Rosetta Version: 21.03 Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Retrospect 6.1/Retrospect.app/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect Exception: EXC_BAD_ACCESS (0x0001) Thread 0: (0xb011cd38, 0xb8152c24) 0x9094f32c: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260 0x088dd04c: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonOperationThreadFunc + 136 0x9099d1d4: /usr/lib/libSystem.B.dylib : __pthread_body + 40 0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0 PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x9094f470 ctr: 0x909174fc r00: 0x0000014e r01: 0xf0101a50 r02: 0xf0101a90 r03: 0x00006f03 r04: 0x00007003 r05: 0x00000000 r06: 0x00000000 r07: 0x00000000 r08: 0x00000000 r09: 0x00000001 r10: 0xfffffff1 r11: 0xa0113934 r12: 0x909174fc r13: 0xf0101b28 r14: 0xf0101b24 r15: 0xf0101b20 r16: 0xf0101b1c r17: 0xf0101b18 r18: 0xf0101ce8 r19: 0x00000000 r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000 r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa010ee54 r28: 0x00174f60 r29: 0x00864200 r30: 0x00174f08 r31: 0x9094ee54 Thread 1: Crashed (0xb7fff9f0, 0xb816030d) 0x909f34e4: /usr/lib/libSystem.B.dylib : _statx1 + 52 0x909f3704: /usr/lib/libSystem.B.dylib : _statx_np$INODE64 + 64 0x909a0344: /usr/lib/libSystem.B.dylib : _acl_get_file1 + 100 0x853c42fc: No symbol 0x853c4620: No symbol 0x85366a64: No symbol 0x853675a4: No symbol 0x852c3960: No symbol 0x850fbe94: No symbol 0x852bf8dc: No symbol 0x85121a24: No symbol 0x85121c20: No symbol 0x852bfef4: No symbol 0x850fbe94: No symbol 0x851cbd3c: No symbol 0x850fbe94: No symbol 0x851cd904: No symbol 0x850fbe94: No symbol 0x851d52b4: No symbol 0x85121a24: No symbol 0x85121c20: No symbol 0x85121a24: No symbol 0x85121c20: No symbol 0x851d5378: No symbol 0x85121a24: No symbol 0x85121c20: No symbol 0x850f48d0: No symbol 0x85121a24: No symbol 0x85121c20: No symbol 0x850f49c8: No symbol 0x850f4b34: No symbol 0x853c5268: No symbol PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x909f3518 ctr: 0x909f3498 r00: 0x00000155 r01: 0xbfffb060 r02: 0xa010d2ac r03: 0xbfffb388 r04: 0xbfffb15c r05: 0x00195780 r06: 0xbfffb09c r07: 0x001fd32f r08: 0x00000001 r09: 0x00000003 r10: 0xf8000001 r11: 0xa0112db8 r12: 0x909f3498 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff r20: 0xbffff650 r21: 0xbffff4a8 r22: 0x00000000 r23: 0x53534267 r24: 0x00188fe0 r25: 0xbfffb09c r26: 0x0000000c r27: 0xbfffb138 r28: 0xbfffb15c r29: 0x909f3498 r30: 0x000001ac r31: 0x909f36d4 Thread 2: (0xb009ad68, 0xb8152b34) 0x088dbe34: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _BSD_watchevent + 44 0x088e0fb8: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonSelectThreadFunc + 204 0x9099d1d4: /usr/lib/libSystem.B.dylib : __pthread_body + 40 0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0 PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x088dbea0 ctr: 0x90961760 r00: 0x00000000 r01: 0xf0080d60 r02: 0x088f9010 r03: 0x000000e8 r04: 0xf0080e34 r05: 0x00000000 r06: 0x00000000 r07: 0x01000000 r08: 0x00000000 r09: 0x01000000 r10: 0x00000000 r11: 0x088f942c r12: 0x90961760 r13: 0x088f9010 r14: 0x00000000 r15: 0x088f9010 r16: 0x088f9008 r17: 0xf0080e18 r18: 0x08900efc r19: 0xf0080e0c r20: 0xf0080dfc r21: 0xf0080e08 r22: 0xf0080e34 r23: 0x00000000 r24: 0x08900efc r25: 0x088f9010 r26: 0x00000000 r27: 0xf0080e04 r28: 0xf0080e34 r29: 0x00000000 r30: 0x088f9010 r31: 0x088e0efc PanicReporter Sat Jul 31 00:25:04 2010 panic(cpu 3 caller 0x001AB0FE): Kernel trap at 0x0017f403, type 14=page fault, registers: CR0: 0x8001003b, CR2: 0x68747555, CR3: 0x00e43000, CR4: 0x00000660 EAX: 0x00000001, EBX: 0x68747541, ECX: 0x07417b58, EDX: 0x0cdaf3d4 CR2: 0x68747555, EBP: 0x5bc2e7a8, ESI: 0x003d7000, EDI: 0x00000000 EFL: 0x00010206, EIP: 0x0017f403, CS: 0x00000008, DS: 0x0cda0010 Error code: 0x00000000 Backtrace (CPU 3), Frame : Return Address (4 potential args on stack) 0x5bc2e5a8 : 0x12b4c6 (0x45f91c 0x5bc2e5dc 0x13355c 0x0) 0x5bc2e5f8 : 0x1ab0fe (0x469a98 0x17f403 0xe 0x469248) 0x5bc2e6d8 : 0x1a1713 (0x5bc2e6f0 0x0 0x5bc2e7a8 0x17f403) 0x5bc2e6e8 : 0x17f403 (0xe 0x48 0x5bc20010 0x3ce0010) 0x5bc2e7a8 : 0x179b34 (0xcdaf3d4 0x3d7000 0x0 0x3) 0x5bc2e8a8 : 0x17a7fe (0xcdaf3d4 0x0 0x0 0x400000) 0x5bc2e988 : 0x431eb6 (0x6e4c8b8 0x19c6000 0x0 0x5bc2ea24) 0x5bc2ea48 : 0x434fbf (0x17b48900 0x0 0x3 0x6e27178) 0x5bc2ea78 : 0x9a6e5a (0x17b48900 0x0 0x400000 0x0) 0x5bc2ead8 : 0x9a6f50 (0x17afd580 0x19c6000 0x0 0x400000) 0x5bc2eb38 : 0x9a6317 (0x5bc2eb7c 0x19c6000 0x0 0x400000) 0x5bc2eb98 : 0x9a6453 (0x7705e00 0x19c6000 0x0 0x400000) 0x5bc2ebd8 : 0x4416d4 (0x7705e00 0x0 0x5bc2ec20 0x0) 0x5bc2ecf8 : 0x18ebc0 (0x7705e00 0x0 0x89edd80 0x3) 0x5bc2fdb8 : 0x12d4d6 (0x89edd58 0x6a395a0 0x0 0x0) 0x5bc2fdf8 : 0x1264fa (0x89edd00 0x0 0x6c 0x5bc2fee4) Backtrace continues... Kernel loadable modules in backtrace (with dependencies): com.apple.driver.AppleRAIDCard(70)@0x9a0000->0x9b4fff dependency: com.apple.iokit.IOSCSIParallelFamily(1.5.2)@0x5e7000 dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(2.1.1)@0x780000 dependency: com.apple.iokit.IOPCIFamily(2.6)@0x654000 dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.1.1)@0x5ce000 BSD process name corresponding to current thread: CoreRAIDServer Mac OS version: 9L34 Kernel version: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 System model name: Xserve2,1 (Mac-F42289C8) System uptime in nanoseconds: 195315544486944 unloaded kexts: com.apple.iokit.IOUSBMassStorageClass 2.0.8 - last unloaded 174093302311588 loaded kexts: com.StudioNetworkSolutions.driver.globalSAN 3 com.apple.filesystems.smbfs 1.4.6 - last loaded 195233276696373 com.apple.filesystems.afpfs 9.0.2 com.apple.nke.asp_tcp 4.7.1 com.apple.filesystems.autofs 2.0.2 com.apple.driver.AppleUpstreamUserClient 2.7.5 com.apple.Dont_Steal_Mac_OS_X 6.0.3 com.apple.iokit.CHUDUtils 201 com.apple.kext.ATY_Sphyrna 5.4.8 com.apple.driver.AppleHWSensor 1.9d0 com.apple.iokit.CHUDProf 211 com.apple.driver.Apple16X50ACPI 1.9 com.apple.driver.VirtualAudioDriver 2.5.8f1 com.apple.iokit.IOFireWireIP 1.7.7 com.apple.driver.AudioIPCDriver 1.0.6 com.apple.ATIRadeonX1000 5.4.8 com.apple.driver.AppleSEP 1.3.0 com.apple.driver.AppleMCEDriver 1.1.7 com.apple.driver.AppleBMC 1.5 com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a17 com.apple.driver.AppleLPC 1.3.1 com.apple.driver.XsanFilter 2.7.91 com.apple.iokit.IOUSBHIDDriver 3.4.6 com.apple.driver.AppleUSBComposite 3.2.0 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1 com.apple.iokit.SCSITaskUserClient 2.1.1 com.apple.iokit.IOATAPIProtocolTransport 1.5.3 com.apple.driver.AppleUSBHub 3.4.9 com.apple.driver.AppleFWOHCI 3.9.7 com.apple.iokit.IOUSBUserClient 3.4.9 com.apple.driver.AppleIntel8254XEthernet 2.1.2b1 com.apple.driver.AppleIntelPIIXATA 2.0.1 com.apple.driver.AppleRAIDCard 70 com.apple.driver.AppleUSBEHCI 3.4.6 com.apple.driver.AppleUSBUHCI 3.3.5 com.apple.driver.AppleEFINVRAM 1.2.0 com.apple.driver.AppleKeyswitch 1.0.4d1 com.apple.driver.AppleACPIButtons 1.2.5 com.apple.driver.AppleRTC 1.2.3 com.apple.driver.AppleHPET 1.4 com.apple.driver.AppleACPIPCI 1.2.5 com.apple.driver.AppleSMBIOS 1.4 com.apple.driver.AppleACPIEC 1.2.5 com.apple.driver.AppleAPIC 1.4 com.apple.security.seatbelt 107.12 com.apple.nke.applicationfirewall 1.6.77 com.apple.security.TMSafetyNet 3 com.apple.driver.AppleIntelCPUPowerManagement 76.2.0 com.apple.driver.DiskImages 199 com.apple.BootCache 30.4 com.apple.iokit.CHUDKernLib 201 com.apple.driver.Apple16X50Serial 1.9 com.apple.iokit.IOSerialFamily 9.4 com.apple.iokit.IOAudioFamily 1.6.9fc5 com.apple.kext.OSvKernDSPLib 1.1 com.apple.iokit.IONDRVSupport 1.7.3 com.apple.iokit.IOGraphicsFamily 1.7.3 com.apple.driver.IOPlatformPluginFamily 3.4.0a17 com.apple.driver.AppleSMC 2.3.1d1 com.apple.iokit.IOBDStorageFamily 1.5 com.apple.iokit.IODVDStorageFamily 1.5 com.apple.iokit.IOCDStorageFamily 1.5 com.apple.iokit.IOFireWireFamily 3.4.9 com.apple.iokit.IONetworkingFamily 1.6.1 com.apple.iokit.IOATAFamily 2.0.1 com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1 com.apple.iokit.IOSCSIParallelFamily 1.5.2 com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1 com.apple.iokit.IOUSBFamily 3.4.9 com.apple.driver.AppleEFIRuntime 1.2.0 com.apple.iokit.IOSMBusFamily 1.1 com.apple.iokit.IOHIDFamily 1.5.5 com.apple.iokit.IOStorageFamily 1.5.6 com.apple.driver.AppleACPIPlatform 1.2.5 com.apple.iokit.IOPCIFamily 2.6 com.apple.iokit.IOACPIFamily 1.2.0 Hope this helps! Quote Link to comment Share on other sites More sharing options...
rhwalker Posted August 4, 2010 Report Share Posted August 4, 2010 Doesn't it seem a bit odd that the reported application is Retrospect 6.1? (see the second line of the Crash Reporter log). Also, the Crash Reporter seems to believe that this is PPC code being executed, but your original post indicated that you've got an Intel xServe: The Retrospect Engine is running on an Intel XServe with Mac OS X Server 10.5.8 here (2,8 GHz Quadcore, 4 GB RAM, Hardware RAID). Sure we are dealing with a full deck here? Something doesn't make sense. Russ Quote Link to comment Share on other sites More sharing options...
MAlexander Posted August 5, 2010 Report Share Posted August 5, 2010 Note that the crash log says "Code Type: PPC (Translated)" which applies to the code in the process that crashed, not the machine it is running on. Since that process is running Retrospect 6.1, it's not surprising that it's PPC code. I agree that it's not clear why 6.1 is running. It also appears that the crash report is from about 4 hours before the kernel panic. Perhaps the two are unrelated. Quote Link to comment Share on other sites More sharing options...
prahn Posted August 5, 2010 Author Report Share Posted August 5, 2010 Sorry, for this confusion! As Retrospect 8 does not backup my local hard disk, I still do backups for the local System disk with Retrospect 6. Also to me the timing of the Crash Reporter logs were a little confusing, as these differ from the timing of the Panic logs. Please just ignore the Crash Reporter logs here!! If you need anything more from me, just tell me.... Quote Link to comment Share on other sites More sharing options...
MaxW Posted August 5, 2010 Report Share Posted August 5, 2010 We're having the same problem. Xserve Intel, Apple Hardware RAID (level 5), 10.5.8. After upgrading from 8.1 to 8.2 launching Retrospect causes a kernel panic. The RAID controller even started to reinitialize the volume... Are there any downgrade instructions yet or official feedback from whoever owns oder supports Retrospect currently? Waiting for support to reply... Regards Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 5, 2010 Report Share Posted August 5, 2010 Are there any downgrade instructions yet... The Retrospect install is pretty straightforward; and an uninstaller AppleScript is included in the application folder. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted August 5, 2010 Report Share Posted August 5, 2010 Sorry, for this confusion! As Retrospect 8 does not backup my local hard disk, I still do backups for the local System disk with Retrospect 6. Also to me the timing of the Crash Reporter logs were a little confusing, as these differ from the timing of the Panic logs. Please just ignore the Crash Reporter logs here!! If you need anything more from me, just tell me.... I suggest that you start over with your problem report. I don't know about others, but I can't figure out what your problem is because of all of this confusion. You initially say you are running Retrospect 8, yet you post a crash report about Retrospect 6.1 and also say that Retrospect 8 is not being used to back up your disk. Start over with a clear statement of your configuration and the problem that you are trying to solve. I don't see anything in your posts that suggests that an "update to 8.2" is causing Kernel Panics for you. Russ Quote Link to comment Share on other sites More sharing options...
prahn Posted August 5, 2010 Author Report Share Posted August 5, 2010 ?!?!?! I do not understand?! The only "wrong" thing that happened in my post was this crash reporter log of Retrospect 6. Retrospect 8 does not backup my ***local System Disk*** because of bug #22185, which should be fixed with 8.2. That's why version 6 is still installed and used for the "Local System Disk". I use Version 8 for networked system (Win + Linux) and also for a local data disk! And now I also wanted to use it for the "Local System Disk" and the delete version 6 forever, but this is causing Kernel Panics. I also could now count at least 3 other posters that have the same error, and they all have the Apple Hardware RAID installed! Quote Link to comment Share on other sites More sharing options...
prahn Posted August 27, 2010 Author Report Share Posted August 27, 2010 Hi! Is this bug filed and will be fixed in the future? Or do I have to look for any other solution? Any response would be nice. Thank you. Regards, prahn Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.