Could you run with debug.witness_ddb and get a stack trace for the warning? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert_at_fledge.watson.org Network Associates Laboratories On Thu, 19 Jun 2003, John-Mark Gurney wrote: > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings > about mallocing data w/ a lock aquired. > > dmesg output: > malloc() of "64" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked _at_ net/netisr.c:215 > malloc() of "64" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked _at_ net/netisr.c:215 > malloc() of "32" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked _at_ net/netisr.c:215 > malloc() of "64" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked _at_ net/netisr.c:215 > malloc() of "64" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked _at_ net/netisr.c:215 > > If I disable IPv6 in /etc/rc.conf, the above warnings don't appear. > I tried to follow the code path in IPv6's source, but it's soooo long > that I couldn't find where it might be allocating memory. > > Anyone have any ideas? > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Thu Jun 19 2003 - 13:33:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:12 UTC