Date: Fri, 16 Apr 2010 01:30:08 GMT From: Andrew Reilly <areilly@bigpond.net.au> To: freebsd-firewire@FreeBSD.org Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Message-ID: <201004160130.o3G1U8xr002447@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/136652; it has been noted by GNATS. From: Andrew Reilly <areilly@bigpond.net.au> To: bug-followup@FreeBSD.org, sbruno@FreeBSD.org Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Date: Fri, 16 Apr 2010 11:28:43 +1000 Hi there, I'm afraid that this problem is back, now that I'm running -CURRENT. One extra piece of information that I can add is that I don't have to actually power-cycle the drive to make it show up: if I run "fwcontrol -r" after boot, then dmesg says: fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2, 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: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' da0 at sbp0 bus 0 scbus0 target 0 lun 0 da0: <WD My Book 1028> Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) ses0 at sbp0 bus 0 scbus0 target 0 lun 1 ses0: <WD My Book Device > Fixed Enclosure Services SCSI-4 device ses0: 50.000MB/s transfers ses0: SCSI-3 SES Device GEOM_JOURNAL: Journal 153133090: da0s1a contains data. GEOM_JOURNAL: Journal 153133090: da0s1a contains journal. GEOM_JOURNAL: Journal da0s1a clean. The relevant pieces of boot-time dmesg (from dmesg.boot) are: 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 fwohci0 fwe0: <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 firewire0 dcons_crom0: bus_addr 0x1194000 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' ... and that's all. da0 doesn't show up until after I manually reset the bus (or power-cycle the drive). Please let me know if there are any other experiments that I can run, or information that I can provide that might help diagnose the problem. Cheers, -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201004160130.o3G1U8xr002447>