From owner-freebsd-firewire@FreeBSD.ORG Mon Mar 16 11:06:54 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D48F01065680 for ; Mon, 16 Mar 2009 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C16EC8FC0A for ; Mon, 16 Mar 2009 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2GB6rdA043220 for ; Mon, 16 Mar 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2GB6rYe043216 for freebsd-firewire@FreeBSD.org; Mon, 16 Mar 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Mar 2009 11:06:53 GMT Message-Id: <200903161106.n2GB6rYe043216@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 11:06:55 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 7 problems total. From owner-freebsd-firewire@FreeBSD.ORG Mon Mar 16 12:09:15 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BB551065A9F for ; Mon, 16 Mar 2009 12:09:15 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 107298FC17 for ; Mon, 16 Mar 2009 12:09:14 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: by wa-out-1112.google.com with SMTP id k34so1850236wah.27 for ; Mon, 16 Mar 2009 05:09:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:organization:to:subject :date:user-agent:cc:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=nnxLP4TAM+kMTN/k1G3QfKffWmpC2L/hL4So3Wi6eAs=; b=o/3JMhJTDNwzVV18WqNO+g3glL2ovkwnOkvgkCeFXK7lskGe/jH4VUyWg77yX1sU9a bHkeAbRDl1z+3Fp9lUnaPtdfIHkfJn1xvvJrvwV7Og/H37Jjg5SX+dPiJykze4QtBywj zOcfi6wn+l17UzUojHarzHf8OCLv+k/u2MZYI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:organization:to:subject:date:user-agent:cc:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=XQQHs+SVTdvaTsm+Zc/u4Wi89sl7b3qLo/2034jodUmieFZbwX3BKgQFrqMo6UKDlt +rWEp8wIjtupZkcbutuiT78ZB7KOFLDrzyrMPZzCxP9/iCrluze6zARHYQzqJ4aicVpR G8GbDEX6HT24lS4O53wyEsNWg34vRxIAUeR9A= Received: by 10.115.94.1 with SMTP id w1mr3228511wal.30.1237205354618; Mon, 16 Mar 2009 05:09:14 -0700 (PDT) Received: from host7.net62.hdsl-213-169.fastbg.net (host7.net62.HDSL-213-169.FastBG.NET [213.169.62.7]) by mx.google.com with ESMTPS id z20sm20760358pod.26.2009.03.16.05.09.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 16 Mar 2009 05:09:10 -0700 (PDT) From: Boris Kotzev Organization: Home To: Sean Bruno Date: Mon, 16 Mar 2009 14:08:50 +0200 User-Agent: KMail/1.11.1 (FreeBSD/8.0-CURRENT; KDE/4.2.1; amd64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903161408.51018.boris.kotzev@gmail.com> Cc: freebsd-firewire@freebsd.org Subject: firewire disk stopped working X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 12:09:24 -0000 >On Fri, 2009-03-13 at 14:42 +0900, Hidetoshi Shimokawa wrote: >> Hi Sean, >> >> It looks like you broke Configuration ROM build procedure in firewire stack in >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/firewire/firewire.c.diff?r1=1.104;r2=1.105 >> >> In this change, you just copy "src" to "fc->config_rom" but it's wrong. >> You have to call crom_load() to get CROM built correctly. >> It is a critical problem for SCSI and dcons(4) target that highly >> depend on CROM. >> I think you can easily check this problem by 'fwcontrol -c [your own node_id]', >> you'll get broken CROM and CRC. If there are anything I can help you to fix this >> bug, let me know. >> >> Thanks, >> >> Hidetoshi at AsiaBSDCon2009 >> >> @@ -739,19 +758,19 @@ fw_busreset(struct firewire_comm *fc, ui >> free(devlistp, M_TEMP); >> } >> >> - newrom = malloc(CROMSIZE, M_FW, M_NOWAIT | M_ZERO); >> src = &fc->crom_src_buf->src; >> - crom_load(src, (uint32_t *)newrom, CROMSIZE); >> - if (bcmp(newrom, fc->config_rom, CROMSIZE) != 0) { >> - /* bump generation and reload */ >> - src->businfo.generation ++; >> - /* generation must be between 0x2 and 0xF */ >> - if (src->businfo.generation < 2) >> - src->businfo.generation ++; >> - crom_load(src, (uint32_t *)newrom, CROMSIZE); >> - bcopy(newrom, (void *)fc->config_rom, CROMSIZE); >> - } >> - free(newrom, M_FW); >> + /* >> + * If the old config rom needs to be overwritten, >> + * bump the businfo.generation indicator to >> + * indicate that we need to be reprobed >> + */ >> + if (bcmp(src, fc->config_rom, CROMSIZE) != 0) { >> + /* generation is a 2 bit field */ >> + /* valid values are only from 0 - 3 */ >> + src->businfo.generation = 1; >> + bcopy(src, (void *)fc->config_rom, CROMSIZE); >> + } else >> + src->businfo.generation = 0; >> } >> >> /* Call once after reboot */ >> @@ -807,13 +826,7 @@ void fw_init(struct firewire_comm *fc) > >Please give this patch at try. I think this should work. > >Sean After updating the source to CURRENT from yesterday and applying your last patch to firewire.c, I found out that the external firewire disk was functional again. The system information is: FreeBSD laptop.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Mar 16 09:13:13 EET 2009 user@laptop.universe:/mnt/ufs/usr/src/sys/CUSTOM amd64 When the disk attaches the dmesg output is: fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=3, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 firewire0: New S400 device ID:0020370004a03421 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0020370004a03421 node:0 speed:2 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'Seagate' 'ATA Device 00' '000102' fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=4, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0020370004a03421 node:0 speed:2 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'Seagate' 'ATA Device 00' '000102' da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 715404MB (1465149168 512 byte sectors: 255H 63S/T 91201C) I have not done much testing - so far it seems to be working o.k. Thank you very much! Best regards, Boris Kotzev From owner-freebsd-firewire@FreeBSD.ORG Tue Mar 17 13:45:22 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D03F10656D2 for ; Tue, 17 Mar 2009 13:45:22 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 0FDD18FC35 for ; Tue, 17 Mar 2009 13:45:21 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 20624 invoked from network); 17 Mar 2009 06:42:33 -0700 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 17 Mar 2009 06:42:33 -0700 From: Sean Bruno To: freebsd-firewire@freebsd.org Content-Type: text/plain Date: Tue, 17 Mar 2009 06:45:20 -0700 Message-Id: <1237297520.27904.67.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10) Content-Transfer-Encoding: 7bit Cc: Torfinn Ingolfsen , Nathan Whitehorn , Boris Kotzev Subject: Firewire Updates X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 13:45:22 -0000 I just patched -CURRENT today. Let me know what's still broken and I'll look into it. I think that there is still an issue with dcons between PPC and x86_64? Sean