Synopsis: [panic] page fault while in kernel mode at _mtx_lock_sleep
Responsible-Changed-From-To: freebsd-net->freebsd-xen
Responsible-Changed-By: cperciva
Responsible-Changed-When: Mon Nov 29 05:19:21 UTC 2010
Responsible-Changed-Why:
This is a Xen bug, not a network stack bug.
http://www.freeb
Synopsis: [panic] mtx_lock() of spin mutex (null) @
/usr/src/sys/net/netisr.c:830
Responsible-Changed-From-To: freebsd-net->freebsd-xen
Responsible-Changed-By: cperciva
Responsible-Changed-When: Sun Nov 28 14:59:04 UTC 2010
Responsible-Changed-Why:
This is actually a FreeBSD/Xen bug. Somehow th
On Sun, Nov 28, 2010 at 01:19:07AM -0800, Jack Vogel wrote:
> Well, its not solving this odd vlan tag change problem, that isn't what the
> workaround was about, at least I dont see how to connect them.
Yes, but I still see the double vlan tags on the mirror port that I
connected to ix3, which is
Hello!
On Sat, Nov 27, 2010 at 02:13:53PM +1100, Lawrence Stewart wrote:
> On 11/13/10 00:18, Lawrence Stewart wrote:
> > On 11/12/10 21:41, Kostik Belousov wrote:
> >> On Fri, Nov 12, 2010 at 09:21:29PM +1100, Lawrence Stewart wrote:
> >>> On 11/12/10 20:44, Lawrence Stewart wrote:
> On 11/
Well, its not solving this odd vlan tag change problem, that isn't what the
workaround was about, at least I dont see how to connect them.
So you arent using HW Filters? or does that just not show up in the ifconfig
display?
Jack
On Sun, Nov 28, 2010 at 12:16 AM, John Hay wrote:
> Hi Jack,
>
Hi Jack,
On Sat, Nov 27, 2010 at 09:59:10AM -0800, Jack Vogel wrote:
> Well, that will be cool if so, its not usually FreeBSD that
> finds bugs, and if it really is hardware then they need to
> know. Thanks Ryan!
>
> Jack
>
>
> On Sat, Nov 27, 2010 at 4:52 AM, Ryan Stone wrote:
>
> > 2010/11/
