Comment # 21 on bug 917411 from macias -

I did all steps. Around 10 minutes before freeze I have such message:

Feb 20 22:03:01 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:03:01 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:03:08 linux-figp [18472]: init] imap
/tmp/ksocket-mist/klauncherftaor8.slav: DIGEST-MD5 common mech free
Feb 20 22:03:11 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:03:11 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:03:11 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:03:18 linux-figp kio_pop3[18508]: nit] pop3
/tmp/ksocket-mist/klauncherftaor8.slave: DIGEST-MD5 common mech free
Feb 20 22:03:21 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:03:21 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1

And up to freeze moment tons of such messages:

Feb 20 22:11:12 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:11:22 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:11:22 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:11:22 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:11:32 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:11:32 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:11:32 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:11:42 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:11:42 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:11:42 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:11:52 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:11:52 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:11:52 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:12:02 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:12:02 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:12:02 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:12:12 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:12:12 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:12:12 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:12:22 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:12:22 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:12:22 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:12:32 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:12:32 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:12:32 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0
Feb 20 22:12:42 linux-figp kernel: i2c i2c-2: master_xfer[0] W, addr=0x50,
len=1
Feb 20 22:12:42 linux-figp kernel: i2c i2c-2: master_xfer[1] R, addr=0x50,
len=1
Feb 20 22:12:42 linux-figp kernel: i2c i2c-2: NAK from device addr 0x50 msg #0

The last line of this quote is the last message registered (I execute
"journalctrl" to get them).

The freeze SEEMS unrelated to pulseaudio, because now I am running PA (however
I am not sure the config is 100% the same due to problematic setup I made much
more steps to make it working). I will run system w/o radiotray, to eliminate
that factor.