<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">The USB mode changes during the
flashing, wonder if that is what is confusing the kernel or not.
During the "wake up the Teensy bootloader mode", I think the USB
is talking to /dev/hidraw4, once the device is programmed, the
Teensy (M7) appears as /dev/ttyACM0. Maybe the kernel can't
handle a lot of these transitions, falsely thinking there's an
error, or there's a goofy hard limit programmed in the kernel...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Can anyone think of why USB
transactions or USB mode switches might trip a trip into lala
land?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 6/13/22 10:20 PM, Bruce Labitt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6f3fd3d0-fca4-98e1-eed2-92c5b3ae3ac1@myfairpoint.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">FWIW, this total system crash has
been isolated to the kernel. Kernel 5.17.5-76051705 crashes.
Which was pushed out to apt on, guess what, May 26, 2022, the
date my computer went to hades. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Kernel 5.15.0-37-generic does not
crash. Kernel 5.18.2 also crashes, only if I use TyCommander,
but not necessarily during a USB flashing. I had 5.18.2 crash
while I was using Firefox, but while Arduino IDE and TyCommander
were active.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Now running on 5.15 and things are
stable.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I know nothing about kernels and
stuff like this. Been forced into it. An average Joe like me
shouldn't have to deal with this kind of thing. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">TyCommander works fine on an RPI4
running Raspberry Pi OS 64 bit, which as I understand it is a
Debian derivative. The kernel is 5.15.30, according to
Wikipedia. Not looking forward to an update of that kernel.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I have no idea how to make a minimal
dying example for any developers...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 6/6/22 4:05 PM, Bruce Labitt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:86c1702b-e8d8-560e-a25d-4a14a11f9544@myfairpoint.net">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix"><font face="monospace">Followup
with SW related items.</font></div>
<div class="moz-cite-prefix"><font face="monospace"><br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace">$ cat
/etc/os-release<br>
NAME="Pop!_OS"<br>
VERSION="22.04 LTS"<br>
ID=pop<br>
ID_LIKE="ubuntu debian"<br>
PRETTY_NAME="Pop!_OS 22.04 LTS"<br>
VERSION_ID="22.04"<br>
HOME_URL=<a class="moz-txt-link-rfc2396E"
href="https://pop.system76.com" moz-do-not-send="true">"https://pop.system76.com"</a><br>
SUPPORT_URL=<a class="moz-txt-link-rfc2396E"
href="https://support.system76.com" moz-do-not-send="true">"https://support.system76.com"</a><br>
BUG_REPORT_URL=<a class="moz-txt-link-rfc2396E"
href="https://github.com/pop-os/pop/issues"
moz-do-not-send="true">"https://github.com/pop-os/pop/issues"</a><br>
PRIVACY_POLICY_URL=<a class="moz-txt-link-rfc2396E"
href="https://system76.com/privacy" moz-do-not-send="true">"https://system76.com/privacy"</a><br>
VERSION_CODENAME=jammy<br>
UBUNTU_CODENAME=jammy<br>
LOGO=distributor-logo-pop-os</font></div>
<div class="moz-cite-prefix"><br>
<font face="monospace">$ uname -a<br>
Linux pop-os 5.17.5-76051705-generic
#202204271406~1653440576~22.04~6277a18 SMP PREEMPT Wed May
25 01 x86_64 x86_64 x86_64 GNU/Linux<br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace"><br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace">Tytools from
<a class="moz-txt-link-freetext"
href="https://github.com/Koromix/tytools"
moz-do-not-send="true">https://github.com/Koromix/tytools</a></font></div>
<div class="moz-cite-prefix"><font face="monospace">Teensyduino
from: <a class="moz-txt-link-freetext"
href="https://www.pjrc.com/teensy/td_download.html"
moz-do-not-send="true">https://www.pjrc.com/teensy/td_download.html</a></font></div>
<div class="moz-cite-prefix"><font face="monospace">Arduino
download from: <a class="moz-txt-link-freetext"
href="https://www.arduino.cc/en/software"
moz-do-not-send="true">https://www.arduino.cc/en/software</a>
V1.8.19.</font></div>
<div class="moz-cite-prefix"><font face="monospace">Data on
Teensy 4.1 microcontroller (Arm M7, NXP </font><font
face="monospace"><font face="monospace">IMXRT1060</font>) <a
class="moz-txt-link-freetext"
href="https://www.pjrc.com/store/teensy41.html"
moz-do-not-send="true">https://www.pjrc.com/store/teensy41.html</a><br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace">IMXRT1060
Processor Reference Manual <a class="moz-txt-link-freetext"
href="https://www.pjrc.com/teensy/IMXRT1060RM_rev3.pdf"
moz-do-not-send="true">https://www.pjrc.com/teensy/IMXRT1060RM_rev3.pdf</a></font></div>
<div class="moz-cite-prefix"><font face="monospace"><br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace">Me, I am
writing code to make an electronic lead screw for my lathe.
Motor control works with NEMA-24 stepper motor and rotary
encoder. Working on the UI on a touch panel tft display.
Or, I was, until my laptop crashed...<br>
</font></div>
<div class="moz-cite-prefix"><font face="monospace"><br>
</font></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 6/6/22 3:47 PM, Bruce Labitt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:287d9413-44da-ccc5-99ae-be9e37787f42@myfairpoint.net">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p><font face="monospace">Will try my best. It's tough to
keep your cool when your life, ie. your own computer is
crapping out. Much easier, when it is someone else's.
Pity the machine is not up at the moment. Been busy
transferring my life to an RPI4, which hasn't been as easy
as it seems like it should. Writing this on my RPI4-8GB
with RaspiOS-64bit.<br>
</font></p>
<p><font face="monospace">Laptop in question, with the
problem: System76 Oryx6. 32GB RAM, 1TB SSD Samsung 970 EVO
Plus<br>
</font></p>
<p><font face="monospace">HW Details:</font></p>
<p><font face="monospace">=================================================================================================================================<br>
</font></p>
<font face="monospace">Intel-10875H CPU, Intel HM470 chipset,
MX25L12872F flash chip running System76 Open Firmware BIOS,
</font><br>
<font face="monospace">ITE IT5570E running<span> </span><a
href="https://github.com/system76/ec"
style="text-decoration: none; color: var(--links);"
moz-do-not-send="true">System76 EC</a>, NVIDIA GeForce RTX
2060, 15.6" 1920x1080@144Hz LCD, LCD panel: Panda LM156LF1F
(or equivalent)</font><br>
<font face="monospace">External video outputs: 1x HDMI, 1x
Mini DisplayPort 1.4, 1x DisplayPort over USB-C</font><br>
<font face="monospace">Memory</font><font face="monospace"> Up
to 64GB (2x32GB) dual-channel DDR4 SO-DIMMs @ 3200 MHz -- 32
GB</font><br>
<p><font face="monospace">Networking:</font><font
face="monospace"> Gigabit Ethernet,</font><font
face="monospace">M.2 PCIe/CNVi WiFi/Bluetooth,</font><font
face="monospace"> Intel Wi-Fi 6 AX200/AX201</font><font
face="monospace"><br>
</font></p>
<p><font face="monospace">Power</font><font face="monospace">:
180W (19.5V, 9.23A) DC-in port,</font><font
face="monospace"> Barrel size: 5.5mm (outer), 2.5mm
(inner),</font><font face="monospace"> Included AC
adapter: Chicony A17-180P4A,</font><font face="monospace">
AC power cord type: IEC C5,</font><font face="monospace">
73Wh 3-cell battery</font><font face="monospace"> <br>
</font></p>
<p><font face="monospace">Sound:</font><font face="monospace">
Internal speakers & microphone,</font><font
face="monospace"> Combined headphone & microphone
3.5mm jack,</font><font face="monospace"> Combined
microphone & S/PDIF (optical) 3.5mm jack,</font><font
face="monospace"> HDMI, Mini DisplayPort, USB-C
DisplayPort audio</font><font face="monospace"><br>
</font></p>
<p><font face="monospace">Storage:</font><font
face="monospace"> 1x M.2 (PCIe NVMe or SATA) - NVME 1 TB
installed</font><font face="monospace">, 1x M.2 (PCIe NVMe
only) - empty,</font><font face="monospace"> MicroSD card
reader</font><font face="monospace"><br>
</font></p>
<p><font face="monospace">USB:</font><font face="monospace">
3x USB 3.2 Gen 1 Type-A,</font><font face="monospace"> 1x
USB Type-C with Thunderbolt 3</font><font face="monospace"><br>
</font></p>
<p><font face="monospace">Dimensions:</font><font
face="monospace"> 15": 35.75cm x 23.8cm x 1.98cm, 1.99kg</font></p>
<p><font face="monospace">=== End HW details
==============================================================================================================<br>
</font></p>
<p><font face="monospace">Pop-OS-64 bit. 22.04. Fresh
install over existing Ubuntu 20.04 LTS.<br>
</font></p>
<p><font face="monospace">I need to reboot the computer to get
the kernel stuff. Will followup with uname -a.<br>
</font></p>
<p><font face="monospace">Problem occurs when using USB to
program Teensy 4.1 microcontroller. Active programs at
time of crash = Arduino IDE V 1.8.19, Teensyduino 1.56
(required to allow Arduino to recognize and program Teensy
microcontrollers), and Tytools, 0.9.7, which is a tool to
program and manage Teensy processors. Prior to 26 May
2022, this all worked flawlessly.</font></p>
<p><font face="monospace">And, the above SW does work
flawlessly on the RPI4B, running RaspberryPiOS-64bit, but
not on my laptop. On my laptop I get system crashes.<br>
</font></p>
<p><font face="monospace">Only clues I have found are in
syslog, and dmesg, but they only show some normal USB
transactions, then the computer powering up again.<br>
</font></p>
<p><font face="monospace">Thanks Ben, for at least answering
(humoring?) me. Been an awful week with this crash.
These crashes are so bad, that there's practically nothing
in the logs. Last entry is using the USB port. And the
power turns off. This is a stab at it. Let me know if
there's anything else I need to add. Beats me what the
crucial details are, if I knew them, it would have been
fixed by now. <br>
</font></p>
<p><font face="monospace">The title of the thread was really
about how to go about doing the debugging. The
methodology. It's improbable that anyone else would have
experienced this particular crash type.<br>
</font></p>
<p><br>
</p>
<div class="moz-cite-prefix">On 6/6/22 14:09, Ben Scott wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAE=no6FdGQMKVLTJAnzK+KM6Tu5wei1u-zCVdvmk2-S2QMGkMg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">On Sun, Jun 5, 2022 at 12:09 PM Bruce Labitt
<a class="moz-txt-link-rfc2396E" href="mailto:bruce.labitt@myfairpoint.net" moz-do-not-send="true"><bruce.labitt@myfairpoint.net></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I am experiencing severe Linux crashes ...
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Long meandering messages with critical details hidden throughout and
others omitted entirely will reduce the likelihood that others will
give you help for free. (Or even when paid.)
In particular, specify what hardware you have, and the software you're
running, in one place. If it's a scavenger hunt just to find that
information you'll get a poor response. I didn't see any mention of
the model of machine, for example. List major components with model
or type (CPU model and speed, RAM size, type and size of storage,
model/type video controller, etc.). You mention distribution and
version, which is good, but also please provide kernel version. Also
include steps to reproduce (when it happens, when it doesn't),
commands you've tried, places you've looked for files, error messages
received, etc., etc.
I know you've been around long enough that you've seen plenty of bug
reports and knowledge base articles and the like. Follow their
example.
<a class="moz-txt-link-freetext" href="http://www.catb.org/~esr/faqs/smart-questions.html" moz-do-not-send="true">http://www.catb.org/~esr/faqs/smart-questions.html</a>
-- Ben
_______________________________________________
gnhlug-discuss mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:gnhlug-discuss@mail.gnhlug.org" moz-do-not-send="true">gnhlug-discuss@mail.gnhlug.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" moz-do-not-send="true">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gnhlug-discuss mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:gnhlug-discuss@mail.gnhlug.org" moz-do-not-send="true">gnhlug-discuss@mail.gnhlug.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" moz-do-not-send="true">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a>
</pre>
</blockquote>
<p><br>
</p>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gnhlug-discuss mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:gnhlug-discuss@mail.gnhlug.org" moz-do-not-send="true">gnhlug-discuss@mail.gnhlug.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" moz-do-not-send="true">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a>
</pre>
</blockquote>
<p><br>
</p>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gnhlug-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnhlug-discuss@mail.gnhlug.org">gnhlug-discuss@mail.gnhlug.org</a>
<a class="moz-txt-link-freetext" href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>