From owner-freebsd-arm@freebsd.org Sun Nov 6 20:03:46 2016 Return-Path: Delivered-To: freebsd-arm@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 B305DC33742 for ; Sun, 6 Nov 2016 20:03:46 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 551A316CB for ; Sun, 6 Nov 2016 20:03:45 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1478462622; l=3820; s=domk; d=ulrich-grey.de; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Subject:To:From: Date; bh=05PqzG7vPfJHZHDWuwNE8D98SFOmlaN8k57OB2NPvCE=; b=pGeAZkhxshszhntkHPhnk08ZiwLFgBKsj5/hZQ062RUTOzzU1jRcTGCXELsnsXGIky5 eCVZUhICLXpXBuPqOcnRhGCm+kVZ+rwUc/KsLJa8DxM4gb3YQSZffN41MaPsxI3orR8AR qGRBgWltCBY0XkaSkwers0i4F4mbAWZcQF4= X-RZG-AUTH: :OX8Be0W8W+pMC3rDLL/lo2xV/LZTbZkYhOcjg8suic3iYr/B8J9Lzp3TJg48uMv49Xo= X-RZG-CLASS-ID: mo00 Received: from work (p54868C42.dip0.t-ipconnect.de [84.134.140.66]) by smtp.strato.de (RZmta 39.7 DYNA|AUTH) with ESMTPSA id 6010c7sA6K3f1yj (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Sun, 6 Nov 2016 21:03:41 +0100 (CET) Date: Sun, 6 Nov 2016 21:03:41 +0100 From: Ulrich Grey To: freebsd-arm@freebsd.org Subject: FreeBSD 11.0-STABLE #0 r307979M: panic: vm_radix_remove: impossible to locate the key Message-Id: <20161106210341.0c452da473c3313165bf3f8c@ulrich-grey.de> Organization: - X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; armv6-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Nov 2016 20:03:46 -0000 Hello, I am running: freebsd@worktest:~ % uname -ap FreeBSD worktest 11.0-STABLE FreeBSD 11.0-STABLE #0 r307979M: Thu Oct 27 09:04:38 UTC 2016 freebsd@worktest:/usr/local/DEVEL/obj/usr/local/DEVEL/SRC/11/sys/IMX6 arm armv6 on a CUBOX. After > 50 hours building ports I got a panic: panic: vm_radix_remove: impossible to locate the key cpuid = 0 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc259e47c lr = 0xc205d1f8 (db_trace_self_wrapper+0x30) sp = 0xfbbe98b8 fp = 0xfbbe99d0 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc205d1f8 lr = 0xc2216f98 (vpanic+0x13c) sp = 0xfbbe99d8 fp = 0xfbbe99f8 r4 = 0x00000100 r5 = 0xc7a356e0 r6 = 0xc265c1c6 r7 = 0x00000001 vpanic() at vpanic+0x13c pc = 0xc2216f98 lr = 0xc2216e5c (vpanic) sp = 0xfbbe9a00 fp = 0xfbbe9a04 r4 = 0xe086130c r5 = 0x00000000 r6 = 0x000c585c r7 = 0xc287a720 r8 = 0x00000001 r9 = 0xc7b8dc5c r10 = 0x00000018 vpanic() at vpanic pc = 0xc2216e5c lr = 0xc258fc9c (vm_radix_remove+0x1c8) sp = 0xfbbe9a0c fp = 0xfbbe9a28 r4 = 0xc287a720 r5 = 0x00000001 r6 = 0xc7b8dc5c r7 = 0x00000018 r8 = 0xfbbe9a04 r9 = 0xc2216e5c r10 = 0xfbbe9a0c vm_radix_remove() at vm_radix_remove+0x1c8 pc = 0xc258fc9c lr = 0xc257fbbc (vm_page_remove+0x34) sp = 0xfbbe9a30 fp = 0xfbbe9a38 r4 = 0xc2c48a50 r5 = 0xca5c1f18 r6 = 0x000c585c r7 = 0xc287a720 vm_page_remove() at vm_page_remove+0x34 pc = 0xc257fbbc lr = 0xc257ee90 (vm_page_free_toq+0x5c) sp = 0xfbbe9a40 fp = 0xfbbe9a58 r4 = 0xc2c48a50 r5 = 0xc2c48a50 vm_page_free_toq() at vm_page_free_toq+0x5c pc = 0xc257ee90 lr = 0xc25b5f90 (free_pv_chunk+0x168) sp = 0xfbbe9a60 fp = 0xfbbe9a70 r4 = 0xc585c000 r5 = 0xc2c48a50 r6 = 0x000c585c r10 = 0x00000018 free_pv_chunk() at free_pv_chunk+0x168 pc = 0xc25b5f90 lr = 0xc25b5c0c (pmap_remove_pages+0x66c) sp = 0xfbbe9a78 fp = 0xfbbe9ad0 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc3ae6170 r7 = 0x56adcc33 pmap_remove_pages() at pmap_remove_pages+0x66c pc = 0xc25b5c0c lr = 0xc256ad00 (vmspace_exit+0xc8) sp = 0xfbbe9ad8 fp = 0xfbbe9af8 r4 = 0xc7b8dc58 r5 = 0x00000001 r6 = 0xc285e650 r7 = 0xcab14000 r8 = 0xc7b8dc5c r9 = 0xc7b8dba0 r10 = 0xc7a356e0 vmspace_exit() at vmspace_exit+0xc8 pc = 0xc256ad00 lr = 0xc21bbdf8 (exit1+0xb9c) sp = 0xfbbe9b00 fp = 0xfbbe9b58 r4 = 0xc7a356e0 r5 = 0x00000004 r6 = 0xc7a356e0 r7 = 0xcab14000 r8 = 0xcab140bc r9 = 0xc707825c r10 = 0xcab140ac exit1() at exit1+0xb9c pc = 0xc21bbdf8 lr = 0xc221bc78 ($a.5+0x934) sp = 0xfbbe9b60 fp = 0xfbbe9d38 r4 = 0xfbbe9c88 r5 = 0x00000000 r6 = 0x00000005 r7 = 0xc261d701 r8 = 0xc7a356e0 r9 = 0x0000000b r10 = 0xc7a356e0 $a.5() at $a.5+0x934 pc = 0xc221bc78 lr = 0xc221cc5c (osigsuspend) sp = 0xfbbe9d40 fp = 0xfbbe9dd0 r4 = 0x0000000b r5 = 0xc7a356e0 r6 = 0xc7a356e0 r7 = 0xcab14000 r8 = 0xcb01aab8 r9 = 0x00020804 r10 = 0x00000000 osigsuspend() at osigsuspend pc = 0xc221cc5c lr = 0xc22865cc (ast+0x620) sp = 0xfbbe9dd8 fp = 0xfbbe9e00 ast() at ast+0x620 pc = 0xc22865cc lr = 0xc25a0da4 (exception_exit+0x40) sp = 0xfbbe9e08 fp = 0xbfbfdf28 r4 = 0x60000113 r5 = 0xc7a356e0 r6 = 0x00000000 r7 = 0x2003a200 r8 = 0x20035bc4 r9 = 0x20036718 r10 = 0x20036700 exception_exit() at exception_exit+0x40 pc = 0xc25a0da4 lr = 0x200287ec (0x200287ec) sp = 0xfbbe9e98 fp = 0xbfbfdf28 r0 = 0x00000000 r1 = 0x00000000 r2 = 0x00000000 r3 = 0x00000002 r4 = 0x00000002 r5 = 0xbfbfe3d8 r6 = 0x00000000 r7 = 0x2003a200 r8 = 0x20035bc4 r9 = 0x20036718 r10 = 0x20036700 r12 = 0x2003a200 Unable to unwind into user mode KDB: enter: panic [ thread pid 17915 tid 100894 ] Stopped at $d.6: ldrb r15, [r15, r15, ror r15]! db> show all pcpu ... For further information please see: http://ulrich-grey.de/dl/cubox_panic20161106.log From owner-freebsd-arm@freebsd.org Mon Nov 7 20:08:22 2016 Return-Path: Delivered-To: freebsd-arm@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 6033DC35A8B for ; Mon, 7 Nov 2016 20:08:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A007B6C for ; Mon, 7 Nov 2016 20:08:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uA7K8MKm062939 for ; Mon, 7 Nov 2016 20:08:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 214299] make buildworld fails on Raspberry Pi B plus Date: Mon, 07 Nov 2016 20:08:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: punasipuli@t-online.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2016 20:08:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214299 Bug ID: 214299 Summary: make buildworld fails on Raspberry Pi B plus Product: Base System Version: 11.0-STABLE Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: punasipuli@t-online.de Created attachment 176750 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176750&action= =3Dedit ObjCMT-185783.cpp --- all_subdir_lib/clang/libclangarcmigrate --- c++: error: unable to execute command: Killed c++: error: clang frontend command failed due to signal (use -v to see invocation) FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) Target: armv6--freebsd11.0-gnueabihf Thread model: posix InstalledDir: /usr/bin c++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preproces= sed source, and associated run script. --- all_subdir_lib/clang/libclangbasic --- --- ObjCRuntime.o --- c++ -target armv6-gnueabihf-freebsd11.0 --sysroot=3D/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -mlong-calls -O -pipe -I/usr/src/lib/clang/libclangbasic/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Ba= sic -I. -I/usr/src/lib/clang/libclangbasic/../../../contrib/llvm/../../lib/clang/in= clude -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MA= CROS -DNDEBUG -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=3D\"armv6-gnueabihf-freebsd11.0\" -DLLVM_HOST_TRIPLE=3D\"armv6-unknown-freebsd11.0\" -DDEFAULT_SYSROOT=3D\"\"= -MD -MF.depend.ObjCRuntime.o -MTObjCRuntime.o -Qunused-arguments -std=3Dc++11 -fno-exceptions -fno-rtti -stdlib=3Dlibc++ -Wno-c++11-extensions -c /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Basi= c/ObjCRuntime.cpp -o ObjCRuntime.o --- all_subdir_lib/clang/libclangarcmigrate --- c++: note: diagnostic msg:=20 ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: c++: note: diagnostic msg: /tmp/ObjCMT-185783.cpp c++: note: diagnostic msg: /tmp/ObjCMT-185783.sh c++: note: diagnostic msg:=20 ******************** *** [ObjCMT.o] Error code 254 make[6]: stopped in /usr/src/lib/clang/libclangarcmigrate 1 error --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Mon Nov 7 20:19:33 2016 Return-Path: Delivered-To: freebsd-arm@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 8A86FC35D64 for ; Mon, 7 Nov 2016 20:19:33 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-55.reflexion.net [208.70.210.55]) (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 3AE891A5 for ; Mon, 7 Nov 2016 20:19:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 30893 invoked from network); 7 Nov 2016 20:19:21 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 7 Nov 2016 20:19:21 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.10.1) with SMTP; Mon, 07 Nov 2016 15:19:30 -0500 (EST) Received: (qmail 7498 invoked from network); 7 Nov 2016 20:19:30 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 7 Nov 2016 20:19:30 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 1DDB1EC7888; Mon, 7 Nov 2016 12:19:25 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)? Message-Id: <65D8A8E5-07F0-4E0F-A412-C2CDE2D9982A@dsl-only.net> Date: Mon, 7 Nov 2016 12:19:24 -0800 To: FreeBSD Toolchain , freebsd-arm , FreeBSD-STABLE Mailing List , FreeBSD Current X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2016 20:19:33 -0000 It looks like http://pkg.freebsd.org is still back as of head being = 11-CURRENT: http://pkg.freebsd.org shows only =E2=80=A2 freebsd:11:aarch64:64 (as http://pkg.freebsd.org/freebsd%3A11%3Aaarch64%3A64 ). So on 12-CURRENT pkg bootstrapping gets: > # pkg > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping pkg from = pkg+http://pkg.FreeBSD.org/FreeBSD:12:aarch64/latest, please wait... > pkg: Error fetching = http://pkg.FreeBSD.org/FreeBSD:12:aarch64/latest/Latest/pkg.txz: Not = Found > A pre-built version of pkg could not be found for your system. > Consider changing PACKAGESITE or installing it from ports: = 'ports-mgmt/pkg'. but ld is also missing at this stage so one cannot link anything --and = pkg is not a route to make an ld available. So how does one currently bootstrap a 12-CURRENT pkg for aarch64 = (context: pine64+ 2GB)? Create a /usr/local/etc/pkg/repos/FreeBSD.conf to reference = FreeBSD:11:aarch64 ? That just reports the wrong architecture is being = attempted: > # pkg > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping pkg from = pkg+http://pkg.FreeBSD.org/FreeBSD:11:aarch64/latest, please wait... > Verifying signature with trusted certificate = pkg.freebsd.org.2013102301... done > pkg-static: Warning: Major OS version upgrade detected. Running = "pkg-static install -f pkg" recommended > Installing pkg-1.9.2... > pkg-static: wrong architecture: FreeBSD:11:aarch64 instead of = FreeBSD:12:aarch64 >=20 > Failed to install the following 1 package(s): /tmp//pkg.txz.zkdHp2 pkg-static install -f pkg fetches meta.txz and packagesite.txz first but = then also reports "wrong architecture": > # pkg-static install -f pkg > pkg-static: Warning: Major OS version upgrade detected. Running = "pkg-static install -f pkg" recommended > Updating FreeBSD repository catalogue... > Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 =20 > Fetching packagesite.txz: 100% 4 MiB 4.3MB/s 00:01 =20 > Processing entries: 0% > pkg-static: wrong architecture: freebsd:11:aarch64:64 instead of = FreeBSD:12:aarch64 > pkg-static: repository FreeBSD contains packages with wrong ABI: = freebsd:11:aarch64:64 > Processing entries: 100% > Unable to update repository FreeBSD > All repositories are up-to-date. > pkg-static: Repository FreeBSD cannot be opened. 'pkg update' required > pkg-static: No packages available to install matching 'pkg' have been = found in the repositories Context details (was cross built from amd64 head -r308247): > # uname -apKU > FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r308247M: Thu Nov = 3 07:10:44 PDT 2016 = markmi@FreeBSDx64:/usr/local/src/crochet/work/obj/arm64.aarch64/usr/src/sy= s/GENERIC-NODBG arm64 aarch64 1200014 1200014 > # svnlite info /usr/ports | grep "Re[lv]" > Relative URL: ^/head > Revision: 424540 > Last Changed Rev: 424540 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Nov 7 21:16:43 2016 Return-Path: Delivered-To: freebsd-arm@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 7FBA8C34372; Mon, 7 Nov 2016 21:16:43 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.87.78.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "valentine.liquidneon.com", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AF40227; Mon, 7 Nov 2016 21:16:42 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id B52342B2C6; Mon, 7 Nov 2016 14:16:41 -0700 (MST) Date: Mon, 7 Nov 2016 14:16:41 -0700 From: Brad Davis To: Mark Millard Cc: FreeBSD Toolchain , freebsd-arm , FreeBSD-STABLE Mailing List , FreeBSD Current Subject: Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)? Message-ID: <20161107211641.GI34174@corpmail.liquidneon.com> References: <65D8A8E5-07F0-4E0F-A412-C2CDE2D9982A@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65D8A8E5-07F0-4E0F-A412-C2CDE2D9982A@dsl-only.net> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2016 21:16:43 -0000 On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote: > It looks like http://pkg.freebsd.org is still back as of head being 11-CURRENT: http://pkg.freebsd.org shows only Correct. I wrote up some details on how to use the 11 packages here: http://www.raspbsd.org/raspberrypi.html Regards, Brad Davis From owner-freebsd-arm@freebsd.org Tue Nov 8 04:36:17 2016 Return-Path: Delivered-To: freebsd-arm@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 5A6C2C35DBE for ; Tue, 8 Nov 2016 04:36:17 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-60.reflexion.net [208.70.210.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 08216103C for ; Tue, 8 Nov 2016 04:36:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6516 invoked from network); 8 Nov 2016 04:36:57 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 8 Nov 2016 04:36:57 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.10.1) with SMTP; Mon, 07 Nov 2016 23:36:03 -0500 (EST) Received: (qmail 12026 invoked from network); 8 Nov 2016 04:36:03 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Nov 2016 04:36:03 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 18674EC7888; Mon, 7 Nov 2016 20:35:58 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)? From: Mark Millard In-Reply-To: <20161107211641.GI34174@corpmail.liquidneon.com> Date: Mon, 7 Nov 2016 20:35:57 -0800 Cc: freebsd-arm , FreeBSD-STABLE Mailing List , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <26573287-17D4-4B1C-A6A0-79B9DD03A18B@dsl-only.net> References: <65D8A8E5-07F0-4E0F-A412-C2CDE2D9982A@dsl-only.net> <20161107211641.GI34174@corpmail.liquidneon.com> To: Brad Davis , FreeBSD Toolchain X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 04:36:17 -0000 On 2016-Nov-7, at 1:16 PM, Brad Davis wrote: > On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote: >> It looks like http://pkg.freebsd.org is still back as of head being = 11-CURRENT: http://pkg.freebsd.org shows only >=20 > Correct. I wrote up some details on how to use the 11 packages here: >=20 > http://www.raspbsd.org/raspberrypi.html >=20 >=20 > Regards, > Brad Davis Thanks. That helped me get to the next issue to figure out. I eventually found that https://wiki.freebsd.org/arm64/rpi3 has a = "Package Repo" section with the alternate ABI information for pkg and = also how to get port builds going (putting an ld in place) --as if the = material was RPI3 specific. https://wiki.freebsd.org/arm64/rpi3 says: > There is no package repo for 12-CURRENT, but the package repo for 11 = can be used on 12-CURRENT by telling pkg to use the FreeBSD 11 aarch64 = ABI:=20 >=20 > env ABI=3DFreeBSD:11:aarch64 pkg bootstrap >=20 > Once pkg is bootstrapped, you can add this to /usr/local/etc/pkg.conf:=20= >=20 > ABI =3D "FreeBSD:11:aarch64"; >=20 > If you want to build your own ports or packages, you'll need to = install the aarch64-binutils package and link /usr/bin/ld to = /usr/local/bin/aarch64-freebsd-ld:=20 >=20 > # pkg install aarch64-binutils > # ln /usr/local/bin/aarch64-freebsd-ld /usr/bin/ld >=20 > Note that if you're building directly on the RPI3, you will definitely = want to use either USB storage or NFS. Building on the sdcard will = likely wear the sdcard out.=20 (I have the root filesystem on a USB SSD.) My context is a Pine64+ 2GB --which https://wiki.freebsd.org/arm64 does = not even mention as covered by TARGET_ARCH=3Daarch64 . But crochet is = set up for pine64's and uses TARGET_ARCH=3Daarch64 style builds. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Tue Nov 8 04:54:11 2016 Return-Path: Delivered-To: freebsd-arm@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 634ABC36687 for ; Tue, 8 Nov 2016 04:54:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-53.reflexion.net [208.70.210.53]) (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 248FE1B06 for ; Tue, 8 Nov 2016 04:54:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29066 invoked from network); 8 Nov 2016 04:55:07 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 8 Nov 2016 04:55:07 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.10.1) with SMTP; Mon, 07 Nov 2016 23:54:18 -0500 (EST) Received: (qmail 3864 invoked from network); 8 Nov 2016 04:54:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Nov 2016 04:54:18 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 8D511EC7888; Mon, 7 Nov 2016 20:54:08 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: FYI: a Pine64+ 2G aarch64 head -r308247 crash and some information about it Message-Id: Date: Mon, 7 Nov 2016 20:54:08 -0800 To: freebsd-arm , FreeBSD Current X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 04:54:11 -0000 This is just in case any of the information happens to prove = useful/interesting. I'm not expecting any assistance. Note: After the crash ddb was not responding to input so this is all = that I have. Note: This was an experiment with head -r308247 but was built like = stable for performance issues (GENERIC included and then overridden, not = GENERIC-UP based). The below was found via dmesg and/or /var/log/messages content while the = Pine64 was busy building lang/gcc6 and its prerequisites (as a stability test). It got lots of spurious interrupt notices per second, such as: > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 106 on CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU1 > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU1 > Spurious interrupt detected: last irq: 27 on CPU3 > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU0 > Spurious interrupt detected: last irq: 27 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 27 happened the most by far. 106 was fairly rare. I'd not noticed any = other figures. =46rom what I saw all were "gic0". sh had a few signal 11's and one signal 4 as of when I had last checked: > pid 13900 (sh), uid 0: exited on signal 11 (core dumped) > pid 19325 (sh), uid 0: exited on signal 11 (core dumped) > pid 49697 (sh), uid 0: exited on signal 11 (core dumped) > pid 68390 (sh), uid 0: exited on signal 4 (core dumped) > pid 81149 (sh), uid 0: exited on signal 11 (core dumped) I did not notice any other core dumps. And the following happened once that I noticed: > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 16 a3 a4 80 00 00 40 00=20= > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error > (da0:umass-sim0:0:0:0): Retrying command The root filesystem was on a USB SSD. The above was all from a ssh session history. The below is from the = serial console. . . Later it got the crash: > panic: ARM64TODO: reclaim_pv_chunk > cpuid =3D 2 > KDB: stack backtrace: > db_trace_self() at db_trace_self_wrapper+0x28 > pc =3D 0xffff00000068b430 lr =3D 0xffff0000000631dc > sp =3D 0xffff000083758080 fp =3D 0xffff000083758290 >=20 > db_trace_self_wrapper() at vpanic+0x170 > pc =3D 0xffff0000000631dc lr =3D 0xffff000000335f10 > sp =3D 0xffff0000837582a0 fp =3D 0xffff000083758320 >=20 > vpanic() at panic+0x4c > pc =3D 0xffff000000335f10 lr =3D 0xffff000000335d9c > sp =3D 0xffff000083758330 fp =3D 0xffff0000837583b0 >=20 > panic() at reclaim_pv_chunk+0x10 > pc =3D 0xffff000000335d9c lr =3D 0xffff0000006a13d4 > sp =3D 0xffff0000837583c0 fp =3D 0xffff0000837583c0 >=20 > reclaim_pv_chunk() at get_pv_entry+0x2bc > pc =3D 0xffff0000006a13d4 lr =3D 0xffff00000069c270 > sp =3D 0xffff0000837583d0 fp =3D 0xffff000083758400 >=20 > get_pv_entry() at pmap_enter+0x68c > pc =3D 0xffff00000069c270 lr =3D 0xffff00000069b41c > sp =3D 0xffff000083758410 fp =3D 0xffff0000837584b0 >=20 > pmap_enter() at vm_fault_hold+0x2f0 > pc =3D 0xffff00000069b41c lr =3D 0xffff000000641eb8 > sp =3D 0xffff0000837584c0 fp =3D 0xffff000083758600 >=20 > vm_fault_hold() at vm_fault_quick_hold_pages+0x120 > pc =3D 0xffff000000641eb8 lr =3D 0xffff000000645004 > sp =3D 0xffff000083758610 fp =3D 0xffff000083758670 >=20 > vm_fault_quick_hold_pages() at vn_io_fault1+0x250 > pc =3D 0xffff000000645004 lr =3D 0xffff00000042b788 > sp =3D 0xffff000083758680 fp =3D 0xffff0000837587c0 >=20 > vn_io_fault1() at vn_io_fault+0x170 > pc =3D 0xffff00000042b788 lr =3D 0xffff0000004297a4 > sp =3D 0xffff0000837587d0 fp =3D 0xffff000083758840 >=20 > vn_io_fault() at dofilewrite+0xbc > pc =3D 0xffff0000004297a4 lr =3D 0xffff0000003a35e4 > sp =3D 0xffff000083758850 fp =3D 0xffff000083758890 >=20 > dofilewrite() at kern_writev+0x6c > pc =3D 0xffff0000003a35e4 lr =3D 0xffff0000003a32d4 > sp =3D 0xffff0000837588a0 fp =3D 0xffff0000837588e0 >=20 > kern_writev() at sys_write+0x7c > pc =3D 0xffff0000003a32d4 lr =3D 0xffff0000003a3258 > sp =3D 0xffff0000837588f0 fp =3D 0xffff000083758930 >=20 > sys_write() at do_el0_sync+0x6fc > pc =3D 0xffff0000003a3258 lr =3D 0xffff0000006a2778 > sp =3D 0xffff000083758940 fp =3D 0xffff000083758a70 >=20 > do_el0_sync() at handle_el0_sync+0x64 > pc =3D 0xffff0000006a2778 lr =3D 0xffff00000068d1d0 > sp =3D 0xffff000083758a80 fp =3D 0xffff000083758b90 >=20 > handle_el0_sync() at 0x696ff0 > pc =3D 0xffff00000068d1d0 lr =3D 0x0000000000696ff0 > sp =3D 0xffff000083758ba0 fp =3D 0x0000ffffffffc610 >=20 > KDB: enter: panic > [ thread pid 850 tid 100149 ] > Stopped at kdb_enter+0x40: undefined d4200000 Side notes: To do the lang/gcc6 test I adjusted lang/gcc6/Makefile to (hopefully) = allow an aarch64 build attempt: > # svnlite diff /usr/ports/lang/gcc6 > Index: /usr/ports/lang/gcc6/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/ports/lang/gcc6/Makefile (revision 424540) > +++ /usr/ports/lang/gcc6/Makefile (working copy) > @@ -35,7 +35,7 @@ > DISTVERSION=3D ${PORTVERSION:C/([0-9]+).*\.s([0-9]+)/\1-\2/} > GCC_VERSION=3D ${PORTVERSION:C/(.+)\.s[0-9]{8}/\1/} > SUFFIX=3D ${PORTVERSION:C/([0-9]+).*/\1/} > -ONLY_FOR_ARCHS=3D amd64 i386 powerpc powerpc64 sparc64 arm armv6 = armv6hf > +ONLY_FOR_ARCHS=3D amd64 i386 powerpc powerpc64 sparc64 arm armv6 = armv6hf aarch64 > USES=3D compiler cpe gmake iconv libtool makeinfo perl5 = tar:bzip2 > USE_BINUTILS=3D yes > USE_PERL5=3D build > @@ -73,7 +73,7 @@ > USE_GCC=3D 4.9+ > .endif > =20 > -.if ${ARCH} =3D=3D "armv6" || ${ARCH} =3D=3D "armv6hf" > +.if ${ARCH} =3D=3D "armv6" || ${ARCH} =3D=3D "armv6hf" || ${ARCH} =3D=3D= "aarch64" > . if ${COMPILER_TYPE} =3D=3D clang > . if empty(PORT_OPTIONS:MBOOTSTRAP) > MAKE_ARGS+=3DCXXFLAGS=3D-fbracket-depth=3D512 It did not make it to lang/gcc6 itself but did build several things. (I did not care if lang/gcc6 really worked or not: Environment stability test.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Tue Nov 8 06:42:11 2016 Return-Path: Delivered-To: freebsd-arm@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 92A00C36490 for ; Tue, 8 Nov 2016 06:42:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-56.reflexion.net [208.70.210.56]) (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 53EFA826 for ; Tue, 8 Nov 2016 06:42:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 11183 invoked from network); 8 Nov 2016 06:41:58 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 8 Nov 2016 06:41:58 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.10.1) with SMTP; Tue, 08 Nov 2016 01:42:13 -0500 (EST) Received: (qmail 21188 invoked from network); 8 Nov 2016 06:42:13 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Nov 2016 06:42:13 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A2C15EC8AB5; Mon, 7 Nov 2016 22:42:08 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: FYI: a Pine64+ 2G aarch64 head -r308247 crash and some information about it Date: Mon, 7 Nov 2016 22:42:08 -0800 References: To: freebsd-arm , FreeBSD Current In-Reply-To: Message-Id: <7561E656-3EFC-4338-A419-C35BBA40D07A@dsl-only.net> X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 06:42:11 -0000 On 2016-Nov-7, at 8:54 PM, Mark Millard wrote: > This is just in case any of the information happens to prove = useful/interesting. > I'm not expecting any assistance. >=20 > Note: After the crash ddb was not responding to input so this is all = that I have. >=20 > Note: This was an experiment with head -r308247 but was built like = stable for > performance issues (GENERIC included and then overridden, not = GENERIC-UP > based). >=20 > The below was found via dmesg and/or /var/log/messages content while = the Pine64 > was busy building lang/gcc6 and its prerequisites (as a stability = test). >=20 > It got lots of spurious interrupt notices per second, such as: >=20 >> gic0: Spurious interrupt detected: last irq: 27 on CPU0 >> gic0: Spurious interrupt detected: last irq: 27 on CPU2 >> gic0: Spurious interrupt detected: last irq: 106 on CPU3 >> gic0: Spurious interrupt detected: last irq: 27 on CPU1 >> gic0: Spurious interrupt detected: last irq: 27 on CPU1 >> gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU1 >> Spurious interrupt detected: last irq: 27 on CPU3 >> gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU0 >> Spurious interrupt detected: last irq: 27 on CPU1 >> gic0: Spurious interrupt detected: last irq: 27 on CPU1 >> gic0: Spurious interrupt detected: last irq: 27 on CPU2 >> gic0: Spurious interrupt detected: last irq: 27 on CPU3 >=20 > 27 happened the most by far. 106 was fairly rare. I'd not noticed any = other > figures. =46rom what I saw all were "gic0". >=20 > sh had a few signal 11's and one signal 4 as of when I had last = checked: >=20 >> pid 13900 (sh), uid 0: exited on signal 11 (core dumped) >> pid 19325 (sh), uid 0: exited on signal 11 (core dumped) >> pid 49697 (sh), uid 0: exited on signal 11 (core dumped) >> pid 68390 (sh), uid 0: exited on signal 4 (core dumped) >> pid 81149 (sh), uid 0: exited on signal 11 (core dumped) >=20 > I did not notice any other core dumps. >=20 > And the following happened once that I noticed: >=20 >> (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 16 a3 a4 80 00 00 40 00=20= >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error >> (da0:umass-sim0:0:0:0): Retrying command >=20 > The root filesystem was on a USB SSD. >=20 > The above was all from a ssh session history. The below is from the = serial > console. . . >=20 > Later it got the crash: >=20 >> panic: ARM64TODO: reclaim_pv_chunk >> cpuid =3D 2 >> KDB: stack backtrace: >> db_trace_self() at db_trace_self_wrapper+0x28 >> pc =3D 0xffff00000068b430 lr =3D 0xffff0000000631dc >> sp =3D 0xffff000083758080 fp =3D 0xffff000083758290 >>=20 >> db_trace_self_wrapper() at vpanic+0x170 >> pc =3D 0xffff0000000631dc lr =3D 0xffff000000335f10 >> sp =3D 0xffff0000837582a0 fp =3D 0xffff000083758320 >>=20 >> vpanic() at panic+0x4c >> pc =3D 0xffff000000335f10 lr =3D 0xffff000000335d9c >> sp =3D 0xffff000083758330 fp =3D 0xffff0000837583b0 >>=20 >> panic() at reclaim_pv_chunk+0x10 >> pc =3D 0xffff000000335d9c lr =3D 0xffff0000006a13d4 >> sp =3D 0xffff0000837583c0 fp =3D 0xffff0000837583c0 >>=20 >> reclaim_pv_chunk() at get_pv_entry+0x2bc >> pc =3D 0xffff0000006a13d4 lr =3D 0xffff00000069c270 >> sp =3D 0xffff0000837583d0 fp =3D 0xffff000083758400 >>=20 >> get_pv_entry() at pmap_enter+0x68c >> pc =3D 0xffff00000069c270 lr =3D 0xffff00000069b41c >> sp =3D 0xffff000083758410 fp =3D 0xffff0000837584b0 >>=20 >> pmap_enter() at vm_fault_hold+0x2f0 >> pc =3D 0xffff00000069b41c lr =3D 0xffff000000641eb8 >> sp =3D 0xffff0000837584c0 fp =3D 0xffff000083758600 >>=20 >> vm_fault_hold() at vm_fault_quick_hold_pages+0x120 >> pc =3D 0xffff000000641eb8 lr =3D 0xffff000000645004 >> sp =3D 0xffff000083758610 fp =3D 0xffff000083758670 >>=20 >> vm_fault_quick_hold_pages() at vn_io_fault1+0x250 >> pc =3D 0xffff000000645004 lr =3D 0xffff00000042b788 >> sp =3D 0xffff000083758680 fp =3D 0xffff0000837587c0 >>=20 >> vn_io_fault1() at vn_io_fault+0x170 >> pc =3D 0xffff00000042b788 lr =3D 0xffff0000004297a4 >> sp =3D 0xffff0000837587d0 fp =3D 0xffff000083758840 >>=20 >> vn_io_fault() at dofilewrite+0xbc >> pc =3D 0xffff0000004297a4 lr =3D 0xffff0000003a35e4 >> sp =3D 0xffff000083758850 fp =3D 0xffff000083758890 >>=20 >> dofilewrite() at kern_writev+0x6c >> pc =3D 0xffff0000003a35e4 lr =3D 0xffff0000003a32d4 >> sp =3D 0xffff0000837588a0 fp =3D 0xffff0000837588e0 >>=20 >> kern_writev() at sys_write+0x7c >> pc =3D 0xffff0000003a32d4 lr =3D 0xffff0000003a3258 >> sp =3D 0xffff0000837588f0 fp =3D 0xffff000083758930 >>=20 >> sys_write() at do_el0_sync+0x6fc >> pc =3D 0xffff0000003a3258 lr =3D 0xffff0000006a2778 >> sp =3D 0xffff000083758940 fp =3D 0xffff000083758a70 >>=20 >> do_el0_sync() at handle_el0_sync+0x64 >> pc =3D 0xffff0000006a2778 lr =3D 0xffff00000068d1d0 >> sp =3D 0xffff000083758a80 fp =3D 0xffff000083758b90 >>=20 >> handle_el0_sync() at 0x696ff0 >> pc =3D 0xffff00000068d1d0 lr =3D 0x0000000000696ff0 >> sp =3D 0xffff000083758ba0 fp =3D 0x0000ffffffffc610 >>=20 >> KDB: enter: panic >> [ thread pid 850 tid 100149 ] >> Stopped at kdb_enter+0x40: undefined d4200000 >=20 >=20 > Side notes: >=20 > To do the lang/gcc6 test I adjusted lang/gcc6/Makefile to (hopefully) = allow > an aarch64 build attempt: >=20 >> # svnlite diff /usr/ports/lang/gcc6 >> Index: /usr/ports/lang/gcc6/Makefile >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- /usr/ports/lang/gcc6/Makefile (revision 424540) >> +++ /usr/ports/lang/gcc6/Makefile (working copy) >> @@ -35,7 +35,7 @@ >> DISTVERSION=3D ${PORTVERSION:C/([0-9]+).*\.s([0-9]+)/\1-\2/} >> GCC_VERSION=3D ${PORTVERSION:C/(.+)\.s[0-9]{8}/\1/} >> SUFFIX=3D ${PORTVERSION:C/([0-9]+).*/\1/} >> -ONLY_FOR_ARCHS=3D amd64 i386 powerpc powerpc64 sparc64 arm armv6 = armv6hf >> +ONLY_FOR_ARCHS=3D amd64 i386 powerpc powerpc64 sparc64 arm armv6 = armv6hf aarch64 >> USES=3D compiler cpe gmake iconv libtool makeinfo perl5 = tar:bzip2 >> USE_BINUTILS=3D yes >> USE_PERL5=3D build >> @@ -73,7 +73,7 @@ >> USE_GCC=3D 4.9+ >> .endif >>=20 >> -.if ${ARCH} =3D=3D "armv6" || ${ARCH} =3D=3D "armv6hf" >> +.if ${ARCH} =3D=3D "armv6" || ${ARCH} =3D=3D "armv6hf" || ${ARCH} =3D=3D= "aarch64" >> . if ${COMPILER_TYPE} =3D=3D clang >> . if empty(PORT_OPTIONS:MBOOTSTRAP) >> MAKE_ARGS+=3DCXXFLAGS=3D-fbracket-depth=3D512 >=20 > It did not make it to lang/gcc6 itself but did build several things. >=20 > (I did not care if lang/gcc6 really worked or not: Environment = stability > test.) >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net There was fsck activity after cutting and applying power but luckily the = SSD content (largely) survived. The compressed message log shows the following as an example of when the = "gic0" Spurious interrupts start: > Nov 7 18:54:28 pine64 kernel: ugen3.2: at usbus3 > Nov 7 18:54:28 pine64 kernel: umass0 on uhub3 > Nov 7 18:54:28 pine64 kernel: umass0: on usbus3 > Nov 7 18:54:28 pine64 kernel: umass0: SCSI over Bulk-Only; quirks =3D = 0x0100 > Nov 7 18:54:28 pine64 kernel: umass0:0:0: Attached to scbus0 > Nov 7 18:54:28 pine64 kernel: mountroot: waiting for device = /dev/ufs/PINE642Grootfs... > Nov 7 18:54:28 pine64 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 = lun 0 > Nov 7 18:54:28 pine64 kernel: da0: Fixed = Direct Access SPC-4 SCSI device > Nov 7 18:54:28 pine64 kernel: da0: Serial Number > Nov 7 18:54:28 pine64 kernel: da0: 40.000MB/s transfers > Nov 7 18:54:28 pine64 kernel: da0: 228936MB (468862128 512 byte = sectors) > Nov 7 18:54:28 pine64 kernel: da0: quirks=3D0x2 > Nov 7 18:54:28 pine64 kernel: awg0: link state changed to DOWN > Nov 7 18:54:28 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU2 > Nov 7 18:54:28 pine64 kernel: awg0: link state changed to UP > Nov 7 18:54:28 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU3 > Nov 7 18:54:31 pine64 kernel: . > Nov 7 18:54:31 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU2 > Nov 7 18:54:31 pine64 ntpd[602]: ntpd 4.2.8p8-a (1): Starting > Nov 7 18:54:31 pine64 ntpd[603]: leapsecond file = ('/var/db/ntpd.leap-seconds.list'): good hash signature > Nov 7 18:54:31 pine64 ntpd[603]: leapsecond file = ('/var/db/ntpd.leap-seconds.list'): loaded, expire=3D2017-06-01T00:00:00Z = last=3D2017-01-01T00:00:00Z ofs=3D37 > Nov 7 19:36:17 pine64 kernel: gic0: gic0: Spurious interrupt = detected: last irq: 27 on CPU1 > Nov 7 19:36:17 pine64 kernel: Spurious interrupt detected: last irq: = 106 on CPU3 > Nov 7 19:36:17 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU1 > Nov 7 19:36:17 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU2 > Nov 7 19:36:17 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU0 > Nov 7 19:36:17 pine64 last message repeated 2 times > Nov 7 19:36:17 pine64 kernel: gic0: gic0: Spurious interrupt = detected: last irq: 27 on CPU0 > Nov 7 19:36:17 pine64 kernel: Spurious interrupt detected: last irq: = 27 on CPU3 Always shortly after awg0's link state changed to down after the da0 = information. In looking at the logs I've seen a 32 and some 114's and 92's as well as = the 27's and 106's. There were a few brief periods over which non-27's were fairly frequent. There are a few of the CAM status message blocks, about 7 over = everything recorded, including a few prior boots of the Pine64. An interesting point is that somewhat before and while the lang/gcc6 = related build activity was active the "gic0" notices stopped: > Nov 8 02:44:40 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 27 on CPU3 > Nov 8 03:01:15 pine64 kernel: pid 13900 (sh), uid 0: exited on signal = 11 (core dumped) > Nov 8 03:01:39 pine64 kernel: pid 19325 (sh), uid 0: exited on signal = 11 (core dumped) > Nov 8 03:02:02 pine64 pkg-static: indexinfo-0.2.5 installed > Nov 8 03:02:04 pine64 pkg-static: gettext-runtime-0.19.8.1 installed > Nov 8 03:04:42 pine64 kernel: pid 49697 (sh), uid 0: exited on signal = 11 (core dumped) > Nov 8 03:05:26 pine64 kernel: pid 68390 (sh), uid 0: exited on signal = 4 (core dumped) > Nov 8 03:06:10 pine64 kernel: pid 81149 (sh), uid 0: exited on signal = 11 (core dumped) > Nov 8 03:08:36 pine64 pkg-static: gettext-tools-0.19.8.1 installed > Nov 8 03:09:07 pine64 pkg-static: gmake-4.2.1_1 installed > Nov 8 03:27:01 pine64 pkg-static: perl5-5.24.1.r4 installed > Nov 8 03:27:33 pine64 pkg-static: p5-Locale-gettext-1.06 installed > Nov 8 03:27:42 pine64 pkg-static: help2man-1.43.3_1 installed > Nov 8 03:30:22 pine64 pkg-static: texinfo-6.1.20160425,1 installed > Nov 8 03:31:59 pine64 pkg-static: m4-1.4.17_1,1 installed > Nov 8 03:34:04 pine64 pkg-static: bison-2.7.1,1 installed > Nov 8 03:37:44 pine64 pkg-static: gmp-5.1.3_3 installed > Nov 8 03:39:14 pine64 pkg-static: mpfr-3.1.5 installed > Nov 8 03:44:53 pine64 kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: = 2a 00 16 bd 19 c0 00 00 80 00=20 > Nov 8 03:44:53 pine64 kernel: (da0:umass-sim0:0:0:0): CAM status: CCB = request completed with an error > Nov 8 03:44:53 pine64 kernel: (da0:umass-sim0:0:0:0): Retrying = command > Nov 8 03:44:55 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 106 on CPU3 > Nov 8 03:44:55 pine64 kernel: gic0: Spurious interrupt detected: last = irq: 106 on CPU3 Somewhat after the mpfr installation above the "gic0" notices return. devel/binutils started to build but did not complete. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Tue Nov 8 21:11:36 2016 Return-Path: Delivered-To: freebsd-arm@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 96985C37165 for ; Tue, 8 Nov 2016 21:11:36 +0000 (UTC) (envelope-from diffusae@yahoo.se) Received: from nm2-vm3.bullet.mail.ir2.yahoo.com (nm2-vm3.bullet.mail.ir2.yahoo.com [212.82.96.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 187DF1A0D for ; Tue, 8 Nov 2016 21:11:35 +0000 (UTC) (envelope-from diffusae@yahoo.se) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.se; s=s2048; t=1478639364; bh=cRZ3TIKZunkzSpAUI2GwNlZ17qjBaO52U2jA4l7uejE=; h=Reply-To:To:From:Subject:Date:From:Subject; b=FdPShWYNVjJQaRZ6tCyU2GG42GYx4CkniNaGd0XJe3kbfSU1jDBnw+FSgA2CAwDOpRzQE7UGh7bZw/cJLs45Vyj+YVyQdTytUUHGaUvJacZW+rbR9zy7dgoer3VrL7dX+W+sdgwcDz+mkEqfci66SG+k95k7MclL13v86YYZ39oRnYGqSSlUgOx/1bc2sU05fgc5On83Q1e7M+88wbH8xh7XQRvAvZGh02HSFZxqBtLpFzPYF1A5QRScxx+81VvjEjysCYn+61A8M43mScdqAl53V4AB+NpklMvhH5CAmdLjqJ+TsgI/CtAN9atZ+b5H9f52ogG5G3RkGUbvdxKcNQ== Received: from [212.82.98.58] by nm2.bullet.mail.ir2.yahoo.com with NNFMP; 08 Nov 2016 21:09:24 -0000 Received: from [46.228.39.89] by tm11.bullet.mail.ir2.yahoo.com with NNFMP; 08 Nov 2016 21:09:24 -0000 Received: from [127.0.0.1] by smtp126.mail.ir2.yahoo.com with NNFMP; 08 Nov 2016 21:09:24 -0000 X-Yahoo-Newman-Id: 438630.88146.bm@smtp126.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: KGDhsqgVM1kQ8631qKCeVUa7vFsHot4sPrYoaPziwkNtKTm 7uo5YsengGVYN.MHektoVlYJM9JMHxjuANBh6WUbggJIkTffGQK9.Y4GvUyl E9GRyk4VykmcPNyop0hwt1vfOd8PVU6UHYIVBEUv_D0ZBxDPl59ryOn1Prpu B70h2nl_KrTJTnEpiAtSe87kxH4DyW7xdZ6ZXdhjyCwB.yCOGsvgRBfO6f_Y yykvHOoc2NRuOiEuQT0Mkdr9x_4pHuwu_vv3tJotklqg60gPN6V7mCVr0vBS hny1HDvrcIK6aUJzNX6n1R4D6IQ.vLAph5SBTqUiZJxVbmX6KkUUGNjrc77z FY_V5kwFnj47talXZxfmD.s9LfeVCbCpDXXMTPgwaTk.SoRefZw5FysD8i8E EnF59NCvFqE5I5r4aeg8IiQ1r5.rouZ_3OXBu3WJQigb_isXPlpL.FaxWfPd 0iKNao0VYeMkSezsb4o5JtUMJeioVf2Kfg1SyTtRFu51_WqDd3xCj8wo6Rbu _hoqiiPcw8e8puVENPjQSDSPmnSmaovPP8pGBWuhtpgknGetKs3vbGfx6iqO lJaXc.qlltbyvFM5UGmCLxpBMhG7wIOdI X-Yahoo-SMTP: QGtXvluswBCI.2arnYPSSygOkYCV Reply-To: diffusae@yahoo.se To: freebsd-arm From: diffusae Subject: Change MAC Adresse on RPI-B Message-ID: <9ad18046-77e1-7c6f-4657-8571afb5c35f@yahoo.se> Date: Tue, 8 Nov 2016 22:09:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 21:11:36 -0000 Hello! Does anyboy know how to change the MAC address on a Raspberry Pi with FreeBSD 11.0-STABLE? I've tried it in /etc/start_if.ue0 this way: ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 But it's only possible to do it in promicous mode of the device. Without there is no more network connection after applying these settings. It could be properly a bug due to the USB network driver. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 Maybe there is another way, how with the Linux kernel command line or an config option, like this: smsc95xx.macaddr=00:FF:CC:00:11:11. Regards, From owner-freebsd-arm@freebsd.org Tue Nov 8 21:18:40 2016 Return-Path: Delivered-To: freebsd-arm@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 84592C374E5 for ; Tue, 8 Nov 2016 21:18:40 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C54D1F88 for ; Tue, 8 Nov 2016 21:18:39 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd05.aul.t-online.de (fwd05.aul.t-online.de [172.20.27.149]) by mailout02.t-online.de (Postfix) with SMTP id 4A27841AC31C for ; Tue, 8 Nov 2016 22:12:21 +0100 (CET) Received: from [192.168.10.43] (E2kXkvZEQhADVgfeVB9TIg74r5iL48WgLEKYrHG99kEJa9pamlpAyGkfr7V4oJYwcC@[86.56.56.128]) by fwd05.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4Dgk-3syLEe0; Tue, 8 Nov 2016 22:12:14 +0100 To: freebsd-arm From: diffusae Subject: How to change MAC address on RPI-B? Message-ID: <950d3edd-6b54-4935-ffec-bfcfbd257bb7@t-online.de> Date: Tue, 8 Nov 2016 22:12:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: E2kXkvZEQhADVgfeVB9TIg74r5iL48WgLEKYrHG99kEJa9pamlpAyGkfr7V4oJYwcC X-TOI-MSGID: 004a2096-56ad-401e-99e9-d4908e4dbd4b X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 21:18:40 -0000 Hello! Does anyboy know how to change the MAC address on a Raspberry Pi with FreeBSD 11.0-STABLE? I've tried it this way in /etc/start_if.ue0: ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 But it's only possible to do it in promicous mode of the device. Without there is no more network connection after applying these settings. It could be properly a bug due to the USB network driver. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 Maybe there is another way, how with the Linux kernel command line or an config option, like this: smsc95xx.macaddr=00:FF:CC:00:11:11. Regards, From owner-freebsd-arm@freebsd.org Tue Nov 8 21:30:10 2016 Return-Path: Delivered-To: freebsd-arm@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 9C3EBC378A9 for ; Tue, 8 Nov 2016 21:30:10 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 6797683C for ; Tue, 8 Nov 2016 21:30:09 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (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 B2E2B1FE022; Tue, 8 Nov 2016 22:30:01 +0100 (CET) Subject: Re: How to change MAC address on RPI-B? To: diffusae , freebsd-arm References: <950d3edd-6b54-4935-ffec-bfcfbd257bb7@t-online.de> From: Hans Petter Selasky Message-ID: Date: Tue, 8 Nov 2016 22:35:12 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <950d3edd-6b54-4935-ffec-bfcfbd257bb7@t-online.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 21:30:10 -0000 On 11/08/16 22:12, diffusae wrote: > Hello! > > Does anyboy know how to change the MAC address on a Raspberry Pi with > FreeBSD 11.0-STABLE? > > I've tried it this way in /etc/start_if.ue0: > > ifconfig ue0 down delete > ifconfig ue0 promisc > ifconfig ue0 ether 00:FF:CC:00:11:11 > > But it's only possible to do it in promicous mode of the device. > Without there is no more network connection after applying these settings. > > It could be properly a bug due to the USB network driver. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 > > Maybe there is another way, how with the Linux kernel command line or an > config option, like this: smsc95xx.macaddr=00:FF:CC:00:11:11. Hi, The sys/dev/usb/net/if_smsc.c driver needs a patch to set the mac address runtime. I think you can change the mac address in the RPI FDT file and it will pick it up. --HPS From owner-freebsd-arm@freebsd.org Tue Nov 8 21:48:41 2016 Return-Path: Delivered-To: freebsd-arm@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 19D5EC37E0B for ; Tue, 8 Nov 2016 21:48:41 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout08.t-online.de (mailout08.t-online.de [194.25.134.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D32C2876 for ; Tue, 8 Nov 2016 21:48:40 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd21.aul.t-online.de (fwd21.aul.t-online.de [172.20.27.66]) by mailout08.t-online.de (Postfix) with SMTP id 939AA41D008D; Tue, 8 Nov 2016 22:48:31 +0100 (CET) Received: from [192.168.10.43] (SaTXqqZHwhC5NnaWNcPiaZUNoM+efrpD+0vfLTL6FDjNY2S8wh7k28gNst+TiBkZGv@[86.56.56.128]) by fwd21.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4EFp-2nv9qy0; Tue, 8 Nov 2016 22:48:29 +0100 Subject: Re: How to change MAC address on RPI-B? To: Hans Petter Selasky , freebsd-arm References: <950d3edd-6b54-4935-ffec-bfcfbd257bb7@t-online.de> From: diffusae Message-ID: <42c16f3e-0419-c23a-adf4-a32d436651ea@t-online.de> Date: Tue, 8 Nov 2016 22:48:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: SaTXqqZHwhC5NnaWNcPiaZUNoM+efrpD+0vfLTL6FDjNY2S8wh7k28gNst+TiBkZGv X-TOI-MSGID: 8024220e-0db5-4b6d-b543-c9158ee77b76 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 21:48:41 -0000 Hi, thanks a lot for your reply. I'm not sure, if it's possible to change it in RPI FDT file, but I will give a try: https://www.raspberrypi.org/forums/viewtopic.php?f=72&t=143011 The MAC address isn't stored anywhere. It is generated from a combination of the MAC range (b8:27:eb) and the last three bytes of the serial number. Best regards, On 08.11.2016 22:35, Hans Petter Selasky wrote: > On 11/08/16 22:12, diffusae wrote: >> Hello! >> >> Does anyboy know how to change the MAC address on a Raspberry Pi with >> FreeBSD 11.0-STABLE? >> >> I've tried it this way in /etc/start_if.ue0: >> >> ifconfig ue0 down delete >> ifconfig ue0 promisc >> ifconfig ue0 ether 00:FF:CC:00:11:11 >> >> But it's only possible to do it in promicous mode of the device. >> Without there is no more network connection after applying these >> settings. >> >> It could be properly a bug due to the USB network driver. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 >> >> Maybe there is another way, how with the Linux kernel command line or an >> config option, like this: smsc95xx.macaddr=00:FF:CC:00:11:11. > > Hi, > > The sys/dev/usb/net/if_smsc.c driver needs a patch to set the mac > address runtime. I think you can change the mac address in the RPI FDT > file and it will pick it up. > > --HPS > > From owner-freebsd-arm@freebsd.org Wed Nov 9 10:58:53 2016 Return-Path: Delivered-To: freebsd-arm@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 6B355C37CA4 for ; Wed, 9 Nov 2016 10:58:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 517DE13A for ; Wed, 9 Nov 2016 10:58:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uA9AwrFE038902 for ; Wed, 9 Nov 2016 10:58:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 214356] Non-optimal partition alignment in RPI2 image Date: Wed, 09 Nov 2016 10:58:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jason.mann+freebsd@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 10:58:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214356 Bug ID: 214356 Summary: Non-optimal partition alignment in RPI2 image Product: Base System Version: 11.0-RELEASE Hardware: arm OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: jason.mann+freebsd@gmail.com The prebuilt image file for FreeBSD 11.0-RELEASE for the Raspberry Pi 2 contains the following partition layout: =3D> 63 2097089 md0 MBR (1.0G) 63 102375 1 !12 [active] (50M) 102438 1994714 2 freebsd (974M) =3D> 0 1994714 md0s2 BSD (974M) 0 90 - free - (45K) 90 1994496 1 freebsd-ufs (974M) 1994586 128 - free - (64K) The partitions are not aligned to any typical power-of-two flash page sizes, which may lead to write amplification, decreasing write performance and increasing the wear rate on the microSD card. Slice 1, containing the firmware and bootloader, has an offset of 63 sector= s.=20 This is probably in line with old MBR partitioning using CHS addressing, but LBA has long since made this practice obsolete. Most mainstream OSs now us= e an offset of 2048 sectors for the first MBR slice. Slice 2 has an offset of 102438 sectors, and is further sub-partitioned usi= ng the BSD scheme. BSD partition 1 has an offset of 90 sectors from the begin= ning of slice 2, for a total device offset of 102528 sectors. SD cards commonly have a flash erase block size of 4MiB, so it may be beneficial for the partitions to be aligned to multiples of 4MiB. This may= be less important for slice 1 which is usually only read from at boot, but very important for slice 2 partition 1 which contains the read/write root filesystem. I have tried recreating the RPI2 image with altered partitioning, as follow= s: =3D> 63 2097089 md1 MBR (1.0G) 63 8129 - free - (4.0M) 8192 122880 1 !12 [active] (60M) 131072 1966080 2 freebsd (960M) =3D> 0 1966080 md1s2 BSD (960M) 0 1966080 1 freebsd-ufs (960M) After copying the partition contents from the official image, then writing = the new image to an SD card, my RPI2 was still able to successfully boot from i= t. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Nov 9 11:37:11 2016 Return-Path: Delivered-To: freebsd-arm@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 4BCBDC38879 for ; Wed, 9 Nov 2016 11:37:11 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB12D9BB for ; Wed, 9 Nov 2016 11:37:10 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 5nbu1u00P4VixDu01nbwNX; Wed, 09 Nov 2016 12:35:56 +0100 Reply-To: From: "John W. Kitz" To: Subject: How to change MAC address on RPI-B? Date: Wed, 9 Nov 2016 12:35:56 +0100 Message-ID: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI6fW+teEMgsnQnQtCJaL6ZKd6lfg== Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 11:37:11 -0000 Hi, I saw a couple of emails whizz by, which discussed how to override the burned in MAC address (BIA) on an RPI-B. First off I'm not familiar with the use or configuration of either a Pi or FreeBSD, but to me it looked like in the emails a dependency between two techniques, i.e. overriding the BIA of a NIC and configuring a NIC into promiscuous mode, was made while such a dependency does not or at least, to the best of my knowledge, should not exist. I used, what in IBM lingo is referred to as a locally administered MAC addresses, numerous times predominantly in the nineties of the previous century in datacenter environments using equipment from big blue or its plug compatible competitors, while such equipment exclusively used IBM's Systems Network Architecture (SNA), i.e. non TCP/IP, protocols. To the best of my recollection at the time there was no need whatsoever to configure these NICs into promiscuous mode, which in itself is needed to have a NIC consider frames that aren't destined for the NIC's BIA address as if they were, so I doubt that such a need exists today. I hope this helps, regards, Jk. From owner-freebsd-arm@freebsd.org Wed Nov 9 12:32:07 2016 Return-Path: Delivered-To: freebsd-arm@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 33B3BC366C8 for ; Wed, 9 Nov 2016 12:32:07 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C7DB2EF4 for ; Wed, 9 Nov 2016 12:32:06 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 5oY11u0054VixDu01oY3US; Wed, 09 Nov 2016 13:32:03 +0100 Reply-To: From: "John W. Kitz" To: References: In-Reply-To: Subject: How to change MAC address on RPI-B? Date: Wed, 9 Nov 2016 13:31:56 +0100 Message-ID: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI6fW+teEMgsnQnQtCJaL6ZKd6lfgABiDxQ Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 12:32:07 -0000 Hi, Further to my earlier email on this topic and assuming you haven't already done so, you may need to have a look at https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/FreeBSD as well as at, a more UNIX flavor independent, discussion of the topic at https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/Linux, which also specifically addresses how to make overriding the burned-in MAC address persistent. In addition I noticed that the MAC address, which you are trying to use instead of the burned-in one, contains 'FF', which, given its use in functional MAC addresses used for broadcast type purposes, might not be such a good idea. I hope this helps, regards, Jk. From owner-freebsd-arm@freebsd.org Wed Nov 9 15:55:01 2016 Return-Path: Delivered-To: freebsd-arm@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 07D96C37563 for ; Wed, 9 Nov 2016 15:55:01 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 90BCEDA for ; Wed, 9 Nov 2016 15:55:00 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id p190so316647112wmp.1 for ; Wed, 09 Nov 2016 07:55:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=1t1AHGpTmR8nHu0sOsmUoafT+lcJrJ9CbU9AkMp9IPg=; b=FGo+Y9246VowJczTXg2APgltgaBFuxTqfbGHLoOhyg/8Cy4fN9mit5PwW4lwlGgCS8 a+B6RngbtycMFaobiy3gd68R9gdx+hA5LziTI5rDTIUZATYA0Xk4ZdC0wcneH9Qj/IO8 piFLQu5iRh2kKPggPobi5VgkSrVsXqt6BS4ZVAnTZOl0PQ561FOuBV/9PCxxYcR0/LoY UhznGH6vf6L146eC1tDi1eXkYEo1cBWtRYVtUmo5kf80w1v25GnDiYP0DD5ByzN/GFhL 9XWfFLTuAIV6qowh1Em6qf4a5n4eeI1l5aTOy2Yfn5yr6ufcWahTEZn13gDl7iSTIo5k ydqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:to:from:subject:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=1t1AHGpTmR8nHu0sOsmUoafT+lcJrJ9CbU9AkMp9IPg=; b=JHXVbesgQGCMe6lT2D41b91nYMrIMpBVJVQWNC/03IxL01UhVG1/6gjf2GBBrDUdVm 3pw0Y3iI4u3myHDYDtrtGBlth+4rWDuC+WPArhy+6mvflETBCZEZCTbyl4lSJNKHrUhF LiUpp90xja6gZ4HwsVvDVM6parwBT+SNM0zL2Xzqs7mZWVcQpjUe1/Mtj0ScCxIZ7PNy hPNiJzQDimC7JlgZ7JgrCDYre+y1owt0m6JDVSPnBVakPM2UX2LiQnNiZlAmN3rLxkhE v2dIrOudnL0mxlPP1VtDVWvU5Y5CppyDtajVmB3ri36daPh6nNS0rn3tyvQ7cS4SHWUy bWaA== X-Gm-Message-State: ABUngveIcHnlctDGyAdrJ/0QEmmSRxQ7Khn4+X7k9VoowqlNByqnFtHV8FU8mffBDzy8Dg== X-Received: by 10.194.189.83 with SMTP id gg19mr191411wjc.165.1478706898092; Wed, 09 Nov 2016 07:54:58 -0800 (PST) Received: from ?IPv6:2001:1620:ff0:c51:7420:f92c:e590:9ebc? ([2001:1620:ff0:c51:7420:f92c:e590:9ebc]) by smtp.gmail.com with ESMTPSA id jq10sm169657wjb.46.2016.11.09.07.54.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Nov 2016 07:54:57 -0800 (PST) Reply-To: mattia.rossi.mailinglists@gmail.com To: freebsd-arm From: Mattia Rossi Subject: Allwinner H3 (orangepi-plus-2) SD card issue - kernel related Message-ID: Date: Wed, 9 Nov 2016 16:54:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 15:55:01 -0000 Hi all, Finally had the guts to rebuild world, kernel (r308464M) and with that the .dtb file, and trying to boot using the generated .dtb file. The good news is: The system boots! The bad news: a) It loses a lot of time searching for the SD card partitions (or whatever it does here), then it continues in the boot process. What's wrong? usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 mmcsd0: 16GB at mmc0 50.0MHz/4bit/65535-block a10_mmc1: error rint: 0x00000100 uhub0: 1 port with 1 removable, self powered uhub1: 1 port with 1 removable, self powered ugen1.2: at usbus1 umass0 on uhub1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0xc100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI device da0: Serial Number 000000000033 da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da0: quirks=0x2 a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout a10_mmc1: controller timeout mmc1: No compatible cards found on bus a10_mmc2: error rint: 0x00000100 a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout a10_mmc2: controller timeout mmc2: No compatible cards found on bus Release APs WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/mmcsd0s2 [rw]... b) No Ethernet Device! What do I have to add (to the .dts i guess) to get that back? 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 groups: lo nd6 options=21 Appreciate any help, Mat From owner-freebsd-arm@freebsd.org Wed Nov 9 21:26:54 2016 Return-Path: Delivered-To: freebsd-arm@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 5AD64C3828D for ; Wed, 9 Nov 2016 21:26:54 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout09.t-online.de (mailout09.t-online.de [194.25.134.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F0C4E30 for ; Wed, 9 Nov 2016 21:26:53 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd22.aul.t-online.de (fwd22.aul.t-online.de [172.20.26.127]) by mailout09.t-online.de (Postfix) with SMTP id 977BF426A38C for ; Wed, 9 Nov 2016 22:24:44 +0100 (CET) Received: from [192.168.10.43] (TFo0B6ZAohZuMxdkArKI2A2SDP9y05KcyiU-JIIDY8XPHHFImm3z74RicOrGh3IwiQ@[86.56.56.128]) by fwd22.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4aMN-3zzdei0; Wed, 9 Nov 2016 22:24:43 +0100 Subject: Re: How to change MAC address on RPI-B? References: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> To: freebsd-arm@freebsd.org From: diffusae Message-ID: Date: Wed, 9 Nov 2016 22:24:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: TFo0B6ZAohZuMxdkArKI2A2SDP9y05KcyiU-JIIDY8XPHHFImm3z74RicOrGh3IwiQ X-TOI-MSGID: a742746f-908e-43d1-8af1-c8be417a439b X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 21:26:54 -0000 Hi! Thanks for you reply. On 09.11.2016 13:31, John W. Kitz wrote: > https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/FreeBSD as well as > at, a more UNIX flavor independent, discussion of the topic at That's the way it works. You could do this on the RPi, but after that you haven't no more network connection. It's like Hans Petter said: The sys/dev/usb/net/if_smsc.c driver needs a patch to set the mac address runtime. I don't know, how to write it, because I am not really familiar with C source code. > https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/Linux, which also > specifically addresses how to make > persistent. In all flavour of Linux that should work, without problems on the RPi. You could set the MAC address from the kernel command line. > In addition I noticed that the MAC address, which you are trying to use > instead of the burned-in one, contains 'FF', which, given its use in > functional MAC addresses used for broadcast type purposes, might not be such > a good idea. Really, that I don't know. I only use it, as an example, instead of 00:11:22:33:44:55. Overriding the burned-in MAC address persistent on a RPi wouldn't work, because it is generated from a combination of the MAC range (b8:27:eb) and the last three bytes of the serial number. But it should be possible to change this in this RPi FTD file, then it might work. Best regards, From owner-freebsd-arm@freebsd.org Wed Nov 9 22:18:10 2016 Return-Path: Delivered-To: freebsd-arm@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 692B0C380DD for ; Wed, 9 Nov 2016 22:18:10 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb2-smtp-cloud3.xs4all.net (lb2-smtp-cloud3.xs4all.net [194.109.24.26]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EBE9BBC for ; Wed, 9 Nov 2016 22:18:09 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud3.xs4all.net with ESMTP id 5yGu1u0034VixDu01yGvNJ; Wed, 09 Nov 2016 23:16:56 +0100 Reply-To: From: "John W. Kitz" To: References: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> In-Reply-To: Subject: RE: How to change MAC address on RPI-B? Date: Wed, 9 Nov 2016 23:16:50 +0100 Message-ID: <000001d23ad6$fce27e80$f6a77b80$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI60AUUYek2BTnARy689OpFzgAeMwAA163w Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 22:18:10 -0000 > https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/FreeBSD as > well as at, a more UNIX flavor independent, discussion of the topic at That's the way it works. You could do this on the RPi, but after that you haven't no more network connection. JKi: Could the information on the two sites that I sent you be an indication that it may work as you intend it to if you configure a locally administered MAC address to override the burned-in one OR promiscuous mode and not both at the same time? At least that is what I interpret the information in the initial emails of this thread to mean. It's like Hans Petter said: The sys/dev/usb/net/if_smsc.c driver needs a patch to set the mac address runtime. I don't know, how to write it, because I am not really familiar with C source code. > https://en.wikibooks.org/wiki/Changing_Your_MAC_Address/Linux, which > also specifically addresses how to make persistent. In all flavour of Linux that should work, without problems on the RPi. You could set the MAC address from the kernel command line. > In addition I noticed that the MAC address, which you are trying to > use instead of the burned-in one, contains 'FF', which, given its use > in functional MAC addresses used for broadcast type purposes, might > not be such a good idea. Really, that I don't know. JKi: Neither do I, but as mentioned I imagined that it wouldn't. I only use it, as an example, instead of 00:11:22:33:44:55. Overriding the burned-in MAC address persistent on a RPi wouldn't work, because it is generated from a combination of the MAC range (b8:27:eb) and the last three bytes of the serial number. JKi: Doesn't that depend on the sequence of events at boot time? In addition, not being familiar with the specifics of this generating of a MAC address that you mention, I'm curious how does this process guarantee a globally unique MAC address as its result, bearing in mind that a MAC address in principle is supposed to be either functional (such as for the purpose of broadcasting), locally administered or globally unique? But it should be possible to change this in this RPi FTD file, then it might work. JKi: I'm curious, are you just in the process of confirming that it can be done or do you actually have some purpose for this and if yes, what is it? Best regards, _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Wed Nov 9 22:25:51 2016 Return-Path: Delivered-To: freebsd-arm@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 A9320C383D1 for ; Wed, 9 Nov 2016 22:25:51 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::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 71336787 for ; Wed, 9 Nov 2016 22:25:51 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id q124so301895557itd.1 for ; Wed, 09 Nov 2016 14:25:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6G4xHFTILy0iyViJKMKxQjeXRNloFzfG+3JYzcc6pNo=; b=BeiAcLJekXn8Dm0sJbNYlRin2ORt2lzELZG+vHh4xHHcj5xk+Z4wJS0rmWdgzc286Q GrXJ6vWazTKdViU2vx60MhCmZmWuhgiB0XBWsr2eXlJJ/pZbWctuWdVF5p61aPZGXOsP cjoHG3KbqgwyerxT2dgk2JdKL4rGgTeljiJhSoIPIwKkQ//b1I2ElAQzJBsW67Vr8k6/ ahGpPBMur6/MTGRHbKnKn0hsdss5vLkK8+P8Wd+QneavBMgBPIMh2BgmMi176Oo5MMaF 6VlJd/k6ytp8UW4KQhq+4hqZ4fM2iedpPYY7q7JI41CxjBAk36O7RoCn4vAlMyhAfIBu flxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6G4xHFTILy0iyViJKMKxQjeXRNloFzfG+3JYzcc6pNo=; b=S3ZDDBh67+vaQJXMUH0v7sz5yxRI6J9b7OpYSr0l+XNWzuSxov7H7dyG7olTc4wOut gW6aNVLWrXa+lpWbTq/M8E76GH6r4hT/Tw2oAN/j1iYoyhWuyu7UrgkXNDVpFmLZA0S8 +QKgm0JGuq/F1842wllroktM4xyK/qgPIFVH204lOyr+Y9kjPlmOBhdpYz7uD1p+qAwV iqNzZEkvLZjp8bwDjOn7H6LYQQfoz3AppbJ7E3LIUOMo5K3j98eG0FlF0h5iTSbG7g/J IRjJVS28unSUIHhLLlDP0c1UbezanSti3CUC0BRkldfBRHOvUwFvXeYrdVXaH+b19qWe LXUg== X-Gm-Message-State: ABUngveIX3swlPYlvHk2nWOtvI/2rmrAaJf/9qivpWChaE+xqu6p3ojzxPW1hh9+HljGEajaYLDdTJLwuMohsA== X-Received: by 10.36.102.2 with SMTP id k2mr15979120itc.114.1478730350776; Wed, 09 Nov 2016 14:25:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.26.199 with HTTP; Wed, 9 Nov 2016 14:25:50 -0800 (PST) In-Reply-To: <20161106210341.0c452da473c3313165bf3f8c@ulrich-grey.de> References: <20161106210341.0c452da473c3313165bf3f8c@ulrich-grey.de> From: Svatopluk Kraus Date: Wed, 9 Nov 2016 23:25:50 +0100 Message-ID: Subject: Re: FreeBSD 11.0-STABLE #0 r307979M: panic: vm_radix_remove: impossible to locate the key To: Ulrich Grey Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 22:25:51 -0000 Thanks for report. Just to be sure, am I right that the kernel was built without INVARIANTS option? Svata On Sun, Nov 6, 2016 at 9:03 PM, Ulrich Grey wrote: > Hello, > > I am running: > > freebsd@worktest:~ % uname -ap > FreeBSD worktest 11.0-STABLE FreeBSD 11.0-STABLE #0 r307979M: Thu Oct 27 09:04:38 UTC > 2016 freebsd@worktest:/usr/local/DEVEL/obj/usr/local/DEVEL/SRC/11/sys/IMX6 arm armv6 > > on a CUBOX. > > After > 50 hours building ports I got a panic: > > panic: vm_radix_remove: impossible to locate the key > cpuid = 0 > KDB: stack backtrace: > db_trace_self() at db_trace_self > pc = 0xc259e47c lr = 0xc205d1f8 (db_trace_self_wrapper+0x30) > sp = 0xfbbe98b8 fp = 0xfbbe99d0 > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > pc = 0xc205d1f8 lr = 0xc2216f98 (vpanic+0x13c) > sp = 0xfbbe99d8 fp = 0xfbbe99f8 > r4 = 0x00000100 r5 = 0xc7a356e0 > r6 = 0xc265c1c6 r7 = 0x00000001 > vpanic() at vpanic+0x13c > pc = 0xc2216f98 lr = 0xc2216e5c (vpanic) > sp = 0xfbbe9a00 fp = 0xfbbe9a04 > r4 = 0xe086130c r5 = 0x00000000 > r6 = 0x000c585c r7 = 0xc287a720 > r8 = 0x00000001 r9 = 0xc7b8dc5c > r10 = 0x00000018 > vpanic() at vpanic > pc = 0xc2216e5c lr = 0xc258fc9c (vm_radix_remove+0x1c8) > sp = 0xfbbe9a0c fp = 0xfbbe9a28 > r4 = 0xc287a720 r5 = 0x00000001 > r6 = 0xc7b8dc5c r7 = 0x00000018 > r8 = 0xfbbe9a04 r9 = 0xc2216e5c > r10 = 0xfbbe9a0c > vm_radix_remove() at vm_radix_remove+0x1c8 > pc = 0xc258fc9c lr = 0xc257fbbc (vm_page_remove+0x34) > sp = 0xfbbe9a30 fp = 0xfbbe9a38 > r4 = 0xc2c48a50 r5 = 0xca5c1f18 > r6 = 0x000c585c r7 = 0xc287a720 > vm_page_remove() at vm_page_remove+0x34 > pc = 0xc257fbbc lr = 0xc257ee90 (vm_page_free_toq+0x5c) > sp = 0xfbbe9a40 fp = 0xfbbe9a58 > r4 = 0xc2c48a50 r5 = 0xc2c48a50 > vm_page_free_toq() at vm_page_free_toq+0x5c > pc = 0xc257ee90 lr = 0xc25b5f90 (free_pv_chunk+0x168) > sp = 0xfbbe9a60 fp = 0xfbbe9a70 > r4 = 0xc585c000 r5 = 0xc2c48a50 > r6 = 0x000c585c r10 = 0x00000018 > free_pv_chunk() at free_pv_chunk+0x168 > pc = 0xc25b5f90 lr = 0xc25b5c0c (pmap_remove_pages+0x66c) > sp = 0xfbbe9a78 fp = 0xfbbe9ad0 > r4 = 0x00000000 r5 = 0x00000000 > r6 = 0xc3ae6170 r7 = 0x56adcc33 > pmap_remove_pages() at pmap_remove_pages+0x66c > pc = 0xc25b5c0c lr = 0xc256ad00 (vmspace_exit+0xc8) > sp = 0xfbbe9ad8 fp = 0xfbbe9af8 > r4 = 0xc7b8dc58 r5 = 0x00000001 > r6 = 0xc285e650 r7 = 0xcab14000 > r8 = 0xc7b8dc5c r9 = 0xc7b8dba0 > r10 = 0xc7a356e0 > vmspace_exit() at vmspace_exit+0xc8 > pc = 0xc256ad00 lr = 0xc21bbdf8 (exit1+0xb9c) > sp = 0xfbbe9b00 fp = 0xfbbe9b58 > r4 = 0xc7a356e0 r5 = 0x00000004 > r6 = 0xc7a356e0 r7 = 0xcab14000 > r8 = 0xcab140bc r9 = 0xc707825c > r10 = 0xcab140ac > exit1() at exit1+0xb9c > pc = 0xc21bbdf8 lr = 0xc221bc78 ($a.5+0x934) > sp = 0xfbbe9b60 fp = 0xfbbe9d38 > r4 = 0xfbbe9c88 r5 = 0x00000000 > r6 = 0x00000005 r7 = 0xc261d701 > r8 = 0xc7a356e0 r9 = 0x0000000b > r10 = 0xc7a356e0 > $a.5() at $a.5+0x934 > pc = 0xc221bc78 lr = 0xc221cc5c (osigsuspend) > sp = 0xfbbe9d40 fp = 0xfbbe9dd0 > r4 = 0x0000000b r5 = 0xc7a356e0 > r6 = 0xc7a356e0 r7 = 0xcab14000 > r8 = 0xcb01aab8 r9 = 0x00020804 > r10 = 0x00000000 > osigsuspend() at osigsuspend > pc = 0xc221cc5c lr = 0xc22865cc (ast+0x620) > sp = 0xfbbe9dd8 fp = 0xfbbe9e00 > ast() at ast+0x620 > pc = 0xc22865cc lr = 0xc25a0da4 (exception_exit+0x40) > sp = 0xfbbe9e08 fp = 0xbfbfdf28 > r4 = 0x60000113 r5 = 0xc7a356e0 > r6 = 0x00000000 r7 = 0x2003a200 > r8 = 0x20035bc4 r9 = 0x20036718 > r10 = 0x20036700 > exception_exit() at exception_exit+0x40 > pc = 0xc25a0da4 lr = 0x200287ec (0x200287ec) > sp = 0xfbbe9e98 fp = 0xbfbfdf28 > r0 = 0x00000000 r1 = 0x00000000 > r2 = 0x00000000 r3 = 0x00000002 > r4 = 0x00000002 r5 = 0xbfbfe3d8 > r6 = 0x00000000 r7 = 0x2003a200 > r8 = 0x20035bc4 r9 = 0x20036718 > r10 = 0x20036700 r12 = 0x2003a200 > Unable to unwind into user mode > KDB: enter: panic > [ thread pid 17915 tid 100894 ] > Stopped at $d.6: ldrb r15, [r15, r15, ror r15]! > db> show all pcpu > ... > > For further information please see: > http://ulrich-grey.de/dl/cubox_panic20161106.log > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Wed Nov 9 22:51:25 2016 Return-Path: Delivered-To: freebsd-arm@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 0A77EC38BD1 for ; Wed, 9 Nov 2016 22:51:25 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (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 E10B82FE for ; Wed, 9 Nov 2016 22:51:24 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=CrYKJ+wGLt7lD1IBSbrSppxLJR0oR+j8RDpyS5CTBSU=; b=xRTww2fl0jhtVQPdHXHx3u5x5t DQR/sxwsOCQnLx5aEq71XqXLFVhUMXKEITMoo71cwWoDaj5gE2jA+2E5o5jkvTnSBxWd8gIKVCCgG AmOlaN9whjv6DAJWvw72Mso80Z10ZJWpT6ElRecpohyByKljNx2Mf+mv6MdUayA5520o=; Received: from [114.125.112.194] (port=32753 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1c4bi9-003K6o-Ll; Wed, 09 Nov 2016 15:51:18 -0700 Date: Thu, 10 Nov 2016 06:51:05 +0800 From: Erich Dollansky To: "John W. Kitz" Cc: Subject: Re: How to change MAC address on RPI-B? Message-ID: <20161110065105.77a19e3b@X220.alogt.com> In-Reply-To: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 22:51:25 -0000 Hi, On Wed, 9 Nov 2016 12:35:56 +0100 "John W. Kitz" wrote: > To the best of my recollection at the time there was no need > whatsoever to configure these NICs into promiscuous mode, which in you need this for fault-tolerant computing. A machine or a device with a known goes down, the failure will be detected and another device or machine is configured to take over the other's task by also taking over the other's MAC address. The communication partners will only a delay but not a failure. Erich From owner-freebsd-arm@freebsd.org Wed Nov 9 23:41:28 2016 Return-Path: Delivered-To: freebsd-arm@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 66553C37E64 for ; Wed, 9 Nov 2016 23:41:28 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 090F5ED for ; Wed, 9 Nov 2016 23:41:27 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1478734884; l=4863; s=domk; d=ulrich-grey.de; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References: In-Reply-To:Subject:Cc:To:From:Date; bh=f7tfDuFgtV4V+EeJEG5aTuW80U+epVOlbmOMJgpTtGA=; b=NQFUGe7brSGgPdh3Q9SLB2Dfbd8fc5+81cwuoGJkzRw7R7pK/pjQS/mh3U3ZdCVWbb NexA3/kEuzu14JCwCUdB/NFJPjGSs28N1sfJccaqEdHZrCmHcb9AtzKAfB0Rw0Qntp7E sl5MB7V3XdIx9mbwevvdgFa+oxI9fARJQx1SQ= X-RZG-AUTH: :OX8Be0W8W+pMC3rDLL/lo2xV/LZTbZkYhOcjg8suic3iYr/B8J9Lzp3TJg49sMv/cWqf X-RZG-CLASS-ID: mo00 Received: from work (p54869EBE.dip0.t-ipconnect.de [84.134.158.190]) by smtp.strato.de (RZmta 39.9 DYNA|AUTH) with ESMTPSA id U05fc6sA9NfN9Y6 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Thu, 10 Nov 2016 00:41:23 +0100 (CET) Date: Thu, 10 Nov 2016 00:41:22 +0100 From: Ulrich Grey To: Svatopluk Kraus Cc: "freebsd-arm@freebsd.org" Subject: Re: FreeBSD 11.0-STABLE #0 r307979M: panic: vm_radix_remove: impossible to locate the key Message-Id: <20161110004122.ec5075bcd4ec91647a2eebf3@ulrich-grey.de> In-Reply-To: References: <20161106210341.0c452da473c3313165bf3f8c@ulrich-grey.de> Organization: - X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; armv6-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 23:41:28 -0000 On Wed, 9 Nov 2016 23:25:50 +0100 Svatopluk Kraus wrote: > Thanks for report. Just to be sure, am I right that the kernel was > built without INVARIANTS option? > > Svata > I have used the default IMX6 kernel for 11.0-STABLE, these options added: options DDB options USB_DEBUG options USB_VERBOSE No INVARIANTS option. > On Sun, Nov 6, 2016 at 9:03 PM, Ulrich Grey wrote: > > Hello, > > > > I am running: > > > > freebsd@worktest:~ % uname -ap > > FreeBSD worktest 11.0-STABLE FreeBSD 11.0-STABLE #0 r307979M: Thu Oct 27 09:04:38 UTC > > 2016 freebsd@worktest:/usr/local/DEVEL/obj/usr/local/DEVEL/SRC/11/sys/IMX6 arm > > armv6 > > > > on a CUBOX. > > > > After > 50 hours building ports I got a panic: > > > > panic: vm_radix_remove: impossible to locate the key > > cpuid = 0 > > KDB: stack backtrace: > > db_trace_self() at db_trace_self > > pc = 0xc259e47c lr = 0xc205d1f8 (db_trace_self_wrapper+0x30) > > sp = 0xfbbe98b8 fp = 0xfbbe99d0 > > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > > pc = 0xc205d1f8 lr = 0xc2216f98 (vpanic+0x13c) > > sp = 0xfbbe99d8 fp = 0xfbbe99f8 > > r4 = 0x00000100 r5 = 0xc7a356e0 > > r6 = 0xc265c1c6 r7 = 0x00000001 > > vpanic() at vpanic+0x13c > > pc = 0xc2216f98 lr = 0xc2216e5c (vpanic) > > sp = 0xfbbe9a00 fp = 0xfbbe9a04 > > r4 = 0xe086130c r5 = 0x00000000 > > r6 = 0x000c585c r7 = 0xc287a720 > > r8 = 0x00000001 r9 = 0xc7b8dc5c > > r10 = 0x00000018 > > vpanic() at vpanic > > pc = 0xc2216e5c lr = 0xc258fc9c (vm_radix_remove+0x1c8) > > sp = 0xfbbe9a0c fp = 0xfbbe9a28 > > r4 = 0xc287a720 r5 = 0x00000001 > > r6 = 0xc7b8dc5c r7 = 0x00000018 > > r8 = 0xfbbe9a04 r9 = 0xc2216e5c > > r10 = 0xfbbe9a0c > > vm_radix_remove() at vm_radix_remove+0x1c8 > > pc = 0xc258fc9c lr = 0xc257fbbc (vm_page_remove+0x34) > > sp = 0xfbbe9a30 fp = 0xfbbe9a38 > > r4 = 0xc2c48a50 r5 = 0xca5c1f18 > > r6 = 0x000c585c r7 = 0xc287a720 > > vm_page_remove() at vm_page_remove+0x34 > > pc = 0xc257fbbc lr = 0xc257ee90 (vm_page_free_toq+0x5c) > > sp = 0xfbbe9a40 fp = 0xfbbe9a58 > > r4 = 0xc2c48a50 r5 = 0xc2c48a50 > > vm_page_free_toq() at vm_page_free_toq+0x5c > > pc = 0xc257ee90 lr = 0xc25b5f90 (free_pv_chunk+0x168) > > sp = 0xfbbe9a60 fp = 0xfbbe9a70 > > r4 = 0xc585c000 r5 = 0xc2c48a50 > > r6 = 0x000c585c r10 = 0x00000018 > > free_pv_chunk() at free_pv_chunk+0x168 > > pc = 0xc25b5f90 lr = 0xc25b5c0c (pmap_remove_pages+0x66c) > > sp = 0xfbbe9a78 fp = 0xfbbe9ad0 > > r4 = 0x00000000 r5 = 0x00000000 > > r6 = 0xc3ae6170 r7 = 0x56adcc33 > > pmap_remove_pages() at pmap_remove_pages+0x66c > > pc = 0xc25b5c0c lr = 0xc256ad00 (vmspace_exit+0xc8) > > sp = 0xfbbe9ad8 fp = 0xfbbe9af8 > > r4 = 0xc7b8dc58 r5 = 0x00000001 > > r6 = 0xc285e650 r7 = 0xcab14000 > > r8 = 0xc7b8dc5c r9 = 0xc7b8dba0 > > r10 = 0xc7a356e0 > > vmspace_exit() at vmspace_exit+0xc8 > > pc = 0xc256ad00 lr = 0xc21bbdf8 (exit1+0xb9c) > > sp = 0xfbbe9b00 fp = 0xfbbe9b58 > > r4 = 0xc7a356e0 r5 = 0x00000004 > > r6 = 0xc7a356e0 r7 = 0xcab14000 > > r8 = 0xcab140bc r9 = 0xc707825c > > r10 = 0xcab140ac > > exit1() at exit1+0xb9c > > pc = 0xc21bbdf8 lr = 0xc221bc78 ($a.5+0x934) > > sp = 0xfbbe9b60 fp = 0xfbbe9d38 > > r4 = 0xfbbe9c88 r5 = 0x00000000 > > r6 = 0x00000005 r7 = 0xc261d701 > > r8 = 0xc7a356e0 r9 = 0x0000000b > > r10 = 0xc7a356e0 > > $a.5() at $a.5+0x934 > > pc = 0xc221bc78 lr = 0xc221cc5c (osigsuspend) > > sp = 0xfbbe9d40 fp = 0xfbbe9dd0 > > r4 = 0x0000000b r5 = 0xc7a356e0 > > r6 = 0xc7a356e0 r7 = 0xcab14000 > > r8 = 0xcb01aab8 r9 = 0x00020804 > > r10 = 0x00000000 > > osigsuspend() at osigsuspend > > pc = 0xc221cc5c lr = 0xc22865cc (ast+0x620) > > sp = 0xfbbe9dd8 fp = 0xfbbe9e00 > > ast() at ast+0x620 > > pc = 0xc22865cc lr = 0xc25a0da4 (exception_exit+0x40) > > sp = 0xfbbe9e08 fp = 0xbfbfdf28 > > r4 = 0x60000113 r5 = 0xc7a356e0 > > r6 = 0x00000000 r7 = 0x2003a200 > > r8 = 0x20035bc4 r9 = 0x20036718 > > r10 = 0x20036700 > > exception_exit() at exception_exit+0x40 > > pc = 0xc25a0da4 lr = 0x200287ec (0x200287ec) > > sp = 0xfbbe9e98 fp = 0xbfbfdf28 > > r0 = 0x00000000 r1 = 0x00000000 > > r2 = 0x00000000 r3 = 0x00000002 > > r4 = 0x00000002 r5 = 0xbfbfe3d8 > > r6 = 0x00000000 r7 = 0x2003a200 > > r8 = 0x20035bc4 r9 = 0x20036718 > > r10 = 0x20036700 r12 = 0x2003a200 > > Unable to unwind into user mode > > KDB: enter: panic > > [ thread pid 17915 tid 100894 ] > > Stopped at $d.6: ldrb r15, [r15, r15, ror r15]! > > db> show all pcpu > > ... > > > > For further information please see: > > http://ulrich-grey.de/dl/cubox_panic20161106.log > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Nov 10 07:42:40 2016 Return-Path: Delivered-To: freebsd-arm@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 EBEAEC39B93 for ; Thu, 10 Nov 2016 07:42:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 A74F6FC4 for ; Thu, 10 Nov 2016 07:42:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.81.13]) by kabab.cs.huji.ac.il with esmtp id 1c4k08-0004wC-OM; Thu, 10 Nov 2016 09:42:24 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: Allwinner H3 (orangepi-plus-2) SD card issue - kernel related From: Daniel Braniss In-Reply-To: Date: Thu, 10 Nov 2016 09:42:25 +0200 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <4DCD0F68-0CB8-4F51-B9CF-0542E2987862@cs.huji.ac.il> References: To: mattia.rossi.mailinglists@gmail.com X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 07:42:41 -0000 > On 9 Nov 2016, at 17:54, Mattia Rossi = wrote: >=20 > Hi all, >=20 > Finally had the guts to rebuild world, kernel (r308464M) and with that = the .dtb file, and trying to boot using the generated .dtb file. >=20 > The good news is: The system boots! >=20 > The bad news: >=20 > a) It loses a lot of time searching for the SD card partitions (or = whatever it does here), then it continues in the boot process. What's = wrong? >=20 > usbus0: 480Mbps High Speed USB v2.0 > usbus1: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on = usbus0 > ugen1.1: at usbus1 > uhub1: on = usbus1 > mmcsd0: 16GB at mmc0 = 50.0MHz/4bit/65535-block > a10_mmc1: error rint: 0x00000100 > uhub0: 1 port with 1 removable, self powered > uhub1: 1 port with 1 removable, self powered > ugen1.2: at usbus1 > umass0 on uhub1 > umass0: = on usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0xc100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SCSI device > da0: Serial Number 000000000033 > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not = present > da0: quirks=3D0x2 > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > a10_mmc1: controller timeout > mmc1: No compatible cards found on bus > a10_mmc2: error rint: 0x00000100 > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > a10_mmc2: controller timeout > mmc2: No compatible cards found on bus > Release APs > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from ufs:/dev/mmcsd0s2 [rw]... >=20 > b) No Ethernet Device! What do I have to add (to the .dts i guess) to = get that back? >=20 > ifconfig > lo0: flags=3D8049 metric 0 mtu 16384 > options=3D600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff000000 > groups: lo > nd6 options=3D21 >=20 > Appreciate any help, >=20 > Mat >=20 hi Mat, I would check that the .dtb file is correct, also check which .dtb gets = loaded. danny From owner-freebsd-arm@freebsd.org Thu Nov 10 09:48:48 2016 Return-Path: Delivered-To: freebsd-arm@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 A323EC39BA4 for ; Thu, 10 Nov 2016 09:48:48 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb2-smtp-cloud2.xs4all.net (lb2-smtp-cloud2.xs4all.net [194.109.24.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4190D3CF for ; Thu, 10 Nov 2016 09:48:47 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 69nY1u0014VixDu019nZCq; Thu, 10 Nov 2016 10:47:33 +0100 Reply-To: From: "John W. Kitz" To: Subject: How to change MAC address on RPI-B? Date: Thu, 10 Nov 2016 10:47:25 +0100 Message-ID: <000601d23b37$780b9230$6822b690$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI7N3FZuuuSrVBnRDqK0e/tYImSkA== Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 09:48:48 -0000 diffusae (if that's your name), I'm not contradicting the possibility that the sys/dev/usb/net/if_smsc.c driver needs a patch to set the mac address runtime, as you quoted a Hans Petter in one of the emails in this thread. But in general if I were you I would have a good look at the relevant documentation at "https://www.freebsd.org/cgi/man.cgi?query=ifconfig&apropos=0&sektion=0&manp ath=FreeBSD+11.0-stable&arch=default&format=html" and compare that to: ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 as you state you've tried and came to conclude that it doesn't do what you intend or expect it to. Success and regards, Jk. From owner-freebsd-arm@freebsd.org Thu Nov 10 10:12:16 2016 Return-Path: Delivered-To: freebsd-arm@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 F36A9C396F1 for ; Thu, 10 Nov 2016 10:12:16 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb1-smtp-cloud2.xs4all.net (lb1-smtp-cloud2.xs4all.net [194.109.24.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE5D32C for ; Thu, 10 Nov 2016 10:12:16 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6AAy1u00D4VixDu01AB3uz; Thu, 10 Nov 2016 11:11:03 +0100 Reply-To: From: "John W. Kitz" To: References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> In-Reply-To: <20161110065105.77a19e3b@X220.alogt.com> Subject: How to change MAC address on RPI-B? Date: Thu, 10 Nov 2016 11:11:02 +0100 Message-ID: <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI628oYuEg4+V6mRT2JRNa2s4YREQAXbvkQ Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 10:12:17 -0000 Erich, > To the best of my recollection at the time there was no need > whatsoever to configure these NICs into promiscuous mode, which in you need this for fault-tolerant computing. A machine or a device with a known goes down, the failure will be detected and another device or machine is configured to take over the other's task by also taking over the other's MAC address. The communication partners will only a delay but not a failure. JKi: I'm curious, would, in your experience, the impact of any delay incurred by tinkering with addresses at both layer-3 AND layer-2 in a failover situation be less in comparison to any delay incurred when tinkering with the addresses at layer-3 ONLY and leave the recovery of addressing issues at layer-2 to the relevant protocols? Jk. From owner-freebsd-arm@freebsd.org Thu Nov 10 17:12:05 2016 Return-Path: Delivered-To: freebsd-arm@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 0FED5C39260 for ; Thu, 10 Nov 2016 17:12:05 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA649CFE for ; Thu, 10 Nov 2016 17:12:04 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd25.aul.t-online.de (fwd25.aul.t-online.de [172.20.26.130]) by mailout11.t-online.de (Postfix) with SMTP id 47CD54252A98 for ; Thu, 10 Nov 2016 18:11:56 +0100 (CET) Received: from [192.168.10.43] (Sx8Y-GZdYhHaOPCQkGtqHEll0cJmSQbuSUtQiWQioXsCzrcaD3BP8BknZaoeKdgZQZ@[86.56.56.128]) by fwd25.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4stD-0IT1eK0; Thu, 10 Nov 2016 18:11:51 +0100 From: diffusae Subject: Re: How to change MAC address on RPI-B? To: freebsd-arm@freebsd.org References: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> <000001d23ad6$fce27e80$f6a77b80$@Kitz@xs4all.nl> Message-ID: Date: Thu, 10 Nov 2016 18:11:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <000001d23ad6$fce27e80$f6a77b80$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: Sx8Y-GZdYhHaOPCQkGtqHEll0cJmSQbuSUtQiWQioXsCzrcaD3BP8BknZaoeKdgZQZ X-TOI-MSGID: 484f4e35-bb6e-44e3-8db7-db973d593e6a X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 17:12:05 -0000 Hi, I've tried both, but not at the same time. To override the burned-in MAC at bootime doesn't work on FreeBSD. It works on Linux, but only the promiscuous mode works as aspected with the FreeBSD RPi build. On 09.11.2016 23:16, John W. Kitz wrote: > JKi: Doesn't that depend on the sequence of events at boot time? I don't think so. The serial number is hard-coded on the RPi. As I know, you could change it, but with a parameter in CONFIG.TXT it doesn't work. That's also the reason, why I like to change it. I have used a RPI with a faulty power connector and suddenly the MAC address was changing after reboot (this happens only once). > JKi: I'm curious, are you just in the process of confirming that it can be > done or do you actually have some purpose for this and if yes, what is it? I've look into the FDT file with dtc and found the following string: mac-address = [00 00 00 00 00 00]; So, I guess it should be possible to change it. I tried it and the the auto configuration of the MAC remains. Maybe I've done something wrong. https://wiki.freebsd.org/FlattenedDeviceTree#How_to_convert_a_platform_to_FDT Regards, From owner-freebsd-arm@freebsd.org Thu Nov 10 17:32:26 2016 Return-Path: Delivered-To: freebsd-arm@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 28AEEC39C9B for ; Thu, 10 Nov 2016 17:32:26 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E215FABC for ; Thu, 10 Nov 2016 17:32:25 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd15.aul.t-online.de (fwd15.aul.t-online.de [172.20.27.63]) by mailout12.t-online.de (Postfix) with SMTP id 5641641E4832 for ; Thu, 10 Nov 2016 18:32:17 +0100 (CET) Received: from [192.168.10.43] (Tnhm5eZcrhaZEf4mA+UDeeRpDiQb67gPgJtWKKU4vSu4r+2MnykTw+h9dDCex9AQAx@[86.56.56.128]) by fwd15.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4tCy-26SKYq0; Thu, 10 Nov 2016 18:32:16 +0100 Subject: Re: How to change MAC address on RPI-B? References: <000601d23b37$780b9230$6822b690$@Kitz@xs4all.nl> To: freebsd-arm@freebsd.org From: diffusae Message-ID: <0d293560-f843-5c16-d63a-0d772280504b@t-online.de> Date: Thu, 10 Nov 2016 18:32:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <000601d23b37$780b9230$6822b690$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: Tnhm5eZcrhaZEf4mA+UDeeRpDiQb67gPgJtWKKU4vSu4r+2MnykTw+h9dDCex9AQAx X-TOI-MSGID: d85e2245-f05d-476a-8a3d-0e52c2b13149 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 17:32:26 -0000 Hello John, On 10.11.2016 10:47, John W. Kitz wrote: > "https://www.freebsd.org/cgi/man.cgi?query=ifconfig&apropos=0&sektion=0&manp > ath=FreeBSD+11.0-stable&arch=default&format=html" and compare that to: Yes, you're right. I've also tried some other options (-RXCSUM). https://forums.freebsd.org/threads/49518/ Extra console error logging (debug) should be interesting, too > as you state you've tried and came to conclude that it doesn't do what you > intend or expect it to. With promisc it works, like expected. But as you mentioned before, that is not the intended use. Don't need to log every packet on the network. https://forums.freebsd.org/threads/57525/ Thanks a lot Best regards, Reiner From owner-freebsd-arm@freebsd.org Thu Nov 10 18:40:35 2016 Return-Path: Delivered-To: freebsd-arm@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 4E419C3862E for ; Thu, 10 Nov 2016 18:40:35 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11F469C7 for ; Thu, 10 Nov 2016 18:40:34 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd08.aul.t-online.de (fwd08.aul.t-online.de [172.20.26.151]) by mailout01.t-online.de (Postfix) with SMTP id 96960426063F for ; Wed, 9 Nov 2016 22:06:26 +0100 (CET) Received: from [192.168.10.43] (VrcMLBZHohEVYDAG5K5IyFKpfXIS1JPrR3xfl7VBGdE9HMRr91xSfamrKgKSW4+QhL@[86.56.56.128]) by fwd08.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c4a4Z-1zsX200; Wed, 9 Nov 2016 22:06:19 +0100 Subject: Re: How to change MAC address on RPI-B? References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> To: freebsd-arm@freebsd.org From: diffusae Message-ID: <0f3e4d38-fa61-c4ec-0754-bd5ed681aa96@t-online.de> Date: Wed, 9 Nov 2016 22:06:19 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ID: VrcMLBZHohEVYDAG5K5IyFKpfXIS1JPrR3xfl7VBGdE9HMRr91xSfamrKgKSW4+QhL X-TOI-MSGID: 96b090b1-306b-40f3-b6bb-65e5690f0fb7 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 18:40:35 -0000 Hi, thanks a lot for your help. On 09.11.2016 12:35, John W. Kitz wrote: > I saw a couple of emails whizz by, which discussed how to override the > burned in MAC address (BIA) on an RPI-B. Do you saw them at this mailing list? Maybe I should have a look into the archive? > techniques, i.e. overriding the BIA of a NIC and configuring a NIC into > promiscuous mode, was made while such a dependency does not or at least, to > the best of my knowledge, should not exist. That's true, if you try this in Linux, you could use one of both techniques. You can override the MAC on boot or set the MAC on runtime. And this works on the fly. > have a NIC consider frames that aren't destined for the NIC's BIA address as > if they were, so I doubt that such a need exists today. Normally you shouldn't use the promiscuous mode for this. You only need it, if you use some kind of sniffing software for the whole network traffic, etc. Best regards, From owner-freebsd-arm@freebsd.org Fri Nov 11 01:49:44 2016 Return-Path: Delivered-To: freebsd-arm@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 E7DB1C3ADFB for ; Fri, 11 Nov 2016 01:49:44 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (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 C934AF43 for ; Fri, 11 Nov 2016 01:49:44 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=DeHODbLPoXynpo9HcLDC/FC0uc3AcWvbWQ1im3W0tzg=; b=ktEfpJvEDKTNL08h95ElIsUsdE EUXypriNiNnhdTRcTYfIw5Rn5PHHlg8fgd/32chDn5mUErPd9IIKMx6Zuc7ig4B6udnWuoxo6G/rR mMxMmPghcwsJGxEqYTF9dYZfsMSoUqWJCtrTP7oQSHlpxl5XWKtjPKbrip8GnDPMeXA0=; Received: from [114.125.84.199] (port=53635 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1c50yI-001UMq-5C; Thu, 10 Nov 2016 18:49:38 -0700 Date: Fri, 11 Nov 2016 09:49:30 +0800 From: Erich Dollansky To: "John W. Kitz" Cc: Subject: Re: How to change MAC address on RPI-B? Message-ID: <20161111094930.46f55a60@X220.alogt.com> In-Reply-To: <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 01:49:45 -0000 Hi John, On Thu, 10 Nov 2016 11:11:02 +0100 "John W. Kitz" wrote: > > To the best of my recollection at the time there was no need > > whatsoever to configure these NICs into promiscuous mode, which in > > you need this for fault-tolerant computing. A machine or a device > with a known goes down, the failure will be detected and another > device or machine is configured to take over the other's task by also > taking over the other's MAC address. The communication partners will > only a delay but not a failure. > > JKi: I'm curious, would, in your experience, the impact of any delay > incurred by tinkering with addresses at both layer-3 AND layer-2 in a > failover situation be less in comparison to any delay incurred when > tinkering with the addresses at layer-3 ONLY and leave the recovery of > addressing issues at layer-2 to the relevant protocols? > it depends of what you want. When the machine connecting to the fault-tolerant machine is not fault-tolerant, it will not be able to change any addresses. All it will do is repeating requests. A watch-dog should have realised by then that either the interface or the machine with the interface is down and should have activated either a different interface or a different machine. It is just one of many option you have. And it is a cheap option as you can make even FreeBSD fault-tolerant with this as the operating system does not play any part in this kind of fault-tolerance. Erich From owner-freebsd-arm@freebsd.org Fri Nov 11 10:29:34 2016 Return-Path: Delivered-To: freebsd-arm@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 834A6C3B7C8 for ; Fri, 11 Nov 2016 10:29:34 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb1-smtp-cloud2.xs4all.net (lb1-smtp-cloud2.xs4all.net [194.109.24.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C38017E0 for ; Fri, 11 Nov 2016 10:29:33 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6aVP1u00B4VixDu01aVQ9e; Fri, 11 Nov 2016 11:29:25 +0100 Reply-To: From: "John W. Kitz" To: References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <0f3e4d38-fa61-c4ec-0754-bd5ed681aa96@t-online.de> In-Reply-To: <0f3e4d38-fa61-c4ec-0754-bd5ed681aa96@t-online.de> Subject: RE: How to change MAC address on RPI-B? Date: Fri, 11 Nov 2016 11:29:21 +0100 Message-ID: <000001d23c06$7bc58be0$7350a3a0$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI7gfLzd2Kn49w9S7SmHCJTtT4nJwAgnttA Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 10:29:34 -0000 > I saw a couple of emails whizz by, which discussed how to override the > burned in MAC address (BIA) on an RPI-B. Do you saw them at this mailing list? Maybe I should have a look into the archive? JKi: I meant your emails and they whizzed by because I had already deleted the first couple of ones in this thread from my email box by the time I decided that I was going to respond to them. So, as it happens, yes, I had to go to the archives to look them up. Actually I've been following this email distribution since late 2015 because I'm hoping to, at some point in time, use FreeBSD on an ARM platform for HAM radio purposes. Consequently I think it's quite nice to see that with 11.0 the developers released the first FreeBSD images specifically aimed at various ARM architectures. > techniques, i.e. overriding the BIA of a NIC and configuring a NIC > into promiscuous mode, was made while such a dependency does not or at > least, to the best of my knowledge, should not exist. That's true, if you try this in Linux, you could use one of both techniques. You can override the MAC on boot or set the MAC on runtime. And this works on the fly. > have a NIC consider frames that aren't destined for the NIC's BIA > address as if they were, so I doubt that such a need exists today. Normally you shouldn't use the promiscuous mode for this. You only need it, if you use some kind of sniffing software for the whole network traffic, etc. Best regards, _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Nov 11 11:26:36 2016 Return-Path: Delivered-To: freebsd-arm@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 2F22DC37A12 for ; Fri, 11 Nov 2016 11:26:36 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb2-smtp-cloud2.xs4all.net (lb2-smtp-cloud2.xs4all.net [194.109.24.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C19831432 for ; Fri, 11 Nov 2016 11:26:35 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6bSR1u00H4VixDu01bSTlh; Fri, 11 Nov 2016 12:26:27 +0100 Reply-To: From: "John W. Kitz" To: References: <000601d23b37$780b9230$6822b690$@Kitz@xs4all.nl> <0d293560-f843-5c16-d63a-0d772280504b@t-online.de> In-Reply-To: <0d293560-f843-5c16-d63a-0d772280504b@t-online.de> Subject: RE: How to change MAC address on RPI-B? Date: Fri, 11 Nov 2016 12:26:29 +0100 Message-ID: <000301d23c0e$73932ec0$5ab98c40$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI7eHFKNKlyFcB3SZGdT6CCtV4FfgAjqA0A Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 11:26:36 -0000 Reiner, > "https://www.freebsd.org/cgi/man.cgi?query=ifconfig&apropos=0&sektion= > 0&manp ath=FreeBSD+11.0-stable&arch=default&format=html" and compare > that to: Yes, you're right. I've also tried some other options (-RXCSUM). https://forums.freebsd.org/threads/49518/ Extra console error logging (debug) should be interesting, too JKi: I had a look at both the posts in the forum you're referring to and at your first emails in this thread in which you wrote that you tried (I quote): ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 And it's not quite clear to me what you're trying to achieve. Why would one override the MAC address of an interface for the sole purpose of initiating a request for a new IP address from the DHCP server (in a home environment typically the ADSL or cable modem supplied by the ISP) that one is using. Surely FreeBSD provides more elegant ways to achieve the same thing. If these don't get you the desired result, based on the information supplied, I think it would be more appropriate to look at reducing the DHCP lease time on the server side and stick with the options available to you to initiate a request for a new IP address from the DHCP server rather than at configuring a locally administered MAC addresses to achieve the same thing. As for the commands in the various post, if I compare these to "https://www.freebsd.org/cgi/man.cgi?query=ifconfig&apropos=0&sektion=0&manp ath=FreeBSD+11.0-stable&arch=default&format=html" I wonder what, in your opinion, the purpose is of sticking "delete" (per the documentation I referred to (I quote) "Another name for the -alias parameter") at the end of the first one. In addition given that operating system commands, particularly the most basic ones, tend to be similar across platforms (in this case I'm referring to similar Cisco commands) and considering the possibility that you may not have supplied all commands you used in the various posts, I would have expected a command like "ifconfig ue0 up" to have been the last one in the sequence. > as you state you've tried and came to conclude that it doesn't do what > you intend or expect it to. With promisc it works, like expected. But as you mentioned before, that is not the intended use. Don't need to log every packet on the network. https://forums.freebsd.org/threads/57525/ Thanks a lot Best regards, Reiner _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Nov 11 11:54:25 2016 Return-Path: Delivered-To: freebsd-arm@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 28C83C3B70C for ; Fri, 11 Nov 2016 11:54:25 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud2.xs4all.net (lb3-smtp-cloud2.xs4all.net [194.109.24.29]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B686312F7 for ; Fri, 11 Nov 2016 11:54:23 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6bt91u00R4VixDu01btB3o; Fri, 11 Nov 2016 12:53:11 +0100 Reply-To: From: "John W. Kitz" To: References: <000001d23a85$47646970$d62d3c50$@Kitz@xs4all.nl> <000001d23ad6$fce27e80$f6a77b80$@Kitz@xs4all.nl> In-Reply-To: Subject: RE: How to change MAC address on RPI-B? Date: Fri, 11 Nov 2016 12:53:13 +0100 Message-ID: <000601d23c12$2fa70ac0$8ef52040$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI7dZodVLbUwpF4QDG03tEj8dOMUgAmPAeg Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 11:54:25 -0000 Reiner, I've tried both, but not at the same time. To override the burned-in MAC at bootime doesn't work on FreeBSD. It works on Linux, but only the promiscuous mode works as aspected with the FreeBSD RPi build. > JKi: Doesn't that depend on the sequence of events at boot time? I don't think so. The serial number is hard-coded on the RPi. As I know, you could change it, but with a parameter in CONFIG.TXT it doesn't work. That's also the reason, why I like to change it. I have used a RPI with a faulty power connector and suddenly the MAC address was changing after reboot (this happens only once). JKi: Again since I don't have a Pi at my disposal and since I don't have any prior experience with one, I'm not in a position to argue this. But are you implying that if one has two or more Pi's attached to one network(segment) there is a, albeit slim, chance that a situation would occur in which two or more of these Pi's would end up having the same MAC address resulting in duplicate MAC addresses on the same LAN? Obviously Pi's are a cheap platform, not designed for professional use, but this would seem very awkward and unlikely to me. In addition you mentioned in one of your emails that the Organizationally Unique Identifier (OUI) or in short vendor portion of the MAC address used by a Pi is b8:27:eb providing for MAC addresses ranging from b8-27-eb-00-00-00 up to and including b8-27-eb-FF-FF-FF. Yet you mention, or at least that is my understanding of what you wrote, that Pi's use some algorithm to determine the last portion of the MAC address based on the Pi's serial number, which doesn't always yield the same result on one and the same Pi? > JKi: I'm curious, are you just in the process of confirming that it > can be done or do you actually have some purpose for this and if yes, what is it? I've look into the FDT file with dtc and found the following string: mac-address = [00 00 00 00 00 00]; So, I guess it should be possible to change it. I tried it and the the auto configuration of the MAC remains. Maybe I've done something wrong. https://wiki.freebsd.org/FlattenedDeviceTree#How_to_convert_a_platform_to_FD T JKi: As mentioned before I don't have a Pi at my disposal and I don't have any prior experience with one, so I have nothing to add to this last portion of your post. Regards, Jk. From owner-freebsd-arm@freebsd.org Fri Nov 11 12:12:19 2016 Return-Path: Delivered-To: freebsd-arm@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 34602C3A6C3 for ; Fri, 11 Nov 2016 12:12:19 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud2.xs4all.net (lb3-smtp-cloud2.xs4all.net [194.109.24.29]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C706B1287 for ; Fri, 11 Nov 2016 12:12:18 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP id 6cCF1u0014VixDu01cCGzY; Fri, 11 Nov 2016 13:12:16 +0100 Reply-To: From: "John W. Kitz" To: References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> <20161111094930.46f55a60@X220.alogt.com> In-Reply-To: <20161111094930.46f55a60@X220.alogt.com> Subject: RE: How to change MAC address on RPI-B? Date: Fri, 11 Nov 2016 13:12:19 +0100 Message-ID: <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI7vd7MQYUHOX7aSpyC5iH/0Duy4AAVNyHw Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 12:12:19 -0000 Erich, > > To the best of my recollection at the time there was no need > > whatsoever to configure these NICs into promiscuous mode, which in > > you need this for fault-tolerant computing. A machine or a device with > a known goes down, the failure will be detected and another device or > machine is configured to take over the other's task by also taking > over the other's MAC address. The communication partners will only a > delay but not a failure. > > JKi: I'm curious, would, in your experience, the impact of any delay > incurred by tinkering with addresses at both layer-3 AND layer-2 in a > failover situation be less in comparison to any delay incurred when > tinkering with the addresses at layer-3 ONLY and leave the recovery of > addressing issues at layer-2 to the relevant protocols? > it depends of what you want. When the machine connecting to the fault-tolerant machine is not fault-tolerant, it will not be able to change any addresses. All it will do is repeating requests. A watch-dog should have realised by then that either the interface or the machine with the interface is down and should have activated either a different interface or a different machine. It is just one of many option you have. And it is a cheap option as you can make even FreeBSD fault-tolerant with this as the operating system does not play any part in this kind of fault-tolerance. JKi: The point I was trying to make is that locally administered MAC addresses serve a purpose in the recovery of hardware failures, e.g. in its basic form when one needs to replace a broken NIC thereby ending up with a system with a different MAC address, in those situations where the higher layer protocol (addressing or rather lack thereof, such as can be the case in SNA / VTAM installations) doesn't. The other point, which you're not answering, is assuming that one would rely on the use of both lower and higher layer addressing in the recovery from hardware failures is there, in your experience, a noticeable gain in recovery time to be made by applying both techniques. Regards, Jk. From owner-freebsd-arm@freebsd.org Fri Nov 11 14:43:13 2016 Return-Path: Delivered-To: freebsd-arm@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 E230AC3BBB0 for ; Fri, 11 Nov 2016 14:43:13 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::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 95DD51AD9 for ; Fri, 11 Nov 2016 14:43:13 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (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 52E741FE022; Fri, 11 Nov 2016 15:43:11 +0100 (CET) Subject: Re: How to change MAC address on RPI-B? To: John.Kitz@xs4all.nl, freebsd-arm@freebsd.org References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> <20161111094930.46f55a60@X220.alogt.com> <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> From: Hans Petter Selasky Message-ID: <445c56a4-2c35-cb4c-f729-950d4e758d8d@selasky.org> Date: Fri, 11 Nov 2016 15:48:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> Content-Type: multipart/mixed; boundary="------------03AE974032C9AA41663BC4B6" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 14:43:14 -0000 This is a multi-part message in MIME format. --------------03AE974032C9AA41663BC4B6 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi, Does the attached patch solve the problem? --HPS --------------03AE974032C9AA41663BC4B6 Content-Type: text/x-patch; name="if_smsc_mac.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="if_smsc_mac.diff" Index: sys/dev/usb/net/if_smsc.c =================================================================== --- sys/dev/usb/net/if_smsc.c (revision 308426) +++ sys/dev/usb/net/if_smsc.c (working copy) @@ -152,7 +152,7 @@ device_printf((sc)->sc_ue.ue_dev, "debug: " fmt, ##args); \ } while(0) #else -#define smsc_dbg_printf(sc, fmt, args...) +#define smsc_dbg_printf(sc, fmt, args...) do { } while (0) #endif #define smsc_warn_printf(sc, fmt, args...) \ @@ -187,6 +187,7 @@ static uether_fn_t smsc_stop; static uether_fn_t smsc_start; static uether_fn_t smsc_tick; +static uether_fn_t smsc_setmac; static uether_fn_t smsc_setmulti; static uether_fn_t smsc_setpromisc; @@ -234,6 +235,7 @@ .ue_init = smsc_init, .ue_stop = smsc_stop, .ue_tick = smsc_tick, + .ue_setmac = smsc_setmac, .ue_setmulti = smsc_setmulti, .ue_setpromisc = smsc_setpromisc, .ue_mii_upd = smsc_ifmedia_upd, @@ -822,7 +824,6 @@ return (0); } - /** * smsc_setmacaddress - Sets the mac address in the device * @sc: driver soft context @@ -860,6 +861,25 @@ } /** + * smsc_setmac - Setup new MAC address + * @ue: usb ethernet device context + * + * LOCKING: + * Should be called with the SMSC lock held. + */ +static void +smsc_setmac(struct usb_ether *ue) +{ + struct smsc_softc *sc = uether_getsc(ue); + struct ifnet *ifp = uether_getifp(ue); + + SMSC_LOCK_ASSERT(sc, MA_OWNED); + + if (smsc_setmacaddress(sc, IF_LLADDR(ifp))) + smsc_dbg_printf(sc, "setting MAC address failed\n"); +} + +/** * smsc_reset - Reset the SMSC chip * @sc: device soft context * Index: sys/dev/usb/net/usb_ethernet.c =================================================================== --- sys/dev/usb/net/usb_ethernet.c (revision 308426) +++ sys/dev/usb/net/usb_ethernet.c (working copy) @@ -72,6 +72,7 @@ static usb_proc_callback_t ue_attach_post_task; static usb_proc_callback_t ue_promisc_task; +static usb_proc_callback_t ue_setmac_task; static usb_proc_callback_t ue_setmulti_task; static usb_proc_callback_t ue_ifmedia_task; static usb_proc_callback_t ue_tick_task; @@ -410,7 +411,8 @@ (struct usb_ether_cfg_task *)_task; struct usb_ether *ue = task->ue; - ue->ue_methods->ue_setpromisc(ue); + if (ue->ue_methods->ue_setpromisc != NULL) + ue->ue_methods->ue_setpromisc(ue); } static void @@ -420,9 +422,21 @@ (struct usb_ether_cfg_task *)_task; struct usb_ether *ue = task->ue; - ue->ue_methods->ue_setmulti(ue); + if (ue->ue_methods->ue_setmulti != NULL) + ue->ue_methods->ue_setmulti(ue); } +static void +ue_setmac_task(struct usb_proc_msg *_task) +{ + struct usb_ether_cfg_task *task = + (struct usb_ether_cfg_task *)_task; + struct usb_ether *ue = task->ue; + + if (ue->ue_methods->ue_setmac != NULL) + ue->ue_methods->ue_setmac(ue); +} + int uether_ifmedia_upd(struct ifnet *ifp) { @@ -529,6 +543,16 @@ } else error = ether_ioctl(ifp, command, data); break; + case SIOCGIFADDR: + error = ether_ioctl(ifp, command, data); + if (error == 0) { + UE_LOCK(ue); + ue_queue_command(ue, ue_setmac_task, + &ue->ue_mac_task[0].hdr, + &ue->ue_mac_task[1].hdr); + UE_UNLOCK(ue); + } + break; default: error = ether_ioctl(ifp, command, data); break; Index: sys/dev/usb/net/usb_ethernet.h =================================================================== --- sys/dev/usb/net/usb_ethernet.h (revision 308426) +++ sys/dev/usb/net/usb_ethernet.h (working copy) @@ -61,6 +61,7 @@ uether_fn_t *ue_start; uether_fn_t *ue_init; uether_fn_t *ue_stop; + uether_fn_t *ue_setmac; uether_fn_t *ue_setmulti; uether_fn_t *ue_setpromisc; uether_fn_t *ue_tick; @@ -96,6 +97,7 @@ struct usb_ether_cfg_task ue_multi_task[2]; struct usb_ether_cfg_task ue_promisc_task[2]; struct usb_ether_cfg_task ue_tick_task[2]; + struct usb_ether_cfg_task ue_mac_task[2]; int ue_unit; --------------03AE974032C9AA41663BC4B6-- From owner-freebsd-arm@freebsd.org Fri Nov 11 23:59:58 2016 Return-Path: Delivered-To: freebsd-arm@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 29599C39F5A for ; Fri, 11 Nov 2016 23:59:58 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (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 097C61F75 for ; Fri, 11 Nov 2016 23:59:57 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=oFCRUype7YL6Ve5njTJOB5pC97ITePCQyGIryiz6m9Y=; b=m+5obPfvZEWKn6tv6CwFj2xSt0 MIWXIWMq4FgLfX9j2/tlibDAgjCmr6BjvwiEwSXY0tOqQHTvG0DqHIi5LB9sKZJCR8aIbL6u2kLeB 2N+6W5pPD4fAZMGGvJBtTxn3tNTnEl4gzmZndKLJwRqHEbGlcTJttQE+AeBJNJ0r8gc0=; Received: from [114.125.104.44] (port=60500 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1c5Ljf-002RYC-16; Fri, 11 Nov 2016 16:59:57 -0700 Date: Sat, 12 Nov 2016 07:59:36 +0800 From: Erich Dollansky To: "John W. Kitz" Cc: Subject: Re: How to change MAC address on RPI-B? Message-ID: <20161112075936.6cf98437@X220.alogt.com> In-Reply-To: <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> <20161111094930.46f55a60@X220.alogt.com> <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 23:59:58 -0000 Hi John, On Fri, 11 Nov 2016 13:12:19 +0100 "John W. Kitz" wrote: > JKi: The point I was trying to make is that locally administered MAC > addresses serve a purpose in the recovery of hardware failures, e.g. > in its basic form when one needs to replace a broken NIC thereby > ending up with a system with a different MAC address, in those > situations where the higher layer protocol (addressing or rather lack > thereof, such as can be the case in SNA / VTAM installations) doesn't. > > The other point, which you're not answering, is assuming that one > would rely on the use of both lower and higher layer addressing in > the recovery from hardware failures is there, in your experience, a > noticeable gain in recovery time to be made by applying both > techniques. we have at the moment only the situation in which non-fault-tolerant systems address our fault-tolerant system. Our emphasis is currently only to detect a fault, switch MAC and IP address, report the fault and let the outside world believe all is fine. We have then 1 to 4 days time to fix the faulty system. Yes, I know, this is not a very common situation. We use this only as users of the system have to have no IT skills. They even wonder that there is some IT used in our system. I can imagine where you come from. Your system is very, very different from our system. Just have a look at our website. The words IT, computer, fault-tolerant etc are not even used a single time. Erich > > Regards, Jk. > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Nov 12 11:38:49 2016 Return-Path: Delivered-To: freebsd-arm@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 D8ED9C3D382 for ; Sat, 12 Nov 2016 11:38:49 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb2-smtp-cloud6.xs4all.net (lb2-smtp-cloud6.xs4all.net [194.109.24.28]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7977C1F97 for ; Sat, 12 Nov 2016 11:38:49 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 6zek1u0054VixDu01zel7D; Sat, 12 Nov 2016 12:38:46 +0100 Reply-To: From: "John W. Kitz" To: Subject: Re: How to change MAC address on RPI-B? Date: Sat, 12 Nov 2016 12:38:43 +0100 Message-ID: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI82VKR1ElkYuSPQ1a6s+l+tbJ7Aw== Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 11:38:49 -0000 Reiner, I was again looking at one of the first posts in the thread in which you wrote: "I've tried it this way in /etc/start_if.ue0: ifconfig ue0 down delete ifconfig ue0 promisc ifconfig ue0 ether 00:FF:CC:00:11:11 But it's only possible to do it in promicous mode of the device." In the man pages for ifconfig the parameter 'down' is explained as follows: "Mark an interface ``down''. When an interface is marked ``down'', the system will not attempt to transmit messages through that interface. If possible, the interface will be reset to disable reception as well. This action does not automatically disable routes using the interface." So based on the information supplied it would seem logical that "there is no more network connection after applying these settings." as you mentioned. Looking further down the man pages you'll notice the parameter "up" to "Mark an interface ``up''. This may be used to enable an interface after an ``ifconfig down''. It happens automatically when setting the first address on an interface. If the interface was reset when previously marked down, the hardware will be re-initialized." Hence my question shouldn't you also use "ifconfig ue0 up" at the end in the example you supplied (see above). Also you are referring to the bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168268 The method stated in this bug report to reproduce the issue is: "How-To-Repeat: /etc/rc.conf ifconfig_re0="inet 192.168.0.2/24" ifconfig_re0="inet 192.168.0.2/24" ifconfig_re0_alias0="ether 00:02:1a:2b:3c:4d" I don't know if the operating system interprets "alias" in "ifconfig_re0_alias0" as per the man pages of ifconfig or if it just considers it to be a label, but if it is being interpreted as per the man pages I'd imagine the operating system to expect the parameter to contain an IP address intended to serve as secondary IP address for the interface, rather than a MAC address. Did you try this command-by-command through the CLI and have the output of that? Jk. From owner-freebsd-arm@freebsd.org Sat Nov 12 14:45:59 2016 Return-Path: Delivered-To: freebsd-arm@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 B11F1C3D1DA for ; Sat, 12 Nov 2016 14:45:59 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78173184D for ; Sat, 12 Nov 2016 14:45:59 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd03.aul.t-online.de (fwd03.aul.t-online.de [172.20.27.148]) by mailout02.t-online.de (Postfix) with SMTP id CBE3641A2436 for ; Sat, 12 Nov 2016 15:45:50 +0100 (CET) Received: from [192.168.10.43] (ZYfGOyZf8h80qHXqKJuHKGStUoRrU6X0N4jemgnxfd0Y4v6L33MjTUvtiWiV89kQ7Y@[86.56.56.128]) by fwd03.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c5ZZ0-2b3QyO0; Sat, 12 Nov 2016 15:45:50 +0100 Subject: Re: How to change MAC address on RPI-B? References: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl> To: freebsd-arm@freebsd.org From: diffusae Message-ID: Date: Sat, 12 Nov 2016 15:45:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ID: ZYfGOyZf8h80qHXqKJuHKGStUoRrU6X0N4jemgnxfd0Y4v6L33MjTUvtiWiV89kQ7Y X-TOI-MSGID: 3b58be16-1611-4465-9214-7c7ca351b287 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 14:45:59 -0000 Hi John, thanks a lot for you reply On 12.11.2016 12:38, John W. Kitz wrote: > "I've tried it this way in /etc/start_if.ue0: /etc/start_if.ue0 will be launched before the interface is up, so ifconfig up is done by the boot process. The only message I get at boot in this stage is: ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address smsc0: chip 0xec00, rev. 0002 ue0: link state changed to DOWN ue0: link state changed to UP I also cannot change the MAC at runtime without loosing network connection. > Hence my question shouldn't you also use "ifconfig ue0 up" at the end in the > example you supplied (see above). There is no network connection, also if I supplied the ifconfig command on the CLI. > "How-To-Repeat: /etc/rc.conf > ifconfig_re0="inet 192.168.0.2/24" > ifconfig_re0_alias0="ether 00:02:1a:2b:3c:4d" That's another way you can set the MAC in /etc/rc.conf > Did you try this command-by-command through the CLI and have the output of > that? Yes, but I can't use alias or add parameter with the ether, lladdr or link options. Than it says: ifconfig: ether: bad value. But I've also tried this settings in /etc/rc.conf and it doesn't work. Regards, Reiner From owner-freebsd-arm@freebsd.org Sat Nov 12 15:46:30 2016 Return-Path: Delivered-To: freebsd-arm@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 1D114C3D3AE for ; Sat, 12 Nov 2016 15:46:30 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud3.xs4all.net (lb3-smtp-cloud3.xs4all.net [194.109.24.30]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AE82813DF for ; Sat, 12 Nov 2016 15:46:28 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud3.xs4all.net with ESMTP id 73lE1u0084VixDu013lF1x; Sat, 12 Nov 2016 16:45:16 +0100 Reply-To: From: "John W. Kitz" To: References: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl> In-Reply-To: Subject: RE: How to change MAC address on RPI-B? Date: Sat, 12 Nov 2016 16:45:20 +0100 Message-ID: <001401d23cfb$c6c6f070$5454d150$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI884OdiwMqWZkYQJKvTS8ptzY4JgAAVHHg Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 15:46:30 -0000 Reiner, > "How-To-Repeat: /etc/rc.conf > ifconfig_re0="inet 192.168.0.2/24" > ifconfig_re0_alias0="ether 00:02:1a:2b:3c:4d" That's another way you can set the MAC in /etc/rc.conf > Did you try this command-by-command through the CLI and have the > output of that? Yes, but I can't use alias or add parameter with the ether, lladdr or link options. JKi: As per the man-pages of ifconfig ether, lladdr and link may be used interchangeably and are all interpreted to mean one and the same thing. Than it says: ifconfig: ether: bad value. JKi: That was exactly what I tried to convey in my previous email. As per the man pages of ifconfig 'alias' and '-alias' are intended to respectively add and remove a, what in Cisco terminology is referred to as a, secondary IP address to or from an interface. Since both 'ether' and the notation of the address in "ifconfig_re0_alias0="ether 00:02:1a:2b:3c:4d" pertain to a MAC address this is behavior that one IMHO would expect as per the man-pages, assuming 'alias' in 'ifconfig_re0_alias0' is interpreted as a command parameter rather than as a mere label. My hands-on experience in the area of UNIX is limited and dated, so these were my 5 cents worth of suggestions. Sorry I can't help you any further at this time. Regards, Jk. From owner-freebsd-arm@freebsd.org Sat Nov 12 16:01:49 2016 Return-Path: Delivered-To: freebsd-arm@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 9A833C3D9F7 for ; Sat, 12 Nov 2016 16:01:49 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 609631FBE for ; Sat, 12 Nov 2016 16:01:49 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd10.aul.t-online.de (fwd10.aul.t-online.de [172.20.26.152]) by mailout01.t-online.de (Postfix) with SMTP id 96F67424C1A3 for ; Sat, 12 Nov 2016 17:01:40 +0100 (CET) Received: from [192.168.10.43] (G5t+nGZ-QhbLpWt9UqRaso4J3517m5zlQkn+TBZm4XpHAQ99-88wkhoow13yfepwP-@[86.56.56.128]) by fwd10.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c5akJ-3dmFg80; Sat, 12 Nov 2016 17:01:35 +0100 Subject: Re: How to change MAC address on RPI-B? References: <001301d23cd9$5775bf70$06613e50$@Kitz@xs4all.nl> <001401d23cfb$c6c6f070$5454d150$@Kitz@xs4all.nl> To: freebsd-arm@freebsd.org From: diffusae Message-ID: Date: Sat, 12 Nov 2016 17:01:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <001401d23cfb$c6c6f070$5454d150$@Kitz@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: G5t+nGZ-QhbLpWt9UqRaso4J3517m5zlQkn+TBZm4XpHAQ99-88wkhoow13yfepwP- X-TOI-MSGID: 19af0592-4e39-47c8-8908-056993d3de07 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 16:01:49 -0000 Hello Jonh, On 12.11.2016 16:45, John W. Kitz wrote: > Sorry I can't help you any further at this time. That doesn't matter. I glad, that you try to find a solution. Best regards. Reiner From owner-freebsd-arm@freebsd.org Sat Nov 12 20:04:04 2016 Return-Path: Delivered-To: freebsd-arm@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 B0AAEC3E672 for ; Sat, 12 Nov 2016 20:04:04 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb1-smtp-cloud6.xs4all.net (lb1-smtp-cloud6.xs4all.net [194.109.24.24]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 523CE260 for ; Sat, 12 Nov 2016 20:04:04 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 782p1u0034VixDu0182qZL; Sat, 12 Nov 2016 21:02:50 +0100 Reply-To: From: "John W. Kitz" To: Subject: How to change MAC address on RPI-B? Date: Sat, 12 Nov 2016 21:02:47 +0100 Message-ID: <000301d23d1f$c2dd76e0$489864a0$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI9H71L5xB/rHUhQuSyBkoTNGdyeQ== Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 20:04:04 -0000 Reiner, I found a couple of examples in the FreeBSd documentation that may be useful to you. "The ether line will contain the MAC address of the specified interface. Now, change the MAC address of the underlying wireless interface: # ifconfig iwn0 ether 00:21:70:da:ae:37 Bring the wireless interface up, but do not set an IP address: # ifconfig wlan0 create wlandev iwn0 ssid my_router up" To retain this configuration across reboots, add the following entries to /etc/rc.conf: ifconfig_iwn0="ether 00:21:70:da:ae:37" Source: https://www.freebsd.org/doc/handbook/network-aggregation.html Are you sure the NIC you are using itself (i.e. aside from the driver) is capable of supporting locally administered MAC addresses? Jk. From owner-freebsd-arm@freebsd.org Sat Nov 12 20:18:43 2016 Return-Path: Delivered-To: freebsd-arm@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 0A47AC3E8D1 for ; Sat, 12 Nov 2016 20:18:43 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA37A15 for ; Sat, 12 Nov 2016 20:18:42 +0000 (UTC) (envelope-from John.Kitz@xs4all.nl) Received: from picard ([82.95.89.208]) by smtp-cloud6.xs4all.net with ESMTP id 78JY1u00A4VixDu018Jail; Sat, 12 Nov 2016 21:18:34 +0100 Reply-To: From: "John W. Kitz" To: Subject: How to change MAC address on RPI-B? Date: Sat, 12 Nov 2016 21:18:39 +0100 Message-ID: <000601d23d21$f5535520$dff9ff60$@Kitz@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdI9IfRbbl5JmsCFQoW6VScnLD6gEQ== Content-Language: en-us X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 20:18:43 -0000 Reiner, Referring to: "(...) Universally administered and locally administered addresses are distinguished by setting the second-least-significant bit of the first octet of the address. This bit is also referred to as the U/L bit, short for Universal/Local, which identifies how the address is administered. If the bit is 0, the address is universally administered. If it is 1, the address is locally administered. In the example address 06-00-00-00-00-00 the first octet is 06 (hex), the binary form of which is 00000110, where the second-least-significant bit is 1. Therefore, it is a locally administered address. Consequently, this bit is 0 in all OUIs. (...)" Source: https://en.wikipedia.org/wiki/MAC_address#Universal_vs._local and my earlier remarks about functional MAC addresses, it could also matter which address you are using as your locally administered address. Jk. From owner-freebsd-arm@freebsd.org Sat Nov 12 22:46:02 2016 Return-Path: Delivered-To: freebsd-arm@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 5E4ABC3B67E for ; Sat, 12 Nov 2016 22:46:02 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout09.t-online.de (mailout09.t-online.de [194.25.134.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21AC011DE for ; Sat, 12 Nov 2016 22:46:01 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd00.aul.t-online.de (fwd00.aul.t-online.de [172.20.26.147]) by mailout09.t-online.de (Postfix) with SMTP id 06F9A4269CB9 for ; Sat, 12 Nov 2016 23:45:53 +0100 (CET) Received: from [192.168.10.43] (XHhtFBZFQhSgH-z1cwlY+TF8A5OTnbIHJDFIIaVdnfC4UaCwQcb2jlX69sYRAEdZSM@[86.56.56.128]) by fwd00.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c5h3Y-0XJ7IG0; Sat, 12 Nov 2016 23:45:52 +0100 Subject: Re: How to change MAC address on RPI-B? References: <005701d23a7d$71400630$53c01290$@Kitz@xs4all.nl> <20161110065105.77a19e3b@X220.alogt.com> <000c01d23b3a$c06e1ef0$414a5cd0$@Kitz@xs4all.nl> <20161111094930.46f55a60@X220.alogt.com> <000f01d23c14$da3a6c00$8eaf4400$@Kitz@xs4all.nl> <445c56a4-2c35-cb4c-f729-950d4e758d8d@selasky.org> To: freebsd-arm@freebsd.org From: diffusae Message-ID: <8cc9d3c6-1c70-c9ac-a3a2-29f73e5ea9c3@t-online.de> Date: Sat, 12 Nov 2016 23:45:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <445c56a4-2c35-cb4c-f729-950d4e758d8d@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ID: XHhtFBZFQhSgH-z1cwlY+TF8A5OTnbIHJDFIIaVdnfC4UaCwQcb2jlX69sYRAEdZSM X-TOI-MSGID: 474c81aa-3dad-4d9c-a6b9-10254b11c997 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 22:46:02 -0000 Hi! Thanks a lot for this patch. On 11.11.2016 15:48, Hans Petter Selasky wrote: > Hi, > > Does the attached patch solve the problem? > > --HPS I've applied the patch and complied a new kernel with all modules. After that, i copied the kernel and modules to the boot partition of the RPi. I also copied the debug symbols to /usr/lib/debug/boot/kernel. Don't know if it's necessary. After rebooting I only get this error message from ifconfig: ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address smsc0: chip 0xec00, rev. 0002 ue0: link state changed to DOWN ue0: link state changed to UP No network connection without promiscuous mode. So, unfortunately it doesn't solve the problem. Or maybe I did something wrong? Best regards,