From owner-freebsd-usb@freebsd.org Mon Feb 26 07:02:23 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48459F2FA59 for ; Mon, 26 Feb 2018 07:02:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7B2F8675E for ; Mon, 26 Feb 2018 07:02:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0AF1A289B0 for ; Mon, 26 Feb 2018 07:02:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1Q72L7o085345 for ; Mon, 26 Feb 2018 07:02:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1Q72LYc085344 for freebsd-usb@FreeBSD.org; Mon, 26 Feb 2018 07:02:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 225794] VM images for 12.0-CURRENT have problem with USB 3.0 ports Date: Mon, 26 Feb 2018 07:02:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2018 07:02:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225794 --- Comment #19 from Andriy Gapon --- (In reply to David.Boyd49 from comment #18) So, it seems that MODE SENSE (10) command completely wedges the device (or maybe the controller) and it stops accepting any subsequent commands. I wonder if it would work better with MODE SENSE (6) or if any form of MODE SENSE is broken. Are you set up for compiling and testing kernel code patches? Or would you prefer that I send you pre-built kernels? But before that, could you please obtain a log from a working Linux guest w= ith the problematic controller? I am not sure how to get the log that I want as I am not very experienced w= ith Linux, but it should look something like this: [ 3902.887849] usb 4-6: new SuperSpeed USB device number 6 using xhci_hcd [ 3902.904584] usb 4-6: New USB device found, idVendor=3D152d, idProduct=3D= 0567 [ 3902.904586] usb 4-6: New USB device strings: Mfr=3D1, Product=3D2, SerialNumber=3D3 [ 3902.904587] usb 4-6: Product: JMS567 [ 3902.904588] usb 4-6: Manufacturer: JMicron [ 3902.904588] usb 4-6: SerialNumber: DB123456789B1D [ 3902.906862] scsi host13: uas [ 3902.907595] scsi 13:0:0:0: Direct-Access Samsung SSD 850 PRO 256G 0= 117 PQ: 0 ANSI: 6 [ 3902.908426] sd 13:0:0:0: Attached scsi generic sg4 type 0 [ 3902.908574] sd 13:0:0:0: [sde] 500118192 512-byte logical blocks: (256 GB/238 GiB) [ 3902.908575] sd 13:0:0:0: [sde] 4096-byte physical blocks [ 3902.909089] sd 13:0:0:0: [sde] Write Protect is off [ 3902.909091] sd 13:0:0:0: [sde] Mode Sense: 53 00 10 08 [ 3902.909368] sd 13:0:0:0: [sde] Disabling FUA [ 3902.909370] sd 13:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3902.910769] sde: sde1 [ 3902.912446] sd 13:0:0:0: [sde] Attached SCSI disk I guess that this requires setting kernel log level to debug before attachi= ng the device and then extracting the logs from the appropriate place (dmesg?, systemd journal?). --=20 You are receiving this mail because: You are on the CC list for the bug.=