From owner-freebsd-ppc@FreeBSD.ORG Tue Aug 19 23:59:31 2014 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83C0A8C5 for ; Tue, 19 Aug 2014 23:59:31 +0000 (UTC) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46C373F36 for ; Tue, 19 Aug 2014 23:59:30 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id f51so6670839qge.39 for ; Tue, 19 Aug 2014 16:59:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:content-type; bh=dvByGiYSdNf/GPs2YXA5M08rIhBi8sCf/+BBQLulU4s=; b=iI3j1QfBdL9av7acKLzgRhZAhPGryqldNBIz0K+43aX9M1ufwf/jpNd0ATwtxx4c/C M5mHgwtamUr79+3DuRN8nmOJ4sH3s2KAcHtuwtjnj1wG6k0Qggju2gzl/U/Iy7YKdEvj 0wXTm6gID17p+GHL81IAC74HxkmIsDZlmynUV5WTR7iNVKfv/kd2T6oJDsvIj5jUrdqL 81+gv7thDwfaw7iobYemuteIzNFoS9rbrIcL7xPR1gFdAhcKA0owXTz5NGxFtfhWCOvj OwaT3/BEkOdl3FDSd7jxteZjkVYV44vUTmlPpUVb0zYwml8qnwN7x3M0tfGzMg50bJkH H5Dw== X-Gm-Message-State: ALoCoQkDtV8b0kwVRvX4uaJkmfQ68+5hORlpFI+kaEiC5gDeibcD06THp2WAvkdAaY2Cb8x5xqpB X-Received: by 10.140.46.55 with SMTP id j52mr69052076qga.27.1408492363467; Tue, 19 Aug 2014 16:52:43 -0700 (PDT) MIME-Version: 1.0 Sender: jmmv@meroh.net Received: by 10.96.83.99 with HTTP; Tue, 19 Aug 2014 16:52:23 -0700 (PDT) X-Originating-IP: [184.153.117.174] From: Julio Merino Date: Tue, 19 Aug 2014 19:52:23 -0400 X-Google-Sender-Auth: 5UH3cMXD5PU-VjpdXyf7WkMbmno Message-ID: Subject: Problems with Firewire drive To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 23:59:31 -0000 Hello, I'm trying to use a Firewire hard drive on my PowerMac G5 running FreeBSD current and am encountering some problems. The reason? Using the G5 to evaluate if I can migrate my G4 Mini home server to FreeBSD ;-) The drive works just fine when plugged via USB, but when connecting it to FW400 it does not seem to be recognized. An excerpt from dmesg: sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2, CYCLEMASTER mode [...] fwohci0: txd err= 3 miss Ack err firewire0: fw_explore_node: fwdev->speed(S800) decremented due to negotiation firewire0: New S400 device ID:00d04b831607baa9 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:14 EUI:00d04b831607baa9 node:0 speed:2 maxrec:8uhub4: 5 ports with 5 removable, self powered sbp0: sbp_show_sdev_info: sbp0:0:0 'LaCie' 'd2 quadra' '000110' lock order reversal: 1st 0x17f3f48 sbp (sbp) @ /home/jmmv/os/freebsd/base/head/sys/kern/kern_mutex.c:159 2nd 0xc00000000ad84870 firewire (firewire) @ /home/jmmv/os/freebsd/base/head/sys/dev/firewire/firewire.c:318 KDB: stack backtrace: 0xc0000000c3e9a120: at .kdb_backtrace+0x5c 0xc0000000c3e9a250: at ._witness_debugger+0x3c 0xc0000000c3e9a2e0: at .witness_checkorder+0xa7c 0xc0000000c3e9a3d0: at .__mtx_lock_flags+0x100 0xc0000000c3e9a470: at .fw_asyreq+0x358 0xc0000000c3e9a520: at .sbp_mgm_orb+0x30c 0xc0000000c3e9a5d0: at .sbp_login_callout+0x48 0xc0000000c3e9a660: at .softclock_call_cc+0x1f8 0xc0000000c3e9a780: at .softclock+0xb4 0xc0000000c3e9a800: at .intr_event_execute_handlers+0x168 0xc0000000c3e9a8a0: at .ithread_loop+0xd0 0xc0000000c3e9a960: at .fork_exit+0xd0 0xc0000000c3e9aa00: at .fork_trampoline+0x10 0xc0000000c3e9aa30: at fffffffffffffffc I don't know if the witness-generated backtrace is a problem given that witness is only logging events (and disabled after boot). But it indeed seems like a problem. Any thoughts? Suggestions? Thanks!