On Sat, Sep 24, 2011 at 3:04 PM, Anirudh Sivaraman <sk.anir...@gmail.com> wrote: > On Sat, Sep 24, 2011 at 1:58 PM, Ali Saidi <sa...@umich.edu> wrote: >> Why don't you try the config file in >> http://www.gem5.org/dist/current/arm/arm-system-2011-08.tar.bz2 >> > > Hi > > I tried this. I was able to build a new vmlinux image with the kernel > configuration provided in the tarball. However, I had to set some of > the configuration options manually to No while running make on the > kernel source. I hope this is fine. > I ran GEM5 with the newly built vmlinux image and it booted fine until > it showed a kernel panic at one place : 2248908940000: > system.cpu.break_event: break event panic triggered > The output on M5term might be helpful in diagnosing the issue: > > VFS: Cannot open root device "sda1" or unknown-block(8,1) > [ 0.003904] VFS: Cannot open root device "sda1" or unknown-block(8,1) > Please append a correct "root=" boot option; here are the available > partitions: > [ 0.003904] Please append a correct "root=" boot option; here are > the available partitions: > 0800 5320248 sda[ 0.003904] 0800 5320248 sda driver: sd > driver: sd > <0>Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,1) > [ 0.003904] Kernel panic - not syncing: VFS: Unable to mount root > fs on unknown-block(8,1) > [<c003440c>] (unwind_backtrace+0x0/0xd0) from [<c02dca50>] (panic+0x3c/0x118) > [ 0.003904] [<c003440c>] (unwind_backtrace+0x0/0xd0) from > [<c02dca50>] (panic+0x3c/0x118) > [<c02dca50>] (panic+0x3c/0x118) from [<c0009190>] > (mount_block_root+0x1c8/0x208) > [ 0.003904] [<c02dca50>] (panic+0x3c/0x118) from [<c0009190>] > (mount_block_root+0x1c8/0x208) > [<c0009190>] (mount_block_root+0x1c8/0x208) from [<c00093ec>] > (prepare_namespace+0x12c/0x180) > [ 0.003904] [<c0009190>] (mount_block_root+0x1c8/0x208) from > [<c00093ec>] (prepare_namespace+0x12c/0x180) > [<c00093ec>] (prepare_namespace+0x12c/0x180) from [<c000872c>] > (kernel_init+0x198/0x1e8) > [ 0.003904] [<c00093ec>] (prepare_namespace+0x12c/0x180) from > [<c000872c>] (kernel_init+0x198/0x1e8) > [<c000872c>] (kernel_init+0x198/0x1e8) from [<c002ece0>] > (kernel_thread_exit+0x0/0x8) > [ 0.003904] [<c000872c>] (kernel_init+0x198/0x1e8) from > [<c002ece0>] (kernel_thread_exit+0x0/0x8) > > > This probably has something to do with the file system or the disk drivers ?? > > Anirudh > >> Ali >> >> >> On Sep 24, 2011, at 12:14 PM, Anirudh Sivaraman wrote: >> >>> On Sat, Sep 24, 2011 at 11:18 AM, Ali Saidi <sa...@umich.edu> wrote: >>>> >>>> On Sep 24, 2011, at 8:37 AM, Anirudh Sivaraman wrote: >>>> >>>>> On Fri, Sep 23, 2011 at 10:57 PM, Ali Saidi <sa...@umich.edu> wrote >>>>>> >>>>>> You need to make sure the board time is a realview PBX. >>>>> >>>>> Thanks for the response. However, I am still confused about where this >>>>> needs to be modified. Is it in a gem5 configuration file or is it in >>>>> the bootloader assembly file ? >>>>> I now have a vmlinux ( ie the ELF style with symbols) image for the >>>>> ARM kernel patched for Android. However, the boot fails with the >>>>> unrecognized machine ID error. >>>> >>>> In the kernel directory run >>>> make ARCH=arm menuconfig >>>> >>>> Select System Type >>>> -> Select ARM System Type >>>> - - > Select ARM Ltd Realview Family >>>> -> Select Realview Platform Type >>>> - - > Support RealView(R) Platform Baseboard Explore >>>> >>>> Exit, save and recompile. >>> >>> Thanks for this. I tried this, recompiled the Android Linux kernel and >>> ran it with the new vmlinux file. But it crashes as soon as it boots >>> with the following error: >>> >>> gem5.debug: build/ARM_FS/cpu/simple/atomic.cc:450: Fault >>> AtomicSimpleCPU::writeMem(uint8_t*, unsigned int, Addr, unsigned int, >>> uint64_t*): Assertion `!pkt.isError()' failed. >>> Program aborted at cycle 32500 >>> >>> Is this a problem with the kernel image or the file system image ? Hi
I have a related question. I downloaded both the old and new versions of the ARM binaries and disk images from http://www.gem5.org/Download Once I extracted the tars, I cded to the disks directory and ran 'file *' in both. I see that the file type is x86 boot sector in the newer arm-system-2011-08.tar.bz2 tar ball and the file type is Linux ext2 file system in the older one. Have x86 file system images been bundled into the arm tar balls by mistake ? Below is the output from file* : anirudh@anirudh:~/Downloads$ file arm-system/disks/* arm-system/disks/ael-arm.ext2: Linux rev 1.0 ext2 filesystem data, UUID=7d6b3d62-f52a-4e74-9502-8ed8ee648c5c anirudh@anirudh:~/Downloads$ file arm-system-2011-08/disks/* arm-system-2011-08/disks/arm-ubuntu-natty-headless.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 6291873 sectors, extended partition table (last)\011, code offset 0x0 arm-system-2011-08/disks/linux-arm-ael.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 1048257 sectors, extended partition table (last)\011, code offset 0x0 Anirudh >>> >>> Anirudh >>> >>>> Ali >>>> >>>> _______________________________________________ >>>> gem5-users mailing list >>>> gem5-users@gem5.org >>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >>>> >>> _______________________________________________ >>> gem5-users mailing list >>> gem5-users@gem5.org >>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> _______________________________________________ >> gem5-users mailing list >> gem5-users@gem5.org >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
