From owner-freebsd-firewire@FreeBSD.ORG  Mon May 11 06:59:53 2009
Return-Path: <owner-freebsd-firewire@FreeBSD.ORG>
Delivered-To: freebsd-firewire@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A6488106564A;
	Mon, 11 May 2009 06:59:53 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com
	(pool-173-50-234-194.ptldor.fios.verizon.net [173.50.234.194])
	by mx1.freebsd.org (Postfix) with ESMTP id 03C7B8FC15;
	Mon, 11 May 2009 06:59:52 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: by sopwith.solgatos.com (Postfix, from userid 66)
	id 59604B64F; Sat,  9 May 2009 20:13:38 -0700 (PDT)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id SAA05694; Sun, 10 May 2009 18:20:29 GMT
Message-Id: <200905101820.SAA05694@sopwith.solgatos.com>
To: Gavin Atkinson <gavin@freebsd.org>
In-reply-to: Your message of "Fri, 06 Mar 2009 16:00:08 GMT."
	<200903061600.n26G082b030204@freefall.freebsd.org> 
Date: Sun, 10 May 2009 11:20:29 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: freebsd-firewire@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/118093: [firewire] firewire bus reset hogs CPU,
	causing data to be lost 
X-BeenThere: freebsd-firewire@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Firewire support in FreeBSD <freebsd-firewire.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-firewire>
List-Post: <mailto:freebsd-firewire@freebsd.org>
List-Help: <mailto:freebsd-firewire-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 May 2009 06:59:53 -0000

>  > > This looks like it may be some bad
>  > > interaction between the firewire stack and using a serial
>  > > console.  To submitter: It may be worth while switching to
>  > > uart(4) rather than sio(4) for your serial ports and seeing
>  > > if that makes any difference (as I don't think uart(4) uses
>  > > the Giant lock).

>  > Looks to me like commenting out sio doesn't work so well on my box.
>  > Is that the wrong way to switch from sio to uart?
>  > Is there something else I need to change instead, or in addition?
>  
>  You'll also need to add the uart hints to your device.hints file, if you
>  haven't already, and update /etc/ttys.
>  
>  hint.uart.0.at="isa"
>  hint.uart.0.port="0x3F8"
>  hint.uart.0.flags="0x10"
>  hint.uart.0.irq="4"
>  
>  /etc/ttys: you may find you need to change "ttyd0" to "ttyu0".
>  
>  Gavin

Thanks, with those changes it works with uart now.

The bad news is that switching from sio to uart didn't fix the
CPU hogging problem.