Date: Thu, 17 Dec 2009 10:51:47 -0800 From: Julian Elischer <julian@elischer.org> To: Venture37 <venture37@geeklan.co.uk> Cc: Marko Zec <zec@FreeBSD.org>, FreeBSD virtualization mailing list <freebsd-virtualization@freebsd.org> Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic Message-ID: <4B2A7DC3.8000504@elischer.org> In-Reply-To: <200912171530.nBHFUDBO087113@freefall.freebsd.org> References: <200912171530.nBHFUDBO087113@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Venture37 wrote: > The following reply was made to PR kern/141696; it has been noted by GNATS. > > From: Venture37 <venture37@geeklan.co.uk> > To: bug-followup@FreeBSD.org, venture37@geeklan.co.uk > Cc: > Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic > Date: Thu, 17 Dec 2009 15:25:28 +0000 > > Photo of the trace output > http://img64.imageshack.us/i/img1517.jpg/ Marko, et al. looking at this, the crash is in ifindex_alloc_locked() from: if_alloc() rum_attach() device_attach() device_probe_and_attach() usb_probe_and_attach_sub() usb_probe_and_attach() uhub_explore() usb_bus_explore() usb_process() the question is "where should we load the current vnet? is it up to the driver (if_rum) or should device_attach assume that the resulting device MIGHT be a network device. Julian > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B2A7DC3.8000504>