Over the weekend I was doing a race and my 935 crashed/rebooted multiple times, which is very unusual in my experience. It was a triathlon which I was tracking in the Triathlon multisport mode. I noticed all of the reboots, but I also verified them happening by looking at the resulting activities and seeing jumps in the tracking. I'm hoping that these crashes get auto-reported to Garmin on the next successful sync, but a) I'm not sure if that actually happens, and b) since I have another race coming up I'd like to figure out how I can avoid having more crashes happen.
Two of the crashes were during the first half of the bike portion and one was in the middle of the run.
For the bike, it was normal Bike profile. I don't have any CIQ data fields in that profile.
- I started riding as usual, but noticed that I forgot to turn on my two Cycliq lights/cameras. I managed to turn the headlight on manually but I couldn't reach the taillight. Then I remembered that I have the lights connected to my 935 but disabled by default because I don't want them coming on if I'm running/etc. I went to Sensors and enabled the lights. This brought up the usual "Forming network" notices on the watch, which happened multiple times throughout the ride, but the taillight did come on. I left that setting in place for the whole ride.
- I also was worried about some of the turns on the course, some of which were sharp and/or not obvious. So I went to Navigation and selected the course. That seemed to start up fine and I could see the map, upcoming turns, and I'd get alerts. After the two crashes, and seeing that the race had made the turns more obvious than they were the day before, I turned off navigation, and there were no more crashes after that point. Therefore I feel like navigation or the course data file caused the crashes, but this could be circumstantial.
The run was normal Run profile. I have 2 CIQ data fields in use (Stryd (https://apps.garmin.com/en-US/apps/18fb2cf0-1a4b-430d-ad66-988c847421f4) and Run Power (https://apps.garmin.com/en-US/apps/a054f515-576a-4a28-b8e5-87987ba737e1)).
- The run was going fine on my default data screen (no CIQ). At some point I wanted to see the Run Power CIQ screen (single whole screen field w/ multiple configurable data displays), so I scrolled to it. As I recall, I had hit the down button but instead of the scroll animation the watch rebooted. When it came back up and resumed, the CIQ fields had been reset to the default Timer field. I didn't do anything about it and continued the race. There were no more crashes. Neither field has been updated recently (latest was June 2021) and I've done dozens of runs with them. That said, I did have some problems changing Run Power settings a few days before the race, and given the crash happened as I was trying to scroll to that screen, I feel it's likely the field/config caused the crash.
935 (SW 21.00) and fields/apps are all up-to-date (I check for updates fairly frequently).
So, is there some way I can actually debug this? I poked around at the 935's filesystem and found the DEBUG directory. There is an ERR_LOG.TXT from today (the watch crashed/rebooted when I plugged it into the PC) and ERR_LOG.BAK (dated from the race). I didn't find any other useful or recent error/log type files.
I can't seem to attach the log files to this post, so I'll just include them below since they're not that big.
Thanks.
ERR_LOG.TXT (today):
2691 (Forerunner 935) SW ver: 2100 Build Type: RELEASE Commit:411945a33c8a05df9cd2f1c12eb8016bcf860647 ESN: 3959316821 08/12/21 20:12:02 AP PWR RST CTRL: 0x00400028 POR ERR_LOG.BAK (dated Sunday, race day): 2691 (Forerunner 935) SW ver: 2100 Build Type: RELEASE Commit:411945a33c8a05df9cd2f1c12eb8016bcf860647 ESN: 3959316821 08/08/21 08:39:57 RTL errnum: 0x00f r0: 0x2007cb10 r1: 0x00080f71 r2: 0x00000818 r3: 0x000000a9 r4: 0x0001c640 Stack frame PC, SP: 0x000c1999, 0x2007c8d8 Call Stack - SP at 0x2007c8d8: 0x00086937 0x0000b969 0x00080f71 0x00080f71 0x00080f71 0x000a34ed 0x00080f71 0x000a2ea7 0x00080f71 0x00080061 0x0008054d 0x0008028d 0x000a24e5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 Uptime: 14240692 2691 (Forerunner 935) SW ver: 2100 Build Type: RELEASE Commit:411945a33c8a05df9cd2f1c12eb8016bcf860647 ESN: 3959316821 08/08/21 08:47:01 RTL errnum: 0x00f r0: 0x2007cb10 r1: 0x00080f71 r2: 0x00000818 r3: 0x000000aa r4: 0x0001d5d8 Stack frame PC, SP: 0x000c1999, 0x2007c8d8 Call Stack - SP at 0x2007c8d8: 0x00086937 0x00066151 0x0000b969 0x00080f71 0x000651b1 0x00080f71 0x00080f71 0x000a34ed 0x00080f71 0x000a2ea7 0x00080f71 0x00080061 0x0008054d 0x000a24e5 0x0008028d 0x000a24e5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 Uptime: 418129 2691 (Forerunner 935) SW ver: 2100 Build Type: RELEASE Commit:411945a33c8a05df9cd2f1c12eb8016bcf860647 ESN: 3959316821 08/08/21 12:11:25 RTL errnum: 0x001 r0: 0x2005c310 r1: 0x00000200 r2: 0x0008c52d Stack frame PC, SP: 0x000c1999, 0x2005bfd0 Call Stack - SP at 0x2005bfd0: 0x00086937 0x0000b98b 0x0008c52d 0x0008c52d 0x00086add 0x000a44c1 0x0008c52d 0x000a34ed 0x0008c52d 0x000a58a5 0x0008c52d 0x00065b1d 0x000660f3 0x00060019 0x0000ffff 0x000659c7 0x00067a29 0x00067563 0x000673d1 0x00075f79 0x00075fd1 0x00075fdd 0x000a576f 0x000da6f7 0x000a24e5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 Uptime: 12257009