Date: Tue, 16 Dec 2008 05:30:04 GMT From: Dieter <freebsd@sopwith.solgatos.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost Message-ID: <200812160530.mBG5U4Kq055956@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/118093; it has been noted by GNATS.
From: Dieter <freebsd@sopwith.solgatos.com>
To: freebsd-firewire@freebsd.org, freebsd-drivers@freebsd.org
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost
Date: Sun, 14 Dec 2008 19:30:04 +0000
I found the source of this problem. When a firewire bus resets,
the firewire driver prints a few lines to the console,
using printf(9) and device_printf(9). I suspect that these are
running at splfw aka splimp, locking out other i/o.
Commenting out the *printf() calls fixes the problem, but that
isn't a good solution.
Would changing the *printf() calls to log(9) calls be safe?
("safe" meaning other i/o doesn't get locked out)
Ah, for the good old days when 19200 baud seemed fast...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812160530.mBG5U4Kq055956>