-
Notifications
You must be signed in to change notification settings - Fork 41
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
To reproduce #452, if Spotify is playing, WDT may timeout.(rarely, 2 times/1 hour reproduce.)
I M 23:07:29.101 kernel_le_client.c:312> Service changed Indication: type: 1 status: 0
D M 23:07:29.105 kernel_le_client.c:288> Found an instance of DIS at 0xa-0xe!
D M 23:07:29.105 dis.c:38> In DIS service discovery CB
I M 23:07:29.105 kernel_le_client.c:285> Found an instance of PPoG at 0x19-0x1f!
D M 23:07:29.109 kernel_le_client.c:288> Found an instance of ANCS at 0x2d-0x36!
D M 23:07:29.109 ancs.c:815> In ANCS service discovery CB
D M 23:07:29.113 gatt_client_subscriptions.c:640> Added BLE subscription for handle 0x35
D M 23:07:29.113 gatt_client_subscriptions.c:640> Added BLE subscription for handle 0x32
D M 23:07:29.117 kernel_le_client.c:288> Found an instance of AMS at 0x37-0x42!
D M 23:07:29.117 ams.c:573> In AMS service discovery CB
D M 23:07:29.117 gatt_client_subscriptions.c:640> Added BLE subscription for handle 0x3d
D B 23:07:29.152 gatt_client_discovery.c:208> Subscribed to service changed
D M 23:07:29.214 gatt_client_subscriptions.c:640> Added BLE subscription for handle 0x1d
I M 23:07:29.273 ancs.c:789> Hurray! ANCS subscribed: 1
I M 23:07:29.332 ancs.c:789> Hurray! ANCS subscribed: 0
I M 23:07:29.421 ams.c:618> Hurray! AMS subscribed
I M 23:07:29.425 music.c:109> Music server connected: AMS
D M 23:07:29.546 ams.c:653> AMS Registered for entity_id=0
23:07:31.284 D M 23:07:29.554 ams.c:665> 0000 00 01 00 31 2c 31 2e 30 2c 35 30 2e 38 31 38 ...1,1.0 ,50.818
D M 23:07:29.554 ams.c:338> Playback info value update 0=1
D M 23:07:29.554 ams.c:338> Playback info value update 1=100
D M 23:07:29.554 ams.c:338> Playback info value update 2=50818
23:07:31.312 D M 23:07:29.578 ams.c:665> 0000 00 02 00 30 2e 31 37 31 38 37 35 ...0.171 875
D B 23:07:29.582 advert.c:372> BLE_GAP_EVENT_SUBSCRIBE
D B 23:07:29.582 advert.c:261> prv_handle_subscription_event: connhandle: 1 attr:31 notify:0/1 indicate:0/0
I M 23:07:29.585 session.c:169> Session event: is_open=1, destination=S, app_uuid={00000000-0000-0000-0000-000000000000}
W ? 23:07:35.453 task_watchdog.c:136> Watchdog feed failed, last feed 5000ms ago, current status 0x182 mask 0x183
W ? 23:07:35.453 task_watchdog.c:130> Task <KernelMain> stuck: LR: 12097771 PC: 1209687e
W ? 23:07:35.972 task_watchdog.c:136> Watchdog feed failed, last feed 5500ms ago, current status 0x182 mask 0x183
W ? 23:07:35.976 task_watchdog.c:130> Task <KernelMain> stuck: LR: 12097771 PC: 1209687e
W ? 23:07:36.496 task_watchdog.c:136> Watchdog feed failed, last feed 6000ms ago, current status 0x182 mask 0x183
W ? 23:07:36.496 task_watchdog.c:130> Task <KernelMain> stuck: LR: 12097771 PC: 1209687e
D ? 23:07:35.453 task_watchdog.c:221> WD: low priority ISR
D ? 23:07:35.972 task_watchdog.c:221> WD: low priority ISR
D ? 23:07:36.496 task_watchdog.c:221> WD: low priority ISR
23:07:38.219 * ? 23:07:36.500 die.c:49> Resetting!
23:07:38.220 * ? 23:07:36.500 core_dump.c:0> Starting core dump
23:07:38.221 * ? 23:07:36.503 core_dump.c:0> CD: starting
23:07:38.228 * ? 23:07:36.503 core_dump.c:0> CD: Checking: 0x12321000
23:07:43.704 * ? 23:07:41.976 core_dump.c:0> CD: Saving to: 0x124a0000
23:07:44.057 * ? 23:07:42.339 core_dump.c:0> CD: Th info IDLE
23:07:44.058 * ? 23:07:42.339 core_dump.c:0> CD: Th info NimbleHost
23:07:44.059 * ? 23:07:42.339 core_dump.c:0> CD: Th info KernelMain
23:07:44.060 * ? 23:07:42.343 core_dump.c:0> CD: Th info App <Launcher>
23:07:44.061 * ? 23:07:42.343 core_dump.c:0> CD: Th info NewTimer
23:07:44.063 * ? 23:07:42.343 core_dump.c:0> CD: Th info KernelBG
23:07:44.064 * ? 23:07:42.343 core_dump.c:0> CD: Th info NimbleHCI
23:07:44.073 * ? 23:07:42.347 core_dump.c:0> CD: Th info PULSE
23:07:44.074 * ? 23:07:42.347 core_dump.c:0> CD: Th info ISR
23:07:44.075 * ? 23:07:42.347 core_dump.c:0> CD: completed
* M 23:07:43.242 main.c:138> PebbleOS
* M 23:07:43.246 main.c:140> v4.9.81-2-g6373f528-dirty(slot0)
* M 23:07:43.246 main.c:145> (c) 2013-2025 The PebbleOS contributors
* M 23:07:43.250 main.c:146>
D M 23:07:43.617 new_timer.c:126> NT: Initializing
E M 23:07:44.710 i2c.c:466> I2C Error on bus i2c1
E M 23:07:44.718 i2c.c:533> Read failed on bus i2c1
E M 23:07:44.718 vibe_aw86225.c:173> Failed to read AW86225 chip ID
I M 23:07:44.750 qspi.c:167> Flash is GD25Q256E
D M 23:07:44.875 cst816.c:215> cst816 fw version:0x4
D M 23:07:44.878 lsm6dso.c:287> LSM6DSO: Sensor detected successfully (WHO_AM_I=0x6c)
D M 23:07:44.886 lsm6dso.c:376> LSM6DSO: Initialization complete
D M 23:07:44.914 mmc5603nj.c:64> MMC5603NJ: Initialization complete
Expected Behavior
WDT should not timeout.
Steps To Reproduce
Play music on Spotify, and try to reproduce #452 , WDT may timeout and system will reset.
Version
Host OS
Ubuntu 24.04 LTS
Watch
Pebble Time 2 (Obelix)
Anything else?
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working