davidcasti Posted September 30, 2002 Report Share Posted September 30, 2002 Hello, I can consistently panic my MacOS 10.2 client when it is being backed up from my Retrospect 6.0 windows server. Here is the panic log -- panic(cpu 0): zalloc Latest stack backtrace for cpu 0: Backtrace: 0x0008598C 0x00085DBC 0x00028B8C 0x000429F0 0x0002D96C 0x001D4730 0x000F1798 0x38DA96A0 0x38DA93FC 0x00203A6C 0x00092870 0x406C6973 Kernel loadable modules in backtrace (with dependencies): com.pliris.FWXDriver(2.2.2)@0x38d8d000 Proceeding back via exception chain: Exception state (sv=0x237E9A00) PC=0x90013C0C; MSR=0x0000D030; DAR=0xE0034000; DSISR=0x40000000; LR=0x00004618; R1=0xF1529530; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 6.1: Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC -- Any ideas? Thanks, David. Link to comment Share on other sites More sharing options...
IrenaS Posted October 1, 2002 Report Share Posted October 1, 2002 What version of the client software? Have you tried uninstalling and reinstalling? Did this ever work? If not, when did the kernel panic start? Link to comment Share on other sites More sharing options...
davidcasti Posted October 1, 2002 Author Report Share Posted October 1, 2002 Client version is 5.0.536. I have tried uninstalling & reinstalling, no luck. The client has never successfully completed a full backup. However, after a crash, the backup will resume once the client is restarted. About 30 - 60 minutes of backup occurs before the next crash. The exact time varies, but the pattern is consistent. Thanks, David. Link to comment Share on other sites More sharing options...
davidcasti Posted October 14, 2002 Author Report Share Posted October 14, 2002 This problem was eventually tracked down to Firewalk X. Version 2.2.3b5, combined with deactivating the client countdown, resolves the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.