-
Notifications
You must be signed in to change notification settings - Fork 1.3k
ESP32-S2 linux crash on circuitpython reboot #3336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes it's intel based system, and circuitpython is connected Bus 001 Device 005: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub processor : 1 |
Not sure if that helps, but I stopped having those problems with SAMD21 after downgrading my kernel to |
This sounds similar to #3268, which occurs on other platforms. See the links there to the linux-usb mailing list and to the Launchpad bug report. There may be multiple crash causes. I fixed one, which is that People have also seen crashes on disconnect (e.g., pulling the USB plug). It's not clear whether this is filesystem-based, or due to other USB devices disappearing abruptly. I think this behavior is less excusable on the kernel's part, because anyone could pull a USB drive or device out at any time. @deshipu I tried multiple kernels for the I have ameliorated these crashes to some extent, but not completely eliminated them, by interposing a cheap USB2 hub. |
@dhalbert in my case it was a crash on disconnect or hard reset |
Is there some option to prevent USB input devices from being They appear by default even though no user's python code |
I'm sure I used that option in my PewPew boards to disable midi and hid, but it seems that it's not there anymore... |
It used to be |
See
You can adjust which HID devices are present as well. The full list is: The USB devices are enumerated after |
EDIT to previous comment: "now", not "not" |
Do we believe we can fix this? Or should we make it a long term issue? Is it still an issue? |
Long term ugly bug!
I pull images for WROVER-S2 on daily basis and this crash is still here.
If I develop something, 1 linux crash per day is minimum :)
If I just try few commands if it works, no crash.
…On 9/30/20, Scott Shawcroft ***@***.***> wrote:
Do we believe we can fix this? Or should we make it a long term issue? Is it
still an issue?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#3336 (comment)
|
I found a reliable way to crash my Pi4: (Save your valuable work before trying this!)
I hope this helps! |
I'm going to mark this as a dupe of #3268. It is a Linux issue which they don't want to fix. We can try to ameliorate it by perhaps inserting some delays before switching from one filesystem to another, but it also occurs when a filesystem disappears, it seems. |
SMP Debian 5.7.10-1 (2020-07-26) x86_64 GNU/Linux
crashes often when using ESP32-S2 and it's starting to become annoying.
Kernel just freezes, I can't see nothing like register dump in syslog to see
in which function and source line crash happened. I can reproduce crash
only in gnome environment which has nice file manager that mouns S2 disk.
If I boot only to textual console, linux won't crash then.
Normal workflow that triggers crash every cca 10-20 retries is this:
cp demo.py /media/user/1234-5678/
screen /dev/ttyACM0
The easiest way to provoke crash is this, it's repeatable and aways the same
syntax errors and crash to otherwise correct syntax:
import gc; gc.collect(); gc.mem_free()
63792
import gc; gc.collect(); gc.mem_free()
Traceback (most recent call last):
File "", line 1
SyntaxError: invalid syntax
import gc; gc.collect(); gc.mem_free()
63536
import gc; gc.collect(); gc.mem_free()
Traceback (most recent call last):
File "", line 1
SyntaxError: invalid syntax
import gc; gc.collect(); gc.mem_free()
63536
circuitpython crashed and sometimes follows by linux crash also
I know this is not directly to blaim circuitpython but
for circuitpython to be user-friendly, adafruit developers would be
the best in coordinating with linux developers to locate this bug and help
them fixing it sooner.
The text was updated successfully, but these errors were encountered: