I have improved recovery code after timeout in -current. Could you try that?
/\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sun, 2 Feb 2003 13:28:33 +0200, mike wrote: > > [1 <text/plain; iso-8859-1 (7bit)>] > On Thu, 30 Jan 2003 14:41:59 +0900, Hidetoshi Shimokawa wrote > > Do you get timeout only for sbp0:0:0? > > Is the other drive still working? > > > > I have no problem with concurrent accesses with `iozone -s 102400m -r > > 1024k`. > ... > > try some of the following: > > > > - fwcontorl -g 20 > > - sysctl hw.firewire.sbp.max_speed=0 > > - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module. > > - sysctl machdep.cpu_idle_hlt=0 > > - sysctl debug.sbp_debug=1 and send me a dmesg. > > with all of the above I get the attached dmesg soon after > setting up two concurrent iozones (one per disk): ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
