From owner-freebsd-virtualization@FreeBSD.ORG Mon May 25 13:16:53 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B153B106566C for ; Mon, 25 May 2009 13:16:53 +0000 (UTC) (envelope-from freebsd-virtualization@dino.sk) Received: from loki.netlab.sk (ns3.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id 443F38FC15 for ; Mon, 25 May 2009 13:16:52 +0000 (UTC) (envelope-from freebsd-virtualization@dino.sk) Received: from via.dino.sk (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Mon, 25 May 2009 15:01:22 +0200 id 0002E033.4A1A96A2.0001147C From: Milan Obuch To: freebsd-virtualization@freebsd.org Date: Mon, 25 May 2009 15:06:27 +0200 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200905251506.27771.freebsd-virtualization@dino.sk> Subject: Panic in netgraph with VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 13:16:53 -0000 Hi, there is some bug in (most probably) netgraph code. I did fresh csup and=20 rebuild today. Whenever I try to turn bluetooth on (equivalent to plugging = in=20 the dongle), panic occurs: ubt0: on usbus3 panic:=20 in /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:634=20 ng_make_node_common() vnet=3D0 curvnet=3D0 cpuid =3D 0 This does not occur with kernel from sources three days old. Part from core.txt file: #0 doadump () at pcpu.h:246 246<--->pcpu.h: No such file or directory. <------>in pcpu.h (kgdb) #0 doadump () at pcpu.h:246 #1 0xc0554e0e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 20 #2 0xc05550e2 in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xc0b947c1 in ng_make_node_common (type=3D0xc0b8f9a0, nodepp=3D0xc416b3= a8) at /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:6= 34 #4 0xc0b8bcc4 in ubt_attach (dev=3D0xc4294280) =20 at /usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../dev/usb/bluetoot= h/ng_ubt.c:443 #5 0xc057dcbf in device_attach (dev=3D0xc4294280) at device_if.h:178 #6 0xc057e88e in device_probe_and_attach (dev=3D0xc4294280) at /usr/src/sys/kern/subr_bus.c:2473 #7 0xc0b38240 in usb2_probe_and_attach_sub (udev=3D0xc41fd800, uaa=3D0xe41= 16c1c) at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1131 #8 0xc0b3871a in usb2_probe_and_attach (udev=3D0xc41fd800, iface_index=3D2= 55 '=FF') at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1288 #9 0xc0b40ff0 in uhub_explore (udev=3D0xc3f07000) at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_hub.c:218 #10 0xc0b31f29 in usb2_bus_explore (pm=3D0xc3ed0dd4) =20 at /usr/src/sys/modules/usb/usb/../../../dev/usb/controller/usb_controller.= c:215 #11 0xc0b4343a in usb2_process (arg=3D0xc3ed0d74) at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_process.c:139 #12 0xc0530008 in fork_exit (callout=3D0xc0b43360 ,. arg=3D0xc3ed0d74, frame=3D0xe4116d38) at /usr/src/sys/kern/kern_fork.c:= 830 #13 0xc070b550 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:= 270 At line 634 in ng_base.c, there is INIT_VNET_NETGRAPH(curvnet); I have options VIMAGE in my kernel config (actually this is first one=20 succesfully compiled with mentioned option, but I did not try it too often,= =20 it just failed to compile before). Now I recompiled kernel again, this time without options VIMAGE in config, = and=20 panic does not occur. So the original problem is INIT_VNET_NETGRAPH implementation in presence of= =20 options VIMAGE in kernel config. If anyone has anything to test, please let= =20 me know. Regards, Milan From owner-freebsd-virtualization@FreeBSD.ORG Mon May 25 13:48:11 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F34B6106566C for ; Mon, 25 May 2009 13:48:10 +0000 (UTC) (envelope-from zec@icir.org) Received: from labs4.cc.fer.hr (labs4.cc.fer.hr [161.53.72.24]) by mx1.freebsd.org (Postfix) with ESMTP id 98DA38FC0A for ; Mon, 25 May 2009 13:48:10 +0000 (UTC) (envelope-from zec@icir.org) Received: from sluga.fer.hr (sluga.cc.fer.hr [161.53.72.14]) by labs4.cc.fer.hr (8.14.2/8.14.2) with ESMTP id n4PDmMVk023895 for ; Mon, 25 May 2009 15:48:22 +0200 (CEST) Received: from [192.168.200.110] ([161.53.19.79]) by sluga.fer.hr over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 25 May 2009 15:48:04 +0200 From: Marko Zec To: freebsd-virtualization@freebsd.org Date: Mon, 25 May 2009 15:47:59 +0200 User-Agent: KMail/1.9.10 References: <200905251506.27771.freebsd-virtualization@dino.sk> In-Reply-To: <200905251506.27771.freebsd-virtualization@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200905251547.59432.zec@icir.org> X-OriginalArrivalTime: 25 May 2009 13:48:05.0049 (UTC) FILETIME=[6DBC1290:01C9DD3F] X-Scanned-By: MIMEDefang 2.64 on 161.53.72.24 Cc: Subject: Re: Panic in netgraph with VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 13:48:11 -0000 On Monday 25 May 2009 15:06:27 Milan Obuch wrote: > Hi, > there is some bug in (most probably) netgraph code. I did fresh csup and > rebuild today. Whenever I try to turn bluetooth on (equivalent to plugging > in the dongle), panic occurs: > > ubt0: 2.00/31.64, addr 2> on usbus3 > panic: > in /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:634 > ng_make_node_common() > vnet=3D0 curvnet=3D0 > cpuid =3D 0 > > This does not occur with kernel from sources three days old. This is a known problem related to curvnet context not being set by the USB= =20 device attach code - I have to lurk / shop around for some cheap USB ethern= et=20 or bt devices to be able to reproduce & fix this locally, the alternative=20 would be wild guessing and planting context setting macros at random places= =20 in the USB code, i.e. without testing, which I'm reluctant to do. Marko > Part from core.txt file: > > #0 doadump () at pcpu.h:246 > 246<--->pcpu.h: No such file or directory. > <------>in pcpu.h > (kgdb) #0 doadump () at pcpu.h:246 > #1 0xc0554e0e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c= :420 > #2 0xc05550e2 in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:576 > #3 0xc0b947c1 in ng_make_node_common (type=3D0xc0b8f9a0, nodepp=3D0xc416= b3a8) > at > /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:634 #4= =20 > 0xc0b8bcc4 in ubt_attach (dev=3D0xc4294280) > > at > /usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../dev/usb/bluetooth= /n >g_ubt.c:443 #5 0xc057dcbf in device_attach (dev=3D0xc4294280) at > device_if.h:178 #6 0xc057e88e in device_probe_and_attach (dev=3D0xc42942= 80) > at /usr/src/sys/kern/subr_bus.c:2473 > #7 0xc0b38240 in usb2_probe_and_attach_sub (udev=3D0xc41fd800, > uaa=3D0xe4116c1c) at > /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1131 #8=20 > 0xc0b3871a in usb2_probe_and_attach (udev=3D0xc41fd800, iface_index=3D255= '=FF') > at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1288 #9=20 > 0xc0b40ff0 in uhub_explore (udev=3D0xc3f07000) > at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_hub.c:218 > #10 0xc0b31f29 in usb2_bus_explore (pm=3D0xc3ed0dd4) > > at > /usr/src/sys/modules/usb/usb/../../../dev/usb/controller/usb_controller.c= :2 >15 #11 0xc0b4343a in usb2_process (arg=3D0xc3ed0d74) > at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_process.c:139 > #12 0xc0530008 in fork_exit (callout=3D0xc0b43360 ,. > arg=3D0xc3ed0d74, frame=3D0xe4116d38) at /usr/src/sys/kern/kern_fork.= c:830 > #13 0xc070b550 in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:270 > > At line 634 in ng_base.c, there is > > INIT_VNET_NETGRAPH(curvnet); > > I have options VIMAGE in my kernel config (actually this is first one > succesfully compiled with mentioned option, but I did not try it too ofte= n, > it just failed to compile before). > > Now I recompiled kernel again, this time without options VIMAGE in config, > and panic does not occur. > > So the original problem is INIT_VNET_NETGRAPH implementation in presence = of > options VIMAGE in kernel config. If anyone has anything to test, please l= et > me know. > > Regards, > Milan > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Mon May 25 18:16:48 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F8CD106564A for ; Mon, 25 May 2009 18:16:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outa.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id 72B798FC14 for ; Mon, 25 May 2009 18:16:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id D4917B9836; Mon, 25 May 2009 11:16:47 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 44CC52D6016; Mon, 25 May 2009 11:16:47 -0700 (PDT) Message-ID: <4A1AE08E.5010007@elischer.org> Date: Mon, 25 May 2009 11:16:46 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Marko Zec References: <200905251506.27771.freebsd-virtualization@dino.sk> <200905251547.59432.zec@icir.org> In-Reply-To: <200905251547.59432.zec@icir.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: usb@freebsd.org, Maksim Yevmenkin , freebsd-virtualization@freebsd.org Subject: Re: Panic in netgraph with VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 18:16:48 -0000 Marko Zec wrote: > On Monday 25 May 2009 15:06:27 Milan Obuch wrote: >> Hi, >> there is some bug in (most probably) netgraph code. I did fresh csup and >> rebuild today. Whenever I try to turn bluetooth on (equivalent to plugging >> in the dongle), panic occurs: >> >> ubt0: > 2.00/31.64, addr 2> on usbus3 >> panic: >> in /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:634 >> ng_make_node_common() >> vnet=0 curvnet=0 >> cpuid = 0 >> >> This does not occur with kernel from sources three days old. > > This is a known problem related to curvnet context not being set by the USB > device attach code - I have to lurk / shop around for some cheap USB ethernet > or bt devices to be able to reproduce & fix this locally, the alternative > would be wild guessing and planting context setting macros at random places > in the USB code, i.e. without testing, which I'm reluctant to do. > it probably requires someone who knows the bluetooth and usb-ethernet code to decide how this is done. It seems to me that the bluetooth stuff should probably just always set itself to the base (default) vimage, as it has many kinds of devices that are not really 'interfaces' so to speak and probably deserve to be in the base virtual machine. It does have SOME interface type devices in theory but I don't know if they are supported. Maksim, in vimage, before yo call teh netgraph code, the mbuf should have an interface pointer and that in turn should have a pointer to the vimage.. Alternatively, the thread coming into netgraph should run code from vimage.h that sets the current image for that thread. can you suggest places that this may occur? > Marko > > >> Part from core.txt file: >> >> #0 doadump () at pcpu.h:246 >> 246<--->pcpu.h: No such file or directory. >> <------>in pcpu.h >> (kgdb) #0 doadump () at pcpu.h:246 >> #1 0xc0554e0e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 >> #2 0xc05550e2 in panic (fmt=Variable "fmt" is not available. >> ) at /usr/src/sys/kern/kern_shutdown.c:576 >> #3 0xc0b947c1 in ng_make_node_common (type=0xc0b8f9a0, nodepp=0xc416b3a8) >> at >> /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:634 #4 >> 0xc0b8bcc4 in ubt_attach (dev=0xc4294280) >> >> at >> /usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../dev/usb/bluetooth/n >> g_ubt.c:443 #5 0xc057dcbf in device_attach (dev=0xc4294280) at >> device_if.h:178 #6 0xc057e88e in device_probe_and_attach (dev=0xc4294280) >> at /usr/src/sys/kern/subr_bus.c:2473 >> #7 0xc0b38240 in usb2_probe_and_attach_sub (udev=0xc41fd800, >> uaa=0xe4116c1c) at >> /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1131 #8 >> 0xc0b3871a in usb2_probe_and_attach (udev=0xc41fd800, iface_index=255 'ÿ') >> at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_device.c:1288 #9 >> 0xc0b40ff0 in uhub_explore (udev=0xc3f07000) >> at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_hub.c:218 >> #10 0xc0b31f29 in usb2_bus_explore (pm=0xc3ed0dd4) >> >> at >> /usr/src/sys/modules/usb/usb/../../../dev/usb/controller/usb_controller.c:2 >> 15 #11 0xc0b4343a in usb2_process (arg=0xc3ed0d74) >> at /usr/src/sys/modules/usb/usb/../../../dev/usb/usb_process.c:139 >> #12 0xc0530008 in fork_exit (callout=0xc0b43360 ,. >> arg=0xc3ed0d74, frame=0xe4116d38) at /usr/src/sys/kern/kern_fork.c:830 >> #13 0xc070b550 in fork_trampoline () at >> /usr/src/sys/i386/i386/exception.s:270 >> >> At line 634 in ng_base.c, there is >> >> INIT_VNET_NETGRAPH(curvnet); >> >> I have options VIMAGE in my kernel config (actually this is first one >> succesfully compiled with mentioned option, but I did not try it too often, >> it just failed to compile before). >> >> Now I recompiled kernel again, this time without options VIMAGE in config, >> and panic does not occur. >> >> So the original problem is INIT_VNET_NETGRAPH implementation in presence of >> options VIMAGE in kernel config. If anyone has anything to test, please let >> me know. >> >> Regards, >> Milan >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to >> "freebsd-virtualization-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Tue May 26 02:46:21 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24F2D106564A; Tue, 26 May 2009 02:46:21 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-px0-f106.google.com (mail-px0-f106.google.com [209.85.216.106]) by mx1.freebsd.org (Postfix) with ESMTP id E50A18FC16; Tue, 26 May 2009 02:46:20 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by pxi4 with SMTP id 4so3053981pxi.3 for ; Mon, 25 May 2009 19:46:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=eTY8GcJf63upJDzZ7datySuDhSFGnICO5o7opNPrJr8=; b=dtM0BKaFMzfX20sITsSlqygEcGHsi0p/NbBSzwmE+LFElP9PMrN8H6BF44gGkBVJis KSr9fI65Ug/X+Or5oTfRBAXFGv8Ar9J8KWUN8xT33YId+9gqs6+8VySfbVRT9Q4X1GEk M7UaK8IcWnge9yvm3z1wR1hhAzY9ZdJO28vMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=GOdwlwprBCorqbGr7vaa95jpbj87WMPsre1G9qM8wtm0yj2XBdywURWXmQz8WWdc1G ju9mp1pmgGqWvzyFyrlP0Fl+UAzKat8iMlUv1VyNBCIdGrXSgb4i5s0AoKd0J1wGrFwO FDrR6wKjVhCQU60BYMhFfJhaJJaDmckVj3+f8= MIME-Version: 1.0 Sender: maksim.yevmenkin@gmail.com Received: by 10.115.32.8 with SMTP id k8mr15504653waj.15.1243304706880; Mon, 25 May 2009 19:25:06 -0700 (PDT) In-Reply-To: <4A1AE08E.5010007@elischer.org> References: <200905251506.27771.freebsd-virtualization@dino.sk> <200905251547.59432.zec@icir.org> <4A1AE08E.5010007@elischer.org> Date: Mon, 25 May 2009 19:25:06 -0700 X-Google-Sender-Auth: 4244dd580da0df06 Message-ID: From: Maksim Yevmenkin To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 26 May 2009 06:11:30 +0000 Cc: usb@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: Panic in netgraph with VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 02:46:21 -0000 On Mon, May 25, 2009 at 11:16 AM, Julian Elischer wro= te: > Marko Zec wrote: >> >> On Monday 25 May 2009 15:06:27 Milan Obuch wrote: >>> >>> Hi, >>> there is some bug in (most probably) netgraph code. I did fresh csup an= d >>> rebuild today. Whenever I try to turn bluetooth on (equivalent to >>> plugging >>> in the dongle), panic occurs: >>> >>> ubt0: >> 2.00/31.64, addr 2> on usbus3 >>> panic: >>> in /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:6= 34 >>> ng_make_node_common() >>> =A0vnet=3D0 curvnet=3D0 >>> cpuid =3D 0 >>> >>> This does not occur with kernel from sources three days old. >> >> This is a known problem related to curvnet context not being set by the >> USB device attach code - I have to lurk / shop around for some cheap USB >> ethernet or bt devices to be able to reproduce & fix this locally, the >> alternative would be wild guessing and planting context setting macros a= t >> random places in the USB code, i.e. without testing, which I'm reluctant= to >> do. >> > > it probably requires someone who knows the bluetooth and usb-ethernet > code to decide how this is done. > > It seems to me that the bluetooth stuff should probably just always set > itself to the base (default) vimage, as it has many kinds of devices that > are not really 'interfaces' so to speak and probably deserve to be in the > base virtual machine. > It does have SOME interface type devices in theory but I don't know if th= ey > are supported. > > Maksim, in vimage, before yo call teh netgraph code, the mbuf should have= an > interface pointer and that in turn should have a pointer to the vimage.. > Alternatively, the thread coming into netgraph should run code from vimag= e.h > that sets the current image for that thread. =A0can you suggest places th= at > this may occur? hmm... i do not really know anything about vimage (yet :), but the call to INIT_VNET_NETGRAPH() in ng_make_node_common() seems (to me) out of place. from what i understand, ng_make_node_common() called on all sorts of nodes. some of those are not even network related. it seems to me that network related netgraph nodes (ng_(e)iface, ng_(k)socket, etc.) obviously should set vimage etc. pointer, however for the rest of the nodes some reasonable defaults should be used. as far as setting interface pointer in mbuf its going to be tricky. bluetooth devices do not associated with any network interface, so i'm not sure how to do it. i will need to study the code for a little bit before i can make any intelligent suggestions. thanks, max From owner-freebsd-virtualization@FreeBSD.ORG Thu May 28 11:27:47 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41D6C1065674 for ; Thu, 28 May 2009 11:27:47 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id A73D08FC17 for ; Thu, 28 May 2009 11:27:46 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: (qmail invoked by alias); 28 May 2009 11:27:44 -0000 Received: from ipa85.86.91.tellas.gr (EHLO [192.168.254.1]) [91.140.86.85] by mail.gmx.com (mp-eu002) with SMTP; 28 May 2009 13:27:44 +0200 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18M5cQcz0IMpRklQVs1kGsCm5Q8zF9RKE4Vup2caK MRYzMi931FduF4 Message-ID: <4A1E7501.7090308@gmx.com> Date: Thu, 28 May 2009 14:26:57 +0300 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.52 Subject: panic with option VIMAGE + PPPoE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 11:27:47 -0000 Hi, I am seeing the following panic trying to use PPPoE. > (kgdb) bt > #0 doadump () at pcpu.h:246 > #1 0xc085a77e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 > #2 0xc085aa52 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:576 > #3 0xc04ba317 in db_panic (addr=Could not find the frame base for "db_panic". > ) at /usr/src/sys/ddb/db_command.c:478 > #4 0xc04ba941 in db_command (last_cmdp=0xc0cf9cdc, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 > #5 0xc04baa9a in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 > #6 0xc04bc8fd in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:229 > #7 0xc0889256 in kdb_trap (type=3, code=0, tf=0xc781ab18) at /usr/src/sys/kern/subr_kdb.c:534 > #8 0xc0b182bb in trap (frame=0xc781ab18) at /usr/src/sys/i386/i386/trap.c:685 > #9 0xc0afabeb in calltrap () at /usr/src/sys/i386/i386/exception.s:165 > #10 0xc08893da in kdb_enter (why=0xc0be3714 "panic", msg=0xc0be3714 "panic") at cpufunc.h:71 > #11 0xc085aa36 in panic (fmt=0xc2718513 "in %s:%d %s()\n vnet=%p curvnet=%p") at /usr/src/sys/kern/kern_shutdown.c:559 > #12 0xc27114c8 in ng_ID2noderef (ID=4) at /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:816 > #13 0xc2712202 in ng_address_ID (here=0xc2666380, item=0xc27ade00, ID=4, retaddr=0) at /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:3547 > #14 0xc27a07b0 in ng_ether_rcvmsg (node=0xc2666380, item=0xc27ade00, lasthook=0x0) at /usr/src/sys/modules/netgraph/ether/../../../netgraph/ng_ether.c:596 > #15 0xc271327d in ng_apply_item (node=0xc2666380, item=0xc27ade00, rw=1) at /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:2417 > #16 0xc27146f6 in ngthread (arg=0x0) at /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:3340 > #17 0xc08342c8 in fork_exit (callout=0xc2714570 , arg=0x0, frame=0xc781ad38) at /usr/src/sys/kern/kern_fork.c:830 > #18 0xc0afac60 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 > (kgdb) list ng_base.c:816 > 811 Node ID handling > 812 ************************************************************************/ > 813 static node_p > 814 ng_ID2noderef(ng_ID_t ID) > 815 { > 816 INIT_VNET_NETGRAPH(curvnet); > 817 node_p node; > 818 mtx_lock(&ng_idhash_mtx); > 819 NG_IDHASH_FIND(ID, node); > 820 if(node) > (kgdb) I use the following ppp.conf: > lab# cat /etc/ppp/ppp.conf > pppoe: > set device PPPoE:le1 > set authname "xxxx@xxxx" > set authkey "xxxxxxx" > enable lqr echo > set cd 5 > set dial > set login > set redial 0 0 > enable dns > add default HISADDR > > lab# To reproduce the panic, you have to use the above ppp.conf, start ppp(8), and then in the ppp "console" type "open". It panics very early, that is, you don't need a PPPoE "server" to reproduce it. My kernel is GENERIC + VIMAGE - SCTP from a few days old -CURRENT. Just reporting, Nikos From owner-freebsd-virtualization@FreeBSD.ORG Fri May 29 11:48:12 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D9CC106566B for ; Fri, 29 May 2009 11:48:12 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with ESMTP id 5D2A38FC1E for ; Fri, 29 May 2009 11:48:12 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from [192.168.4.8] (unknown [192.168.4.8]) (Authenticated sender: svein) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id D1C9D26 for ; Fri, 29 May 2009 13:29:06 +0200 (CEST) Message-ID: <4A1FC702.4080100@stillbilde.net> Date: Fri, 29 May 2009 13:29:06 +0200 From: "Svein Skogen (listmail accont)" User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Not sure but: VMWare PVSCSI? X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 11:48:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed that VMWare ESXi 4 introduces pvscsi, and that the openvm-tools already has the driver module for linux. Have anybody started porting this to FreeBSD yet? //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg Østli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkofxwIACgkQODUnwSLUlKSs3gCfTxM52k/PJCis1oF91n/Kmix5 IaAAnA1yCUPPUkPw2AKsew50WtDKhz2j =7oyf -----END PGP SIGNATURE-----