From owner-freebsd-current@freebsd.org Sun Jan 21 10:43:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 463ACEC54FE for ; Sun, 21 Jan 2018 10:43:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A599327F4 for ; Sun, 21 Jan 2018 10:43:00 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.231.178.168]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MQzoI-1eELWF40AY-00UMUG for ; Sun, 21 Jan 2018 11:37:50 +0100 Date: Sun, 21 Jan 2018 11:37:16 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: mounting UFS2 filesystem with access mode via fstab Message-ID: <20180121113743.1e6bf774@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/N81HJopBacYIBv.dlcVhj6C"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:m5g+a3ny4R+7dtGMYPzPEItlwQApPtunQDuRMXKkip75tmaZJIo W/I6P4djflHdHrvDrtYqz0s2gzuT0xAYI2sL8JXO1svRlmRBSix62fxFiwTP2L0Gz8giUMK aqFvwV+kYR+5xMC7L+coicgsCf2EnOR/+x8lDPCLwYvCQX2OVzz1szeI54xJL15QPe6SW5B Enwo52YULbkjoomfm0yIQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:4T66eANzaQk=:esjtZcBJoIb0hvlluVAn49 N97NUvm5iNKn+K1DyfleySveui3gmLa7ZSgaxpPKQlAWeoebGrX3co0kn16wqRaOI/aOSXkBu 5yuZ/5+S+g1lD7BYKWV4fY1nP9jyCayAJWUSzjzW02OBbOK2g2TPV8ltKKOviePzZJbns2tGB NUS7QVghvpd9MIoLY+Eh5DK+pPhSo3SqQ0adTutNd7iVwbcl7uPgbt8C81E+7+uEdk44PzEix /bXrm1Vj0ek8n04+bHB+R9xZsEy2ZKFFdx9M7D5VjePdE08sxeL1ZJ2JQHxU19WQpAmvD4i5Y 6krIADyGkSP2jBqjBIEESb7rL+WznnCeQ3yPQW96+shsI7wgEroKfzL7Zmsz4qKDGaZFo3I+f CuNhETvFiZUyTJXxXWmKqTvYl5vr8UQvomBb60iLo9rFOMOmFwVy2z74VwDAUZf1+TRxohAba Uug9hrX5Q4zIc+dHUBcVJSu8rSHT8flNeiO/F6WOf/5mtR0crQJCqI9AYq4og0XsNl/2Y8Xr0 sFTTIaVCuAVu5sfC85JE/XGJL3R+dO0qMBxFSZ+LNCixBf8F9kwJMTjDSJwh7gwABCkk84jou YDpfmvV35uGggtPf6P/4M/xG3NlaXUuaOu+Sz5gc85W5IwPaAmTXr5Sz+ZoK6hjOcstAJcoQ0 FwZ+vNP9xLGj+8ihWDDhyFkL9D1UqxHeIg73Sd1dwnDXbNkkKmQCB3F9jqwPTvmss4nBbK8pf HjUX10uZsRyO99G2SGLehTYlXgtWzCfEsbUCKVCqgfKlpT15hjzQlotNgdKl5XN+kj7pt1fEG t2nvxAkGbUIKrtylXRAGztaZ+MI/Q== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 10:43:02 -0000 --Sig_/N81HJopBacYIBv.dlcVhj6C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Recently, I ran into the problem mounting a newly created /tmp, when I swit= ched back from a tmpfs-backed /tmp to a UFS2/SSD/HDD backed /tmp.=20 The convenience to set mode=3D01777 for the memory/tmpfs backed /tmp seems = not to exist for UFS2 backed filesystems, since manpage mount(8) doesn't give me any option = provided via -o which could accomplish what I can achieve with mode=3D, see man tmpfs(5). Well, I guess I do miss something here or is this achievement reached on a = different path I'm unaware of? Thanks in advance, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/N81HJopBacYIBv.dlcVhj6C Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmRtdwAKCRDS528fyFhY lFTdAf9u01eAv4FPJx23ClcUieG3wixQ/jUDHi2or+VsumaCIxt6As6hEV8pXs5z +OG9X+awZCirKzaXAe5KiCA/OOQMAf9GJAnLQqRU67Pu+M8BpewX+C/zAbR3ScIc mUo5MhhjQShKtInxi+vvkREkBa551B5CwI5wcbEmRb/RBE1/06f9 =7guK -----END PGP SIGNATURE----- --Sig_/N81HJopBacYIBv.dlcVhj6C-- From owner-freebsd-current@freebsd.org Sun Jan 21 15:42:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D55B8ECFAA5 for ; Sun, 21 Jan 2018 15:42:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 6B48170854 for ; Sun, 21 Jan 2018 15:42:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id g1so11776294wmg.2 for ; Sun, 21 Jan 2018 07:42:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=rARkayDCQbYDYkTEEDphHO7L8WyJw4sT3yAl93gpVAg=; b=GPyNiF2hvsKuMX8p4CEHwMD+N4OEZud69hTyUNYiogEWUvwulecodZdJ0nwMt6dL0c r+hN5ZPWeFCInUpEpueUT2PaEYQidhdMHmxfHUADfJcFkXDaX5aCpM8XO4nX2D/MS1wp 8GMqXWWNNfJ0ap2gJMenNJgq31/zSOR9NhlNtega8y96cQ7WETvgmvo4OQ2B9Jv+PZjX 8la0HBo7iTxmXP1esfHMRuixTJCNEPx7OPXz5ikgRfAoo0tQXwF6TmCAcTXPhdxghZpX GstDKKiSCQGdenn2Q6j5XNvjyN6Z66zvM7IqOwgU5QB5xC63+9DYkfgz2n8IaD9vSV5Z pygw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rARkayDCQbYDYkTEEDphHO7L8WyJw4sT3yAl93gpVAg=; b=pZ1llkwq7wFaIie60ROCQT2Q9lJ7sjFl9EWFsFEbE0AYgz4AoxVHQT/4XRKxPBQe8s yXhm/LsvIAKJggkVwxxzsJgdFXzcVE4/1ri3X0lfn0Sry0ckzYmOyCSYNBeOsOE65emS VghE0qotJC+l4iK4NPvGLe84m/osUgnqgIdAB/XJJ/2T6vHB1K3S/8md81/cFqhWHE0V f3wameyXacWPRWmrqj2LcAXup5+Jak9lP5svUaMVTgpbDGDivrVY/+3/Ntxh7wm1Z1vC ekhp+mkKuxSFx6i56G2NOsQXbomWQwsh5bQeRSPXmEynHN2vLw+IMJFZCiFHIYZeLzCr R7/Q== X-Gm-Message-State: AKwxytcOs8cr94ngiFz8m9O4AgDoUo8O9m8/KRLgtvCLXLtcy2W8KR/q f2IYeivtkfXBSsyRt2NsjDG97sBG1kQGa5bI8Ic92w== X-Google-Smtp-Source: AH8x2268cPuwt15IbUceqFkg16mp/ELeYq4D/Mh0CWx1BvyadV2Fqn+FqID7qPo4En2Nd75EGyiglibE2k9OHZJqzPo= X-Received: by 10.28.179.9 with SMTP id c9mr2756647wmf.99.1516549340562; Sun, 21 Jan 2018 07:42:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Sun, 21 Jan 2018 07:41:40 -0800 (PST) From: Johannes Lundberg Date: Sun, 21 Jan 2018 15:41:40 +0000 Message-ID: Subject: Periodical interrupt storm when playing game with USB keyboard To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 15:42:22 -0000 Hi Finally I found the root to the problem that's been having me puzzled for the last week. I started playing UT2004 on my laptop while away from home. Worked perfectly. When I'm home and connect external display+mouse/keyboard, I get weird random lag. It is intr process that goes up to 100% CPU usage (swi4: clock) for a couple of seconds every 30 seconds or so, but only when I'm moving around in the game. To move around you need to hold down any of the wasd-keys. Turns out, the interrupt storms only happen when I use my external keyboard, not with the laptop keyboard. The internal keyboard is: atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 and external (Microsoft sculpt ergonomic desktop): ugen0.2: at usbus0 ukbd0: on usbus0 The game runs with a linux binary. 32/64bit both act the same. It uses libSDL-1.2 from /compat/linux/lib for rendering but not sure about input events. I tried lowering the key repeat rate both with xset and kbdcontrol but it has no effect. I don't have any wired USB keyboard to try with. Anyone have a clue to what's going on? Hardware is Dell Latitude E7270 with FreeBSD 12-CURRENT drm-next-kmod linux-c6 From owner-freebsd-current@freebsd.org Sun Jan 21 17:15:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6958EED26E9 for ; Sun, 21 Jan 2018 17:15:16 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 EF901735BB for ; Sun, 21 Jan 2018 17:15:15 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id f71so12037693wmf.0 for ; Sun, 21 Jan 2018 09:15:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=vPS7zRhPAqr0rE4m2GmLi6i0Gu88NQqZ7ksXU82KonI=; b=aQfL5B4/emQs+eMXRKqalh/ZLqJ94zTrKou1tXNbzuX5kYnd3hGSUKIOzt51NZqoIS g7yBL0F1We/89xiuqyP7CchiVhMSdpqBaxD0S0mDU7Sb1JyvEeXbEwZ6Tp7IVyuAUFFJ aR3aDDejyCcHx/cyKVyNZ4hJxNL30FyZxGUuMGkp+JAwC3KM4RyxIumYSqkE6esnjbE5 VHU/XeslZyOR+SYkzlTLTWxuSc8gcwYrST68lole7kEJ9EfMFdIrcdv0PFGhWA7u8ZjD xPqbiJN3/5tzEAOhTV1tq4ZU/vAPnEGiUQnSA6IE0YKPqbeVqomnWpEsGjwIGwAt9Vcr GIXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=vPS7zRhPAqr0rE4m2GmLi6i0Gu88NQqZ7ksXU82KonI=; b=PQZ8PxDT0IQjdbPh1F1dLWvh5CpxgnXBQ3WWzAR9tkgh99mP9gFPeHNts4o5qvTXfP hq5t495OwCJYb1R3UUZZCpH/x3NtnfiOp2+3ek7ny6vmemEkvpYkEmYLpcCGwPkk6Vac WbgRU7zC+b/lflyeWZeTMTDRsbcEcm3RgpGTDkb5wd/B3qV2ElcMIN3Ih4TMLRsPhEJC oPJUVZW6JA70phi/Y9RAXasA5gb2Pb8zVsGKDslUUBV45YgmNf0saowDKLkiG0z8FczO NsTU0uKcqTJPKs4YF02SVxUVQALR91b5bGWO3zkx/y37NreEayjn4AAzMVkVf9k0ej7f 7SfQ== X-Gm-Message-State: AKwxyte5ZroISS1qfum9VNkg5t5yvokAbcJGxyMrM2Jjrq9f5RSKOw+c soqY8jtUvsYP31ECJXltMSnogg== X-Google-Smtp-Source: AH8x227H4Io+JXoIAPJMnwp3fJEQWqB0g8E9ZoBkYIUejI8ujdUcM6cLS/yBwXlzDUkTs5rjBFPa8A== X-Received: by 10.28.239.3 with SMTP id n3mr3524763wmh.88.1516554914408; Sun, 21 Jan 2018 09:15:14 -0800 (PST) Received: from ernst.home (p5B023419.dip0.t-ipconnect.de. [91.2.52.25]) by smtp.gmail.com with ESMTPSA id v31sm27026739wrb.12.2018.01.21.09.15.13 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 21 Jan 2018 09:15:13 -0800 (PST) Date: Sun, 21 Jan 2018 18:15:11 +0100 From: Gary Jennejohn To: "O. Hartmann" Cc: FreeBSD CURRENT Subject: Re: mounting UFS2 filesystem with access mode via fstab Message-ID: <20180121181511.0e1c02d4@ernst.home> In-Reply-To: <20180121113743.1e6bf774@thor.intern.walstatt.dynvpn.de> References: <20180121113743.1e6bf774@thor.intern.walstatt.dynvpn.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 17:15:16 -0000 On Sun, 21 Jan 2018 11:37:16 +0100 "O. Hartmann" wrote: > Recently, I ran into the problem mounting a newly created /tmp, when I switched back from > a tmpfs-backed /tmp to a UFS2/SSD/HDD backed /tmp. > > The convenience to set mode=01777 for the memory/tmpfs backed /tmp seems not to exist for > UFS2 backed filesystems, since manpage mount(8) doesn't give me any option provided via > -o which could accomplish what I can achieve with mode=, see man tmpfs(5). > > Well, I guess I do miss something here or is this achievement reached on a different path > I'm unaware of? > chmod 1777 /tmp as root -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Jan 21 19:00:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BE0CEB48EA for ; Sun, 21 Jan 2018 19:00:47 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B95A877612 for ; Sun, 21 Jan 2018 19:00:46 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.231.178.168]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LnDof-1fICRj30Vp-00hQZ1; Sun, 21 Jan 2018 20:00:42 +0100 Date: Sun, 21 Jan 2018 20:00:09 +0100 From: "O. Hartmann" To: Gary Jennejohn Cc: "O. Hartmann" , FreeBSD CURRENT , "N.J. Mann" Subject: Re: mounting UFS2 filesystem with access mode via fstab Message-ID: <20180121200036.4982e096@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180121181511.0e1c02d4@ernst.home> References: <20180121113743.1e6bf774@thor.intern.walstatt.dynvpn.de> <20180121181511.0e1c02d4@ernst.home> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ThvILhH20OeyTSfLNVLNn=v"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:lWhCO0IC0nL61JaSEr7OtXc/Mu3y5v386cQGmaqxhRyLURhsi7v nTge/QHGtcKYL3WndCS9PQ+Q7Jx09GDVQ9Ulkhw6lyFYT3Z0lQ16s94Jj7XG1Yc5/whW8zb y4YmhG/GeeoZWwzLrqfsWAcSZcjjhKBpe7c+dt8XiO1FQhmOp+jE1tzA3Rqtz2kkCtFkRi1 qMcPOMvAXJa/FMKjOCcDg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Dko/0TruCqY=:tWKRCcjQX2900+NEcx30WR XCZYlB/quKj2XL9AKsXlTf7Nrn6s30o4upF53jRtTTeFotqO+bmkQXd+28luZH7jVJ9MBI5bX HcGmPCQZGwzyl8gXfpoJyFGq5JqKESzqMpGgpMlu0239B6G+wCUCx6rzXL/KKqKMX5t/S33lm FXLYXX75lPZ3smX37JPR81ylmafhET339+584X/iH4/onj7gYhKD4EC1lRyGbyap1tHl2Jonl 8rA+CQDQmWcIG36ELJD7EUVHzM0v5jmtIX/bPWyD4ekfUC5yDrBv/nZKI2JR2YLOPiFe+G18b +DllGvRRvnnvCSPt+YqV0XFzJksxES0Ym9xeUxv97PoF0ypJBPtlZZ+KrpyYaW9gTaW0HITVr D6gAyFcDYoR4Hy1SkxKWLo7CtE+mCtEZx+grfpwMHl56S8OYgV4rqk9zMDVldxPegTs2+NTms 8ZMxmjAPc5ehnnmKI2E0kziC1FwfJcdzfPyuq0VrglzsBQ++HWJzEBcmhOYoURJpUlLskeydH 9qwCt6O0BIEz4EVMwTjdQfTr2CPG6xS021GaBuratgbbMAVjUIlmFv9+MeFaTBR0nVv8NK0gL sqcKjwongEep1sMjTLhs8MMRZfTGOBTQHuUlmpwcbOhdyF0xKV2Fnw6EJgsU4HK26gEX6JhBv Acy9yRSqJxcb3asvQGen4Zi+Kfiva6Yy1oCF0CFWWk3vAIlSJ6ww1Xio4bT1kI8b0btolxLB9 kNZU2N4T8HQ8Ocm3/8DkSRtKN6tvhuJ8BEPqU4IIh3eo3uA81UGq9gKmV8JBPYrpZfdkPdliO CdP1MFobtf6eUKXivSnB7oLCtUTmA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 19:00:47 -0000 --Sig_/ThvILhH20OeyTSfLNVLNn=v Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 21 Jan 2018 18:15:11 +0100 Gary Jennejohn schrieb: > On Sun, 21 Jan 2018 11:37:16 +0100 > "O. Hartmann" wrote: >=20 > > Recently, I ran into the problem mounting a newly created /tmp, when I = switched back > > from a tmpfs-backed /tmp to a UFS2/SSD/HDD backed /tmp.=20 > >=20 > > The convenience to set mode=3D01777 for the memory/tmpfs backed /tmp se= ems not to exist > > for UFS2 backed filesystems, since manpage mount(8) doesn't give me any= option > > provided via -o which could accomplish what I can achieve with mode=3D,= see man > > tmpfs(5). > >=20 > > Well, I guess I do miss something here or is this achievement reached o= n a different > > path I'm unaware of? > > =20 >=20 > chmod 1777 /tmp as root >=20 Well, that is the way we do it usually. But is there now way to perform the setti= ngs via fstab entry? Look at man tmpfs, man mount_msdosfs, for instance, they provide op= tions which can be put into the option column of fstab. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ThvILhH20OeyTSfLNVLNn=v Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmTjVAAKCRDS528fyFhY lGREAf9zFI0xx/zJjjb0qXoH4GIbqPSqjfD75aUbDlPqViFzK7osYlUT34QPkgQ7 2V8arBzJBUWd3Xd1BL2XOccHErwMAf0bFYLB+sCwg1EQqnEYnFbmB1NiDsXt7Qjk rvn3iAtQ7/MYr+HKuKz1tzyFFPJl4no5ZrZbKYomqd1fMPG1qYCs =vty0 -----END PGP SIGNATURE----- --Sig_/ThvILhH20OeyTSfLNVLNn=v-- From owner-freebsd-current@freebsd.org Sun Jan 21 19:25:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65743EB618E for ; Sun, 21 Jan 2018 19:25:13 +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 47937788E3 for ; Sun, 21 Jan 2018 19:25:12 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 879995cd-fee0-11e7-93a5-cd02e7dc7692 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 879995cd-fee0-11e7-93a5-cd02e7dc7692; Sun, 21 Jan 2018 19:23:16 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0LJO38U001720; Sun, 21 Jan 2018 12:24:03 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516562643.42536.96.camel@freebsd.org> Subject: Re: mounting UFS2 filesystem with access mode via fstab From: Ian Lepore To: "O. Hartmann" , Gary Jennejohn Cc: FreeBSD CURRENT , "N.J. Mann" Date: Sun, 21 Jan 2018 12:24:03 -0700 In-Reply-To: <20180121200036.4982e096@thor.intern.walstatt.dynvpn.de> References: <20180121113743.1e6bf774@thor.intern.walstatt.dynvpn.de> <20180121181511.0e1c02d4@ernst.home> <20180121200036.4982e096@thor.intern.walstatt.dynvpn.de> 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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 19:25:13 -0000 On Sun, 2018-01-21 at 20:00 +0100, O. Hartmann wrote: > Am Sun, 21 Jan 2018 18:15:11 +0100 > Gary Jennejohn schrieb: > > > > > On Sun, 21 Jan 2018 11:37:16 +0100 > > "O. Hartmann" wrote: > > > > > > > > Recently, I ran into the problem mounting a newly created /tmp, > > > when I switched back > > > from a tmpfs-backed /tmp to a UFS2/SSD/HDD backed /tmp.  > > > > > > The convenience to set mode=01777 for the memory/tmpfs backed > > > /tmp seems not to exist > > > for UFS2 backed filesystems, since manpage mount(8) doesn't give > > > me any option > > > provided via -o which could accomplish what I can achieve with > > > mode=, see man > > > tmpfs(5). > > > > > > Well, I guess I do miss something here or is this achievement > > > reached on a different > > > path I'm unaware of? > > >    > > chmod 1777 /tmp as root > > > Well, > that is the way we do it usually. But is there now way to perform the > settings via fstab > entry? Look at man  tmpfs, man mount_msdosfs, for instance, they > provide options which > can be put into the option column of fstab. > You don't need to do it via the fstab, because the permissions are persistent in the filesystem.  Just mount the filesystem on /tmp by hand, then chmod /tmp after mounting it and then it will always have those permissions (wherever it is mounted). With tmpfs there is no persistent storage to keep the permissions, so there must be a way to set it from fstab.  With msdosfs there is no way to store the unix-style permissions in the fs, so there must be a way to set it from fstab.  For UFS, the mode is just stored in the fs. -- Ian From owner-freebsd-current@freebsd.org Sun Jan 21 19:37:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDCFBEB6AE7 for ; Sun, 21 Jan 2018 19:37:52 +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 B54C379135 for ; Sun, 21 Jan 2018 19:37: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 4108F2604F8; Sun, 21 Jan 2018 20:37:50 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg , freebsd-current References: From: Hans Petter Selasky Message-ID: Date: Sun, 21 Jan 2018 20:34:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 19:37:53 -0000 On 01/21/18 16:41, Johannes Lundberg wrote: > Hi > > Finally I found the root to the problem that's been having me puzzled for > the last week. > > I started playing UT2004 on my laptop while away from home. Worked > perfectly. When I'm home and connect external display+mouse/keyboard, I get > weird random lag. > > It is intr process that goes up to 100% CPU usage (swi4: clock) for a > couple of seconds every 30 seconds or so, but only when I'm moving around > in the game. To move around you need to hold down any of the wasd-keys. > > Turns out, the interrupt storms only happen when I use my external > keyboard, not with the laptop keyboard. > > The internal keyboard is: > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > > and external (Microsoft sculpt ergonomic desktop): > ugen0.2: at usbus0 > ukbd0: 2.00/7.97, addr 1> on usbus0 > > The game runs with a linux binary. 32/64bit both act the same. > It uses libSDL-1.2 from /compat/linux/lib for rendering but not sure about > input events. > > I tried lowering the key repeat rate both with xset and kbdcontrol but it > has no effect. > > I don't have any wired USB keyboard to try with. > > Anyone have a clue to what's going on? > > Hardware is Dell Latitude E7270 > with > FreeBSD 12-CURRENT > drm-next-kmod > linux-c6 Hi, What does "vmstat -i" say? The issue can also be caused by a timer with a small or zero timeout. This can be checked by setting: kern.eventtimer.periodic=1 in /boot/loader.conf and rebooting. --HPS From owner-freebsd-current@freebsd.org Sun Jan 21 20:36:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8446FEB9991 for ; Sun, 21 Jan 2018 20:36:07 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 180C87B3C4 for ; Sun, 21 Jan 2018 20:36:07 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id r78so13133807wme.0 for ; Sun, 21 Jan 2018 12:36:07 -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=RCUIibq8/HZDU2m89IMHJzRbE0wMFHS8a0DdJX44kvk=; b=tbN/JX/ZbFKCDfKR6LB5MARHn+cMyTIihbrnKvCRTtR7r2jjXGQbauVnMLwbn94fh5 p2V9MFRFSdVEnZDXoYkAZl3t69zowRparaTd9lVrkyp68TFRRqgzHpQgqqxp1wCVdg8X +kMtOUKxFV8apAHz+HEkRoCrPYLaO+Qe62EKZsJB8JlpPwyNs89TIw/3e212lwZRcEtp A/7RhhStsuvC0aAxWe+NPqlwdbahdwC3no9WxEhUGoLQ3tgYH0co9u/lb0XsKiKu/uNq h4fb+6zQq2wL28acjilPMxpl9H3vwtuBqrBxPsZTs1vykTyqi8aTiA0/K7mUdtwQRLKG SUEg== 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=RCUIibq8/HZDU2m89IMHJzRbE0wMFHS8a0DdJX44kvk=; b=B/vVZUv6N8xzN+g6fiS2g3dUAWSHiU2Z3od+GFRWRRqDxgCKt/A7X/RqR7Ge1WyL7R CPP4i8vfbzmBwb1XDGgj8MN2MVoww5RTTQmRIVSnaaPs1D1g4MgE4CL/9dXqjIDWBpHk KUAl6UH5ow4UWhLEiMmf6l4MBwgaTCI1RQ+oQTQDJQ4d4YLg/hvUIp1+2E6pSOh8EH7k bCr3/9a6+FnsQ3q/GXYAXED+riwYOOvbgsceinC+xVWnBi+Fe1Fh/dQE24eo2Xhoc+W5 0cEOViP8hLoaC9SDvSuyn7sDqdtau3xXzDERxcx8HauY7INYA3WJS1nzEEOpIZ7lY42h D8xw== X-Gm-Message-State: AKwxytfdiSA4HVUhFQjohfDLorFlf77V0rCpwIzHsxNDnRUEWM5LJf6Z 393OCbWWAo/QFF2gsIkzDWQSPxrH3wF9fJa90UF6vA== X-Google-Smtp-Source: AH8x226Lr2j/vcWTOc5+W+Q5RomnB/AvKikBpaBf5/DsceepBnojxcjqIXJY1HNn9Q5DLjgB2MLYU29f+Q1a7ovtgyI= X-Received: by 10.28.101.196 with SMTP id z187mr3613647wmb.29.1516566965006; Sun, 21 Jan 2018 12:36:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Sun, 21 Jan 2018 12:35:24 -0800 (PST) In-Reply-To: References: From: Johannes Lundberg Date: Sun, 21 Jan 2018 20:35:24 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Hans Petter Selasky Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 20:36:07 -0000 Sending the same again, this time cc the list. On Sun, Jan 21, 2018 at 7:34 PM, Hans Petter Selasky wrote: > On 01/21/18 16:41, Johannes Lundberg wrote: > >> Hi >> >> Finally I found the root to the problem that's been having me puzzled fo= r >> the last week. >> >> I started playing UT2004 on my laptop while away from home. Worked >> perfectly. When I'm home and connect external display+mouse/keyboard, I >> get >> weird random lag. >> >> It is intr process that goes up to 100% CPU usage (swi4: clock) for a >> couple of seconds every 30 seconds or so, but only when I'm moving aroun= d >> in the game. To move around you need to hold down any of the wasd-keys. >> >> Turns out, the interrupt storms only happen when I use my external >> keyboard, not with the laptop keyboard. >> >> The internal keyboard is: >> atkbdc0: port 0x60,0x64 irq 1 on acpi0 >> atkbd0: irq 1 on atkbdc0 >> >> and external (Microsoft sculpt ergonomic desktop): >> ugen0.2: at usbus0 >> ukbd0: > 2.00/7.97, addr 1> on usbus0 >> >> The game runs with a linux binary. 32/64bit both act the same. >> It uses libSDL-1.2 from /compat/linux/lib for rendering but not sure abo= ut >> input events. >> >> I tried lowering the key repeat rate both with xset and kbdcontrol but i= t >> has no effect. >> >> I don't have any wired USB keyboard to try with. >> >> Anyone have a clue to what's going on? >> >> Hardware is Dell Latitude E7270 >> with >> FreeBSD 12-CURRENT >> drm-next-kmod >> linux-c6 >> > > Hi, > > What does "vmstat -i" say? > Don=E2=80=99t remember the exact values now but it says cpu0:timer is getti= ng A LOT of interrupts. Like at least 10-50x the others. Otherwise normal. > > The issue can also be caused by a timer with a small or zero timeout. > > This can be checked by setting: > kern.eventtimer.periodic=3D1 > > in /boot/loader.conf and rebooting. > Wow, kern.eventtimer.periodic=3D1 really made all the difference. No problem at all now and all cpu timers have equal interrupt total and rate. What does kern.eventtimer.periodic do? The sysctl description wasn't that elaborate... > --HPS > From owner-freebsd-current@freebsd.org Sun Jan 21 20:45:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6270CEBA23E for ; Sun, 21 Jan 2018 20:45:43 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 E51C17B944 for ; Sun, 21 Jan 2018 20:45:42 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id v15so3661023wrb.8 for ; Sun, 21 Jan 2018 12:45:42 -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=qM4nVWE3FUSBBkTmjZfLnxHiYh71Be190jAvqVDUfo8=; b=CjOtJCeSJcV8+QOgUffy0DOX8q8J9h2xbH8XC4i44krldMAPyMCLoCLtrabNEKD/b+ w/+Exq+gEHgA5jyX4er5bxwNBGZtaj8z0fGm1QZHglhcgSRVNVDM4b1MVXkYpPsIEwpC Unh7u5ImtueB3cBvch7hUcUqXadMdhfuZv3qK+dNQ/VqI9VanDGg+hzaWB8KIWerFnXZ ATTiAFDxFefYQ9+Ej+MBBJRtavMOA1e1dzTImymmzr/8UfCBCCE2NE+hQBgfv2UxuNLl UQkycczEGyWyE6OIbzYqAtVtLV8rQfO26HYpmVHZ+GCObrc24jzGaNiNx0ldp9WZUFMH Dqhw== 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=qM4nVWE3FUSBBkTmjZfLnxHiYh71Be190jAvqVDUfo8=; b=jSYQExbRq8ib2TjXJUH6vyGo73PS8iQjL87zsuVK0oeNJDz99HhYNG6KOwnivr4ztp qnTQLTs4Tts8L7Q7ByS1Dp4hZd7KHITyNNIkXSKvrGiExsz/Ny46ksYe2ohjwNtdzuSu J4TmpmMOn9PC4pWG9wLBLVeExuMu2HqRLFjRyp9esEo+a1NAl3pI6vNc+nROceUl8BMA EuPRzFd1XXIzAGxwv9b73bFpKb4gAyGrz6QepIZlMaK++4FMQoVBI0UDbUNKBULqrIzg niZZLkR09Cj7Xvxr724OZ8X0mPaiQ2Fs4AYJBpeMsPr534jePzMVHtqd1yLgA1U6KQQ2 lffQ== X-Gm-Message-State: AKwxyteTif4z2uXIrbs5I+ZEmGMLw5CaAygto0e4xiR3O8R7GzEmZeYc tClL4YygFeEOGNTgKLwVaGJaycFAE+FVajft8uM= X-Google-Smtp-Source: AH8x225ST/OXdsvpNsLrKxuz/mcXi0aixvgnF12T/6YVnXGBDoloh630fmNj3bBT8nrIlM3yC+GxBBqbfLHiK5Bivic= X-Received: by 10.223.196.147 with SMTP id m19mr4545946wrf.56.1516567541381; Sun, 21 Jan 2018 12:45:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Sun, 21 Jan 2018 12:45:01 -0800 (PST) In-Reply-To: References: From: Johannes Lundberg Date: Sun, 21 Jan 2018 20:45:01 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Hans Petter Selasky Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 20:45:43 -0000 On Sun, Jan 21, 2018 at 8:35 PM, Johannes Lundberg wrote: > Sending the same again, this time cc the list. > > > On Sun, Jan 21, 2018 at 7:34 PM, Hans Petter Selasky > wrote: > >> On 01/21/18 16:41, Johannes Lundberg wrote: >> >>> Hi >>> >>> Finally I found the root to the problem that's been having me puzzled f= or >>> the last week. >>> >>> I started playing UT2004 on my laptop while away from home. Worked >>> perfectly. When I'm home and connect external display+mouse/keyboard, I >>> get >>> weird random lag. >>> >>> It is intr process that goes up to 100% CPU usage (swi4: clock) for a >>> couple of seconds every 30 seconds or so, but only when I'm moving arou= nd >>> in the game. To move around you need to hold down any of the wasd-keys. >>> >>> Turns out, the interrupt storms only happen when I use my external >>> keyboard, not with the laptop keyboard. >>> >>> The internal keyboard is: >>> atkbdc0: port 0x60,0x64 irq 1 on acpi0 >>> atkbd0: irq 1 on atkbdc0 >>> >>> and external (Microsoft sculpt ergonomic desktop): >>> ugen0.2: at usbus0 >>> ukbd0: >> 2.00/7.97, addr 1> on usbus0 >>> >>> The game runs with a linux binary. 32/64bit both act the same. >>> It uses libSDL-1.2 from /compat/linux/lib for rendering but not sure >>> about >>> input events. >>> >>> I tried lowering the key repeat rate both with xset and kbdcontrol but = it >>> has no effect. >>> >>> I don't have any wired USB keyboard to try with. >>> >>> Anyone have a clue to what's going on? >>> >>> Hardware is Dell Latitude E7270 >>> with >>> FreeBSD 12-CURRENT >>> drm-next-kmod >>> linux-c6 >>> >> >> Hi, >> >> What does "vmstat -i" say? >> > > Don=E2=80=99t remember the exact values now but it says cpu0:timer is get= ting A > LOT of interrupts. Like at least 10-50x the others. Otherwise normal. > > >> >> The issue can also be caused by a timer with a small or zero timeout. >> >> This can be checked by setting: >> kern.eventtimer.periodic=3D1 >> >> in /boot/loader.conf and rebooting. >> > > Wow, kern.eventtimer.periodic=3D1 really made all the difference. > No problem at all now and all cpu timers have equal interrupt total and > rate. > > What does kern.eventtimer.periodic do? The sysctl description wasn't > that elaborate... > Replying myself. Found some explanation at https://www.freebsd.org/cgi/man.cgi?query=3Deventtimers&apropos=3D0&sektion= =3D0&manpath=3DFreeBSD+12-current&arch=3Ddefault&format=3Dhtml With periodic each cpu timer has an interrupt rate of 1999 while on one shot it's around 700. Maybe not a very power efficient and precise solution to the problem but it works. > > >> --HPS >> > > From owner-freebsd-current@freebsd.org Sun Jan 21 21:10:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A627AEBB602 for ; Sun, 21 Jan 2018 21:10:33 +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 6BD217C64C for ; Sun, 21 Jan 2018 21:10:33 +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 19FD32604F8; Sun, 21 Jan 2018 22:10:31 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg Cc: freebsd-current References: From: Hans Petter Selasky Message-ID: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> Date: Sun, 21 Jan 2018 22:07:39 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 21:10:33 -0000 On 01/21/18 21:45, Johannes Lundberg wrote: > What does kern.eventtimer.periodic do? The sysctl description wasn't > that elaborate... It turns off re-programming the timer every time there is a new callout with earlier completion time. --HPS From owner-freebsd-current@freebsd.org Sun Jan 21 21:22:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57397EBC235 for ; Sun, 21 Jan 2018 21:22:19 +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 E913B7D12B for ; Sun, 21 Jan 2018 21:22:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 23a5a400-fef1-11e7-8dac-d32f5c2d02ef X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 23a5a400-fef1-11e7-8dac-d32f5c2d02ef; Sun, 21 Jan 2018 21:22:10 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0LLM5wd001899; Sun, 21 Jan 2018 14:22:05 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516569725.42536.99.camel@freebsd.org> Subject: Re: Periodical interrupt storm when playing game with USB keyboard From: Ian Lepore To: Hans Petter Selasky , Johannes Lundberg Cc: freebsd-current Date: Sun, 21 Jan 2018 14:22:05 -0700 In-Reply-To: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> 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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 21:22:19 -0000 On Sun, 2018-01-21 at 22:07 +0100, Hans Petter Selasky wrote: > On 01/21/18 21:45, Johannes Lundberg wrote: > > > > What does kern.eventtimer.periodic do?  The sysctl description > > wasn't > > that elaborate... > It turns off re-programming the timer every time there is a new > callout  > with earlier completion time. > > --HPS Well, it does more than that.  It makes the system run "the old way" where there are periodic timer interrupts that happen whether they need to or not (bad for power saving), and there's no way to schedule anything to happen on intervals other than when the periodic ticks occur (so if kern.hz = 1000 and you ask to sleep for a microsecond you may actually sleep up to a millisecond). -- Ian From owner-freebsd-current@freebsd.org Sun Jan 21 22:58:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BDF7EBFFA8 for ; Sun, 21 Jan 2018 22:58:03 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 1D14A7FA34; Sun, 21 Jan 2018 22:58:03 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id i186so12983829wmi.4; Sun, 21 Jan 2018 14:58:03 -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=t3D0JAnLAY2qwXkfrtzPQtsfTViZXL2ikSmvvaqBoPo=; b=CwvDxPX6yYNliulDR00hBF9CEDY/DrXHYsUZldbMKHEI65stAFtQ7N4UrNPVNmYNuf iI7DkTUdiRVqe6CP2GIw4dsvW6kvcfiTv71PWJeFxPU0ika1ag6g3Hn5SRO0dXzCslKf kdGO6GOncjIfkhhW0n2i3aGLLN7Fcxu885qDxynFcobYRvHSHdz8DO9t8tA+R4AGjgyW Wo7Ny/RBdXvHgpAj55K+J58rYmHV1L1dGm/m7a/ygT7VOiCA2wuN4Dr8t9gx20L5vStS NOaWEw7Ye6cvKvyi7u/SBykb0KRyb0g5NFF0wrLGiDUWBtY8II9H7PrZ993SNv6qkhQN naag== 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=t3D0JAnLAY2qwXkfrtzPQtsfTViZXL2ikSmvvaqBoPo=; b=axSgumSvHs2ni+4WQuOJQMRCDHm6viY02GNrXrMA//5ABWAwpbHJ+rVYeNZO14NVHB ERFzXPBTOm1Y6snhvfvyKx5zey7ahPWj8chRf09raD2K3KX+uDaUHnJA/NT4/Mce4vSw fFyThiDmn9MyUOsvvReL1QKRcfkUO0ptKRoKVMctil6hHC/5kTbqQs+vO83oAgkWPVuv dakM9k0kV0e0tFkgd/MyWMm5EL4dQetW2kYPKjfBUY9EuAe2RkHX3TWVadrHzN/W6jjG ZkX/qpZRTGlC011AaLfir2IZw2Cu4K5boUytOlSyRGQVkxdgBpKeSAe+KndEbxasBW7r kS1Q== X-Gm-Message-State: AKwxytef5waBV61uJRqgivI9sYRgpTIrB/we8thrzizw0tehVXbcvnhE ZGqpv6IfAbuVXHwrmipc92Spok6AHst/b3e1iNU= X-Google-Smtp-Source: AH8x227geMhWzUMxBnXrXrHHrHwa0d+iYwgI63JQhnN0UC4QNFr3QKpyOCm+meIsvotLKrH2CCrpyR1GIo7LTysGVgA= X-Received: by 10.28.179.9 with SMTP id c9mr3204571wmf.99.1516575480479; Sun, 21 Jan 2018 14:58:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Sun, 21 Jan 2018 14:57:20 -0800 (PST) In-Reply-To: <1516569725.42536.99.camel@freebsd.org> References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> From: Johannes Lundberg Date: Sun, 21 Jan 2018 22:57:20 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Ian Lepore Cc: Hans Petter Selasky , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 22:58:03 -0000 On Sun, Jan 21, 2018 at 9:22 PM, Ian Lepore wrote: > On Sun, 2018-01-21 at 22:07 +0100, Hans Petter Selasky wrote: > > On 01/21/18 21:45, Johannes Lundberg wrote: > > > > > > What does kern.eventtimer.periodic do? The sysctl description > > > wasn't > > > that elaborate... > > It turns off re-programming the timer every time there is a new > > callout > > with earlier completion time. > > > > --HPS > > Well, it does more than that. It makes the system run "the old way" > where there are periodic timer interrupts that happen whether they need > to or not (bad for power saving), and there's no way to schedule > anything to happen on intervals other than when the periodic ticks > occur (so if kern.hz = 1000 and you ask to sleep for a microsecond you > may actually sleep up to a millisecond). > > Thanks for the further explanation. I curious as to where the problem might be though.. It is the game's binary-only Linux executable (Unreal Engine 2.5), Linux SDL 1.2, or on the FreeBSD side? Haven't experienced anything similar with Quake3... Switching to periodic timer feels like overkill but it does the job as a work around. > -- Ian > From owner-freebsd-current@freebsd.org Mon Jan 22 08:23:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E5C1ED5AFA for ; Mon, 22 Jan 2018 08:23:22 +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 12E6A7137C; Mon, 22 Jan 2018 08:23:21 +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 D569F26012B; Mon, 22 Jan 2018 09:23:17 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg , Ian Lepore Cc: freebsd-current References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> From: Hans Petter Selasky Message-ID: Date: Mon, 22 Jan 2018 09:20:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 08:23:22 -0000 On 01/21/18 23:57, Johannes Lundberg wrote: > Thanks for the further explanation. > I curious as to where the problem might be though.. It is the game's > binary-only Linux executable (Unreal Engine 2.5), Linux SDL 1.2, or on the > FreeBSD side? Haven't experienced anything similar with Quake3... > Switching to periodic timer feels like overkill but it does the job as a > work around. You might get a clue if you ktrace the binary and look for timer or system calls which have a timeout. --HPS From owner-freebsd-current@freebsd.org Mon Jan 22 08:26:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7899BED5D42 for ; Mon, 22 Jan 2018 08:26:19 +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 40B4971565; Mon, 22 Jan 2018 08:26:19 +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 EB6E626012B; Mon, 22 Jan 2018 09:26:16 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg , Ian Lepore Cc: freebsd-current References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> From: Hans Petter Selasky Message-ID: <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> Date: Mon, 22 Jan 2018 09:23:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 08:26:19 -0000 On 01/21/18 23:57, Johannes Lundberg wrote: > Thanks for the further explanation. > I curious as to where the problem might be though.. It is the game's > binary-only Linux executable (Unreal Engine 2.5), Linux SDL 1.2, or on the > FreeBSD side? Haven't experienced anything similar with Quake3... > Switching to periodic timer feels like overkill but it does the job as a > work around. Hi, It might be simply this, that the wrong clock-type is used when setting up absolute timeouts. --HPS From owner-freebsd-current@freebsd.org Mon Jan 22 09:54:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4616EB6CAA for ; Mon, 22 Jan 2018 09:54:53 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 6479074BB1; Mon, 22 Jan 2018 09:54:53 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id 36so7922613wrh.1; Mon, 22 Jan 2018 01:54:53 -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=Y2uffdl1jWy6Zz/LOxumI+V7JKc+6qhZeZrfvPsCW2E=; b=DgOZzaxLrYl+xj1HKTytxsdXzPK5h3wcBrIHuZqkMakgprFaxGb+cDDu0lGmCYzkQl z7PEAFgLmlGZWSlmqLJtlkfDrrnBxewTqGGM/TaxsB62v5OAP9C+t3++93dnLu5JJTK7 dBCIKyC1HiKEfXOv3qVMncOrOd9ha8KNmNHyAZAqFvIVq2IWzCpMtXp/RyIGLTqk5RJ4 p8N7EQApd8AaBwpl606BnksLy9lWiVbM6nwx8hCfFJ+y+F7CAv27z4lIOhjnhP9oi//Y NvO4lzBys58YIgHrqzeT1Pv7ueNz5kH6Xt1BgS5ul8GTXNAAzKMcALhBkS0Hjwm148Cc vGPA== 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=Y2uffdl1jWy6Zz/LOxumI+V7JKc+6qhZeZrfvPsCW2E=; b=t1NMa5F0dIT+uv2W8TYPsAO11lTZ80TQGW/36aLB20BnkCPomn2AVdtMeIfEX1KLjr lKH1FkRbPyy1eY4vHpWV1HKDMbnGdsK8IEywM3GZa52dVPW1qNmNtFXHBGP5S0SKfoT+ a3M79v1wB5wUNm5G7LhGSvNoLh398Mwttw+orQYumVxk4eNe/ZJbrClfw0elQZ4e5VRw 5Ol7QTl2br5zp1mq7QJzjV2fcKBeOzxDCR0C/J2HRVLpc1iHM5h7iyuNV+tKSBRC2Jp4 KCamFNeUFzplPQTiPDFBs4ISHzO/bYh4e55Fa4ODqO/XjXbSmCIxJNofEPrFGRcHd2EE fBqg== X-Gm-Message-State: AKwxyte1os7nuk9oN9Mgutt+SGdmUyPwOf8HsgcXhCXv7iF97/KQn1ds EiIqC3l3jvBydTDDFgdMNv16Ya6fDxMXgjGg0Xc= X-Google-Smtp-Source: AH8x225L22D7OBFWvME7liAXyyxyr0oUVpeQIsa8S0SQ2NvAUY0Cfrn/H8P4iPaw2hW/zPvuMBR+UCze0n2He33Jlds= X-Received: by 10.223.135.18 with SMTP id a18mr3653652wra.122.1516614891388; Mon, 22 Jan 2018 01:54:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Mon, 22 Jan 2018 01:54:11 -0800 (PST) In-Reply-To: <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Johannes Lundberg Date: Mon, 22 Jan 2018 09:54:11 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Hans Petter Selasky Cc: Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 09:54:53 -0000 On Mon, Jan 22, 2018 at 8:23 AM, Hans Petter Selasky wrote: > On 01/21/18 23:57, Johannes Lundberg wrote: > >> Thanks for the further explanation. >> I curious as to where the problem might be though.. It is the game's >> binary-only Linux executable (Unreal Engine 2.5), Linux SDL 1.2, or on the >> FreeBSD side? Haven't experienced anything similar with Quake3... >> Switching to periodic timer feels like overkill but it does the job as a >> work around. >> > > Hi, > > It might be simply this, that the wrong clock-type is used when setting up > absolute timeouts. > Actually I think the same thing happens on the Macbook (with MacOS) which has a USB internal keyboard. The Mac binary is probably the same code base as the Linux one. Running Windows binary with wine does not experience this problem, unfortunately wine can only launch this game on MacOS, not FreeBSD. I assume USB can generate higher rate of interrupts than a PS/2 which this game (*nix version) was probably designed for initially. > > --HPS > From owner-freebsd-current@freebsd.org Mon Jan 22 17:06:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A002AECA886 for ; Mon, 22 Jan 2018 17:06:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1507284CCA for ; Mon, 22 Jan 2018 17:06:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id o89so11469323lfg.10 for ; Mon, 22 Jan 2018 09:06:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=iWWa23i/GOyQaY8bReUeT4UTezqFyo52fk+GS/AjXZ8=; b=gDhH0N3jxsAXpjEizx/ZcqxDL+exUk9iBKMIRx3gOtJ2bEXhGEp1/q3eglWcQC0TzU EwP17Q/v6QoGtYGnfF/nHOJiPk8RJt3g1b+XwI+cwihkhHk6H406/vRzqUsPjxKtNY+x Mh8VTg/hbEGCeDCHS2hHV3nZKW2QeE1+QsKqXQ3soNtf61lzlf/OTNGXnoWTBvCSzxNS RrP0lzufsRb1+AuN/6JYJNN1EAs32xdFxk8yYo+rkAyxLrXAvVKWpPfsdySoIhQVO/jw /MhNTlksVCWpxu02UDP0Eer1Us7W5bNOiwhmL/KJJpF9l3nraPimdjI01H/LGM2YI2eU eCeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mime-version:content-disposition:user-agent; bh=iWWa23i/GOyQaY8bReUeT4UTezqFyo52fk+GS/AjXZ8=; b=gOTmK80XJb69nzAMOUWGyztJ/gY/CLUsOzUiGxopIBGLey84KF/GSpwJsRLUwBTQMy TXO/0Hu6XpzqrA5Wg3MdxJemTQsH68BCeh0BGcLvHxCurWHBm2FV+o3M/l45usYSb/tK r4ZiukZcRM12czqec9PvHglieY08qir6ewtM+Re+6zY39dgxCbkYAZWrX7/N4vP2hJxM Gpuj6yMaio9A7gzy4E3HEnMXRU09oMWSEAMpx8dRl5Je/lHcgpza9+11FJGkZmdxumqv TuHeKUPDa7Do1yAI2F4WqVeTrEhHow7VY1QCihVJcsYK765m3iKPOVQtrNDct/nRLXkN rEtA== X-Gm-Message-State: AKwxyteJFYK7yMFr+kTSGyUEiuaqROAfj6p1CDO7s4ai11B17ULd3h9d GLpahGB7zJsuWnlz8N/Tbq0rxA== X-Google-Smtp-Source: AH8x227Kes5I/TKCbgyjBqd70V+EsdqgAgHOyk7GVSX0bC1W+GYpZMvwL/AwOb8Ypv1/75toVj9j5A== X-Received: by 10.25.83.4 with SMTP id h4mr3776906lfb.121.1516640767332; Mon, 22 Jan 2018 09:06:07 -0800 (PST) Received: from kloomba ([213.147.223.186]) by smtp.gmail.com with ESMTPSA id b84sm2797193ljf.87.2018.01.22.09.06.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jan 2018 09:06:06 -0800 (PST) Sender: Roman Bogorodskiy Date: Mon, 22 Jan 2018 21:06:00 +0400 From: Roman Bogorodskiy To: freebsd-current Subject: lldb 6.0.0 segfaults on opening a core file Message-ID: <20180122170558.GA74490@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 17:06:10 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Running on -CURRENT @ Jan 20 with llvm 6.0.0, I have the following issue op= ening a core file with lldb: $ lldb /usr/local/bin/python2.7 -c /tmp/python2.7_90218_0.core=20 (lldb) target create "/usr/local/bin/python2.7" --core "/tmp/python2.7_9021= 8_0.core" Assertion failed: (template_counter >=3D 0), function ConsumeTemplateArgs, = file /usr/src/contrib/llvm/tools/lldb/source/Plugins/Language/CPlusPlus/CPl= usPlusNameParser.cpp, line 245. This nothing happens for a couple of minutes and then it dumps core. Interestingly though, it can open its own core: %> lldb /usr/bin/lldb -c /tmp/lldb_1129_0.core=20 (lldb) target create "/usr/bin/lldb" --core "/tmp/lldb_1129_0.core" Core file '/tmp/lldb_1129_0.core' (x86_64) was loaded. = = =20 (lldb) bt = = =20 * thread #1, name =3D 'lldb', stop reason =3D signal SIGABRT = = =20 * frame #0: 0x0000000803e642ea libc.so.7`__sys_thr_kill at thr_kill.S:3 = = =20 frame #1: 0x0000000803e642b4 libc.so.7`__raise(s=3D6) at raise.c:54 = = =20 frame #2: 0x0000000803e64229 libc.so.7`abort at abort.c:67 = = =20 frame #3: 0x0000000803ee38f1 libc.so.7`__assert(func=3D, f= ile=3D, line=3D, failedexpr=3D) at a= ssert.c:53 =20 frame #4: 0x00000000017fa8e5 lldb`::ConsumeTemplateArgs() at CPlusPlusN= ameParser.cpp:245 = =20 frame #5: 0x00000000017f9f12 lldb`::ParseFullNameImpl() at CPlusPlusNam= eParser.cpp:551 = =20 frame #6: 0x00000000017f97d9 lldb`::ParseFunctionImpl() at CPlusPlusNam= eParser.cpp:114 = =20 frame #7: 0x00000000017f96f5 lldb`::ParseAsFunctionDefinition() at CPlu= sPlusNameParser.cpp:45 = =20 frame #8: 0x00000000017ec364 lldb`::Parse() at CPlusPlusLanguage.cpp:20= 2 = =20 frame #9: 0x00000000017ec3e7 lldb`lldb_private::CPlusPlusLanguage::Meth= odName::GetBasename(void) at CPlusPlusLanguage.cpp:218 = =20 frame #10: 0x00000000016ffcba lldb`::InitNameIndexes() at Symtab.cpp:29= 4 = =20 frame #11: 0x00000000017008b1 lldb`::PreloadSymbols() at Symtab.cpp:407= = =20 frame #12: 0x00000000018dce19 lldb`::PreloadSymbols() at Module.cpp:141= 6 = =20 frame #13: 0x00000000016b1e14 lldb`::GetSharedModule() at Target.cpp:20= 28 = =20 frame #14: 0x00000000019c14ed lldb`::LoadModuleAtAddress() at DynamicLo= ader.cpp:171 = =20 frame #15: 0x000000000199fd35 lldb`::LoadAllCurrentModules() at Dynamic= LoaderPOSIXDYLD.cpp:537 = =20 frame #16: 0x000000000199d9aa lldb`::DidAttach() at DynamicLoaderPOSIXD= YLD.cpp:171 = =20 frame #17: 0x0000000001698231 lldb`::LoadCore() at Process.cpp:2853 = = =20 frame #18: 0x000000000184b85d lldb`::DoExecute() at CommandObjectTarget= =2Ecpp:371 = =20 frame #19: 0x000000000181811f lldb`::Execute() at CommandObject.cpp:991= = =20 frame #20: 0x00000000018268f8 lldb`::HandleCommand() at CommandInterpre= ter.cpp:1683 = =20 frame #21: 0x0000000001829e2a lldb`::IOHandlerInputComplete() at Comman= dInterpreter.cpp:2771 = =20 frame #22: 0x00000000018e25ff lldb`::Run() at IOHandler.cpp:573 = = =20 frame #23: 0x000000000190ab5f lldb`::ExecuteIOHandlers() at Debugger.cp= p:961 = =20 frame #24: 0x000000000182a9a3 lldb`::RunCommandInterpreter() at Command= Interpreter.cpp:2971 = =20 frame #25: 0x000000000192ce29 lldb`::RunCommandInterpreter() at SBDebug= ger.cpp:905 = =20 frame #26: 0x0000000001677263 lldb`::MainLoop() at Driver.cpp:1105 = = =20 frame #27: 0x00000000016779bc lldb`main at Driver.cpp:1253 = = =20 frame #28: 0x0000000001674095 lldb`_start(ap=3D, cleanup= =3D) at crt1.c:74 = =20 (lldb) fr s 4 = = =20 frame #4: 0x00000000017fa8e5 lldb`::ConsumeTemplateArgs() at CPlusPlusNameP= arser.cpp:245 = =20 242 } = = =20 243 } = = =20 244 = = =20 -> 245 assert(template_counter >=3D 0); = = =20 246 if (template_counter > 0) { = = =20 247 return false; = = =20 248 } = = =20 (lldb) expr template_counter = = =20 error: use of undeclared identifier 'template_counter' <-- is that because = of some optimizations? (lldb) Is that a known problem? Or maybe something wrong with my system? I don't use lldb very often, but I don't remember it crashing like that. Roman Bogorodskiy --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaZhn2AAoJEMltX/4IwiJq5mEIAMBBJhQDdrxAQNPOiZ8hrPGc cTEl5NsfSi+ZOMih0Zbf8zGwX+oQNE5YAHQ9yzaIMIGenzBZnxO7KNg2cOq67hKd 5VLOCVeAzfQBsF6ARiWwDJH1MENzKLvKGxNDkzFztQEXo63JAKr8KdvEyONMfh6G iXWdpeOJzrVCrBzuZ5VzQckWRIaNi8hlUK1PrrczY9ULGOyAZv4OJSXtcOj86xjw qNHX5qqPbQVLD7mMMCMPYJe7MSh2epNBtT9+wVLRScDig3zjhLqP2L+KuKChNMS/ +HEWeHve9dehd+9Bnqg73ry2tGOIJ7uT7ZBu/DN9Yj+M22/Kzv5HfnFeEx/Y7ME= =Z3+U -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-current@freebsd.org Mon Jan 22 21:50:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F8C9ED7705 for ; Mon, 22 Jan 2018 21:50:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A7A68709CB for ; Mon, 22 Jan 2018 21:50:03 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.15.2/8.15.2/ALCHEMY.FRANKEN.DE) with ESMTPS id w0MLns2Z030968 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Jan 2018 22:49:54 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.15.2/8.15.2/Submit) id w0MLnrE1030967; Mon, 22 Jan 2018 22:49:53 +0100 (CET) (envelope-from marius) Date: Mon, 22 Jan 2018 22:49:53 +0100 From: Marius Strobl To: KIRIYAMA Kazuhiko Cc: freebsd-current@freebsd.org Subject: Re: SG116j install crashed Message-ID: <20180122214953.GA7649@alchemy.franken.de> References: <201801180635.w0I6Zfdb083944@kx.openedu.org> <201801201125.w0KBP8Hl039214@kx.openedu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201801201125.w0KBP8Hl039214@kx.openedu.org> User-Agent: Mutt/1.9.2 (2017-12-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (alchemy.franken.de [0.0.0.0]); Mon, 22 Jan 2018 22:49:54 +0100 (CET) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 21:50:04 -0000 On Sat, Jan 20, 2018 at 08:25:08PM +0900, KIRIYAMA Kazuhiko wrote: > At Thu, 18 Jan 2018 15:35:41 +0900, > my wrote: > > > > Hi, all > > > > I've bought Biccamera's original bland note PC (SG116j) > > impulsively because of cheapness($1780). I've installed > > 12.0-CURRENT(r327788) right away. Booted smoothly but set > > loader conf "unset hint.uart.1.at" and configure disk with > > > > mmcsd0 58 GB GPT > > mmcsd0p1 200MB efi > > mmcsd0p2 54 GB freebsd-ufs / > > mmcsd0p3 4.2 GB freebsd-swap none > > > > But in "Tetching distribution files" of base.txz, crashed > > with: > > > > sdhci_acpi0-slot0: Controller timeout > > sdhci_acpi0-slot0: ============== REGISTER DUMP ============== > > sdhci_acpi0-slot0: Sys addr: 0x02158000 | Version: 0x00001002 > > sdhci_acpi0-slot0: Blk size: 0x00000200 | Blk cnt: 0x000000f8 > > sdhci_acpi0-slot0: Argument: 0x017f57e8 | Trn mode: 0x00000027 > > sdhci_acpi0-slot0: Present: 0x1fff0106 | Host ctl: 0x00001025 > > sdhci_acpi0-slot0: Power: 0x0000000b | Blk gap: 0x00000080 > > sdhci_acpi0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 > > sdhci_acpi0-slot0: Timeout: 0x00000007 | Int stat: 0x00000001 > > sdhci_acpi0-slot0: Int enab: 0x05ff0033 | Sig enab: 0x05ff003a > > sdhci_acpi0-slot0: AC12 err: 0x80000000 | Host ctl2:0x0000008b > > sdhci_acpi0-slot0: Caps: 0x446cc8b2 | Caps2: 0x00000807 > > sdhci_acpi0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 > > sdhci_acpi0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 > > sdhci_acpi0-slot0: =========================================== > > mmcsd0: Error indicated: 1 Timeout > > : > > (snip) > > : > > Stopped at kdb_enter+0x3b: movq $0,kdb_why > > db> > > > > Detail log has put in [1]. BTW I used [2] so all stuffs are > > within it and it should not be fetched to internet. > > > > Is there any idea to go forth? > > > > Best regards. > > > > [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install.jpeg > > [2] FreeBSD-12.0-CURRENT-amd64-20180110-r327788-memstick.img > > I've got r328126 memstic and install with it, then all went > to perfect! Thanx for FreeBSD-CURRENT team! FYI, I believe that you had hit the bug fixed in r327924; sorry about that. Marius From owner-freebsd-current@freebsd.org Tue Jan 23 01:49:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F23BEC0559 for ; Tue, 23 Jan 2018 01:49:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 0FF2879F8C; Tue, 23 Jan 2018 01:49:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id 16so10747303wry.12; Mon, 22 Jan 2018 17:49:01 -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=fevZup30op1VofeVQFWF/M4R1YZdbh1oCXThcvM8bxs=; b=fvNYGqJvotkz9wQe/dfGQ8akg6FJU+Z3VcDeqYgvHn87+tGB1bGZO8tXD0c3/QWRNi Vx+Qu4M/eFg5yYf5ouHT1cjWcVZT+7Jkdl1TlqO6pyRSXHWVzKMMHTJ3MBqt4VL7vp4g D6XjDY03V0ncO6UiiljJsbJuQMHkcTgfaLeAH44ke/Bwin41PcXs3zq7SMjO3iCrdM/F z4aNQcXEBe0uVcaaiJweSioO2L0OlYH5UPW8gdMy7UUrx1WrB87Za/hMCw5Yk820/f+G OF768kVc99+sE3L21HzAmUAy5UL9L+P5u+3UXNqVw3iAfqM8h7qlXc5OjgcsibwFQBw0 txGQ== 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=fevZup30op1VofeVQFWF/M4R1YZdbh1oCXThcvM8bxs=; b=kFw3504RV+cDFeg8rf/aGDm8+BnHn6ykEuSYGJSChVh6WopdEfqZFY86cFBX7c7vdX azUWpl7XCJFP2HFHDH80m+VyZ6gvpGeLM+ZCZWMYJdcap2o421a9Vu3ZarshVleUZPmZ TtQ3Wk3c/X0B6qlduQZlI+HeA1f9yXPw1Oui7awIwubsexP3KvgMd3txTXBoVwki1fZn t2G8sxHyRM9FeQ4Yeio4LQDmNkypVuN9QJeQhxBHg7ExjiF+s/orIDhs4MYEYvThJcVn qGwxmgFXyP5S/bFeE8YEF1kRCH1sgd4jwgI/ccxe9mxmGJp2iqTRL6chfswPw+sDqet9 wOoA== X-Gm-Message-State: AKwxytfmrFtSD/anfY2JVbclHvJy1GwofODFqHqpbo1Ftga0SOUmxWgn NMADJQKFm9euWiuKFbmCPo/wsWoaEKOHHNW0avU= X-Google-Smtp-Source: AH8x227r9xLDF6VxbBwj55z6mMw1yz1zTMFHUR7bTlqVGaTl3iEYKPF2DFe1rdQuK3Jq9vN7VZRHrKUEq5/8QO/2tEo= X-Received: by 10.223.198.198 with SMTP id c6mr582485wrh.159.1516672139942; Mon, 22 Jan 2018 17:48:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.181.3 with HTTP; Mon, 22 Jan 2018 17:48:58 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Adrian Chadd Date: Mon, 22 Jan 2018 17:48:58 -0800 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg Cc: Hans Petter Selasky , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 01:49:02 -0000 Hi Yeah the timers eventually get coalesced unless someone's asking for a ridciulously accurate timer value. So is some driver asking for hyper-accurate callout timer that isn't being coalesced? hps, is there any useful debugging to try and find callouts that are requesting stupidly accurate timers? Maybe a dtrace probe on the callout schedule entry point? -adrian From owner-freebsd-current@freebsd.org Tue Jan 23 02:33:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58869EC532A for ; Tue, 23 Jan 2018 02:33:59 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 18F947CC96; Tue, 23 Jan 2018 02:33:59 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id e1so12079550ita.0; Mon, 22 Jan 2018 18:33:59 -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=LOJfhOKCcbI0XkewET91qJ0KUyPkjxAJyZ7dQKXrt9E=; b=IR30767IcCvL5AEpChBtsyFU1jP426kP52l5/xr4ON1RuRBQ8ojp5AfbCt1VNXpo7K 0NIW1QnVaEOafnMHBA4tQvnOgU4W+cdItvcrqPeic/4WUXJm9OR2psWS1wxZhMrsRWXH Gtnr5UHXV/y6UkgvPE6MyO8i97YBcxmCb5QTaCrdy4UrsUJXvliivQVYXhkNqyWhZoEC Afkye04IQxm01CwDq4nR2V+c8o4x3juEpTopdgDKMJEQXyGWdIKY3tMUKmUlAI0wEIZ8 Mt8rgise84t3bOgT0kp5aVP+LbrXk5biGTCpbv5ZbbrS6/EM/IEvg4/6rkHkJv4Jok/9 AYEA== 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=LOJfhOKCcbI0XkewET91qJ0KUyPkjxAJyZ7dQKXrt9E=; b=X1tjPSr7uqgznpuQZLCk0/vgqqvmELi+3dM7m3hAonX77fEniptl08IPWuhP/hCfgr 8AoYu0YlA/kVDxBDI3giOvVnUOesFr7eeyS4BAAhVGo6SON4Q3pCTpO46pqfG8C3zrJq ue8pufnUHhTfeKI+XwYJ/T7cBueNd4BNOi85LtcemRPDsTJgkCdCYEfhsoigsIgXYZy4 rwLqO60NYBPST0x4QvwDHfW84FuiZK/hret+MppZju5OXhj352tg7uyqXyGLDruuuVPU kZ/lCjUoUi8k0GgEJTI7hy13PKDSpDITGWmVw8BviH/sPbpgcxcBqrJdd65mJbI2CH/d q/OA== X-Gm-Message-State: AKwxyteR0vYWU51bvFNEhqKsDtxKDEykQlS2toIeAnJj4AQQzaS9oI6/ e7J90PERNSrdjdk6lNwtQl2nPPnobmr//tR0vJ0= X-Google-Smtp-Source: AH8x227sY/tM8tyUXpKIyrcqFKOjykDrf+jC4x8sY0PoFXOuPZec0H8KsY/L+JDwcFsDluq8Nld2ZtzcPtMXOOy0ZWc= X-Received: by 10.36.50.73 with SMTP id j70mr1548259ita.149.1516674838423; Mon, 22 Jan 2018 18:33:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.10.97 with HTTP; Mon, 22 Jan 2018 18:33:57 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: blubee blubeeme Date: Tue, 23 Jan 2018 10:33:57 +0800 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Adrian Chadd Cc: Johannes Lundberg , Hans Petter Selasky , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 02:33:59 -0000 On Tue, Jan 23, 2018 at 9:48 AM, Adrian Chadd wrote: > Hi > > Yeah the timers eventually get coalesced unless someone's asking for a > ridciulously accurate timer value. > > So is some driver asking for hyper-accurate callout timer that isn't > being coalesced? hps, is there any useful debugging to try and find > callouts that are requesting stupidly accurate timers? Maybe a dtrace > probe on the callout schedule entry point? > > > > -adrian > _______________________________________________ > 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" > I'd say dtrace might be able to get you in the right direction very quickly. I used SDL in the past for android apps and the code is very Linux specific. I am sure there's some Linux related timers in there somewhere that FreeBSD is returning nothing from and that's what's killing the performance. I can almost guarantee that none of the SDL designers and or programmers use any *BSD systems. The easiest solution would be to go look at the timer code and implement something that FreeBSD can work with and try to get that upstream. These are just a few of the issues that will crop up when devs try to just use shims to hook into the Linux kernel. Do the design work up front and implement things in a native way or enjoy the jank. DTrace should be able to point you in the right direction relatively quickly. The DTraceBook: https://www.amazon.com/DTrace-Dynamic-Tracing-Solaris-FreeBSD/dp/0132091518 Best From owner-freebsd-current@freebsd.org Tue Jan 23 06:56:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2B4EEB523D for ; Tue, 23 Jan 2018 06:56:07 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51E6D1CFE for ; Tue, 23 Jan 2018 06:56:06 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MAgzj-1eX0yq1fZL-00Bsjt for ; Tue, 23 Jan 2018 06:46:39 +0100 Date: Tue, 23 Jan 2018 06:46:33 +0100 From: "O. Hartmann" To: freebsd-current Subject: PkgBase: Can not upgrade base system Message-ID: <20180123064633.45e2710b@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:lmWMX2ouMtVj9mYbbR9KsJr+YscNLkIcS2coRAe2ZxFDvIuDudo ndgdppsES22rjALs9CnNYzPEqTyAeBz/okU8ykHj2FdpLi+w/+QCWp4/eZnJOEYOddmBqpa xzfowBmw7fCjYRliPAOWWHSxuHvDBoBtyq/++QxHxLQkMgIUcDO6633lsEVngjfQR+j0HAe xOyGT2M2WROT2WMXNAivA== X-UI-Out-Filterresults: notjunk:1;V01:K0:Vn6EPTBgOPg=:V84wg5jwtqEqtpc6WFdNaQ zO8/Ae4wwxW9vyEOk9iOtqfwbtk6BcGXRFckmYUIIHYfN4hTdRyvakV8R8bu82zlLVEdECerx 0FFt4dd7EjuEifup6B07q3MrNqJUuOp62SgZWyULZAd2YJ36mzrZ+RJU44EUghYrwU6X8dxod yUVKGLJYqKELF1ggVi4kLb4A2gNoRUij9lC45L3uwfQosMCKWvUMLG/ubX68oN4qrC1O+mzKH bfxxjSSo2fx0nnUB+0xsg2XDLIexPAxvNawkurMtX0XkVJfTp8zUrAHaP8uJTsRb41Cu4rydP DDyMs81oBzaJ5jFqLl3i0T+JaWiL64iB2Tfico3/QSB4+wcFnp+IIM7wYTWn+bX1OzDxsCnaa ZcTmT0KyA939UipRr6SfE1q/Ko+tdXslKU2ii62HudgNbzVWYd5AgI/oiBGwjINrFPdyzphoB J0UWPAKQFgc809pJDe/IyS+uQO7C40Xj4Y584AwB8IE8owTXhcRwU2EcjxUiqfJkBqNOGc3J2 V+g5Wkfl59n46fz3GRypqAl7d5ujgmyBPSvWkv8lLDanivGgqtJn/bNykINM28i7GfUt+ORys GBrZZRYUMZmqiZFEPdN0PWIUhv8yzx47RtcS+lAOt0yNm/BwiGWWmQESHcI1UXJDZRCITbk8D FPKT36ul5oXHCLVgdGu9Ivheww+6+mT2G4JuVw9E+wFWLg1AP5I6c9ECFYPd+kYmNGYhehZSa PoPdwCFqoWCpduvJSBdlmRgBWfLyFEliYM2J5BSwdnvZAco3+Ze+h/zSepJzOhf0eCyg3+vN9 Kvw9Xn/9HV54uzhiHV38bLyZd4rNmxaCS6WTtsZmnPQtr7wpFs= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 06:56:08 -0000 For a client I tried PkgBase and followed the procedures recommended (first build the OS from /usr/src/, installworld/kernel, then proceed with pkg update -r FreeBSD-base and pkg install -g 'FreeBSD-*'. This doesn't work for any update I try to apply. Since the target host is a two years old Intel NUC based on some Broadwell snail CPU, building world and kernel is performed on another, much more potent host. In the first place, when performing a "pkg upgrade", the system complains about mismatching OSVERSION, 1200055 forthe running system, and 1200056 for the packages to be updated. When setting env OSVERSION=1200056, pkg (not pkg-static!) complains about revision numbers (the long date trailing the package's name), for instance the newest one is FreeBSD-hast-12.0.s20180123050738.txz contained within the repository to be used for the update, but installed is something older, like FreeBSD-hast-12.0.s20171103114456.txz. When trying pkg-static, I get a crash of pkg-static, segmentation fault is its death-cause. How am I supposed to update a base system via PkgBase? Kind regards, oh p.s. sorry for the lack of data, the box in question is on a remote site without net. From owner-freebsd-current@freebsd.org Tue Jan 23 11:28:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88F11ECC8AB for ; Tue, 23 Jan 2018 11:28:10 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 0BBC47609A; Tue, 23 Jan 2018 11:28:10 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id i186so1122674wmi.4; Tue, 23 Jan 2018 03:28:09 -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=OoMpC7FYu9gf8eYInDUSRwJOydnf1kvBJz/+ZGPx3M0=; b=r639+ksMUUg6HlqgJCo/Uy65ZBq0m/MUHzazisVTyyTHyotF9FNi88GbnPhvigCq6L I1XpGu+ez76RhyeWPU7k1xd0EubMdT7Teq5VcPGe9whOyX6RpwABSPWaRYtqlcaahZNF GU3rpCa28AULzCELlBmWPPj+sYFJXTT1+5MmjXVYYf4tcvbKE90ZAlU/sOhJJ6q5O4xa hhFuBsvpXFoV3yEABza5T8cKNIDtxd/KgdXBrTbUTJrSqW45s+1h2WrARRAlgQfYZ77v ainOI/c1KfHULjmwKG0I/bhObD3sN9mdyEiRRx4GyYTuus/LyoV5BUqXDgepsujIg5Ep MTNg== 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=OoMpC7FYu9gf8eYInDUSRwJOydnf1kvBJz/+ZGPx3M0=; b=elJ03sbI0EnZyVs1YiSTIY0FHJzYPdo5NOez9Ije8Hh/J/51lKtgk7/rHRAE4P8Qx+ aFI9I3/EmVgOeER5Ph8E4RVUgvaMbjtBIHMEEuFwmUXHxNnFzfcMHTqr7J+9QORsJ1lo IqOWhEkfYs5PTxG6159vAq/2cdZ6ulrzjeRfmRsZ5j8Gkil2USNCrL+kGIpysViu1ZBo sq0INOzoQ75KYvromjqRBc4zyjpJg2M1bzKYPJBS3LM7N2eqzCR7c/GYUJr0vZI/vOM1 r2XmTK1lgJwIjX+BVXiTTYKaouthAinDaBl5NXWw8GF89o5Jfzhqui9wvadNM+evDyxw zAuw== X-Gm-Message-State: AKwxytd+jHzq6vArF8X8F3QxnkWUtFWZ4bdDVN8/WIW18wl0HGAh5FBG jOs8z38Mti60tFpTWFpQEpzDL7QsFg6yfLgybdI= X-Google-Smtp-Source: AH8x2277T433k/0WKV7E6x8m8dU/5UNuDtfYRhHrE6Lj0xTCEVxBGw5NG2gcBaLhhehgP57e8QSHr4pB/knaGhC1BBI= X-Received: by 10.28.111.219 with SMTP id c88mr1760233wmi.41.1516706888408; Tue, 23 Jan 2018 03:28:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Tue, 23 Jan 2018 03:27:28 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Johannes Lundberg Date: Tue, 23 Jan 2018 11:27:28 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: blubee blubeeme Cc: Adrian Chadd , Hans Petter Selasky , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 11:28:10 -0000 Hi all Some quick dtracing with play causing lag, vs play not causing lag (that is not hold down any key on a usb keyboard for too long). # dtrace -n 'profile-997hz /arg0/ { @[func(arg0)]=count(); }' Lag version -- snip -- linuxkpi.ko`idr_find 7 kernel`nanotime 8 kernel`__cap_rights_init 8 kernel`amd64_syscall 8 i915kms.ko`i915_gem_obj_lookup_or_create_vma 8 kernel`selfdfree 9 kernel`feed_matrix_S16LE 11 kernel`callout_lock 11 kernel`uma_zalloc_arg 11 kernel`z_feed_linear_S16LE 12 kernel`0xffffffff80f6877e 12 kernel`copyin 12 kernel`tsc_get_timecount_low_lfence 12 kernel`bzero 13 kernel`fget_unlocked 14 i915kms.ko`gen8_ppgtt_insert_pte_entries 14 kernel`callout_when 16 kernel`0xffffffff80f68fbc 26 kernel`kern_select 32 kernel`lock_mtx 50 kernel`spinlock_enter 53 kernel`bcopy 57 kernel`unlock_mtx 104 i915kms.ko`fw_domains_get 113 * kernel`ukbd_timeout 126 kernel`callout_reset_sbt_on 128 kernel`ukbd_interrupt 136* * kernel`softclock_call_cc 192* kernel`memcpy 284 kernel`cpu_idle 4257 * kernel`spinlock_exit 4312 kernel`lock_delay 11921* kernel`acpi_cpu_idle 15265 No lag version -- snip -- kernel`free 19 kernel`copyout 20 kernel`copyin 20 linuxkpi.ko`idr_find 21 kernel`selfdfree 24 kernel`tsc_get_timecount_low_lfence 25 kernel`__mtx_lock_flags 28 kernel`uma_zalloc_arg 30 kernel`bzero 31 i915kms.ko`gen8_ppgtt_insert_entries 31 drm.ko`drm_ioctl 32 kernel`fget_unlocked 36 kernel`amd64_syscall 37 kernel`kern_select 49 i915kms.ko`gen8_ppgtt_insert_pte_entries 61 kernel`0xffffffff80f68fbc 78 kernel`bcopy 90 i915kms.ko`fw_domains_get 228 kernel`spinlock_exit 284 kernel`cpu_idle 4698 kernel`acpi_cpu_idle 36288 I also tried rebuilding linux-c6_sdl-1.2 using get time functions in librt vs libc but no difference. Will dig deeper next time I have free time to spare. On Tue, Jan 23, 2018 at 2:33 AM, blubee blubeeme wrote: > > > On Tue, Jan 23, 2018 at 9:48 AM, Adrian Chadd > wrote: > >> Hi >> >> Yeah the timers eventually get coalesced unless someone's asking for a >> ridciulously accurate timer value. >> >> So is some driver asking for hyper-accurate callout timer that isn't >> being coalesced? hps, is there any useful debugging to try and find >> callouts that are requesting stupidly accurate timers? Maybe a dtrace >> probe on the callout schedule entry point? >> >> >> >> -adrian >> _______________________________________________ >> 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 >> " >> > I'd say dtrace might be able to get you in the right direction very > quickly. > > I used SDL in the past for android apps and the code is very Linux > specific. I am sure there's some Linux related timers in there somewhere > that FreeBSD is returning nothing from and that's what's killing the > performance. > > I can almost guarantee that none of the SDL designers and or programmers > use any *BSD systems. > > The easiest solution would be to go look at the timer code and implement > something that FreeBSD can work with and try to get that upstream. > > These are just a few of the issues that will crop up when devs try to just > use shims to hook into the Linux kernel. Do the design work up front and > implement things in a native way or enjoy the jank. > > DTrace should be able to point you in the right direction relatively > quickly. > The DTraceBook: https://www.amazon.com/DTrace-Dynamic- > Tracing-Solaris-FreeBSD/dp/0132091518 > > Best > From owner-freebsd-current@freebsd.org Tue Jan 23 12:06:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4A33ECF552 for ; Tue, 23 Jan 2018 12:06:25 +0000 (UTC) (envelope-from gurenchan@gmail.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 7706B77E4A; Tue, 23 Jan 2018 12:06:25 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x236.google.com with SMTP id t22so675232ioa.7; Tue, 23 Jan 2018 04:06:25 -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=HGM88yBs0KT2Ym+tj/xVpuZic82Yw4X+FSvcbTCyTWY=; b=sn5bimvu1o5N+wUEeNsnd9Xh+gluHCKdlc7vgKwgNx8roDorAMsGzQ5FQLZasd5N9l fchy5cAgGzD9LsuWOL3IrHfkJ+jTtQnHrQq6hAJ8OhOanEc4RpUcbvz72fO6TLg7pek+ cATMcb2cM6EVa7KEZ086stKIGW7RsPLFCS44/ieFBtG1eKVb5/a4FhGJ8Hw5/AOhf6Mi uTeZo308v4/qRFvxpnrQ8lvdRXLJsp0BQU3DBJGOv2hYHhmcjace1unEZY7mSu4JJPt4 Uh5/XAmIXbmt4ZFm9RCHDQYLE7696vtmHDmdonCIjVBNlC+INIxuwrQC8jrxAO5uJVm4 6Kqg== 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=HGM88yBs0KT2Ym+tj/xVpuZic82Yw4X+FSvcbTCyTWY=; b=H1CLqQsiQ4DcUOtS8//s+7QICAFEVSrwxKpXKmhxh0X9YAJzBmdQsasklBZV2uv0P8 oqGtSd1V74oeKaNu8ZXv5O4vm3yPzJcVHfVq5z7stb2ZjHitOYAbj7uOk8Z/t6d1uTtS DQ+IIMv7iro7V4fhwItAYcGtfobyjbtTAqgABlflJ+9GO3qxxiCporaYMLuzF6r0/NO1 5MkVeOOrnAgPrzbvNXWsfdUScPxgL9I4hmYcmekKg9f+sNzOrAeOzgg839SwwLhlrq5f r/lw5ooAaTXDhj980SqrlUXrjYSwNNgQ0Wb8Hkm07tZPIKBLl6snmfpt+ji4tGeW86ZR Zdgw== X-Gm-Message-State: AKwxyteOGbjx23OGiYYmAm8PAvdWhoqi3L44N/mDOP8ct6Uky/T13usG qOmLsb6R7d1feLeh01Xo2LMKUmoUJj9Rx/UqKY7mYA== X-Google-Smtp-Source: AH8x227MBAtjhkbUmyH71qxowxyG5kZeyVwEjfHd6dN0mBJhDSNd4waH59SCg5YUhIxxXzHx/MEDHyZ8Ja7koQ07MvE= X-Received: by 10.107.97.24 with SMTP id v24mr3289532iob.296.1516709184633; Tue, 23 Jan 2018 04:06:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.10.97 with HTTP; Tue, 23 Jan 2018 04:06:24 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: blubee blubeeme Date: Tue, 23 Jan 2018 20:06:24 +0800 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg Cc: Adrian Chadd , Hans Petter Selasky , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 12:06:25 -0000 On Tue, Jan 23, 2018 at 7:27 PM, Johannes Lundberg wrote: > Hi all > > Some quick dtracing with play causing lag, vs play not causing lag (that > is not hold down any key on a usb keyboard for too long). > > > # dtrace -n 'profile-997hz /arg0/ { @[func(arg0)]=count(); }' > > Lag version > -- snip -- > linuxkpi.ko`idr_find 7 > kernel`nanotime 8 > kernel`__cap_rights_init 8 > kernel`amd64_syscall 8 > i915kms.ko`i915_gem_obj_lookup_or_create_vma 8 > kernel`selfdfree 9 > kernel`feed_matrix_S16LE 11 > kernel`callout_lock 11 > kernel`uma_zalloc_arg 11 > kernel`z_feed_linear_S16LE 12 > kernel`0xffffffff80f6877e 12 > kernel`copyin 12 > kernel`tsc_get_timecount_low_lfence 12 > kernel`bzero 13 > kernel`fget_unlocked 14 > i915kms.ko`gen8_ppgtt_insert_pte_entries 14 > kernel`callout_when 16 > kernel`0xffffffff80f68fbc 26 > kernel`kern_select 32 > kernel`lock_mtx 50 > kernel`spinlock_enter 53 > kernel`bcopy 57 > kernel`unlock_mtx 104 > i915kms.ko`fw_domains_get 113 > > > * kernel`ukbd_timeout 126 > kernel`callout_reset_sbt_on 128 > kernel`ukbd_interrupt 136* > * kernel`softclock_call_cc 192* > kernel`memcpy 284 > kernel`cpu_idle 4257 > > * kernel`spinlock_exit 4312 > kernel`lock_delay 11921* > kernel`acpi_cpu_idle 15265 > A question on the mailing list about spinlocks and high cpu time: https://lists.freebsd.org/pipermail/freebsd-questions/2008-October/183943.html Although I think that for USB you can most likely fully replace the spinlock with a lock free queue, stack allocator and a ring buffer. Tony Van Eerd has been doing some very interesting work on lock free queue and refined his implementation, his talk from this year's cpp con looks very promising. You can check it out here: https://www.youtube.com/watch?v=HP2InVqgBFM Locks just have overhead that can't be avoided, with something like USB you can use a heap allocator, a ring buffer and a lock free queue and that should be able to get rid of the lock. I remember looking at the USB stack a while ago, there's one global lock or something like that and looking at the DTrace logs it's definitely that causing issues somehwere. It'll need testing though. > > > No lag version > -- snip -- > kernel`free 19 > kernel`copyout 20 > kernel`copyin 20 > linuxkpi.ko`idr_find 21 > kernel`selfdfree 24 > kernel`tsc_get_timecount_low_lfence 25 > kernel`__mtx_lock_flags 28 > kernel`uma_zalloc_arg 30 > kernel`bzero 31 > i915kms.ko`gen8_ppgtt_insert_entries 31 > drm.ko`drm_ioctl 32 > kernel`fget_unlocked 36 > kernel`amd64_syscall 37 > kernel`kern_select 49 > i915kms.ko`gen8_ppgtt_insert_pte_entries 61 > kernel`0xffffffff80f68fbc 78 > kernel`bcopy 90 > i915kms.ko`fw_domains_get 228 > kernel`spinlock_exit 284 > kernel`cpu_idle 4698 > kernel`acpi_cpu_idle 36288 > > > I also tried rebuilding linux-c6_sdl-1.2 using get time functions in librt > vs libc but no difference. > Will dig deeper next time I have free time to spare. > > > > On Tue, Jan 23, 2018 at 2:33 AM, blubee blubeeme > wrote: > >> >> >> On Tue, Jan 23, 2018 at 9:48 AM, Adrian Chadd >> wrote: >> >>> Hi >>> >>> Yeah the timers eventually get coalesced unless someone's asking for a >>> ridciulously accurate timer value. >>> >>> So is some driver asking for hyper-accurate callout timer that isn't >>> being coalesced? hps, is there any useful debugging to try and find >>> callouts that are requesting stupidly accurate timers? Maybe a dtrace >>> probe on the callout schedule entry point? >>> >>> >>> >>> -adrian >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >> I'd say dtrace might be able to get you in the right direction very >> quickly. >> >> I used SDL in the past for android apps and the code is very Linux >> specific. I am sure there's some Linux related timers in there somewhere >> that FreeBSD is returning nothing from and that's what's killing the >> performance. >> >> I can almost guarantee that none of the SDL designers and or programmers >> use any *BSD systems. >> >> The easiest solution would be to go look at the timer code and implement >> something that FreeBSD can work with and try to get that upstream. >> >> These are just a few of the issues that will crop up when devs try to >> just use shims to hook into the Linux kernel. Do the design work up front >> and implement things in a native way or enjoy the jank. >> >> DTrace should be able to point you in the right direction relatively >> quickly. >> The DTraceBook: https://www.amazon.com/DTrace-Dynamic-Tracing- >> Solaris-FreeBSD/dp/0132091518 >> >> Best >> > > From owner-freebsd-current@freebsd.org Tue Jan 23 12:39:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBECEED184E for ; Tue, 23 Jan 2018 12:39:51 +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 A05BD7976E; Tue, 23 Jan 2018 12:39:51 +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 42D5626009E; Tue, 23 Jan 2018 13:39:48 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg , blubee blubeeme Cc: Adrian Chadd , Ian Lepore , freebsd-current References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Hans Petter Selasky Message-ID: Date: Tue, 23 Jan 2018 13:36:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 12:39:52 -0000 On 01/23/18 12:27, Johannes Lundberg wrote: > Hi all > > Some quick dtracing with play causing lag, vs play not causing lag (that is > not hold down any key on a usb keyboard for too long). > > Hi, The only thing I can think about is that one or more of kb_delay1 or kb_delay2 are zero: sys/dev/usb/input/ukbd.c > case KDSETREPEAT: /* set keyboard repeat rate (new > * interface) */ > if (!KBD_HAS_DEVICE(kbd)) { > return (0); > } > /* > * Convert negative, zero and tiny args to the same limits > * as atkbd. We could support delays of 1 msec, but > * anything much shorter than the shortest atkbd value > * of 250.34 is almost unusable as well as incompatible. > */ > kbd->kb_delay1 = imax(((int *)arg)[0], 250); > kbd->kb_delay2 = imax(((int *)arg)[1], 34); > #ifdef EVDEV_SUPPORT > if (sc->sc_evdev != NULL) > evdev_push_repeats(sc->sc_evdev, kbd); > #endif > return (0); Can you add some prints in ukbd.c where kb_delayX are set and see if their value are zero? Lowest supported value should be 1. --HPS From owner-freebsd-current@freebsd.org Tue Jan 23 22:34:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4BECECC698 for ; Tue, 23 Jan 2018 22:34:27 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::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 604DC73417 for ; Tue, 23 Jan 2018 22:34:27 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-ua0-x22e.google.com with SMTP id x10so1474922ual.8 for ; Tue, 23 Jan 2018 14:34:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pA9wDo+J5j27ovJk2HChIBQnwkUBwV7CggKvBAYluBY=; b=MjpbROi5Z+yLNgm9X734+sQR36jGJc2klxLoRFsaxRfUsnwpG7jgeGJ7rMwi+qOGFJ q1Nq7ZL2GFVh5HiopqDNGv9aaU20TilgVAJBNgxe8Y/XqpE4HiuVPezbV5Y/aECny3aV 2YwqTTPIGVOdw2nwvB4LNnWuTG+HkKaoGzkGX2JshrfhVfhpLck0QZ+1rmipG5N5GRfj aSwXo1Es6gFCf8m0tv7eYpBqyzwfElc8IvBKm65ZwdoVgr28CXfMJHlm3PLZ9y8p+k8X 91AV6Q2thB6L8uknOtN+A2YtHnuYYJUIfPyc+nkFWfJdcOaiHuVJ3kPm/UBxDfiFljFq XXdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pA9wDo+J5j27ovJk2HChIBQnwkUBwV7CggKvBAYluBY=; b=Lp8/Cl69EsyWWHP7e8pRRAgfxsfoxdG+ZZpbyG4AptMnM5/Mi6O6SUK/i77hd6Yv3h J8vAS4jjbDWQK48PJeu41UE5wvTVdff4urDBnTMnBEP0XseAYe/birVyKaa0akBJJ+b2 6QaAM44I6xISi1lVGdsCPg11O7MR8R/1JvRHmJLUFMtTDNiz8ZHr6/HZEAsqk/bR4qbg XlWyn6wyOjRnBl6kjYR/4dS4Gt6X6oiQJzAXigjKZvjZ8dpRpw1+e3vENG2FJrpx3do+ Q0MPXeyixLMwwj5FAHOfCEsmXo3f127X+b41utxPpNoj3978OZkmTfHbshuUL0ZTHVWg rYnQ== X-Gm-Message-State: AKwxytd79TqapVHeZ+H9HzGJh7ccayk61n2nQ52jkAvyUUEyl+sRk13V Lnpb/mAWv2tHWuKLKFgrNpwSGQltwtsV2wFzPFSJfQ== X-Google-Smtp-Source: AH8x225qHDJyL/q/9OPnCewYI49ps57sC0UvJNtll0j2VwaG4WkjUatDnRxmXwFoH0UBYvqGp3V8jYEEdNOd6xyTFJA= X-Received: by 10.176.16.15 with SMTP id f15mr3201558uab.77.1516746865934; Tue, 23 Jan 2018 14:34:25 -0800 (PST) MIME-Version: 1.0 References: <20180123064633.45e2710b@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20180123064633.45e2710b@freyja.zeit4.iv.bundesimmobilien.de> From: Ben Woods Date: Tue, 23 Jan 2018 22:34:15 +0000 Message-ID: Subject: Re: PkgBase: Can not upgrade base system To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 22:34:27 -0000 On Tue, 23 Jan 2018 at 4:12 pm, O. Hartmann wrote: > For a client I tried PkgBase and followed the procedures recommended (first > build the OS from /usr/src/, installworld/kernel, then proceed with pkg > update > -r FreeBSD-base and pkg install -g 'FreeBSD-*'. > > This doesn't work for any update I try to apply. Since the target host is > a two > years old Intel NUC based on some Broadwell snail CPU, building world and > kernel is performed on another, much more potent host. > > In the first place, when performing a "pkg upgrade", the system complains > about > mismatching OSVERSION, 1200055 forthe running system, and 1200056 for the > packages to be updated. When setting env OSVERSION=1200056, pkg (not > pkg-static!) complains about revision numbers (the long date trailing the > package's name), for instance the newest one is > > FreeBSD-hast-12.0.s20180123050738.txz > > contained within the repository to be used for the update, but installed is > something older, like FreeBSD-hast-12.0.s20171103114456.txz. > > When trying pkg-static, I get a crash of pkg-static, segmentation fault is > its > death-cause. > > How am I supposed to update a base system via PkgBase? > > Kind regards, > > oh > > p.s. sorry for the lack of data, the box in question is on a remote site > without net. > > _______________________________________________ > 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" This issue was discussed on the FreeBSD-current mailing list. A workaround has been provided there, but a proper fix is still to be developed: https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068153.html Workaround: # pkg -o OSVERSION=1200056 upgrade Regards, Ben > -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-current@freebsd.org Tue Jan 23 23:19:24 2018 Return-Path: Delivered-To: freebsd-current@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 0D1F6ECF7BE for ; Tue, 23 Jan 2018 23:19:23 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 441396A08E for ; Tue, 23 Jan 2018 23:19:21 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0NN34Zq024737; Wed, 24 Jan 2018 08:03:04 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801232303.w0NN34Zq024737@kx.openedu.org> Date: Wed, 24 Jan 2018 08:03:04 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current Cc: kiri@kx.openedu.org Subject: Broadcom 802.11ac WDI SDIO Adapter (Version 1.605.1.0) not configured User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 23:19:24 -0000 HI, Broadcom 802.11ac WDI SDIO Adapter works in Windows but does not recognaized in my machne[1]. Actually both ifconfig and pciconf show nothing wifi drives found: root@t:~ # ifconfig lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo ue0: flags=8843 metric 0 mtu 1500 options=80008 ether 00:24:a5:9b:81:97 inet 192.168.1.249 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active root@t:~ # pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x72708086 chip=0x22808086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 card=0x72708086 chip=0x22b08086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers' class = display subclass = VGA none0@pci0:0:3:0: class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit' class = multimedia none1@pci0:0:11:0: class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller' class = serial bus subclass = USB none2@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' class = encrypt/decrypt isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU' class = bridge subclass = PCI-ISA root@t:~ # In CURRENT(r328126) Broadcom drivers support with bwn and bwi. I tried to those but can not work: root@t:~ # kldstat Id Refs Address Size Name 1 75 0xffffffff80200000 1ef2aa8 kernel 2 1 0xffffffff820f4000 6c418 if_bwn.ko 3 15 0xffffffff82161000 81b70 bhnd.ko 4 3 0xffffffff821e3000 9298 gpiobus.ko 5 2 0xffffffff821ed000 f5e0 siba_bwn.ko 6 2 0xffffffff821fd000 3d28 if_bwn_pci.ko 7 2 0xffffffff82201000 2e08 siba_bhndb.ko 8 5 0xffffffff82204000 1b0b0 bhndb.ko 9 2 0xffffffff82220000 d568 siba.ko 10 2 0xffffffff8222e000 2120 bcma_bhndb.ko 11 2 0xffffffff82231000 b400 bcma.ko 12 2 0xffffffff8223d000 a640 bhndb_pci.ko 13 2 0xffffffff82248000 5388 bhnd_pci_hostb.ko 14 3 0xffffffff8224e000 61a0 bhnd_pci.ko 15 1 0xffffffff82bfa000 11df77 i915kms.ko 16 1 0xffffffff82d18000 718d0 drm.ko 17 4 0xffffffff82d8a000 fe30 linuxkpi.ko 18 3 0xffffffff82d9a000 e470 linuxkpi_gplv2.ko 19 2 0xffffffff82da9000 6b8 debugfs.ko 20 1 0xffffffff82daa000 3e40 if_axe.ko 21 1 0xffffffff82dae000 1450 uether.ko 22 1 0xffffffff82db0000 2388 ums.ko 23 1 0xffffffff82db3000 1a90 logo_saver.ko 24 1 0xffffffff82db5000 1b180 if_bwi.ko root@t:~ # ifconfig wlan create wlandev bwi0 ssid kiri up ifconfig: SIOCIFCREATE2: Device not configured root@t:~ # ifconfig wlan create wlandev bwn0 ssid kiri up ifconfig: SIOCIFCREATE2: Device not configured root@t:~ # Any pointers or suggestions? My dmesg.boot is in [2]. Best regards [1] https://www.biccamera.com/bc/item/3716011/ [2] http://ds.truefc.org/~kiri/freebsd/sg116j/dmesg.boot --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Wed Jan 24 05:09:23 2018 Return-Path: Delivered-To: freebsd-current@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 8707CEBE186 for ; Wed, 24 Jan 2018 05:09:23 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 2630877D49 for ; Wed, 24 Jan 2018 05:09:22 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1eeDEZ-0048zA-Tn>; Wed, 24 Jan 2018 06:04:27 +0100 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1eeDEZ-000XZY-LY>; Wed, 24 Jan 2018 06:04:27 +0100 Date: Wed, 24 Jan 2018 06:04:21 +0100 From: "O. Hartmann" To: freebsd-current Subject: installworld failure: strip: elf_strptr failed: Invalid argument Message-ID: <20180124060415.063da21c@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 05:09:23 -0000 This drives me nuts: After a successful buildworld, installworld fails. It is always strip: elf_strptr failed: and it hits always different binaries in the obj tree, t= his one is an example: =3D=3D=3D> usr.sbin/nologin (install) install -s -o root -g wheel -m 555 nologin /usr/sbin/nologin strip: elf_strptr failed: Invalid argument install: strip command strip failed on /usr/sbin/nologin *** [_proginstall] Error code 70 I manually deleted /usr/obj/usr/src/amd64.amd64/[s]bin/* and performed a make -jX buildworld again, which completes successfully. But after that, the error pops up in another place, so I delete, rebuild. Now it closed the circle: it starts again with nologin as shown above - the game starts again. What is this about? I try now to rebuild world starting with cleanworld. Hope this resolves the problem. Kind regards, oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). From owner-freebsd-current@freebsd.org Wed Jan 24 10:12:30 2018 Return-Path: Delivered-To: freebsd-current@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 01265ECB3B2 for ; Wed, 24 Jan 2018 10:12:30 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (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 766D481603 for ; Wed, 24 Jan 2018 10:12:29 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pg0-x22b.google.com with SMTP id k68so2365075pga.3 for ; Wed, 24 Jan 2018 02:12:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/3IS3BVFWG1bVSFwS6YSithpKgDf2llJ2sRtMktYe/k=; b=hjF+dxs//AIwC3rRck7OOyOD8swUBXgd2yDQLOiTZ9+yNI/awfttvzph6YnUEZsFxr 0uoKqMNIg5ALlEP2Acnl2Rr26VghJ41SLQXIq/FxZ5qBeqAsLzDtPZO8fldxvTifxTUH qCmMoyF7Hekp4eA+MPg1KrjYLjNtQyCjGudNk/2z+O7d8gHfuKZ6J4Chjrv7oXmh/4sA L68vK3bReIhlYOOePakgK73tYUiI6L1jxvgDZKY14Z8xtpInYPToJ4wrFpxQhilfw9G4 cw2SfsNAzPsgRpex2XDiWGnopIrcjShvM/JXkq346PIDMFUkqvu4+jE2rUZn1ErAkdNY 3yDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/3IS3BVFWG1bVSFwS6YSithpKgDf2llJ2sRtMktYe/k=; b=rTRw7n+lUg47gUlW/5f7zyqVUtvGMixD7KWzJ8Hf+AqCbxZM+R2j6hx/3yWAHHPih+ 3Jdx+FTQR2w+sZ6/T0msi6dAjCAbJMSf7c2hZOax3RCwxJCp5odHi0R+IHJL7sTqrXWh c13+AEs4CWDcEu63wsbX9tY5sGdX0XE8OFfIaPUjc4naQhT8C+75nddNkvQzFLrek6KZ Pm0DXWGiSUwI3t2foPf8cxhoGkbmbWatzgMsXWDNFlwuM0W0e4MZunB1mwtjkf3iyhVO O3LV2COifWox9F8qth5ltYxP/evSQvoPVyuYsNxu1csZa+so39ouf8YUyheNfaX6mr+x bZHQ== X-Gm-Message-State: AKwxytcTcBvRHVlD0T2g234OtPhL53o3n+fh+E83lxfoNf+G0zfFzxOh Dei0KZhWdGdCvM3rJV0j90bMdbDtU83oH00Xf0lDwg== X-Google-Smtp-Source: AH8x226NHPD5VaLSR8cRDDxFLiwMGywbeLJ8NZsr6xaT3+OXTDLHwT7AfHSHYh621bTkaR3jVPQhKBw3d690hA644qM= X-Received: by 2002:a17:902:2cc3:: with SMTP id n61-v6mr7594711plb.440.1516788748177; Wed, 24 Jan 2018 02:12:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.138.144 with HTTP; Wed, 24 Jan 2018 02:12:27 -0800 (PST) From: Maurizio Vairani Date: Wed, 24 Jan 2018 11:12:27 +0100 Message-ID: Subject: Error compiling isboot-kmod To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 10:12:30 -0000 On this CURRENT snapshot # uname -a FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed Jan 10 22:55:40 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I can't compile the kernel module isboot-kmod: # cd /usr/ports/net/isboot-kmod && make ===> License BSD2CLAUSE accepted by the user ===> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for building ===> Extracting for isboot-kmod-0.2.13_1 => SHA256 Checksum OK for isboot-0.2.13.tar.gz. ===> Patching for isboot-kmod-0.2.13_1 ===> Applying FreeBSD patches for isboot-kmod-0.2.13_1 ===> Configuring for isboot-kmod-0.2.13_1 ===> Building for isboot-kmod-0.2.13_1 --- machine --- --- x86 --- --- machine --- machine -> /usr/src/sys/amd64/include --- x86 --- x86 -> /usr/src/sys/x86/include --- objwarn --- --- opt_cam.h --- --- objwarn --- Warning: Object directory not changed from original /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src --- opt_cam.h --- :> opt_cam.h --- isboot.o --- --- ibft.o --- --- isboot.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depe$ d.isboot.o -MTisboot.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-dec$ s -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs $ fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-s$ gn -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c isboot.c -o isboot.o --- ibft.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depe$ d.ibft.o -MTibft.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -$ nested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdi$ gnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign $ Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c ibft.c -o ibft.o --- iscsi.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depe$ d.iscsi.o -MTiscsi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -f$ iagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sig$ -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c iscsi.c -o iscsi.o In file included from iscsi.c:62: In file included from /usr/src/sys/cam/cam_ccb.h:1035: In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: In file included from /usr/src/sys/dev/mmc/bridge.h:59: /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^~~~~~~~~~~~~ 1 error generated. *** [iscsi.o] Error code 1 make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src 1 error make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/net/isboot-kmod *** Error code 1 Stop. make: stopped in /usr/ports/net/isboot-kmod -- Regards Maurizio From owner-freebsd-current@freebsd.org Wed Jan 24 11:37:54 2018 Return-Path: Delivered-To: freebsd-current@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 53982ECE8A4 for ; Wed, 24 Jan 2018 11:37:54 +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 CF02B84AA2 for ; Wed, 24 Jan 2018 11:37:53 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 2fbf76bb TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 24 Jan 2018 11:37:45 +0000 (UTC) Subject: Re: Broadcom 802.11ac WDI SDIO Adapter (Version 1.605.1.0) not configured To: KIRIYAMA Kazuhiko , freebsd-current References: <201801232303.w0NN34Zq024737@kx.openedu.org> From: Greg V Message-ID: <172d461d-5851-090f-1b5d-7c80d69e855f@unrelenting.technology> Date: Wed, 24 Jan 2018 14:37:43 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <201801232303.w0NN34Zq024737@kx.openedu.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 11:37:54 -0000 On 01/24/2018 02:03, KIRIYAMA Kazuhiko wrote: > HI, > > Broadcom 802.11ac WDI SDIO Adapter works in Windows but does > not recognaized in my machne[1]. Actually both ifconfig and > pciconf show nothing wifi drives found: Hi. SDIO support is not there yet. Some development is going on: https://wiki.freebsd.org/SDIO?action=AttachFile&do=view&target=sdio_bsdcam.pdf But seems like it's quite far from actually working with Wi-Fi cards. From owner-freebsd-current@freebsd.org Wed Jan 24 12:09:01 2018 Return-Path: Delivered-To: freebsd-current@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 0A8E3ED09A5 for ; Wed, 24 Jan 2018 12:09:01 +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 9ABA2864B4; Wed, 24 Jan 2018 12:09:00 +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 5DE282604F8; Wed, 24 Jan 2018 13:08:58 +0100 (CET) Subject: Re: Periodical interrupt storm when playing game with USB keyboard From: Hans Petter Selasky To: Johannes Lundberg , blubee blubeeme Cc: Adrian Chadd , Ian Lepore , freebsd-current References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> Message-ID: Date: Wed, 24 Jan 2018 13:06:06 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 12:09:01 -0000 Hi, Can you test and review: https://reviews.freebsd.org/D14027 --HPS From owner-freebsd-current@freebsd.org Wed Jan 24 14:07:59 2018 Return-Path: Delivered-To: freebsd-current@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 7006EED5DC5 for ; Wed, 24 Jan 2018 14:07:59 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 BD3D68AAB0; Wed, 24 Jan 2018 14:07:58 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id v15so4162365wrb.8; Wed, 24 Jan 2018 06:07:58 -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=HYnfIMMTnAxYxpeomDjfos38H41lFJr0kkesqqMe/Ws=; b=b1F6ClaJLKvNjEBfiFYUcxV+mtMNji1a4ysIAMRBJonsoKj2AWAsAezkKMdY7Iq2x9 AqLAWMQ34EUsdkesOV+Ca2DMIx0RCi4gUF+NuC8RuJvZhnDiEptmGlc2cXRkTbQ8y4IL enOuNbfun1sjVI9lZ7eTu9A9MzP2gfRLzD3XhNxzQrU2IG3xQTZim0AQG2HWev+hHxpl PoiDIF+0JZIBAu5ft7F2a6wzWvppWVEbAvHt6axqh7nDGKs1XkRQhRK59Jl4enhRqL7u VvKBUG2YGIHHvI05l3uVQL3CRwwfckHiCN7ibX63iXL8dCwaxWWxMp2GlA4nOG+E84IM hjrA== 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=HYnfIMMTnAxYxpeomDjfos38H41lFJr0kkesqqMe/Ws=; b=PAJhpJC4qfba2SfFZY4f48Z1nWnrtJqXzx5F9jp1xHx2fWDcKqHg2LbzpUcoeeEHAX 9wMpfFDD4WpJqwhQL+XmcUaozTGt1XgZxWt0SjV3f+HcVvRWNQu0xKous6YIh0SphEq+ Tcr2LhGS12Ui14V5CUgniLk49h2oDNkorLnu47kad4zqPOoArFGx2bbgtvxGOQ2pppZm lmWiy9QRtDWZCVdDY+e58L1ItoUQMkojUnGIYavpalnSJxWjU8mOkt0AlVWEqs8B8qJw a45lMHwOxCAZzVxu4CpbIrQH5nRCpLpu7xINLjDqdmYvf539XNJM+L/s/bsuw5hGNfXO IhWg== X-Gm-Message-State: AKwxytcigZmOarJep6ejdLS7d9VX9PXO2On/dh9oRivTCSTP9W3hSm98 zZ6ymIOsGKScWDG45vjIJO+0AtuW0V8EPoBL2XQ= X-Google-Smtp-Source: AH8x227gSMUxg+q0ZXcEGeEMWElti5QkpHqKhnAcYXslT3KVTDvQuDjiITm/JMdCMVK/7pR5tSaROZ6BX9Xm6/ugROo= X-Received: by 10.223.163.6 with SMTP id c6mr6247861wrb.234.1516802876943; Wed, 24 Jan 2018 06:07:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.136.187 with HTTP; Wed, 24 Jan 2018 06:07:16 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Johannes Lundberg Date: Wed, 24 Jan 2018 14:07:16 +0000 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Hans Petter Selasky Cc: blubee blubeeme , Adrian Chadd , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 14:07:59 -0000 On Wed, Jan 24, 2018 at 12:06 PM, Hans Petter Selasky wrote: > Hi, > > Can you test and review: > > https://reviews.freebsd.org/D14027 > > It seems better. Not as many lock_delays and lag but there still is some lag when holding down a key for too long. kernel`z_feed_linear_S16LE 11 kernel`uma_zfree_arg 11 i915kms.ko`gen8_ppgtt_clear_pte_range 11 kernel`bzero 12 kernel`sopoll 13 kernel`sopoll_generic 13 kernel`atomic_add_int 13 kernel`trash_ctor 14 kernel`0xffffffff80f4b548 15 kernel`callout_reset_sbt_on 16 kernel`trash_dtor 16 kernel`spinlock_enter 16 kernel`copyout 16 ichsmb.ko`ichsmb_device_intr 16 kernel`__mtx_lock_spin_flags 17 kernel`softclock_call_cc 18 kernel`selfdfree 20 kernel`uma_dbg_alloc 20 kernel`uma_dbg_free 20 kernel`uma_zalloc_arg 21 i915kms.ko`gen8_ppgtt_insert_pte_entries 21 kernel`copyin 22 kernel`amd64_syscall 22 kernel`witness_warn 23 * kernel`ukbd_interrupt 24* kernel`fget_unlocked 24 kernel`ukbd_timeout 25 kernel`__mtx_assert 28 kernel`usbd_in_polling_mode 30 kernel`_isitmyx 33 kernel`witness_lock 47 kernel`kern_select 54 kernel`bcopy 78 kernel`__mtx_unlock_flags 79 kernel`witness_checkorder 91 kernel`memcpy 100 kernel`__mtx_lock_flags 136 kernel`witness_unlock 160 i915kms.ko`fw_domains_get 184 kernel`spinlock_exit 1904 kernel`cpu_idle 3564 * kernel`lock_delay 3634* kernel`acpi_cpu_idle 29591 --HPS > From owner-freebsd-current@freebsd.org Wed Jan 24 16:19:33 2018 Return-Path: Delivered-To: freebsd-current@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 A9A92EDB3AA for ; Wed, 24 Jan 2018 16:19:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::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 34F528F9A5 for ; Wed, 24 Jan 2018 16:19:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id q8so5793263itb.2 for ; Wed, 24 Jan 2018 08:19:33 -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=w4NXbLEPBkDi3PLzj74t675Fii/URGCDRy+mnnzHkys=; b=TDwslQTbHfU6iygllVtZ7JTJAhV8G0aEqxP+6/Sxtalmp+D/1FqydBLEoQ5L4HUNNx 7gllzTB0VSINwx2Ip9iNXzIpAsEg+SHES3n8aToNtpxCjNMNgq98aA+mxNbPjeiy7pmd /lBlfX+IJ0AtIIayekEN6RqaDrAn0l6NIuE8ICmSw6ogO2GJHfe8qKFI6KWmGU3BO9OT MEPe7/GbWk+Oj3cwdH6jUe1A2d11/v8bWx0FrrfdUaoX3xV7hq4Hg6da59v11EA1plkq aui6X3HHt751iEZlwEuCNvehC2d3a/dypUn80bza9pO9jYERV+n3ETJq2gC6+yEt8VxI GHyw== 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=w4NXbLEPBkDi3PLzj74t675Fii/URGCDRy+mnnzHkys=; b=dqpU/w+L3PXzNagRVdPV9/qsTbfdC4t5QJQ//a95KX75gAFyWwbP+Va79WE8FestC8 ALz7dkJ7EG7m5nG6F2Vn62GECD81cGxr6z9GGgUYOJuZhvYNjh30CD78JQCqzbelpSOw Xexs7C9ySQIyz1+7GKXlhm3E05jMLk3lpm1JDcEdqtcCjxGcWyPPqzt5UHCFVNKIr+fT D97fvV0iiWOSMbPis/HdaCI2QQMrtHn2WgFeCF2aZozrh3R+HaSs3iXDwfjSjwU9gmtd ZTvDuUIiiVi2WxSirvjxfZK8HjnwWRr9Big2gnSMSjbzdYauYbmcL5E6ZfF7dsdlG8ra Ax3Q== X-Gm-Message-State: AKwxytdugB5VV4G/rbflAruF9yIMqfGV0kksQHEGAvc8gwgNKXWEMgEL 0Nw6r0QOFBfD7Ts9V+XYFxkM75AzcB5/KrJNLfYk1A== X-Google-Smtp-Source: AH8x227lEQtPPXUPQOxAG+xx/w/FxISnmMa8Em01GOQav7Q8zjCFwxiKUNEGgVP4+e9lhUTXryRILSBzUUWGOm2mhzA= X-Received: by 10.36.91.210 with SMTP id g201mr9275833itb.50.1516810772614; Wed, 24 Jan 2018 08:19:32 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Wed, 24 Jan 2018 08:19:31 -0800 (PST) X-Originating-IP: [50.227.106.226] In-Reply-To: References: From: Warner Losh Date: Wed, 24 Jan 2018 09:19:31 -0700 X-Google-Sender-Auth: gyq-r2MQwslP330G8_l8_SIrl4Y Message-ID: Subject: Re: Error compiling isboot-kmod To: Maurizio Vairani Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 16:19:33 -0000 On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani wrote: > On this CURRENT snapshot > # uname -a > FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed Jan 10 > 22:55:40 UTC 2018 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > I can't compile the kernel module isboot-kmod: > # cd /usr/ports/net/isboot-kmod && make > ===> License BSD2CLAUSE accepted by the > user > > ===> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for building > ===> Extracting for isboot-kmod-0.2.13_1 > => SHA256 Checksum OK for isboot-0.2.13.tar.gz. > ===> Patching for isboot-kmod-0.2.13_1 > ===> Applying FreeBSD patches for isboot-kmod-0.2.13_1 > ===> Configuring for isboot-kmod-0.2.13_1 > ===> Building for isboot-kmod-0.2.13_1 > --- machine --- > --- x86 --- > --- machine --- > machine -> /usr/src/sys/amd64/include > --- x86 --- > x86 -> /usr/src/sys/x86/include > --- objwarn --- > --- opt_cam.h --- > --- objwarn --- > Warning: Object directory not changed from original > /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > --- opt_cam.h --- > :> opt_cam.h > --- isboot.o --- > --- ibft.o --- > --- isboot.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.isboot.o -MTisboot.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-dec$ > s -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs $ > fdiagnostics-show-option -Wno-unknown-pragmas > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -Wno-error-unused-function > -Wno-error-pointer-s$ > gn -Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=iso9899:1999 -c isboot.c -o isboot.o > --- ibft.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.ibft.o -MTibft.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-decls -$ > nested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdi$ > gnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare > -Wno-error-empty-body -Wno-error-parentheses-equality > -Wno-error-unused-function -Wno-error-pointer-sign $ > Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=iso9899:1999 -c ibft.c -o ibft.o > --- iscsi.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.iscsi.o -MTiscsi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -f$ > iagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological- > compare > -Wno-error-empty-body -Wno-error-parentheses-equality > -Wno-error-unused-function -Wno-error-pointer-sig$ > -Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=iso9899:1999 -c iscsi.c -o iscsi.o > In file included from iscsi.c:62: > In file included from /usr/src/sys/cam/cam_ccb.h:1035: > In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: > In file included from /usr/src/sys/dev/mmc/bridge.h:59: > /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not found > #include "device_if.h" > ^~~~~~~~~~~~~ > I think this was fixed in a newer -current. Warner From owner-freebsd-current@freebsd.org Wed Jan 24 16:39:49 2018 Return-Path: Delivered-To: freebsd-current@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 567E7EB437B for ; Wed, 24 Jan 2018 16:39:49 +0000 (UTC) (envelope-from flo@snakeoilproductions.net) Received: from turad.lysandor.de (turad.lysandor.de [136.243.10.60]) (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 E238D68AB9 for ; Wed, 24 Jan 2018 16:39:48 +0000 (UTC) (envelope-from flo@snakeoilproductions.net) Received: from localhost (localhost [127.0.0.1]) by turad.lysandor.de (Postfix) with ESMTP id A7716AA262A for ; Wed, 24 Jan 2018 17:34:37 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at turad.lysandor.de Received: from turad.lysandor.de ([127.0.0.1]) by localhost (turad.lysandor.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id bGQr_w-36Rwr for ; Wed, 24 Jan 2018 17:34:34 +0100 (CET) Received: from [192.168.2.107] (p4FDCC05B.dip0.t-ipconnect.de [79.220.192.91]) (Authenticated sender: flo@snakeoilproductions.net) by turad.lysandor.de (Postfix) with ESMTPSA id 5236CAA1D4A for ; Wed, 24 Jan 2018 17:34:34 +0100 (CET) To: freebsd-current@freebsd.org From: Florian Limberger Subject: Build error: 'emmintrin.h' file not found Message-ID: <41437fcc-70ee-2cf6-45d5-d4c5635c8b5b@snakeoilproductions.net> Date: Wed, 24 Jan 2018 17:34:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 16:39:49 -0000 Hi, since a few days I can't build 12-CURRENT anymore, due to the 'emmintrin.h' header missing. I hope this is all relevant information: uname -a: FreeBSD $HOSTNAME 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327931: Sat Jan 13 23:47:34 CET 2018 root@$HOSTNAME:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 Build log (make buildworld, using meta mode): -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- cd /usr/src; INSTALL="sh /usr/src/tools/install.sh" TOOLS_PREFIX=/usr/obj/usr/src/amd64.amd64/tmp PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/$ sr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/amd64.amd64/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f Makefile.inc1 DE$ TDIR= OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' OBJROOT='${OBJTOP}/' MAKEOBJDIRPREFIX= BOOTSTRAPPING=1200055 BWPHASE=cross-tools SSP_CFLAGS= MK_HTML=no NO_LINT=yes MK_MAN=no -DNO_PIC MK$ PROFILE=no -DNO_SHARED -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no MK_CLANG_EXTRAS=no MK_CLANG_FULL=no MK_LLDB=no MK_TESTS=no MK_LLD=yes MK_INCLUDES=yes TARGET=amd64 TARGET_ARCH=amd64 MK_GDB=no MK_LLD_I$ _LD=yes MK_TESTS=no cross-tools ===> lib/clang (obj,all,install) ===> lib/clang/libllvm (all) ===> lib/clang/libclang (all) Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang/Basic/SourceManager.o /usr/src/contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp:1175:10: fatal error: 'emmintrin.h' file not found #include ^~~~~~~~~~~~~ 1 error generated. *** Error code 1 Stop. make[4]: stopped in /usr/src/lib/clang/libclang .ERROR_TARGET='Basic/SourceManager.o' .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang/Basic_SourceManager.o.meta' .MAKE.LEVEL='4' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='c++ -O2 -pipe -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/$ sr/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=\"x86_64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" -ffunction-sections -f$ ata-sections -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/$ asic/SourceManager.cpp -o Basic/SourceManager.o;' .CURDIR='/usr/src/lib/clang/libclang' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang' .TARGETS='all' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk /usr/src/sha re/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/lib/clang/libclang/Makefile /usr/src/share/mk/src.opts.mk /usr/src/sh are/mk/bsd.own.mk /usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.linker.mk /usr/src/lib/clang/clang.pre.mk /usr/src/lib/clang/llvm.pre.m k /usr/src/lib/clang/clang.build.mk /usr/src/lib/clang/llvm.build.mk /usr/src/tools/build/mk/bsd.lib.mk /usr/src/share/mk/bsd.lib.mk /usr/src/share/mk/bsd.init.mk /usr/src/share/mk/local.init.mk /usr/src/ share/mk/src.init.mk /usr/src/lib/clang/libclang/../Makefile.inc /usr/src/share/mk/bsd.libnames.mk /usr/src/share/mk/src.libnames.mk /usr/src/share/mk/bsd.symver.mk /usr/src/share/mk/bsd.nls.mk /usr/src/s hare/mk/bsd.files.mk /usr/src/share/mk/bsd.incs.mk /usr/src/share/mk/bsd.confs.mk /usr/src/share/mk/bsd.links.mk /usr/src/share/mk/bsd.dep.mk /usr/src/share/mk/bsd.clang-analyze.mk /usr/src/share/mk/bsd.o bj.mk /usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.sys.mk /usr/src/tools/build/mk/Makefile.boot' .PATH='. /usr/src/lib/clang/libclang /usr/src/contrib/llvm/tools/clang/lib' *** Error code 1 Stop. make[3]: stopped in /usr/src/lib/clang .ERROR_TARGET='all_subdir_lib/clang/libclang' .ERROR_META_FILE='' .MAKE.LEVEL='3' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='.PHONY' .CURDIR='/usr/src/lib/clang' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang' .TARGETS='all' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk /usr/src/sha re/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/lib/clang/Makefile /usr/src/share/mk/src.opts.mk /usr/src/share/mk/bs d.own.mk /usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.linker.mk /usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.init.mk /usr/src /share/mk/local.init.mk /usr/src/share/mk/src.init.mk /usr/src/lib/clang/../Makefile.inc' .PATH='. /usr/src/lib/clang' *** Error code 1 Stop. make[2]: stopped in /usr/src .ERROR_TARGET='cross-tools' .ERROR_META_FILE='' .MAKE.LEVEL='2' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='.PHONY' .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' .TARGETS='cross-tools' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk /usr/src/sha re/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/Makefile.inc1 /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd .opts.mk /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/bsd.linker.mk /usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk /usr/src/Makefile.libcompat /usr/src/share/mk/bsd.subdir.mk /usr/src/share/ mk/bsd.init.mk /usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk' .PATH='. /usr/src' *** Error code 1 Stop. make[1]: stopped in /usr/src .ERROR_TARGET='_cross-tools' .ERROR_META_FILE='' .MAKE.LEVEL='1' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='.PHONY' .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64' .TARGETS='buildworld' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk /usr/src/sha re/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/Makefile.inc1 /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd .opts.mk /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/bsd.linker.mk /usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk /usr/src/Makefile.libcompat /usr/src/share/mk/bsd.subdir.mk /usr/src/share/ mk/bsd.init.mk /usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk' .PATH='. /usr/src' *** Error code 1 Stop. make: stopped in /usr/src .ERROR_TARGET='buildworld' .ERROR_META_FILE='' .MAKE.LEVEL='0' MAKEFILE='' .MAKE.MODE='normal' _ERROR_CMD='.PHONY' .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64' .TARGETS='buildworld' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='/usr/obj' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64' /etc/src.conf: WITHOUT_PROFILE=YES WITHOUT_DEBUG_FILES=YES WITHOUT_TESTS=YES /etc/src-env.conf: WITH_META_MODE=YES Regards flo From owner-freebsd-current@freebsd.org Wed Jan 24 18:54:37 2018 Return-Path: Delivered-To: freebsd-current@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 E34A3EBEAA0 for ; Wed, 24 Jan 2018 18:54:36 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24FEF716FA for ; Wed, 24 Jan 2018 18:54:35 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id w0OIsH9L022335 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=OK); Thu, 25 Jan 2018 05:54:23 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w0OIsBCS091240 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Thu, 25 Jan 2018 05:54:11 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w0OIsBvu091239; Thu, 25 Jan 2018 05:54:11 +1100 (AEDT) (envelope-from peter) Date: Thu, 25 Jan 2018 05:54:11 +1100 From: Peter Jeremy To: Florian Limberger Cc: freebsd-current@freebsd.org Subject: Re: Build error: 'emmintrin.h' file not found Message-ID: <20180124185411.GI75633@server.rulingia.com> References: <41437fcc-70ee-2cf6-45d5-d4c5635c8b5b@snakeoilproductions.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5L6AZ1aJH5mDrqCQ" Content-Disposition: inline In-Reply-To: <41437fcc-70ee-2cf6-45d5-d4c5635c8b5b@snakeoilproductions.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 18:54:37 -0000 --5L6AZ1aJH5mDrqCQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Jan-24 17:34:33 +0100, Florian Limberger wrote: >since a few days I can't build 12-CURRENT anymore, due to the 'emmintrin.h' >header missing. I ran into a similar problem about a month ago. First of all, does your host system have emmintrin.h? E.g. what is the output of "find /usr/lib/clang -name emmintrin.h" ? --=20 Peter Jeremy --5L6AZ1aJH5mDrqCQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAlpo1lNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzR85A/+KlEdsuFo7k2BRttItBYz52YcDMVdV3dAwXHoMc+IhAiJbF5ZabxUMiqb fNWNvlAo5LdfHuyfWDCAsuB7rAYlQvkVvtW4o0vq0FyUnYdGjhGBlSXmW0/G+zJB VQwCKIug5C39R+s8qXG8evv8r02oSMcn2kkrlXfin4kq7to0CL1pbNoNjW+kos4P k+2w4Ic6b74sbsluAobCnEbzPL4vaEdEiQ2Ewt6G0XuZAum2Gy0Sh6TS8CxrN4tR O3L3bHEUxOj546/be3rIaI3oXHM3vAaSSrhs8vT2xNVIj76SAbTdk0qkZMNG7qHO 5jc/wKXtvzHJaL8PMlmP6/5d40CDo1zZWjc7MGlrnkC5S/zfDOp17l8h7FJ/QJZ1 Q7EoYo8k2vN1mbyO18Yf8TS7ospiZkOqaiko7M53L03JyppBsAKcye3U9dhYQ+pL qc+EvIFFt6hZLmhpAsiWPkUXXpzeg4hlNKK+yDaOMKIJ0kh7PGuJjEGU5TcNNKJz 4XaDHuE0NbxEwtkRfYrBmwFNF4D0YjItXeQ0bVVesqFGBlwkc5UGbOnq6wNJIGgA 8JbX4kDv0KStySjLrNxOKT5oUevmR734eO7zCJDAk+S4k5oBOCr+pODTfw+A+z+e OM93X/TmG3UNIGWoxx5RJ0YS8vHKxlg2RvE/qfSc4xTiHUSXPbY= =aujP -----END PGP SIGNATURE----- --5L6AZ1aJH5mDrqCQ-- From owner-freebsd-current@freebsd.org Thu Jan 25 07:12:53 2018 Return-Path: Delivered-To: freebsd-current@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 E011AEC50D9 for ; Thu, 25 Jan 2018 07:12:53 +0000 (UTC) (envelope-from flo@snakeoilproductions.net) Received: from turad.lysandor.de (turad.lysandor.de [136.243.10.60]) (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 819056F35D for ; Thu, 25 Jan 2018 07:12:53 +0000 (UTC) (envelope-from flo@snakeoilproductions.net) Received: from localhost (localhost [127.0.0.1]) by turad.lysandor.de (Postfix) with ESMTP id 878F4AA2867; Thu, 25 Jan 2018 08:12:48 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at turad.lysandor.de Received: from turad.lysandor.de ([127.0.0.1]) by localhost (turad.lysandor.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id V-MGPHOgAOg8; Thu, 25 Jan 2018 08:12:46 +0100 (CET) Received: from [192.168.2.104] (p4FDCC05B.dip0.t-ipconnect.de [79.220.192.91]) (Authenticated sender: flo@snakeoilproductions.net) by turad.lysandor.de (Postfix) with ESMTPSA id 717F4AA27F0; Thu, 25 Jan 2018 08:12:46 +0100 (CET) Subject: Re: Build error: 'emmintrin.h' file not found To: Peter Jeremy Cc: freebsd-current@freebsd.org References: <41437fcc-70ee-2cf6-45d5-d4c5635c8b5b@snakeoilproductions.net> <20180124185411.GI75633@server.rulingia.com> From: Florian Limberger Message-ID: Date: Thu, 25 Jan 2018 08:12:45 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180124185411.GI75633@server.rulingia.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 07:12:54 -0000 Hi, indeed, `emmintrin.h` was missing. Along with everything else in `/usr/lib/clang`. I copied its contents from a recent snapshot release and the build went fine. I just don't know how I managed to mess that up. Thank you for the pointer! Regards flo Am 2018-01-24 um 19:54 schrieb Peter Jeremy: > On 2018-Jan-24 17:34:33 +0100, Florian Limberger wrote: >> since a few days I can't build 12-CURRENT anymore, due to the 'emmintrin.h' >> header missing. > > I ran into a similar problem about a month ago. First of all, does > your host system have emmintrin.h? E.g. what is the output of "find > /usr/lib/clang -name emmintrin.h" ? > From owner-freebsd-current@freebsd.org Thu Jan 25 18:36:18 2018 Return-Path: Delivered-To: freebsd-current@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 5BB1CEC5507 for ; Thu, 25 Jan 2018 18:36:18 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from dnvrco-cmomta03.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A6DA86B267 for ; Thu, 25 Jan 2018 18:36:17 +0000 (UTC) (envelope-from david.boyd49@twc.com) Received: from bashful.bsd1.net ([74.138.140.144]) by cmsmtp with ESMTPA id emIQeuWpVJ07YemIheTYGe; Thu, 25 Jan 2018 18:31:13 +0000 Message-ID: <1516905044.8143.4.camel@twc.com> Subject: 12.0-CURRENT VM image won't mount USB flash drive From: David Boyd To: freebsd-current@freebsd.org Date: Thu, 25 Jan 2018 13:30:44 -0500 X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 X-CMAE-Envelope: MS4wfM3QPoIkraiYWeWPDf6bp9Jy7+tp/A86RWrY2jh6hEzzIV696GTZHgYq2+QJMBNZ8N0R8goKZW8x/aFJ+jDbBVI8YtNF6ZC9b1Tm7ztod8784i9Cjjq4 OjWV8xxvWDn9uBi1bBgIcDXyZDc7iAf4gR8= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 18:36:18 -0000 Beginning with 12.0-CURRENT VM image:  FreeBSD-12.0-CURRENT-amd64-20180118-r328126.vmdk.xz and continuing with 12.0-CURRENT VM image: FreeBSD-12.0-CURRENT-amd64-20180125-r328383.vmdk.xz when a USB flash drive is present via the attached USB 3.0 controller the console hangs for 10-12 minutes during boot and then emits the error messages seen in the attachment. The UFS filesystem on the USB flash drive cannot be mounted. If the USB flash drive is connected via the attached USB 2.0 controller, everything is good. This problem is not manifested in any 10.4-STABLE or 11.1-STABLE VM images. The host system is CentOS EL7 7.1708. VirtualBox version is 5.2.6. The USB 3.0 controller uses a VIA chipset. System is for test purposes only, so it is easy to try anything that might help resolve this problem. Thanks. David Boyd From owner-freebsd-current@freebsd.org Thu Jan 25 18:41:56 2018 Return-Path: Delivered-To: freebsd-current@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 7E6F6EC5B27 for ; Thu, 25 Jan 2018 18:41:56 +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 0216E6B6E1 for ; Thu, 25 Jan 2018 18:41:55 +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 w0PIfsG8001264; Thu, 25 Jan 2018 10:41:54 -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 w0PIfs6m001263; Thu, 25 Jan 2018 10:41:54 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201801251841.w0PIfs6m001263@pdx.rh.CN85.dnsmgr.net> Subject: Re: 12.0-CURRENT VM image won't mount USB flash drive In-Reply-To: <1516905044.8143.4.camel@twc.com> To: David Boyd Date: Thu, 25 Jan 2018 10:41:53 -0800 (PST) CC: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Thu, 25 Jan 2018 19:12:35 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 18:41:56 -0000 > Beginning with 12.0-CURRENT VM image: > > ?FreeBSD-12.0-CURRENT-amd64-20180118-r328126.vmdk.xz > > and continuing with 12.0-CURRENT VM image: > > FreeBSD-12.0-CURRENT-amd64-20180125-r328383.vmdk.xz > > when a USB flash drive is present via the attached USB 3.0 controller > the console hangs for 10-12 minutes during boot and then emits the > error messages seen in the attachment. > > The UFS filesystem on the USB flash drive cannot be mounted. > > If the USB flash drive is connected via the attached USB 2.0 > controller, everything is good. > > This problem is not manifested in any 10.4-STABLE or 11.1-STABLE VM > images. > > The host system is CentOS EL7 7.1708. > > VirtualBox version is 5.2.6. > > The USB 3.0 controller uses a VIA chipset. > > System is for test purposes only, so it is easy to try anything that > might help resolve this problem. I think I hit this the other night, and just chocked it off to some problem on my set up. I plugged a USB stick into a build box to splat a Chromebook-Snow/arm image on and nota, the usb stick did not show up. I just unplugged it and plugged it into another socket without looking and boom, it showed up. Now that I go look at where I was plugging this in the first connector was a USB 3.0, the second was a USB 2.0. The machine is running FreeBSD-12.0-CURRENT-amd64-20180118-r328126 > Thanks. > David Boyd -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu Jan 25 20:19:12 2018 Return-Path: Delivered-To: freebsd-current@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 6A1D0ECAEF4 for ; Thu, 25 Jan 2018 20:19:12 +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 09E546F88B for ; Thu, 25 Jan 2018 20:19:11 +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 1eenzE-0006iy-Hm for freebsd-current@freebsd.org; Thu, 25 Jan 2018 21:19:04 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Date: Thu, 25 Jan 2018 21:19:06 +0100 To: "FreeBSD Current" Subject: pkg OSVERSION problem 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: a2d32f98be707cbcda8602d5fffa976a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:19:12 -0000 Hi, After I have an error about OSVERSION pkg upgrade says there is no update anymore. I know there should be multiple updates of packages. Even with -o OSVERSION it does not give any new pkgs anymore. What will help this? Regards, Ronald. [root@sjakie ~]# pkg upgrade Updating FreeBSD repository catalogue... Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 Fetching packagesite.txz: 100% 6 MiB 3.0MB/s 00:02 Processing entries: 0% pkg: Newer FreeBSD version for package pear-HTML_Template_IT: - package: 1200056 - running kernel: 1200054 pkg: repository FreeBSD contains packages for wrong OS version: FreeBSD:12:amd64 Processing entries: 100% Unable to update repository FreeBSD Error updating repositories! [root@sjakie ~]# pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking for upgrades (15 candidates): 100% Processing candidates (15 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [root@sjakie ~]# pkg -o OSVERSION=1200056 upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking for upgrades (15 candidates): 100% Processing candidates (15 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. From owner-freebsd-current@freebsd.org Thu Jan 25 20:22:51 2018 Return-Path: Delivered-To: freebsd-current@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 EA391ECB344 for ; Thu, 25 Jan 2018 20:22:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C08D6FCEB; Thu, 25 Jan 2018 20:22:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.182.13.183]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LoE4f-1fGaY73jCL-00gDWT; Thu, 25 Jan 2018 21:17:31 +0100 Date: Thu, 25 Jan 2018 21:16:56 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Cc: Warner Losh , Mark Johnston , Michael Tuexen , Ed Maste Subject: Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 30 23:29:24 <0.2> Message-ID: <20180125211723.6e65329f@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> <20180108153356.GA2412@raichu> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/DrIwn3ci4fBg94yiFsXxNhQ"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:gvvNPEgkKJiuXdku+fb8JhgFwLmgQkmAZq+ubG3Uv6qcG1bel8e XQzKONB+CfbVvXJG6ZnhRiP5grA2/K4mIYF3PBMkUpTL+zBmgVxTT683JgcjMxuLMKvJTQn 66DH/yd+hoTCFf3gOlf/b80o2uy/rnZ6S8sSljsvb6z8arUrcKEhc6iu/tYlqcWV1LgNdQS 3DxP/zEizPUmVOUh/tGsw== X-UI-Out-Filterresults: notjunk:1;V01:K0:b1z5xNYR7xk=:rV5f32CbMUM1dA8ou0yjiP o9ednCojd5IT8C2OVjOgLWdTKspHQ8o9aIJN9iLquIhARme1/rqAeifKNBKZV3jKXL9Wv6DV0 c08N9Vtb60u584x/zhweiyydgE1Oy+NathB58VnNHR/+8R3DAkWjGvEz972QMpl+wmyiWf4WR sv1x72xjPNAd+ObSMLMNt107f8BdIL24BQ02q/3M3m5lvta2XIFL9bQRp21PrToWzWPE+ONHh 4cL84/j1nPvpd+wkWy0u9YER2aI35vBqBTG4s3KO26tOrHP50SwKq62MpkLA+uOdOPbDhkY7e zTNnajd8/9+HpioPyaWx9W55YU7PI9nPSdgf1Y4UnasaVY1pJbCQoU0t5QXbi2eGOy4H4feOO v3IzOkeRPrJs0IecWxKQj1HOhCPLzREkjg8PzXA7mfpo8gHmBKvH5U3IY8SKg9qyRTfiCIA2s dCu8miNunx3INPD309Es8ao0qJ6XKIcFFqdkZkiVYuZAqIQXRibKwvUUyO8EJni0U2CZrGh9h NZ/NvWpFy0c5MDxl3VqtWvlHbyTTnQJBzeZaykE6l0NOgDJXQQ+tsFh9HZCyP9aQngLpRuWoq DNvf/myDCiRzX3ZVYAoIj7iQm1ZcSfB9TaU5g9VhOBR0PVWr6pg3I0XCo6KnPRcwWf8CH4EqQ xfpQzLciHyXWYt6jjaHckja5jXbiJIoKm0ss0o5E1ZJsaaVRLnU2kkArJu4e2tItnRX+pyiB3 ZI+saeGAumlvg2xzHWi5uMu47Se3kaf+O52gT9PvUPmVvsM6KUYjAHlt0IG9KcO4w3XmUBlNa DJ7TdZv5VSKulZO9IIoNNUA34W8Kw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:22:51 -0000 --Sig_/DrIwn3ci4fBg94yiFsXxNhQ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 8 Jan 2018 09:12:16 -0700 Warner Losh schrieb: > On Jan 8, 2018 8:34 AM, "Mark Johnston" wrote: >=20 > On Thu, Jan 04, 2018 at 09:10:37AM +0100, Michael Tuexen wrote: > > > On 31. Dec 2017, at 02:45, Warner Losh wrote: > > > > > > On Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann = =20 > wrote: > > > =20 > > >> On most recent CURRENT I face the error shwon below on /tmp filesyst= em > > >> (UFS2) residing > > >> on a Samsung 850 Pro SSD: > > >> > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: =20 > 0x4515d2a3 !=3D > > >> bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> > > >> I've already formatted the /tmp filesystem, but obviously without any > > >> success. > > >> > > >> Since I face such strange errors also on NanoBSD images dd'ed to SD = =20 > cards, > > >> I guess there > > >> is something fishy ... =20 > > > > > > > > > It indicates a problem. We've seen these 'corruptions' on data in =20 > motion at > > > work, but I hacked fsck to report checksum mismatches (it silently =20 > corrects > > > them today) and we've not seen any mismatch when we unmount and fsck = the > > > filesystem. =20 > > Not sure this helps: But we have seen this also after system panics > > when having soft update journaling enabled. Having soft update journali= ng > > disabled, we do not observed this after several panics. > > Just to be clear: The panics are not related to this issue, > > but to other network development we do. =20 >=20 > I saw the same issue this morning on a mirrored root filesystem after my > workstation came up following a power failure. fsck recovered using the > journal, and I subsequently saw a number of these checksum failures. > Upon shutdown, I saw the same handle_workitem_freefile errors as above. > I then ran a full fsck from single-user mode, which didn't turn up any > inconsistencies, and after that the checksum failure errors disappeared, > presumably because fsck fixed them. >=20 >=20 > Yes. Fsck automatically fixes issues like that. It does it silently. I ha= ve > patched to make it noisy, and the dozen cases I saw the errors, fsck was > silent with my whiny patches. I can put them up for review if people want= ... >=20 > Warner within the past couple of weeks - or since the first occurence of these str= ange reports, I have had mysterious crashes: when installing FreeBSD even the proper (rec= ommended) way, the box suddenly crashes out of the blue. The symptoms are always the same = and the result is also always the same: the box is unusable, the boot process is stuck at = BTX halted with a list of dumped CPU registers (I guess it is the CPU registers) and t= he filesystem is corrupt. I have had this strange problem on several hosts with SSDs - I = reported end November/beginning of December 2017 of those crashes. On on machine I refom= ated the SSD and did a playback from ab 'dump'-backup - since then those crashes went aw= ay. The box now in question is the last of them not being traeted that way. it seems, t= here is somewhere/somehow a minefield hidden and I have no clue what it could be :-( I'm going to do the very same soon with the SSD of the remaining box - dump= and restore. I just wanted to note this for the record. The crash happend with FreeBSD 12.0-CURRENT #14 r328409: Thu Jan 25 20:40:= 27 CET amd64. Kind regards, Oliver 2018=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/DrIwn3ci4fBg94yiFsXxNhQ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmo7UwAKCRDS528fyFhY lJeQAf0XYgWzSL4pWHomsqM9lPYnUYhN3hHA+pKBjv/BdPWKVsn4vLOjADwmn/Xn f2nyB6LIabgQ9HnAThOCPeFXoEjyAf9Y5KQDS0n+6WC/TpL4HBSQYXjW9Kx2yTBu EgDJ9XIRiZiSaQ3+unW/q7LmNZaNL7sj340RIxNJ1E8HgDbCHoza =DIAb -----END PGP SIGNATURE----- --Sig_/DrIwn3ci4fBg94yiFsXxNhQ-- From owner-freebsd-current@freebsd.org Thu Jan 25 20:29:52 2018 Return-Path: Delivered-To: freebsd-current@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 52FADECB87F for ; Thu, 25 Jan 2018 20:29:52 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA4846FFC6 for ; Thu, 25 Jan 2018 20:29:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.182.13.183]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MgLMU-1eSCiI10UQ-00NjFg; Thu, 25 Jan 2018 21:29:48 +0100 Date: Thu, 25 Jan 2018 21:29:14 +0100 From: "O. Hartmann" To: "Ronald Klop" Cc: "FreeBSD Current" Subject: Re: pkg OSVERSION problem Message-ID: <20180125212941.3b0252f9@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/EBfQB6YqJUs+i69Ow.BeOis"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:o7+yMBhmqAOsv2qLyklubq+BhO9gKLMqkWfgYBPVGxbAFI3XC6S BjvIM1dN2GMyKhLtUHQuuPN2BzkdqjqL31M8K3RSbAwlTE+e3hq2v+RyyPA+2//LcegB7j8 3LvF41Z6TTHOHly5zeKpiNh0vKgMZw9/V2Vyo/AUnMiMNgvN+AJipoDVMRpZTXhBpyCxCR/ RYV3sUplUhWzCUk2AdOvg== X-UI-Out-Filterresults: notjunk:1;V01:K0:sQRv0hkWoXg=:51QUGezNtPqSeCgRJao9r6 wzX1IQllr9wiEeUnTjYMjJCwUTjDgo4bLsjecye7JB/mhH8OG/u9kPtzy/slHQ9WNiWtKAHFU iFROF1G9Yq9Qf4oe+xYJZl08HFdFoV0DmZ4QIdo3BYYTo2qtkv9iL3VzetQeab/CMHpPIZ7h2 Y8Xg9ZpvGkYXKN3fLUAeExUc/ktwzK1wDOs0BRHW+gulfJkdDyuu9Tg/URGkWCY+NX5HirmBF /wxr41UGwL/+t3yc5i1PnDxe49cy2wXMFYyPlMCB3aH8EMsih6HopJd5BbpFiKsRur8rIuMU9 qkUFMwbcy4MJU2eO6j28OGydcgFKME+GLHHhEryfYgyKwOvsilSX6qoO/2BBssAXkoJEF2scP 7X/JJlv0N1fZZKwZRxt4u3gmJ8c8mDzzpU7x/W2SIpU8N2Hm7csEA/VWgtjxNd6W2tyy6Om8M dE85CWIvLRtbHMbFLhDFLb2poOGLIxoC3DkpZwww01sWnPworGLJalAbZVqLDB8lGSnd+lVZk 2onrG+McVD/UUIIX6k9si5vU7dBOJ2LRrI1YOI999ROlRBn17K75ZZjIUoBIkaThLlCoVEZT3 A3pbV375YDp45L5LRWb99bOaeSTl1+gSLNGfDFsYoyo/I1qYSQfFPuEUIsm8vMBO0gYSU7Rw9 PVw8U0CkS7nzDzTFz3+N1nzH1yy8xDr2+hfTmhEfpVr7wXOal9bWnGYWQUQnq2xcnFPy10V9m 1awBMaGigPAooKu+Lr87w7dCn1IBiZtxgIxmvkjg8ntfg7pXwg8KCNBVMuUR4uPWVx+GCwUe/ kjmXa1pYXtrjBaXZXbNxEssAeKWpQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:29:52 -0000 --Sig_/EBfQB6YqJUs+i69Ow.BeOis Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 25 Jan 2018 21:19:06 +0100 "Ronald Klop" schrieb: > Hi, >=20 > After I have an error about OSVERSION pkg upgrade says there is no update= =20 > anymore. > I know there should be multiple updates of packages. > Even with -o OSVERSION it does not give any new pkgs anymore. > What will help this? >=20 > Regards, > Ronald. >=20 >=20 > [root@sjakie ~]# pkg upgrade > Updating FreeBSD repository catalogue... > Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 > Fetching packagesite.txz: 100% 6 MiB 3.0MB/s 00:02 > Processing entries: 0% > pkg: Newer FreeBSD version for package pear-HTML_Template_IT: > - package: 1200056 > - running kernel: 1200054 > pkg: repository FreeBSD contains packages for wrong OS version: =20 > FreeBSD:12:amd64 > Processing entries: 100% > Unable to update repository FreeBSD > Error updating repositories! >=20 > [root@sjakie ~]# pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > Checking for upgrades (15 candidates): 100% > Processing candidates (15 candidates): 100% > Checking integrity... done (0 conflicting) > Your packages are up to date. >=20 > [root@sjakie ~]# pkg -o OSVERSION=3D1200056 upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > Checking for upgrades (15 candidates): 100% > Processing candidates (15 candidates): 100% > Checking integrity... done (0 conflicting) > Your packages are up to date. > _______________________________________________ > 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" me, too. I saw the same thing last week, when I tried the first time to upd= ate a CURRENT and I saw it again on Monday. Funny: when I sync the base repository (built= on another machine due to performance issue and rysnc'ed), the initial error about the= OS mismatch occurs one time again and the disappears - as decribed above. Regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/EBfQB6YqJUs+i69Ow.BeOis Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmo+NQAKCRDS528fyFhY lAW5Af4us5Y5wYQS+HGPiv+bDmT4OphE6etSXaKlIEo1uxb4iPJyTHUWOc50qkwE jyqNi1Q+gbga7NPp6geOFetMWQo8AfsHxtX7D8AXkrbkSuwZ/Mp3+56OOVNADcNZ CdNvxqpjwNLooBSYmmg7gHXcz49yDKANGBiOgrUcY4BUbiZ7ocMT =SrX5 -----END PGP SIGNATURE----- --Sig_/EBfQB6YqJUs+i69Ow.BeOis-- From owner-freebsd-current@freebsd.org Thu Jan 25 20:38:32 2018 Return-Path: Delivered-To: freebsd-current@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 70B3BECC0E6 for ; Thu, 25 Jan 2018 20:38:32 +0000 (UTC) (envelope-from jan.kokemueller@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 C0E33705FD for ; Thu, 25 Jan 2018 20:38:31 +0000 (UTC) (envelope-from jan.kokemueller@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id q194so11470248lfe.13 for ; Thu, 25 Jan 2018 12:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=lIc85aOpCia7eePKQDNF9wqf59ycQUYba8LacqSC4lY=; b=rQyRaGCkfmE6fVt55NLjjUG+hQzm5Wbk1TtMdqhT67rhZqqSOB+W7uDbIzMUu9RiHq n4cb8v1QySFrc8BvmlyJ5PIMcqK6sZCJkhOvY1OPz+Id4KwFVUDAILSZO9HEU5RD30Pw neXeGuONVuM5PCydJtzIz6cDmQT/CN6tKo4r8th2RLFAoyg0reaCyl7vhBKIvC/tu0HL 8cV262LOQPGKom0AQYQM6yyiotPuga5uLyJggGAwdZTgbZS9/yAfa2sj4kmNG+m9YKMU a6DPaWn4IT3bd6sWW1Am4E50zqMZUohT+vUpzljThT8xTX1bM1kBtmSAb8IprZ0zelQ4 Au8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=lIc85aOpCia7eePKQDNF9wqf59ycQUYba8LacqSC4lY=; b=djRgNOdTtswEe8hV5EW3E4iiszbQuCn4ubeKsbZT3lFizl/pZJcQLK+uqDY7/55nvN 0ep8Rlkkgd/yD0TxfhbbagT9RIY/JnwDw0UJsc8oVeuGIqgLPPPZFHTkkyCBxZcN9Zo9 xaPDLi5q4DUY8Kc+PmCw07JeNIoAL3YY3CrUYzhq5b6AQdWtP2AhEsu0wyMdbFWc0H3X TNFoy89WVYTfG/I2YDkxDins6AzH+/8Gk/fyIgT7mBAA4D0dIdjHdgCh8ckGAlthKvJb 5NkyZ5Eooep0viXH0e9aMEa5H+N0k/LzPa0exsAEk8E5rJh7beOQXnCMs7OI3ZSaGvtm hKgA== X-Gm-Message-State: AKwxytd9xZHAfOQOPMQ67H+o+57npZYN0q3IRM6GoBKgDb6NEe+3ggz/ A/bX2pE86UFOCd/s0Dc8EZSmSg== X-Google-Smtp-Source: AH8x2251GuRoHMWaswLRDV57uB1ExK+ji2+wlGYQ5eAwFRvdTzDl+BeR0TliqMcuPGBGOzhNptmxVA== X-Received: by 10.46.115.22 with SMTP id o22mr7041364ljc.89.1516912710138; Thu, 25 Jan 2018 12:38:30 -0800 (PST) Received: from [192.168.1.168] (p5B3D2F59.dip0.t-ipconnect.de. [91.61.47.89]) by smtp.googlemail.com with ESMTPSA id 28sm1136076lfw.57.2018.01.25.12.38.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 12:38:29 -0800 (PST) Subject: Re: pkg OSVERSION problem To: Ronald Klop , FreeBSD Current References: From: =?UTF-8?Q?Jan_Kokem=c3=bcller?= Message-ID: Date: Thu, 25 Jan 2018 21:38:27 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:38:32 -0000 On 25.01.2018 21:19, Ronald Klop wrote: > I know there should be multiple updates of packages. > Even with -o OSVERSION it does not give any new pkgs anymore. > What will help this? I've just had the same issue and solved it by forcefully updating the package database: # pkg -o OSVERSION=1200056 update -f # pkg -o OSVERSION=1200056 upgrade -Jan From owner-freebsd-current@freebsd.org Thu Jan 25 21:58:07 2018 Return-Path: Delivered-To: freebsd-current@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 83CD5ED02B9 for ; Thu, 25 Jan 2018 21:58:07 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1B50673C3B for ; Thu, 25 Jan 2018 21:58:07 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mailman.ysv.freebsd.org (Postfix) id CD851ED02B4; Thu, 25 Jan 2018 21:58:06 +0000 (UTC) Delivered-To: current@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 BB52DED02B3 for ; Thu, 25 Jan 2018 21:58:06 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BA0E73C39 for ; Thu, 25 Jan 2018 21:58:06 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-yb0-x22c.google.com with SMTP id k127so3619883ybc.12 for ; Thu, 25 Jan 2018 13:58:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=IPe9BoDhUGy94Aoqp/iXvxq6Kky+OpSDm8tMzIqFPaY=; b=a/iys7AFPKM0rw0qIDFVyQy141m6XHtqlnG8h3qrQtsq0J/JEHuPLKb+xd++6zdnop cT1h3ZVzkMUq3hvbYMROmLhpxeuy6kAmJM/2Xp49JCotG8VSXsUjcr786f2RYo+dECmI JrWaPNMpK36+EROIPYBIfu3CV/cZdls3d/X5VXkQO6+gebmF0UQD2SADZvfTe+p4smLe FnEyIrxl31vBaTRQ1VmFkVk+PeFBWkyA7qcfEKdIELQ1zqsheDGKK9tc0+cuOmhBljAg n1mirvgyj9Bsdkw7soKFPlhJKY0iGnJT2GQux2thAs5i355CYzDaqurN6mKOdpQ8jhen I3YA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=IPe9BoDhUGy94Aoqp/iXvxq6Kky+OpSDm8tMzIqFPaY=; b=krCHPcg42yh4k373nsR8lV5XOrq6nxS6n8XZJPweUfCkzeY596SuqY0Pcsqo7KdY8A NwUVjIRUPQwqvhoDJB7PEBuejdB1yi/XY2DAiEBUtYxPxIXWFJQR4GYJ7U2XLkPj6rFU NOqEx4+jsf4zZMNsTRk1FSlImzHGt5NPX4iO+GINttMZJLodMH6DzUHPUslcor0bgyku ebYNdnkxk8nqdHZbyDADlYB2yArUW3O2ADC4WIjacEZYBpBz9MPLsyP+wOHYyVpBzq94 ivRmOGiJOR7wnKjo0lvLyfNiW9xPu2XuhBdpjmwma+NKszSkFg1oG9NoJRmicT8pZZQq ww9g== X-Gm-Message-State: AKwxytcZoWAEosY7rBt2upxAy0F3ERy7wGXf42KrgDlkQRX7j3zMkdzt GrsMiz2YTbhpkeiqLpPRzMY7ctZNO7pUj2R78wCUt3w+vMcK9VdLzPw6WJV+I920USSfpaJw1ml jeiPci/jVb+x9qnSVwHxOFEmG0e2SgXtfjqSJTwyHhiV7xxBxgxySlsQfjfkg6o++xf2w0caOEk gE X-Google-Smtp-Source: AH8x227GD6Iu+1P9cF66eI6C15R3xQyNZsbgnuELUxQOiGPwGG4anA9yP8PlRM6mQSRIp92Jwy01TQ== X-Received: by 10.37.34.8 with SMTP id i8mr9782780ybi.114.1516917485433; Thu, 25 Jan 2018 13:58:05 -0800 (PST) Received: from zen.clue.co.za (c-69-254-3-228.hsd1.ga.comcast.net. [69.254.3.228]) by smtp.gmail.com with ESMTPSA id t12sm1498629ywe.45.2018.01.25.13.58.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 13:58:04 -0800 (PST) To: current From: Ian FREISLICH Subject: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1 Message-ID: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> Date: Thu, 25 Jan 2018 16:58:04 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 21:58:07 -0000 Hi I cannot for the life of me recall why I had vm.pmap.pcid_enabled=3D1 set in loader.conf, but I did.=C2=A0 Most likely very historical reasons. r328166 and later reset without dropping into the debugger during boot, no panic message. Ian --=20 Ian Freislich --=20 From owner-freebsd-current@freebsd.org Thu Jan 25 22:13:22 2018 Return-Path: Delivered-To: freebsd-current@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 AE748ED0FE5 for ; Thu, 25 Jan 2018 22:13:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 44C4C7469D for ; Thu, 25 Jan 2018 22:13:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 03FD1ED0FE4; Thu, 25 Jan 2018 22:13:22 +0000 (UTC) Delivered-To: current@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 E41EDED0FE3 for ; Thu, 25 Jan 2018 22:13:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 5772E7469C for ; Thu, 25 Jan 2018 22:13:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w0PMDCLI008393 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 00:13:15 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w0PMDCLI008393 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w0PMDCQJ008392; Fri, 26 Jan 2018 00:13:12 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 26 Jan 2018 00:13:12 +0200 From: Konstantin Belousov To: Ian FREISLICH Cc: current Subject: Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1 Message-ID: <20180125221312.GU55707@kib.kiev.ua> References: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 22:13:22 -0000 On Thu, Jan 25, 2018 at 04:58:04PM -0500, Ian FREISLICH wrote: > Hi > > I cannot for the life of me recall why I had vm.pmap.pcid_enabled=1 set > in loader.conf, but I did.š Most likely very historical reasons. > > r328166 and later reset without dropping into the debugger during boot, > no panic message. Yes, this is how it is currently behaves. PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985. It is used for very differrent algorithm when PTI=1, comparing with PTI=0. From owner-freebsd-current@freebsd.org Thu Jan 25 22:21:38 2018 Return-Path: Delivered-To: freebsd-current@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 299A7ED173B for ; Thu, 25 Jan 2018 22:21:38 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AB8E074BAF for ; Thu, 25 Jan 2018 22:21:37 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6B060ED1738; Thu, 25 Jan 2018 22:21:37 +0000 (UTC) Delivered-To: current@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 43ED6ED1737 for ; Thu, 25 Jan 2018 22:21:37 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 BD38974BA7 for ; Thu, 25 Jan 2018 22:21:36 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-oi0-x235.google.com with SMTP id 8so2242745oix.13 for ; Thu, 25 Jan 2018 14:21:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=gyukN+dyLHrleDfkEqhU7jh4/IFeCfoCo4Yy4DmqyD4=; b=f+7BW9lZunTT9IyW/9x4IG2BOkzE7zyOCT3LNOwxgehUBfTnsD0BC/ng5F2YlyGf5k OvHwhKrgyTJgij33z/FFqHqDVyHxUvt4IVdQlJibnLdt8wXL62OTfFCyTY0oe0wnKP1i veuRXxtTedQrqbRuk/k3uPrCi9aFwL8yXoxgB61uYPMqPa2Liitu67MITXctFxbQ7wCf jUJLQIDg0azOIagNxQmpW8nCVuyizcMItSCAlQrS0EcDqZH+ogMj5uJnrftrBL31wvAo 1Sf+jC+W5efFpbYgXGUU6d5GgtPBkW0Qir5dEYlvIgIeyvdfA8BCnusiSGJS7QPWck9b EtXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=gyukN+dyLHrleDfkEqhU7jh4/IFeCfoCo4Yy4DmqyD4=; b=hULTjsPBz9o6c1SI3c5uh9ugHvKwleQcpvD67HlAiGNzjHJpqnYNG9UoHyrCHbQWyU HxlNos0oD0OyYy+TY+9OqVwO4h3O8Vd/5U2ajJ4GyZ2isrq960RhEgErsUt5En8u9C/g g0nw3N2E+dgio7gsy+qHMl7fvLMhl8RyP0FmXoEIdr/ET5U25EbutVfPGAiliAcc2gDM VFjBGE3Sq6UAt5/Px3eA+TnpS6/71Q4pnIPIVUCqL4p0QnWv1Rco1/yCDSM/qdC8P5X3 1BvJ+CXUo/YFw4lDG2ZHeJTvBYn7myqHlLMhxQaTvssvDi16TF2NXfLaz0LD1D+ruNO6 Q6lg== X-Gm-Message-State: AKwxytf/LlMXrc9AAxzcXt3d5u60lMHg0bmXb1LixNqm/NSnwHNQIK4r dJF17zo70J6dQLN2essiBVWxRQj8nXmO299OPngoa4ZSqEXSY/aS7oqjT3poUmfVW3GdyK/Xvlj /85kovbu1/O+60IwDvQQ/XmqXqzaLkjtJ0b41rmmIpcK5PfFmJjr7vxfx634tcLJBfthLfYWl7y fT X-Google-Smtp-Source: AH8x2265CTRlxIIaF0NVGtBcX8xepRP5WRxtUiOiyMp47BC3LEQHi1bhcdLNPvrTo6nFy9e1yMHt4w== X-Received: by 10.202.244.137 with SMTP id s131mr2032088oih.327.1516918895547; Thu, 25 Jan 2018 14:21:35 -0800 (PST) Received: from zen.clue.co.za (c-69-254-3-228.hsd1.ga.comcast.net. [69.254.3.228]) by smtp.gmail.com with ESMTPSA id a24sm3042210otd.78.2018.01.25.14.21.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 14:21:34 -0800 (PST) Subject: Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1 To: Konstantin Belousov Cc: current References: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> <20180125221312.GU55707@kib.kiev.ua> From: Ian FREISLICH Message-ID: Date: Thu, 25 Jan 2018 17:21:34 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180125221312.GU55707@kib.kiev.ua> Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 22:21:38 -0000 On 01/25/18 17:13, Konstantin Belousov wrote: > On Thu, Jan 25, 2018 at 04:58:04PM -0500, Ian FREISLICH wrote: >> Hi >> >> I cannot for the life of me recall why I had vm.pmap.pcid_enabled=3D1 se= t >> in loader.conf, but I did.=9A Most likely very historical reasons. >> >> r328166 and later reset without dropping into the debugger during boot, >> no panic message. > Yes, this is how it is currently behaves. > PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985. > It is used for very differrent algorithm when PTI=3D1, comparing with PTI= =3D0. Maybe there should be an "interlock" on these knobs, although judging from the number of reports I'm the only that shot my foot. Ian --=20 Ian Freislich --=20 From owner-freebsd-current@freebsd.org Thu Jan 25 23:14:50 2018 Return-Path: Delivered-To: freebsd-current@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 951E3ED45CD for ; Thu, 25 Jan 2018 23:14:50 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 202447743C for ; Thu, 25 Jan 2018 23:14:50 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w0PNEh0G001159 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 25 Jan 2018 15:14:43 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w0PNEgiB001158 for freebsd-current@freebsd.org; Thu, 25 Jan 2018 15:14:42 -0800 (PST) (envelope-from sgk) Date: Thu, 25 Jan 2018 15:14:42 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: Wedge system == lost files Message-ID: <20180125231409.GA940@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 23:14:50 -0000 So, my system just wedge itself. No panic. No keyboard. No mouse. No remote login. Nothing. Just wedged. The system is FreeBSD 12.0-CURRENT r326432 Fri Dec 1 2017 amd64. Imagine my surprise when I rebooted system and the file I had been editing (and saving after every change) is gone. /usr/lost+found is empty. The file pl19-21.tex is gone along with a few files from latex. -rw-r--r-- 1 kargl kargl - 0 Jan 25 14:53 pl19-21.aux -rw-r--r-- 1 kargl kargl - 0 Jan 25 14:53 pl19-21.log -rw-r--r-- 1 kargl kargl - 0 Jan 25 14:53 pl19-21.out -rw-r--r-- 1 kargl kargl - 0 Jan 25 14:53 pl19-21.pdf -rw-r--r-- 1 kargl kargl - 0 Jan 25 14:52 pl19-21.tex /dev/ada0p5 on /usr (ufs, local, journaled soft-updates) Are there known issues with SUJ, again? -- Steve From owner-freebsd-current@freebsd.org Fri Jan 26 01:04:14 2018 Return-Path: Delivered-To: freebsd-current@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 02AFFED9AF8 for ; Fri, 26 Jan 2018 01:04:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 83EE77B800 for ; Fri, 26 Jan 2018 01:04:13 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w0Q14BvM071788 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 25 Jan 2018 17:04:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w0Q14B0k071786 for freebsd-current@freebsd.org; Thu, 25 Jan 2018 17:04:11 -0800 (PST) (envelope-from sgk) Date: Thu, 25 Jan 2018 17:04:11 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: kldxref: ...: Bad address. Message-ID: <20180126010411.GA59487@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 01:04:14 -0000 This can't be good. make buildworld make buildkernel make installkernel ... ===> zlib (install) install -T release -o root -g wheel -m 555 zlib.ko /boot/kernel/ install -T debug -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug/boot/kernel/ kldxref /boot/kernel kldxref: error while reading /boot/kernel/accf_data.ko: Bad address kldxref: error while reading /boot/kernel/amr_linux.ko: Bad address kldxref: error while reading /boot/kernel/chacha20.ko: Bad address kldxref: error while reading /boot/kernel/cxgb_t3fw.ko: Bad address kldxref: error while reading /boot/kernel/if_cc.ko: Bad address kldxref: error while reading /boot/kernel/if_ccv.ko: Bad address kldxref: error while reading /boot/kernel/if_cxl.ko: Bad address kldxref: error while reading /boot/kernel/if_cxlv.ko: Bad address kldxref: error while reading /boot/kernel/ipmi_linux.ko: Bad address kldxref: error while reading /boot/kernel/nfslock.ko: Bad address kldxref: error while reading /boot/kernel/nfssvc.ko: Bad address kldxref: error while reading /boot/kernel/ng_nat.ko: Bad address kldxref: error while reading /boot/kernel/pflog.ko: Bad address kldxref: error while reading /boot/kernel/plip.ko: Bad address kldxref: error while reading /boot/kernel/pty.ko: Bad address kldxref: error while reading /boot/kernel/rc4.ko: Bad address kldxref: error while reading /boot/kernel/rdrand_rng.ko: Bad address kldxref: error while reading /boot/kernel/udf_iconv.ko: Bad address -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-current@freebsd.org Fri Jan 26 07:31:13 2018 Return-Path: Delivered-To: freebsd-current@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 4F6D4EC70B8 for ; Fri, 26 Jan 2018 07:31:13 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 9FDEC876F2 for ; Fri, 26 Jan 2018 07:31:11 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0Q7V842079870; Fri, 26 Jan 2018 16:31:08 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801260731.w0Q7V842079870@kx.openedu.org> Date: Fri, 26 Jan 2018 16:31:08 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current Cc: kiri@kx.openedu.org Subject: microSDXC can't recognized User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 07:31:13 -0000 Hi, Builtin microSDXC card device can't recognized in may machine[1]. Inserted it but nothing happened. Inserted card is SanDisk SDSQAR-128G-GNMA[2]. But in may another machine, it recognized da0: root@kazu:~ # uname -v FreeBSD 9.2-STABLE #5 r259404M: Mon Dec 16 00:12:52 JST 2013 admin@kazu.pis:/usr/obj/usr/src/sys/GENERIC root@kazu:~ # dmesg | tail -10 ugen4.3: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:1:0:-1: Attached to scbus1 da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: Serial Number 058F63666433 da0: 40.000MB/s transfers da0: 121942MB (249737216 512 byte sectors: 255H 63S/T 15545C) da0: quirks=0x2 root@kazu:~ # My machine in question is r328126 and it's dmesg is [3]. The cause is either my SD card adaptor phisically collapsed or r328126 does not work. BTW I've added pciconf: root@t:~ # pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x72708086 chip=0x22808086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 card=0x72708086 chip=0x22b08086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers' class = display subclass = VGA none0@pci0:0:3:0: class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit' class = multimedia none1@pci0:0:11:0: class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller' class = serial bus subclass = USB none2@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' class = encrypt/decrypt isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU' class = bridge subclass = PCI-ISA root@t:~ # Best regards. [1] https://www.biccamera.com/bc/item/3716011/ [2] http://kakaku.com/item/K0001002985/ [3] http://ds.truefc.org/~kiri/freebsd/sg116j/dmesg.boot --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Fri Jan 26 10:37:47 2018 Return-Path: Delivered-To: freebsd-current@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 77191ECEC68 for ; Fri, 26 Jan 2018 10:37:47 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::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 EFFCD6D63D for ; Fri, 26 Jan 2018 10:37:46 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pg0-x231.google.com with SMTP id u1so47582pgr.0 for ; Fri, 26 Jan 2018 02:37:46 -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=TNEz1xcqAZvgVwxtVme+cRaSs7Auw074o0WgOXLZ1hk=; b=BfMKHcRQ+Z3i+vUFLPv9oMwAVBndxGUb637DjA+YDw1VDkPZuFN2fgRxQmPL877ef6 enNI7ikKA/xy/hvLeta8NxroyMX4+nYecJG8gaAohVCMk1uorfQhqsMqeJ4T0a49Xk5n U1e+Lccpx5ikKhwF2dQNzt0Ho5Fx3zllSHzqCdxXnZoYyKdptHVuOJBxEwsijK4BCr7V 9KDXprSOcmecN8SA+VU3J5umFR1vAzLx9Xw8i/3alPqwYFldbEY5L/85QpxHcueiHwdU gWumaVctbGRY1secXdA/FCEFolgVbPsdDggcj5NspOt8Y6zSJD1iIS6ymH8XO9eMsYaG AzbQ== 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=TNEz1xcqAZvgVwxtVme+cRaSs7Auw074o0WgOXLZ1hk=; b=itv5NYHzk7bYqzwJUi+pbnKMYVt5dssk/jJBW4msvc8YjPTI1VWTOVOk9iW696zzUQ rdlNY4n1SrnXxdE7XW4dKjK4Ov3gqEouqgVLl3LWRkhrpjd1BMYQeDMlQtd34frtqVsS 8Wu3OgtOOPgzE9fhJpaPzjRwcaZE03ZpuCfnUY5KAr+BXUEcE8ZKstpFyhM1I55OGWgl 44btZAEt9AVPbcNrgGjwnEUHvONz4Iq4269uLsb3Hr8tCxxuMr6mgJ+ibljGKoNUZfAD p80gzKBoQQy+QslYE6S7kn4ArhGaqRoQzTZpBXcpEYc7ZffNaL5fuI7LNly3L5G1jwlI 0nfQ== X-Gm-Message-State: AKwxytfG2SoJikJXBKIM6XCkIPMdWBy2gf3hyWohj2AXPz9uEFpHWabd u90QEo3IXHlb1SshTnN3/8ebe32NI6M1mL08UOg= X-Google-Smtp-Source: AH8x226vd3UK+FosxdvgKFidzZo6/Or6J1f8kJi2Jx3dcP2NXDKnV6kN/Dig8BAjO0Vf+exPqgOingsoWIIUjZj7dqc= X-Received: by 2002:a17:902:d24:: with SMTP id 33-v6mr13920245plu.40.1516963065718; Fri, 26 Jan 2018 02:37:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.138.144 with HTTP; Fri, 26 Jan 2018 02:37:45 -0800 (PST) In-Reply-To: References: From: Maurizio Vairani Date: Fri, 26 Jan 2018 11:37:45 +0100 Message-ID: Subject: Re: Error compiling isboot-kmod To: Warner Losh Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 10:37:47 -0000 2018-01-24 17:19 GMT+01:00 Warner Losh : > > > On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani > wrote: > >> On this CURRENT snapshot >> # uname -a >> FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed Jan 10 >> 22:55:40 UTC 2018 >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >> >> I can't compile the kernel module isboot-kmod: >> # cd /usr/ports/net/isboot-kmod && make >> ===> License BSD2CLAUSE accepted by the >> user >> >> ===> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - found >> ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for building >> ===> Extracting for isboot-kmod-0.2.13_1 >> => SHA256 Checksum OK for isboot-0.2.13.tar.gz. >> ===> Patching for isboot-kmod-0.2.13_1 >> ===> Applying FreeBSD patches for isboot-kmod-0.2.13_1 >> ===> Configuring for isboot-kmod-0.2.13_1 >> ===> Building for isboot-kmod-0.2.13_1 >> --- machine --- >> --- x86 --- >> --- machine --- >> machine -> /usr/src/sys/amd64/include >> --- x86 --- >> x86 -> /usr/src/sys/x86/include >> --- objwarn --- >> --- opt_cam.h --- >> --- objwarn --- >> Warning: Object directory not changed from original >> /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src >> --- opt_cam.h --- >> :> opt_cam.h >> --- isboot.o --- >> --- ibft.o --- >> --- isboot.o --- >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE >> -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer >> -mno-omit-leaf-frame-pointer -MD -MF.depe$ >> d.isboot.o -MTisboot.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse >> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv >> -fstack-protector -Wall -Wredundant-dec$ >> s -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes >> -Wpointer-arith >> -Winline -Wcast-qual -Wundef -Wno-pointer-sign >> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs $ >> fdiagnostics-show-option -Wno-unknown-pragmas >> -Wno-error-tautological-compare -Wno-error-empty-body >> -Wno-error-parentheses-equality -Wno-error-unused-function >> -Wno-error-pointer-s$ >> gn -Wno-error-shift-negative-value -Wno-error-address-of-packed-member >> -mno-aes -mno-avx -std=iso9899:1999 -c isboot.c -o isboot.o >> --- ibft.o --- >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE >> -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer >> -mno-omit-leaf-frame-pointer -MD -MF.depe$ >> d.ibft.o -MTibft.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse >> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv >> -fstack-protector -Wall -Wredundant-decls -$ >> nested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >> -Winline -Wcast-qual -Wundef -Wno-pointer-sign >> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdi$ >> gnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare >> -Wno-error-empty-body -Wno-error-parentheses-equality >> -Wno-error-unused-function -Wno-error-pointer-sign $ >> Wno-error-shift-negative-value -Wno-error-address-of-packed-member >> -mno-aes -mno-avx -std=iso9899:1999 -c ibft.c -o ibft.o >> --- iscsi.o --- >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE >> -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer >> -mno-omit-leaf-frame-pointer -MD -MF.depe$ >> d.iscsi.o -MTiscsi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse >> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv >> -fstack-protector -Wall -Wredundant-decls >> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >> -Winline -Wcast-qual -Wundef -Wno-pointer-sign >> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -f$ >> iagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compar >> e >> -Wno-error-empty-body -Wno-error-parentheses-equality >> -Wno-error-unused-function -Wno-error-pointer-sig$ >> -Wno-error-shift-negative-value -Wno-error-address-of-packed-member >> -mno-aes -mno-avx -std=iso9899:1999 -c iscsi.c -o iscsi.o >> In file included from iscsi.c:62: >> In file included from /usr/src/sys/cam/cam_ccb.h:1035: >> In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: >> In file included from /usr/src/sys/dev/mmc/bridge.h:59: >> /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not found >> #include "device_if.h" >> ^~~~~~~~~~~~~ >> > > I think this was fixed in a newer -current. > > Warner > Thanks Warner, but I have the same error in : # uname -a FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 # MAKE_JOBS_UNSAFE=yes make ===> License BSD2CLAUSE accepted by the user ===> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for building ===> Extracting for isboot-kmod-0.2.13_1 => SHA256 Checksum OK for isboot-0.2.13.tar.gz. ===> Patching for isboot-kmod-0.2.13_1 ===> Applying FreeBSD patches for isboot-kmod-0.2.13_1 ===> Configuring for isboot-kmod-0.2.13_1 ===> Building for isboot-kmod-0.2.13_1 machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include :> opt_cam.h Warning: Object directory not changed from original /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depend.isboot.o -MTisboot.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c isboot.c -o isboot.o cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depend.ibft.o -MTibft.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c ibft.c -o ibft.o cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depend.iscsi.o -MTiscsi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c iscsi.c -o iscsi.o In file included from iscsi.c:62: In file included from /usr/src/sys/cam/cam_ccb.h:1035: In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: In file included from /usr/src/sys/dev/mmc/bridge.h:59: /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^~~~~~~~~~~~~ 1 error generated. *** Error code 1 Stop. make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src *** Error code 1 Stop. make[1]: stopped in /usr/ports/net/isboot-kmod *** Error code 1 Stop. make: stopped in /usr/ports/net/isboot-kmod -- Maurizio From owner-freebsd-current@freebsd.org Fri Jan 26 12:29:57 2018 Return-Path: Delivered-To: freebsd-current@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 A5E13ED4453 for ; Fri, 26 Jan 2018 12:29:57 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2927130C for ; Fri, 26 Jan 2018 12:29:57 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id DA63CED4452; Fri, 26 Jan 2018 12:29:56 +0000 (UTC) Delivered-To: current@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 B6A15ED4451 for ; Fri, 26 Jan 2018 12:29:56 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 08DB97130B for ; Fri, 26 Jan 2018 12:29:55 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w0QCTlkj072373 for ; Fri, 26 Jan 2018 12:29:47 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w0QCTlZU072372 for current@freebsd.org; Fri, 26 Jan 2018 04:29:47 -0800 (PST) (envelope-from david) Date: Fri, 26 Jan 2018 04:29:47 -0800 From: David Wolfskill To: current@freebsd.org Subject: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242" Message-ID: <20180126122947.GA1287@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7ULH7gtHJxM9ukDW" Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 12:29:57 -0000 --7ULH7gtHJxM9ukDW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is on my "build machine" (laptop is still building updated ports for today, so I don't know yet whether or not it encounters this.)=20 I had performed a source-based update from r328393 to r328436, rebooted, performed "make delete-old-libs", and all seemed well. I then issued "sudo shutdown -p now", and serial console shows: FreeBSD/amd64 (freebeast.catwhisker.org) (ttyu0) login: Jan 26 12:11:03 Stopping sshd. Waiting for PIDS: 681. Stopping rsyncd. Waiting for PIDS: 652. Stopping powerd. Waiting for PIDS: 636. Stopping ntpd. Waiting for PIDS: 633, 633. Stopping lpd. Waiting for PIDS: 610. Stopping lockd. WaitingWARNING: autofs_unmount: vflush failed with error 16 for PIDS: 592. Stopping statd. Waiting for PIDS: 589. Stopping nfsd. WaitinlJan 26 12:11:05 ock ordefreebeast syslogr reversal: 1st 0xfffff800692cd490 filed: exiting on sidesc structure (filedesc struct= ure) @ /usr/src/sys/kern/sys_generic.c:1567 2nd 0xfffff8006973f9a0 devfs (devfs) @ /usr/src/gnal 15 sys/kern/vfs_vnops.c:1526 stack backtrace: #0 0xffffffff80b2c2e3 at witness_debugger+0x73 #1 0xffffffff80b2c164 at witness_checkorder+0xe34 #2 0xffffffff80a9ca21 at lockmgr_lock_fast_path+0x1b1 #3 0xffffffff810f8ca9 at VOP_LOCK1_APV+0xd9 #4 0xffffffff80ba7746 at _vn_lock+0x66 #5 0xffffffff80ba654b at vn_poll+0x3b #6 0xffffffff80992f4d at devfs_poll_f+0xcd #7 0xffffffff80b33255 at kern_poll+0x385 #8 0xffffffff80b32ec0 at sys_poll+0x50 #9 0xffffffff80f7a37b at amd64_syscall+0x79b #10 0xffffffff80f569c8 at fast_syscall_common+0xfc 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 Syncing disks, vnodes remaining... 5 5 lock order reversal: 1st 0xfffff80007927240 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2157 2nd 0xfffff80007570d50 devfs (devfs) @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1= 583 stack backtrace: #0 0xffffffff80b2c2e3 at witness_debugger+0x73 #1 0xffffffff80b2c164 at witness_checkorder+0xe34 #2 0xffffffff80a9ca21 at lockmgr_lock_fast_path+0x1b1 #3 0xffffffff810f8ca9 at VOP_LOCK1_APV+0xd9 #4 0xffffffff80ba7746 at _vn_lock+0x66 #5 0xffffffff80dc1dac at ffs_sync+0x2cc #6 0xffffffff80b9ce8f at sync_fsync+0xff #7 0xffffffff810f7c19 at VOP_FSYNC_APV+0xd9 #8 0xffffffff80b9acc4 at sched_sync+0x284 #9 0xffffffff80a88414 at fork_exit+0x84 #10 0xffffffff80f56e1e at fork_trampoline+0xe 5 3 2 2 1 1 1 1 1 0 0 0 0 0 done All buffers synced. lock order reversal: 1st 0xfffff800079c57c8 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1280 2nd 0xfffff8000795e418 devfs (devfs) @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1= 371 stack backtrace: #0 0xffffffff80b2c2e3 at witness_debugger+0x73 #1 0xffffffff80b2c164 at witness_checkorder+0xe34 #2 0xffffffff80a9ca21 at lockmgr_lock_fast_path+0x1b1 #3 0xffffffff810f8ca9 at VOP_LOCK1_APV+0xd9 #4 0xffffffff80ba7746 at _vn_lock+0x66 #5 0xffffffff80dbef63 at ffs_flushfiles+0x93 #6 0xffffffff80da24f2 at softdep_flushfiles+0x82 #7 0xffffffff80dc15f7 at ffs_unmount+0x77 #8 0xffffffff80b8e2c9 at dounmount+0x519 #9 0xffffffff80b9800b at vfs_unmountall+0x6b #10 0xffffffff80b73d25 at bufshutdown+0x3a5 #11 0xffffffff80ac754a at kern_reboot+0x1da #12 0xffffffff80ac7312 at sys_reboot+0x3c2 #13 0xffffffff80f7a37b at amd64_syscall+0x79b #14 0xffffffff80f569c8 at fast_syscall_common+0xfc Swap device [file] removed. Uptime: 1m44s (ada0:ahcich0:0:0:0): spin-down (ada1:ahcich2:0:0:0): spin-down (ada2:ahcich3:0:0:0): spin-down (ada3:ahcich4:0:0:0): spin-down panic: Unholding 6 with cnt =3D -559038242 cpuid =3D 3 time =3D 1516968697 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0000428= 8c0 vpanic() at vpanic+0x18d/frame 0xfffffe0000428920 panic() at panic+0x43/frame 0xfffffe0000428980 dadiskgonecb() at dadiskgonecb+0x42/frame 0xfffffe00004289a0 g_disk_providergone() at g_disk_providergone+0x25/frame 0xfffffe00004289d0 g_destroy_provider() at g_destroy_provider+0xae/frame 0xfffffe00004289f0 g_wither_washer() at g_wither_washer+0x87/frame 0xfffffe0000428a30 g_run_events() at g_run_events+0x3ca/frame 0xfffffe0000428a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- KDB: enter: panic [ thread pid 13 tid 100044 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db>=20 As noted, this is a build machine, and it was to be powered off for the rest of the day anyway, so I don't need to get it up & running immediately: I can poke at the ddb prompt, given some clues. When running head, the system does not use ZFS (only UFS2+SU -- not SUJ -- & tmpfs). Same system had completed a source-based update for stable/11 from r328392 to r328429 earlier today without incident (using a different slice of the boot drive). Peace, david --=20 David H. Wolfskill david@catwhisker.org "unfortunately, no trust!=E2=80=9D -- well, of course! You reap what you s= ow. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --7ULH7gtHJxM9ukDW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlprHztfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfl0QgAkIRYZ8zKVQUwM80iXVpTV8FeAj6Y24EHtEEolm8IaAfrYEAqklibp84X izxlp9raYgLNZuPKBqFBgQFVCkiZMypGfOOzVfDuetkYHXhxzJg6SVmJW8hc3gvg Cj1IqcsbPEucmfBZJmmF6juDVsPw0zEQkLeVCp58PKmZ8W/ziy3GLOwfYZakqkCn 0zIxJZL/FwNESDVl532qVDlc9k8yQ0RbajnIlMAHsvHY0b5ROI5TJgBSeokj0QXi swr3wc05Gb35XTEG7UxzSGD/FvUainNL0opTFN649o7xickDFeO9XijzAYDzyJjr IzBAmfbeHPw/MhiQr7Z852e1qyDhLA== =4NS6 -----END PGP SIGNATURE----- --7ULH7gtHJxM9ukDW-- From owner-freebsd-current@freebsd.org Fri Jan 26 13:24:01 2018 Return-Path: Delivered-To: freebsd-current@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 B9663ED6A53 for ; Fri, 26 Jan 2018 13:24:01 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CF5772E35 for ; Fri, 26 Jan 2018 13:24:01 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1516973039; bh=E9cJttGQQjdOEW/FtpqZ/xSJe0KPM17ktYUplu9 ljBs=; b=mHGd1pD9TTqIUjFV2VBr7jDVeH1XxP9YrCa2dEBb9/duWvUwo6eX4NY /ToRJhC1Nad+k9dOiGLSVIfhf2gjZloHXTmuz8GhOxWHEk0+OCvQVpiWiNZFLe8O +ZwWXy3nSrdNeiE5uxhMCiLIsHvAyV+WpLIdCAzBOpfc8mxO/fpE= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id C11BE29BBC for ; Fri, 26 Jan 2018 08:23:59 -0500 (EST) To: FreeBSD Current From: Michael Butler Subject: dump drops core :-( Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492; url=0442D492 Message-ID: Date: Fri, 26 Jan 2018 08:23:58 -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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 13:24:01 -0000 This has been happening for a couple of weeks now .. DUMP: Date of this level 2 dump: Fri Jan 26 08:11:22 2018 DUMP: Date of last level 1 dump: Tue Jan 23 00:10:24 2018 DUMP: Dumping snapshot of /dev/ada0s3a (/) to standard output DUMP: mapping (Pass I) [regular files] DUMP: Cache 32 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 8222982 tape blocks. DUMP: SIGSEGV: ABORTING! DUMP: DUMP: SIGSEGV: ABORTING! SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! DUMP: Segmentation fault SIGSEGV: ABORTING! GDB output doesn't appear to be helpful :-( Reading symbols from /sbin/dump...(no debugging symbols found)...done. [New LWP 100539] Core was generated by `/sbin/dump 2Lauf - -C 32 /'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000080079eb98 in _wait4 () from /lib/libc.so.7 (gdb) bt #0 0x000000080079eb98 in _wait4 () from /lib/libc.so.7 #1 0x0000000000406f73 in ?? () #2 0x0000000000403e99 in ?? () #3 0x0000000000402674 in ?? () #4 0x0000000800633000 in ?? () #5 0x0000000000000000 in ?? () (gdb) How to proceed? imb From owner-freebsd-current@freebsd.org Fri Jan 26 14:07:12 2018 Return-Path: Delivered-To: freebsd-current@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 C2598ED8540 for ; Fri, 26 Jan 2018 14:07:11 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5C87B7439F for ; Fri, 26 Jan 2018 14:07:11 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 14117ED853E; Fri, 26 Jan 2018 14:07:11 +0000 (UTC) Delivered-To: current@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 01517ED853D for ; Fri, 26 Jan 2018 14:07:11 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 4463A7439E for ; Fri, 26 Jan 2018 14:07:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w0QE7834074770 for ; Fri, 26 Jan 2018 14:07:08 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w0QE78wi074769 for current@freebsd.org; Fri, 26 Jan 2018 06:07:08 -0800 (PST) (envelope-from david) Date: Fri, 26 Jan 2018 06:07:08 -0800 From: David Wolfskill To: current@freebsd.org Subject: Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242" Message-ID: <20180126140708.GT1287@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org References: <20180126122947.GA1287@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vw/GEePxV8pVp8Qw" Content-Disposition: inline In-Reply-To: <20180126122947.GA1287@albert.catwhisker.org> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 14:07:12 -0000 --vw/GEePxV8pVp8Qw Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 26, 2018 at 04:29:47AM -0800, David Wolfskill wrote: > This is on my "build machine" (laptop is still building updated ports > for today, so I don't know yet whether or not it encounters this.)=20 > .... The laptop did the same source-based update, and did not exhibit the panic. (On the laptop) following the "make delete-old-libs", I did a normal "shutdown -r now" (as I normally continue using the laptop throughout the day); when it started to boot, I coerced it to boot head again, then logged in an ran "poweroff" -- to which it complied without issue. The build machine went from FreeBSD 12.0-CURRENT #83 r328393M/328393:1200056: Thu Jan 25 04:37:47 PST = 2018 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/s= ys/GENERIC amd64 to FreeBSD 12.0-CURRENT #84 r328436M/328436:1200056: Fri Jan 26 04:02:06 PST = 2018 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/s= ys/GENERIC amd64 The laptop went from FreeBSD 12.0-CURRENT #80 r328393M/328393:1200056: Thu Jan 25 04:56:41 PST = 2018 root@g1-252.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/= CANARY amd64 to FreeBSD 12.0-CURRENT #81 r328436M/328436:1200056: Fri Jan 26 05:41:19 PST = 2018 root@g1-252.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/= CANARY amd64 Peace, david --=20 David H. Wolfskill david@catwhisker.org "unfortunately, no trust!=E2=80=9D -- well, of course! You reap what you s= ow. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --vw/GEePxV8pVp8Qw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlprNgtfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7he4TAgAiZEg9Vs9p9+V3dN3pj/gF83T23HT87O/rNYLOFawvApA8zhKKwrX5L5u Nlf62G7NgYWymWZBaBvgXu8+BKN0NoYwP9MfR5/6q58s2XR3+0fY8kT8GwoOJca/ XDJVeUabx4Algka48Yj3iPnoxc4rEgjeLk4L6tw7SCnIQYDv1nLwK1oSAzLq4I0t RFlZiHmtndH1VyrYm5QL7m7Um9FYXvgqFjnIT2PB04bwsF6MmjSIwTGqkSgPfjA+ 78j3Vwr+A7omuXBtFoLmWI8jkTxHV3AIuov5D3U18qZmlMYiIMllke/PTJTfpu7D 4OhbGlAlW1PrOtkyzU0gdPHFAM4wUw== =rB8p -----END PGP SIGNATURE----- --vw/GEePxV8pVp8Qw-- From owner-freebsd-current@freebsd.org Fri Jan 26 14:09:48 2018 Return-Path: Delivered-To: freebsd-current@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 0930AED8734 for ; Fri, 26 Jan 2018 14:09:48 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 574DE744E6 for ; Fri, 26 Jan 2018 14:09:46 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0QE9hR2085651; Fri, 26 Jan 2018 23:09:43 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801261409.w0QE9hR2085651@kx.openedu.org> Date: Fri, 26 Jan 2018 23:09:43 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current Cc: kiri@kx.openedu.org Subject: Re: microSDXC can't recognized In-Reply-To: <201801260731.w0Q7V842079870@kx.openedu.org> References: <201801260731.w0Q7V842079870@kx.openedu.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-2022-JP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 14:09:48 -0000 At Fri, 26 Jan 2018 16:31:08 +0900, $B;d(B wrote: > > Hi, > > Builtin microSDXC card device can't recognized in may > machine[1]. Inserted it but nothing happened. Inserted card > is SanDisk SDSQAR-128G-GNMA[2]. But in may another machine, > it recognized da0: > > root@kazu:~ # uname -v > FreeBSD 9.2-STABLE #5 r259404M: Mon Dec 16 00:12:52 JST 2013 admin@kazu.pis:/usr/obj/usr/src/sys/GENERIC > root@kazu:~ # dmesg | tail -10 > ugen4.3: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x4001 > umass0:1:0:-1: Attached to scbus1 > da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: Serial Number 058F63666433 > da0: 40.000MB/s transfers > da0: 121942MB (249737216 512 byte sectors: 255H 63S/T 15545C) > da0: quirks=0x2 > root@kazu:~ # > > My machine in question is r328126 and it's dmesg is [3]. The > cause is either my SD card adaptor phisically collapsed or > r328126 does not work. BTW I've added pciconf: I've rebooted and then recognized by mmcsd1! dmesg shows: mmcsd1: 128GB at mmc1 50.0MHz/4bit/65535-block WARNING: WITNESS option enabled, expect reduced performance. and gpart shows: root@t:~ # gpart show /dev/mmcsd1 => 34 249737149 mmcsd1 GPT (119G) 34 249737149 1 freebsd-ufs (119G) I can mount with /dev/mmcsd1p1 and could be accessed with UFS :-) root@t:~ # mount /dev/mmcsd1p1 /mnt root@t:~ # df -h Filesystem Size Used Avail Capacity Mounted on /dev/mmcsd0p2 53G 11G 38G 23% / devfs 1.0K 1.0K 0B 100% /dev linprocfs 4.0K 4.0K 0B 100% /compat/linux/proc tmpfs 6.5G 4.0K 6.5G 0% /compat/linux/dev/shm /dev/mmcsd1p1 115G 8.0K 106G 0% /mnt root@t:~ # I supposed SD card to be a pnp device but this embedded micro sd port seems to be eMMC device. Actually it is teated same as internal eMMC device as HDD. That is micro SD card must not be pull out by umount on running isn't it? Regards. > > root@t:~ # pciconf -lv > hostb0@pci0:0:0:0: class=0x060000 card=0x72708086 chip=0x22808086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register' > class = bridge > subclass = HOST-PCI > vgapci0@pci0:0:2:0: class=0x030000 card=0x72708086 chip=0x22b08086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers' > class = display > subclass = VGA > none0@pci0:0:3:0: class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit' > class = multimedia > none1@pci0:0:11:0: class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller' > class = dasp > xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller' > class = serial bus > subclass = USB > none2@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' > class = encrypt/decrypt > isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU' > class = bridge > subclass = PCI-ISA > root@t:~ # > > Best regards. > > [1] https://www.biccamera.com/bc/item/3716011/ > [2] http://kakaku.com/item/K0001002985/ > [3] http://ds.truefc.org/~kiri/freebsd/sg116j/dmesg.boot > > --- > KIRIYAMA Kazuhiko > --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Fri Jan 26 14:10:57 2018 Return-Path: Delivered-To: freebsd-current@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 E4052ED87EE for ; Fri, 26 Jan 2018 14:10:56 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 84FEC74611 for ; Fri, 26 Jan 2018 14:10:56 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1516975848; bh=03/zoJXZ Xpeg8CFZkebebza57vmwJAlLHy7FRPDG8f4=; b=EHF2KCaPMk6wNtV6phHzx9Fn rhIN1aEeH58WSmrZ+BN8iXSHOZJMcdIjg3kDYNVkT4EcfV1E/159UxtIpizAzzuY blI4OrmX/I0Lv2MD7bGVmw7DJQT3jpLtxnkF/DTe16t5ibOET8Y6kflRFRZcDjGM uTBy3fx6BzCMOMwuPkU= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id B3B072B868 for ; Fri, 26 Jan 2018 09:10:48 -0500 (EST) Subject: Re: dump drops core :-( To: freebsd-current@freebsd.org References: From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492; url=0442D492 Message-ID: Date: Fri, 26 Jan 2018 09:10:48 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 14:10:57 -0000 On 01/26/18 08:23, Michael Butler wrote: > This has been happening for a couple of weeks now .. > > DUMP: Date of this level 2 dump: Fri Jan 26 08:11:22 2018 > DUMP: Date of last level 1 dump: Tue Jan 23 00:10:24 2018 > DUMP: Dumping snapshot of /dev/ada0s3a (/) to standard output > DUMP: mapping (Pass I) [regular files] > DUMP: Cache 32 MB, blocksize = 65536 > DUMP: mapping (Pass II) [directories] > DUMP: estimated 8222982 tape blocks. > DUMP: SIGSEGV: ABORTING! > DUMP: DUMP: SIGSEGV: ABORTING! > SIGSEGV: ABORTING! > DUMP: SIGSEGV: ABORTING! > DUMP: Segmentation fault > SIGSEGV: ABORTING! I should have mentioned that this is UFS + SU and a forced 'fsck -y /' reported no inconsistencies, imb From owner-freebsd-current@freebsd.org Fri Jan 26 14:17:55 2018 Return-Path: Delivered-To: freebsd-current@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 740E2ED8E69 for ; Fri, 26 Jan 2018 14:17:55 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 D7A7C74C7B for ; Fri, 26 Jan 2018 14:17:54 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w0QDSEum077296; Fri, 26 Jan 2018 22:28:14 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 26 Jan 2018 22:28:13 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: sgk@troutmask.apl.washington.edu Subject: Re: kldxref: ...: Bad address. Message-Id: <20180126222813.a7f446eb253e8b4fc14c3b81@dec.sakura.ne.jp> In-Reply-To: <20180126010411.GA59487@troutmask.apl.washington.edu> References: <20180126010411.GA59487@troutmask.apl.washington.edu> Organization: Junchoon corps X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 14:17:55 -0000 Hi. Try `make install` in /usr/src/usr.sbin/kldxref BEFORE `make installkernel`. (Backup kldxref for safety.) I had kldxref problem a while ago and it helped. Possibly running /usr/obj/usr/src/usr.sbin/kldxref/(amd64.amd64/)kldxref /boot/kernel after installkernel can do the last job correctly. *Maybe old (currently installed) kldxref was used and it cannot handle new kernel and modules. *Some point AFTER r328071 broke installkernel but not bi-sected. Last non-style update for kldxref was r328052 ATM, but I've built world at r328071 with -DNO_CLEAN at the rev, so not shure kldxref was on the safe state. The finally-successful build was at r328163, with kldxref installed before installkernel. If it also helps for you, kldxref should be considered as toolchain (kernel-toolchain?) and forcibly used for installkernel. *If (kernel-)toolchains are used for build* only, new target would be needed. On Thu, 25 Jan 2018 17:04:11 -0800 Steve Kargl wrote: > This can't be good. > > make buildworld > make buildkernel > make installkernel > ... > ===> zlib (install) > install -T release -o root -g wheel -m 555 zlib.ko /boot/kernel/ > install -T debug -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug/boot/kernel/ > kldxref /boot/kernel > kldxref: error while reading /boot/kernel/accf_data.ko: Bad address > kldxref: error while reading /boot/kernel/amr_linux.ko: Bad address > kldxref: error while reading /boot/kernel/chacha20.ko: Bad address > kldxref: error while reading /boot/kernel/cxgb_t3fw.ko: Bad address > kldxref: error while reading /boot/kernel/if_cc.ko: Bad address > kldxref: error while reading /boot/kernel/if_ccv.ko: Bad address > kldxref: error while reading /boot/kernel/if_cxl.ko: Bad address > kldxref: error while reading /boot/kernel/if_cxlv.ko: Bad address > kldxref: error while reading /boot/kernel/ipmi_linux.ko: Bad address > kldxref: error while reading /boot/kernel/nfslock.ko: Bad address > kldxref: error while reading /boot/kernel/nfssvc.ko: Bad address > kldxref: error while reading /boot/kernel/ng_nat.ko: Bad address > kldxref: error while reading /boot/kernel/pflog.ko: Bad address > kldxref: error while reading /boot/kernel/plip.ko: Bad address > kldxref: error while reading /boot/kernel/pty.ko: Bad address > kldxref: error while reading /boot/kernel/rc4.ko: Bad address > kldxref: error while reading /boot/kernel/rdrand_rng.ko: Bad address > kldxref: error while reading /boot/kernel/udf_iconv.ko: Bad address > > -- > Steve > 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 > 20161221 https://www.youtube.com/watch?v=IbCHE-hONow > _______________________________________________ > 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" > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Fri Jan 26 14:47:52 2018 Return-Path: Delivered-To: freebsd-current@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 C0A63EDA0A6 for ; Fri, 26 Jan 2018 14:47:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 41CE1762EB for ; Fri, 26 Jan 2018 14:47:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id F3EDDEDA0A3; Fri, 26 Jan 2018 14:47:50 +0000 (UTC) Delivered-To: current@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 B70DAEDA0A2 for ; Fri, 26 Jan 2018 14:47:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (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 52E29762E9 for ; Fri, 26 Jan 2018 14:47:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x243.google.com with SMTP id m11so24507664iti.1 for ; Fri, 26 Jan 2018 06:47:50 -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; bh=YqvseDz4JKHmVlfsQuAg52nQA5QXbwVv+wh+QeJiWD0=; b=0KaOkyk6P5xGPrXrWB5Rf+iSmZ8/i/87khGEKy9jmoGuiwSBj6DP+cWxTkIwJc79zc 5IgO9AF1ELFV91HvMUwqbM8bVhTp+gpJ7GLx58lIWr6M6JmwinpkX+HMR2xhBZeAE2MP iQ9sDLasvrvZvqvYA7JqBeIR/JhiSu6PHJTL+R9lFLKzyBejGDEm6jHNlgUkq6UpKxsB qdrlLdu37lhhT7R4RZjZkQeyXmgXl/66Y4YwhKLc9Cn0Zp0uI/9jNd4Dzwqj40ZFSVHM P46x+roQyzalpDLORwKFen/SjE8fyGwlkLBsTJFdTDOUSmKRhKFdxjtuLKORAn8uR8fo V3tQ== 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; bh=YqvseDz4JKHmVlfsQuAg52nQA5QXbwVv+wh+QeJiWD0=; b=SYiE0AYymb/N19FwAi8oCiyE8SbPDL/2MKurCEGR5n71nCppqu58BayHzZROuCxNPv x/6qyR4synmx7VPN2f48/28ARt7XjG3czWGfuzKYpdq9aPCOeXqBjO9kcS+HbXAn93VW tV7xMyhscQxbgabk74GTszsFIvOWB90UJnLyIKgPJQcPMqAZFyQABNbT8iamHA6MGZub Kq4S0iBSm+aW3BWc01sz2dcBTqBLesI2Vx2lnqIely45vAotD57C0OveB5GMX0KJfRcB U1b+B52yLLiNp62F3GTkzqucNLddwceFLCVmQNyLBzTfaUk4J4Tn1m2/gB5imPlU7JXW 1azg== X-Gm-Message-State: AKwxytfbq+oyQugiZFk9ZSxFWyIIk/uQZg9cS1YsP5itBdCQGHVjPqLJ 1hqnQ4q5Y7D/dfQ3Po49BFVTu2UfHWg+xGrrcw5+WdZC X-Google-Smtp-Source: AH8x225fnFS3sGxzPPo5+WxSVFNEwI0uJFxfBnM1cNRyali4tzosUCZ2/dvKwZCm+c8pNpqUZDjXQHq7YCYzsca5tgI= X-Received: by 10.36.146.196 with SMTP id l187mr17574746itd.115.1516978069227; Fri, 26 Jan 2018 06:47:49 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Fri, 26 Jan 2018 06:47:48 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <20180126122947.GA1287@albert.catwhisker.org> References: <20180126122947.GA1287@albert.catwhisker.org> From: Warner Losh Date: Fri, 26 Jan 2018 07:47:48 -0700 X-Google-Sender-Auth: 9zCTlsyPt9iSsVegTdpCGJqwymI Message-ID: Subject: Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242" To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 14:47:52 -0000 On Fri, Jan 26, 2018 at 5:29 AM, David Wolfskill wrote: > This is on my "build machine" (laptop is still building updated ports > for today, so I don't know yet whether or not it encounters this.) > Running a kernel with INVARIANTS, right? > I had performed a source-based update from r328393 to r328436, > rebooted, performed "make delete-old-libs", and all seemed well. > This has my change 328415 in it. > I then issued "sudo shutdown -p now", and serial console shows: > panic: Unholding 6 with cnt = -559038242 > cpuid = 3 > time = 1516968697 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00004288c0 > vpanic() at vpanic+0x18d/frame 0xfffffe0000428920 > panic() at panic+0x43/frame 0xfffffe0000428980 > dadiskgonecb() at dadiskgonecb+0x42/frame 0xfffffe00004289a0 > g_disk_providergone() at g_disk_providergone+0x25/frame 0xfffffe00004289d0 > g_destroy_provider() at g_destroy_provider+0xae/frame 0xfffffe00004289f0 > g_wither_washer() at g_wither_washer+0x87/frame 0xfffffe0000428a30 > g_run_events() at g_run_events+0x3ca/frame 0xfffffe0000428a70 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 13 tid 100044 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> > That's no good. We're releasing a reference to the da peripheral because geom has finished with the disk and is giving us a final callback so we can drop the reference we took when we created the geom. Trouble is, cnt should be like 1 always for this code, but it's not. It looks like it may be bytes to a pointer :( > As noted, this is a build machine, and it was to be powered off for > the rest of the day anyway, so I don't need to get it up & running > immediately: I can poke at the ddb prompt, given some clues. > I don't suppose you can attach kgdb to this machine? I'd be interested to see what the contents of the softc are...a > Same system had completed a source-based update for stable/11 from > r328392 to r328429 earlier today without incident (using a different > slice of the boot drive). > Thanks for the report. This is quite troubling. Warner From owner-freebsd-current@freebsd.org Fri Jan 26 15:07:15 2018 Return-Path: Delivered-To: freebsd-current@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 22415EDB05C for ; Fri, 26 Jan 2018 15:07:15 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B041977051 for ; Fri, 26 Jan 2018 15:07:14 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 67D64EDB05B; Fri, 26 Jan 2018 15:07:14 +0000 (UTC) Delivered-To: current@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 431EFEDB05A for ; Fri, 26 Jan 2018 15:07:14 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 A95AA77050 for ; Fri, 26 Jan 2018 15:07:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w0QF7Adx075742; Fri, 26 Jan 2018 15:07:10 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w0QF7AN6075741; Fri, 26 Jan 2018 07:07:10 -0800 (PST) (envelope-from david) Date: Fri, 26 Jan 2018 07:07:10 -0800 From: David Wolfskill To: Warner Losh Cc: FreeBSD Current Subject: Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242" Message-ID: <20180126150710.GV1287@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Warner Losh References: <20180126122947.GA1287@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LJa15rN3LQ9Y2Ulo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 15:07:15 -0000 --LJa15rN3LQ9Y2Ulo Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 26, 2018 at 07:47:48AM -0700, Warner Losh wrote: > On Fri, Jan 26, 2018 at 5:29 AM, David Wolfskill > wrote: >=20 > > This is on my "build machine" (laptop is still building updated ports > > for today, so I don't know yet whether or not it encounters this.) > > >=20 > Running a kernel with INVARIANTS, right? Yes -- GENERIC. > > I had performed a source-based update from r328393 to r328436, > > rebooted, performed "make delete-old-libs", and all seemed well. > > >=20 > This has my change 328415 in it. :-) > > I then issued "sudo shutdown -p now", and serial console shows: > > panic: Unholding 6 with cnt =3D -559038242 > > cpuid =3D 3 > > time =3D 1516968697 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe00004288c0 > > vpanic() at vpanic+0x18d/frame 0xfffffe0000428920 > > panic() at panic+0x43/frame 0xfffffe0000428980 > > dadiskgonecb() at dadiskgonecb+0x42/frame 0xfffffe00004289a0 > > g_disk_providergone() at g_disk_providergone+0x25/frame 0xfffffe0000428= 9d0 > > g_destroy_provider() at g_destroy_provider+0xae/frame 0xfffffe00004289f0 > > g_wither_washer() at g_wither_washer+0x87/frame 0xfffffe0000428a30 > > g_run_events() at g_run_events+0x3ca/frame 0xfffffe0000428a70 > > fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 > > --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- > > KDB: enter: panic > > [ thread pid 13 tid 100044 ] > > Stopped at kdb_enter+0x3b: movq $0,kdb_why > > db> > > >=20 > That's no good. We're releasing a reference to the da peripheral because > geom has finished with the disk and is giving us a final callback so we c= an > drop the reference we took when we created the geom. Trouble is, cnt shou= ld > be like 1 always for this code, but it's not. It looks like it may be byt= es > to a pointer :( >=20 >=20 > > As noted, this is a build machine, and it was to be powered off for > > the rest of the day anyway, so I don't need to get it up & running > > immediately: I can poke at the ddb prompt, given some clues. > > >=20 > I don't suppose you can attach kgdb to this machine? I'd be interested to > see what the contents of the softc are...a Pointer to how to do that? I do have ddb right now.... > .... > Thanks for the report. This is quite troubling. Well, let's get it fixed, then! :-) > Warner > .... I should still have access to the serial console after I get in to the office (heading out shortly). Peace, david --=20 David H. Wolfskill david@catwhisker.org "unfortunately, no trust!=E2=80=9D -- well, of course! You reap what you s= ow. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --LJa15rN3LQ9Y2Ulo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlprRB1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfNdggAqYHLXjkXPcdnKW8jgNJz3GCXvzzq7Dn9RMcpvXZnyOYbI2Lz+suwNgDn sOvSzQfXkG2QvvLyGQxsueSAKW/OOo06/Xtd6lwkwikHuTR+swjymI5SQZcBHs+3 Th92uwfMKRB9SPbhbyF/kBw0P+EsBAMpq/jnsSF6p4aL5qfJT+G0d8t228O2l2fR KKsaWU7uz6T9b9Zcn0JWzgyzKyw87UHRX8bm6xalLT3OhrwVvnC4kBNegJrfBEbK nZlTXcsTR7Q2SlJ+UXjzGpr2nzmBbV9c2g8gRqc2Akfhm468PahjmNdjILVCEEG/ OvriPQ3pIZLDy4hDehz7zwttUCo4MA== =ualf -----END PGP SIGNATURE----- --LJa15rN3LQ9Y2Ulo-- From owner-freebsd-current@freebsd.org Fri Jan 26 15:25:55 2018 Return-Path: Delivered-To: freebsd-current@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 9DB7CEDBFCC for ; Fri, 26 Jan 2018 15:25:55 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 277C77802B for ; Fri, 26 Jan 2018 15:25:55 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w0QFPpsa047166 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 07:25:51 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w0QFPpPT047165; Fri, 26 Jan 2018 07:25:51 -0800 (PST) (envelope-from sgk) Date: Fri, 26 Jan 2018 07:25:51 -0800 From: Steve Kargl To: Tomoaki AOKI Cc: freebsd-current@freebsd.org Subject: Re: kldxref: ...: Bad address. Message-ID: <20180126152551.GA44359@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180126010411.GA59487@troutmask.apl.washington.edu> <20180126222813.a7f446eb253e8b4fc14c3b81@dec.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180126222813.a7f446eb253e8b4fc14c3b81@dec.sakura.ne.jp> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 15:25:55 -0000 On Fri, Jan 26, 2018 at 10:28:13PM +0900, Tomoaki AOKI wrote: > Hi. > Try `make install` in /usr/src/usr.sbin/kldxref BEFORE > `make installkernel`. (Backup kldxref for safety.) > Thanks! This at least allowed 'make installkernel' to finish cleanly. Now, outward to rebooting ... -- Steve From owner-freebsd-current@freebsd.org Fri Jan 26 16:20:33 2018 Return-Path: Delivered-To: freebsd-current@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 5257DEDE069 for ; Fri, 26 Jan 2018 16:20:33 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CB03A799F0 for ; Fri, 26 Jan 2018 16:20:32 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w0QGKT8Y001212 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 08:20:29 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w0QGKTNQ001211; Fri, 26 Jan 2018 08:20:29 -0800 (PST) (envelope-from sgk) Date: Fri, 26 Jan 2018 08:20:29 -0800 From: Steve Kargl To: Tomoaki AOKI Cc: freebsd-current@freebsd.org Subject: Re: kldxref: ...: Bad address. Message-ID: <20180126162029.GA1199@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180126010411.GA59487@troutmask.apl.washington.edu> <20180126222813.a7f446eb253e8b4fc14c3b81@dec.sakura.ne.jp> <20180126152551.GA44359@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180126152551.GA44359@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 16:20:33 -0000 On Fri, Jan 26, 2018 at 07:25:51AM -0800, Steve Kargl wrote: > On Fri, Jan 26, 2018 at 10:28:13PM +0900, Tomoaki AOKI wrote: > > Hi. > > Try `make install` in /usr/src/usr.sbin/kldxref BEFORE > > `make installkernel`. (Backup kldxref for safety.) > > > > Thanks! This at least allowed 'make installkernel' to > finish cleanly. Now, outward to rebooting ... > To close the loop, I was able to reboot and complete the upgrade. -- Steve From owner-freebsd-current@freebsd.org Fri Jan 26 16:42:16 2018 Return-Path: Delivered-To: freebsd-current@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 5C8ECEDEE46 for ; Fri, 26 Jan 2018 16:42:16 +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 D88B97A752 for ; Fri, 26 Jan 2018 16:42:15 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d70fa45d-02b7-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id d70fa45d-02b7-11e8-b951-f99fef315fd9; Fri, 26 Jan 2018 16:42:04 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0QGg7D6013961; Fri, 26 Jan 2018 09:42:07 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516984927.42536.248.camel@freebsd.org> Subject: Re: microSDXC can't recognized From: Ian Lepore To: KIRIYAMA Kazuhiko , freebsd-current Date: Fri, 26 Jan 2018 09:42:07 -0700 In-Reply-To: <201801261409.w0QE9hR2085651@kx.openedu.org> References: <201801260731.w0Q7V842079870@kx.openedu.org> <201801261409.w0QE9hR2085651@kx.openedu.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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 16:42:16 -0000 On Fri, 2018-01-26 at 23:09 +0900, KIRIYAMA Kazuhiko wrote: > At Fri, 26 Jan 2018 16:31:08 +0900, > $B;d(B wrote: > > > > > > Hi, > > > > Builtin microSDXC card device can't recognized in may > > machine[1]. Inserted it but nothing happened. Inserted card > > is SanDisk SDSQAR-128G-GNMA[2]. But in may another machine, > > it recognized da0: > > > > [...] > I've rebooted and then recognized by mmcsd1! dmesg shows: > > mmcsd1: 128GB at > mmc1 50.0MHz/4bit/65535-block > WARNING: WITNESS option enabled, expect reduced performance. > > [...] > > I supposed SD card to be a pnp device but this embedded > micro sd port seems to be eMMC device. Actually it is teated > same as internal eMMC device as HDD. That is micro SD card > must not be pull out by umount on running isn't it? You should be able to insert and remove the sdcard whenever you want, as long as it has no mounted filesystems. Every time you insert or remove it, you should see a notification on the console and in dmesg. If that doesn't happen, then somehow the card-detect logic isn't working right on your hardware. -- Ian From owner-freebsd-current@freebsd.org Fri Jan 26 17:00:34 2018 Return-Path: Delivered-To: freebsd-current@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 79C35EB6D72 for ; Fri, 26 Jan 2018 17:00:34 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail4.jnielsen.net (webmail4.jnielsen.net [IPv6:2607:f7a0:a:18c::c0de]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 194347AFFD for ; Fri, 26 Jan 2018 17:00:33 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [10.3.135.15] (50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162]) (authenticated bits=0) by webmail4.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w0QH0Rt7016546 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 10:00:29 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail4.jnielsen.net: Host 50-207-240-162-static.hfc.comcastbusiness.net [50.207.240.162] claimed to be [10.3.135.15] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Error compiling isboot-kmod From: John Nielsen In-Reply-To: Date: Fri, 26 Jan 2018 10:00:25 -0700 Cc: Warner Losh , Maurizio Vairani Content-Transfer-Encoding: quoted-printable Message-Id: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.net> References: To: freebsd-current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 17:00:34 -0000 > On Jan 26, 2018, at 3:37 AM, Maurizio Vairani = wrote: >=20 > 2018-01-24 17:19 GMT+01:00 Warner Losh : >=20 >=20 > On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani = wrote: > On this CURRENT snapshot > # uname -a > FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed = Jan 10 > 22:55:40 UTC 2018 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 >=20 > I can't compile the kernel module isboot-kmod: > # cd /usr/ports/net/isboot-kmod && make > =3D=3D=3D> License BSD2CLAUSE accepted by the > user >=20 > =3D=3D=3D> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg = - found > =3D=3D=3D> Fetching all distfiles required by isboot-kmod-0.2.13_1 for = building > =3D=3D=3D> Extracting for isboot-kmod-0.2.13_1 > =3D> SHA256 Checksum OK for isboot-0.2.13.tar.gz. > =3D=3D=3D> Patching for isboot-kmod-0.2.13_1 > =3D=3D=3D> Applying FreeBSD patches for isboot-kmod-0.2.13_1 > =3D=3D=3D> Configuring for isboot-kmod-0.2.13_1 > =3D=3D=3D> Building for isboot-kmod-0.2.13_1 > --- machine --- > --- x86 --- > --- machine --- > machine -> /usr/src/sys/amd64/include > --- x86 --- > x86 -> /usr/src/sys/x86/include > --- objwarn --- > --- opt_cam.h --- > --- objwarn --- > Warning: Object directory not changed from original > /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > --- opt_cam.h --- > :> opt_cam.h > --- isboot.o --- > --- ibft.o --- > --- isboot.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.isboot.o -MTisboot.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx = -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-dec$ > s -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=3D__freebsd_kprintf__ -Wmissing-include-dirs $ > fdiagnostics-show-option -Wno-unknown-pragmas > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -Wno-error-unused-function > -Wno-error-pointer-s$ > gn -Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=3Diso9899:1999 -c isboot.c -o isboot.o > --- ibft.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.ibft.o -MTibft.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-decls -$ > nested-externs -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=3D__freebsd_kprintf__ -Wmissing-include-dirs -fdi$ > gnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare > -Wno-error-empty-body -Wno-error-parentheses-equality > -Wno-error-unused-function -Wno-error-pointer-sign $ > Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=3Diso9899:1999 -c ibft.c -o ibft.o > --- iscsi.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -MD -MF.depe$ > d.iscsi.o -MTiscsi.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv > -fstack-protector -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=3D__freebsd_kprintf__ -Wmissing-include-dirs -f$ > iagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare > -Wno-error-empty-body -Wno-error-parentheses-equality > -Wno-error-unused-function -Wno-error-pointer-sig$ > -Wno-error-shift-negative-value -Wno-error-address-of-packed-member > -mno-aes -mno-avx -std=3Diso9899:1999 -c iscsi.c -o iscsi.o > In file included from iscsi.c:62: > In file included from /usr/src/sys/cam/cam_ccb.h:1035: > In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: > In file included from /usr/src/sys/dev/mmc/bridge.h:59: > /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not = found > #include "device_if.h" > ^~~~~~~~~~~~~ >=20 > I think this was fixed in a newer -current. >=20 > Warner=20 > Thanks Warner, but I have the same error in : > # uname -a > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 = 04:48:52 UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC = amd64 Whatever change broke it happened around the beginning of July 2017. I = started getting (and ignoring, sadly, due to lack of time and certainty = that anyone cared) messages with this error from pkg-fallout@ on July = 11. I'm looking through the revision history but nothing stands out to = me yet. Maybe someone with better svn-foo will find it faster. :) JN > # MAKE_JOBS_UNSAFE=3Dyes make=20 > =3D=3D=3D> License BSD2CLAUSE accepted by the user > =3D=3D=3D> isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg = - found > =3D=3D=3D> Fetching all distfiles required by isboot-kmod-0.2.13_1 for = building > =3D=3D=3D> Extracting for isboot-kmod-0.2.13_1 > =3D> SHA256 Checksum OK for isboot-0.2.13.tar.gz. > =3D=3D=3D> Patching for isboot-kmod-0.2.13_1 > =3D=3D=3D> Applying FreeBSD patches for isboot-kmod-0.2.13_1 > =3D=3D=3D> Configuring for isboot-kmod-0.2.13_1 > =3D=3D=3D> Building for isboot-kmod-0.2.13_1 > machine -> /usr/src/sys/amd64/include > x86 -> /usr/src/sys/x86/include > :> opt_cam.h > Warning: Object directory not changed from original = /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE = -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.isboot.o -MTisboot.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c isboot.c -o isboot.o > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE = -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.ibft.o -MTibft.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c ibft.c -o ibft.o > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE = -nostdinc -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.iscsi.o -MTiscsi.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c iscsi.c -o iscsi.o > In file included from iscsi.c:62: > In file included from /usr/src/sys/cam/cam_ccb.h:1035: > In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: > In file included from /usr/src/sys/dev/mmc/bridge.h:59: > /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not = found > #include "device_if.h" > ^~~~~~~~~~~~~ > 1 error generated. = = =20 > *** Error code 1 >=20 > Stop. > make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/ports/net/isboot-kmod > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/net/isboot-kmod > -- > Maurizio From owner-freebsd-current@freebsd.org Fri Jan 26 17:35:50 2018 Return-Path: Delivered-To: freebsd-current@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 D0921EB9B14 for ; Fri, 26 Jan 2018 17:35:49 +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 5AFA97CCD6 for ; Fri, 26 Jan 2018 17:35:48 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 5231a47b-02bf-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 5231a47b-02bf-11e8-91c6-33ffc249f3e8; Fri, 26 Jan 2018 17:35:38 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0QHZboe014056; Fri, 26 Jan 2018 10:35:37 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516988137.42536.255.camel@freebsd.org> Subject: Re: Error compiling isboot-kmod From: Ian Lepore To: John Nielsen , freebsd-current Cc: Warner Losh , Maurizio Vairani Date: Fri, 26 Jan 2018 10:35:37 -0700 In-Reply-To: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.net> References: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 17:35:50 -0000 On Fri, 2018-01-26 at 10:00 -0700, John Nielsen wrote: > > > > On Jan 26, 2018, at 3:37 AM, Maurizio Vairani > om> wrote: > > > > 2018-01-24 17:19 GMT+01:00 Warner Losh : > > > > > > On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani > il.com> wrote: > > On this CURRENT snapshot > > # uname -a > > FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed > > Jan 10 > > 22:55:40 UTC 2018 > > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENER > > IC > > amd64 > > > > I can't compile the kernel module isboot-kmod: > > # cd /usr/ports/net/isboot-kmod && make > > ===>  License BSD2CLAUSE accepted by the > > user > > > > ===>   isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - > > found > > ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for > > building > > ===>  Extracting for isboot-kmod-0.2.13_1 > > => SHA256 Checksum OK for isboot-0.2.13.tar.gz. > > ===>  Patching for isboot-kmod-0.2.13_1 > > ===>  Applying FreeBSD patches for isboot-kmod-0.2.13_1 > > ===>  Configuring for isboot-kmod-0.2.13_1 > > ===>  Building for isboot-kmod-0.2.13_1 > > --- machine --- > > --- x86 --- > > --- machine --- > > machine -> /usr/src/sys/amd64/include > > --- x86 --- > > x86 -> /usr/src/sys/x86/include > > --- objwarn --- > > --- opt_cam.h --- > > --- objwarn --- > > Warning: Object directory not changed from original > > /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > > --- opt_cam.h --- > > :> opt_cam.h > > --- isboot.o --- > > --- ibft.o --- > > --- isboot.o --- > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depe$ > > d.isboot.o -MTisboot.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno- > > sse > > -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding > > -fwrapv > > -fstack-protector -Wall -Wredundant-dec$ > > s -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs $ > > fdiagnostics-show-option -Wno-unknown-pragmas > > -Wno-error-tautological-compare -Wno-error-empty-body > > -Wno-error-parentheses-equality -Wno-error-unused-function > > -Wno-error-pointer-s$ > > gn -Wno-error-shift-negative-value -Wno-error-address-of-packed- > > member > > -mno-aes -mno-avx  -std=iso9899:1999 -c isboot.c -o isboot.o > > --- ibft.o --- > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depe$ > > d.ibft.o -MTibft.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > > -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding > > -fwrapv > > -fstack-protector -Wall -Wredundant-decls -$ > > nested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer- > > arith > > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdi$ > > gnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological- > > compare > > -Wno-error-empty-body -Wno-error-parentheses-equality > > -Wno-error-unused-function -Wno-error-pointer-sign $ > > Wno-error-shift-negative-value -Wno-error-address-of-packed-member > > -mno-aes -mno-avx  -std=iso9899:1999 -c ibft.c -o ibft.o > > --- iscsi.o --- > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depe$ > > d.iscsi.o -MTiscsi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno- > > sse > > -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding > > -fwrapv > > -fstack-protector -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -f$ > > iagnostics-show-option -Wno-unknown-pragmas -Wno-error- > > tautological-compare > > -Wno-error-empty-body -Wno-error-parentheses-equality > > -Wno-error-unused-function -Wno-error-pointer-sig$ > >  -Wno-error-shift-negative-value -Wno-error-address-of-packed- > > member > > -mno-aes -mno-avx  -std=iso9899:1999 -c iscsi.c -o iscsi.o > > In file included from iscsi.c:62: > > In file included from /usr/src/sys/cam/cam_ccb.h:1035: > > In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: > > In file included from /usr/src/sys/dev/mmc/bridge.h:59: > > /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not > > found > > #include "device_if.h" > >          ^~~~~~~~~~~~~ > > > > I think this was fixed in a newer -current. > > > > Warner  > > Thanks Warner, but I have the same error in : > > # uname -a > > FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 > > 04:48:52 UTC 2018     root@releng3.nyi.freebsd.org:/usr/obj/usr/src > > /amd64.amd64/sys/GENERIC  amd64 > Whatever change broke it happened around the beginning of July 2017. > I started getting (and ignoring, sadly, due to lack of time and > certainty that anyone cared) messages with this error from pkg- > fallout@ on July 11. I'm looking through the revision history but > nothing stands out to me yet. Maybe someone with better svn-foo will > find it faster. :) > > JN > > > > > # MAKE_JOBS_UNSAFE=yes make  > > ===>  License BSD2CLAUSE accepted by the user > > ===>   isboot-kmod-0.2.13_1 depends on file: /usr/local/sbin/pkg - > > found > > ===> Fetching all distfiles required by isboot-kmod-0.2.13_1 for > > building > > ===>  Extracting for isboot-kmod-0.2.13_1 > > => SHA256 Checksum OK for isboot-0.2.13.tar.gz. > > ===>  Patching for isboot-kmod-0.2.13_1 > > ===>  Applying FreeBSD patches for isboot-kmod-0.2.13_1 > > ===>  Configuring for isboot-kmod-0.2.13_1 > > ===>  Building for isboot-kmod-0.2.13_1 > > machine -> /usr/src/sys/amd64/include > > x86 -> /usr/src/sys/x86/include > > :> opt_cam.h > > Warning: Object directory not changed from original > > /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depend.isboot.o -MTisboot.o > > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno- > > asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector > > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > > -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing- > > include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno- > > error-tautological-compare -Wno-error-empty-body -Wno-error- > > parentheses-equality -Wno-error-unused-function -Wno-error-pointer- > > sign -Wno-error-shift-negative-value -Wno-error-address-of-packed- > > member  -mno-aes -mno-avx  -std=iso9899:1999 -c isboot.c -o > > isboot.o > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depend.ibft.o -MTibft.o > > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno- > > asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector > > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > > -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing- > > include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno- > > error-tautological-compare -Wno-error-empty-body -Wno-error- > > parentheses-equality -Wno-error-unused-function -Wno-error-pointer- > > sign -Wno-error-shift-negative-value -Wno-error-address-of-packed- > > member  -mno-aes -mno-avx  -std=iso9899:1999 -c ibft.c -o ibft.o > > cc  -O2 -pipe -fno-strict-aliasing  -Werror -D_KERNEL -DKLD_MODULE > > -nostdinc   -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer   -MD  -MF.depend.iscsi.o -MTiscsi.o > > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno- > > asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector > > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > > -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing- > > include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno- > > error-tautological-compare -Wno-error-empty-body -Wno-error- > > parentheses-equality -Wno-error-unused-function -Wno-error-pointer- > > sign -Wno-error-shift-negative-value -Wno-error-address-of-packed- > > member  -mno-aes -mno-avx  -std=iso9899:1999 -c iscsi.c -o iscsi.o > > In file included from iscsi.c:62: > > In file included from /usr/src/sys/cam/cam_ccb.h:1035: > > In file included from /usr/src/sys/cam/mmc/mmc_bus.h:5: > > In file included from /usr/src/sys/dev/mmc/bridge.h:59: > > /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not > > found > > #include "device_if.h" > >          ^~~~~~~~~~~~~ I've never looked into how kernel modules compile when built as a port, but when built as part of the system kernel build, the SRCS= in the module makefile needs to name all of the dynamically generated header files such as device_if.h (basically anything ending in _if.h used by the module needs to be in SRCS=). So adding device_if.h to SRCS may be all that's needed.  Or maybe that's incremental and you'll find that several others are needed as well. As for commits in the July timeframe that led to this, maybe r320844. -- Ian From owner-freebsd-current@freebsd.org Sat Jan 27 02:07:52 2018 Return-Path: Delivered-To: freebsd-current@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 49F9DED7882 for ; Sat, 27 Jan 2018 02:07:52 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D4BED70CB7 for ; Sat, 27 Jan 2018 02:07:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8EEE2ED787B; Sat, 27 Jan 2018 02:07:51 +0000 (UTC) Delivered-To: current@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 7C706ED7878 for ; Sat, 27 Jan 2018 02:07:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 0F36170CB5 for ; Sat, 27 Jan 2018 02:07:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x233.google.com with SMTP id q8so3739804itb.2 for ; Fri, 26 Jan 2018 18:07:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ItdssmlIdB2obolr13ToStxKBS8ZBq0mvqrT5PPLmps=; b=kGHCzg/w+9bWU37UjGb17s9ZjRr+ch3/hcz4Z4ma2MVdQS1+N+WdqzIBzCjmJq/fo4 q5EdZ3e6WirYSWb1KumoU0wV/MG8fYkGJRj8xbaT0DFrE9RYpjRhGyeSRRcvUlr/SPVL L93pGw0zIKO1CDb9hu7mU2QayTIZKelm3Lnt5h8aRiGSkNysKcO+CYayJmSanWevx4nJ TnuF1j70qqpFvEJGoOETVzd56jWElOBwI+m1LtLM5JNQW6KFlXNugjR8uECErhIR4OMu Ut/uiWTewYBse4hovo6gCOnnVi6jMr7Jhse0Qdbl+OwkDxekfeJk7NdcGnepkLtquLw5 ss4w== 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=ItdssmlIdB2obolr13ToStxKBS8ZBq0mvqrT5PPLmps=; b=NZZsbhvOD3MitPEIM2Q34ywDmcdXddPmO2PCLOFxQ9UAmjDH1Z3pq9JhFAvSbN8oqP ewWz6VxECxtUvM0Pp+QLOCqYL3dF+JJzXL65aFO3uvnK/36LdziqGGFmc16ei13noEw7 59lybt2cyNaXtICtQsY4R0npvK/vMUzMf0u237wahxeqlmG6Lzw6RqJIarmHHctUxp8B tJ4xrjUa78RnjxbSthp6YIjq/I/c7BA+l0b4dU/WLHgpFaVV5B1iFYCe0zZL0ugLEorH 2z032elNP+oJA8JQb6awu+k2rh43ehq6PWcllhnpyiKPmiTZesPOaoiEOh5xwk+DVlIW nEsw== X-Gm-Message-State: AKwxytdlJukMsl1VZ3v4b0sn7cjoKI/GAC+cXk/SjymZOiHOdxibm0Sb VGKhFH1dB2NaMrcu1L2T32bROq8Qmp4l1QH12zs= X-Google-Smtp-Source: AH8x225Ln0nPhqAimPJ+s8i0flpLL3SAz2+8JMp1DmOOKspzzB8KHsDYn5K2IwJOrkjkVH+BZfh1GuRayTgk46ywHWU= X-Received: by 10.36.172.45 with SMTP id s45mr20482108ite.69.1517018870450; Fri, 26 Jan 2018 18:07:50 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.152.9 with HTTP; Fri, 26 Jan 2018 18:07:29 -0800 (PST) In-Reply-To: References: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> <20180125221312.GU55707@kib.kiev.ua> From: Ed Maste Date: Fri, 26 Jan 2018 21:07:29 -0500 X-Google-Sender-Auth: 9YrukM5DXJpQOnjpICKL4bcW8p0 Message-ID: Subject: Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1 To: Ian FREISLICH Cc: Konstantin Belousov , current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 02:07:52 -0000 On 25 January 2018 at 17:21, Ian FREISLICH wrote: >> Yes, this is how it is currently behaves. >> PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985. >> It is used for very differrent algorithm when PTI=1, comparing with PTI=0. > > Maybe there should be an "interlock" on these knobs, although judging > from the number of reports I'm the only that shot my foot. Sorry for the trouble. Once D13985 is committed these knobs can both be set to 1 (and in fact that will be the default configuration on Intel systems). I suspect the commit will happen soon and until then it's just a temporary bump inherent in running -current. From owner-freebsd-current@freebsd.org Sat Jan 27 04:42:23 2018 Return-Path: Delivered-To: freebsd-current@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 3EE60EDCD6C for ; Sat, 27 Jan 2018 04:42:23 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail4.jnielsen.net (webmail4.jnielsen.net [IPv6:2607:f7a0:a:18c::c0de]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D4B2275E51; Sat, 27 Jan 2018 04:42:22 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [192.168.2.101] (stealth.jnielsen.net [68.69.164.122]) (authenticated bits=0) by webmail4.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w0R4gGSP022824 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 21:42:19 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail4.jnielsen.net: Host stealth.jnielsen.net [68.69.164.122] claimed to be [192.168.2.101] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Error compiling isboot-kmod From: John Nielsen In-Reply-To: <1516988137.42536.255.camel@freebsd.org> Date: Fri, 26 Jan 2018 21:42:16 -0700 Cc: Warner Losh , Maurizio Vairani , Ian Lepore Content-Transfer-Encoding: quoted-printable Message-Id: References: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.net> <1516988137.42536.255.camel@freebsd.org> To: freebsd-current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 04:42:23 -0000 > On Jan 26, 2018, at 10:35 AM, Ian Lepore wrote: >=20 > On Fri, 2018-01-26 at 10:00 -0700, John Nielsen wrote: >>>=20 >>> On Jan 26, 2018, at 3:37 AM, Maurizio Vairani >> om> wrote: >>>=20 >>> 2018-01-24 17:19 GMT+01:00 Warner Losh : >>>=20 >>>=20 >>> On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani >> il.com> wrote: >>> On this CURRENT snapshot >>> # uname -a >>> FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed >>> Jan 10 >>> 22:55:40 UTC 2018 >>> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENER >>> IC >>> amd64 >>>=20 >>> I can't compile the kernel module isboot-kmod: >>>=20 >>> /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not >>> found >>> #include "device_if.h" >>> ^~~~~~~~~~~~~ >>>=20 >>> I think this was fixed in a newer -current. >>>=20 >>> Warner=20 >>> Thanks Warner, but I have the same error in : >>> # uname -a >>> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 >>> 04:48:52 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src >>> /amd64.amd64/sys/GENERIC amd64 >> Whatever change broke it happened around the beginning of July 2017. >> I started getting (and ignoring, sadly, due to lack of time and >> certainty that anyone cared) messages with this error from pkg- >> fallout@ on July 11. I'm looking through the revision history but >> nothing stands out to me yet. Maybe someone with better svn-foo will >> find it faster. :) >>=20 >>> In file included from /usr/src/sys/dev/mmc/bridge.h:59: >>> /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not >>> found >>> #include "device_if.h" >>> ^~~~~~~~~~~~~ >=20 > I've never looked into how kernel modules compile when built as a = port, > but when built as part of the system kernel build, the SRCS=3D in the > module makefile needs to name all of the dynamically generated header > files such as device_if.h (basically anything ending in _if.h used by > the module needs to be in SRCS=3D). >=20 > So adding device_if.h to SRCS may be all that's needed. Or maybe > that's incremental and you'll find that several others are needed as > well. Thanks! Patching the Makefile with: SRCS+=3D device_if.h bus_if.h solves the above issue but now there's something else. Anyone have an = idea off the top of their head? root@freebsd12:/usr/ports/net/isboot-kmod # make =3D=3D=3D> Configuring for isboot-kmod-0.2.13_1 =3D=3D=3D> Building for isboot-kmod-0.2.13_1 --- machine --- --- x86 --- --- objwarn --- Warning: Object directory not changed from original = /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src --- x86 --- x86 -> /usr/src/sys/x86/include --- machine --- machine -> /usr/src/sys/amd64/include --- opt_cam.h --- --- device_if.h --- --- bus_if.h --- --- opt_cam.h --- :> opt_cam.h --- device_if.h --- awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/device_if.m = -h --- bus_if.h --- awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/bus_if.m -h --- isboot.o --- --- ibft.o --- --- iscsi.o --- --- isboot.o --- cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing -DNO_MALLOC_EXTRAS = -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys = -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD = -MF.depend.isboot.o -MTisboot.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx = -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding = -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline = -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c isboot.c -o isboot.o --- iscsi.o --- cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing -DNO_MALLOC_EXTRAS = -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys = -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD = -MF.depend.iscsi.o -MTiscsi.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx = -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding = -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline = -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c iscsi.c -o iscsi.o --- ibft.o --- cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing -DNO_MALLOC_EXTRAS = -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys = -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD = -MF.depend.ibft.o -MTibft.o -mcmodel=3Dkernel -mno-red-zone -mno-mmx = -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding = -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline = -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c ibft.c -o ibft.o --- iscsi.o --- iscsi.c:1146:3: error: incompatible pointer types passing 'void (struct = mbuf *, void *, void *)' to parameter of type 'm_ext_free_t *' (aka = 'void (*)(struct mbuf *)') [-Werror,-Wincompatible-pointer-types] MEXTADD(md, (caddr_t)ds_dd, (ISCSI_ALIGN(pp->ds_len) ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/sys/sys/mbuf.h:887:42: note: expanded from macro 'MEXTADD' m_extadd((m), (char *)(buf), (size), (free), (arg1), (arg2), = \ ^~~~~~ /usr/src/sys/sys/mbuf.h:634:59: note: passing argument to parameter here void m_extadd(struct mbuf *, char *, u_int, m_ext_free_t, ^ 1 error generated. *** [iscsi.o] Error code 1 make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src 1 error make[2]: stopped in /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src =3D=3D=3D> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the = failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/net/isboot-kmod *** Error code 1 Stop. make: stopped in /usr/ports/net/isboot-kmod > As for commits in the July timeframe that led to this, maybe r320844. From owner-freebsd-current@freebsd.org Sat Jan 27 06:21:02 2018 Return-Path: Delivered-To: freebsd-current@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 3CFA6EDFBD9 for ; Sat, 27 Jan 2018 06:21:02 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail4.jnielsen.net (webmail4.jnielsen.net [IPv6:2607:f7a0:a:18c::c0de]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0C8378B5B; Sat, 27 Jan 2018 06:21:01 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [192.168.2.101] (stealth.jnielsen.net [68.69.164.122]) (authenticated bits=0) by webmail4.jnielsen.net (8.15.2/8.15.2) with ESMTPSA id w0R6KuY0023648 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jan 2018 23:20:59 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail4.jnielsen.net: Host stealth.jnielsen.net [68.69.164.122] claimed to be [192.168.2.101] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Error compiling isboot-kmod From: John Nielsen In-Reply-To: Date: Fri, 26 Jan 2018 23:20:56 -0700 Cc: Warner Losh , Maurizio Vairani , Ian Lepore Content-Transfer-Encoding: quoted-printable Message-Id: <09C92929-BC36-4C75-A2F2-0607C9701D40@jnielsen.net> References: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.net> <1516988137.42536.255.camel@freebsd.org> To: freebsd-current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 06:21:02 -0000 > On Jan 26, 2018, at 9:42 PM, John Nielsen wrote: >=20 >> On Jan 26, 2018, at 10:35 AM, Ian Lepore wrote: >>=20 >> On Fri, 2018-01-26 at 10:00 -0700, John Nielsen wrote: >>>>=20 >>>> On Jan 26, 2018, at 3:37 AM, Maurizio Vairani >>> om> wrote: >>>>=20 >>>> 2018-01-24 17:19 GMT+01:00 Warner Losh : >>>>=20 >>>>=20 >>>> On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani >>> il.com> wrote: >>>> On this CURRENT snapshot >>>> # uname -a >>>> FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed >>>> Jan 10 >>>> 22:55:40 UTC 2018 >>>> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENER >>>> IC >>>> amd64 >>>>=20 >>>> I can't compile the kernel module isboot-kmod: >>>>=20 >>>> /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not >>>> found >>>> #include "device_if.h" >>>> ^~~~~~~~~~~~~ >>>>=20 >>>> I think this was fixed in a newer -current. >>>>=20 >>>> Warner=20 >>>> Thanks Warner, but I have the same error in : >>>> # uname -a >>>> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 >>>> 04:48:52 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src >>>> /amd64.amd64/sys/GENERIC amd64 >>> Whatever change broke it happened around the beginning of July 2017. >>> I started getting (and ignoring, sadly, due to lack of time and >>> certainty that anyone cared) messages with this error from pkg- >>> fallout@ on July 11. I'm looking through the revision history but >>> nothing stands out to me yet. Maybe someone with better svn-foo will >>> find it faster. :) >>>=20 >>>> In file included from /usr/src/sys/dev/mmc/bridge.h:59: >>>> /usr/src/sys/sys/bus.h:726:10: fatal error: 'device_if.h' file not >>>> found >>>> #include "device_if.h" >>>> ^~~~~~~~~~~~~ >>=20 >> I've never looked into how kernel modules compile when built as a = port, >> but when built as part of the system kernel build, the SRCS=3D in the >> module makefile needs to name all of the dynamically generated header >> files such as device_if.h (basically anything ending in _if.h used by >> the module needs to be in SRCS=3D). >>=20 >> So adding device_if.h to SRCS may be all that's needed. Or maybe >> that's incremental and you'll find that several others are needed as >> well. >=20 > Thanks! Patching the Makefile with: > SRCS+=3D device_if.h bus_if.h >=20 > solves the above issue but now there's something else. Anyone have an = idea off the top of their head? >=20 > root@freebsd12:/usr/ports/net/isboot-kmod # make > =3D=3D=3D> Configuring for isboot-kmod-0.2.13_1 > =3D=3D=3D> Building for isboot-kmod-0.2.13_1 > --- machine --- > --- x86 --- > --- objwarn --- > Warning: Object directory not changed from original = /usr/ports/net/isboot-kmod/work/isboot-0.2.13/src > --- x86 --- > x86 -> /usr/src/sys/x86/include > --- machine --- > machine -> /usr/src/sys/amd64/include > --- opt_cam.h --- > --- device_if.h --- > --- bus_if.h --- > --- opt_cam.h --- > :> opt_cam.h > --- device_if.h --- > awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/device_if.m = -h > --- bus_if.h --- > awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/bus_if.m -h > --- isboot.o --- > --- ibft.o --- > --- iscsi.o --- > --- isboot.o --- > cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing = -DNO_MALLOC_EXTRAS -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. = -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.isboot.o -MTisboot.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c isboot.c -o isboot.o > --- iscsi.o --- > cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing = -DNO_MALLOC_EXTRAS -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. = -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.iscsi.o -MTiscsi.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c iscsi.c -o iscsi.o > --- ibft.o --- > cc -O2 -pipe -DNO_MALLOC_EXTRAS -fno-strict-aliasing = -DNO_MALLOC_EXTRAS -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. = -I/usr/src/sys -fno-common -fno-omit-frame-pointer = -mno-omit-leaf-frame-pointer -MD -MF.depend.ibft.o -MTibft.o = -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector = -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef = -Wno-pointer-sign -D__printf__=3D__freebsd_kprintf__ = -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas = -Wno-error-tautological-compare -Wno-error-empty-body = -Wno-error-parentheses-equality -Wno-error-unused-function = -Wno-error-pointer-sign -Wno-error-shift-negative-value = -Wno-error-address-of-packed-member -mno-aes -mno-avx = -std=3Diso9899:1999 -c ibft.c -o ibft.o > --- iscsi.o --- > iscsi.c:1146:3: error: incompatible pointer types passing 'void = (struct mbuf *, void *, void *)' to parameter of type 'm_ext_free_t *' = (aka 'void (*)(struct mbuf *)') [-Werror,-Wincompatible-pointer-types] > MEXTADD(md, (caddr_t)ds_dd, (ISCSI_ALIGN(pp->ds_len) > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > /usr/src/sys/sys/mbuf.h:887:42: note: expanded from macro 'MEXTADD' > m_extadd((m), (char *)(buf), (size), (free), (arg1), (arg2), = \ > ^~~~~~ > /usr/src/sys/sys/mbuf.h:634:59: note: passing argument to parameter = here > void m_extadd(struct mbuf *, char *, u_int, m_ext_free_t, Looks like iscsi.c needs to be fixed up following r324446 = (https://svnweb.freebsd.org/changeset/base/324446). Starting to be out = of my depth unless there's a mechanical way to make the changes? From owner-freebsd-current@freebsd.org Sat Jan 27 07:37:42 2018 Return-Path: Delivered-To: freebsd-current@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 7CE44E65E18 for ; Sat, 27 Jan 2018 07:37:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BAFFB7AC22 for ; Sat, 27 Jan 2018 07:37:41 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.229.130.206]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LjquD-1fCk3p2nv7-00bwfU; Sat, 27 Jan 2018 08:37:32 +0100 Date: Sat, 27 Jan 2018 08:36:58 +0100 From: "O. Hartmann" To: Jan =?ISO-8859-1?Q?Kokem=FCller?= Cc: Ronald Klop , FreeBSD Current Subject: Re: pkg OSVERSION problem Message-ID: <20180127083725.081d5b08@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/JaIym.Vnm/a/8s.suBTMuOP"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:PJpYac7RNrz/QOyS8BzSjVerTsy9Qvj+MoMJ375OT7OU2PROokp 27PKVu9CL5Fe31BbW3k98btkAoAhtWkYYVmtvKttMpQy71eyhWsE8dX87q/A3s1ucx2s9TY vCgnfSzwTbyFQa+bQ6Q1T4TtixCUjaj2DWbPM+072fZ1g9E7VbWqKzeXOyY95iqriXquFwz eNZbS21KjB8djJi9TzT5g== X-UI-Out-Filterresults: notjunk:1;V01:K0:XtNcwNwxeb4=:InPcsCxt/nhxrpXP8iIxa/ gp0A7BNyuLNqTglx+bTIz1F5ERogle2Kp5slpmJqsGCjdvhszBj+MuNXG4uOjpd6NJp8AdszS YagQSBLtdcVukg292y8kusB/pOS/CNCH+VaQRtAUcFsnsxqNmxqao8dd+N/QSGT0XIm6pYePd g8z1cEDTVpj7Zouisa8pJ1sySgfubkpN0xGAHHxVdVIhFpTtFHkwlrj0Jp4jLNqJDkYCJq2ko pFfg/rhj8qBfvHDn5e3Mu0pCfB5VAy7/DtaW6X5/TafQFDG59pgHZtm1QgW1s5lG9ezXpOqgh GI+s7RLpeVh4ogkXayVu3pdHQ3ze4/7gBTYG5XKLPi45f4AJFZSktmg7bjUWx1Af0KgrKgWIt 6rgFd6b+Os+m4eiMJQrPkfLYeKeZKO3jlq172WuedsZqxru8luA+8A5SR3y6VoL2rVwSW+Xjh +Zi9MOITpeGgA5SqZvakc2yioIJNj69VPh3HIrC27RLkNUbDJOvHRHA7ZfFr4c3lX6cY7hlp9 RiSKUOXcsYXevNaMKL9ybmMFXrL1x+CwBHh7ewYpZVem9BLsNhyNBC49KoUkkTVpkd8DU7nqJ 1eZbYDh7iUL9cd66thSuROBgQiVWnMDm4kRkUGNUrMpNnAPRbDkSsz9XWT68ir3iMcfs665TR R51/V0DQd2GyZybaZD53p2Kd75guVwV0W5n8e1V85hnerkjnQcwUqIeQcx5ZeEZHcNJAT9JK1 vBMoJRope0iM76DwERnEi/nwnLUaDEJfEYC7RbP7ZnEQuyqXkI1BXSLj6makjqjmk8jgaIOUE xwB4swQxNN/pLu3ry5hY3kagWb6WA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 07:37:42 -0000 --Sig_/JaIym.Vnm/a/8s.suBTMuOP Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 25 Jan 2018 21:38:27 +0100 Jan Kokem=C3=BCller schrieb: > On 25.01.2018 21:19, Ronald Klop wrote: > > I know there should be multiple updates of packages. > > Even with -o OSVERSION it does not give any new pkgs anymore. > > What will help this? =20 >=20 > I've just had the same issue and solved it by forcefully updating the > package database: >=20 > # pkg -o OSVERSION=3D1200056 update -f > # pkg -o OSVERSION=3D1200056 upgrade >=20 >=20 > -Jan > _______________________________________________ > 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" Thanks, I'll give it a try. regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/JaIym.Vnm/a/8s.suBTMuOP Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmwsNQAKCRDS528fyFhY lELJAf4sGn/48ZZuXhSksXkrGcmJD8HwyFPvLEFDZRHOPuJtPi06frx/8IduQ2XD wK5KDL4YDL52Td1GqHJj1RLaUD9WAf9jqOM5E5JTpODZN6C434h4H6jiLqsB0I9G vR4q4kcjMfnI/lmP0vHrqF+iF3/WTh+1f0xjQ31PLEN7SLhXUw1t =sjYZ -----END PGP SIGNATURE----- --Sig_/JaIym.Vnm/a/8s.suBTMuOP-- From owner-freebsd-current@freebsd.org Sat Jan 27 08:07:04 2018 Return-Path: Delivered-To: freebsd-current@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 0BA2BE75653 for ; Sat, 27 Jan 2018 08:07:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 703077BB14 for ; Sat, 27 Jan 2018 08:07:03 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.229.130.206]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MTBfe-1eEQza3Dss-00S546; Sat, 27 Jan 2018 09:07:00 +0100 Date: Sat, 27 Jan 2018 09:06:27 +0100 From: "O. Hartmann" To: Ben Woods Cc: "O. Hartmann" , freebsd-current Subject: Re: PkgBase: Can not upgrade base system Message-ID: <20180127090654.74d9fda9@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20180123064633.45e2710b@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/5G_zLYdaGbSGDXnjl9u1FGT"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ZQ/jjWpDTCXoxfcaa7uspZrL5B7ntIYJXYpIJpfXGC6pB/ArqBM kjr4E8lmhgL+XcOcGBjI1BDTN6obLx+F8N4L4Vb/1qhb0tPIAirUSUaK1mhPA2RnlDge/Zo xEvETi9DsBScaP3oOpZmMubpKjQDhMmACK7Td4kD3SeO4wdKSKvQXVOwZWyRVHQHJWZM0A+ vI7rh0OD08tXsyGa22Isg== X-UI-Out-Filterresults: notjunk:1;V01:K0:ypN2SJ+J4qc=:0qlNY90lKaSt/LXzt/G179 u0GwKmNLajb5e8kqD4NMhn/2O5QKMqFKXkAhK2y4BGnSUNfxgpaWe7zjKmm3poLN3cA+MocwG mmp6HXH4yX6AB7GJY45RJIJdeBa8JxV3pJaIdKO6OAxnr7t2G1Ws+Dugpd5VeZgIUP+okQfwT mm/o7/J6S++0YdPH9nNT57Pe03jG3zEOkjyoQo8PgPICzJoi+orzO7at5stk2dRC3cCa9/QoC uiuQxOKmaouTFZqw4URDiG8yDIvxOXh184rnnjvadWkrOf3tp3vNaZaIvZT1nt6oztQRnR2dP YXOOksGg2TOHhno/nx7NAYEM9dHglv2eYb7enzX9/tTReI29nElBTFDoeDsjnDP7x6WkKiGq/ L99iHiC6+Mx8vJA6uT3VQXos+1PVrbsrNBssIq7NOCAv3ImxGz/I/dJ08Z3VquVS9HmymsXQV dbMy1I/0oj3KbJAyRQawyDeGnjfoJW7FJhW9DObHMcYR9NjC/lZfqEWXneNxWHFeiYaVL/LSO djceX6oBf30wN+/mXIjiWoYdL4RrtjBjHFOh1JJ4E62RfSKLyl38u5e6xh5OXl8QLq8+TJ9oD vivNBWcbQZ4yLc6MdI/MBqwJb60yE+wHN4HUwXCVKWRxJnHxbvLQ350uo6fkI5F9snqtIfQCw JzGa6Ho/TULMcrITrBPKqmhhmCS0fDdsjskNt41887ON7kPDDXWx9KOX6tlVVXFDJrFG+ZSob QU83zLea4Rx7Pe+xThcXNh9qyjSncW8AmXboeyMKIW4ffMW7Ts3F6IBdcVSaOKPNKs046hBId qjpSOr0X+TEVf/HVPA75IAzvifU/w== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 08:07:04 -0000 --Sig_/5G_zLYdaGbSGDXnjl9u1FGT Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Tue, 23 Jan 2018 22:34:15 +0000 Ben Woods schrieb: > On Tue, 23 Jan 2018 at 4:12 pm, O. Hartmann wrot= e: >=20 > > For a client I tried PkgBase and followed the procedures recommended (f= irst > > build the OS from /usr/src/, installworld/kernel, then proceed with pkg > > update > > -r FreeBSD-base and pkg install -g 'FreeBSD-*'. > > > > This doesn't work for any update I try to apply. Since the target host = is > > a two > > years old Intel NUC based on some Broadwell snail CPU, building world a= nd > > kernel is performed on another, much more potent host. > > > > In the first place, when performing a "pkg upgrade", the system complai= ns > > about > > mismatching OSVERSION, 1200055 forthe running system, and 1200056 for t= he > > packages to be updated. When setting env OSVERSION=3D1200056, pkg (not > > pkg-static!) complains about revision numbers (the long date trailing t= he > > package's name), for instance the newest one is > > > > FreeBSD-hast-12.0.s20180123050738.txz > > > > contained within the repository to be used for the update, but installe= d is > > something older, like FreeBSD-hast-12.0.s20171103114456.txz. > > > > When trying pkg-static, I get a crash of pkg-static, segmentation fault= is > > its > > death-cause. > > > > How am I supposed to update a base system via PkgBase? > > > > Kind regards, > > > > oh > > > > p.s. sorry for the lack of data, the box in question is on a remote site > > without net. > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" =20 >=20 >=20 >=20 > This issue was discussed on the FreeBSD-current mailing list. A workaround > has been provided there, but a proper fix is still to be developed: >=20 > https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068153.h= tml >=20 >=20 > Workaround: >=20 > # pkg -o OSVERSION=3D1200056 upgrade >=20 >=20 > Regards, > Ben >=20 > > -- =20 >=20 > -- > From: Benjamin Woods > woodsb02@gmail.com Thanks. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/5G_zLYdaGbSGDXnjl9u1FGT Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWmwzHgAKCRDS528fyFhY lHqDAf9rIKRGQy+54rX88fP7ulVWiubVJdptNlzTbTjleVhngfWa8p6jS7vA2Ytd 4I5mnQegt8j2N6i1KxGh8jUn/z3/Af9FpWzesLDYgeSWPavPvmtkYkSGPn8EVsrN DAnbYh+Scs1b6xENN/a9WJbsU4Fbul8/6cJHF1ohhcv1o3Qcam18 =4a1B -----END PGP SIGNATURE----- --Sig_/5G_zLYdaGbSGDXnjl9u1FGT-- From owner-freebsd-current@freebsd.org Sat Jan 27 09:23:37 2018 Return-Path: Delivered-To: freebsd-current@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 05146E7A365 for ; Sat, 27 Jan 2018 09:23:37 +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 84E847E9D5 for ; Sat, 27 Jan 2018 09:23:36 +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 1efMhr-0004So-TC; Sat, 27 Jan 2018 10:23:28 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: =?utf-8?Q?Jan_Kokem=C3=BCller?= , "O. Hartmann" Cc: "FreeBSD Current" Subject: Re: pkg OSVERSION problem References: <20180127083725.081d5b08@thor.intern.walstatt.dynvpn.de> Date: Sat, 27 Jan 2018 10:23:28 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: <20180127083725.081d5b08@thor.intern.walstatt.dynvpn.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: 4b95630a2805109a2fafe329e7ec4fd6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 09:23:37 -0000 On Sat, 27 Jan 2018 08:36:58 +0100, O. Hartmann = = wrote: > Am Thu, 25 Jan 2018 21:38:27 +0100 > Jan Kokem=C3=BCller schrieb: > >> On 25.01.2018 21:19, Ronald Klop wrote: >> > I know there should be multiple updates of packages. >> > Even with -o OSVERSION it does not give any new pkgs anymore. >> > What will help this? >> >> I've just had the same issue and solved it by forcefully updating the= >> package database: >> >> # pkg -o OSVERSION=3D1200056 update -f >> # pkg -o OSVERSION=3D1200056 upgrade >> >> >> -Jan >> _______________________________________________ >> 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" > > Thanks, > > I'll give it a try. > > regards, > > Oliver > Thanks also. It kicked pkg upgrade into upgrading again, but in the end = I = missed libdl.so (clang 6?) which was fixed by updating my system to = 1200056 anyway. Otherwise Firefox wouldn't start. So although the OSVERSION check is annoying it does warn for actual = problems. Regards, Ronald. From owner-freebsd-current@freebsd.org Sat Jan 27 11:04:18 2018 Return-Path: Delivered-To: freebsd-current@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 BDD51E7E6C2 for ; Sat, 27 Jan 2018 11:04:18 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic301-21.consmr.mail.ir2.yahoo.com (sonic301-21.consmr.mail.ir2.yahoo.com [77.238.176.98]) (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 4505382841 for ; Sat, 27 Jan 2018 11:04:18 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: _6fPs40VM1k6jihiFSAqxrAEUaoB38.UtXYGeLmusOiT1PxPsl8Mf4Bg7uPhiwq omxZlzesYLVmC7IOD_Yms2JVXl7jhh036Sse22p6ZArL_1g21KFVpcdJBOgzxM2QBd92MppWA8Fc 5CuJE2UMtBLh6kpa1npvgwrBLIAA6Ti60CYFabwNhWZQL1B.ZEJIGZsIuFS6YLNIHDPumvIAEiO1 CadSI1v4yq6uroD2gvlaf60PA.zaQzTBzVg1LLuqcyddpUVpNndylNCnfujFsDEm7MXI_KJFLydx Kj3dSspdREs7oaf2U1ia0AJPI.GLThMh6NISIIswNXqkAwR3X3Crawvz4vglZRYpU14I_F8y0lWp rTIttdClBO_0y7v7qEf.qC9ZdtT8VqiNAZfzdq80cq5thXbcqpW_kXrnklztFz7YFP2pJUz1AS4T 2e5iz868hVVYGhvCMxdUildqv_HHkJj1sq3R4yMLkIJx7.fVAwBMEWt3OUakdTYU8INT4dnpFoFL LMrFz8KI2J57jPmIgx60GUa6g8A-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.ir2.yahoo.com with HTTP; Sat, 27 Jan 2018 11:04:16 +0000 Received: from smtp174.mail.ir2.yahoo.com (EHLO [10.0.0.5]) ([46.228.39.41]) by smtp401.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 5dcab9bc0d6c34d29fee752545dbc9c7 for ; Sat, 27 Jan 2018 10:54:08 +0000 (UTC) To: freebsd-current@freebsd.org From: Per Gunnarsson Subject: Kernel build error Message-ID: Date: Sat, 27 Jan 2018 11:53:48 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 11:04:18 -0000 SGVsbG8hCgpJIGFtIHRyeWluZyB0byBidWlsZCB0aGUga2VybmVsIHdpdGggcmV2aXNpb24g MzI4NDYzLgoKSXQgaGFsdHMgd2l0aCB0aGlzIGVycm9yOgoKL3Vzci9zcmMvc3lzL2NhbS9z Y3NpL3Njc2lfZGEuYzoxNTE0Ojk6IGVycm9yOiAnQ0FNX1BFUklQSF9QUklOVCcgbWFjcm8K cmVkZWZpbmVkIFstV2Vycm9yLC1XbWFjcm8tcmVkZWZpbmVkXQojZGVmaW5lIENBTV9QRVJJ UEhfUFJJTlQocCwgbXNnLCBhcmdzLi4uKQrCoMKgwqDCoMKgwqDCoCBeCi91c3Ivc3JjL3N5 cy9jYW0vY2FtX3BlcmlwaC5oOjI2Mzo5OiBub3RlOiBwcmV2aW91cyBkZWZpbml0aW9uIGlz IGhlcmUKI2RlZmluZSBDQU1fUEVSSVBIX1BSSU5UKHAsIG1zZywgYXJncy4uLinCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAg XArCoMKgwqDCoMKgwqDCoCBeCjEgZXJyb3IgZ2VuZXJhdGVkLgoqKiogRXJyb3IgY29kZSAx CgpTdG9wLgptYWtlWzJdOiBzdG9wcGVkIGluIC91c3Ivb2JqL3Vzci9zcmMvYW1kNjQuYW1k NjQvc3lzL0dFTkVSSUMKKioqIEVycm9yIGNvZGUgMQoKU3RvcC4KbWFrZVsxXTogc3RvcHBl ZCBpbiAvdXNyL3NyYwoqKiogRXJyb3IgY29kZSAxCgpTdG9wLgptYWtlOiBzdG9wcGVkIGlu IC91c3Ivc3JjCgpSZWdhcmRzLAoKUGVyIEd1bm5hcnNzb24KCg== From owner-freebsd-current@freebsd.org Sat Jan 27 16:20:40 2018 Return-Path: Delivered-To: freebsd-current@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 ECEC4EC9A46 for ; Sat, 27 Jan 2018 16:20:39 +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 701A16E9B2 for ; Sat, 27 Jan 2018 16:20:39 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: ff9eabbe-037d-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 ff9eabbe-037d-11e8-91c6-33ffc249f3e8; Sat, 27 Jan 2018 16:20:34 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0RGKWVU002463; Sat, 27 Jan 2018 09:20:32 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1517070032.84051.6.camel@freebsd.org> Subject: Re: Error compiling isboot-kmod From: Ian Lepore To: John Nielsen , freebsd-current Cc: Warner Losh , Maurizio Vairani Date: Sat, 27 Jan 2018 09:20:32 -0700 In-Reply-To: <09C92929-BC36-4C75-A2F2-0607C9701D40@jnielsen.net> References: <9D0C6C9E-3020-4EC0-97AF-6498FB7356C7@jnielsen.net> <1516988137.42536.255.camel@freebsd.org> <09C92929-BC36-4C75-A2F2-0607C9701D40@jnielsen.net> Content-Type: multipart/mixed; boundary="=-OEf9P6vz26f1zq+0BtTv" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 16:20:40 -0000 --=-OEf9P6vz26f1zq+0BtTv Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: > > > > On Jan 26, 2018, at 9:42 PM, John Nielsen wrote: > > > > > > > > [...] > > --- iscsi.o --- > > iscsi.c:1146:3: error: incompatible pointer types passing 'void (struct mbuf *, void *, void *)' to parameter of type 'm_ext_free_t *' (aka 'void (*)(struct mbuf *)') [-Werror,-Wincompatible-pointer-types] > >                MEXTADD(md, (caddr_t)ds_dd, (ISCSI_ALIGN(pp->ds_len) > >                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > /usr/src/sys/sys/mbuf.h:887:42: note: expanded from macro 'MEXTADD' > >    m_extadd((m), (char *)(buf), (size), (free), (arg1), (arg2),        \ > >                                         ^~~~~~ > > /usr/src/sys/sys/mbuf.h:634:59: note: passing argument to parameter here > > void             m_extadd(struct mbuf *, char *, u_int, m_ext_free_t, > Looks like iscsi.c needs to be fixed up following r324446 > (https://svnweb.freebsd.org/changeset/base/324446). Starting to be > out of my depth unless there's a mechanical way to make the changes? > > I'm not set up to test-compile this against -current right now, so I'm not sure if this is all that remains or just another breadcrumb on the trail, but... try the attached patch. -- Ian --=-OEf9P6vz26f1zq+0BtTv Content-Disposition: inline; filename="iscsi_mbuf_free.diff" Content-Type: text/x-patch; name="iscsi_mbuf_free.diff"; charset="ASCII" Content-Transfer-Encoding: 7bit --- iscsi.c.orig 2018-01-27 08:43:26.937858000 -0700 +++ iscsi.c 2018-01-27 09:15:39.631501000 -0700 @@ -1071,17 +1071,23 @@ } -#if __FreeBSD_version >= 1100000 +#if __FreeBSD_version >= 1200051 +static void +isboot_free_mbufext(struct mbuf *m) +{ + void *p = m->m_ext.ext_arg1; +#elif __FreeBSD_version >= 1100000 static void isboot_free_mbufext(struct mbuf *m, void *p, void *optarg) #elif __FreeBSD_version >= 1000050 && __FreeBSD_version < 1100000 static int isboot_free_mbufext(struct mbuf *m, void *p, void *optarg) +{ #else static void isboot_free_mbufext(void *p, void *optarg) -#endif { +#endif ISBOOT_TRACE("isboot_free_mbufext\n"); if (p == NULL) --=-OEf9P6vz26f1zq+0BtTv-- From owner-freebsd-current@freebsd.org Sat Jan 27 18:04:41 2018 Return-Path: Delivered-To: freebsd-current@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 17398ECEA55 for ; Sat, 27 Jan 2018 18:04:41 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic306-20.consmr.mail.ir2.yahoo.com (sonic306-20.consmr.mail.ir2.yahoo.com [77.238.176.206]) (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 8DDE57320A for ; Sat, 27 Jan 2018 18:04:40 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: jHI7xdAVM1mFThEtuZhWCkIBL0HwKX7y9aWRTQUq8U0W5ZDNciHaWGgM7NVxVUc VL5S.5WmXWGw_LNonfqTfpMHfQm2tWH6KjhkPoVDWZKddQO6sVGD2a7GzYT5zbSqg58oU7SDcoSk 8OesYV5xiYKvqVtn94gZwkrqj5ygTVR5lXi5MgjmwFupIv3qF.kD.24s2XeFxSmk0zcR5fE0zGYy UIhjKr8VpEU86tkAdTZBHCDcl4nxzpYgL2gQspK7vYqBXohPzxCW7AShwPDCscR9XNoYJUkOAAx_ D10NbvzT9sCcLZZEr3SVAVHCdjhBzAzn7nSz4NA.DCCcnUUeMuJl24HeoHJMZEd1QYSBIPEbNQ20 D3cJa7RHmKyCYINkEoJYIqj3F8KoeYKMbyTptaemOwLzsb_idFs6fRNtwAuPGS6kMu1oBxPEX6TQ sbQhYt1Mp27ZV1OoOVqW6SZ0JKCxXrfV5ciXd0mRCAL6yleaUVCFLACUQimVnmRzLo6LBbKO3yVy RegNlalmqDYg1G_C7biWSxQnYXA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ir2.yahoo.com with HTTP; Sat, 27 Jan 2018 18:04:33 +0000 Received: from smtp166.mail.ir2.yahoo.com (EHLO [10.0.0.5]) ([46.228.39.33]) by smtp411.mail.ir2.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 0e71df6affa36cac8d6f54b94b8be9dc for ; Sat, 27 Jan 2018 17:54:23 +0000 (UTC) To: freebsd-current From: Per Gunnarsson Subject: Kernel build error rev.328485 Message-ID: <95eb22f2-64e8-2921-3f72-dca1ce048271@yahoo.com> Date: Sat, 27 Jan 2018 18:54:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 18:04:41 -0000 I am back with new build errors. If I post too frequently, please inform me. /usr/src/sys/compat/freebsd32/freebsd32_misc.c:122:1: error: static_assert failed "compile-time assertion failed" CTASSERT(sizeof(struct kevent32) == 20); ^        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/sys/sys/systm.h:107:21: note: expanded from macro 'CTASSERT' #define CTASSERT(x)     _Static_assert(x, "compile-time assertion failed")                         ^              ~ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:126:1: error: static_assert failed "compile-time assertion failed" CTASSERT(sizeof(struct stat32) == 96); ^        ~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/sys/sys/systm.h:107:21: note: expanded from macro 'CTASSERT' #define CTASSERT(x)     _Static_assert(x, "compile-time assertion failed")                         ^              ~ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:612:24: error: no member named 'data' in 'struct kevent32'                 CP(kevp[i], ks32[i], data);                 ~~~~~~~~~~~~~~~~~~~~~^~~~~ /usr/src/sys/compat/freebsd32/freebsd32.h:41:36: note: expanded from macro 'CP' #define CP(src,dst,fld) do { (dst).fld = (src).fld; } while (0)                              ~~~~~ ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:644:24: error: no member named 'data' in 'struct kevent32'                 CP(ks32[i], kevp[i], data);                 ~~~~~~~~~~~~~~~~~~~~~^~~~~ /usr/src/sys/compat/freebsd32/freebsd32.h:41:48: note: expanded from macro 'CP' #define CP(src,dst,fld) do { (dst).fld = (src).fld; } while (0)                                          ~~~~~ ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1738:42: error: declaration of 'struct freebsd32_stat_args' will not be visible outside of this function [-Werror,-Wvisibility] freebsd32_stat(struct thread *td, struct freebsd32_stat_args *uap)                                          ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1744:42: error: incomplete definition of type 'struct freebsd32_stat_args'         error = kern_statat(td, 0, AT_FDCWD, uap->path, UIO_USERSPACE,                                              ~~~^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1738:42: note: forward declaration of 'struct freebsd32_stat_args' freebsd32_stat(struct thread *td, struct freebsd32_stat_args *uap)                                          ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1749:28: error: incomplete definition of type 'struct freebsd32_stat_args'         error = copyout(&sb32, uap->ub, sizeof (sb32));                                ~~~^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1738:42: note: forward declaration of 'struct freebsd32_stat_args' freebsd32_stat(struct thread *td, struct freebsd32_stat_args *uap)                                          ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1738:1: error: no previous prototype for function 'freebsd32_stat' [-Werror,-Wmissing-prototypes] freebsd32_stat(struct thread *td, struct freebsd32_stat_args *uap) ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1820:43: error: declaration of 'struct freebsd32_lstat_args' will not be visible outside of this function [-Werror,-Wvisibility] freebsd32_lstat(struct thread *td, struct freebsd32_lstat_args *uap)                                           ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1826:60: error: incomplete definition of type 'struct freebsd32_lstat_args'         error = kern_statat(td, AT_SYMLINK_NOFOLLOW, AT_FDCWD, uap->path,                                                                ~~~^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1820:43: note: forward declaration of 'struct freebsd32_lstat_args' freebsd32_lstat(struct thread *td, struct freebsd32_lstat_args *uap)                                           ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1831:28: error: incomplete definition of type 'struct freebsd32_lstat_args'         error = copyout(&sb32, uap->ub, sizeof (sb32));                                ~~~^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1820:43: note: forward declaration of 'struct freebsd32_lstat_args' freebsd32_lstat(struct thread *td, struct freebsd32_lstat_args *uap)                                           ^ /usr/src/sys/compat/freebsd32/freebsd32_misc.c:1820:1: error: no previous prototype for function 'freebsd32_lstat' [-Werror,-Wmissing-prototypes] freebsd32_lstat(struct thread *td, struct freebsd32_lstat_args *uap) ^ 12 errors generated. *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src Regards, Per Gunnarsson From owner-freebsd-current@freebsd.org Sat Jan 27 17:32:21 2018 Return-Path: Delivered-To: freebsd-current@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 6CA00ECD28C for ; Sat, 27 Jan 2018 17:32:21 +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 D86F871C2E for ; Sat, 27 Jan 2018 17:32:20 +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 w0RHWGFd010465; Sat, 27 Jan 2018 09:32:16 -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 w0RHWFlu010464; Sat, 27 Jan 2018 09:32:15 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201801271732.w0RHWFlu010464@pdx.rh.CN85.dnsmgr.net> Subject: Re: Kernel build error In-Reply-To: To: Per Gunnarsson Date: Sat, 27 Jan 2018 09:32:15 -0800 (PST) CC: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Sat, 27 Jan 2018 18:49:23 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2018 17:32:21 -0000 [ Charset UTF-8 unsupported, converting... ] > Hello! > > I am trying to build the kernel with revision 328463. > > It halts with this error: > > /usr/src/sys/cam/scsi/scsi_da.c:1514:9: error: 'CAM_PERIPH_PRINT' macro > redefined [-Werror,-Wmacro-redefined] > #define CAM_PERIPH_PRINT(p, msg, args...) > ??????? ^ > /usr/src/sys/cam/cam_periph.h:263:9: note: previous definition is here > #define CAM_PERIPH_PRINT(p, msg, args...)?????????????????????????????? \ > ??????? ^ > 1 error generated. > *** Error code 1 > > Stop. > make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > Regards, > > Per Gunnarsson Fixed in https://svnweb.freebsd.org/changeset/base/328464 -- Rod Grimes rgrimes@freebsd.org