maemo.org - Talk - View Single Post - The N9/N950 Kernel Upstreaming Force

	filip.pz	2015-09-21 , 16:47
	Posts: 108 \| Thanked: 579 times \| Joined on Feb 2013 @ Požega, Croatia	#33

Just an update on progress so far (or lack of it).

I've ported hack from 3.5.3 that deals with broken watchdogs, but it hasn't made any difference. To be sure that watchdogs are not to blame, I've used flasher to disable them (good idea marmistrz):

Code:

sudo flasher --enable-rd-mode --set-rd-flags=no-omap-wd,no-ext-wd,no-lifeguard-reset

but that didn't help.
Also wehen 3.5.3 gets compiled with:

Code:

CONFIG_WATCHDOG_NOWAYOUT=y

I also get warnings about watchdogs (thanks nieldk), twice about two independent watchdogs:

Code:

omap_wdt: Unexpected close, not stopping!
twl4030_wdt twl4030_wdt: Unexpected close, watchdog still running!
...
omap_wdt: Unexpected close, not stopping!
twl4030_wdt twl4030_wdt: Unexpected close, watchdog still running!

Funny thing is that in 4.3.0-rc2: I get two warnings of single watchdog:

Code:

watchdog watchdog0: watchdog did not stop!
...
watchdog watchdog0: watchdog did not stop!

I'll rechek if kernel knows about both watchdogs (omap_wdt and twl4030_wdt), and why I get warning for just one of them as opposed to 3.5.3 where both warn about Unexpected close

If nothing helps I'll try to disable systemd services that can't work at this stage, but can make problems (loading kernel modules, starting SGX driver) - still I would expect to see somthing in console, if that's the case

Quote & Reply |

The Following 4 Users Say Thank You to filip.pz For This Useful Post:
hrbani, marmistrz, minimos, wicket