Booting Fedora 19 on OMAP5432 uEVM board
by Chen Baozi
Hi all,
I have installed Fedora 19 rootfs on my OMAP5432 uEVM board and booted
successfully with a patched upstream kernel. Everything looks fine except
the following message when booting:
Starting Terminate Plymouth Boot Screen...
dm.c: 1701
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/lib/python2.7/site-packages/initial_setup/__main__.py", line 5, in <module>
from pyanaconda.users import Users
File "/usr/lib/python2.7/site-packages/pyanaconda/__init__.py", line 36, in <module>
from pyanaconda.bootloader import get_bootloader
File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 32, in <module>
from blivet.devicelibs import mdraid
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 68, in <module>
from devices import *
File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 105, in <module>
from devicelibs import dm
File "/usr/lib/python2.7/site-packages/blivet/devicelibs/dm.py", line 25, in <module>
import block
File "/usr/lib/python2.7/site-packages/block/__init__.py", line 23, in <module>
from device import MultiPath, RaidDev, RaidSet, BlockDev, DeviceMaps, \
File "/usr/lib/python2.7/site-packages/block/device.py", line 259, in <module>
class MPNameCache(_IUD):
File "/usr/lib/python2.7/site-packages/block/device.py", line 264, in MPNameCache
for map in _dm.maps():
MemoryError
[ 17.228284] usb 1-3: link qh8-0001/edcd9b80 start 2 [1/0 us]
[ 17.235653] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.703451] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 18.712073] smsc95xx 1-3:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
Although I don't think it is a big deal, is there anyone who could tell me
what problem it might be?
Thanks.
Chen Baozi
10 years, 8 months
Valgrind: unrecognised instruction
by Jerry James
Hello all,
I am trying to track down a problem with the frama-c package. It runs
normally on i386 and x86_64, but exits immediately with an unhandled
exception on arm. It is written in ocaml, which makes debugging
difficult. I tried running it under valgrind to see if I could get any
clues, but valgrind says:
disInstr(arm): unhandled instruction: 0xEEBA5BEF
cond=14(0xE) 27:20=235(0xEB) 4:4=0 3:0=15(0xF)
==23036== valgrind: Unrecognised instruction at address 0x4f2d30.
==23036== at 0x4F2D30: caml_adjust_gc_speed (in
/home/jamesjer/rpmbuild/BUILD/frama-c-Fluorine-20130601/bin/toplevel.opt)
A gdb disassembly of the containing function shows that instruction as:
0x004f2d30 <+128>: vcvt.f64.s32 d5, d5, #1
Is that a legal instruction? I'm wondering if I should file a bug against
valgrind for not recognizing the instruction, or whether something in the
toolchain is emitting an instruction that is not valid for all CPUs in the
class Fedora supports.
Thank you for any help you can provide.
--
Jerry James
http://www.jamezone.org/
10 years, 8 months
Fwd: KVM on Samsung Chromebook A15
by Jon
There is a HYP enabled u-boot floating around.
http://www.virtualopensystems.com/media/chromebook/nv_u-boot-snow.kpart
So far I've been unable to get it to boot Fedora, but others are welcome to try.
Here is the git for the above:
https://github.com/virtualopensystems/u-boot
They also have some documentation:
https://lists.cs.columbia.edu/pipermail/kvmarm/2013-July/006481.html
Regards,
-Jon Disnard
fas: parasense
irc: masta
On Wed, Aug 7, 2013 at 10:51 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> On Wed, Aug 7, 2013 at 4:47 PM, Adam Goode <adam(a)spicenitz.org> wrote:
>> Was there ever a resolution to this? I am happy to file a bug in the
>> chromium tracker to get this looked at, if needed.
>
> None that I'm aware of but if you could file a bug in the chromium
> tracker that would be fab.
>
> Peter
>
>> Adam
>>
>>
>> On Fri, Jul 5, 2013 at 12:16 PM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
>>> On Fri, Jul 05, 2013 at 11:30:01AM -0400, Jon Masters wrote:
>>>> On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
>>>> > On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
>>>> >> I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung
>>>> >> Chromebook featuring ARM Exynos dual core A15 processor.
>>>> >
>>>> > Sorry to slightly hijack this thread. I will try your remix later.
>>>> >
>>>> > Reading the comments on https://lwn.net/Articles/557132/#Comments
>>>> > it seems as if the news on KVM on the Chromebook is not good. It
>>>> > doesn't boot into HYP mode, and there's no way to make it boot into
>>>> > HYP mode, so KVM won't be supported. Is that right?
>>>>
>>>> That's roughly what I'd expect to be the case. There might be a signed
>>>> U-Boot someone has hacked that does enable HYP mode, but otherwise I
>>>> suspect you're out of luck. I'll ask around during Linaro Connect.
>>>
>>> I asked about this on #kvm-arm earlier today and got this long reply:
>>>
>>> 11:58 < rwmjones> I'm reading a comment here:
>>> 11:58 < rwmjones> https://lwn.net/Articles/557561/
>>> 11:58 < rwmjones> which suggests that KVM on the Samsung Chromebook 2012 (ARM A15 version) isn't possible because the
>>> bootloader doesn't boot into HYP mode
>>> 11:58 < rwmjones> is this true? if so is there a way around it?
>>> 11:59 < pm215> IIRC the bootloader gets control in secure-SVC
>>> 11:59 < pm215> it is from there possible to get to NS-HYP
>>> 11:59 < pm215> it's just that the stock bootloader doesn't do this before booting the kernel
>>> 11:59 < rwmjones> so what's involved in making it work?
>>> 11:59 < pm215> somebody needs to write some code and get it into the bootloader
>>> 12:00 < rwmjones> ok, and the bootloader can be replaced (next comment down suggests this requires soldering)?
>>> 12:01 < pm215> I believe this to be true, though I don't have a chromebook
>>> 12:01 < pm215> I think you get the google bootloader to chain boot some other bootloader which you do have control of, and then
>>> that can actually boot your os
>>> 12:02 < suihkulokki> or maybe we could just prepend some code in front of the kernel zimage that switches to HYP mode?
>>> 12:02 < pm215> nope
>>> 12:02 < suihkulokki> damn
>>> 12:02 < pm215> we spent quite a long time being very firm that the ABI here is "bootloader's job to get this right"
>>> 12:03 < pm215> there are some u-boot patches currently going through code review to do the go-to-hyp-mode thing properly for
>>> arndale
>>> 12:03 < pm215> hopefully if they get upstream it will be more straightforward to say "ok, I have $other-board and it needs to
>>> do this too"
>>> 12:05 < apritzel> which would require that the Chromebook u-boot support is upstream as well
>>> 12:05 < apritzel> AFAIK this is not the case currently
>>>
>>> [There's more of this, but that seems to cover the main points]
>>>
>>> Reading around this, it does seem as if it's possible to get from
>>> secure SVC to HYP (although not easy).
>>>
>>> Rich.
>>>
>>> --
>>> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
>>> virt-top is 'top' for virtual machines. Tiny program with many
>>> powerful monitoring features, net stats, disk stats, logging, etc.
>>> http://people.redhat.com/~rjones/virt-top
>>> _______________________________________________
>>> arm mailing list
>>> arm(a)lists.fedoraproject.org
>>> https://admin.fedoraproject.org/mailman/listinfo/arm
>> _______________________________________________
>> arm mailing list
>> arm(a)lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/arm
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
--
-Jon
--
-Jon
10 years, 8 months
ARM Getting Started Guide
by Zach Oglesby
I started working on moving some of the information from the ARM "Secret
Decoder Ring"[1] page into the ARM Getting Started Guide. Right now I have
everything up to the section "Currently Supported ARM Architecture". I was
going to work down to the section title "What is U-Boot", but I am not sure
if that should all be in Introduction.xml or not.
Jared or Pete, do either of you have a working outline for this yet? I
would like to see this document ready for F20.
(I am including the ARM list of this to solicit feedback as well)
[1]: https://fedoraproject.org/wiki/Architectures/ARM/Secret_Decoder_Ring
Zach
10 years, 8 months
Automatic AArch64 bootstrap daily update for August 22, 2013
by Brendan Conoboy
Number of candidate source rpms: 13606
Number of source rpms built in stage 4: 11952
Number of packages built in stage4 with aarch64 components: 5078
Currently building packages
ascii-design-1.0.2-1.fc19.src.rpm
chrony-1.29-1.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
gnustep-make-2.6.5-1.fc19.src.rpm
grisbi-0.8.9-3.fc19.src.rpm
grub2-2.00-23.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mate-session-manager-1.6.1-1.fc19.src.rpm
mate-text-editor-1.6.0-5.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
qtwebkit-2.3.2-1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
Packages building since previous report (which might be stuck or crashed)
ascii-design-1.0.2-1.fc19.src.rpm
chrony-1.29-1.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
gnustep-make-2.6.5-1.fc19.src.rpm
grisbi-0.8.9-3.fc19.src.rpm
grub2-2.00-23.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mate-session-manager-1.6.1-1.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
qtwebkit-2.3.2-1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
Total current build failure count: 707 failed
Build failures from unsatisfied dependencies: 442 failed-dep-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list.
Build failures after dependency resolution: 265 failed-build-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list.
Naive Top 25 dependency issues
269 ghc-Cabal-devel
206 nodejs-devel
161 kdelibs4-devel
154 kdelibs4-devel >= 4.10.5
77 kdelibs4-devel >= 4.10.4
76 libkdegames-devel >= 4.10.5
54 mingw32-gcc
47 erlang-rebar
44 mono-devel
44 R-devel >= 3.0.0
40 libkdegames-devel >= 4.10.4
26 valgrind-devel
25 mingw32-gcc-c++
24 openmpi-devel
22 ldc
21 octave-devel
20 prelink
20 gdal-devel
20 PyQt4-devel
19 qtwebkit-devel
19 kdelibs-devel
18 nautilus-devel
16 qt-webkit-devel
16 gtkglext-devel
15 netcdf-devel
Previously broken builds that are now fixed:
firewalld-0.3.4-1.fc19
gstreamer1-plugins-bad-free-1.0.9-1.fc19
gtkmathview-0.8.0-12.fc19
qsynth-0.3.7-1.fc19
valknut-0.4.9-8.fc19
znc-1.2-0.1.alpha1.fc19
Newly attempted builds that failed:
apmud-1.0.0-11.fc12
cpmtools-2.13-5.fc19
flush-0.9.12-5.fc19
libEMF-1.0.7-2.fc19
libyui-bindings-1.0.1-2.fc19
libyui-ncurses-2.43.9-3.fc19
ocaml-lablgl-20120306-5.fc19
postgresql-table_log-0.4.4-12.fc18
sugar-turtleart-182-1.fc19
svgalib-1.9.25-12.fc19
10 years, 8 months
Automatic AArch64 bootstrap daily update for August 21, 2013
by Brendan Conoboy
Number of candidate source rpms: 13606
Number of source rpms built in stage 4: 11950
Number of packages built in stage4 with aarch64 components: 5076
Currently building packages
apmud-1.0.0-11.fc12.src.rpm
ascii-design-1.0.2-1.fc19.src.rpm
chrony-1.29-1.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
gnustep-make-2.6.5-1.fc19.src.rpm
grisbi-0.8.9-3.fc19.src.rpm
grub2-2.00-23.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mate-session-manager-1.6.1-1.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
postgresql-9.2.4-7.fc19.src.rpm
printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
qtwebkit-2.3.2-1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
Packages building since previous report (which might be stuck or crashed)
ascii-design-1.0.2-1.fc19.src.rpm
chrony-1.29-1.fc19.src.rpm
community-mysql-5.5.32-2.fc19.src.rpm
dtc-1.4.0-1.fc19.src.rpm
equalx-0.6.0-1.fc19.src.rpm
gnustep-make-2.6.5-1.fc19.src.rpm
grisbi-0.8.9-3.fc19.src.rpm
java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm
libguac-0.7.0-5.fc19.src.rpm
libtommath-0.41-16.fc19.src.rpm
lpg-2.0.17-10.fc19.src.rpm
mate-session-manager-1.6.1-1.fc19.src.rpm
mesa-9.2-0.12.20130610.fc19.src.rpm
nyquist-3.04-7b.fc19.src.rpm
oat-1.6.0-7.fc19.src.rpm
pacemaker-1.1.9-3.fc19.src.rpm
postgresql-9.2.4-7.fc19.src.rpm
printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm
python-flask-whooshee-0.0.5-2.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qt-4.8.4-19.fc19.src.rpm
qt-4.8.4-19.x1.fc19.src.rpm
qtwebkit-2.3.2-1.fc19.src.rpm
sane-backends-1.0.23-11.fc19.src.rpm
teamgit-0.0.12-1.20130626.fc19.src.rpm
texlive-2013-0.1.20130608_r30832.fc19.src.rpm
xonotic-data-0.7.0-1.fc19.src.rpm
Total current build failure count: 703 failed
Build failures from unsatisfied dependencies: 455 failed-dep-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list.
Build failures after dependency resolution: 248 failed-build-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list.
Naive Top 25 dependency issues
445 ghc-Cabal-devel
245 kdelibs4-devel
214 nodejs-devel
154 kdelibs4-devel >= 4.10.5
142 kdelibs4-devel >= 4.10.4
82 erlang-rebar
76 libkdegames-devel >= 4.10.5
76 libkdegames-devel >= 4.10.4
74 R-devel >= 3.0.0
70 mono-devel
54 mingw32-gcc
37 octave-devel
36 valgrind-devel
33 kdelibs-devel
30 openmpi-devel
29 nautilus-devel
28 gdal-devel
27 ldc
27 gtkglext-devel
27 PyQt4-devel
26 prelink
25 netcdf-devel
24 qtwebkit-devel
24 mingw32-gcc-c++
24 kdebase-workspace-devel
Previously broken builds that are now fixed:
chinese-calendar-0.7.9-1.fc19
clutter-gtkmm-0.91.8-7.fc19
drupal7-context-3.0-0.6.beta7.fc19
gobby-0.4.12-11.fc19
qmmp-0.7.1-1.fc19
Newly attempted builds that failed:
boinc-client-7.0.65-1.git79b00ef.fc19
flamerobin-0.9.3-1.20130401snap.fc19
fossil-1.25-2.20130216000435.fc19
gluegen2-2.0-0.8.rc11.fc19
grubby-8.24-1.fc19
grubby-8.26-2.fc19
grubby-8.28-1.x1.fc19
httpd-itk-2.2.22-9.fc19
libopensync-plugin-opie-0.22-8.fc18
ocaml-ancient-0.9.0-11.fc19
olpc-powerd-108-2.fc19
rats-2.1-10.fc18
udis86-1.7.1-1.fc19
xulrunner-22.0-4.x1.fc19
10 years, 8 months
