Is there reason to believe that we won't have dead lock
problems from the M_WAITOK? It seems like that if anything in
the path needed to full fill the malloc needs to log there
is a problem.
Chuck
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
FYI, this is very likely not caused by the heavy weight
interrupt threads, but rather because the interrupt threads can't
be run because the giant lock is held by a process running in the
kernel. Once we get drivers to have their own locking and pulled out
from under the giant lock this pr
