-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sched_ext: BPF scheduler "lavd" errored, disabling #476
Comments
Never mind. It did in fact fail again a few minutes later.
8986 is another generic workqueue thread, |
Thank you, @anh0516, for reporting the problem. Could you share your rough scenario of how to trigger the watchdog error? I will try to reproduce the problem from my side. |
It just failed randomly while playing 2.4's story content twice. Not reproducible at all, but if I play some more, it could hopefully happen again. What I put in this issue was all the info I have. Do you have any recommendations on debugging or profiling tools that I could set up so I can try to better capture the issue? |
@anh0516 Do you use either multi-CCX or multi-NUMA processor? |
I'm running an R5 5600G, so single-CCX.
…On Sun, Aug 18, 2024, 11:41 PM Changwoo Min ***@***.***> wrote:
@anh0516 <https://github.com/anh0516> Do you use either multi-CCX or
multi-NUMA processor?
—
Reply to this email directly, view it on GitHub
<#476 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATSSZDFUM6OSQDSL7ZLYV73ZSFSPVAVCNFSM6AAAAABMG6FELWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGYYDMOBZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Built from the current main branch, with Linux 6.10.3. It failed while playing Honkai: Star Rail.
The thread in question with ID 86 is
kworker/11:1-mm_percpu_wq
, which says absolutely nothing about what exactly went wrong.I stopped and started the scheduler and it's happy now. I do not have a reliable way to reproduce this and it hasn't happened again, but I figured I would report it anyway as it indicates lavd is not 100% stable in its current condition.
The text was updated successfully, but these errors were encountered: