Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Dec 2014 09:40:26 -0800
From:      Peter Grehan <grehan@freebsd.org>
To:        Shawn Webb <lattera@gmail.com>
Cc:        FreeBSD-current <freebsd-current@freebsd.org>, Bryan Venteicher <bryanv@daemoninthecloset.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: Bug in virtio-net
Message-ID:  <5487340A.7040208@freebsd.org>
In-Reply-To: <1418088637.1493.4.camel@gmail.com>
References:  <1418081692.1493.2.camel@gmail.com> <CAMo0n6R72mZZbNgQgmW_D9FL=Bp2OVZEu28eZDQaCAetApoSMQ@mail.gmail.com> <1418088637.1493.4.camel@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Shawn,

>> ​I doubt this has anything to do with vtnet. My guess is that
>> netisr_proto[NETISR_ETHER].np_handler(m) is ​NULL for some reason. 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 than a bug in the virtio driver. The core dump would be able to 
point to what went wrong.

later,

Peter.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5487340A.7040208>