Bug 194633

Summary:	FreeBSD 10.1-RC3 can't detect all available USB devices
Product:	Base System	Reporter:	rff1917
Component:	usb	Assignee:	freebsd-usb (Nobody) <usb>
Status:	Closed Feedback Timeout
Severity:	Affects Only Me	CC:	arrowd, hselasky, mav
Priority:	---
Version:	10.1-STABLE
Hardware:	i386
OS:	Any

Description rff1917 2014-10-27 15:07:53 UTC

The device is a portable MP3 player.

On FreeBSD 9.1, its internal memory is detected as da0 and the micro-SD card extension is detected as da1. Both can be mounted read-write without any issue.

On FreeBSD 10.1-RC3, only the internal memory is detected and can be mounted. No da1 is visible in /dev.


Following is the output of /var/log/messages on both systems:

ON 10.1-RC3
===========

Oct 27 16:17:55 pc1 kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
Oct 27 16:17:55 pc1 kernel: da0: <Intenso VideoShooter 0100> Removable Direct Access SCSI-0 device 
Oct 27 16:17:55 pc1 kernel: da0: Serial Number K
Oct 27 16:17:55 pc1 kernel: da0: 40.000MB/s transfers
Oct 27 16:17:55 pc1 kernel: da0: 3748MB (7675904 512 byte sectors: 255H 63S/T 477C)
Oct 27 16:17:55 pc1 kernel: da0: quirks=0x2<NO_6_BYTE>

Oct 27 16:17:55 pc1 kernel: da1 at umass-sim0 bus 0 scbus2 target 0 lun 1
Oct 27 16:17:55 pc1 kernel: da1: <Intenso VideoShooter 0100> Removable Direct Access SCSI-0 device 
Oct 27 16:17:55 pc1 kernel: da1: Serial Number K
Oct 27 16:17:55 pc1 kernel: da1: 40.000MB/s transfers
Oct 27 16:17:55 pc1 kernel: da1: 30335MB (62126080 512 byte sectors: 255H 63S/T 3867C)
Oct 27 16:17:55 pc1 kernel: da1: quirks=0x2<NO_6_BYTE>

Oct 27 16:17:55 pc1 kernel: da1 at umass-sim0 bus 0 scbus2 target 0 lun 1
Oct 27 16:17:55 pc1 kernel: da1: <Intenso VideoShooter 0100> s/n K detached
Oct 27 16:17:55 pc1 kernel: (da1:umass-sim0:0:0:1): Periph destroyed

WHEN POWERING OFF THE DEVICE

Oct 27 16:21:46 pc1 kernel: ugen3.2: <Actions> at usbus3 (disconnected)
Oct 27 16:21:46 pc1 kernel: umass0: at uhub3, port 3, addr 2 (disconnected)
Oct 27 16:21:46 pc1 kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
Oct 27 16:21:46 pc1 kernel: da0: <Intenso VideoShooter 0100> s/n K detached
Oct 27 16:21:46 pc1 kernel: (da0:umass-sim0:0:0:0): Periph destroyed


ON 9.1
======

Oct 27 16:30:48 pc1 kernel: ugen3.2: <Actions> at usbus3
Oct 27 16:30:48 pc1 kernel: umass0: <Mass Storage> on usbus3
Oct 27 16:30:48 pc1 kernel: umass0:  8070i (ATAPI) over Bulk-Only; quirks = 0x0000
Oct 27 16:30:48 pc1 kernel: umass0:2:0:-1: Attached to scbus2

Oct 27 16:30:48 pc1 kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
Oct 27 16:30:48 pc1 kernel: da0: <Intenso VideoShooter 0100> Removable Direct Access SCSI-0 device 
Oct 27 16:30:48 pc1 kernel: da0: 40.000MB/s transfers
Oct 27 16:30:48 pc1 kernel: da0: 3748MB (7675904 512 byte sectors: 255H 63S/T 477C)

Oct 27 16:30:48 pc1 kernel: da1 at umass-sim0 bus 0 scbus2 target 0 lun 1
Oct 27 16:30:48 pc1 kernel: da1: <Intenso VideoShooter 0100> Removable Direct Access SCSI-0 device 
Oct 27 16:30:48 pc1 kernel: da1: 40.000MB/s transfers
Oct 27 16:30:48 pc1 kernel: da1: 30335MB (62126080 512 byte sectors: 255H 63S/T 3867C)

WHEN POWERING OFF THE DEVICE

Oct 27 16:32:18 pc1 kernel: ugen3.2: <Actions> at usbus3 (disconnected)
Oct 27 16:32:18 pc1 kernel: umass0: at uhub3, port 3, addr 2 (disconnected)
Oct 27 16:32:18 pc1 kernel: (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 1 refs
Oct 27 16:32:18 pc1 kernel: (da1:umass-sim0:0:0:1): lost device - 0 outstanding, 1 refs
Oct 27 16:32:18 pc1 kernel: (pass2:umass-sim0:0:0:0): passdevgonecb: devfs entry is gone
Oct 27 16:32:18 pc1 kernel: (pass3:umass-sim0:0:0:1): passdevgonecb: devfs entry is gone
Oct 27 16:32:18 pc1 kernel: (da1:umass-sim0:0:0:1): removing device entry
Oct 27 16:32:18 pc1 kernel: (da0:umass-sim0:0:0:0): removing device entry

Comment 1 Hans Petter Selasky freebsd_committer

2014-10-28 06:39:55 UTC

Hi,

There are no big changes in the USB UMASS area. Possibly SCSI/CAM related.

--HPS

Comment 2 rff1917 2014-10-28 17:41:32 UTC

Do you have any suggestion what I could try? This is pretty much the only regression I can see in 10.1 so far. And this device is the only USB device that doesn't work properly.

Comment 3 Hans Petter Selasky freebsd_committer

2014-10-28 20:29:01 UTC

Hi,

There are some options and commands that will give you more debugging output from the CAM/SCSI layer. mav @ knows more about this.

--HPS

Comment 4 Marcus von Appen freebsd_committer

2015-02-18 11:54:22 UTC

Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.

Comment 5 Gleb Popov freebsd_committer

2019-08-01 12:36:10 UTC

Should we close this due to feedback timeout?