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`.
tty ad0 da0 da1
tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s
21 360 0.00 0 0.00 63.76 199 12.39 64.00 249 15.54
3 1431 1.00 1 0.00 64.00 213 13.34 64.00 228 14.27
0 153 0.00 0 0.00 64.00 214 13.38 64.00 199 12.45
0 154 0.00 0 0.00 64.00 234 14.61 63.76 200 12.44
0 154 0.00 0 0.00 63.74 188 11.68 64.00 241 15.09
6 154 0.00 0 0.00 64.00 214 13.36 64.00 213 13.30
....
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.
At Tue, 28 Jan 2003 20:42:41 +0100 (CET),
Michael Reifenberger wrote:
> fwohci0: vendor=1180, dev=522
> fwohci0: <1394 Open Host Controller Interface> mem 0xc0201000-0xc02017ff irq 11 at
>device 0.2 on pci2
It's new to me. dev=522 is not listed in /usr/share/misc/pci_vendors...
> system power profile changed to 'economy'
Can you chane it to 'performance' mode?
/\ Hidetoshi Shimokawa
\/ [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
