Bug#787203: /lib64/ld-linux-x86-64.so.2: /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not defined w/ kernel 4.0 only
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-amd644.0.2-1
libc62.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=0x7f00
(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-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787203: /lib64/ld-linux-x86-64.so.2: /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not defined w/ kernel 4.0 only
On 06/15/2015 05:58 AM, Aurelien Jarno wrote: On 2015-05-29 12:45, Zack Weinberg wrote: ... 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=0x7f00 (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 ... 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? No error messages, and I already tried force-regenerating the initramfs (update-initramfs -k all -u) which succeeded for both installed kernels, without complaint. I will check whether there is indeed enough disk space later today, but I'm almost certain this isn't it. zw signature.asc Description: OpenPGP digital signature
Bug#787203: /lib64/ld-linux-x86-64.so.2: /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not defined w/ kernel 4.0 only
On 2015-06-15 09:55, Zack Weinberg wrote: On 06/15/2015 05:58 AM, Aurelien Jarno wrote: On 2015-05-29 12:45, Zack Weinberg wrote: ... 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=0x7f00 (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 ... 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? No error messages, and I already tried force-regenerating the initramfs (update-initramfs -k all -u) which succeeded for both installed kernels, without complaint. I will check whether there is indeed enough disk space later today, but I'm almost certain this isn't it. Ok. Then maybe you can try to unpack the initramfs to see what is the problem. Or share the file so that I can try to reproduce the issue here. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Bug#787203: /lib64/ld-linux-x86-64.so.2: /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not defined w/ kernel 4.0 only
On 2015-06-15 16:03, Aurelien Jarno wrote: On 2015-06-15 09:55, Zack Weinberg wrote: On 06/15/2015 05:58 AM, Aurelien Jarno wrote: On 2015-05-29 12:45, Zack Weinberg wrote: ... 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=0x7f00 (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 ... 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? No error messages, and I already tried force-regenerating the initramfs (update-initramfs -k all -u) which succeeded for both installed kernels, without complaint. I will check whether there is indeed enough disk space later today, but I'm almost certain this isn't it. Ok. Then maybe you can try to unpack the initramfs to see what is the problem. Or share the file so that I can try to reproduce the issue here. OTOH the problem seems to appear after exiting the initramfs when executing /sbin/init from the root filesystem. Can you check where does the /sbin/init symlink point to on this machine? Also it might be worth checking you don't have another libc installation outside of /lib/x86_64-linux-gnu and maybe /lib/i386-linux-gnu (look for libc.so.6). -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Bug#787203: /lib64/ld-linux-x86-64.so.2: /sbin/init: relocation error: symbol rewind, version GLIBC_2.2.5 not defined w/ kernel 4.0 only
Small update: the problem is definitely not disk space in /boot, which has some 400MB free. However, I couldn't do any other testing because the machine is now showing symptoms of a severe hardware fault - freezes to the point of requiring a physical power cycle less than a minute after power-on (with kernel 3.16), subsequent boot doesn't even get out of the BIOS before doing the same thing. I doubt this bug was another symptom of the same problem because it was so very predictable, but I suppose kernel 4.0 might've been predictably allocating some critical piece of data to a page of RAM that no longer works, or like that. Anyway, I'll get back to this bug eventually but I will need to nail down the hardware fault first, and if I wind up having to replace the motherboard it's probable that that will perturb the bug out of manifesting :-/ zw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
