Re: NetBSD 3.x, IPv6 and IPF

[Dominik Bia³y <dmb%yenn.underlegend.net@localhost>]

On Mon, 18 Aug 2008 11:18:31 +0200, Dominik Bia³y 
<dmb%yenn.underlegend.net@localhost>
wrote:
> On Sun, 17 Aug 2008 17:47:38 +0000 (UTC), Michael van Elst 
> <mlelstv%serpens.de@localhost>
> wrote:
>> dmb%yenn.underlegend.net@localhost (Dominik =?iso-8859-1?Q?Bia=B3y?=) writes:
>>
>>>>>fr_checkicmp6matchingstate(c0911980,0,28,c0911980,8) at 
>>>>>netbsd:fr_checkicmp6matchingstate+0x95
>>>> Sounds like an old bug, which was 'fixed' by an ipf upgrade on the
>>>> way to netbsd-4. I doubt that this will be backported to netbsd-3.
>>>>
>>>I have also hit this bug. Is there any workaround? I see the bug is in
>>>fragmented ipv6 packets handling (am I right?). Would not using
>>>``keep frags'' be sufficient?
>>
>> I don't think so. One step of the fix was sys/dist/ipf/netinet/fil.c 1.38
>> but since multiple ipf upgrades happened since netbsd-3 I doubt that
>> this will solve your problem.
>
> I've upgraded to NetBSD 4.0_STABLE from 20080813 and got another panic
> today. Alas, no backtrace. Trying gdb netbsd.8 netbsd.8.core, but gdb
> says netbsd.8.core is not a corefile. How do I get the backtrace?
>
Never mind my last question. I found the answer, but sadly gdb only
gives this:

(gdb) bt
#0  0xc0516726 in cpu_reboot ()
#1  0xc0488698 in panic ()
#2  0xc051f0bc in trap ()
#3  0xc0102caf in calltrap ()
#4  0xc0b10010 in ?? ()
#5  0x00000030 in ?? ()
#6  0x00000010 in ?? ()
#7  0x000b0010 in ?? ()
#8  0x00000001 in ?? ()
#9  0x00000072 in ?? ()
#10 0xc0b155f8 in ?? ()
#11 0x0000004d in ?? ()
#12 0xc1077980 in ?? ()
#13 0x00000000 in ?? ()

I guess I have to wait for yet another panic.

Thanks
        Dominik Bia³y
-- 
Serwer darmowych kont shell: http://yenn.underlegend.net/
tel. +48 698 182 161; email: dmb%yenn.underlegend.net@localhost
--