Turns out tytools does not have a make uninstall. I made the mistake of doing sudo make install.
I did compile tytools with the debug flag, but I am not sure if the optimization was turned off. Ran valgrind with checking for memory leaks and found quite a few, but, without knowing if -O0 was set, then not sure if the errors are valid. And the system crashed while running valgrind. So much for that. Here is part of the kernel log right at crash time. Jun 5 15:28:52 pop-os kernel: [ 4935.833558] usb 1-1.4: new high-speed USB device number 6 using xhci_hcd Jun 5 15:28:52 pop-os kernel: [ 4935.933900] usb 1-1.4: New USB device found, idVendor=045b, idProduct=0209, bcdDevice= 1.00 Jun 5 15:28:52 pop-os kernel: [ 4935.933911] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jun 5 15:28:52 pop-os kernel: [ 4935.935650] hub 1-1.4:1.0: USB hub found Jun 5 15:28:52 pop-os kernel: [ 4935.935690] hub 1-1.4:1.0: 4 ports detected Jun 5 15:28:52 pop-os kernel: [ 4936.013918] usb 2-1.4: new SuperSpeed USB device number 3 using xhci_hcd Jun 5 15:28:53 pop-os kernel: [ 4936.036122] usb 2-1.4: New USB device found, idVendor=045b, idProduct=0210, bcdDevice= 1.00 Jun 5 15:28:53 pop-os kernel: [ 4936.036133] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jun 5 15:28:53 pop-os kernel: [ 4936.040168] hub 2-1.4:1.0: USB hub found Jun 5 15:28:53 pop-os kernel: [ 4936.040482] hub 2-1.4:1.0: 4 ports detected Jun 5 15:28:53 pop-os kernel: [ 4936.221573] usb 1-1.4.1: new high-speed USB device number 7 using xhci_hcd Jun 5 15:28:53 pop-os kernel: [ 4936.322294] usb 1-1.4.1: New USB device found, idVendor=045b, idProduct=0209, bcdDevice= 1.00 Jun 5 15:28:53 pop-os kernel: [ 4936.322305] usb 1-1.4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jun 5 15:28:53 pop-os kernel: [ 4936.324336] hub 1-1.4.1:1.0: USB hub found Jun 5 15:28:53 pop-os kernel: [ 4936.324418] hub 1-1.4.1:1.0: 4 ports detected Jun 5 15:28:53 pop-os kernel: [ 4936.401953] usb 2-1.4.1: new SuperSpeed USB device number 4 using xhci_hcd Jun 5 15:28:53 pop-os kernel: [ 4936.424603] usb 2-1.4.1: New USB device found, idVendor=045b, idProduct=0210, bcdDevice= 1.00 Jun 5 15:28:53 pop-os kernel: [ 4936.424615] usb 2-1.4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jun 5 15:28:53 pop-os kernel: [ 4936.428945] hub 2-1.4.1:1.0: USB hub found Jun 5 15:28:53 pop-os kernel: [ 4936.429395] hub 2-1.4.1:1.0: 4 ports detected Jun 5 15:28:53 pop-os kernel: [ 4936.501581] usb 1-1.4.4: new high-speed USB device number 8 using xhci_hcd Jun 5 15:28:53 pop-os kernel: [ 4936.602470] usb 1-1.4.4: New USB device found, idVendor=16c0, idProduct=0483, bcdDevice= 2.80 Jun 5 15:28:53 pop-os kernel: [ 4936.602483] usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 5 15:28:53 pop-os kernel: [ 4936.602488] usb 1-1.4.4: Product: USB Serial Jun 5 15:28:53 pop-os kernel: [ 4936.602491] usb 1-1.4.4: Manufacturer: Teensyduino Jun 5 15:28:53 pop-os kernel: [ 4936.602495] usb 1-1.4.4: SerialNumber: 11951490 Jun 5 15:28:53 pop-os kernel: [ 4936.618812] cdc_acm 1-1.4.4:1.0: ttyACM0: USB ACM device Jun 5 15:28:53 pop-os kernel: [ 4936.618825] usbcore: registered new interface driver cdc_acm Jun 5 15:28:53 pop-os kernel: [ 4936.618826] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Jun 5 15:29:11 pop-os kernel: [ 4954.562570] usb 1-1.4.4: USB disconnect, device number 8 Jun 5 15:29:11 pop-os kernel: [ 4954.789711] usb 1-1.4.4: new high-speed USB device number 9 using xhci_hcd Jun 5 15:29:11 pop-os kernel: [ 4954.894057] usb 1-1.4.4: New USB device found, idVendor=16c0, idProduct=0478, bcdDevice= 1.07 Jun 5 15:29:11 pop-os kernel: [ 4954.894070] usb 1-1.4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=1 Jun 5 15:29:11 pop-os kernel: [ 4954.894075] usb 1-1.4.4: SerialNumber: 00123C8D Jun 5 15:29:11 pop-os kernel: [ 4954.896882] hid-generic 0003:16C0:0478.0007: hidraw4: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:14.0-1.4.4/input0 Jun 5 15:29:13 pop-os kernel: [ 4956.610526] usb 1-1.4.4: USB disconnect, device number 9 Jun 5 15:29:14 pop-os kernel: [ 4957.329719] usb 1-1.4.4: new high-speed USB device number 10 using xhci_hcd Jun 5 15:29:14 pop-os kernel: [ 4957.430023] usb 1-1.4.4: New USB device found, idVendor=16c0, idProduct=0483, bcdDevice= 2.80 Jun 5 15:29:14 pop-os kernel: [ 4957.430036] usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 5 15:29:14 pop-os kernel: [ 4957.430041] usb 1-1.4.4: Product: USB Serial Jun 5 15:29:14 pop-os kernel: [ 4957.430044] usb 1-1.4.4: Manufacturer: Teensyduino Jun 5 15:29:14 pop-os kernel: [ 4957.430047] usb 1-1.4.4: SerialNumber: 11951490 Jun 5 15:29:14 pop-os kernel: [ 4957.434656] cdc_acm 1-1.4.4:1.0: ttyACM0: USB ACM device Jun 5 15:45:11 pop-os kernel: [ 0.000000] microcode: microcode updated early to revision 0xea, date = 2021-02-07 The last error I get is related to USB, then the system hard collapses. Nothing else happens. syslog got a string of \00\00... to it. dmesg shows the same time for the reboot, the same USB message and nothing else. This has been pretty frustrating. On 6/5/22 12:08 PM, Bruce Labitt wrote: > I am experiencing severe Linux crashes, due to some unknown causes. > They appear to be related to the use of Ty Commander and programming a > Teensy 4.1 in the Arduino IDE environment, but I am not positive. All I > know at the moment, is that the screen freezes and is unresponsive to > keyboard or mouse inputs. The freeze lasts about 10 seconds and the > laptop computer simply powers off. The error seems to be quite > repeatable. It may or may not have started after a Nvidia graphics > update. I do know after a normal system update in Ubuntu 20.04 on May > 26, my system has been subject to this problem. > > I have purged nvidia drivers and reinstalled them. Didn't matter. > Syslog and journalctl really didn't seem to show anything interesting, > at least to my unsophisticated gaze. Have been a wits end. In the > interim, I moved a lot of my "life" off the laptop onto an RPI4B-8GB > running Raspberry Pi OS 64 bits. Been a difficult transition, > recovering my capabilities, computing-wise. > > I backed up my whole laptop, and decided, perhaps insanely, to do a > fresh install of Pop-OS 22.04. With the base install, I ran into the > same darn wifi issue that initially plagued me with this laptop. After > 2 days of seaching, I found the answer to the slow and constantly > rebooting iwlwifi card was to set powersave =2, which for some darned > reason means powersave is off! I am amazed that this issue still exists > this day and age, I found mentions of it over all Linux distros. The > issue is the wrong microcode is being sent to the wifi adapter, and the > adapter kernel panics when it receives illegal commands from the Linux > OS. You can see it in the syslog very clearly. I changed the powersave > to 2, and the wifi adapter seemingly works fine now. This is the Intel > WiFi 6 AX200/AX201. > > Anyways, even with this brand new installation, and fixed wifi, my > computer crashes with the combination of Arduino IDE 1.8.19, Teensyduino > 1.56, and Ty Commander 0.9.7. > > However, I found that if I use Arduino IDE, and Teensyduino 1.56 only, I > have been able to program my Teensy 4.1 without crashing. Unfortunately, > I'd like to use Ty Commander to enable multiple Teensy's to be debugged. > > I'm looking for some suggestions on how to proceed. > > Is there a way to get or retain more information on system crashes? I > don't even know the true cause of the crash yet. For some reason, I am > having difficulty opening the kernel log. Is it a text file? Or do I > need a special viewer? I can open the syslog without issue. In Pop OS > I don't see multiple or older versions of logs. I don't know why. > Often older logs have a .0 or .1 extension. The log I want to see is > not the one created after the boot following the crash, it is the one > before! > > I'm not sure I really have the skills to deal with linux-crashdump. I > haven't seen a step by step procedure that I feel comfortable enough to > proceed with. The references use a lot of words, re: fiddling with > grub, not so many pictures, and I don't want to really go there without > a really complete script. Is this the path I need to take? > > I could compile Ty Commander with debug binaries, I just need to type > out: cmake -DCMAKE_BUILD_TYPE=Debug ../.. > > Can I run Ty Commander with valgrind, or something like that would > prevent yet another total crash, but perhaps capture something useful? > > > > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
