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

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:
:On Mon, Sep 06, 2010 at 08:43:00PM +0000, Matthew Dillon (via DragonFly issue tracker) wrote:
:> 
:> Matthew Dillon <dillon@apollo.backplane.com> added the comment:
:> 
:> I pushed some socket changes that might have an effect on your crash.
:>     I'm beginning to think that it isn't related to the pipe code at all
:>     but that some other file descriptor w/ kqueue on it is causing
:>     the corruption.  I'm guessing its the socket code but I don't know
:>     for sure.
:> 
:>     I only give the changes I pushed a 10% chance of fixing the problem,
:>     but lets find out.
:
: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).

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>