Date: Fri, 2 Jul 2010 09:46:27 +1000 From: Andrew Reilly <areilly@bigpond.net.au> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/148302: Firewire-attached "My Book" drive gets no device node at boot time, but does after Message-ID: <1278027987.56113@duncan.reilly.home> Resent-Message-ID: <201007012350.o61No1hN080691@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 148302
>Category: kern
>Synopsis: Firewire-attached "My Book" drive gets no device node at boot time, but does after
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jul 01 23:50:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Andrew Reilly
>Release: FreeBSD 9.0-CURRENT amd64
>Organization:
>Environment:
System: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #4: Sat Jun 26 00:24:47 EST 2010 root@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64
Machine is an AthlonX2-4200 on a Gigabyte motherboard with NVidia chipset.
>Description:
This isn't really a new problem, but I noticed that the original report that I made (kern/136652) has been closed.
Apparently I reported that the problem had gone away. I can't remember when it re-appeared, but it's back. Perhaps it
came back after I upgraded to current from stable?
Anyway, the problem is that the firewire stack seems to "see" the drive at boot (mentions it in the dmesg lines, eg:)
fwohci0: <Texas Instruments TSB82AA2> mem 0xf2004000-0xf20047ff,0xf2000000-0xf2003fff irq 18 at device 10.0 on pci1
fwohci0: [ITHREAD]
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:14:85:56:00:e6:80:b0
fwohci0: invalid speed 7 (fixed to 3).
fwohci0: Phy 1394a available S800, 3 ports.
fwohci0: Link S800, max_rec 4096 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:14:85:e6:80:b0
fwe0: Ethernet address: 02:14:85:e6:80:b0
fwip0: <IP over FireWire> on firewire0
fwip0: Firewire address: 00:14:85:56:00:e6:80:b0 @ 0xfffe00000000, S800, maxrec 4096
sbp0: <SBP-2/SCSI over FireWire> on firewire0
dcons_crom0: <dcons configuration ROM> on firewire0dcons_crom0: bus_addr 0x11c4000
fwohci0: Initiate bus reset
fwohci0: fwohci_intr_core: BUS reset
fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=1, CYCLEMASTER mode
:
:
firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me)
firewire0: bus manager 1
fwohci0: phy int
:
:
firewire0: New S800 device ID:0090a97488ce53aa
sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8
sbp0: sbp_show_sdev_info: sbp0:0:0 'WD' 'My Book' '001028'
sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:13 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8
sbp0: sbp_show_sdev_info: sbp0:0:1 'WD' 'My Book' '001028'
:
:
but /dev/da0 does not show up until after boot, after I've
manually run "fwcontrol -r".
This This doesn't seem to be critical, because if I'm careful
I know how to work around the problem, but it does mean that
I have to remember to comment that drive out of /etc/fstab
before I reboot remotely, or the box will wind up sitting in
single-user mode after failing the fsck -p pass...
>How-To-Repeat:
Works (or fails to) every time, on my hardware. Not
sure how to replicate it elsewhere.
>Fix:
No fix, but my work-around is to have an rc script that
tweaks that drive out of fstab on shutdown, and tweaks
it back in on boot, then fwcontrol -r/sleep/fsck -p
manually.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1278027987.56113>