Re: IP stack problem -- possibly mac-related

2003-03-26 Thread Daniel C. Sobral
X marks the spot. Robert Watson wrote: On Mon, 24 Mar 2003, Daniel C. Sobral wrote: The messages below are from today's kernel + mac_mls and mac_biba kld-loaded from loader(8). None of the warning appear if these modules are not loaded (I haven't tried not loading one and then the other, but I

IP stack problem -- possibly mac-related

2003-03-24 Thread Daniel C. Sobral
The messages below are from today's kernel + mac_mls and mac_biba kld-loaded from loader(8). None of the warning appear if these modules are not loaded (I haven't tried not loading one and then the other, but I can do it on request) fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Robert Watson
On Mon, 24 Mar 2003, Daniel C. Sobral wrote: The messages below are from today's kernel + mac_mls and mac_biba kld-loaded from loader(8). None of the warning appear if these modules are not loaded (I haven't tried not loading one and then the other, but I can do it on request) ... malloc()

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Christian Brueffer
On Mon, Mar 24, 2003 at 01:08:37PM -0500, Robert Watson wrote: On Mon, 24 Mar 2003, Daniel C. Sobral wrote: The messages below are from today's kernel + mac_mls and mac_biba kld-loaded from loader(8). None of the warning appear if these modules are not loaded (I haven't tried not

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Christian Brueffer
On Mon, Mar 24, 2003 at 08:28:38PM +0100, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 01:08:37PM -0500, Robert Watson wrote: On Mon, 24 Mar 2003, Daniel C. Sobral wrote: The messages below are from today's kernel + mac_mls and mac_biba kld-loaded from loader(8). None of the

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Robert Watson
On Mon, 24 Mar 2003, Christian Brueffer wrote: FYI, debug.witness_trace is set (seems to default to 1). Any other ways to get more info out of this? Are you only looking at syslog, or also at the actual console? It could be that the Witness traces only appear on the console itself, not in

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Robert Watson
On Mon, 24 Mar 2003, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 02:45:57PM -0500, Robert Watson wrote: On Mon, 24 Mar 2003, Christian Brueffer wrote: FYI, debug.witness_trace is set (seems to default to 1). Any other ways to get more info out of this? Are you only

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Christian Brueffer
On Mon, Mar 24, 2003 at 02:53:08PM -0500, Robert Watson wrote: It's on the console. Any chance you could copy/paste it using a serial console or the like? Well, not much to see here: malloc() of 128 with the following non-sleepablelocks held: exclusive sleep mutex netisr lock r = 0

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Christian Brueffer
On Mon, Mar 24, 2003 at 08:59:29PM +0100, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 02:53:08PM -0500, Robert Watson wrote: It's on the console. Any chance you could copy/paste it using a serial console or the like? Well, not much to see here: malloc() of 128 with the

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Robert Watson
On Mon, 24 Mar 2003, Christian Brueffer wrote: Well, not much to see here: malloc() of 128 with the following non-sleepablelocks held: exclusive sleep mutex netisr lock r = 0 (0xc0466d40) locked @ /usr/src/sys/net/n etisr.c:215 which is repeated over and over again, when I copy a

Re: IP stack problem -- possibly mac-related

2003-03-24 Thread Christian Brueffer
On Mon, Mar 24, 2003 at 03:43:19PM -0500, Robert Watson wrote: On Mon, 24 Mar 2003, Christian Brueffer wrote: Well, not much to see here: malloc() of 128 with the following non-sleepablelocks held: exclusive sleep mutex netisr lock r = 0 (0xc0466d40) locked @ /usr/src/sys/net/n