[fedora-arm] createrepo hotfix deployed on ARM (affects all architectures)
Folks,
I tracked down the createrepo stalls to a fundamental bug in createrepo.
I have made the attached patch, a form of which will ultimately be
required for all Fedora architectures.
Currently deployed for production test on bahamas.
http://koji.fedoraproject.org/koji/taskinfo?taskID=4786005
Jon.
commit de9d6312e45d3283cae2ceffc11d50a45fe0dda7
Author: Jon Masters
Date: Thu Dec 13 04:37:27 2012 -0500
createrep: Fix pipe stalls caused by blocking IO in worker stdio monitoring
The existing logic in createrepo assumes that pipe-based IO of workers
is infinite without blocking. Unfortunately, neither of these are true.
Change the logic to have worker output collected during its run (rather
than after it has been terminated), and remove the blocking IO actions.
Incidentally improve interactive output of createrepo in the process.
Signed-off-by: Jon Masters
diff --git a/createrepo-fix-pipe-handling.patch b/createrepo-fix-pipe-handling.patch
new file mode 100644
index 000..6899c9e
--- /dev/null
+++ b/createrepo-fix-pipe-handling.patch
@@ -0,0 +1,42 @@
+diff -urNp createrepo-0.9.9_orig/createrepo/__init__.py createrepo-0.9.9/createrepo/__init__.py
+--- createrepo-0.9.9_orig/createrepo/__init__.py 2012-12-13 04:16:24.800994125 -0500
createrepo-0.9.9/createrepo/__init__.py 2012-12-13 04:21:02.365980802 -0500
+@@ -26,6 +26,7 @@ import tempfile
+ import stat
+ import fcntl
+ import subprocess
++import select
+
+ from yum import misc, Errors
+ from yum.repoMDObject import RepoMD, RepoData
+@@ -662,15 +663,22 @@ class MetaDataGenerator:
+ while gimmebreak != len(worker_jobs.keys()):
+ gimmebreak = 0
+ for (num,job) in worker_jobs.items():
++
++if job.poll() is None:
++readyio = select.select([job.stdout.fileno(), job.stderr.fileno()], [], [])
++
++if (job.stdout.fileno() in readyio[0]):
++line = job.stdout.readline()
++if line:
++self.callback.log('Worker %s: %s' % (num, line.rstrip()))
++if (job.stderr.fileno() in readyio[0]):
++line = job.stderr.readline()
++if line:
++self.callback.errorlog('Worker %s: %s' % (num, line.rstrip()))
++
+ if job.poll() is not None:
+ gimmebreak+=1
+-line = job.stdout.readline()
+-if line:
+-self.callback.log('Worker %s: %s' % (num, line.rstrip()))
+-line = job.stderr.readline()
+-if line:
+-self.callback.errorlog('Worker %s: %s' % (num, line.rstrip()))
+-
++
+ for (num, job) in worker_jobs.items():
+ if job.returncode != 0:
+ msg = "Worker exited with non-zero value: %s. Fatal." % job.returncode
+Binary files createrepo-0.9.9_orig/createrepo/.__init__.py.swp and createrepo-0.9.9/createrepo/.__init__.py.swp differ
diff --git a/createrepo.spec b/createrepo.spec
index 2a7e7e3..ba92a03 100644
--- a/createrepo.spec
+++ b/createrepo.spec
@@ -3,12 +3,13 @@
Summary: Creates a common metadata repository
Name: createrepo
Version: 0.9.9
-Release: 11%{?dist}
+Release: 11%{?dist}.jcm1
License: GPLv2
Group: System Environment/Base
Source: %{name}-%{version}.tar.gz
Patch0: createrepo-head.patch
Patch1: ten-changelog-limit.patch
+Patch2: createrepo-fix-pipe-handling.patch
URL: http://createrepo.baseurl.org/
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArchitectures: noarch
@@ -24,6 +25,7 @@ packages.
%setup -q
%patch0 -p1
%patch1 -p0
+%patch2 -p1
%build
@@ -47,6 +49,9 @@ rm -rf $RPM_BUILD_ROOT
%{python_sitelib}/createrepo
%changelog
+* Thu Dec 13 2012 Jon Masters - 0.9.9-11.jcm1
+- Fix pipe stalls caused by blocking IO in worker stdio monitoring
+
* Thu Feb 16 2012 James Antill - 0.9.9-11
- update to latest head
- fix for lots of workers and not many rpms.
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 17 v6hl First Compose Image
On Thu, 13 Dec 2012, Sean Omalley wrote: It is all good. I didn't expect it to be perfect by any means. :) I may have missed it. But how are you building these? I need the dev tools, at least enough to rebuild the kernel. ( I need to hardwire my wireless keyboard driver. It makes it less flaky...) Or can i just do it on the armv5 image with different flags? i don't have a cross compiler and such set up. (and if you have them build already, no sense in redoing it.) You can install extra v6hl packages that aren't in the image (see the first message of this thread) by running yum install -y --disablerepo=\* --enablerepo=fedora-rpfr packagename I pulled in gdm to get the graphical login working and gnome-terminal for a terminal, but dev packages are probably there as well. Note the kernel used by this image is the same kernel as the v5 image. Michael Young___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] arm F-18 Branched report: 20121213 changes
Compose started at Thu Dec 13 11:10:36 UTC 2012 Broken deps for arm -- [GMT-coastlines] GMT-coastlines-2.2.0-3.fc18.noarch requires GMT-common [PyKDE] PyKDE-3.16.6-10.fc18.armv5tel requires sip-api(8) >= 0:8.1 [PyQt] PyQt-3.18.1-12.fc18.armv5tel requires sip-api(8) >= 0:8.1 [PyQt4] PyQt4-4.9.4-5.fc18.armv5tel requires sip-api(8) >= 0:8.1 python3-PyQt4-4.9.4-5.fc18.armv5tel requires python3-sip-api(8) >= 0:8.1 [PyQwt] PyQwt-5.2.0-19.fc18.armv5tel requires sip-api(8) >= 0:8.1 [PyX] PyX-0.11.1-3.fc18.armv5tel requires libkpathsea.so.4 [aeolus-conductor] aeolus-all-0.10.6-2.fc18.noarch requires mongodb-server aeolus-all-0.10.6-2.fc18.noarch requires iwhd aeolus-all-0.10.6-2.fc18.noarch requires imagefactory-jeosconf-ec2-rhel aeolus-all-0.10.6-2.fc18.noarch requires imagefactory-jeosconf-ec2-fedora aeolus-all-0.10.6-2.fc18.noarch requires imagefactory [asterisk] asterisk-fax-10.0.0-2.fc18.1.armv5tel requires libtiff.so.3 asterisk-snmp-10.0.0-2.fc18.1.armv5tel requires perl(:MODULE_COMPAT_5.14.2) asterisk-snmp-10.0.0-2.fc18.1.armv5tel requires librpmio.so.2 asterisk-snmp-10.0.0-2.fc18.1.armv5tel requires librpm.so.2 [avogadro] avogadro-libs-1.0.3-11.fc18.armv5tel requires sip-api(8) >= 0:8.1 [bochs] bochs-2.6-1.fc18.armv5tel requires bochs-bios = 0:2.6-1.fc18 [bootconf] bootconf-1.4-6.fc18.noarch requires grub [calibre] calibre-0.9.6-2.fc18.armv5tel requires sip-api(8) >= 0:8.1 [calligra-l10n] calligra-l10n-2.5.3-1.fc18.noarch requires calligra-core >= 0:2.5.3 [cloud-init] cloud-init-0.7.1-1.fc18.noarch requires dmidecode [coccinella] coccinella-0.96.20-4.fc18.noarch requires iaxclient [condor-cloud] condor-cloud-0.1-5.fc18.noarch requires qemu-kvm >= 0:0.14 condor-cloud-0.1-5.fc18.noarch requires condor-vm-gahp >= 0:7.7.0 condor-cloud-node-0.1-5.fc18.noarch requires qemu-kvm >= 0:0.14 condor-cloud-node-0.1-5.fc18.noarch requires condor-vm-gahp >= 0:7.7.0 [condor-ec2-enhanced] condor-ec2-enhanced-1.3.1-1.fc18.noarch requires condor >= 0:7.4.4-0.9 [condor-ec2-enhanced-hooks] condor-ec2-enhanced-hooks-1.3.1-1.fc18.noarch requires condor >= 0:7.2.0-4 [condor-job-hooks] condor-job-hooks-1.5-6.fc18.noarch requires condor >= 0:7.0.2-4 [condor-low-latency] condor-low-latency-1.2-2.fc18.2.noarch requires condor >= 0:7.0.2-4 [condor-wallaby] condor-wallaby-client-5.0.3-1.fc18.noarch requires python-qmf >= 0:0.9.1073306 condor-wallaby-client-5.0.3-1.fc18.noarch requires condor >= 0:7.4.4-0.9 [cumin] cumin-0.1.5220-2.fc18.noarch requires python-qpid-qmf [dvisvgm] dvisvgm-1.0.12-1.fc18.armv5tel requires libkpathsea.so.4 [ekiga] ekiga-3.9.90-1.fc18.armv5tel requires libpt.so.2.10.7 ekiga-3.9.90-1.fc18.armv5tel requires libopal.so.3.10.7 [ember-media] ember-media-0.6.2.1-3.fc18.noarch requires ember < 0:0.6.3 ember-media-0.6.2.1-3.fc18.noarch requires ember >= 0:0.6.2 [empathy] empathy-3.6.2-1.fc18.armv5tel requires libtelepathy-logger.so.2 [evince] evince-dvi-3.6.1-1.fc18.armv5tel requires libkpathsea.so.4 [gdal] gdal-1.9.0-1.fc18.armv5tel requires libtiff.so.3 gdal-1.9.0-1.fc18.armv5tel requires libspatialite.so.2 gdal-1.9.0-1.fc18.armv5tel requires libpoppler.so.19 gdal-java-1.9.0-1.fc18.armv5tel requires libtiff.so.3 gdal-java-1.9.0-1.fc18.armv5tel requires libspatialite.so.2 gdal-java-1.9.0-1.fc18.armv5tel requires libpoppler.so.19 gdal-libs-1.9.0-1.fc18.armv5tel requires libtiff.so.3 gdal-libs-1.9.0-1.fc18.armv5tel requires libspatialite.so.2 gdal-libs-1.9.0-1.fc18.armv5tel requires libpoppler.so.19 gdal-perl-1.9.0-1.fc18.armv5tel requires perl(:MODULE_COMPAT_5.14.2) gdal-perl-1.9.0-1.fc18.armv5tel requires libtiff.so.3 gdal-perl-1.9.0-1.fc18.armv5tel requires libspatialite.so.2 gdal-perl-1.9.0-1.fc18.armv5tel requires libpoppler.so.19 gdal-ruby-1.9.0-1.fc18.armv5tel requires ruby(abi) = 0:1.9 gdal-ruby-1.9.0-1.fc18.armv5tel requires libtiff.so.3 gdal-ruby-1.9.0-1.fc18.armv5tel requires libspatialite.so.2 gdal-ruby-1.9.0-1.fc18.armv5tel requires libpoppler.so.19 [ghc-blaze-builder-conduit] ghc-blaze-builder-conduit-devel-0.4.0.2-3.fc18.armv5tel requires ghc-devel(transformers-0.2.2.0-f4e1b941e0825c00ee0acf24d73c8a87) ghc-blaze-builder-conduit-devel-0.4.0.2-3.fc18.armv5tel requires ghc-devel(conduit-0.4.2-5f88c11b8a186be06897e40ef93e7de5) [ghc-network-conduit] ghc-network-conduit-devel-0.4.0-1.fc17.armv5tel requires ghc-prof(transformers-0.2.2.0) = 0:657fc7647251d805ae3451204e506340 ghc-network-conduit-devel-0.4.0-1.fc17.armv5tel requires ghc-prof(network-2.3.0.5) = 0:34
[fedora-arm] nacl-gcc
All, I'm rebuilding things on F18, the good news is that the webrtc fixes are the same. Anyone know what the bootstrap variable in nacl-gcc.spec is for? If < 1 it pulls in nacl-newlib which, in turn, depends on nacl-gcc (and doesn't have a bootstrap variable / mode) Dave David Rusling, CTO Linaro 220, The Quorum Barnwell Rd Cambridge CB5 8RE Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] nacl-gcc
I suspect the bootstrap if set to 1 will use pre-built binaries in the source tarball to build the initial package set and then you turn it off and bump the release so that it will rebuild the fedora binaries using the fedora binaries. Peter On Thu, Dec 13, 2012 at 2:15 PM, David Rusling wrote: > All, > I'm rebuilding things on F18, the good news is that the webrtc fixes are the > same. Anyone know what the bootstrap variable in nacl-gcc.spec is for? > If < 1 it pulls in nacl-newlib which, in turn, depends on nacl-gcc (and > doesn't have a bootstrap variable / mode) > Dave > > > David Rusling, CTO > > Linaro > 220, The Quorum > Barnwell Rd > Cambridge > CB5 8RE > > Linaro.org │ Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog > > > > > > > > > > > ___ > arm mailing list > arm@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] nacl-gcc
Peter, yes, I thought that, but I can't find any reference to nacl-newlib in gcc-nacl... Dave On 13 Dec 2012, at 14:18, Peter Robinson wrote: > I suspect the bootstrap if set to 1 will use pre-built binaries in the > source tarball to build the initial package set and then you turn it > off and bump the release so that it will rebuild the fedora binaries > using the fedora binaries. > > Peter > > On Thu, Dec 13, 2012 at 2:15 PM, David Rusling > wrote: >> All, >> I'm rebuilding things on F18, the good news is that the webrtc fixes are the >> same. Anyone know what the bootstrap variable in nacl-gcc.spec is for? >> If < 1 it pulls in nacl-newlib which, in turn, depends on nacl-gcc (and >> doesn't have a bootstrap variable / mode) >> Dave >> >> >> David Rusling, CTO >> >> Linaro >> 220, The Quorum >> Barnwell Rd >> Cambridge >> CB5 8RE >> >> Linaro.org │ Open source software for ARM SoCs >> Follow Linaro: Facebook | Twitter | Blog >> >> >> >> >> >> >> >> >> >> >> ___ >> arm mailing list >> arm@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] F18 ARM Beta Test Candidate 2
There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images available for testing, including: PandaBoard, Trim Slice, Versatile Express (QEMU) and Kirkwood. Images can be downloaded from: http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/ Please read the release notes: http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/f18-beta-tc2-release-notes.txt for information on installing/testing these images. Please download and test any images you are interested in. A VFAD (Virtual Fedora Activity Day) will be scheduled later to officially validate the images. Thank you for testing, d.marlin ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
No Beagle? Or is blc doing them later today? Peter On Thu, Dec 13, 2012 at 3:36 PM, David A. Marlin wrote: > There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images > available for testing, including: PandaBoard, Trim Slice, Versatile Express > (QEMU) and Kirkwood. > > Images can be downloaded from: > > http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/ > > > Please read the release notes: > > > http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/f18-beta-tc2-release-notes.txt > > for information on installing/testing these images. > > Please download and test any images you are interested in. A VFAD (Virtual > Fedora Activity Day) will be scheduled later to officially validate the > images. > > > Thank you for testing, > > d.marlin > > ___ > arm mailing list > arm@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
On 12/13/2012 07:40 AM, Peter Robinson wrote: No Beagle? Or is blc doing them later today? It's unofficial, but try: http://scotland.proximity.on.ca/arm-nightlies/vault/tmp/beagle.img.bz2 I'm about to get on a plane but will resume beagle dev upon my return Monday. -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] createrepo hotfix deployed on ARM (affects all architectures)
On 12/13/2012 09:09 AM, James Antill wrote: > On Thu, 2012-12-13 at 04:44 -0500, Jon Masters wrote: >> Folks, >> >> I tracked down the createrepo stalls to a fundamental bug in createrepo. >> I have made the attached patch, a form of which will ultimately be >> required for all Fedora architectures. > > This has been re-written upstream by Zdeněk for similar reasons (and > should be in rawhide too IIRC) ... can you try that? Ah. There we go. When I look in rawhide I see there is some select going on there now. Well, great. I'm glad someone found that eventually. I don't think we should switch to the rawhide version (this is not in F18, and it should be, it's going to cause problems), but I am encouraged that my smaller hotfix is going to be sufficient for now, since it is even more obviously correct. I think we might be interested in upgrading, when a fix is pushed to F18 and F17, which should happen immediately. I hope PA Koji is running a fixed version of createrepo. It would also be nice if there were some way to get notified of this. Note, I didn't notice this because I checked out F18, and because I then looked to see if F19 had a higher version. "0.9.9" is the version I see in all of the branches. I (wrongly as it turns out) assumed that this might bump if such a change had happened. I don't mean to sound grumpy. I am incredibly annoyed - beyond livid really - but not with you, or anyone else individually. It's not personal. I'm just annoyed that I wasted all night and am now exhausted, tracking down something for which someone has a fix that should have been released already. Jon. ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
On Thu, Dec 13, 2012 at 8:36 AM, David A. Marlin wrote: > Please download and test any images you are interested in. A VFAD (Virtual > Fedora Activity Day) will be scheduled later to officially validate the > images. I have a package that is failing to build on F-18 ARM (but not F-17), so I grabbed the Versatile Express image to try to track down the problem. The very first boot attempt did this: [ OK ] Started udev Kernel Device Manager. [8.727567] systemd-udevd[96]: starting version 195 Starting dracut pre-trigger hook... [ OK ] Started dracut pre-trigger hook. Starting udev Coldplug all Devices... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot Screen... Starting dracut initqueue hook... [ 12.353831] amba mb:mmci: Driver mmci-pl18x requests probe deferral [ 12.413569] scsi0 : pata_platform [ 12.416519] ata1: PATA max PIO0 no IRQ, using PIO polling mmio cmd 0x1001a000 ctl 0x1001a100 [ 12.436697] amba mb:mmci: Driver mmci-pl18x requests probe deferral [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[142]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[142]: Warning: Could not boot. dracut-initqueue[142]: Warning: /dev/mmcblk0p3 does not exist Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. dracut:/# Regards, -- Jerry James http://www.jamezone.org/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
Hi, "David A. Marlin" writes: > There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images > available for testing, including: PandaBoard, Trim Slice, Versatile Express > (QEMU) and Kirkwood. Are there instructions for Kirkwood? In particular, what uboot commands/environment do I need to set up? The release notes don't mention kirkwood, and I was having trouble with the F17 on my Guruplug Server (not Plus) so figured I'd try F18 to see if it was better. Thanks, -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
On 12/13/2012 10:01 AM, Derek Atkins wrote: Hi, "David A. Marlin" writes: There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images available for testing, including: PandaBoard, Trim Slice, Versatile Express (QEMU) and Kirkwood. Are there instructions for Kirkwood? In particular, what uboot commands/environment do I need to set up? The release notes don't mention kirkwood, and I was having trouble with the F17 on my Guruplug Server (not Plus) so figured I'd try F18 to see if it was better. Jon Masters tested the first image (TC1) and posted some notes on it: http://lists.fedoraproject.org/pipermail/arm/2012-December/004609.html I guess we should add that to the release notes, unless we come up with a better approach. Please post if you have suggestions. Thanks, d.marlin === Thanks, -derek ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] createrepo hotfix deployed on ARM (affects all architectures)
On 12/13/2012 10:54 AM, Jon Masters wrote: > I don't think we should switch to the rawhide version (this is not in > F18, and it should be, it's going to cause problems), but I am > encouraged that my smaller hotfix is going to be sufficient for now, > since it is even more obviously correct. I think we might be interested > in upgrading, when a fix is pushed to F18 and F17, which should happen > immediately. I hope PA Koji is running a fixed version of createrepo. It > would also be nice if there were some way to get notified of this. I pulled down the RHEL6.3 and RHEL6.4 versions just now and see that a fix is in RHEL6.4. RHEL6.3 has an older version with different code. So, probably this isn't a problem for PA at the moment. Jon. ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Daily Koji Compare Stats
Thu Dec 13 09:05:01 EST 2012 f17-updates : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 2655 |0 | 334 |1 | 385 | 413 | http://142.204.133.82/jon/koji/kc.f17-updates.diff.html f18 : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 12072 |8 | 261 |3 | 285 | 327 | http://142.204.133.82/jon/koji/kc.f18.diff.html f18-updates-testing : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 2722 |1 | 258 |2 | 236 | 276 | http://142.204.133.82/jon/koji/kc.f18-updates-testing.diff.html f19 : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 10761 | 17 | 1646 |3 | 309 | 2816 | http://142.204.133.82/jon/koji/kc.f19.diff.html ARM Build Status Wiki: https://fedoraproject.org/wiki/Architectures/ARM https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide Thu Dec 13 11:22:24 EST 2012 ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
On 12/13/2012 09:58 AM, Jerry James wrote: On Thu, Dec 13, 2012 at 8:36 AM, David A. Marlin wrote: Please download and test any images you are interested in. A VFAD (Virtual Fedora Activity Day) will be scheduled later to officially validate the images. I have a package that is failing to build on F-18 ARM (but not F-17), so I grabbed the Versatile Express image to try to track down the problem. The very first boot attempt did this: [ OK ] Started udev Kernel Device Manager. [8.727567] systemd-udevd[96]: starting version 195 Starting dracut pre-trigger hook... [ OK ] Started dracut pre-trigger hook. Starting udev Coldplug all Devices... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot Screen... Starting dracut initqueue hook... [ 12.353831] amba mb:mmci: Driver mmci-pl18x requests probe deferral [ 12.413569] scsi0 : pata_platform [ 12.416519] ata1: PATA max PIO0 no IRQ, using PIO polling mmio cmd 0x1001a000 ctl 0x1001a100 [ 12.436697] amba mb:mmci: Driver mmci-pl18x requests probe deferral [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[142]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[142]: Warning: Could not boot. dracut-initqueue[142]: Warning: /dev/mmcblk0p3 does not exist Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. dracut:/# We are looking into this issue. d.marlin === Regards, -- Jerry James http://www.jamezone.org/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] nacl-gcc
On 12/13/2012 09:15 AM, David Rusling wrote:
> All,
> I'm rebuilding things on F18, the good news is that the webrtc fixes are
> the same. Anyone know what the bootstrap variable in nacl-gcc.spec is
> for? If < 1 it pulls in nacl-newlib which, in turn, depends on
> nacl-gcc (and doesn't have a bootstrap variable / mode)
Look in the spec, that's an RPM macro:
%if %{bootstrap}
--disable-threads \
--enable-languages="c" \
--without-headers \
CFLAGS_FOR_TARGET="-O2 -g" \
CXXFLAGS_FOR_TARGET="-O2 -g" \
%else
CFLAGS_FOR_TARGET="-O2 -g -mtls-use-call
-I/usr/x86_64-nacl/include/" \
CXXFLAGS_FOR_TARGET="-O2 -g -mtls-use-call
-I/usr/x86_64-nacl/include/" \
--enable-threads=nacl \
--enable-languages="c,c++,objc" \
--enable-tls \
--with-newlib \
%endif
Basically, at the very first bootstrap, we can't build nacl-gcc against
nacl-newlib (the optimal configuration, because newlib enables
threading), so we disable threading and build a minimal nacl-gcc for C
only. Then, build nacl-newlib. Then, flip %{bootstrap} off and rebuild
nacl-gcc.
~tom
==
Fedora Project
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
David, "David A. Marlin" writes: > There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images > available for testing, including: PandaBoard, Trim Slice, Versatile Express > (QEMU) and Kirkwood. > > Images can be downloaded from: > > http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/ I just tried the Kirkwood image and it didn't work because the 1st partition is EXT and not FAT. UBoot on my GuruPlug doesn't support that. Also note that I suspect I'm also running into a known kernel bug with the F17 release: https://bugzilla.kernel.org/show_bug.cgi?id=42680 Unfortunately I don't know if there is a workaround for this, especially considering that uImage-kirkwood reports that it is not compressed: /media/boot/uImage-kirkwood: u-boot legacy uImage, 3.4.2-3.fc17.armv5tel.kirkwood, Linux/ARM, OS Kernel Image (Not compressed), 3291832 bytes, Mon Jun 18 00:58:01 2012, Load Address: 0x8000, Entry Point: 0x8000, Header CRC: 0xCDB8004D, Data CRC: 0x6C6E299A Any ideas? -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F18 ARM Beta Test Candidate 2
Update your uBoot? http://loginroot.com/installing-uboot-to-guruplug-server-plus/ From: Derek Atkins To: David A. Marlin Cc: Fedora ARM Sent: Thursday, December 13, 2012 5:02 PM Subject: Re: [fedora-arm] F18 ARM Beta Test Candidate 2 David, "David A. Marlin" writes: > There are a number of pre-created F18 ARM Beta TC2 (Test Candidate 2) images > available for testing, including: PandaBoard, Trim Slice, Versatile Express > (QEMU) and Kirkwood. > > Images can be downloaded from: > > http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc2/ I just tried the Kirkwood image and it didn't work because the 1st partition is EXT and not FAT. UBoot on my GuruPlug doesn't support that. Also note that I suspect I'm also running into a known kernel bug with the F17 release: https://bugzilla.kernel.org/show_bug.cgi?id=42680 Unfortunately I don't know if there is a workaround for this, especially considering that uImage-kirkwood reports that it is not compressed: /media/boot/uImage-kirkwood: u-boot legacy uImage, 3.4.2-3.fc17.armv5tel.kirkwood, Linux/ARM, OS Kernel Image (Not compressed), 3291832 bytes, Mon Jun 18 00:58:01 2012, Load Address: 0x8000, Entry Point: 0x8000, Header CRC: 0xCDB8004D, Data CRC: 0x6C6E299A Any ideas? -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warl...@mit.edu PGP key available ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
