Date: | Sat, 15 Mar 2008 10:13:48 -0400 |
---|---|
From: | "Abdullah Kayi" <apokayi@xxxxxxxxx> |
Subject: | [Gems-users] Checkpoints creation problem |
Hi all, I compiled Ruby and Opal successfully using gcc 3.4.6 on an x86_64 Linux machine. I am using gems2.1 and I used simics 3.0.31 in that process. However for the checkpoint creation as suggested earlier I tried to use simics 2.2.19. But again I have problems with the checkpoint creation, here are the details of the error: I tried to install Solaris 10; OS_INSTALL_CD_1=/home/apokayi/Solaris_Images/sol-10-u4-ga-sparc-v1.iso OS_INSTALL_CD_2=/home/apokayi/Solaris_Images/sol-10-u4-ga-sparc-v2.iso after i run ./naked-check-create.sh 16 65536 I am again getting some warnings and errors: I am pasting whatever I see on my konsole, I appreciate any comments on this. Using CD-ROM image file: /home/apokayi/Solaris_Images/sol-10-u4-ga-sparc-v1.iso setting media file-cd25B_2_6 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 exec: No such file or directory *** [text-console] Window output disabled [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 : Sat Mar 15 01:31:31 2008 [system info] Disabling slave processors. [system info] Enabling slave processors. [qlc24B_2 info] Undocumented MAILBOX command: 0x5a [qlc28B_2 info] Undocumented MAILBOX command: 0x5a [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [hme0 info] Dropping packet, not connected to network. (Will not warn again) [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc28B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong [qlc24B_2 info] Note: Abort Command Received - Something probably went wrong Many thanks, Abdullah |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] please help: XACT CONSISTENCY CHECK FAILURE DUE TO OVERLAP BETWEEN ESCAPE ACTIONS AND TRANSACTIONS, Jim Leek |
---|---|
Next by Date: | Re: [Gems-users] Checkpoints creation problem, Dan Gibson |
Previous by Thread: | Re: [Gems-users] big CPI?, Dan Gibson |
Next by Thread: | Re: [Gems-users] Checkpoints creation problem, Dan Gibson |
Indexes: | [Date] [Thread] |