Debian 8 (Console 5-31) Bug report (does not respond to serial port input after boot.

REGARDING: bone-debian-8.0-console-armhf-2015-05-31-2gb.img
BUG: Does not respond to inputs on serial port tty0 after boot.

Note:
bone-debian-8.0-lxqt-4gb-armhf-2015-05-31-4gb.img does not have this problem.
bone-debian-8.0-console-armhf-2015-05-17-2gb.img does not have this problem.

serial port tty0 boot log (partial):

[ OK ] Started System Logging Service.
[ OK ] Started Login Service.
Starting Getty on tty1…
[ OK ] Started Getty on tty1.
Starting Serial Getty on ttyS0…
[ OK ] Started Serial Getty on ttyS0.
[ 17.050606] musb-hdrc musb-hdrc.0.auto: otg: usb_otg_register_gadget: device not registered to otg core
[ OK ] Found device /dev/ttyGS0.
Starting Serial Getty on ttyGS0…
[ OK ] Started Serial Getty on ttyGS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started Generic Board Startup.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes…
[ OK ] Started Update UTMP about System Runlevel Changes.

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2015-05-31

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

The IP Address for eth0 is: 192.168.1.200
beaglebone login:

BBB-eMMC-flasher-debian-8.0-console-armhf-2015-05-31-2gb.img
does the same thing.

tty0 should be ttyS0 now I believe. Where this is changed with images using systemd I am not sure, but with SYSV this was changed in /etc/inittab.

Yes, tty0 now identifies as ttyGS0.

After fighting it for several hours, I went to lunch.
When I return, the problem has disappeared, is no longer reproducible, and everything is working fine.
I didn’t knowingly do anything to fix it.
So, I guess disregard the BugReport.

Anyway, in the future, I will try having more lunches when problems occur.

— Graham