On 1 Oct 2009, at 12:24, pluknet wrote:
If you run into this again, let me know. Also, are you using
accept filters
on the box?
Got it again (this time on 6.4-p5).
P.S.
It's funny to say: I got it on two boxes nearly simultaneously.
Both from proftpd. See also my first mail (the same).
2009/10/1 pluknet :
> 2009/4/25 Robert Watson :
>>
>> On Fri, 24 Apr 2009, pluknet wrote:
>>
>>> 2009/4/23 Robert Watson :
On Thu, 23 Apr 2009, pluknet wrote:
> Please, give me comment on this. The panic is on 6.2-REL. Is it known to
> be fixed in the latter releases?
>>
2009/4/25 Robert Watson :
>
> On Fri, 24 Apr 2009, pluknet wrote:
>
>> 2009/4/23 Robert Watson :
>>>
>>> On Thu, 23 Apr 2009, pluknet wrote:
>>>
Please, give me comment on this. The panic is on 6.2-REL. Is it known to
be fixed in the latter releases?
>>>
>>> It may well be -- there have b
2009/4/25 Robert Watson :
>
> On Fri, 24 Apr 2009, pluknet wrote:
>
>> 2009/4/23 Robert Watson :
>>>
>>> On Thu, 23 Apr 2009, pluknet wrote:
>>>
Please, give me comment on this. The panic is on 6.2-REL. Is it known to
be fixed in the latter releases?
>>>
>>> It may well be -- there have b
On Fri, 24 Apr 2009, pluknet wrote:
2009/4/23 Robert Watson :
On Thu, 23 Apr 2009, pluknet wrote:
Please, give me comment on this. The panic is on 6.2-REL. Is it known to
be fixed in the latter releases?
It may well be -- there have been quite significant architectural
improvements to soc
2009/4/23 Robert Watson :
> On Thu, 23 Apr 2009, pluknet wrote:
>
>> Please, give me comment on this. The panic is on 6.2-REL. Is it known to
>> be fixed in the latter releases?
>
> It may well be -- there have been quite significant architectural
> improvements to socket life cycle (etc) between 6
On Thu, 23 Apr 2009, pluknet wrote:
Please, give me comment on this. The panic is on 6.2-REL. Is it known to be
fixed in the latter releases?
It may well be -- there have been quite significant architectural improvements
to socket life cycle (etc) between 6.2 and 7.x releases, which may well
Hi all.
Please, give me comment on this.
The panic is on 6.2-REL. Is it known to be fixed in the latter releases?
Thanks.
db> bt
Tracing pid 14677 tid 101677 td 0xcf8e2640
_mtx_lock_sleep(ce7b9a30,cf8e2640,0,0,0) at _mtx_lock_sleep+0x9d
soabort(ce7b99bc) at soabort+0x82
soclose(c83a2858) at socl
