From owner-freebsd-firewire@FreeBSD.ORG Tue Jun 24 00:42:19 2003 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CF4A37B401 for ; Tue, 24 Jun 2003 00:42:19 -0700 (PDT) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 827A343FB1 for ; Tue, 24 Jun 2003 00:42:18 -0700 (PDT) (envelope-from kleiner@panix.com) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail3.panix.com (Postfix) with ESMTP id C9EFE982A2; Tue, 24 Jun 2003 03:42:17 -0400 (EDT) Received: (from kleiner@localhost) by panix2.panix.com (8.11.6p2/8.8.8/PanixN1.1) id h5O7gHf25394; Tue, 24 Jun 2003 03:42:17 -0400 (EDT) Date: Tue, 24 Jun 2003 03:42:17 -0400 From: David Kleiner To: Hidetoshi Shimokawa Message-ID: <20030624074217.GA24922@panix.com> References: <20030525061631.GA15205@panix.com> <20030525102020.GA22040@panix.com> <20030623082736.GA8364@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-firewire@freebsd.org Subject: Re: que! cdrw support X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 07:42:19 -0000 Hi, I tried your patch - it increased the number of retries, then I did # sysctl hw.firewire.fwmem.speed=0 hw.firewire.fwmem.speed: 2 -> 0 wallaby# sysctl hw.firewire.sbp.max_speed=0 hw.firewire.sbp.max_speed: 2 -> 0 and reconnected. After a few tries, I got this: fwohci0: node_id=0xc000ffc1, gen=9, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) cd0 at sbp0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 50.000MB/s transfers cd0: cd present [330066 x 2048 byte records] sbp0:0:0 request timeout ... agent reset sbp0:0:0 request timeout ... target reset fwohci0: txd err=14 ack busy_X fw_asybusy fwohci0: txd err=14 ack busy_X fw_asybusy fwohci0: txd err=14 ack busy_X fw_asybusy fwohci0: txd err=14 ack busy_X fw_asybusy firewire0: max_asyretry exceeded sbp0:0:0 management ORB timeout I don't know if it helps, but I also see this: wallaby# fwcontrol -c 0 first quad: 0x04213830 info_len=4 crc_len=33 crc=0x3830(OK) bus_name: 0x31333934 irmc:0 cmc:0 isc:0 bmc:0 pmc:0 cyc_clk_acc:255 max_rec:10 max_rom:0 generation:0 link_spd:0 EUI64: 0x0001f302 0x40001b5e root_directory: len=0x0004(4) crc=0x4ffc(OK) 03(I:03) 0001f3 module_vendor_ID: 81(L:01) 00000f text_leaf: len=4 crc=0x43ec(OK) QPS 0c(I:0c) 0083c0 node_capabilities: d1(D:11) 000001 unit_directory: len=11 crc=0xb32b(OK) 12(I:12) 00609e unit_spec_ID: 13(I:13) 010483 unit_sw_version: SBP-2 3c(I:3c) 000232 firmware_revision: 38(I:38) 00609e command_set_spec_ID: 39(I:39) 0104d8 command_set: 54(C:14) 004008 management_agent: offset=0x4008(16392) 3a(I:3a) 000a08 unit_characteristics: 3d(I:3d) 000000 reconnect_timeout: 14(I:14) 450000 logical_unit_number: 17(I:17) 000240 model_ID: 81(L:01) 000006 text_leaf: len=6 crc=0x479d(OK) QBP-2 Bridge Unfortunetly (or luckily :) I don't have any other OS to try this drive with... Thank you, David On Mon, Jun 23, 2003 at 08:27:08PM +0900, Hidetoshi Shimokawa wrote: > It might be too early for the device to start probing. > Try the following patch: > [ ... deleted ... ] > > >