[Bug 250638] insyde BMC virtual CDROM unresponsive to FreeBSD

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Oct 26 17:29:47 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250638

            Bug ID: 250638
           Summary: insyde BMC virtual CDROM unresponsive to FreeBSD
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs at FreeBSD.org
          Reporter: emaste at freebsd.org

Discovered while attempting to install FreeBSD from a virtual CDROM ISO image,
where the installer stops trying to mount the root fs, but reproduced after
installing FreeBSD by dd'ing an image to the disk from Ubuntu. Hardware is an
experimental platform but with (I believe) a standard BMC; will try to
reproduce on off-the-shelf hardware.

Upon attaching the virtual CDROM console emits:

ugen0.6: <Linux 4.9.135 with astvhub Virtual Media Gadget 0> at usbus0
umass1 numa-domain 0 on uhub3
umass1: <Linux 4.9.135 with astvhub Virtual Media Gadget 0, class 0/0, rev
2.00/4.09, addr 5> on usbus0
umass1:  SCSI over Bulk-Only; quirks = 0x0100
umass1:2:1: Attached to scbus2
uhub_explore: illegal enable change, port 1
(probe0:umass-sim1:1:0:0): Down reving Protocol Version from 2 to 0?
GEOM: new disk cd0
pass2 at umass-sim1 bus 1 scbus2 target 0 lun 0
pass2: <GENERIC Virtual CDROM YS0J> Removable CD-ROM SCSI device
pass2: 40.000MB/s transfers
cd0 at umass-sim1 bus 1 scbus2 target 0 lun 0
cd0: <GENERIC Virtual CDROM YS0J> Removable CD-ROM SCSI device
cd0: 40.000MB/s transfers
cd0: 337MB (172775 2048 byte sectors)
cd0: quirks=0x10<10_BYTE_ONLY>

but no /dev/cd0 is created

"camcontrol devlist" reports:

<SAMSUNG MZ7LH240HAHQ-00005 HXT7404Q>  at scbus0 target 0 lun 0 (ada0,pass0)
<SanDisk Cruzer Blade 1.26>        at scbus1 target 0 lun 0 (da0,pass1)
<GENERIC Virtual CDROM YS0J>       at scbus2 target 0 lun 0 (pass2,cd0)

running "gpart show" produces on the console:

(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e6 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 3 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e6 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 2 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e6 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 1 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e6 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 0 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e6 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Error 5, Retries exhausted
(cd0:umass-sim1:1:0:0): cddone: got error 0x5 back
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e5 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 3 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e5 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 2 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e5 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 1 more tries remain
(cd0:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 02 a2 e5 00 00 01 00 
(cd0:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(cd0:umass-sim1:1:0:0): Retrying command, 0 more tries remain

^T shows:
load: 0.00  cmd: gpart 2516 [g_waitfor_event] 44.52r 0.00u 0.00s 0% 2540k
mi_switch+0x155 sleepq_switch+0x109 sleepq_timedwait+0x4b _sleep+0x29b
g_waitfor_event+0xf0 sysctl_kern_geom_confany+0xc1
sysctl_root_handler_locked+0x9c sysctl_root+0x20a userland_sysctl+0x17d
sys___sysctl+0x5f amd64_syscall+0x135 fast_syscall_common+0xf8 

BMC details:
Host Power Status :     Host is currently ON
BMC Uptime :    3 Day(s) 21 Hour(s) 29 Min(s) 9 Second(s)
BMC Firmware Build Time :       Fri May 15 21:19:31 2020
BMC FW Rev :    03.51.05.2020
Backup BMC FW Rev :     03.51.05.2020
Build ID :      05.202000

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list