On Wed, 12 Mar 2003, Jonathan Lemon wrote: JL>In article <local.mail.freebsd-net/[EMAIL PROTECTED]> you write: JL>> JL>>Hi all, JL>> JL>>I was under the impression that the if_start function is NOT called from JL>>an interrupt context, so I should be able to call uma_zalloc_arg(..., JL>>M_WAITOK) there. I get however JL>> JL>>Mar 12 18:12:49 catssrv kernel: malloc() of "en dma maps" with the JL>>following non-sleepablelocks held: JL>>Mar 12 18:12:49 catssrv kernel: exclusive sleep mutex netisr lock r = 0 JL>>(0xc022d9c0) locked @ /usr/src/sys/net/netisr.c:209 JL>> JL>>I'm wrong with my assumption? JL> JL>if_start() can be called from interrupt context from the bridging, JL>fast-forwarding, (and now) direct dispatch codepaths. That being JL>said, the message can be ignored, I'll rework things to use a gate JL>instead of a mutex, although this seems to be catching some hidden bugs.
Is there a fast method to get rid of exactly this one warning until you rework the code? It really makes debugging and testing a driver very hard. I'm working on mutexifying the driver so I need witness. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
