-
Notifications
You must be signed in to change notification settings - Fork 534
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
LOR with panic [mutex nm_kn_lock not owned] on FreeBSD INVARIANTS/WITNESS enabled kernels #314
Comments
Hi, |
Thanks a lot, I tried your diff by applying manually (don't know how I can download it via GH).
Please note that I'm running stable/11 (11.1-Beta1 atm.), with netmap code from HEAD! To double-check. here's the actual diff I applied:
Thanks, -harry |
The patch is ok and it fixes the first panic you reported. To download github code you can just
and a You get a panic again, but this is a different one. What is needed to reproduce it? Can you report it on a separate github issue? |
Try @github not me.
…On 13/06/17 05:05 AM, gharry-bsd wrote:
Bezüglich Vincenzo Maffione's Nachricht vom 12.06.2017 19:51 (localtime):
> Hi,
> I did a fix, can you retry with the latest code?
Thanks, I reported @gh, but don't know if it's needed to re-open the
issue or how to...
-harry
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#314 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA7JJAkWDQ3fHATUWxNaib9uP6wfP0Xks5sDlDXgaJpZM4NzvHm>.
|
Since I'm only netmap user (no developer), I can just report this issue here, no patch unfortunately.
Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219846 for the original report, referencing netmap code base from FreeBSD HEAD (which should be very close to the one here on GH), merged to stable/11.
With WITNESS/INVARIANTS options, there's this panic:
-harry
The text was updated successfully, but these errors were encountered: