Re: [issue1818] panic: Bad tailq NEXT (kqueue issue ?)

[Francois Tigeot <ftigeot@xxxxxxxxxxxx>]

On Tue, Sep 07, 2010 at 01:34:40PM -0700, Matthew Dillon wrote:
> 
> :No new crash so far; I guess we will need a few more days to be sure.
> :
> :-- 
> :Francois Tigeot
> 
>    I pushed more changes on the 6th, make sure you have commit
>    14343ad3b815bafa1bcec3656de2d614fcc75bec or later.  Probably
>    getting commit through 12d442975420e1da3daae44f5c20a3c1dce055df is
>    best.
> 
>    Absolute latest master will work too if you don't need wireless.
>    (wireless is going to be broken for a day or two while we clean
>    up the locks).

I'm running 2.7.3.865.g12d44-DEVELOPMENT. I think I've got all the latest
changes up to the LWKT_SERIALIZE_INITIALIZER bit (not included).

-- 
Francois Tigeot