From owner-freebsd-current@freebsd.org Sun Jan 7 04:20:20 2018 Return-Path: Delivered-To: freebsd-current@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 D0D04E65B02 for ; Sun, 7 Jan 2018 04:20:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CE9E7484B for ; Sun, 7 Jan 2018 04:20:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id n14so9709384iob.4 for ; Sat, 06 Jan 2018 20:20:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=J2tsNpd5a/ldBKWge62j7cVN2UyVHTZIK/3L/ksTO9Q=; b=VIArw18DFU+EQnEIMmiU1R5v4jxPp+pj7mHWz36okOJ0QHHqP5cLn14/pb0Of0QXRx eIO3g8H16jVCHV8LnG0vwQd7mrftzGdza8CcxcXsAAa1Kf8th3pBPHWr4RighvMrXRaH WoO/uYj+o/qPAiKIMHUyWGsvcXfjLbNBOyeYHhDHhaV69Y+3woh7r/92W4sgWM1CD2mB vwwQH6vQeO/VcsOWdaT4xV+2dA3MUKttc4xcWB22spaLe/SD0hfW36O6b6+s04m8NPoR 6LdXaKwFjqPP7StXDKvcrUb4N3GTG8MmCTcOedcv83MU+joYlhP2THAe2Zk3B4YuIAzs frAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=J2tsNpd5a/ldBKWge62j7cVN2UyVHTZIK/3L/ksTO9Q=; b=G21o8WKyzWJgvaL86B8ml9xzMCzga4MWzrritTggnfaTBVtvaoP1Q8gsyKyHFeQlCe UYPMXSrNMpmhtKL8lr/QRKoSSXq3hJ11iOkiItUSLMC9MqFGOWFkA66FJZeoQn95/HDJ RL9B2OBTF0Ey33tZ4Aeud6NIBFCbEOopPKoaPlqCF4qXO+SEag9llHaoM5vXhKwi679D 8GKInj4o10lFQj1hfzOVFtpfRcXLhj+Yxgzy7Np11Qf50DOkGYT21/ffsg1Qg1LabMvO DX9N5XCA0BVjq8pMqEMIwbM+SBS02bBiyimwoK+W0CnRlz6XWVvVskOApYN3XepugKlM mJNA== X-Gm-Message-State: AKwxytf4UTun/H+Q7u6+0ulzxzSNK0J1QdU72HqUJfWPPpQHVKnPmNch pj/8RNf0wfB0tu6MbvXL5TvpeIs3nWX1jXOmtarV/A== X-Google-Smtp-Source: ACJfBosinBsNzTSuuXQvM738+3EvchJaSsx/RU1NqgpA6f2d1hw2L/q5l8jgBldECdwYg990V0VbooLgzAB5xDY4ZDo= X-Received: by 10.107.78.12 with SMTP id c12mr7320995iob.63.1515298819920; Sat, 06 Jan 2018 20:20:19 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.160.217 with HTTP; Sat, 6 Jan 2018 20:20:19 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: References: <1FD1FE97-D25C-4BAC-A3E0-F22509FB0C2B@dons.net.au> <6A4FF1B9-D98B-4E73-9E3E-E951749E0C21@dons.net.au> <20180104092349.2821f9f9@ernst.home> <18F01F2F-8907-4CF8-A80A-B6B5C16593B7@dons.net.au> From: Warner Losh Date: Sat, 6 Jan 2018 21:20:19 -0700 X-Google-Sender-Auth: U4J7CwAxB44lSP2iNoELs9KECxs Message-ID: Subject: Re: USB stack To: blubee blubeeme Cc: "O'Connor, Daniel" , gljennjohn@gmail.com, FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 04:20:20 -0000 On Sat, Jan 6, 2018 at 9:18 PM, blubee blubeeme wrote: > > > On Sun, Jan 7, 2018 at 12:11 PM, Warner Losh wrote: > >> >> >> On Sat, Jan 6, 2018 at 8:56 PM, blubee blubeeme >> wrote: >> >>> I ask does FreeBSD usb stack actually implements USB spec 2.0 or greater >>> and the topic gets derailed...? >>> >> >> Yes, it does. >> >> >>> Are you guys saying that 7-8MB/s is USB speeds? >>> >> >> I've gotten up to 24MB/s for maybe a decade. That's not possible with USB >> 1.x. More recently, I've maxed out the writes on a USB stick at about >> 75MB/s (the fastest it will do), which isn't possible with USB 2.0... I've >> not tried USB3 with an SSD that can do more.... >> >> Warner >> >> >>> On Thu, Jan 4, 2018 at 6:44 PM, O'Connor, Daniel >>> wrote: >>> >>> > >>> > >>> > > On 4 Jan 2018, at 09:23, Gary Jennejohn >>> wrote: >>> > >> What is an "LG v30"? >>> > >> >>> > > It's a smartphone from LG and only supports USB2 speed. The reported >>> > > transfer rate is no big surprise. >>> > >>> > OK thanks. >>> > >>> > -- >>> > Daniel O'Connor >>> > "The nice thing about standards is that there >>> > are so many of them to choose from." >>> > -- Andrew Tanenbaum >>> > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >>> > >>> > >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >> >> I just connected a Transcend StorageJet 1TB hdd not a mobile phone > ------------------------------------------------------------------- > Jan 7 11:56:56 blubee kernel: umass0 on uhub0 > Jan 7 11:56:56 blubee kernel: umass0: Transcend, class 0/0, rev 3.00/80.00, addr 4> on usbus0 > Jan 7 11:56:56 blubee kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0100 > Jan 7 11:56:56 blubee kernel: umass0:3:0: Attached to scbus3 > Jan 7 11:56:56 blubee kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun > 0 > Jan 7 11:56:56 blubee kernel: da0: Fixed Direct > Access SPC-4 SCSI device > Jan 7 11:56:56 blubee kernel: da0: Serial Number W9328YZN > Jan 7 11:56:56 blubee kernel: da0: 400.000MB/s transfers > Jan 7 11:56:56 blubee kernel: da0: 953869MB (1953525168 512 byte sectors) > Jan 7 11:56:56 blubee kernel: da0: quirks=0x2 > Jan 7 12:06:08 blubee kernel: lock order reversal: > Jan 7 12:06:08 blubee kernel: 1st 0xfffffe07c26336c0 bufwait (bufwait) @ > /usr/src/sys/vm/vm_pager.c:374 > Jan 7 12:06:08 blubee kernel: 2nd 0xfffff80148c425f0 zfs (zfs) @ > /usr/src/sys/dev/md/md.c:952 > Jan 7 12:06:08 blubee kernel: stack backtrace: > Jan 7 12:06:08 blubee kernel: #0 0xffffffff80acfa03 at > witness_debugger+0x73 > Jan 7 12:06:08 blubee kernel: #1 0xffffffff80acf882 at > witness_checkorder+0xe02 > Jan 7 12:06:08 blubee kernel: #2 0xffffffff80a41b8e at > lockmgr_lock_fast_path+0x1ae > Jan 7 12:06:08 blubee kernel: #3 0xffffffff81094309 at VOP_LOCK1_APV+0xd9 > Jan 7 12:06:08 blubee kernel: #4 0xffffffff80b4ac36 at _vn_lock+0x66 > Jan 7 12:06:08 blubee kernel: #5 0xffffffff80611d32 at mdstart_vnode+0x442 > Jan 7 12:06:08 blubee kernel: #6 0xffffffff806102ce at md_kthread+0x1fe > Jan 7 12:06:08 blubee kernel: #7 0xffffffff80a2d654 at fork_exit+0x84 > Jan 7 12:06:08 blubee kernel: #8 0xffffffff80ef5e0e at fork_trampoline+0xe > Jan 7 12:06:15 blubee kernel: lock order reversal: > Jan 7 12:06:15 blubee kernel: 1st 0xfffffe07c41d5dc0 bufwait (bufwait) @ > /usr/src/sys/kern/vfs_bio.c:3562 > Jan 7 12:06:15 blubee kernel: 2nd 0xfffff8002bb31a00 dirhash (dirhash) @ > /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 > Jan 7 12:06:15 blubee kernel: stack backtrace: > Jan 7 12:06:15 blubee kernel: #0 0xffffffff80acfa03 at > witness_debugger+0x73 > Jan 7 12:06:15 blubee kernel: #1 0xffffffff80acf882 at > witness_checkorder+0xe02 > Jan 7 12:06:15 blubee kernel: #2 0xffffffff80a748a8 at _sx_xlock+0x68 > Jan 7 12:06:15 blubee kernel: #3 0xffffffff80d6a28d at ufsdirhash_add+0x3d > Jan 7 12:06:15 blubee kernel: #4 0xffffffff80d6d119 at ufs_direnter+0x459 > Jan 7 12:06:15 blubee kernel: #5 0xffffffff80d76313 at ufs_makeinode+0x613 > Jan 7 12:06:15 blubee kernel: #6 0xffffffff80d71ff4 at ufs_create+0x34 > Jan 7 12:06:15 blubee kernel: #7 0xffffffff810919e3 at VOP_CREATE_APV+0xd3 > Jan 7 12:06:15 blubee kernel: #8 0xffffffff80b4a53d at vn_open_cred+0x2ad > Jan 7 12:06:15 blubee kernel: #9 0xffffffff80b42e92 at kern_openat+0x212 > Jan 7 12:06:15 blubee kernel: #10 0xffffffff80f16d2b at > amd64_syscall+0x79b > Jan 7 12:06:15 blubee kernel: #11 0xffffffff80ef5b7b at Xfast_syscall+0xfb > > > Is the slow transfers user error? > It's likely due to the slow UFS issue... Warner