Hi,
On 21 August 2013 12:46, Phi Debian phi.debian@gmail.com wrote:
Hi Fathi,
Do you know someone who could help me progress on this, I am stuck since Jul 12, well doing other things meanwhile :)
I follow the receipe to download an boot and armv8 image, all that goes well.
Which recipe? http://www.linaro.org/engineering/engineering-projects/armv8 http://releases.linaro.org/13.07/openembedded/aarch64 (build from source tab)
I then follow the receipe to build the latest kernel from git, it all goes well, I got an Image along with a vmlinux (with debug info).
Which tree?
I made the boot linux-system-foundation.axf file as descrived, I can see that my kernel in in there
$ strings -a linux-system-foundation.axf | grep phi %s version %s (phi@hpfrcu82) (gcc version 4.8.2 20130624 ...
Then this is where I am stuck and can't find receipe how to boot this.
I tried a brute ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./linux-system-foundation.axf --block-device ./rootfs.img --network=nat
I assume you tried our 13.07 release and it works fine, right? (to rule out an issue with your set up or the rootfs)
Where rootfs.img is the vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then I thougt 'may be' I got to populate the /boot in the rootfs.img with my new kernel stuff, so I mounted it (losetp _offset, etc..) placed Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
This part isn't needed.
Is there someone at linaro who know how to boot a fresshly build kernel, the receipe on the web must be incorect or out dated?
linaro-dev mailing list is more appropriate.
Cheers, Fathi
Hi Fathi
Ha, ouch, I wrote a request into linaro-kernel in July...
Ok you cc'ed linaro.dev, let see if one can help.
My need is to boot a freshly build kernel, with a standard (regular?) rootfs.
I provide here more detail about what I did today.
I first downloaded and boot a pre-build system like this.
Dowloaded this as explained at http://www.linaro.org/engineering/engineering-projects/armv8
FM000-KT-00035-r0p8-48rel5.tgz gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux.tar.xz img-foundation.axf vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
I exploded the img.gz into rootfs.img
And booted like this ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./img-foundation .axf --block-device ./rootfs.img --network=nat
All boot fine and I get this at the console root@genericarmv8:~# uname -a Linux genericarmv8 3.10.1.0-1-linaro-vexpress64 #1ubuntu1~ci+130718012724 SMP Thu Jul 18 01:30:58 UTC 2013 aarch64 GNU/Linux root@genericarmv8:~#
The to build a kernel I follow this receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
With the little variation tha tI used the 4.8 toolchain (My prev attempt failed the same way with 4.7).
So I get the gits given on the receipe page.
From there I can sucessfully build the kernel for this git source.
CU82$ ls boot-wrapper-aarch64 linaro-aarch64
CU82$ ll linaro-aarch64/vmlinux -rwxr-xr-x 1 phi phi 66629618 Aug 21 10:34 linaro-aarch64/vmlinux
And an Image is built too CU82$ ll linaro-aarch64/arch/arm64/boot/Image -rwxr-xr-x 1 phi phi 4878372 Aug 21 10:34 linaro-aarch64/arch/arm64/boot/Image
I can verify with strings that is is all my build in there.
From there I followed the receipe to obtain a boot loader
I made the symlinks as specified and made the make for vexpress.
make clean
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf
I got a .axf file
CU82$ ll boot-wrapper-aarch64/*axf -rwxr-xr-x 1 phi phi 5114841 Aug 21 09:41 boot-wrapper-aarch64/linux-system-foun dation.axf
And I am stuck there I dunno what to do with the the Image and linux-system-foun dation.axf,
I thought I got to boot the linux-system-foundation.axf with the original rootfs.img unchanged but it doesn't work
./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./boot.axf --bl ock-device ./rootfs.img --network=nat
(boot.axf is a cp of the linux-system-foundation.axf)
. . . msgmni has been set to 7928 io scheduler noop registered io scheduler cfq registered (default) vda: vda1 vda2 smc91x: IOADDR ffffff800001a000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001a000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 254:2. Freeing init memory: 164K INIT: version 2.88 booting init[390]: undefined instruction: pc=0000007f9c80e4b8 Code: 2947bcce d50339bf b94038cd d5033fdf (d53be029) init[1]: undefined instruction: pc=0000007f9c80e4b8 Code: 2947bcce d50339bf b94038cd d5033fdf (d53be029) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
Call trace: [<ffffffc0000875a4>] dump_backtrace+0x0/0x12c [<ffffffc0003ab01c>] dump_stack+0x14/0x1c [<ffffffc0003ab26c>] panic+0xe8/0x208 [<ffffffc000097b9c>] do_exit+0x714/0x7c0 [<ffffffc000098ca4>] do_group_exit+0x3c/0xd0 [<ffffffc0000a4238>] get_signal_to_deliver+0x150/0x48c [<ffffffc000086f24>] do_signal+0x5c0/0x5dc [<ffffffc0000871ac>] do_notify_resume+0x84/0x94
Thanx in advance for any help, for booting a freshly made kernel.
Cheers, Phi
On Wed, Aug 21, 2013 at 11:09 AM, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi,
On 21 August 2013 12:46, Phi Debian phi.debian@gmail.com wrote:
Hi Fathi,
Do you know someone who could help me progress on this, I am stuck since Jul 12, well doing other things meanwhile :)
I follow the receipe to download an boot and armv8 image, all that goes well.
Which recipe? http://www.linaro.org/engineering/engineering-projects/armv8 http://releases.linaro.org/13.07/openembedded/aarch64 (build from source tab)
I then follow the receipe to build the latest kernel from git, it all goes well, I got an Image along with a vmlinux (with debug info).
Which tree?
I made the boot linux-system-foundation.axf file as descrived, I can see that my kernel in in there
$ strings -a linux-system-foundation.axf | grep phi %s version %s (phi@hpfrcu82) (gcc version 4.8.2 20130624 ...
Then this is where I am stuck and can't find receipe how to boot this.
I tried a brute ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./linux-system-foundation.axf --block-device ./rootfs.img --network=nat
I assume you tried our 13.07 release and it works fine, right? (to rule out an issue with your set up or the rootfs)
Where rootfs.img is the vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then I thougt 'may be' I got to populate the /boot in the rootfs.img with my new kernel stuff, so I mounted it (losetp _offset, etc..) placed Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
This part isn't needed.
Is there someone at linaro who know how to boot a fresshly build kernel, the receipe on the web must be incorect or out dated?
linaro-dev mailing list is more appropriate.
Cheers, Fathi
I encounter the same problem when compiled my own kernel following " https://wiki.linaro.org/HowTo/BuildArm64Kernel"
The new kernel failed to be booted :( got the same error as you described.
On 21 August 2013 18:34, Phi Debian phi.debian@gmail.com wrote:
Hi Fathi
Ha, ouch, I wrote a request into linaro-kernel in July...
Ok you cc'ed linaro.dev, let see if one can help.
My need is to boot a freshly build kernel, with a standard (regular?) rootfs.
I provide here more detail about what I did today.
I first downloaded and boot a pre-build system like this.
Dowloaded this as explained at http://www.linaro.org/engineering/engineering-projects/armv8
FM000-KT-00035-r0p8-48rel5.tgz gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux.tar.xz img-foundation.axf vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
I exploded the img.gz into rootfs.img
And booted like this ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./img-foundation .axf --block-device ./rootfs.img --network=nat
All boot fine and I get this at the console root@genericarmv8:~# uname -a Linux genericarmv8 3.10.1.0-1-linaro-vexpress64 #1ubuntu1~ci+130718012724 SMP Thu Jul 18 01:30:58 UTC 2013 aarch64 GNU/Linux root@genericarmv8:~#
The to build a kernel I follow this receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
With the little variation tha tI used the 4.8 toolchain (My prev attempt failed the same way with 4.7).
So I get the gits given on the receipe page.
From there I can sucessfully build the kernel for this git source. CU82$ ls boot-wrapper-aarch64 linaro-aarch64
CU82$ ll linaro-aarch64/vmlinux -rwxr-xr-x 1 phi phi 66629618 Aug 21 10:34 linaro-aarch64/vmlinux
And an Image is built too CU82$ ll linaro-aarch64/arch/arm64/boot/Image -rwxr-xr-x 1 phi phi 4878372 Aug 21 10:34 linaro-aarch64/arch/arm64/boot/Image
I can verify with strings that is is all my build in there.
From there I followed the receipe to obtain a boot loader I made the symlinks as specified and made the make for vexpress.
make clean
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf
I got a .axf file
CU82$ ll boot-wrapper-aarch64/*axf -rwxr-xr-x 1 phi phi 5114841 Aug 21 09:41 boot-wrapper-aarch64/linux-system-foun dation.axf
And I am stuck there I dunno what to do with the the Image and linux-system-foun dation.axf,
I thought I got to boot the linux-system-foundation.axf with the original rootfs.img unchanged but it doesn't work
./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./boot.axf --bl ock-device ./rootfs.img --network=nat
(boot.axf is a cp of the linux-system-foundation.axf)
. . . msgmni has been set to 7928 io scheduler noop registered io scheduler cfq registered (default) vda: vda1 vda2 smc91x: IOADDR ffffff800001a000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001a000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 254:2. Freeing init memory: 164K INIT: version 2.88 booting init[390]: undefined instruction: pc=0000007f9c80e4b8 Code: 2947bcce d50339bf b94038cd d5033fdf (d53be029) init[1]: undefined instruction: pc=0000007f9c80e4b8 Code: 2947bcce d50339bf b94038cd d5033fdf (d53be029) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
Call trace: [<ffffffc0000875a4>] dump_backtrace+0x0/0x12c [<ffffffc0003ab01c>] dump_stack+0x14/0x1c [<ffffffc0003ab26c>] panic+0xe8/0x208 [<ffffffc000097b9c>] do_exit+0x714/0x7c0 [<ffffffc000098ca4>] do_group_exit+0x3c/0xd0 [<ffffffc0000a4238>] get_signal_to_deliver+0x150/0x48c [<ffffffc000086f24>] do_signal+0x5c0/0x5dc [<ffffffc0000871ac>] do_notify_resume+0x84/0x94
Thanx in advance for any help, for booting a freshly made kernel.
Cheers, Phi
On Wed, Aug 21, 2013 at 11:09 AM, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi,
On 21 August 2013 12:46, Phi Debian phi.debian@gmail.com wrote:
Hi Fathi,
Do you know someone who could help me progress on this, I am stuck since Jul 12, well doing other things meanwhile :)
I follow the receipe to download an boot and armv8 image, all that goes
well.
Which recipe? http://www.linaro.org/engineering/engineering-projects/armv8 http://releases.linaro.org/13.07/openembedded/aarch64 (build from
source tab)
I then follow the receipe to build the latest kernel from git, it all goes well, I got an Image along with a vmlinux (with debug info).
Which tree?
I made the boot linux-system-foundation.axf file as descrived, I can see that my kernel in in there
$ strings -a linux-system-foundation.axf | grep phi %s version %s (phi@hpfrcu82) (gcc version 4.8.2 20130624 ...
Then this is where I am stuck and can't find receipe how to boot this.
I tried a brute ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./linux-system-foundation.axf --block-device ./rootfs.img --network=nat
I assume you tried our 13.07 release and it works fine, right? (to rule out an issue with your set up or the rootfs)
Where rootfs.img is the
vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then I thougt 'may be' I got to populate the /boot in the rootfs.img with my new kernel stuff, so I mounted it (losetp _offset, etc..) placed Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
This part isn't needed.
Is there someone at linaro who know how to boot a fresshly build kernel, the receipe on the web must be incorect or out dated?
linaro-dev mailing list is more appropriate.
Cheers, Fathi
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hi Bintian, As Chistopher said in this post, did you add ext4 in the menuconfig ?
things to check after menuconfig in your .config
CONFIG_BLK_DEV=y CONFIG_VIRTIO_BLK=y <<=== need to be added menuconfig missed(*) CONFIG_VIRTIO=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
(*) may be I goofed with menuconfig, so I added a posteriori manually in .config and forced y
The make the kernel rebuild your linux-system-foundation.axf and give it to the Foundation.
Should do the trick I guess
Thanks for your discussion, I will try later.
Thanks!
On 5 September 2013 19:00, Phi Debian phi.debian@gmail.com wrote:
Hi Bintian, As Chistopher said in this post, did you add ext4 in the menuconfig ?
things to check after menuconfig in your .config
CONFIG_BLK_DEV=y CONFIG_VIRTIO_BLK=y <<=== need to be added menuconfig missed(*) CONFIG_VIRTIO=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
(*) may be I goofed with menuconfig, so I added a posteriori manually in .config and forced y
The make the kernel rebuild your linux-system-foundation.axf and give it to the Foundation.
Should do the trick I guess
Hi Phi Debian,
Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said: * latest linux-linaro https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or * latest mainline kernel https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
Super!!!! I try that immedialty.
Regarding the web page, I went throuh it a couple of iteration in July then Aug, and amazingly the links to version specif stuff where always accurate like
wget http://releases.linaro.org/13.07/openembedded/aarch64/img-foundation.axf or wget http://releases.linaro.org/12.10/components/toolchain/...
letting me think that all was accurate, so I was looping on this broken link :)
I let you know my progress. Cheers, Phi
On Wed, Aug 21, 2013 at 3:45 PM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said:
- latest linux-linaro
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or
- latest mainline kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
Image.gz-3.7.0-rc2+ config-3.7.0-rc2+ System.map-3.7.0-rc2+ boot.axf In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
-- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs
Do I need some credential to do this ?
CU82$ tsocks git clone https://git.kernel.org/cgit/linux/kernel/git/torvalds/%3E Cloning into v3.11-rc6... warning: remote HEAD refers to nonexistent ref, unable to checkout.
CU82$ tsocks git clone https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git Cloning into linux-linaro-tracking... fatal: https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git/info/refs not found: did you run git update-server-info on the server?
On Wed, Aug 21, 2013 at 4:24 PM, Phi Debian phi.debian@gmail.com wrote:
Super!!!! I try that immedialty.
Regarding the web page, I went throuh it a couple of iteration in July then Aug, and amazingly the links to version specif stuff where always accurate like
wget http://releases.linaro.org/13.07/openembedded/aarch64/img-foundation.axf or wget http://releases.linaro.org/12.10/components/toolchain/...
letting me think that all was accurate, so I was looping on this broken link :)
I let you know my progress. Cheers, Phi
On Wed, Aug 21, 2013 at 3:45 PM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said:
- latest linux-linaro
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or
- latest mainline kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
> Image.gz-3.7.0-rc2+ > config-3.7.0-rc2+ > System.map-3.7.0-rc2+ > boot.axf > In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
-- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs
got this working .... tsocks git clone git://git.linaro.org/kernel/linux-linaro-tracking.git
Cheers, Phi
On Wed, Aug 21, 2013 at 5:01 PM, Phi Debian phi.debian@gmail.com wrote:
Do I need some credential to do this ?
CU82$ tsocks git clone https://git.kernel.org/cgit/linux/kernel/git/torvalds/%3E Cloning into v3.11-rc6... warning: remote HEAD refers to nonexistent ref, unable to checkout.
CU82$ tsocks git clone https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git Cloning into linux-linaro-tracking... fatal: https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git/info/refs not found: did you run git update-server-info on the server?
On Wed, Aug 21, 2013 at 4:24 PM, Phi Debian phi.debian@gmail.com wrote:
Super!!!! I try that immedialty.
Regarding the web page, I went throuh it a couple of iteration in July then Aug, and amazingly the links to version specif stuff where always accurate like
wget http://releases.linaro.org/13.07/openembedded/aarch64/img-foundation.axf or wget http://releases.linaro.org/12.10/components/toolchain/...
letting me think that all was accurate, so I was looping on this broken link :)
I let you know my progress. Cheers, Phi
On Wed, Aug 21, 2013 at 3:45 PM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said:
- latest linux-linaro
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or
- latest mainline kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi Phi Debian,
>> Image.gz-3.7.0-rc2+ >> config-3.7.0-rc2+ >> System.map-3.7.0-rc2+ >> boot.axf >> In there but still no joy
You might want to try to build a newer kernel, either the latest linux-linaro or latest mainline kernel.
Riku
-- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs
Well git.linaro.org/kernel/linux-linaro-tracking.git don't have arm64 inside arch/ so doesn't work really.
I am downloading from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
takes for ever real slow...
Still digging...
On Wed, Aug 21, 2013 at 5:06 PM, Phi Debian phi.debian@gmail.com wrote:
got this working .... tsocks git clone git://git.linaro.org/kernel/linux-linaro-tracking.git
Cheers, Phi
On Wed, Aug 21, 2013 at 5:01 PM, Phi Debian phi.debian@gmail.com wrote:
Do I need some credential to do this ?
CU82$ tsocks git clone https://git.kernel.org/cgit/linux/kernel/git/torvalds/%3E Cloning into v3.11-rc6... warning: remote HEAD refers to nonexistent ref, unable to checkout.
CU82$ tsocks git clone https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git Cloning into linux-linaro-tracking... fatal: https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git/info/refs not found: did you run git update-server-info on the server?
On Wed, Aug 21, 2013 at 4:24 PM, Phi Debian phi.debian@gmail.com wrote:
Super!!!! I try that immedialty.
Regarding the web page, I went throuh it a couple of iteration in July then Aug, and amazingly the links to version specif stuff where always accurate like
wget http://releases.linaro.org/13.07/openembedded/aarch64/img-foundation.axf or wget http://releases.linaro.org/12.10/components/toolchain/...
letting me think that all was accurate, so I was looping on this broken link :)
I let you know my progress. Cheers, Phi
On Wed, Aug 21, 2013 at 3:45 PM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said:
- latest linux-linaro
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or
- latest mainline kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote:
Well not being a got expert I did the line given in the receipe https://wiki.linaro.org/HowTo/BuildArm64Kernel
% git clone git://git.linaro.org/kernel/linaro-aarch64.git % cd linaro-aarch64 % git checkout -b linaro-aarch64 origin/linaro-aarch64
I dunno how to get the latest? Cheers, Phi
On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote: > Hi Phi Debian, > >>> Image.gz-3.7.0-rc2+ >>> config-3.7.0-rc2+ >>> System.map-3.7.0-rc2+ >>> boot.axf >>> In there but still no joy > > You might want to try to build a newer kernel, either the latest > linux-linaro or latest mainline kernel. > > Riku
-- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs
It is still a non trivial operation.
I can built linus kernel, but I can't build the boot loader, the
vexpress-foundation-v8.dts is missing, them
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf
then the FDT_SRC doesn't work
And I can't find what to link symlink with...
Thanx in advance for any lights :) Spend the all day on trying to boot a regular new build kernel but so far no success.
Cheers, Phi
On Wed, Aug 21, 2013 at 6:13 PM, Phi Debian phi.debian@gmail.com wrote:
Well git.linaro.org/kernel/linux-linaro-tracking.git don't have arm64 inside arch/ so doesn't work really.
I am downloading from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
takes for ever real slow...
Still digging...
On Wed, Aug 21, 2013 at 5:06 PM, Phi Debian phi.debian@gmail.com wrote:
got this working .... tsocks git clone git://git.linaro.org/kernel/linux-linaro-tracking.git
Cheers, Phi
On Wed, Aug 21, 2013 at 5:01 PM, Phi Debian phi.debian@gmail.com wrote:
Do I need some credential to do this ?
CU82$ tsocks git clone https://git.kernel.org/cgit/linux/kernel/git/torvalds/%3E Cloning into v3.11-rc6... warning: remote HEAD refers to nonexistent ref, unable to checkout.
CU82$ tsocks git clone https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git Cloning into linux-linaro-tracking... fatal: https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git/info/refs not found: did you run git update-server-info on the server?
On Wed, Aug 21, 2013 at 4:24 PM, Phi Debian phi.debian@gmail.com wrote:
Super!!!! I try that immedialty.
Regarding the web page, I went throuh it a couple of iteration in July then Aug, and amazingly the links to version specif stuff where always accurate like
wget http://releases.linaro.org/13.07/openembedded/aarch64/img-foundation.axf or wget http://releases.linaro.org/12.10/components/toolchain/...
letting me think that all was accurate, so I was looping on this broken link :)
I let you know my progress. Cheers, Phi
On Wed, Aug 21, 2013 at 3:45 PM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 21 August 2013 16:57, Phi Debian phi.debian@gmail.com wrote:
I am git iliterate, looking at https://git.linaro.org/gitweb, git://git.linaro.org/kernel/linaro-aarch64.git seems the latest... How could I get a better one?
We need to update this page.
As Riku said:
- latest linux-linaro
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or
- latest mainline kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs...
Phi
On Wed, Aug 21, 2013 at 1:33 PM, Phi Debian phi.debian@gmail.com wrote: > Well not being a got expert I did the line given in the receipe > https://wiki.linaro.org/HowTo/BuildArm64Kernel > > % git clone git://git.linaro.org/kernel/linaro-aarch64.git > % cd linaro-aarch64 > % git checkout -b linaro-aarch64 origin/linaro-aarch64 > > I dunno how to get the latest? > Cheers, > Phi > > > > On Wed, Aug 21, 2013 at 12:46 PM, Riku Voipio riku.voipio@linaro.org wrote: >> Hi Phi Debian, >> >>>> Image.gz-3.7.0-rc2+ >>>> config-3.7.0-rc2+ >>>> System.map-3.7.0-rc2+ >>>> boot.axf >>>> In there but still no joy >> >> You might want to try to build a newer kernel, either the latest >> linux-linaro or latest mainline kernel. >> >> Riku
-- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs
On 08/21/2013 03:04 PM, Phi Debian wrote:
It is still a non trivial operation.
I can built linus kernel, but I can't build the boot loader, the
vexpress-foundation-v8.dts is missing, them
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf
then the FDT_SRC doesn't work
And I can't find what to link symlink with...
You should be able to give the full path with FDT_SRC and not worry about symlinking.
arch/arm64/boot/dts/foundation-v8.dts was added in commit 90556ca1.
Christopher
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
Cheers, Phi
On Wed, Aug 21, 2013 at 9:51 PM, Christopher Covington cov@codeaurora.org wrote:
On 08/21/2013 03:04 PM, Phi Debian wrote:
It is still a non trivial operation.
I can built linus kernel, but I can't build the boot loader, the
vexpress-foundation-v8.dts is missing, them
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf
then the FDT_SRC doesn't work
And I can't find what to link symlink with...
You should be able to give the full path with FDT_SRC and not worry about symlinking.
arch/arm64/boot/dts/foundation-v8.dts was added in commit 90556ca1.
Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Cheers, Phi
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hi Phi,
On 08/23/2013 01:52 AM, Phi Debian wrote:
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log?
Christopher
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hi Christopher,
There is no virtio in this log... (and never saw a virtio reference in the receipe)
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059836K/4194304K available (2995K kernel code, 198K rwdata, 1076K rodata, 167K init, 150K bss, 134468K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc00047b000 - 0xffffffc0004a4c80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc00047ac30 ( 4076 kB) .data : 0xffffffc0004a8000 - 0xffffffc0004d99a0 ( 199 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004db000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled smc91x: IOADDR ffffff8000018000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff8000018000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
On Fri, Aug 23, 2013 at 2:33 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 01:52 AM, Phi Debian wrote:
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log?
Christopher
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
May be I should use another receipe to build and boot a kernel instead of the the one given on the web site https://wiki.linaro.org/HowTo/BuildArm64Kernel
Does someone do this another way ?
To me the docco there is almost good sounds like a tiny bit is missing, but I can decipher myslf.
Cheers, Phi
On Fri, Aug 23, 2013 at 2:48 PM, Phi Debian phi.debian@gmail.com wrote:
Hi Christopher,
There is no virtio in this log... (and never saw a virtio reference in the receipe)
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059836K/4194304K available (2995K kernel code, 198K rwdata, 1076K rodata, 167K init, 150K bss, 134468K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc00047b000 - 0xffffffc0004a4c80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc00047ac30 ( 4076 kB) .data : 0xffffffc0004a8000 - 0xffffffc0004d99a0 ( 199 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004db000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled smc91x: IOADDR ffffff8000018000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff8000018000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
On Fri, Aug 23, 2013 at 2:33 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 01:52 AM, Phi Debian wrote:
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log?
Christopher
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hi Phi,
On 08/23/2013 08:56 AM, Phi Debian wrote:
May be I should use another receipe to build and boot a kernel instead of the the one given on the web site https://wiki.linaro.org/HowTo/BuildArm64Kernel
Does someone do this another way ?
To me the docco there is almost good sounds like a tiny bit is missing, but I can decipher myslf.
If you run `make menuconfig` in between using the defconfig and building the image and make sure you've got the following configured, does that help?
Symbol: VIRTIO_MMIO [=y] Type : tristate Prompt: Platform bus driver for memory mapped virtio devices Location: -> Device Drivers (1) -> Virtio drivers Defined at drivers/virtio/Kconfig:34 Depends on: HAS_IOMEM [=y] Selects: VIRTIO [=y]
Symbol: VIRTIO_BLK [=y] Type : tristate Prompt: Virtio block driver Location: -> Device Drivers (2) -> Block devices (BLK_DEV [=y]) Defined at drivers/block/Kconfig:498 Depends on: BLK_DEV [=y] && VIRTIO [=y]
Christopher
On Fri, Aug 23, 2013 at 2:48 PM, Phi Debian phi.debian@gmail.com wrote:
Hi Christopher,
There is no virtio in this log... (and never saw a virtio reference in the receipe)
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059836K/4194304K available (2995K kernel code, 198K rwdata, 1076K rodata, 167K init, 150K bss, 134468K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc00047b000 - 0xffffffc0004a4c80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc00047ac30 ( 4076 kB) .data : 0xffffffc0004a8000 - 0xffffffc0004d99a0 ( 199 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004db000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled smc91x: IOADDR ffffff8000018000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff8000018000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
On Fri, Aug 23, 2013 at 2:33 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 01:52 AM, Phi Debian wrote:
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log?
Christopher
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote:
Hi Christopher,
Progress!!! giving the full path for FDT_SRC give make(1) success I obtained a linux-system-foundation.axf
Note that I build linux-system-foundation.axf this way.
make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts IMAGE=linux-system-foundation.axf
Now booting it gives ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf --block-device ./rootfs.img --network=nat
Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes)
. . . TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
So its not an illegal instruction anymore be really a wrong FS, The rootfs.img I used in the runstring is a gunzip of vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok The message Please append a correct "root=" boot option seems strange since the top console log gives Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0
Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Using .config - Linux/arm64 3.11.0-rc6 Kernel Configuration
I got Device Drivers ---> | | [ ] Virtualization drivers (NEW) ---- | | | | Virtio drivers ---> | |
I enter Virtio drivers as you suggest and I got only 1 line tha tis | | < > Platform bus driver for memory mapped virtio devices (NEW) | |
I select all this and save
I check the .config CONFIG_VIRTIO=y CONFIG_HAS_IOMEM=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_BLK=m <<== change this to y CONFIG_BLK_DEV=y
make kernel and bootloader
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #2 SMP Fri Aug 23 16:34:00 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059816K/4194304K available (3015K kernel code, 200K rwdata, 1080K rodata, 167K init, 150K bss, 134488K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc000481000 - 0xffffffc0004aac80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc000480c30 ( 4100 kB) .data : 0xffffffc0004ac000 - 0xffffffc0004de0a0 ( 201 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004e0000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled vda: vda1 vda2 smc91x: IOADDR ffffff800001c000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001c000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240) List of all partitions: fe00 2097152 vda driver: virtio_blk fe01 53216 vda1 00000000-01 fe02 2043904 vda2 00000000-02 No filesystem could mount root, tried: ext3 ext2 vfat fuseblk Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,2) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #2 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc00036628c>] dump_stack+0x70/0x90 [<ffffffc0003639a4>] panic+0xe8/0x208 [<ffffffc000481d80>] mount_block_root+0x254/0x278 [<ffffffc000481ebc>] mount_root+0x118/0x134 [<ffffffc000482018>] prepare_namespace+0x140/0x188 [<ffffffc000481958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc000362294>] kernel_init+0x18/0x148
Sounds like we progressed on more step.
May be now I should use a pure non partioned FS, so either I got to build an fs, or I got to dd the partition #2 I got from /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
I go try this...
On Fri, Aug 23, 2013 at 3:43 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 08:56 AM, Phi Debian wrote:
May be I should use another receipe to build and boot a kernel instead of the the one given on the web site https://wiki.linaro.org/HowTo/BuildArm64Kernel
Does someone do this another way ?
To me the docco there is almost good sounds like a tiny bit is missing, but I can decipher myslf.
If you run `make menuconfig` in between using the defconfig and building the image and make sure you've got the following configured, does that help?
Symbol: VIRTIO_MMIO [=y] Type : tristate Prompt: Platform bus driver for memory mapped virtio devices Location: -> Device Drivers (1) -> Virtio drivers Defined at drivers/virtio/Kconfig:34 Depends on: HAS_IOMEM [=y] Selects: VIRTIO [=y]
Symbol: VIRTIO_BLK [=y] Type : tristate Prompt: Virtio block driver Location: -> Device Drivers (2) -> Block devices (BLK_DEV [=y]) Defined at drivers/block/Kconfig:498 Depends on: BLK_DEV [=y] && VIRTIO [=y]
Christopher
On Fri, Aug 23, 2013 at 2:48 PM, Phi Debian phi.debian@gmail.com wrote:
Hi Christopher,
There is no virtio in this log... (and never saw a virtio reference in the receipe)
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059836K/4194304K available (2995K kernel code, 198K rwdata, 1076K rodata, 167K init, 150K bss, 134468K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc00047b000 - 0xffffffc0004a4c80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc00047ac30 ( 4076 kB) .data : 0xffffffc0004a8000 - 0xffffffc0004d99a0 ( 199 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004db000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled smc91x: IOADDR ffffff8000018000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff8000018000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 Call trace: [<ffffffc000087098>] dump_backtrace+0x0/0x12c [<ffffffc0000871d8>] show_stack+0x14/0x1c [<ffffffc0003618b0>] dump_stack+0x70/0x90 [<ffffffc00035efc8>] panic+0xe8/0x208 [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 [<ffffffc00047bebc>] mount_root+0x118/0x134 [<ffffffc00047c018>] prepare_namespace+0x140/0x188 [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 [<ffffffc00035d8b8>] kernel_init+0x18/0x148
On Fri, Aug 23, 2013 at 2:33 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 01:52 AM, Phi Debian wrote:
Hi Christopher, I was traveling yesterday, I will resume on this hopefully today....
This rootfs.imf is a short rename of standard (downloaded) decompressed /home/phi/armv8-dl/vexpress64-openembedded_lamp-armv8_20130719-403.img.gz
Then CU82$ file rootfs.img rootfs.img: x86 boot sector; partition 1: ID=0xe, active, starthead 1, startsector 63, 106432 sectors; partition 2: ID=0x83, starthead 0, startsector 106496, 4087808 sectors, code offset 0x0
And I can indeed mount the partition #2 and change file in there if needed later. For instance adding some .ko that I would have compiled along with my freshly build kernel.
Do you have virtio block device support properly configured? What kind of virtio-related messages do you see in the kernel log?
Christopher
On Thu, Aug 22, 2013 at 5:09 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/22/2013 02:22 AM, Phi Debian wrote: > Hi Christopher, > > Progress!!! giving the full path for FDT_SRC give make(1) success > I obtained a linux-system-foundation.axf > > Note that I build linux-system-foundation.axf this way. > > make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 > consolelog=9 rw console=ttyAMA0"' > FDT_SRC=../linux/arch/arm64/boot/dts/foundation-v8.dts > IMAGE=linux-system-foundation.axf > > Now booting it gives > ./Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 --image > ./kbuild/boot-wrapper-aarch64/linux-system-foundation.axf > --block-device ./rootfs.img --network=nat > > Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 > (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC > 2013.07) ) #1 SMP Wed Aug 21 19:05:06 CEST 2013 > CPU: AArch64 Processor [410fd000] revision 0 > Machine: Foundation-v8A > PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 > Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 > PID hash table entries: 4096 (order: 3, 32768 bytes) > > . > . > . > TCP: cubic registered > NET: Registered protocol family 17 > VFS: Cannot open root device "vda2" or unknown-block(0,0): error -6 > Please append a correct "root=" boot option; here are the available partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc6+ #1 > Call trace: > [<ffffffc000087098>] dump_backtrace+0x0/0x12c > [<ffffffc0000871d8>] show_stack+0x14/0x1c > [<ffffffc0003618b0>] dump_stack+0x70/0x90 > [<ffffffc00035efc8>] panic+0xe8/0x208 > [<ffffffc00047bd04>] mount_block_root+0x1d8/0x278 > [<ffffffc00047bebc>] mount_root+0x118/0x134 > [<ffffffc00047c018>] prepare_namespace+0x140/0x188 > [<ffffffc00047b958>] kernel_init_freeable+0x1b4/0x1d4 > [<ffffffc00035d8b8>] kernel_init+0x18/0x148 > > So its not an illegal instruction anymore be really a wrong FS, > The rootfs.img I used in the runstring is a gunzip of > vexpress64-openembedded_lamp-armv8_20130719-403.img.gz > > Dunno why it can't open /dev/vda2, the --block-device ./rootfs.img seems ok > The message Please append a correct "root=" boot option seems strange > since the top console log gives > Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 > > Well looks like we are getting closer to boot a newly build OS.
When you run `file rootfs.img` does it start with something like "x86 boot sector; partition 1" or "Linux rev 0.0 ext2 filesystem data"?
If it's the latter, the image doesn't have partitions and you'll need to use "root=/dev/vda" (no partition number specified).
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hi Phi,
On 08/23/2013 10:55 AM, Phi Debian wrote:
Using .config - Linux/arm64 3.11.0-rc6 Kernel Configuration
I got Device Drivers ---> | | [ ] Virtualization drivers (NEW) ---- | | | | Virtio drivers ---> | |
I enter Virtio drivers as you suggest and I got only 1 line tha tis | | < > Platform bus driver for memory mapped virtio devices (NEW) | |
I select all this and save
I check the .config CONFIG_VIRTIO=y CONFIG_HAS_IOMEM=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_BLK=m <<== change this to y CONFIG_BLK_DEV=y
make kernel and bootloader
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #2 SMP Fri Aug 23 16:34:00 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059816K/4194304K available (3015K kernel code, 200K rwdata, 1080K rodata, 167K init, 150K bss, 134488K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc000481000 - 0xffffffc0004aac80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc000480c30 ( 4100 kB) .data : 0xffffffc0004ac000 - 0xffffffc0004de0a0 ( 201 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004e0000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled vda: vda1 vda2 smc91x: IOADDR ffffff800001c000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001c000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240)
Make sure EXT4 support is compiled in as well.
Regards, Christopher
Opps missed that one rebuild
On Fri, Aug 23, 2013 at 5:05 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 10:55 AM, Phi Debian wrote:
Using .config - Linux/arm64 3.11.0-rc6 Kernel Configuration
I got Device Drivers ---> | | [ ] Virtualization drivers (NEW) ---- | | | | Virtio drivers ---> | |
I enter Virtio drivers as you suggest and I got only 1 line tha tis | | < > Platform bus driver for memory mapped virtio devices (NEW) | |
I select all this and save
I check the .config CONFIG_VIRTIO=y CONFIG_HAS_IOMEM=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_BLK=m <<== change this to y CONFIG_BLK_DEV=y
make kernel and bootloader
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #2 SMP Fri Aug 23 16:34:00 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059816K/4194304K available (3015K kernel code, 200K rwdata, 1080K rodata, 167K init, 150K bss, 134488K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc000481000 - 0xffffffc0004aac80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc000480c30 ( 4100 kB) .data : 0xffffffc0004ac000 - 0xffffffc0004de0a0 ( 201 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004e0000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled vda: vda1 vda2 smc91x: IOADDR ffffff800001c000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001c000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240)
Make sure EXT4 support is compiled in as well.
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
Hurray!!! Jeez I definitly owe you a pint !!!
The docco page need a cleanup, dunno who can do that, I may try but I guess there must be some procedure to follow to do so.
The booted OS root@genericarmv8:/# uname -a Linux genericarmv8 3.11.0-rc6+ #3 SMP Fri Aug 23 16:55:42 CEST 2013 aarch64 GNU/Linux
The current untouched vexpress lamp FS root@genericarmv8:/# ls /boot/config* /boot/config-3.10.1.0-1-linaro-vexpress64
I got to populate the fs with my own dev .ko and check in insmod works ok :)
Cheers Phi
On Fri, Aug 23, 2013 at 5:12 PM, Phi Debian phi.debian@gmail.com wrote:
Opps missed that one rebuild
On Fri, Aug 23, 2013 at 5:05 PM, Christopher Covington cov@codeaurora.org wrote:
Hi Phi,
On 08/23/2013 10:55 AM, Phi Debian wrote:
Using .config - Linux/arm64 3.11.0-rc6 Kernel Configuration
I got Device Drivers ---> | | [ ] Virtualization drivers (NEW) ---- | | | | Virtio drivers ---> | |
I enter Virtio drivers as you suggest and I got only 1 line tha tis | | < > Platform bus driver for memory mapped virtio devices (NEW) | |
I select all this and save
I check the .config CONFIG_VIRTIO=y CONFIG_HAS_IOMEM=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_BLK=m <<== change this to y CONFIG_BLK_DEV=y
make kernel and bootloader
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Initializing cgroup subsys cpu Linux version 3.11.0-rc6+ (phi@hpfrcu82) (gcc version 4.8.2 20130624 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.07-1 - Linaro GCC 2013.07) ) #2 SMP Fri Aug 23 16:34:00 CEST 2013 CPU: AArch64 Processor [410fd000] revision 0 Machine: Foundation-v8A PERCPU: Embedded 10 pages/cpu @ffffffc87ffaa000 s11392 r8192 d21376 u40960 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/vda2 consolelog=9 rw console=ttyAMA0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) software IO TLB [mem 0x8f8000000-0x8fc000000] (64MB) mapped at [ffffffc878000000-ffffffc87bffffff] Memory: 4059816K/4194304K available (3015K kernel code, 200K rwdata, 1080K rodata, 167K init, 150K bss, 134488K reserved) Virtual kernel memory layout: vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000 (245759 MB) vmemmap : 0xffffffbc01c00000 - 0xffffffbc1f800000 ( 476 MB) modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB) .init : 0xffffffc000481000 - 0xffffffc0004aac80 ( 168 kB) .text : 0xffffffc000080000 - 0xffffffc000480c30 ( 4100 kB) .data : 0xffffffc0004ac000 - 0xffffffc0004de0a0 ( 201 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. NR_IRQS:64 nr_irqs:64 0 GIC CPU mask not found - kernel will fail to boot. GIC CPU mask not found - kernel will fail to boot. Architected local timer running at 100.00MHz (phys). Console: colour dummy device 80x25 Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=1000000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 256 hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available CPU1: failed to boot: -38 CPU2: failed to boot: -38 CPU3: failed to boot: -38 Brought up 1 CPUs SMP: Total of 1 processors activated (200.00 BogoMIPS). devtmpfs: initialized atomic64 test passed NET: Registered protocol family 16 vdso: 2 pages (1 code, 1 data) at base ffffffc0004e0000 hw-breakpoint: found 16 breakpoint and 16 watchpoint registers. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized Switched to clocksource arch_sys_counter NET: Registered protocol family 2 TCP established hash table entries: 32768 (order: 7, 524288 bytes) TCP bind hash table entries: 32768 (order: 7, 524288 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP: reno registered UDP hash table entries: 2048 (order: 4, 65536 bytes) UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. fuse init (API version 7.22) msgmni has been set to 7929 io scheduler noop registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled vda: vda1 vda2 smc91x: IOADDR ffffff800001c000 doesn't match configuration (300). smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre nico@fluxnic.net eth0: SMC91C11xFD (rev 1) at ffffff800001c000 IRQ 47 [nowait] eth0: Ethernet addr: 00:02:f7:ef:7e:f2 mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 EXT3-fs (vda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (vda2): error: couldn't mount because of unsupported optional features (240)
Make sure EXT4 support is compiled in as well.
Regards, Christopher
-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.
-
Bintian Wang -
Christopher Covington -
Fathi Boudra -
Phi Debian -
Riku Voipio