Opened 6 years ago

Closed 5 years ago

#381 closed defect (fixed)

Power status events ignored

Reported by: Nytowl Owned by: mickey
Priority: major Milestone: milestone5.5
Component: framework/oeventsd Version:
Keywords: Cc: angus.ainslie@…, seba.dos1@…, ayers@…

Description

possible race condition during power up that causes oeventsd to ignore power status signals

Attachments (1)

frameworkd.log.gz (63.8 KB) - added by Nytowl 5 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 5 years ago by daniel

Could you please explain some more, maybe provide logs?

comment:2 Changed 5 years ago by Nytowl

When the phone starts up none of the power events are honoured. This is because oeventds failed to start because one of it's startup conditions was bad or missing.

I showed Mickey the log but I don't seem to have a copy of it anywhere

Changed 5 years ago by Nytowl

comment:3 Changed 5 years ago by Nytowl

  • Cc angus.ainslie@… added
  • Milestone set to milestone5.5

oeventsd requests the display resource before the resource is registered. The yaml rule that causes this is :

-

while: PowerStatus?()
filters: Not(HasAttr?(status, "discharging"))
actions: OccupyResource?(Display)

comment:4 follow-up: Changed 5 years ago by mickey

The action needs to be tought to wait until the resource is present before trying to access it.

comment:5 Changed 5 years ago by mickey

  • Owner changed from jluebbe to mickey
  • Status changed from new to assigned

comment:6 Changed 5 years ago by dos

  • Cc seba.dos1@… added

comment:7 in reply to: ↑ 4 Changed 5 years ago by dos

Replying to mickey:

The action needs to be tought to wait until the resource is present before trying to access it.

Looks like teaching it that should fix #435 as well.

comment:8 Changed 5 years ago by ayers

  • Cc ayers@… added

comment:9 Changed 5 years ago by mickey

  • Status changed from assigned to in_testing

comment:10 Changed 5 years ago by mickey

  • Resolution set to fixed
  • Status changed from in_testing to closed

The new "intelligent" OccupyResource? action has fixed this.

Note: See TracTickets for help on using tickets.