Thanks Ali. I got my error, one of the "let" command was not working(as shown in the error message). Now it is perfect and I can build a blank disk image of any size.
Thanks, Dibakar On Tue, Sep 28, 2010 at 12:46 PM, Ali Saidi <sa...@umich.edu> wrote: > > Using bash your still getting: util/mkblankimage.sh: line 209: [: -eq: > unary operator expected? > > Ali > > > > On Tue, 28 Sep 2010 12:11:53 -0500, dibakar gope <dibakar...@gmail.com> > wrote: >> Hi Ali, >> >> Thanks for the reply. I already changed the shell to !/bin/bash >> instead of sh shell in the very 1st line of that code (as you >> suggested in one of your prior thread). Before changing it to bash >> shell, it was not accepting “let” as sh shell command (as the code >> uses let command for expression evaluation). >> >> But now getting this issue with the desired disk size. >> >> Thanks and Regards, >> Dibakar >> >> >> Re: [m5-users] Queries in disk-image build using util/mkblankimage.sh script >> >> Ali Saidi >> Tue, 28 Sep 2010 09:11:43 -0700 >> >> I would guess that it's a sh vs. bash issue. Try changing !/bin/sh at >> the top of the script to !/bin/bash and your problem might go away. >> >> Ali >> >> >> On Tue, 28 Sep 2010 01:49:07 -0500, dibakar gope <dibakar...@gmail.com> >> wrote: >>> Hi All, >>> >>> (1) I got few queries during the blank disk_image build using >>> util/mkblankimage.sh. The script asks for the size of the disk image >>> to be built in MB. Although my input size is 128MB, but the eventual >>> disk image it creates turns out to be of 7.9 GB. I tried out with >>> other input sizes (256, 512, 1024, 2048.... etc), but the everytime >>> the final disk image is of size 7.9GB. So is there any way so that I >>> can make the disk size as 2GB? >>> >>> The command-line with the output are as follows:- >>> diba...@dibakar-desktop:~/m5-aab017d1adc6$ bash util/mkblankimage.sh >>> Do you have sudo access? [y/n] y >>> How large do you want this disk image (in MB): 128 >>> util/mkblankimage.sh: line 101: let: crosstool-ng-1.7.1: syntax error: >>> invalid arithmetic operator (error token is ".7.1") >>> What directory would you like to build the image in? /home/dibakar >>> What would you like to name the image? x86root.img >>> >>> dd'ing the blank image (this make take a while)... >>> >>> Binding the image and partitioning... >>> >>> Remounting image and formatting... >>> util/mkblankimage.sh: line 209: [: -eq: unary operator expected >>> >>> Disk image creation complete. >>> >>> ----------------------------------------- >>> >>> (2) Once I use that 7.9 GB disk Image for x86_FS run, I got the >>> following errors:- >>> >>> command line: build/X86_FS_v1/m5.opt configs/example/fs.py >>> --kernel=/dist/m5/system/binaries/vmlinux >>> Global frequency set at 1000000000000 ticks per second >>> info: kernel located at: /dist/m5/system/binaries/vmlinux >>> 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012 >>> Listening for pc connection on port 3456 >>> warn: Reading current count from inactive timer. >>> For more information see: http://www.m5sim.org/warn/1ea2be46 >>> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 >>> **** REAL SIMULATION **** >>> info: Entering event queue @ 0. Starting simulation... >>> warn: Don't know what interrupt to clear for console. >>> For more information see: http://www.m5sim.org/warn/7fe1004f >>> warn: instruction 'wbinvd' unimplemented >>> For more information see: http://www.m5sim.org/warn/437d5238 >>> warn: instruction 'fxsave' unimplemented >>> For more information see: http://www.m5sim.org/warn/437d5238 >>> warn: Tried to clear PCI interrupt 14 >>> For more information see: http://www.m5sim.org/warn/77378d57 >>> panic: access out of bounds >>> @ cycle 4797427973501 >>> [read:build/X86_FS/dev/disk_image.cc, line 369] >>> Memory Usage: 251564 KBytes >>> For more information see: http://www.m5sim.org/panic/6dc55e82 >>> Program aborted at cycle 4797427973501 >>> Aborted >>> >>> From the script build/X86_FS/dev/disk_image.cc, it seems that the >>> panic is due to the these following set of lines in CowDiskImage::read >>> function:- >>> if (offset > size()) >>> panic("access out of bounds"); >>> >>> Is this error showing due to this disk-image size? Have anyone faced >>> similar kind of problems during X86_FS run? >>> .. >>> >>> Thanks and Regards, >>> Dibakar > > _______________________________________________ m5-users mailing list m5-users@m5sim.org http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
