[Motorola Photon Q 4G LTE] mrvek:
[MENTION=2218140]kabaldan[/MENTION]: how did you solve the initial issue with modem goint to restart as soon as it was brought out of reset by PIL? What was is the issue there?

A snippet of rild dying up until the watchdog bite:

<6>[ 77.662719,0] init: command 'write' r=0
<7>[ 78.103891,0] rmnet0: no IPv6 routers present
<6>[ 78.396276,0] init: waitpid returned pid 2697, status = 00000000
<5>[ 78.396429,0] init: process 'start_fd', pid 2697 exited
<6>[ 78.948512,0] init: waitpid returned pid 367, status = 00000009
<5>[ 78.948634,0] init: process 'ril-daemon', pid 367 exited
<5>[ 78.948756,0] init: process 'ril-daemon' killing any children in process group
<6>[ 78.949122,0] init: computing context for service '/system/bin/rild'
<5>[ 78.949305,0] init: starting 'ril-daemon'
<6>[ 78.950770,1] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'
<6>[ 78.951167,1] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'
<3>[ 78.974515,0] init: sys_prop: permission denied uid:1001 name:ro.radio.adb_log.on
<6>[ 78.998351,0] init: waitpid returned pid 463, status = 00000009
<3>[ 78.998443,0] init: untracked pid 463 exited
<6>[ 78.998596,0] init: waitpid returned pid 366, status = 00000009
<5>[ 78.998687,0] init: process 'debuggerd', pid 366 exited
<5>[ 78.998809,0] init: process 'debuggerd' killing any children in process group
<6>[ 78.999084,0] init: computing context for service '/system/bin/debuggerd'
<5>[ 78.999328,0] init: starting 'debuggerd'
<6>[ 82.025209,0] init: waitpid returned pid 2773, status = 00000100
<3>[ 82.025331,0] init: untracked pid 2773 exited
<6>[ 82.045627,0] init: waitpid returned pid 2779, status = 00000100
<3>[ 82.045780,0] init: untracked pid 2779 exited
<6>[ 88.985258,0] binder: undelivered transaction 28903
<6>[ 89.183274,0] init: waitpid returned pid 2033, status = 00000000
<3>[ 89.183366,0] init: untracked pid 2033 exited
<6>[ 89.254814,0] init: waitpid returned pid 2030, status = 00000000
<3>[ 89.254906,0] init: untracked pid 2030 exited
<6>[ 91.212604,0] init: processing action 0x824c8 (property:gsm.network.type=Unknown)
<6>[ 91.212849,0] init: computing context for service '/system/bin/sh'
<5>[ 91.213093,0] init: starting 'stop_fd'
<6>[ 91.213428,0] init: command 'start' r=0
<6>[ 91.237967,0] init: processing action 0x824c8 (property:gsm.network.type=Unknown)
<6>[ 91.238150,0] init: command 'start' r=0
<6>[ 91.669372,0] init: processing action 0x57e40 (property:sys.sysctl.tcp_def_init_rwnd=*)
<6>[ 91.669555,0] init: command 'write' r=0
<6>[ 92.224599,1] init: waitpid returned pid 2877, status = 00000000
<5>[ 92.224721,1] init: process 'stop_fd', pid 2877 exited
<3>[ 94.730016,0] Watchdog bite received from modem software!
<3>[ 94.730383,0] modem subsystem failure reason: (unknown, smem_get_entry failed).

I'm not sure what to make of it since you and stargo do not get the same. I can also see other services dying, sometimes ueventd, etc. Though the system seems to be functioning normal.

Has someone noticed modem going to SMSM_RESET state and restarting? On my builds it is less common than watchdog bite but is happenning.

<6>[ 466.541217,0] request_suspend_state: sleep (0->3) at 466527380624 (2014-07-23 19:00:03.705349418 UTC)
<6>[ 466.541706,0] lm3532_early_suspend: suspended
<3>[ 466.563009,0] dtv_pipe is not configured yet
<6>[ 466.586570,0] pm_debug: sleep uah=-1163
<6>[ 466.586906,0] atmxt_set_ic_state: IC state ACTIVE -> SLEEP
<3>[ 467.149549,0]
<3>[ 467.149549,0] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 467.149763,1] Notify: start reset
<3>[ 467.149763,0]
<3>[ 467.149763,0] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 467.149854,0] Probable fatal error on the modem.
<3>[ 467.149854,0] modem subsystem failure reason: (unknown, smem_get_entry failed).
<6>[ 467.149854,0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = 3.
<3>[ 467.150282,1] Notify: start reset
<6>[ 467.263909,0] subsys-restart: subsystem_shutdown(): [e3b639c0]: Shutting down modem

The same I've noticed on moto's drop for razr m (3.4.42, patched with kabaldan's changes, using CM defconfig), modem was up about 1 min after powerup and it went to smsm_reset about 18 mins later, soon folllowed by a watchdog bite, but that build had other issues (display was derpy, took forever to boot, "MDP ioctl unsupported" filling the log, sensors, audio broken...) so it may not be fully reliable, I'm not really sure, didn't have much time to play with it.

I've also prevented modem restart, right after logging "Watchdog timeout..." what left modem in a non-working state so it might safe to assume that we are not getting false bp panics.

Could someone please post their kernel log so I'd have something to comapre it to before I start writing more crap?

Thanks.