Bug#822936: Occurs on Stretch

2017-11-05 Thread Jiann-Ming Su
# uname -v #1 SMP Debian 4.9.51-1 (2017-09-28) [256204.725417] INFO: rcu_sched self-detected stall on CPU [256204.725450] INFO: rcu_sched detected stalls on CPUs/tasks: [256204.725473] 0-...: (2 GPs behind) idle=52b/2/0 softirq=1717403/1717404 fqs=0 [256204.725477] [256204.725485] (detected by

Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

2017-11-05 Thread intrigeri
Ben Hutchings: > Yes, I now understand this. I'll add a Recommends: apparmor for the > next upload so this broken configuration is less likely to occur. Thanks! Cheers, -- intrigeri

Processed: limit source to linux, tagging 880441

2017-11-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 880441 + pending Bug #880441 [src:linux] linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other

Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

2017-11-05 Thread Ben Hutchings
On Sun, 2017-11-05 at 12:21 +0100, intrigeri wrote: > Hi, > > Ben Hutchings: > > My understanding was that enabling AppArmor shouldn't do very much > > until a policy is loaded (which it won't be if you don't install the > > userland tools). As you've found, that isn't entirely correct. > > Let

Re: [pkg-apparmor] Bug#880502: lxc: cannot start container with kernel 4.13.10

2017-11-05 Thread intrigeri
Hi! Sorry for the delay, I didn't expect AppArmor to be enabled in the kernel a week ago (I thought I would coordinate this with Ben) and I was busy with the Reproducible Builds summit this week. Thanks Felix & Antonio for being on top of things. I'm glad the immediate RC issue was fixed. Felix

Re: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10

2017-11-05 Thread intrigeri
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 setting this for all containers. This > is not the greatest solution, but it's also not

Bug#880441: linux-image-4.13.0-1-amd64: silently enabled AppArmor breaks other programs

2017-11-05 Thread intrigeri
Hi, Ben Hutchings: > My understanding was that enabling AppArmor shouldn't do very much > until a policy is loaded (which it won't be if you don't install the > userland tools). As you've found, that isn't entirely correct. Let me clear a potential misunderstanding: - It *is* correct that the

Bug#880864: linux-image-4.9.0-4-amd64: Hanged at poweroff

2017-11-05 Thread Olivier Cailloux
Package: src:linux Version: 4.9.51-1 Severity: normal Dear Maintainer, When running sudo poweroff, the computer proceeds to normal shutdown, unmounting disks, etc., ending with the message "ACPI: Preparing to enter system sleep state S5". Then the system hangs. Importantly, the problem does