[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 Roger Pau Monné changed: What|Removed |Added CC||h...@barafranca.com --- Comment #14 from Roger Pau Monné --- *** Bug 182884 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 miguelmcl...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Severity|Affects Only Me |Affects Many People Status|In Progress |Closed --- Comment #13 from miguelmcl...@gmail.com --- Fixed by https://svnweb.freebsd.org/base?view=revision&revision=299542 should be MFC to stable/10 soon so closing this :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
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 netback/front and xn_intr All three commit after and including the following are "bad": Improve the Xen para-virtualized device infrastructure of FreeBSD: … gibbs authored on Oct 19, 2010 831bbfa The one before is the same "version" runnning on stable/9 it seems. also disabling txcsum stops the panic when I try ssh-in but I stil see the "xn_txeof: WARNING: response is -1" message and it eventually times out. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #11 from miguelmcl...@gmail.com --- Is the kgbd info helpful? Any extra info I can add? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
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 at panic+0x155 #2 0x80d1ee1f at trap_fatal+0x38f #3 0x80d1f138 at trap_pfault+0x308 #4 0x80d1e79a at trap+0x47a #5 0x80d044b2 at calltrap+0x8 #6 0x80802804 at xn_intr+0x74 #7 0x808f257b at intr_event_execute_handlers+0xab #8 0x808f29c6 at ithread_loop+0x96 #9 0x808f019a at fork_exit+0x9a #10 0x80d049ee at fork_trampoline+0xe Uptime: 54s Dumping 77 out of 727 MB:..21%..42%..63%..83% #0 doadump (textdump=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) i li *xn_intr+0x74 Line 1209 of "/usr/src/sys/dev/xen/netfront/netfront.c" starts at address 0x808027fc and ends at 0x80802809 . Current language: auto; currently minimal If relevant bt: (kgdb) bt #0 doadump (textdump=) at pcpu.h:219 #1 0x8091f3e2 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:452 #2 0x8091f7a4 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0x80d1ee1f in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:865 #4 0x80d1f138 in trap_pfault (frame=0xfe2b2920, usermode=) at /usr/src/sys/amd64/amd64/trap.c:676 #5 0x80d1e79a in trap (frame=0xfe2b2920) at /usr/src/sys/amd64/amd64/trap.c:440 #6 0x80d044b2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #7 0x80800c82 in xn_txeof (np=0xfe9e4000) at /usr/src/sys/dev/xen/netfront/netfront.c:1137 #8 0x80802804 in xn_intr (xsc=0xfe9e4000) at /usr/src/sys/dev/xen/netfront/netfront.c:1209 #9 0x808f257b in intr_event_execute_handlers ( p=, ie=0xf800025db700) at /usr/src/sys/kern/kern_intr.c:1264 #10 0x808f29c6 in ithread_loop (arg=0xf800025d5520) at /usr/src/sys/kern/kern_intr.c:1277 #11 0x808f019a in fork_exit ( ---Type to continue, or q to quit--- callout=0x808f2930 , arg=0xf800025d5520, frame=0xfe2b2c00) at /usr/src/sys/kern/kern_fork.c:996 #12 0x80d049ee in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #13 0x in ?? () -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: [Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
load the kernel in to gdb or kgdb and type: i li *xn_intr+0x74 to get the offending line number On Sat, Jan 31, 2015 at 6:44 AM, wrote: > 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 = 0x3 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0x80800c65 > stack pointer = 0x28:0xfe2b29d0 > frame pointer = 0x28:0xfe2b2a20 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 12 (irq771: xn0) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0x8095b050 at kdb_backtrace+0x60 > #1 0x8091f745 at panic+0x155 > #2 0x80d1edff at trap_fatal+0x38f > #3 0x80d1f118 at trap_pfault+0x308 > #4 0x80d1e77a at trap+0x47a > #5 0x80d04492 at calltrap+0x8 > #6 0x808027e4 at xn_intr+0x74 > #7 0x808f255b at intr_event_execute_handlers+0xab > #8 0x808f29a6 at ithread_loop+0x96 > #9 0x808f017a at fork_exit+0x9a > #10 0x80d049ce at fork_trampoline+0xe > > -- > You are receiving this mail because: > You are the assignee for the bug. > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
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 = 0x3 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80800c65 stack pointer = 0x28:0xfe2b29d0 frame pointer = 0x28:0xfe2b2a20 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (irq771: xn0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x8095b050 at kdb_backtrace+0x60 #1 0x8091f745 at panic+0x155 #2 0x80d1edff at trap_fatal+0x38f #3 0x80d1f118 at trap_pfault+0x308 #4 0x80d1e77a at trap+0x47a #5 0x80d04492 at calltrap+0x8 #6 0x808027e4 at xn_intr+0x74 #7 0x808f255b at intr_event_execute_handlers+0xab #8 0x808f29a6 at ithread_loop+0x96 #9 0x808f017a at fork_exit+0x9a #10 0x80d049ce at fork_trampoline+0xe -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #8 from miguelmcl...@gmail.com --- PARTICULARY THIS: +/* GSO Prefix descriptor. */ +#define _NETRXF_gso_prefix (4) +#define NETRXF_gso_prefix (1U<<_NETRXF_gso_prefix) + GSO is not supported by the netbsd backend I had the same issue with Windows GPLPV drivers a while back (see: http://mail-index.netbsd.org/port-xen/2013/12/12/msg008172.html) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #7 from miguelmcl...@gmail.com --- Dunno if this will help in anyway... I lack C skills and I certainly don't know much about the Xen code... In anycase I will post my findings: I decided to compare the changes on 9 and 10, because 9 is working for me. I noticed that warning comes from netfront.c: if (txr->status != NETIF_RSP_OKAY) { printf("%s: WARNING: response is %d!\n", __func__, txr->status); } So I decided to try and find out whats "NETIF_RSP_OKAY", which apears to "come from" sys/xen/interface/io/netif.h This is the diff from 9 to 10 (stable) src, could any of this changes be the cause!? % diff -u sys/xen/interface/io/netif.h /tmp/netif.h --- sys/xen/interface/io/netif.h2014-04-11 01:41:58.0 +0100 +++ /tmp/netif.h2015-01-31 06:42:58.0 + @@ -41,7 +41,7 @@ /* * This is the 'wire' format for packets: * Request 1: netif_tx_request -- NETTXF_* (any flags) - * [Request 2: netif_tx_extra] (only if request 1 has NETTXF_extra_info) + * [Request 2: netif_tx_extra] (only if request 1 has NETTXF_extra_info) * [Request 3: netif_tx_extra] (only if request 2 has XEN_NETIF_EXTRA_FLAG_MORE) * Request 4: netif_tx_request -- NETTXF_more_data * Request 5: netif_tx_request -- NETTXF_more_data @@ -173,6 +173,10 @@ #define _NETRXF_extra_info (3) #define NETRXF_extra_info (1U<<_NETRXF_extra_info) +/* GSO Prefix descriptor. */ +#define _NETRXF_gso_prefix (4) +#define NETRXF_gso_prefix (1U<<_NETRXF_gso_prefix) + struct netif_rx_response { uint16_t id; uint16_t offset; /* Offset in page of start of received packet */ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #6 from miguelmcl...@gmail.com --- And since FreeBSD10 comes with XENHVM precompiled/loaded any freebsd10+ guest starts in a none working state! :( I should clarify that statement by saying: It start in a non working sate in regards to network. tks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #5 from miguelmcl...@gmail.com --- NOTE: NetBSD just announced support for Xen 4.5. I've tested with FreeBSD 9.3 which works fine but anything 10.0+ fails with this error! And since FreeBSD10 comes with XENHVM precompiled/loaded any freebsd10+ guest starts in a none working state! :( -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: kern/188369: [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)
Old Synopsis: FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1) New Synopsis: [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1) State-Changed-From-To: open->open State-Changed-By: linimon State-Changed-When: Sun Apr 20 01:48:45 UTC 2014 State-Changed-Why: Over to maintainer(s). Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 01:48:45 UTC 2014 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=188369 ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: xn_txeof: WARNING: response is -1!
On 05/29/11 14:11, K. Macy wrote: > Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this > problems? It sounds almost as if xend isn't configuring the domain > properly. > Hello, I'm not sure about Linux but a NetBSD 5.1 PV domU works fine. Others are running Linux PV on NetBSD afaik. Maybe http://www.freebsd.org/cgi/query-pr.cgi?pr=143340 is the same issue? (it may be of interest to note that pr is still open - maybe the patch does work and one less pr to worry about :)) I do get "packet corrupt" until txc and rxc are disabled, with both off then the xn_txeof warning is logged and the ssh connection seems to hang. Couldn't apply the patch in the link, the text appears to be mangled. I tried to correct it, but no luck. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: xn_txeof: WARNING: response is -1!
Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this problems? It sounds almost as if xend isn't configuring the domain properly. -Kip On Sun, May 29, 2011 at 1:02 PM, Hugo Silva wrote: > On 05/25/11 17:20, Hugo Silva wrote: >> On 05/24/11 21:14, Hugo Silva wrote: >>> On 05/24/11 14:45, Hugo Silva wrote: Trying to ssh to the VM produces the error in the subject line on the FreeBSD domU; It's impossible to login. >>> >>> Some more information for those looking to reproduce this: the above is >>> with rxcsum and txcsum disabled in the xn interface: Without that, the >>> ssh client on the other side would just say 'Disconnected: Packet corrupt'. >>> >>> With tx/rxsum disabled, the ssh client will seem to hang, while the >>> server spits the xn_txeof message. >>> >>> >>> I seem to recall that disabling TSO helped fix a similar error under >>> Citrix XenServer, but alas. No difference. >> >> Same thing with i386 and full PV. > > Just tested, also in current. > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" > ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: xn_txeof: WARNING: response is -1!
On 05/25/11 17:20, Hugo Silva wrote: > On 05/24/11 21:14, Hugo Silva wrote: >> On 05/24/11 14:45, Hugo Silva wrote: >>> Trying to ssh to the VM produces the error in the subject line on the >>> FreeBSD domU; It's impossible to login. >>> >> >> Some more information for those looking to reproduce this: the above is >> with rxcsum and txcsum disabled in the xn interface: Without that, the >> ssh client on the other side would just say 'Disconnected: Packet corrupt'. >> >> With tx/rxsum disabled, the ssh client will seem to hang, while the >> server spits the xn_txeof message. >> >> >> I seem to recall that disabling TSO helped fix a similar error under >> Citrix XenServer, but alas. No difference. > > Same thing with i386 and full PV. Just tested, also in current. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: xn_txeof: WARNING: response is -1!
On 05/24/11 21:14, Hugo Silva wrote: > On 05/24/11 14:45, Hugo Silva wrote: >> Trying to ssh to the VM produces the error in the subject line on the >> FreeBSD domU; It's impossible to login. >> > > Some more information for those looking to reproduce this: the above is > with rxcsum and txcsum disabled in the xn interface: Without that, the > ssh client on the other side would just say 'Disconnected: Packet corrupt'. > > With tx/rxsum disabled, the ssh client will seem to hang, while the > server spits the xn_txeof message. > > > I seem to recall that disabling TSO helped fix a similar error under > Citrix XenServer, but alas. No difference. Same thing with i386 and full PV. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: xn_txeof: WARNING: response is -1!
On 05/24/11 14:45, Hugo Silva wrote: > Trying to ssh to the VM produces the error in the subject line on the > FreeBSD domU; It's impossible to login. > Some more information for those looking to reproduce this: the above is with rxcsum and txcsum disabled in the xn interface: Without that, the ssh client on the other side would just say 'Disconnected: Packet corrupt'. With tx/rxsum disabled, the ssh client will seem to hang, while the server spits the xn_txeof message. I seem to recall that disabling TSO helped fix a similar error under Citrix XenServer, but alas. No difference. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
xn_txeof: WARNING: response is -1!
Hello, NetBSD -current dom0 FreeBSD 8.2-STABLE domU. Trying to ssh to the VM produces the error in the subject line on the FreeBSD domU; It's impossible to login. I found a few references in google, but nothing conclusive. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"