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:
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.
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.