I'm working in FreeBSD 5.3-RELEASE.
In various places in the buffer management code (e.g. ibwrite()) the
buffer lock reference count is checked (see below), presumably to make
sure the buffer is safely locked before working with it. Is there a
reason that it's not neccesary to ensure that the cur
On Saturday 04 October 2003 11:39 am, Sam Leffler wrote:
> On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> > I keep getting these panics on my SMP box (no backtrace or DDB or
> > crash dump of course, because panic() == hang to FreeBSD these days):
> > panic: receive: m == 0
Sam Leffler <[EMAIL PROTECTED]> wrote:
> On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> > I keep getting these panics on my SMP box (no backtrace or DDB or crash
> > dump of course, because panic() == hang to FreeBSD these days):
> > panic: receive: m == 0 so->so_rcv.sb_cc =
On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> I keep getting these panics on my SMP box (no backtrace or DDB or crash
> dump of course, because panic() == hang to FreeBSD these days):
> panic: receive: m == 0 so->so_rcv.sb_cc == 52
> From what I can tell, all sorts of socke
On Sat, 4 Oct 2003, Brian Fundakowski Feldman wrote:
> I keep getting these panics on my SMP box (no backtrace or DDB or crash
> dump of course, because panic() == hang to FreeBSD these days): panic:
> receive: m == 0 so->so_rcv.sb_cc == 52 From what I can tell, all sorts
> of socket-related cal
I keep getting these panics on my SMP box (no backtrace or DDB or crash
dump of course, because panic() == hang to FreeBSD these days):
panic: receive: m == 0 so->so_rcv.sb_cc == 52
>From what I can tell, all sorts of socket-related calls are "MP-safe"
and yet never even come close to locking the s
6 matches
Mail list logo