Discussion:
error related to block device while running make run/l4linux
john stokes
2016-06-27 19:15:12 UTC
Permalink
after doing make menuconfig and selecting block device support for l4linux
so that when i boot it on real hardware the root file system can be
mounted easily.but i am getting this infinite loop is there any solution
for bloc device support ?

[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
Norman Feske
2016-06-29 18:20:26 UTC
Permalink
Hello,
Post by john stokes
after doing make menuconfig and selecting block device support for
l4linux so that when i boot it on real hardware the root file system
can be mounted easily.but i am getting this infinite loop is there any
solution for bloc device support ?
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
L4Linux is not permitted to access physical devices directly. In order
to use a block device, you will need to add a block driver component
(such as the AHCI driver) to your Genode scenario. If the L4Linux config
contains a sub node like '<block label="sda"/>', L4Linux will request a
block session, which needs to be routed to the block driver.

Please refer ports-foc/README for more information about configuring
L4Linux. For integrating the AHCI driver into your scenario, you may
find the run scripts at os/run/ahci_* useful.

Cheers
Norman
--
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
john stokes
2016-06-29 19:25:51 UTC
Permalink
thanks
Post by Norman Feske
Hello,
Post by john stokes
after doing make menuconfig and selecting block device support for
l4linux so that when i boot it on real hardware the root file system
can be mounted easily.but i am getting this infinite loop is there any
solution for bloc device support ?
[init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64
L4Linux is not permitted to access physical devices directly. In order
to use a block device, you will need to add a block driver component
(such as the AHCI driver) to your Genode scenario. If the L4Linux config
contains a sub node like '<block label="sda"/>', L4Linux will request a
block session, which needs to be routed to the block driver.
Please refer ports-foc/README for more information about configuring
L4Linux. For integrating the AHCI driver into your scenario, you may
find the run scripts at os/run/ahci_* useful.
Cheers
Norman
--
Dr.-Ing. Norman Feske
Genode Labs
http://www.genode-labs.com · http://genode.org
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
GeschÀftsfÌhrer: Dr.-Ing. Norman Feske, Christian Helmuth
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
Loading...