From owner-freebsd-arm@freebsd.org Sun Mar 4 01:08:07 2018 Return-Path: Delivered-To: freebsd-arm@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 51A13F2795E; Sun, 4 Mar 2018 01:08:07 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 EE6BA8049F; Sun, 4 Mar 2018 01:08:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 468FF209B0; Sat, 3 Mar 2018 20:08:00 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 03 Mar 2018 20:08:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=1q3o1jKFvIWWrCAW4eOjnQQ4Ukxbjj6RXDeEbUf/R50=; b=j6mYEnP7 QVDEMEvI98VeFRxZK/9GDwKWjXx4WKcwgIEe5E+9k1Dy6HIqJGgUo+zaWsrI1Jzo yWPsR3aCc/zvv+Lc2wBWH2eI8YIlzTz+qQ4ffcSAxl5YEGGdT6TxV1mDa+g7n6c9 EYIDsGeoCrpdmY5jh+5lFLrN66tVJfJZrnKpUK/gzeW1d9jsI9rfSu+rUnNfmg53 3flUxruFZqovOfYPsbvR45xRlS2SlHATZKQ5s74EfUIm8gKaJLdy6khUH5kprE6Y cIg9RcZVKrkSoEQnvuUlrkGx+Xf+Z7L5pywFLzBJe7C0GgwwnwCoTf7rE7mfG4KS zWZor09oUsxYMA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=1q3o1jKFvIWWrCAW4eOjnQQ4Ukxbj j6RXDeEbUf/R50=; b=KXWjZh54eZ/WIxOYRjvp5+ApgcbR8iQOAKz54gWTQVbtR EE3R1EGtqbmqrqB/kdxFroxjJd6/rP4CBRhiqZj334a4Bw0Cl7gZl2Z3LRjOvSs/ p+vGiLHBCn9MqHBe1McMi3woVN/CkR9EphCLSF0CWWIDUbBUx8CyRO6e07S2o9l6 mHhvCTMFK7Y7TY5jk5ibvf+Hchag4NNPw0HS+/iiYCleShm2FkMpbhI73Bz6+QLI OodeCstcYNUirFHYjTpYiMUNxe3tmwqUgZLCmnt7+OiWhyc4JrwwgYmTH7FVPzks m+CTKO3SfKjnV7+C3pXoFgXeuEjv3cpmMTXnglc+w== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id BE4EB7E140; Sat, 3 Mar 2018 20:07:59 -0500 (EST) To: freebsd-ports@freebsd.org From: tech-lists Subject: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github Cc: freebsd-arm@freebsd.org Message-ID: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> Date: Sun, 4 Mar 2018 01:07:58 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 01:08:07 -0000 Hello ports@ I don't know whether this is a freebsd/crochet (https://github.com/freebsd/crochet) problem or a /usr/ports/sysutils/u-boot-rpi2 problem. When I use crochet to build for rpi2 it never completes writing the image because it looks for things in /usr/local/share/u-boot/u-boot-rpi2 and doesn't find for example LICENCE.broadcom. There's just two files there: root@desktop:/usr/local/share/u-boot/u-boot-rpi2 # ls -lah total 295 drwxr-xr-x 2 root wheel 4B Mar 3 20:26 . drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. -rw-r--r-- 1 root wheel 765B Mar 3 20:23 README -rw-r--r-- 1 root wheel 371K Mar 3 20:23 u-boot.bin The build fails with the following: [...] Creating a 50m FAT partition at Sun Mar 4 00:56:08 UTC 2018 with start block 63 and label BOOT active set on md0s1 Creating an auto-sized UFS partition at Sun Mar 4 00:56:08 UTC 2018 md0s2 created /dev/md0s2a: 3668.5MB (7513088 sectors) block size 32768, fragment size 4096 using 6 cylinder groups of 626.09MB, 20035 blks, 80256 inodes. super-block backups (for fsck_ffs -b #) at: 192, 1282432, 2564672, 3846912, 5129152, 6411392 tunefs: soft updates set Using inode 4 in cg 0 for 4194304 byte journal tunefs: soft updates journaling set tunefs: NFSv4 ACLs set Mounting all file systems: Mounting FAT partition 1 at /root/crochet/work/_.mount.boot Mounting UFS partition 1 at /root/crochet/work/_.mount.freebsd cp: /usr/local/share/u-boot/u-boot-rpi2/LICENCE.broadcom: No such file or directory In contrast, /usr/ports/sysutils/u-boot-rpi3 installs the following into /usr/local/share/u-boot/u-boot-rpi3: root@desktop:/usr/local/share/u-boot/u-boot-rpi3 # ls -lah total 9078 drwxr-xr-x 2 root wheel 16B Mar 4 00:58 . drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. -rw-r--r-- 1 root wheel 1.5K Mar 4 00:58 LICENCE.broadcom -rw-r--r-- 1 root wheel 123B Mar 4 00:58 README -rw-r--r-- 1 root wheel 6.0K Mar 4 00:58 armstub8.bin -rw-r--r-- 1 root wheel 18K Mar 4 00:58 bootcode.bin -rw-r--r-- 1 root wheel 136B Mar 4 00:58 config.txt -rw-r--r-- 1 root wheel 6.3K Mar 4 00:58 fixup.dat -rw-r--r-- 1 root wheel 2.4K Mar 4 00:58 fixup_cd.dat -rw-r--r-- 1 root wheel 9.5K Mar 4 00:58 fixup_db.dat -rw-r--r-- 1 root wheel 9.5K Mar 4 00:58 fixup_x.dat -rw-r--r-- 1 root wheel 2.6M Mar 4 00:58 start.elf -rw-r--r-- 1 root wheel 604K Mar 4 00:58 start_cd.elf -rw-r--r-- 1 root wheel 4.7M Mar 4 00:58 start_db.elf -rw-r--r-- 1 root wheel 3.7M Mar 4 00:58 start_x.elf -rw-r--r-- 1 root wheel 361K Mar 4 00:58 u-boot.bin and it builds fine, which leads me to think the problem isn't with crochet. Both u-boot-rpi2 and u-boot-rpi3 build and install cleanly from ports. -- J. From owner-freebsd-arm@freebsd.org Sun Mar 4 01:20:49 2018 Return-Path: Delivered-To: freebsd-arm@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 75F94F28BCA for ; Sun, 4 Mar 2018 01:20:49 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 2168280E83 for ; Sun, 4 Mar 2018 01:20:49 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 581C120D3B; Sat, 3 Mar 2018 20:20:48 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 03 Mar 2018 20:20:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=vZEif3AEwTe3I0SB794wZKYa1pkg4 mXDX1WVh6B8uM4=; b=B5XnKTCZU5IistyxxnoqNKFxcOJAseN16YZEp0BmdecHv eUTc1x/lsRe4jBJmjkWevH0hFutoazHkfMkIs2j2XT3lURT4bJ0TuwRHwwclNEY4 eNkSLxOT1nQHczUtQ2E3o2L+nBNasLaTtGV9mdn99dvSNwjbDzuvKU7HxY71HqRJ PLB1/NTS1jjSfKcWq58suV7t7PKTmH452W/sP/sT2u29GFBONKlWJULwUZyIm/QZ E+MQHomK0bXbgJ7dmYIKpA++IW2eEFcdRyie/knZKNvpqkHElFRaaq8MuSq/6vcm jrwTa3jD52yegVbhoJ1g8x0wAcmsSaCF9s9y4mOJQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=vZEif3 AEwTe3I0SB794wZKYa1pkg4mXDX1WVh6B8uM4=; b=P2JlmJpeTIiNRkVoxK/lmm EeeLg4sBCyYJEPAskRNkXBK3ZvbU9WdFweMQjAR8uOZ+Fdgvdrd9/+MHpfkdOXmu adVAYib+MFl5XGkOLb7qgMTIdAtvmrl2zam6uUme0xeHjL6YIFAqRmI3S//Dh++x MN14YVGIAkzySpuFaX8ogEr+Mvq2sv7IdWqstpBTFAO497aAD1hbW6eKOw6slte2 KEXshLVrLH4Z2PQ3PTtou48rggvUmRGadsPBKVt0hq+aS0wOX7C9q3ah2z1dkWFp 6j5lD0DCXQU6CzGWkmi6DnD3QAi55At1cduksESYaQ+mL/oi/PO5A6PBtlAxxZcw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id C94E37E0DF; Sat, 3 Mar 2018 20:20:47 -0500 (EST) Subject: Re: Can two USB flash drives conflict with each other? To: "Rodney W. Grimes" , bob prohaska Cc: freebsd-arm@freebsd.org References: <201803030105.w2315sH7032500@pdx.rh.CN85.dnsmgr.net> From: tech-lists Message-ID: <4420a9b9-e627-3cbc-e47a-d99cbedbfad3@zyxst.net> Date: Sun, 4 Mar 2018 01:20:47 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803030105.w2315sH7032500@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 01:20:49 -0000 On 03/03/2018 01:05, Rodney W. Grimes wrote: > unless somehow in the physical act of plugging it in the other > one became disconnected and a bus probe happened. Yeah, I've seen that happen. -- J. From owner-freebsd-arm@freebsd.org Sun Mar 4 02:15:45 2018 Return-Path: Delivered-To: freebsd-arm@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 833A4F2BAB5 for ; Sun, 4 Mar 2018 02:15:45 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D427A82DB1 for ; Sun, 4 Mar 2018 02:15:44 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w242FbEB043348 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 3 Mar 2018 18:15:38 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w242Fbal043347; Sat, 3 Mar 2018 18:15:37 -0800 (PST) (envelope-from fbsd) Date: Sat, 3 Mar 2018 18:15:37 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Kernel build problems on Pi3 Message-ID: <20180304021537.GA43316@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 02:15:45 -0000 In trying to make a kernel on a Pi3 at r329893 a buildkernel after kernel-toolchain stops with: In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:228:25: error: typedef redefinition with different types ('int16_t' (aka 'short') vs '__int_fast16_t' (aka 'int')) typedef __int_least16_t int_fast16_t; ^ /usr/src/sys/sys/stdint.h:51:25: note: previous definition is here typedef __int_fast16_t int_fast16_t; ^ In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:229:26: error: typedef redefinition with different types ('uint16_t' (aka 'unsigned short') vs '__uint_fast16_t' (aka 'unsigned int')) typedef __uint_least16_t uint_fast16_t; ^ /usr/src/sys/sys/stdint.h:56:26: note: previous definition is here typedef __uint_fast16_t uint_fast16_t; ^ In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:245:24: error: typedef redefinition with different types ('int8_t' (aka 'signed char') vs '__int_fast8_t' (aka 'int')) typedef __int_least8_t int_fast8_t; ^ /usr/src/sys/sys/stdint.h:50:24: note: previous definition is here typedef __int_fast8_t int_fast8_t; ^ In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:246:25: error: typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs '__uint_fast8_t' (aka 'unsigned int')) typedef __uint_least8_t uint_fast8_t; ^ /usr/src/sys/sys/stdint.h:55:25: note: previous definition is here typedef __uint_fast8_t uint_fast8_t; ^ 4 errors generated. *** [armv8_crypto_wrap.o] Error code 1 Updating sources to 330366 didn't help, svnlite status finds nothing unexpected in /usr/src/. The kernel config can be seen at http://www.zefox.net/~fbsd/rpi3/kernel_config/ZEFOX It worked for the kernel running now, so I don't _think_ that's the problem. Thanks for reading, and any guidance! bob prohaska From owner-freebsd-arm@freebsd.org Sun Mar 4 03:39:00 2018 Return-Path: Delivered-To: freebsd-arm@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 72D3CF2FBA0; Sun, 4 Mar 2018 03:39:00 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 D222E86487; Sun, 4 Mar 2018 03:38:59 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5A7DB20C76; Sat, 3 Mar 2018 22:38:59 -0500 (EST) Received: from web1 ([10.202.2.211]) by compute7.internal (MEProxy); Sat, 03 Mar 2018 22:38:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= caffeinated.codes; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=QQLs7R 9ZFAV5yvOLVDvBZJSC2YaXUz1LCBsL4cjBu+M=; b=Ph2T1zL+9t4tC+lSb07DKe 3+8/Gn3D9bv8C8OauRQF74RyRUfOQHvJuY8WIcIV7oJlRFyvuOoz6D5O/BFXMSdz zEFIdksj1l/LNoCx3N9zM/UrGvXuXPaxw1pOQWl3fT3vfZlbLsAGToaZTZ6BW0Nc Zy8TNA5hfUN+T4ynOWlZ9p0gK10QaRnTtsR6o10fohVf2iDsXS32QAiJJ4dZZTSB x10v5NbOAj+C6fUyCPt5JrRmb1fhtQqqWn5l6LWWmANgl0U5yX1/qy6VropwvuOM 3tLsZ9b4J5EFHaY/VksJbYunXaqXFF9IsXc8omzAECZG9R0MipHTsnZegvJn1tXQ == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QQLs7R 9ZFAV5yvOLVDvBZJSC2YaXUz1LCBsL4cjBu+M=; b=HMkkKuBBewzTnUrlaysN7k 4+o7AgjkorR50YiU3hJ4UH1tIVFq/WcSmwDdlAuFCwtqBPsFfpEU4KibJKZuX9Zp PKQe2DKQdgW/tqcf3LUW4Braqlk94Xr1mMpHF+sAn2ILxJzBtJXIKBDCDomJ3sn2 GXmx4LVO0I/cVAn/wG/pYqrJaokdDcJ6DVUKGaAlu+eM3qAHW5qgWxmcXwj2AiRx BdIlO6y365IpKMiujhp13p6IamjbFK65lFncHe7EPPWF9KiQJm8Nre1myKRBrlwr vmjfen1sYESmXuquJnChPobP4QNyflpCpGWWWcMoVF2ueFc4cVbEQthcR4HRM2nQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 06A8C940AA; Sat, 3 Mar 2018 22:38:59 -0500 (EST) Message-Id: <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> From: Hyun Hwang To: "tech-lists" Cc: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b08ff009 Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github Date: Sat, 03 Mar 2018 22:38:58 -0500 References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> In-Reply-To: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 03:39:00 -0000 On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > When I use crochet to build for rpi2 it never completes writing the > image because it looks for things in /usr/local/share/u-boot/u-boot-rpi2 > and doesn't find for example LICENCE.broadcom. There's just two files > there: > > root@desktop:/usr/local/share/u-boot/u-boot-rpi2 # ls -lah > total 295 > drwxr-xr-x 2 root wheel 4B Mar 3 20:26 . > drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. > -rw-r--r-- 1 root wheel 765B Mar 3 20:23 README > -rw-r--r-- 1 root wheel 371K Mar 3 20:23 u-boot.bin > (My email client messed up and sent the reply only to -arm; so I'm sending this message again to -ports as well. Sorry for duplicate post.) I see that firmware files are separated from `sysutils/u-boot-rpi2` port and are now located in `sysutils/rpi-firmware` port as of [ports r454265](https://svnweb.freebsd.org/ports?view=revision&revision=454265). Looks like Crochet requires some update. My wild guess is that RPi3 is yet to be separated because of gonzo's SMP binary (armstub8.bin)? -- Hyun Hwang From owner-freebsd-arm@freebsd.org Sun Mar 4 03:34:10 2018 Return-Path: Delivered-To: freebsd-arm@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 B215BF2F727 for ; Sun, 4 Mar 2018 03:34:10 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 4DCC8862DE for ; Sun, 4 Mar 2018 03:34:09 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0D44620B16 for ; Sat, 3 Mar 2018 22:34:09 -0500 (EST) Received: from web1 ([10.202.2.211]) by compute7.internal (MEProxy); Sat, 03 Mar 2018 22:34:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= caffeinated.codes; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=T6fW7KbVH6UdnahSU vRCHeeExDvL60wlz6qshPfXwho=; b=Q9Yd0d9um1Xl+UOb8unctu/pjZCrxHLNk 366I64xfkKoNHte81FE8rf4aswUDjyNVtDPYndjcamO9xNBwBa1eu43fPAMQp7tG yUb3DYlMgAMW/44Bp3Qz6VKDxYrtpMXAJwj366eQEo/V8OsAVZjPjl/xZ14fx0FJ shXmwosZW/WHXFJFj1zc7yCyw46d49Lzs+anjlRcov0Ov2ZcmcMzrDRvotKm/NYM PtdH2tKa0um1dDJizACYbURzMEjYWB2+/KfWagb09NoiA9BYv1nce37D768db/6F CaDcuNJHMe6rd/Dyp3fOwCTINDXvSf4gIA5hBl3PxXpV4GKsTaZlw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=T6fW7K bVH6UdnahSUvRCHeeExDvL60wlz6qshPfXwho=; b=EbcO4VqH0b80zw5+eI/s1x w+S/I1SWq7JimoKW+oXSYdr5FAiS2MxnFsPgsGK+0sFr4y0ZnTBv1LKYoNQxkXfY 4VbEKW42nxjXoZNFhQSG5RTVfpoBJjprpik0YOk7cy7RwSbvuRAnmyoV3OQcdSKG Yigsa17upQGz7C82ih1YpEtzsttuu6jildNr2iVro7h5zPcd6uelA5mEL0uopQcf qY2W9M5LgXrqcRy00thP3UyuhwTICDHEtGtmfPw1xiKb6TfbhZt9FM5bgy6lFisd 3Uo/lAQPg/s+912XavnGFOxncVZmOq0dcsbWEjFZS2myb083zrkUTxzHqblRx0MA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id CE0F7940AA; Sat, 3 Mar 2018 22:34:08 -0500 (EST) Message-Id: <1520134448.2036261.1290615272.657281E4@webmail.messagingengine.com> From: Hyun Hwang To: freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b08ff009 Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> Date: Sat, 03 Mar 2018 22:34:08 -0500 In-Reply-To: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 03:34:10 -0000 On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > When I use crochet to build for rpi2 it never completes writing the > image because it looks for things in /usr/local/share/u-boot/u-boot-rpi2 > and doesn't find for example LICENCE.broadcom. There's just two files > there: > > root@desktop:/usr/local/share/u-boot/u-boot-rpi2 # ls -lah > total 295 > drwxr-xr-x 2 root wheel 4B Mar 3 20:26 . > drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. > -rw-r--r-- 1 root wheel 765B Mar 3 20:23 README > -rw-r--r-- 1 root wheel 371K Mar 3 20:23 u-boot.bin I see that firmware files are separated from `sysutils/u-boot-rpi2` port and are now located in `sysutils/rpi-firmware` port as of [ports r454265](https://svnweb.freebsd.org/ports?view=revision&revision=454265). Looks like Crochet requires some update. My wild guess is that RPi3 is yet to be separated because of gonzo's SMP binary (armstub8.bin)? -- Hyun Hwang From owner-freebsd-arm@freebsd.org Sun Mar 4 06:33:34 2018 Return-Path: Delivered-To: freebsd-arm@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 B86F0F3996C for ; Sun, 4 Mar 2018 06:33:33 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic302-20.consmr.mail.gq1.yahoo.com (sonic302-20.consmr.mail.gq1.yahoo.com [98.137.68.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AB1C6CD50 for ; Sun, 4 Mar 2018 06:33:32 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: c9GBk7EVM1k5rPgRE1o1hEXG9mIs977gGe_bVjhPcv14Bt6Dlxg_opePQXnavLZ yBjnhKK2_Lo1gdj013y4ZN73S1FNVPLmfpc1fCJnRmGQ3xbWMS8WrYPyrq_nUNO1iV3NE0j.dia4 xC_UgW8BHVNR2cGBZVOeN54BlEWhcsPNZINH9b.TqO7rTf_iHOvSPm.kU1CLGj2.x55yLoYn5OHF OtLuDkgmsin7OSpHlp49j7Vr4j4U.7TKB..h_m0LbuaPQ4U4GCcgrz9ywoojqMQ5CRPuInIg7bSL BBeLNBb0lZDEyJ9UfFDTWPZSGaGcS0SFTLYSpbi6J4z48mDWcDy2AkTdltiSsm312wwkVQ2721DC civz51wAwfGAE.jaCdgY6.L5meVYQWnkDL2spP7v8OU9MTJQMZSSZhMPHXkvVI3qkt3aJfe4iAx. FoWGpN6SIIdIMci2kTmZCC4ke9100bvkbd8P1hWoLzLlRFgpdxkFWZtj2ophPazdu4t.e Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.gq1.yahoo.com with HTTP; Sun, 4 Mar 2018 06:33:26 +0000 Received: from smtp102.rhel.mail.gq1.yahoo.com (EHLO [192.168.1.25]) ([216.39.57.211]) by smtp409.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 23e4bfcce3e7d97568c905f784d3c7c3 for ; Sun, 04 Mar 2018 06:02:59 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Running FreeBSD-12.0-CURRENT-arm64-aarch64-20180226-r330034.vmdk with --enable-kvm under qemu-system-aarch64: how to enable networking? Message-Id: Date: Sat, 3 Mar 2018 22:02:58 -0800 To: Freebsd-arm X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 06:33:34 -0000 Based on https://wiki.freebsd.org/arm64/QEMU I've done my first experiments with running FreeBSD via the likes of: qemu-system-aarch64 -m 14336M -cpu host -smp 3 \ -M virt,gic-version=3D2 \ -bios QEMU_EFI.fd \ -serial telnet::4444,server -nographic \ -drive = if=3Dnone,file=3DFreeBSD-12.0-CURRENT-arm64-aarch64-20180226-r330034.vmdk,= id=3Dhd0 \ -device virtio-blk-device,drive=3Dhd0 \ --enable-kvm on a (Cortex-A72 based) MACCHIATOBin Double Shot (Rev 1.3) that I now have access to. The MACCHIATOBin is booted with: Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.52-armada-17.10.1-gc645ecc = aarch64) . . . # uname -ap Linux pod0 4.4.52-armada-17.10.1-gc645ecc #1 SMP PREEMPT Thu Jan 25 = 05:36:06 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux I've not figure out how to get networking to work inside FreeBSD. If I try also listing in the command above: -device virtio-net-device,netdev=3Dnet0 \ -netdev user,id=3Dnet0 \ it always hangs up after "Feeding entropy": load: 1.26 cmd: ifconfig 220 [running] 3.91r 0.00u 2.58s 40% 2572k load: 1.37 cmd: ifconfig 220 [running] 15.10r 0.00u 14.93s 93% 2572k load: 1.37 cmd: ifconfig 220 [running] 19.44r 0.00u 19.12s 100% 2572k load: 1.34 cmd: ifconfig 220 [running] 20.60r 0.00u 20.18s 93% 2572k load: 1.34 cmd: ifconfig 220 [running] 21.71r 0.00u 21.49s 95% 2572k load: 1.34 cmd: ifconfig 220 [running] 22.50r 0.00u 22.27s 100% 2572k . . . Apparently this is associated with the default: # more /etc/rc.conf hostname=3D"freebsd" ifconfig_DEFAULT=3D"DHCP inet6 accept_rtadv" (dhcp is what I hope to use.) On the Ubuntu side of things the network is configured via: # ls -ld /etc/network/interfaces.d/* -rw-r--r-- 1 root root 177 Mar 3 23:29 /etc/network/interfaces.d/eth2 # more /etc/network/interfaces.d/eth2 auto eth2 iface eth2 inet dhcp (eth2 is the 1 Gbit/sec Ethernet interface, no attempt at use of the other, faster ones. eth2 seems to work fine in Ubuntu. Ubuntu does not seem to be having problems of itself.) Other problems: # find / -name "*.core" -print /root/top.core /root/csh.core /sh.core FreeBSD randomly gets cores (but there is no gdb present to look at them with --and I do not have enough working to build gdb via ports). I've also had problems during "shutdown -p now" . . . Stopping devd. Waiting for PIDS: 203 load: 0.28 cmd: sh 720 [biowr] 15.13r 0.00u 0.28s 1% 4196k sleep: about 72 second(s) left out of the original 90 load: 0.21 cmd: sh 720 [biowr] 26.40r 0.00u 0.48s 1% 7516k sleep: about 61 second(s) left out of the original 90 Segmentation fault (core dumped) Writing entropy file:. Writing early boot entropy file:. . Mar 4 02:59:55 freebsd syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `bufdaemon' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop...=20 Another example . . . Terminated Mar 4 04:25:00 freebsd syslogd: exiting on signal 15 Mar 4 04:25:00 init: fatal signal: Segmentation fault init died (signal 0, exit 11) panic: Going nowhere without my init! cpuid =3D 0 time =3D 1520137530 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff000000632564 lr =3D 0xffff0000000bffc0 sp =3D 0xffff0000402395e0 fp =3D 0xffff0000402397f0 db_trace_self_wrapper() at vpanic+0x184 pc =3D 0xffff0000000bffc0 lr =3D 0xffff000000354af8 sp =3D 0xffff000040239800 fp =3D 0xffff000040239880 vpanic() at panic+0x44 pc =3D 0xffff000000354af8 lr =3D 0xffff000000354ba8 sp =3D 0xffff000040239890 fp =3D 0xffff000040239910 panic() at exit1+0xd14 pc =3D 0xffff000000354ba8 lr =3D 0xffff000000313b64 sp =3D 0xffff000040239920 fp =3D 0xffff000040239990 exit1() at sys_sys_exit+0x10 pc =3D 0xffff000000313b64 lr =3D 0xffff000000312e4c sp =3D 0xffff0000402399a0 fp =3D 0xffff0000402399a0 sys_sys_exit() at do_el0_sync+0x8bc pc =3D 0xffff000000312e4c lr =3D 0xffff00000064d59c sp =3D 0xffff0000402399b0 fp =3D 0xffff000040239a70 do_el0_sync() at handle_el0_sync+0x74 pc =3D 0xffff00000064d59c lr =3D 0xffff0000006349f4 sp =3D 0xffff000040239a80 fp =3D 0xffff000040239b90 handle_el0_sync() at 0x310a0 pc =3D 0xffff0000006349f4 lr =3D 0x00000000000310a0 sp =3D 0xffff000040239ba0 fp =3D 0x0000ffffffffe340 KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at 0x94e40: undefined 54000042 db>=20 For reference: U-Boot 2017.03-armada-17.10.1 (Oct 15 2017 - 14:03:12 +0300) Model: MACCHIATOBin-8040 Clock: CPU 2000 [MHz] DDR 1200 [MHz] FABRIC 1200 [MHz] MSS 200 [MHz] DRAM: 16 GiB # lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 2 CPU max MHz: 2000.0000 CPU min MHz: 100.0000 Hypervisor vendor: (null) Virtualization type: full =3D=3D=3D Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-arm@freebsd.org Sun Mar 4 07:37:38 2018 Return-Path: Delivered-To: freebsd-arm@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 D7F5AF3D2C2; Sun, 4 Mar 2018 07:37:38 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 68F546EE41; Sun, 4 Mar 2018 07:37:37 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1esOD3-0007jw-FL; Sat, 03 Mar 2018 23:37:30 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w247bSA3029755; Sat, 3 Mar 2018 23:37:28 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sat, 3 Mar 2018 23:37:27 -0800 From: Oleksandr Tymoshenko To: Hyun Hwang Cc: tech-lists , freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github Message-ID: <20180304073727.GA29648@bluezbox.com> References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hyun Hwang (hyun@caffeinated.codes) wrote: > On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > > When I use crochet to build for rpi2 it never completes writin [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 07:37:39 -0000 Hyun Hwang (hyun@caffeinated.codes) wrote: > On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > > When I use crochet to build for rpi2 it never completes writing the > > image because it looks for things in /usr/local/share/u-boot/u-boot-rpi2 > > and doesn't find for example LICENCE.broadcom. There's just two files > > there: > > > > root@desktop:/usr/local/share/u-boot/u-boot-rpi2 # ls -lah > > total 295 > > drwxr-xr-x 2 root wheel 4B Mar 3 20:26 . > > drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. > > -rw-r--r-- 1 root wheel 765B Mar 3 20:23 README > > -rw-r--r-- 1 root wheel 371K Mar 3 20:23 u-boot.bin > > > > (My email client messed up and sent the reply only to -arm; so I'm sending this message again to -ports as well. Sorry for duplicate post.) > > I see that firmware files are separated from `sysutils/u-boot-rpi2` port and are now located in `sysutils/rpi-firmware` port as of [ports r454265](https://svnweb.freebsd.org/ports?view=revision&revision=454265). Looks like Crochet requires some update. > > My wild guess is that RPi3 is yet to be separated because of gonzo's SMP binary (armstub8.bin)? There is ongoing work on using RPi firmware port for all RPi models and switching u-boot-rpi3 to the same framework as u-boot-rpi2 but it involves changes across multiple areas (drivers, ports, release scripts). Some of this stuff is already committed, some is in review, some is WIP. -- gonzo From owner-freebsd-arm@freebsd.org Sun Mar 4 13:15:01 2018 Return-Path: Delivered-To: freebsd-arm@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 13AAEF32079; Sun, 4 Mar 2018 13:15:01 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 B20017A631; Sun, 4 Mar 2018 13:15:00 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9C18E20A43; Sun, 4 Mar 2018 08:14:59 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 04 Mar 2018 08:14:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Cq0n8q9o9qEt7KB8ua4+ePQXQ77o9 GxX5/dysuNxEqo=; b=s7Jq2gc7rlQIzvFslN6GAnwWej02JsneZ0wBPEPFu1v7k KpHHWdgsKWw1YIPwI6cJ2c0oHG4wpHI58FNTciHA4GHRaa65zYf3n8MCYSy2KVsz sa253eAzzHRQdl13kJ7K3BAq2MM9vLAvw1tgt732GgWzrm76k/Qrf0NEYEN7lVia kSJa2dMyg0SkHIG0XcZBgq+NP1YbYE+URCiXYXiiU64K2kfnr0zTF30bBWVxgPtg Yr+aHm+0B569wnsvW+HS/bOYU6bUiLSViwlAGoBmXdZQE8rAm8XzlxzxjmP0LBSY AXZbqB2KrsqDIgSQ6THrlcT1BCn1TysYTmxXwzNNA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Cq0n8q 9o9qEt7KB8ua4+ePQXQ77o9GxX5/dysuNxEqo=; b=B0Ht3KRXkntsSxihyhw4jB 6uKyFQXb/Q8BExMs3ze5bjqTr3IC2KFKGJvWtYvdDqruX4Sg5ZPjspUELo4puYQ0 SVHZXRLaG6yxoIZ7ynCbQLHCaBPr7+tT1CD1EPG6/0wISmtg09yGjlUtSTRfvINK E20TnEq86aFU1YRjAgLAuatk4f8Ym8gY4qv7/jrPUV2wWxHxDkZy2HMrUPCcRYSy pqHmvfUubpJvzPBz37m5n/9m9WxzCgNBdK4RxCjHF5xO+eA+kO2wkg8lK6AQWJwx HVrU2ZOrkdU9cds+/uit89ip6k3TDP/BzIwbqoIzk10mM9o+pf2uEvzHXmrjS3hA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 734227E3C7; Sun, 4 Mar 2018 08:14:58 -0500 (EST) Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github To: Hyun Hwang Cc: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> From: tech-lists Message-ID: <0e13bcfe-54e4-ac26-acf6-64d233cd3070@zyxst.net> Date: Sun, 4 Mar 2018 13:14:57 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 13:15:01 -0000 On 04/03/2018 03:38, Hyun Hwang wrote: > Looks like Crochet requires some update. Hi, thanks for this. I've posted the issue to freebsd/crochet -- J. From owner-freebsd-arm@freebsd.org Sun Mar 4 18:28:35 2018 Return-Path: Delivered-To: freebsd-arm@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 C693EF2519F for ; Sun, 4 Mar 2018 18:28:35 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 194796855B for ; Sun, 4 Mar 2018 18:28:34 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w24ISWUi046357 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 4 Mar 2018 10:28:32 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w24ISVhV046356; Sun, 4 Mar 2018 10:28:31 -0800 (PST) (envelope-from fbsd) Date: Sun, 4 Mar 2018 10:28:31 -0800 From: bob prohaska To: Warner Losh Cc: Mike , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180304182831.GA44154@www.zefox.net> References: <20180228170311.GA26187@www.zefox.net> <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180303162605.GA41874@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 18:28:36 -0000 On Sat, Mar 03, 2018 at 08:26:05AM -0800, bob prohaska wrote: > > Is there some sort of experiment which can distinguish hardware delays > from software delays? For example, would logging gstat output shed any > light? > For lack of any better ideas, I tried running make -j2 -DNO_CLEAN buildworld > buildworld.log && make -j2 -DNO_CLEAN KERNCONF= ZEFOX buildkernel > buildkernel.log while also running gstat -a -B -I 10s > j2_gstat.log & in another ssh session In due course the console reported FreeBSD/arm64 (www.zefox.org) (ttyu0) login: Mar 4 09:28:30 www kernel: pid 9310 (c++), uid 0, was killed: out of swap space as expected. However, a grep of j2_gstat revealed a maximum write delay of 30ms/w for swap on microSD. Swap on USB flash is slower, but still generally under 100 ms. Only a handful of widely spaced delays exceeded 200 ms/w. The worst-case events were dT: 10.002s w: 10.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 6 0 0 0.0 6 113 14.6 3.3 da0b 0 4 0 0 0.0 4 48 29.0 3.1 da0b 0 9 5 79 3.0 5 47 7.9 2.6 da0b 4 8 0 0 0.0 8 99 67.5 32.5 da0b 0 1 0 13 5.6 1 28 5674 88.3 da0b 0 0 0 0 0.0 0 38 18.6 0.3 da0b 0 1 1 9 2.8 0 0 0.0 0.2 da0b 0 1 1 26 5.1 0 0 0.0 0.4 da0b 0 0 0 3 2.6 0 0 0.0 0.1 da0b 0 1 1 9 161.8 0 0 0.0 14.3 da0b No "indefinite delay" warnings were presented on the console. uname -a reports r329893, sources are at 330383. I hope this is useful information, bob prohaska From owner-freebsd-arm@freebsd.org Sun Mar 4 18:35:14 2018 Return-Path: Delivered-To: freebsd-arm@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 765ADF25C6F for ; Sun, 4 Mar 2018 18:35:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 0B17968B7A for ; Sun, 4 Mar 2018 18:35:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id c11so6938272ith.4 for ; Sun, 04 Mar 2018 10:35:14 -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=Ba/purXlbLnwcXfHK8yDOR2jkzCsYAHREfqAOVVcR5U=; b=aS/BQMdOuUQ1qoLYq6CsUlapWMhr2H3S5l+e4SUCCt7lOP1HHEKS9EM7xaNv4BAdsS TfICPPAv11jy3MeeROJpYekECVjNEwSco2XZ+CXmuwyp/m2jpvnfHpmaEvgiiol4LPPS PVWzCJBzrQVN0g5fi7/HPiyFLu0c2JhBNVE9Q9mhjoLXodPb5rY4NMI5q84ci3fABcez w1VDkMGj6UVymxPzYO4l8/zahk1dqGCrGW4VW0xzYfw1F5tzVVd5VUsQ0zw1e/B2nW7M ybgO8k/ISrQYoed+ipD6+wo6DpfZ+qr/Q8ZnilUwsdkArS3WcV+Ewzz5QybMxOCB2aqy gzIQ== 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=Ba/purXlbLnwcXfHK8yDOR2jkzCsYAHREfqAOVVcR5U=; b=ufAqpclD99RutbEO8jjz91YDTElbfm6o4t2xwSb2mFjEduqqvrPTPEauAYU8m5L7wm bSfHUSdnduIoqGocOWU7Gv5miVMxJLFdKNhrh2LTGBYi6yrv94wAKnFWna9eItN9QEtu 0ONx3bnjVIHrfpGp3ngzs3z53HGQoM+8u7taOHNdrlZ3uRhYYWlyb9CyyLSqA4LKzQaK nZRBnLPM/jyNAEJK4tBNY6Q3j2X7lCJQCsEaEp8n0Zf9Io382PoRZFQg0ZhKZoO63sXH ndyW9pmoMn7efLB5YVuHqPiQk25XCz+Iq575DnqRb2DJifWvPUix2zdvSKdrDb7huTfS 8BHg== X-Gm-Message-State: AElRT7HW+Z7fzZEvRhAF422WcljdxEfVYtWUTtz8QrBuwPZtyqlEHB7/ yfPbiRkTL93/5DxEqz7G5+hkX0cTpPEXLTdnk7+NAw== X-Google-Smtp-Source: AG47ELvYc5gUd2Kt2AKdsOkS8832LIpW/Q6xZut/k6tlioLig2AEQvhB+s5L6Raw8LGjgC3bPnUPI8XlxrniaIq6WBE= X-Received: by 10.36.179.8 with SMTP id e8mr11000607itf.36.1520188513206; Sun, 04 Mar 2018 10:35:13 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sun, 4 Mar 2018 10:35:12 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180304182831.GA44154@www.zefox.net> References: <20180228170311.GA26187@www.zefox.net> <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> From: Warner Losh Date: Sun, 4 Mar 2018 11:35:12 -0700 X-Google-Sender-Auth: BFAkSE7xZeOYK2QkOUvC7qEio8s Message-ID: Subject: Re: Is maximum swap usage tunable? To: bob prohaska Cc: Mike , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 18:35:14 -0000 On Sun, Mar 4, 2018 at 11:28 AM, bob prohaska wrote: > On Sat, Mar 03, 2018 at 08:26:05AM -0800, bob prohaska wrote: > > > > Is there some sort of experiment which can distinguish hardware delays > > from software delays? For example, would logging gstat output shed any > > light? > > > For lack of any better ideas, I tried running > make -j2 -DNO_CLEAN buildworld > buildworld.log && make -j2 -DNO_CLEAN > KERNCONF= > ZEFOX buildkernel > buildkernel.log > > while also running > gstat -a -B -I 10s > j2_gstat.log & in another ssh session > > In due course the console reported > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > login: Mar 4 09:28:30 www kernel: pid 9310 (c++), uid 0, was killed: out > of swap space > > as expected. > > However, a grep of j2_gstat revealed a maximum write delay of 30ms/w > for swap on microSD. > > Swap on USB flash is slower, but still generally under 100 ms. > Only a handful of widely spaced delays exceeded 200 ms/w. > gstat doesn't tell you the worst-case. It tells you the average of the requests. This can (and does) hide very long outlier behavior which drives the crazy delayed swap messages. The worst-case events were > dT: 10.002s w: 10.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > > 0 6 0 0 0.0 6 113 14.6 3.3 da0b > 0 4 0 0 0.0 4 48 29.0 3.1 da0b > 0 9 5 79 3.0 5 47 7.9 2.6 da0b > 4 8 0 0 0.0 8 99 67.5 32.5 da0b > 0 1 0 13 5.6 1 28 5674 88.3 da0b > 0 0 0 0 0.0 0 38 18.6 0.3 da0b > 0 1 1 9 2.8 0 0 0.0 0.2 da0b > 0 1 1 26 5.1 0 0 0.0 0.4 da0b > 0 0 0 3 2.6 0 0 0.0 0.1 da0b > 0 1 1 9 161.8 0 0 0.0 14.3 da0b > > No "indefinite delay" warnings were presented on the console. > uname -a reports r329893, sources are at 330383. > > I hope this is useful information, > Despite my quibble over what you're measuring (I look at this stuff all the time for Netflix), I think this is quite useful.... Thanks! Warner From owner-freebsd-arm@freebsd.org Sun Mar 4 18:46:25 2018 Return-Path: Delivered-To: freebsd-arm@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 C9C84F26C3F for ; Sun, 4 Mar 2018 18:46:25 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 5380869306 for ; Sun, 4 Mar 2018 18:46:25 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 5150f898-1fdc-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 5150f898-1fdc-11e8-91c6-33ffc249f3e8; Sun, 04 Mar 2018 18:46:17 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w24IkBhx093540; Sun, 4 Mar 2018 11:46:11 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520189171.38056.2.camel@freebsd.org> Subject: Re: Is maximum swap usage tunable? From: Ian Lepore To: Warner Losh , bob prohaska Cc: "freebsd-arm@freebsd.org" Date: Sun, 04 Mar 2018 11:46:11 -0700 In-Reply-To: References: <20180228170311.GA26187@www.zefox.net> <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 18:46:26 -0000 On Sun, 2018-03-04 at 11:35 -0700, Warner Losh wrote: > On Sun, Mar 4, 2018 at 11:28 AM, bob prohaska wrote: > > > > > On Sat, Mar 03, 2018 at 08:26:05AM -0800, bob prohaska wrote: > > > > > > > > > Is there some sort of experiment which can distinguish hardware delays > > > from software delays? For example, would logging gstat output shed any > > > light? > > > > > For lack of any better ideas, I tried running > > make -j2 -DNO_CLEAN buildworld > buildworld.log && make -j2 -DNO_CLEAN > > KERNCONF= > > ZEFOX buildkernel > buildkernel.log > > > > while also running > > gstat -a -B -I 10s > j2_gstat.log & in another ssh session > > > > In due course the console reported > > > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > > > login: Mar  4 09:28:30 www kernel: pid 9310 (c++), uid 0, was killed: out > > of swap space > > > > as expected. > > > > However, a grep of j2_gstat  revealed a maximum write delay of 30ms/w > > for swap on microSD. > > > > Swap on USB flash is slower, but still generally under 100 ms. > > Only a handful of widely spaced delays exceeded 200 ms/w. > > > gstat doesn't tell you the worst-case. It tells you the average of the > requests. This can (and does) hide very long outlier behavior which drives > the crazy delayed swap messages. > > The worst-case events were > > > > dT: 10.002s  w: 10.000s > >  L(q)  ops/s    r/s   kBps   ms/r    w/s   kBps   ms/w   %busy Name > > > >     0      6      0      0    0.0      6    113   14.6    3.3  da0b > >     0      4      0      0    0.0      4     48   29.0    3.1  da0b > >     0      9      5     79    3.0      5     47    7.9    2.6  da0b > >     4      8      0      0    0.0      8     99   67.5   32.5  da0b > >     0      1      0     13    5.6      1     28   5674   88.3  da0b > >     0      0      0      0    0.0      0     38   18.6    0.3  da0b > >     0      1      1      9    2.8      0      0    0.0    0.2  da0b > >     0      1      1     26    5.1      0      0    0.0    0.4  da0b > >     0      0      0      3    2.6      0      0    0.0    0.1  da0b > >     0      1      1      9  161.8      0      0    0.0   14.3  da0b > > > > No "indefinite delay" warnings were presented on the console. > > uname -a reports r329893, sources are at 330383. > > > > I hope this is useful information, > > > Despite my quibble over what you're measuring (I look at this stuff all the > time for Netflix), I think this is quite useful.... Thanks! > I think it would be more useful with a -I1 instead of 10.  Including the -d flag might also be useful, since deleting is what's so slow on flash-based devices (I'm not sure if swapping triggers BIO_DELETE stuff, but other filesystem activity does). Also, I see a 5-second write latency there at one point.  -- Ian From owner-freebsd-arm@freebsd.org Sun Mar 4 19:38:21 2018 Return-Path: Delivered-To: freebsd-arm@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 EE01CF2C261 for ; Sun, 4 Mar 2018 19:38:20 +0000 (UTC) (envelope-from thomasskibo@yahoo.com) Received: from sonic312-21.consmr.mail.bf2.yahoo.com (sonic312-21.consmr.mail.bf2.yahoo.com [74.6.128.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA0E6C15D for ; Sun, 4 Mar 2018 19:38:20 +0000 (UTC) (envelope-from thomasskibo@yahoo.com) X-YMail-OSG: n5CcW_MVM1kKR6pFgS9T4kP8OUoNH8Qt3sJILdkLntbOrPtAhyyhQGnJpwEDnQu zUH4r1UgJs66JZMg23Qh2cX2vt4.CX0TBVGEJc2U3MydvYvA_3fX2xzXUTjibHhueqg6fMULuLhW 9YK6Fh_EErFEcap2grE0_pXra4f6VJoJwjZjkgPB5IuKOdHE4G0GR7vLgA9ooPUEuG0zz9RaXYKe EUYZUPa0aCfjfk4MhgutXvOCGEt87SR2ZXdTFMORWz6bHPXBUx6Iw8e.RUZ2Xw4ztM1w5K6YWvOp LrCvgbfCQ.2bIUmq40Fcsmj.hf0oNs_yxkBIYMRO.xIYuhPLlxnAMiVPcV4PFnOjad.LkuZMpmQ. CfVpPB4DI0Mspn.EsGs7Qf9xumcEQEiw20hEqeUC5uYoKrXXgLlZVq0QarA4jlZrxjkpx3hrA6Bi dQnPxJmdndlKGtc7oI8g9rPeqhw4Lyv42GU8E43zln5n9wbavp7tELi9lwWNCJlYgifmPv5a5lMr 12.mnryBCBlvJ Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Sun, 4 Mar 2018 19:38:14 +0000 Received: from smtp106.rhel.mail.bf1.yahoo.com (EHLO [192.168.1.21]) ([98.139.231.40]) by smtp405.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID f2ccdda6b7ce1570858a90498488fea1 for ; Sun, 04 Mar 2018 19:38:14 +0000 (UTC) From: Thomas Skibo Content-Type: multipart/mixed; boundary="Apple-Mail=_5921723D-9B2B-449D-91BA-7076B225BE32" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Panic in spi driver Message-Id: <838BFE5B-61CD-4EC4-BB4F-8124B5B3AF9F@yahoo.com> Date: Sun, 4 Mar 2018 11:38:12 -0800 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 19:38:21 -0000 --Apple-Mail=_5921723D-9B2B-449D-91BA-7076B225BE32 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m developing a qspi driver for Zynq/Zedboard and running into = a problem that might affect other spi drivers. When my driver does its = attach, it triggers the attach of the flash driver, dev/flash/mx25l.c, = through spibus. In turn, the flash driver attempts to read the flash = device ident by calling back to my driver=E2=80=99s transfer function. = My driver initiates the transfer and then sleeps on its lock with a = timeout (mtx_sleep(=E2=80=A6, 2 * hz)). That panics the system: = =E2=80=9Cpanic: timed sleep before timers are working=E2=80=9D. I=E2=80=99= ve attached the stack backtrace. I loosely based my driver on bcm2835_spi.c which also sleeps with a = timeout in its transfer function. I tried greping through a few other = spi drivers and noticed dev/intel/spi.c does it too. =20 Okay, before I hit send, I noticed that the other flash driver, at45d.c, = uses some hook to do a delayed attach with the comment =E2=80=9CWe=E2=80=99= ll see what kind of flash we have later=E2=80=A6=E2=80=9D. Maybe = mx25l.c needs something like this. My other idea is to create a =E2=80=9Cfast transfer=E2=80=9D function = that doesn=E2=80=99t use interrupts to be used for trivial transfers. = That would take care of the IDENT and READ_STATUS commands that happen = in the flash driver=E2=80=99s attach routine. It might be a nice = optimization too. =E2=80=94Thomas --Apple-Mail=_5921723D-9B2B-449D-91BA-7076B225BE32 Content-Disposition: attachment; filename=panic.txt Content-Type: text/plain; x-unix-mode=0644; name="panic.txt" Content-Transfer-Encoding: 7bit .... spi0: mem 0xd000-0xdfff irq 13 on simplebus1 spibus0: on spi0 mx25l0: at cs 0 mode 0 on spibus0 panic: timed sleep before timers are working cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc04cef94 lr = 0xc0097da0 (db_trace_self_wrapper+0x30) sp = 0xc0913938 fp = 0xc0913a50 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0097da0 lr = 0xc01e7394 (vpanic+0x154) sp = 0xc0913a58 fp = 0xc0913a78 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc05540f8 r7 = 0xc06789f0 vpanic() at vpanic+0x154 pc = 0xc01e7394 lr = 0xc01e742c (kproc_shutdown) sp = 0xc0913a80 fp = 0xc0913a84 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc30b6c80 r7 = 0xc30b6c80 r8 = 0xc06f6660 r9 = 0x00000001 r10 = 0xfffffdb0 kproc_shutdown() at kproc_shutdown pc = 0xc01e742c lr = 0xc023e184 (sleepq_timeout) sp = 0xc0913a8c fp = 0xc0913ad8 r4 = 0xc01e742c r5 = 0xc0913a8c sleepq_timeout() at sleepq_timeout pc = 0xc023e184 lr = 0xc01f211c (_sleep+0x320) sp = 0xc0913ae0 fp = 0xc0913b40 r4 = 0x00000001 r5 = 0xc30b6c80 r6 = 0xfffffdb0 r7 = 0xc3070904 r8 = 0xc065f780 r10 = 0x00000001 _sleep() at _sleep+0x320 pc = 0xc01f211c lr = 0xc0502024 (zy7_qspi_transfer+0x17c) sp = 0xc0913b48 fp = 0xc0913b80 r4 = 0xfffffdb0 r5 = 0xc3070900 r6 = 0xc30b6c80 r7 = 0xc3070904 r8 = 0x00000000 r9 = 0xc3070880 r10 = 0xc0913b90 zy7_qspi_transfer() at zy7_qspi_transfer+0x17c pc = 0xc0502024 lr = 0xc009ed70 (mx25l_attach+0xe4) sp = 0xc0913b88 fp = 0xc0913bd8 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc30b5400 r7 = 0xc30b5380 r8 = 0xc30b5400 r9 = 0xc3070880 r10 = 0xc30b5450 mx25l_attach() at mx25l_attach+0xe4 pc = 0xc009ed70 lr = 0xc0220f8c (device_attach+0x468) sp = 0xc0913be0 fp = 0xc0913c28 r4 = 0xc30b5400 r5 = 0xc30b5380 r6 = 0xc30b5438 r7 = 0x00000000 r8 = 0xc0554c3d r9 = 0xc022506c device_attach() at device_attach+0x468 pc = 0xc0220f8c lr = 0xc0220a88 (device_probe_and_attach+0x8c) sp = 0xc0913c30 fp = 0xc0913c48 r4 = 0xc30b5400 r5 = 0xc2ec6920 r6 = 0x3e0d8f29 r7 = 0xc0913c64 r8 = 0xc2ebe340 r9 = 0x00000000 r10 = 0xc0913c68 device_probe_and_attach() at device_probe_and_attach+0x8c pc = 0xc0220a88 lr = 0xc022231c (bus_generic_attach+0x1c) sp = 0xc0913c50 fp = 0xc0913c58 r4 = 0xc30b5400 r5 = 0x00000000 r6 = 0xc0532cdc r10 = 0xc0913c68 bus_generic_attach() at bus_generic_attach+0x1c pc = 0xc022231c lr = 0xc00c71b4 (ofw_spibus_attach+0x1e4) sp = 0xc0913c60 fp = 0xc0913c88 r4 = 0xc0634708 r10 = 0xc0913c68 ofw_spibus_attach() at ofw_spibus_attach+0x1e4 pc = 0xc00c71b4 lr = 0xc0220f8c (device_attach+0x468) sp = 0xc0913c90 fp = 0xc0913cd8 r4 = 0xc30b5380 r5 = 0xc30b6c80 r6 = 0xc30b53b8 r7 = 0x00000000 r8 = 0xc0554c3d r9 = 0xc022506c r10 = 0xc30b53d0 device_attach() at device_attach+0x468 pc = 0xc0220f8c lr = 0xc0220a88 (device_probe_and_attach+0x8c) sp = 0xc0913ce0 fp = 0xc0913cf8 r4 = 0xc30b5380 r5 = 0xc2ec6920 r6 = 0x3e0d8f29 r7 = 0xc3070900 r8 = 0xc30b6cd0 r9 = 0xc01f4fb4 r10 = 0xc30b6c80 device_probe_and_attach() at device_probe_and_attach+0x8c pc = 0xc0220a88 lr = 0xc022231c (bus_generic_attach+0x1c) sp = 0xc0913d00 fp = 0xc0913d08 r4 = 0xc30b5380 r5 = 0x00000000 r6 = 0xd2b789c0 r10 = 0xc30b6c80 bus_generic_attach() at bus_generic_attach+0x1c pc = 0xc022231c lr = 0xc0501cb8 (zy7_qspi_attach+0x440) sp = 0xc0913d10 fp = 0xc0913d58 r4 = 0xc051fe8f r10 = 0xc30b6c80 zy7_qspi_attach() at zy7_qspi_attach+0x440 pc = 0xc0501cb8 lr = 0xc0220f8c (device_attach+0x468) sp = 0xc0913d60 fp = 0xc0913da8 r4 = 0xc30b6c80 r5 = 0xc30b7680 r6 = 0xc30b6cb8 r7 = 0x00000000 r8 = 0xc0554c3d r9 = 0xc022506c r10 = 0xc30b6cd0 device_attach() at device_attach+0x468 pc = 0xc0220f8c lr = 0xc0220a88 (device_probe_and_attach+0x8c) sp = 0xc0913db0 fp = 0xc0913dc8 r4 = 0xc30b6c80 r5 = 0xc2ec6920 r6 = 0x3e0d8f29 r7 = 0x00000000 r8 = 0xc0688af4 r9 = 0xc06f744c r10 = 0xc06f6a28 device_probe_and_attach() at device_probe_and_attach+0x8c pc = 0xc0220a88 lr = 0xc0222940 (bus_generic_new_pass+0xe8) sp = 0xc0913dd0 fp = 0xc0913de8 r4 = 0xc30b6c80 r5 = 0xc062b0b4 r6 = 0xc0659b3c r10 = 0xc06f6a28 bus_generic_new_pass() at bus_generic_new_pass+0xe8 pc = 0xc0222940 lr = 0xc0222930 (bus_generic_new_pass+0xd8) sp = 0xc0913df0 fp = 0xc0913e08 r4 = 0xc30b7680 r5 = 0xc062b0b4 r6 = 0xc062182c r7 = 0x00000000 r8 = 0xc0688af4 r10 = 0xc06f6a28 bus_generic_new_pass() at bus_generic_new_pass+0xd8 pc = 0xc0222930 lr = 0xc0222930 (bus_generic_new_pass+0xd8) sp = 0xc0913e10 fp = 0xc0913e28 r4 = 0xc30b7780 r5 = 0xc062b0b4 r6 = 0xc0650600 r7 = 0x00000000 r8 = 0xc0688af4 r10 = 0xc06f6a28 bus_generic_new_pass() at bus_generic_new_pass+0xd8 pc = 0xc0222930 lr = 0xc0222930 (bus_generic_new_pass+0xd8) sp = 0xc0913e30 fp = 0xc0913e48 r4 = 0xc30b7900 r5 = 0xc062b0b4 r6 = 0xc30b7b00 r7 = 0x00000000 r8 = 0xc0688af4 r10 = 0xc06f6a28 bus_generic_new_pass() at bus_generic_new_pass+0xd8 pc = 0xc0222930 lr = 0xc021e568 (bus_set_pass+0x94) sp = 0xc0913e50 fp = 0xc0913e68 r4 = 0xc2ec6680 r5 = 0xc062b0b4 r6 = 0xc30b7b00 r7 = 0xc0688af4 r8 = 0x7fffffff r10 = 0xc06f6a28 bus_set_pass() at bus_set_pass+0x94 pc = 0xc021e568 lr = 0xc01847e0 (mi_startup+0x18c) sp = 0xc0913e70 fp = 0xc0913e90 r4 = 0xc06f6b24 r5 = 0x00000001 r6 = 0xc058b084 r7 = 0x00000000 r8 = 0xc06f6b20 r9 = 0xc058bb48 mi_startup() at mi_startup+0x18c pc = 0xc01847e0 lr = 0xc00002c4 (_start+0x144) sp = 0xc0913e98 fp = 0x00000000 r4 = 0xc00003f8 r5 = 0xc0710000 r6 = 0x01059480 r7 = 0x00c52078 r8 = 0xc0823000 r9 = 0x0000000a r10 = 0x0000000a _start() at _start+0x144 pc = 0xc00002c4 lr = 0xc00002c4 (_start+0x144) sp = 0xc0913e98 fp = 0x00000000 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! db> --Apple-Mail=_5921723D-9B2B-449D-91BA-7076B225BE32-- From owner-freebsd-arm@freebsd.org Sun Mar 4 19:48:30 2018 Return-Path: Delivered-To: freebsd-arm@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 20BF3F2CFC7 for ; Sun, 4 Mar 2018 19:48:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 A93E46C94C for ; Sun, 4 Mar 2018 19:48:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x232.google.com with SMTP id f1so15728148iob.0 for ; Sun, 04 Mar 2018 11:48:29 -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=5zSpcBMiMXnE0c2uHedkMBrARVJmyjMo5hRAUeFkdJc=; b=zchDfsdRn+xPQmP/ENeF7opiLQOV5qksWigxS1V3gaksqvL+YTDvSL1VwsYxBppfFS 00ux+Kcff4Nwp2ILBRSNUcj9FM3uv0iOmoy30nFk9miIZReZL4uljQRRPdfIDnK4SVCP mE3UvU2Bv6hPJ8CvI+ObvvpKYmJUc0iqjbghkYA/c52IFyWMjxZeoQIgZb6+u+7i5fcC fk3mgZTqhV1Rc80620SVy+LtnmD3haKG2+Chv9k1nvL8zonBdD7jutCOT34VDku/iCuD FkUQjQ0Mh7qw5yYVwtfsI5KXgNHovuV20THQffXZguVj7zEGIaXPTyaQdK7TvTYZ5J3+ /1Ow== 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=5zSpcBMiMXnE0c2uHedkMBrARVJmyjMo5hRAUeFkdJc=; b=iN+3IPwP7wwV+n1mfqebXC2kkgtKHMWjA6y3lUh6eSYPgTqvvJP8pDzyokiR+ALtrI bLu5dfaiMzbYF1PQ8gxRm+7j2mG7wvPo8VEYlgFAg5xg1SC1RgrX+IB2RZQqBk4uIZOW fqUnqAg8vCEoRqsq2pqjEejOi5a674HGMEJuTChlTcJKTkyUs6O/9LKqHM5lihtrJWI8 UAyBrnwPF3Kl8PhSE5c1RQHrjRIzEbQ5it6PB4KBpG+xukilI9XIj11mr8YzYoRt1PfX Cdmgu15qXqYf4MXt3l3hq995d0YYQcyhUsa61rDS9J8uTu0GlY53GLTvk4DauC3IROgT DWxA== X-Gm-Message-State: AElRT7Ejhviwdx+IXrwvYQ2SJFgTVtMrYJaJ47k2qsRN3h2QhcBjAJsZ q6RVTcVZXzhN63rRWCO6wjq2AS+9ec/b3XWC/s9Znw== X-Google-Smtp-Source: AG47ELvYquBXxnP/mHfZeb6v1A55uiiHBRv11dZVJl7cU7jeGl0ezA3HkZ+bGIKKsuDp2rTL/S4gem6JBcjGIkG0p1I= X-Received: by 10.107.142.79 with SMTP id q76mr14591333iod.299.1520192908898; Sun, 04 Mar 2018 11:48:28 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sun, 4 Mar 2018 11:48:28 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <1520189171.38056.2.camel@freebsd.org> References: <20180228170311.GA26187@www.zefox.net> <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> From: Warner Losh Date: Sun, 4 Mar 2018 12:48:28 -0700 X-Google-Sender-Auth: pOQF2n9O4s84dS5WPG-907kMb2Q Message-ID: Subject: Re: Is maximum swap usage tunable? To: Ian Lepore Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 19:48:30 -0000 On Sun, Mar 4, 2018 at 11:46 AM, Ian Lepore wrote: > On Sun, 2018-03-04 at 11:35 -0700, Warner Losh wrote: > > On Sun, Mar 4, 2018 at 11:28 AM, bob prohaska > wrote: > > > > > > > > On Sat, Mar 03, 2018 at 08:26:05AM -0800, bob prohaska wrote: > > > > > > > > > > > > Is there some sort of experiment which can distinguish hardware > delays > > > > from software delays? For example, would logging gstat output shed > any > > > > light? > > > > > > > For lack of any better ideas, I tried running > > > make -j2 -DNO_CLEAN buildworld > buildworld.log && make -j2 -DNO_CLEAN > > > KERNCONF= > > > ZEFOX buildkernel > buildkernel.log > > > > > > while also running > > > gstat -a -B -I 10s > j2_gstat.log & in another ssh session > > > > > > In due course the console reported > > > > > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > > > > > login: Mar 4 09:28:30 www kernel: pid 9310 (c++), uid 0, was killed: > out > > > of swap space > > > > > > as expected. > > > > > > However, a grep of j2_gstat revealed a maximum write delay of 30ms/w > > > for swap on microSD. > > > > > > Swap on USB flash is slower, but still generally under 100 ms. > > > Only a handful of widely spaced delays exceeded 200 ms/w. > > > > > gstat doesn't tell you the worst-case. It tells you the average of the > > requests. This can (and does) hide very long outlier behavior which > drives > > the crazy delayed swap messages. > > > > The worst-case events were > > > > > > dT: 10.002s w: 10.000s > > > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > > > > > > 0 6 0 0 0.0 6 113 14.6 3.3 da0b > > > 0 4 0 0 0.0 4 48 29.0 3.1 da0b > > > 0 9 5 79 3.0 5 47 7.9 2.6 da0b > > > 4 8 0 0 0.0 8 99 67.5 32.5 da0b > > > 0 1 0 13 5.6 1 28 5674 88.3 da0b > > > 0 0 0 0 0.0 0 38 18.6 0.3 da0b > > > 0 1 1 9 2.8 0 0 0.0 0.2 da0b > > > 0 1 1 26 5.1 0 0 0.0 0.4 da0b > > > 0 0 0 3 2.6 0 0 0.0 0.1 da0b > > > 0 1 1 9 161.8 0 0 0.0 14.3 da0b > > > > > > No "indefinite delay" warnings were presented on the console. > > > uname -a reports r329893, sources are at 330383. > > > > > > I hope this is useful information, > > > > > Despite my quibble over what you're measuring (I look at this stuff all > the > > time for Netflix), I think this is quite useful.... Thanks! > > > > I think it would be more useful with a -I1 instead of 10. Including > the -d flag might also be useful, since deleting is what's so slow on > flash-based devices (I'm not sure if swapping triggers BIO_DELETE > stuff, but other filesystem activity does). > BIO_DELETE is generated only by filesystems. Nobody has thought through the best strategies to swap to flash. The swap pager doesn't issue BIO_DELETE at all. Warner From owner-freebsd-arm@freebsd.org Sun Mar 4 19:51:49 2018 Return-Path: Delivered-To: freebsd-arm@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 E0FD0F2D508 for ; Sun, 4 Mar 2018 19:51:49 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic315-14.consmr.mail.bf2.yahoo.com (sonic315-14.consmr.mail.bf2.yahoo.com [74.6.134.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8EEE76CDC0 for ; Sun, 4 Mar 2018 19:51:49 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: HMtfn1gVM1m7LxnKKmAfZk4jClMebx4T7soa4kUzvGzfFwwmp5opx8A6wWuQez3 gy4aRbyGqIzbFxr9iY5sK2kcij2vYYwEIC0lVD4toMwV4ENV9OwqhKNoHPSX12160RH3g6c8g5e1 iuNSQII7oNBNhUiwkUmUpCeD6l6U5OAUFVY0kDz0taoQeUg41g9pZJjttYCmYvpxHtagSE5h79dQ yll8n0kjCR8ILTL8uOyPNTqsac1DyqEQJsFw7vnALl1_KrN_K_.Jzy6zVN8G4XF.iY2U_vh29Z2P 2GQodRKdto_aOs4XKhVqMpuY2JCP063mCqUUFuFtL2Agif.ubsXSbdfH1gqWwRa15ttYaIA.J9M5 nsf0er2q3cw0IL4.oOUlb1AZxKmtWS313Q4SB7a_.omvTY4x7grrRqC3nPnJrD.pcJddEZapDmyc X6r4Qd89Q2NWBbrxpUWu98_o7ifJvRKT38my1fQJi6v9ODz3d6RF6tsR8cb__VvV7iVLI Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Sun, 4 Mar 2018 19:51:43 +0000 Received: from smtpgate101.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([72.30.28.45]) by smtp414.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 2b50a3b4302e038f5dd8031ef3222bb2 for ; Sun, 04 Mar 2018 19:51:40 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Is maximum swap usage tunable? Message-Id: <1EB91943-C141-4EA6-AD63-A629525E206E@yahoo.com> Date: Sun, 4 Mar 2018 11:51:39 -0800 To: Freebsd-arm X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 19:51:50 -0000 bob prohaska fbsd at www.zefox.net write on Sun Mar 4 18:28:36 UTC 2018: > The worst-case events were > dT: 10.002s w: 10.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > . . . > 0 1 0 13 5.6 1 28 5674 88.3 da0b > . . . I'll note that (1000s/ms)*(ms/w) != 1/(w/s) here (and frequently). (ms/r and r/s are similarly related.) It appears that ms/w counts time with the write waiting in a queue to be executed or some such but w/s is strictly the observed rate of writes happening, independent of how long each waited. (The columns need not refer to the exact same time frame either as far as I can tell.) [Someone may know the actual details of what ms/w and ms/r spans. The above includes guess work.] Also: 5674 ms/w is over 5 seconds "per write" (probably a "mean" form of average, but possibly only one write covered). I doubt that we can be sure of much about the stages involved in that large figure if "time waiting in the queue" and later stages of the processing all contribute. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-arm@freebsd.org Sun Mar 4 19:55:14 2018 Return-Path: Delivered-To: freebsd-arm@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 2F145F2D8C4 for ; Sun, 4 Mar 2018 19:55:14 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-14.consmr.mail.bf2.yahoo.com (sonic311-14.consmr.mail.bf2.yahoo.com [74.6.131.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBEEE6CF85 for ; Sun, 4 Mar 2018 19:55:13 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 98TUnA0VM1lhVDp02cZGYBQ6TAzHRg8KXGENjl8vBqnJQBGGGi.xmke026xRKUC CkfnKp.1amx_MqqdBjKWAgjh.4r0UTMMgRpWOQe6Y1MTKaAtcgrUaH6qXYUX9ggZWBj9v0qvouh. eeqRbsLFQ96_retrfeTWfx_I1y8KGv8TtSq3i3WcQNExPHa1e04IIJoLG_FF9.bGo8FazZmhGXJQ NBEXmlbuwAns736O8HwvCOKQ8WUH7ay2izDRJIKfiwXNxkflEwIh1stJ0l58bjJcos2sUOdFvMRp .teNxXXUzx6fdOxLwGJANYUXG8MbX_EtiUxodluKuvNG3Q5jshMR7fEllyolba4ANSu1yDccEMfF XWkEf85IJJDypR1bijqBrmNIBvChwMcPRpGOGRuWsRZDNx3LPnRJMQ3Ffjz5ere7PDdCYvdC7Xmd N.3sCm.G_B3BBJ53yR2DqGhAUwLsGsLuOFC0WpM_tSTgUcr6_49i6YAlbiWcLNRIUgSLZ Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.bf2.yahoo.com with HTTP; Sun, 4 Mar 2018 19:55:07 +0000 Received: from smtp104.rhel.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([98.139.230.215]) by smtp404.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 1245dd2daae98c5d26e08a06f08c696d; Sun, 04 Mar 2018 19:55:07 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Is maximum swap usage tunable? Date: Sun, 4 Mar 2018 11:55:05 -0800 References: <1EB91943-C141-4EA6-AD63-A629525E206E@yahoo.com> To: bob prohaska , Freebsd-arm In-Reply-To: <1EB91943-C141-4EA6-AD63-A629525E206E@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 19:55:14 -0000 On 2018-Mar-4, at 11:51 AM, Mark Millard wrote: > bob prohaska fbsd at www.zefox.net write on > Sun Mar 4 18:28:36 UTC 2018: > >> The worst-case events were >> dT: 10.002s w: 10.000s >> L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name >> . . . >> 0 1 0 13 5.6 1 28 5674 88.3 da0b >> . . . > > I'll note that (1000s/ms)*(ms/w) != 1/(w/s) here > (and frequently). (ms/r and r/s are similarly related.) I was interrupted and screwed up the calculation text without noticing: (s/(1000ms))*(ms/w) != 1/(w/s) > It appears that ms/w counts time with the write > waiting in a queue to be executed or some such but > w/s is strictly the observed rate of writes happening, > independent of how long each waited. (The columns need > not refer to the exact same time frame either as far > as I can tell.) > > [Someone may know the actual details of what ms/w > and ms/r spans. The above includes guess work.] > > Also: 5674 ms/w is over 5 seconds "per write" (probably > a "mean" form of average, but possibly only one write > covered). I doubt that we can be sure of much about the > stages involved in that large figure if "time waiting > in the queue" and later stages of the processing all > contribute. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-arm@freebsd.org Sun Mar 4 20:03:15 2018 Return-Path: Delivered-To: freebsd-arm@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 D971EF2E244 for ; Sun, 4 Mar 2018 20:03:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 5BAAA6D4D5 for ; Sun, 4 Mar 2018 20:03:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id l12so15708100ioc.10 for ; Sun, 04 Mar 2018 12:03:14 -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=nwXTUA81kWjRG5TRI77oWxrcUWQkNjvWFYssPFU4dbA=; b=fhsZhgGJJlzLr2QCpeSE4aevJcuyjMqpYiw1oyYtkFQZrhhJnX9BGaN1iWqknurdCN 4Q/ufDwXJQUtL2fHiVEOwjAY6EZ6RNibbvIgIeT7Wu+n5JO3N5/pKR/pTYq0XPuX6OeN 38214vQkELnKF172fYAV94b9UCB16uMQDy8izQ8QQsKp8rBxE/n/UY4yrBOR1ZAqayws S4fKeFXR4c5yZx2J4N18W3c4Ixp7bDhEV1AflwUSpCytJri/48N/W+3krhNxapqZk9wv cwcRWPXnXnoaxTkHDT7M2o4CqIyXqtTqDF0EoAMA8hAYXtreRToKVxqIzexBs8uM1u6Y yCoQ== 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=nwXTUA81kWjRG5TRI77oWxrcUWQkNjvWFYssPFU4dbA=; b=SUmC07bl+tAAywq7hxY9qg7KFhElDAgzpl2OhCz6KVtMegbfcakz6zTg6ASzpse+5b L6O2uCmsIgrDBdCgxHf4Jc4sm/8RmiVslPa/EGDylqSIuZALXs6ovh78b1/1MRPSBCp1 G1zsikr3S4vcn2niZkKl6aIHl5uGwJXNG3v3IKNjuWMRctxj7rD0/go8QOprijQpjDsW kYsSsH4d6XKecSrlABBKcnZF4HBWkgWrO2LvVOJ46goUlBQMI4ffRsZloEHDldv3KgNa wNUMXov+bKlkzAOUtqv2VO37Fky9h1+PPMps32G+SUzCdhkc0DOk3f+66KJ0JeSDn14I xczw== X-Gm-Message-State: APf1xPCLQWgWSYX8hW1VPK3E+fH4LofY8rJwEJqJwyknH+U9tDRo9L9R /yBMfs9ABnxrD6u0aDNcReC9mmaAbo7OToXEawAglg== X-Google-Smtp-Source: AG47ELsQ/BtIT++hU0LUyJQ/mMywomMkwKeixP4glgWqsmm1Op6rRYO0gDX23hg2SWaK7zaLIRN0kybMRa4sjuOrS2k= X-Received: by 10.107.187.129 with SMTP id l123mr14061649iof.39.1520193793564; Sun, 04 Mar 2018 12:03:13 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sun, 4 Mar 2018 12:03:12 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <1EB91943-C141-4EA6-AD63-A629525E206E@yahoo.com> References: <1EB91943-C141-4EA6-AD63-A629525E206E@yahoo.com> From: Warner Losh Date: Sun, 4 Mar 2018 13:03:12 -0700 X-Google-Sender-Auth: nNGdJRLzVWj3H1rBsDUDZUZIgRk Message-ID: Subject: Re: Is maximum swap usage tunable? To: Mark Millard Cc: Freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 20:03:15 -0000 On Sun, Mar 4, 2018 at 12:51 PM, Mark Millard via freebsd-arm < freebsd-arm@freebsd.org> wrote: > bob prohaska fbsd at www.zefox.net write on > Sun Mar 4 18:28:36 UTC 2018: > > > The worst-case events were > > dT: 10.002s w: 10.000s > > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > > . . . > > 0 1 0 13 5.6 1 28 5674 88.3 da0b > > . . . > > I'll note that (1000s/ms)*(ms/w) != 1/(w/s) here > (and frequently). (ms/r and r/s are similarly related.) > > It appears that ms/w counts time with the write > waiting in a queue to be executed or some such but > w/s is strictly the observed rate of writes happening, > independent of how long each waited. (The columns need > not refer to the exact same time frame either as far > as I can tell.) > > [Someone may know the actual details of what ms/w > and ms/r spans. The above includes guess work.] > ms/w is the average time each write, that completed in the polling interval, took to complete after being submitted to the block layer. This includes both software queueing time, if any, and hardware transaction time (including interrupt latency). It's an all-in number. The w/s number is the number of writes completed in the polling interval, divided by the polling interval. > Also: 5674 ms/w is over 5 seconds "per write" (probably > a "mean" form of average, but possibly only one write > covered). I doubt that we can be sure of much about the > stages involved in that large figure if "time waiting > in the queue" and later stages of the processing all > contribute. It means that during the polling interval, the average time of the transactions ending in the polling interval, took 5.6s to complete. Even with mad-queueing, that's about 10x-100x the latency one should normally expect. But it doesn't really matter, for these purposes, if it took 5s to complete 1 I/O, or if it was in the queue for 4.9s and then took .1s to complete. It's still really long and stretching the bounds of what the system can put up with. The write-link to the device is hyper-saturated and no good, and likely some bad, will come from that. Warner From owner-freebsd-arm@freebsd.org Sun Mar 4 21:00:08 2018 Return-Path: Delivered-To: freebsd-arm@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 907C6F321BB for ; Sun, 4 Mar 2018 21:00:08 +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 542A56F18A for ; Sun, 4 Mar 2018 21:00:08 +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 7F69114405 for ; Sun, 4 Mar 2018 21:00:07 +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 w24L074a069711 for ; Sun, 4 Mar 2018 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w24L06U4069284 for freebsd-arm@FreeBSD.org; Sun, 4 Mar 2018 21:00:06 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201803042100.w24L06U4069284@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 4 Mar 2018 21:00:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 21:00:08 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 220297 | arch(7) rename arm64 to aarch64 respecting `uname 1 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Sun Mar 4 21:40:07 2018 Return-Path: Delivered-To: freebsd-arm@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 D052FF35ED0 for ; Sun, 4 Mar 2018 21:40:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 406CD7178F; Sun, 4 Mar 2018 21:40:05 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w24Le420046782 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 4 Mar 2018 13:40:04 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w24Le3RQ046781; Sun, 4 Mar 2018 13:40:03 -0800 (PST) (envelope-from fbsd) Date: Sun, 4 Mar 2018 13:40:03 -0800 From: bob prohaska To: Ian Lepore Cc: Warner Losh , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180304214003.GB44154@www.zefox.net> References: <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520189171.38056.2.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 21:40:07 -0000 On Sun, Mar 04, 2018 at 11:46:11AM -0700, Ian Lepore wrote: > On Sun, 2018-03-04 at 11:35 -0700, Warner Losh wrote: > > On Sun, Mar 4, 2018 at 11:28 AM, bob prohaska wrote: > > > > > > > > On Sat, Mar 03, 2018 at 08:26:05AM -0800, bob prohaska wrote: > > > > > > > > > > > > Is there some sort of experiment which can distinguish hardware delays > > > > from software delays? For example, would logging gstat output shed any > > > > light? > > > > > > > For lack of any better ideas, I tried running > > > make -j2 -DNO_CLEAN buildworld > buildworld.log && make -j2 -DNO_CLEAN > > > KERNCONF= > > > ZEFOX buildkernel > buildkernel.log > > > > > > while also running > > > gstat -a -B -I 10s > j2_gstat.log & in another ssh session > > > > > > In due course the console reported > > > > > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > > > > > login: Mar??4 09:28:30 www kernel: pid 9310 (c++), uid 0, was killed: out > > > of swap space > > > > > > as expected. > > > > > > However, a grep of j2_gstat??revealed a maximum write delay of 30ms/w > > > for swap on microSD. > > > > > > Swap on USB flash is slower, but still generally under 100 ms. > > > Only a handful of widely spaced delays exceeded 200 ms/w. > > > > > gstat doesn't tell you the worst-case. It tells you the average of the > > requests. This can (and does) hide very long outlier behavior which drives > > the crazy delayed swap messages. > > > > The worst-case events were > > > > > > dT: 10.002s??w: 10.000s > > > ?L(q)??ops/s????r/s???kBps???ms/r????w/s???kBps???ms/w???%busy Name > > > > > > ????0??????6??????0??????0????0.0??????6????113???14.6????3.3??da0b > > > ????0??????4??????0??????0????0.0??????4?????48???29.0????3.1??da0b > > > ????0??????9??????5?????79????3.0??????5?????47????7.9????2.6??da0b > > > ????4??????8??????0??????0????0.0??????8?????99???67.5???32.5??da0b > > > ????0??????1??????0?????13????5.6??????1?????28???5674???88.3??da0b > > > ????0??????0??????0??????0????0.0??????0?????38???18.6????0.3??da0b > > > ????0??????1??????1??????9????2.8??????0??????0????0.0????0.2??da0b > > > ????0??????1??????1?????26????5.1??????0??????0????0.0????0.4??da0b > > > ????0??????0??????0??????3????2.6??????0??????0????0.0????0.1??da0b > > > ????0??????1??????1??????9??161.8??????0??????0????0.0???14.3??da0b > > > [where did all the question marks come from?] > > > No "indefinite delay" warnings were presented on the console. > > > uname -a reports r329893, sources are at 330383. > > > > > > I hope this is useful information, > > > > > Despite my quibble over what you're measuring (I look at this stuff all the > > time for Netflix), I think this is quite useful.... Thanks! > > > > I think it would be more useful with a -I1 instead of 10. ?Including > the -d flag might also be useful, since deleting is what's so slow on > flash-based devices (I'm not sure if swapping triggers BIO_DELETE > stuff, but other filesystem activity does). > A few minutes before reading your reply a make -j4 buildworld was started with the usb-hosted swap partition turned off, leaving only the microSD-hosted swap running. It got past the first cycle of llvm-tblgen showing only half of the one GB available swap in use, with no errors or warnings. There is some decent chance it'll run to completion, probably late tomorrow. For now I'll just see how far it gets. > Also, I see a 5-second write latency there at one point.? > Yes, just one. Are there perhaps more specific monitoring tests that could distinguish between swap-related, flash-related and usb-related sources of delay? Armv7 seems to have some USB debugging options in the kernel config, is there something similar for arm64? I looked but didn't see any. Thanks for reading, and any guidance! bob prohaska From owner-freebsd-arm@freebsd.org Mon Mar 5 02:24:00 2018 Return-Path: Delivered-To: freebsd-arm@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 E0B08F247D1 for ; Mon, 5 Mar 2018 02:23:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 6F5267D795 for ; Mon, 5 Mar 2018 02:23:59 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 41983f24-201c-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 41983f24-201c-11e8-91c6-33ffc249f3e8; Mon, 05 Mar 2018 02:23:57 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w252Nr1w094455; Sun, 4 Mar 2018 19:23:53 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520216633.38056.12.camel@freebsd.org> Subject: Re: Panic in spi driver From: Ian Lepore To: Thomas Skibo , freebsd-arm@freebsd.org Date: Sun, 04 Mar 2018 19:23:53 -0700 In-Reply-To: <838BFE5B-61CD-4EC4-BB4F-8124B5B3AF9F@yahoo.com> References: <838BFE5B-61CD-4EC4-BB4F-8124B5B3AF9F@yahoo.com> Content-Type: text/plain; charset="windows-1251" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 02:24:00 -0000 On Sun, 2018-03-04 at 11:38 -0800, Thomas Skibo via freebsd-arm wrote: > I’m developing a qspi driver for Zynq/Zedboard and running into a > problem that might affect other spi drivers.  When my driver does its > attach, it triggers the attach of the flash driver, > dev/flash/mx25l.c, through spibus.  In turn, the flash driver > attempts to read the flash device ident by calling back to my > driver’s transfer function.  My driver initiates the transfer and > then sleeps on its lock with a timeout (mtx_sleep(…, 2 * hz)).  That > panics the system: “panic: timed sleep before timers are > working”.  I’ve attached the stack backtrace. > > I loosely based my driver on bcm2835_spi.c which also sleeps with a > timeout in its transfer function.  I tried greping through a few > other spi drivers and noticed dev/intel/spi.c does it too.   > > Okay, before I hit send, I noticed that the other flash driver, > at45d.c, uses some hook to do a delayed attach with the comment > “We’ll see what kind of flash we have later…”.  Maybe mx25l.c needs > something like this. > > My other idea is to create a “fast transfer” function that doesn’t > use interrupts to be used for trivial transfers.  That would take > care of the IDENT and READ_STATUS commands that happen in the flash > driver’s attach routine.  It might be a nice optimization too. > > —Thomas Ooops, I just realized I had the same problem in the new imx6 spi driver I committed a couple days ago.  I did all my testing using loadable modules, forgot to ever test compiling everything in.  As soon as I did, panic. So in the i2c world this problem was historically fixed by every individual slave device driver using a config_intrhook_establish() in its attach routine to do the real attach work later, after interrupts are working.  We should avoid the same mistake in the spi world. The way I see it, if a driver that performs IO for its children requires interrupts to function, it should not attach the child devices until interrupts are working.  In other words, put the config_intrhook in the single driver that really needs it, not in every child driver. If there's a situation where the spi driver has to do IO before interrupts can be enabled (maybe to make a PMIC or other hardware- control device work early in boot), then it has to have a transfer implementation that uses some kind of polling loop until interrupts are available (basically, have two implementations of transfer()). I just committed the imx_spi fix in r330438.  The basic fix is instead of ending attach() with    return (bus_generic_attach(sc->dev)); do    config_intrhook_oneshot((ich_func_t)bus_generic_attach, dev);   return (0); -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 5 04:57:33 2018 Return-Path: Delivered-To: freebsd-arm@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 BCB72F3082B for ; Mon, 5 Mar 2018 04:57:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1783082B68; Mon, 5 Mar 2018 04:57:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w254vOac048265 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 4 Mar 2018 20:57:25 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w254vN1w048264; Sun, 4 Mar 2018 20:57:23 -0800 (PST) (envelope-from fbsd) Date: Sun, 4 Mar 2018 20:57:23 -0800 From: bob prohaska To: Ian Lepore Cc: Warner Losh , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180305045723.GA47820@www.zefox.net> References: <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180304214003.GB44154@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 04:57:33 -0000 On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: > make -j4 buildworld > > was started with the usb-hosted swap partition turned off, leaving only > the microSD-hosted swap running. It got past the first cycle of llvm-tblgen > showing only half of the one GB available swap in use, with no errors or > warnings. There is some decent chance it'll run to completion, probably > late tomorrow. For now I'll just see how far it gets. > The j4 buildworld using only 1 GB swap on microSD really ran out of swap after a prolonged (half hour or so) interval of swread and pfault status in top and a stream of swap_pager_getswapspace(4): failed swap_pager_getswapspace(4): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(3): failed Mar 4 20:02:09 www kernel: pid 25154 (c++), uid 0, was killed: out of swap space swap_pager_getswapspace(4): failed swap_pager_getswapspace(4): failed swap_pager_getswapspace(4): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(4): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(4): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(4): failed Mar 4 20:02:49 www kernel: pid 25128 (c++), uid 0, was killed: out of swap space swap_pager_getswapspace(4): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(7): failed on the console. There were no "indefinite wait" messages at all It appears that swap on microSD worked much better than swap on USB, only failing after hitting 85% or more of utilization and even then not giving up easily. The log files for buildworld and gstat are at http://www.zefox.net/~fbsd/rpi3/swap_issues/ on the chance they're worth looking at. bob prohaska From owner-freebsd-arm@freebsd.org Mon Mar 5 05:30:19 2018 Return-Path: Delivered-To: freebsd-arm@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 AB613F32B41 for ; Mon, 5 Mar 2018 05:30:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 2717F83BD4 for ; Mon, 5 Mar 2018 05:30:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id p78so16583167iod.13 for ; Sun, 04 Mar 2018 21:30:19 -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=iiRLT6sfk4gu+OPTBKEY8f0NSglpdajcDgwhpYNIhLA=; b=j9WGKqnG2X+FYTfDpmicBaPqOOls7N2wcuxSASK766gPZNbX90/bUY8GPuyL7xk6rj b1LkfwPMnGgDouy5FHeJ/lvCH6V9nb7rtEKtQK2CTDN74TLZ8Aestciv04z8n7OCB3L8 qzhzC19Fyrs45vF206I56/OCoWBEW+HJGHD8+7wbYL8lkfz0/AKOyHv18+oUEzvj6gnQ QMPLkOzRuLzXh2xpNnxX6CFkKuBPtXn++a7Nk+k3KwlyF4/tgrDgyjVE7m1Z0q3l9tjC GyXr6sunzGUuKv6kQMZtpWVpxn6xSzThpcsX+Xj6kFVO0EO3ExU8vM/z/f2TjDuyc5fy rkfw== 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=iiRLT6sfk4gu+OPTBKEY8f0NSglpdajcDgwhpYNIhLA=; b=Kh1h7DMBZp7pm7DtbGXAOuENPlB3NQvBbCz2S9VfnNtnewbhb8a7qr0X63wiP8wJKL PQvh/0gDf1h5j9cmAX+dsR6FayI9HVLFM5hi25k2xfv+aV+PPpRF9nHTzY3ZSQ3gUMtz pfpAwQTvopoUXF/S8eVS+w7hh8TpreU0eIxAXbJMp6vxNHNGItWNhYTUZfaOB5wcNeu4 fnLF9KiecwvAsqPiVYFGBsP2Uyudj9dKknClw1dz8R+TfP0yrdQUW+tWd8x3maQilQ8l ToXosyB+/CQTzoQQxcjtR7/YeeOITxdWVTiZW4rdR4NO6L87k/rqHwTjjh+BvfigpY/Q nlVg== X-Gm-Message-State: APf1xPClHxG98wO5Xklbh2dkqn5LgOJQiC8WU6P/gd38dMNb3V9/fVus BK4J1lS1NOoZz+YinQ2+Ewww/qrMRIdejLIx0+QETA== X-Google-Smtp-Source: AG47ELu0tIzbNLnOcD8tSF/R04C6LAef8R6ad8Jvo+BosVvDjXNWmNDJceYeAs20HQPKS5T3BJIlQLgd0Qkk3HXvSYQ= X-Received: by 10.107.2.6 with SMTP id 6mr15606405ioc.117.1520227818409; Sun, 04 Mar 2018 21:30:18 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sun, 4 Mar 2018 21:30:17 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180305045723.GA47820@www.zefox.net> References: <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> From: Warner Losh Date: Sun, 4 Mar 2018 22:30:17 -0700 X-Google-Sender-Auth: E8AMPtj56PeX4dCzEpELpjE2Szg Message-ID: Subject: Re: Is maximum swap usage tunable? To: bob prohaska Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 05:30:20 -0000 On Sun, Mar 4, 2018 at 9:57 PM, bob prohaska wrote: > On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: > > make -j4 buildworld > > > > was started with the usb-hosted swap partition turned off, leaving only > > the microSD-hosted swap running. It got past the first cycle of > llvm-tblgen > > showing only half of the one GB available swap in use, with no errors or > > warnings. There is some decent chance it'll run to completion, probably > > late tomorrow. For now I'll just see how far it gets. > > > The j4 buildworld using only 1 GB swap on microSD really ran out of > swap after a prolonged (half hour or so) interval of swread and pfault > status in top and a stream of > > swap_pager_getswapspace(4): failed > Yes. This meant that the swapper tried to get space, but failed. It prints this once, then all further requests print nothing until one succeeds and then it prints it again. So you are rockering back and forth on the edge until it finally fails... > Mar 4 20:02:09 www kernel: pid 25154 (c++), uid 0, was killed: out of > swap space > and kills something, the C++ compiler. A good choice if you are low on space. > on the console. There were no "indefinite wait" messages at all > That just means that the SD card wasn't overwhelmed this time.... > It appears that swap on microSD worked much better than > swap on USB, only failing after hitting 85% or more of utilization > and even then not giving up easily. > You likely have power issues then. Power issues and/or cheap-ass USB<->SD adapters can cause the extremely slow writes that lead to the indefinite wait. > The log files for buildworld and gstat are at > http://www.zefox.net/~fbsd/rpi3/swap_issues/ > on the chance they're worth looking at. I'd look at power. And add more swap. Warner > > bob prohaska > > > > > > From owner-freebsd-arm@freebsd.org Mon Mar 5 08:04:43 2018 Return-Path: Delivered-To: freebsd-arm@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 11D87F3B3BE; Mon, 5 Mar 2018 08:04:43 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 AD4A7698AD; Mon, 5 Mar 2018 08:04:42 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9A1A320C7C; Mon, 5 Mar 2018 03:04:36 -0500 (EST) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Mon, 05 Mar 2018 03:04:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=nKrfoILRSA38D/xBQfMJRQO3ikWud u7HfJHwEU+ITH4=; b=wxkJGMvSK/5LtbVA4BMKnk+X7SZAvXpAvwd1ag+t0t+XO aSuT0at0iMayIZDJZiqOJ0aHM2VGSQj6l7aXYK1bLniBb0yxxbTAul3Z3QnzQNgN UabVOL4utY+34q/dSgtl29ydP8vFVtMMvIXEB+qIUWE+gJ2xI2u8QGwZqQYdJouV xdM8cGzndd8meb3HfSdWYRhebJE9I8TPoGxCp5AwR3g95Mm6PdI8i4DEhWvkATwB dft2Sd/ZR25caBNFU09kvzwVf0cdJV88+EN4adMWxqtDG5/SzUQX3yrA8tx0Kgac Licy/I8T3upmHJdqsxO33fwSw+goINTzZfsK0QU9w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=nKrfoI LRSA38D/xBQfMJRQO3ikWudu7HfJHwEU+ITH4=; b=cZuq+Y3AVHB0epvltFoV/6 +TVr+AU9jGQDSwa1rqBalkodhr5Fd5oZu6b37MUpaz5RtNgtmSulJhL1V7V08G4q h/+LSdYkUocM7Z5Z5cp01TXqPYKSYLePtnQUvTVWsBRUeHcxpdEmfun2tk1A/9OR J8ifuHSS77RDVhLP/IFt96JDiLSVNuscuIq3J+AuguASSxu4ST5kp7+9wOE2mayB 7no/L/kj4ymA6Gd6EwZvXERf22bYrbe2uqaqh9iIGHHOrS4WJF3uJSAIbsVNPVnR o1Nyk8gozKSoFQfMNlbsOzT8NWArfEzjxeU+kcoMDGPtsPrnLmIYKuMhyXzib5sA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 7362EBA43B; Mon, 5 Mar 2018 03:04:36 -0500 (EST) Message-Id: <52ea5465-7d89-b699-b997-e026b7726bfb@zyxst.net> From: John To: Oleksandr Tymoshenko , Hyun Hwang Cc: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b86e6959 Date: Mon, 05 Mar 2018 08:04:36 +0000 Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github In-Reply-To: <20180304073727.GA29648@bluezbox.com> References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> <20180304073727.GA29648@bluezbox.com> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 08:04:43 -0000 On 04/03/2018 07:37, Oleksandr Tymoshenko wrote: > There is ongoing work on using RPi firmware port for all RPi models and > switching u-boot-rpi3 to the same framework as u-boot-rpi2 but it > involves changes across multiple areas (drivers, ports, release > scripts). Some of this stuff is already committed, some is in review, > some is WIP. Hi, I managed to build a freebsd-12-arm6-rpi2 image with freebsd/crochet by installing the rpi-firmware port and copying the files from /usr/local/share/rpi-firmware into /usr/local/share/u-boot/u-boot-rpi2 then running freebsd/crochet as usual. Thank you for pointing me in the right direction :D -- J. From owner-freebsd-arm@freebsd.org Mon Mar 5 14:59:35 2018 Return-Path: Delivered-To: freebsd-arm@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 89B18F35AC9 for ; Mon, 5 Mar 2018 14:59:35 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [IPv6:2607:f2f8:af30::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E52A7D4A2 for ; Mon, 5 Mar 2018 14:59:34 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zw3390R1VzWCVy for ; Mon, 5 Mar 2018 09:59:33 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520261973; bh=stLERMD3slgpNYIyhlZMsIkzNVnF5UXBDsxgBzm/vpM=; h=Subject:To:From:Message-ID:Date; b=ZEna5B4FbCiom7uz9SL5mkDAsJE0Onrj/xzWTGR0ORfvMgvGK07buVo64IL2b1pMu WU7DQxEcEAyv659QiahHNjeg44hEo9kNLGVnJ4JhKsX13pySA6Ht2La8Ly+RINWsiK v6uUT83Ja0POW5qqqQV/BMmhe9GYrNIlyPax6J9wTv/df3xx+TLjCVK5l2G8oKgwBK 4i9MMZaz7MGX/RWlbbUcgKWAw4hu4/8t21f8X2a6Yk34K3VnYsSL4ThaMnoO9dapzF AtD9HkjiuU2N+fiMZ/pGndwNc38D1xQsfUwve/JjWZ0n2UoQOeCYQGd2tPlKm7yCOH in4xxb8/Ex+ew== Received: from [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f] (unknown [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f]) by sentry.24cl.com (Postfix) with ESMTP id 3zw3380XTdzkB4D for ; Mon, 5 Mar 2018 09:59:32 -0500 (EST) Subject: Re: Is maximum swap usage tunable? To: freebsd-arm@freebsd.org References: <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> From: Mike Message-ID: <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> Date: Mon, 5 Mar 2018 09:59:15 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305045723.GA47820@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 14:59:35 -0000 On 3/4/2018 11:57 PM, bob prohaska wrote: > On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: >> make -j4 buildworld >[snip] I tried a buildworld using spinning rust for swap connected via USB" ======== /usr/bin/make -j3 buildworld [lots of output omitted, can be supplied if needed] --- Sema/SemaExprCXX.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.Sema_SemaExprCXX.o -MTSema/SemaExprCXX.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/Sema/SemaExprCXX.cpp -o Sema/SemaExprCXX.o --- Sema/SemaExprMember.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.Sema_SemaExprMember.o -MTSema/SemaExprMember.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/Sema/SemaExprMember.cpp -o Sema/SemaExprMember.o --- Sema/SemaExprObjC.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.Sema_SemaExprObjC.o -MTSema/SemaExprObjC.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/Sema/SemaExprObjC.cpp -o Sema/SemaExprObjC.o Killed *** [all_subdir_lib/clang/libclang] Error code 137 make[3]: stopped in /usr/src/lib/clang 1 error make[3]: stopped in /usr/src/lib/clang *** [cross-tools] Error code 2 make[2]: stopped in /usr/src 1 error make[2]: stopped in /usr/src *** [_cross-tools] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src >From /var/log/messages Mar 4 23:32:39 rpi3 kernel: pid 27325 (c++), uid 0, was killed: out of swap space Mar 4 23:32:54 rpi3 kernel: pid 27322 (c++), uid 0, was killed: out of swap space Mar 4 23:32:54 rpi3 kernel: pid 27387 (c++), uid 0, was killed: out of swap space Mar 4 23:32:54 rpi3 kernel: pid 24978 (make), uid 0, was killed: out of swap space Mar 4 23:32:54 rpi3 kernel: pid 757 (qmgr), uid 125, was killed: out of swap space # swapctl -l Device: 1024-blocks Used: /dev/md99 1048576 13248 ======= I plan to try again, same hardware but with 2GB swap space. From owner-freebsd-arm@freebsd.org Mon Mar 5 16:22:30 2018 Return-Path: Delivered-To: freebsd-arm@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 DA85AF3C799 for ; Mon, 5 Mar 2018 16:22:30 +0000 (UTC) (envelope-from thomasskibo@yahoo.com) Received: from sonic316-8.consmr.mail.gq1.yahoo.com (sonic316-8.consmr.mail.gq1.yahoo.com [98.137.69.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E85C811F8 for ; Mon, 5 Mar 2018 16:22:30 +0000 (UTC) (envelope-from thomasskibo@yahoo.com) X-YMail-OSG: PQipgT0VM1ltkJkYEC0tFM8Ik.NELhXwhsEcY51zYg7iUSQMcOzclIiuQno0l9c c4ij9MaGkhTZYf9nJe99hJq8swq_x_zxXrWw7SzT9PwX8a5UJx4vPnmP_wgQWCAxODLSwV6MOfhx Wdsp2dRlEGRRx0iAKkrp0izqBmwS7cGr9YZz5k71mFJ8K7q7BN6lb6g4SUpcUBO.XgWES6BOpdN4 WUNgAMESets0uLVyLxVrf5WceoFuotO56qjJPH1_ReEE2x6uaXM6zg9q9HaelobSBr2sFbPZbgMv LFnhzNeQkvxYYn9DjogJInXxdbRoaujaL94WmlrEXP4.y3yB4A8xiMH4KrbwC_U83BHj3SlN04g4 wYQEjwNLV9vVHAJHqlXnU57XWNcCiEPunTVjhY5nrIBJOWCCtGo53kUV8sHBslrmITC2PBYHvI8a .QxBX5nEQMLFG02p1qMYe.AzjgYU8ZHpAkxY08tk2efWtB_9w5618dcEpssOgeOVi7veb_qcokKb W16WP6dT_g9IakHyl2sQkdAjiIQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Mon, 5 Mar 2018 16:22:23 +0000 Received: from smtp109.rhel.mail.gq1.yahoo.com (EHLO [192.168.1.20]) ([10.211.35.160]) by smtp408.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID fd0cc64d147ee957e1470c758161a0b2; Mon, 05 Mar 2018 16:12:13 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Panic in spi driver From: Thomas Skibo In-Reply-To: <1520216633.38056.12.camel@freebsd.org> Date: Mon, 5 Mar 2018 08:12:12 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <165F26C2-AD03-41FC-92A5-105D3CE2E514@yahoo.com> References: <838BFE5B-61CD-4EC4-BB4F-8124B5B3AF9F@yahoo.com> <1520216633.38056.12.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 16:22:31 -0000 > On Mar 4, 2018, at 6:23 PM, Ian Lepore wrote: >=20 >=20 > I just committed the imx_spi fix in r330438. The basic fix is instead > of ending attach() with=20 >=20 > return (bus_generic_attach(sc->dev)); >=20 > do=20 >=20 > config_intrhook_oneshot((ich_func_t)bus_generic_attach, dev); > return (0); >=20 > -- Ian Thanks, Ian. This works slick. I did manage to implement a polling = loop transfer function for transfers 4 bytes or less and that worked = too. But this is cleaner. =E2=80=94Thomas From owner-freebsd-arm@freebsd.org Mon Mar 5 16:59:42 2018 Return-Path: Delivered-To: freebsd-arm@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 32B9DF3F231 for ; Mon, 5 Mar 2018 16:59:42 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CF7482A35 for ; Mon, 5 Mar 2018 16:59:41 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w25GxbMw024384 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 5 Mar 2018 17:59:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w25GxYJ1040237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 17:59:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w25GxYOs065250 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 17:59:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w25GxYCi065249; Mon, 5 Mar 2018 17:59:34 +0100 (CET) (envelope-from ticso) Date: Mon, 5 Mar 2018 17:59:34 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: Bernd Walter Subject: Webbrowser Message-ID: <20180305165934.GH31939@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 16:59:42 -0000 It seems that there is not useable webbrowser for arm. I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. The only brwosers I got running is billo and midori. The first one is practically unuseable these days and midori always crashes when the javascript engine starts. With javascript disabled midori runs fine, but I need JS. Did anyone already spend some time debugging this issue? -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 5 17:11:35 2018 Return-Path: Delivered-To: freebsd-arm@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 5ACCBF40448 for ; Mon, 5 Mar 2018 17:11:35 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C6775837B7 for ; Mon, 5 Mar 2018 17:11:34 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w25HBW9M024603 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 5 Mar 2018 18:11:32 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w25HBTjJ040461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 18:11:29 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w25HBTCU065327 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 18:11:29 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w25HBTb8065326; Mon, 5 Mar 2018 18:11:29 +0100 (CET) (envelope-from ticso) Date: Mon, 5 Mar 2018 18:11:29 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: Bernd Walter Subject: growfs problem on current Message-ID: <20180305171128.GI31939@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 17:11:35 -0000 Not sure if this is stricly current, but so far I could see this problem with current only. The filesystem expands and everything seems to be fine. But in fact the filesystem is broken and fails in a way, which can't be solved by fsck anymore. Somehow it tries to access data not reachable. I havn't had the time to investigate it further. Don't know if something in the partition tables or the filesystem is wrong. As a workaround I always expand the FS on my stable running desktop before booting on the ARM. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 5 17:18:51 2018 Return-Path: Delivered-To: freebsd-arm@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 A4A29F40E70 for ; Mon, 5 Mar 2018 17:18:51 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 1912384715 for ; Mon, 5 Mar 2018 17:18:51 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: by mail-pl0-x22e.google.com with SMTP id bb3-v6so10044406plb.2 for ; Mon, 05 Mar 2018 09:18:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9jUmJUWVLbMSoNV959l+zP+d38PvikCR1RiFeXkuIco=; b=XMUCe/lZpuardWEvsXTfhCW14MQqtmketXVT1uq+AFljVieuDbTrmblPAObhSaiRgi jr79q0ryooBpopMwkt7L6heoUt6O3RaBK+iONzwDjB5/afhf1DheHrFfINf9msBFjogy AhFI7yvIQmDhRtB6+noDE4Hc+g3iX5SkVtUmAqFfjnMWuYNNULLFHU7tAhj6GVDVepuG cecWgE1GWZjNXferDcKIjhy/Rr87ClCUcM/9xpCdgVYIcwVtHlqYs8NeoQqrL7z6Tjre tXSHF/PHJCMRkfXdROPEcJl/of8uCFLXTMj0+8XI5qY6amNB6pvorTatz5lvVPT0qW8U CguA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9jUmJUWVLbMSoNV959l+zP+d38PvikCR1RiFeXkuIco=; b=Bj/iuVSqnrCSv7E098Of3K3mNM47YLn8PZ1GIHetW77LoFiaBqTMyhfzl4zPtb/Lez wDJwTx+A1/lsdcy59HhX5AhbQakGxdHiuXjgN16gh7AGAbLCO8uX1K2SAPstMUzuLsmj trhVD74a5v2gfFVcdY3w3NVYchAEtZ6M9SmGf3jHEGjb17oP7IiaAGEuZUryGMxHejgj +6bW+vNz/gd6a6RNmRq7Qh6PivmGw8R736ULK2kD+3QZIjmTgIk/8BSDDE+fTNTYMOYF 7YcRt/M/QRzChVhsATgN3nvHxXOeZug4uwWlmSSUdz3AvnsLpwZXardfurGaW7zM9+jH 9eHQ== X-Gm-Message-State: AElRT7FycH0LGImlR8KrrXVzUe9MGbQpSHmOpCz8eUtvomt8LckQ+zyd 0oQTrUxLSXclYoYJSMjUSu1Hd37t+Wgb5uF37AE= X-Google-Smtp-Source: AG47ELuUBh7Rvzj5LnwLMuDjpJiNQSb67x/H8l97XPLkzDyP9RyBKQpTumtWeK/JoOG0qVBwuz0BOpCCBJj2bla/RTk= X-Received: by 2002:a17:902:ad0b:: with SMTP id i11-v6mr5449991plr.10.1520270329748; Mon, 05 Mar 2018 09:18:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.132.9 with HTTP; Mon, 5 Mar 2018 09:18:09 -0800 (PST) In-Reply-To: <20180305165934.GH31939@cicely7.cicely.de> References: <20180305165934.GH31939@cicely7.cicely.de> From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Date: Mon, 5 Mar 2018 18:18:09 +0100 Message-ID: Subject: Re: Webbrowser To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, Bernd Walter Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 17:18:51 -0000 Le 5 mars 2018 18:00, "Bernd Walter" a =C3=A9crit= : It seems that there is not useable webbrowser for arm. I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. The only brwosers I got running is billo and midori. The first one is practically unuseable these days and midori always crashes when the javascript engine starts. With javascript disabled midori runs fine, but I need JS. Did anyone already spend some time debugging this issue? The jit in webkit is broken on armv6/7, you need to recompile it with this configure flag: --disable-jit I created a PR for firefox-esr: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225279 From owner-freebsd-arm@freebsd.org Mon Mar 5 17:32:47 2018 Return-Path: Delivered-To: freebsd-arm@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 31139F41FBE for ; Mon, 5 Mar 2018 17:32:47 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A195685459 for ; Mon, 5 Mar 2018 17:32:46 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w25HWhvk024922 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 18:32:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w25HWeAD040799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 18:32:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w25HWe2X065395 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 18:32:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w25HWeuC065394; Mon, 5 Mar 2018 18:32:40 +0100 (CET) (envelope-from ticso) Date: Mon, 5 Mar 2018 18:32:40 +0100 From: Bernd Walter To: =?iso-8859-1?Q?Mika=EBl?= Urankar Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: Webbrowser Message-ID: <20180305173240.GJ31939@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180305165934.GH31939@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 17:32:47 -0000 On Mon, Mar 05, 2018 at 06:18:09PM +0100, Mikaël Urankar wrote: > Le 5 mars 2018 18:00, "Bernd Walter" a écrit : > > It seems that there is not useable webbrowser for arm. > I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. > The only brwosers I got running is billo and midori. > The first one is practically unuseable these days and midori always > crashes when the javascript engine starts. > With javascript disabled midori runs fine, but I need JS. > Did anyone already spend some time debugging this issue? > > > The jit in webkit is broken on armv6/7, you need to recompile it with this > configure flag: --disable-jit > I created a PR for firefox-esr: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225279 Ok - this is a patch to get the JIT running in firefox? A quick look showed that you do ${ARCH} == armv6 || ${ARCH} == armv7 In my case I also see the problem on the pi3, which is arm64. You may want to expand your patch, if you can test it. I will recompile webkit without jit. Will take some hours to complete, so far I've used packages. Thank you very much. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 5 18:33:34 2018 Return-Path: Delivered-To: freebsd-arm@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 971FAF45D14 for ; Mon, 5 Mar 2018 18:33:34 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E918F87D2F for ; Mon, 5 Mar 2018 18:33:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w25IXWiP050434 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 10:33:33 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w25IXW9a050433; Mon, 5 Mar 2018 10:33:32 -0800 (PST) (envelope-from fbsd) Date: Mon, 5 Mar 2018 10:33:32 -0800 From: bob prohaska To: Mike Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180305183331.GB47820@www.zefox.net> References: <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 18:33:34 -0000 On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: > On 3/4/2018 11:57 PM, bob prohaska wrote: > > On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: > >> make -j4 buildworld > >[snip] > > > I tried a buildworld using spinning rust for swap connected via USB" > > ======== > > /usr/bin/make -j3 buildworld > > > [lots of output omitted, can be supplied if needed] [even more output omitted] > > -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include > -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL > -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS > -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" > -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" > -ffunction-sections -fdata-sections -gline-tables-only -MD > -MF.depend.Sema_SemaExprObjC.o -MTSema/SemaExprObjC.o -Qunused-arguments > -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 > -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ > -Wno-c++11-extensions -c > /usr/src/contrib/llvm/tools/clang/lib/Sema/SemaExprObjC.cpp -o > Sema/SemaExprObjC.o > > Killed > *** [all_subdir_lib/clang/libclang] Error code 137 Error 137 was common on my system when USB flash swap was used, but I don't recall seeing it when microSD swap alone was in use and the system ran out of swap > [further snippage] > > > > >From /var/log/messages > > Mar 4 23:32:39 rpi3 kernel: pid 27325 (c++), uid 0, was killed: out of > swap space > Mar 4 23:32:54 rpi3 kernel: pid 27322 (c++), uid 0, was killed: out of > swap space > Mar 4 23:32:54 rpi3 kernel: pid 27387 (c++), uid 0, was killed: out of > swap space > Mar 4 23:32:54 rpi3 kernel: pid 24978 (make), uid 0, was killed: out of > swap space > Mar 4 23:32:54 rpi3 kernel: pid 757 (qmgr), uid 125, was killed: out of > swap space > Make seems to take a while to figure out something's wrong... my system behaves similarly. > > # swapctl -l > Device: 1024-blocks Used: > /dev/md99 1048576 13248 > > ======= > Was swapctl run during the swap shortage, or after? In my observation swap seems to be freed very quickly once make gives up, a few seconds usually. Catching the swap shortage at its peak seems to require either watchful waiting at a top window or more clever logging than I know how to implement. Running gstat into a log file records device activity, which is interesting, but one still has to rake through the log. > > I plan to try again, same hardware but with 2GB swap space. > Please post what you learn... bob prohaska From owner-freebsd-arm@freebsd.org Mon Mar 5 19:50:48 2018 Return-Path: Delivered-To: freebsd-arm@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 A59D8F4AA5E for ; Mon, 5 Mar 2018 19:50:48 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [174.136.99.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41C416ABC7 for ; Mon, 5 Mar 2018 19:50:47 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zw9W46rfHzWCVy for ; Mon, 5 Mar 2018 14:50:40 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520279441; bh=Xcck9AmDoygF956rn8R49gAxG5QCgGlQBgoabl9TZQ0=; h=Subject:Cc:From:Message-ID:Date; b=Chxuhx9jRfwufoMw33Hm+/2wiI+ZNjSA1o5XELiAAyn9nXCHJBT93TNOpOhtRSpV5 vE84L07CwtbBahUJrxIOxivKqWpRHQX6B36RaLGoz8Fkn4/yDdld50c7Swa6faDOn1 vzJhVV4MaDnD4p5gvIPrV5LRTyrn+hAHOt4YPT5HwP2xwrRgdkc1OMKlKijsHQ3stz bkRHfgGTF0CCbwfRZ6Ngl4yzFxRsKRGwW+8DX24cVbFY+GsMNFK+nTQ/zhSdcOf9cp cB5tMNq1WnEX4ED8649Zs/IdZKhM36lbPmj1+xmXWRXEiBM7r9H28lzXuk+3kuhBdg EqH880Ni4NXGg== Received: from [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f] (unknown [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f]) by sentry.24cl.com (Postfix) with ESMTP id 3zw9W36kPDzkB4D for ; Mon, 5 Mar 2018 14:50:39 -0500 (EST) Subject: Re: Is maximum swap usage tunable? Cc: freebsd-arm@freebsd.org References: <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> From: Mike Message-ID: Date: Mon, 5 Mar 2018 14:50:23 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305183331.GB47820@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 19:50:48 -0000 On 3/5/2018 1:33 PM, bob prohaska wrote: > On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: >> On 3/4/2018 11:57 PM, bob prohaska wrote: >>> On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: >>>> make -j4 buildworld >>> [snip] >[snip] >> >> # swapctl -l >> Device: 1024-blocks Used: >> /dev/md99 1048576 13248 >> >> ======= >> > Was swapctl run during the swap shortage, or after? In my observation swap > seems to be freed very quickly once make gives up, a few seconds usually. > Catching the swap shortage at its peak seems to require either watchful > waiting at a top window or more clever logging than I know how to implement. > Running gstat into a log file records device activity, which is interesting, > but one still has to rake through the log. > swapctl was run after the build had stopped. Oh I wish there were an option on swapctl to show min and max swap usage since the last time said stats were reset. :) >> >> I plan to try again, same hardware but with 2GB swap space. >> > Please post what you learn... Yup. It's running now. 2GB swap on USB-connected spinning rust. From owner-freebsd-arm@freebsd.org Mon Mar 5 19:53:27 2018 Return-Path: Delivered-To: freebsd-arm@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 93618F4ADCD for ; Mon, 5 Mar 2018 19:53:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 363436AF13 for ; Mon, 5 Mar 2018 19:53:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7FC74212E6; Mon, 5 Mar 2018 14:53:26 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 05 Mar 2018 14:53:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=1uPrDMJTzomM6IdEPm5R9TiQ42Uoj N0o+94pORfDT4I=; b=Go+wqcsvM2z9sq4EHlxPMH4D9zyuJSLRDN8+a7FEfONjC C/NcNHRdvo4QqjWl8uld/95RcYhHT35MTVMtIBOKPTcStsr1/JH/rtkWJuY+XYyr nzNneR4RwWQIVdGkO9z5EEB3YqCgEGxfLur/609M1GnGxS+w8CZJ9SnJ8Z2cKJ3Z j/Ya6ml5aVLSMzEAvG2LQIFkofjukPyQZcDJn5taiEB78LZP6CAdq4++ryKlR5WW Lj+1yr5GjLmZrPQDcxsSd8cqnOUeyYFyOdM+GayZiJabY1pH3V2hxFbVIF7OBE3z Zag8SQhZCfD5pWt5d6TtYIIqSvfvVVZGa/m4HB7pA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=1uPrDM JTzomM6IdEPm5R9TiQ42UojN0o+94pORfDT4I=; b=jsn3eFsQB+plWl9lovFLDw MtPjhsIN9eAJKH6QpN1IPpS2lJAp0Iztf8nyPL/KJ2PbqxpnCXaoP8x+7qKc1Hck vY5NsvG2a/f+GhMpOlXBh+Zzk58pHCWhldLwAYkoeuuhTgm5s+ktEQM3ZFofHz8B jXRTYrRSvAIzL4C2hq+QREubAY0WYJyCaFi2rOJbB11hh/pL4AHmsWpDmQR7xjMY WfZgY50YHhHyLmX+779Nh6wJKzy7TR27vqWLqzoPcESMpavP3wcJ0XA1CefRr1l6 ZchnWW9vSDOWiu1s2bZjTVuMg/G6UL8kYvB5M02YojwysFV96iewI/RfzhXpYUYA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A9A68244F9; Mon, 5 Mar 2018 14:53:25 -0500 (EST) Subject: Re: growfs problem on current To: freebsd-arm@freebsd.org References: <20180305171128.GI31939@cicely7.cicely.de> From: tech-lists Cc: ticso@cicely.de Message-ID: Date: Mon, 5 Mar 2018 19:53:12 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305171128.GI31939@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 19:53:27 -0000 On 05/03/2018 17:11, Bernd Walter wrote: > Not sure if this is stricly current, but so far I could see this > problem with current only. > The filesystem expands and everything seems to be fine. > But in fact the filesystem is broken and fails in a way, which can't > be solved by fsck anymore. > Somehow it tries to access data not reachable. > I havn't had the time to investigate it further. > Don't know if something in the partition tables or the filesystem is > wrong. > As a workaround I always expand the FS on my stable running desktop > before booting on the ARM. Not noticed any issue. I built arm6 for rpi2 just yesterday. From these sources: $ svnlite info fbsd-12-src/ Path: fbsd-12-src Working Copy Root Path: /root/crochet/fbsd-12-src URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 330287 Node Kind: directory Schedule: normal Last Changed Author: kevans Last Changed Rev: 330287 Last Changed Date: 2018-03-02 17:07:08 +0000 (Fri, 02 Mar 2018) The built image: -rw-r--r-- 1 root wheel 7.3G 4 Mar 23:31 FreeBSD-armv6-12-GENERIC-NODEBUG-RaspberryPi2.img written to a 32GB card: Filesystem Size Used Avail Capacity Mounted on /dev/mmcsd0s2a 28G 3.0G 23G 11% / devfs 1.0K 1.0K 0B 100% /dev /dev/mmcsd0s1 50M 8.7M 41M 17% /boot/msdos /dev/md1 14M 88K 13M 1% /var/log /dev/md2 11M 12K 10M 0% /var/tmp /dev/md3 242M 8.0K 222M 0% /tmp uname from installed system: FreeBSD 12.0-CURRENT (GENERIC-NODEBUG) #0 f2f8a36(master): Sun Mar 4 23:30:06 GMT 2018 this is in /etc/rc.conf: growfs_enable="YES" I'm not seeing any errors at all. What errors are you getting that make you think it's the filesystem, and what sources (revision) did you build from, and what method did you use to build? I used freebsd/crochet. -- J. From owner-freebsd-arm@freebsd.org Mon Mar 5 20:49:05 2018 Return-Path: Delivered-To: freebsd-arm@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 20E10F277DC for ; Mon, 5 Mar 2018 20:49:05 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A03EE6D4DA for ; Mon, 5 Mar 2018 20:49:04 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w25Kn0rH028980 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 21:49:00 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w25Kmvw4043238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 5 Mar 2018 21:48:57 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w25KmvHS066191 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 21:48:57 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w25Kmvka066190; Mon, 5 Mar 2018 21:48:57 +0100 (CET) (envelope-from ticso) Date: Mon, 5 Mar 2018 21:48:57 +0100 From: Bernd Walter To: tech-lists Cc: freebsd-arm@freebsd.org, ticso@cicely.de Subject: Re: growfs problem on current Message-ID: <20180305204857.GK31939@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180305171128.GI31939@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 20:49:05 -0000 On Mon, Mar 05, 2018 at 07:53:12PM +0000, tech-lists wrote: > On 05/03/2018 17:11, Bernd Walter wrote: > > Not sure if this is stricly current, but so far I could see this > > problem with current only. > > The filesystem expands and everything seems to be fine. > > But in fact the filesystem is broken and fails in a way, which can't > > be solved by fsck anymore. > > Somehow it tries to access data not reachable. > > I havn't had the time to investigate it further. > > Don't know if something in the partition tables or the filesystem is > > wrong. > > As a workaround I always expand the FS on my stable running desktop > > before booting on the ARM. > > Not noticed any issue. I built arm6 for rpi2 just yesterday. From these > sources: > > $ svnlite info fbsd-12-src/ > Path: fbsd-12-src > Working Copy Root Path: /root/crochet/fbsd-12-src > URL: https://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 330287 > Node Kind: directory > Schedule: normal > Last Changed Author: kevans > Last Changed Rev: 330287 > Last Changed Date: 2018-03-02 17:07:08 +0000 (Fri, 02 Mar 2018) > > The built image: > > -rw-r--r-- 1 root wheel 7.3G 4 Mar 23:31 > FreeBSD-armv6-12-GENERIC-NODEBUG-RaspberryPi2.img > > written to a 32GB card: > > Filesystem Size Used Avail Capacity Mounted on > /dev/mmcsd0s2a 28G 3.0G 23G 11% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/mmcsd0s1 50M 8.7M 41M 17% /boot/msdos > /dev/md1 14M 88K 13M 1% /var/log > /dev/md2 11M 12K 10M 0% /var/tmp > /dev/md3 242M 8.0K 222M 0% /tmp > > uname from installed system: > > FreeBSD 12.0-CURRENT (GENERIC-NODEBUG) #0 f2f8a36(master): Sun Mar 4 > 23:30:06 GMT 2018 > > this is in /etc/rc.conf: > > growfs_enable="YES" > > I'm not seeing any errors at all. > > What errors are you getting that make you think it's the filesystem, and > what sources (revision) did you build from, and what method did you use > to build? I used freebsd/crochet. I've used countless prebuild current images. The last one was this: FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180226-r330034.img.xz In that case everything seemed to be ok. I've installed countless packages, including X. Then I needed to preload a specific kernel module, so I've created a /boot/loader.conf The loader complained that the file is unreadable. Otherwise the system booted ok and I could access the file without problems. After removing the file everything was fine again. The I've added my lines to /boot/defaults/loader.conf and the loader complained about this file. After booting I could access the file without problems. Removing those lines didn't avoid the problem with loader. Then I've removed the card from the machine and did an fsck from desktop, which spit some read errors on reading blocks. I wasn't physical read error from a failing card, just an out of scope block number. I don't have the exact output anymore. In a previous case I've had a filesystem panic and fsck failed. Maybe it is something specific on the way the official images are build to trigger this problem. I've seen this problem with different cards, different boards, over several weeks of current images and with armv7 as well as arm64. Not a single system survived when the system increased the FS itself. I know I should have more data about this and should have done more low level tests. I didn't expect that I'm the only one having problems with this. Will do some tests with a self grown FS directly after it has been increased. So far I'd only seen the corruption after some heavy writes. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 5 21:12:33 2018 Return-Path: Delivered-To: freebsd-arm@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 141CBF2A5BD for ; Mon, 5 Mar 2018 21:12:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BBE936E705 for ; Mon, 5 Mar 2018 21:12:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w25LB0ZJ050819 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Mar 2018 13:11:03 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w25LAn44050806; Mon, 5 Mar 2018 13:10:49 -0800 (PST) (envelope-from fbsd) Date: Mon, 5 Mar 2018 13:10:28 -0800 From: bob prohaska To: ticso@cicely.de Cc: Mika?l Urankar , freebsd-arm@freebsd.org, Bernd Walter , bob prohaska Subject: Re: Webbrowser Message-ID: <20180305211028.GA50528@www.zefox.net> References: <20180305165934.GH31939@cicely7.cicely.de> <20180305173240.GJ31939@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180305173240.GJ31939@cicely7.cicely.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 21:12:33 -0000 On Mon, Mar 05, 2018 at 06:32:40PM +0100, Bernd Walter wrote: > On Mon, Mar 05, 2018 at 06:18:09PM +0100, Mika?l Urankar wrote: > > Le 5 mars 2018 18:00, "Bernd Walter" a ?crit : > > > > It seems that there is not useable webbrowser for arm. > > I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. > > The only brwosers I got running is billo and midori. > > The first one is practically unuseable these days and midori always > > crashes when the javascript engine starts. > > With javascript disabled midori runs fine, but I need JS. > > Did anyone already spend some time debugging this issue? > > > > > > The jit in webkit is broken on armv6/7, you need to recompile it with this > > configure flag: --disable-jit > > I created a PR for firefox-esr: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225279 > > Ok - this is a patch to get the JIT running in firefox? > A quick look showed that you do ${ARCH} == armv6 || ${ARCH} == armv7 > In my case I also see the problem on the pi3, which is arm64. > You may want to expand your patch, if you can test it. > Firefox-esr compiled on a Pi2 a couple of months ago, I don't recall having to do anything special. Neiher have I tested it extensively, but it works to some extent. One thing I _haven't_ tested is sound. hth, bob prohaska From owner-freebsd-arm@freebsd.org Tue Mar 6 05:47:05 2018 Return-Path: Delivered-To: freebsd-arm@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 E6386F2EE10 for ; Tue, 6 Mar 2018 05:47:04 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from mailssl03.asahi-net.or.jp (mailssl03.asahi-net.or.jp [202.224.55.62]) by mx1.freebsd.org (Postfix) with ESMTP id 6AFC583261 for ; Tue, 6 Mar 2018 05:47:03 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) (Authenticated sender: WJ8S-YMMT) by mailssl03.asahi-net.or.jp (Postfix) with ESMTPSA id ABEAE4005E; Tue, 6 Mar 2018 14:40:17 +0900 (JST) Date: Tue, 06 Mar 2018 14:38:22 +0900 (JST) Message-Id: <20180306.143821.1832586840341832816.shigeru@os-hackers.jp> To: tech-lists@zyxst.net Cc: freebsd-arm@freebsd.org Subject: Re: rpi2/zfs From: YAMAMOTO Shigeru In-Reply-To: <2427949f-c76d-3d04-e379-3f398110fff1@zyxst.net> References: <2427949f-c76d-3d04-e379-3f398110fff1@zyxst.net> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 05:47:05 -0000 Hi, all, >>>>> "tech-lists" == tech-lists writes: tech-lists> Hi, Has anyone tried running the rpi2 with zfs (an attached hard tech-lists> drive the thing having zfs filesystem)? I'd imagine it'd be slow tech-lists> but is it usable? Within expectations? I tryed to work ZFS on RaspberryPi2 about 2 years ago. https://twitter.com/BsdHacker/status/715181264391655424 ZFS on RaspberryPi2 is work, but it is slow, and NOT STABLE! It is stop by assertion at zrl_destory(). https://github.com/bsd-hacker/freebsd/blob/master/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zrlock.c#L65 Currently, I can't fix it. and a ZFS on RaspberryPi2 environment is not running because it's filesystem broken. I need to create a new ZFS file system to test. Thanks, --- YAMAMOTO Shigeru From owner-freebsd-arm@freebsd.org Tue Mar 6 10:01:34 2018 Return-Path: Delivered-To: freebsd-arm@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 3522CF45E01 for ; Tue, 6 Mar 2018 10:01:34 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A53E26E074 for ; Tue, 6 Mar 2018 10:01:33 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w26A1SgN043471 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Mar 2018 11:01:29 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w26A1M1B059121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Mar 2018 11:01:22 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w26A1Ld7070429 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Mar 2018 11:01:21 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w26A1LXB070428; Tue, 6 Mar 2018 11:01:21 +0100 (CET) (envelope-from ticso) Date: Tue, 6 Mar 2018 11:01:21 +0100 From: Bernd Walter To: =?iso-8859-1?Q?Mika=EBl?= Urankar Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: Webbrowser Message-ID: <20180306100121.GM31939@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180305165934.GH31939@cicely7.cicely.de> <20180305173240.GJ31939@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180305173240.GJ31939@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 10:01:34 -0000 On Mon, Mar 05, 2018 at 06:32:40PM +0100, Bernd Walter wrote: > On Mon, Mar 05, 2018 at 06:18:09PM +0100, Mikaël Urankar wrote: > > Le 5 mars 2018 18:00, "Bernd Walter" a écrit : > > > > It seems that there is not useable webbrowser for arm. > > I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. > > The only brwosers I got running is billo and midori. > > The first one is practically unuseable these days and midori always > > crashes when the javascript engine starts. > > With javascript disabled midori runs fine, but I need JS. > > Did anyone already spend some time debugging this issue? > > > > > > The jit in webkit is broken on armv6/7, you need to recompile it with this > > configure flag: --disable-jit > > I created a PR for firefox-esr: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225279 > > Ok - this is a patch to get the JIT running in firefox? > A quick look showed that you do ${ARCH} == armv6 || ${ARCH} == armv7 > In my case I also see the problem on the pi3, which is arm64. > You may want to expand your patch, if you can test it. > > I will recompile webkit without jit. > Will take some hours to complete, so far I've used packages. Cool - that helped. Midori is now running with JS enabled. > Thank you very much. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Tue Mar 6 10:04:48 2018 Return-Path: Delivered-To: freebsd-arm@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 32895F46185 for ; Tue, 6 Mar 2018 10:04:48 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (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 A564D6E38C for ; Tue, 6 Mar 2018 10:04:47 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: by mail-pg0-x22d.google.com with SMTP id r26so8069801pgv.13 for ; Tue, 06 Mar 2018 02:04:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TUqgY7z69BEmWmOHkfvvBaDsT4WgoIbFAeBWcI+BUAs=; b=WMPWHbS29Epo5uYkOr2qIyM4FfBf4Qpg/zhv00QhBKISmWHKRUxh0Y+ubNFiPA+vXx zmDfCzQJmjpfuE+fT5q4W8DpASMOem1GDsTm0mOLb1FFyZ6UaNWJocoZpF8gEKckmxuD jYjzP3DOZtMIJ+jVAOnkPuV72MjwY3JhoPi2MmgyerfHI7fikfDAU0Pji26MPUgRUjQa LAevnwPa7Dpi3dtXBIlb2QJaDnzOxao5fQ32Yf8/b+825WWfQhlddR/NlWpjCKRGtfem mTHZ6TRyYzj6tg3lWZDBv59IkxG/eGx/oIiJ+IPQyHRVtAyOLRzPpnU5FF1P9E2fz5lV 5Uuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TUqgY7z69BEmWmOHkfvvBaDsT4WgoIbFAeBWcI+BUAs=; b=pY1IqNnfW3ED4mJRWEQo6bbES8NjdM+e++uj1wvQPPGIR1JA992/fptsiMoZZa2oIE fmUdr0v3FIkWoE8IRLwGWfuhq9y/sZxWTCUhAHzgUQKjC6GD4ctVKXgbTy9t0TlHaNtv psZ/xoNQBTM8alQHglEhljepBQYXzdwW7mvGKBucOVJptw9homuU32lg/Fl1wuJAMH/o La/gh5MqWfUGhlEpvoPqHHQuzgazcLBS1wIK6jLxAEOWgTwU44O1HXxBv7Zwaas2dV0t 0F7tzuDdhHNZKhcA7TfAmvhDuaTypIwKnf3snc2V6g0YuyA4oVjfdjcLxoj0pvDc4l73 LZsQ== X-Gm-Message-State: APf1xPAzgCuTexW/+So3e4b+9j2mSni8wf8Kg9xmP57Pi/hgpdx5NMWu Qs8m8ZNk+awfE/infPMqcqKMUVLHGA7lkuNentgg/EiC X-Google-Smtp-Source: AG47ELu+a2tIVgOCbp5lRhIA2rdhBVPz+jgSPShKMoEffgoAkJmqXJXogAWMs1UCCBIYUjpye3rS3PeLFsTtrQFuxYo= X-Received: by 10.101.97.139 with SMTP id c11mr13942583pgv.431.1520330686550; Tue, 06 Mar 2018 02:04:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.132.9 with HTTP; Tue, 6 Mar 2018 02:04:06 -0800 (PST) In-Reply-To: <20180306100121.GM31939@cicely7.cicely.de> References: <20180305165934.GH31939@cicely7.cicely.de> <20180305173240.GJ31939@cicely7.cicely.de> <20180306100121.GM31939@cicely7.cicely.de> From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Date: Tue, 6 Mar 2018 11:04:06 +0100 Message-ID: Subject: Re: Webbrowser To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, Bernd Walter Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 10:04:48 -0000 2018-03-06 11:01 GMT+01:00 Bernd Walter : > On Mon, Mar 05, 2018 at 06:32:40PM +0100, Bernd Walter wrote: > > On Mon, Mar 05, 2018 at 06:18:09PM +0100, Mika=C3=ABl Urankar wrote: > > > Le 5 mars 2018 18:00, "Bernd Walter" a > =C3=A9crit : > > > > > > It seems that there is not useable webbrowser for arm. > > > I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. > > > The only brwosers I got running is billo and midori. > > > The first one is practically unuseable these days and midori always > > > crashes when the javascript engine starts. > > > With javascript disabled midori runs fine, but I need JS. > > > Did anyone already spend some time debugging this issue? > > > > > > > > > The jit in webkit is broken on armv6/7, you need to recompile it with > this > > > configure flag: --disable-jit > > > I created a PR for firefox-esr: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225279 > > > > Ok - this is a patch to get the JIT running in firefox? > > A quick look showed that you do ${ARCH} =3D=3D armv6 || ${ARCH} =3D=3D = armv7 > > In my case I also see the problem on the pi3, which is arm64. > > You may want to expand your patch, if you can test it. > > > > I will recompile webkit without jit. > > Will take some hours to complete, so far I've used packages. > > Cool - that helped. > Midori is now running with JS enabled. Would you mind creating a PR for this issue? FYI firefox-esr builds fine on aarch64, http://thunderx1.nyi.freebsd.org/data/head-arm64-default/p461032_s328914/lo= gs/firefox-esr-52.6.0_3,1.log From owner-freebsd-arm@freebsd.org Tue Mar 6 17:37:39 2018 Return-Path: Delivered-To: freebsd-arm@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 AAFF9F45586 for ; Tue, 6 Mar 2018 17:37:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24322818B1; Tue, 6 Mar 2018 17:37:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w26HbUBQ053847 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Mar 2018 09:37:31 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w26HbTkE053846; Tue, 6 Mar 2018 09:37:29 -0800 (PST) (envelope-from fbsd) Date: Tue, 6 Mar 2018 09:37:29 -0800 From: bob prohaska To: Warner Losh Cc: Ian Lepore , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180306173729.GA51223@www.zefox.net> References: <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 17:37:40 -0000 On Sun, Mar 04, 2018 at 10:30:17PM -0700, Warner Losh wrote: > > I'd look at power. And add more swap. > Both have now been done. Voltage at the GPIO header is 5.01-5.04, idle all the way up to make -j4 buildworld. Swap was increased to 3 GB in two partitions on the microSD, with the usb-flash partition turned off for now. As make -j4 buildworld's logfile approached the 1.6 MB mark, I started gstat -a -d -B -I 1s > j4_3Gswap2_gstat.log and began watching the top display. Pretty soon, swap usage began to rise, peaking a little over 700 MB. Idle time remained low, no swread or pfault states were observed in top. Here's a snippet of gstat output from about this time: dT: 1.003s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 7 878 235 2213 9.9 643 3808 6.2 0 0 0.0 100.0 mmcsd0 7 878 235 2213 9.9 643 3808 6.2 0 0 0.0 100.0 mmcsd0s3 5 444 125 1228 9.6 319 1898 6.2 0 0 0.0 100.1 mmcsd0s3b 2 435 111 985 10.3 324 1910 6.1 0 0 0.0 99.8 mmcsd0s3d Perhaps an hour later the swap usage again rose, to somewhere around 500 MB, but swread and pfault began to appear in the top window's state column, and the idle time approached 50%, occasionally exceeding it. It's hard to locate the spot in the gstat output corresponding, but I think this is representative: dT: 1.006s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 6 240 22 219 11.5 218 2795 13.2 0 0 0.0 88.9 mmcsd0 6 240 22 219 11.5 218 2795 13.6 0 0 0.0 90.2 mmcsd0s3 3 123 15 179 10.3 108 1380 16.3 0 0 0.0 91.4 mmcsd0s3b 3 116 7 40 14.3 109 1416 11.9 0 0 0.0 68.7 mmcsd0s3d The machine got over this hump too, and is still running as I write. The log file is up to ~15MB, in the "building libraries" stage. It's curious that the initial burst of swap use seems to be handled more gracefully than the later, smaller, flurry of activity. Moreover, both are far below the 3GB swap limit of the partitions active. There is no warning from the kernel about too much swap space being allocated. Nor are there any "indefinite wait..." messages on the console. As an aside, the write speed of 2.8 MB/sec for the microSD card corresponds fairly well with the claimed 4k random write speed of 2.2 MB/sec for SanDisk Extreme flash memory. I'm not sure how this compares to a mechanical hard disk, but it _used_ to be ok. I note in passing that r330367 armv7 on a Pi2 also halts a make -j4 buildworld with 2GB of USB-hosted swap available. A previous revision, a couple of weeks older, ran to completion with the same configuration. Thanks for reading, if anybody can suggest more informative tests please do. Buildworld is a very clumsy stress test, Peter Holm's stress2 didn't compile the last time I tried it, many months ago. bob prohaska From owner-freebsd-arm@freebsd.org Tue Mar 6 18:03:26 2018 Return-Path: Delivered-To: freebsd-arm@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 A587BF46F6A for ; Tue, 6 Mar 2018 18:03:26 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1150A827BC; Tue, 6 Mar 2018 18:03:25 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w26I3LMM050010; Tue, 6 Mar 2018 10:03:21 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w26I3Lif050009; Tue, 6 Mar 2018 10:03:21 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803061803.w26I3Lif050009@pdx.rh.CN85.dnsmgr.net> Subject: Re: Is maximum swap usage tunable? In-Reply-To: <20180306173729.GA51223@www.zefox.net> To: bob prohaska Date: Tue, 6 Mar 2018 10:03:21 -0800 (PST) CC: Warner Losh , "freebsd-arm@freebsd.org" , Ian Lepore X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 18:03:26 -0000 > On Sun, Mar 04, 2018 at 10:30:17PM -0700, Warner Losh wrote: > > > > I'd look at power. And add more swap. > > > > Both have now been done. Voltage at the GPIO header is 5.01-5.04, > idle all the way up to make -j4 buildworld. What are you using to measure the power with? The average DMM is not going to see the rapid pulses of noise that increase with current consumption that can lead to "odd behavior". You need a good and fairly fast scope to truely rule this out. Also the GPIO header is a good electrical distance from the SOC and much of the noise would be filtered out before then. But atleast you have confirmed your not sagging VCC down to 4.75 or 4.5 as I have seen on some of the power power bricks used to run *Pi*'s with. It would probably be benificial if someone could duplicate to a reasonable degree your failure mode, this would make a hardware related problem less likely as the cause. > > Swap was increased to 3 GB in two partitions on the microSD, with > the usb-flash partition turned off for now. ... Axe applied for brief reply ... -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Tue Mar 6 18:27:33 2018 Return-Path: Delivered-To: freebsd-arm@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 F374DF48E46 for ; Tue, 6 Mar 2018 18:27:32 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [IPv6:2607:f2f8:af30::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C07883AFA for ; Tue, 6 Mar 2018 18:27:32 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zwlcf1SvHzWCW2 for ; Tue, 6 Mar 2018 13:27:30 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520360850; bh=4KFKK4KTqEi65QcJBf8+gwRgxg+JzLyvURQxxJtmbZY=; h=Subject:Cc:From:Message-ID:Date; b=pb5sDKE0knEvjm5iRU1Vi4C+bqMACfdNOW617foP2z7Q2qdoeS1PoF7amwFWq7CJP ggP2PAflSWRRIjrD3z42kCbNlX11ZXZPL6am/TE4EY9jSgn+mUoBegM21LdQ5xfq4e RhsQzaDjjYZrLTeZzEkMzTDMBWUd+67nDLejVDSt+Z+RTR7eaq22SLmpd0bB7w1kVN wO+1jrCZ5yaSEraAJ2tmKAuzGu2H5DakRg7FRx2PhvanFHE1gy2vuCKN5fpND977f8 0os0K+06cJZs6vqQy6TSTZSBLBgvM4hoLkPpN2g47wgpnGPZR4W3/GTXBzVN9hiw/+ 8v9XfA3gHj9tg== Received: from [IPv6:fdcf:b715:2f4d:1:8cce:939f:8e2a:c719] (unknown [IPv6:fdcf:b715:2f4d:1:8cce:939f:8e2a:c719]) by sentry.24cl.com (Postfix) with ESMTP id 3zwlcd17FfzkB4D for ; Tue, 6 Mar 2018 13:27:29 -0500 (EST) Subject: Re: Is maximum swap usage tunable? Cc: freebsd-arm@freebsd.org References: <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> From: Mike Message-ID: <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> Date: Tue, 6 Mar 2018 13:27:10 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305183331.GB47820@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 18:27:33 -0000 On 3/5/2018 1:33 PM, bob prohaska wrote: > On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: >[snip] >> I plan to try again, same hardware but with 2GB swap space. >> > Please post what you learn... The compile stopped in the middle of build-worls. Here are the last things in the build log: === --- CodeGen/CGDebugInfo.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.CodeGen_CGDebugInfo.o -MTCodeGen/CGDebugInfo.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp -o CodeGen/CGDebugInfo.o --- CodeGen/CGDecl.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.CodeGen_CGDecl.o -MTCodeGen/CGDecl.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGDecl.cpp -o CodeGen/CGDecl.o === The Pi3 was hung. No response to keyboard or ssh. There were some messages in what appeared to be a looping scroll on the console. I was able to get a fuzzy pic, here: https://archive.mgm51.com/fbsd-build.jpg /var/log/messages had nothing odd except for: ===== Mar 5 11:18:16 rpi3 login: ROOT LOGIN (root) ON ttyv0 Mar 5 11:19:03 rpi3 kernel: lock order reversal: Mar 5 11:19:03 rpi3 kernel: 1st 0xffff000040937360 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3735 Mar 5 11:19:03 rpi3 kernel: 2nd 0xfffffd00018f0000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:289 Mar 5 11:19:03 rpi3 kernel: stack backtrace: Mar 5 11:19:03 rpi3 kernel: #0 0xffff0000003b59d8 at witness_debugger+0x64 Mar 5 11:19:03 rpi3 kernel: #1 0xffff00000035cc30 at _sx_xlock+0x7c Mar 5 11:19:03 rpi3 kernel: #2 0xffff0000005cd5e0 at ufsdirhash_remove+0x38 Mar 5 11:19:03 rpi3 kernel: #3 0xffff0000005d03ec at ufs_dirremove+0x124 Mar 5 11:19:03 rpi3 kernel: #4 0xffff0000005d7700 at ufs_rmdir+0x114 Mar 5 11:19:03 rpi3 kernel: #5 0xffff00000067b528 at VOP_RMDIR_APV+0xac Mar 5 11:19:03 rpi3 kernel: #6 0xffff0000004210b0 at kern_rmdirat+0x16c Mar 5 11:19:03 rpi3 kernel: #7 0xffff00000064d59c at do_el0_sync+0x8bc Mar 5 11:19:03 rpi3 kernel: #8 0xffff0000006349f4 at handle_el0_sync+0x74 Mar 5 11:37:36 rpi3 kernel: lock order reversal: Mar 5 11:37:36 rpi3 kernel: 1st 0xffff0000408228f8 bufwait (bufwait) @ /usr/src/sys/vm/vm_pager.c:374 Mar 5 11:37:36 rpi3 kernel: 2nd 0xfffffd0001c119c8 ufs (ufs) @ /usr/src/sys/dev/md/md.c:952 Mar 5 11:37:36 rpi3 kernel: stack backtrace: Mar 5 11:37:36 rpi3 kernel: #0 0xffff0000003b59d8 at witness_debugger+0x64 Mar 5 11:37:36 rpi3 kernel: #1 0xffff00000032bcbc at __lockmgr_args+0x6ac Mar 5 11:37:36 rpi3 kernel: #2 0xffff0000005c8864 at ffs_lock+0x88 Mar 5 11:37:36 rpi3 kernel: #3 0xffff00000067bf18 at VOP_LOCK1_APV+0xac Mar 5 11:37:36 rpi3 kernel: #4 0xffff000000426fac at _vn_lock+0x64 Mar 5 11:37:36 rpi3 kernel: #5 0xffff000000173fd0 at mdstart_vnode+0x398 Mar 5 11:37:36 rpi3 kernel: #6 0xffff0000001729d4 at md_kthread+0x1bc Mar 5 11:37:36 rpi3 kernel: #7 0xffff00000031807c at fork_exit+0x7c ====== The entries before 11:37 were during boot-up. The 11:37 entries were around the time the RPi3 hung. Oh yeah... # uname -a FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r330034: Mon Feb 26 22:51:01 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 Note sure how to show the version of source it was building, suggestions? fwiw, and YMMV. Hope this helps. From owner-freebsd-arm@freebsd.org Tue Mar 6 19:01:40 2018 Return-Path: Delivered-To: freebsd-arm@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 AE752F4B21C for ; Tue, 6 Mar 2018 19:01:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 29E99850D7; Tue, 6 Mar 2018 19:01:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w26J1aXp054069 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Mar 2018 11:01:37 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w26J1ZH0054068; Tue, 6 Mar 2018 11:01:35 -0800 (PST) (envelope-from fbsd) Date: Tue, 6 Mar 2018 11:01:35 -0800 From: bob prohaska To: "Rodney W. Grimes" Cc: Warner Losh , "freebsd-arm@freebsd.org" , Ian Lepore , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180306190135.GB51223@www.zefox.net> References: <20180306173729.GA51223@www.zefox.net> <201803061803.w26I3Lif050009@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201803061803.w26I3Lif050009@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 19:01:40 -0000 On Tue, Mar 06, 2018 at 10:03:21AM -0800, Rodney W. Grimes wrote: > > What are you using to measure the power with? > The average DMM is not going to see the rapid pulses of > noise that increase with current consumption that can > lead to "odd behavior". You need a good and fairly > fast scope to truely rule this out. Alas, no scope, just a DVM. But, there are four other RPis on the same outlet strip, three running 11-stable are trouble free, the fourth only started running out of swap with the latest revision of -current.. > > Also the GPIO header is a good electrical distance > from the SOC and much of the noise would be filtered > out before then. That would qualify as a hardware failure, but what could cause it, and why only after recent upgrades to the sources? > > But atleast you have confirmed your not sagging VCC down > to 4.75 or 4.5 as I have seen on some of the power power > bricks used to run *Pi*'s with. > > It would probably be benificial if someone could duplicate > to a reasonable degree your failure mode, this would make > a hardware related problem less likely as the cause. > I think that might be coming, what with Mike's lastest report in this thread. Could the new thread Re: Strange ARC/Swap/CPU be related? I haven't been watching wired memory, on the Pi3 it's at 160MB about ten hours into buildworld. Idle time is zero, swap usage is at 51MB with essentially no activity. If there are other things to check please tell me. Are there any explict swap performance tests that react quicker than make buildworld? Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Tue Mar 6 19:14:01 2018 Return-Path: Delivered-To: freebsd-arm@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 2F9B3F24005 for ; Tue, 6 Mar 2018 19:14:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8060D85C50 for ; Tue, 6 Mar 2018 19:14:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w26JE0U3054099 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Mar 2018 11:14:01 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w26JDxnA054098; Tue, 6 Mar 2018 11:13:59 -0800 (PST) (envelope-from fbsd) Date: Tue, 6 Mar 2018 11:13:59 -0800 From: bob prohaska To: Mike Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180306191359.GC51223@www.zefox.net> References: <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 19:14:01 -0000 On Tue, Mar 06, 2018 at 01:27:10PM -0500, Mike wrote: > On 3/5/2018 1:33 PM, bob prohaska wrote: > > On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: > >[snip] > >> I plan to try again, same hardware but with 2GB swap space. > >> > > Please post what you learn... > > The compile stopped in the middle of build-worls. Here are the last > things in the build log: [snip] > > How big did the build log get? Mine usually stop a little shy of 2 MB, with troubles appearing after around 1.6 MB. > > The Pi3 was hung. No response to keyboard or ssh. > > There were some messages in what appeared to be a looping scroll on the > console. I was able to get a fuzzy pic, here: > https://archive.mgm51.com/fbsd-build.jpg Never seen that on my machines, it looks like a kernel panic. > > > /var/log/messages had nothing odd except for: > > ===== > [snippage] > > ====== > > The entries before 11:37 were during boot-up. The 11:37 entries were > around the time the RPi3 hung. Looks normal, if not good, to me. > > > Oh yeah... > > # uname -a > FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r330034: Mon Feb 26 > 22:51:01 UTC 2018 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC > arm64 > > Note sure how to show the version of source it was building, suggestions? > svnlite info /usr/src will give the source revision. hth, and thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Tue Mar 6 19:28:24 2018 Return-Path: Delivered-To: freebsd-arm@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 0EE2DF263F8 for ; Tue, 6 Mar 2018 19:28:24 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EEEA864B1; Tue, 6 Mar 2018 19:28:23 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w26JSJU4050296; Tue, 6 Mar 2018 11:28:19 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w26JSHmQ050295; Tue, 6 Mar 2018 11:28:17 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803061928.w26JSHmQ050295@pdx.rh.CN85.dnsmgr.net> Subject: Re: Is maximum swap usage tunable? In-Reply-To: <20180306190135.GB51223@www.zefox.net> To: bob prohaska Date: Tue, 6 Mar 2018 11:28:17 -0800 (PST) CC: "freebsd-arm@freebsd.org" , Ian Lepore X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 19:28:24 -0000 > On Tue, Mar 06, 2018 at 10:03:21AM -0800, Rodney W. Grimes wrote: > > > > What are you using to measure the power with? > > The average DMM is not going to see the rapid pulses of > > noise that increase with current consumption that can > > lead to "odd behavior". You need a good and fairly > > fast scope to truely rule this out. > > Alas, no scope, just a DVM. But, there are four other RPis on > the same outlet strip, three running 11-stable are trouble free, > the fourth only started running out of swap with the latest revision > of -current.. THey are running this same work load too? It does not sound like they are all running the same code? Three on 11-stable, one on ? > > Also the GPIO header is a good electrical distance > > from the SOC and much of the noise would be filtered > > out before then. > That would qualify as a hardware failure, but what could > cause it, and why only after recent upgrades to the sources? Marginal hardware can have very slight tickle points, especially when it comes to noise on power, or an ever so slightly slow component. At 1Ghz+ frequencies it does not take much of a slight power supply noise change to go from a working siutaion to a not working. A software change can cause a change in the amount of nose generated. > > But atleast you have confirmed your not sagging VCC down > > to 4.75 or 4.5 as I have seen on some of the power power > > bricks used to run *Pi*'s with. > > > > It would probably be benificial if someone could duplicate > > to a reasonable degree your failure mode, this would make > > a hardware related problem less likely as the cause. > > > > I think that might be coming, what with Mike's lastest report in > this thread. Could the new thread Re: Strange ARC/Swap/CPU be > related? I haven't been watching wired memory, on the Pi3 it's > at 160MB about ten hours into buildworld. Idle time is zero, > swap usage is at 51MB with essentially no activity. If there are > other things to check please tell me. Are there any explict swap > performance tests that react quicker than make buildworld? Watch the output of the command I posted in the other thread, vmstat -z | egrep 'ITEM|g_bio|UMA' There was a known g_bio leak. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Tue Mar 6 20:20:27 2018 Return-Path: Delivered-To: freebsd-arm@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 A8198F2B6BC for ; Tue, 6 Mar 2018 20:20:27 +0000 (UTC) (envelope-from hondareyte.luc@laposte.net) Received: from smtp.laposte.net (smtpoutz26.laposte.net [194.117.213.101]) (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 3D2826876C for ; Tue, 6 Mar 2018 20:20:26 +0000 (UTC) (envelope-from hondareyte.luc@laposte.net) Received: from smtp.laposte.net (localhost [127.0.0.1]) by lpn-prd-vrout014 (Postfix) with ESMTP id 85C12122891 for ; Tue, 6 Mar 2018 20:59:37 +0100 (CET) Received: from smtp.laposte.net (localhost [127.0.0.1]) by lpn-prd-vrout014 (Postfix) with ESMTP id 780B912289E for ; Tue, 6 Mar 2018 20:59:37 +0100 (CET) Received: from lpn-prd-vrin002 (lpn-prd-vrin002.laposte [10.128.63.3]) by lpn-prd-vrout014 (Postfix) with ESMTP id 73909122891 for ; Tue, 6 Mar 2018 20:59:37 +0100 (CET) Received: from lpn-prd-vrin002 (localhost [127.0.0.1]) by lpn-prd-vrin002 (Postfix) with ESMTP id 63CE95C3703 for ; Tue, 6 Mar 2018 20:59:37 +0100 (CET) Received: from Hibiscus.local (unknown [88.190.12.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lpn-prd-vrin002 (Postfix) with ESMTPSA id 3C5B85C36D9 for ; Tue, 6 Mar 2018 20:59:37 +0100 (CET) To: freebsd-arm@freebsd.org From: Luc Hondareyte Subject: cpufreq support on Allwinner H3 Message-ID: <5332936b-f38b-ca7a-03d9-dfc7c92e2727@laposte.net> Date: Tue, 6 Mar 2018 20:59:37 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr X-VR-FullState: 0 X-VR-Score: 0 X-VR-Cause-1: gggruggvucftvghtrhhoucdtuddrgedtfedrjeelgddufeduucetufdoteggodetrfdotffvucfrrhho X-VR-Cause-2: fhhilhgvmecunfetrffquffvgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpefvhffukfff X-VR-Cause-3: fgggtgfgsehtkeertddtfeejnecuhfhrohhmpefnuhgtucfjohhnuggrrhgvhihtvgcuoehhohhnuggr X-VR-Cause-4: rhgvhihtvgdrlhhutgeslhgrphhoshhtvgdrnhgvtheqnecukfhppeekkedrudeltddruddvrddukeek X-VR-Cause-5: necurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtpdhhvghlohepjfhisghishgtuhhsrdhlohgtrghl X-VR-Cause-6: pdhinhgvthepkeekrdduledtrdduvddrudekkedpmhgrihhlfhhrohhmpehhohhnuggrrhgvhihtvgdr X-VR-Cause-7: lhhutgeslhgrphhoshhtvgdrnhgvthdprhgtphhtthhopehfrhgvvggsshguqdgrrhhmsehfrhgvvggs X-VR-Cause-8: shgurdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-VR-AvState: No X-VR-State: 0 X-VR-State: 0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 20:20:27 -0000 Hi, I've just build 12-current for Allwinner H3  (armv7) and it seems that cpufreq support is missing (orangepi or nanopi): root@allwinner-h3:~ # service powerd onestart Starting powerd. powerd: no cpufreq(4) support -- aborting: No such file or directory /etc/rc.d/powerd: WARNING: failed to start powerd So, on nanopi neo, it's slowdown (not on orange-pi that seems to run at full speed). I am using a custom kernel conf that just contains: include GENERIC nooptions       INVARIANTS nooptions       INVARIANT_SUPPORT nooptions       WITNESS nooptions       WITNESS_SKIPSPIN nooptions       BUF_TRACKING nooptions       DEADLKRES nooptions       FULL_BUF_TRACKING Here the output I get on orange-pi: U-Boot SPL 2016.03 (Jun 17 2016 - 18:48:42) DRAM: 1024 MiB Trying to boot from MMC U-Boot 2016.03 (Jun 17 2016 - 18:48:42 +0200) Allwinner Technology CPU:   Allwinner H3 (SUN8I) I2C:   ready DRAM:  1 GiB WARNING: Caches not enabled MMC:   SUNXI SD/MMC: 0 reading u-boot.env ** Unable to read "u-boot.env" from mmc0:1 ** Using default environment In:    serial Out:   serial Err:   serial Net:   No ethernet found. starting USB... USB0:   USB EHCI 1.00 USB1:   USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found Hit any key to stop autoboot:  0 Booting from: mmc 0 ubldr.bin reading ubldr.bin 238600 bytes read in 57 ms (4 MiB/s) ## No elf image at address 0x42000000 ## Starting application at 0x42000000 ... Consoles: U-Boot console Compatible U-Boot API signature found @0x7bf4a610 FreeBSD/armv7 U-Boot loader, Revision 1.2 (Mon Mar  5 23:38:55 CET 2018 luc@unxbox) DRAM: 1024MB MMC Device 1 not found Number of U-Boot devices: 1 U-Boot env: loaderdev='mmc 0' Found U-Boot device: disk   Checking unit=0 slice= partition=... good. Booting from disk0s2a: Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x8ad654+0x1869ac syms=[0x4+0x979b0+0x4+0xdbf6a] /boot/entropy size=0x1000 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 1 second... Type '?' for a list of commands, 'help' for more detailed help. loader> load -t dtb boot/dtb/sun8i-h3-orangepi-one.dtb boot/dtb/sun8i-h3-orangepi-one.dtb size=0x4ec5 loader> boot Booting... Using DTB from loaded file 'boot/dtb/sun8i-h3-orangepi-one.dtb'. Kernel entry at 0x42200100... Kernel args: (null) KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994     The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #0 34d79fcc910(master)-dirty: Tue Mar  6 02:11:39 CET 2018 luc@unxbox:/usr/home/luc/ARM/obj/usr/home/luc/ARM/src/arm.armv7/sys/CUSTOM arm FreeBSD clang version 6.0.0 (branches/release_60 325932) (based on LLVM 6.0.0) VT: init without driver. module_register: cannot register simplebus/ahci from kernel; already loaded from kernel Module simplebus/ahci failed to register: 17 module_register: cannot register simplebus/ehci from kernel; already loaded from kernel Module simplebus/ehci failed to register: 17 module_register: cannot register simplebus/pcib from kernel; already loaded from kernel Module simplebus/pcib failed to register: 17 module_register: cannot register simplebus/ehci from kernel; already loaded from kernel Module simplebus/ehci failed to register: 17 CPU: ARM Cortex-A7 r0p5 (ECO: 0x00000000) CPU Features:   Multiprocessing, Thumb2, Security, Virtualization, Generic Timer, VMSAv7,   PXN, LPAE, Coherent Walk Optional instructions:   SDIV/UDIV, UMULL, SMULL, SIMD(ext) LoUU:2 LoC:3 LoUIS:2 Cache level 1:  32KB/64B 4-way data cache WB Read-Alloc Write-Alloc  32KB/32B 2-way instruction cache Read-Alloc Cache level 2:  512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc real memory  = 1073741824 (1024 MB) avail memory = 1036685312 (988 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: unblocking device. random: entropy device external interface kbd0 at kbdmux0 ofwbus0: aw_ccu0: on ofwbus0 clk_fixed0: on aw_ccu0 clk_fixed1: on aw_ccu0 clk_fixed2: on aw_ccu0 simplebus0: on ofwbus0 aw_ccung0: mem 0x1c20000-0x1c203ff on simplebus0 aw_ccung1: mem 0x1f01400-0x1f014ff on simplebus0 regfix0: on ofwbus0 regfix1: on ofwbus0 regfix2: on ofwbus0 regfix3: on ofwbus0 awusbphy0: mem 0x1c19400-0x1c1942b,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803,0x1c1c800-0x1c1c803,0x1c1d800-0x1c1d803 on simplebus0 gic0: mem 0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff irq 36 on simplebus0 gic0: pn 0x1, arch 0x2, rev 0x1, implementer 0x43b irqs 160 gpio0: mem 0x1c20800-0x1c20bff irq 17,18 on simplebus0 gpiobus0: on gpio0 gpio1: mem 0x1f02c00-0x1f02fff irq 40 on simplebus0 gpiobus1: on gpio1 rtc0: mem 0x1f00000-0x1f00053 irq 37,38 on simplebus0 rtc0: registered as a time-of-day clock, resolution 1.000000s generic_timer0: irq 0,1,2,3 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000 aw_syscon0: mem 0x1c00000-0x1c00fff on simplebus0 a31dmac0: mem 0x1c02000-0x1c02fff irq 4 on simplebus0 aw_mmc0: mem 0x1c0f000-0x1c0ffff irq 5 on simplebus0 mmc0: on aw_mmc0 ehci0: mem 0x1c1a000-0x1c1a0ff irq 9 on simplebus0 usbus0: EHCI version 1.0 usbus0 on ehci0 ohci0: mem 0x1c1a400-0x1c1a4ff irq 10 on simplebus0 usbus1 on ohci0 ehci1: mem 0x1c1b000-0x1c1b0ff irq 11 on simplebus0 usbus2: EHCI version 1.0 usbus2 on ehci1 ohci1: mem 0x1c1b400-0x1c1b4ff irq 12 on simplebus0 usbus3 on ohci1 gpioc0: on gpio0 awg0: mem 0x1c30000-0x1c3ffff irq 21 on simplebus0 miibus0: on awg0 ukphy0: PHY 0 on miibus0 ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow ukphy1: PHY 1 on miibus0 ukphy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow awg0: Ethernet address: f2:00:ee:63:b5:59 aw_wdog0: mem 0x1c20ca0-0x1c20cbf irq 24 on simplebus0 uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 29 on simplebus0 uart0: console (115384,n,8,1) gpioc1: on gpio1 cpulist0: on ofwbus0 cpu0: on cpulist0 cpu1: on cpulist0 cpu2: on cpulist0 cpu3: on cpulist0 gpioled0: on ofwbus0 cryptosoft0: Timecounters tick every 1.000 msec usbus0: 480Mbps High Speed USB v2.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen3.1: at usbus3 uhub2: on usbus3 ugen2.1: at usbus2 uhub3: on usbus2 mmcsd0: 16GB at mmc0 50.0MHz/4bit/65535-block Release APs Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... mmc0: ACMD42 failed, RESULT: 4 mmc0: Card at relative address 43690 failed to set bus width uhub1: 1 port with 1 removable, self powered uhub2: 1 port with 1 removable, self powered uhub0: 1 port with 1 removable, self powered uhub3: 1 port with 1 removable, self powered Setting hostuuid: ae41a69a-f668-11de-b3da-93fd68e687d1. Setting hostid: 0x3905964e. No suitable dump device was found. Starting file system checks: /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 3583737 free (57 frags, 447960 blocks, 0.0% fragmentation) Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat Soft Float compatibility ldconfig path: Setting hostname: allwinner-h3. Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: . Starting devd. awg0: link state changed to DOWN add host 127.0.0.1: gateway lo0 add host ::1: gateway lo0 add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Waiting 30s for the default route interface: .....(no carrier) Creating and/or trimming log files. Starting syslogd. Clearing /tmp (X related). Updating motd:. Mounting late filesystems:. Starting ntpd. Performing sanity check on sshd configuration. Jan  1 11:34:21 allwinner-h3 ntpd[419]: unable to bind to wildcard address :: - another process may be running - EXITING Starting sshd. Jan  1 11:34:22 allwinner-h3 sshd[449]: error: Bind to port 22 on :: failed: Can't assign requested address. Jan  1 11:34:22 allwinner-h3 sshd[449]: error: Bind to port 22 on 0.0.0.0 failed: Can't assign requested address. Jan  1 11:34:22 allwinner-h3 sshd[449]: fatal: Cannot bind any address. Starting sendmail_msp_queue. Starting cron. devmatch: Can't read linker hints file. Starting background file system checks in 60 seconds. Fri Jan  1 11:34 FreeBSD/arm (allwinner-h3) (ttyu0) login: Thanks From owner-freebsd-arm@freebsd.org Tue Mar 6 20:22:29 2018 Return-Path: Delivered-To: freebsd-arm@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 8B0D1F2BAB4 for ; Tue, 6 Mar 2018 20:22:29 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [174.136.99.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 287AC68AF6 for ; Tue, 6 Mar 2018 20:22:29 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zwp9B1chHzWCW2 for ; Tue, 6 Mar 2018 15:22:22 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520367742; bh=x+hug8AkYmFfq6GJU3CBnbjg1XvdN1YZFePi7kAfY6Q=; h=Subject:Cc:From:Message-ID:Date; b=Txit61i5ON3QqzusTvBcS+LsNb5gn112i/t2j+gIjB7P/9y7sCbkMGmyz8MlRrKsU HjxI6Atu1ZQGCYdIce9KOKhUnwVFglgdVx3UsbOQRMlBp4xN4WTePl6TeeVBcNZTvz 8FlvPEGilivfQCdHftplJRsM31PYTpSIChw9g5sGIYNS8QDjbBBV+eoNw2smgbmmBs iRBazqfgvE0vNX6o/aZB63jDUKD/RjANwdq8LNHdi+gMjq32afwsFXUskr6g9xUfrw /ID3r8uKQK4lgy5vXi3VpRcW2ZfumqXUvzplAev0CXzN2F+SrtREYn2AYwFZ/A2rOa QtrEbrJFCbp4A== Received: from [IPv6:fdcf:b715:2f4d:1:8cce:939f:8e2a:c719] (unknown [IPv6:fdcf:b715:2f4d:1:8cce:939f:8e2a:c719]) by sentry.24cl.com (Postfix) with ESMTP id 3zwp991LVPzkB4D for ; Tue, 6 Mar 2018 15:22:21 -0500 (EST) Subject: Re: Is maximum swap usage tunable? Cc: freebsd-arm@freebsd.org References: <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> <20180306191359.GC51223@www.zefox.net> From: Mike Message-ID: <2ea8176a-87b5-b5ea-527e-03f1312be49d@mgm51.com> Date: Tue, 6 Mar 2018 15:22:02 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180306191359.GC51223@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 20:22:29 -0000 On 3/6/2018 2:13 PM, bob prohaska wrote: > > svnlite info /usr/src will give the source revision. # svnlite info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 330354 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 330354 Last Changed Date: 2018-03-03 15:42:39 -0500 (Sat, 03 Mar 2018) From owner-freebsd-arm@freebsd.org Tue Mar 6 20:37:55 2018 Return-Path: Delivered-To: freebsd-arm@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 51089F2D381 for ; Tue, 6 Mar 2018 20:37:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BAF4C6A76D; Tue, 6 Mar 2018 20:37:54 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w26KbrHP054302 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Mar 2018 12:37:54 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w26Kbrx4054301; Tue, 6 Mar 2018 12:37:53 -0800 (PST) (envelope-from fbsd) Date: Tue, 6 Mar 2018 12:37:53 -0800 From: bob prohaska To: "Rodney W. Grimes" Cc: "freebsd-arm@freebsd.org" , Ian Lepore , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180306203753.GD51223@www.zefox.net> References: <20180306190135.GB51223@www.zefox.net> <201803061928.w26JSHmQ050295@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201803061928.w26JSHmQ050295@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 20:37:55 -0000 On Tue, Mar 06, 2018 at 11:28:17AM -0800, Rodney W. Grimes wrote: > > Watch the output of the command I posted in the other > thread, > vmstat -z | egrep 'ITEM|g_bio|UMA' > > There was a known g_bio leak. > Here are a couple examples: bob@www:~ % vmstat -z | egrep 'ITEM|g_bio|UMA' ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 408, 0, 199, 8, 199, 0, 0 UMA Zones: 520, 0, 200, 3, 200, 0, 0 UMA Slabs: 80, 0, 561, 1239, 119978, 0, 0 UMA Hash: 256, 0, 4, 11, 11, 0, 0 g_bio: 376, 0, 16, 14,34532188, 0, 0 bob@www:~ % vmstat -z | egrep 'ITEM|g_bio|UMA' ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 408, 0, 199, 8, 199, 0, 0 UMA Zones: 520, 0, 200, 3, 200, 0, 0 UMA Slabs: 80, 0, 1172, 628, 120604, 0, 0 UMA Hash: 256, 0, 4, 11, 11, 0, 0 g_bio: 376, 0, 32, 168,34710061, 0, 0 The very large integer in the REQ column looks odd, is it significant? At roughly the same time, top looked like this: last pid: 67582; load averages: 3.48, 2.75, 2.50 up 0+22:38:54 12:14:09 52 processes: 4 running, 48 sleeping CPU: 88.0% user, 0.0% nice, 3.9% system, 2.5% interrupt, 5.6% idle Mem: 625M Active, 48M Inact, 57M Laundry, 158M Wired, 84M Buf, 20M Free Swap: 3072M Total, 827M Used, 2245M Free, 26% Inuse, 1016K In, 4308K Out PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 67533 root 1 102 0 543M 131M RUN 1 4:55 97.13% c++ 67573 root 1 103 0 330M 302M RUN 2 1:45 96.64% c++ 67582 root 1 102 0 140M 113M RUN 0 0:39 95.64% c++ 67460 root 1 52 0 594M 115M swread 0 9:16 66.24% c++ 665 bob 1 20 0 13608K 892K CPU1 1 3:57 0.32% top 7915 bob 1 20 0 12976K 512K nanslp 0 0:46 0.13% gstat 652 bob 1 20 0 21008K 620K select 1 0:31 0.04% sshd 571 root 1 20 0 15468K 736K select 1 0:08 0.02% sendmail 66462 root 1 20 0 16484K 2244K select 2 0:19 0.00% make 667 root 1 20 0 10408K 208K select 0 0:09 0.00% make 695 root 1 20 0 11096K 208K select 3 0:07 0.00% make 7903 bob 1 20 0 21044K 320K select 2 0:06 0.00% sshd 20380 root 1 20 0 11008K 208K select 0 0:05 0.00% make 47745 root 1 20 0 14428K 216K select 0 0:04 0.00% make 47734 root 1 20 0 11000K 204K select 2 0:03 0.00% make 578 root 1 20 0 11704K 216K nanslp 2 0:02 0.00% cron 56893 root 1 20 0 10408K 208K select 0 0:02 0.00% make There were a couple of brief swread entries in the STATES column, but the machine is generally making good progress; buildworld.log is up to nearly 15 MB. I haven't noticed any pfault entries today. Of the five machines on my local net only two are being thoroughly exercised, a Pi2 and a Pi3. Both are running -current as of a couple days ago. Both are having difficulty building world lately. The other machines (all Pi2) also build their own worlds and kernels but not often. They are running 11. Thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Wed Mar 7 06:15:27 2018 Return-Path: Delivered-To: freebsd-arm@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 54B46F2F97C; Wed, 7 Mar 2018 06:15:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 EE9A58033C; Wed, 7 Mar 2018 06:15:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 052FA20DD9; Wed, 7 Mar 2018 01:15:26 -0500 (EST) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 01:15:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=U2sL02wso5H+LbA3Dv/bVTM9DbqX+LYxffds5XzKVHg=; b=mnzyhIPu gMVLlGYw2CMu1OcrOguFl0wvfhh8LUA9pXWwk4b0pTZn9RC7VAxk9XxYGxxOg9Ny wNuT3QCRHYc0xHkfMmNdEhiEHEWHZERegz39FlgK/0BOLub1RXv+hD3EVJICK0wv YU3kY8JueF6LfT60N/qa3LsmmUboZlk/iZb/ZlzE0NztyKIVs2OUDm1Twn3G7gcv vNvBGjBNh6s8iDcRWFx8vrdZbJ6RUvyxF4BkD4y2D+mUAEtwqTxCRtsN09jzIS9e 4dY1yNqp8OMb0bx4o4rlgXBUeF4uohlbUbYzoN5DxNlY7kBX3SIODTjiocpxhIzQ s2Czs7gSt6h4oQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=U2sL02wso5H+LbA3Dv/bVTM9DbqX+ LYxffds5XzKVHg=; b=e615j9CBRbvs/aIGiJxdVwjbZaXgCpyIR3ofaJqw7hYYn 4w2u1y6cTUfwIUi7fDYhharGTtvDCpWXkJQKITUiSx/1TC4VOxcmUYQ16h2YDm64 HCXPmxqIPFN+nAwbgjmwWGE7lhtKDTaX/g/UlklyspuPdp/CapAtnv8+sdCIH+5v dxz//2yYRgGTs0nuAnzKGlz1zOke4fkWh13178zKCaN20J2fahB2jyU5Sw5lhNxx xpQhWQToECMVrIMXsF+aOE+aRApjx7ru+55Dw6tuSfxl9FNHPg0yshwi4YFNSLgu JAOO1zGWX0TIA5oHBL3zeWWDoJIa+RAFwMTQTyXoQ== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id BDF30BA43B; Wed, 7 Mar 2018 01:15:25 -0500 (EST) Message-Id: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> From: John To: freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-54087d22 Subject: best settings for usb2 and attached disks, and sdcards Date: Wed, 07 Mar 2018 06:15:25 +0000 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 06:15:27 -0000 Hi, [cc'd to arm@ and fs@ where it's also relevant] I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: [...] /dev/da0p2 on /ext (ufs, local, noatime, soft-updates) [...] was mounted with the command "mount -o async,noatime,rw /dev/da0s2 /ext" but I can't tell if async is on or just ignored, no error message. And I still have to run svnlite cleanup /ext/ports until svnlite stops bailing out. When newfs was written, I passed -t to it to enable trim, which seems to make a difference on this for deletes but not writes. Can anyone please suggest anything I can so to speed up disk i/o? And is async being applied or ignored? thanks, -- John tech-lists@zyxst.net From owner-freebsd-arm@freebsd.org Wed Mar 7 17:15:28 2018 Return-Path: Delivered-To: freebsd-arm@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 C178DF4181C for ; Wed, 7 Mar 2018 17:15:28 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [IPv6:2607:f2f8:af30::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D12081D2F for ; Wed, 7 Mar 2018 17:15:28 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zxKz074h6zWCW1 for ; Wed, 7 Mar 2018 12:15:24 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520442926; bh=s4+7OWLe/weMbRz4gsK+LDQiov3s79LO8j7PNivviDs=; h=Subject:Cc:From:Message-ID:Date; b=LjpOZ9Vup7J1M8pEwYaJpKa4U0IndqYlDsVSyFV30f+uQMBEBToclYZATLDZlowSs hwOYnglSM9oobBk9Mg6DlYhqRaPBrB8yElZdH0/52f+40vhYtiv4Z6gPoP1AxZIwMZ ZFZ/Yxs64iImY4ref6JApCY0sJnZd81uPHzNYjCvCOatWITeZuVoPOmWPlmEurqL9S VFS7EbpkeT4lH3sqFCb+arB8DYImmUFyp08JVN8FSigy5xpwgcqZzHw+IY5/6ENu3j +C9PiypGWxTW6jQQQdLnvsPvM3XgeAnj6v2B/bg2a9sMPPOym0UStx6LfeJ5fzgCKD Ve4RQXZgulnoA== Received: from [IPv6:fdcf:b715:2f4d:1:7869:bb8f:59e2:27f7] (unknown [IPv6:fdcf:b715:2f4d:1:7869:bb8f:59e2:27f7]) by sentry.24cl.com (Postfix) with ESMTP id 3zxKyz6p1ZzkB4D for ; Wed, 7 Mar 2018 12:15:23 -0500 (EST) Subject: Re: Is maximum swap usage tunable? Cc: freebsd-arm@freebsd.org References: <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> <20180306191359.GC51223@www.zefox.net> From: Mike Message-ID: <90c0a76b-8682-1277-d0b5-297759e16b4f@mgm51.com> Date: Wed, 7 Mar 2018 12:15:03 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180306191359.GC51223@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 17:15:28 -0000 fwiw... here is the script that I use to initialize the RPi3 after I install the image file. ===== #! /bin/sh # this script preps the Raspberry Pi for use # sequence is: # - find and load the image # - boot # - switch over to ssh, and upload this script # - log in, su to root, and run this script # echo " " echo "setting timezone" tzsetup # echo " " echo "removing freebsd account" cd /tmp pw userdel -n freebsd -r # echo " " User=test UserName="Test User" echo "adding ${User}" pw groupadd -n ${User} -g 1001 pw useradd -n ${User} -u 1001 -g 1001 -G wheel -c "${UserName}" \ -md /home/${User} -M 755 -w no -s /bin/tcsh # echo " " echo "setting password for root" /usr/bin/passwd root echo "setting password for ${User}" /usr/bin/passwd ${User} # echo " " echo "setting root's name to rpi3" pw usermod root -c rpi3 root # echo " " echo "setting up pkg" # needed for pkg because image was built against older userland ln -s /usr/lib/libarchive.so /usr/lib/libarchive.so.6 env ABI=FreeBSD:11:aarch64 pkg bootstrap test ! -d /usr/local/etc && mkdir -p /usr/local/etc echo 'ABI = "FreeBSD:11:aarch64";' >> /usr/local/etc/pkg.conf # # echo " " echo "creating swap space" SwapFile=/mnt/swap0 dd if=/dev/zero of=${SwapFile} bs=1m count=2048 chmod 0600 ${SwapFile} echo "md99 none swap sw,file=${SwapFile},late 0 0" >> /etc/fstab swapon -aL swapctl -l # df -h # echo " " # #=fini= ========== From owner-freebsd-arm@freebsd.org Wed Mar 7 17:16:36 2018 Return-Path: Delivered-To: freebsd-arm@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 C4D96F41A63 for ; Wed, 7 Mar 2018 17:16:36 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 1BEB581EBE for ; Wed, 7 Mar 2018 17:16:35 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 35ee8aa1-222b-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 35ee8aa1-222b-11e8-bb8e-b35b57339d60; Wed, 07 Mar 2018 17:16:02 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w27HGR9h002443; Wed, 7 Mar 2018 10:16:27 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520442987.84937.12.camel@freebsd.org> Subject: Re: best settings for usb2 and attached disks, and sdcards From: Ian Lepore To: John , freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Date: Wed, 07 Mar 2018 10:16:27 -0700 In-Reply-To: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 17:16:37 -0000 On Wed, 2018-03-07 at 06:15 +0000, John wrote: > Hi, > [cc'd to arm@ and fs@ where it's also relevant] > > I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. > > When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: > > [...] > /dev/da0p2 on /ext (ufs, local, noatime, soft-updates) > [...] > > was mounted with the command "mount -o async,noatime,rw /dev/da0s2 /ext" > but I can't tell if async is on or just ignored, no error message. And I still have to run svnlite cleanup /ext/ports until svnlite stops bailing out. When newfs was written, I passed -t  to it to enable trim, which seems to make a difference on this for deletes but not writes. Can anyone please suggest anything I can so to speed up disk i/o? And is async being applied or ignored? > > thanks, If your ufs2 filesystem is formatted with soft dependencies, the async mount option does nothing (the ufs mount code forces it off when the softdeps flag is on).  Basically, softdeps IS async for ufs. If you have journaling enabled on the usb or sdcard filesystems, turn it off.  It just amplifies the writes to devices that are already very slow on writes, and the only benefit to journaling is that it speeds up fsck recovery.  Since sdcard and thumb drive filesystems tend to be very small already, the speed up from having journaling enabled amounts to a few seconds at best, and even that benefit only comes after a crash. -- Ian From owner-freebsd-arm@freebsd.org Wed Mar 7 17:43:38 2018 Return-Path: Delivered-To: freebsd-arm@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 CF410F44059; Wed, 7 Mar 2018 17:43:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 77A1183AB2; Wed, 7 Mar 2018 17:43:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C32F320D4A; Wed, 7 Mar 2018 12:43:36 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 12:43:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=6B2C3TIbVTffR3XnCzbOLfgGbejfPlXdHV7sEpjB34I=; b=RMnN0EXd wZWBvyq5v2xlTfOSpJGrOHXavvjVtsOgayuhV5KWpLtRvstbHzPz0qmNbId6b5cQ s1JnrZQ1kzyKMQgHm9F9qZmQINFsURIHZga7eMQm7HnICyvF2l+rlsRPwoJ41djl RitlPXwVC+NBNkC+SyhvAb5/1GYZTjt5V4XxiFD4V1/cq6T6A+puAH+Glrk2N9XJ aEx0DAOOzt5pYwKXKqYibXfTITgNWXsYKhpidcek4sVC7KKajjWScB0MGKICxhD8 2yM5rfewQuLDm3BolSDdOKWOpP7fRNudIqHV8ILAJK5/0tMQL2KuVptxsrJKdJRU bmfQEIyop5v05Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=6B2C3TIbVTffR3XnCzbOLfgGbejfP lXdHV7sEpjB34I=; b=GOV9wJr2NiXg1nFZ68wBFu9KyyZGuFGaKrgWkPrFBehXP LhF1kPRppFj99/Uz4HLAb/SXIqAgzgFxuK5nPyjQQl2kE7EaJC6wwh28QFQXfNqS 7+gX9QSeqg+/u2dEO7qnclWHieaHYUqU/wVfAMm4mXtmMDjDB/AX3d/oLTvD78WN Yf0WzkEUD4z3RToc55hS5ntdZwV3e2t+0iqczy+p9v+ACGTH7NiCHy/YyzFtA+hR xlZkopzgv9FAV776JnJtRaUqKtrHKzXCbCmCRLgvzNKCfC3V7B8wmPvYpnKVGTxY RLmmVh/4C1rnL7zdxIrrplygiMIUZNX0uYagpdxbw== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 27C79246D5; Wed, 7 Mar 2018 12:43:36 -0500 (EST) To: freebsd-fs Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org From: tech-lists Subject: updating via svn and usb2 thumbdrives Message-ID: <5f3f4e06-c72f-0384-a428-823a30810368@zyxst.net> Date: Wed, 7 Mar 2018 17:43:35 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 17:43:38 -0000 Hi, When updating, particularly when downloading the src or ports tree for the first time, even though I've taken all approaches possible to speed up access to attached usb2 drives, I'll get these errors which will cause the update to bail: A ports/www/py-django-otp svn: E120106: ra_serf: The server sent a truncated HTTP response body. where it'll remain until I restart it but sometimes it'll crash so badly svn will demand svn cleanup on the dir I'm downloading to, like this: A ports/www/elgg/files svn: E120106: ra_serf: The server sent a truncated HTTP response body. # svnlite co https://svn0.eu.FreeBSD.org/ports/head /ext/ports svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) svn: E155004: Working copy '/ext/ports' locked. svn: E155004: '/ext/ports' is already locked. So I do this: # svnlite cleanup /ext/ports ...and I can start svnlite again. I'm sure this has to do with the thumbdrive 'catching up' with writing. So my question is this: Is there some switch in svnlite or some tool or parameter I can give to the process that will either buffer or limit the demands made of the device? It's UFS2 mounted with -o async[might be redundant],rw and has soft-updates but no journalling. My connection speed is 23Mbit so I'm thinking that on usb2 this might be approaching its random write speed but i'm unsure. What's the best way to permanently fix this? thanks, -- J. From owner-freebsd-arm@freebsd.org Wed Mar 7 18:05:06 2018 Return-Path: Delivered-To: freebsd-arm@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 A866DF45AD2; Wed, 7 Mar 2018 18:05:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4F35C84BDC; Wed, 7 Mar 2018 18:05:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B197620DC5; Wed, 7 Mar 2018 13:05:05 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 13:05:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=bzrbeGB+9oxp3z8KHDw+8bsPTqB9x u64kHn2l7IK0oc=; b=gSa9oMyU0bzj/2nRvpDi7okBYshqIijHr8uXMVt4r57EI 4+OeNOA2TaaoAi+F3oCUhB/uaBVRT67G7X2lO9as3tat7BhJUB12Zf+n/vNz+a5z YdsbkozT5mJO/Hb3LbQXWtxkdIQ4Qb7/cpIICPYqaqvokEYclVxMqMmgeU44zjBx PeP+E/cROCsrYjmJz6BJxUZuHSmnQH7LfIcOG7Qy3Ex4e/zq36/ZIJhlBdoovEvE oGa16oEOMYm91jel12CcB5aA9Vt4wD7sXkvWs/jA1F188IpaUPp9c94ERtv7b8dK gKsPBbTLHzawsFsXhuMU8v4NHJMiBlMIpDuSc6a7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bzrbeG B+9oxp3z8KHDw+8bsPTqB9xu64kHn2l7IK0oc=; b=cCnypJMg3238Eo6KO0gio6 K0iwLYaxK1NAsxigkPDuVVOlbYrgu140KXlowdvYaJsL7gr3QUhYbAuItNuBmAkA v93P4+91RkDPe9WYpwo1lYohkkMONsXUhFTRzn/0OoqYgJtZZQ/sOJRVcdGqdMde 8WeH0Pge0uFxCVsp+rMCp6LR/33Xx7efcKa0DqCL2I26AZN7RmyKgDb+A5b/5f3R Z5ug2PBAYjiqj2qMYmez9FbmmkczZcIX3LIfB2pKZHhHzQ/hwHhLcAIkdnV88gvD wQdgM5rHw+We0DqNMximwagjZRtxKKPtDLVzHFlbKQ+nw4qhAUw6TKCVNRPsjolw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 0784E24505; Wed, 7 Mar 2018 13:05:04 -0500 (EST) Subject: Re: best settings for usb2 and attached disks, and sdcards To: Ian Lepore , freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <1520442987.84937.12.camel@freebsd.org> From: tech-lists Message-ID: Date: Wed, 7 Mar 2018 18:05:04 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1520442987.84937.12.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 18:05:06 -0000 On 07/03/2018 17:16, Ian Lepore wrote: > If you have journaling enabled on the usb or sdcard filesystems, turn > it off. Yes, it's turned off. The new fs was made with newfs -U -n -t. I found later that the thumb drives didn't have TRIM functionality but didn't know for sure at the time (only found out when a notification popped up on the console that TRIM was switched on the filesystem but the disk didn't support it). thanks, -- J. From owner-freebsd-arm@freebsd.org Wed Mar 7 18:21:32 2018 Return-Path: Delivered-To: freebsd-arm@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 8E260F47037 for ; Wed, 7 Mar 2018 18:21:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DA52185C53 for ; Wed, 7 Mar 2018 18:21:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w27ILPCZ057641 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Mar 2018 10:21:26 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w27ILPIx057640; Wed, 7 Mar 2018 10:21:25 -0800 (PST) (envelope-from fbsd) Date: Wed, 7 Mar 2018 10:21:17 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Garbled console output on Pi3 Message-ID: <20180307182117.GA55819@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 18:21:32 -0000 >From time to time I observe garbled console output on a Pi3 running -current. The present revision is FreeBSD 12.0-CURRENT (ZEFOX) #1 r330571: Wed Mar 7 00:58:23 PST 2018 but I don't think that's special; the same thing has shown up sporadically for the past month or so. The output looks like this: Mar 7 09:53:53 www kernel: pid 44970 (llvm-tblgen), uid 0, was killed: out of swap space sswawpa_spp_apgaegr:er iw:ndsaewap fii_ppnand_ieptge fiweaanrig:eti r:teb u wfiifannidt deefebr:i fnbuiiuffontife tberwajit:e : bu0f, bufeblfokb nj:r:o: 0,w2 b b22u3fo94aibj,tl: k b0nosui:,z fe b1siz87erlk6:n, o:sbi 4zue: : 202f901o669b604, ej0sw: : r:ag le4,0paap9 g6_epb inrkd: inendefifnioini:te t w1eai35t bu w2fai6t0f b,er:uf fbufoerbj: :bufo bjs0:i , z0bl, blkeknno: 2: o16: 4260191,52 9393s7ize:, 1siz63e:84 4 096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 210573, size: 4096 The first and last lines look normal, which seems to rule out errors in the serial link. It seems to happen when the system is overloaded. In this case make -j8 buildworld was running as a stress test, but much lower j values have done the same thing in the past. All the output seen in ssh sessions looks normal, although sometimes very delayed. In this case top reported (shortly after the fact): last pid: 58112; load averages: 1.98, 1.45, 1.52 up 0+01:25:14 10:10:15 49 processes: 3 running, 46 sleeping CPU: 56.5% user, 0.0% nice, 6.6% system, 8.0% interrupt, 29.0% idle Mem: 586M Active, 63M Inact, 36M Laundry, 154M Wired, 97M Buf, 68M Free Swap: 3072M Total, 1369M Used, 1703M Free, 44% Inuse, 22M In PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 58053 root 1 81 0 271M 45704K RUN 0 0:53 97.15% llvm-tblgen 58086 root 1 96 0 185M 26820K CPU2 2 3:24 93.95% llvm-tblgen 58049 root 1 29 0 265M 24924K swread 2 0:50 27.49% llvm-tblgen 58048 root 1 26 0 392M 63920K swread 2 0:37 16.72% llvm-tblgen 58046 root 1 22 0 254M 21816K swread 1 0:45 8.05% llvm-tblgen 58051 root 1 21 0 268M 26680K swread 1 0:49 3.14% llvm-tblgen 58044 root 1 20 0 67828K 11000K swread 2 0:35 1.51% llvm-tblgen 643 bob 1 20 0 13872K 876K CPU1 1 0:10 0.18% top 638 bob 1 20 0 21148K 600K select 2 0:01 0.03% sshd 58041 root 1 20 0 23776K 588K select 3 0:19 0.00% make 573 root 1 20 0 15468K 560K select 3 0:00 0.00% sendmail 45034 root 1 20 0 11024K 184K select 0 0:00 0.00% make 19864 bob 1 20 0 13788K 32K ttyin 3 0:00 0.00% tcsh 58016 root 1 20 0 10920K 184K select 0 0:00 0.00% make 30893 bob 1 20 0 13788K 32K ttyin 3 0:00 0.00% tcsh 570 It seems odd that the console should malfunction in this fashion, perhaps there is some significance to more learned eyes. In this case buildworld worked through the bottleneck and is again running at 0% idle. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Wed Mar 7 19:17:49 2018 Return-Path: Delivered-To: freebsd-arm@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 BDCCEF4B83F for ; Wed, 7 Mar 2018 19:17:49 +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 5554F68EBE for ; Wed, 7 Mar 2018 19:17:49 +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 680BB1936A for ; Wed, 7 Mar 2018 19:17:48 +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 w27JHmYA014923 for ; Wed, 7 Mar 2018 19:17:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w27JHmMN014921 for freebsd-arm@FreeBSD.org; Wed, 7 Mar 2018 19:17:48 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-arm@FreeBSD.org Subject: [Bug 226430] Can't netboot Orange Pi PC (Allwinner H3) Date: Wed, 07 Mar 2018 19:17:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@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 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-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 19:17:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226430 Bug ID: 226430 Summary: Can't netboot Orange Pi PC (Allwinner H3) Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: greg@unrelenting.technology Trying ubldr: dhcp env set serverip 192.168.1.2 tftp ${fdt_addr_r} dtb/sun8i-h3-orangepi-pc.dtb fdt addr ${fdt_addr_r} env set loaderdev net env set rootpath ${serverip}:/solitude-tank/greg/Netboot/OrangePCFBSD12 tftp ${kernel_addr_r} ubldr.bin go ${kernel_addr_r} Result: FreeBSD/armv6 U-Boot loader, Revision 1.2=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 (Mon Feb 19 00:23:06 MSK 2018 greg@ruunvald.lan) [=E2=80=A6] Booting from net0: net_probe: no network devices found, maybe not enumerated yet..? netboot: couldn't probe uboot_eth0 net_open: netif_open() failed net_probe: no network devices found, maybe not enumerated yet..? netboot: couldn't probe uboot_eth0 net_open: netif_open() failed [=E2=80=A6same stuff repeats a few more times=E2=80=A6] Trying EFI: dhcp env set serverip 192.168.1.2 tftp ${fdt_addr_r} dtb/sun8i-h3-orangepi-pc.dtb fdt addr ${fdt_addr_r} env set bootargs boot.nfsroot.server=3D${serverip} boot.nfsroot.path=3D/solitude-tank/greg/Netboot/OrangePCFBSD12 tftp ${kernel_addr_r} loader.efi bootefi ${kernel_addr_r} ${fdt_addr_r} Result: ## Starting EFI application at 42000000 ... [=E2=80=A6] FreeBSD/arm EFI loader, Revision 1.1 (Mon Feb 19 00:23:06 MSK 2018 greg@ruunvald.lan) \ (hangs forever on the slash) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Thu Mar 8 01:08:04 2018 Return-Path: Delivered-To: freebsd-arm@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 E9BB0F43F98 for ; Thu, 8 Mar 2018 01:08:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 67A8879FCE for ; Thu, 8 Mar 2018 01:08:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w281828d058707 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Mar 2018 17:08:03 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w28182QY058706; Wed, 7 Mar 2018 17:08:02 -0800 (PST) (envelope-from fbsd) Date: Wed, 7 Mar 2018 17:08:02 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Garbled console output on Pi3 Message-ID: <20180308010802.GA58656@www.zefox.net> References: <20180307182117.GA55819@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180307182117.GA55819@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 01:08:04 -0000 The j8 buildworld ended with a crash. Console, backtrace, gstat log, buildworld log and top window are available at http://www.zefox.net/~fbsd/rpi3/crashes/20180307/ in case they're of interest. The most curious feature to my untrained eye is the gstat log, which ends with dT: 10.002s w: 10.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 3 2 0 10 27226 1 58 27002 0 0 0.0 275.3 da0 1 0 0 3 36.7 0 0 0.0 0 0 0.0 0.4 mmcsd0s3 0 0 0 0 0.0 0 6 26958 0 0 0.0 275.3 da0a 3 1 0 10 27246 1 52 26875 0 0 0.0 275.6 da0d On this host da0a is /var and da0d is /usr. There are 3GB of swap on mmcsd0s3b and d, which don't seem particularly busy. Nonetheless, /var and /usr are showing a physically impossible level of activity. I hope this makes sense to somebody..... bob prohaska From owner-freebsd-arm@freebsd.org Thu Mar 8 03:46:27 2018 Return-Path: Delivered-To: freebsd-arm@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 5ED4AF2C331 for ; Thu, 8 Mar 2018 03:46:27 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CFC9B81BD0 for ; Thu, 8 Mar 2018 03:46:26 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w283kQ2n059084 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Mar 2018 19:46:27 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w283kQ9J059083; Wed, 7 Mar 2018 19:46:26 -0800 (PST) (envelope-from fbsd) Date: Wed, 7 Mar 2018 19:46:26 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Garbled console output on Pi3 Message-ID: <20180308034626.GA59034@www.zefox.net> References: <20180307182117.GA55819@www.zefox.net> <20180308010802.GA58656@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308010802.GA58656@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 03:46:27 -0000 Just for sake of curiosity I tried Peter Holm's stress2 test suite, which compiles without issue on the RPi3 when svn'd from his website. After running for not quite three hours the following appeared on the console: Mar 7 18:19:25 www kernel: onc-mpdr etshern2t psicdh ed1_6y7i4e5l dt Mar 7 18:19:25 www kernel: resenctm ds <118>Mar 7 18:19:25 www kernel: trcimedd tthor 2u spei dn on1-6p7r4e2 upsied no1n6h7r425 p-tiprdri eesd1e 6nt7to sucshee dn_oyni-eplrde 5- pt7r4e5sr ietenrdti tos cuhseed _nyoine-lpdr Mar 7 18:19:25 www kernel: senctm d stchehrde2 d t_poyiide l1d6 Mar 7 18:19:25 www kernel: cmd thr2 pid 16745 tried to<118>Mar 7 18:19:25 www kernel: ldc Mar 7 18:19:25 www kernel: 16c7m4d5 ttrhire2d ptiod u1s6e7 4n5o nt-rpireeds etnot ussec hneodn_-ypireelsde Mar 7 18:19:25 www kernel: id c1m6d7 45t htrr2i epdi dt o 1u6s7e4 5n otnr-iperde steon tu ses cnhoend-_pyrieesledn Mar 7 18:19:35 www last message repeated 308 times Mar 7 18:19:35 www kernel: ield Mar 7 18:19:35 www kernel: id 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: 5 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: e non-present sched_yield Mar 7 18:19:35 www kernel: _yield Mar 7 18:19:35 www kernel: non-present sched_yield Mar 7 18:19:35 www kernel: ied to use non-present sched_yield Mar 7 18:19:35 www kernel: to use non-present sched_yield Mar 7 18:19:35 www kernel: d to use non-present sched_yield Mar 7 18:19:35 www kernel: n-present sched_yield Mar 7 18:19:35 www kernel: r2 pid 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: use non-present sched_yield Mar 7 18:19:35 www kernel: -present sched_yield Mar 7 18:19:35 www kernel: pid 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: non-present sched_yield Mar 7 18:19:35 www kernel: ed to use non-present sched_yield Mar 7 18:19:35 www kernel: hed_yield Mar 7 18:19:35 www kernel: cmd thr2 pid 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: 16745 tried to use non-present sched_yield Mar 7 18:19:35 www kernel: t sched_yield Mar 7 18:19:25 www kernel: sccmhde dt_hyri2e lpdi Mar 7 18:19:25 www kernel: cmd thr126 7p4i5d tr1i6e7d4 5t ot ried to use non-present sched_yield Mar 7 18:19:25 www kernel: 67c4m5d trtiherd2 tpoi du se1 6n7o4n5- ptrreiseedn tt os cuhseed _nyoine-lpdr Mar 7 18:19:25 www kernel: scemndt tshcrh2e dp_iydi el1d6 d thr2 pid 16745 tried to use non-p 1n6o7n4-5p rtersieendt tor eusseen tn osnc-hperde_syeinetl d Mar 7 18:19:27 www kernel: pidc m 1ds cht6he7r425 ptirdi ed1 6t7o4 5u ste2t hpri2d pi1d6 74156 7t4r5i etdr iteod utsoe unsoen -nporne-spernets esncth eds_cyhieedl_dy Mar 7 18:19:27 www kernel: t csmcdh edt_hyri2e lpdid Mar 7 18:19:27 www kernel: nt cmsdc htehdr_2 pyiide ld1 Mar 7 18:19:28 www kernel: sccmhedd _tyhire2l dp FreeBSD/arm64 (www.zefox.org) (ttyu0) login: smsc0: warning: failed to create new mbuf Mar 7 18:21:46 www kernel: pid 16763 (swap), uid 1001, was killed: out of swap space pagwaeitr buff: einite wait buffer: bufobj: 0, blkno: 559829, siszeswwa: p4a0_pager: i9ndefpinit6_e rn: budefinifote waibt bjuf:fer: b 0, blkno:uf ob559820, js: 0, blknoize: 4096 : 555233, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 560096, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 555285, size: 4096 The thing which most struck me was lines such as Mar 7 18:19:27 www kernel: t csmcdh edt_hyri2e lpdid in which the timestamp and origin of the message is undamaged, but the content is thoroughly mangled. Does it provide any help in localizing within the system what is out of sorts? bob prohaska From owner-freebsd-arm@freebsd.org Thu Mar 8 05:18:15 2018 Return-Path: Delivered-To: freebsd-arm@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 11E3DF33A55 for ; Thu, 8 Mar 2018 05:18:15 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 76F24859D3 for ; Thu, 8 Mar 2018 05:18:14 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id b59aad4e; Thu, 8 Mar 2018 06:18:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=bS6g6ovSGHh++ZJKorIbU+NMYvk=; b=TP4OZ37YdNFjcQa0tCsoJI+OZdqH E9yR0LSC4d9BTN80hnRxqTJzHg7ROA0IHvNvJddp+xs+5iYZ6KZtOiZSi+9NhUJe GAYODTLFkern0eVZ+2BfZIIvzILdyNqctqqYGGxkcbHGDX6R66QRkIOxSgQARLLp shRQSbfOZ6ao7Xc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=rFhwU4jngehD3s2+n18fdQoSO8ku2V0Av4nO2qBxNKu2TQBkA+yk0uXz k0emm6k4FeIY2I/1CNCbkAlTk+Yw8YdwPiiNj0tM0LKScNBYtIX8ISY+Ey41OoB8 rYqN5re3NdlTgn444OddZCoCMsQ5GG9xiK00b9ro82gulkqkNNE= Received: from arcadia (ai126160036254.39.access-internet.ne.jp [126.160.36.254]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 261b9e6e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 8 Mar 2018 06:18:11 +0100 (CET) Date: Thu, 8 Mar 2018 06:18:06 +0100 From: Emmanuel Vadot To: Luc Hondareyte Cc: Luc Hondareyte via freebsd-arm Subject: Re: cpufreq support on Allwinner H3 Message-Id: <20180308061806.d9c9c7282d1a956d86b6bb22@bidouilliste.com> In-Reply-To: <5332936b-f38b-ca7a-03d9-dfc7c92e2727@laposte.net> References: <5332936b-f38b-ca7a-03d9-dfc7c92e2727@laposte.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 05:18:15 -0000 On Tue, 6 Mar 2018 20:59:37 +0100 Luc Hondareyte via freebsd-arm wrote: > Hi, >=20 > I've just build 12-current for Allwinner H3=A0 (armv7) and it seems that= =20 > cpufreq support is missing (orangepi or nanopi): There is no opp table (freq<->voltage table) in the DTS that's why it's not working. I think I've seen patches on the linux-arm kernel mailing list to add them but even with thoses we will need support for the v2 opp. > root@allwinner-h3:~ # service powerd onestart > Starting powerd. > powerd: no cpufreq(4) support -- aborting: No such file or directory > /etc/rc.d/powerd: WARNING: failed to start powerd >=20 > So, on nanopi neo, it's slowdown (not on orange-pi that seems to run at=20 > full speed). I am using a custom kernel conf that just contains: >=20 > include GENERIC > nooptions=A0=A0=A0=A0=A0=A0 INVARIANTS > nooptions=A0=A0=A0=A0=A0=A0 INVARIANT_SUPPORT > nooptions=A0=A0=A0=A0=A0=A0 WITNESS > nooptions=A0=A0=A0=A0=A0=A0 WITNESS_SKIPSPIN > nooptions=A0=A0=A0=A0=A0=A0 BUF_TRACKING > nooptions=A0=A0=A0=A0=A0=A0 DEADLKRES > nooptions=A0=A0=A0=A0=A0=A0 FULL_BUF_TRACKING >=20 You can use the GENERIC-NODEBUG for that --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Mar 8 09:46:52 2018 Return-Path: Delivered-To: freebsd-arm@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 D46A8F4688C; Thu, 8 Mar 2018 09:46:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36E0371396; Thu, 8 Mar 2018 09:46:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w289khtX001252 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 10:46:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w289kb0s007764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 10:46:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w289kbvh084359 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 10:46:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w289ka53084358; Thu, 8 Mar 2018 10:46:36 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 10:46:36 +0100 From: Bernd Walter To: John Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308094636.GA80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 09:46:53 -0000 On Wed, Mar 07, 2018 at 06:15:25AM +0000, John wrote: > Hi, > [cc'd to arm@ and fs@ where it's also relevant] > > I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. > > When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: I'm currently very pleased with the SanDisk Extreme Plus micro SD cards. They are quite expensive, but behave way better with random writes. Event better in random write performance are the SanDisk Extreme USB sticks. Also quite expensive though and quite big. I can't tell, however, if they are better in case of power loss related data corruption. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 10:06:30 2018 Return-Path: Delivered-To: freebsd-arm@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 0ABF4F481F5; Thu, 8 Mar 2018 10:06:30 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EC46723A6; Thu, 8 Mar 2018 10:06:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1etsRK-0005to-2u; Thu, 08 Mar 2018 11:06:22 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Date: Thu, 08 Mar 2018 11:06:23 +0100 Subject: gstat more writes per seconds than there are seconds per write MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 2ecd0b53b7de9511489f92806276a3d7 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 10:06:30 -0000 Hello, I'm confused by this output. w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the average write takes more than a second? Is my SD card super parallel? :-) Sometimes the numbers are even higher. dT: 1.010s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 0 0 0 0 0.0 0 0 0.0 0.0 da0 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 0 0 0 0 0.0 0 0 0.0 0.0 msdosfs/MSDOSBOOT 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs [root@rpi2 ~]# uname -a dmesg | grep mmc FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan 30 20:10:37 CET 2018 root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm [root@rpi2 ~]# dmesg | grep mmc mmc0: on sdhci_bcm0 mmc0: CMD8 failed, RESULT: 1 mmcsd0: 2GB at mmc0 41.6MHz/4bit/65535-block Regards, Ronald. From owner-freebsd-arm@freebsd.org Thu Mar 8 10:20:17 2018 Return-Path: Delivered-To: freebsd-arm@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 152B2F492E6; Thu, 8 Mar 2018 10:20:17 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C5B872C2F; Thu, 8 Mar 2018 10:20:16 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28AKDPS001769 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 11:20:14 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28AKBdp008201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 11:20:11 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28AKAs0084498 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 11:20:10 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28AKAR8084497; Thu, 8 Mar 2018 11:20:10 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 11:20:10 +0100 From: Bernd Walter To: Ronald Klop Cc: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Subject: Re: gstat more writes per seconds than there are seconds per write Message-ID: <20180308102010.GB80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 10:20:17 -0000 On Thu, Mar 08, 2018 at 11:06:23AM +0100, Ronald Klop wrote: > Hello, > > I'm confused by this output. > w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the > average write takes more than a second? It is the time a request has to wait until it is done. But your L(q) says that 17 are queued. > Is my SD card super parallel? :-) Maybe, maybe not, flash device vendors don't tell how they work internally, which is a shame, but you can only request a single transaction with an SD card. On USB sticks you might be able to do tagged command queuing, not that many support that... Nevertheless you can always queue more than one request at the OS layer. > Sometimes the numbers are even higher. > > dT: 1.010s w: 1.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 > 0 0 0 0 0.0 0 0 0.0 0.0 da0 > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 > 0 0 0 0 0.0 0 0 0.0 0.0 msdosfs/MSDOSBOOT > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a > 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs > > [root@rpi2 ~]# uname -a > dmesg | grep mmc > FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan > 30 20:10:37 CET 2018 > root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm > > [root@rpi2 ~]# dmesg | grep mmc > mmc0: on sdhci_bcm0 > mmc0: CMD8 failed, RESULT: 1 > mmcsd0: 2GB at mmc0 > 41.6MHz/4bit/65535-block > > Regards, > Ronald. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 10:42:36 2018 Return-Path: Delivered-To: freebsd-arm@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 178C0F4AE20; Thu, 8 Mar 2018 10:42:36 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A682173C40; Thu, 8 Mar 2018 10:42:35 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1ett0L-0000DB-Ms; Thu, 08 Mar 2018 11:42:34 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Bernd Walter" , ticso@cicely.de Cc: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Subject: Re: gstat more writes per seconds than there are seconds per write References: <20180308102010.GB80981@cicely7.cicely.de> Date: Thu, 08 Mar 2018 11:42:36 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20180308102010.GB80981@cicely7.cicely.de> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 4cc6a862e0a753e674eb374334b394fd X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 10:42:36 -0000 On Thu, 08 Mar 2018 11:20:10 +0100, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 11:06:23AM +0100, Ronald Klop wrote: >> Hello, >> >> I'm confused by this output. >> w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the >> average write takes more than a second? > > It is the time a request has to wait until it is done. > But your L(q) says that 17 are queued. Thanks, that makes sense. Any ideas how to retrieve the ms/w without the time-in-queue included? Regards, Ronald. > >> Is my SD card super parallel? :-) > > Maybe, maybe not, flash device vendors don't tell how they work > internally, which is a shame, but you can only request a single > transaction with an SD card. > On USB sticks you might be able to do tagged command queuing, > not that many support that... > Nevertheless you can always queue more than one request at the OS layer. > >> Sometimes the numbers are even higher. >> >> dT: 1.010s w: 1.000s >> L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 >> 0 0 0 0 0.0 0 0 0.0 0.0 da0 >> 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 >> 0 0 0 0 0.0 0 0 0.0 0.0 >> msdosfs/MSDOSBOOT >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a >> 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs >> >> [root@rpi2 ~]# uname -a >> dmesg | grep mmc >> FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan >> 30 20:10:37 CET 2018 >> root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm >> >> [root@rpi2 ~]# dmesg | grep mmc >> mmc0: on sdhci_bcm0 >> mmc0: CMD8 failed, RESULT: 1 >> mmcsd0: 2GB at mmc0 >> 41.6MHz/4bit/65535-block >> >> Regards, >> Ronald. >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Mar 8 11:55:34 2018 Return-Path: Delivered-To: freebsd-arm@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 5347CF27E5F for ; Thu, 8 Mar 2018 11:55:34 +0000 (UTC) (envelope-from hondareyte.luc@laposte.net) Received: from smtp.laposte.net (smtpoutz27.laposte.net [194.117.213.102]) (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 DD79F766EA for ; Thu, 8 Mar 2018 11:55:33 +0000 (UTC) (envelope-from hondareyte.luc@laposte.net) Received: from smtp.laposte.net (localhost [127.0.0.1]) by lpn-prd-vrout015 (Postfix) with ESMTP id E54E61D1158 for ; Thu, 8 Mar 2018 12:33:44 +0100 (CET) Received: from smtp.laposte.net (localhost [127.0.0.1]) by lpn-prd-vrout015 (Postfix) with ESMTP id DA7B71D2180 for ; Thu, 8 Mar 2018 12:33:44 +0100 (CET) Received: from lpn-prd-vrin003 (lpn-prd-vrin003.laposte [10.128.63.4]) by lpn-prd-vrout015 (Postfix) with ESMTP id D3D7C1D2187 for ; Thu, 8 Mar 2018 12:33:44 +0100 (CET) Received: from lpn-prd-vrin003 (localhost [127.0.0.1]) by lpn-prd-vrin003 (Postfix) with ESMTP id C3296493E2A for ; Thu, 8 Mar 2018 12:33:44 +0100 (CET) Received: from Hibiscus.local (unknown [88.190.12.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lpn-prd-vrin003 (Postfix) with ESMTPSA id 9A5D34933E8; Thu, 8 Mar 2018 12:33:44 +0100 (CET) Subject: Re: cpufreq support on Allwinner H3 To: Emmanuel Vadot Cc: Luc Hondareyte via freebsd-arm References: <5332936b-f38b-ca7a-03d9-dfc7c92e2727@laposte.net> <20180308061806.d9c9c7282d1a956d86b6bb22@bidouilliste.com> From: Luc Hondareyte Message-ID: <542a7663-b4e0-2093-4dfc-9b8e9c3b513b@laposte.net> Date: Thu, 8 Mar 2018 12:33:44 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180308061806.d9c9c7282d1a956d86b6bb22@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr X-VR-FullState: 0 X-VR-Score: -100 X-VR-Cause-1: gggruggvucftvghtrhhoucdtuddrgedtfedrkeeggdduvdcutefuodetggdotefrodftvfcurfhrohhf X-VR-Cause-2: ihhlvgemucfntefrqffuvffgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhs X-VR-Cause-3: ucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefn X-VR-Cause-4: uhgtucfjohhnuggrrhgvhihtvgcuoehhohhnuggrrhgvhihtvgdrlhhutgeslhgrphhoshhtvgdrnhgv X-VR-Cause-5: theqnecuffhomhgrihhnpehinhhfrhgruggvrggurdhorhhgnecukfhppeekkedrudeltddruddvrddu X-VR-Cause-6: keeknecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtpdhhvghlohepjfhisghishgtuhhsrdhlohgt X-VR-Cause-7: rghlpdhinhgvthepkeekrdduledtrdduvddrudekkedpmhgrihhlfhhrohhmpehhohhnuggrrhgvhiht X-VR-Cause-8: vgdrlhhutgeslhgrphhoshhtvgdrnhgvthdprhgtphhtthhopehmrghnuhessghiughouhhilhhlihhs X-VR-Cause-9: thgvrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-VR-AvState: No X-VR-State: 0 X-VR-State: 0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 11:55:34 -0000 Le 08/03/2018 à 06:18, Emmanuel Vadot a écrit : > On Tue, 6 Mar 2018 20:59:37 +0100 > Luc Hondareyte via freebsd-arm wrote: > >> Hi, >> >> I've just build 12-current for Allwinner H3  (armv7) and it seems that >> cpufreq support is missing (orangepi or nanopi): > There is no opp table (freq<->voltage table) in the DTS that's why > it's not working. This thread? http://lists.infradead.org/pipermail/linux-arm-kernel/2018-February/557940.html > I think I've seen patches on the linux-arm kernel mailing list to add > them but even with thoses we will need support for the v2 opp. v2 opp? Does it mean that, as a workaround, with the appropriate DTS patch and a switch back to armv6, this should work? I say that because, on nanopi neo, with the "old" 12-current image build by Ganbold Tsagaankhuu (that was available on FriendlyArm Wiki), cpu_freq support is OK and it’s run at full speed: root@allwinner-h3:~ # uname -a FreeBSD allwinner-h3 12.0-CURRENT FreeBSD 12.0-CURRENT #7 r308116M: Mon Oct 31 10:56:20 ULAT 2016 tsgan@beastie.mstride.com:/usr/obj/arm.armv6/usr/src/sys/GENERIC arm root@allwinner-h3:~ # sysctl dev.cpu.0.freq cpufreq: get returning known freq 1008 cpufreq: get returning known freq 1008 dev.cpu.0.freq: 1008 And this image does not seem to use Linux DTS. >> root@allwinner-h3:~ # service powerd onestart >> Starting powerd. >> powerd: no cpufreq(4) support -- aborting: No such file or directory >> /etc/rc.d/powerd: WARNING: failed to start powerd >> >> So, on nanopi neo, it's slowdown (not on orange-pi that seems to run at >> full speed). I am using a custom kernel conf that just contains: >> >> include GENERIC >> nooptions       INVARIANTS >> nooptions       INVARIANT_SUPPORT >> nooptions       WITNESS >> nooptions       WITNESS_SKIPSPIN >> nooptions       BUF_TRACKING >> nooptions       DEADLKRES >> nooptions       FULL_BUF_TRACKING >> > You can use the GENERIC-NODEBUG for that > Oh, I missed that. Thanks. From owner-freebsd-arm@freebsd.org Thu Mar 8 13:23:47 2018 Return-Path: Delivered-To: freebsd-arm@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 1A58CF3127A for ; Thu, 8 Mar 2018 13:23:47 +0000 (UTC) (envelope-from toshi@ruby.ocn.ne.jp) Received: from mfdf017.ocn.ad.jp (mfdf017.ocn.ad.jp [153.128.50.72]) by mx1.freebsd.org (Postfix) with ESMTP id 9527C7A4E7 for ; Thu, 8 Mar 2018 13:23:46 +0000 (UTC) (envelope-from toshi@ruby.ocn.ne.jp) Received: from mogw0638.ocn.ad.jp (mogw0638.ocn.ad.jp [153.149.228.39]) by mfdf017.ocn.ad.jp (Postfix) with ESMTP id 142D18B34FA for ; Thu, 8 Mar 2018 22:02:56 +0900 (JST) Received: from mf-smf-ucb020c3 (mf-smf-ucb020c3.ocn.ad.jp [153.153.66.135]) by mogw0638.ocn.ad.jp (Postfix) with ESMTP id 12897200478; Thu, 8 Mar 2018 22:02:49 +0900 (JST) Received: from ntt.pod01.mv-mta-ucb024 ([153.149.142.98]) by mf-smf-ucb020c3 with ESMTP id tvC3em0y8Q0QOtvC5ewVDe; Thu, 08 Mar 2018 22:02:49 +0900 Received: from smtp.ocn.ne.jp ([153.149.227.167]) by ntt.pod01.mv-mta-ucb024 with id KR2o1x00W3dLKTM01R2oHp; Thu, 08 Mar 2018 13:02:49 +0000 Received: from localhost (p795042-ipngn200602sizuokaden.shizuoka.ocn.ne.jp [180.9.168.42]) by smtp.ocn.ne.jp (Postfix) with ESMTPA; Thu, 8 Mar 2018 22:02:48 +0900 (JST) Date: Thu, 08 Mar 2018 22:02:28 +0900 (JST) Message-Id: <20180308.220228.985768279546235038.toshi@ruby.ocn.ne.jp> Subject: PWM of BeagleBone Black on 11.1-RELEASE From: SAITOU Toshihide To: freebsd-arm@freebsd.org X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 13:23:47 -0000 How can I setup the PWM of BeagleBone Black? The driver attached but no signal observed with the followings. $ sysctl dev.am335x_ehrpwm.1.dutyB=50 $ sysctl dev.am335x_ehrpwm.1.dutyA=50 $ sysctl dev.am335x_ehrpwm.1.period=100 (nothing was observed) $ uname -a FreeBSD beaglebone 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 10:22:32 UTC 2017 root@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/BEAGLEBONE arm # dtc -I dts -O dtb pwm.dts -o pwm.dtb # cp pwm.dtb /boot/dtb/ # cat /boot/loader.conf fdt_overlays="pwm.dtb" # cat pwm.dts /dts-v1/; /plugin/; / { compatible = "ti,beaglebone", "ti,beaglebone-black", "ti,beaglebone-green"; fragment@4 { target = <&am33xx_pinmux>; __overlay__ { pinctrl-single,pins = < 0x048 0xe >; /* P9.21, gpio0_3 */ }; }; fragment@5 { target = <&epwmss1>; __overlay__ { status = "okay"; }; }; fragment@6 { target = <&ehrpwm1>; __overlay__ { status = "okay"; }; }; fragment@7 { target = <&ecap1>; __overlay__ { status = "okay"; }; }; }; -- SAITOU Toshihide From owner-freebsd-arm@freebsd.org Thu Mar 8 15:26:20 2018 Return-Path: Delivered-To: freebsd-arm@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 56EB0F3B405; Thu, 8 Mar 2018 15:26:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C5C3A7F4D8; Thu, 8 Mar 2018 15:26:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w28FQCpG061089 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 07:26:13 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w28FQBp1061088; Thu, 8 Mar 2018 07:26:11 -0800 (PST) (envelope-from fbsd) Date: Thu, 8 Mar 2018 07:26:11 -0800 From: bob prohaska To: ticso@cicely.de Cc: John , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, bob prohaska Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308152611.GA61027@www.zefox.net> References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <20180308094636.GA80981@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308094636.GA80981@cicely7.cicely.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 15:26:20 -0000 On Thu, Mar 08, 2018 at 10:46:36AM +0100, Bernd Walter wrote: > > I'm currently very pleased with the SanDisk Extreme Plus micro SD > cards. > They are quite expensive, but behave way better with random writes. > I don't think I've seen Sandisk Extreme Plus devices, how do they differ from "ordinary" Sandisk extreme devices? I think there is a "Pro" version, is that the same thing? > Event better in random write performance are the SanDisk Extreme > USB sticks. > Also quite expensive though and quite big. > Likewise, my experiece, spread over 4 RPi2's and 2 RPi3's, has been good. > I can't tell, however, if they are better in case of power loss > related data corruption. > Never done a systematic test, but accidental unplugs and power cycles after a crash have never caused problems fsck -f won't fix. hth, bob prohaska From owner-freebsd-arm@freebsd.org Thu Mar 8 16:02:51 2018 Return-Path: Delivered-To: freebsd-arm@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 A2A7BF3ECCB; Thu, 8 Mar 2018 16:02:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 33CB78229C; Thu, 8 Mar 2018 16:02:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28G2lvR007513 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:02:47 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28G2djo012490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:02:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28G2dkl085959 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 17:02:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28G2c4j085958; Thu, 8 Mar 2018 17:02:38 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 17:02:38 +0100 From: Bernd Walter To: bob prohaska Cc: ticso@cicely.de, freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308160238.GD80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <20180308094636.GA80981@cicely7.cicely.de> <20180308152611.GA61027@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308152611.GA61027@www.zefox.net> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:02:51 -0000 On Thu, Mar 08, 2018 at 07:26:11AM -0800, bob prohaska wrote: > On Thu, Mar 08, 2018 at 10:46:36AM +0100, Bernd Walter wrote: > > > > I'm currently very pleased with the SanDisk Extreme Plus micro SD > > cards. > > They are quite expensive, but behave way better with random writes. > > > I don't think I've seen Sandisk Extreme Plus devices, how do they differ > from "ordinary" Sandisk extreme devices? I think there is a "Pro" version, > is that the same thing? I don't know any other SanDisk Extreme SD cards than the Extreme Plus I have. The Ultra, I usually use, have those typical long delay problems, while the Extreme Plus never showed up in gstat with more than 100ms absolute worst case, usually below 25ms under random write load with 4-8MB/s datarate. Those I have are labeled as SDSQXBG-032G-GN6MA. > > Event better in random write performance are the SanDisk Extreme > > USB sticks. > > Also quite expensive though and quite big. > > > Likewise, my experiece, spread over 4 RPi2's and 2 RPi3's, has been good. > > > I can't tell, however, if they are better in case of power loss > > related data corruption. > > > > Never done a systematic test, but accidental unplugs and power cycles > after a crash have never caused problems fsck -f won't fix. I've had those problems with any kind of card I've used. This even happened for me with fully readonly mounted cards. Cards have to do ocassional refresh writes for reads, which means at low level there's no such thing as read-only, but it is amazing that customers even mange to catch those. The Extreme Plus however are new for me and I can't tell yet. At least they are way better during development. So far I've went to NFS, but NFS has a higher latency and 100MBit ethernet is slower than local cards could deliver. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 16:05:52 2018 Return-Path: Delivered-To: freebsd-arm@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 071C4F3F127 for ; Thu, 8 Mar 2018 16:05:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D1908251E for ; Thu, 8 Mar 2018 16:05:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28G5nd0007560 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:05:50 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28G5kO7012532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:05:46 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28G5kxR085975 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 17:05:46 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28G5klS085974; Thu, 8 Mar 2018 17:05:46 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 17:05:46 +0100 From: Bernd Walter To: =?iso-8859-1?Q?Mika=EBl?= Urankar Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: Webbrowser Message-ID: <20180308160546.GE80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180305165934.GH31939@cicely7.cicely.de> <20180305173240.GJ31939@cicely7.cicely.de> <20180306100121.GM31939@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:05:52 -0000 On Tue, Mar 06, 2018 at 11:04:06AM +0100, Mikaël Urankar wrote: > 2018-03-06 11:01 GMT+01:00 Bernd Walter : > > > On Mon, Mar 05, 2018 at 06:32:40PM +0100, Bernd Walter wrote: > > > On Mon, Mar 05, 2018 at 06:18:09PM +0100, Mikaël Urankar wrote: > > > > Le 5 mars 2018 18:00, "Bernd Walter" a > > écrit : > > > > > > > > It seems that there is not useable webbrowser for arm. > > > > I've tested 11.1 on a Pi2 and a recent current snapshot on a Pi3. > > > > The only brwosers I got running is billo and midori. > > > > The first one is practically unuseable these days and midori always > > > > crashes when the javascript engine starts. > > > > With javascript disabled midori runs fine, but I need JS. > > > > Did anyone already spend some time debugging this issue? > > > > > > > > > > > > The jit in webkit is broken on armv6/7, you need to recompile it with > > this > > > > configure flag: --disable-jit > > > > I created a PR for firefox-esr: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225279 > > > > > > Ok - this is a patch to get the JIT running in firefox? > > > A quick look showed that you do ${ARCH} == armv6 || ${ARCH} == armv7 > > > In my case I also see the problem on the pi3, which is arm64. > > > You may want to expand your patch, if you can test it. > > > > > > I will recompile webkit without jit. > > > Will take some hours to complete, so far I've used packages. > > > > Cool - that helped. > > Midori is now running with JS enabled. > > > Would you mind creating a PR for this issue? Will do - just give me a few days. > FYI firefox-esr builds fine on aarch64, > http://thunderx1.nyi.freebsd.org/data/head-arm64-default/p461032_s328914/logs/firefox-esr-52.6.0_3,1.log Didn't know. My first selection was based on available packages. But the aarch64 current packages are quite fresh, so maybe that's the reason. In my case I need a kiosk mode, which the Firefox only can do with a plugin, so it wasn't my first choice anyway. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 16:16:53 2018 Return-Path: Delivered-To: freebsd-arm@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 46F27F40180; Thu, 8 Mar 2018 16:16:53 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C85D382EC3; Thu, 8 Mar 2018 16:16:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28GGnbq007734 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:16:50 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28GGjFe012664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:16:45 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28GGja4086035 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 17:16:45 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28GGjjQ086034; Thu, 8 Mar 2018 17:16:45 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 17:16:45 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Cc: Bernd Walter Subject: webcamd based touchscreen problem on Pi3 Message-ID: <20180308161645.GF80981@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:16:53 -0000 Hardware is a Raspberry Pi3 with current r330034. I'm trying to run a USB touchscreen. Tested wmt and uep, but neither wants to attach, although the Waveshare display I'm using is likely running an egalaxy firmware. However webcamd accepts the device and creates a /dev/input/event0. But I can't get X to use it. xf86-input-evdev-2.10.5 is installed and it created an X config file under /usr/local/share/X11/xorg.conf.d/10-evdev.conf. I also tried some google results in /etc/X11/xorg.conf, but X never touches the device: [ 19417.932] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 19417.932] X Protocol Version 11, Revision 0 [ 19417.932] Build Operating System: FreeBSD 12.0-CURRENT arm64 [ 19417.932] Current Operating System: FreeBSD sa 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Mon Mar 5 16:28:19 UTC 2018 ticso@sa:/usr/obj/usr/src-nfs/builder/current-anlage/head/arm64.aarch64/sys/GENERIC arm64 [ 19417.933] Build Date: 19 January 2018 09:58:28PM [ 19417.934] [ 19417.934] Current version of pixman: 0.34.0 [ 19417.934] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 19417.934] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 19417.934] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 7 15:59:15 2018 [ 19417.935] (==) Using config file: "/etc/X11/xorg.conf" [ 19417.935] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [ 19417.936] (==) No Layout section. Using the first Screen section. [ 19417.936] (==) No screen section available. Using defaults. [ 19417.936] (**) |-->Screen "Default Screen Section" (0) [ 19417.936] (**) | |-->Monitor "" [ 19417.937] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 19417.938] (==) Automatically adding devices [ 19417.938] (==) Automatically enabling devices [ 19417.938] (==) Not automatically adding GPU devices [ 19417.938] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 19417.938] (==) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/ [ 19417.938] (==) ModulePath set to "/usr/local/lib/xorg/modules" [ 19417.938] (II) The server relies on devd to provide the list of input devices. If no devices become available, reconfigure devd or disable AutoAddDevices. [ 19417.938] (II) Loader magic: 0x1e0018 [ 19417.939] (II) Module ABI versions: [ 19417.939] X.Org ANSI C Emulation: 0.4 [ 19417.939] X.Org Video Driver: 20.0 [ 19417.939] X.Org XInput driver : 22.1 [ 19417.939] X.Org Server Extension : 9.0 [ 19417.939] (II) LoadModule: "glx" [ 19417.940] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 19417.951] (II) Module glx: vendor="X.Org Foundation" [ 19417.951] compiled for 1.18.4, module version = 1.0.0 [ 19417.951] ABI class: X.Org Server Extension, version 9.0 [ 19417.951] (==) AIGLX enabled [ 19417.951] (==) Matched modesetting as autoconfigured driver 0 [ 19417.951] (==) Matched scfb as autoconfigured driver 1 [ 19417.951] (==) Assigned the driver to the xf86ConfigLayout [ 19417.951] (II) LoadModule: "modesetting" [ 19417.952] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so [ 19417.952] (II) Module modesetting: vendor="X.Org Foundation" [ 19417.952] compiled for 1.18.4, module version = 1.18.4 [ 19417.952] Module class: X.Org Video Driver [ 19417.952] ABI class: X.Org Video Driver, version 20.0 [ 19417.952] (II) LoadModule: "scfb" [ 19417.953] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so [ 19417.953] (II) Module scfb: vendor="X.Org Foundation" [ 19417.953] compiled for 1.18.4, module version = 0.0.4 [ 19417.953] ABI class: X.Org Video Driver, version 20.0 [ 19417.954] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 19417.954] (II) scfb: driver for wsdisplay framebuffer: scfb [ 19417.954] (--) Using syscons driver with X support (version 2.0) [ 19417.954] (--) using VT number 2 [ 19417.954] (WW) Falling back to old probe method for modesetting [ 19417.955] (EE) open /dev/dri/card0: No such file or directory [ 19417.955] (WW) Falling back to old probe method for scfb [ 19417.955] scfb trace: probe start [ 19417.955] (II) scfb(0): using default device [ 19417.955] scfb trace: probe done [ 19417.955] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 19417.955] scfb: PreInit 0 [ 19417.955] (II) scfb(0): Using: depth (24), width (1280), height (800) [ 19417.956] (II) scfb(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/24 [ 19417.956] (==) scfb(0): Depth 24, (==) framebuffer bpp 24 [ 19417.956] (==) scfb(0): RGB weight 888 [ 19417.956] (==) scfb(0): Default visual is TrueColor [ 19417.956] (==) scfb(0): Using gamma correction (1.0, 1.0, 1.0) [ 19417.956] (II) scfb(0): Vidmem: 3000k [ 19417.956] (==) scfb(0): DPI set to (96, 96) [ 19417.956] (**) scfb(0): Using "Shadow Framebuffer" [ 19417.956] (II) Loading sub module "shadow" [ 19417.956] (II) LoadModule: "shadow" [ 19417.957] (II) Loading /usr/local/lib/xorg/modules/libshadow.so [ 19417.958] (II) Module shadow: vendor="X.Org Foundation" [ 19417.958] compiled for 1.18.4, module version = 1.1.0 [ 19417.958] ABI class: X.Org ANSI C Emulation, version 0.4 [ 19417.958] (II) Loading sub module "fb" [ 19417.958] (II) LoadModule: "fb" [ 19417.958] (II) Loading /usr/local/lib/xorg/modules/libfb.so [ 19417.960] (II) Module fb: vendor="X.Org Foundation" [ 19417.960] compiled for 1.18.4, module version = 1.0.0 [ 19417.961] ABI class: X.Org ANSI C Emulation, version 0.4 [ 19417.961] scfb: PreInit done [ 19417.961] (II) UnloadModule: "modesetting" [ 19417.961] (II) Unloading modesetting [ 19417.961] (--) Depth 24 pixmap format is 24 bpp [ 19417.961] scfb: ScfbScreenInit 0 [ 19417.961] bitsPerPixel=24, depth=24, defaultVisual=TrueColor mask: ff0000,ff00,ff, offset: 16,8,0 [ 19417.962] mmap returns: addr 0x41abb000 len 0x2ee000, fd 5, off 0 [ 19417.962] scfb: ScfbSave 0 [ 19417.962] scfb: ScfbSave done [ 19417.963] (==) scfb(0): Backing store enabled [ 19417.963] scfb: ScfbScreenInit done [ 19417.963] (==) RandR enabled [ 19417.964] (II) AIGLX: Screen 0 is not DRI2 capable [ 19417.964] (EE) AIGLX: reverting to software rendering [ 19418.375] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 19418.382] (II) AIGLX: Loaded and initialized swrast [ 19418.382] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 19419.556] (II) config/devd: probing input devices... [ 19419.556] (II) config/devd: adding input device (null) (/dev/kbdmux) [ 19419.556] (II) LoadModule: "kbd" [ 19419.558] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so [ 19419.558] (II) Module kbd: vendor="X.Org Foundation" [ 19419.558] compiled for 1.18.4, module version = 1.9.0 [ 19419.558] Module class: X.Org XInput Driver [ 19419.559] ABI class: X.Org XInput driver, version 22.1 [ 19419.559] (II) Using input driver 'kbd' for 'kbdmux' [ 19419.559] (**) kbdmux: always reports core events [ 19419.559] (**) kbdmux: always reports core events [ 19419.559] (**) Option "Protocol" "standard" [ 19419.559] (**) Option "XkbRules" "base" [ 19419.559] (**) Option "XkbModel" "pc105" [ 19419.559] (**) Option "XkbLayout" "us" [ 19419.559] (**) Option "config_info" "devd:kbdmux" [ 19419.560] (II) XINPUT: Adding extended input device "kbdmux" (type: KEYBOARD, id 6) [ 19419.562] (II) config/devd: adding input device (null) (/dev/sysmouse) [ 19419.562] (II) LoadModule: "mouse" [ 19419.563] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 19419.564] (II) Module mouse: vendor="X.Org Foundation" [ 19419.564] compiled for 1.18.4, module version = 1.9.2 [ 19419.564] Module class: X.Org XInput Driver [ 19419.564] ABI class: X.Org XInput driver, version 22.1 [ 19419.564] (II) Using input driver 'mouse' for 'sysmouse' [ 19419.565] (**) sysmouse: always reports core events [ 19419.565] (**) Option "Device" "/dev/sysmouse" [ 19419.565] (==) sysmouse: Protocol: "Auto" [ 19419.565] (**) sysmouse: always reports core events [ 19419.565] (==) sysmouse: Emulate3Buttons, Emulate3Timeout: 50 [ 19419.565] (**) sysmouse: ZAxisMapping: buttons 4 and 5 [ 19419.565] (**) sysmouse: Buttons: 5 [ 19419.565] (**) Option "config_info" "devd:sysmouse" [ 19419.566] (II) XINPUT: Adding extended input device "sysmouse" (type: MOUSE, id 7) [ 19419.566] (**) sysmouse: (accel) keeping acceleration scheme 1 [ 19419.566] (**) sysmouse: (accel) acceleration profile 0 [ 19419.566] (**) sysmouse: (accel) acceleration factor: 2.000 [ 19419.566] (**) sysmouse: (accel) acceleration threshold: 4 [ 19419.567] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 19419.567] (II) sysmouse: SetupAuto: protocol is SysMouse [ 19419.567] (II) config/devd: device /dev/ums0 already opened [67]sa# grep webcam /etc/rc.conf webcamd_enable="YES" webcamd_0_flags="-N BYZHYYZHY-By-ZH851 -M 0" #webcamd [-d ugen0.5] -N BYZHYYZHY-By-ZH851 -S P39112398 -M 0 [68]sa# ps -axl | grep webcam 0 592 1 0 -44 0 21736 1580 cuse-ser I http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 16:20:29 2018 Return-Path: Delivered-To: freebsd-arm@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 5671BF406BD; Thu, 8 Mar 2018 16:20:29 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 E390883298; Thu, 8 Mar 2018 16:20:28 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C2C7B2602E8; Thu, 8 Mar 2018 17:20:26 +0100 (CET) Subject: Re: webcamd based touchscreen problem on Pi3 To: ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Cc: Bernd Walter References: <20180308161645.GF80981@cicely7.cicely.de> From: Hans Petter Selasky Message-ID: <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> Date: Thu, 8 Mar 2018 17:20:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180308161645.GF80981@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:20:29 -0000 On 03/08/18 17:16, Bernd Walter wrote: > Hardware is a Raspberry Pi3 with current r330034. > I'm trying to run a USB touchscreen. > Tested wmt and uep, but neither wants to attach, although the Waveshare > display I'm using is likely running an egalaxy firmware. > However webcamd accepts the device and creates a /dev/input/event0. > But I can't get X to use it. > xf86-input-evdev-2.10.5 is installed and it created an X config file > under /usr/local/share/X11/xorg.conf.d/10-evdev.conf. > I also tried some google results in /etc/X11/xorg.conf, but X never > touches the device: > [ 19417.932] > X.Org X Server 1.18.4 > Release Date: 2016-07-19 > [ 19417.932] X Protocol Version 11, Revision 0 > [ 19417.932] Build Operating System: FreeBSD 12.0-CURRENT arm64 > [ 19417.932] Current Operating System: FreeBSD sa 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Mon Mar 5 16:28:19 UTC 2018 ticso@sa:/usr/obj/usr/src-nfs/builder/current-anlage/head/arm64.aarch64/sys/GENERIC arm64 > [ 19417.933] Build Date: 19 January 2018 09:58:28PM > [ 19417.934] > [ 19417.934] Current version of pixman: 0.34.0 > [ 19417.934] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 19417.934] Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 19417.934] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 7 15:59:15 2018 > [ 19417.935] (==) Using config file: "/etc/X11/xorg.conf" > [ 19417.935] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" > [ 19417.936] (==) No Layout section. Using the first Screen section. > [ 19417.936] (==) No screen section available. Using defaults. > [ 19417.936] (**) |-->Screen "Default Screen Section" (0) > [ 19417.936] (**) | |-->Monitor "" > [ 19417.937] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 19417.938] (==) Automatically adding devices > [ 19417.938] (==) Automatically enabling devices > [ 19417.938] (==) Not automatically adding GPU devices > [ 19417.938] (==) Max clients allowed: 256, resource mask: 0x1fffff > [ 19417.938] (==) FontPath set to: > /usr/local/share/fonts/misc/, > /usr/local/share/fonts/TTF/, > /usr/local/share/fonts/OTF/, > /usr/local/share/fonts/Type1/, > /usr/local/share/fonts/100dpi/, > /usr/local/share/fonts/75dpi/ > [ 19417.938] (==) ModulePath set to "/usr/local/lib/xorg/modules" > [ 19417.938] (II) The server relies on devd to provide the list of input devices. > If no devices become available, reconfigure devd or disable AutoAddDevices. > [ 19417.938] (II) Loader magic: 0x1e0018 > [ 19417.939] (II) Module ABI versions: > [ 19417.939] X.Org ANSI C Emulation: 0.4 > [ 19417.939] X.Org Video Driver: 20.0 > [ 19417.939] X.Org XInput driver : 22.1 > [ 19417.939] X.Org Server Extension : 9.0 > [ 19417.939] (II) LoadModule: "glx" > [ 19417.940] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so > [ 19417.951] (II) Module glx: vendor="X.Org Foundation" > [ 19417.951] compiled for 1.18.4, module version = 1.0.0 > [ 19417.951] ABI class: X.Org Server Extension, version 9.0 > [ 19417.951] (==) AIGLX enabled > [ 19417.951] (==) Matched modesetting as autoconfigured driver 0 > [ 19417.951] (==) Matched scfb as autoconfigured driver 1 > [ 19417.951] (==) Assigned the driver to the xf86ConfigLayout > [ 19417.951] (II) LoadModule: "modesetting" > [ 19417.952] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so > [ 19417.952] (II) Module modesetting: vendor="X.Org Foundation" > [ 19417.952] compiled for 1.18.4, module version = 1.18.4 > [ 19417.952] Module class: X.Org Video Driver > [ 19417.952] ABI class: X.Org Video Driver, version 20.0 > [ 19417.952] (II) LoadModule: "scfb" > [ 19417.953] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so > [ 19417.953] (II) Module scfb: vendor="X.Org Foundation" > [ 19417.953] compiled for 1.18.4, module version = 0.0.4 > [ 19417.953] ABI class: X.Org Video Driver, version 20.0 > [ 19417.954] (II) modesetting: Driver for Modesetting Kernel Drivers: kms > [ 19417.954] (II) scfb: driver for wsdisplay framebuffer: scfb > [ 19417.954] (--) Using syscons driver with X support (version 2.0) > [ 19417.954] (--) using VT number 2 > > [ 19417.954] (WW) Falling back to old probe method for modesetting > [ 19417.955] (EE) open /dev/dri/card0: No such file or directory > [ 19417.955] (WW) Falling back to old probe method for scfb > [ 19417.955] scfb trace: probe start > [ 19417.955] (II) scfb(0): using default device > [ 19417.955] scfb trace: probe done > [ 19417.955] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support > [ 19417.955] scfb: PreInit 0 > [ 19417.955] (II) scfb(0): Using: depth (24), width (1280), height (800) > [ 19417.956] (II) scfb(0): Creating default Display subsection in Screen section > "Default Screen Section" for depth/fbbpp 24/24 > [ 19417.956] (==) scfb(0): Depth 24, (==) framebuffer bpp 24 > [ 19417.956] (==) scfb(0): RGB weight 888 > [ 19417.956] (==) scfb(0): Default visual is TrueColor > [ 19417.956] (==) scfb(0): Using gamma correction (1.0, 1.0, 1.0) > [ 19417.956] (II) scfb(0): Vidmem: 3000k > [ 19417.956] (==) scfb(0): DPI set to (96, 96) > [ 19417.956] (**) scfb(0): Using "Shadow Framebuffer" > [ 19417.956] (II) Loading sub module "shadow" > [ 19417.956] (II) LoadModule: "shadow" > [ 19417.957] (II) Loading /usr/local/lib/xorg/modules/libshadow.so > [ 19417.958] (II) Module shadow: vendor="X.Org Foundation" > [ 19417.958] compiled for 1.18.4, module version = 1.1.0 > [ 19417.958] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 19417.958] (II) Loading sub module "fb" > [ 19417.958] (II) LoadModule: "fb" > [ 19417.958] (II) Loading /usr/local/lib/xorg/modules/libfb.so > [ 19417.960] (II) Module fb: vendor="X.Org Foundation" > [ 19417.960] compiled for 1.18.4, module version = 1.0.0 > [ 19417.961] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 19417.961] scfb: PreInit done > [ 19417.961] (II) UnloadModule: "modesetting" > [ 19417.961] (II) Unloading modesetting > [ 19417.961] (--) Depth 24 pixmap format is 24 bpp > [ 19417.961] scfb: ScfbScreenInit 0 > [ 19417.961] bitsPerPixel=24, depth=24, defaultVisual=TrueColor > mask: ff0000,ff00,ff, offset: 16,8,0 > [ 19417.962] mmap returns: addr 0x41abb000 len 0x2ee000, fd 5, off 0 > [ 19417.962] scfb: ScfbSave 0 > [ 19417.962] scfb: ScfbSave done > [ 19417.963] (==) scfb(0): Backing store enabled > [ 19417.963] scfb: ScfbScreenInit done > [ 19417.963] (==) RandR enabled > [ 19417.964] (II) AIGLX: Screen 0 is not DRI2 capable > [ 19417.964] (EE) AIGLX: reverting to software rendering > [ 19418.375] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer > [ 19418.382] (II) AIGLX: Loaded and initialized swrast > [ 19418.382] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 19419.556] (II) config/devd: probing input devices... > [ 19419.556] (II) config/devd: adding input device (null) (/dev/kbdmux) > [ 19419.556] (II) LoadModule: "kbd" > [ 19419.558] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so > [ 19419.558] (II) Module kbd: vendor="X.Org Foundation" > [ 19419.558] compiled for 1.18.4, module version = 1.9.0 > [ 19419.558] Module class: X.Org XInput Driver > [ 19419.559] ABI class: X.Org XInput driver, version 22.1 > [ 19419.559] (II) Using input driver 'kbd' for 'kbdmux' > [ 19419.559] (**) kbdmux: always reports core events > [ 19419.559] (**) kbdmux: always reports core events > [ 19419.559] (**) Option "Protocol" "standard" > [ 19419.559] (**) Option "XkbRules" "base" > [ 19419.559] (**) Option "XkbModel" "pc105" > [ 19419.559] (**) Option "XkbLayout" "us" > [ 19419.559] (**) Option "config_info" "devd:kbdmux" > [ 19419.560] (II) XINPUT: Adding extended input device "kbdmux" (type: KEYBOARD, id 6) > [ 19419.562] (II) config/devd: adding input device (null) (/dev/sysmouse) > [ 19419.562] (II) LoadModule: "mouse" > [ 19419.563] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so > [ 19419.564] (II) Module mouse: vendor="X.Org Foundation" > [ 19419.564] compiled for 1.18.4, module version = 1.9.2 > [ 19419.564] Module class: X.Org XInput Driver > [ 19419.564] ABI class: X.Org XInput driver, version 22.1 > [ 19419.564] (II) Using input driver 'mouse' for 'sysmouse' > [ 19419.565] (**) sysmouse: always reports core events > [ 19419.565] (**) Option "Device" "/dev/sysmouse" > [ 19419.565] (==) sysmouse: Protocol: "Auto" > [ 19419.565] (**) sysmouse: always reports core events > [ 19419.565] (==) sysmouse: Emulate3Buttons, Emulate3Timeout: 50 > [ 19419.565] (**) sysmouse: ZAxisMapping: buttons 4 and 5 > [ 19419.565] (**) sysmouse: Buttons: 5 > [ 19419.565] (**) Option "config_info" "devd:sysmouse" > [ 19419.566] (II) XINPUT: Adding extended input device "sysmouse" (type: MOUSE, id 7) > [ 19419.566] (**) sysmouse: (accel) keeping acceleration scheme 1 > [ 19419.566] (**) sysmouse: (accel) acceleration profile 0 > [ 19419.566] (**) sysmouse: (accel) acceleration factor: 2.000 > [ 19419.566] (**) sysmouse: (accel) acceleration threshold: 4 > [ 19419.567] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0 > [ 19419.567] (II) sysmouse: SetupAuto: protocol is SysMouse > [ 19419.567] (II) config/devd: device /dev/ums0 already opened > > [67]sa# grep webcam /etc/rc.conf > webcamd_enable="YES" > webcamd_0_flags="-N BYZHYYZHY-By-ZH851 -M 0" > #webcamd [-d ugen0.5] -N BYZHYYZHY-By-ZH851 -S P39112398 -M 0 > [68]sa# ps -axl | grep webcam > 0 592 1 0 -44 0 21736 1580 cuse-ser I 0 10267 738 0 21 0 11560 2640 - R+ 1 0:00.01 grep webcam > [69]sa# ls -la /dev/input/event0 > crw-rw---- 1 webcamd webcamd 0x6c Mar 7 10:35 /dev/input/event0 > See here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 --HPS From owner-freebsd-arm@freebsd.org Thu Mar 8 16:37:14 2018 Return-Path: Delivered-To: freebsd-arm@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 5DF18F420CB; Thu, 8 Mar 2018 16:37:14 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C5626844A9; Thu, 8 Mar 2018 16:37:13 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 58dcd093 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 8 Mar 2018 16:30:29 +0000 (UTC) Received: from localhost (markarth.lan [local]) by markarth.lan (OpenSMTPD) with ESMTPA id 9fe441cf; Thu, 8 Mar 2018 19:30:26 +0300 (MSK) Date: Thu, 8 Mar 2018 19:30:26 +0300 From: Greg To: Hans Petter Selasky Cc: ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> References: <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> OpenPGP: url=https://unrelenting.technology/pub/3B011BAF.asc User-Agent: the one that sucks less X-Hashcash: 1:20:180308:hps@selasky.org::lPXtTLw6Ufn3DaRr:1NRM X-Hashcash: 1:20:180308:freebsd-arm@freebsd.org::2p6xsw8qGTrWDsuF:0Y2C X-Hashcash: 1:20:180308:ticso@cicely7.cicely.de::6pxJbXR0l0jyRZKK:0Pkc X-Hashcash: 1:20:180308:ticso@cicely.de::M50k720fvpCplVMd:1FBf X-Hashcash: 1:20:180308:freebsd-current@freebsd.org::TRDzCR/pbT/Lqczs:cpw X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:37:14 -0000 On 03/08, Hans Petter Selasky wrote: >On 03/08/18 17:16, Bernd Walter wrote: >>Hardware is a Raspberry Pi3 with current r330034. >>I'm trying to run a USB touchscreen. >>Tested wmt and uep, but neither wants to attach, although the Waveshare >>display I'm using is likely running an egalaxy firmware. >>However webcamd accepts the device and creates a /dev/input/event0. >>But I can't get X to use it. >>xf86-input-evdev-2.10.5 is installed and it created an X config file >>under /usr/local/share/X11/xorg.conf.d/10-evdev.conf. >>I also tried some google results in /etc/X11/xorg.conf, but X never >>touches the device: > >See here: > >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 Or here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222609 But that's all about hotplug. It is definitely possible to manually configure the device on the stock xorg-server package. I can't say if the "google results" are correct without actually seeing them, but it should explicitly specify the /dev/input/event0 path. From owner-freebsd-arm@freebsd.org Thu Mar 8 16:46:13 2018 Return-Path: Delivered-To: freebsd-arm@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 40135F42D4E; Thu, 8 Mar 2018 16:46:13 +0000 (UTC) (envelope-from r.fernandez-cueto@bally-wulff.de) Received: from mail.bally-wulff.de (mail.bally-wulff.de [212.144.118.8]) by mx1.freebsd.org (Postfix) with ESMTP id AA55D84F59; Thu, 8 Mar 2018 16:46:12 +0000 (UTC) (envelope-from r.fernandez-cueto@bally-wulff.de) Received: from bw-ex-01.bally-wulff.de (bw-ex-01.bally-wulff.de [192.168.204.106]) by mail.bally-wulff.de (Postfix) with ESMTPS id 3F88F135; Thu, 8 Mar 2018 17:36:45 +0100 (CET) Received: from BWEPCFERNANDEZ (192.168.205.134) by BW-EX-01.bally-wulff.de (192.168.204.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1415.2; Thu, 8 Mar 2018 17:36:44 +0100 Date: Thu, 8 Mar 2018 17:36:06 +0100 From: Roberto Fernandez Cueto To: CC: , , Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308163605.GA61875@BWEPCFERNANDEZ> References: <20180308161645.GF80981@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20180308161645.GF80981@cicely7.cicely.de> User-Agent: Mutt/1.9.1 (2017-09-22) X-ClientProxiedBy: BW-EX-01.bally-wulff.de (192.168.204.106) To BW-EX-01.bally-wulff.de (192.168.204.106) X-OLX-Disclaimer: BW-EX-01.BALLY-WULFF.DE Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:46:13 -0000 Roberto Fernandez-Cueto schrieb am 08.03.2018 17:36 _____________________________________________________________________ You have to explicitely tell Xorg that you want to use the touch with the layout. Something like, Section "ServerLayout" Identifier "MyLayout" InputDevice "touchscreen" EndSection On Thu, Mar 08, 2018 at 05:16:45PM +0100, Bernd Walter wrote: > Hardware is a Raspberry Pi3 with current r330034. > I'm trying to run a USB touchscreen. > Tested wmt and uep, but neither wants to attach, although the Waveshare > display I'm using is likely running an egalaxy firmware. > However webcamd accepts the device and creates a /dev/input/event0. > But I can't get X to use it. > xf86-input-evdev-2.10.5 is installed and it created an X config file > under /usr/local/share/X11/xorg.conf.d/10-evdev.conf. > I also tried some google results in /etc/X11/xorg.conf, but X never > touches the device: > [ 19417.932]=20 > X.Org X Server 1.18.4 > Release Date: 2016-07-19 > [ 19417.932] X Protocol Version 11, Revision 0 > [ 19417.932] Build Operating System: FreeBSD 12.0-CURRENT arm64=20 > [ 19417.932] Current Operating System: FreeBSD sa 12.0-CURRENT FreeBSD 12= .0-CURRENT #0: Mon Mar 5 16:28:19 UTC 2018 ticso@sa:/usr/obj/usr/src-n= fs/builder/current-anlage/head/arm64.aarch64/sys/GENERIC arm64 > [ 19417.933] Build Date: 19 January 2018 09:58:28PM > [ 19417.934] =20 > [ 19417.934] Current version of pixman: 0.34.0 > [ 19417.934] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 19417.934] Markers: (--) probed, (**) from config file, (=3D=3D) defaul= t setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 19417.934] (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 7 1= 5:59:15 2018 > [ 19417.935] (=3D=3D) Using config file: "/etc/X11/xorg.conf" > [ 19417.935] (=3D=3D) Using system config directory "/usr/local/share/X11= /xorg.conf.d" > [ 19417.936] (=3D=3D) No Layout section. Using the first Screen section. > [ 19417.936] (=3D=3D) No screen section available. Using defaults. > [ 19417.936] (**) |-->Screen "Default Screen Section" (0) > [ 19417.936] (**) | |-->Monitor "" > [ 19417.937] (=3D=3D) No monitor specified for screen "Default Screen Sec= tion". > Using a default monitor configuration. > [ 19417.938] (=3D=3D) Automatically adding devices > [ 19417.938] (=3D=3D) Automatically enabling devices > [ 19417.938] (=3D=3D) Not automatically adding GPU devices > [ 19417.938] (=3D=3D) Max clients allowed: 256, resource mask: 0x1fffff > [ 19417.938] (=3D=3D) FontPath set to: > /usr/local/share/fonts/misc/, > /usr/local/share/fonts/TTF/, > /usr/local/share/fonts/OTF/, > /usr/local/share/fonts/Type1/, > /usr/local/share/fonts/100dpi/, > /usr/local/share/fonts/75dpi/ > [ 19417.938] (=3D=3D) ModulePath set to "/usr/local/lib/xorg/modules" > [ 19417.938] (II) The server relies on devd to provide the list of input = devices. > If no devices become available, reconfigure devd or disable AutoA= ddDevices. > [ 19417.938] (II) Loader magic: 0x1e0018 > [ 19417.939] (II) Module ABI versions: > [ 19417.939] X.Org ANSI C Emulation: 0.4 > [ 19417.939] X.Org Video Driver: 20.0 > [ 19417.939] X.Org XInput driver : 22.1 > [ 19417.939] X.Org Server Extension : 9.0 > [ 19417.939] (II) LoadModule: "glx" > [ 19417.940] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.s= o > [ 19417.951] (II) Module glx: vendor=3D"X.Org Foundation" > [ 19417.951] compiled for 1.18.4, module version =3D 1.0.0 > [ 19417.951] ABI class: X.Org Server Extension, version 9.0 > [ 19417.951] (=3D=3D) AIGLX enabled > [ 19417.951] (=3D=3D) Matched modesetting as autoconfigured driver 0 > [ 19417.951] (=3D=3D) Matched scfb as autoconfigured driver 1 > [ 19417.951] (=3D=3D) Assigned the driver to the xf86ConfigLayout > [ 19417.951] (II) LoadModule: "modesetting" > [ 19417.952] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting= _drv.so > [ 19417.952] (II) Module modesetting: vendor=3D"X.Org Foundation" > [ 19417.952] compiled for 1.18.4, module version =3D 1.18.4 > [ 19417.952] Module class: X.Org Video Driver > [ 19417.952] ABI class: X.Org Video Driver, version 20.0 > [ 19417.952] (II) LoadModule: "scfb" > [ 19417.953] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so > [ 19417.953] (II) Module scfb: vendor=3D"X.Org Foundation" > [ 19417.953] compiled for 1.18.4, module version =3D 0.0.4 > [ 19417.953] ABI class: X.Org Video Driver, version 20.0 > [ 19417.954] (II) modesetting: Driver for Modesetting Kernel Drivers: kms > [ 19417.954] (II) scfb: driver for wsdisplay framebuffer: scfb > [ 19417.954] (--) Using syscons driver with X support (version 2.0) > [ 19417.954] (--) using VT number 2 >=20 > [ 19417.954] (WW) Falling back to old probe method for modesetting > [ 19417.955] (EE) open /dev/dri/card0: No such file or directory > [ 19417.955] (WW) Falling back to old probe method for scfb > [ 19417.955] scfb trace: probe start > [ 19417.955] (II) scfb(0): using default device > [ 19417.955] scfb trace: probe done > [ 19417.955] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card = support > [ 19417.955] scfb: PreInit 0 > [ 19417.955] (II) scfb(0): Using: depth (24), width (1280), height (= 800) > [ 19417.956] (II) scfb(0): Creating default Display subsection in Screen = section > "Default Screen Section" for depth/fbbpp 24/24 > [ 19417.956] (=3D=3D) scfb(0): Depth 24, (=3D=3D) framebuffer bpp 24 > [ 19417.956] (=3D=3D) scfb(0): RGB weight 888 > [ 19417.956] (=3D=3D) scfb(0): Default visual is TrueColor > [ 19417.956] (=3D=3D) scfb(0): Using gamma correction (1.0, 1.0, 1.0) > [ 19417.956] (II) scfb(0): Vidmem: 3000k > [ 19417.956] (=3D=3D) scfb(0): DPI set to (96, 96) > [ 19417.956] (**) scfb(0): Using "Shadow Framebuffer" > [ 19417.956] (II) Loading sub module "shadow" > [ 19417.956] (II) LoadModule: "shadow" > [ 19417.957] (II) Loading /usr/local/lib/xorg/modules/libshadow.so > [ 19417.958] (II) Module shadow: vendor=3D"X.Org Foundation" > [ 19417.958] compiled for 1.18.4, module version =3D 1.1.0 > [ 19417.958] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 19417.958] (II) Loading sub module "fb" > [ 19417.958] (II) LoadModule: "fb" > [ 19417.958] (II) Loading /usr/local/lib/xorg/modules/libfb.so > [ 19417.960] (II) Module fb: vendor=3D"X.Org Foundation" > [ 19417.960] compiled for 1.18.4, module version =3D 1.0.0 > [ 19417.961] ABI class: X.Org ANSI C Emulation, version 0.4 > [ 19417.961] scfb: PreInit done > [ 19417.961] (II) UnloadModule: "modesetting" > [ 19417.961] (II) Unloading modesetting > [ 19417.961] (--) Depth 24 pixmap format is 24 bpp > [ 19417.961] scfb: ScfbScreenInit 0 > [ 19417.961] bitsPerPixel=3D24, depth=3D24, defaultVisual=3DTrueColor > mask: ff0000,ff00,ff, offset: 16,8,0 > [ 19417.962] mmap returns: addr 0x41abb000 len 0x2ee000, fd 5, off 0 > [ 19417.962] scfb: ScfbSave 0 > [ 19417.962] scfb: ScfbSave done > [ 19417.963] (=3D=3D) scfb(0): Backing store enabled > [ 19417.963] scfb: ScfbScreenInit done > [ 19417.963] (=3D=3D) RandR enabled > [ 19417.964] (II) AIGLX: Screen 0 is not DRI2 capable > [ 19417.964] (EE) AIGLX: reverting to software rendering > [ 19418.375] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer > [ 19418.382] (II) AIGLX: Loaded and initialized swrast > [ 19418.382] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 19419.556] (II) config/devd: probing input devices... > [ 19419.556] (II) config/devd: adding input device (null) (/dev/kbdmux) > [ 19419.556] (II) LoadModule: "kbd" > [ 19419.558] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so > [ 19419.558] (II) Module kbd: vendor=3D"X.Org Foundation" > [ 19419.558] compiled for 1.18.4, module version =3D 1.9.0 > [ 19419.558] Module class: X.Org XInput Driver > [ 19419.559] ABI class: X.Org XInput driver, version 22.1 > [ 19419.559] (II) Using input driver 'kbd' for 'kbdmux' > [ 19419.559] (**) kbdmux: always reports core events > [ 19419.559] (**) kbdmux: always reports core events > [ 19419.559] (**) Option "Protocol" "standard" > [ 19419.559] (**) Option "XkbRules" "base" > [ 19419.559] (**) Option "XkbModel" "pc105" > [ 19419.559] (**) Option "XkbLayout" "us" > [ 19419.559] (**) Option "config_info" "devd:kbdmux" > [ 19419.560] (II) XINPUT: Adding extended input device "kbdmux" (type: KE= YBOARD, id 6) > [ 19419.562] (II) config/devd: adding input device (null) (/dev/sysmouse) > [ 19419.562] (II) LoadModule: "mouse" > [ 19419.563] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so > [ 19419.564] (II) Module mouse: vendor=3D"X.Org Foundation" > [ 19419.564] compiled for 1.18.4, module version =3D 1.9.2 > [ 19419.564] Module class: X.Org XInput Driver > [ 19419.564] ABI class: X.Org XInput driver, version 22.1 > [ 19419.564] (II) Using input driver 'mouse' for 'sysmouse' > [ 19419.565] (**) sysmouse: always reports core events > [ 19419.565] (**) Option "Device" "/dev/sysmouse" > [ 19419.565] (=3D=3D) sysmouse: Protocol: "Auto" > [ 19419.565] (**) sysmouse: always reports core events > [ 19419.565] (=3D=3D) sysmouse: Emulate3Buttons, Emulate3Timeout: 50 > [ 19419.565] (**) sysmouse: ZAxisMapping: buttons 4 and 5 > [ 19419.565] (**) sysmouse: Buttons: 5 > [ 19419.565] (**) Option "config_info" "devd:sysmouse" > [ 19419.566] (II) XINPUT: Adding extended input device "sysmouse" (type: = MOUSE, id 7) > [ 19419.566] (**) sysmouse: (accel) keeping acceleration scheme 1 > [ 19419.566] (**) sysmouse: (accel) acceleration profile 0 > [ 19419.566] (**) sysmouse: (accel) acceleration factor: 2.000 > [ 19419.566] (**) sysmouse: (accel) acceleration threshold: 4 > [ 19419.567] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0 > [ 19419.567] (II) sysmouse: SetupAuto: protocol is SysMouse > [ 19419.567] (II) config/devd: device /dev/ums0 already opened >=20 > [67]sa# grep webcam /etc/rc.conf > webcamd_enable=3D"YES" > webcamd_0_flags=3D"-N BYZHYYZHY-By-ZH851 -M 0" > #webcamd [-d ugen0.5] -N BYZHYYZHY-By-ZH851 -S P39112398 -M 0 > [68]sa# ps -axl | grep webcam > 0 592 1 0 -44 0 21736 1580 cuse-ser I 0 10267 738 0 21 0 11560 2640 - R+ 1 0:00.01 grep = webcam > [69]sa# ls -la /dev/input/event0=20 > crw-rw---- 1 webcamd webcamd 0x6c Mar 7 10:35 /dev/input/event0 >=20 > --=20 > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " BALLY WULFF Games & Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, Po= stanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: 030-62= 0 02-200, Geschaeftsfuehrer: Thomas Niehenke, Lars Rogge, Thomas Wendt, Amt= sgericht Berlin-Charlottenburg HRB 139020 B, UST-IdNr. DE815328376 _____________________________________________________________________ Dieses E-Mail ist nur fuer den Empfaenger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- aeusserung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Games & Entertainment GmbH dar. Sind Sie nicht der Empfaenger, so haben Sie diese E-Mail irrtuemlich erhalten und jegliche Verwendung, Veroeffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Games & Entertainment GmbH noch der Absender uebernehmen die Haftung fuer Viren. Es obliegt Ihrer Verantwortung, die E-Mail und deren Anhaenge auf Viren zu pruefen. Anhaenge: _____________________________________________________________________ Versand am 08.03.2018 17:36 von Fernandez-Cueto Roberto From owner-freebsd-arm@freebsd.org Thu Mar 8 16:49:50 2018 Return-Path: Delivered-To: freebsd-arm@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 6DCA0F4310F for ; Thu, 8 Mar 2018 16:49:50 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [IPv6:2605:2700:0:3:a800:ff:fee9:2feb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA4AE85253 for ; Thu, 8 Mar 2018 16:49:49 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 11b2ed77 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 8 Mar 2018 16:49:48 +0000 (UTC) Received: from localhost (markarth.lan [local]) by markarth.lan (OpenSMTPD) with ESMTPA id 34a2d396; Thu, 8 Mar 2018 19:49:45 +0300 (MSK) Date: Thu, 8 Mar 2018 19:49:45 +0300 From: Greg To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org Subject: Re: Rock64 status Message-ID: <20180308164945.p33ofc2njtjhqhj2@unrelenting.technology> References: <20180226224214.64b14ec9f016f713cd8dec6f@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20180226224214.64b14ec9f016f713cd8dec6f@bidouilliste.com> OpenPGP: url=https://unrelenting.technology/pub/3B011BAF.asc User-Agent: the one that sucks less X-Hashcash: 1:20:180308:freebsd-arm@freebsd.org::/rlW+klnrf5Y1JES:1fxX X-Hashcash: 1:20:180308:manu@bidouilliste.com::i9MK3FEmCep4v97/:AJ5W X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 16:49:50 -0000 On 02/26, Emmanuel Vadot wrote: >This u-boot is based on 2017.09 which have some problems with EFI block >devices, this means that using boot1.efi or loader.efi from the sdcard >will fail. However netbooting works like a charm and for now this is >perfect for me as I don't want to swap sdcard when doing kernel dev. >I hope that the u-boot status will change soon. Hi! Finally got around to trying to boot my ROCK64. Trying to netboot the March 7 current snapshot, the loader doesn't work: => bootefi ${kernel_addr_r} ${fdt_addr_r} ## Starting EFI application at 02000000 ... Consoles: EFI console efipart_inithandles failed 2, expect failuresCommand line arguments: loader.efi Image base: 0x2000000 EFI version: 2.05 EFI Firmware: Das U-boot (rev 0.00) FreeBSD/arm64 EFI loader, Revision 1.1 (Wed Mar 7 17:24:53 UTC 2018 root@releng3.nyi.freebsd.org) ## Application terminated, r = 14 Replacing loader.efi with an older one (the one I use on the RPi3) gets me into the loader prompt, but the network doesn't work: FreeBSD/arm64 EFI loader, Revision 1.1 (Thu Jan 11 15:18:47 UTC 2018 root@releng3.nyi.freebsd.org) Speed: 1000, full duplex \ can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. The u-boot version is: U-Boot 2017.09-ga0a2b48 (Mar 04 2018 - 20:21:36 +0000), Build: jenkins-linux-build-rock-64-193 From owner-freebsd-arm@freebsd.org Thu Mar 8 19:11:41 2018 Return-Path: Delivered-To: freebsd-arm@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 79644F4D137; Thu, 8 Mar 2018 19:11:41 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0954B6B76E; Thu, 8 Mar 2018 19:11:40 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28JBaU9011438 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 20:11:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28JBX4U015012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 20:11:33 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28JBWKo086818 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 20:11:32 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28JBVYR086817; Thu, 8 Mar 2018 20:11:31 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 20:11:31 +0100 From: Bernd Walter To: Greg , Roberto Fernandez Cueto Cc: Hans Petter Selasky , ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308191131.GB86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 19:11:41 -0000 On Thu, Mar 08, 2018 at 07:30:26PM +0300, Greg wrote: > On 03/08, Hans Petter Selasky wrote: > >On 03/08/18 17:16, Bernd Walter wrote: > >>Hardware is a Raspberry Pi3 with current r330034. > >>I'm trying to run a USB touchscreen. > >>Tested wmt and uep, but neither wants to attach, although the Waveshare > >>display I'm using is likely running an egalaxy firmware. > >>However webcamd accepts the device and creates a /dev/input/event0. > >>But I can't get X to use it. > >>xf86-input-evdev-2.10.5 is installed and it created an X config file > >>under /usr/local/share/X11/xorg.conf.d/10-evdev.conf. > >>I also tried some google results in /etc/X11/xorg.conf, but X never > >>touches the device: > > > >See here: > > > >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 > > Or here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222609 > > But that's all about hotplug. It is definitely possible to manually > configure the device on the stock xorg-server package. I can't say if > the "google results" are correct without actually seeing them, but it > should explicitly specify the /dev/input/event0 path. Thank you both for the links. I'd already seen them and had been a bit confused if they are required or not and also found references that a manual configuration should work. On Thu, Mar 08, 2018 at 05:36:06PM +0100, Roberto Fernandez Cueto wrote: > Roberto Fernandez-Cueto schrieb am 08.03.2018 17:36 > _____________________________________________________________________ > > You have to explicitely tell Xorg that you want to use the touch with > the layout. > > Something like, > > Section "ServerLayout" > Identifier "MyLayout" > InputDevice "touchscreen" > EndSection Thank you - this was the missing link, why my static configuration failed. I'd only setup the InputDevice section. This is what I have right now: [20]sa# cat /etc/X11/xorg.conf Section "InputDevice" Identifier "Touchscreen" Driver "evdev" Option "Device" "/dev/input/event0" EndSection Section "ServerLayout" Identifier "MyLayout" InputDevice "Touchscreen" EndSection Unfortunately now I face the next problem. [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen' [112753.536] (**) evdev touchscreen: always reports core events [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0" [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5 [112753.598] (--) evdev: evdev touchscreen: Found absolute axes [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one. [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5 [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" (type: TOUCHSCREEN, id 6) [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes. [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1 [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0 [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000 [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4 [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument [26]sa-moeller> xinput Virtual core pointer id=2 [master pointer (3)] Virtual core XTEST pointer id=4 [slave pointer (2)] Touchscreen id=6 [slave pointer (2)] sysmouse id=8 [slave pointer (2)] Virtual core keyboard id=3 [master keyboard (2)] Virtual core XTEST keyboard id=5 [slave keyboard (3)] kbdmux id=7 [slave keyboard (3)] Everything looks good so far, at least in my eyes. Well - wheel emulation and such sounds a bit strange, as if it is handled as a touchpad and not like a touchscreen. But it says type touchscreen, so I assume that's ok. However, I get no touch events. I've started xev fullscreen and still nothing. Somewhere else I've read that /dev/input/event0 should deliver something if read and a touch happens, but this is not the case for me. Any ideas how I can debug this thing? There was a reference somewhere about a commandline programm to run against an evdev, but I can't find it anymore. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 20:08:58 2018 Return-Path: Delivered-To: freebsd-arm@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 2674BF2BEB5; Thu, 8 Mar 2018 20:08:58 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9110B6E38B; Thu, 8 Mar 2018 20:08:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28K8rhd012275 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 21:08:53 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28K8oFY015755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 21:08:50 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28K8n52087094 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 21:08:49 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28K8nl9087093; Thu, 8 Mar 2018 21:08:49 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 21:08:49 +0100 From: Bernd Walter To: Greg , Roberto Fernandez Cueto Cc: Hans Petter Selasky , ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308200849.GC86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308191131.GB86413@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 20:08:58 -0000 On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > This is what I have right now: > [20]sa# cat /etc/X11/xorg.conf > > Section "InputDevice" > Identifier "Touchscreen" > Driver "evdev" > Option "Device" "/dev/input/event0" > EndSection > > Section "ServerLayout" > Identifier "MyLayout" > InputDevice "Touchscreen" > EndSection > > > Unfortunately now I face the next problem. > > [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen' > [112753.536] (**) evdev touchscreen: always reports core events > [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0" > [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5 > [112753.598] (--) evdev: evdev touchscreen: Found absolute axes > [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes > [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one. > [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes > [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen > [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen > [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5 > [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 > [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" (type: TOUCHSCREEN, id 6) > [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes. > [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1 > [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0 > [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000 > [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4 > [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument > > [26]sa-moeller> xinput > Virtual core pointer id=2 [master pointer (3)] > Virtual core XTEST pointer id=4 [slave pointer (2)] > Touchscreen id=6 [slave pointer (2)] > sysmouse id=8 [slave pointer (2)] > Virtual core keyboard id=3 [master keyboard (2)] > Virtual core XTEST keyboard id=5 [slave keyboard (3)] > kbdmux id=7 [slave keyboard (3)] > > Everything looks good so far, at least in my eyes. > Well - wheel emulation and such sounds a bit strange, as if it is handled > as a touchpad and not like a touchscreen. > But it says type touchscreen, so I assume that's ok. > However, I get no touch events. > I've started xev fullscreen and still nothing. > > Somewhere else I've read that /dev/input/event0 should deliver something > if read and a touch happens, but this is not the case for me. > > Any ideas how I can debug this thing? > There was a reference somewhere about a commandline programm to run against > an evdev, but I can't find it anymore. xinput test delivers nothing on the touchscreen. Neither evtest nor evdev-dump compiles because they are both missing linux include files at some point. https://cgit.freedesktop.org/~whot/evtest/ [48]sa> make make all-am cc -DHAVE_CONFIG_H -I. -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c -o evtest.o evtest.c evtest.c:46:10: fatal error: 'linux/version.h' file not found #include ^~~~~~~~~~~~~~~~~ 1 error generated. *** Error code 1 Stop. make[1]: stopped in /home/ticso/evtest *** Error code 1 Stop. make: stopped in /home/ticso/evtest Exit 1 https://github.com/gonzoua/evdev-dump/tree/freebsd ... checking for unistd.h... yes checking linux/input.h usability... no checking linux/input.h presence... no checking for linux/input.h... no checking for /usr/include/linux/input.h... no configure: error: /usr/include/linux/input.h not found 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w Exit 1 The touchscreen itself should be functional as it has a touch area outside the display, which is interpreted by the USB controller to change the backlight. The exact same display also worked fine on Raspbian. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 20:38:52 2018 Return-Path: Delivered-To: freebsd-arm@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 7D61EF2E3F1; Thu, 8 Mar 2018 20:38:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 128F76F500; Thu, 8 Mar 2018 20:38:51 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1eu2JE-000Pi8-VO; Thu, 08 Mar 2018 12:38:42 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w28Kcce3098829; Thu, 8 Mar 2018 12:38:38 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 8 Mar 2018 12:38:38 -0800 From: Oleksandr Tymoshenko To: ticso@cicely.de Cc: Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308203838.GA98731@bluezbox.com> References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308200849.GC86413@cicely7.cicely.de> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > https://github.com/gonzoua/evdev-dump/tree/freebsd > ... > checking for unistd.h... yes [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 20:38:52 -0000 Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > https://github.com/gonzoua/evdev-dump/tree/freebsd > ... > checking for unistd.h... yes > checking linux/input.h usability... no > checking linux/input.h presence... no > checking for linux/input.h... no > checking for /usr/include/linux/input.h... no > configure: error: /usr/include/linux/input.h not found > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > Exit 1 I've just checked, evdev-dump should be buildable: git clone git@github.com:gonzoua/evdev-dump.git cd evdev-dump git checkout freebsd sudo pkg install gawk gmake sh bootstrap ./configure gmake -- gonzo From owner-freebsd-arm@freebsd.org Thu Mar 8 21:08:26 2018 Return-Path: Delivered-To: freebsd-arm@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 2DB98F307D4; Thu, 8 Mar 2018 21:08:26 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AEE6706AA; Thu, 8 Mar 2018 21:08:25 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28L8AFh013155 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 22:08:10 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28L86Nc016503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 22:08:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28L86KF087380 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 22:08:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28L85SP087379; Thu, 8 Mar 2018 22:08:05 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 22:08:05 +0100 From: Bernd Walter To: Greg , Roberto Fernandez Cueto Cc: Hans Petter Selasky , ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308210805.GE86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308200849.GC86413@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 21:08:26 -0000 On Thu, Mar 08, 2018 at 09:08:49PM +0100, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > This is what I have right now: > > [20]sa# cat /etc/X11/xorg.conf > > > > Section "InputDevice" > > Identifier "Touchscreen" > > Driver "evdev" > > Option "Device" "/dev/input/event0" > > EndSection > > > > Section "ServerLayout" > > Identifier "MyLayout" > > InputDevice "Touchscreen" > > EndSection > > > > > > Unfortunately now I face the next problem. > > > > [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen' > > [112753.536] (**) evdev touchscreen: always reports core events > > [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0" > > [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5 > > [112753.598] (--) evdev: evdev touchscreen: Found absolute axes > > [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes > > [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one. > > [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes > > [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen > > [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen > > [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5 > > [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 > > [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" (type: TOUCHSCREEN, id 6) > > [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes. > > [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1 > > [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0 > > [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000 > > [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4 > > [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument > > > > [26]sa-moeller> xinput > > Virtual core pointer id=2 [master pointer (3)] > > Virtual core XTEST pointer id=4 [slave pointer (2)] > > Touchscreen id=6 [slave pointer (2)] > > sysmouse id=8 [slave pointer (2)] > > Virtual core keyboard id=3 [master keyboard (2)] > > Virtual core XTEST keyboard id=5 [slave keyboard (3)] > > kbdmux id=7 [slave keyboard (3)] > > > > Everything looks good so far, at least in my eyes. > > Well - wheel emulation and such sounds a bit strange, as if it is handled > > as a touchpad and not like a touchscreen. > > But it says type touchscreen, so I assume that's ok. > > However, I get no touch events. > > I've started xev fullscreen and still nothing. > > > > Somewhere else I've read that /dev/input/event0 should deliver something > > if read and a touch happens, but this is not the case for me. > > > > Any ideas how I can debug this thing? > > There was a reference somewhere about a commandline programm to run against > > an evdev, but I can't find it anymore. > > xinput test delivers nothing on the touchscreen. > > Neither evtest nor evdev-dump compiles because they are both missing > linux include files at some point. > https://cgit.freedesktop.org/~whot/evtest/ > [48]sa> make > make all-am > cc -DHAVE_CONFIG_H -I. -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c -o evtest.o evtest.c > evtest.c:46:10: fatal error: 'linux/version.h' file not found > #include > ^~~~~~~~~~~~~~~~~ > 1 error generated. > *** Error code 1 > > Stop. > make[1]: stopped in /home/ticso/evtest > *** Error code 1 > > Stop. > make: stopped in /home/ticso/evtest > Exit 1 > > https://github.com/gonzoua/evdev-dump/tree/freebsd > ... > checking for unistd.h... yes > checking linux/input.h usability... no > checking linux/input.h presence... no > checking for linux/input.h... no > checking for /usr/include/linux/input.h... no > configure: error: /usr/include/linux/input.h not found > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > Exit 1 > > The touchscreen itself should be functional as it has a touch area outside > the display, which is interpreted by the USB controller to change the > backlight. > The exact same display also worked fine on Raspbian. This is with webcamd compiled with debug support. [18]sa# /usr/local/sbin/webcamd -d ugen0.5 Linux video capture interface: v2.00 IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR LIRC bridge handler initialized IR XMP protocol handler initialized b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully USB Video Class driver (1.1.1) cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1 pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner pvrusb2: Debug mask is 31 (0x1f) USBVision USB Video Device Driver for Linux : 0.9.11 Attached to ugen0.5[0] INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-/dev/usb-/dev/usb/input0 DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0 Creating /dev/input/event0 I really think that it has some problems with the controller. When I run webcamd against the mouse I get some kind data from the evdev. Well - I had to reboot after testing with the mouse, but probably it was disabled by default for a reason. So my assumption is that I have to look up my problem somewhere between webcamd and the USB device. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 21:10:53 2018 Return-Path: Delivered-To: freebsd-arm@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 1DE74F30A24; Thu, 8 Mar 2018 21:10:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 A4CAD70852; Thu, 8 Mar 2018 21:10:52 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 56180260B8A; Thu, 8 Mar 2018 22:10:50 +0100 (CET) Subject: Re: webcamd based touchscreen problem on Pi3 To: ticso@cicely.de, Greg , Roberto Fernandez Cueto Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> From: Hans Petter Selasky Message-ID: Date: Thu, 8 Mar 2018 22:10:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180308210805.GE86413@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 21:10:53 -0000 On 03/08/18 22:08, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 09:08:49PM +0100, Bernd Walter wrote: >> On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: >>> This is what I have right now: >>> [20]sa# cat /etc/X11/xorg.conf >>> >>> Section "InputDevice" >>> Identifier "Touchscreen" >>> Driver "evdev" >>> Option "Device" "/dev/input/event0" >>> EndSection >>> >>> Section "ServerLayout" >>> Identifier "MyLayout" >>> InputDevice "Touchscreen" >>> EndSection >>> >>> >>> Unfortunately now I face the next problem. >>> >>> [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen' >>> [112753.536] (**) evdev touchscreen: always reports core events >>> [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0" >>> [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5 >>> [112753.598] (--) evdev: evdev touchscreen: Found absolute axes >>> [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes >>> [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one. >>> [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes >>> [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen >>> [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen >>> [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5 >>> [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 >>> [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" (type: TOUCHSCREEN, id 6) >>> [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes. >>> [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1 >>> [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0 >>> [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000 >>> [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4 >>> [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument >>> >>> [26]sa-moeller> xinput >>> Virtual core pointer id=2 [master pointer (3)] >>> Virtual core XTEST pointer id=4 [slave pointer (2)] >>> Touchscreen id=6 [slave pointer (2)] >>> sysmouse id=8 [slave pointer (2)] >>> Virtual core keyboard id=3 [master keyboard (2)] >>> Virtual core XTEST keyboard id=5 [slave keyboard (3)] >>> kbdmux id=7 [slave keyboard (3)] >>> >>> Everything looks good so far, at least in my eyes. >>> Well - wheel emulation and such sounds a bit strange, as if it is handled >>> as a touchpad and not like a touchscreen. >>> But it says type touchscreen, so I assume that's ok. >>> However, I get no touch events. >>> I've started xev fullscreen and still nothing. >>> >>> Somewhere else I've read that /dev/input/event0 should deliver something >>> if read and a touch happens, but this is not the case for me. >>> >>> Any ideas how I can debug this thing? >>> There was a reference somewhere about a commandline programm to run against >>> an evdev, but I can't find it anymore. >> >> xinput test delivers nothing on the touchscreen. >> >> Neither evtest nor evdev-dump compiles because they are both missing >> linux include files at some point. >> https://cgit.freedesktop.org/~whot/evtest/ >> [48]sa> make >> make all-am >> cc -DHAVE_CONFIG_H -I. -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c -o evtest.o evtest.c >> evtest.c:46:10: fatal error: 'linux/version.h' file not found >> #include >> ^~~~~~~~~~~~~~~~~ >> 1 error generated. >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /home/ticso/evtest >> *** Error code 1 >> >> Stop. >> make: stopped in /home/ticso/evtest >> Exit 1 >> >> https://github.com/gonzoua/evdev-dump/tree/freebsd >> ... >> checking for unistd.h... yes >> checking linux/input.h usability... no >> checking linux/input.h presence... no >> checking for linux/input.h... no >> checking for /usr/include/linux/input.h... no >> configure: error: /usr/include/linux/input.h not found >> 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w >> Exit 1 >> >> The touchscreen itself should be functional as it has a touch area outside >> the display, which is interpreted by the USB controller to change the >> backlight. >> The exact same display also worked fine on Raspbian. > > This is with webcamd compiled with debug support. > > [18]sa# /usr/local/sbin/webcamd -d ugen0.5 > Linux video capture interface: v2.00 > IR NEC protocol handler initialized > IR RC5(x/sz) protocol handler initialized > IR RC6 protocol handler initialized > IR JVC protocol handler initialized > IR Sony protocol handler initialized > IR SANYO protocol handler initialized > IR LIRC bridge handler initialized > IR XMP protocol handler initialized > b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully > USB Video Class driver (1.1.1) > cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1 > pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner > pvrusb2: Debug mask is 31 (0x1f) > USBVision USB Video Device Driver for Linux : 0.9.11 > Attached to ugen0.5[0] > INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-/dev/usb-/dev/usb/input0 > > DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0 > Creating /dev/input/event0 > > I really think that it has some problems with the controller. > When I run webcamd against the mouse I get some kind data from the > evdev. > Well - I had to reboot after testing with the mouse, but probably > it was disabled by default for a reason. > So my assumption is that I have to look up my problem somewhere between > webcamd and the USB device. > You can try running usbdump to capture USB packets. ktrace is also your friend. dd if=/dev/input/event0 bs=1 Also check ownership of devices, that X.org can read from them. --HPS From owner-freebsd-arm@freebsd.org Thu Mar 8 22:23:31 2018 Return-Path: Delivered-To: freebsd-arm@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 E211BF368E3; Thu, 8 Mar 2018 22:23:30 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E01B73F7D; Thu, 8 Mar 2018 22:23:30 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28MNMfk014418 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:23:23 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28MN8Sk017482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:23:08 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28MN89j087712 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 23:23:08 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28MN7h1087711; Thu, 8 Mar 2018 23:23:07 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 23:23:07 +0100 From: Bernd Walter To: Oleksandr Tymoshenko Cc: ticso@cicely.de, Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308222307.GF86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308203838.GA98731@bluezbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308203838.GA98731@bluezbox.com> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 22:23:31 -0000 On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > https://github.com/gonzoua/evdev-dump/tree/freebsd > > ... > > checking for unistd.h... yes > > checking linux/input.h usability... no > > checking linux/input.h presence... no > > checking for linux/input.h... no > > checking for /usr/include/linux/input.h... no > > configure: error: /usr/include/linux/input.h not found > > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > > Exit 1 > > I've just checked, evdev-dump should be buildable: > > git clone git@github.com:gonzoua/evdev-dump.git > cd evdev-dump > git checkout freebsd > sudo pkg install gawk gmake > sh bootstrap > ./configure > gmake That's exactly how I did. Well - I've used git clone https://github.com/gonzoua/evdev-dump.git Even with a fresh clone it failed at the same file. I have the following: /usr/include/dev/evdev/input.h /usr/local/include/linux/input.h /usr/local/include/xorg/input.h -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 22:29:51 2018 Return-Path: Delivered-To: freebsd-arm@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 33FAFF36F4E; Thu, 8 Mar 2018 22:29:51 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 BE71A742C3; Thu, 8 Mar 2018 22:29:50 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1eu42k-000Pxq-JU; Thu, 08 Mar 2018 14:29:47 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w28MTjmt099809; Thu, 8 Mar 2018 14:29:45 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 8 Mar 2018 14:29:44 -0800 From: Oleksandr Tymoshenko To: ticso@cicely.de Cc: Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308222944.GA99801@bluezbox.com> References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308203838.GA98731@bluezbox.com> <20180308222307.GF86413@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308222307.GF86413@cicely7.cicely.de> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 08 [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 22:29:51 -0000 Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > > https://github.com/gonzoua/evdev-dump/tree/freebsd > > > ... > > > checking for unistd.h... yes > > > checking linux/input.h usability... no > > > checking linux/input.h presence... no > > > checking for linux/input.h... no > > > checking for /usr/include/linux/input.h... no > > > configure: error: /usr/include/linux/input.h not found > > > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > > > Exit 1 > > > > I've just checked, evdev-dump should be buildable: > > > > git clone git@github.com:gonzoua/evdev-dump.git > > cd evdev-dump > > git checkout freebsd > > sudo pkg install gawk gmake > > sh bootstrap > > ./configure > > gmake > > That's exactly how I did. > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git > Even with a fresh clone it failed at the same file. > > I have the following: > /usr/include/dev/evdev/input.h > /usr/local/include/linux/input.h > /usr/local/include/xorg/input.h Could you show output of "git branch" and "grep -rl /usr/include/linux/input.h ." in cloned directory? Thanks -- gonzo From owner-freebsd-arm@freebsd.org Thu Mar 8 22:38:57 2018 Return-Path: Delivered-To: freebsd-arm@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 CDC83F37C68; Thu, 8 Mar 2018 22:38:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 45EBF74B32; Thu, 8 Mar 2018 22:38:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28McmbG014652 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:38:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28MchQF017699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:38:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28Mchr0087804 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 23:38:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28McgZh087803; Thu, 8 Mar 2018 23:38:42 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 23:38:42 +0100 From: Bernd Walter To: Oleksandr Tymoshenko Cc: ticso@cicely.de, Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308223842.GG86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308203838.GA98731@bluezbox.com> <20180308222307.GF86413@cicely7.cicely.de> <20180308222944.GA99801@bluezbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308222944.GA99801@bluezbox.com> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 22:38:58 -0000 On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote: > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > > > https://github.com/gonzoua/evdev-dump/tree/freebsd > > > > ... > > > > checking for unistd.h... yes > > > > checking linux/input.h usability... no > > > > checking linux/input.h presence... no > > > > checking for linux/input.h... no > > > > checking for /usr/include/linux/input.h... no > > > > configure: error: /usr/include/linux/input.h not found > > > > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > > > > Exit 1 > > > > > > I've just checked, evdev-dump should be buildable: > > > > > > git clone git@github.com:gonzoua/evdev-dump.git > > > cd evdev-dump > > > git checkout freebsd > > > sudo pkg install gawk gmake > > > sh bootstrap > > > ./configure > > > gmake > > > > That's exactly how I did. > > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git > > Even with a fresh clone it failed at the same file. > > > > I have the following: > > /usr/include/dev/evdev/input.h > > /usr/local/include/linux/input.h > > /usr/local/include/xorg/input.h > > Could you show output of "git branch" and > "grep -rl /usr/include/linux/input.h ." in cloned directory? [55]sa# git branch * master [56]sa# grep -rl /usr/include/linux/input.h . ./configure.ac ./autom4te.cache/output.0 ./autom4te.cache/output.1 ./configure ./config.log -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Mar 8 22:41:55 2018 Return-Path: Delivered-To: freebsd-arm@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 5F7C2F38165; Thu, 8 Mar 2018 22:41:55 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 E208C74F11; Thu, 8 Mar 2018 22:41:54 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1eu4EQ-000Pza-Mn; Thu, 08 Mar 2018 14:41:52 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w28MfohY099917; Thu, 8 Mar 2018 14:41:50 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 8 Mar 2018 14:41:50 -0800 From: Oleksandr Tymoshenko To: ticso@cicely.de Cc: Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308224150.GA99889@bluezbox.com> References: <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308203838.GA98731@bluezbox.com> <20180308222307.GF86413@cicely7.cicely.de> <20180308222944.GA99801@bluezbox.com> <20180308223842.GG86413@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308223842.GG86413@cicely7.cicely.de> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 12 [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 22:41:55 -0000 Bernd Walter (ticso@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > > > > https://github.com/gonzoua/evdev-dump/tree/freebsd > > > > > ... > > > > > checking for unistd.h... yes > > > > > checking linux/input.h usability... no > > > > > checking linux/input.h presence... no > > > > > checking for linux/input.h... no > > > > > checking for /usr/include/linux/input.h... no > > > > > configure: error: /usr/include/linux/input.h not found > > > > > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > > > > > Exit 1 > > > > > > > > I've just checked, evdev-dump should be buildable: > > > > > > > > git clone git@github.com:gonzoua/evdev-dump.git > > > > cd evdev-dump > > > > git checkout freebsd > > > > sudo pkg install gawk gmake > > > > sh bootstrap > > > > ./configure > > > > gmake > > > > > > That's exactly how I did. > > > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git > > > Even with a fresh clone it failed at the same file. > > > > > > I have the following: > > > /usr/include/dev/evdev/input.h > > > /usr/local/include/linux/input.h > > > /usr/local/include/xorg/input.h > > > > Could you show output of "git branch" and > > "grep -rl /usr/include/linux/input.h ." in cloned directory? > > [55]sa# git branch > * master > [56]sa# grep -rl /usr/include/linux/input.h . > ./configure.ac > ./autom4te.cache/output.0 > ./autom4te.cache/output.1 > ./configure > ./config.log You need freebsd branch. master branch is unmodified version of upstream, all my changes are on freebsd branch. Run: gmake clean git checkout freebsd <- this step is important sh bootstrap ./configure gmake Also you need bash installed, because original .h to .inc conversion script uses some bash-isms. -- gonzo From owner-freebsd-arm@freebsd.org Thu Mar 8 22:58:47 2018 Return-Path: Delivered-To: freebsd-arm@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 6BCE4F396E7; Thu, 8 Mar 2018 22:58:47 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F246E75DD2; Thu, 8 Mar 2018 22:58:46 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28MweC5014964 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:58:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28MwaUn017955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 23:58:36 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28Mwa8E087919 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 23:58:36 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28MwYW4087918; Thu, 8 Mar 2018 23:58:34 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 23:58:34 +0100 From: Bernd Walter To: Oleksandr Tymoshenko Cc: ticso@cicely.de, Greg , Roberto Fernandez Cueto , Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180308225834.GH86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308203838.GA98731@bluezbox.com> <20180308222307.GF86413@cicely7.cicely.de> <20180308222944.GA99801@bluezbox.com> <20180308223842.GG86413@cicely7.cicely.de> <20180308224150.GA99889@bluezbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308224150.GA99889@bluezbox.com> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 22:58:47 -0000 On Thu, Mar 08, 2018 at 02:41:50PM -0800, Oleksandr Tymoshenko wrote: > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote: > > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > > > > Bernd Walter (ticso@cicely7.cicely.de) wrote: > > > > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > > > > > https://github.com/gonzoua/evdev-dump/tree/freebsd > > > > > > ... > > > > > > checking for unistd.h... yes > > > > > > checking linux/input.h usability... no > > > > > > checking linux/input.h presence... no > > > > > > checking for linux/input.h... no > > > > > > checking for /usr/include/linux/input.h... no > > > > > > configure: error: /usr/include/linux/input.h not found > > > > > > 4.765u 3.954s 0:08.64 100.8% 31397+2201k 0+27io 0pf+0w > > > > > > Exit 1 > > > > > > > > > > I've just checked, evdev-dump should be buildable: > > > > > > > > > > git clone git@github.com:gonzoua/evdev-dump.git > > > > > cd evdev-dump > > > > > git checkout freebsd > > > > > sudo pkg install gawk gmake > > > > > sh bootstrap > > > > > ./configure > > > > > gmake > > > > > > > > That's exactly how I did. > > > > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git > > > > Even with a fresh clone it failed at the same file. > > > > > > > > I have the following: > > > > /usr/include/dev/evdev/input.h > > > > /usr/local/include/linux/input.h > > > > /usr/local/include/xorg/input.h > > > > > > Could you show output of "git branch" and > > > "grep -rl /usr/include/linux/input.h ." in cloned directory? > > > > [55]sa# git branch > > * master > > [56]sa# grep -rl /usr/include/linux/input.h . > > ./configure.ac > > ./autom4te.cache/output.0 > > ./autom4te.cache/output.1 > > ./configure > > ./config.log > > You need freebsd branch. master branch is unmodified > version of upstream, all my changes are on freebsd branch. Lol - that makes sense. Ok - it works, but I get nothing from my display, which this is more or less already expected. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 9 00:44:41 2018 Return-Path: Delivered-To: freebsd-arm@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 EC2B4F41700; Fri, 9 Mar 2018 00:44:40 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 79F1479AD1; Fri, 9 Mar 2018 00:44:40 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w290ibUo016619 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 01:44:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w290iY26023060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 01:44:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w290iY9q088458 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 01:44:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w290iYrH088457; Fri, 9 Mar 2018 01:44:34 +0100 (CET) (envelope-from ticso) Date: Fri, 9 Mar 2018 01:44:34 +0100 From: Bernd Walter To: Hans Petter Selasky Cc: ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180309004433.GI86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 00:44:41 -0000 On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote: > You can try running usbdump to capture USB packets. > > ktrace is also your friend. > > dd if=/dev/input/event0 bs=1 > > Also check ownership of devices, that X.org can read from them. It happens earlier, /dev/input/event0 delivers nothing at all. But usbdump is interesting. I've booted with webcamd disabled, started usbdump and started webcamd. This is what I get: [22]sa# usbdump -v -f 4 00:30:09.379930 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.382401 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.382448 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.385398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.385439 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.388398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 12 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. | 00:30:09.388434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 12 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 18 bytes 00:30:09.391399 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 18 bytes 0000 12 03 42 00 79 00 20 00 5A 00 48 00 38 00 35 00 |..B.y. .Z.H.8.5.| 0010 31 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |1. | 00:30:09.391474 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.394398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.394435 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.397398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.397436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.400398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 14 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. | 00:30:09.400433 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 14 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 20 bytes 00:30:09.403398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 20 bytes 0000 14 03 42 00 59 00 5A 00 48 00 59 00 59 00 5A 00 |..B.Y.Z.H.Y.Y.Z.| 0010 48 00 59 00 -- -- -- -- -- -- -- -- -- -- -- -- |H.Y. | 00:30:09.403440 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.406398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.406437 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.409397 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.409434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.412398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.412434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 26 bytes 00:30:09.415398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 26 bytes 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1.| 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. | 00:30:09.420243 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.422400 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.422441 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.425398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.425436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes 00:30:09.428398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... | 00:30:09.428436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 26 bytes 00:30:09.431398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 26 bytes 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1.| 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. | 00:30:09.431941 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 21 0A 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |!....... | 00:30:09.433396 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=STALLED frame[0] WRITE 8 bytes 00:30:09.433442 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 00 00 FB 00 -- -- -- -- -- -- -- -- |...".... | frame[1] READ 251 bytes 00:30:09.439403 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=252,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 251 bytes 00:30:09.447376 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 A1 01 02 03 00 00 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes 00:30:09.450400 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 02 0A -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | 00:30:09.451878 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 03 03 00 00 03 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 3 bytes 0000 03 02 00 -- -- -- -- -- -- -- -- -- -- -- -- -- |... | 00:30:09.454404 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 3 bytes 00:30:09.466235 usbus0.4 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=10 frame[0] READ 14 bytes 00:30:09.523430 usbus0.4 DONE-INTR-EP=00000082,SPD=FULL,NFR=0,SLEN=0,IVAL=10,ERR=CANCELLED It is obvious that the communication fails very early. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 9 08:19:54 2018 Return-Path: Delivered-To: freebsd-arm@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 588EDF3611B; Fri, 9 Mar 2018 08:19:54 +0000 (UTC) (envelope-from r.fernandez-cueto@bally-wulff.de) Received: from mail.bally-wulff.de (mail.bally-wulff.de [212.144.118.8]) by mx1.freebsd.org (Postfix) with ESMTP id B2EE269D6A; Fri, 9 Mar 2018 08:19:53 +0000 (UTC) (envelope-from r.fernandez-cueto@bally-wulff.de) Received: from bw-ex-01.bally-wulff.de (bw-ex-01.bally-wulff.de [192.168.204.106]) by mail.bally-wulff.de (Postfix) with ESMTPS id DED50116; Fri, 9 Mar 2018 09:19:51 +0100 (CET) Received: from BWEPCFERNANDEZ (192.168.205.134) by BW-EX-01.bally-wulff.de (192.168.204.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1415.2; Fri, 9 Mar 2018 09:19:51 +0100 Date: Fri, 9 Mar 2018 09:19:11 +0100 From: Roberto Fernandez Cueto To: CC: Hans Petter Selasky , , , Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180309081911.GA65154@BWEPCFERNANDEZ> References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20180309004433.GI86413@cicely7.cicely.de> User-Agent: Mutt/1.9.1 (2017-09-22) X-ClientProxiedBy: BW-EX-01.bally-wulff.de (192.168.204.106) To BW-EX-01.bally-wulff.de (192.168.204.106) X-OLX-Disclaimer: BW-EX-01.BALLY-WULFF.DE Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 08:19:54 -0000 Roberto Fernandez-Cueto schrieb am 09.03.2018 09:19 _____________________________________________________________________ I do not if this helps, but what I usually do when I get to work with a new touchscreen is to see if FreeBSD detects it as UHID. If it is recognized, then I check if the touchscreen send absolute coordinates or relative coordinates. You can do it with usbhidctl(1). See the collection, items and get the values parsed by the HID layer. If it helps, let me know. Roberto Fernandez Cueto On Fri, Mar 09, 2018 at 01:44:34AM +0100, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote: > > You can try running usbdump to capture USB packets. > >=20 > > ktrace is also your friend. > >=20 > > dd if=3D/dev/input/event0 bs=3D1 > >=20 > > Also check ownership of devices, that X.org can read from them. >=20 > It happens earlier, /dev/input/event0 delivers nothing at all. > But usbdump is interesting. > I've booted with webcamd disabled, started usbdump and started webcamd. >=20 > This is what I get: > [22]sa# usbdump -v -f 4 > 00:30:09.379930 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.382401 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.382448 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.385398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.385439 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 02 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.388398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 12 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. = | > 00:30:09.388434 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 02 03 09 04 12 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 18 bytes > 00:30:09.391399 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D20,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 18 bytes > 0000 12 03 42 00 79 00 20 00 5A 00 48 00 38 00 35 00 |..B.y. .Z.H.8.5= .| > 0010 31 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |1. = | > 00:30:09.391474 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.394398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.394435 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.397398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.397436 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 01 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.400398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 14 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. = | > 00:30:09.400433 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 01 03 09 04 14 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 20 bytes > 00:30:09.403398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D20,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 20 bytes > 0000 14 03 42 00 59 00 5A 00 48 00 59 00 59 00 5A 00 |..B.Y.Z.H.Y.Y.= Z.| > 0010 48 00 59 00 -- -- -- -- -- -- -- -- -- -- -- -- |H.Y. = | > 00:30:09.403440 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.406398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.406437 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.409397 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.409434 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.412398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.412434 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 26 bytes > 00:30:09.415398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D28,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 26 bytes > 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1= .| > 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. = | > 00:30:09.420243 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.422400 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.422441 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.425398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.425436 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 4 bytes > 00:30:09.428398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... = | > 00:30:09.428436 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 26 bytes > 00:30:09.431398 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D28,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 26 bytes > 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1= .| > 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. = | > 00:30:09.431941 usbus0.4 SUBM-CTRL-EP=3D00000000,SPD=3DFULL,NFR=3D1,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 21 0A 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |!....... = | > 00:30:09.433396 usbus0.4 DONE-CTRL-EP=3D00000000,SPD=3DFULL,NFR=3D1,SLEN= =3D0,IVAL=3D0,ERR=3DSTALLED > frame[0] WRITE 8 bytes > 00:30:09.433442 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 81 06 00 22 00 00 FB 00 -- -- -- -- -- -- -- -- |...".... = | > frame[1] READ 251 bytes > 00:30:09.439403 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D252,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 251 bytes > 00:30:09.447376 usbus0.4 SUBM-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D8,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 A1 01 02 03 00 00 02 00 -- -- -- -- -- -- -- -- |........ = | > frame[1] READ 2 bytes > 00:30:09.450400 usbus0.4 DONE-CTRL-EP=3D00000080,SPD=3DFULL,NFR=3D2,SLEN= =3D4,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] READ 2 bytes > 0000 02 0A -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. = | > 00:30:09.451878 usbus0.4 SUBM-CTRL-EP=3D00000000,SPD=3DFULL,NFR=3D2,SLEN= =3D12,IVAL=3D0 > frame[0] WRITE 8 bytes > 0000 21 09 03 03 00 00 03 00 -- -- -- -- -- -- -- -- |!....... = | > frame[1] WRITE 3 bytes > 0000 03 02 00 -- -- -- -- -- -- -- -- -- -- -- -- -- |... = | > 00:30:09.454404 usbus0.4 DONE-CTRL-EP=3D00000000,SPD=3DFULL,NFR=3D2,SLEN= =3D0,IVAL=3D0,ERR=3D0 > frame[0] WRITE 8 bytes > frame[1] WRITE 3 bytes > 00:30:09.466235 usbus0.4 SUBM-INTR-EP=3D00000082,SPD=3DFULL,NFR=3D1,SLEN= =3D0,IVAL=3D10 > frame[0] READ 14 bytes > 00:30:09.523430 usbus0.4 DONE-INTR-EP=3D00000082,SPD=3DFULL,NFR=3D0,SLEN= =3D0,IVAL=3D10,ERR=3DCANCELLED >=20 > It is obvious that the communication fails very early. >=20 > --=20 > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " BALLY WULFF Games & Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, Po= stanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: 030-62= 0 02-200, Geschaeftsfuehrer: Thomas Niehenke, Lars Rogge, Thomas Wendt, Amt= sgericht Berlin-Charlottenburg HRB 139020 B, UST-IdNr. DE815328376 _____________________________________________________________________ Dieses E-Mail ist nur fuer den Empfaenger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- aeusserung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Games & Entertainment GmbH dar. Sind Sie nicht der Empfaenger, so haben Sie diese E-Mail irrtuemlich erhalten und jegliche Verwendung, Veroeffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Games & Entertainment GmbH noch der Absender uebernehmen die Haftung fuer Viren. Es obliegt Ihrer Verantwortung, die E-Mail und deren Anhaenge auf Viren zu pruefen. Anhaenge: _____________________________________________________________________ Versand am 09.03.2018 09:19 von Fernandez-Cueto Roberto From owner-freebsd-arm@freebsd.org Fri Mar 9 08:40:05 2018 Return-Path: Delivered-To: freebsd-arm@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 4E500F37F2F; Fri, 9 Mar 2018 08:40:05 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 D50966AE8B; Fri, 9 Mar 2018 08:40:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 74210260178; Fri, 9 Mar 2018 09:40:03 +0100 (CET) Subject: Re: webcamd based touchscreen problem on Pi3 To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter References: <20180308161645.GF80981@cicely7.cicely.de> <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> From: Hans Petter Selasky Message-ID: <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> Date: Fri, 9 Mar 2018 09:40:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180309004433.GI86413@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 08:40:05 -0000 On 03/09/18 01:44, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote: >> You can try running usbdump to capture USB packets. >> >> ktrace is also your friend. >> >> dd if=/dev/input/event0 bs=1 >> >> Also check ownership of devices, that X.org can read from them. > > It happens earlier, /dev/input/event0 delivers nothing at all. > But usbdump is interesting. > I've booted with webcamd disabled, started usbdump and started webcamd. > > This is what I get: > [22]sa# usbdump -v -f 4 > 00:30:09.379930 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.382401 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.382448 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.385398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.385439 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 02 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.388398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 12 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. | > 00:30:09.388434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 02 03 09 04 12 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 18 bytes > 00:30:09.391399 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 18 bytes > 0000 12 03 42 00 79 00 20 00 5A 00 48 00 38 00 35 00 |..B.y. .Z.H.8.5.| > 0010 31 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |1. | > 00:30:09.391474 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.394398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.394435 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.397398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.397436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 01 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.400398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 14 03 42 00 -- -- -- -- -- -- -- -- -- -- -- -- |..B. | > 00:30:09.400433 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 01 03 09 04 14 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 20 bytes > 00:30:09.403398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 20 bytes > 0000 14 03 42 00 59 00 5A 00 48 00 59 00 59 00 5A 00 |..B.Y.Z.H.Y.Y.Z.| > 0010 48 00 59 00 -- -- -- -- -- -- -- -- -- -- -- -- |H.Y. | > 00:30:09.403440 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.406398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.406437 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.409397 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.409434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.412398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.412434 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 26 bytes > 00:30:09.415398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 26 bytes > 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1.| > 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. | > 00:30:09.420243 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.422400 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.422441 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.425398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.425436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 04 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 4 bytes > 00:30:09.428398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 4 bytes > 0000 1A 03 1A 00 -- -- -- -- -- -- -- -- -- -- -- -- |.... | > 00:30:09.428436 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 26 bytes > 00:30:09.431398 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 26 bytes > 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1.| > 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. | > 00:30:09.431941 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 21 0A 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |!....... | > 00:30:09.433396 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=STALLED > frame[0] WRITE 8 bytes > 00:30:09.433442 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 81 06 00 22 00 00 FB 00 -- -- -- -- -- -- -- -- |...".... | > frame[1] READ 251 bytes > 00:30:09.439403 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=252,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 251 bytes > 00:30:09.447376 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 A1 01 02 03 00 00 02 00 -- -- -- -- -- -- -- -- |........ | > frame[1] READ 2 bytes > 00:30:09.450400 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] READ 2 bytes > 0000 02 0A -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | > 00:30:09.451878 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 > frame[0] WRITE 8 bytes > 0000 21 09 03 03 00 00 03 00 -- -- -- -- -- -- -- -- |!....... | > frame[1] WRITE 3 bytes > 0000 03 02 00 -- -- -- -- -- -- -- -- -- -- -- -- -- |... | > 00:30:09.454404 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 > frame[0] WRITE 8 bytes > frame[1] WRITE 3 bytes > 00:30:09.466235 usbus0.4 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=10 > frame[0] READ 14 bytes > 00:30:09.523430 usbus0.4 DONE-INTR-EP=00000082,SPD=FULL,NFR=0,SLEN=0,IVAL=10,ERR=CANCELLED > > It is obvious that the communication fails very early. > Can you try connecting the device through an external USB HUB? Can you capture the whole enumeration sequence. Can you also try setting the UQ_NO_STRINGS quirk using usbconfig for this device and re-plug it? --HPS --HPS From owner-freebsd-arm@freebsd.org Fri Mar 9 11:40:38 2018 Return-Path: Delivered-To: freebsd-arm@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 6FEB0F458E3; Fri, 9 Mar 2018 11:40:38 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EF49A721AA; Fri, 9 Mar 2018 11:40:37 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w29BeVa8027647 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 12:40:32 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w29BePhh033039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 12:40:25 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w29BePKb092393 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 12:40:25 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w29BePnj092392; Fri, 9 Mar 2018 12:40:25 +0100 (CET) (envelope-from ticso) Date: Fri, 9 Mar 2018 12:40:25 +0100 From: Bernd Walter To: Hans Petter Selasky Cc: ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180309114025.GJ86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, UPPERCASE_50_75=0.008 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 11:40:38 -0000 On Fri, Mar 09, 2018 at 09:40:00AM +0100, Hans Petter Selasky wrote: > On 03/09/18 01:44, Bernd Walter wrote: > >On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote: > >>You can try running usbdump to capture USB packets. > >> > >>ktrace is also your friend. > >> > >>dd if=/dev/input/event0 bs=1 > >> > >>Also check ownership of devices, that X.org can read from them. > > > > Can you try connecting the device through an external USB HUB? This test has to wait for me to change the setup > Can you capture the whole enumeration sequence. Can you also try setting > the UQ_NO_STRINGS quirk using usbconfig for this device and re-plug it? This is on plug in: [25]sa# usbdump -v -v -v -v -f 4 11:36:27.190408 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 00 05 04 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | flags 0x50 status 0xc03a3 11:36:27.191546 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x50 status 0xc03a1 11:36:27.191568 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0 frame[0] WRITE 0 bytes flags 0x10 status 0xc00a3 11:36:27.192542 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 0 bytes flags 0x10 status 0xc00a1 11:36:27.203447 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 01 00 00 08 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 8 bytes flags 0x10 status 0xc01a3 11:36:27.206539 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 8 bytes 0000 12 01 00 02 00 00 00 40 -- -- -- -- -- -- -- -- |.......@ | flags 0x10 status 0xc01a1 11:36:27.206618 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 01 00 00 12 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 18 bytes flags 0x10 status 0xc01a3 11:36:27.209538 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 18 bytes 0000 12 01 00 02 00 00 00 40 EF 0E 05 00 00 02 01 02 |.......@........| 0010 03 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.209578 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xc01a3 11:36:27.212537 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 04 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.212559 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes flags 0x10 status 0xc01a3 11:36:27.215537 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | flags 0x10 status 0xc01a1 11:36:27.215561 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xc01a3 11:36:27.218536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 1A 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.218557 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 03 03 09 04 1A 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 26 bytes flags 0x10 status 0xc01a3 11:36:27.221536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 26 bytes 0000 1A 03 1A 00 95 00 50 00 33 00 39 00 31 00 31 00 |......P.3.9.1.1.| 0010 06 00 32 00 33 00 39 00 38 00 -- -- -- -- -- -- |..2.3.9.8. | flags 0x10 status 0xc01a1 11:36:27.221560 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xc01a3 11:36:27.224537 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 14 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.224559 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 14 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 20 bytes flags 0x10 status 0xc01a3 11:36:27.227536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 20 bytes 0000 14 03 42 00 59 00 5A 00 48 00 59 00 59 00 5A 00 |..B.Y.Z.H.Y.Y.Z.| 0010 48 00 59 00 -- -- -- -- -- -- -- -- -- -- -- -- |H.Y. | flags 0x10 status 0xc01a1 11:36:27.227559 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xc01a3 11:36:27.230537 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 12 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.230559 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 12 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 18 bytes flags 0x10 status 0xc01a3 11:36:27.233536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 18 bytes 0000 12 03 42 00 79 00 20 00 5A 00 48 00 38 00 35 00 |..B.y. .Z.H.8.5.| 0010 31 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |1. | flags 0x10 status 0xc01a1 11:36:27.233590 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 02 00 00 09 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 9 bytes flags 0x10 status 0xc01a3 11:36:27.236536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 9 bytes 0000 09 02 29 00 01 01 00 C0 32 -- -- -- -- -- -- -- |..).....2 | flags 0x10 status 0xc01a1 11:36:27.236560 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 02 00 00 29 00 -- -- -- -- -- -- -- -- |......). | frame[1] READ 41 bytes flags 0x10 status 0xc01a3 11:36:27.239537 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 41 bytes 0000 09 02 29 00 01 01 00 C0 32 09 04 00 00 02 03 00 |..).....2.......| 0010 00 00 09 21 10 01 00 01 22 FB 00 07 05 82 03 10 |...!....".......| 0020 00 0A 07 05 01 03 40 00 10 -- -- -- -- -- -- -- |......@.. | flags 0x10 status 0xc01a1 11:36:27.239561 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 00 00 00 00 00 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xc01a3 11:36:27.242536 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 00 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xc01a1 11:36:27.242559 usbus0.4 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 00 09 01 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | flags 0x10 status 0xc01a3 11:36:27.244538 usbus0.4 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xc01a1 11:36:27.247225 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 00 00 FB 00 -- -- -- -- -- -- -- -- |...".... | frame[1] READ 251 bytes flags 0x10 status 0xc01a3 11:36:27.252550 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=252,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 251 bytes flags 0x10 status 0xc01a1 11:36:27.252709 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 00 00 FB 00 -- -- -- -- -- -- -- -- |...".... | frame[1] READ 251 bytes flags 0x10 status 0xc01a3 11:36:27.258546 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=252,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 251 bytes flags 0x10 status 0xc01a1 Will do the quirk test later. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 9 11:44:38 2018 Return-Path: Delivered-To: freebsd-arm@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 09056F45DB9; Fri, 9 Mar 2018 11:44:38 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 721D97276B; Fri, 9 Mar 2018 11:44:37 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w29BiYUN027725 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 12:44:35 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w29BiNGh033084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 12:44:23 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w29BiMgc092435 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 12:44:22 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w29BiM7q092434; Fri, 9 Mar 2018 12:44:22 +0100 (CET) (envelope-from ticso) Date: Fri, 9 Mar 2018 12:44:22 +0100 From: Bernd Walter To: Roberto Fernandez Cueto Cc: ticso@cicely.de, Hans Petter Selasky , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180309114422.GK86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <20180309081911.GA65154@BWEPCFERNANDEZ> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180309081911.GA65154@BWEPCFERNANDEZ> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 11:44:38 -0000 On Fri, Mar 09, 2018 at 09:19:11AM +0100, Roberto Fernandez Cueto wrote: > Roberto Fernandez-Cueto schrieb am 09.03.2018 09:19 > _____________________________________________________________________ > > I do not if this helps, but what I usually do when I get to work with a > new touchscreen is to see if FreeBSD detects it as UHID. I hadn't loaded uhid, but it detects the device. > If it is recognized, then I check if the touchscreen send absolute > coordinates or relative coordinates. > > You can do it with usbhidctl(1). See the collection, items and get the > values parsed by the HID layer. Well, this has to wait until I found time to read more about it. HID is something I've always hated and never really spend much time into. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 9 12:20:00 2018 Return-Path: Delivered-To: freebsd-arm@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 12974F4928E; Fri, 9 Mar 2018 12:20:00 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 A77B4743F2; Fri, 9 Mar 2018 12:19:59 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 4E1A3260140; Fri, 9 Mar 2018 13:19:58 +0100 (CET) Subject: Re: webcamd based touchscreen problem on Pi3 To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter References: <20180308163605.GA61875@BWEPCFERNANDEZ> <20180308161645.GF80981@cicely7.cicely.de> <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> From: Hans Petter Selasky Message-ID: Date: Fri, 9 Mar 2018 13:19:54 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180309114025.GJ86413@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 12:20:00 -0000 On 03/09/18 12:40, Bernd Walter wrote: > Will do the quirk test later. I don't see any stalls during plug-in, so it might be a request webcamd issues, which the device doesn't support. Try building webcamd with debug support. --HPS From owner-freebsd-arm@freebsd.org Fri Mar 9 13:25:49 2018 Return-Path: Delivered-To: freebsd-arm@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 B7E9DF4DD8F; Fri, 9 Mar 2018 13:25:49 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3ECB976C8A; Fri, 9 Mar 2018 13:25:49 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w29DPjAi029191 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 14:25:45 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w29DPd8n034339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 9 Mar 2018 14:25:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w29DPd2N092882 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 14:25:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w29DPdUF092881; Fri, 9 Mar 2018 14:25:39 +0100 (CET) (envelope-from ticso) Date: Fri, 9 Mar 2018 14:25:39 +0100 From: Bernd Walter To: Hans Petter Selasky Cc: ticso@cicely.de, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, Bernd Walter Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180309132539.GL86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <818e1917-0472-c0dd-a9d6-b7532faf4d4b@selasky.org> <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 13:25:50 -0000 On Fri, Mar 09, 2018 at 01:19:54PM +0100, Hans Petter Selasky wrote: > On 03/09/18 12:40, Bernd Walter wrote: > >Will do the quirk test later. > > I don't see any stalls during plug-in, so it might be a request webcamd > issues, which the device doesn't support. Try building webcamd with > debug support. It is already build with debug. But I don't see anything of special interest in the output. [24]sa# webcamd -d ugen0.4 Linux video capture interface: v2.00 IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR LIRC bridge handler initialized IR XMP protocol handler initialized b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully USB Video Class driver (1.1.1) cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1 pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner pvrusb2: Debug mask is 31 (0x1f) USBVision USB Video Device Driver for Linux : 0.9.11 Attached to ugen0.4[0] INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-/dev/usb-/dev/usb/input0 DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0 Creating /dev/input/event0 I will redo a test with raspbian. Waveshare delivered a binary kernel (so much about GPL) for their 7" HDMI C until they changed something in the device firmware and upgraded for a newer panel about 2-3 years ago. This is the 10.1" HMDI B and it is a very early version I have, which however should use a firmware similar to the newer 7" HDMI C. I will retest with a stock Raspbian image to be sure I wasn't accidently using a Waveshare image back then. As far as I can see the Linux drivers just quirk the device to the egalaxy driver, so they do know the Waveshare by ID. I couldn't spot a difference between Linux and what is included in the webcamd source. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 9 18:56:53 2018 Return-Path: Delivered-To: freebsd-arm@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 3D715F42E6D for ; Fri, 9 Mar 2018 18:56:53 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD06A86FE1 for ; Fri, 9 Mar 2018 18:56:52 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-24-163-43-246.nc.res.rr.com [24.163.43.246]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w29IuEC1048918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 9 Mar 2018 18:56:20 GMT (envelope-from swills@FreeBSD.org) To: freebsd-arm@freebsd.org From: Steve Wills Subject: No arch specific invalidate_icache_all available! Message-ID: <0ea2ec57-da6f-c8df-aaf4-d986b56a8ecd@FreeBSD.org> Date: Fri, 9 Mar 2018 13:56:07 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 09 Mar 2018 18:56:20 +0000 (UTC) X-Spam-Status: No, score=1.3 required=4.5 tests=RCVD_IN_RP_RNBL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 18:56:53 -0000 Hi, Trying to boot r330240 on my Raspberry Pi B, I'm getting: Booting [/boot/kernel/kernel]... /boot/dtb/bcm2835-rpi-b-rev2.dtb size=0x3366 Loaded DTB from file 'bcm2835-rpi-b-rev2.dtb'. Kernel entry at 0x1200100... No arch specific invalidate_icache_all available! Kernel args: (null) Then it goes back to U-Boot. Any ideas on what's wrong here? Thanks, Steve From owner-freebsd-arm@freebsd.org Fri Mar 9 20:44:34 2018 Return-Path: Delivered-To: freebsd-arm@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 2FD97F4A263 for ; Fri, 9 Mar 2018 20:44:34 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 B2AA76B852 for ; Fri, 9 Mar 2018 20:44:33 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 8deb4d7e-23da-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 8deb4d7e-23da-11e8-b951-f99fef315fd9; Fri, 09 Mar 2018 20:43:43 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w29KiUDS008647; Fri, 9 Mar 2018 13:44:31 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520628270.84937.56.camel@freebsd.org> Subject: Re: Garbled console output on Pi3 From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Fri, 09 Mar 2018 13:44:30 -0700 In-Reply-To: <20180307182117.GA55819@www.zefox.net> References: <20180307182117.GA55819@www.zefox.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 20:44:34 -0000 On Wed, 2018-03-07 at 10:21 -0800, bob prohaska wrote: > From time to time I observe garbled console output on a Pi3 running -current. > The present revision is  > FreeBSD 12.0-CURRENT (ZEFOX) #1 r330571: Wed Mar  7 00:58:23 PST 2018 > but I don't think that's special; the same thing has shown up sporadically > for the past month or so. > > The output looks like this: > > Mar  7 09:53:53 www kernel: pid 44970 (llvm-tblgen), uid 0, was killed: out of swap space > sswawpa_spp_apgaegr:er iw:ndsaewap fii_ppnand_ieptge fiweaanrig:eti  r:teb u wfiifannidt deefebr:i fnbuiiuffontife tberwajit:e  : bu0f, bufeblfokb nj:r:o:  0,w2 b b22u3fo94aibj,tl: k  b0nosui:,z fe b1siz87erlk6:n,  o:sbi 4zue: : 202f901o669b604,  >     ej0sw: : > r:ag le4,0paap9 g6_epb >        inrkd: inendefifnioini:te t w1eai35t bu w2fai6t0f b,er:uf fbufoerbj: :bufo  bjs0:i , z0bl, blkeknno: 2: o16: 4260191,52 >  9393s7ize:,  1siz63e:84 4 > 096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 210573, size: 4096 > > The first and last lines look normal, which seems to rule out errors in > the serial link.  I can't come up with a reason for this. This was normal in the old days, but console output is buffered these days, and the buffer size is 128 bytes on arm[64], so if things are going to interleave it should be in chunks of 128, not a few chars at a time like that. Oh... unless it's a case of userland and the kernel writing to the terminal at the same time, independently of each other.  Were you running the commands that are failing from the console? -- Ian From owner-freebsd-arm@freebsd.org Fri Mar 9 21:05:35 2018 Return-Path: Delivered-To: freebsd-arm@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 1858FF4B897 for ; Fri, 9 Mar 2018 21:05:35 +0000 (UTC) (envelope-from mmitchel@gmail.com) Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (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 7C8506C7D0; Fri, 9 Mar 2018 21:05:34 +0000 (UTC) (envelope-from mmitchel@gmail.com) Received: by mail-pl0-x242.google.com with SMTP id i6-v6so5880673plt.7; Fri, 09 Mar 2018 13:05:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pnsrRuUzf92R+tc7OR+tHL4CKbutzXyRVsFiB+qdDUI=; b=Smlkrfcp1fjZXj4LyVtAvNNsuKLWr7orp8MEnFc6nqy2F/u7KSD5YHGbyTurrSaO/G FkFdvj9cckwXFc5j33hN1z5eBG7uNhft4BWHjUg+OaxiKvyM2woHIrb3HMNID0ivEUCC kk3lXebyeIKeSr10VZhr3THoaBYs3ByaBNoWRes2ABr9ISpPLWFPUph57Y96iFrnFhHd vs+6v13lcxTDdeje99N3LDlNhLBHBel0cskR0NH4F4IoHq/yerSuNjUeTz0OdDhWCYxw Obd0nHG+XVrt3F7G5jw2WygmuDLJxgEFAQFGmK+KPl/2Jf+rP5QswJY73pV79hs41Y0y WFoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pnsrRuUzf92R+tc7OR+tHL4CKbutzXyRVsFiB+qdDUI=; b=HZhdgZ9Hzfo243tLDUbaLgEUnA04ayqNhVLQPKpkAwrkmp0ajp6+pUyIGIvFc7vXop /L6Jv9fwwxUdkAIjN4fj6OCtlqMGpRxaHvs1RahM2nVCUHsQuxvnP6111w728PEcvm2y 22DGoBCsgX7vb/jU8uf7kR8SAPojrV5/tt43s8D6a1IzIRWIvREpA2e8zhPwmrwG9D02 aPaMGxYYwS0TnLRFBvvcMeWWzCHf/ykfxW6Qub7xT91SqwqKhkoIDcRdECS305/SCQ2i WTSz3GK+4wYyNBb5XJt7S5ctBzQ/M9J1DbEJGGQiulPx6AVYcEqI+WofXry/lzyUM3nn lNBQ== X-Gm-Message-State: APf1xPA8CGNVGwkJwnB9WZoz5/7QL5V9PwcQET8o+Fiz17ndBmasjRl5 Yt6EmUeglLeQbBdopq3m+tCsQNRKZ5mq X-Google-Smtp-Source: AG47ELtSHkkXcW/zBkuTAQ8CpUccLNdFu6bUCzkw+PYa4zKJZCd9vfyfRbxqrjCHXYLW6DaEcVMdIw== X-Received: by 2002:a17:902:788e:: with SMTP id q14-v6mr29310892pll.396.1520629532844; Fri, 09 Mar 2018 13:05:32 -0800 (PST) Received: from ?IPv6:2606:6000:c206:ce00:358a:fbf8:258d:68f0? ([2606:6000:c206:ce00:358a:fbf8:258d:68f0]) by smtp.gmail.com with ESMTPSA id d13sm3322053pgn.64.2018.03.09.13.05.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Mar 2018 13:05:32 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Garbled console output on Pi3 From: "Michael Mitchell (megabyte)" In-Reply-To: <1520628270.84937.56.camel@freebsd.org> Date: Fri, 9 Mar 2018 13:05:27 -0800 Cc: bob prohaska , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1F29E846-6EFE-4966-85BC-742F0B59B774@gmail.com> References: <20180307182117.GA55819@www.zefox.net> <1520628270.84937.56.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 21:05:35 -0000 This happens to me when the cable FTDI USB/232TTL isn't seated very = well. Pin header connectors do have a limited cycle count, and become loose over time. The first thing I = always blame is the cable... Michael Mitchell > On Mar 9, 2018, at 12:44 PM, Ian Lepore wrote: >=20 > On Wed, 2018-03-07 at 10:21 -0800, bob prohaska wrote: >> =46rom time to time I observe garbled console output on a Pi3 running = -current. >> The present revision is=20 >> FreeBSD 12.0-CURRENT (ZEFOX) #1 r330571: Wed Mar 7 00:58:23 PST 2018 >> but I don't think that's special; the same thing has shown up = sporadically >> for the past month or so. >>=20 >> The output looks like this: >>=20 >> Mar 7 09:53:53 www kernel: pid 44970 (llvm-tblgen), uid 0, was = killed: out of swap space >> sswawpa_spp_apgaegr:er iw:ndsaewap fii_ppnand_ieptge fiweaanrig:eti = r:teb u wfiifannidt deefebr:i fnbuiiuffontife tberwajit:e : bu0f, = bufeblfokb nj:r:o: 0,w2 b b22u3fo94aibj,tl: k b0nosui:,z fe = b1siz87erlk6:n, o:sbi 4zue: : 202f901o669b604,=20 >> ej0sw: : >> r:ag le4,0paap9 g6_epb >> inrkd: inendefifnioini:te t w1eai35t bu w2fai6t0f b,er:uf = fbufoerbj: :bufo bjs0:i , z0bl, blkeknno: 2: o16: 4260191,52 >> 9393s7ize:, 1siz63e:84 4 >> 096 >> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 210573, size: = 4096 >>=20 >> The first and last lines look normal, which seems to rule out errors = in >> the serial link.=20 >=20 > I can't come up with a reason for this. This was normal in the old > days, but console output is buffered these days, and the buffer size = is > 128 bytes on arm[64], so if things are going to interleave it should = be > in chunks of 128, not a few chars at a time like that. >=20 > Oh... unless it's a case of userland and the kernel writing to the > terminal at the same time, independently of each other. Were you > running the commands that are failing from the console? >=20 > -- Ian >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Mar 9 21:44:37 2018 Return-Path: Delivered-To: freebsd-arm@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 DFB30F4DE61 for ; Fri, 9 Mar 2018 21:44:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 414DC6E126; Fri, 9 Mar 2018 21:44:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w29LiV1R065969 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 13:44:32 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w29LiV0m065968; Fri, 9 Mar 2018 13:44:31 -0800 (PST) (envelope-from fbsd) Date: Fri, 9 Mar 2018 13:44:31 -0800 From: bob prohaska To: Ian Lepore Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Garbled console output on Pi3 Message-ID: <20180309214431.GA65874@www.zefox.net> References: <20180307182117.GA55819@www.zefox.net> <1520628270.84937.56.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520628270.84937.56.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 21:44:38 -0000 On Fri, Mar 09, 2018 at 01:44:30PM -0700, Ian Lepore wrote: > On Wed, 2018-03-07 at 10:21 -0800, bob prohaska wrote: > > From time to time I observe garbled console output on a Pi3 running -current. > > The present revision is? > > FreeBSD 12.0-CURRENT (ZEFOX) #1 r330571: Wed Mar??7 00:58:23 PST 2018 > > but I don't think that's special; the same thing has shown up sporadically > > for the past month or so. > > > > The output looks like this: > > > > Mar??7 09:53:53 www kernel: pid 44970 (llvm-tblgen), uid 0, was killed: out of swap space > > sswawpa_spp_apgaegr:er iw:ndsaewap fii_ppnand_ieptge fiweaanrig:eti??r:teb u wfiifannidt deefebr:i fnbuiiuffontife tberwajit:e??: bu0f, bufeblfokb nj:r:o:??0,w2 b b22u3fo94aibj,tl: k??b0nosui:,z fe b1siz87erlk6:n,??o:sbi 4zue: : 202f901o669b604,? > > ????ej0sw: : > > r:ag le4,0paap9 g6_epb > > ???????inrkd: inendefifnioini:te t w1eai35t bu w2fai6t0f b,er:uf fbufoerbj: :bufo??bjs0:i , z0bl, blkeknno: 2: o16: 4260191,52 > > ?9393s7ize:,??1siz63e:84 4 > > 096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 210573, size: 4096 > > > > The first and last lines look normal, which seems to rule out errors in > > the serial link.? > > I can't come up with a reason for this. This was normal in the old > days, but console output is buffered these days, and the buffer size is > 128 bytes on arm[64], so if things are going to interleave it should be > in chunks of 128, not a few chars at a time like that. > > Oh... unless it's a case of userland and the kernel writing to the > terminal at the same time, independently of each other. ?Were you > running the commands that are failing from the console? > Nothing running from the console, all commands were through ssh sessions. Can you suggest any experiments that might shed light on what's going on? So far it seems -j8 buildworld and stress2 can provoke the effect. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Fri Mar 9 23:05:33 2018 Return-Path: Delivered-To: freebsd-arm@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 7A266F2E266 for ; Fri, 9 Mar 2018 23:05:33 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 DDB1172706; Fri, 9 Mar 2018 23:05:32 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id 188so6547917wme.1; Fri, 09 Mar 2018 15:05:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5hYqB+24UDT7XW2SD7FjXGjq0TcqxmttpxMqlGOZT1g=; b=sZEn2qKAcceBPqKsoU6gfUPWSrt0XK49xHD9h+YOW6YvOMzilRtrppvZSiDC0QrXCP JCMrGYnUyU2ZH+YErnczefReockzKMJ/AGlBSxoicRi/UC0V4GjU6KPa0PLdIfRGAKex 5sW0TJj3V1ER7KaOPwvnVTE5cPCTDb+tR+ye3Q+/1rGHidh2eOtaDJUDc+xwIN/4Eisj akIqGTktmAybu80QuHGfAU+9DD057elQECqj+nZ/nQDavEYYqM5d9KbrvTzYP7tW9tox vzo3RuyYrML+sQFieRZB0lX9WMJxHAbAG84vjXKcf2qUAqFdbddp+x/XuiBJQyvYR5+2 blkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5hYqB+24UDT7XW2SD7FjXGjq0TcqxmttpxMqlGOZT1g=; b=cLvCU60ijAWnU33rydikXarm03PVxXi+7stwq48XYXpiBMJLhm45kGdpFtgBeYEiPt 8+/6utk2mjdh3XG52NAGno9RG8/PPEPe0dIgNZMvOdW3HFY3xQDUWzuNrxwAf3BXe7mu YVTbTL6AFRjcry0qKh4ijeVLcWvZiDQjSE4DkNjKvClZbO1qZKI1gDp4xy+ACK7fekLl Kf/UlWIGbpzuf45qFX/WyrhrKTAH6BfbHhDPJfo2honMJn0EDYoFNDKCDm9kf9BSUB8a MejjLE0P3Q0HRSj5DLvdU9kS/vud+3wynhh6dExz4YMXHT8o3318pTHjlgK/PWHG9AE8 h3vw== X-Gm-Message-State: AElRT7GWBN2VU7M+1drRaoYux58rP8IYDeeeq7GfbzjEMMHVL6mcCv25 bmvRiWLFL9RC+trL6wJzWR9YV/k0jzbvL9Ldav6oQA== X-Google-Smtp-Source: AG47ELvsLawaM4c+flq02cC0W+idX0v5qyJHuY71obOGo2rmvOBI7tCpHp2Huk4+Zw67wvfgwf/g3v8CPKPCqz9Z6e0= X-Received: by 10.28.147.73 with SMTP id v70mr389154wmd.128.1520636731692; Fri, 09 Mar 2018 15:05:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.169.206 with HTTP; Fri, 9 Mar 2018 15:05:31 -0800 (PST) In-Reply-To: <0ea2ec57-da6f-c8df-aaf4-d986b56a8ecd@FreeBSD.org> References: <0ea2ec57-da6f-c8df-aaf4-d986b56a8ecd@FreeBSD.org> From: =?UTF-8?Q?Eddy_Petri=C8=99or?= Date: Sat, 10 Mar 2018 01:05:31 +0200 Message-ID: Subject: Re: No arch specific invalidate_icache_all available! To: Steve Wills Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 23:05:33 -0000 2018-03-09 20:56 GMT+02:00 Steve Wills : > Hi, Hi, > > Trying to boot r330240 on my Raspberry Pi B, I'm getting: > > Booting [/boot/kernel/kernel]... > /boot/dtb/bcm2835-rpi-b-rev2.dtb size=3D0x3366 > Loaded DTB from file 'bcm2835-rpi-b-rev2.dtb'. > Kernel entry at 0x1200100... > No arch specific invalidate_icache_all available! > Kernel args: (null) > > Then it goes back to U-Boot. Any ideas on what's wrong here? Without claiming to know the FreeBSD code in any reasonable way, but using my experiance with low level stuff, it seems the memory management system expects a platform specific implementation of the" invalidate all instruction caches" functionality. Typically this is needed in situations where you might expect the cached results you might have loaded are possibly out of sync relative to the main memory contents. In some cases, it is just a good defensive programming (e.g. invalidating caches during the initalization sequence would be done just to make sure there is no funny business going on and the code from the main memory will be executed. At this stage, during initilization, the invalidation might not be necessary and the message in question could generated because there is some intial inventory of necessary serivices and APIs and thati failed. I expect someone with more intimate knowledge of this exact section of the FreeBSD code could provide more info, because, frankly, you made me curious. --=20 Eddy Petri=C8=99or From owner-freebsd-arm@freebsd.org Fri Mar 9 23:23:46 2018 Return-Path: Delivered-To: freebsd-arm@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 AA88FF2F8E9 for ; Fri, 9 Mar 2018 23:23:46 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 342C173208 for ; Fri, 9 Mar 2018 23:23:45 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: e5bef324-23f0-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id e5bef324-23f0-11e8-91c6-33ffc249f3e8; Fri, 09 Mar 2018 23:23:40 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w29NNY23009041; Fri, 9 Mar 2018 16:23:34 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520637814.84937.93.camel@freebsd.org> Subject: Re: No arch specific invalidate_icache_all available! From: Ian Lepore To: Eddy Petri , Steve Wills Cc: freebsd-arm@freebsd.org Date: Fri, 09 Mar 2018 16:23:34 -0700 In-Reply-To: References: <0ea2ec57-da6f-c8df-aaf4-d986b56a8ecd@FreeBSD.org> Content-Type: text/plain; charset="iso-2022-jp" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 23:23:46 -0000 On Sat, 2018-03-10 at 01:05 +0200, Eddy Petrior wrote: > 2018-03-09 20:56 GMT+02:00 Steve Wills : > > > > Hi, > Hi, > > > > > > > Trying to boot r330240 on my Raspberry Pi B, I'm getting: > > > > Booting [/boot/kernel/kernel]... > > /boot/dtb/bcm2835-rpi-b-rev2.dtb size=0x3366 > > Loaded DTB from file 'bcm2835-rpi-b-rev2.dtb'. > > Kernel entry at 0x1200100... > > No arch specific invalidate_icache_all available! > > Kernel args: (null) > > > > Then it goes back to U-Boot. Any ideas on what's wrong here? > Without claiming to know the FreeBSD code in any reasonable way, but > using my experiance with low level stuff, it seems the memory > management system expects a platform specific implementation of the" > invalidate all instruction caches" functionality. > Typically this is needed in situations where you might expect the > cached results you might have loaded are possibly out of sync relative > to the main memory contents. > > In some cases, it is just a good defensive programming (e.g. > invalidating caches during the initalization sequence would be done > just to make sure there is no funny business going on and the code > from the main memory will be executed. > > At this stage, during initilization, the invalidation might not be > necessary and the message in question could generated because there is > someintial inventory of necessary serivices and APIs and thati > failed. > > > I expect someone with more intimate knowledge of this exact section of > the FreeBSD code could provide more info, because, frankly, you made > me curious. > It sounds to me like the wrong uboot is in use, like the one for the armv7 flavor of rpi being used on the armv6 hardware (v6 and v7 require different cache maintenance operations). U-boot runs with caches enabled, so it definitely needs to flush both the dcache and the icache before jumping to the code it just loaded. -- Ian From owner-freebsd-arm@freebsd.org Fri Mar 9 23:24:45 2018 Return-Path: Delivered-To: freebsd-arm@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 84E3FF2F9E9 for ; Fri, 9 Mar 2018 23:24:45 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EDB7B7329F; Fri, 9 Mar 2018 23:24:44 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w29NOi5g066180 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Mar 2018 15:24:45 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w29NOiXK066179; Fri, 9 Mar 2018 15:24:44 -0800 (PST) (envelope-from fbsd) Date: Fri, 9 Mar 2018 15:24:44 -0800 From: bob prohaska To: "Michael Mitchell (megabyte)" Cc: Ian Lepore , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Garbled console output on Pi3 Message-ID: <20180309232444.GB65874@www.zefox.net> References: <20180307182117.GA55819@www.zefox.net> <1520628270.84937.56.camel@freebsd.org> <1F29E846-6EFE-4966-85BC-742F0B59B774@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1F29E846-6EFE-4966-85BC-742F0B59B774@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 23:24:45 -0000 On Fri, Mar 09, 2018 at 01:05:27PM -0800, Michael Mitchell (megabyte) wrote: > This happens to me when the cable FTDI USB/232TTL isn't seated very well. Pin header connectors do have > a limited cycle count, and become loose over time. The first thing I always blame is the cable... > > Michael Mitchell > I tried switching usb-serial adapters, in this case going from pl2303 to ftdi-232. Didn't make any difference. On connection, the console output looks fine. When I started up stress2 (as a regular, unpriviledged user) the console started putting out Mar 9 15:18:31 www kernel: ecsmedn tt hsrc2h epdid_ yi8e8l1d9 Mar 9 15:18:31 www kernel: <3t>crmide d tthor 2u spei dn oi8d8 n1-9898 1pt9r9r iterdi etdo tuessee nnto n-spcrheesde_nyti eslcdh Mar 9 15:18:31 www kernel: d_ycimedl dt Mar 9 15:18:31 www kernel: r2c mpdi dt hr828 1p9i9d tr8i8e1d9 9ot tursoiee dnu ostneo- unsoen -nporne-spernets enstc hsecdh_eydi_eylide Mar 9 15:18:31 www kernel: d Mar 9 15:18:31 www kernel: mdc mtdh rt2h rp2i dp id8 81898199 9t rtireide dt ot ou sues en onno-np-rperseesnetn tpsrce sheends_tyci ehlesddc_ Mar 9 15:18:31 www kernel: ield In this particular case, the other four ssh sessions began to exhibit snippets of scrambled out put also, for example Message from syslogd@www at Mar 9 15:18:31 ... www kernel: rc2m d and last pid: 89780; load averages: 16.42, 43.26, 23.613 up 0+21:25:33 15:21:17 45 processes: 1 running, 40 sleeping, 4 zombie CPU: 0.0% user, 0.0% nice, 1.3% system, 5.7% interrupt, 93.0% idle Mem: 13M Active, 2868K Inact, 105M Wired, 12M Buf, 788M Free Swap: 4096M Total, 34M Used, 4062M Free Message from syslogd@www at Mar 9 15:18:31 ...ATE C TIME WCPU COMMAND 88255 bob : rc2m d0c18d20tthr2 11128K 296K ufs 2 0:00 0.48% dirrename 88248 bob ldd_ 1 20 0 11128K 296K ufs 1 0:00 0.47% dirrename 88253 bob 1 20 0 11128K 292K ufs 1 0:00 0.45% dirrename 88254 bob 1 20 0 11128K 292K biowr 1 0:00 0.45% dirrename 88256 bob 1 20 0 11128K 296K ufs 3 0:00 0.43% dirrename 88249 bob 1 20 0 11128K 292K ufs 1 0:00 0.42% dirrename 88252 bob 1 20 0 11128K 292K ufs 1 0:00 0.41% dirrename also bob@www:/usr/src % Message from syslogd@www at Mar 9 15:16:06 ... www kernel: 38 8t2r0i0e dt rtioe du stedo nutoshner- 2pn ropeisde nn8t8 2-2psr3c hetesrdeinetd _ sytciohe eldd_ Message from syslogd@www at Mar 9 15:18:29 ... www kernel: 83s2>c0cm8d tthr2 pidd t8o8 us208e tnroine-dp rteos eunhseetd nsocnh-epdr_eysieenltdr Message from syslogd@www at Mar 9 15:18:31 ... www kernel: rc2m d and finally, in the session where stress2 was running 15:15:20 Loop #1 rw: run time 0+00:02:00, incarnations 8, load 70, verbose 1 swap: run time 0+00:02:00, incarnations 30, load 80, verbose 1 symlink: run time 0+00:02:00, incarnations 11, load 20, verbose 1 thr2: run time 0+00:02:00, incarnations 13, load 20, verbose 1 creat: run time 0+00:02:00, incarnations 9, load 80, verbose 1 dirrename: run time 0+00:02:00, incarnations 9, load 20, verbose 1 Message from syslogd@www at Mar 9 15:16:06 ... www kernel: 38 8t2r0i0e dt rtioe du stedo nutoshner- 2pn ropeisde nn8t8 2-2psr3c hetesrdeinetd _ sytciohe eldd_ Message from syslogd@www at Mar 9 15:18:29 ... www kernel: 83s2>c0cm8d tthr2 pidd t8o8 us208e tnroine-dp rteos eunhseetd nsocnh-epdr_eysieenltdr Message from syslogd@www at Mar 9 15:18:31 ... www kernel: rc2m d 20180309 15:21:32 creat.cfg, elapsed 00:06:14 Note: all.sh in stress2/misc is the preferred test to run. run: run time 0+00:05:00, incarnations 1, load 100, verbose 1 15:21:32 Loop #1 creat: run time 0+00:02:00, incarnations 5, load 100, verbose 1 So, I don't think it's the usb-serial adapter.... Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Sat Mar 10 00:03:49 2018 Return-Path: Delivered-To: freebsd-arm@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 DF765F3264B; Sat, 10 Mar 2018 00:03:48 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64CC07488D; Sat, 10 Mar 2018 00:03:48 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w2A03hOj039888 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 10 Mar 2018 01:03:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w2A03emW046232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 10 Mar 2018 01:03:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w2A03ec5095601 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 10 Mar 2018 01:03:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w2A03daR095600; Sat, 10 Mar 2018 01:03:39 +0100 (CET) (envelope-from ticso) Date: Sat, 10 Mar 2018 01:03:39 +0100 From: Bernd Walter To: Hans Petter Selasky Cc: Bernd Walter , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180310000336.GM86413@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308163026.z3ptrc7376smnsrt@unrelenting.technology> <20180308191131.GB86413@cicely7.cicely.de> <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> <20180309132539.GL86413@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180309132539.GL86413@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 00:03:49 -0000 On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote: > On Fri, Mar 09, 2018 at 01:19:54PM +0100, Hans Petter Selasky wrote: > > On 03/09/18 12:40, Bernd Walter wrote: > > >Will do the quirk test later. > > > > I don't see any stalls during plug-in, so it might be a request webcamd > > issues, which the device doesn't support. Try building webcamd with > > debug support. > > It is already build with debug. > But I don't see anything of special interest in the output. > > [24]sa# webcamd -d ugen0.4 > Linux video capture interface: v2.00 > IR NEC protocol handler initialized > IR RC5(x/sz) protocol handler initialized > IR RC6 protocol handler initialized > IR JVC protocol handler initialized > IR Sony protocol handler initialized > IR SANYO protocol handler initialized > IR LIRC bridge handler initialized > IR XMP protocol handler initialized > b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully > USB Video Class driver (1.1.1) > cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1 > pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner > pvrusb2: Debug mask is 31 (0x1f) > USBVision USB Video Device Driver for Linux : 0.9.11 > Attached to ugen0.4[0] > INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-/dev/usb-/dev/usb/input0 > > DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0 > Creating /dev/input/event0 > > I will redo a test with raspbian. > Waveshare delivered a binary kernel (so much about GPL) for their 7" HDMI C > until they changed something in the device firmware and upgraded for a newer > panel about 2-3 years ago. > This is the 10.1" HMDI B and it is a very early version I have, which however > should use a firmware similar to the newer 7" HDMI C. > I will retest with a stock Raspbian image to be sure I wasn't accidently > using a Waveshare image back then. > As far as I can see the Linux drivers just quirk the device to the egalaxy > driver, so they do know the Waveshare by ID. > I couldn't spot a difference between Linux and what is included in the webcamd > source. So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but it always needed some special binary support for Linux, no surprises here. The newer Rev 2.1 with the IPS panel claims to be the same and work with webcamd, at least I get data via /dev/input/event0, which looks reasonable with evdev-dump. That's an interesting starting point. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Mar 10 09:33:40 2018 Return-Path: Delivered-To: freebsd-arm@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 0B8F3F2F4AB for ; Sat, 10 Mar 2018 09:33:40 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh502-vm7.bullet.mail.kks.yahoo.co.jp (nh502-vm7.bullet.mail.kks.yahoo.co.jp [183.79.56.152]) by mx1.freebsd.org (Postfix) with SMTP id F0A626C3FB for ; Sat, 10 Mar 2018 09:33:38 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.141] by nh502.bullet.mail.kks.yahoo.co.jp with NNFMP; 10 Mar 2018 09:31:11 -0000 Received: from [183.79.100.135] by t504.bullet.mail.kks.yahoo.co.jp with NNFMP; 10 Mar 2018 09:31:11 -0000 Received: from [127.0.0.1] by omp504.mail.kks.yahoo.co.jp with NNFMP; 10 Mar 2018 09:31:11 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 355671.80340.bm@omp504.mail.kks.yahoo.co.jp Received: (qmail 27020 invoked by uid 60001); 10 Mar 2018 09:31:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1520674271; bh=iDDv0u8IWJ5b5Hzs4MT+LH90mIFXuIQSjIJIuJwTiPU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=itLJFxC0o804UuHC10ZW0iKiSKoou/0fmI/P7p+sP53+AhoGZHxS7N9Gpn4mfAYZZ6H+0DB6w0E61aDDt0YtirOgJQuETe0tOywgaGHCfggF6gz5N9uz/ZQvVmGCI6a1Sex0X2VC1n7NQO1CYrTe4NxbbRuv03oXJDq0QlEEZ8g= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ThbahFcgsBejKk0uGoY21WYh3OQb9v/V94pO+KpOyLS4/8eqEzjrbsLy7T2lYnIXdkTR7ge++mXYD2rdwPPJXYhK6RQUXSeLlKh0QbD77cdLXlt5chv/4IlK7GRsMkdSKvt3IGtnvBGoz2u4YoSGU7KkIxJWWyVEvT+TnplVeTM=; Message-ID: <408.23467.qm@web101707.mail.ssk.yahoo.co.jp> X-YMail-OSG: Y8mk.RQVM1kkk4R3UylLzqIKug_YKyMRkr.f.Km5t3boOKHENWexY2zZ47axeIg5NL_vHp0fL1eYLdEZaj_X94OsPlExdYXHBhkKc1jJEvuArzeKSlrF8oxVTRwQtYVbv5sGkgVb1oFB_ZrPCFYe60sF32N84ie5183HH9e4FpVJ_RGBiCGndYfJXq5qNhJcB94WK6uVzM.TBdKkurfcYIte8oKjzCXXf51Dl4jj09hsY.5qEYJ7JhCz7TH9TQDSFQ7sepow1MWuTTH8SL1QOK5ZwXYaun_coAalVkh.jnNDu1YCtshWC5eJxaETU._.mHWVLOWxEXlDYUY53idYs0or4MQnf7OeYCjqzjlKrGmHDoLQe5bFCHERLQA_Cuy.5as_HVN5GyPaUP2RPZDt0SIwzoTCXyBjpD.CH4b9AxA3VeP73hWyRuOCeZenxJ2HY9obNVpfZT.1QsNOmTCfL29Feday_U.wWl_83UcillvflxWztM7r29QXnApbl33s_9DTG.lct2cU_GUMIt2gUv1YQq9WZZTIazXuM6Q4aIQHUzIinTYocBe2ZSDsR.HGvqnSiWuKxKziWDTfFhRo5WumMNbbOYcHWdavXPyv1th85faOXqaYq1Hg4QkssF5t748PP4Ig15m1WykncaIeqQ-- Received: from [203.165.91.75] by web101707.mail.ssk.yahoo.co.jp via HTTP; Sat, 10 Mar 2018 18:31:09 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: dJQ5HdQVM1mXy5RtWaZTqK1IiX_X0_YTmcEb9fv.A7QM2YNPXlfDYUbQ8br6Nf_qOkk_DxjXekKrYQoCk_RAFU2n.dttoqRz.2mM1H2k6mPpm7LeMKbC3kkTz8QigyFWUYqN References: <64850.63077.qm@web101706.mail.ssk.yahoo.co.jp> <387823.67007.qm@web101711.mail.ssk.yahoo.co.jp> <812183.70978.qm@web101705.mail.ssk.yahoo.co.jp> <892631.23713.qm@web101718.mail.ssk.yahoo.co.jp> Date: Sat, 10 Mar 2018 18:31:09 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: solved Re: still hang up arm/ralink To: Michael Zhilin , "freebsd-arm@freebsd.org" In-Reply-To: <892631.23713.qm@web101718.mail.ssk.yahoo.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 09:33:40 -0000 Hi=0A=0AI do try to todays current. It' work find on RT1310.=0A=0Ahttps://g= ist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5=0A=0A=0AThanks=0A= =0AHiroki Mori From owner-freebsd-arm@freebsd.org Sat Mar 10 11:38:32 2018 Return-Path: Delivered-To: freebsd-arm@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 47CA3F32838 for ; Sat, 10 Mar 2018 11:38:32 +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 D6448700D5 for ; Sat, 10 Mar 2018 11:38:31 +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 EA27B1B0DF for ; Sat, 10 Mar 2018 11:38:30 +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 w2ABcUpk084774 for ; Sat, 10 Mar 2018 11:38:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2ABcU9G084773 for freebsd-arm@FreeBSD.org; Sat, 10 Mar 2018 11:38:30 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-arm@FreeBSD.org Subject: [Bug 222256] RPI random number generator underruns when BCM2835_RNG_USE_CALLOUT is set Date: Sat, 10 Mar 2018 11:38:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sylvain@sylvaingarrigues.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 11:38:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222256 Sylvain Garrigues changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |FIXED --- Comment #3 from Sylvain Garrigues --- Fixed by commit r330727. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Sat Mar 10 11:42:36 2018 Return-Path: Delivered-To: freebsd-arm@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 E737AF32A7D for ; Sat, 10 Mar 2018 11:42:35 +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 82AC5703DB for ; Sat, 10 Mar 2018 11:42: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CF3A11B249 for ; Sat, 10 Mar 2018 11:42:34 +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 w2ABgYFI000476 for ; Sat, 10 Mar 2018 11:42:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2ABgYjs000475 for freebsd-arm@FreeBSD.org; Sat, 10 Mar 2018 11:42:34 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-arm@FreeBSD.org Subject: [Bug 222255] RPI random number generator breaks kernel build when BCM2835_RNG_USE_CALLOUT is set Date: Sat, 10 Mar 2018 11:42:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sylvain@sylvaingarrigues.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 11:42:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222255 Sylvain Garrigues changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |FIXED --- Comment #1 from Sylvain Garrigues --- Fixed in r330727 --=20 You are receiving this mail because: You are the assignee for the bug.=