Re: kern/118093: [firewire] firewire bus reset hogs CPU, causing data to be lost

Dieter <[email protected]>
Newsgroups gmane.os.freebsd.devel.firewire
Message-ID <[email protected]>
The following reply was made to PR kern/118093; it has been noted by GNATS.

From: Dieter <[email protected]>
To: Gavin Atkinson <[email protected]>
Cc: [email protected], [email protected]
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.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.