panic: sbflush_locked on 5.4-p5/i386
Robert Watson
rwatson at FreeBSD.org
Sat Aug 6 10:51:47 GMT 2005
On Fri, 29 Jul 2005, Robert Watson wrote:
> On Fri, 29 Jul 2005, Alexander S. Usov wrote:
>
>>>> I got a few similar panics.
>>>> It looks that I managet to get rid of them by setting mpsafenet=0, but I
>>>> am not sure -- I have to monitor it for a bit longer.
>>>> I have managed to get a few dumps, so the traces are:
>>
>> Unfortunately I don't have these dumps anymore, I will try to switch
>> mpsafenet back on and wait for a new ones. They were quite reproducable for
>> me.
>
> Thanks. I will be away this weekend, but hope to have a chance to look
> into this early next week. If you could send me the dmesg of the box
> also, and the output of "sysctl -a", that would be helpful. Probably
> out of band rather than via the list (or if you could put it on a web
> page I could reach).
Two quetions:
- Is there substantial IPv6 traffic on this system? I've had at least one
report that this panic happens on a system only in the context of IPv6.
- Is it possible for you to try running with a latest 5-STABLE kernel?
Mohan at Yahoo!, who did the TCP SACK work, has been investigating the
problem but has been unable to reproduce it either. Fortunately, it
sounds like Geore Neville-Neil is able to reprodeuce it in a test
environment, albeit only with IPv6, so we'll see what we can do. Mohan
may shortly have a diagnostic patch to run with.
Thanks,
Robert N M Watson
More information about the freebsd-stable
mailing list