On Wed, Aug 17, 2011 at 12:18:38AM +0200, Émeric Maschino wrote: > Package: initramfs-tools > Version: 0.99 > Severity: grave > > As stated in this thread > http://lists.debian.org/debian-ia64/2011/08/msg00001.html, Debian > "Wheezy" Testing cannot be booted at all on IA-64 (current > linux-image-3.0.0-1-mckinley in Testing depends on initramfs-tools > 0.99, so initramfs-tools cannot be downgraded to previously working > 0.98.8). Hence severity set to grave. Last message displayed on > console is: > > [ 17.146492] Freeing unused kernel memory: 1024kB freed > Loading, please wait... > > And then, nothing. > > Regression has been bisected to commit > 8f8299d9ba017d2a5af853a52be37ee50c89fac2 (mkinitramfs: copy over on > build instead of using symlink tree) from maximilian attems, > 2011-02-21 (initramfs-tools v0.99 development cycle). > > Comparison of last good and first bad generated initrd.img ramdisks show that: > - good one has bin/busybox and bin/sh, bin/sh being a soft link on > bin/busybox and size of bin/busybox matching size of system > /bin/busybox (1320720 bytes) > - bad one has no bin/busybox, only bin/sh (executable, not a link) but > size (199144 bytes) doesn't match size of system /bin/busybox (1320720 > bytes). Indeed, analyzing hook-functions and hooks/busybox source > code, it's my understanding that bin/sh should be a copy of system > /bin/busybox and thus should have the same size, right? I don't know > where this 199144 bytes executable comes from.
does initramfs-tools boot with BUSYBOX=no in initramfs.conf? according to your aboves statement it might not as the shared klibc dash and not the static dash might end up in the initramfs? see ls /usr/lib/klibc/bin > Applying patch proposed in bug #628374 (initramfs-tools: Recent > changes to hooks break busybox in initrd) to revert changes on busybox > hook doesn't help. > > Simply reverting commit 8f8299d9ba017d2a5af853a52be37ee50c89fac2 from > initramfs-tools v0.99 source code doesn't help either as resulting > initramfs-tools binaries generate initrd.img failing to boot system > with kernel panic, probably because of > post-8f8299d9ba017d2a5af853a52be37ee50c89fac2 commits. > > The problem is still present in current initramfs-tools git repository. are you sure? there are easy test build around that fixes the busybox breakage: dpkg -l initramfs-tools | grep ^ii ii initramfs-tool 0.100~16.gbp8d generic modular initramfs generator relevant apt source line is: deb http://jenkins.grml.org/debian initramfs-tools main please test that one, thank you. -- maks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
