Hi,
On Sun, Nov 05, 2017 at 01:09:10PM +0100, intrigeri wrote:
> Hi,
>
> Antonio Terceiro:
> > The workaround that works is using the setting in the container
> > configuration:
>
> > lxc.aa_profile = unconfined
>
> > with disables apparmor entirely.
>
> > I have just uploaded lxc 1:2.0.9-4
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
Been running linux-image-4.13.0-0.bpo.1-amd64 (4.13.13-1~bpo9+1) for a few days
now without incident. So it seems free from the bug as well.
--
John Eikenberry
[ j...@zhar.net - http://zhar.net ]
[ PGP public key @ http://zhar.net/jae_at_zhar_net.gpg ]
Can we also make sure that this bug gets fixed in the netboot kernel?
http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Cheers,
Phil
Package: src:linux
Version: 4.13.13-1
Dear Maintainer,
This problem isn't exactly new (several months, with various kernels), but I
mostly use ethernet so am usually not annoyed by it.
After connecting to wifi networks, and usually when there is network activity,
my terminals/consoles are
On Tue, 2017-12-19 at 12:09 -0600, Phil Kauffman wrote:
> Can we also make sure that this bug gets fixed in the netboot kernel?
>
> http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/cur
> rent/images/netboot/debian-installer/amd64/linux
The netboot kernel won't be updated until
6 matches
Mail list logo