From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 01:27:38 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 C033D37B401 for ; Mon, 23 Jun 2003 01:27:38 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCE8843FB1 for ; Mon, 23 Jun 2003 01:27:37 -0700 (PDT) (envelope-from kleiner@panix.com) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mail1.panix.com (Postfix) with ESMTP id EEC1748B6D; Mon, 23 Jun 2003 04:27:36 -0400 (EDT) Received: (from kleiner@localhost) by panix1.panix.com (8.11.6p2/8.8.8/PanixN1.1) id h5N8Rad11238; Mon, 23 Jun 2003 04:27:36 -0400 (EDT) Date: Mon, 23 Jun 2003 04:27:36 -0400 From: David Kleiner To: Hidetoshi Shimokawa Message-ID: <20030623082736.GA8364@panix.com> References: <20030525061631.GA15205@panix.com> <20030525102020.GA22040@panix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="PNTmBPCT7hxwcZjr" 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: Mon, 23 Jun 2003 08:27:39 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Shimokawa-san, I believe, a while ago I have replied to your suggestion to try lower speed - it didn't change things much. I have enabled CAMDEBUG in my kernel config, I've attached the log to this mail. The bottom line is this: camcontrol reset does not work. Camcontrol rescan all hangs and camcontrol reset all hangs the laptop (no response to keyboard/mouse fan noise is high). Perhaps I need to point out that this is an I-Link to firewire cable - this laptop only has Sony I-Link socket. The multiple lines are due to turning on/off the drive and plugging/unplugging the firewire cable. I am running -CURRENT, with WITNESS'es: FreeBSD wallaby.homeunix.net 5.1-CURRENT FreeBSD 5.1-CURRENT #28: Mon Jun 23 00:23:40 PDT 2003 Please let me know if you need any additional information or if I can add debugging to f/w probes. Thank you, David Kleiner On Sun, May 25, 2003 at 08:26:44PM +0900, Hidetoshi Shimokawa wrote: > At Sun, 25 May 2003 06:20:20 -0400, > David Kleiner wrote: > > after turning the device off and on, I finally get > > wallaby% fwcontrol -d 0 > > 04213830 31333934 00ffa000 0001f302 40001b5e 00044ffc 030001f3 8100000f > > The third quadlet(0x00ffa000) indicates that it supports only 100Mbps. > Can you try with the following? > > # sysctl hw.firewire.sbp.max_speed=0 > > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="camcontrol.log" Jun 23 01:02:07 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:07 wallaby kernel: fwohci0: node_id=0xc000ffc1, gen=4, CYCLEMASTER mode Jun 23 01:02:07 wallaby kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Jun 23 01:02:07 wallaby kernel: firewire0: bus manager 1 (me) Jun 23 01:02:08 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:08 wallaby kernel: fw_asybusy Jun 23 01:02:08 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:08 wallaby kernel: fw_asybusy Jun 23 01:02:08 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:08 wallaby kernel: fw_asybusy Jun 23 01:02:08 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:08 wallaby kernel: fw_asybusy Jun 23 01:02:08 wallaby kernel: firewire0: max_asyretry exceeded Jun 23 01:02:08 wallaby kernel: node0: resp=16 addr=0x400 Jun 23 01:02:08 wallaby kernel: probe failed for 1 node Jun 23 01:02:10 wallaby kernel: fwohci0: Initiate bus reset Jun 23 01:02:11 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:11 wallaby kernel: fwohci0: node_id=0xc000ffc1, gen=5, CYCLEMASTER mode Jun 23 01:02:11 wallaby kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Jun 23 01:02:11 wallaby kernel: firewire0: bus manager 1 (me) Jun 23 01:02:11 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:11 wallaby kernel: fw_asybusy Jun 23 01:02:11 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:11 wallaby kernel: fw_asybusy Jun 23 01:02:11 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:11 wallaby kernel: fw_asybusy Jun 23 01:02:11 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:11 wallaby kernel: fw_asybusy Jun 23 01:02:11 wallaby kernel: firewire0: max_asyretry exceeded Jun 23 01:02:11 wallaby kernel: node0: resp=16 addr=0x400 Jun 23 01:02:11 wallaby kernel: probe failed for 1 node Jun 23 01:02:12 wallaby kernel: fwohci0: Initiate bus reset Jun 23 01:02:12 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:12 wallaby kernel: fwohci0: node_id=0xc000ffc1, gen=6, CYCLEMASTER mode Jun 23 01:02:12 wallaby kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Jun 23 01:02:12 wallaby kernel: firewire0: bus manager 1 (me) Jun 23 01:02:13 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:13 wallaby kernel: fw_asybusy Jun 23 01:02:13 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:13 wallaby kernel: fw_asybusy Jun 23 01:02:13 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:13 wallaby kernel: fw_asybusy Jun 23 01:02:13 wallaby kernel: fwohci0: txd err=14 ack busy_X Jun 23 01:02:13 wallaby kernel: fw_asybusy Jun 23 01:02:13 wallaby kernel: firewire0: max_asyretry exceeded Jun 23 01:02:13 wallaby kernel: node0: resp=16 addr=0x400 Jun 23 01:02:13 wallaby kernel: probe failed for 1 node Jun 23 01:02:16 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:16 wallaby kernel: fwohci0: node_id=0xc000ffc0, gen=7, CYCLEMASTER mode Jun 23 01:02:16 wallaby kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Jun 23 01:02:16 wallaby kernel: firewire0: bus manager 0 (me) Jun 23 01:02:23 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:23 wallaby kernel: fwohci0: node_id=0xc000ffc1, gen=9, CYCLEMASTER mode Jun 23 01:02:23 wallaby kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Jun 23 01:02:23 wallaby kernel: firewire0: bus manager 1 (me) Jun 23 01:02:24 wallaby kernel: fwohci0: txd err= 3 miss Ack err Jun 23 01:02:24 wallaby kernel: node0: resp=22 addr=0x400 Jun 23 01:02:24 wallaby kernel: probe failed for 1 node Jun 23 01:02:25 wallaby kernel: fwohci0: BUS reset Jun 23 01:02:25 wallaby kernel: fwohci0: node_id=0xc000ffc1, gen=10, CYCLEMASTER mode Jun 23 01:02:25 wallaby kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Jun 23 01:02:25 wallaby kernel: firewire0: bus manager 1 (me) Jun 23 01:02:25 wallaby kernel: firewire0: New S400 device ID:0001f30240001b5e Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:25 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:25 wallaby kernel: cam_debug: running device 0xc2d97800 Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_done Jun 23 01:02:25 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_async Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): lost device Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_free_path Jun 23 01:02:25 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_release_path Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): camisr Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): entering cddone Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:25 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:25 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:25 wallaby kernel: cam_debug: running device 0xc2d97800 Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): removing device entry Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_free_path Jun 23 01:02:25 wallaby kernel: (cd0:sbp0:0:0:0): xpt_release_path Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_done Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_done Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): entering cdgetccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_schedule Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): added periph to queue Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:25 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): calling xpt_run_devq Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:25 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:25 wallaby kernel: cam_debug: running device 0xc2d97800 Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:25 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_action Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:25 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:25 wallaby kernel: cam_debug: running device 0xc2d97800 Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_done Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): camisr Jun 23 01:02:25 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_free_path Jun 23 01:02:25 wallaby kernel: (pass0:sbp0:0:0:0): xpt_release_path Jun 23 01:02:27 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_compile_path Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_scan_lun Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (xpt0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_compile_path Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_schedule Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): added periph to queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): calling xpt_run_devq Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:29 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probestart Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): camisr Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probedone Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_schedule Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): added periph to queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): calling xpt_run_devq Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:29 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probestart Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): camisr Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probedone Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_schedule Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): added periph to queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): calling xpt_run_devq Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:29 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probestart Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): camisr Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probedone Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_done Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_release_ccb Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_schedule Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): added periph to queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): calling xpt_run_devq Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_allocq Jun 23 01:02:29 wallaby kernel: cam_debug: qfrozen_cnt == 0x0, entries == 1, openings == 104, active == 0 Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_setup_ccb Jun 23 01:02:29 wallaby kernel: cam_debug: calling periph start Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): probestart Jun 23 01:02:29 wallaby kernel: (probe0:sbp0:0:0:0): xpt_action Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_schedule_dev Jun 23 01:02:29 wallaby kernel: cam_debug: Inserting onto queue Jun 23 01:02:29 wallaby kernel: cam_debug: xpt_run_dev_sendq Jun 23 01:02:29 wallaby kernel: cam_debug: running device 0xc2d97c00 Jun 23 01:02:41 wallaby kernel: (xpt0:xpt0:0:-1:-1): xpt_action --PNTmBPCT7hxwcZjr-- From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 01:51:54 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 EA5F637B401 for ; Mon, 23 Jun 2003 01:51:54 -0700 (PDT) Received: from mail.drunkencomputing.de (ratz.drunkencomputing.de [195.244.235.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4183143F75 for ; Mon, 23 Jun 2003 01:51:54 -0700 (PDT) (envelope-from hscholz@raisdorf.net) Received: from localhost (localhost [127.0.0.1]) by mail.drunkencomputing.de (Postfix) with ESMTP id C577E8AF68 for ; Mon, 23 Jun 2003 10:52:57 +0200 (CEST) Received: from mail.drunkencomputing.de ([127.0.0.1])port 10024) with ESMTP id 82292-07 for ; Mon, 23 Jun 2003 10:52:56 +0200 (CEST) Received: from goanna.lan.raisdorf.net (pD952702B.dip.t-dialin.net [217.82.112.43]) by mail.drunkencomputing.de (Postfix) with ESMTP id 4A6308AF67 for ; Mon, 23 Jun 2003 10:52:50 +0200 (CEST) Date: Mon, 23 Jun 2003 10:51:28 +0200 From: Hendrik Scholz To: firewire@freebsd.org Message-Id: <20030623105128.4d7d6fd5.hscholz@raisdorf.net> X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at drunkencomputing.de Subject: Ricoh R5C551 support on Samsung Q10 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: Mon, 23 Jun 2003 08:51:55 -0000 Hi! I'm encountering the following error on both 5.1-RELEASE and -current: fwohci0: mem 0xe0200000-0xe02007ff irq 11 at device 3.1 on pci2 fwohci0: Could not map memory device_probe_and_attach: fwohci0 attach returned 6 (full dmesg on http://www.raisdorf.net/files/samsungq10.dmesg) man fwohci does not list the R5C551 (only the 552) but since sys/dev/firewire/fwohci_pci.c shows the 551 version I gave it a try. Is there anything I can do to help? (verbose booting did not show any additional error). Thanks, Hendrik -- Hendrik Scholz - - http://raisdorf.net/ Forcast for tonight: Dark. From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 04:01:38 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 F3B5F37B401 for ; Mon, 23 Jun 2003 04:01:37 -0700 (PDT) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [133.11.205.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69DB243F75 for ; Mon, 23 Jun 2003 04:01:36 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is2.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id D2B9E3780E4 for ; Mon, 23 Jun 2003 20:01:34 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h5NB1YmQ020305; Mon, 23 Jun 2003 20:01:34 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJA64075; Mon, 23 Jun 2003 20:01:33 +0900 (JST) Date: Mon, 23 Jun 2003 20:01:33 +0900 Message-ID: From: Hidetoshi Shimokawa To: Hendrik Scholz In-Reply-To: <20030623105128.4d7d6fd5.hscholz@raisdorf.net> References: <20030623105128.4d7d6fd5.hscholz@raisdorf.net> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 11:01:38 -0000 How about if you disable ACPI or disalbe PnP-OS setting in BIOS? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Mon, 23 Jun 2003 10:51:28 +0200, Hendrik Scholz wrote: > > Hi! > > I'm encountering the following error on both 5.1-RELEASE and -current: > > fwohci0: mem 0xe0200000-0xe02007ff irq 11 at device 3.1 on pci2 > fwohci0: Could not map memory > device_probe_and_attach: fwohci0 attach returned 6 > > (full dmesg on http://www.raisdorf.net/files/samsungq10.dmesg) > > man fwohci does not list the R5C551 (only the 552) but since > sys/dev/firewire/fwohci_pci.c shows the 551 version I gave it a try. > > Is there anything I can do to help? (verbose booting did not show any additional error). > > Thanks, Hendrik > > -- > Hendrik Scholz - - http://raisdorf.net/ > > Forcast for tonight: Dark. > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@freebsd.org" > From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 04:05:43 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 710B137B401 for ; Mon, 23 Jun 2003 04:05:43 -0700 (PDT) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [133.11.205.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C7043FB1 for ; Mon, 23 Jun 2003 04:05:42 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is1.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id 3E87E218103 for ; Mon, 23 Jun 2003 20:05:40 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h5NB5d3V029868; Mon, 23 Jun 2003 20:05:39 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJA64153; Mon, 23 Jun 2003 20:05:39 +0900 (JST) Date: Mon, 23 Jun 2003 20:05:39 +0900 Message-ID: From: Hidetoshi Shimokawa To: David Kleiner In-Reply-To: <20030623082736.GA8364@panix.com> References: <20030525061631.GA15205@panix.com> <20030525102020.GA22040@panix.com> <20030623082736.GA8364@panix.com> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 11:05:43 -0000 I suppose there is something wrong with the hardware. CAM debug shouldn't help for this case. Can you use this device with the machine without problem in other OS? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Mon, 23 Jun 2003 04:27:36 -0400, David Kleiner wrote: > > [1 ] > Shimokawa-san, > > I believe, a while ago I have replied to your suggestion to try lower speed - it didn't > change things much. > > I have enabled CAMDEBUG in my kernel config, I've attached the log to this mail. > The bottom line is this: camcontrol reset does not work. Camcontrol rescan all > hangs and camcontrol reset all hangs the laptop (no response to keyboard/mouse > fan noise is high). Perhaps I need to point out that this is an I-Link to > firewire cable - this laptop only has Sony I-Link socket. The multiple lines > are due to turning on/off the drive and plugging/unplugging the firewire cable. > > > I am running -CURRENT, with WITNESS'es: > > FreeBSD wallaby.homeunix.net 5.1-CURRENT FreeBSD 5.1-CURRENT #28: > Mon Jun 23 00:23:40 PDT 2003 > > Please let me know if you need any additional information or if I can add debugging > to f/w probes. > > Thank you, From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 04:27:12 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 576AB37B401 for ; Mon, 23 Jun 2003 04:27:12 -0700 (PDT) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [133.11.205.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 483EA43FE3 for ; Mon, 23 Jun 2003 04:27:11 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is1.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id 3591B2180DA for ; Mon, 23 Jun 2003 20:27:10 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h5NBR93V031498; Mon, 23 Jun 2003 20:27:09 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJA64613; Mon, 23 Jun 2003 20:27:08 +0900 (JST) Date: Mon, 23 Jun 2003 20:27:08 +0900 Message-ID: From: Hidetoshi Shimokawa To: David Kleiner In-Reply-To: References: <20030525061631.GA15205@panix.com> <20030525102020.GA22040@panix.com> <20030623082736.GA8364@panix.com> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 11:27:12 -0000 It might be too early for the device to start probing. Try the following patch: Index: firewire.c =================================================================== RCS file: /home/ncvs/src/sys/dev/firewire/firewire.c,v retrieving revision 1.53 diff -u -r1.53 firewire.c --- firewire.c 15 Jun 2003 04:09:26 -0000 1.53 +++ firewire.c 23 Jun 2003 11:25:48 -0000 @@ -1204,7 +1204,7 @@ } else fc->status = FWBUSMGRDONE; - callout_reset(&fc->busprobe_callout, hz/4, + callout_reset(&fc->busprobe_callout, hz*2, (void *)fw_bus_probe, (void *)fc); } /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Mon, 23 Jun 2003 20:05:39 +0900, Hidetoshi Shimokawa wrote: > > I suppose there is something wrong with the hardware. > CAM debug shouldn't help for this case. > > Can you use this device with the machine without problem in other OS? > > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > > > At Mon, 23 Jun 2003 04:27:36 -0400, > David Kleiner wrote: > > > > [1 ] > > Shimokawa-san, > > > > I believe, a while ago I have replied to your suggestion to try lower speed - it didn't > > change things much. > > > > I have enabled CAMDEBUG in my kernel config, I've attached the log to this mail. > > The bottom line is this: camcontrol reset does not work. Camcontrol rescan all > > hangs and camcontrol reset all hangs the laptop (no response to keyboard/mouse > > fan noise is high). Perhaps I need to point out that this is an I-Link to > > firewire cable - this laptop only has Sony I-Link socket. The multiple lines > > are due to turning on/off the drive and plugging/unplugging the firewire cable. > > > > > > I am running -CURRENT, with WITNESS'es: > > > > FreeBSD wallaby.homeunix.net 5.1-CURRENT FreeBSD 5.1-CURRENT #28: > > Mon Jun 23 00:23:40 PDT 2003 > > > > Please let me know if you need any additional information or if I can add debugging > > to f/w probes. > > > > Thank you, From owner-freebsd-firewire@FreeBSD.ORG Mon Jun 23 04:29:03 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 50BBD37B401 for ; Mon, 23 Jun 2003 04:29:03 -0700 (PDT) Received: from mail.drunkencomputing.de (ratz.drunkencomputing.de [195.244.235.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FCDA43FE1 for ; Mon, 23 Jun 2003 04:29:02 -0700 (PDT) (envelope-from hscholz@raisdorf.net) Received: from localhost (localhost [127.0.0.1]) by mail.drunkencomputing.de (Postfix) with ESMTP id 666E28AF68 for ; Mon, 23 Jun 2003 13:30:06 +0200 (CEST) Received: from mail.drunkencomputing.de ([127.0.0.1])port 10024) with ESMTP id 83040-04 for ; Mon, 23 Jun 2003 13:30:05 +0200 (CEST) Received: from goanna.lan.raisdorf.net (pD952702B.dip.t-dialin.net [217.82.112.43]) by mail.drunkencomputing.de (Postfix) with ESMTP id 097A58AF67 for ; Mon, 23 Jun 2003 13:30:04 +0200 (CEST) Date: Mon, 23 Jun 2003 13:28:56 +0200 From: Hendrik Scholz To: firewire@freebsd.org Message-Id: <20030623132856.05a2346b.hscholz@raisdorf.net> In-Reply-To: References: <20030623105128.4d7d6fd5.hscholz@raisdorf.net> X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at drunkencomputing.de Subject: Re: Ricoh R5C551 support on Samsung Q10 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: Mon, 23 Jun 2003 11:29:03 -0000 Hi! On Mon, 23 Jun 2003 20:01:33 +0900 Hidetoshi Shimokawa wrote: > How about if you disable ACPI or disalbe PnP-OS setting in BIOS? I checked all combinations with ACPI on/off PNP on/off and always encounter the same problem. Beside that wi0 (mini pci lucent) doesn't work when ACPI is off. Hendrik -- Hendrik Scholz - - http://raisdorf.net/ Forcast for tonight: Dark. 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 ... ] > > > From owner-freebsd-firewire@FreeBSD.ORG Tue Jun 24 01:44:13 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 1215137B401 for ; Tue, 24 Jun 2003 01:44:13 -0700 (PDT) Received: from maltanet.net (mailer1.maltanet.net [194.158.37.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B94F543FAF for ; Tue, 24 Jun 2003 01:44:11 -0700 (PDT) (envelope-from peterk@maltanet.net) Received: (qmail 10513 invoked from network); 24 Jun 2003 08:44:06 -0000 Received: from unknown (HELO webmail.maltanet.net) ([194.158.37.235]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 24 Jun 2003 08:44:06 -0000 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: EMUmail 4.0 X-Originating-Ip: 80.85.96.2 X-Webmail-User: peterk@maltanet.net To: freebsd-firewire@freebsd.org MIME-Version: 1.0 X-Http_host: webmail.maltanet.net From: Peter Korsten Date: Tue, 24 Jun 2003 9:50:03 CET Message-Id: <20030624084411.B94F543FAF@mx1.FreeBSD.org> Subject: Card advice sought X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Korsten List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 08:44:13 -0000 This may be slightly off-topic, for which I apoligise. I would like to put a firewire card in my aging P2-350, to connect my Canon MV 600i DV (once I get it) and after some negative experiences with no-name peripherals, I prefer a known brand. Needless to say, it should work well with FreeBSD. Are there certain cards to be recommended? Asus, for instance? Certain cards or chipsets to avoid? Thank you, - Peter -- ------------------------------------------------------------------------------------------------------------------------------------------------- Birthdays? Anniversaries? Send a gift online from http://shop.di-ve.com . FREE DELIVERY TO MALTA ADDRESSES From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 03:17:34 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 DC5B137B401 for ; Fri, 27 Jun 2003 03:17:34 -0700 (PDT) Received: from internal.mail.uk.tiscali.com (internal.mail.uk.tiscali.com [212.74.96.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id E491B43FAF for ; Fri, 27 Jun 2003 03:17:29 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by internal.mail.uk.tiscali.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 19VqII-0004Rl-00 for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 11:17:27 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19VqJV-000Fq8-AP for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 11:18:41 +0100 Date: Fri, 27 Jun 2003 11:18:41 +0100 From: Brian Candler To: freebsd-firewire@freebsd.org Message-ID: <20030627101841.GA60838@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Firewire resets/performance problems 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: Fri, 27 Jun 2003 10:17:35 -0000 I have FreeBSD-4.8 running with a Lucent DV1000LE card. I have it talking to my brand new Apple iPod (new-style, 15GB), which seems to be detected fine; relevant log messages are attached below. However I have a couple of problems which I think are related: (1) Data transfer is extremely slow. Using 'dd' to read from /dev/da0, I get perhaps 10MB per minute; using 'dd' to write is maybe 3MB per minute max. (2) About every 2 seconds I get the following kernel message logged: sbp:0:0:0 No additional information to report Setting debug.firewire_debug=1 doesn't show anything extra. Setting debug.sbp_debug does give some additional information which doesn't mean much to me, apart from the fact that it seems to be doing a lot of bus resets and attaches, and "dead:1" doesn't look healthy either :-( Jun 27 11:03:01 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:01 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:000010c10 Jun 27 11:03:01 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:01 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 1a 00 0a 00 14 00 00 00 00 00, flags: 0x40, 6b cmd/20b data/32b sense Jun 27 11:03:01 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 0 qlfr 0 len 2 Jun 27 11:03:01 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:01 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:03 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:03 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:000010fac Jun 27 11:03:03 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:03 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense Jun 27 11:03:03 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 26 qlfr 1 len 2 Jun 27 11:03:03 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:03 playdog /kernel: sbp0:0:0 sbp_cam_scan_lun Jun 27 11:03:03 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:05 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:05 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:000011a80 Jun 27 11:03:05 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:05 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 1a 00 0a 00 14 00 00 00 00 00, flags: 0x40, 6b cmd/20b data/32b sense Jun 27 11:03:05 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 0 qlfr 0 len 2 Jun 27 11:03:05 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:05 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:07 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:07 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:000011e1c Jun 27 11:03:07 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:07 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense Jun 27 11:03:07 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 26 qlfr 1 len 2 Jun 27 11:03:07 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:07 playdog /kernel: sbp0:0:0 sbp_cam_scan_lun Jun 27 11:03:07 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:09 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:09 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:000010270 Jun 27 11:03:09 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:09 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 1a 00 0a 00 14 00 00 00 00 00, flags: 0x40, 6b cmd/20b data/32b sense Jun 27 11:03:09 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 0 qlfr 0 len 2 Jun 27 11:03:09 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:09 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:11 playdog /kernel: sbp0:0:0 sbp_cam_scan_target Jun 27 11:03:11 playdog /kernel: sbp0:0:0 ORB status src:0 resp:0 dead:1 len:2 stat:0 orb:00001060c Jun 27 11:03:11 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 11:03:11 playdog /kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense Jun 27 11:03:11 playdog /kernel: sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 26 qlfr 1 len 2 Jun 27 11:03:11 playdog /kernel: sbp0:0:0 sbp_agent_reset Jun 27 11:03:11 playdog /kernel: sbp0:0:0 sbp_cam_scan_lun Jun 27 11:03:11 playdog /kernel: sbp0:0:0 sbp_do_attach Jun 27 11:03:13 playdog /kernel: sbp0:0:0 No additional information to report Any clues? Would setting any of the hw.firewire / kern.cam sysctl variables help? Cheers, Brian. Jun 27 08:52:55 playdog /kernel: fwohci0: mem 0xe4000000-0xe4000fff irq 9 at device 8.0 on pci0 Jun 27 08:52:55 playdog /kernel: fwohci0: PCI bus latency is 32. Jun 27 08:52:55 playdog /kernel: fwohci0: OHCI version 1.0 (ROM=1) Jun 27 08:52:55 playdog /kernel: fwohci0: No. of Isochronous channel is 8. Jun 27 08:52:55 playdog /kernel: fwohci0: EUI64 00:60:1d:00:00:00:c8:f5 Jun 27 08:52:55 playdog /kernel: fwohci0: Phy 1394a available S400, 3 ports. Jun 27 08:52:55 playdog /kernel: fwohci0: Link S400, max_rec 2048 bytes. Jun 27 08:52:55 playdog /kernel: firewire0: on fwohci0 Jun 27 08:52:55 playdog /kernel: fwohci0: Initiate bus reset Jun 27 08:52:55 playdog /kernel: fwohci0: BUS reset Jun 27 08:52:55 playdog /kernel: fwohci0: node_id = 0xc800ffc0, CYCLEMASTER mode Jun 27 08:52:55 playdog /kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Jun 27 08:52:55 playdog /kernel: sbp0: on firewire0 Jun 27 09:00:33 playdog /kernel: fwohci0: BUS reset Jun 27 09:00:33 playdog /kernel: fwohci0: node_id = 0x8800ffc0, non CYCLEMASTER mode Jun 27 09:00:33 playdog /kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) Jun 27 09:00:34 playdog /kernel: firewire0: New S400 device ID:000a2700020f9552 Jun 27 09:00:34 playdog /kernel: firewire0: Device SBP-II Jun 27 09:00:38 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 09:00:40 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 09:00:42 playdog /kernel: da0 at sbp0 bus 0 target 0 lun 0 Jun 27 09:00:42 playdog /kernel: da0: Removable Simplified Direct Access SCSI-2 device Jun 27 09:00:42 playdog /kernel: da0: 50.000MB/s transfers, Tagged Queueing Enabled Jun 27 09:00:42 playdog /kernel: da0: 14305MB (29297520 512 byte sectors: 255H 63S/T 1823C) Jun 27 09:00:42 playdog /kernel: sbp0:0:0 No additional information to report From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 04:02:08 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 7671837B401 for ; Fri, 27 Jun 2003 04:02:08 -0700 (PDT) Received: from internal.mail.uk.tiscali.com (internal.mail.uk.tiscali.com [212.74.96.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F91143F3F for ; Fri, 27 Jun 2003 04:02:05 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by internal.mail.uk.tiscali.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 19VqzT-0006pO-00 for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 12:02:03 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19Vr0g-000Frh-1a for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 12:03:18 +0100 Date: Fri, 27 Jun 2003 12:03:17 +0100 From: Brian Candler To: freebsd-firewire@freebsd.org Message-ID: <20030627110317.GA60951@uk.tiscali.com> References: <20030627101841.GA60838@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030627101841.GA60838@uk.tiscali.com> User-Agent: Mutt/1.4.1i Subject: Re: Firewire resets/performance problems 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: Fri, 27 Jun 2003 11:02:08 -0000 On Fri, Jun 27, 2003 at 11:18:41AM +0100, Brian Candler wrote: > (1) Data transfer is extremely slow. Using 'dd' to read from /dev/da0, I get > perhaps 10MB per minute; using 'dd' to write is maybe 3MB per minute max. Supplementary information: My system also has a SCSI card with a couple of CD-ROMs on it, so that's scbus0 and the firewire is scbus1. I just tried removing the SCSI card and the firewire is zooming along (8MB per second!) This may or may not be a red herring - perhaps it's just the fact that I did a reboot - but is it possible that something is wrongly assuming the device to be on scbus0 when it's on scbus1 ? Regards, Bran. From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 10:38:35 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 5538737B401 for ; Fri, 27 Jun 2003 10:38:35 -0700 (PDT) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [133.11.205.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF38243FBD for ; Fri, 27 Jun 2003 10:38:33 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is2.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id E376E3782D0 for ; Sat, 28 Jun 2003 02:35:13 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h5RHZDo4014301; Sat, 28 Jun 2003 02:35:13 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJC00766; Sat, 28 Jun 2003 02:35:12 +0900 (JST) Date: Sat, 28 Jun 2003 02:35:12 +0900 Message-ID: From: Hidetoshi Shimokawa To: Brian Candler In-Reply-To: <20030627110317.GA60951@uk.tiscali.com> References: <20030627101841.GA60838@uk.tiscali.com> <20030627110317.GA60951@uk.tiscali.com> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 17:38:35 -0000 At Fri, 27 Jun 2003 12:03:17 +0100, Brian Candler wrote: > > On Fri, Jun 27, 2003 at 11:18:41AM +0100, Brian Candler wrote: > > (1) Data transfer is extremely slow. Using 'dd' to read from /dev/da0, I get > > perhaps 10MB per minute; using 'dd' to write is maybe 3MB per minute max. > > Supplementary information: > > My system also has a SCSI card with a couple of CD-ROMs on it, so that's > scbus0 and the firewire is scbus1. > > I just tried removing the SCSI card and the firewire is zooming along (8MB > per second!) > > This may or may not be a red herring - perhaps it's just the fact that I did > a reboot - but is it possible that something is wrongly assuming the device > to be on scbus0 when it's on scbus1 ? > > Regards, > > Bran. I thinks there is no difference between scbus0 and scbus1 at CAM layer. I suspect you have problem in PCI bus and removing the SCSI card hides the problem. You can easily exchange scbus 0 and 1 without removing the card by adding the following line into the kernel config file. device scbus0 at sbp0 /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 10:56:12 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 3D27637B404 for ; Fri, 27 Jun 2003 10:56:12 -0700 (PDT) Received: from internal.mail.uk.tiscali.com (internal.mail.uk.tiscali.com [212.74.96.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DBBA43FE3 for ; Fri, 27 Jun 2003 10:56:11 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by internal.mail.uk.tiscali.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 19VxSC-0004Ct-00; Fri, 27 Jun 2003 18:56:09 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19VxTO-000GC6-MB; Fri, 27 Jun 2003 18:57:22 +0100 Date: Fri, 27 Jun 2003 18:57:22 +0100 From: Brian Candler To: Hidetoshi Shimokawa Message-ID: <20030627175722.GA62233@uk.tiscali.com> References: <20030627101841.GA60838@uk.tiscali.com> <20030627110317.GA60951@uk.tiscali.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: Firewire resets/performance problems 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: Fri, 27 Jun 2003 17:56:12 -0000 On Sat, Jun 28, 2003 at 02:35:12AM +0900, Hidetoshi Shimokawa wrote: > > My system also has a SCSI card with a couple of CD-ROMs on it, so that's > > scbus0 and the firewire is scbus1. > > > > I just tried removing the SCSI card and the firewire is zooming along (8MB > > per second!) > > > > This may or may not be a red herring - perhaps it's just the fact that I did > > a reboot - but is it possible that something is wrongly assuming the device > > to be on scbus0 when it's on scbus1 ? > > > > Regards, > > > > Bran. > > I thinks there is no difference between scbus0 and scbus1 at CAM > layer. I suspect you have problem in PCI bus and removing the SCSI card > hides the problem. > > You can easily exchange scbus 0 and 1 without removing the card by > adding the following line into the kernel config file. > > device scbus0 at sbp0 Cheers. I have actually done some further reboots, with the SCSI card in place, and it's intermittent. Sometimes when I boot everything works fine; sometimes when I boot, and then attach the iPod, I get what appears to be an infinite loop of: fwohci0: BUS reset fwohci0: node_id = 0xc800ffc0, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) (logged once per second). In that case it never gets as far as making detecting da0 and making it available. I did a hard power-cycle of the machine, without unplugging any cards, and it worked after that. So now my best guess is that there's something in the Lucent chipset which is not getting properly initialised. It seems to work more often than it doesn't, and it works really well when it does. Regards, Brian. From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 11:30:38 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 1990537B401 for ; Fri, 27 Jun 2003 11:30:38 -0700 (PDT) Received: from internal.mail.uk.tiscali.com (internal.mail.uk.tiscali.com [212.74.96.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF3D43FAF for ; Fri, 27 Jun 2003 11:30:37 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by internal.mail.uk.tiscali.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 19VxzX-0005g2-00; Fri, 27 Jun 2003 19:30:36 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19Vy0k-000GD5-BB; Fri, 27 Jun 2003 19:31:50 +0100 Date: Fri, 27 Jun 2003 19:31:50 +0100 From: Brian Candler To: Hidetoshi Shimokawa Message-ID: <20030627183150.GA62268@uk.tiscali.com> References: <20030627101841.GA60838@uk.tiscali.com> <20030627110317.GA60951@uk.tiscali.com> <20030627175722.GA62233@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030627175722.GA62233@uk.tiscali.com> User-Agent: Mutt/1.4.1i cc: freebsd-firewire@freebsd.org Subject: Re: Firewire resets/performance problems 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: Fri, 27 Jun 2003 18:30:38 -0000 On Fri, Jun 27, 2003 at 06:57:22PM +0100, Brian Candler wrote: > So now my best guess is that there's something in the Lucent chipset which > is not getting properly initialised. Another symptom I just saw: I connected my iPod and got Jun 27 18:58:22 playdog /kernel: fwohci0: BUS reset Jun 27 18:58:22 playdog /kernel: fwohci0: node_id = 0x8800ffc0, non CYCLEMASTER mode Jun 27 18:58:22 playdog /kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) Jun 27 18:58:23 playdog /kernel: firewire0: New S400 device ID:000a2700020f9552 Jun 27 18:58:23 playdog /kernel: firewire0: Device SBP-II Jun 27 18:58:30 playdog /kernel: sbp0:0:0 No additional information to report Now I get this sbp0:0:0 message repeated every two seconds, and it does not get as far as detecting the iPod as da0. If I try to reset the bus: playdog# camcontrol reset 1 Reset of bus 1 returned error 0x6 Disconnecting the iPod and doing 'fwcontrol -r' doesn't help, I get the same symptom when I reconnect the iPod. So I did a reboot and pressed the hard-reset button (but did not power-cycle). On the next bootup it was detected properly: Jun 27 19:04:09 playdog /kernel: firewire0: New S400 device ID:000a2700020f9552 Jun 27 19:04:09 playdog /kernel: firewire0: Device SBP-II Jun 27 19:04:15 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 19:04:17 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 19:04:19 playdog /kernel: da0 at sbp0 bus 0 target 0 lun 0 Jun 27 19:04:19 playdog /kernel: da0: Removable Simplified Direct Access SCSI-2 device Jun 27 19:04:19 playdog /kernel: da0: 50.000MB/s transfers, Tagged Queueing Enabled Jun 27 19:04:19 playdog /kernel: da0: 14305MB (29297520 512 byte sectors: 255H 63S/T 1823C) Jun 27 19:04:19 playdog /kernel: sbp0:0:0 No additional information to report Jun 27 19:04:19 playdog last message repeated 3 times Notice how the "sbp0:0:0 No additional information" message appears a few times anyway. But after this I can mount the device and copy files to it (quickly) Cheers, Brian.