Date: Tue, 16 Dec 2008 05:40:05 GMT From: Sean Bruno <sbruno@miralink.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost Message-ID: <200812160540.mBG5e5wT064570@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: Sean Bruno <sbruno@miralink.com>
To: Dieter <freebsd@sopwith.solgatos.com>
Cc: freebsd-firewire@freebsd.org, bug-followup@FreeBSD.org
Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be
lost
Date: Mon, 15 Dec 2008 21:14:32 -0800
Dieter wrote:
> 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...
> _______________________________________________
>
Which one are you looking at Dieter?
Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812160540.mBG5e5wT064570>