sbp0:0:0 No ocb(260d628c) on the queue

[Hidetoshi Shimokawa]

Some HDD's seems not to work with tagged queuing.
try 'camcontrol [device id] tags -N 1'.

/\ Hidetoshi Shimokawa
\/  simokawa at sat.t.u-tokyo.ac.jp
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

At Sun, 29 Jun 2003 14:30:41 +0200,
Manfred Lotz wrote:
> 
> Hi there,
> 
> I have the following firewire controller:
> 
> fwohci0: <VIA VT6306> port 0xc800-0xc87f mem 0xea004000-0xea0047ff irq 3 at 
> devi
> ce 12.0 on pci0
> fwohci0: OHCI version 1.0 (ROM=1)
> fwohci0: No. of Isochronous channel is 8.
> fwohci0: EUI64 00:11:06:00:00:00:4a:1d
> fwohci0: Phy 1394a available S400, 3 ports.
> fwohci0: Link S400, max_rec 2048 bytes.
> firewire0: <IEEE1394(FireWire) bus> on fwohci0
> 
> 
> It works quite good with an IBM disk although I also get ack err messages from 
> tiem to time. 
> 
> However when connecting a 80 GB Seagate disk and copying to the mounted 
> partition I get lots of messages like this:
> sbp0:0:0 No ocb(260d628c) on the queue
> 
> When booting from my rescue CD (FreeBSD 5.0 Current, created in April) the 
> copy process seems to work fine despite the "No ocb..."-messages.
> 
> When copying from my current desktop system FreeBSD 5.1 Release I additionally 
> get kenel panics, e.g. ffs_valloc: dup alloc.
> 
> In all cases: If  I do a fsck this works fine. No complaints from teh firewire 
> point of view.
> 
> What should I do to get more meaningful informations which  I can provide to 
> the developer when making a bugreport? Can I assume to be fine with FreeBSD 
> 4.8 STABLE?
> 
> Manfred
> 
> _______________________________________________
> freebsd-firewire at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
> To unsubscribe, send any mail to "freebsd-firewire-unsubscribe at freebsd.org"
>