Re: Introducing ubiboot N9 (multiboot OS loader)
 

Might be something to do with configuring the device on powerup, as I see at least on some occasions "Power Management for TI OMAP3" before the crash.
Maybe it's related to the fact that the device boots first to ubiboot and then to the default kernel which takes longer than booting straight to the default kernel from powerup... Could be some watchdog gets in a wrong state during that phase?

Does it do this often?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

G'd morning. Sorry, just fell asleep (laying in bed :)).

Yes, it does it almost always, when I plug in the wall charger in powered off state. But sometimes it also works and it boots ubiboot and then harmattan lwfix kernel and correctly charges.

The reason why you see different log reports may be that it behaves differently when booted from powered off state and after crash it boots with another boot reason (sw_rst)?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You are correct, if the device goes into kernel panic for some reason I think the bootreason is not trusted, it can have correct value or it can be "32wd_to" or something else..

Hm i just thought of something, have you tried disabling watchdogs, with "sudo flasher --set-rd-flags=no-omap-wd,no-ext-wd,no-lifeguard-reset"

It would be intresting to hear if that makes any difference in either the cold-powerup crashing or the problem to starts kernel-plus.


PS: I do recommend you to fix yourself a serial-console cable... Just this morning, when I debugged a problem in my new-hopefully-soon-to-be-released ubiboot kernel I had to hook up console to find out why going to repair console did not work... and yes, it turned to be the case I had wrong g_multi.ko in my buildscripts... :D:D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Going to set those rd flags and report back later...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So, needed some time to get my available HW ready for flashing :(
I disabled the watchdogs. And the first two tests were absolutely successful and I thought thats it. But the third time was unsuccessful: the screen stayed black after loading ubi kernel and no charging happened. Tried a few more times and 50/50 was okay/not charging. This time I needed to push power button for 8s, as no reset is done. Pulling/plugging USB did not help, a real power cut was needed. I think due to no-lifeguard-reset?
So in general no change, but the symptoms are different!

Same to the plus_nat kernel. No change here: screen stays black and needs power cut.


Some else info I could provide?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK, I thought that it might help in the charging startup situation but alas, seems it's not the watchdoggies this time.

About the boot to kernel plus, that really bugs me... Just few hours ago TMavica reported that booting from ubiboot to kernel-plus-extfat works without problems, so unless there is something wrong with your setup this is again some HWREV related thingy :mad:

And the strange thing here's that TMavica's got a 1603 device and you have 1601, and up to now it has always been 1603 that are the most troublesome devices?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

What should I say? :(

I also removed kernel and modules and started all over, no change.

I tried many times without booting problem until now

Re: Introducing ubiboot N9 (multiboot OS loader)
 

^Are you saying you have a problem now?
Or that you still don't have any problems?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thats nothing to do with open mode, it happens on secure mode too. System kills background applications if it decides that its low on RAM. Its a feature and not a bug.