https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290925

--- Comment #3 from Michael Gmelin <[email protected]> ---
Thanks for your swift response, Kristof.

The patch applied cleanly and we could build/install a custom kernel using it.
If it will help, only time can tell - we haven't seen this panic before, my
suspicion is that the node in question was overloaded at the time, making the
issue (potentially) more likely to happen. I'm not sure if I will be able to
confirm it to be the ultimate fix, as it's a rare issue for us and I didn't
spend time on creating any reproducible test case.

Do you have any link to the issue that was fixed in
8efd2acf07bc0e1c3ea1f7390e0f1cfb7cf6f86c? I checked the phabricator review, but
it didn't have any details beyond what is in the commit message.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to