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
The issue report is done badly. Can you please close and open a new one at least with dmesg/logger? If all you have is "I have some issue", what's the value of opening an issue and attracting others' attention?
@wenqingfu When I firstly boot up, I met the timeout issue in initialization. And I found the playback is timeout. At first, I think they are the same issue. So I reported the issue contains 2 issues actually. And after Bard debugged, he found that they are different bugs. So I will file a bug for the playback timeout later. And I will paste the log when I report the issue. The other initialization timeout bug is very hard to reproduce.
The issue report is done badly. Can you please close and open a new one at least with dmesg/logger? If all you have is "I have some issue", what's the value of opening an issue and attracting others' attention?
Activity
wenqingfu commentedon Apr 9, 2019
The issue report is done badly. Can you please close and open a new one at least with dmesg/logger? If all you have is "I have some issue", what's the value of opening an issue and attracting others' attention?
libinyang commentedon Apr 10, 2019
@wenqingfu When I firstly boot up, I met the timeout issue in initialization. And I found the playback is timeout. At first, I think they are the same issue. So I reported the issue contains 2 issues actually. And after Bard debugged, he found that they are different bugs. So I will file a bug for the playback timeout later. And I will paste the log when I report the issue. The other initialization timeout bug is very hard to reproduce.
libinyang commentedon Apr 10, 2019
#808 is created instead of the issue.
io_uring: add a schedule point in io_add_buffers()