kern/148302: Firewire-attached "My Book" drive gets no device node at boot time, but does after

[Garrett Cooper]

On Jul 4, 2010, at 4:48 PM, Andrew Reilly wrote:

> Hi Garrett,
> 
> On Thu, Jul 01, 2010 at 09:48:48PM -0700, Garrett Cooper wrote:
>> On Thu, Jul 1, 2010 at 6:35 PM, Andrew Reilly <areilly at bigpond.net.au> wrote:
>>> Noauto on its own prevents the mount, but it does not stop the
>>> fsck pass, which fails because the device isn't present yet,
>>> which leaves you in single-user mode.  If I change the last
>>> digit (the fsck pass number) to zero, then that should fix that
>>> problem, too.  Wonder why that never occurred to me before?
>> 
>> That seems a bit off, but I need to read some documentation to clarify
>> first. Hmmm..
> 
> Actually, it's dramatically worse than that, now that I've tried
> it!  On the up-side, the system boots cleanly now, without
> manual intervention.  On the downside, I can't make that
> firewire drive show up *at all*, at least not remotely.  I still
> have a hope that if I physically power cycle the drive then
> perhaps it will "arrive", but I'm not in the same building for
> another several hours, so can't just try it.  Grr.
> 
> At least the log messages are different, now:
> 
> Jul  5 09:39:53 duncan kernel: fwohci0: Initiate bus reset
> Jul  5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: BUS reset
> Jul  5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: node_id=0x00000002, SelfID Count=2, CYCLEMASTER mode
> Jul  5 09:39:53 duncan kernel: firewire0: 3 nodes, maxhop <= 2 cable IRM irm(2)  (me) 
> Jul  5 09:39:53 duncan kernel: firewire0: bus manager 2 
> Jul  5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X
> Jul  5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure
> Jul  5 09:39:53 duncan kernel: firewire0: New S800 device ID:0090a97488ce53aa
> Jul  5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X
> Jul  5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure
> Jul  5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X
> Jul  5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure
> Jul  5 09:39:53 duncan kernel: firewire0: fw_attach_dev:Removing missing device ID:0090a97488ce53aa
> 
> I never used to get those explore_read_quads failure messages.
> Perhaps I should post this to the firewire group?

	Sure -- that's definitely a good idea to post to the firewire group. CCing Sean Bruno for visibility in the issue.
Thanks!
-Garrett