Re: kernel panic. pppoe

On 5/29/06, Max Laier <max_at_love2party.net> wrote:
>
> On Monday 29 May 2006 11:05, sekes wrote:
> > Cause my message has been lost in threads i repost it again here.
> >
> > http://lists.freebsd.org/pipermail/freebsd-current/2006-May/062955.html
> > Sorry for annoying :-)
> >
> > Strange panic occurs in the kernel every time i'm trying to make PPPoE
> > connection
> > This problem is very important to me because since all that time it
> > presents in the kernel i am not able to establish any succesfull
> internet
> > sessions longer than on 10-15 minutes:(
> >
> > panic: mutex Giant not owned at /usr/src/sys/net/if.c:2209
> > cpuid = 0
> > KDB: enter: panic
> > [thread pid 11 tid 100005 ]
> > Stopped at      kdb_enter+0x2b: nop
> > db>
> > db>
> > db>
> > db> bt
> > Tracing pid 11 tid 100005 td 0xc28916c0
> > kdb_enter(3230725374) at kdb_enter+43
> > panic(3230722033,3230813051,3230769714,2209,3264851968) at panic+295
> > _mtx_assert(3231693000,1,3230769714,2209) at _mtx_assert+102
> > if_start(3264851968) at if_start+38
> > ether_output_frame(3264851968,3265936896,3265938176,0,3270958224) at
> > ether_output_frame+384
> > ng_ether_rcvdata(3270304512,3270958224,1717,3231718100,0) at
> > ng_ether_rcvdata+308
> > ng_apply_item(0,3265938176,5,0,0) at ng_apply_item+278
> > ng_snd_item(3270958224,0,3270958224,3266710848,3270315648) at
> > ng_snd_item+230
> > pppoe_ticker(3270315648,3270304384,0,0,3227049343) at pppoe_ticker+229
> > ng_apply_item(1,622,2,1,0) at ng_apply_item+495
> > ng_snd_item(3270958272,0,3548757204,3228176966,3270958272) at
> > ng_snd_item+230
> > ng_callout_trampoline(3270958272) at ng_callout_trampoline+13
> > softclock(0) at softclock+518
> > ithread_execute_handlers(3263761156,3263960576) at
> > ithread_execute_handlers+234
> > ithread_loop(3263596944,3548757304) at ithread_loop+103
> > fork_exit(3228039632,3263596944,3548757304) at fork_exit+164
> > fork_trampoline() at fork_trampoline+8
> > --- trap 1, eip = 0, esp = 3548757356, ebp = 0 ---
>
> Looks like you have a NIC that still requires the Giant lock around the
> network stack and you found a callpath that does not pick it up.  As a
> workaround you can try to disable the mpsafe networking (debug.mpsafenet=0
> ),
> be sure to tell us if that helps and examine "ifp" in the if_start frame
> if
> possible.


 debug.mpsafenet=0 in /boot/loader.conf didn't solve it all. i mentioned it
earlier in previous threads.
and i don't know what can i do on this anymore. in this thread you can see
the kernel crashdump of this  outrage which i made. i have no any expirience
in programming or other stuff like that and i don't know how to examine ifp
without step-by-step explanation :( maybe somebody can send me any
dummy-patches which temporarily will fix my problem at least ?