Hi Steve,
I'm not sure what I saw back then.
You are right, GDB is able to find the debug infos.
Sorry for the noise.
** Changed in: gdb (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: gdb
I'm facing issues when debugging into a glibc call on Natty. The ARM
version of the libc6 ddeb (libc6-dbgsym) put its files into
/usr/lib/debug/lib/arm-linux-gnueabi. The gdb (7.2-1ubuntu11) is
configured with prefix=/usr and doesn't know about the
I see a very similar issue even with -O0 when using GCC 4.5.2-8ubuntu1
on my ARM board.
Here is a simple test:
snip
$ cat test.c gcc -O0 -Wall -Winline test.c -o test.bin echo O0:
./test.bin gcc -O2 -Wall -Winline test.c -o test.bin echo O2:
./test.bin
#include stdio.h
static long
As shown above this bug makes it a bit difficult to obtain the thumb
marker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721531
Title:
[armel] gcc computes wrong address for main() at build time
Public bug reported:
The 2.6.38-1001-linaro-omap kernel reports unable to reserve pmu when
attempting to access hw counters using perf:
snip
$ uname -a
Linux panda 2.6.38-1001-linaro-omap #2-Ubuntu SMP Mon Mar 21 21:40:07 UTC
2011 armv7l armv7l armv7l GNU/Linux
$ sudo su -c echo -1
Is there any chance to put the workaround/patch into the Linaro omap4
kernel as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708883
Title:
Panda board shuts down during boot
--
ubuntu-bugs
I can also confirm that the 2.6.38-1000-linaro-omap kernel works on my
panda. I'm using the hwpack_linaro-
panda_20110303-0_armel_supported.tar.gz with the linaro-n-developer-
tar-20110303-0.tar.gz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When using the 2.6.38-1000-linaro-omap kernel the process hangs as the
open call never returns. Here is a small testcase:
#include sys/stat.h
#include fcntl.h
#include stdio.h
#include unistd.h
#include stdlib.h
int main (int argc, char **argv){
int fd;
fd =
I've got the Oops but only once. It looked very similar to what David
posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728565
Title:
open(/dev/ttyO2, O_RDONLY) never returns on the
I think this the issue has been fixed by #643171. I do not see this
testcase failing using a recent (e)glibc and GCC. Could anyone of the
original reporters check if it works for them? Please make sure that you
use at least glibc 2.12.1-0ubuntu11 and GCC 4.5.
--
You received this bug
I think this the issue has been fixed by #643171. I do not see this
testcase failing using a recent (e)glibc and GCC. Could anyone of the
original reporters check if it works for them? Please make sure that you
use at least glibc 2.12.1-0ubuntu11 and GCC 4.5.
--
You received this bug
Public bug reported:
Binary package hint: flash-kernel
When using flash-kernel with a recent Linaro kernel on an OMAP4 board
the subarch check fails because the kfile does not end with a '3' or '4'
- it's just named like this: vmlinuz-2.6.37-1002-linaro-omap. Since the
linaro-omap kernel
** Patch added: flash-kernel_linaro-omap.patch
https://bugs.launchpad.net/bugs/721147/+attachment/1857303/+files/flash-kernel_linaro-omap.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721147
** Branch linked: lp:~kwerner/flash-kernel/lp-721147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721147
Title:
flash-kernel subarch check fails with Linaro OMAP kernels
--
ubuntu-bugs mailing
I can reproduce the error on my board (every boot fails at the same
place) but the addresses change. The error occurs right before the OMAP
components are initialized (DSS, DISPC, DSI, DSI2). It doesn't matter if
I build the kernel myself or use a recent prebuild kernel from a hwpack
(e.g.
I had a quick look into the apr sources. Their locks/unix/proc_mutex.c can map
the proc_mutex functionality to various methods:
1) Posix sem implemenation (see mutex_posixsem_methods)
2) SysV sem implementation (see mutex_sysv_methods)
3) pthread implementation (see
I ran the testprocmutex test on a panda board using ubuntu natty alpha 2 and it
passed:
$ ./testall testprocmutex
testprocmutex : SUCCESS
All tests passed.
$ apt-cache show libc6 gcc|grep Version
Version: 4:4.5.1-1ubuntu3
Version: 2.12.1-0ubuntu16
--
You received this bug notification
I ran the apr testsuite (svn revision 1071306) several times and I
notice that the testlock:test_timeoutcond test fails sometimes because
the timer returned to late. Not sure sure if this is related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I had a quick look into the apr sources. Their locks/unix/proc_mutex.c can map
the proc_mutex functionality to various methods:
1) Posix sem implemenation (see mutex_posixsem_methods)
2) SysV sem implementation (see mutex_sysv_methods)
3) pthread implementation (see
I ran the testprocmutex test on a panda board using ubuntu natty alpha 2 and it
passed:
$ ./testall testprocmutex
testprocmutex : SUCCESS
All tests passed.
$ apt-cache show libc6 gcc|grep Version
Version: 4:4.5.1-1ubuntu3
Version: 2.12.1-0ubuntu16
--
You received this bug notification
I ran the apr testsuite (svn revision 1071306) several times and I
notice that the testlock:test_timeoutcond test fails sometimes because
the timer returned to late. Not sure sure if this is related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@warmcat
Your patch fixes the issue on my board. I've applied your patch to the linaro
natty kernel and the system stays alive.
kernel: http://git.linaro.org/gitweb?p=ubuntu/linux-linaro-
natty.git;a=commit;h=ab75502a50e83d38a2b7892ff81f63decf5fb363
--
You received this bug notification
@warmcat
Thanks for the LED heartbeat hint. I've added ledtrig-heartbeat to /etc/modules
and I see that the Status1-LED begins to flash during boot. When the system
dies (shortly after it gets to the bash prompt on my board) the LED stays off
and the CPU cools down. The board works fine as soon
The latest (20110214) Linaro headless snapshot plus corresponding hwpack
still powers down my pandaboard shortly after it gets to the bash boot.
As Paul said this seems to be independent of the attached devices (HDMI,
USB, Ethernet). To check if it's related to something that is started by
upstart
To check if it's x-loader/u-boot related I replaced the MLO and
u-boot.bin of the 20110214 Linaro snapshot with the files from the
working Ubuntu Natty alpha2 installation but that didn't change anything
- the board still goes off.
--
You received this bug notification because you are a member
@Aneesh
Thanks for looking into this. I can reproduce this bug on my A1 ES2.1 8-layer
750-2152-010(D) board. H ere are the details:
snip
$ for gpio in 171 101 182; do read gpio${gpio}
/sys/class/gpio/gpio${gpio}/value; done echo Revision: ${gpio171}
${gpio101} ${gpio182}
Revision: 0 1 1
I've tried various hwpacks and (headless) images and encountered exact
the same issue while the Ubuntu 10.10 image works flawlessly on this
board. In order to exclude faulty external components I used different
power supplies and several SD cards - also no difference. My next step
was to use a
With these two patches applied, the GCC trunk r167715 bootstrapped fine on the
vexpress:
* http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00915.html
(PR46040: crtstuff.c:308:26: error: '__DTOR_LIST__' undeclared)
* http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00402.html
(PR46667: libstdc++
The patch was accepted upstream and has been committed.
** Changed in: linaro-toolchain-misc
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643171
Title:
I just tried to compile r167352 from the GCC svn and encountered the
very same issue. Therefore I applied the patch from #46040. After
restricting the build to the C language only it finishes but I see the
same testsuite failures as Matthias described in comment #10.
In case C++ is enabled the
** Changed in: linaro-toolchain-misc
Status: Confirmed = In Progress
--
Use the __sync primitives in EGLIBC
https://bugs.launchpad.net/bugs/643171
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
31 matches
Mail list logo
