Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 213245 Details for
Bug 297231
dev-util/catalyst fails to generate netboot image
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
dev-util/catalyst log
dump (text/plain), 12.87 KB, created by
Tiago Cunha (RETIRED)
on 2009-12-16 23:18:07 UTC
(
hide
)
Description:
dev-util/catalyst log
Filename:
MIME Type:
Creator:
Tiago Cunha (RETIRED)
Created:
2009-12-16 23:18:07 UTC
Size:
12.87 KB
patch
obsolete
>Catalyst, version 2.0.6.905 >Copyright 2003-2008 Gentoo Foundation >Copyright 2008 various authors >Distributed under the GNU General Public License version 2.1 > >Using default Catalyst configuration file, /etc/catalyst/catalyst.conf >Setting sharedir to config file value "/usr/lib/catalyst" >Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache" >Setting hash_function to config file value "crc32" >Setting storedir to config file value "/var/tmp/catalyst" >Setting portdir to config file value "/usr/portage" >Setting distdir to config file value "/usr/portage/distfiles" >Setting options to config file value "autoresume kerncache metadata_overlay pkgcache seedcache snapcache" >Autoresuming support enabled. >Kernel cache support enabled. >Package cache support enabled. >Seed cache support enabled. >Snapshot cache support enabled. >Use of metadata_overlay module for portage enabled. >Envscript support enabled. >Using target: netboot2 >Building natively for sparc >Source path set to /var/tmp/catalyst/builds/default/stage3-sparc64-20091214.tar.bz2 >Caching snapshot to /var/tmp/catalyst/snapshot_cache/20091214/ >The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-netboot2-sparc64-20091216/ >Location of the package cache is /var/tmp/catalyst/packages/default/netboot2-sparc64-20091216/ >Location of the kerncache is /var/tmp/catalyst/kerncache/default/netboot2-sparc64-20091216/ >Checking for processes running in chroot and killing them. >--- Running action sequence: unpack >Referenced SEEDCACHE does not appear to be a directory, trying to untar... >No Valid Resume point detected, cleaning up... >Removing AutoResume Points: ... >Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-netboot2-sparc64-20091216/ >Emptying directory /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ > >Starting tar extract from /var/tmp/catalyst/builds/default/stage3-sparc64-20091214.tar.bz2 >to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ (This may take some time) ... > >--- Running action sequence: unpack_snapshot >Cleaning up invalid snapshot cache at > /var/tmp/catalyst/snapshot_cache/20091214/ (This can take a long time)... >Unpacking portage tree (This can take a long time) ... >lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20091214/.catalyst_lock' >--- Running action sequence: config_profile_link >Configuring profile link... >--- Running action sequence: setup_confdir >Configuring /etc/portage... >--- Running action sequence: portage_overlay >--- Running action sequence: bind >--- Running action sequence: chroot_setup >Setting up chroot... > >Warning!!!! > Overriding certain env variables may cause catastrophic failure. > If your build fails look here first as the possible problem. > Catalyst assumes you know what you are doing when setting > these variables. > Catalyst Maintainers use VERY minimal envscripts if used at all > You have been warned > > >Warning!!! > The use of -* in netboot2/use will cause portage to ignore > package.use in the profile and portage_confdir. You've been warned! >--- Running action sequence: setup_environment >--- Running action sequence: build_packages >>>> Building packages ... >copying netboot2-pkg.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >Running netboot2-pkg.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ >>>> Regenerating /etc/ld.so.cache... >>>> Regenerating /etc/ld.so.cache... >emerge --quiet --usepkg --buildpkg --newuse dropbear e2fsprogs mdadm nano qla-fc-firmware sdparm util-linux >>>> Verifying ebuild manifests >>>> Starting parallel fetch >>>> Emerging (1 of 7) net-misc/dropbear-0.52 >>>> Installing (1 of 7) net-misc/dropbear-0.52 >>>> Recording net-misc/dropbear in "world" favorites file... >>>> Emerging (2 of 7) app-editors/nano-2.1.10 >>>> Installing (2 of 7) app-editors/nano-2.1.10 >>>> Recording app-editors/nano in "world" favorites file... >>>> Emerging (3 of 7) sys-block/qla-fc-firmware-20071207-r1 >>>> Installing (3 of 7) sys-block/qla-fc-firmware-20071207-r1 >>>> Recording sys-block/qla-fc-firmware in "world" favorites file... >>>> Emerging (4 of 7) sys-apps/sdparm-1.03 >>>> Installing (4 of 7) sys-apps/sdparm-1.03 >>>> Recording sys-apps/sdparm in "world" favorites file... >>>> Emerging (5 of 7) sys-apps/util-linux-2.16.1 >>>> Installing (5 of 7) sys-apps/util-linux-2.16.1 >>>> Emerging (6 of 7) sys-fs/e2fsprogs-1.41.9 >>>> Installing (6 of 7) sys-fs/e2fsprogs-1.41.9 >>>> Emerging (7 of 7) sys-fs/mdadm-3.0 >>>> Installing (7 of 7) sys-fs/mdadm-3.0 >>>> Recording sys-fs/mdadm in "world" favorites file... > > * Messages for package net-misc/dropbear-0.52: > > * Your configuration for net-misc/dropbear-0.52 has been saved in > * /etc/portage/savedconfig/net-misc/dropbear-0.52 for your editing pleasure. > * You can edit these files by hand and remerge this package with > * USE=savedconfig to customise the configuration. > * You can rename this file/directory to one of the following for > * its configuration to apply to multiple versions: > * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ > * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] > > * Messages for package sys-fs/e2fsprogs-1.41.9: > > > * Messages for package sys-fs/mdadm-3.0: > > * If using baselayout-2 and not relying on kernel auto-detect > * of your RAID devices, you need to add 'mdraid' to your 'boot' > * runlevel. Run the following command: > * rc-update add mdraid boot > * Regenerating GNU info directory index... > * Processed 74 info files. >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/chroot-functions.sh from the chroot >--- Running action sequence: root_overlay >--- Running action sequence: copy_files_to_image >>>> Preparing Image ... >copying netboot2-copyfile.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >Running netboot2-copyfile.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ >>>> Regenerating /etc/ld.so.cache... >>>> Regenerating /etc/ld.so.cache... >>>> Copying initramfs files to /tmp/image/ (in chroot) ... >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/chroot-functions.sh from the chroot >--- Running action sequence: setup_overlay >--- Running action sequence: build_kernel >copying pre-kmerge.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >Running pre-kmerge.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ >>>> Regenerating /etc/ld.so.cache... >emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel >>>> Verifying ebuild manifests >>>> Emerging (1 of 1) sys-kernel/genkernel-3.4.10.906 >>>> Installing (1 of 1) sys-kernel/genkernel-3.4.10.906 > > * Messages for package sys-kernel/genkernel-3.4.10.906: > > * Copying files to /var/cache/genkernel/src... > * Documentation is available in the genkernel manual page > * as well as the following URL: > * http://www.gentoo.org/doc/en/genkernel.xml > * GNU info directory index is up-to-date. >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/chroot-functions.sh from the chroot >copying kmerge.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >Running kmerge.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ >>>> Regenerating /etc/ld.so.cache... >Genkernel version 3.4.10.906 found ... continuing >emerge --quiet --nodeps --update --newuse gentoo-sources >>>> Verifying ebuild manifests >>>> Emerging (1 of 1) sys-kernel/gentoo-sources-2.6.31-r7 for /tmp/kerncache/gentoo/ >>>> Installing (1 of 1) sys-kernel/gentoo-sources-2.6.31-r7 to /tmp/kerncache/gentoo/ >>>> Recording sys-kernel/gentoo-sources in "world" favorites file... > > * Messages for package sys-kernel/gentoo-sources-2.6.31-r7 merged to /tmp/kerncache/gentoo/: > > * If you are upgrading from a previous kernel, you may be interested > * in the following document: > * - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml > * NOTE: Since 2.6.25 the kernel Makefile has changed in a way that > * you now need to do > * make CROSS_COMPILE=sparc64-unknown-linux-gnu- > * instead of just > * make > * to compile the kernel. For more information please browse to > * https://bugs.gentoo.org/show_bug.cgi?id=214765 > * GNU info directory index is up-to-date. >[32;01m*[32;01m Gentoo Linux Genkernel; Version 3.4.10.906[0m >[32;01m*[0m Running with options: --firmware-files=/lib/firmware/ql2200_fw.bin --makeopts=-j3 --cachedir=/tmp/kerncache/gentoo-genkernel_cache-20091216 --no-mountboot --kerneldir=/usr/src/linux --modulespackage=/tmp/kerncache/gentoo-modules-20091216.tar.bz2 --minkernpackage=/tmp/kerncache/gentoo-kernel-initrd-20091216.tar.bz2 all --kerncache=/tmp/kerncache/gentoo-kerncache-20091216.tar.bz2 --kernel-config=/var/tmp/gentoo.config --busybox-config=/tmp/busy-config --netboot --initramfs-overlay="/tmp/image/" > >[32;01m*[0;01m Linux Kernel [0;01m2.6.31-gentoo-r7[0m for [0;01msparc64[0m... >[32;01m*[0m kernel: >> Running mrproper... >[32;01m*[0m config: Using config from /var/tmp/gentoo.config >[32;01m*[0m Previous config backed up to .config.bak >[32;01m*[0m >> Running oldconfig... >[32;01m*[0m kernel: >> Cleaning... >[32;01m*[0m >> Compiling 2.6.31-gentoo-r7 vmlinux... >[32;01m*[0m >> Starting supplimental compile of 2.6.31-gentoo-r7: image... >[32;01m*[0m >> Compiling 2.6.31-gentoo-r7 modules... >[32;01m*[0m Copying config for successful build to /etc/kernels/kernel-config-sparc64-2.6.31-gentoo-r7 >[32;01m*[0m busybox: >> Applying patches... >[32;01m*[0m busybox: >> Configuring... >[32;01m*[0m busybox: >> Compiling... >[32;01m*[0m busybox: >> Copying to cache... >[32;01m*[0m initramfs: >> Initializing... >[32;01m*[0m >> Appending base_layout cpio data... >[32;01m*[0m >> Appending auxilary cpio data... >[32;01m*[0m >> Appending busybox cpio data... >[32;01m*[0m >> Appending modules cpio data... >[32;01m*[0m >> Appending firmware cpio data... >[32;01m*[0m >> Appending overlay cpio data... >[32;01m*[0m Creating kernel cache >[32;01m*[0m Creating minimal kernel package >[32;01m*[0m Creating modules package >[32;01m*[0m >[32;01m*[0m Kernel compiled successfully! >[32;01m*[0m >[32;01m*[0m Required Kernel Parameters: >[32;01m*[0m real_root=/dev/$ROOT >[32;01m*[0m >[32;01m*[0m Where $ROOT is the device node for your root partition as the >[32;01m*[0m one specified in /etc/fstab >[32;01m*[0m >[32;01m*[0m If you require Genkernel's hardware detection features; you MUST >[32;01m*[0m tell your bootloader to use the provided INITRAMFS file. Otherwise; >[32;01m*[0m substitute the root argument for the real_root argument if you are >[32;01m*[0m not planning to use the initramfs... > >[32;01m*[0m WARNING... WARNING... WARNING... >[32;01m*[0m Additional kernel cmdline arguments that *may* be required to boot properly... > >[32;01m*[0m Do NOT report kernel bugs as genkernel bugs unless your bug >[32;01m*[0m is about the default genkernel configuration... >[32;01m*[0m >[32;01m*[0m Make sure you have the latest genkernel before reporting bugs. >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/chroot-functions.sh from the chroot >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/busy-config from the chroot >copying post-kmerge.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/ >Running post-kmerge.sh in chroot /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/ > [32;01m*[0m Caching service dependencies ... >[A[134C [34;01m[ [32;01mok[34;01m ][0m >removing /var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/tmp/chroot-functions.sh from the chroot >--- Running action sequence: move_kernels >>>> Copying completed kernels to /var/tmp/catalyst/builds/default/netboot2-sparc64-20091216/ ... >PT 0 Entry: Loadable to 0x400000[0x525881] from 0x0[0x499c80] align 0x100000 >PT 1 Entry: Note >PT 2 Entry: unknown >PT 3 Entry: unknown > >Traceback (most recent call last): > File "modules/netboot2_target.py", line 113, in move_kernels > " final",env=self.env) > File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd > raise CatalystError,myexc >CatalystError >None > >!!! catalyst: Failed to move kernel images! > >Traceback (most recent call last): >File "/usr/lib/catalyst/catalyst", line 208, in build_target > mytarget.run() >File "modules/generic_stage_target.py", line 1260, in run > apply(getattr(self,x)) >File "modules/netboot2_target.py", line 117, in move_kernels > raise CatalystError,"Failed to move kernel images!" >CatalystError >!!! catalyst: Error encountered during run of target netboot2 >Catalyst aborting.... >lockfile does not exist '/var/tmp/catalyst/tmp/default/netboot2-sparc64-20091216/.catalyst_lock'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 297231
: 213245 |
213247