From owner-freebsd-current@freebsd.org Mon Sep 18 11:41:10 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C4B1E0A16D for ; Mon, 18 Sep 2017 11:41:10 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 108766512D for ; Mon, 18 Sep 2017 11:41:10 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id c80so251024lfh.0 for ; Mon, 18 Sep 2017 04:41:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=BozhTnkLYhkmu0J8FkghNZgHN4ZLkiAuTyfZUxkS5F0=; b=ArPC//XVcufDdxm66w9Ai0/x60rp7y/p9HjY03b1vxSRhaDIuFSlTER07dB6YJckyp tONBoZAHQYUKsNr4CvE2p85SrtsmyC+RPph+oEWTuqBOoy/DNAyPLRA1qGSO1/ujOYmS cYXlCr6Bc4oan0Z9kMhoEuKyr/i1yvBX8ne+G2d7zCrdtc4lF/Px86fd5azerDP4hP6d ZHgShWNLllKkyFOph/g0JgMYWKrqgC8RMyJroSNorS+oYKakc0vgaIh4lCvUJE+DAjW6 4Z2gUhyKmir4uPySlR5xpWSVFqYAtSa+qR6kNFmdfIx+kRqbOU05l7Gnceb5gStstslU pDWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=BozhTnkLYhkmu0J8FkghNZgHN4ZLkiAuTyfZUxkS5F0=; b=c8I96oWLJOsr6R2v0PRa7dtwWZb4LVFT0BzG9Ew/cZQpXjGDe3Eqfjr6sug/AqSYBh 8ebBqWaZEaeA7spMH/eDJP7SP0np7hZgatuXmWCiFCIr4WEORM6dwvDr0y7tCMfM0NXb LiuXOtwUxpR8ZeNDcdlXnEUXSz414F7YGTjLlZfpE/ejV97/8kjr5IX3MfrkzFXb47xd OJrABYv9pYj5wZ0/sZL28wV3E9lsLPX0ZxEKngboDPgyLqNk76jmCldyAZ5gGEdUikn5 TSaYaqOCtOLMdx7cdwcX7lMLpRFKXdgRRuieJFxaIoynjAyTQsA9h56eVrpo4tETuciC +v2g== X-Gm-Message-State: AHPjjUjKjiOE9zke9h1Vlmip5IcXkYFGafFbvLPd+uh18snzMqvZbDJ/ TsRw95aASPfhTXRjVZ0= X-Google-Smtp-Source: AOwi7QAwO4RTNjCbsQ1GWBTcBCmmZvGsF7GoDjpNr6r7OimPE2YZoZswwfL1aojh8+EVZUCCDxbLGw== X-Received: by 10.25.41.147 with SMTP id p141mr3296984lfp.56.1505734867748; Mon, 18 Sep 2017 04:41:07 -0700 (PDT) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id g132sm1416669lfe.13.2017.09.18.04.41.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Sep 2017 04:41:07 -0700 (PDT) Date: Mon, 18 Sep 2017 14:41:06 +0300 From: Vladimir Zakharov To: freebsd-current@freebsd.org Subject: lldb unusable for regular user Message-ID: <20170918114106.jkmpcde6tmvhizhj@vzakharov> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 11:41:10 -0000 Hello! lldb coredumps for regular user, but works for root. > uname -a FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r323675: Sun Sep 17 21:14:33 MSK 2017 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG amd64 > cat test.c #include #include int main() { printf("PID: %d\n", getpid()); sleep(10); return 0; } > cc -O0 -g test.c -o test > lldb ./test (lldb) target create "./test" Current executable set to './test' (x86_64). (lldb) run Process 37758 launching Process 37758 launched: './test' (x86_64) Segmentation fault (core dumped) Exit 139 > sudo lldb ./test (lldb) target create "./test" Current executable set to './test' (x86_64). (lldb) run Process 37776 launching Process 37776 launched: './test' (x86_64) PID: 37776 Process 37776 exited with status = 0 (0x00000000) (lldb) Postmortem by gdb: > gdb ./test test.core ... [New LWP 101456] Core was generated by `./test'. Program terminated with signal SIGTRAP, Trace/breakpoint trap. #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 50 { (gdb) bt #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 (gdb) f #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 50 { > gdb `which lldb` lldb.core ... Reading symbols from /usr/bin/lldb...Reading symbols from /usr/lib/debug//usr/bin/lldb.debug...done. done. [New LWP 101610] [New LWP 100968] [New LWP 100126] [New LWP 101631] [New LWP 101637] [New LWP 101662] [New LWP 101672] [New LWP 100337] [New LWP 101593] Core was generated by `lldb ./test'. Program terminated with signal SIGSEGV, Segmentation fault. #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 60 ./md-unwind-support.h: No such file or directory. [Current thread is 1 (LWP 101610)] (gdb) f #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 60 in ./md-unwind-support.h (gdb) bt #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 #1 uw_frame_state_for (context=context@entry=0x7fffddff6e20, fs=fs@entry=0x7fffddff6b70) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind-dw2.c:1249 #2 0x0000000804f6cffb in _Unwind_ForcedUnwind_Phase2 (exc=exc@entry=0x806b23230, context=context@entry=0x7fffddff6e20) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:155 #3 0x0000000804f6d334 in _Unwind_ForcedUnwind (exc=0x806b23230, stop=0x804631760 , stop_argument=) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:207 #4 0x00000008046315c3 in _Unwind_ForcedUnwind (ex=, stop_func=0xe, stop_arg=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:106 #5 thread_unwind () at /usr/src/lib/libthr/thread/thr_exit.c:172 #6 _pthread_exit_mask (status=, mask=) at /usr/src/lib/libthr/thread/thr_exit.c:254 #7 0x00000008046313eb in _pthread_exit (status=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:206 #8 0x0000000804623c0d in thread_start (curthread=0x806b23000) at /usr/src/lib/libthr/thread/thr_create.c:289 #9 0x00007fffdddf7000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffddff7000 -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Mon Sep 18 13:19:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D43CE0F9D8; Mon, 18 Sep 2017 13:19:24 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 620D168146; Mon, 18 Sep 2017 13:19:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.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 B12CF26034B; Mon, 18 Sep 2017 15:19:12 +0200 (CEST) To: FreeBSD Current , "freebsd-x11@FreeBSD.org" , Mark Johnston , "kwm@freebsd.org" , jmd@FreeBSD.org From: Hans Petter Selasky Subject: [HEADS UP] Update of graphics/drm-next-kmod is required after FreeBSD r323702 Message-ID: <67457171-5a50-bdeb-d371-1c5aa1017c17@selasky.org> Date: Mon, 18 Sep 2017 15:16:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 13:19:24 -0000 Hi, If you are using the drm-next-kmod from ports, don't upgrade your kernel beyond r323702 until the drm-next-kmod port has been updated. There are some changes planned for the LinuxKPI which can lead to memory leaks if you mix the versions together. Rebuilding the drm-next-kmod module is not enough to fix this. Possibly a FreeBSD kernel version check should be added to drm-next-kmod before building after the planned update. Thank you for the attention. --HPS From owner-freebsd-current@freebsd.org Mon Sep 18 14:07:08 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 993A6E12CA9 for ; Mon, 18 Sep 2017 14:07:08 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 23A7E6A4B4; Mon, 18 Sep 2017 14:07:07 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v8IEDCL4064044 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 18 Sep 2017 17:13:14 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v8IE6uFo002442 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Sep 2017 17:06:56 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v8IE6u0A002441; Mon, 18 Sep 2017 17:06:56 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: freebsd-current Current Cc: Conrad Meyer Subject: r323694 amd64 - crash in linsysfs: Was: svn commit: r323692 - in head/sys/compat: linsysfs linux Date: Mon, 18 Sep 2017 17:06:56 +0300 Message-ID: <1912719.8THT5byUfT@asus.theweb.org.ua> Organization: Private person User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.30; amd64; ; ) In-Reply-To: <201709172340.v8HNeGuP016998@repo.freebsd.org> References: <201709172340.v8HNeGuP016998@repo.freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 14:07:08 -0000 On Sunday 17 September 2017 23:40:16 Conrad Meyer wrote: > Author: cem > Date: Sun Sep 17 23:40:16 2017 > New Revision: 323692 > URL: https://svnweb.freebsd.org/changeset/base/323692 > > Log: > linsysfs(5): Add support for recent libdrm > > Expose more information about PCI devices (and GPUs in particular) via > linsysfs to libdrm. > > This allows unmodified modern 64-bit Linux libdrm to work, which allows > modern Linux Mesa to work. The submitter reports that he tested the > change with an Ubuntu 16.04 chroot + amdgpu from graphics/drm- next-kmod. > > PR: 222375 > Submitted by: Greg V > > Modified: > head/sys/compat/linsysfs/linsysfs.c > head/sys/compat/linux/linux_util.c > > Modified: head/sys/compat/linsysfs/linsysfs.c > Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x3f fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff81027779 stack pointer = 0x28:0xfffffe034bc66e70 frame pointer = 0x28:0xfffffe034bc66f00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 65 (mount) trap number = 12 panic: page fault cpuid = 0 time = 1505752282 Uptime: 2s ... #0 doadump (textdump=) at pcpu.h:232 232 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:232 #1 0xffffffff804d74f6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:386 #2 0xffffffff804d791c in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:779 #3 0xffffffff804d7773 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:710 #4 0xffffffff806bc877 in trap_fatal (frame=0xfffffe034bc66db0, eva=63) at /usr/src/sys/amd64/amd64/trap.c:799 #5 0xffffffff806bca59 in trap_pfault (frame=, usermode=) at pcpu.h:247 #6 0xffffffff806bc1c3 in trap (frame=0xfffffe034bc66db0) at /usr/src/sys/amd64/amd64/trap.c:420 #7 0xffffffff806a2363 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:237 #8 0xffffffff81027779 in linsysfs_run_bus (dir=) at /usr/src/sys/compat/linsysfs/linsysfs.c:357 #9 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff8000e028600) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #10 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff8000e028600) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #11 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff80004c8fe00) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #12 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff80004c8fe00) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #13 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff80004c8fe00) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #14 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff80004c8fe00) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #15 0xffffffff810278a1 in linsysfs_run_bus (dir=0xfffff80004c8fe00) at /usr/src/sys/compat/linsysfs/linsysfs.c:382 #16 0xffffffff81027194 in linsysfs_init (pi=, vfc=) at /usr/src/sys/compat/linsysfs/linsysfs.c:478 #17 0xffffffff80462773 in pfs_init (pi=0xffffffff810285e8, vfc=0xffffffff810284e0) at /usr/src/sys/fs/pseudofs/pseudofs.c:395 #18 0xffffffff805792b0 in vfs_modevent (mod=, type=, data=0xffffffff810284e0) at /usr/src/sys/kern/vfs_init.c:281 #19 0xffffffff804c09a8 in module_register_init (arg=0xffffffff810284c8) at /usr/src/sys/kern/kern_module.c:123 #20 0xffffffff804b5df6 in linker_load_module (kldname=, modname=0xfffff80004062a70 "linsysfs", parent=0x0, verinfo=, lfpp=) at /usr/src/sys/kern/kern_linker.c:234 #21 0xffffffff804b731f in kern_kldload (td=, file=, fileid=0xfffffe034bc677c4) at /usr/src/sys/kern/kern_linker.c:1042 #22 0xffffffff80578e1d in vfs_byname_kld ( fstype=0xfffff80004062a70 "linsysfs", td=0xfffff80004c1f560, error=0xfffffe034bc679ec) at /usr/src/sys/kern/vfs_init.c:147 #23 0xffffffff8057c44f in vfs_donmount (td=, fsflags=, fsoptions=0xfffff80004ca2400) at /usr/src/sys/kern/vfs_mount.c:1088 #24 0xffffffff8057ba70 in sys_nmount (td=0xfffff80004c1f560, uap=) at /usr/src/sys/kern/vfs_mount.c:421 #25 0xffffffff806bd2a2 in amd64_syscall (td=0xfffff80004c1f560, traced=0) at subr_syscall.c:132 #26 0xffffffff806a26bb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:419 #27 0x0000000800a88b3a in ?? () Previous frame inner to this frame (corrupt stack?) From owner-freebsd-current@freebsd.org Mon Sep 18 17:16:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36D17E1FB84 for ; Mon, 18 Sep 2017 17:16:22 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-yw0-f179.google.com (mail-yw0-f179.google.com [209.85.161.179]) (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 EFF9F72347 for ; Mon, 18 Sep 2017 17:16:21 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-yw0-f179.google.com with SMTP id v72so824333ywa.3 for ; Mon, 18 Sep 2017 10:16:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=8DhFa4KbIAaENh+6jPxhaspB2VibgUfyfAVrt91rOQU=; b=mWnR+ucmSt9NF6DeFFXsOCb4ZgttaGI/43fw19O8pRe9ZaB+rrLyvsnWuThNwWP6AL kV5b2JwsyFUHw9DMlNtj8gY2lX/ax1zUJvaf4bHmay/uMCnXMilHQ1WpoA7tkzSgUdy2 Nae0E1a3NpOlB3tqyeCueFpPbI1dk9GtBNknjooy115eRSZap3J65b3YrIO+cDhu3d1M ZPO6f1AljYWAzrilK5HYxfadG8r2aIG3OcA7rDB/cPt/D1JYHRidU9fa4UGKLVIh5txC JWTQP1tuv3PZa4cmKZbpUSXqWaXRRj/93fgdKzXQIEoTijqCSrzcftAya1CIDSTOtKur FJjA== X-Gm-Message-State: AHPjjUhBnklHoAyVSfwaaYTJwTJXqCJWnXBqrochmCIl3BAsE9G9EeWw T2r2pxHqHbdNgFE3rj4= X-Received: by 10.37.232.18 with SMTP id k18mr5485143ybd.304.1505754974663; Mon, 18 Sep 2017 10:16:14 -0700 (PDT) Received: from mail-io0-f171.google.com (mail-io0-f171.google.com. [209.85.223.171]) by smtp.gmail.com with ESMTPSA id b6sm3138766ywd.3.2017.09.18.10.16.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Sep 2017 10:16:14 -0700 (PDT) Received: by mail-io0-f171.google.com with SMTP id n69so3854024ioi.5 for ; Mon, 18 Sep 2017 10:16:13 -0700 (PDT) X-Google-Smtp-Source: AOwi7QAmayDlXYLS/d4bmGpTYAYQT8gIPDGAdzzXf20zmJtoAooCkawgZBUp7tiTu5/+AT7FfwyGCDH9GMBkFIhPedY= X-Received: by 10.107.97.5 with SMTP id v5mr20295844iob.174.1505754973644; Mon, 18 Sep 2017 10:16:13 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.81.131 with HTTP; Mon, 18 Sep 2017 10:16:13 -0700 (PDT) In-Reply-To: <1912719.8THT5byUfT@asus.theweb.org.ua> References: <201709172340.v8HNeGuP016998@repo.freebsd.org> <1912719.8THT5byUfT@asus.theweb.org.ua> From: Conrad Meyer Date: Mon, 18 Sep 2017 10:16:13 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r323694 amd64 - crash in linsysfs: Was: svn commit: r323692 - in head/sys/compat: linsysfs linux To: "Oleg V. Nauman" Cc: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 17:16:22 -0000 Please try r323710. I believe you're running into the issue Hans noticed here: https://lists.freebsd.org/pipermail/svn-src-all/2017-September/151324.html . It should be addressed in r323710. Sorry, Conrad From owner-freebsd-current@freebsd.org Tue Sep 19 00:40:21 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B081BE13D66 for ; Tue, 19 Sep 2017 00:40:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0059.outbound.protection.outlook.com [104.47.40.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56CDD28F7 for ; Tue, 19 Sep 2017 00:40:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR0101MB1008.CANPRD01.PROD.OUTLOOK.COM (52.132.35.30) by YTXPR0101MB2207.CANPRD01.PROD.OUTLOOK.COM (52.132.40.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.11; Tue, 19 Sep 2017 00:40:19 +0000 Received: from YTXPR0101MB1008.CANPRD01.PROD.OUTLOOK.COM ([fe80::d073:6f17:920d:d373]) by YTXPR0101MB1008.CANPRD01.PROD.OUTLOOK.COM ([fe80::d073:6f17:920d:d373%13]) with mapi id 15.20.0056.016; Tue, 19 Sep 2017 00:40:19 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" Subject: adding flex file layout support to the pNFS client Thread-Topic: adding flex file layout support to the pNFS client Thread-Index: AQHTMN8BaptWr/T0JkqLnYlYB2Lqbg== Date: Tue, 19 Sep 2017 00:40:19 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR0101MB2207; 6:RP7hBUtjGKMQpinTPwh8F9Al4W2uwTt/YfQstuIIT+BHZxhw9+P7Xlr0p8i3jftxwExk8+TC3xxoo1+jv04H2B6vTZQQ8W2W3kYOhQjswfzymlzAXk9DvCCziY43MW6LHGDBKKZ2DZAOI5x7pDHlqE+vLOCZ3EDEyoFH74jtUafrd36ddXdlsNCdpa+XrrY6BA/w0oQL1jEDltz4Np1PESrgwMR72SqsXE90tZO1cmuRtuARFCS2NUTEplp+DK1ui7QDlHoOmH8n2pGbGbm12tcQ+QqTa5FqZQU5TNXCiQDWRVKEaQTh+ud5Nn2PbHEKiemqP34E1iNy1DQ6mSUbFw==; 5:5xB6U5uFy+8FI6H2mz9xo7G29uPxDPNlITgD7kjqaEEexY6kffutuc87EDzQcS5wb84dBLCNcbeeQ9IdarjflzNXpuZ5DInKdRSVyi2vCnF806gjTE0cBSzED0EbbqKFM68xiUuCW9PQIGLx9VVeTg==; 24:Ts/zO4VCWp+DN6MvvWCrqNqUy7boyOizO1Mz90a+70Szw1hTkyp6bSzynPUeG80qx53SEduMqQY1WLFo7N/EJrgwWg4nkjfuZ85SXgei1VI=; 7:5R8COquITvbrgzacxv0VQY0M/2rCaQmTSpmiPpXXqnJCnzK2PzvmWoZbg58HI/I3mceggbwHvVqPxf+yVRCouFolzcnfFg0fTjJDVPZGwbYPbQXyRQIrGK/GgLTjneVBmUbZafly/s4Utjgw6OSr7+0S4X91n53S3784eBCtiokOfQ/nCm7+UaDnKvam2pnO668Ko4CR8TMIaJP/pZWzjlOzuv+1TuHpjQgR2DVKr2g= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: e6934e40-1075-42b1-6391-08d4fef70103 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:YTXPR0101MB2207; x-ms-traffictypediagnostic: YTXPR0101MB2207: x-exchange-antispam-report-test: UriScan:(158342451672863)(5213294742642); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(100000703101)(100105400095)(6041248)(20161123558100)(20161123560025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR0101MB2207; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR0101MB2207; x-forefront-prvs: 04359FAD81 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(376002)(39860400002)(346002)(199003)(189002)(74482002)(55016002)(5640700003)(74316002)(25786009)(6506006)(6436002)(53936002)(478600001)(7696004)(9686003)(3660700001)(5250100002)(316002)(2501003)(81156014)(81166006)(8676002)(189998001)(8936002)(305945005)(2351001)(3280700002)(101416001)(97736004)(102836003)(2906002)(106356001)(786003)(86362001)(50986999)(54356999)(14454004)(6916009)(105586002)(68736007)(5660300001)(33656002)(2900100001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR0101MB2207; H:YTXPR0101MB1008.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2017 00:40:19.2990 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR0101MB2207 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 00:40:21 -0000 Hi, I now have a series of patches that adds Flex File layout support to the NF= Sv4 client for pNFS. I am now thinking about how to get them into head. 1 - I could put them up on reviews.freebsd.org, but since they are purely N= FS patches and there is no Flex file layout server to test against (except the on= e I have in a projects tree under subversion), I doubt anyone will want to review = them. 2 - I could create another projects tree under subversion but, again, I dou= bt anyone will be able to test them and the result will be one large patch to merge = into head. 3 - I can put them in head as a series of patches and then they will be usa= ble for testing of the pNFS server in the projects area. Some of these patches are fairly large, but they should not affect current = operation of the NFS client. I am leaning towards #3, but thought I would ask others for comments w.r.t.= how I should do this? Thanks for any comments, rick From owner-freebsd-current@freebsd.org Tue Sep 19 08:28:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B5BEE04650 for ; Tue, 19 Sep 2017 08:28:51 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54771707D9 for ; Tue, 19 Sep 2017 08:28:51 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-qt0-x234.google.com with SMTP id s18so2973405qta.3 for ; Tue, 19 Sep 2017 01:28:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HcPUHKR/HteEOHuc2i7gJmGYe0sJ6sIwY1giGU0bBIY=; b=HDzenmJuX+9wSMBnnsHosbkjzAfXy356/XxHr+ecFVwfXjDFlITwvharHadkraeaAK Wk97chFH323PTmdwFhzgYXR8ksURR2z9Z6KWpg6XKxgi8HokaG2gROBh+XdZVVR+/wSF +sCpiBaJUQAs33wc99WXy0+vIGneLfpQXF/LLq00IgHzD1V+22Gzj/lcjYVxKxz92xrL fqLuw2YlaEIzod1T1Mb5p6y/Ju9ppoOn6WUfgG6EhDxBOyYozD6FsmVPLcZ6SiH9VNqS 6HbeWjhw0hvxN9wkIYNgpImcVw9VZq7QhUxqiA+yRkLz1lyGgDsNJ31lqbFLWA2MR7t/ trSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HcPUHKR/HteEOHuc2i7gJmGYe0sJ6sIwY1giGU0bBIY=; b=f1uGI5aHs5xiZ0xGVBvT4tfnKUGALMF3Hgy7O0ShwX/kLjjFL57JTDSo3N+URyXJYF MJoNOHL3IgP/B/l3yQaXM2ld3sv/AiZgZQrTZgTqm8gZcKGxRTAtzS4zcfcfJ/j1whKH 0RuJYYTEyQ0kyXs6lRkf8qdd+u+TmMEl3IKXmD/ja3rKs3ugp0KJ10L2yuOBx/HXRDLA vfJKuRPW8gaefdp7ajby8dOEGqr/hWSUJ1Qqkj/1eUA/M52WTTwaX6jroaPmy/dBWQkK iNxFzN+C9CZ93f0s1OWxCNPl+StcQWngum3ZjejFxLM9cUQPYHLigRs3wk+8pTfa9MSD et2g== X-Gm-Message-State: AHPjjUjQmxYR9+VjPHJmxyGs/MslzdAziBh9i4XZKcmi6ZA+n3LEBy3s plCwgeabeiR3ibOJt3p7VVCN9oluQo+nL6gTzQk= X-Google-Smtp-Source: AOwi7QDrinswcD8xhJWTtIg9KwBU4z5nFX31qgcJvxH225hI/g8Dm/QCI5iPe6RJG6MdzJ3xvhHfmvJqSQyUUTKD5Z8= X-Received: by 10.237.63.15 with SMTP id p15mr781124qtf.113.1505809730336; Tue, 19 Sep 2017 01:28:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.85.101 with HTTP; Tue, 19 Sep 2017 01:28:49 -0700 (PDT) In-Reply-To: <20170918114106.jkmpcde6tmvhizhj@vzakharov> References: <20170918114106.jkmpcde6tmvhizhj@vzakharov> From: Michael Zhilin Date: Tue, 19 Sep 2017 11:28:49 +0300 Message-ID: Subject: Re: lldb unusable for regular user To: Vladimir Zakharov Cc: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 08:28:51 -0000 Hi Volodya, It works for me: [mizhka@gidrarium ~/temp/20170919]$ cc -O0 -g test.c -o test [mizhka@gidrarium ~/temp/20170919]$ ./test PID: 12293 (failed reverse-i-search)`': ^C [mizhka@gidrarium ~/temp/20170919]$ ./test PID: 12294 load: 0.68 cmd: test 12294 [nanslp] 1.39r 0.00u 0.00s 0% 2316k load: 0.68 cmd: test 12294 [nanslp] 3.57r 0.00u 0.00s 0% 2316k load: 0.68 cmd: test 12294 [nanslp] 3.88r 0.00u 0.00s 0% 2316k load: 0.68 cmd: test 12294 [nanslp] 4.18r 0.00u 0.00s 0% 2316k load: 0.71 cmd: test 12294 [nanslp] 8.57r 0.00u 0.00s 0% 2316k load: 0.71 cmd: test 12294 [nanslp] 9.33r 0.00u 0.00s 0% 2316k load: 0.71 cmd: test 12294 [nanslp] 9.83r 0.00u 0.00s 0% 2316k [mizhka@gidrarium ~/temp/20170919]$ lldb ./test (lldb) target create "./test" Current executable set to './test' (x86_64). (lldb) run Process 12300 launching Process 12300 launched: './test' (x86_64) PID: 12300 Process 12300 exited with status = 0 (0x00000000) (lldb) exit [mizhka@gidrarium ~/temp/20170919]$ uname -a FreeBSD gidrarium 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r321414: Mon Jul 24 21:41:54 MSK 2017 mizhka@gidrarium:/usr/obj/usr/src/sys/GENERIC amd64 [mizhka@gidrarium ~/temp/20170919]$ type lldb lldb is hashed (/usr/bin/lldb) [mizhka@gidrarium ~/temp/20170919]$ /usr/bin/lldb -v lldb version 5.0.0 clang revision 308421 But I have r321414 with small patch: https://reviews.freebsd.org/D11738 Today/tomorrow I'll update to latest revision. Hope this information will be useful for you to identify root cause. Thanks! On Mon, Sep 18, 2017 at 2:41 PM, Vladimir Zakharov wrote: > Hello! > > lldb coredumps for regular user, but works for root. > > > uname -a > FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r323675: Sun Sep 17 > 21:14:33 MSK 2017 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG > amd64 > > cat test.c > #include > #include > > int main() > { > printf("PID: %d\n", getpid()); > sleep(10); > return 0; > } > > cc -O0 -g test.c -o test > > lldb ./test > (lldb) target create "./test" > Current executable set to './test' (x86_64). > (lldb) run > Process 37758 launching > Process 37758 launched: './test' (x86_64) > Segmentation fault (core dumped) > Exit 139 > > sudo lldb ./test > (lldb) target create "./test" > Current executable set to './test' (x86_64). > (lldb) run > Process 37776 launching > Process 37776 launched: './test' (x86_64) > PID: 37776 > Process 37776 exited with status = 0 (0x00000000) > (lldb) > > > Postmortem by gdb: > > gdb ./test test.core > ... > [New LWP 101456] > Core was generated by `./test'. > Program terminated with signal SIGTRAP, Trace/breakpoint trap. > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at > /usr/src/lib/csu/amd64/crt1.c:50 > 50 { > (gdb) bt > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at > /usr/src/lib/csu/amd64/crt1.c:50 > (gdb) f > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at > /usr/src/lib/csu/amd64/crt1.c:50 > 50 { > > > gdb `which lldb` lldb.core > ... > Reading symbols from /usr/bin/lldb...Reading symbols from > /usr/lib/debug//usr/bin/lldb.debug...done. > done. > [New LWP 101610] > [New LWP 100968] > [New LWP 100126] > [New LWP 101631] > [New LWP 101637] > [New LWP 101662] > [New LWP 101672] > [New LWP 100337] > [New LWP 101593] > Core was generated by `lldb ./test'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, > context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > 60 ./md-unwind-support.h: No such file or directory. > [Current thread is 1 (LWP 101610)] > (gdb) f > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, > context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > 60 in ./md-unwind-support.h > (gdb) bt > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, > context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > #1 uw_frame_state_for (context=context@entry=0x7fffddff6e20, fs=fs@entry=0x7fffddff6b70) > at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind-dw2.c:1249 > #2 0x0000000804f6cffb in _Unwind_ForcedUnwind_Phase2 (exc=exc@entry=0x806b23230, > context=context@entry=0x7fffddff6e20) at /wrkdirs/usr/ports/lang/gcc6/ > work/gcc-6.4.0/libgcc/unwind.inc:155 > #3 0x0000000804f6d334 in _Unwind_ForcedUnwind (exc=0x806b23230, > stop=0x804631760 , stop_argument=) at > /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:207 > #4 0x00000008046315c3 in _Unwind_ForcedUnwind (ex=, > stop_func=0xe, stop_arg=0x806b23000) at /usr/src/lib/libthr/thread/ > thr_exit.c:106 > #5 thread_unwind () at /usr/src/lib/libthr/thread/thr_exit.c:172 > #6 _pthread_exit_mask (status=, mask=) at > /usr/src/lib/libthr/thread/thr_exit.c:254 > #7 0x00000008046313eb in _pthread_exit (status=0x806b23000) at > /usr/src/lib/libthr/thread/thr_exit.c:206 > #8 0x0000000804623c0d in thread_start (curthread=0x806b23000) at > /usr/src/lib/libthr/thread/thr_create.c:289 > #9 0x00007fffdddf7000 in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffddff7000 > > -- > Regards, | "In theory there is no difference between theory > Vladimir Zakharov | and practice. In practice there is."- Yogi Berra > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue Sep 19 18:42:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D965E24029 for ; Tue, 19 Sep 2017 18:42:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB1E267545 for ; Tue, 19 Sep 2017 18:42:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 6651A10A7DB; Tue, 19 Sep 2017 14:41:59 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Vladimir Zakharov Subject: Re: lldb unusable for regular user Date: Tue, 19 Sep 2017 11:31:08 -0700 Message-ID: <1591968.Y6pkDZZxzA@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20170918114106.jkmpcde6tmvhizhj@vzakharov> References: <20170918114106.jkmpcde6tmvhizhj@vzakharov> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Tue, 19 Sep 2017 14:41:59 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 18:42:02 -0000 On Monday, September 18, 2017 02:41:06 PM Vladimir Zakharov wrote: > Hello! > > lldb coredumps for regular user, but works for root. > > > uname -a > FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r323675: Sun Sep 17 21:14:33 MSK 2017 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG amd64 > > cat test.c > #include > #include > > int main() > { > printf("PID: %d\n", getpid()); > sleep(10); > return 0; > } > > cc -O0 -g test.c -o test > > lldb ./test > (lldb) target create "./test" > Current executable set to './test' (x86_64). > (lldb) run > Process 37758 launching > Process 37758 launched: './test' (x86_64) > Segmentation fault (core dumped) > Exit 139 > > sudo lldb ./test > (lldb) target create "./test" > Current executable set to './test' (x86_64). > (lldb) run > Process 37776 launching > Process 37776 launched: './test' (x86_64) > PID: 37776 > Process 37776 exited with status = 0 (0x00000000) > (lldb) > > > Postmortem by gdb: > > gdb ./test test.core > ... > [New LWP 101456] > Core was generated by `./test'. > Program terminated with signal SIGTRAP, Trace/breakpoint trap. > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 > 50 { > (gdb) bt > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 > (gdb) f > #0 _start (ap=0x7fffffffe858, cleanup=0x800605910 ) at /usr/src/lib/csu/amd64/crt1.c:50 > 50 { > > > gdb `which lldb` lldb.core > ... > Reading symbols from /usr/bin/lldb...Reading symbols from /usr/lib/debug//usr/bin/lldb.debug...done. > done. > [New LWP 101610] > [New LWP 100968] > [New LWP 100126] > [New LWP 101631] > [New LWP 101637] > [New LWP 101662] > [New LWP 101672] > [New LWP 100337] > [New LWP 101593] > Core was generated by `lldb ./test'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > 60 ./md-unwind-support.h: No such file or directory. > [Current thread is 1 (LWP 101610)] > (gdb) f > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > 60 in ./md-unwind-support.h > (gdb) bt > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > #1 uw_frame_state_for (context=context@entry=0x7fffddff6e20, fs=fs@entry=0x7fffddff6b70) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind-dw2.c:1249 > #2 0x0000000804f6cffb in _Unwind_ForcedUnwind_Phase2 (exc=exc@entry=0x806b23230, context=context@entry=0x7fffddff6e20) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:155 > #3 0x0000000804f6d334 in _Unwind_ForcedUnwind (exc=0x806b23230, stop=0x804631760 , stop_argument=) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:207 > #4 0x00000008046315c3 in _Unwind_ForcedUnwind (ex=, stop_func=0xe, stop_arg=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:106 > #5 thread_unwind () at /usr/src/lib/libthr/thread/thr_exit.c:172 > #6 _pthread_exit_mask (status=, mask=) at /usr/src/lib/libthr/thread/thr_exit.c:254 > #7 0x00000008046313eb in _pthread_exit (status=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:206 > #8 0x0000000804623c0d in thread_start (curthread=0x806b23000) at /usr/src/lib/libthr/thread/thr_create.c:289 > #9 0x00007fffdddf7000 in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffddff7000 Your backtrace shows it crashed during thread exit inside of libthr, not in lldb itself. Also, it seems you are using libgcc_s from external gcc rather than the base system libgcc_s which is built from contrib/llvm/projects/libunwind. If lldb dlopen'd some object that depends on libgcc_s.so from ports gcc then that might explain this crash as it means you are mixing two different unwind libraries. What does 'info sharedlibrary' from gdb show? -- John Baldwin From owner-freebsd-current@freebsd.org Wed Sep 20 07:16:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB86EE27253 for ; Wed, 20 Sep 2017 07:16:50 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B4A683517; Wed, 20 Sep 2017 07:16:50 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id u21so1740582lfk.12; Wed, 20 Sep 2017 00:16:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=n7zkxbc0U6L6YPPM9Fr5nwwPvsfzpAqfWI+qw6OGrpg=; b=KAX9S1WxqBITrbszRyZuv69fPqTT8ggnyMWGE9WYHtrSXyYtxw/jOn59mOI2G+Zay4 gDPYORrQTfjFrEWMT/cQY28Q9UWX0ouykEW6gclJEYL67ntd3mpRhByjN8w1En1uoU6/ RH1G9l7njsFdOwiCtMjHwzk1qmjKG4nd8wObQIF0nc3FmtSNczaXSuZXCMUfZ5mFwek8 wlEc4urRqKFWIniYczrYLt412NyMyeRvmkM0SPXh/M20Qcm9uR6fZZdPtMZNg9ih9SAE dNnzCc9xiHSXDjh68JjwNGg0vQBZCIjn65IpB5/1e9L1fpVToACUmJcuv1PyrUNNRuAK oYPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=n7zkxbc0U6L6YPPM9Fr5nwwPvsfzpAqfWI+qw6OGrpg=; b=mbvKnoaqqe7EIN19nT6sKgB/Ldb2BXzPs8Ih5c7cd9EKY7qr0aLWGHOmNFuqaC+iww 9L+JEHNXr4BnBk97Ovv8xXzt9O1wN7CHKGMWHdMx/ORkpTiy+KeUDh/4BcubkyjA0kul vwhye40aSBiszh3XRA1jGlB2e8E3g/9AewokXP7zK85H63qKoOXsBtKPGHLXkxAPYjkg OZ/qnaX/mdkjQ119JxPtjo5KqYOKOgrqmNASYY2+t/KWtObvhS976AYYuvN46GfoYk8z QQ8U48WXKmSCLEatGvYCuZzW/f7kPiM4Ba4FjtpHvbtdSQz1hHSys4P2nnVVyktX8xUl V8LQ== X-Gm-Message-State: AHPjjUj5gPc44OXXeU6hgqeMIdxTRDHP1RWLlne+ClgJI3pqho3eXsbF Hf7KctmnassXMz4iOti4CCndIki1 X-Google-Smtp-Source: AOwi7QDs7FuLC/NkHP0MUokMUG9VvARLznDCIdXcpIl6eZ1ZSkAX1Li2hXM3H0mZefAL9hC8PBuYFA== X-Received: by 10.46.7.26 with SMTP id 26mr1748569ljh.77.1505891808244; Wed, 20 Sep 2017 00:16:48 -0700 (PDT) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id 67sm223913lfq.15.2017.09.20.00.16.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 00:16:47 -0700 (PDT) Date: Wed, 20 Sep 2017 10:16:46 +0300 From: Vladimir Zakharov To: John Baldwin Cc: freebsd-current@freebsd.org Subject: Re: lldb unusable for regular user Message-ID: <20170920071646.h3deef6crx26s5wi@vzakharov> References: <20170918114106.jkmpcde6tmvhizhj@vzakharov> <1591968.Y6pkDZZxzA@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1591968.Y6pkDZZxzA@ralph.baldwin.cx> X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 07:16:51 -0000 On Tue, Sep 19, 2017, John Baldwin wrote: > On Monday, September 18, 2017 02:41:06 PM Vladimir Zakharov wrote: > > Hello! > > > > lldb coredumps for regular user, but works for root. > > > gdb `which lldb` lldb.core > > ... > > Reading symbols from /usr/bin/lldb...Reading symbols from /usr/lib/debug//usr/bin/lldb.debug...done. > > done. > > [New LWP 101610] > > [New LWP 100968] > > [New LWP 100126] > > [New LWP 101631] > > [New LWP 101637] > > [New LWP 101662] > > [New LWP 101672] > > [New LWP 100337] > > [New LWP 101593] > > Core was generated by `lldb ./test'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > > 60 ./md-unwind-support.h: No such file or directory. > > [Current thread is 1 (LWP 101610)] > > (gdb) f > > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > > 60 in ./md-unwind-support.h > > (gdb) bt > > #0 x86_64_freebsd_fallback_frame_state (context=0x7fffddff6e20, context=0x7fffddff6e20, fs=0x7fffddff6b70) at ./md-unwind-support.h:60 > > #1 uw_frame_state_for (context=context@entry=0x7fffddff6e20, fs=fs@entry=0x7fffddff6b70) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind-dw2.c:1249 > > #2 0x0000000804f6cffb in _Unwind_ForcedUnwind_Phase2 (exc=exc@entry=0x806b23230, context=context@entry=0x7fffddff6e20) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:155 > > #3 0x0000000804f6d334 in _Unwind_ForcedUnwind (exc=0x806b23230, stop=0x804631760 , stop_argument=) at /wrkdirs/usr/ports/lang/gcc6/work/gcc-6.4.0/libgcc/unwind.inc:207 > > #4 0x00000008046315c3 in _Unwind_ForcedUnwind (ex=, stop_func=0xe, stop_arg=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:106 > > #5 thread_unwind () at /usr/src/lib/libthr/thread/thr_exit.c:172 > > #6 _pthread_exit_mask (status=, mask=) at /usr/src/lib/libthr/thread/thr_exit.c:254 > > #7 0x00000008046313eb in _pthread_exit (status=0x806b23000) at /usr/src/lib/libthr/thread/thr_exit.c:206 > > #8 0x0000000804623c0d in thread_start (curthread=0x806b23000) at /usr/src/lib/libthr/thread/thr_create.c:289 > > #9 0x00007fffdddf7000 in ?? () > > Backtrace stopped: Cannot access memory at address 0x7fffddff7000 > > Your backtrace shows it crashed during thread exit inside of libthr, not in > lldb itself. Also, it seems you are using libgcc_s from external gcc rather > than the base system libgcc_s which is built from > contrib/llvm/projects/libunwind. If lldb dlopen'd some object that depends > on libgcc_s.so from ports gcc then that might explain this crash as it means > you are mixing two different unwind libraries. What does 'info sharedlibrary' > from gdb show? You're right, John. My environment had been polluted: $ env | grep gcc LIBRARY_PATH=/usr/local/lib/gcc6 LD_LIBRARY_PATH=/usr/local/lib/gcc6 I've deleted these variables, and lldb works now as expected. Thanks a lot -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Wed Sep 20 09:25:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA6D8E04FA6 for ; Wed, 20 Sep 2017 09:25:33 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 461F163CCE for ; Wed, 20 Sep 2017 09:25:32 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([141.89.152.122]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MNO33-1e1T1J2DSj-006wqH for ; Wed, 20 Sep 2017 11:25:24 +0200 Date: Wed, 20 Sep 2017 11:25:23 +0200 From: "Hartmann, O." To: FreeBSD CURRENT Subject: src.conf: setting WITHOUT_DEBUG_FILES has no effect Message-ID: <20170920112518.5964c4d9@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:jEy8HRZD/l0exE350kA4gzwycOrWSeJ4v+Xn+kWJDtmF201Doy3 eR6g7FboBr40H3nKveiiOBkK1GI0IPW3Z7fgXUI+M5+Qjz0OnIL33pgoCuhj10eTbRAHs33 81oG7Vc9RiG9Ej9982AegqL8dT7borATW5rBOLs2zPgzh1sNrhFizbO623lTabCvbKY20eV M7wfs5AmZmI3SudKwSgbA== X-UI-Out-Filterresults: notjunk:1;V01:K0:7U/6G5vIPcw=:qb+Tz4OGklp/LpV3jwSHRi ZQ4xgjlKtkjddlBFIDRuH8Ov/1Y3yXb93Oft8r1gEnVO5RQ/Vj1JgnoYBLkpd9qedMjIihLf0 EBwioYKDXXz4YxWOXg8RqWtKVbM3nj9WCi1CWpJcXa9Efxsbqs3fka0CATAx1XizI1gT/nMR1 lYTuv4MRg1YB6vh+C5mgl7+dtqYWmxXLpbvMowE4m2Jr9gYitDivDLKIACURExsL4Xpjr42+r bV6/jD6yxA/q3YH0W8G8FBNrXp+sF9q/bzIcr5S44v8XN6stGwMay9UtX5AksyFv4yttUMNSS jcd+/1wPNKY3nw5lIOjt0x1cQChBm5FHOuNYPu/VSmm4hfjKsRzfAaYx6SUS6RVdQePW7RJaO IGn9+lnqhJNIN3lWRnuuqJeTt2QK2FSVK5LUkI1JsKjlZejj4vGCZZndG91uMMst++07MG/O5 p/0/TwnJLRmgZC8DmcVCVqz8qIF86vj3tNrI2vcIkuUroL5kIl+5gbsFo3ZQyBQv3VltrV4yk Z9wrwgR2esTo/2c7hKefkuaHynGt7cT9gkXMB9Y+p8HzlSMUYS3SCqgsxlPHFYIccyAcrz5Ak Mv0Qf93zwbonBLtrM0d6Na+iqZa3V40OVBkU0nvX563AVnAvn5P7UWMRt2XcCEyZ9qfIuzYcw lZSECHA0sJ3iSwVtLuWMRk8f1XJFB6RTdCjDSi6WHnkJWtVki9LmSz3rM46GNfPjwl/Vp6325 G+KUjiOAS30odaWfpyic+zRFlYXyMZBjV9TDcAiMld8bD4Z1xJwhM8+6r/M4YItPND40/vtxK paJBorJfH0MxbDmpHXhRwERD1bi9Bzd1VdE31x9uNY0gyhR/14= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 09:25:34 -0000 Setting WITHOUT_DEBUG_FILES=YES in /etc/src.conf is supposed to prevent building debug files for shared libs and binaries - that is my interpretation of the manpage of src.conf(5). After each run of buildworld buildkernel && installkernel && installworld and performing a make delete-old the cleaning skript picks up lots of files every time after a rebuild and installation of world situated in /usr/lib/debug/usr/tests/XXX Is this hardcoded? Or do I miss here some extra knob? Or is it a bug? Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Wed Sep 20 12:52:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57049E0D44E for ; Wed, 20 Sep 2017 12:52:05 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 422876A649 for ; Wed, 20 Sep 2017 12:52:05 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 41752E0D44D; Wed, 20 Sep 2017 12:52:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4105FE0D44C for ; Wed, 20 Sep 2017 12:52:05 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (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 DC3026A647 for ; Wed, 20 Sep 2017 12:52:04 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [192.168.0.135] (197-234-181-199.cipherwave.net [197.234.181.199] (may be forged)) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id v8KCoJAb003153; Wed, 20 Sep 2017 13:50:19 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Removal of catman from base From: Bob Bishop In-Reply-To: <78909.1505251253@critter.freebsd.dk> Date: Wed, 20 Sep 2017 13:50:16 +0100 Cc: Gordon Tetlow , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170912184200.GD99742@gmail.com> <77524.1505242222@critter.freebsd.dk> <78909.1505251253@critter.freebsd.dk> To: Lyndon Nerenberg , Poul-Henning Kamp X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 12:52:05 -0000 Hi, > On 12 Sep 2017, at 22:20, Poul-Henning Kamp = wrote: >=20 > -------- > In message , Lyndon = Nerenberg writes: >>> That was actually not why catman was brought into the world: = ATT/USL >>> thought text-processing was The Goods so they unbundled it base SVR >>> and invented catman to make up for the missing nroff. >>=20 >> Not quite. They (AT&T) sold the rights to sell typeset manuals to = some=20 >> publishing house (I forget which), at which point they stopped = shipping=20 >> the *roff source for the manpages on the source tapes. Instead, you = got=20 >> pre-formatted "cat" pages on the source tape. I think this happened=20= >> starting with SVR3. That is correct. We wrote some excruciatingly ugly scripts that mostly = reconstructed the *roff source from the formatted pages. > I'm pretty sure that SVR1 had catman and roff was an extra and = somewhat > pricey software package. That is also correct: by SVR5 that had become the Documenter=E2=80=99s = Workbench (DWB). > --=20 > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe =20 > Never attribute to malice what can adequately be explained by = incompetence. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" >=20 -- Bob Bishop rb@gid.co.uk From owner-freebsd-current@freebsd.org Thu Sep 21 03:10:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F89AE0DA34 for ; Thu, 21 Sep 2017 03:10:14 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 719F86578D for ; Thu, 21 Sep 2017 03:10:14 +0000 (UTC) (envelope-from jon@brawn.org) Received: by mailman.ysv.freebsd.org (Postfix) id 70690E0DA33; Thu, 21 Sep 2017 03:10:14 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D6A8E0DA32 for ; Thu, 21 Sep 2017 03:10:14 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mx2.ahs1.r4l.com (mx2.ahs1.r4l.com [192.95.23.229]) (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 448EF6578C for ; Thu, 21 Sep 2017 03:10:14 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=To:Date:Message-Id:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ja5q0W8gCX+1IttNpnpKX/9LoWUfjS+5o5f9tkrIZJw=; b=r3t2UjsdIGGdrjVNTLnfGK/yN4 oo7NIeOq9+KU8rtb5BbNerktSYR28qy7frKCGu8tUSvIu/JklVW2MYkBRO9LNhNnk+s6kWy/MDu0x U0sYCUaXaLU1XYsR2AZMifcSRZQOS2RQ8QuWYbVtzjdBnPw8MmkLEixIvsoPIkLdM471bCzz9HJ2x 9GCuPVNbAuB+Ln04Yy1zfrfEEgZExR0JMhd9c5kWs3zwGtuygM9I4xcbqiuVIEE+J85n0ZbwIpS3A 2YkSoLruF1h1FWWFVrZFPu8LU6Hd6/I2AlCx/MK6MiI7uXrRG/mvwckLSLoBcCKRcCSUHahHgLl5C CCiNiVGg==; Received: from [136.62.171.86] (port=49635 helo=[192.168.1.159]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1durZf-0049Bi-Uh for current@freebsd.org; Wed, 20 Sep 2017 22:50:48 -0400 From: Jon Brawn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Pre-filled RAM disk. Message-Id: Date: Wed, 20 Sep 2017 21:50:46 -0500 To: current@freebsd.org X-Mailer: Apple Mail (2.3273) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:10:14 -0000 Wotcha! I work for Arm for my sins, and in my spare time I=E2=80=99ve been = playing with FreeBSD. In my day job I work with the CPU core validation = team, and one of the things we do is take the hardware design of a new = core and run it on a machine called an emulator. This emulator isn=E2=80=99= t the same thing as QEMU, nor is it just an FPGA, it=E2=80=99s something = in the middle - you compile the hardware design and download it to the = emulator, and it can then run programs on your design at about 1MHz. = Which is lovely. Our main bread and butter is to take such a design and = get it to boot Arm Linux, a very cut down version, and then run some = tests hosted in the Linux environment. These tests would typically = thrash the snot out of some particular aspect of the architecture, such = as memory sharing amongst multiple processor cores. Now, we would like = to use other operating systems that behave differently to Linux, there = are some obvious candidates that I=E2=80=99m not going to talk about for = legal reasons, but one that was suggested was using FreeBSD under = emulation. So, what is needed is someway of telling the operating system that it is = going to use a ram disk for its root filesystem, and that the ram disk = is going to be at a fixed physical address in the memory map. That way = we can pre-load root from a file in the emulation environment. In the = Linux environment we would package the kernel, it=E2=80=99s DRB and the = root filesystem memory image inside a light-weight bootloader wrapper, = load that at the right offset into the emulator=E2=80=99s memory map, = and twang the virtual reset line of the emulated processor. There=E2=80=99= s some magic jiggery pokery to get console output from what the OS = thinks is an AMBA UART, but that=E2=80=99s about size of it. So, what does FreeBSD have to offer in the way of ramdisk functionality? Jon.= From owner-freebsd-current@freebsd.org Thu Sep 21 03:14:46 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CC7DE0DFE3 for ; Thu, 21 Sep 2017 03:14:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id ED38265C1B for ; Thu, 21 Sep 2017 03:14:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EC165E0DFDF; Thu, 21 Sep 2017 03:14:45 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB897E0DFDE for ; Thu, 21 Sep 2017 03:14:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C9B565C1A for ; Thu, 21 Sep 2017 03:14:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id l196so4508177lfl.1 for ; Wed, 20 Sep 2017 20:14:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=x2Q9FYF9JawJtYHsElSFQ5NMnQO3b8J9h9CnpnvHlIw=; b=lxE9+bc4qA/UOsn3nrIo8fwGNuVV9zZm8pk3JEMbxUOyQyA629bLWBtgrOFoUsUD07 WfbtxxZXJBqAmxapeyytoGY1NsmoQUuFPdB2nqmHGHgNSyhiW99y2YMlIddPnq/zRM2f P5e5vf0s6koxcY1XJshxFILut+rJ8PrbBFAin1jhYH1qwv1rkTXOAsfE1VmzC1ojpUJ3 NtzWR20f0nydXG0qIOip9H6IddkP0Pu1zVO3NdocfxGVBBUAS+kIkdby8cJHnp8OZ8bI 7kPAS4J8J5IxNCH6f2iT+gBI2BsfGtLG7sWevqrdZOcmKR/yDe8wryq31mwM7hQVP8l0 cwEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=x2Q9FYF9JawJtYHsElSFQ5NMnQO3b8J9h9CnpnvHlIw=; b=rdRZx6D4clP0xqFILBamxn/n5Ghmkf5E+fZaaXCUAIoUtXzB1gglNIfK+wIMzbcNUL VXTJt6ZT4TPEql/1k1gQb5PstQTyde2kAhT51px9xNHltVrBvdTubOiUSVCeAGcPyRAI dDp0cqKyBFCIWAn8KhL8sHCKUlEDsIXaMfyKX37weJYGdndVXxadMTtr0x2PotmleSlL GIRGcgFI2jh87/5jBDxGlRaoz+MZlFIomb0n4JTRbMcYaoaIQYUAwTieO46CBmuEABhn V3uQXS4NkvtY7jpCAtPabdAOPtNXJajJZ2b5yyBRVNwp24L8O5qJxEDxoToqmqr6q3Gf wu+w== X-Gm-Message-State: AHPjjUhluRzutLSa1ApKcgzcELjQRHE3Ea0sM4lu81M0Fbuvk/rARepy Bc+W5bfL5T/LhVkvJb3Dj1NgacHwTwOWPVKAD0QSSQ== X-Google-Smtp-Source: AOwi7QDUottKywPkN643VJs9P5hIdZmVQG7e/w3KsiSaR1XnE31uChWPdX5ilqOZezHNjcg5itFTsfd+pyCjsGIH3qA= X-Received: by 10.46.27.6 with SMTP id b6mr311830ljb.123.1505963683142; Wed, 20 Sep 2017 20:14:43 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.26.6 with HTTP; Wed, 20 Sep 2017 20:14:42 -0700 (PDT) In-Reply-To: References: From: Alan Somers Date: Wed, 20 Sep 2017 21:14:42 -0600 X-Google-Sender-Auth: 2o8LdKGzZrjxdDv06kU_QhnceLg Message-ID: Subject: Re: Pre-filled RAM disk. To: Jon Brawn Cc: "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:14:46 -0000 On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: > Wotcha! > > I work for Arm for my sins, and in my spare time I=E2=80=99ve been playin= g with FreeBSD. In my day job I work with the CPU core validation team, and= one of the things we do is take the hardware design of a new core and run = it on a machine called an emulator. This emulator isn=E2=80=99t the same th= ing as QEMU, nor is it just an FPGA, it=E2=80=99s something in the middle -= you compile the hardware design and download it to the emulator, and it ca= n then run programs on your design at about 1MHz. Which is lovely. Our main= bread and butter is to take such a design and get it to boot Arm Linux, a = very cut down version, and then run some tests hosted in the Linux environm= ent. These tests would typically thrash the snot out of some particular asp= ect of the architecture, such as memory sharing amongst multiple processor = cores. Now, we would like to use other operating systems that behave differ= ently to Linux, there are some obvious candidates that I=E2=80=99m not goin= g to talk about for legal reasons, but one that was suggested was using Fre= eBSD under emulation. > > So, what is needed is someway of telling the operating system that it is = going to use a ram disk for its root filesystem, and that the ram disk is g= oing to be at a fixed physical address in the memory map. That way we can p= re-load root from a file in the emulation environment. In the Linux environ= ment we would package the kernel, it=E2=80=99s DRB and the root filesystem = memory image inside a light-weight bootloader wrapper, load that at the rig= ht offset into the emulator=E2=80=99s memory map, and twang the virtual res= et line of the emulated processor. There=E2=80=99s some magic jiggery poker= y to get console output from what the OS thinks is an AMBA UART, but that= =E2=80=99s about size of it. > > So, what does FreeBSD have to offer in the way of ramdisk functionality? > > Jon. Cool project! There is something called MFSBSD which is basically exactly what you want. It creates a small ramdisk and boots from that. It's often used for stuff like booting from PXE, CD, or USB. I don't know if you can force it to be located at a specific memory address, though. It's normally used in combination with a bootloader. http://mfsbsd.vx.sk/ -Alan From owner-freebsd-current@freebsd.org Thu Sep 21 03:16:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A5AAE0E229 for ; Thu, 21 Sep 2017 03:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4592C65DCB for ; Thu, 21 Sep 2017 03:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 44D72E0E228; Thu, 21 Sep 2017 03:16:44 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44641E0E227 for ; Thu, 21 Sep 2017 03:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D13E65DCA for ; Thu, 21 Sep 2017 03:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id v36so8068592ioi.1 for ; Wed, 20 Sep 2017 20:16:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=4BHC22q2E4S/16XkLqHZRe0P3KENb8bvtpVc6YHW2aY=; b=ZTDmhc+sfCNodsJvibr6f7x89uqfptU6lDk81GK2brv7oRuDSGgL92AEzApIl5eToz 2l5WkEAgymQW9Y31B0mICjPTGEDO/+AsDheRkcslnrnspz26ifliRR0XtbsmUSycCCMz YYPj9GfOi4VisQOvDTDNAZzN53wI6twxCiTaZXgn2qAifJ7T9z+5uBV+6F8nGMLzJEW6 4nEX86Dq5klXobCqWhTRmuqSPh3dQlPaH8XEQ3OjzQc3F3s/DQytgNTkIeX35lYrbQc2 wShsCuBP5XHeO71l7qQfp71upOIjHeOhwmyufQPbmvq3602SPEYrCu7+CawqO6ivibXe OiZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=4BHC22q2E4S/16XkLqHZRe0P3KENb8bvtpVc6YHW2aY=; b=OmOBZ2VPvbyg+tifO2v69MHZKuSANj9hkycX4JNarxJvGyKXRQVWGp/UGzT7rtk7vq 9tIZeHOc8LyJ69nMsd0BEYiz6wkPrBcfHu3w0KY808nMy4N7QnwlLbtzRDthS6wPSGNE opl7YpoaatMwZPeWgcPCRtzze/AOJjLDIEquvLjZG0WDpQkC9Nej6chWbZ5YXlRn5seW 5RfHWkmsdZDPZsnlatqwhcibwubky9lPdXhsCWvmLexzQe8pTBlLbzF8gpxGl+TC7JHn tYS1nfAfGAuBnclJm6vEr53xWOvMIqU5Vr3E9k03wsUG6f8Z5Q03ITWa9njtizfBwdjA k4Dg== X-Gm-Message-State: AHPjjUi8xwBdyXEmZWqi5Q/fUYWY+7kZQvM19QOiH451p1L48UxSO1MI QPRzfKMxNxbJiEUwifyApZatKvcIqGO+t0Esp5akGg== X-Google-Smtp-Source: AOwi7QA8OnFPd5UBFNnlKBiFOeb6s33GOti4Ax5ZYlc8WPwKnNyQot47AzgkbAiQvKCZux8Vazpwv8vFF32aiIyqcU0= X-Received: by 10.107.7.161 with SMTP id g33mr1013114ioi.169.1505963803282; Wed, 20 Sep 2017 20:16:43 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.2.194 with HTTP; Wed, 20 Sep 2017 20:16:42 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Wed, 20 Sep 2017 21:16:42 -0600 X-Google-Sender-Auth: U4BRVTHh97VZN4qveqAzufDsPFM Message-ID: Subject: Re: Pre-filled RAM disk. To: Jon Brawn Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:16:44 -0000 On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: > Wotcha! > > I work for Arm for my sins, and in my spare time I=E2=80=99ve been playin= g with > FreeBSD. In my day job I work with the CPU core validation team, and one = of > the things we do is take the hardware design of a new core and run it on = a > machine called an emulator. This emulator isn=E2=80=99t the same thing as= QEMU, nor > is it just an FPGA, it=E2=80=99s something in the middle - you compile th= e hardware > design and download it to the emulator, and it can then run programs on > your design at about 1MHz. Which is lovely. Our main bread and butter is = to > take such a design and get it to boot Arm Linux, a very cut down version, > and then run some tests hosted in the Linux environment. These tests woul= d > typically thrash the snot out of some particular aspect of the > architecture, such as memory sharing amongst multiple processor cores. No= w, > we would like to use other operating systems that behave differently to > Linux, there are some obvious candidates that I=E2=80=99m not going to ta= lk about > for legal reasons, but one that was suggested was using FreeBSD under > emulation. > > So, what is needed is someway of telling the operating system that it is > going to use a ram disk for its root filesystem, and that the ram disk is > going to be at a fixed physical address in the memory map. That way we ca= n > pre-load root from a file in the emulation environment. In the Linux > environment we would package the kernel, it=E2=80=99s DRB and the root fi= lesystem > memory image inside a light-weight bootloader wrapper, load that at the > right offset into the emulator=E2=80=99s memory map, and twang the virtua= l reset > line of the emulated processor. There=E2=80=99s some magic jiggery pokery= to get > console output from what the OS thinks is an AMBA UART, but that=E2=80=99= s about > size of it. > > So, what does FreeBSD have to offer in the way of ramdisk functionality? > Yes. See MD_ROOT and friends. Warner From owner-freebsd-current@freebsd.org Thu Sep 21 03:23:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9565AE0E9BB for ; Thu, 21 Sep 2017 03:23:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6F207664D7 for ; Thu, 21 Sep 2017 03:23:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6E2DAE0E9BA; Thu, 21 Sep 2017 03:23:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DB63E0E9B9 for ; Thu, 21 Sep 2017 03:23:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 300E9664D6 for ; Thu, 21 Sep 2017 03:23:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id y126so4151743itb.5 for ; Wed, 20 Sep 2017 20:23:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rcOWy7oEW6bODkDcc1a02QEfLEXTWL9dOtQFSEnVduA=; b=Aey1WqgK+Tp36IDL40BRsKBwOwJ3vH8V2jCVN0Qiur6H+x5do3PNdyRrZYerx/Kbs3 ZklNU3yXByMhcd3xKF7s+5xNfoxkyCwpFwAgQ2ANqVf8IkMtyUPhAOQl+nMEwbxWwcc7 fG68UU6xqyADo/Lm8P7lAbyO/5PkPPvnaDnJQndvJF3dkVjEIlV0IFmK8jK+1ALvCeko yt5mkNtgeiZqIqOWDq/JsoNJJu9JjSQoPn6kQmydr2r0QToJ+ygyhRJ09tqlPEhh/701 7RwhufNIr8eqk/2t0cXtxO201rVviZjBk97URAihe1Abh/cJIWH0cV80Dq4htTmvv34d eejQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rcOWy7oEW6bODkDcc1a02QEfLEXTWL9dOtQFSEnVduA=; b=tTngYLRXnURqsmrx7y1SqQwreW+gx/MsFeEpVxOxKfiKk5uRy28hfoYEi8ecUjqO9T rxo8pdIdULSIhdSjJgbm/ig6sqx/xWWj2yrZ3xGMz7gO1vVVhkJjhlEtBnIX4brYkjdf KXZkgVhDfhk0IqEXdmMBttappDAsNocSXI44d5Rnu7LshgDha4qNPfFFoabD2Sr4JdAK KAy4wTgoW6ZhYpTj5HYlboyIRFM+a1f+DPwMlpgwRE7rnlKdhpX/MxIEZhrUodlS6Odt I/83Mpt//aPQB5fWjDbb2XSPKUo5o9PPuqoCix0RjRAtVggGsiOD7J/GrbXKPhd/Wqx9 b6cg== X-Gm-Message-State: AHPjjUiunPmYeoXMSP8EzPIe10I71TAtQejIChkOkMsdXClWkxLQO+nK eLNDOMdkZkeiydMDutWxWjyuKUJgPR7hXZjHp2n43A== X-Google-Smtp-Source: AOwi7QDxgzFRg5buRC/4VlAjmJ3kpwRjx6AkCkd5Sw+nYYHSqllCvMDV9c/LYa4SYVId87uCWcTT9uT/mO4NSTl0xfU= X-Received: by 10.36.6.18 with SMTP id 18mr3101141itv.15.1505964181562; Wed, 20 Sep 2017 20:23:01 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.2.194 with HTTP; Wed, 20 Sep 2017 20:23:00 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Wed, 20 Sep 2017 21:23:00 -0600 X-Google-Sender-Auth: e9fvYwoe1PbR4-uVg7scaHuXedg Message-ID: Subject: Re: Pre-filled RAM disk. To: Jon Brawn Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:23:02 -0000 On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh wrote: > > > On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: > >> Wotcha! >> >> I work for Arm for my sins, and in my spare time I=E2=80=99ve been playi= ng with >> FreeBSD. In my day job I work with the CPU core validation team, and one= of >> the things we do is take the hardware design of a new core and run it on= a >> machine called an emulator. This emulator isn=E2=80=99t the same thing a= s QEMU, nor >> is it just an FPGA, it=E2=80=99s something in the middle - you compile t= he hardware >> design and download it to the emulator, and it can then run programs on >> your design at about 1MHz. Which is lovely. Our main bread and butter is= to >> take such a design and get it to boot Arm Linux, a very cut down version= , >> and then run some tests hosted in the Linux environment. These tests wou= ld >> typically thrash the snot out of some particular aspect of the >> architecture, such as memory sharing amongst multiple processor cores. N= ow, >> we would like to use other operating systems that behave differently to >> Linux, there are some obvious candidates that I=E2=80=99m not going to t= alk about >> for legal reasons, but one that was suggested was using FreeBSD under >> emulation. >> >> So, what is needed is someway of telling the operating system that it is >> going to use a ram disk for its root filesystem, and that the ram disk i= s >> going to be at a fixed physical address in the memory map. That way we c= an >> pre-load root from a file in the emulation environment. In the Linux >> environment we would package the kernel, it=E2=80=99s DRB and the root f= ilesystem >> memory image inside a light-weight bootloader wrapper, load that at the >> right offset into the emulator=E2=80=99s memory map, and twang the virtu= al reset >> line of the emulated processor. There=E2=80=99s some magic jiggery poker= y to get >> console output from what the OS thinks is an AMBA UART, but that=E2=80= =99s about >> size of it. >> >> So, what does FreeBSD have to offer in the way of ramdisk functionality? >> > > Yes. > > See MD_ROOT and friends. > The MFS_IMAGE kernel option has replaced this. Warner From owner-freebsd-current@freebsd.org Thu Sep 21 03:47:18 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26E17E0FC1C for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 05BB366E2B for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: by mailman.ysv.freebsd.org (Postfix) id 050E1E0FC1B; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04A9FE0FC1A for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mx2.ahs1.r4l.com (mx2.ahs1.r4l.com [192.95.23.229]) (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 CC37A66E2A; Thu, 21 Sep 2017 03:47:17 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type: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=VjFtQXS0OxVIWuiSIjpxMb96jekGbWPj4z9iRos+2kw=; b=UBbPCB/3WmVKlYxDgWdQyz77Cl Hkbe5Y5npz79v0AlZmBDHdSAT3MCcz1Jz2UUYZz0zRL1Diq7SJnWgDOU8+TB7NkCMkDoeipW/Vk6f WJTAoIil9YlYIDfVTkLbUoVW8pje4mOVo3mEE3gU4mnY3QxvMoMPOJh+xabKIjH4pza4S/vQLkKpK L2fDARp/4sGW3zTDA83kcPy3JBDPsbuDAenvjkE3fyg4o/fpjH+h8RBVbk5t2N9jYMEqGvjjNdCFU Vy+aw/8jhWliUxs+Eh5gi8q1fVO44XzYgzlWK/e170UsQDuUEMxlx38IRZ2gwvoa8c9HaJuMQNgTK ULlE4uMg==; Received: from [136.62.171.86] (port=49878 helo=[192.168.1.159]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dusSJ-004EtY-Ql; Wed, 20 Sep 2017 23:47:16 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Pre-filled RAM disk. From: Jon Brawn In-Reply-To: <1505964913.73082.65.camel@freebsd.org> Date: Wed, 20 Sep 2017 22:47:12 -0500 Cc: FreeBSD Current , Warner Losh Content-Transfer-Encoding: quoted-printable Message-Id: <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> References: <1505964913.73082.65.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3273) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:47:18 -0000 On Sep 20, 2017, at 10:35 PM, Ian Lepore wrote: >=20 > On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: >> On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh wrote: >>=20 >>> On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: >>>=20 >>>>=20 >>>> Wotcha! >>>>=20 >>>> >>>> So, what does FreeBSD have to offer in the way of ramdisk >>>> functionality? >>>>=20 >>> Yes. >>>=20 >>> See MD_ROOT and friends. >>>=20 >> The MFS_IMAGE kernel option has replaced this. >>=20 >> Warner >=20 > And the documentation (such as it is) for MFS_IMAGE is in the md(4) > manpage. In a nutshell, it's a mechanism that lets you compile an > existing filesystem image directly into the kernel and it is mounted = as > a memory filesystem at boot time. Hopefully being contained within = the > kernel will make the problem of loading it at a fixed physical address > go away for you. >=20 > -- Ian >=20 I really need to bring more of my work problems to this list, obviously. = Thanks folks! Jon.= From owner-freebsd-current@freebsd.org Thu Sep 21 03:51:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEF09E100AE for ; Thu, 21 Sep 2017 03:51:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9D36067151 for ; Thu, 21 Sep 2017 03:51:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9C48FE100AD; Thu, 21 Sep 2017 03:51:32 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B993E100AC for ; Thu, 21 Sep 2017 03:51:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from bat.yew.relay.mailchannels.net (bat.yew.relay.mailchannels.net [23.83.220.13]) (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 6B5D46714C for ; Thu, 21 Sep 2017 03:51:30 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id C279612A612 for ; Thu, 21 Sep 2017 03:35:21 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.147.57]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 2051F12A622 for ; Thu, 21 Sep 2017 03:35:20 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.107.195]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Thu, 21 Sep 2017 03:35:21 +0000 X-MC-Relay: Junk X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Absorbed-Obese: 4193011f75005457_1505964921590_325726657 X-MC-Loop-Signature: 1505964921590:80548277 X-MC-Ingress-Time: 1505964921589 X-MHO-User: e13cd544-9e7d-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id e13cd544-9e7d-11e7-a893-25625093991c; Thu, 21 Sep 2017 03:35:15 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8L3ZDX5014106; Wed, 20 Sep 2017 21:35:13 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1505964913.73082.65.camel@freebsd.org> Subject: Re: Pre-filled RAM disk. From: Ian Lepore To: Jon Brawn Cc: FreeBSD Current , Warner Losh Date: Wed, 20 Sep 2017 21:35:13 -0600 In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:51:32 -0000 On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: > On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh wrote: >=20 > >=20 > >=20 > >=20 > > On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: > >=20 > > >=20 > > > Wotcha! > > >=20 > > > I work for Arm for my sins, and in my spare time I=A2ve been > > > playing with > > > FreeBSD. In my day job I work with the CPU core validation team, > > > and one of > > > the things we do is take the hardware design of a new core and > > > run it on a > > > machine called an emulator. This emulator isn=A2t the same thing as > > > QEMU, nor > > > is it just an FPGA, it=A2s something in the middle - you compile > > > the hardware > > > design and download it to the emulator, and it can then run > > > programs on > > > your design at about 1MHz. Which is lovely. Our main bread and > > > butter is to > > > take such a design and get it to boot Arm Linux, a very cut down > > > version, > > > and then run some tests hosted in the Linux environment. These > > > tests would > > > typically thrash the snot out of some particular aspect of the > > > architecture, such as memory sharing amongst multiple processor > > > cores. Now, > > > we would like to use other operating systems that behave > > > differently to > > > Linux, there are some obvious candidates that I=A2m not going to > > > talk about > > > for legal reasons, but one that was suggested was using FreeBSD > > > under > > > emulation. > > >=20 > > > So, what is needed is someway of telling the operating system > > > that it is > > > going to use a ram disk for its root filesystem, and that the ram > > > disk is > > > going to be at a fixed physical address in the memory map. That > > > way we can > > > pre-load root from a file in the emulation environment. In the > > > Linux > > > environment we would package the kernel, it=A2s DRB and the root > > > filesystem > > > memory image inside a light-weight bootloader wrapper, load that > > > at the > > > right offset into the emulator=A2s memory map, and twang the > > > virtual reset > > > line of the emulated processor. There=A2s some magic jiggery pokery > > > to get > > > console output from what the OS thinks is an AMBA UART, but > > > that=A2s about > > > size of it. > > >=20 > > > So, what does FreeBSD have to offer in the way of ramdisk > > > functionality? > > >=20 > > Yes. > >=20 > > See MD_ROOT and friends. > >=20 > The MFS_IMAGE kernel option has replaced this. >=20 > Warner And the documentation (such as it is) for MFS_IMAGE is in the md(4) manpage. =A0In a nutshell, it's a mechanism that lets you compile an existing filesystem image directly into the kernel and it is mounted as a memory filesystem at boot time. =A0Hopefully being contained within the kernel will make the problem of loading it at a fixed physical address go away for you. -- Ian From owner-freebsd-current@freebsd.org Thu Sep 21 05:10:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3C04E138D3 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B0B14695D5 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AFFAFE138D2; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF9AFE138D1 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from nov-007-i577.relay.mailchannels.net (nov-007-i577.relay.mailchannels.net [46.232.183.131]) (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 525D4695D0 for ; Thu, 21 Sep 2017 05:10:01 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id E751636A429 for ; Thu, 21 Sep 2017 03:50:56 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.147.57]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 53B88368A0B for ; Thu, 21 Sep 2017 03:50:56 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.72.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Thu, 21 Sep 2017 03:50:56 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Spill-Descriptive: 6ea39ab13f4ee63b_1505965856714_550263714 X-MC-Loop-Signature: 1505965856714:2905040376 X-MC-Ingress-Time: 1505965856713 X-MHO-User: 0eab0e3c-9e80-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 0eab0e3c-9e80-11e7-a893-25625093991c; Thu, 21 Sep 2017 03:50:51 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8L3omOm014138; Wed, 20 Sep 2017 21:50:48 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1505965848.73082.69.camel@freebsd.org> Subject: Re: Pre-filled RAM disk. From: Ian Lepore To: Jon Brawn Cc: FreeBSD Current , Warner Losh Date: Wed, 20 Sep 2017 21:50:48 -0600 In-Reply-To: <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> References: <1505964913.73082.65.camel@freebsd.org> <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 05:10:06 -0000 On Wed, 2017-09-20 at 22:47 -0500, Jon Brawn wrote: > On Sep 20, 2017, at 10:35 PM, Ian Lepore wrote: > >=20 > >=20 > > On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: > > >=20 > > > On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh > > > wrote: > > >=20 > > > >=20 > > > > On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn > > > > wrote: > > > >=20 > > > > >=20 > > > > >=20 > > > > > Wotcha! > > > > >=20 > > > > > > > > > > So, what does FreeBSD have to offer in the way of ramdisk > > > > > functionality? > > > > >=20 > > > > Yes. > > > >=20 > > > > See MD_ROOT and friends. > > > >=20 > > > The MFS_IMAGE kernel option has replaced this. > > >=20 > > > Warner > > And the documentation (such as it is) for MFS_IMAGE is in the md(4) > > manpage.=A0=A0In a nutshell, it's a mechanism that lets you compile a= n > > existing filesystem image directly into the kernel and it is > > mounted as > > a memory filesystem at boot time.=A0=A0Hopefully being contained with= in > > the > > kernel will make the problem of loading it at a fixed physical > > address > > go away for you. > >=20 > > -- Ian > >=20 > I really need to bring more of my work problems to this list, > obviously. Thanks folks! >=20 > Jon. > _______________________________________________ Another good place for help with freebsd on arm is the #bsdmips channel on efnet, if you're an irc-using kind of person. =A0Don't let the 'mips' in the name throw you, it's the channel where the arm, powerpc, and mips developers hang out. Oh, and of course, there is also the freebsd-arm@ mailing list. -- Ian From owner-freebsd-current@freebsd.org Thu Sep 21 17:40:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2BE1E14CDE for ; Thu, 21 Sep 2017 17:40:28 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1.freebsd.org (Postfix) with ESMTP id C2D0B3B6D for ; Thu, 21 Sep 2017 17:40:27 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 778971D58C15 for ; Thu, 21 Sep 2017 10:40:21 -0700 (MST) Date: Thu, 21 Sep 2017 10:40:21 -0700 (MST) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1506015621453-0.post@n6.nabble.com> In-Reply-To: <20170920112518.5964c4d9@hermann> References: <20170920112518.5964c4d9@hermann> Subject: Re: src.conf: setting WITHOUT_DEBUG_FILES has no effect MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 17:40:28 -0000 I saw this few weeks ago with -STABLE. It's only recently that make delete-old delete debug files, so it might started a lot earlier that we think. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html From owner-freebsd-current@freebsd.org Fri Sep 22 13:00:39 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3198E27EE0 for ; Fri, 22 Sep 2017 13:00:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4A06B0C7 for ; Fri, 22 Sep 2017 13:00:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA11820 for ; Fri, 22 Sep 2017 16:00:36 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dvNZL-0008ke-W7 for freebsd-current@FreeBSD.org; Fri, 22 Sep 2017 16:00:36 +0300 To: FreeBSD Current From: Andriy Gapon Subject: D12420 fix the misleading log facility used in devd/zfs.conf Message-ID: <991f0019-0b72-54cb-74a3-24d194aec236@FreeBSD.org> Date: Fri, 22 Sep 2017 15:59:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2017 13:00:40 -0000 https://reviews.freebsd.org/D12420 Who would be the best people to review this change? Where are they lurking? Please point me towards them or add yourself as a reviewer if you are one of them :) Thanks! -- Andriy Gapon