Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Aug 2014 19:52:23 -0400
From:      Julio Merino <jmmv@freebsd.org>
To:        freebsd-ppc@freebsd.org
Subject:   Problems with Firewire drive
Message-ID:  <CAFY7cWC3ggT-fjo1Z4pHWhMxWZc20r3_md_SzBwmXgGn8e%2B8fg@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
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: <SBP-2/SCSI over FireWire> 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!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFY7cWC3ggT-fjo1Z4pHWhMxWZc20r3_md_SzBwmXgGn8e%2B8fg>