[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2016-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 Roger Pau Monné changed: What|Removed |Added CC|

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #12 from miguelmcl...@gmail.com --- UPDATE: I've been trying to bisect with git, so far I tried only to bisect the changes here: https://github.com/freebsd/freebsd/commits/stable/10/sys/xen/xen_intr.h As they seem to affect

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-02-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #10 from miguelmcl...@gmail.com --- As requested in freebsd-xen mailing list: this is from a core dumb after reboot (saved to /var/crash) KDB: stack backtrace: #0 0x8095b070 at kdb_backtrace+0x60 #1 0x8091f765

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-01-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #9 from miguelmcl...@gmail.com --- One thing to note is that the panic is not related to the mbuf already on the free list anymore: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address