Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Aug 2001 21:49:11 +0400
From:      Yar Tikhiy <yar@FreeBSD.ORG>
To:        Mike Tancsa <mike@sentex.net>
Cc:        Archie Cobbs <archie@dellroad.org>, stable@FreeBSD.ORG
Subject:   Re: kernel panic when bringing up a VLAN interface (netgraph?)
Message-ID:  <20010829214910.A204@comp.chem.msu.su>
In-Reply-To: <5.1.0.14.0.20010828000259.024e98e8@192.168.0.12>; from mike@sentex.net on Tue, Aug 28, 2001 at 12:07:20AM -0400
References:  <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,

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?20010829214910.A204>