Ticket #9733 (closed Bug Report - Hang/Deadlock: Fixed)
Opened 2 years ago
Last modified 21 months ago
Putting FE to S3 sleep deadlocks BE
| Reported by: | warpme@… | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.25 |
| Component: | MythTV - General | Version: | 0.24-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
My sys is 3x ION FE on minimyth derivate + separate BE. 0.24-fixes git20110416 on ArchLinux?.
I'm using S3 suspend for my disk-less FEs.
I have issues with BE deadlock when any of FE is put to S3 sleep.
Use case:
2 FE
-FE1, FE2 are running
-Sent FE1 to S3 sleep, keep FE2 idle
-After some time (15-30 min) try start LiveTV on FE2.
-FE2 behaves like with deadlocked BE (famous "cant determine MYTH_PROTO_VERSION...." in logs)
-Resume FE1
-FE2 LiveTV now works again as expected
Above scenario is repeatable.
BE, FE logs attached. Also gdb backtrace from deadlocked BE is attached.
br
Attachments
Change History
Changed 2 years ago by warped <warpme@…>
- Attachment backtrace.txt added
comment:1 Changed 2 years ago by beirdo
- Type changed from Bug Report - General to Bug Report - Hang/Deadlock
comment:2 Changed 21 months ago by warpme@…
Hi, After switching to latest master I didn't observe this issue on 24/7 working production system. From my perspective we can close this ticket with status resolved.
comment:3 Changed 21 months ago by beirdo
- Status changed from new to closed
- Resolution set to Fixed
- Milestone changed from unknown to 0.25
backtrace of deadlocked BE