Crash after flashing FW 2.0.0 #56

DF4OR commented 2025年07月22日 20:37:48 +02:00 (Migrated from github.com)

Hi.
Installed bmputil-cli 1.0.0. from git on an arch box.
Flashed my BMP with the latest firmware, common targets

Got the following output

[2025年07月22日T18:13:42Z INFO bmputil::flasher] Flash complete!
[2025年07月22日T18:13:42Z WARN bmputil::bmp] Possibly spurious error from OS while rebooting probe: hardware fault or protocol violation
Error: ------------[ ✂ cut here ✂ ]------------
Unhandled crash in bmputil-cli v1.0.0
 0: hardware fault or protocol violation
Location:
 src/bmp.rs:83
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Please include all lines down to this one from the cut here
 marker, and report this issue to our issue tracker at
https://github.com/blackmagic-debug/bmputil/issues

Hi. Installed bmputil-cli 1.0.0. from git on an arch box. Flashed my BMP with the latest firmware, common targets Got the following output ``` [2025年07月22日T18:13:42Z INFO bmputil::flasher] Flash complete! [2025年07月22日T18:13:42Z WARN bmputil::bmp] Possibly spurious error from OS while rebooting probe: hardware fault or protocol violation Error: ------------[ ✂ cut here ✂ ]------------ Unhandled crash in bmputil-cli v1.0.0 0: hardware fault or protocol violation Location: src/bmp.rs:83 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. Run with RUST_BACKTRACE=full to include source snippets. Please include all lines down to this one from the cut here marker, and report this issue to our issue tracker at https://github.com/blackmagic-debug/bmputil/issues ```

dragonmux commented 2025年07月23日 05:43:44 +02:00

After getting this message, were you able to run bmputil-cli probe info and see the rebooted probe? If so, then this looks like probably a missing suppression for the multitude of ways an "error" that's not actually an error can get reported up from the OS - one we hadn't run into yet.

After getting this message, were you able to run `bmputil-cli probe info` and see the rebooted probe? If so, then this looks like probably a missing suppression for the multitude of ways an "error" that's not actually an error can get reported up from the OS - one we hadn't run into yet.

DF4OR commented 2025年07月23日 09:13:46 +02:00 (Migrated from github.com)

Yes, I was able to run bmputil-cli and got a proper response with "probe info", showing that the FW has been upgraded.

Yes, I was able to run bmputil-cli and got a proper response with "probe info", showing that the FW has been upgraded.

dragonmux commented 2025年07月24日 07:58:54 +02:00

Ok, that confirms then this is a missing suppression. Please advice which platform you're running bmputil on so we can apply the suppression correctly?

Ok, that confirms then this is a missing suppression. Please advice which platform you're running `bmputil` on so we can apply the suppression correctly?

DF4OR commented 2025年07月24日 08:11:42 +02:00 (Migrated from github.com)

Linux grappa 6.15.7-arch1-1 #1 SMP PREEMPT_DYNAMIC 2025年7月17日 21:05:29 +0000 x86_64 GNU/Linux
aka arch Linux

Architecture: x86_64
CPU Model name: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz

Linux grappa 6.15.7-arch1-1 #1 SMP PREEMPT_DYNAMIC 2025年7月17日 21:05:29 +0000 x86_64 GNU/Linux aka arch Linux Architecture: x86_64 CPU Model name: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz

dragonmux commented 2025年07月24日 08:57:21 +02:00

Please give the branch fix/linux-protocol-fault-suppression a go and let us know how you get on - that should fix this issue. If you can confirm it does, then we'll get it PR'd for the next release.

Please give the branch `fix/linux-protocol-fault-suppression` a go and let us know how you get on - that should fix this issue. If you can confirm it does, then we'll get it PR'd for the next release.