From: Timo Benk <timo.benk@gmx.de>
To: Xen devel list <xen-devel@lists.xensource.com>
Subject: Direct Ethernet Connection Bug (3.0.4-1)
Date: Fri, 02 Feb 2007 12:53:12 +0100 [thread overview]
Message-ID: <45C32628.6000801@gmx.de> (raw)
Hello,
i am trying to configure a direct ethernet connection between two Domain-Us:
If i start the Domain with the frontend-Device-Driver, i get the following
log message inside the domain hosting the backend-device-driver:
Feb 2 12:53:04 xendom1 kernel: ------------[ cut here ]------------
Feb 2 12:53:04 xendom1 kernel: kernel BUG at drivers/xen/netback/interface.c:205!
Feb 2 12:53:04 xendom1 kernel: invalid opcode: 0000 [#1]
Feb 2 12:53:04 xendom1 kernel: SMP
Feb 2 12:53:04 xendom1 kernel: Modules linked in: netbk xenbus_be ipv6 dm_mod
Feb 2 12:53:04 xendom1 kernel: CPU: 0
Feb 2 12:53:04 xendom1 kernel: EIP: 0061:[<e1117832>] Tainted: GF VLI
Feb 2 12:53:04 xendom1 kernel: EFLAGS: 00210286 (2.6.16.38-xenU #1)
Feb 2 12:53:04 xendom1 kernel: EIP is at netif_map+0x292/0x2e0 [netbk]
Feb 2 12:53:04 xendom1 kernel: eax: c0647ee0 ebx: 00000000 ecx: ffffffff edx: 00000001
Feb 2 12:53:04 xendom1 kernel: esi: 0000020a edi: 0000020b ebp: cca49b80 esp: cfdade7c
Feb 2 12:53:04 xendom1 kernel: ds: 007b es: 007b ss: 0069
Feb 2 12:53:04 xendom1 kernel: Process xenwatch (pid: 8, threadinfo=cfdac000 task=c095a570)
Feb 2 12:53:04 xendom1 kernel: Stack: <0>fffffffe c032dbe8 cf8147c0 00000002 ffffffff 00000000 00000000 cfdade9c
Feb 2 12:53:04 xendom1 kernel: e10f6000 00000000 00000002 0000020a c0250008 00000001 00000000 cf8147c0
Feb 2 12:53:04 xendom1 kernel: cf8147c0 fffffffe 00000000 00000001 c0258db3 00000000 c1602400 cf864940
Feb 2 12:53:04 xendom1 kernel: Call Trace:
Feb 2 12:53:04 xendom1 kernel: [<c0250008>] redo_format+0xe8/0x230
Feb 2 12:53:04 xendom1 kernel: [<c0258db3>] xenbus_read+0x43/0x60
Feb 2 12:53:04 xendom1 kernel: [<c02591ad>] xenbus_scanf+0x1d/0x60
Feb 2 12:53:04 xendom1 kernel: [<e1116a5c>] frontend_changed+0x23c/0x670 [netbk]
Feb 2 12:53:04 xendom1 kernel: [<c025a548>] otherend_changed+0xa8/0xb0
Feb 2 12:53:04 xendom1 kernel: [<c0259290>] xenwatch_thread+0x0/0x180
Feb 2 12:53:04 xendom1 kernel: [<c02587d2>] xenwatch_handle_callback+0x12/0x50
Feb 2 12:53:04 xendom1 kernel: [<c02593f6>] xenwatch_thread+0x166/0x180
Feb 2 12:53:04 xendom1 kernel: [<c02587c0>] xenwatch_handle_callback+0x0/0x50
Feb 2 12:53:04 xendom1 kernel: [<c0130810>] autoremove_wake_function+0x0/0x50
Feb 2 12:53:04 xendom1 kernel: [<c013058b>] kthread+0xab/0xe0
Feb 2 12:53:04 xendom1 kernel: [<c01304e0>] kthread+0x0/0xe0
Feb 2 12:53:04 xendom1 kernel: [<c0102b45>] kernel_thread_helper+0x5/0x10
Feb 2 12:53:04 xendom1 kernel: Code: 95 fb ff ff e8 50 33 18 df e9 ad fd ff ff 89 e8 e8 b4 f8 ff ff 8d 74 26 00 e9 dc fe ff ff 0f 0b dd 00 48 7d 11 e1 e9 c2 fe ff ff <0f> 0b cd 00 48 7d 11 e1 e9 31 fe ff ff 8d 44 24 44 b9 06 00 00
Greetings,
-timo
--
Timo Benk - Jabber ID: fry@downtempo.de - ICQ ID: #414944731
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc
next reply other threads:[~2007-02-02 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 11:53 Timo Benk [this message]
2007-02-02 15:22 ` Direct Ethernet Connection Bug (3.0.4-1) Keir Fraser
2007-02-02 15:28 ` Timo Benk
2007-02-02 15:47 ` Keir Fraser
2007-02-02 15:50 ` Timo Benk
2007-02-02 16:06 ` Mark Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C32628.6000801@gmx.de \
--to=timo.benk@gmx.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.