Subject: Re: panic with named on -current (panic: looutput: no header mbuf)
To: Christos Zoulas <firstname.lastname@example.org>
From: Steven M. Bellovin <email@example.com>
Date: 08/15/2004 00:13:22
In message <I2GyH1.14G@tac.nyc.ny.us>, Christos Zoulas writes:
>In article <20040815034139.434281AE4D@berkshire.research.att.com>,
>Steven M. Bellovin <firstname.lastname@example.org> wrote:
>>In message <200408142217.i7EMHRAr000598@dsl-217-9-35-195.berlikomm.net>, Stef
>> "Kr ger" writes:
>>>I got a nice panic today, triggered by named, sources are from 14. Aug,
>>>around 18:00 CEST. Everything is fine when I do not enable/try to run named!
>>I've seen and reported the same thing. I have no fix, though I wonder
>>if it's a combination of ipv6 and some unusual hardware -- my machine
>>has a bge0 NIC.
>I think that it has to do with ipv6. Is there a pr for it?
I have not filed one, since I'm not able to verify or provide further
information for a few weeks. But I doubt that it's only ipv6 that
triggers this or we'd see a lot more people experiencing the problem.
--Steve Bellovin, http://www.research.att.com/~smb