Re: Is socket buffer locking as questionable as it seems?

2003-10-04 Thread Robert Watson
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 calls

Re: Is socket buffer locking as questionable as it seems?

2003-10-04 Thread Sam Leffler
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

Re: Is socket buffer locking as questionable as it seems?

2003-10-04 Thread Brian F. Feldman
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 == 52

Re: Is socket buffer locking as questionable as it seems?

2003-10-04 Thread Wes Peters
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

Is socket buffer locking as questionable as it seems?

2003-10-03 Thread Brian Fundakowski Feldman
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