You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[APL][JSL] suspend-resume with playback/capture test failure with 'rtcwake: /dev/rtc0: unable to find device: Device or resource busy" #2495
This issue cannot be reproduced by CI in daily test on 09/26, report ID 485.
Kernel Branch: topic/sof-dev
Kernel Commit: 779efb5
SOF Branch: master
SOF Commit: 52e82f4
This issue can be reproduced on APL_UP2_NOCODEC on 10/09/2020, test report ID 519
Kernel Branch: topic/sof-dev
Kernel Commit: c8849c7
SOF Branch: master
SOF Commit: e5d17f3
changed the title [-][JSL] suspend-resume with playback/capture test failure with 'rtcwake: /dev/rtc0: unable to find device: Device or resource busy"[/-][+][APL][JSL] suspend-resume with playback/capture test failure with 'rtcwake: /dev/rtc0: unable to find device: Device or resource busy"[/+]on Oct 10, 2020
Activity
mengdonglin commentedon Oct 10, 2020
This issue cannot be reproduced by CI in daily test on 09/26, report ID 485.
Kernel Branch: topic/sof-dev
Kernel Commit: 779efb5
SOF Branch: master
SOF Commit: 52e82f4
mengdonglin commentedon Oct 10, 2020
This issue can be reproduced on APL_UP2_NOCODEC on 10/09/2020, test report ID 519
Kernel Branch: topic/sof-dev
Kernel Commit: c8849c7
SOF Branch: master
SOF Commit: e5d17f3
[-][JSL] suspend-resume with playback/capture test failure with 'rtcwake: /dev/rtc0: unable to find device: Device or resource busy"[/-][+][APL][JSL] suspend-resume with playback/capture test failure with 'rtcwake: /dev/rtc0: unable to find device: Device or resource busy"[/+]plbossart commentedon Oct 12, 2020
@mengdonglin if the error is still present, why is this issue closed?
mengdonglin commentedon Oct 19, 2020
@plbossart I'm using it to identify non-audio issues in our daily test. But we can only depend on upstream to fix this rtc issue.
plbossart commentedon Oct 19, 2020
Has anyone reported this issue upstream or through Intel Linux channels? if not this could remain for a very long time.