freebsd stable - Aug 2012 - unrecognised external drive

Hi all, I bought a Western Digital external drive a few months ago
but it gets kicked out 20 seconds after I plug it in. I've updated to
the latest 8.3-STABLE:

$ uname -a
FreeBSD file 8.3-STABLE FreeBSD 8.3-STABLE #0: Sun Aug 12 12:45:04 SAST 2012    
root@file:/usr/obj/usr/src/sys/COWNEL  amd64

Aug 12 15:49:55 file kernel: ugen4.2: <Western Digital> at usbus4
Aug 12 15:49:55 file kernel: umass0: <MSC Bulk-Only Transport> on usbus4
Aug 12 15:49:55 file kernel: umass0:  SCSI over Bulk-Only; quirks = 0x4101
Aug 12 15:49:55 file kernel: umass0:5:0:-1: Attached to scbus5
Aug 12 15:50:15 file kernel: (da0:umass-sim0:0:0:0): got CAM status 0x4
Aug 12 15:50:15 file kernel: (da0:umass-sim0:0:0:0): fatal error, failed to
attach to device
Aug 12 15:50:15 file kernel: (da0:umass-sim0:0:0:0): lost device - 0
outstanding, 3 refs
Aug 12 15:50:15 file kernel: (da0:umass-sim0:0:0:0): removing device entry

and 

Aug 12 16:10:15 file kernel: ugen4.2: <Western Digital> at usbus4
(disconnected)
Aug 12 16:10:15 file kernel: umass0: at uhub4, port 5, addr 2 (disconnected)
Aug 12 16:10:38 file kernel: ugen4.2: <Western Digital> at usbus4
Aug 12 16:10:38 file kernel: umass0: <MSC Bulk-Only Transport> on usbus4
Aug 12 16:10:38 file kernel: umass0:  SCSI over Bulk-Only; quirks = 0x4101
Aug 12 16:10:38 file kernel: umass0:5:0:-1: Attached to scbus5
Aug 12 16:10:57 file kernel: (da0:umass-sim0:0:0:0): got CAM status 0x4
Aug 12 16:10:57 file kernel: (da0:umass-sim0:0:0:0): fatal error, failed to
attach to device
Aug 12 16:10:57 file kernel:
Aug 12 16:10:57 file kernel: (da0:umass-sim0:0:0:0): lost device - 0
outstanding, 3 refs
Aug 12 16:10:57 file kernel: (da0:umass-sim0:0:0:0): removing device entry
Aug 12 16:12:55 file kernel: ugen4.2: <Western Digital> at usbus4
(disconnected)
Aug 12 16:12:55 file kernel: umass0: at uhub4, port 6, addr 2 (disconnected)

My kernel is slightly stripped but the relevant parts are included afaik - other
drives mount fine. Same thing happens with a GENERIC but older kernel:

$ uname -a
FreeBSD imap1 9.0-STABLE FreeBSD 9.0-STABLE #0: Thu Jun  7 07:51:08 SAST 2012   
root@imap1:/usr/obj/usr/src/sys/GENERIC  amd64

Aug 13 09:58:20 imap1 kernel: ugen1.4: <Western Digital> at usbus1
Aug 13 09:58:20 imap1 kernel: umass1: <MSC Bulk-Only Transport> on usbus1
Aug 13 09:58:20 imap1 kernel: umass1:  SCSI over Bulk-Only; quirks = 0x4101
Aug 13 09:58:20 imap1 kernel: umass1:19:1:-1: Attached to scbus19
Aug 13 09:58:39 imap1 kernel: (da1:umass-sim1:1:0:0): got CAM status 0x4
Aug 13 09:58:39 imap1 kernel: (da1:umass-sim1:1:0:0): fatal error, failed to
attach to device
Aug 13 09:58:39 imap1 kernel: (da1:umass-sim1:1:0:0): lost device - 0
outstanding, 3 refs
Aug 13 09:58:40 imap1 kernel: (da1:umass-sim1:1:0:0): removing device entry
Aug 13 09:59:06 imap1 kernel: ugen1.4: <Western Digital> at usbus1
(disconnected)
Aug 13 09:59:06 imap1 kernel: umass1: at uhub1, port 3, addr 4 (disconnected)

The drive works on linux, is it not supported on FreeBSD?

Some info from the linux machine:

Aug 14 18:27:32 fire kernel: [338650.300883] scsi 6:0:0:0: Direct-Access     WD 
Elements 1042    1007 PQ: 0 ANSI: 6

lsusb -v:

Bus 002 Device 003: ID 1058:1042 Western Digital Technologies, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1058 Western Digital Technologies, Inc.
  idProduct          0x1042 
  bcdDevice           10.07
  iManufacturer           1 Western Digital
  iProduct                2 Elements 1042
  iSerial                 5 575846314331324537303135
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 USB Mass Storage
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              6 MSC Bulk-Only Transport
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Hi,

On Tue, 14 Aug 2012 18:34:37 +0200
Gareth de Vaux <bsd@lordcow.org> wrote:
>   idVendor           0x1058 Western Digital Technologies, Inc.
>   idProduct          0x1042 
could it be that the kernel does not know this product?

You can check the sources (usbdevs should be the name of the file) and
add this ID by copying an entry from another WD product which could be
the same.

This works some times but also can fail some time.

Erich