Bug#934707: [dbus,systemd,sssd]: Unresponsive domain and nonexistent user in policy lead to reload fail and fall of dependant daemons.

2019-08-13 Thread Arano-kai
Package: dbus
Version: 1.12.16-1
Severity: normal

Dear Maintainer.

As subject says, if sssd can't reach dc, dbus get NoReply fail and succesfully 
restarted aftervards with following consequences:
1. reload process lagging due sssd timeouts;
2. other daemons fail because 1 or dbus restart;
3. failed reload at packet install process may lead to overall install fail;

Because of automatic config reload, 1 is strikes at periodic manner.
The most notorious example of 2 is NetworkManager, which gets SIGTERM 
(org.freedesktop.nm_dispatcher timeout), shutdown network and require manual 
restart, despite the fact that dbus already restarted. Nice to have bunch of 
isolated instances at midnight because of network spike (:
3 is theoretical and depends on packages postinstall scripts and hooks.

Steps to reproduce:
1a. Get minimal setup with some additional packages:
  # debootstrap --arch=amd64 
--include=network-manager,sssd,iio-sensor-proxy,ovirt-guest-agent,linux-image-amd64,grub-pc
 stable /mnt
  # #Do other stuff to boot from...
1b. Or add network-manager, sssd, iio-sensor-proxy and ovirt-guest-agent to 
fresh setup. Last two will add policy with currently nonexistent users gdm and 
geoclue. Skip sssd realm config. You may notice NoReply fail due setup.
2. Check NetworkManager status and restart if already dead.
3. Do systemctl reload dbus.service. Notice time taken.
4. Check NetworkManager again. Status change to 'dead' after step 3 or some 
short time.
5. Check dbus journal. Notice org.freedesktop.nm_dispatcher activation fail, 
NoReply and restart.
BONUS STAGE: remove one user policy (eg. purge ovirt-guest-agent OR 
iio-sensor-proxy), restart NetworkManager and do dbus reload again. This time 
NM not fail.


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dbus depends on:
ii  adduser   3.118
ii  libapparmor1  2.13.2-10
ii  libaudit1 1:2.8.4-3
ii  libc6 2.28-10
ii  libcap-ng00.7.9-2
ii  libdbus-1-3   1.12.16-1
ii  libexpat1 2.2.6-2
ii  libselinux1   2.8-1+b1
ii  libsystemd0   241-5

dbus recommends no packages.

Versions of packages dbus suggests:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1

Versions of packages dbus is related to:
pn  dbus-x11  
ii  systemd   241-5
ii  systemd-sysv  241-5

-- no debconf information
-- Logs begin at Tue 2019-08-13 14:27:09 UTC, end at Tue 2019-08-13 17:45:55 
UTC. --
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: 
NetworkManager-wait-online.service: Succeeded.
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Stopped Network Manager 
Wait Online.
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Stopping Network Manager 
Wait Online...
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Starting Network 
Manager...
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.3909] NetworkManager (version 1.14.6) is starting... (after a 
restart)
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.3917] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 
no-mac-addr-change.conf)
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Started Network Manager.
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Starting Network Manager 
Wait Online...
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4021] bus-manager: acquired D-Bus service 
"org.freedesktop.NetworkManager"
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4029] manager[0x55a91f88b020]: monitoring kernel firmware directory 
'/lib/firmware'.
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4031] monitoring ifupdown state file '/run/network/ifstate'.
Aug 13 17:43:29 test-dbus-fail.fake.domain dbus-daemon[7179]: [system] 
Activating via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.8' (uid=0 
pid=7338 comm="/usr/sbin/NetworkManager --no-daemon ")
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Starting Hostname 
Service...
Aug 13 17:43:29 test-dbus-fail.fake.domain dbus-daemon[7179]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
Aug 13 17:43:29 test-dbus-fail.fake.domain systemd[1]: Started Hostname Service.
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4680] hostname: hostname: using hostnamed
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4681] hostname: hostname changed from (none) to 
"test-dbus-fail.fake.domain"
Aug 13 17:43:29 test-dbus-fail.fake.domain NetworkManager[7338]:   
[1565718209.4683] dns-mgr[0x5

Bug#861746: linux-image-4.9.0-2-amd64: Infinity `soft lockup` at kernel 4.9.0-1+ on HP ProLiant DL360G5

2017-05-03 Thread Arano-kai
Package: src:linux
Version: 4.9.18-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,
after updating the kernel to `4.9.0-2-amd64` on HP DL360G5, the system hangs up 
with repeating `NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! 
[swapper/0:1]`.
`4.9.0-1-amd64` also affected.
Last working kernel is `4.8.0-2-amd64`

Boot possible only if `acpi=off` provided in kernel opts.

Tried so far:
nolapic (booted with ony one core available)
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off

Boot log from the serial console is attached.

-- Package-specific info:
** Version:
Linux version 4.9.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170321 (Debian 6.3.0-11) ) #1 SMP Debian 4.9.18-1 (2017-03-30)

** Command line:
BOOT_IMAGE=/root/boot/vmlinuz-4.9.0-2-amd64 
root=UUID=74c84a83-8418-4579-9b0c-44a9298a39aa ro rootflags=subvol=root 
radeon.dpm=1 zswap.enabled=1 zswap.compressor=lz4 zswap.zpool=zbud 
zswap.max_pool_percent=15 acpi=off quiet

** Not tainted

** Kernel log:
[4.875659] ipmi message handler version 39.2
[4.910133] hpilo :01:04.2: PCI->APIC IRQ transform: INT B -> IRQ 22
[4.928771] IPMI System Interface driver.
[4.928811] ipmi_si :01:04.6: probing via PCI
[4.928828] ipmi_si :01:04.6: PCI->APIC IRQ transform: INT A -> IRQ 21
[4.928861] ipmi_si :01:04.6: [mem 0xf7ef-0xf7ef00ff] regsize 1 
spacing 1 irq 21
[4.928862] ipmi_si: Adding PCI-specified kcs state machine
[4.929716] intel_rng: FWH not detected
[4.929746] ipmi_si: probing via SMBIOS
[4.929748] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[4.929749] ipmi_si: Adding SMBIOS-specified kcs state machine
[4.929752] ipmi_si: Trying PCI-specified kcs state machine at mem address 
0xf7ef, slave address 0x0, irq 21
[4.932683] [drm] radeon kernel modesetting enabled.
[4.956838] CRAT table not found
[4.956841] Finished initializing topology ret=0
[4.956855] kfd kfd: Initialized module
[4.957167] radeon :01:03.0: PCI->APIC IRQ transform: INT A -> IRQ 23
[4.957363] [drm] initializing kernel modesetting (RV100 0x1002:0x515E 
0x103C:0x31FB 0x02).
[4.957381] [drm] register mmio base: 0xF7FF
[4.957382] [drm] register mmio size: 65536
[4.957496] radeon :01:03.0: VRAM: 128M 0xD800 - 
0xDFFF (32M used)
[4.957499] radeon :01:03.0: GTT: 512M 0xB800 - 
0xD7FF
[4.957512] [drm] Detected VRAM RAM=128M, BAR=128M
[4.957513] [drm] RAM width 16bits DDR
[4.957583] [TTM] Zone  kernel: Available graphics memory: 509350 kiB
[4.957584] [TTM] Initializing pool allocator
[4.957591] [TTM] Initializing DMA pool allocator
[4.957621] [drm] radeon: 32M of VRAM memory ready
[4.957623] [drm] radeon: 512M of GTT memory ready.
[4.957640] [drm] GART: num cpu pages 131072, num gpu pages 131072
[4.978717] [drm] PCI GART of 512M enabled (table at 0x3BA8).
[4.978885] radeon :01:03.0: WB disabled
[4.978890] radeon :01:03.0: fence driver on ring 0 use gpu addr 
0xb800 and cpu addr 0x9c093b4e3000
[4.978892] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[4.978893] [drm] Driver supports precise vblank timestamp query.
[4.978917] [drm] radeon: irq initialized.
[4.978939] [drm] Loading R100 Microcode
[4.979594] input: PC Speaker as /devices/platform/pcspkr/input/input5
[4.981521] sr 0:0:0:0: Attached scsi generic sg0 type 5
[5.026313] radeon :01:03.0: firmware: direct-loading firmware 
radeon/R100_cp.bin
[5.026523] [drm] radeon: ring at 0xB8001000
[5.026550] [drm] ring test succeeded in 1 usecs
[5.026687] [drm] ib test succeeded in 0 usecs
[5.027062] [drm] No TV DAC info found in BIOS
[5.027118] [drm] Radeon Display Connectors
[5.027119] [drm] Connector 0:
[5.027120] [drm]   VGA-1
[5.027122] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[5.027123] [drm]   Encoders:
[5.027124] [drm] CRT1: INTERNAL_DAC1
[5.027125] [drm] Connector 1:
[5.027126] [drm]   VGA-2
[5.027127] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[5.027128] [drm]   Encoders:
[5.027129] [drm] CRT2: INTERNAL_DAC2
[5.093779] [drm] fb mappable at 0xD804
[5.093781] [drm] vram apper at 0xD800
[5.093782] [drm] size 786432
[5.093783] [drm] fb depth is 8
[5.093784] [drm]pitch is 1024
[5.093992] fbcon: radeondrmfb (fb0) is primary device
[5.253797] Console: switching to colour frame buffer device 128x48
[5.261376] radeon :01:03.0: fb0: radeondrmfb frame buffer device
[5.276027] [drm] Initialized radeon 2.48.0 20080528 for :01:03.0 on 
minor 0
[5.357185] iTCO_vendor_support: vendor-support=0
[5.406046] iTC