Related to "checkpoint" problem: when I check /usr/fox/sp/files ... two files from the Micro station giving the checkpoint problem are linked : BBMICRO1.UC and DBMICRO1.UC, while the files from the other stations are not ??? Can that be the reason ? Jef [EMAIL PROTECTED]@lists.TheCassandraProject.org on 14/11/2000 14:35:25 Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: AW51panic Asynchronous memory faults in the 'B' boxes are caused by bad memory chips. CAC will recommend you reseat the chips but I have very little faith that that will fix it, it has never worked for me. There is a document that will tell you which of the chips to change using the MFAR parameter... get it from field service. Check the database for that station using 'check_db_sync', a tool that might be on your system in /opt/fox/bin/tools/check_sync. If you don't have it, you can also get these utilities from field service. Depending on the results of check_db_sync, you may be able to get CAC to repair the database or you may have to initialize and reload to cure it. I know that sounds like a standard CAC statement but unfortunately it's fact. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 14, 2000 3:18 AM To: [EMAIL PROTECTED] Subject: AW51panic Hi, We last had a problem with a AW51B going down ( panic error : asynchronous memory fault) while checkpointing a Micro station. Since then , we have an error when we checkpoint that station: Checkpoint type 5;class8;code -24 failed Everything is working ok in that station, we can make block changes in the configurator, ... but always have that message when leaving the Configurator. We rebooted that station , but the error remains. We also had a panic error on the AW51 : panic: asynchronous memory fault: MFSR= ... dma error etc... We always have that message now in /var/adm/messages when rebooting that AW