Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Wed, Feb 22, 2017 at 12:06 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> Control: retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init
> Control: tag -1 moreinfo
>
> On Mon, 20 Feb 2017 04:00:03 +0000 lkcl <lkcl@lkcl.net> wrote:
>> Package: src:linux
>> Version: 4.9.6-3
>> Severity: important
>> Tags: upstream
>>
>> this is a very recent (skylake) very expensive laptop with an intel core i7
>> full report is here, with a link (at the bottom of the report) to
>> hardware info:
>> http://lkcl.net/reports/aorus_x3_plus_v6.html
>>
>> it includes some information not listed below in the usual automated
>> info-collection (below)
>>
>>
>> i cannot boot the 4.9.0 kernel because of a segfault on /sbin/init.
>> a screenshot is here:
>> http://hands.com/~lkcl/IMG_20170220_1127225_rewind.jpg
> [...]
>
> I see no segfault. I do see:
>
> "Failed to execute /init (Error -2)"
>
> That would be "file not found".
ah! i didn't see that - i focussed on the first error.
> Is this a standard initramfs built by
> initramfs-tools?
it is indeed. the only thing i've been forced to do is specify a
hard-coded list of modules because "all" gives an INSANE 200mybte
initramfs - something i've never encountered before and the only
reason it loaded so quickly is because this is an NVMe SSD with a
staggering 2500 Mbyte/sec read speed (yes, really - 2.5gbyte/sec!) - i
didn't feel comfortable with that so cut it down to "most", which
failed.... so i hard-coded a list after doing "lsmod" and that worked
fine. that's the *only* difference.
lkcl@fizzy:~$ dpkg -l | grep initramfs
ii initramfs-tools 0.127
all generic modular initramfs generator
(automation)
ii initramfs-tools-core 0.127
all generic modular initramfs generator (core
tools)
ii libklibc 2.0.4-9
amd64 minimal libc subset for use with initramfs
> Can you check whether /init and /bin/sh are included
> in it, using the "lsinitramfs" command?
root@fizzy:/boot# lsinitramfs initrd.img-4.9.0-1-amd64 | grep init
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
scripts/init-top
scripts/init-top/blacklist
scripts/init-top/all_generic_ide
scripts/init-top/udev
scripts/init-top/ORDER
scripts/init-top/keymap
bin/run-init
sbin/init
init
conf/initramfs.conf
root@fizzy:/boot# lsinitramfs initrd.img-4.9.0-1-amd64 | grep sh
bin/sha512sum
bin/sha1sum
bin/sh
bin/sha256sum
bin/ash
lib/modules/4.9.0-1-amd64/kernel/arch/x86/crypto/ghash-clmulni-intel.ko
lib/modules/4.9.0-1-amd64/kernel/drivers/md/dm-snapshot.ko
lib/modules/4.9.0-1-amd64/kernel/drivers/md/dm-region-hash.ko
lib/modules/4.9.0-1-amd64/kernel/drivers/pci/hotplug/shpchp.ko
hmmm, they are indeed. so we are left with the perplexing /
paradoxical interpretation that *trying* to run /init results in
that... oh wait: look at line 5: it says "Method parse/execution
failed"
i bet you that's related to the "failed to run /init". i'll do some
google searches on that and see what i can find.
l.
Reply to: