Date: Mon, 11 May 2009 07:00:14 GMT From: Dieter <freebsd@sopwith.solgatos.com> To: freebsd-firewire@FreeBSD.org Subject: Re: kern/118093: [firewire] firewire bus reset hogs CPU, causing data to be lost Message-ID: <200905110700.n4B70EGT010504@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/118093; it has been noted by GNATS. From: Dieter <freebsd@sopwith.solgatos.com> To: Gavin Atkinson <gavin@freebsd.org> Cc: freebsd-firewire@freebsd.org, bug-followup@freebsd.org Subject: Re: kern/118093: [firewire] firewire bus reset hogs CPU, causing data to be lost Date: Sun, 10 May 2009 11:20:29 +0100 > > > 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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905110700.n4B70EGT010504>