@Tiago-Couto I looked over your log file. Your kernel panic is happening ~31 seconds, just as the Wifi is turning on - this is at the time of the Omega's highest power load. How are you powering the Omega2+, ie what is your power source and how is the Omega2+ wired to the source?
Well next time I better look for official announcement. I figured they were too busy and just added 2 versions, 151 and 152, so I went ahead. Nothing adverse I see yet. Command oupgrade shows b150 as latest. I hope the official release can override what I did.
If one wants to get to the bottom of it, old and new factory images can be extracted via tricky application of squashfs tools (and maybe dd and whatever compression tool, I forget) and the various startup scripts and programs diffed directly.
Or you can poke around on the running system (or two side by side?) and see what is changed.
Of course checking any changes in the public repo would be worthwhile, but unclear if whatever is causing the issue made it there. My initial sense after looking at it is that the upstream change WereCatf mentioned would not apply to this hardware, but not 100% sure of that. It would not be at all surprising if the issue does turn to to be a similarly tiny detail breaking some part of the automated process.
This fixes the cloud connect issue, but I still have an issue with expled not working for the RGB led on the expansion board. I have to downgrade the firmware to 0.1.6-b137 in order to get it working, and then I can;t connect to the cloud! Can we have an upgrade that fixes both issues please?