Fabrice: That's probably a different error given that this lp seems to be with
x86 vmx flags.
Check your /var/log/libvirt/qemu/ on the host to see if there's a particular
error shown in the destination qemu after migration.
--
You received this bug notification because you are a member of Ubunt
same seems to happen on Fedora 32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
To manage notifications about this bug go to:
https://bugs.launchpad.net
I *think* it's the cf-protection that's adding the endbr32 instructions
that I spotted as being the failing instruction each time; but I don't
understand why they would be CPU type specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
That's getting more fun :-)
You could look at whether seabios's config works out hte same in the two
environments, or whether something makes use of new build flags - try looking
at the gcc lines that are invoked in the good/bad cases and see if they're
passing any options that the other doesn't
I think the one I was thinking of is 0723cc8a5558c94388db75ae1f4991314914edd3
which is in a 4.2.0 rc
and there was 2605188240f939fa9ae9353f53a0985620b34769 - but that's a
different crash to what you have.
So hmm.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The vmx things make me wonder about a fix Paolo did a while ago for
enabling inidivudal vmx features rather than vmx as a whole; but I
can't remember if that was a kernel or qemu fix.
One thing I notice, that may be a red-herring, all of the machine code
in the errors are 'f3 0f 1e fb' which is t
Dnaiel: That's a different problem; 'Bad config data: i=0x10 read: a1
device: 1 cmask: ff wmask: c0 w1cmask:0'; so should probably be a
separate bug.
I'd bet on this being the one fixed by
2bbadb08ce272d65e1f78621002008b07d1e0f03
--
You received this bug notification because you are a member of
lInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1769053/+sub
gt; dmi.modalias:
> dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
&g
* ChristianEhrhardt (1769...@bugs.launchpad.net) wrote:
> On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert > wrote:
>
> > * ChristianEhrhardt (1769...@bugs.launchpad.net) wrote:
> > > > Interesting; I thought this was supposed to work.
> > >
> > &
ard.version: A00
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9360
> dm
Ah right Dan, if you're seeing the 40 bits physical in the guest you
definitely need to try the flags I suggest in comment 6; host-phys-
bits=true should work for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Interesting; I thought this was supposed to work.
I know we (RH) have some downstream patches for >1TB RAM, but the last I'd
heard they weren't supposed to be necessary any more, except for compatibility
with old versions.
It's probably worth checking the guest view fo the CPUs physical address
Re Laszlo's comment #8 - it feels the opposite way around to lp 1715700
- in that I don't think downgrading OVMF helped; so perhaps something
else is going on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
just tested current head - 1eed33994e28d4a0437ba6e944bbc3ec5e4a29a0 -
seems to work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu 2.10
To
Looks good here, just retested:
here's teh top of my git:
f89f59fad5119f878aaedf711af90802ddcb99c7 nbd-client: avoid spurious
qio_channel_yield() re-entry
cf26039a2b50f078b4ad90b88eea5bb28971c0d8 block: Update open_flags after
->inactivate() callback
8ccc527d84ec9a5052cfae19edbc44abb5ac03ae mir
I need to recheck with that combo - I'd seen that error but only when
I'd commented out 'if (!blk->dev && !blk_name(blk)[0]) {' when
debugging earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
yes, seems to fix it for me.
Thanks Christian for filing this; we probably wouldn't have spotted it before
the release without it
(which the test Stefan has just added will hopefully cure!).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
OK, yeh that's the same symptom I saw - it's that final failure that
causes bdrv_inactivate_all to return a failure and fail the source
migration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
OK, Stefan posted a patch for that assert (see 'nbd-client: avoid spurious
qui_channel_yield() re-entry) so now I'm running with the following patch and
I'm seeing the bdrv_inactivate return a -1 for
drive-virtio-disk0
Christian: Could you see what your source says with this patch?
diff --git a
repeated the assert in #26:
Program received signal SIGABRT, Aborted.
0x7f02163005f7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) where
#0 0x7f02163005f7 in __GI_raise (sig=sig@entry=6)
The difference with the qemu_file_set_error is I'm looking on the source
- because what's happening is the source is erroring so closing the
socket, and so the error you're seeing on the destination is real - the
socket just EOF'd!
--
You received this bug notification because you are a member of
(4th try) breakpoint on qemu_file_set_error, it's bdrv_inactivate_all
that's returning the error.
(gdb) list
1155if (inactivate_disks) {
1156/* Inactivate before sending QEMU_VM_EOF so that the
1157 * bdrv_invalidate_cache_all() on the other end won't fail. */
1158
OK, 3rd try and I've hit the same behaviour as Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu 2.10
To manage notifications about this b
Hmm i just tried to reproduce this and hit (on the source):
main_channel_client_handle_migrate_connected: client 0x5607d785f610 connected:
0 seamless 0
qemu-system-x86_64: /root/qemu/io/channel.c:303: qio_channel_yield: Assertion
`!ioc->write_coroutine' failed.
2017-08-22 10:50:04.888+: shut
also, you might want to chase it a bit further down, I think we've got:
qemu-file-channel.c:channel_get_buffer
io/channel-socket.c or io/channel-file.c qio_channel_file_readv
it would be good to know what the readv/readmsg is actually
returning in the case where it's failing.
Dave
OK, so that looks like a real case of the migration stream failing and getting
an IO error; so the question is why:
a) Is the source qemu dieing first and closing the socket?
b) Is libvirt closing the socket for some reason
--
You received this bug notification because you are a member of Ub
oh yeh you want to tell gdb to ignore SIGUSR1, something like:
handle SIGUSR1 nostop noprint pass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu
The 'host doesn't support requested feature' is probably a red-herring in this
case
The fact it's failing with an IO error but nothing else suggests either:
a) it's something closing the socket between the two qemu's
b) The I/O error is from storage/NBD
Assuming it fails on precopy, I'd look
There seem to be 6 people+ hitting it -> marking confirmed
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643911
Title:
libvirt rando
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643911
Title:
libvirt randomly crashes on xenial nodes with "*** Error in
Ondergetekende: Physically is there *anything* different between the nodes in
your #33 that exhibited no errors and those that exhibited a lot? CPU
model/vendor, number of sockets, system vendor etc?
(I'm wondering about a synchronised/unsynchronised tsc type issue).
--
You received this bug
*** This bug is a duplicate of bug 811024 ***
https://bugs.launchpad.net/bugs/811024
** This bug has been marked a duplicate of bug 811024
ARM FTBFS (timeout)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
*** This bug is a duplicate of bug 745879 ***
https://bugs.launchpad.net/bugs/745879
** This bug has been marked a duplicate of bug 745879
haskell-src-exts version 1.9.6-1~ubuntu1 failed to build on armel (timeout)
--
You received this bug notification because you are a member of Ubuntu
B
*** This bug is a duplicate of bug 788140 ***
https://bugs.launchpad.net/bugs/788140
** This bug has been marked a duplicate of bug 788140
FTBFS on armel (timeout)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I can see the change to the snprintf in the sqlite3_3.7.7-2ubuntu2 source, and
it seems to have gone in through the sqlite change here:
http://www.sqlite.org/cgi/src/info/6d78a25ddce75f63581be60c34dbc75f34c243df
So marking as fix-released. (Not retested!)
Dave
** Changed in: sqlite3 (Ubuntu)
Given that this is a kernel issue, this just needs this test adding
somewhere.
Run 5000 times in a loop; if it always completes then it's OK.
Dave
** Changed in: linux-linaro (Ubuntu)
Assignee: Dr. David Alan Gilbert (davidgil-uk) => (unassigned)
--
You received this bug noti
Beware that ctypes may be broken in other ways on armhf as well; in
particular it uses libffi to do its binding and a while ago when I
looked I came to the conclusion it probably won't call variadic
functions correctly if they are passed FP values.
My post to the ctypes list:
http://permalink.gman
Reopening; still happening as of todays PP build:
https://launchpadlibrarian.net/83934300/buildlog_ubuntu-precise-
armel.linux_3.1.0-2.3_BUILDING.txt.gz
cd /build/buildd/linux-3.1.0/debian/build/tools/tools/perf && \
make HAVE_CPLUS_DEMANGLE=1 -j2
make[1]: Entering directory
`/b
Public bug reported:
(tools bzr r 456)
run -l-i-fetch-ui, select Versatile Express, Select stable tested software, and
open Advanced Options.
It shows Linaro Ubuntu Desktop.
Available releases show 11.07,11.08, 11.09 - no 11.10
Yet I can see:
http://releases.linaro.org/11.10/ubuntu/oneiric-imag
Public bug reported:
I tried to create an image for Overo with 11.10 using the bzr (rev 456)
and enabled swap; it failed with the following in the bottom of the log:
Creating SWAP File
Traceback (most recent call last):
File "/home/dg/linaro/tools/linaro-image-tools/linaro-media-create", line
Thanks to dmart for pointing at https://lkml.org/lkml/2011/9/28/534 as the
likely culprit;
seems to work in 3.1.0-1401-linaro-lt-omap
** Package changed: eglibc (Ubuntu) => linux-linaro (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "test routine"
https://bugs.launchpad.net/bugs/884676/+attachment/2581478/+files/pthreadtest.c
** Changed in: eglibc (Ubuntu)
Assignee: (unassigned) => Dr. David Alan Gilbert (davidgil-uk)
--
You received this bug notification because you are a mem
087e4 in thread_init ()
No symbol table info available.
#4 0x8694 in main ()
No symbol table info available.
(gdb) q
A debugging session is active.
Inferior 1 [process 2511] will be detached.
** Affects: eglibc (Ubuntu)
Importance: Undecided
Assignee: Dr. David Alan Gilbert (da
Public bug reported:
I've got a set of benchmarks that use clock_gettime like:
clock_gettime(CLOCK_REALTIME, &tbefore);
for(l=0;lhttps://bugs.launchpad.net/bugs/873453
Title:
odd timing behaviour on panda
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
That one is much more fun; running under gdb it fails at:
2031Mb allocated using slize size = 5*406Mb OK
2031Mb allocated using slize size = 4*507Mb OK
Couldn't allocate the heap: 2031Mb
slize size = 677Mb slize no= 2/3
I added debug to print the pointers:
Slize 2 @ 0x
Slize 1 @ 0x6a6130
This is an artefact of a different in where the libraries are mapped on
the two architectures.
On ARM we have;
executable
heap
< ~1GB
libs
< ~3GB
stack
So there isn't one big 2GB chunk to allocate.
On x86 they have:
I can confirm that 0.14.50-2011.06-0-0ubuntu1 gets further with that
patch; it does trip over a lot of set-but-not-used warnings converted
into errors that I had to comment out to get it to build in random other
bits of the code - some of which do look like real bugs.
The easiest thing would seem
Public bug reported:
Version: 0.15.50-2011.08-0ubuntu3 (also bzr rev 12866)
debian/binfmt/qemu-armeb has:
interpreter /usr/bin/qemu-arm-static
that should be
interpreter /usr/bin/qemu-armeb-static
This results in the error 'Invalid ELF image for this architecture' if
you run a big endian bin
Hi James T,
Yep it works in 11.08 - but 11.08 hasn't made it into Oneiric yet which is
how I tripped over this.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845696
Title:
linaro-fetch-imag
** Branch linked: lp:~davidgil-uk/ubuntu/oneiric/eglibc/fix-842258
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/842258
Title:
ARM strchr fails to convert c to char
To manage notifications about th
Hi Colin,
Thanks for that (very clear) report - I've just created a branch that appears
to do the trick:
https://code.launchpad.net/~davidgil-uk/ubuntu/oneiric/eglibc/fix-842258
and added you as a reviewer on it.
Dave
** Changed in: eglibc (Ubuntu)
Status: New => In Progress
--
You r
** Changed in: eglibc (Ubuntu)
Assignee: (unassigned) => Dr. David Alan Gilbert (davidgil-uk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/842258
Title:
ARM strchr fails to convert c to c
Looking at Qt's qglobal.h it looks like it defines qreal as float on ARM
(and a lot of non-x86)
In those scribus lines we have:
ymax = qMax(ymax, gp.y());
ymax is a qreal, gp is a Fpoint and gp.y is going to give a double.
Might get away with changing ymax to be a double, if the later qRound
This seems to work with current oneiric (gcc is 4.6.1-2ubuntu3 rather
than the 4.6.0-14ubuntu1 that this build happened with).
Richard thinks it's likely that this was fixed by the fixes for
PR rtl-optimization/48830, PR rtl-optimization/48808, PR
rtl-optimization/48792 that went in a couple o
gcc:
bin/bash ../../libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"wxsvg\"
-DPACKAGE_TARNAME=\"wxsvg\" -DPACKAGE_VERSION=\"1.0.10\"
-DPACKAGE_STRING=\"wxsvg\ 1.0.10\"
-DPACKAGE_BUGREPORT=\"wx-svg-us...@lists.sourceforge.net\" -DPACKAGE_URL=\"\"
-DPACKAGE=\"wxsvg\" -DVERSION=\"1.0.10\"
On 3.0.0-1001-linaro-omap in the hwpack_linaro-omap3-20110726-1 we still don't
have MUSB_HDRC configured
and also there are very few modules; the asix module which I need for my
ethernet module is missing.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Looking at test_conf.c:752 we see:
nih_io_select_fds (&nfds, &readfds, &writefds, &exceptfds);
nih_io_handle_fds (&readfds, &writefds, &exceptfds);
file = (ConfFile *)nih_hash_lookup (source->files, filename);
>>> TEST_EQ_P (file, NULL);
TEST_FREE (old_job);
The
make[3]: Entering directory `/build/buildd/libnih-1.0.3/nih'
/bin/bash: line 5: 24330 Segmentation fault ${dir}$tst
FAIL: test_alloc
/bin/bash: line 5: 24335 Segmentation fault ${dir}$tst
FAIL: test_string
/bin/bash: line 5: 24340 Segmentation fault ${dir}$tst
FAIL: test_list
/bin/ba
When fixed please check if it cures bug 791294
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791315
Title:
libnih version 1.0.3-4ubuntu1 failed to build on armel
--
ubuntu-bugs mailing list
ubuntu
Fails in a different test in my test environment (oneiric chroot on
panda):
Testing conf_source_reload() with job directory
...with new job directory
...with new file in directory (direct write)
...with modified job (direct write)
...with modified job (atomic rename)
...with deleted job
...with m
>From log:
PASS: test_initctl
/bin/bash: line 5: 17756 Segmentation fault ${dir}$tst
FAIL: test_utmp
/bin/bash: line 5: 17761 Segmentation fault ${dir}$tst
FAIL: test_sysv
Testing env_option()
...with first argument
...with further argument
PASS: test_telinit
** Summary changed:
- meshlab version 1.3.0a+dfsg1-2 failed to build on armel
+ [uses GL] meshlab version 1.3.0a+dfsg1-2 failed to build on armel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791252
First error doesn't look very ARM specific:
autoheader: error: AC_CONFIG_HEADERS not found in configure.in
configure.in:26: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.
*** This bug is a duplicate of bug 788253 ***
https://bugs.launchpad.net/bugs/788253
** This bug has been marked a duplicate of bug 788253
[armel] ld segs in elf32_arm_gc_sweep_hook while building dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: binutils
https://launchpadlibrarian.net/72358389/buildlog_ubuntu-oneiric-armel.dbus_1.4.8-3ubuntu4_FAILEDTOBUILD.txt.gz
shows a seg in ld when building dbus on oneiric; I can recreate this with
binutils2.21.51.20110421-6ubuntu1
a
*** This bug is a duplicate of bug 788140 ***
https://bugs.launchpad.net/bugs/788140
** This bug has been marked a duplicate of bug 788140
FTBFS on armel (timeout)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Note that this patch should not break any existing package; it provides
an extra API that some (currently broken on armhf and some other
platforms) packages should start to use. Getting the patch in provides
the API and gives us the opportunity to get the other packages fixed
during the O cycle.
libffi with the patch in comment #1
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739305
Title:
[armhf] libffi variadic support
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Hi Avik,
Interesting - when I tried my patch it didn't pass the test suite (as
described in comment 9) - which version of ltrace did you patch exactly?
Does the 3 line shell script in patch 9 also work for you?
Dave
--
You received this bug notification because you are a member of Ubuntu
Bu
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774175
Title:
apt segfaults on armel in oneiric
--
ubuntu-bugs mailing list
ubun
This goes away if I rebuild apt-utils; the backtrace that I get is very
similar to the bug 774175 problem with binutils.
Dave
** Package changed: python2.7 (Ubuntu) => binutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 774175 ***
https://bugs.launchpad.net/bugs/774175
** This bug has been marked a duplicate of bug 774175
apt segfaults on armel in oneiric
* You can subscribe to bug 774175 by following this link:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/774175/
*** This bug is a duplicate of bug 774175 ***
https://bugs.launchpad.net/bugs/774175
** This bug is no longer a duplicate of bug 745843
vtk version 5.4.2-8ubuntu4 failed to build on armel
** This bug has been marked a duplicate of bug 774175
apt segfaults on armel in oneiric
* You can s
*** This bug is a duplicate of bug 774175 ***
https://bugs.launchpad.net/bugs/774175
** This bug is no longer a duplicate of bug 745843
vtk version 5.4.2-8ubuntu4 failed to build on armel
** This bug has been marked a duplicate of bug 774175
apt segfaults on armel in oneiric
* You can s
Merged bug 745843 as a dupe of this one; tested that the natty proposed
binutils package fixes vtk's FTBFS.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774175
Title:
apt segfaults on armel i
** Changed in: python2.7 (Ubuntu)
Assignee: (unassigned) => Dr. David Alan Gilbert (davidgil-uk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784188
Title:
segv in libpython2.7 oneiric
the backtrace I get is the following and it is prior to main:
Program received signal SIGSEGV, Segmentation fault.
0x40330f92 in
std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) ()
from /usr/lib/arm-linux-gnueabi/libstdc++.so.6
(gdb) where
#0 0x40330f92 in
std::__detail
** Tags added: arm-porting-queue armel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784188
Title:
segv in libpython2.7 oneiric arm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
ok, not so fast, so while that works for simple single processes, it
fails three tests:
FAIL: sleep in
/discs/more/daveg/git/ltrace/testsuite/ltrace.minor/attach-process.ltrace for 0
times, should be 1
FAIL: ^[0-9]* puts in
/discs/more/daveg/git/ltrace/testsuite/ltrace.minor/trace-exec.ltrace f
Oh, that patch is against git rev
4649a4cbb3bd6bc516c093adefa5dc7da8141b92 which still seems to be head-
of-tree.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771805
Title:
[armel] ltrace han
Interesting, well with that in hand the following patch seems to work OK;
I can see the MIPS sysdep has a separate implementation of
set_instruction_pointer
that explicitly talks about avoiding PTRACE_SINGLESTEP but it's only MIPS that
does that so far.
Dave
--- a/sysdeps/linux-gnu/trace.c
+++
Well we originally found this in a Natty ftbfs in bug 745843 (vtk), so
yes it breaks something - whether it breaks anything important however
is a different matter; it's a bit of a timebomb - it's a case of a
branch landing on a particular boundary under certain conditions and you
never know what o
This should be fixed by Richard's patch here:
http://sourceware.org/ml/binutils/2011-04/msg00177.html
It's probably worth pulling it in relatively quickly since this bug
could trigger on anything else.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, I think I've got it - it certainly smells like a linkerism but I
didn't want to blame it until I actually found the bad code, but I
believe it's another instance of bug 745843 - a problem with the fixup
for the cortex-a8 branch erratum:
In the bad build we have:
00021fe0 <_GLOBAL__sub_I_netrc
Compiling with -O1 -finline-small-functions -fpeephole2 -freorder-
functions -fschedule-insns fails, but removing the -freorder-functions
works.
The only difference in the assembler files produces is a set of section
directives:
diff error.S.noreorder error-bad.S
503a504
> .section
Building with
-O1 works
-O1 -finline-small-functions -fpeephole2 -freorder-functions -fschedule-insns
failsRemoving any of these options and it works.
-O2 fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Observation (which may or may not be relevant):
It doesn't seem to get anywhere near main or libc startup (gdb break on main
or __start or anything like that just doesn't stop).
Break'ing on _GLOBAL__sub_I_error.cc does stop and is an initialisation
routine from the error.cc which is known to b
Indeed I've been using latrace, but I have a different selection of more
subtle bugs with that.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771805
Title:
[armel] ltrace hangs
--
ubuntu-bug
Still broken on 1.2.2-0ubuntu1:
https://launchpadlibrarian.net/68809918/buildlog_ubuntu-natty-
armel.kdevelopphp_1.2.2-0ubuntu1_FAILEDTOBUILD.txt.gz
The first odd error seems to be:
dh build --parallel --list-missing --with kde
dh_testdir -O--parallel -O--list-missing
dh_auto_configure --b
Public bug reported:
Binary package hint: ltrace
On armel ltrace just hangs:
ltrace /bin/ls
signal(55381, 0x0001
ltrace: 0.5.3-2.1ubuntu1
kernel: 2.6.38-1207-omap4 #10-Ubuntu
This is running on a panda board.
Dave
** Affects: ltrace (Ubuntu)
Importance: Unde
It stops on my panda in a cc1 using >400MB of RAM and at that point it's
getting ~1% cpu and swapping.
I can see on x86 the peak (later on in the build) is over 600MB - so we
need to sit back and wait for build boxes with more RAM.
** Changed in: washngo (Ubuntu)
Status: New => Invalid
-
Setting as invalid and we can just sit back and wait for the amount of
RAM to catch up.
Dave
** Changed in: ants (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7
this file needs ~640MB of RAM and 3-4 mins on a core2 x86; I think it's
just swapping itself to death on the ARM; it stands a chance maybe on a
panda with all its RAM.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This test case fails with -O1 but works with -fno-shrink-wrap and seems
to be the same failure pattern.
** Attachment added: "shrink wrap error case"
https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/758082/+attachment/2024821/+files/shrinkwraperr.c
--
You received this bug notification
Thanks to Ramana for suggesting -fno-shrink-wrap which does indeed fix it.
(L153 is an early exit).
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/758082
Title:
[armel] segfaults in make check
This is from a -O1 of syntax.c - note how it stamps on r2 as a temp
which is the 1st variadic argument before it gets to stack the original.
.global syntax_error < void syntax_error(struct info *info, const
char *format, ...) {
.thumb
.thumb_func
.type syn
Just poking about, it looks like just recompiling syntax.c with -O0 gets it
working.
(indeed compiling it with -O1 makes it fail more tests that -O2).
It's a whole chain of passing va_args down throuhg about 5 different
levels of printf type thing.
Dave
--
You received this bug notification be
MPI makes my heads hurt;
OK - some other observations:
* petsc has a dependency on libhdf5-mpi-dev
* libhdf5-mpi-dev is a meta that is supposed to get the right libhdf5 for the
platform mpi defaults but actually ends up depending on
libhdf5-openmpi-dev, mpi-default-dev
whic
I suspect this isn't ARM specific exactly, but it's specific to those
platforms (i.e. ARM) that use lam as the default mpi implementation
rather than OpenMPI.
If I add a -llam to the configure test case that fails then the link
succeeds.
Dave
--
You received this bug notification because you ar
1 - 100 of 148 matches
Mail list logo
