Sudden USB Permanent Death

I’ve been using the Alchitry AU for some time now and have been happy with the board. For a long time I’ve noticed that the board gets pretty hot although I never got around to giving it cooling. I accidentally left my design running overnight which hammers DDR pretty hard. I came back to my desk today and noticed the USB was not responding. I then checked my /dev/ttyUSB entries and the alchitry was not there. I did some more digging and noticed that after programming with the loader one of the 2 interfaces would come back. My guess is programming still works because you are doing bulk transfers and that somehow kicks the chip back to life but since the port for programming is not the standard UART port but the weird JTAG thing I’m guessing the TTY I see coming back is not the one I want.

Below is a paste from dmesg I get. Notice how when I plug in the board it notices the FTDI chip. Creates the 2 USB Serial interfaces. Then immediately disconnects them. Then a few seconds later I start programming with loader. The FTDI chip is re detected but only for 1 of the ports. Any idea what to do here? I really would like to keep developing on this thing but my design was using the UART as the debug/control until my ESP32 interface is done.

[ 1345.158663] usb 1-10: new high-speed USB device number 18 using xhci_hcd
[ 1345.289513] usb 1-10: New USB device found, idVendor=0403, idProduct=6010, bcdDevice= 7.00
[ 1345.289548] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1345.289555] usb 1-10: Product: Alchitry Au
[ 1345.289560] usb 1-10: Manufacturer: Alchitry
[ 1345.289564] usb 1-10: SerialNumber:
[ 1345.294804] ftdi_sio 1-10:1.0: FTDI USB Serial Device converter detected
[ 1345.294896] usb 1-10: Detected FT2232H
[ 1345.295163] usb 1-10: FTDI USB Serial Device converter now attached to ttyUSB1
[ 1345.297472] ftdi_sio 1-10:1.1: FTDI USB Serial Device converter detected
[ 1345.297604] usb 1-10: Detected FT2232H
[ 1345.297915] usb 1-10: FTDI USB Serial Device converter now attached to ttyUSB2
[ 1345.319011] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 1345.319090] ftdi_sio 1-10:1.0: device disconnected
[ 1345.319370] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
[ 1345.319423] ftdi_sio 1-10:1.1: device disconnected
[ 1370.977659] ftdi_sio 1-10:1.0: FTDI USB Serial Device converter detected
[ 1370.977774] usb 1-10: Detected FT2232H
[ 1370.978031] usb 1-10: FTDI USB Serial Device converter now attached to ttyUSB1
[ 1378.456886] usb 1-10: USB disconnect, device number 18
[ 1378.457593] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1

Well now I feel dumb. Please ignore everything above and just head this warning. If you randomly one day decide to upgrade 3 LTS of Linux distros. In the process notice the old alchitry loader has no CLI interface and migrate to the new alchitry tool. Then expect your udev rules to all just work out of the box. You are an idiot like me. So instead delete the old alchitry udev rule that conflicts with the new software.

Keeping original post to share my shame.