-------- Original-Nachricht -------- > Datum: Wed, 15 Jul 2009 14:00:35 +0200 CEST > Von: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> > Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > The only problem I know of, is that dprintf() must not be called with > > interrupts disabled, since it potentially writes to a port. That only > > triggers a panic though and doesn't cause any weird crashes. > > dprintf_no_syslog() should be used in respective places. > > Actually, dprintf() does not write to a port itself, and is generally > safe to be called with interrupts disabled *unless* you also hold > certain spinlocks. Indeed, the thread spinlock only. Oh my, I'm getting senile (have I said that before? ;-)). CU, Ingo