Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Aug 2001 13:56:35 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        Yar Tikhiy <yar@FreeBSD.ORG>
Cc:        Archie Cobbs <archie@dellroad.org>, stable@FreeBSD.ORG
Subject:   Re: kernel panic when bringing up a VLAN interface (netgraph?)
Message-ID:  <5.1.0.14.0.20010829135412.01af71c0@marble.sentex.ca>
In-Reply-To: <20010829214910.A204@comp.chem.msu.su>
References:  <5.1.0.14.0.20010828000259.024e98e8@192.168.0.12> <5.1.0.14.0.20010827183043.042e6198@192.168.0.12> <200108280337.f7S3bhD33238@arch20m.dellroad.org> <5.1.0.14.0.20010828000259.024e98e8@192.168.0.12>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
         Peter Blok on freebsd-net ran into the same problem and has some 
insight as well. The thread is "Runt frames = broken VLAN ? "

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=155593+0+current/freebsd-net

         ---Mike

At 09:49 PM 8/29/01 +0400, Yar Tikhiy wrote:
>Hi,
>
>I was able to reproduce the panic and get a core file.
>However, gdb output looks rather strange to me:
>
>(kgdb) where
>#5  0xc020951f in trap (frame={tf_fs = 16, tf_es = 125960208, tf_ds =
>[...]
>#6  0xc01973e4 in ng_ether_output (ifp=0xc026d2e0, mp=0xc8735d34)
>     at ../../netgraph/ng_ether.c:274
>[...]
>
>(kgdb) up 6
>#6  0xc01973e4 in ng_ether_output (ifp=0xc026d2e0, mp=0xc8735d34)
>     at ../../netgraph/ng_ether.c:274
>274             const node_p node = IFP2NG(ifp);
>
>(kgdb) p ifp
>$1 = (struct ifnet *) 0x0
>(kgdb) p mp
>$2 = (struct mbuf **) 0x6718ba
>
>Why does gdb report the values of "ifp" and "mp" inconsistently?
>The kernel crashed at the first line of ng_ether_output(), so
>the arguments couldn't be modified... I'm confused.
>
>--
>Yar


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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