Comment # 4 on bug 1208783 from Scott Bahling

I'm not that familiar with analyzing kdumps. Crash does show two active
jackdbus tasks running in parallel.

> 14517   6347   4  ffff8d228fb3c000  RU   0.1  308228  18904  jackdbus
> 14532   6347  15  ffff8d1ffab08000  RU   0.1  308228  18904  jackdbus

crash> files 14517
PID: 14517  TASK: ffff8d228fb3c000  CPU: 4   COMMAND: "jackdbus"
ROOT: /@/.snapshots/1/snapshot    CWD:
/@/.snapshots/1/snapshot/home/@/home/sbahling
 FD       FILE            DENTRY           INODE       TYPE PATH
  0 ffff8d2260d48300 ffff8d224040f200 ffff8d2243b0a178 CHR 
/@/.snapshots/1/snapshot/dev/null
  1 ffff8d20c70fc700 ffff8d20096e8540 ffff8d1ec0448080 SOCK UNIX
  2 ffff8d20c70fc600 ffff8d1eff9838c0 ffff8d1ec044b480 SOCK UNIX
  3 ffff8d1edf47df00 ffff8d1fdc92db00 ffff8d22aa82ef78 REG 
/@/.snapshots/1/snapshot/home/@/home/sbahling/.log/jack/jackdbus.log
  4 ffff8d1edf47c400 ffff8d2092c56a80 ffff8d229666aac0 SOCK UNIX
  5 ffff8d1ffdaf0d00 ffff8d1fdc908300 ffff8d2050860678 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_system
  6 ffff8d1ffdaede00 ffff8d1ec6c40000 ffff8d1ed5975478 CHR 
/@/.snapshots/1/snapshot/dev/snd/controlC3
  7 ffff8d1ffdaec800 ffff8d1fdc909500 ffff8d1fdc9e1740 SOCK UNIX
  8 ffff8d1ffdaec700 ffff8d1ec6c415c0 ffff8d1ed5973378 CHR 
/@/.snapshots/1/snapshot/dev/snd/pcmC3D0p
  9 ffff8d1ffdaecc00 ffff8d1ec6c403c0 ffff8d1ed5976378 CHR 
/@/.snapshots/1/snapshot/dev/snd/pcmC3D0c
 10 ffff8d1ffdaec300 ffff8d1fdc908840 ffff8d1fdc9e3480 SOCK UNIX
 11 ffff8d1ffdaedb00 ffff8d1fdc9098c0 ffff8d2050863378 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_freewheel
 12 ffff8d1ffdaec400 ffff8d1fdc908180 ffff8d2050863978 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_dbusapi
 13 ffff8d228dea2700 ffff8d2257bbfd40 ffff8d224685ebc0 SOCK UNIX

crash> files 14532
PID: 14532  TASK: ffff8d1ffab08000  CPU: 15  COMMAND: "jackdbus"
ROOT: /@/.snapshots/1/snapshot    CWD:
/@/.snapshots/1/snapshot/home/@/home/sbahling
 FD       FILE            DENTRY           INODE       TYPE PATH
  0 ffff8d2260d48300 ffff8d224040f200 ffff8d2243b0a178 CHR 
/@/.snapshots/1/snapshot/dev/null
  1 ffff8d20c70fc700 ffff8d20096e8540 ffff8d1ec0448080 SOCK UNIX
  2 ffff8d20c70fc600 ffff8d1eff9838c0 ffff8d1ec044b480 SOCK UNIX
  3 ffff8d1edf47df00 ffff8d1fdc92db00 ffff8d22aa82ef78 REG 
/@/.snapshots/1/snapshot/home/@/home/sbahling/.log/jack/jackdbus.log
  4 ffff8d1edf47c400 ffff8d2092c56a80 ffff8d229666aac0 SOCK UNIX
  5 ffff8d1ffdaf0d00 ffff8d1fdc908300 ffff8d2050860678 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_system
  6 ffff8d1ffdaede00 ffff8d1ec6c40000 ffff8d1ed5975478 CHR 
/@/.snapshots/1/snapshot/dev/snd/controlC3
  7 ffff8d1ffdaec800 ffff8d1fdc909500 ffff8d1fdc9e1740 SOCK UNIX
  8 ffff8d1ffdaec700 ffff8d1ec6c415c0 ffff8d1ed5973378 CHR 
/@/.snapshots/1/snapshot/dev/snd/pcmC3D0p
  9 ffff8d1ffdaecc00 ffff8d1ec6c403c0 ffff8d1ed5976378 CHR 
/@/.snapshots/1/snapshot/dev/snd/pcmC3D0c
 10 ffff8d1ffdaec300 ffff8d1fdc908840 ffff8d1fdc9e3480 SOCK UNIX
 11 ffff8d1ffdaedb00 ffff8d1fdc9098c0 ffff8d2050863378 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_freewheel
 12 ffff8d1ffdaec400 ffff8d1fdc908180 ffff8d2050863978 REG 
/@/.snapshots/1/snapshot/dev/shm/jack_sem.1000_default_dbusapi
 13 ffff8d228dea2700 ffff8d2257bbfd40 ffff8d224685ebc0 SOCK UNIX


I guess that is not normal. On my currently running system there is only one
jackdbus task running. I see the parallel jackdbus tasks in another crash dump
I have.

I do have problems with jackdbus hanging from time to time and I kill the
current task - the service restarts a new jackdbus task. Might be that the task
that has been "killed" but is really still alive when the next task starts?