Re: Unbootable initramfs in Testing (was Re: Unbootable linux-image-2.6.39-2-mckinley)

[Émeric Maschino <emeric.maschino@gmail.com>]

Hi,

Regression bisected to commit 8f8299d9ba017d2a5af853a52be37ee50c89fac2
(mkinitramfs: copy over on
build instead of using symlink tree) during initramfs-tools 0.9
development cycle.

Current initramfs-tools in git repository is still broken.

Bug report filed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638068).

Cheers,

     Emeric

2011/8/7 Émeric Maschino <emeric.maschino@gmail.com>:
> Hi,
>
> Just to let you know that the culprit is definitely initramfs-tools 0.99.
>
> Indeed, my system successfully booted with
> linux-image-2.6.39-2-mckinley, but initrd.img had to be created with
> initramfs-tools < 0.99. So from e.g. a Squeeze environment, as
> linux-image-2.6.39-2-mckinley unlikely depends on initramfs-tools 0.99
> and thus cannot be downgraded :-(
>
> initramfs-tools failure can also be double-checked from a native
> Squeeze environment, that comes with initramfs-tools 0.98.8 and
> linux-image-2.6.32-5-mckinley. Backup your initrd.img and update to
> initramfs-tools 0.99 from Testing. initrd.img is regenerated and
> you'll end up with an unbootable system stalling at:
> [   17.146492] Freeing unused kernel memory: 1024kB freed
> Loading, please wait...
> Reverting to initramfs-tools 0.98.8 solves the problem.
>
> Is initramfs-tools still the way to create initrd.img on Debian? I
> remember that other tools were available in the past (yaird comes to
> memory). If initramfs-tools is still the correct utility, do I have to
> file a bug report? I can't find something similar with the currently
> open initramfs-tools issues, but I may be wrong.
>
> Cheers,
>
>    Émeric
>
>
> 2011/6/22 Émeric Maschino <emeric.maschino@gmail.com>:
>> Hi,
>>
>> Just to warn you that linux-image-2.6.39-2-mckinley in today's Debian
>> "Wheezy" Testing updates fails to boot my hp workstation zx6000.
>>
>> Same problem than a week ago:
>>
>>> It all started with hundreds of
>>>
>>> udevd[325]: unable to receive ctrl connection: Function not implemented
>>>
>>> at boot time.
>>>
>>> And eventually:
>>>
>>>
>>> then nothing.
>>
>> Cheers,
>>
>>     Émeric
>>
>