On 19.11.2013, at 20:49, G. Heim <heelgeh...@hotmail.com> wrote: > Thanks for your reply again. > > I tried to upgrade as follows and it failed. > 1. I changed the repository to > http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and > removed the old repositories) > 2. I did "zypper dup" > 3. then about 576 packages needed to be upgraded, etc > 4. it downloaded all these packages > 5. it installed 23 packages > 6. then it failed. > > This is the log ("rtas" is my hostname): > > ( 21/845) Installing: xbitmaps-1.1.1-9.1.1 > ...............................[done] > ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 > ....................[done] > ( 23/845) Installing: glibc-2.18-4.4.1 > ...................................[done] > Additional rpm output: > /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig > child terminated abnormally > warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115 > > ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 > ....................[error] > Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: > (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command > was killed by signal 4 (Illegal instruction). > > Abort, retry, ignore? [a/r/i] (a): r > ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 > ....................[error] > Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: > (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command > was killed by signal 4 (Illegal instruction). > > Abort, retry, ignore? [a/r/i] (a): a > Problem occured during or after installation or removal of packages: > Installation aborted by user > > Please see the above error message for a hint. > There are some running programs that use files deleted by recent upgrade. You > may wish to restart some of them. Run 'zypper ps' to list these programs. > rtas:~ # zypper ps > Check failed: > Executing 'lsof' failed (132). > rtas:~ # zypper dup > Illegal instruction > rtas:~ # > > Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC. That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though. Do you think you could just put a 13.1 rootfs into a chroot and call $ /chroot/lib/ld-linux.so.2 directly? If that works, try $ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls If any of the two commands give you an illegal instruction, you can then try to run it in gdb: $ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run It will tell you which instruction it stumbled over on. We can then debug on from that point. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
