Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
control: found -1 linux/5.10.28-1
Ohai,
On Mon, May 11, 2020 at 10:22:23PM +0200, Uwe Kleine-König wrote:
> > Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume
> > without issues.
>
> I brought this problem to the attention of the x86 guys; see above URL
> for the conversation.
>
> Up to now no breaking insights.
>
> @Lennert: Did you change your BIOS settings since the problem occured to
> you? Lenny Szubowicz hinted it might be related to the TPM chip and
> indeed switching it in the BIOS settings from 2.0 to 1.2 mode makes the
> problem go away for me.
I can reproduce this on a Lenovo Thinkpad Yoga 260 with the latest
kernel in bullseye.
Disabling IOMMU on the command line or changing the TPM to 1.2
("dedicated") in the BIOS fixes the issue here.
Would be nice if we could at least document this issue as a known thing
in the release notes.
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Control: forwarded -1 https://lore.kernel.org/r/20200506144558.ga4...@taurus.defre.kleine-koenig.org Hello, On Tue, Apr 21, 2020 at 12:59:15PM +, Lennert Van Alboom wrote: > ‐‐‐ Original Message ‐‐‐ > On Sunday, 19 April 2020 17:02, Lennert Van Alboom > wrote: > > ‐‐‐ Original Message ‐‐‐ > > On Sunday, 19 April 2020 15:56, Uwe Kleine-König u...@kleine-koenig.org > > wrote: > > > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your > > > custom kernel? (If only the former: Do you suffer from the reported > > > problem when you add intel_iommu=on to the kernel command line?) > > > > > I started with the stock Debian 5.5-rc config, and just did make oldconfig > > from there on (don't like to stray too far from the official packages). So > > the option should be identical to the Debian kernels. > > > > > $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config > > CONFIG_INTEL_IOMMU=y > > CONFIG_INTEL_IOMMU_SVM=y > > > > > CONFIG_INTEL_IOMMU_DEFAULT_ON is not set > > > > > = > > > > > CONFIG_INTEL_IOMMU_FLOPPY_WA=y > > CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y > > > > > I don't reboot often, but I'll very likely run into the i915 hang above > > again soon, so I'll try the intel_iommu=on then. > > > Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without > issues. I brought this problem to the attention of the x86 guys; see above URL for the conversation. Up to now no breaking insights. @Lennert: Did you change your BIOS settings since the problem occured to you? Lenny Szubowicz hinted it might be related to the TPM chip and indeed switching it in the BIOS settings from 2.0 to 1.2 mode makes the problem go away for me. Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
‐‐‐ Original Message ‐‐‐ On Sunday, 19 April 2020 17:02, Lennert Van Alboom wrote: > ‐‐‐ Original Message ‐‐‐ > On Sunday, 19 April 2020 15:56, Uwe Kleine-König u...@kleine-koenig.org wrote: > > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your > > custom kernel? (If only the former: Do you suffer from the reported > > problem when you add intel_iommu=on to the kernel command line?) > > I started with the stock Debian 5.5-rc config, and just did make oldconfig > from there on (don't like to stray too far from the official packages). So > the option should be identical to the Debian kernels. > > $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config > CONFIG_INTEL_IOMMU=y > CONFIG_INTEL_IOMMU_SVM=y > > CONFIG_INTEL_IOMMU_DEFAULT_ON is not set > > = > > CONFIG_INTEL_IOMMU_FLOPPY_WA=y > CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y > > I don't reboot often, but I'll very likely run into the i915 hang above again > soon, so I'll try the intel_iommu=on then. Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without issues. publickey - lennert@vanalboom.org - 0x0320C886.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
‐‐‐ Original Message ‐‐‐ On Sunday, 19 April 2020 15:56, Uwe Kleine-König wrote: > Hello Lennert, > > On Sat, Apr 18, 2020 at 11:29:42PM +, Lennert Van Alboom wrote: > > > \ Original Message > > On 19 Apr 2020, 00:42, Uwe Kleine-König < u...@kleine-koenig.org> wrote: > > > > > @Lennert: I assume you can still reproduce the problem. Do you care to > > > test with intel_iommu=off and report about the result? Just to make > > > sure you and I see the same problems? > > > > I'm afraid I can't test this anymore - due to serious i915 issues I've > > been building and running my own kernel packages. Currently running > > 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh). > > So the newer kernels don't fix your problems? In my experience the i915 > guys are quite responsive and willing to help if you run a recent > kernel. They don't. I've reported a bug for it a good while back: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949021 https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/183 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2352 Awfully quiet there. There seem to be multiple similar bugs around; so far the only response I got upstream was the bug being closed and moved to "mesa" (which I don't really get either). Debian bug didn't get any acknowledgement or comment. > > . I haven't seen the poweroff/suspend problem in a good while. > > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your > custom kernel? (If only the former: Do you suffer from the reported > problem when you add intel_iommu=on to the kernel command line?) I started with the stock Debian 5.5-rc config, and just did make oldconfig from there on (don't like to stray too far from the official packages). So the option should be identical to the Debian kernels. $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config CONFIG_INTEL_IOMMU=y CONFIG_INTEL_IOMMU_SVM=y # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set CONFIG_INTEL_IOMMU_FLOPPY_WA=y CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y I don't reboot often, but I'll very likely run into the i915 hang above again soon, so I'll try the intel_iommu=on then. publickey - lennert@vanalboom.org - 0x0320C886.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Hello Lennert, On Sat, Apr 18, 2020 at 11:29:42PM +, Lennert Van Alboom wrote: > \ Original Message > On 19 Apr 2020, 00:42, Uwe Kleine-König < u...@kleine-koenig.org> wrote: > > @Lennert: I assume you can still reproduce the problem. Do you care to > > test with intel_iommu=off and report about the result? Just to make > > sure you and I see the same problems? > > I'm afraid I can't test this anymore - due to serious i915 issues I've > been building and running my own kernel packages. Currently running > 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh). So the newer kernels don't fix your problems? In my experience the i915 guys are quite responsive and willing to help if you run a recent kernel. > . I haven't seen the poweroff/suspend problem in a good while. Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your custom kernel? (If only the former: Do you suffer from the reported problem when you add intel_iommu=on to the kernel command line?) Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
\ Original Message On 19 Apr 2020, 00:42, Uwe Kleine-König < u...@kleine-koenig.org> wrote: @Lennert: I assume you can still reproduce the problem. Do you care to test with intel\_iommu=off and report about the result? Just to make sure you and I see the same problems? Best regards Uwe I'm afraid I can't test this anymore - due to serious i915 issues I've been building and running my own kernel packages. Currently running 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh) . I haven't seen the poweroff/suspend problem in a good while. publickey - lennert@vanalboom.org - 0x0320C886.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Hello, On Sat, Apr 18, 2020 at 03:18:35PM +0200, Uwe Kleine-König wrote: > On Sat, Apr 18, 2020 at 01:22:26PM +0200, Uwe Kleine-König wrote: > > On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote: > > > Control: found -1 5.5.13-2 > > > > > > On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote: > > > > Package: src:linux > > > > Version: 5.5~rc5-1~exp1 > > > > Severity: normal > > > > > > > > Neither shutdown nor suspend works in this kernel version. Systemd seems > > > > to indicate it is trying at least, but the system hangs either right > > > > before shutdown (clean situation, requiring a poweroff with the power > > > > button) or before sleep (hung system, can't do anything except also hard > > > > powering off and rebooting later). > > > > > > > > Syslog from a suspend action: > > > > > > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6342] > > > > manager: sleep: sleep requested (sleeping: no enabled: yes) > > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6343] > > > > device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason > > > > 'sleeping', sys-iface-state: 'managed') > > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6345] > > > > manager: NetworkManager state is now ASLEEP > > > > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep. > > > > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend... > > > > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry > > > > (s2idle) > > > > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system... > > > > > > I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with > > > 4.19 from buster there is no such problem. I didn't debug any further > > > yet. > > > > I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer > > from this problem, but linux-image-5.6.0-trunk-amd64-unsigned > > 5.6.4-1~exp1 has the same problem. > > I started bisecting (but didn't complete yet, the weather is too good to > sit inside :-). Currently I see > > bad: 5.2.17-1+b1 > good: 5.2.6-1 > I checked the remaining versions in between the two above and the bisect result is that 5.2.7-1 is the last good; and 5.2.9-1 is the first bad kernel image. The relevant change between these two is: * [x86] iommu: Enable INTEL_IOMMU_DEFAULT_ON (Closes: #934309) . At least 5.2.7-1 shows the problematic behaviour when I add "intel_iommu=on" on the kernel command line. I suspect I can boot newer kernels with "intel_iommu=off", but didn't try that yet. Related: https://bugzilla.kernel.org/show_bug.cgi?id=197029 @Lennert: I assume you can still reproduce the problem. Do you care to test with intel_iommu=off and report about the result? Just to make sure you and I see the same problems? Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
hello, On Sat, Apr 18, 2020 at 01:22:26PM +0200, Uwe Kleine-König wrote: > On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote: > > Control: found -1 5.5.13-2 > > > > On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote: > > > Package: src:linux > > > Version: 5.5~rc5-1~exp1 > > > Severity: normal > > > > > > Neither shutdown nor suspend works in this kernel version. Systemd seems > > > to indicate it is trying at least, but the system hangs either right > > > before shutdown (clean situation, requiring a poweroff with the power > > > button) or before sleep (hung system, can't do anything except also hard > > > powering off and rebooting later). > > > > > > Syslog from a suspend action: > > > > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6342] > > > manager: sleep: sleep requested (sleeping: no enabled: yes) > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6343] > > > device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason > > > 'sleeping', sys-iface-state: 'managed') > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6345] > > > manager: NetworkManager state is now ASLEEP > > > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep. > > > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend... > > > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle) > > > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system... > > > > I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with > > 4.19 from buster there is no such problem. I didn't debug any further > > yet. > > I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer > from this problem, but linux-image-5.6.0-trunk-amd64-unsigned > 5.6.4-1~exp1 has the same problem. I started bisecting (but didn't complete yet, the weather is too good to sit inside :-). Currently I see bad: 5.2.17-1+b1 good: 5.2.6-1 So this is either a regression (also) in stable or something Debian-specific (or I did something wrong). Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Hello again, On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote: > Control: found -1 5.5.13-2 > > On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote: > > Package: src:linux > > Version: 5.5~rc5-1~exp1 > > Severity: normal > > > > Neither shutdown nor suspend works in this kernel version. Systemd seems > > to indicate it is trying at least, but the system hangs either right > > before shutdown (clean situation, requiring a poweroff with the power > > button) or before sleep (hung system, can't do anything except also hard > > powering off and rebooting later). > > > > Syslog from a suspend action: > > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6342] > > manager: sleep: sleep requested (sleeping: no enabled: yes) > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6343] > > device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason > > 'sleeping', sys-iface-state: 'managed') > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6345] > > manager: NetworkManager state is now ASLEEP > > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep. > > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend... > > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle) > > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system... > > I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with > 4.19 from buster there is no such problem. I didn't debug any further > yet. I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer from this problem, but linux-image-5.6.0-trunk-amd64-unsigned 5.6.4-1~exp1 has the same problem. On thing I noticed: When I send my Laptop in suspend, the power LED starts blinking slowly (as it does with 4.19), but the FnLk LED stays on which on 4.19 goes off shortly after suspend is reached. So I think the problem is in the going to sleep step, not only when (not) waking up. Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Control: found -1 5.5.13-2 On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote: > Package: src:linux > Version: 5.5~rc5-1~exp1 > Severity: normal > > Neither shutdown nor suspend works in this kernel version. Systemd seems > to indicate it is trying at least, but the system hangs either right > before shutdown (clean situation, requiring a poweroff with the power > button) or before sleep (hung system, can't do anything except also hard > powering off and rebooting later). > > Syslog from a suspend action: > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6342] > manager: sleep: sleep requested (sleeping: no enabled: yes) > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6343] device > (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', > sys-iface-state: 'managed') > Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6345] > manager: NetworkManager state is now ASLEEP > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep. > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend... > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle) > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system... I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with 4.19 from buster there is no such problem. I didn't debug any further yet. Best regards Uwe signature.asc Description: PGP signature
Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Package: src:linux Version: 5.5~rc5-1~exp1 Severity: normal Neither shutdown nor suspend works in this kernel version. Systemd seems to indicate it is trying at least, but the system hangs either right before shutdown (clean situation, requiring a poweroff with the power button) or before sleep (hung system, can't do anything except also hard powering off and rebooting later). Syslog from a suspend action: Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6342] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 16 06:43:53 Nesbitt NetworkManager[749]: [1579153433.6345] manager: NetworkManager state is now ASLEEP Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep. Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend... Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle) Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system... -- Package-specific info: ** Version: Linux version 5.5.0-rc5-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20200104 (Debian 9.2.1-22)) #1 SMP Debian 5.5~rc5-1~exp1 (2020-01-06) ** Command line: BOOT_IMAGE=/vmlinuz-5.5.0-rc5-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet ** Not tainted ** Kernel log: [ 11.240204] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x3 has wMaxPacketSize 0, skipping [ 11.240207] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x83 has wMaxPacketSize 0, skipping [ 11.240213] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02 [ 11.240215] usb 3-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 11.268290] mc: Linux media interface: v0.10 [ 11.269619] alg: No test for fips(ansi_cprng) (fips_ansi_cprng) [ 11.272214] SCSI subsystem initialized [ 11.275443] usb-storage 4-1:1.0: USB Mass Storage device detected [ 11.275734] scsi host0: usb-storage 4-1:1.0 [ 11.275814] videodev: Linux video capture interface: v2.00 [ 11.275824] usbcore: registered new interface driver usb-storage [ 11.277009] usbcore: registered new interface driver uas [ 11.285112] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:56b2) [ 11.303110] uvcvideo 3-1:1.0: Entity type for entity Extension 4 was not initialized! [ 11.303111] uvcvideo 3-1:1.0: Entity type for entity Extension 3 was not initialized! [ 11.303112] uvcvideo 3-1:1.0: Entity type for entity Processing 2 was not initialized! [ 11.303112] uvcvideo 3-1:1.0: Entity type for entity Camera 1 was not initialized! [ 11.303150] input: Integrated Camera: Integrated C as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/input/input21 [ 11.303195] usbcore: registered new interface driver uvcvideo [ 11.303195] USB Video Class driver (1.1.1) [ 11.309377] Bluetooth: Core ver 2.22 [ 11.309386] NET: Registered protocol family 31 [ 11.309386] Bluetooth: HCI device and connection manager initialized [ 11.309388] Bluetooth: HCI socket layer initialized [ 11.309390] Bluetooth: L2CAP socket layer initialized [ 11.309391] Bluetooth: SCO socket layer initialized [ 11.313933] usbcore: registered new interface driver btusb [ 11.315171] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017 [ 11.316154] Bluetooth: hci0: Device revision is 2 [ 11.316169] Bluetooth: hci0: Secure boot is enabled [ 11.316169] Bluetooth: hci0: OTP lock is enabled [ 11.316169] Bluetooth: hci0: API lock is enabled [ 11.316170] Bluetooth: hci0: Debug lock is disabled [ 11.316170] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.317265] bluetooth hci0: firmware: direct-loading firmware intel/ibt-19-32-4.sfi [ 11.317267] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi [ 12.307973] scsi 0:0:0:0: Direct-Access USB Disk 3.0 0009 PQ: 0 ANSI: 6 [ 12.318811] scsi 0:0:0:0: Attached scsi generic sg0 type 0 [ 12.321712] sd 0:0:0:0: [sda] 60825600 512-byte logical blocks: (31.1 GB/29.0 GiB) [ 12.322349] sd 0:0:0:0: [sda] Write Protect is off [ 12.322367] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 12.323064] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 12.346647] sda: sda1 [ 12.347847] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 12.400600] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 12.419559] audit: type=1400 audit(1579159022.895:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=734 comm="apparmor_parser" [ 12.420287] audit: type=1400 audit(1579159022.895:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=730 comm="apparmor_parser" [ 12.420374] audit: type=1400 audit(1579159022.895:4): apparmor="STATUS" operation="profile_load"
