linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

Presentation on Kernel Shark by Steven Rostedt

by Viresh Kumar

In case somebody needs.. Video: http://www.youtube.com/watch?v=ABRtzVtUVBo Presentation: http://elinux.org/images/6/64/Elc2011_rostedt.pdf

11 years, 9 months

Heap reclaim question/documentation

by Karlsson, Magnus

Hi, Just wondering if somebody could point me to a good document on how the heap reclamation algorithm works for memory allocated in a user space program using the regular malloc/calloc functions. I am specifically interested in how effective it is in reclaiming memory. E.g., does it only reclaim from top of heap or does it reclaim from the complete heap? Are there multiple options for reclamation algorithms? Etc. Thank you: Magnus Magnus Karlsson Software Development Engineering Manager LSI Corporation Box 1024, Knarrarnäsgatan 15 SE-164 21 Kista, Sweden TEL +46 8 594 607 09 FAX +46 8 594 607 10 CELL +46 73 80 444 88 magnus.karlsson(a)lsi.com

11 years, 9 months

X11 crash on Cotton Candy

by Daniel Barker

I couldn't find a Cotton Candy-specific forum. Perhaps someone here will have advice. My apologies if I'm off-topic. I'm using Linaro on the FXI Cotton Candy. At least every few hours, it experiences an X server crash, which logs me out. Here is an example syslog message from the time of the crash: Nov 20 08:27:46 linaro-ubuntu-desktop gnome-session[3350]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 A brief search online suggests this may be a problem with the video driver. But I'm not sure. I will be very glad of any assistance. The crash is intermittent and difficult to reproduce. It seems to happen when I'm 'doing something', e.g. opening a new window, clicking a link or scrolling in Firefox, resizing a window, or viewing a photo attached to email. It does not seem to crash when the machine is idle. I'm running Linaro (Ubuntu-beta-20130309.zip from FXI's Web site), which I reinstalled earlier this week then did 'apt-get update' and 'apt-get upgrade', and configured in various simple ways (e.g. software firewall, wireless networks, software installations using apt). The X server crash has happened before and after the reinstallation. Without a swap file, there were some out of memory problems. I added a swapfile, which removed the out of memory problems. The X server still crashes. I've also emailed FXI support but have not yet heard. Thank you very much, in advance, Daniel Daniel Barker http://biology.st-andrews.ac.uk/staff/db60 The University of St Andrews is a charity registered in Scotland : No SC013532

11 years, 9 months

one exception about "aplay" on ARM64

by Nenghua Cao

Hi, expert: Recently, I encounter a tricky issue when using "aplay" to playback music on arm64 core, but "aplay" application and "alsa-lib" are 32 bit version. The exception happens and it results in "aplay" segment fault. I tried to root cause it thought adding some logs, but I don't catch it. Any suggestion will be appreciated! Thanks! 1. Aplay will call the "writei" function in alsa-lib. This function is used to transfer audio sample from user space to kernel space. It will be called many times. This issue maybe happened when calling this function at the first time. Or it happened at the second/third time. static snd_pcm_sframes_t snd_pcm_hw_writei(snd_pcm_t *pcm, const void *buffer, snd_pcm_uframes_t size) { printf("writei++\n"); /*my log: this log is printed out*/ err = ioctl(fd, SNDRV_PCM_IOCTL_WRITEI_FRAMES, &xferi); printf("writei--, err=0x%x\n", err); /*my log: this log isn't printed out when issue happened*/ } 2. So the ioctl will trap into kernel function. static long snd_pcm_ioctl_compat(struct file *file, unsigned int cmd, unsigned long arg) { case SNDRV_PCM_IOCTL_WRITEI_FRAMES32: printk("======snd_pcm_ioctl_compat11\n"); return snd_pcm_ioctl_xferi_compat(substream, SNDRV_PCM_STREAM_PLAYBACK, argp); /*I checked this function, and it is retuned with the correct value*/ } 3. Exception happens. And the log is as the following. writei++ [ 39.752267] 832 (aplay) ======snd_pcm_ioctl_compat++++++++ [ 39.760480] 832 (aplay) ======snd_pcm_ioctl_compat11 [ 39.767334] 832 (aplay) ========snd_pcm_ioctl_xferi_compat++++ [ 39.899134] 832 (aplay) ========snd_pcm_ioctl_xferi_compat------ [ 39.907413] 832 (aplay) Bad mode in Error handler detected, code 0xbf000000 [ 39.916944] 832 (aplay) CPU: 0 PID: 832 Comm: aplay Not tainted 3.10.0+ #64 [ 39.926508] 832 (aplay) task: ffffffc000861380 ti: ffffffc019ff8000 task.ti: ffffffc019ff8000 [ 39.937823] 832 (aplay) PC is at 0xf747baec [ 39.943600] 832 (aplay) LR is at 0x0 [ 39.948736] 832 (aplay) pc : [<00000000f747baec>] lr : [<0000000000000000>] pstate: 60000010 [ 39.959785] 832 (aplay) sp : ffffffc019ff9ff0 [ 39.965819] x29: 0000000000000000 x28: 0000000000000000 [ 39.973168] x27: 0000000000000000 x26: 0000000000000000 [ 39.980522] x25: 0000000000000000 x24: 0000000000000000 [ 39.987861] x23: 0000000000000000 x22: 0000000000000000 [ 39.995212] x21: 0000000000000000 x20: 0000000000000000 [ 40.002560] x19: 0000000000000000 x18: 0000000000000000 [ 40.009882] x17: 0000000000000000 x16: 0000000000000000 [ 40.017132] x15: 0000000000000000 x14: 00000000f764e7a0 [ 40.024415] x13: 00000000ffc06b88 x12: 000000000001e2cc [ 40.031706] x11: 00000000ffc06bc4 x10: 000000000001e32c [ 40.039035] x9 : 000000000001e31c x8 : 0000000000000000 [ 40.046346] x7 : 0000000000000036 x6 : 000000000001e298 [ 40.053629] x5 : 0000000000580830 x4 : 00000000f76feffc [ 40.060943] x3 : 00000000ffc06ba0 x2 : 00000000ffc06ba0 [ 40.068288] x1 : 00000000400c4150 x0 : 0000000000000000 [ 40.075529] 832 (aplay) [ 40.079571] 832 (aplay) Bad mode in Synchronous Abort handler detected, code 0x86000007 [ 40.090335] 832 (aplay) CPU: 0 PID: 832 Comm: aplay Not tainted 3.10.0+ #64 [ 40.099783] 832 (aplay) task: ffffffc000861380 ti: ffffffc019ff8000 task.ti: ffffffc019ff8000 [ 40.110928] 832 (aplay) PC is at 0x0 [ 40.116025] 832 (aplay) LR is at 0x0 [ 40.121211] 832 (aplay) pc : [<0000000000000000>] lr : [<0000000000000000>] pstate: 800003c5 [ 40.132337] 832 (aplay) sp : ffffffc019ff9ed0 [ 40.138387] x29: 0000000000000000 x28: 0000000000000000 [ 40.145718] x27: 0000000000000000 x26: 0000000000000000 [ 40.153007] x25: 0000000000000000 x24: 0000000000000000 [ 40.160335] x23: 0000000060000010 x22: 00000000f747baec [ 40.167745] x21: ffffffc019ff9ff0 x20: 0000000000000000 [ 40.175117] x19: 0000000000000000 x18: 0000000000000000 [ 40.182421] x17: 0000000000000000 x16: 0000000000000000 [ 40.189693] x15: 0000000000000002 x14: 0000000000000082 [ 40.197060] x13: 0000000000000000 x12: 0000000000002090 [ 40.204380] x11: ffffffc000fb73f8 x10: 0000000000000030 [ 40.211699] x9 : ffffffc019ff9c60 x8 : ffffffc000590298 [ 40.219046] x7 : 0000000000000003 x6 : 0000000000000261 [ 40.226390] x5 : 0050000100000000 x4 : 0000000000000000 [ 40.233682] x3 : 0000000000000001 x2 : 0000000000000001 [ 40.241037] x1 : ffffffc019ff9de0 x0 : 0000000000000000 [ 40.248277] 832 (aplay) [ 40.252134] 832 (aplay) Internal error: Oops - bad mode: 0 [#1] PREEMPT [ 40.261235] 832 (aplay) CPU: 0 PID: 832 Comm: aplay Not tainted 3.10.0+ #64 [ 40.270649] 832 (aplay) task: ffffffc000861380 ti: ffffffc019ff8000 task.ti: ffffffc019ff8000 [ 40.281834] 832 (aplay) PC is at 0x0 [ 40.286856] 832 (aplay) LR is at 0x0 [ 40.292028] 832 (aplay) pc : [<0000000000000000>] lr : [<0000000000000000>] pstate: 800003c5 [ 40.303084] 832 (aplay) sp : ffffffc019ff9ed0 [ 40.309148] x29: 0000000000000000 x28: 0000000000000000 [ 40.316465] x27: 0000000000000000 x26: 0000000000000000 [ 40.323826] x25: 0000000000000000 x24: 0000000000000000 [ 40.331048] x23: 0000000060000010 x22: 00000000f747baec [ 40.338425] x21: ffffffc019ff9ff0 x20: 0000000000000000 [ 40.345726] x19: 0000000000000000 x18: 0000000000000000 [ 40.353023] x17: 0000000000000000 x16: 0000000000000000 [ 40.360327] x15: 0000000000000002 x14: 0000000000000082 [ 40.367670] x13: 0000000000000000 x12: 0000000000002090 [ 40.375078] x11: ffffffc000fb73f8 x10: 0000000000000030 [ 40.382440] x9 : ffffffc019ff9c60 x8 : ffffffc000590298 [ 40.389725] x7 : 0000000000000003 x6 : 0000000000000261 [ 40.396999] x5 : 0050000100000000 x4 : 0000000000000000 [ 40.404289] x3 : 0000000000000001 x2 : 0000000000000001 [ 40.411597] x1 : ffffffc019ff9de0 x0 : 0000000000000000 [ 40.418853] 832 (aplay) [ 40.422720] 832 (aplay) Process aplay (pid: 832, stack limit = 0xffffffc019ff8058) [ 40.432872] 832 (aplay) Stack: (0xffffffc019ff9ed0 to 0xffffffc019ffa000) [ 40.442304] 832 (aplay) 9ec0: 00000000 00000000 400c4150 00000000 [ 40.454976] 832 (aplay) 9ee0: ffc06ba0 00000000 ffc06ba0 00000000 f76feffc 00000000 00580830 00000000 [ 40.467667] 832 (aplay) 9f00: 0001e298 00000000 00000036 00000000 00000000 00000000 0001e31c 00000000 [ 40.480310] 832 (aplay) 9f20: 0001e32c 00000000 ffc06bc4 00000000 0001e2cc 00000000 ffc06b88 00000000 [ 40.492832] 832 (aplay) 9f40: f764e7a0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 40.505377] 832 (aplay) 9f60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 40.517829] 832 (aplay) 9f80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 40.530276] 832 (aplay) 9fa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 40.542804] 832 (aplay) 9fc0: 00000000 00000000 19ff9ff0 ffffffc0 f747baec 00000000 60000010 00000000 [ 40.555294] 832 (aplay) 9fe0: 00000004 00000000 00000036 00000000 00000000 00000000 00000000 00000000 [ 40.567276] 832 (aplay) Call trace: [ 40.572258] 832 (aplay) Code: bad PC value [ 40.578899] 832 (aplay) ---[ end trace 329143aae073dffd ]--- Segmentation fault [\u@\h: \W]\# BR nhcao

11 years, 9 months

Test Result Summary of Calendar Week 47, 2013, for Linaro Android Jellybean.

by Soumya Basak

Calendar Week 47 2013: Here is the test result summary for Linaro Android Jellybean image on following boards: 1) TI Panda 4430; 2) TI Panda 4460; 4) ARM Versatile Express A9; 5) Versatile Express LSK TC2; 1) TI Panda 4430 + Linaro Android Jellybean (Column: BJ) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 2) TI Panda 4460 + Linaro Android Jellybean (Column: BJ) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 3) ARM Versatile Express A9 + Linaro Android Jellybean (Column: BI) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 4) Versatile Express LSK TC2 + Linaro Android Jellybean (Column: H) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… please refer to the test result spreadsheet. Thank You. Best Regards Soumya Basak.

11 years, 9 months

Release Critical Test Result Summary of Calendar Week 46,2013 for Linaro Android Jellybean.

by Soumya Basak

Calendar Week 46 2013: Here is release critical test result summary for Linaro Android Jellybean image on following boards: 1) TI Panda 4430; 2) TI Panda 4460; 3) Galaxy Nexus; 4) ARM Versatile Express A9; 5) Versatile Express LSK TC2; 1) TI Panda 4430 + Linaro Android Jellybean (Column: BI) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 2) TI Panda 4460 + Linaro Android Jellybean (Column: BI) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 3) Galaxy Nexus + Linaro Android Jellybean (Column: M) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdFhhe… 4) ARM Versatile Express A9 + Linaro Android Jellybean (Column: BH) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 5) Versatile Express LSK TC2 + Linaro Android Jellybean (Column: G) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… please refer to the test result spreadsheet. Thank You. Best Regards Soumya Basak.

11 years, 10 months

Release Critical Test Result Summary of Calendar Week 46, 2013 for Linux Linaro ubuntu Raring.

by Botao Sun

Calendar Week 46 2013: Here is release critical test result summary for Linux Linaro ubuntu Raring image on following boards: 1) ARM Versatile Express A9; 2) Samsung Arndale; 3) TI Panda 4430; 4) TI Panda 4460; 1. ARM Versatile Express A9 + Linux Linaro Raring (Column AS): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… 2. Samsung Arndale + Linux Linaro Raring (Column AL): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS… 3. TI Panda 4430 + Linux Linaro Raring (Column AS): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… 4. TI Panda 4460 + Linux Linaro Raring (Column AS): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… For Linaro 13.10 monthly release test summary, please refer to attachment. Thank you. Best Regards Botao Sun

11 years, 10 months

[Query]: How to sync gmail contacts with thunderbird

by Viresh Kumar

Hi Guys, I was wondering if somebody has gone through an LDAP setup and has this stuff working? I found this page as well: https://support.mozillamessaging.com/en-US/kb/thunderbird-and-gmail/discuss… but its not working. Actually I am not able to ping ldap.gmail.com and so the problem.. Thanks in Advance. -- viresh

11 years, 10 months

Re: Running Linaro toolchain on ubuntu 13.10 x86_64

by Zhenqiang Chen

> From: Deepak Saxena <dsaxena(a)linaro.org> > Date: 12 November 2013 07:25 > Subject: Running Linaro toolchain on ubuntu 13.10 x86_64 > To: Linaro Dev <linaro-dev(a)lists.linaro.org> > > > I'm working on getting my new build system up and running and with > 13.10. Running any of our toolchain commands leads to "No such file or > directory". I'm guessing this has to with my system being x86_64 and > 13.10 no longer including ia32_libs package, but could be incorrect. Yip. This is due to lack of /lib/ld-linux.so.2 which is included in 32-bit libc. > If this is indeed the issue, my understanding is that I need to > manually install 32 bit versions of every library that's needed. Can > toolchain folks comment on this? Any possibility of getting 64 bit Yip. You have to manually install 32 bit versions of every library that's needed. > native binaries or just having a repository that we can install from > and thus auto-pull the dependent 32 bit libraries? We need support both 32-bit and 64-bit systems. Ubuntu is not the only Linux host we want to support. We also support Debian, Fedora, openSUSE and RHEL. Thanks! -Zhenqiang

11 years, 10 months

Cross compiling a package for aarch64 foundation model

by Anil Singhar

Hi, I am trying to cross compile a package wi the following steps. The build goes fine except that when I try to run the same on the foundation model it doesn't work. Here are all the steps in details: 1. Installed the linaro gcc and set up the environment as follows: ------------------------------------------------------------------------------------------------ export AARCH64_TOOLCHAIN=/home/anilss/Linaro/tools/gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux/bin export PATH=$PATH:$AARCH64_TOOLCHAIN export ARCH=aarch64 export CROSS_COMPILE=aarch64-linux-gnu- 2. Now on my build machine (x86_64 machine running linux), from source root of the package (i.e. GMP) I want to cross compile: anilss@anilss:~/Linaro/pkgs/gmp/cross_arm64/gmp-5.1.3-aarch64$./configure --build=coreisbr-unknown-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu anilss@anilss:~/Linaro/pkgs/gmp/cross_arm64/gmp-5.1.3-aarch64$make 3. Then On the foundation model, where the above source tree is mounted, I do: $ make check However this fails. Any ideas on what is going wrong..? Also is the triplet correct for host and foundation model (running oe linux)? Thanks and Regards, Anil

11 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev