Date: Tue, 9 Dec 2014 12:42:49 -0500 From: Shawn Webb <lattera@gmail.com> To: Peter Grehan <grehan@freebsd.org> Cc: FreeBSD-current <freebsd-current@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Bug in virtio-net Message-ID: <CADt0fhxrCR66178pDA4z5UVDZ2ypFN9s=VgQSs4MPK4iv=3A9w@mail.gmail.com> In-Reply-To: <5487340A.7040208@freebsd.org> References: <1418081692.1493.2.camel@gmail.com> <CAMo0n6R72mZZbNgQgmW_D9FL=Bp2OVZEu28eZDQaCAetApoSMQ@mail.gmail.com> <1418088637.1493.4.camel@gmail.com> <5487340A.7040208@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 9, 2014 at 12:40 PM, Peter Grehan <grehan@freebsd.org> wrote: > Hi Shawn, > > =E2=80=8BI doubt this has anything to do with vtnet. My guess is that >>> netisr_proto[NETISR_ETHER].np_handler(m) is =E2=80=8BNULL for some reas= on. Do >>> you have a dump? >>> >> >> core.txt is attached. I've also uploaded it to the link below in case >> the attachment is scrubbed. >> >> http://0xfeedface.org/~shawn/2014-12-08_2028_core.txt >> > > Is the core dump available ? > > As Bryan mentioned, this is a NULL function pointer deref and not a data > access so is possibly related to corruption of data structures rather tha= n > a bug in the virtio driver. The core dump would be able to point to what > went wrong. > > later, > > Peter. > > Gotcha. I'll see if I can upload it to Google Drive or somewhere. It's 1.6GB in size. I'm assuming just like any other core dump, they can contain sensitive info. I'll ping you both directly with the link when it's uploaded. Please keep sharing it to a minimum. Thanks, Shawn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADt0fhxrCR66178pDA4z5UVDZ2ypFN9s=VgQSs4MPK4iv=3A9w>