Date: | Thu, 15 Jan 2009 21:32:54 +0800 |
---|---|
From: | "Xiongfei Liao" <xiongfei.liao@xxxxxxxxx> |
Subject: | [Gems-users] Is this failure fatal in the process of creating naked checkpoints? |
Hi, GEMSers, I used the script in GEMS to create naked checkpoints. At the beginning of the process, there were output lines as follows. The words in red color indicate a failure.. This time i created for 16 processors with 64G memory. Could this loading failure lead to errors which make the checkpoints unusable later? If this failure is fatal, how to fix it? Thanks! ======================================================================= Using CD-ROM image file: /home/liao0016/software-backup/opensolaris/sol-nv-b104-sparc-dvd-iso-a setting media file-cd25B_2_6 Failed to load module 'sparc-u3-turbo' ('/home/liao0016/installed_software/gems-2.1/simics-2.2.19/amd64-linux/lib/sparc-u3-turbo.so'): "/home/liao0016/installed_software/gems-2.1/simics-2.2.19/amd64-linux/sys/lib/libstdc++.so.5: version `CXXABI_1.2' not found (required by /home/liao0016/installed_software/gems-2.1/simics-2.2.19/amd64-linux/lib/sparc-u3-turbo.so)" CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted CRAFF warning: File was not closed cleanly; may be corrupted [qlc24B_2 info] Disk registering: Loop id: 0x3 [qlc24B_2 info] Disk registering: Loop id: 0xc [qlc24B_2 info] Disk registering: Loop id: 0xd [qlc24B_2 info] Disk registering: Loop id: 0xe [qlc24B_2 info] Disk registering: Loop id: 0xf [qlc24B_2 info] Disk registering: Loop id: 0x10 [qlc24B_2 info] Disk registering: Loop id: 0x11 [qlc24B_2 info] Disk registering: Loop id: 0x12 [qlc24B_2 info] Disk registering: Loop id: 0x13 [qlc24B_2 info] Disk registering: Loop id: 0x14 [qlc28B_2 info] Disk registering: Loop id: 0x3 [qlc24B_2 info] Disk registering: Loop id: 0x4 [qlc28B_2 info] Disk registering: Loop id: 0x4 [qlc28B_2 info] Disk registering: Loop id: 0x5 [qlc28B_2 info] Disk registering: Loop id: 0x6 [qlc28B_2 info] Disk registering: Loop id: 0x7 [qlc28B_2 info] Disk registering: Loop id: 0x8 [qlc24B_2 info] Disk registering: Loop id: 0x2 [qlc28B_2 info] Disk registering: Loop id: 0x9 [qlc28B_2 info] Disk registering: Loop id: 0xa [qlc28B_2 info] Disk registering: Loop id: 0xb [qlc28B_2 info] Disk registering: Loop id: 0xc [qlc28B_2 info] Disk registering: Loop id: 0xd [qlc24B_2 info] Disk registering: Loop id: 0x5 [qlc28B_2 info] Disk registering: Loop id: 0xe [qlc28B_2 info] Disk registering: Loop id: 0xf [qlc28B_2 info] Disk registering: Loop id: 0x10 [qlc28B_2 info] Disk registering: Loop id: 0x11 [qlc28B_2 info] Disk registering: Loop id: 0x12 [qlc28B_2 info] Disk registering: Loop id: 0x13 [qlc28B_2 info] Disk registering: Loop id: 0x14 [qlc28B_2 info] Disk registering: Loop id: 0x15 [qlc24B_2 info] Disk registering: Loop id: 0x6 [qlc24B_2 info] Disk registering: Loop id: 0x7 [qlc24B_2 info] Disk registering: Loop id: 0x8 [qlc24B_2 info] Disk registering: Loop id: 0x9 [qlc24B_2 info] Disk registering: Loop id: 0xa [qlc24B_2 info] Disk registering: Loop id: 0xb New VTOC written to disk: Label : SIMDISK cyl 10938 alt 2 hd 19 sec 80 RPM : 7200 Data cylinders : 10938 Alt cylinders : 2 Physical cylinders : 10940 Heads : 19 Sectors per Track : 80 Number of data blocks : 16625760 Partition Table: Number Tag Flag Start End Size 2 5 (backup) 1 (unmountable) 0 16625759 16625760 Capturing output to 'install-log.txt' Image memory limited to 8 G Start at : Thu Jan 15 18:28:47 2009 [system info] Disabling slave processors. ======================================================================= |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] checkpoint error, Polina Dudnik |
---|---|
Next by Date: | Re: [Gems-users] Is this failure fatal in the process of creating naked checkpoints?, Derek Hower |
Previous by Thread: | Re: [Gems-users] How long does it take to generate the "naked checkpoints"?, Dan Gibson |
Next by Thread: | Re: [Gems-users] Is this failure fatal in the process of creating naked checkpoints?, Derek Hower |
Indexes: | [Date] [Thread] |