On 2015-05-29 12:45, Zack Weinberg wrote:
> Package: libc6
> Version: 2.19-18
> Severity: critical
> File: /lib64/ld-linux-x86-64.so.2
> Justification: breaks the whole system
>
> If I attempt to boot one of my computers with the combination of:
>
> linux-image-4.0.0-1-amd64 4.0.2-1
> libc6 2.19-18
> systemd{,-sysv} 215-18
> initramfs-tools 0.120
>
> it crashes immediately after "Running /scripts/init-bottom ... done." with
> the error messages
>
> /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not
> defined in file libc.so.6 with link time reference
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
>
> (I attach a photograph of the complete crash display.)
>
> Reverting to the previous kernel (linux-image-3.16.0-4-amd64,
> version 3.16.7-ckt9-3) allows a successful boot, which is bizarre.
> Equally bizarre is that this does *not* occur with the same combination
> of packages on a different computer -- there must be some hardware-specific
> issue. For that reason I have appended the output of the bug script for
> the *bootable* kernel (3.16) to this bug report.
>
> This could easily turn out to be an issue with any of the above packages;
> feel free to reassign as appropriate. I'm filing it against libc because
> the proximate cause is a dynamic linker failure.
I really doubt it's a libc issue. It looks like to me your initramfs is
corrupted. Did you get any error message when installing the
linux-image-4.0.0-1-amd64 package? Do you have enough disk space on your
/boot partition?
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
