[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#884762: linux-image-3.16.0-4-amd64: Kernel panic on boot (rest_init / build_sched_domains) make system unbootable
To
:
884762@bugs.debian.org
Subject
: Bug#884762: linux-image-3.16.0-4-amd64: Kernel panic on boot (rest_init / build_sched_domains) make system unbootable
From
: Olivier Hanesse <
olivier.hanesse@gmail.com
>
Date
: Tue, 19 Dec 2017 15:21:14 +0100
Message-id
: <
[🔎]
CABx4GKqiPYO_FcfPjMHA=P_kGQM2usf0Acc5veZnhts2gpCuQQ@mail.gmail.com
>
Reply-to
: Olivier Hanesse <
olivier.hanesse@gmail.com
>,
884762@bugs.debian.org
References
: <0eaf62a1-0ac1-c1e1-feee-2ecd71b08711@d2france.fr>
Hello,
We got the same issue on Vmware with this specific kernel.
VMs with more than 12 vcpus (we got 12 cpus / socket) crashed at boot time.
Setting cpus to 12 is a workaround (if this can help people .. )
Regards
Reply to:
debian-kernel@lists.debian.org
Olivier Hanesse (on-list)
Olivier Hanesse (off-list)
Prev by Date:
Re: Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10
Next by Date:
Bug#883938: fixed in linux 3.16.51-3
Previous by thread:
Re: Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10
Next by thread:
Bug#884803: linux-image-4.13.0-1-686-pae: kernel traces output when using wifi (ath9k)
Index(es):
Date
Thread