From owner-freebsd-amd64@freebsd.org Sun Apr 10 12:00:35 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F87CB0154A for ; Sun, 10 Apr 2016 12:00:35 +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 mx1.freebsd.org (Postfix) with ESMTPS id 644DB1EC6 for ; Sun, 10 Apr 2016 12:00:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3AC0ZMv088964 for ; Sun, 10 Apr 2016 12:00:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 208668] 11.0-CURRENT since around December 2015 can be remarkably troublesome with USB (for PersonaCrypt) Date: Sun, 10 Apr 2016 12:00:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: grahamperrin@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc attachments.created Message-ID: 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-Mailman-Approved-At: Sun, 10 Apr 2016 12:05:28 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2016 12:00:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208668 Bug ID: 208668 Summary: 11.0-CURRENT since around December 2015 can be remarkably troublesome with USB (for PersonaCrypt) Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: grahamperrin@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 169141 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D169141&action= =3Dedit A diagnostic file, produced by 'PC-BSD bug report tool'; includes dmesg and other information USB 3.1 Gen 1 (USB 3.0) Kingston DataTraveler G4=20 http://web.archive.org/web/20151107114009/http://www.kingston.com/en/usb/pe= rsonal_business#DTIG4=20 32GB USB flash drive for PersonaCrypt in PC-BSD 11.0-CURRENT.=20 If required: https://www.ixsystems.com/blog/pc-bsd-version-1012-now-available-for-the-se= curity-conscious-desktop-user/ includes an outline of PersonaCrypt.=20 With PC-BSD 11.0-CURRENTNOV2015 and less, the Kingston device is *entirely reliable* for PersonaCrypt with a circa 2007 Ergo Vista 621 notebook, with = 4 GB memory, where the interface is probably limited to USB=C2=A02.0.=20 With the following distributions, the same combination of hardware *ceases = to work very quickly* (typically within ten minutes of GELI attachment):=20 * PC-BSD 11.0-CURRENTDEC2015 * PC-BSD 11.0-CURRENTJAN2016 * PC-BSD 11.0-CURRENTFEB2016 * PC-BSD 11.0-CURRENTMAR2016 For a few weeks the Kingston device was good for PersonaCrypt with PC-BSD 11.0-CURRENTMAR2016 on a more modern notebook -- an early 2011 Apple MacBookPro8,2 with 4 GB memory, https://support.apple.com/kb/SP620 =E2=80= =93 again, USB 2.0.=20 Today with PC-BSD 11.0-CURRENTAPRIL2016 before attempting to use the Kingst= on device, I gave that Mac notebook an unusually 'hard push' (overnight, with synth at ttyv1) =E2=80=93 hard enough to use around 2=C2=A0GB of 4=C2=A0GB = available swap. Then, as I attempted to log in with PersonaCrypt, the problem recurred.=20 An extract:=20 ---- usb_pc_common_mem_cb: Page offset was not preserved (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 a8 00 00 80 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command usb_pc_common_mem_cb: Page offset was not preserved (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 a8 00 00 80 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command usb_pc_common_mem_cb: Page offset was not preserved (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 a8 00 00 80 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command usb_pc_common_mem_cb: Page offset was not preserved (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 a8 00 00 80 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command usb_pc_common_mem_cb: Page offset was not preserved (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 a8 00 00 80 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Error 5, Retries exhausted ---- I have photographs of today's incident, but I can not attach them at this t= ime.=20 I understand that users of USB devices may be cautioned against using USB= =C2=A02.0 for ZFS, but the difference between NOV2015 and DEC2015 was so extreme that= a bug report seems appropriate.=20 ---- Historically (2010) ------------------- https://wiki.freebsd.org/USB noted: Q: I see the following error and USB stops working=20 "Page offset was not preserved!" A: Update your sources, this issue is fixed. Recently (2015-11-24) --------------------- svn commit: r291251 - stable/9/sys/dev/usb https://lists.freebsd.org/pipermail/svn-src-stable-9/2015-November/008097.h= tml > MFC r290326: > Relax the BUS_DMA_KEEP_PG_OFFSET requirement to=20 > allow optimising allocation of DMA bounce buffers. Modified: stable/9/sys/dev/usb/usb_busdma.c A wild guess: I wonder whether the problem(s) affecting my use of a USB dev= ice are an unintended consequence of that allowance for optimisation. --=20 You are receiving this mail because: You are on the CC list for the bug.=