The stack trace shows a NULL ptr dereference in __uart_start() and that made me think that the attached patch could solve it, but it wasn't enough.
Another peculiarity of the serial in the rpi3 is that it's a sw serial, and to void baud rate changes we fixed the core frequency in config.txt: core_freq=250 By commenting the above line in config.txt, and using a patched kernel (with the aforementioned patch) i can't reproduce this panic anymore - here's a prerolled image with these modifications: http://people.canonical.com/~ppisati/lp1630586/ubuntu- core-16-pi3-lp1630586.img.xz To get back the serial, people will have to manually uncomment the core_freq line in config.txt - i'll keep digging into this, in the mean time it would be nice to have some testing of this image. ** Patch added: "0001-serial-Take-care-starting-a-hung-up-tty-s-port.patch" https://bugs.launchpad.net/snappy/+bug/1630586/+attachment/4755999/+files/0001-serial-Take-care-starting-a-hung-up-tty-s-port.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630586 Title: Pi3 kernel crash and is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1630586/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
