[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#814288: marked as done (Generates corrupt (?) initrd images)

Your message dated Fri, 22 Jul 2016 12:23:06 -0400
with message-id <2744ab28-8a74-0e11-7323-45255a0bec93@chrishowie.com>
and subject line Re: Bug#814288: Generates corrupt (?) initrd images
has caused the Debian Bug report #814288,
regarding Generates corrupt (?) initrd images
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
814288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814288
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initramfs-tools
Version: 0.120

I have a rather odd case where update-initramfs sometimes generates good
initrds and sometimes it does not.  I'm not sure if the bug lies here or
in the kernel, but after sinking hours into investigating this issues
I'm very confident there is a bug somewhere.  I figure I will start with
this package and see where we get.

Kernel info, for the record:

-----
Linux debian-workstation 3.16.0-4-amd64 #1 SMP Debian
3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux
-----

Every initrd generated on the target machine with "update-initramfs -k
all -u" causes a kernel panic on the next boot:

-----
Initramfs unpacking failed: no cpio magic
/bin/sh: error while loading shared libraries: libc.so.6: cannot open
shared object file: No such file or directory
(usual "attempted to kill init" flood)
-----

However, if I boot from the amd64-8.1.0 netinstall CD in rescue mode and
select the options that will chroot me into the root volume of the
target machine and run the same update-initramfs command there, then the
machine boots.

I captured an example of a working and a broken initrd.  If I extract
them (gunzip < $file | cpio -i -dv) and diff the two trees, only one
file reports as being different: /etc/boottime.kmap.gz .  If I gunzip
this file in both trees, diff reports no differences.

I am at a total loss to explain this behavior.  The same
update-initramfs / mkinitramfs are used to build both, since I am
chroot'd into the root volume when building from the rescue CD.  The
only different pieces are the running kernel, and various mounts (/dev,
/proc, etc.).  The same kernel is used to actually boot both generated
initrds.

Since the initrds are not small, I'm linking them instead of attaching them.

Working:
<http://static.chrishowie.com/files/initrd.img-3.16.0-4-amd64.working>

Broken:
<http://static.chrishowie.com/files/initrd.img-3.16.0-4-amd64.broken>

Thanks for your time,

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5

------------------------------------------------------------------------
                    IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On 02/10/2016 11:10 AM, Ben Hutchings wrote:
> On Tue, 2016-02-09 at 17:51 -0500, Christopher David Howie wrote:
>> Package: initramfs-tools
>> Version: 0.120
>>
>> I have a rather odd case where update-initramfs sometimes generates good
>> initrds and sometimes it does not.  I'm not sure if the bug lies here or
>> in the kernel, but after sinking hours into investigating this issues
>> I'm very confident there is a bug somewhere.  I figure I will start with
>> this package and see where we get.

Somewhere in the last few kernel upgrades, this problem disappeared for
me.  I'm not sure if that's because there was a bug that got fixed, or
if my kernel was subtly corrupted and an upgrade fixed it.  Either way,
this bug (or whatever it was) no longer applies to me.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5

------------------------------------------------------------------------
                    IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: