hi, I had build an image.elf with the l4android.run in the directory ports-foc/run on genode13.02 . I build with the platform foc_panda. When I run the image.elf on Pandaboard, it goes to some errors. here is the Error log: ////////////////////////////////////////////////////// [init] nitpicker: invalid route to non-existing server "fb-drv" ///////////////////////////////////////// so I added the follow into l4android.run: <start name="fb_drv"> <binary name="omap4_fb_drv"/> <resource name="RAM" quantum="4M"/> <provides><service name="Framebuffer"/></provides> </start> <start name="sd_card_drv"> <resource name="RAM" quantum="4M"/> <provides><service name="Block"/></provides> </start> <start name="usb_drv"> <resource name="RAM" quantum="12M"/> <provides> <service name="Input"/> <service name="Nic"/> </provides> <config> <hid/> <nic mac="2e:60:90:0c:4e:01" /> </config> </start> after that, I can start the l4android on Pandaboard. I can see something on "log_term" part and "terminal_log" part,but there are nothing on "android_term " part, l4android can not work rightly and system-ginger.img can not be started on Pandaboard ? How I can do to fix these problems? 2013-03-25
longjks
Hi,
On 03/25/2013 03:38 PM, longjks wrote:
hi, I had build an image.elf with the l4android.run in the directory ports-foc/run on genode13.02 . I build with the platform foc_panda. When I run the image.elf on Pandaboard, it goes to some errors. here is the Error log: ////////////////////////////////////////////////////// [init] nitpicker: invalid route to non-existing server "fb-drv" /////////////////////////////////////////
ok, I've to admit this script is used to test L4Android on top of Fiasco.OC x86 32bit QEMU and Fiasco.OC ARM pbxa9 QEMU only!
So it's not tested on top of the Pandaboard, that's why some driver configuration data are missing. So you're exploring new frontiers ;-).
Nevertheless, all necessary tools exist to run the scenario on top of Pandaboard.
so I added the follow into l4android.run:
<start name="fb_drv"> <binary name="omap4_fb_drv"/> <resource name="RAM" quantum="4M"/> <provides><service name="Framebuffer"/></provides> </start> <start name="sd_card_drv"> <resource name="RAM" quantum="4M"/> <provides><service name="Block"/></provides> </start> <start name="usb_drv"> <resource name="RAM" quantum="12M"/> <provides> <service name="Input"/> <service name="Nic"/> </provides> <config> <hid/> <nic mac="2e:60:90:0c:4e:01" /> </config> </start>
ok, that looks fine!
after that, I can start the l4android on Pandaboard. I can see something on "log_term" part and "terminal_log" part,but there are nothing on "android_term " part, l4android can not work rightly and system-ginger.img can not be started on Pandaboard ? How I can do to fix these problems?
Well, the debug messages in "terminal_log" should help you to solve problems of Linux booting the android stuff. Without having that information, my first guess is that your Android system image (system-ginger.img) is not in the place like Linux is expecting it.
If you're looking at the unmodified "l4android.run" script, you'll see that QEMU is instructed to provide the system image as a sd-card. If you are booting the scenario on real Pandaboard hardware, you're forced to use a sd-card with a partition-table, where the bootloader stuff is located on the first bootable vfat partition. So here lies the first problem. You'll have to prepare a second partition holding the Android system image. Moreover, you've to either modify the Android initramfs to take the second partition of the sd-card as root filesystem, or FMPOV even easier: add Genode's partition server ("part_blk") to your setup. That will enable you to give exactly one of the partitions, containing the system image, as a block device to Linux. It might look like the following, assuming you copied the system image to the second partition:
<start name="part_blk"> <resource name="RAM" quantum="2M"/> <provides><service name="Block"/></provides> <config> <policy label="l4android -> sda" partition="2" /> </config> <route> <service name="Block"> <child name="sd_card_drv"/></service> <any-service> <parent/> <any-child/> </any-service> </route> </start>
As already said, I can only guess what's missing without some logs, your sd-card layout, or/and a complete script.
Best regards Stefan
2013-03-25
longjks
Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Like Stefan said , I can started L4Android on top of Fiasco.OC x86 32bit QEMU. It is exciting to see that Android is runing on genode. Then I decided to modify the 'l4android.run' script to started L4Andaroid on PandaBoard. I have add the necessary driver into the 'l4android.run' script and copy the system image(system-ginger.img)to the second partition. But l4android still can not run rightly. I can see the last log in 'terminal_log ' is that: !io scheduler cfq registered(default) !brd:module loaded !mousedev: PS/2 mouse device common for all mice !ashemen: initialized !logger:created 256K log 'log_main' !logger:created 256K log 'log_events' !logger:created 256K log 'log_radio' !logger:created 256K log 'log_system' !ttyS0 at MMIO 0x1(irq=211) is a L4 !rtc-genode rtc-genode.0: rtc core:registered rtc-genode as rtc0 !genode_fb:framebuffer at 0x00000000, size 600k !genode_fb:mode is 640x480x16 !Console:switching to colour frame buffer device 80x30 ! input: Genode input key as /devices/virtual/input/input0 !intput:Genode intput mouse as /devices/virtual/intput/intput! Then it stops. What is the problem? and how can I get the whole log from "terminal_log"? You can get the log and l4android.run I modified in attachment. thanks. longjks
Hi,
On 03/30/2013 08:03 AM, longjks wrote:
Like Stefan said , I can started L4Android on top of Fiasco.OC x86 32bit QEMU. It is exciting to see that Android is runing on genode. Then I decided to modify the 'l4android.run' script to started L4Andaroid on PandaBoard. I have add the necessary driver into the 'l4android.run' script and copy the system image(system-ginger.img)to the second partition. But l4android still can not run rightly. I can see the last log in 'terminal_log' is that: !io scheduler cfq registered(default) !brd:module loaded !mousedev: PS/2 mouse device common for all mice !ashemen: initialized !logger:created 256K log 'log_main' !logger:created 256K log 'log_events' !logger:created 256K log 'log_radio' !logger:created 256K log 'log_system' !ttyS0 at MMIO 0x1(irq=211) is a L4 !rtc-genode rtc-genode.0: rtc core:registered rtc-genode as rtc0 !genode_fb:framebuffer at 0x00000000, size 600k !genode_fb:mode is 640x480x16 !Console:switching to colour frame buffer device 80x30 ! input: Genode input key as /devices/virtual/input/input0 !intput:Genode intput mouse as /devices/virtual/intput/intput! Then it stops. What is the problem? and how can I get the whole log from "terminal_log"?
You can get the whole log by removing the log_term, and use core's LOG service for all children instead. Then all logs will appear on serial line. We've put the log_term in place in some run-scripts only for demonstration purposes, when there is no serial line available. For debugging it's often more convenient to use only the serial line.
You can get the log and l4android.run I modified in attachment.
The patch you've sent is not complete, it won't build all necessary components. Anyway, what I could see from your log file is an unresolved pagefault from one component:
"Could not resolve pf=400feff8 ip=10004b8"
After rebuilding your scenario myself, and entering the kernel debugger (via escape on the serial console) after the boot process completes, I've seen it is the sd_card driver that caused the fault.
The address 0x400feff8 immediately set off my alarm bells. In Genode at address 0x40000000 normally the thread context area starts including the thread's stacks. Moreover, the pagefault address is nearby a page boundary. When looking at the instruction that raised the fault ("push {r3,lr}") it gets obvious that a stack overflow occured.
The problem was the usleep function implemented in the omap4 sd_card driver. When this driver was written, there was no usleep function existent in the timer session interface. Therefore, usleep was provided in this driver by simply wrapping the msleep function of the timer session. Some time ago, the timer session interface was rewritten to use an asynchronous signal mechanism. The msleep call in this interface was replaced by a simple wrapper around the latterly available usleep function. When usleep got available in the timer session interface, nobody removed the superfluous function in the sd-card driver. Now, when either usleep or msleep were called in the Omap4 sd-card driver, that function called the other one, and vice versa in an endless loop.
I've opened a corresponding issue in our tracker:
https://github.com/genodelabs/genode/issues/705
There you'll find a patch to resolve that problem. With that patch in place Android boots fine on my Pandaboard.
Regards Stefan
thanks.
longjks
Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
hi,
I've opened a corresponding issue in our tracker: https://github.com/genodelabs/genode/issues/705 There you'll find a patch to resolve that problem. With that patch in place Android boots fine on my Pandaboard.
using this patch, I can not see the error log " Could not resolve pf=400feff8 ip=10004b8". Howerver, Android can not boot fine on my Pandaboard.
From the log, I found this code can not work.
In ports-foc/src/lib/l4lx/genode_block.cc,214 line. !!devices[j] = new (env()->heap()) Block_device(label); It can not run into the construction function of Block_device. I think there are something wrong in this three line: In ports-foc/src/lib/l4lx/genode_block.cc,103-105 line. !: _alloc(Genode::env()->heap()), ! _session(&_alloc, TX_BUF_SIZE, label), ! _irq_cap(L4lx::vcpu_connection()->alloc_irq()) But i can not know how to fix this wrong.
You can get the whole log by removing the log_term, and use core's LOG service for all children instead. Then all logs will appear on serial line. We've put the log_term in place in some run-scripts only for demonstration purposes, when there is no serial line available. For debugging it's often more convenient to use only the serial line.
I can removing the log_term, you can see my whole log in the attachement.
The patch you've sent is not complete, it won't build all necessary components.
Would you give me you run script for l4android?
thanks 2013-04-06
longjks
Hi,
On 04/06/2013 05:43 AM, longjks wrote:
hi,
I've opened a corresponding issue in our tracker: https://github.com/genodelabs/genode/issues/705 There you'll find a patch to resolve that problem. With that patch in place Android boots fine on my Pandaboard.
using this patch, I can not see the error log " Could not resolve pf=400feff8 ip=10004b8". Howerver, Android can not boot fine on my Pandaboard. From the log, I found this code can not work. In ports-foc/src/lib/l4lx/genode_block.cc,214 line. !!devices[j] = new (env()->heap()) Block_device(label); It can not run into the construction function of Block_device. I think there are something wrong in this three line: In ports-foc/src/lib/l4lx/genode_block.cc,103-105 line. !: _alloc(Genode::env()->heap()), ! _session(&_alloc, TX_BUF_SIZE, label), ! _irq_cap(L4lx::vcpu_connection()->alloc_irq()) But i can not know how to fix this wrong.
The constructor of the "Block_device" in the L4Linux block para-virtualized driver simply waits for the connection to the Block service. It can't get a connection, because the sd-card driver seems to exit when trying to detect the card. Have a look at this part of your log:
[init -> sd_card_drv] Could not detect high-capacity card [init -> sd_card_drv] C++ runtime: Sd_card::Host_controller::Detection_failed
Maybe, you're not using a high capacity card? The driver only supports SDHC cards.
You can get the whole log by removing the log_term, and use core's LOG service for all children instead. Then all logs will appear on serial line. We've put the log_term in place in some run-scripts only for demonstration purposes, when there is no serial line available. For debugging it's often more convenient to use only the serial line.
I can removing the log_term, you can see my whole log in the attachement.
The patch you've sent is not complete, it won't build all necessary components.
Would you give me you run script for l4android?
Have a look here:
https://raw.github.com/skalk/genode/l4android-panda/ports-foc/run/l4android_...
I've written a simplified version of the l4android.run script for you, which runs on Fiasco.OC/Pandaboard only.
thanks 2013-04-06
longjks
Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
hi, Stefan wrote
Maybe, you're not using a high capacity card? The driver only supports SDHC cards.
You are right! I used a sdcard, not SDHC card. Now I used SDHC card to start l4Android on PandaBoard. However it still can not boot well. some error like this: "virtual void Genode::Pager_activation_base::entry(): Could not resolve pf=400fef3c ip=1023ad0" Just like you mail said before,you put a patch on the Internet(https://github.com/genodelabs/genode/issues/705). Before I use this batch, the sdcard_driver can not find the SDHC card. After I use this patch, the sdcard_driver can find the SDHC card, but there are another error like above. I used the l4android.run script your said, this error is still there. I am finding the way to solving this error, maybe you can help me to fix this error. You can get the log of using my l4android.run script, my l4android run script. and the log of using your l4android.run script in the attachment. By the way, my genode version is 13.02, that is same with you ? My SDHC card's capacity is 4G. It has three partitions. The first partition is bootable FAT32 partition, 128M,where I put MIO and uboot.bin. The second partition is EXTS partition, 256M, where I put Android system image. The third partition is EXTS partititon, 1000M. that is OK?
thanks
Sorry for forgetting attachment !!!
hi, Stefan wrote
Maybe, you're not using a high capacity card? The driver only supports SDHC cards.
You are right! I used a sdcard, not SDHC card. Now I used SDHC card to start l4Android on PandaBoard. However it still can not boot well. some error like this: "virtual void Genode::Pager_activation_base::entry(): Could not resolve pf=400fef3c ip=1023ad0" Just like you mail said before,you put a patch on the Internet(https://github.com/genodelabs/genode/issues/705). Before I use this batch, the sdcard_driver can not find the SDHC card. After I use this patch, the sdcard_driver can find the SDHC card, but there are another error like above. I used the l4android.run script your said, this error is still there. I am finding the way to solving this error, maybe you can help me to fix this error. You can get the log of using my l4android.run script, my l4android run script. and the log of using your l4android.run script in the attachment. By the way, my genode version is 13.02, that is same with you ? My SDHC card's capacity is 4G. It has three partitions. The first partition is bootable FAT32 partition, 128M,where I put MIO and uboot.bin. The second partition is EXTS partition, 256M, where I put Android system image. The third partition is EXTS partititon, 1000M. that is OK?
thanks
Hi,
On 04/10/2013 02:08 PM, longjks wrote:
hi,
Stefan wrote
Maybe, you're not using a high capacity card? The driver only supports SDHC cards.
You are right! I used a sdcard, not SDHC card. Now I used SDHC card to start l4Android on PandaBoard.
However it still can not boot well. some error like this:
"virtual void Genode::Pager_activation_base::entry(): Could not resolve pf=400fef3c ip=1023ad0"
Just like you mail said before,you put a patch on the Internet(https://github.com/genodelabs/genode/issues/705).
Before I use this batch, the sdcard_driver can not find the SDHC card. After I use this patch, the sdcard_driver can find the SDHC card, but
there are another error like above. I used the l4android.run script your said, this error is still there.
I am finding the way to solving this error, maybe you can help me to fix this error.
You can get the log of using my l4android.run script, my l4android run script. and the log of using your l4android.run script in the attachment.
well, from the log I only can see, there is probably still a thread that exceeds its stack. You can enter the kernel-debugger yourself (pressing ESC in the serial terminal), and press "lp" to show the process list. One thread will wait for the pager of the system, thereby you can identify the component that raised the fault.
By the way, my genode version is 13.02, that is same with you ?
I've used current master branch of Genode's Github repository. You can simply checkout the branch, where I've put the run-script into:
repo: git://github.com/skalk/genode.git branch: l4android-panda
From your log messages I can see, that you've modified the code, and
added at least several print messages. Please, ensure that you take the unmodified version first.
My SDHC card's capacity is 4G. It has three partitions. The first partition is bootable FAT32 partition, 128M,where I put MIO and uboot.bin. The second partition is EXTS partition, 256M, where I put Android system image. The third partition is EXTS partititon, 1000M. that is OK?
You don't need to format the second partition, but the size is ok. Just copy the system-ginger.img file e.g. via "dd" to the second partition. The third partition won't be affected.
Regards Stefan
thanks
Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
hi, Stefan wrote:
I've used current master branch of Genode's Github repository. You can
simply checkout the branch, where I've put the run-script into: repo: git://github.com/skalk/genode.git branch: l4android-panda
Using the current master branch fo Genode's Github repository, I can run Android on my PandaBoard. thanks for you help.^-^ From the l4android.run script, I know that I got root-arm-ginger.gz and systemarm-ginger.img from the url below: "http://genode.org/files/release-11.11/l4lx/root-arm-ginger.gz" "http://genode.org/files/release-11.11/l4lx/system-arm-ginger.img" Do you modify the source code of Android ( Gingerbread) and initramfs? Can I run other version of Android（like Ice Cream Sandwich）on Pandaboard?
thanks, longjks
Hi,
On 04/11/2013 04:31 PM, longjks wrote:
hi,
Stefan wrote:
I've used current master branch of Genode's Github repository. You can
simply checkout the branch, where I've put the run-script into: repo: git://github.com/skalk/genode.git branch: l4android-panda
Using the current master branch fo Genode's Github repository, I can run Android on my PandaBoard. thanks for you help.^-^ From the l4android.run script, I know that I got root-arm-ginger.gz and systemarm-ginger.img from the url below: "http://genode.org/files/release-11.11/l4lx/root-arm-ginger.gz" "http://genode.org/files/release-11.11/l4lx/system-arm-ginger.img" Do you modify the source code of Android ( Gingerbread) and initramfs?
The images are taken from the L4Android project: http://l4android.org/ I think I've modified the initramfs a bit, so that it will use our block device. But to be honest: I can't remember anymore.
Can I run other version of Android（like Ice Cream Sandwich）on Pandaboard?
I've never tried that before. It'll depend on, whether the L4Android patch contains all necessary Android patches. Moreover, you'll probably have to build an own Android system image. Maybe you should ask that question on the L4Android mailing list, there is some chance somebody did that work before:
http://lists.l4android.org/mailman/listinfo/l4android-dev
Regards Stefan
thanks, longjks
Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
hi, I am working to make Android4.0.4 boot on PandaBoard. However the l4android stop unexpected. I can see some page-fault error in the android_term, but I can not save it from android_term. !WARN: rild: Page-fault above task size: pfa=ffff00c0 pc=b7b02758 !0:ffff00b4 00000005 00000000 ffff00b4 4:b7b2e004 00000005 00000004 0000ab1c !8:b0012fa8 b7b31000 00050000 b7aec000 12:00000000 bf4d56d8 b0003a43 b7ba5758 !CPSR:40000130 Err:0041000f What does this error mean? last mail, Stefan said:
well, from the log I only can see, there is probably still a thread that exceeds its stack. You can enter the kernel-debugger yourself (pressing ESC in the serial terminal), and press "lp" to show the process list. One thread will wait for the pager of the system, thereby you can identify the component that raised the fault.
How to decide which thread is waiting for the pager of the system? Do you have some help doc for debugging？
By the way, You can see my log in attachment.
thanks.
hi, I am working on genode-13.02, from the source code, I can find that it used the l4android 3.5.
From the l4android.org, I can see that l4android has update to 3.6. Do you have plan to update l4android to 3.6 in the next
version of genode?
hi, last mail, Stefan said
You can get the whole log by removing the log_term, and use core's LOG service for all children instead. Then all logs will appear on serial line. We've put the log_term in place in some run-scripts only for demonstration purposes, when there is no serial line available. For debugging it's often more convenient to use only the serial line.
By removing the log_term in l4android, I can see the log appear on serial line. How can I make the log on android_term appear on serial line? When I debugging, it is not convenient to use android_term. thanks. longjks
Hi,
sorry for my late response!
On 04/15/2013 01:59 PM, longjks wrote:
hi, I am working to make Android4.0.4 boot on PandaBoard. However the l4android stop unexpected. I can see some page-fault error in the android_term, but I can not save it from android_term. !WARN: rild: Page-fault above task size: pfa=ffff00c0 pc=b7b02758 !0:ffff00b4 00000005 00000000 ffff00b4 4:b7b2e004 00000005 00000004 0000ab1c !8:b0012fa8 b7b31000 00050000 b7aec000 12:00000000 bf4d56d8 b0003a43 b7ba5758 !CPSR:40000130 Err:0041000f What does this error mean?
Well, that error is printed by the Linux kernel, and informs you about the pagefault of one of its user tasks. The rild process (radio interface layer daemon of Android) caused a pagefault. I recommend to first examine the corresponding binary (/system/bin/rild ?) what's going on at address 0xb7b02758.
last mail, Stefan said:
well, from the log I only can see, there is probably still a thread that exceeds its stack. You can enter the kernel-debugger yourself (pressing ESC in the serial terminal), and press "lp" to show the process list. One thread will wait for the pager of the system, thereby you can identify the component that raised the fault.
How to decide which thread is waiting for the pager of the system?
You've to distinct L4Linux processes here from native L4 processes. As I said, above error message comes from the Linux kernel. The para-virtualized L4Linux kernel uses a special feature of the Fiasco.OC kernel, namely the VCPU, to implement its own scheduling, and exception mechanisms. A virtual CPU, or short VCPU, is a special thread. When associated with Fiasco.OC IRQ objects, its execution can be interrupted. Moreover, it's possible to run one and the same VCPU in different address spaces (L4 tasks). Therefore, VCPUs enable implementation of CPU virtualization in L4Linux, more easily and effectively in contrast to the formerly used model, where all Linux processes where mapped to L4 threads. As a consequence, all Linux threads (including kernel threads) that run on top of the same CPU in Linux are seen as one and the same thread in the Fiasco.OC kernel debugger. Thereby the Fiasco.OC kernel debugger mostly isn't the right place to debug Linux userland problems.
Instead you should either try the Android Debug Bridge, or strace, gdb etc. from within your Android initramfs. If that all doesn't help, you might instrument the L4Linux kernel to find out what happens.
Do you have some help doc for debugging？
I'm afraid no we haven't. In fact we're just users of the Fiasco.OC kernel too. The actual development of the Fiasco.OC and L4Linux kernel isn't done by the Genode community, but by TU-Dresden and the l4-hackers community. Nevertheless, AFAIK there isn't such a document available.
By the way, You can see my log in attachment.
thanks.
Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
On 04/16/2013 03:17 PM, longjks wrote:
hi, I am working on genode-13.02, from the source code, I can find that it used the l4android 3.5. From the l4android.org, I can see that l4android has update to 3.6. Do you have plan to update l4android to 3.6 in the next version of genode?
concurrently, there is no such item on the road map of the Genode community. But we're always happy about any type of contribution!
Regards Stefan
Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi, At 2013-04-26 20:50:24,"Stefan Kalkowski" <stefan.kalkowski@...1...> wrote:
Hi,
On 04/16/2013 03:17 PM, longjks wrote:
hi, I am working on genode-13.02, from the source code, I can find that it used the l4android 3.5. From the l4android.org, I can see that l4android has update to 3.6. Do you have plan to update l4android to 3.6 in the next version of genode?
concurrently, there is no such item on the road map of the Genode community. But we're always happy about any type of contribution!
Regards Stefan
I am working on l4android3.6 to start android4.0, now there are some problem in there: the l4android3.6 can not work well the last log is that: [init -> l4android] Terminating L4Linux. [init -> l4android] Still alive, going zombie??? I found the patch files in the directory 'ports-foc/patches' and use these patches to l4android3.6. You know that l4android3.6 is different from l4android3.5, so that some patches will not take effect. I have to change these file manually. I am sure I have add all patches to l4android3.6, but it still can not work. Maybe there are some more place to change in l4android3.6. Where you can figure out the problem? Any suggestions would be greatly appreciated. I know the l4android3.6 is not no your road map, but I still hope to get some suggestions from you. You can see the run script and the whole log in the attachment. thanks. longjks
Hi,
On 05/29/2013 05:13 PM, longjks wrote:
I am working on l4android3.6 to start android4.0, now there are some problem in there: the l4android3.6 can not work well the last log is that: [init -> l4android] Terminating L4Linux. [init -> l4android] Still alive, going zombie???
This last log is the outcome of a reboot triggered by the Android userland processes, have a look at the lines above those last ones:
init: critical process 'ueventd' exited 4 times in 4 minutes; ... Restarting system with command 'recovery'.
Android's init process tells you that the uevent daemon for whatever reasons crashed repeatedly. To investigate the root cause of the problem, you might increase the loglevel of Android's init process (init.rc file) or otherwise instrument your Android initramfs. Normally, you should also be able to connect via Android's debug bridge 'adb' to your Android instance. With it you can use the 'logcat' command to dump the log files. Alternatively, if you aren't able to connect via 'adb', you might add a service to Android's init configuration that dumps the logfiles to the Linux console. Here is a hint how to do that:
https://groups.google.com/forum/?fromgroups#!topic/android-kernel/h9kphjznwp...
In general, these are Android porting specific questions, and you'll find probably more Android expertise on an Android specific mailing lists, like e.g. the l4android mailing list:
http://lists.l4android.org/mailman/listinfo
I found the patch files in the directory 'ports-foc/patches' and use these patches to l4android3.6. You know that l4android3.6 is different from l4android3.5, so that some patches will not take effect. I have to change these file manually. I am sure I have add all patches to l4android3.6, but it still can not work. Maybe there are some more place to change in l4android3.6. Where you can figure out the problem? Any suggestions would be greatly appreciated. I know the l4android3.6 is not no your road map, but I still hope to get some suggestions from you.
My suggestion is: try to find out the root cause of the problem at first. Why do the Android user processes crash? Mostly, it's not even a kernel source problem, but just a different kernel configuration that is needed.
Good luck, and best regards Stefan
You can see the run script and the whole log in the attachment. thanks. longjks
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-
longjks -
Stefan Kalkowski