From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 03:08:09 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66ED0322 for ; Sun, 25 Jan 2015 03:08:09 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 568A2894 for ; Sun, 25 Jan 2015 03:08:09 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id DA4F61DC6 for ; Sun, 25 Jan 2015 03:08:09 +0000 (UTC) Date: Sun, 25 Jan 2015 03:08:09 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <897857596.7.1422155289704.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <354421615.6.1422142074021.JavaMail.jenkins@jenkins-9.freebsd.org> References: <354421615.6.1422142074021.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to stable : FreeBSD_HEAD-tests2 #588 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 03:08:09 -0000 See From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 07:41:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E6A0D78; Sun, 25 Jan 2015 07:41:50 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81B03FA8; Sun, 25 Jan 2015 07:41:49 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id b6so3470852lbj.11; Sat, 24 Jan 2015 23:41:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=+AbjC8mDY9nmVhfGeDTjcu3SpZsTxXrUIpxHGc5Ifmo=; b=DgYxKdXCXxmMat7ZzG62pgonSX2OKGCSrhS+8k/Tydxz+jTXEESw94nvEa9e1z2Zrx of1+LwuGWXVmZtNyPzyCvnQlKgW7LnYevJMLCM6j7lF6wlKtfp2lW2r8lptiKh7DnCiF 756mDwo/6yGbc/gaHUnLNEM82gDuH/mESA+i7YnlWRnJJfLxaz04itUgKsYcAfC5IwGG yksdl6LK4LwVJgCaDEAOXrV6TwMhfLHHHWkXGtcptFbYVBvah9zZBXI/yzMPtsNgBu0q j8Y1kHUTMMhCFxKuvV9MKJ7bRiAoZp+/oAf/PcNygEgE25medkqNX314vALPNPH3JHKZ EJQQ== MIME-Version: 1.0 X-Received: by 10.112.44.230 with SMTP id h6mr15401923lbm.98.1422171707418; Sat, 24 Jan 2015 23:41:47 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.129.3 with HTTP; Sat, 24 Jan 2015 23:41:47 -0800 (PST) In-Reply-To: <54B5B4EF.3010109@freebsd.org> References: <54B5B4EF.3010109@freebsd.org> Date: Sat, 24 Jan 2015 23:41:47 -0800 X-Google-Sender-Auth: Z-ZIGuzar5d1oqAepZ1tY8OdQUA Message-ID: Subject: Re: Devops question: freebsd-update needs a real tty to run, problem for automation From: Craig Rodrigues To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 07:41:50 -0000 On Tue, Jan 13, 2015 at 4:14 PM, Allan Jude wrote: > On 2015-01-13 18:11, Craig Rodrigues wrote: > > Hi, > > > > Ahmed Kamal, a devops expert, is helping me to script the steps to > > upgrade a cluster of FreeBSD machines. For certain machines, > > we want to track the official FreeBSD releases and use freebsd-update > > to install official updates. > > > > We found that when the invocation of freebsd-update was scripted > > and not run via a real tty, we can into this error: > > > > "freebsd-update fetch should not be run non-interactively." > > > > There are various workarounds mentioned on various web pages. > > However, should we modify freebsd-update so that it can work better > > when not run via a real tty? This would make it more devops/automation > > friendly. > > > > The closest thing I have found is "freebsd-update cron", which can fetch > > the updates and run without a real tty. The only problem with > > "freebsd-update cron" > > is that it sleeps a random amount of time between 1 and 3600 seconds > before > > fetching the updates. This is OK when run in a cron job, > > but not OK when run as part of a devops automation framework. > > > > Anybody have ideas as to the best way to proceed in fixing this in > > freebsd-update? > > -- > > Craig > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > I think this requirement was originally added when Colin hosted the > mirrors for FreeBSD update himself, and was worried about everyone > scripting it to run via crontab at midnight every night. > > It is likely a false requirement, and can be safely removed. > > Dealing with the merges, only really affects version upgrades, and is > less of an issue compared to being able to automate security fixes. > Hi, I submitted this review: https://reviews.freebsd.org/D1665 to remove the check for an interactive tty in "freebsd-update fetch". Being able to run "freebsd-update fetch" via automation will make it much more convenient to update clusters of FreeBSD nodes. -- Craig From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:10:54 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43CFCBB9; Sun, 25 Jan 2015 09:10:54 +0000 (UTC) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (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 248A2A59; Sun, 25 Jan 2015 09:10:54 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t0P9AiXW014415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 25 Jan 2015 01:10:44 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id t0P9AiY9014414; Sun, 25 Jan 2015 01:10:44 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA00489; Sun, 25 Jan 15 00:31:48 PST Date: Sun, 25 Jan 2015 00:31:46 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: freebsd-current@freebsd.org Subject: What replaces DIOCGDINFO? Message-Id: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: imp@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 09:10:54 -0000 -r276737 removed 4 ioctls, including DIOCGDINFO, from . The commit log entry says only "Remove old ioctl use and support, once and for all." What are users of that mechanism supposed to use instead? A grep in UPDATING for either DIOCGDINFO or ioctl came up empty. BTW I ran into this because it breaks a port I maintain. I do not run CURRENT, and thus have not been reading current@ -- but a quick perusal of the current month's archives did not turn up anything obviously pertinent. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:40:20 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1E33923; Sun, 25 Jan 2015 09:40:19 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FD14DCD; Sun, 25 Jan 2015 09:40:19 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id hv19so3658646lab.13; Sun, 25 Jan 2015 01:40:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1zAqamWUEPEHuUwJcRqdbIXh+ms6ngTcMzAZriaBlEo=; b=OVH47R2MKjGyWVlhH6D8Ua7WIYaKGhdsZgQ/eZzXR3IXupJbYCVX1WJzKLdXr/3j86 e9j81cNph6EFyOQFpPxPu2U7FeHwlyH8sEu6njbb6uTt23f85Uyd3ZDaKz5rWJE3VI5E B/JWEXJXMr4cvYirJBscRHseKwju1RU5Hc0Eo8S0/4mPcKhluM1fIn9WyxNXzNcd50mm qbEwA0blhY6B2otqFAbf4iyEzMDLnCOMYe/OLLPLNizu7PN4bi2EKrthEIP1QlZhcAqr +TkenPC7OmZwoeS1W5It24nSzl4s5RVJ4eIlrFxf3vAZIB1dZfvGtKYKqa1ljvuR0Wzz Hz7w== MIME-Version: 1.0 X-Received: by 10.112.198.233 with SMTP id jf9mr16196438lbc.9.1422178817636; Sun, 25 Jan 2015 01:40:17 -0800 (PST) Received: by 10.25.30.80 with HTTP; Sun, 25 Jan 2015 01:40:17 -0800 (PST) In-Reply-To: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> References: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> Date: Sun, 25 Jan 2015 10:40:17 +0100 Message-ID: Subject: Re: What replaces DIOCGDINFO? From: Andreas Nilsson To: Perry Hutchison Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Current FreeBSD , imp@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 09:40:20 -0000 http://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html might have the answer for you. Best regards Andreas On Sun, Jan 25, 2015 at 9:31 AM, Perry Hutchison wrote: > -r276737 removed 4 ioctls, including DIOCGDINFO, from . > The commit log entry says only "Remove old ioctl use and support, once > and for all." > > What are users of that mechanism supposed to use instead? > A grep in UPDATING for either DIOCGDINFO or ioctl came up empty. > > BTW I ran into this because it breaks a port I maintain. I do not > run CURRENT, and thus have not been reading current@ -- but a quick > perusal of the current month's archives did not turn up anything > obviously pertinent. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 05:16:54 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02FA3BF0 for ; Sun, 25 Jan 2015 05:16:54 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F2C0343 for ; Sun, 25 Jan 2015 05:16:53 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id 10so3289274lbg.10 for ; Sat, 24 Jan 2015 21:16:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=J77b2p6XZBIh2HY+JGc63mo+pmdbyE8aMy6Fq9xXryc=; b=TCWpykutbTwrfF6MDG3AJtaxMmbXE7ookPkDKJBfgc4LpGP007QudTfcptXCfAYV4F ZoVwBAYwoMc9rjSDhlQ/egdmJsDCCXTLxjDfQbW95KRy5nf8g3t5FJdQEKPjQH8CBhL1 v79+k/qgZ9E/UNQO061mx5Vg0A8/zy36bQ10E7h8tXTjeUrJB0+bLsx/Y8VdQ7qQGHUv eVeyZFxD754Eu8U8QV4do6vYI40wYXsbtg6E+ryHYG1+DeCrThPUH+DR++GzH2xUq9jO 8Zyqbddnzm+RuhSwKPHNndoMbvMgFRyBgsi8bn/bRvAjk4JmQhmya/N4WoE3EKcOPeOQ FvEA== X-Received: by 10.152.21.228 with SMTP id y4mr15326012lae.72.1422163011393; Sat, 24 Jan 2015 21:16:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.12.6 with HTTP; Sat, 24 Jan 2015 21:16:21 -0800 (PST) From: Yue Chen Date: Sun, 25 Jan 2015 00:16:21 -0500 Message-ID: Subject: How to get the source code of FreeBSD-Clang? To: freebsd-current@freebsd.org X-Mailman-Approved-At: Sun, 25 Jan 2015 12:06:58 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 05:16:54 -0000 When I use the original versions (even 3.4.1) of LLVM/Clang to compile FreeBSD kernel, it always has problems. Since I need to modify something in LLVM source and then build the kernel, where can I get the FreeBSD-friendly Clang/LLVM source code? Thanks. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 12:07:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E42053D; Sun, 25 Jan 2015 12:07:01 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 8738BCDA; Sun, 25 Jan 2015 12:07:00 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0PC6mlg024786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2015 14:06:48 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0PC6mlg024786 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0PC6mlv024785; Sun, 25 Jan 2015 14:06:48 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 25 Jan 2015 14:06:48 +0200 From: Konstantin Belousov To: Chagin Dmitry Subject: Re: dblfault panic r277611 Message-ID: <20150125120648.GX42409@kib.kiev.ua> References: <20150124094633.GA1804@dchagin.static.corbina.net> <20150124103519.GR42409@kib.kiev.ua> <20150124194245.GA72881@dchagin.static.corbina.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150124194245.GA72881@dchagin.static.corbina.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-current@freebsd.org, dim@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 12:07:01 -0000 On Sat, Jan 24, 2015 at 10:42:45PM +0300, Chagin Dmitry wrote: > On Sat, Jan 24, 2015 at 12:35:19PM +0200, Konstantin Belousov wrote: > > On Sat, Jan 24, 2015 at 12:46:33PM +0300, Chagin Dmitry wrote: > > > Hi, > > > > > > > > > dchagin.static.corbina.net dumped core - see /var/crash/vmcore.7 > > > > > > Sat Jan 24 01:02:20 MSK 2015 > > > > > > FreeBSD dchagin.static.corbina.net 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r277611+c41ef74(lemul): Sat Jan 24 00:53:45 MSK 2015 root@dchagin.static.corbina.net:/home/rootobj/home/git/head/sys/YOY amd64 > > > > > > panic: double fault > > > > > > GNU gdb 6.1.1 [FreeBSD] > > > Copyright 2004 Free Software Foundation, Inc. > > > GDB is free software, covered by the GNU General Public License, and you are > > > welcome to change it and/or distribute copies of it under certain conditions. > > > Type "show copying" to see the conditions. > > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > > This GDB was configured as "amd64-marcel-freebsd"... > > > > > > Unread portion of the kernel message buffer: > > > ffs_syncvnode+0x3b0/frame 0xfffffe033c22bd50 > > > ffs_truncate() at ffs_truncate+0xc6a/frame 0xfffffe033c22c150 > > > ufs_direnter() at ufs_direnter+0xde5/frame 0xfffffe033c22c280 > > > ufs_mkdir() at ufs_mkdir+0xb07/frame 0xfffffe033c22c4a0 > > > > > > Fatal double fault > > > rip = 0xffffffff807a8d03 > > > rsp = 0xfffffe033c228e60 > > > rbp = 0xfffffe033c229000 > > > cpuid = 5; apic id = 05 > > > panic: double fault > > > cpuid = 5 > > > KDB: enter: panic > > > > > > Reading symbols from /boot/kernel/if_tap.ko.symbols...done. > > > Loaded symbols for /boot/kernel/if_tap.ko.symbols > > > Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. > > > Loaded symbols for /boot/kernel/if_bridge.ko.symbols > > > Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. > > > Loaded symbols for /boot/kernel/bridgestp.ko.symbols > > > Reading symbols from /boot/kernel/usb.ko.symbols...done. > > > Loaded symbols for /boot/kernel/usb.ko.symbols > > > Reading symbols from /boot/kernel/xhci.ko.symbols...done. > > > Loaded symbols for /boot/kernel/xhci.ko.symbols > > > Reading symbols from /boot/kernel/vmm.ko.symbols...done. > > > Loaded symbols for /boot/kernel/vmm.ko.symbols > > > Reading symbols from /boot/kernel/nmdm.ko.symbols...done. > > > Loaded symbols for /boot/kernel/nmdm.ko.symbols > > > Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. > > > Loaded symbols for /boot/kernel/linprocfs.ko.symbols > > > Reading symbols from /boot/kernel/pseudofs.ko.symbols...done. > > > Loaded symbols for /boot/kernel/pseudofs.ko.symbols > > > Reading symbols from /boot/kernel/linux_common.ko.symbols...done. > > > Loaded symbols for /boot/kernel/linux_common.ko.symbols > > > Reading symbols from /boot/kernel/procfs.ko.symbols...done. > > > Loaded symbols for /boot/kernel/procfs.ko.symbols > > > Reading symbols from /boot/kernel/ukbd.ko.symbols...done. > > > Loaded symbols for /boot/kernel/ukbd.ko.symbols > > > Reading symbols from /boot/kernel/ums.ko.symbols...done. > > > Loaded symbols for /boot/kernel/ums.ko.symbols > > > #0 doadump (textdump=771179792) > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > 262 dumptid = curthread->td_tid; > > > (kgdb) #0 doadump (textdump=771179792) > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > #1 0xffffffff803c1b08 in db_fncall_generic (addr=-2139713712, > > > rv=0xfffffe032df744a0, nargs=0, args=0xfffffe032df744b0) > > > at /home/git/head/sys/ddb/db_command.c:568 > > > #2 0xffffffff803c17d3 in db_fncall (dummy1=-2185367173664, dummy2=0, > > > dummy3=0, dummy4=0xfffffe032df745e0 "\n") > > > at /home/git/head/sys/ddb/db_command.c:616 > > > #3 0xffffffff803c142b in db_command (last_cmdp=0xffffffff810fd6a8, > > > cmd_table=0x0, dopager=1) at /home/git/head/sys/ddb/db_command.c:440 > > > #4 0xffffffff803c0f9d in db_command_loop () > > > at /home/git/head/sys/ddb/db_command.c:493 > > > #5 0xffffffff803c58d9 in db_trap (type=3, code=0) > > > at /home/git/head/sys/ddb/db_main.c:251 > > > #6 0xffffffff807cc704 in kdb_trap (type=3, code=0, tf=0xfffffe032df74cc0) > > > at /home/git/head/sys/kern/subr_kdb.c:654 > > > #7 0xffffffff80c94e1d in trap (frame=0xfffffe032df74cc0) > > > at /home/git/head/sys/amd64/amd64/trap.c:546 > > > #8 0xffffffff80c9655f in trap_check (frame=0xfffffe032df74cc0) > > > at /home/git/head/sys/amd64/amd64/trap.c:645 > > > #9 0xffffffff80c691a2 in calltrap () > > > at /home/git/head/sys/amd64/amd64/exception.S:235 > > > #10 0xffffffff807cbf15 in breakpoint () at cpufunc.h:63 > > > #11 0xffffffff807cbaff in kdb_enter (why=0xffffffff80dcd635 "panic", > > > msg=0xffffffff80dcd635 "panic") at /home/git/head/sys/kern/subr_kdb.c:443 > > > #12 0xffffffff80769768 in vpanic (fmt=0xffffffff80e24597 "double fault", > > > ap=0xfffffe032df74ec0) at /home/git/head/sys/kern/kern_shutdown.c:740 > > > #13 0xffffffff80769820 in panic (fmt=0xffffffff80e24597 "double fault") > > > at /home/git/head/sys/kern/kern_shutdown.c:676 > > > #14 0xffffffff80c9667d in dblfault_handler (frame=0xfffffe032df74f40) > > > at /home/git/head/sys/amd64/amd64/trap.c:912 > > > #15 0xffffffff80c6929c in Xdblfault () > > > at /home/git/head/sys/amd64/amd64/exception.S:291 > > > #16 0xffffffff807a8d03 in cpu_search_lowest (cg=Cannot access memory at address 0xfffffe033c228ec8 > > > ) > > > at /home/git/head/sys/kern/sched_ule.c:764 > > > #17 0xffffffff807a9094 in cpu_search_lowest (cg=0xffffffff8128a6e8, > > > low=0xfffffe033c2292f8) at /home/git/head/sys/kern/sched_ule.c:690 > > > #18 0xffffffff807a9094 in cpu_search_lowest (cg=0xffffffff8128a6b0, > > > low=0xfffffe033c229380) at /home/git/head/sys/kern/sched_ule.c:690 > > > #19 0xffffffff807b0f56 in sched_lowest (cg=0xffffffff8128a6b0, mask= > > > {__bits = {255, 0, 0, 0}}, pri=121, maxload=2147483647, prefer=5) > > > at /home/git/head/sys/kern/sched_ule.c:796 > > > #20 0xffffffff807abcdb in sched_pickcpu (td=0xfffff80009e5a9a0, flags=0) > > > at /home/git/head/sys/kern/sched_ule.c:1276 > > > #21 0xffffffff807ace35 in sched_add (td=0xfffff80009e5a9a0, flags=0) > > > at /home/git/head/sys/kern/sched_ule.c:2395 > > > #22 0xffffffff807acac9 in sched_wakeup (td=0xfffff80009e5a9a0) > > > at /home/git/head/sys/kern/sched_ule.c:2029 > > > #23 0xffffffff8077d6a8 in setrunnable (td=0xfffff80009e5a9a0) > > > at /home/git/head/sys/kern/kern_synch.c:544 > > > #24 0xffffffff807e4e98 in sleepq_resume_thread (sq=0xfffff80009e55d80, > > > td=0xfffff80009e5a9a0, pri=0) > > > at /home/git/head/sys/kern/subr_sleepqueue.c:776 > > > #25 0xffffffff807e306a in sleepq_timeout (arg=0xfffff80009e5a9a0) > > > at /home/git/head/sys/kern/subr_sleepqueue.c:915 > > > #26 0xffffffff80791b40 in softclock_call_cc (c=0xfffff80009e5ad38, > > > cc=0xffffffff813a4200, direct=1) > > > at /home/git/head/sys/kern/kern_timeout.c:724 > > > #27 0xffffffff807913bd in callout_process (now=740683739317) > > > at /home/git/head/sys/kern/kern_timeout.c:499 > > > #28 0xffffffff80ce346a in handleevents (now=740683739317, fake=0) > > > at /home/git/head/sys/kern/kern_clocksource.c:212 > > > #29 0xffffffff80ce3fd6 in timercb (et=0xffffffff8137df68, arg=0x0) > > > at /home/git/head/sys/kern/kern_clocksource.c:345 > > > #30 0xffffffff80d376e3 in lapic_handle_timer (frame=0xfffffe033c229c50) > > > at /home/git/head/sys/x86/x86/local_apic.c:883 > > > #31 0xffffffff80c69cfc in Xtimerint () at apic_vector.S:109 > > > #32 0xffffffff80c745ef in write_rflags (rf=642) at cpufunc.h:382 > > > #33 0xffffffff80c6f225 in intr_restore (rflags=642) at cpufunc.h:775 > > > #34 0xffffffff80c71ce8 in spinlock_exit () > > > at /home/git/head/sys/amd64/amd64/machdep.c:2177 > > > #35 0xffffffff8074335c in __mtx_unlock_spin_flags (c=0xffffffff8119ec80, > > > opts=0, file=0xffffffff80dc3d2b "/home/git/head/sys/kern/kern_cons.c", > > > line=530) at /home/git/head/sys/kern/kern_mutex.c:305 > > > #36 0xffffffff806df9fc in cnputs (p=0xfffffe033c22a402 "\"<\003þÿÿ") > > > at /home/git/head/sys/kern/kern_cons.c:530 > > > #37 0xffffffff807d76ae in putbuf (c=10, ap=0xfffffe033c22a3b8) > > > at /home/git/head/sys/kern/subr_prf.c:427 > > > #38 0xffffffff807d60d6 in putchar (c=10, arg=0xfffffe033c22a3b8) > > > at /home/git/head/sys/kern/subr_prf.c:471 > > > #39 0xffffffff807d43e3 in kvprintf (fmt=0xffffffff80d77b33 "", > > > func=0xffffffff807d6010 , arg=0xfffffe033c22a3b8, radix=10, > > > ap=0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:720 > > > #40 0xffffffff807d6569 in _vprintf (level=-1, flags=5, > > > fmt=0xffffffff80d77b31 "%c", ap=0xfffffe033c22a510) > > > at /home/git/head/sys/kern/subr_prf.c:271 > > > #41 0xffffffff807d68dd in vprintf (fmt=0xffffffff80d77b31 "%c", > > > ap=0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:388 > > > #42 0xffffffff807d689b in printf (fmt=0xffffffff80d77b31 "%c") > > > at /home/git/head/sys/kern/subr_prf.c:377 > > > #43 0xffffffff803c5d55 in db_putc (c=10) > > > at /home/git/head/sys/ddb/db_output.c:156 > > > #44 0xffffffff803c5b21 in db_putchar (c=10, arg=0xfffffe033c22aad8) > > > at /home/git/head/sys/ddb/db_output.c:128 > > > #45 0xffffffff807d3b65 in kvprintf (fmt=0xffffffff80d8090f "", > > > func=0xffffffff803c5af0 , arg=0xfffffe033c22aad8, radix=16, > > > ap=0xfffffe033c22aac0) at /home/git/head/sys/kern/subr_prf.c:645 > > > #46 0xffffffff803c5ad8 in db_printf (fmt=0xffffffff80d8090e "\n") > > > at /home/git/head/sys/ddb/db_output.c:340 > > > #47 0xffffffff80c67f73 in db_print_stack_entry ( > > > name=0xffffffff815c8262 "ufs_mkdir", narg=0, argnp=0x0, > > > argp=0xfffffe033c22c4b0, callpc=18446744071574694567, > > > frame=0xfffffe033c22c4a0) at /home/git/head/sys/amd64/amd64/db_trace.c:260 > > > #48 0xffffffff80c66f3b in db_backtrace (td=0xfffff801ad926000, tf=0x0, > > > frame=0xfffffe033c22c4a0, pc=18446744071574694567, count=1005) > > > at /home/git/head/sys/amd64/amd64/db_trace.c:462 > > > #49 0xffffffff80c66bdf in db_trace_self () > > > at /home/git/head/sys/amd64/amd64/db_trace.c:498 > > > #50 0xffffffff803c568e in db_trace_self_wrapper () > > > at /home/git/head/sys/ddb/db_main.c:268 > > > #51 0xffffffff807cbcd8 in kdb_backtrace () > > > at /home/git/head/sys/kern/subr_kdb.c:370 > > > #52 0xffffffff807fe924 in _witness_debugger (cond=1, > > > msg=0xffffffff80dd6e29 "witness_checkorder") > > > at /home/git/head/sys/kern/subr_witness.c:2904 > > > #53 0xffffffff807fe2de in witness_checkorder (lock=0xfffff80193effd50, > > > flags=9, file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > > > line=2164, interlock=0xfffff80193effd80) > > > at /home/git/head/sys/kern/subr_witness.c:1365 > > > #54 0xffffffff80730d65 in __lockmgr_args (lk=0xfffff80193effd50, > > > flags=524544, ilk=0xfffff80193effd80, wmesg=0x0, pri=0, timo=0, > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", line=2164) > > > at /home/git/head/sys/kern/kern_lock.c:756 > > > #55 0xffffffff80bf1438 in _lockmgr_args (lk=0xfffff80193effd50, flags=524544, > > > ilk=0xfffff80193effd80, wmesg=0x0, prio=0, timo=0, > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", line=2164) > > > at lockmgr.h:98 > > > #56 0xffffffff80bef677 in ffs_lock (ap=0xfffffe033c22b7c8) > > > at /home/git/head/sys/ufs/ffs/ffs_vnops.c:385 > > > #57 0xffffffff80d47cd4 in VOP_LOCK1_APV (vop=0xffffffff810cd328, > > > a=0xfffffe033c22b7c8) at vnode_if.c:2082 > > > #58 0xffffffff808ac2f3 in VOP_LOCK1 (vp=0xfffff80193effce8, flags=524544, > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", line=2164) > > > at vnode_if.h:859 > > > #59 0xffffffff808aa122 in _vn_lock (vp=0xfffff80193effce8, flags=524544, > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", line=2164) > > > at /home/git/head/sys/kern/vfs_vnops.c:1531 > > > #60 0xffffffff8088d636 in vget (vp=0xfffff80193effce8, flags=524544, > > > td=0xfffff801ad926000) at /home/git/head/sys/kern/vfs_subr.c:2164 > > > #61 0xffffffff8087884f in vfs_hash_get (mp=0xfffff80009db2000, hash=71269052, > > > flags=524288, td=0xfffff801ad926000, vpp=0xfffffe033c22bb40, fn=0, > > > arg=0x0) at /home/git/head/sys/kern/vfs_hash.c:89 > > > #62 0xffffffff80be7969 in ffs_vgetf (mp=0xfffff80009db2000, ino=71269052, > > > flags=524288, vpp=0xfffffe033c22bb40, ffs_flags=1) > > > at /home/git/head/sys/ufs/ffs/ffs_vfsops.c:1636 > > > #63 0xffffffff80bd1d02 in flush_pagedep_deps (pvp=0xfffff80193c8d588, > > > mp=0xfffff80009db2000, diraddhdp=0xfffff80193769b58) > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12929 > > > #64 0xffffffff80bd182c in softdep_sync_buf (vp=0xfffff80193c8d588, > > > bp=0xfffffe02d6a8d6d0, waitfor=1) > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12621 > > > #65 0xffffffff80bf0d40 in ffs_syncvnode (vp=0xfffff80193c8d588, waitfor=1, > > > flags=0) at /home/git/head/sys/ufs/ffs/ffs_vnops.c:280 > > > #66 0xffffffff80babd9a in ffs_truncate (vp=0xfffff80193c8d588, length=512, > > > flags=2176, cred=0xfffff80009c52b00) > > > at /home/git/head/sys/ufs/ffs/ffs_inode.c:339 > > > #67 0xffffffff80bfd315 in ufs_direnter (dvp=0xfffff80193c8d588, > > > tvp=0xfffff80193effce8, dirp=0xfffffe033c22c390, cnp=0xfffffe033c22c720, > > > newdirbp=0xfffffe02d66d7db0, isrename=0) > > > at /home/git/head/sys/ufs/ufs/ufs_lookup.c:1133 > > > #68 0xffffffff80c0aaa7 in ufs_mkdir (ap=0xfffffe033c22c558) > > > at /home/git/head/sys/ufs/ufs/ufs_vnops.c:1963 > > > #69 0xffffffff80d460fd in VOP_MKDIR_APV (vop=0xffffffff810cddd8, > > > a=0xfffffe033c22c558) at vnode_if.c:1607 > > > #70 0xffffffff808a5979 in VOP_MKDIR (dvp=0xfffff80193c8d588, > > > vpp=0xfffffe033c22c6f8, cnp=0xfffffe033c22c720, vap=0xfffffe033c22c768) > > > at vnode_if.h:665 > > > #71 0xffffffff808a585c in kern_mkdirat (td=0xfffff801ad926000, fd=-100, > > > path=0x7fffffffe949
, > > > segflg=UIO_USERSPACE, mode=511) > > > at /home/git/head/sys/kern/vfs_syscalls.c:3747 > > > #72 0xffffffff808a54c3 in sys_mkdir (td=0xfffff801ad926000, > > > uap=0xfffffe033c22ca58) at /home/git/head/sys/kern/vfs_syscalls.c:3678 > > > #73 0xffffffff80c97044 in syscallenter (td=0xfffff801ad926000, > > > sa=0xfffffe033c22ca48) at subr_syscall.c:133 > > > #74 0xffffffff80c9694a in amd64_syscall (td=0xfffff801ad926000, traced=0) > > > at /home/git/head/sys/amd64/amd64/trap.c:986 > > > #75 0xffffffff80c6948b in Xfast_syscall () > > > at /home/git/head/sys/amd64/amd64/exception.S:395 > > > #76 0x0000000800946eca in ?? () > > > Previous frame inner to this frame (corrupt stack?) > > > Current language: auto; currently minimal > > > (kgdb) > > > > > > > > > > This is fun, for some definition of it. > > > > The process was in the guts of VFS from mkdir(2) syscall, witness > > triggered printing of the warning for dreaded buf->hashdir->buf non-real > > LOR. From the ddb stack backtrace routine, when cnputs released the > > console spinlock yet another time, timer interrupt fired and started > > proceeding callouts. One of the callout triggered and needs to wake > > up a thread sleeping with timeout. There, inside the scheduler, > > cpu_search_lowest() was called, recursed twice and finally > > overflown the stack. > > > > Is this yet another clang regression ? The cpu_search_lowest() saga seems > > to never end. r268211 is uneffective, probably after clang 3.5 import. > > yes, you are right. building kernel without SSP fixes the panic. > How did you ensured that it is fixed ? There must be very specific circumstances: timer interrupt fired while in witness, callout activated, etc to trigger the panic. Or, do you mean that you looked at the assembly for the cpu_search() and see that it is no longer recursive ? From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 12:20:23 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C835882 for ; Sun, 25 Jan 2015 12:20:23 +0000 (UTC) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2C43DC6 for ; Sun, 25 Jan 2015 12:20:22 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id k48so4761950wev.9 for ; Sun, 25 Jan 2015 04:20:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H6o7/rojKd+JtQjqQfO7VfH/e/uF875BUZjSH6qz0ts=; b=mdn/+ojjU9ozLRHruVLUaT/kIx66n+DEtUywm46h8HcJSgf4QheLGH6SSSZuy+UoIz EhXd0A1UftY22+vwpmrp5gJXP5bZHvHPba8Yp7UYT2A/dtcXlSOdrsdoQdQFxIXJGmkp J0pJEryrad0xk5ZMtnK+4+6LzPHHTcDjfELMUHw5+xvCQJ42AVPkthzsW4FaaAr6zqNq fCO0VIpoO7vgr9nRKTmZd0JmYHDmbPvO8L6mImNFZ4Iv9NLGffSs+ajSrQJok6GbrTFI y7tmS6e7dVhrszyfzd57quyg67SwlkTHHxzrmZ0sFQ4ddKTcR5Zluq9oaOrsdC0ktMl6 p/HA== MIME-Version: 1.0 X-Received: by 10.194.236.200 with SMTP id uw8mr34153928wjc.10.1422188421034; Sun, 25 Jan 2015 04:20:21 -0800 (PST) Received: by 10.27.48.74 with HTTP; Sun, 25 Jan 2015 04:20:20 -0800 (PST) In-Reply-To: References: Date: Sun, 25 Jan 2015 06:20:20 -0600 Message-ID: Subject: Re: How to get the source code of FreeBSD-Clang? From: "Sam Fourman Jr." To: Yue Chen Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 12:20:23 -0000 On Sat, Jan 24, 2015 at 11:16 PM, Yue Chen wrote: > When I use the original versions (even 3.4.1) of LLVM/Clang to compile > FreeBSD kernel, it always has problems. > > Since I need to modify something in LLVM source and then build the kernel, > where can I get the FreeBSD-friendly Clang/LLVM source code? > > It comes in base, if you have FreeBSD 10 or the source for 10.x all the source is included. -- Sam Fourman Jr. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 14:16:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08622F9B; Sun, 25 Jan 2015 14:16:01 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8313A8A; Sun, 25 Jan 2015 14:16:00 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id r5so3847114qcx.11; Sun, 25 Jan 2015 06:15:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oISMA5AMgVnfFx2zWx6p+9eX86pIRwhbK632DJcPPPM=; b=TaQaaBBvSlbb+ZqpzUEIIkJ/ej/4IC79MKwQuUlBfQHNmzxS5gg6Z+0S25vAi4BmtY Zrh1nEu92F9kxwticm8an2DFh4LtnD11cNQoiWnOFos502g3yheWhTSV7/Dj5PZQuvX0 USV9NcUa1KDhRR1Rb8cOKW8VZI1rmTZCzp3qbxW70ONZ/oQNBFUnAiy5h4NzwrHOc1E5 IL5RmF/qvIHJ9WnbrDUYj4yO3YXZAwqcdNjOC4xhgbJKxnbtb6dUkV1tlFnufq3oDF9U RXtYclf8aOgEZa/nTyIjFTewVc9nz5HooUNN28O5HFj6+7xuPdTwq/x1/fg3dR4yCUOs IApA== MIME-Version: 1.0 X-Received: by 10.229.80.3 with SMTP id r3mr2673643qck.23.1422195359707; Sun, 25 Jan 2015 06:15:59 -0800 (PST) Sender: chagin.dmitry@gmail.com Received: by 10.96.84.228 with HTTP; Sun, 25 Jan 2015 06:15:59 -0800 (PST) In-Reply-To: <20150125120648.GX42409@kib.kiev.ua> References: <20150124094633.GA1804@dchagin.static.corbina.net> <20150124103519.GR42409@kib.kiev.ua> <20150124194245.GA72881@dchagin.static.corbina.net> <20150125120648.GX42409@kib.kiev.ua> Date: Sun, 25 Jan 2015 17:15:59 +0300 X-Google-Sender-Auth: J3_bH89SPSVUnke0SMSAIGSwGrM Message-ID: Subject: Re: dblfault panic r277611 From: Dmitry Chagin To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Current , dim@freebsd.org, Chagin Dmitry X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 14:16:01 -0000 2015-01-25 15:06 GMT+03:00 Konstantin Belousov : > On Sat, Jan 24, 2015 at 10:42:45PM +0300, Chagin Dmitry wrote: > > On Sat, Jan 24, 2015 at 12:35:19PM +0200, Konstantin Belousov wrote: > > > On Sat, Jan 24, 2015 at 12:46:33PM +0300, Chagin Dmitry wrote: > > > > Hi, > > > > > > > > > > > > dchagin.static.corbina.net dumped core - see /var/crash/vmcore.7 > > > > > > > > Sat Jan 24 01:02:20 MSK 2015 > > > > > > > > FreeBSD dchagin.static.corbina.net 11.0-CURRENT FreeBSD > 11.0-CURRENT #2 r277611+c41ef74(lemul): Sat Jan 24 00:53:45 MSK 2015 > root@dchagin.static.corbina.net:/home/rootobj/home/git/head/sys/YOY > amd64 > > > > > > > > panic: double fault > > > > > > > > GNU gdb 6.1.1 [FreeBSD] > > > > Copyright 2004 Free Software Foundation, Inc. > > > > GDB is free software, covered by the GNU General Public License, an= d > you are > > > > welcome to change it and/or distribute copies of it under certain > conditions. > > > > Type "show copying" to see the conditions. > > > > There is absolutely no warranty for GDB. Type "show warranty" for > details. > > > > This GDB was configured as "amd64-marcel-freebsd"... > > > > > > > > Unread portion of the kernel message buffer: > > > > ffs_syncvnode+0x3b0/frame 0xfffffe033c22bd50 > > > > ffs_truncate() at ffs_truncate+0xc6a/frame 0xfffffe033c22c150 > > > > ufs_direnter() at ufs_direnter+0xde5/frame 0xfffffe033c22c280 > > > > ufs_mkdir() at ufs_mkdir+0xb07/frame 0xfffffe033c22c4a0 > > > > > > > > Fatal double fault > > > > rip =3D 0xffffffff807a8d03 > > > > rsp =3D 0xfffffe033c228e60 > > > > rbp =3D 0xfffffe033c229000 > > > > cpuid =3D 5; apic id =3D 05 > > > > panic: double fault > > > > cpuid =3D 5 > > > > KDB: enter: panic > > > > > > > > Reading symbols from /boot/kernel/if_tap.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/if_tap.ko.symbols > > > > Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/if_bridge.ko.symbols > > > > Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/bridgestp.ko.symbols > > > > Reading symbols from /boot/kernel/usb.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/usb.ko.symbols > > > > Reading symbols from /boot/kernel/xhci.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/xhci.ko.symbols > > > > Reading symbols from /boot/kernel/vmm.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/vmm.ko.symbols > > > > Reading symbols from /boot/kernel/nmdm.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/nmdm.ko.symbols > > > > Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/linprocfs.ko.symbols > > > > Reading symbols from /boot/kernel/pseudofs.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/pseudofs.ko.symbols > > > > Reading symbols from /boot/kernel/linux_common.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/linux_common.ko.symbols > > > > Reading symbols from /boot/kernel/procfs.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/procfs.ko.symbols > > > > Reading symbols from /boot/kernel/ukbd.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/ukbd.ko.symbols > > > > Reading symbols from /boot/kernel/ums.ko.symbols...done. > > > > Loaded symbols for /boot/kernel/ums.ko.symbols > > > > #0 doadump (textdump=3D771179792) > > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > > 262 dumptid =3D curthread->td_tid; > > > > (kgdb) #0 doadump (textdump=3D771179792) > > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > > #1 0xffffffff803c1b08 in db_fncall_generic (addr=3D-2139713712, > > > > rv=3D0xfffffe032df744a0, nargs=3D0, args=3D0xfffffe032df744b0) > > > > at /home/git/head/sys/ddb/db_command.c:568 > > > > #2 0xffffffff803c17d3 in db_fncall (dummy1=3D-2185367173664, dummy= 2=3D0, > > > > dummy3=3D0, dummy4=3D0xfffffe032df745e0 "\n") > > > > at /home/git/head/sys/ddb/db_command.c:616 > > > > #3 0xffffffff803c142b in db_command (last_cmdp=3D0xffffffff810fd6a= 8, > > > > cmd_table=3D0x0, dopager=3D1) at > /home/git/head/sys/ddb/db_command.c:440 > > > > #4 0xffffffff803c0f9d in db_command_loop () > > > > at /home/git/head/sys/ddb/db_command.c:493 > > > > #5 0xffffffff803c58d9 in db_trap (type=3D3, code=3D0) > > > > at /home/git/head/sys/ddb/db_main.c:251 > > > > #6 0xffffffff807cc704 in kdb_trap (type=3D3, code=3D0, > tf=3D0xfffffe032df74cc0) > > > > at /home/git/head/sys/kern/subr_kdb.c:654 > > > > #7 0xffffffff80c94e1d in trap (frame=3D0xfffffe032df74cc0) > > > > at /home/git/head/sys/amd64/amd64/trap.c:546 > > > > #8 0xffffffff80c9655f in trap_check (frame=3D0xfffffe032df74cc0) > > > > at /home/git/head/sys/amd64/amd64/trap.c:645 > > > > #9 0xffffffff80c691a2 in calltrap () > > > > at /home/git/head/sys/amd64/amd64/exception.S:235 > > > > #10 0xffffffff807cbf15 in breakpoint () at cpufunc.h:63 > > > > #11 0xffffffff807cbaff in kdb_enter (why=3D0xffffffff80dcd635 "pani= c", > > > > msg=3D0xffffffff80dcd635 "panic") at > /home/git/head/sys/kern/subr_kdb.c:443 > > > > #12 0xffffffff80769768 in vpanic (fmt=3D0xffffffff80e24597 "double > fault", > > > > ap=3D0xfffffe032df74ec0) at > /home/git/head/sys/kern/kern_shutdown.c:740 > > > > #13 0xffffffff80769820 in panic (fmt=3D0xffffffff80e24597 "double > fault") > > > > at /home/git/head/sys/kern/kern_shutdown.c:676 > > > > #14 0xffffffff80c9667d in dblfault_handler (frame=3D0xfffffe032df74= f40) > > > > at /home/git/head/sys/amd64/amd64/trap.c:912 > > > > #15 0xffffffff80c6929c in Xdblfault () > > > > at /home/git/head/sys/amd64/amd64/exception.S:291 > > > > #16 0xffffffff807a8d03 in cpu_search_lowest (cg=3DCannot access mem= ory > at address 0xfffffe033c228ec8 > > > > ) > > > > at /home/git/head/sys/kern/sched_ule.c:764 > > > > #17 0xffffffff807a9094 in cpu_search_lowest (cg=3D0xffffffff8128a6e= 8, > > > > low=3D0xfffffe033c2292f8) at > /home/git/head/sys/kern/sched_ule.c:690 > > > > #18 0xffffffff807a9094 in cpu_search_lowest (cg=3D0xffffffff8128a6b= 0, > > > > low=3D0xfffffe033c229380) at > /home/git/head/sys/kern/sched_ule.c:690 > > > > #19 0xffffffff807b0f56 in sched_lowest (cg=3D0xffffffff8128a6b0, ma= sk=3D > > > > {__bits =3D {255, 0, 0, 0}}, pri=3D121, maxload=3D214748364= 7, > prefer=3D5) > > > > at /home/git/head/sys/kern/sched_ule.c:796 > > > > #20 0xffffffff807abcdb in sched_pickcpu (td=3D0xfffff80009e5a9a0, > flags=3D0) > > > > at /home/git/head/sys/kern/sched_ule.c:1276 > > > > #21 0xffffffff807ace35 in sched_add (td=3D0xfffff80009e5a9a0, flags= =3D0) > > > > at /home/git/head/sys/kern/sched_ule.c:2395 > > > > #22 0xffffffff807acac9 in sched_wakeup (td=3D0xfffff80009e5a9a0) > > > > at /home/git/head/sys/kern/sched_ule.c:2029 > > > > #23 0xffffffff8077d6a8 in setrunnable (td=3D0xfffff80009e5a9a0) > > > > at /home/git/head/sys/kern/kern_synch.c:544 > > > > #24 0xffffffff807e4e98 in sleepq_resume_thread > (sq=3D0xfffff80009e55d80, > > > > td=3D0xfffff80009e5a9a0, pri=3D0) > > > > at /home/git/head/sys/kern/subr_sleepqueue.c:776 > > > > #25 0xffffffff807e306a in sleepq_timeout (arg=3D0xfffff80009e5a9a0) > > > > at /home/git/head/sys/kern/subr_sleepqueue.c:915 > > > > #26 0xffffffff80791b40 in softclock_call_cc (c=3D0xfffff80009e5ad38= , > > > > cc=3D0xffffffff813a4200, direct=3D1) > > > > at /home/git/head/sys/kern/kern_timeout.c:724 > > > > #27 0xffffffff807913bd in callout_process (now=3D740683739317) > > > > at /home/git/head/sys/kern/kern_timeout.c:499 > > > > #28 0xffffffff80ce346a in handleevents (now=3D740683739317, fake=3D= 0) > > > > at /home/git/head/sys/kern/kern_clocksource.c:212 > > > > #29 0xffffffff80ce3fd6 in timercb (et=3D0xffffffff8137df68, arg=3D0= x0) > > > > at /home/git/head/sys/kern/kern_clocksource.c:345 > > > > #30 0xffffffff80d376e3 in lapic_handle_timer > (frame=3D0xfffffe033c229c50) > > > > at /home/git/head/sys/x86/x86/local_apic.c:883 > > > > #31 0xffffffff80c69cfc in Xtimerint () at apic_vector.S:109 > > > > #32 0xffffffff80c745ef in write_rflags (rf=3D642) at cpufunc.h:382 > > > > #33 0xffffffff80c6f225 in intr_restore (rflags=3D642) at cpufunc.h:= 775 > > > > #34 0xffffffff80c71ce8 in spinlock_exit () > > > > at /home/git/head/sys/amd64/amd64/machdep.c:2177 > > > > #35 0xffffffff8074335c in __mtx_unlock_spin_flags > (c=3D0xffffffff8119ec80, > > > > opts=3D0, file=3D0xffffffff80dc3d2b > "/home/git/head/sys/kern/kern_cons.c", > > > > line=3D530) at /home/git/head/sys/kern/kern_mutex.c:305 > > > > #36 0xffffffff806df9fc in cnputs (p=3D0xfffffe033c22a402 "\"<\003= =D0=A7=D0=AA=D0=AA") > > > > at /home/git/head/sys/kern/kern_cons.c:530 > > > > #37 0xffffffff807d76ae in putbuf (c=3D10, ap=3D0xfffffe033c22a3b8) > > > > at /home/git/head/sys/kern/subr_prf.c:427 > > > > #38 0xffffffff807d60d6 in putchar (c=3D10, arg=3D0xfffffe033c22a3b8= ) > > > > at /home/git/head/sys/kern/subr_prf.c:471 > > > > #39 0xffffffff807d43e3 in kvprintf (fmt=3D0xffffffff80d77b33 "", > > > > func=3D0xffffffff807d6010 , arg=3D0xfffffe033c22a3b8, > radix=3D10, > > > > ap=3D0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:= 720 > > > > #40 0xffffffff807d6569 in _vprintf (level=3D-1, flags=3D5, > > > > fmt=3D0xffffffff80d77b31 "%c", ap=3D0xfffffe033c22a510) > > > > at /home/git/head/sys/kern/subr_prf.c:271 > > > > #41 0xffffffff807d68dd in vprintf (fmt=3D0xffffffff80d77b31 "%c", > > > > ap=3D0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:= 388 > > > > #42 0xffffffff807d689b in printf (fmt=3D0xffffffff80d77b31 "%c") > > > > at /home/git/head/sys/kern/subr_prf.c:377 > > > > #43 0xffffffff803c5d55 in db_putc (c=3D10) > > > > at /home/git/head/sys/ddb/db_output.c:156 > > > > #44 0xffffffff803c5b21 in db_putchar (c=3D10, arg=3D0xfffffe033c22a= ad8) > > > > at /home/git/head/sys/ddb/db_output.c:128 > > > > #45 0xffffffff807d3b65 in kvprintf (fmt=3D0xffffffff80d8090f "", > > > > func=3D0xffffffff803c5af0 , arg=3D0xfffffe033c22aad= 8, > radix=3D16, > > > > ap=3D0xfffffe033c22aac0) at /home/git/head/sys/kern/subr_prf.c:= 645 > > > > #46 0xffffffff803c5ad8 in db_printf (fmt=3D0xffffffff80d8090e "\n") > > > > at /home/git/head/sys/ddb/db_output.c:340 > > > > #47 0xffffffff80c67f73 in db_print_stack_entry ( > > > > name=3D0xffffffff815c8262 "ufs_mkdir", narg=3D0, argnp=3D0x0, > > > > argp=3D0xfffffe033c22c4b0, callpc=3D18446744071574694567, > > > > frame=3D0xfffffe033c22c4a0) at > /home/git/head/sys/amd64/amd64/db_trace.c:260 > > > > #48 0xffffffff80c66f3b in db_backtrace (td=3D0xfffff801ad926000, > tf=3D0x0, > > > > frame=3D0xfffffe033c22c4a0, pc=3D18446744071574694567, count=3D= 1005) > > > > at /home/git/head/sys/amd64/amd64/db_trace.c:462 > > > > #49 0xffffffff80c66bdf in db_trace_self () > > > > at /home/git/head/sys/amd64/amd64/db_trace.c:498 > > > > #50 0xffffffff803c568e in db_trace_self_wrapper () > > > > at /home/git/head/sys/ddb/db_main.c:268 > > > > #51 0xffffffff807cbcd8 in kdb_backtrace () > > > > at /home/git/head/sys/kern/subr_kdb.c:370 > > > > #52 0xffffffff807fe924 in _witness_debugger (cond=3D1, > > > > msg=3D0xffffffff80dd6e29 "witness_checkorder") > > > > at /home/git/head/sys/kern/subr_witness.c:2904 > > > > #53 0xffffffff807fe2de in witness_checkorder > (lock=3D0xfffff80193effd50, > > > > flags=3D9, file=3D0xffffffff80ddfb99 > "/home/git/head/sys/kern/vfs_subr.c", > > > > line=3D2164, interlock=3D0xfffff80193effd80) > > > > at /home/git/head/sys/kern/subr_witness.c:1365 > > > > #54 0xffffffff80730d65 in __lockmgr_args (lk=3D0xfffff80193effd50, > > > > flags=3D524544, ilk=3D0xfffff80193effd80, wmesg=3D0x0, pri=3D0,= timo=3D0, > > > > file=3D0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > line=3D2164) > > > > at /home/git/head/sys/kern/kern_lock.c:756 > > > > #55 0xffffffff80bf1438 in _lockmgr_args (lk=3D0xfffff80193effd50, > flags=3D524544, > > > > ilk=3D0xfffff80193effd80, wmesg=3D0x0, prio=3D0, timo=3D0, > > > > file=3D0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > line=3D2164) > > > > at lockmgr.h:98 > > > > #56 0xffffffff80bef677 in ffs_lock (ap=3D0xfffffe033c22b7c8) > > > > at /home/git/head/sys/ufs/ffs/ffs_vnops.c:385 > > > > #57 0xffffffff80d47cd4 in VOP_LOCK1_APV (vop=3D0xffffffff810cd328, > > > > a=3D0xfffffe033c22b7c8) at vnode_if.c:2082 > > > > #58 0xffffffff808ac2f3 in VOP_LOCK1 (vp=3D0xfffff80193effce8, > flags=3D524544, > > > > file=3D0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > line=3D2164) > > > > at vnode_if.h:859 > > > > #59 0xffffffff808aa122 in _vn_lock (vp=3D0xfffff80193effce8, > flags=3D524544, > > > > file=3D0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > line=3D2164) > > > > at /home/git/head/sys/kern/vfs_vnops.c:1531 > > > > #60 0xffffffff8088d636 in vget (vp=3D0xfffff80193effce8, flags=3D52= 4544, > > > > td=3D0xfffff801ad926000) at /home/git/head/sys/kern/vfs_subr.c:= 2164 > > > > #61 0xffffffff8087884f in vfs_hash_get (mp=3D0xfffff80009db2000, > hash=3D71269052, > > > > flags=3D524288, td=3D0xfffff801ad926000, vpp=3D0xfffffe033c22bb= 40, > fn=3D0, > > > > arg=3D0x0) at /home/git/head/sys/kern/vfs_hash.c:89 > > > > #62 0xffffffff80be7969 in ffs_vgetf (mp=3D0xfffff80009db2000, > ino=3D71269052, > > > > flags=3D524288, vpp=3D0xfffffe033c22bb40, ffs_flags=3D1) > > > > at /home/git/head/sys/ufs/ffs/ffs_vfsops.c:1636 > > > > #63 0xffffffff80bd1d02 in flush_pagedep_deps (pvp=3D0xfffff80193c8d= 588, > > > > mp=3D0xfffff80009db2000, diraddhdp=3D0xfffff80193769b58) > > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12929 > > > > #64 0xffffffff80bd182c in softdep_sync_buf (vp=3D0xfffff80193c8d588= , > > > > bp=3D0xfffffe02d6a8d6d0, waitfor=3D1) > > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12621 > > > > #65 0xffffffff80bf0d40 in ffs_syncvnode (vp=3D0xfffff80193c8d588, > waitfor=3D1, > > > > flags=3D0) at /home/git/head/sys/ufs/ffs/ffs_vnops.c:280 > > > > #66 0xffffffff80babd9a in ffs_truncate (vp=3D0xfffff80193c8d588, > length=3D512, > > > > flags=3D2176, cred=3D0xfffff80009c52b00) > > > > at /home/git/head/sys/ufs/ffs/ffs_inode.c:339 > > > > #67 0xffffffff80bfd315 in ufs_direnter (dvp=3D0xfffff80193c8d588, > > > > tvp=3D0xfffff80193effce8, dirp=3D0xfffffe033c22c390, > cnp=3D0xfffffe033c22c720, > > > > newdirbp=3D0xfffffe02d66d7db0, isrename=3D0) > > > > at /home/git/head/sys/ufs/ufs/ufs_lookup.c:1133 > > > > #68 0xffffffff80c0aaa7 in ufs_mkdir (ap=3D0xfffffe033c22c558) > > > > at /home/git/head/sys/ufs/ufs/ufs_vnops.c:1963 > > > > #69 0xffffffff80d460fd in VOP_MKDIR_APV (vop=3D0xffffffff810cddd8, > > > > a=3D0xfffffe033c22c558) at vnode_if.c:1607 > > > > #70 0xffffffff808a5979 in VOP_MKDIR (dvp=3D0xfffff80193c8d588, > > > > vpp=3D0xfffffe033c22c6f8, cnp=3D0xfffffe033c22c720, > vap=3D0xfffffe033c22c768) > > > > at vnode_if.h:665 > > > > #71 0xffffffff808a585c in kern_mkdirat (td=3D0xfffff801ad926000, > fd=3D-100, > > > > path=3D0x7fffffffe949
, > > > > segflg=3DUIO_USERSPACE, mode=3D511) > > > > at /home/git/head/sys/kern/vfs_syscalls.c:3747 > > > > #72 0xffffffff808a54c3 in sys_mkdir (td=3D0xfffff801ad926000, > > > > uap=3D0xfffffe033c22ca58) at > /home/git/head/sys/kern/vfs_syscalls.c:3678 > > > > #73 0xffffffff80c97044 in syscallenter (td=3D0xfffff801ad926000, > > > > sa=3D0xfffffe033c22ca48) at subr_syscall.c:133 > > > > #74 0xffffffff80c9694a in amd64_syscall (td=3D0xfffff801ad926000, > traced=3D0) > > > > at /home/git/head/sys/amd64/amd64/trap.c:986 > > > > #75 0xffffffff80c6948b in Xfast_syscall () > > > > at /home/git/head/sys/amd64/amd64/exception.S:395 > > > > #76 0x0000000800946eca in ?? () > > > > Previous frame inner to this frame (corrupt stack?) > > > > Current language: auto; currently minimal > > > > (kgdb) > > > > > > > > > > > > > > This is fun, for some definition of it. > > > > > > The process was in the guts of VFS from mkdir(2) syscall, witness > > > triggered printing of the warning for dreaded buf->hashdir->buf > non-real > > > LOR. From the ddb stack backtrace routine, when cnputs released the > > > console spinlock yet another time, timer interrupt fired and started > > > proceeding callouts. One of the callout triggered and needs to wake > > > up a thread sleeping with timeout. There, inside the scheduler, > > > cpu_search_lowest() was called, recursed twice and finally > > > overflown the stack. > > > > > > Is this yet another clang regression ? The cpu_search_lowest() saga > seems > > > to never end. r268211 is uneffective, probably after clang 3.5 import= . > > > > yes, you are right. building kernel without SSP fixes the panic. > > > How did you ensured that it is fixed ? There must be very specific > circumstances: timer interrupt fired while in witness, callout activated, > etc to trigger the panic. > > Or, do you mean that you looked at the assembly for the cpu_search() and > see that it is no longer recursive ? > ouch, sorry. panic was easily reproducible (every buildworld) I disassembled the kernel: ffffffff807a9210 : ffffffff807a9210: 55 push %rbp ffffffff807a9211: 48 89 e5 mov %rsp,%rbp ffffffff807a9214: 48 81 ec a0 01 00 00 sub $0x1a0,%rsp ffffffff807a921b: 48 8b 04 25 f0 d4 29 mov 0xffffffff8129d4f0,%rax ffffffff807a9222: 81 ffffffff807a9223: 48 89 45 f8 mov %rax,-0x8(%rbp) the panic was here ^^^^ ffffffff807a9227: 48 89 bd c8 fe ff ff mov %rdi,-0x138(%rbp) ffffffff807a922e: 48 89 b5 c0 fe ff ff mov %rsi,-0x140(%rbp) ffffffff807a9235: 48 8b 85 c8 fe ff ff mov -0x138(%rbp),%rax it seem to me that failed instruction from SSP prologue. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 15:39:18 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 965FA4A1 for ; Sun, 25 Jan 2015 15:39:18 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FC0B16B for ; Sun, 25 Jan 2015 15:39:16 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::79cb:885c:d74b:842b] (unknown [IPv6:2001:7b8:3a7:0:79cb:885c:d74b:842b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8D6B25C2E; Sun, 25 Jan 2015 16:39:07 +0100 (CET) Subject: Re: How to get the source code of FreeBSD-Clang? Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_96F42615-3601-4EDC-A750-5187EA97B308"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b4 From: Dimitry Andric In-Reply-To: Date: Sun, 25 Jan 2015 16:39:11 +0100 Message-Id: References: To: Yue Chen X-Mailer: Apple Mail (2.1993) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 15:39:18 -0000 --Apple-Mail=_96F42615-3601-4EDC-A750-5187EA97B308 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii O 25 Jan 2015, at 06:16, Yue Chen wrote: > > When I use the original versions (even 3.4.1) of LLVM/Clang to compile > FreeBSD kernel, it always has problems. > > Since I need to modify something in LLVM source and then build the kernel, > where can I get the FreeBSD-friendly Clang/LLVM source code? See the contrib/llvm/patches directory for the list of patches that you need to apply. Not all of these are strictly needed to compile just a kernel, but it is safest to just apply them all. For 3.4.1, you can use the set available here: https://svnweb.freebsd.org/base/stable/10/contrib/llvm/patches/ Alternatively, you can compile the kernel using: make buildkernel WERROR= MK_FORMAT_EXTENSIONS=no which should fix any errors that were emitted because of -Werror. -Dimitry --Apple-Mail=_96F42615-3601-4EDC-A750-5187EA97B308 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlTFDiIACgkQsF6jCi4glqN3vACguBkboPIoHfsz/o52D60Gssqw HboAn0BxwLwt1MBXDnrMmm4UxwtvD6cl =y9yf -----END PGP SIGNATURE----- --Apple-Mail=_96F42615-3601-4EDC-A750-5187EA97B308-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 17:22:48 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B62BBB33; Sun, 25 Jan 2015 17:22:48 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 10FFACF3; Sun, 25 Jan 2015 17:22:47 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0PHMfMq094890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2015 19:22:41 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0PHMfMq094890 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0PHMfUg094889; Sun, 25 Jan 2015 19:22:41 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 25 Jan 2015 19:22:40 +0200 From: Konstantin Belousov To: Dmitry Chagin Subject: Re: dblfault panic r277611 Message-ID: <20150125172240.GC42409@kib.kiev.ua> References: <20150124094633.GA1804@dchagin.static.corbina.net> <20150124103519.GR42409@kib.kiev.ua> <20150124194245.GA72881@dchagin.static.corbina.net> <20150125120648.GX42409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: FreeBSD Current , dim@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 17:22:48 -0000 On Sun, Jan 25, 2015 at 05:15:59PM +0300, Dmitry Chagin wrote: > 2015-01-25 15:06 GMT+03:00 Konstantin Belousov : > > > On Sat, Jan 24, 2015 at 10:42:45PM +0300, Chagin Dmitry wrote: > > > On Sat, Jan 24, 2015 at 12:35:19PM +0200, Konstantin Belousov wrote: > > > > On Sat, Jan 24, 2015 at 12:46:33PM +0300, Chagin Dmitry wrote: > > > > > Hi, > > > > > > > > > > > > > > > dchagin.static.corbina.net dumped core - see /var/crash/vmcore.7 > > > > > > > > > > Sat Jan 24 01:02:20 MSK 2015 > > > > > > > > > > FreeBSD dchagin.static.corbina.net 11.0-CURRENT FreeBSD > > 11.0-CURRENT #2 r277611+c41ef74(lemul): Sat Jan 24 00:53:45 MSK 2015 > > root@dchagin.static.corbina.net:/home/rootobj/home/git/head/sys/YOY > > amd64 > > > > > > > > > > panic: double fault > > > > > > > > > > GNU gdb 6.1.1 [FreeBSD] > > > > > Copyright 2004 Free Software Foundation, Inc. > > > > > GDB is free software, covered by the GNU General Public License, and > > you are > > > > > welcome to change it and/or distribute copies of it under certain > > conditions. > > > > > Type "show copying" to see the conditions. > > > > > There is absolutely no warranty for GDB. Type "show warranty" for > > details. > > > > > This GDB was configured as "amd64-marcel-freebsd"... > > > > > > > > > > Unread portion of the kernel message buffer: > > > > > ffs_syncvnode+0x3b0/frame 0xfffffe033c22bd50 > > > > > ffs_truncate() at ffs_truncate+0xc6a/frame 0xfffffe033c22c150 > > > > > ufs_direnter() at ufs_direnter+0xde5/frame 0xfffffe033c22c280 > > > > > ufs_mkdir() at ufs_mkdir+0xb07/frame 0xfffffe033c22c4a0 > > > > > > > > > > Fatal double fault > > > > > rip = 0xffffffff807a8d03 > > > > > rsp = 0xfffffe033c228e60 > > > > > rbp = 0xfffffe033c229000 > > > > > cpuid = 5; apic id = 05 > > > > > panic: double fault > > > > > cpuid = 5 > > > > > KDB: enter: panic > > > > > > > > > > Reading symbols from /boot/kernel/if_tap.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/if_tap.ko.symbols > > > > > Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/if_bridge.ko.symbols > > > > > Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/bridgestp.ko.symbols > > > > > Reading symbols from /boot/kernel/usb.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/usb.ko.symbols > > > > > Reading symbols from /boot/kernel/xhci.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/xhci.ko.symbols > > > > > Reading symbols from /boot/kernel/vmm.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/vmm.ko.symbols > > > > > Reading symbols from /boot/kernel/nmdm.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/nmdm.ko.symbols > > > > > Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/linprocfs.ko.symbols > > > > > Reading symbols from /boot/kernel/pseudofs.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/pseudofs.ko.symbols > > > > > Reading symbols from /boot/kernel/linux_common.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/linux_common.ko.symbols > > > > > Reading symbols from /boot/kernel/procfs.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/procfs.ko.symbols > > > > > Reading symbols from /boot/kernel/ukbd.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/ukbd.ko.symbols > > > > > Reading symbols from /boot/kernel/ums.ko.symbols...done. > > > > > Loaded symbols for /boot/kernel/ums.ko.symbols > > > > > #0 doadump (textdump=771179792) > > > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > > > 262 dumptid = curthread->td_tid; > > > > > (kgdb) #0 doadump (textdump=771179792) > > > > > at /home/git/head/sys/kern/kern_shutdown.c:262 > > > > > #1 0xffffffff803c1b08 in db_fncall_generic (addr=-2139713712, > > > > > rv=0xfffffe032df744a0, nargs=0, args=0xfffffe032df744b0) > > > > > at /home/git/head/sys/ddb/db_command.c:568 > > > > > #2 0xffffffff803c17d3 in db_fncall (dummy1=-2185367173664, dummy2=0, > > > > > dummy3=0, dummy4=0xfffffe032df745e0 "\n") > > > > > at /home/git/head/sys/ddb/db_command.c:616 > > > > > #3 0xffffffff803c142b in db_command (last_cmdp=0xffffffff810fd6a8, > > > > > cmd_table=0x0, dopager=1) at > > /home/git/head/sys/ddb/db_command.c:440 > > > > > #4 0xffffffff803c0f9d in db_command_loop () > > > > > at /home/git/head/sys/ddb/db_command.c:493 > > > > > #5 0xffffffff803c58d9 in db_trap (type=3, code=0) > > > > > at /home/git/head/sys/ddb/db_main.c:251 > > > > > #6 0xffffffff807cc704 in kdb_trap (type=3, code=0, > > tf=0xfffffe032df74cc0) > > > > > at /home/git/head/sys/kern/subr_kdb.c:654 > > > > > #7 0xffffffff80c94e1d in trap (frame=0xfffffe032df74cc0) > > > > > at /home/git/head/sys/amd64/amd64/trap.c:546 > > > > > #8 0xffffffff80c9655f in trap_check (frame=0xfffffe032df74cc0) > > > > > at /home/git/head/sys/amd64/amd64/trap.c:645 > > > > > #9 0xffffffff80c691a2 in calltrap () > > > > > at /home/git/head/sys/amd64/amd64/exception.S:235 > > > > > #10 0xffffffff807cbf15 in breakpoint () at cpufunc.h:63 > > > > > #11 0xffffffff807cbaff in kdb_enter (why=0xffffffff80dcd635 "panic", > > > > > msg=0xffffffff80dcd635 "panic") at > > /home/git/head/sys/kern/subr_kdb.c:443 > > > > > #12 0xffffffff80769768 in vpanic (fmt=0xffffffff80e24597 "double > > fault", > > > > > ap=0xfffffe032df74ec0) at > > /home/git/head/sys/kern/kern_shutdown.c:740 > > > > > #13 0xffffffff80769820 in panic (fmt=0xffffffff80e24597 "double > > fault") > > > > > at /home/git/head/sys/kern/kern_shutdown.c:676 > > > > > #14 0xffffffff80c9667d in dblfault_handler (frame=0xfffffe032df74f40) > > > > > at /home/git/head/sys/amd64/amd64/trap.c:912 > > > > > #15 0xffffffff80c6929c in Xdblfault () > > > > > at /home/git/head/sys/amd64/amd64/exception.S:291 > > > > > #16 0xffffffff807a8d03 in cpu_search_lowest (cg=Cannot access memory > > at address 0xfffffe033c228ec8 > > > > > ) > > > > > at /home/git/head/sys/kern/sched_ule.c:764 > > > > > #17 0xffffffff807a9094 in cpu_search_lowest (cg=0xffffffff8128a6e8, > > > > > low=0xfffffe033c2292f8) at > > /home/git/head/sys/kern/sched_ule.c:690 > > > > > #18 0xffffffff807a9094 in cpu_search_lowest (cg=0xffffffff8128a6b0, > > > > > low=0xfffffe033c229380) at > > /home/git/head/sys/kern/sched_ule.c:690 > > > > > #19 0xffffffff807b0f56 in sched_lowest (cg=0xffffffff8128a6b0, mask= > > > > > {__bits = {255, 0, 0, 0}}, pri=121, maxload=2147483647, > > prefer=5) > > > > > at /home/git/head/sys/kern/sched_ule.c:796 > > > > > #20 0xffffffff807abcdb in sched_pickcpu (td=0xfffff80009e5a9a0, > > flags=0) > > > > > at /home/git/head/sys/kern/sched_ule.c:1276 > > > > > #21 0xffffffff807ace35 in sched_add (td=0xfffff80009e5a9a0, flags=0) > > > > > at /home/git/head/sys/kern/sched_ule.c:2395 > > > > > #22 0xffffffff807acac9 in sched_wakeup (td=0xfffff80009e5a9a0) > > > > > at /home/git/head/sys/kern/sched_ule.c:2029 > > > > > #23 0xffffffff8077d6a8 in setrunnable (td=0xfffff80009e5a9a0) > > > > > at /home/git/head/sys/kern/kern_synch.c:544 > > > > > #24 0xffffffff807e4e98 in sleepq_resume_thread > > (sq=0xfffff80009e55d80, > > > > > td=0xfffff80009e5a9a0, pri=0) > > > > > at /home/git/head/sys/kern/subr_sleepqueue.c:776 > > > > > #25 0xffffffff807e306a in sleepq_timeout (arg=0xfffff80009e5a9a0) > > > > > at /home/git/head/sys/kern/subr_sleepqueue.c:915 > > > > > #26 0xffffffff80791b40 in softclock_call_cc (c=0xfffff80009e5ad38, > > > > > cc=0xffffffff813a4200, direct=1) > > > > > at /home/git/head/sys/kern/kern_timeout.c:724 > > > > > #27 0xffffffff807913bd in callout_process (now=740683739317) > > > > > at /home/git/head/sys/kern/kern_timeout.c:499 > > > > > #28 0xffffffff80ce346a in handleevents (now=740683739317, fake=0) > > > > > at /home/git/head/sys/kern/kern_clocksource.c:212 > > > > > #29 0xffffffff80ce3fd6 in timercb (et=0xffffffff8137df68, arg=0x0) > > > > > at /home/git/head/sys/kern/kern_clocksource.c:345 > > > > > #30 0xffffffff80d376e3 in lapic_handle_timer > > (frame=0xfffffe033c229c50) > > > > > at /home/git/head/sys/x86/x86/local_apic.c:883 > > > > > #31 0xffffffff80c69cfc in Xtimerint () at apic_vector.S:109 > > > > > #32 0xffffffff80c745ef in write_rflags (rf=642) at cpufunc.h:382 > > > > > #33 0xffffffff80c6f225 in intr_restore (rflags=642) at cpufunc.h:775 > > > > > #34 0xffffffff80c71ce8 in spinlock_exit () > > > > > at /home/git/head/sys/amd64/amd64/machdep.c:2177 > > > > > #35 0xffffffff8074335c in __mtx_unlock_spin_flags > > (c=0xffffffff8119ec80, > > > > > opts=0, file=0xffffffff80dc3d2b > > "/home/git/head/sys/kern/kern_cons.c", > > > > > line=530) at /home/git/head/sys/kern/kern_mutex.c:305 > > > > > #36 0xffffffff806df9fc in cnputs (p=0xfffffe033c22a402 "\"<\003þÿÿ") > > > > > at /home/git/head/sys/kern/kern_cons.c:530 > > > > > #37 0xffffffff807d76ae in putbuf (c=10, ap=0xfffffe033c22a3b8) > > > > > at /home/git/head/sys/kern/subr_prf.c:427 > > > > > #38 0xffffffff807d60d6 in putchar (c=10, arg=0xfffffe033c22a3b8) > > > > > at /home/git/head/sys/kern/subr_prf.c:471 > > > > > #39 0xffffffff807d43e3 in kvprintf (fmt=0xffffffff80d77b33 "", > > > > > func=0xffffffff807d6010 , arg=0xfffffe033c22a3b8, > > radix=10, > > > > > ap=0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:720 > > > > > #40 0xffffffff807d6569 in _vprintf (level=-1, flags=5, > > > > > fmt=0xffffffff80d77b31 "%c", ap=0xfffffe033c22a510) > > > > > at /home/git/head/sys/kern/subr_prf.c:271 > > > > > #41 0xffffffff807d68dd in vprintf (fmt=0xffffffff80d77b31 "%c", > > > > > ap=0xfffffe033c22a510) at /home/git/head/sys/kern/subr_prf.c:388 > > > > > #42 0xffffffff807d689b in printf (fmt=0xffffffff80d77b31 "%c") > > > > > at /home/git/head/sys/kern/subr_prf.c:377 > > > > > #43 0xffffffff803c5d55 in db_putc (c=10) > > > > > at /home/git/head/sys/ddb/db_output.c:156 > > > > > #44 0xffffffff803c5b21 in db_putchar (c=10, arg=0xfffffe033c22aad8) > > > > > at /home/git/head/sys/ddb/db_output.c:128 > > > > > #45 0xffffffff807d3b65 in kvprintf (fmt=0xffffffff80d8090f "", > > > > > func=0xffffffff803c5af0 , arg=0xfffffe033c22aad8, > > radix=16, > > > > > ap=0xfffffe033c22aac0) at /home/git/head/sys/kern/subr_prf.c:645 > > > > > #46 0xffffffff803c5ad8 in db_printf (fmt=0xffffffff80d8090e "\n") > > > > > at /home/git/head/sys/ddb/db_output.c:340 > > > > > #47 0xffffffff80c67f73 in db_print_stack_entry ( > > > > > name=0xffffffff815c8262 "ufs_mkdir", narg=0, argnp=0x0, > > > > > argp=0xfffffe033c22c4b0, callpc=18446744071574694567, > > > > > frame=0xfffffe033c22c4a0) at > > /home/git/head/sys/amd64/amd64/db_trace.c:260 > > > > > #48 0xffffffff80c66f3b in db_backtrace (td=0xfffff801ad926000, > > tf=0x0, > > > > > frame=0xfffffe033c22c4a0, pc=18446744071574694567, count=1005) > > > > > at /home/git/head/sys/amd64/amd64/db_trace.c:462 > > > > > #49 0xffffffff80c66bdf in db_trace_self () > > > > > at /home/git/head/sys/amd64/amd64/db_trace.c:498 > > > > > #50 0xffffffff803c568e in db_trace_self_wrapper () > > > > > at /home/git/head/sys/ddb/db_main.c:268 > > > > > #51 0xffffffff807cbcd8 in kdb_backtrace () > > > > > at /home/git/head/sys/kern/subr_kdb.c:370 > > > > > #52 0xffffffff807fe924 in _witness_debugger (cond=1, > > > > > msg=0xffffffff80dd6e29 "witness_checkorder") > > > > > at /home/git/head/sys/kern/subr_witness.c:2904 > > > > > #53 0xffffffff807fe2de in witness_checkorder > > (lock=0xfffff80193effd50, > > > > > flags=9, file=0xffffffff80ddfb99 > > "/home/git/head/sys/kern/vfs_subr.c", > > > > > line=2164, interlock=0xfffff80193effd80) > > > > > at /home/git/head/sys/kern/subr_witness.c:1365 > > > > > #54 0xffffffff80730d65 in __lockmgr_args (lk=0xfffff80193effd50, > > > > > flags=524544, ilk=0xfffff80193effd80, wmesg=0x0, pri=0, timo=0, > > > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > > line=2164) > > > > > at /home/git/head/sys/kern/kern_lock.c:756 > > > > > #55 0xffffffff80bf1438 in _lockmgr_args (lk=0xfffff80193effd50, > > flags=524544, > > > > > ilk=0xfffff80193effd80, wmesg=0x0, prio=0, timo=0, > > > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > > line=2164) > > > > > at lockmgr.h:98 > > > > > #56 0xffffffff80bef677 in ffs_lock (ap=0xfffffe033c22b7c8) > > > > > at /home/git/head/sys/ufs/ffs/ffs_vnops.c:385 > > > > > #57 0xffffffff80d47cd4 in VOP_LOCK1_APV (vop=0xffffffff810cd328, > > > > > a=0xfffffe033c22b7c8) at vnode_if.c:2082 > > > > > #58 0xffffffff808ac2f3 in VOP_LOCK1 (vp=0xfffff80193effce8, > > flags=524544, > > > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > > line=2164) > > > > > at vnode_if.h:859 > > > > > #59 0xffffffff808aa122 in _vn_lock (vp=0xfffff80193effce8, > > flags=524544, > > > > > file=0xffffffff80ddfb99 "/home/git/head/sys/kern/vfs_subr.c", > > line=2164) > > > > > at /home/git/head/sys/kern/vfs_vnops.c:1531 > > > > > #60 0xffffffff8088d636 in vget (vp=0xfffff80193effce8, flags=524544, > > > > > td=0xfffff801ad926000) at /home/git/head/sys/kern/vfs_subr.c:2164 > > > > > #61 0xffffffff8087884f in vfs_hash_get (mp=0xfffff80009db2000, > > hash=71269052, > > > > > flags=524288, td=0xfffff801ad926000, vpp=0xfffffe033c22bb40, > > fn=0, > > > > > arg=0x0) at /home/git/head/sys/kern/vfs_hash.c:89 > > > > > #62 0xffffffff80be7969 in ffs_vgetf (mp=0xfffff80009db2000, > > ino=71269052, > > > > > flags=524288, vpp=0xfffffe033c22bb40, ffs_flags=1) > > > > > at /home/git/head/sys/ufs/ffs/ffs_vfsops.c:1636 > > > > > #63 0xffffffff80bd1d02 in flush_pagedep_deps (pvp=0xfffff80193c8d588, > > > > > mp=0xfffff80009db2000, diraddhdp=0xfffff80193769b58) > > > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12929 > > > > > #64 0xffffffff80bd182c in softdep_sync_buf (vp=0xfffff80193c8d588, > > > > > bp=0xfffffe02d6a8d6d0, waitfor=1) > > > > > at /home/git/head/sys/ufs/ffs/ffs_softdep.c:12621 > > > > > #65 0xffffffff80bf0d40 in ffs_syncvnode (vp=0xfffff80193c8d588, > > waitfor=1, > > > > > flags=0) at /home/git/head/sys/ufs/ffs/ffs_vnops.c:280 > > > > > #66 0xffffffff80babd9a in ffs_truncate (vp=0xfffff80193c8d588, > > length=512, > > > > > flags=2176, cred=0xfffff80009c52b00) > > > > > at /home/git/head/sys/ufs/ffs/ffs_inode.c:339 > > > > > #67 0xffffffff80bfd315 in ufs_direnter (dvp=0xfffff80193c8d588, > > > > > tvp=0xfffff80193effce8, dirp=0xfffffe033c22c390, > > cnp=0xfffffe033c22c720, > > > > > newdirbp=0xfffffe02d66d7db0, isrename=0) > > > > > at /home/git/head/sys/ufs/ufs/ufs_lookup.c:1133 > > > > > #68 0xffffffff80c0aaa7 in ufs_mkdir (ap=0xfffffe033c22c558) > > > > > at /home/git/head/sys/ufs/ufs/ufs_vnops.c:1963 > > > > > #69 0xffffffff80d460fd in VOP_MKDIR_APV (vop=0xffffffff810cddd8, > > > > > a=0xfffffe033c22c558) at vnode_if.c:1607 > > > > > #70 0xffffffff808a5979 in VOP_MKDIR (dvp=0xfffff80193c8d588, > > > > > vpp=0xfffffe033c22c6f8, cnp=0xfffffe033c22c720, > > vap=0xfffffe033c22c768) > > > > > at vnode_if.h:665 > > > > > #71 0xffffffff808a585c in kern_mkdirat (td=0xfffff801ad926000, > > fd=-100, > > > > > path=0x7fffffffe949
, > > > > > segflg=UIO_USERSPACE, mode=511) > > > > > at /home/git/head/sys/kern/vfs_syscalls.c:3747 > > > > > #72 0xffffffff808a54c3 in sys_mkdir (td=0xfffff801ad926000, > > > > > uap=0xfffffe033c22ca58) at > > /home/git/head/sys/kern/vfs_syscalls.c:3678 > > > > > #73 0xffffffff80c97044 in syscallenter (td=0xfffff801ad926000, > > > > > sa=0xfffffe033c22ca48) at subr_syscall.c:133 > > > > > #74 0xffffffff80c9694a in amd64_syscall (td=0xfffff801ad926000, > > traced=0) > > > > > at /home/git/head/sys/amd64/amd64/trap.c:986 > > > > > #75 0xffffffff80c6948b in Xfast_syscall () > > > > > at /home/git/head/sys/amd64/amd64/exception.S:395 > > > > > #76 0x0000000800946eca in ?? () > > > > > Previous frame inner to this frame (corrupt stack?) > > > > > Current language: auto; currently minimal > > > > > (kgdb) > > > > > > > > > > > > > > > > > > This is fun, for some definition of it. > > > > > > > > The process was in the guts of VFS from mkdir(2) syscall, witness > > > > triggered printing of the warning for dreaded buf->hashdir->buf > > non-real > > > > LOR. From the ddb stack backtrace routine, when cnputs released the > > > > console spinlock yet another time, timer interrupt fired and started > > > > proceeding callouts. One of the callout triggered and needs to wake > > > > up a thread sleeping with timeout. There, inside the scheduler, > > > > cpu_search_lowest() was called, recursed twice and finally > > > > overflown the stack. > > > > > > > > Is this yet another clang regression ? The cpu_search_lowest() saga > > seems > > > > to never end. r268211 is uneffective, probably after clang 3.5 import. > > > > > > yes, you are right. building kernel without SSP fixes the panic. > > > > > How did you ensured that it is fixed ? There must be very specific > > circumstances: timer interrupt fired while in witness, callout activated, > > etc to trigger the panic. > > > > Or, do you mean that you looked at the assembly for the cpu_search() and > > see that it is no longer recursive ? > > > > ouch, sorry. panic was easily reproducible (every buildworld) > I disassembled the kernel: > > ffffffff807a9210 : > ffffffff807a9210: 55 push %rbp > ffffffff807a9211: 48 89 e5 mov %rsp,%rbp > ffffffff807a9214: 48 81 ec a0 01 00 00 sub $0x1a0,%rsp > ffffffff807a921b: 48 8b 04 25 f0 d4 29 mov > 0xffffffff8129d4f0,%rax > ffffffff807a9222: 81 > ffffffff807a9223: 48 89 45 f8 mov %rax,-0x8(%rbp) > the panic was here ^^^^ > ffffffff807a9227: 48 89 bd c8 fe ff ff mov %rdi,-0x138(%rbp) > ffffffff807a922e: 48 89 b5 c0 fe ff ff mov %rsi,-0x140(%rbp) > ffffffff807a9235: 48 8b 85 c8 fe ff ff mov -0x138(%rbp),%rax > > it seem to me that failed instruction from SSP prologue. It happens to be a first instruction accessing the new stack frame after the space for locals is reserved. It might be that SSP results in slightly higher stack usage, so its removal indeed allows the stack to suffice. But for me, it is clang which is broken and compiles cpu_search() into recursion, again. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 17:59:05 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F52541F; Sun, 25 Jan 2015 17:59:05 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3F71FD4; Sun, 25 Jan 2015 17:59:04 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id q1so4603808lam.2; Sun, 25 Jan 2015 09:59:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2/9dn2zZpe67hrn5NiHOSlGbBs79TWlZThrUGOtHtc8=; b=pN7eWASenGYIX38tBjyF10jATrjo2fWzDICxouJu9l35JjGedBafeRaw8O2uQFseeq 1Ji2Mo3qTkm/thjd3n2n6ibx/k/juObSg+5KepQzOu73Urfd+JuyD/VqhP/W1DHAos8b wkhUFWmgNkqQM4V5UpxLuGT7DNIYdWsqn+O6v2FXJk4bYYYVm1EiS/Go1yuPyeKMD2HZ yrd4oyhFVpu/M1BQiq9MQylsF83h9HpAEZ/fGjAA649HhQ1Xj1uQiMoFemNMStR4wkCH n8b+oN/d8YDzQ3lrfcjIFbY65Y7Ea3s4VqVWGuHn74iKubEBG1rMSmKjWrPX7/wvLahS 5+pg== X-Received: by 10.152.116.43 with SMTP id jt11mr11297406lab.69.1422208742734; Sun, 25 Jan 2015 09:59:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.12.6 with HTTP; Sun, 25 Jan 2015 09:58:32 -0800 (PST) In-Reply-To: References: From: Yue Chen Date: Sun, 25 Jan 2015 12:58:32 -0500 Message-ID: Subject: Re: How to get the source code of FreeBSD-Clang? To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 17:59:05 -0000 Any patch available for LLVM 3.5 ? As I build using the command you provide, the DWARF section still has problems. On Sun, Jan 25, 2015 at 10:39 AM, Dimitry Andric wrote: > O 25 Jan 2015, at 06:16, Yue Chen wrote: > > > > When I use the original versions (even 3.4.1) of LLVM/Clang to compile > > FreeBSD kernel, it always has problems. > > > > Since I need to modify something in LLVM source and then build the > kernel, > > where can I get the FreeBSD-friendly Clang/LLVM source code? > > See the contrib/llvm/patches directory for the list of patches that you > need to apply. Not all of these are strictly needed to compile just a > kernel, but it is safest to just apply them all. > > For 3.4.1, you can use the set available here: > > https://svnweb.freebsd.org/base/stable/10/contrib/llvm/patches/ > > Alternatively, you can compile the kernel using: > > make buildkernel WERROR= MK_FORMAT_EXTENSIONS=no > > which should fix any errors that were emitted because of -Werror. > > -Dimitry > > From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 18:01:44 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6D2055F for ; Sun, 25 Jan 2015 18:01:44 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E88DFF for ; Sun, 25 Jan 2015 18:01:43 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::79cb:885c:d74b:842b] (unknown [IPv6:2001:7b8:3a7:0:79cb:885c:d74b:842b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 7DF0A5C2E; Sun, 25 Jan 2015 19:01:41 +0100 (CET) Subject: Re: How to get the source code of FreeBSD-Clang? Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_3ACF7F2B-07F1-4E08-92DF-7F6CDCDF6518"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b4 From: Dimitry Andric In-Reply-To: Date: Sun, 25 Jan 2015 19:01:41 +0100 Message-Id: <284EA046-63F5-4BBF-BA66-D6895E448F0E@FreeBSD.org> References: To: Yue Chen X-Mailer: Apple Mail (2.1993) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 18:01:44 -0000 --Apple-Mail=_3ACF7F2B-07F1-4E08-92DF-7F6CDCDF6518 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 25 Jan 2015, at 18:58, Yue Chen wrote: > Any patch available for LLVM 3.5 ? Yes, use this patch set for 3.5.x: https://svnweb.freebsd.org/base/head/contrib/llvm/patches/ > As I build using the command you provide, the DWARF section still has = problems. What error are you getting? Please provide more information. -Dimitry --Apple-Mail=_3ACF7F2B-07F1-4E08-92DF-7F6CDCDF6518 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlTFL40ACgkQsF6jCi4glqOhMwCfQUwnvDgijtO1aSb//99F6DzU nXMAoJekCLePqZ7W1pj6ZFqwvCzgyUFd =mR/T -----END PGP SIGNATURE----- --Apple-Mail=_3ACF7F2B-07F1-4E08-92DF-7F6CDCDF6518-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 23:38:53 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F512183 for ; Sun, 25 Jan 2015 23:38:53 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id 08944852 for ; Sun, 25 Jan 2015 23:38:51 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id 9D83D11B1D8F for ; Sun, 25 Jan 2015 15:38:52 -0800 (PST) Date: Sun, 25 Jan 2015 16:38:50 -0700 (MST) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1422229130804-5983627.post@n5.nabble.com> In-Reply-To: <20150124002956.GI1101@hades.panopticon> References: <20150124002956.GI1101@hades.panopticon> Subject: Re: OptionalObsoleteFiles.inc completeness improvement, try 2 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.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 23:38:53 -0000 > In other words, if a user has some WITHOUT_* set in src.conf, > specific files are not installed by installworld, but not removed > by remove-old, which I try to fix. Please carry on, I saw quite a few times that this behaviour was assumed by new users, only it is not (yet), to their surprise :) -- View this message in context: http://freebsd.1045724.n5.nabble.com/OptionalObsoleteFiles-inc-completeness-improvement-try-2-tp5983192p5983627.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 06:13:06 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0338BC0E; Mon, 26 Jan 2015 06:13:06 +0000 (UTC) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (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 D48EBF94; Mon, 26 Jan 2015 06:13:05 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t0Q6CuiI071632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 25 Jan 2015 22:12:56 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id t0Q6CuGo071631; Sun, 25 Jan 2015 22:12:56 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA04819; Sun, 25 Jan 15 21:57:51 PST Date: Sun, 25 Jan 2015 21:57:49 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: andrnils@gmail.com Subject: How to read a disklabel (Re: What replaces DIOCGDINFO?) Message-Id: <54c5d75d.vYjlikWm5nAMV9br%perryh@pluto.rain.com> References: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, imp@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 06:13:06 -0000 Andreas Nilsson wrote: > On Sun, Jan 25, 2015 at 9:31 AM, Perry Hutchison > wrote: > > -r276737 removed 4 ioctls, including DIOCGDINFO, from . > > The commit log entry says only "Remove old ioctl use and support, once > > and for all." > > > > What are users of that mechanism supposed to use instead? > > http://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html > might have the answer for you. Same symptom, but DIOCGMEDIASIZE is not the solution in this case because the port reads the disklabel to identify the partition that contains a particular sector of the device. To do that, AFAIK it needs to actually retrieve and examine the label. The other ioctls in don't look all that promising, either. From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 07:22:58 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60124C0B for ; Mon, 26 Jan 2015 07:22:58 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2912E857 for ; Mon, 26 Jan 2015 07:22:57 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id ar1so7169502iec.13 for ; Sun, 25 Jan 2015 23:22:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=VqBLw2o3Pb+kVQcBXTX8vBp8dia7bM/Egmj3TBR4qSs=; b=LkQMpz3Be2vvPQ1Z7LV9viruRqhHcbHSczNXHsOtMnUgcwFVr6tUP9+C3gtL3TDlLc OiCN1YkFH55ebfCJ3HrPtK6if4yvvuZ3/S9SVZIvh9IOPndLB07F9nvh9vOWLasMdGzY f4utT/KO5/0gEnx5BI+nOvpy8OaldvyQJFYW/yLfRJ3tZkLiFzB90g0E16kWknCH3h3h VJ9AQ4YQfglvABJrIMG40U7uJoxC5vvou4YCjLojvDMDnfKTtMw9tO2r8YPbTSuQjBqH d2AnIleBjFiSf04KrDNuvXZlAA2yQucybVreOWiQ3G5Ee8T07b6elopcqGVo7bYO8Ewo NLuQ== X-Gm-Message-State: ALoCoQkC05U6A14L2vrRBKpYVOfDKcxHWu8/YYKOivA9F74VBSDRSfp3HfeJWsfhclfyHsOScVCP X-Received: by 10.42.214.212 with SMTP id hb20mr18972479icb.19.1422256977137; Sun, 25 Jan 2015 23:22:57 -0800 (PST) Received: from netflix-mac-wired.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id p18sm540928iop.27.2015.01.25.23.22.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 Jan 2015 23:22:56 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: How to read a disklabel (Re: What replaces DIOCGDINFO?) From: Warner Losh In-Reply-To: <54c5d75d.vYjlikWm5nAMV9br%perryh@pluto.rain.com> Date: Mon, 26 Jan 2015 00:22:55 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <197159D3-4654-4F2E-A6CB-582029DAF329@bsdimp.com> References: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> <54c5d75d.vYjlikWm5nAMV9br%perryh@pluto.rain.com> To: Perry Hutchison X-Mailer: Apple Mail (2.1993) Cc: freebsd-current@freebsd.org, imp@freebsd.org, andrnils@gmail.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 07:22:58 -0000 > On Jan 25, 2015, at 10:57 PM, Perry Hutchison = wrote: >=20 > Andreas Nilsson wrote: >> On Sun, Jan 25, 2015 at 9:31 AM, Perry Hutchison = >> wrote: >>> -r276737 removed 4 ioctls, including DIOCGDINFO, from = . >>> The commit log entry says only "Remove old ioctl use and support, = once >>> and for all." >>>=20 >>> What are users of that mechanism supposed to use instead? >>=20 >> = http://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.htm= l >> might have the answer for you. >=20 > Same symptom, but DIOCGMEDIASIZE is not the solution in this case > because the port reads the disklabel to identify the partition that > contains a particular sector of the device. To do that, AFAIK it > needs to actually retrieve and examine the label. The other ioctls > in don't look all that promising, either. Most modern disks don=E2=80=99t even have BSD disk labels. They just = have GPT partitions. So the DIOCGDINFO failed to work an interesting amount of the time. There=E2=80=99s no easy way to fix that, since the disk label = sizes aren=E2=80=99t big enough to return GPT data. gpart list contains the information needed. You can find the source in /usr/src/sbin/geom/class/part/geom_part.c libgeom(3) has some of the info you=E2=80=99ll need as well. However, it is likely easier to pull = it out of either the XML version of the config sysctl (kern.geom.confxml) or the simple text version (kern.geom.conftxt). I imagine the latter is likely best = for finding which partition an absolute sector belongs to. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 12:19:10 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62DCB1D6; Mon, 26 Jan 2015 12:19:10 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0416FA2F; Mon, 26 Jan 2015 12:19:09 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id h11so9486969wiw.5; Mon, 26 Jan 2015 04:19:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gcRsygA/4ID882XSaojXZwFAjdzV4LO2xE70JLM79Wg=; b=r5SyTFzJ9fpMchJaLrTGtU9oZyW8UjhpKn44p2Fvc64d5r2Fl/2+MsX7f0zlYdAZnc wnZsObTva0jx3fZn3ePG4zvRlJtAW81/oEaczBip3x0lVFXxsXzF9FCt1EPzaFFcJyQx xxo+pLQ7yVEXbIXp1nCL9QWghhEF/csib/WzSDXgHQxAe0CqdD9VbHd19CwvQjzmulpE FmtSZKnV5e0GAldfqKogItnC8rcvBGKt3AwLcDCCp5eIQrDesEJsKBSfu/kcvqtcZV2V pS82cZlEV00FJN4s0YsTnEuuEmTcbh0GFQLBqINCr/wwjSEW5/qZX103dHHQ10CeP2jm FjeA== MIME-Version: 1.0 X-Received: by 10.180.98.228 with SMTP id el4mr5501560wib.77.1422274748196; Mon, 26 Jan 2015 04:19:08 -0800 (PST) Received: by 10.217.64.10 with HTTP; Mon, 26 Jan 2015 04:19:08 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Jan 2015 13:19:08 +0100 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: "Ranjan1018 ." <214748mv@gmail.com> To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current , Konstantin Belousov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 12:19:10 -0000 2015-01-24 23:25 GMT+01:00 Adrian Chadd : > Hi, > > I've just found a regression. > > The backlight adjustment doesn't work on my ivybridge mobile laptop > (Lenovo X230) after the dri update. > > I've added debugging. It's making it all the way to the pch backlight > panel update routine in intel_panel.c, but it's not changing the > backlight appearance itself. > > The "intel_backlight" program from intel-gpu-tools" also no longer > changes the backlight value. > > I'm going to finish rebuilding -HEAD on the sandy bridge laptop here > and try it out. > > Thanks, > > > > -adrian > Hi, I have the same issue on my Samsung Ativ 2 laptop. Regards, Maurizio From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 19:32:35 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2C8A403; Mon, 26 Jan 2015 19:32:35 +0000 (UTC) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30B5CD5; Mon, 26 Jan 2015 19:32:35 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3kWLnV1lxXzb9; Mon, 26 Jan 2015 20:32:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1422300742; x=1424892743; bh=FPU/iGlKX/TBWUaPN5ywvkGCkZsvwfGWIdn YX6YUvU4=; b=aJhDzUSH0EpWSS6xsHS0+bq5QXERbAzMELS/OMfvbnsLGcxvvW+ dhw6ZA7iI2WC2gjxGqN48G7qyV4PXfWoItu5k5xQMMKmFTfs8OBgWDSYBK6ky00+ 2MCy3uPQqdekH8uv0aIb3n9xWqwyibU2kNYHswxSMLUjwPtfnCbKZtNw= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id Mxl_gSk0gBLR; Mon, 26 Jan 2015 20:32:22 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP; Mon, 26 Jan 2015 20:32:22 +0100 (CET) Received: from neli.ijs.si (neli.ijs.si [IPv6:2001:1470:ff80:88:21c:c0ff:feb1:8c91]) by mildred.ijs.si (Postfix) with ESMTP id 3kWLnL2wyWzfS; Mon, 26 Jan 2015 20:32:22 +0100 (CET) Received: from neli.ijs.si ([2001:1470:ff80:88:21c:c0ff:feb1:8c91]) by neli.ijs.si with HTTP (HTTP/1.1 POST); Mon, 26 Jan 2015 20:32:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 26 Jan 2015 20:32:22 +0100 From: Mark Martinec To: freebsd-current@freebsd.org, perl@freebsd.org Subject: Memory corruption in a master perl process after child exits - only under FreeBSD 10.0 amd64 (not in 10.1 or 9.*) Organization: J. Stefan Institute Message-ID: <1ac9f02be1360da3969ddb9501d0375a@mailbox.ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.0.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 19:32:35 -0000 There is a problem report since July 2014 in a Perl bug tracker, which seems to affect only FreeBSD 10.0 amd64 (regardless of a version of Perl or usage of clang vs. gcc compiler): https://rt.perl.org/Ticket/Display.html?id=122199 I wonder if someone intimately familiar with handling of virtual memory, fork, swap, and process exit / wait(2) under FreeBSD would be able to recognize what has changed in these areas between 9.2 -> 10.0 and 10.0 -> 10.1, so that only 10.0 is misbehaving, but 10.1 apparently fixed the problem again. Below is my short summary of the issue (it is the last comment in the referenced problem report). Further details are in that PR. It's been a real mystery, difficult to reproduce, but definitely there. It might be a Perl bug, but it looks ever more likely that it is a FreeBSD issue. Mark After upgrading to FreeBSD 10.1 (from 10.0) and running the same application with the same version of Perl for two months now, with child process periodic retiring and re-spawning new child process by a master process as previously under FreeBSD 9.x, I can now confirm that the problem no longer occurs. I can also confirm that the problem under 10.0 can be avoided by not letting child processes to voluntarily exit, so the master process never sees a child termination in wait() and never needs to spawn (fork) another child process. A brief summary of the problem: Setup: an application consisting of a master perl process spawning worker child processes, which periodically voluntarily self-terminate, to be replaced by a fresh child process forked from the master process. Environent: - occurs only on FreeBSD 10.0 amd64, any recent version of perl, gcc or clang. - does not occur on FreeBSD 9.x or 10.1, and not on i383, not reproducible on Linux What seems to be happening: - a child process after doing some work (possibly touching swap) does a normal exit; - a parent process gets a SIGCHLD signal, handles a wait() and for some obscure reason some of its memory gets corrupted; - a parent process forks creating a new worker child process, which inherits corrupted sections of parent's memory, consequently later leading to its (child) crash if it happens to use that part of the memory (opcodes or data structures) during its normal work. Any newly born child process inherits the same memory corruption and crashes alike. So it seems the problem is somehow connected with how FreeBSD 10.0 on amd64 manages virtual memory (fork, exit, wait, possibly involving swap). The problem is apparently fixed in 10.1, and not present in 9.x. Does anybody have a sound explanation? From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 20:06:04 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2193810B for ; Mon, 26 Jan 2015 20:06:04 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFC1E660 for ; Mon, 26 Jan 2015 20:06:03 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id rl12so10948815iec.11 for ; Mon, 26 Jan 2015 12:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=SjpvWUyD0iNAnX6smIbHEXmgOjBYEY7YAEGugGQX47M=; b=KmJqnZp9xMmbc9j5NiO6RLFLBgC7EMwuLsYFtVRWI5jk7xHNgkvovBS3Zr2d+E5bWd WO50wB5rQ3Mejs9EgJCdzNY9xkQz/ZW+dKHA3/AEixP7CcKMgRSIPZOnxFnSA7ib+gMy LlO31pacFieQf/jw+boXmlfCm2AnT2gPnGHeOyyTAZn0XrdyBVWSdrfXK96RgeeCOmOc wFa12eEkHFbl5mPxpfl4NEscjN8Kixe7dIA/yt4TkUGL9/6wiB6ABbLoNh4rdaqvSzES 4W6EhVDl5EhYcELBcEN4DB36FkqnOx5THRuKW99Vsicjq8cDfAslqOWGM2ZQNbEoa36k DVjA== MIME-Version: 1.0 X-Received: by 10.50.79.135 with SMTP id j7mr12416636igx.32.1422302758542; Mon, 26 Jan 2015 12:05:58 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Mon, 26 Jan 2015 12:05:58 -0800 (PST) Date: Mon, 26 Jan 2015 12:05:58 -0800 X-Google-Sender-Auth: t73tbyblHhMkgvpN7dc6sS3f1rM Message-ID: Subject: Is anyone using the schedgraph.d script? From: Adrian Chadd To: freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 20:06:04 -0000 Hi, I'm having problems with Ryan's schedgraph.d script (people.freebsd.org/~rstone/dtrace/) It runs fine, but if a CPU core is 100% busy, I get zero scheduler events logged from it. Said core is doing around 30,000 syscalls a second, around 250,000 context switches and 125,000 interrupt sa second - but whilst it's doing this, I get zero events from dtrace for said CPU. Has anyone hit this kind of situation before? -a From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 20:11:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBFE445A for ; Mon, 26 Jan 2015 20:11:50 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83F36797 for ; Mon, 26 Jan 2015 20:11:50 +0000 (UTC) Received: by mail-ig0-f176.google.com with SMTP id hl2so337281igb.3 for ; Mon, 26 Jan 2015 12:11:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=QG1gRCWzWBuCmxVxFZml8Dfd845q/+NI0TLb7lerS+U=; b=Q5vgZZQ3XaH5tQuN2vn7Nstd84ZZN3ii4LJRXbpgU5qZ7KdL7K8gt/pGSr0k+3K1jP 1rsn3vMQdI5Ql/LsZbDvomPlmnsSM7yW/dcStFTtbArvXVLUMUfVoCEXBCtSA/06TfVd SaPb3ZSxPdaa+VuVRVf8ibcynBbymhRSZ4XDDoaTj6Fr4O86AD+awPrePykWr45GcwPU dor9UuJrmJ48Kjvjw366P8hriq0udZsuVHjho3r3ugxJ/g/CpWkXcLLpG1j2HK/GBPor /HOwCX4l3k/iQm13A2ukD3GVtiYooq0pM4bpL07GcWE0yUHzV+Huw4oYjeToWh5lardm XxFA== MIME-Version: 1.0 X-Received: by 10.42.201.78 with SMTP id ez14mr22495945icb.22.1422303110009; Mon, 26 Jan 2015 12:11:50 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Mon, 26 Jan 2015 12:11:49 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Jan 2015 12:11:49 -0800 X-Google-Sender-Auth: qbT8WRVU6Z0LUqXuZAJpWJOHfqM Message-ID: Subject: Re: Is anyone using the schedgraph.d script? From: Adrian Chadd To: freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Jan 2015 20:11:50 -0000 ... ignore it for now; I ran some other profiling and then when I tried schedgraph.d again, it started spitting out events for that CPU. I'll file a PR if I see it happen more often. :( -a On 26 January 2015 at 12:05, Adrian Chadd wrote: > Hi, > > I'm having problems with Ryan's schedgraph.d script > (people.freebsd.org/~rstone/dtrace/) > > It runs fine, but if a CPU core is 100% busy, I get zero scheduler > events logged from it. Said core is doing around 30,000 syscalls a > second, around 250,000 context switches and 125,000 interrupt sa > second - but whilst it's doing this, I get zero events from dtrace for > said CPU. > > Has anyone hit this kind of situation before? > > > > -a From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 03:01:53 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 54D36E6E; Tue, 27 Jan 2015 03:01:53 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCF64E2F; Tue, 27 Jan 2015 03:01:52 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id 10so10855663lbg.10; Mon, 26 Jan 2015 19:01:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KH+88kTKnBlWwe+9O8xH3mL0EcZ7XJ+nWTzWxkP94A4=; b=o1meekv/yC1us4RrKSPHI/vFGvv46YHr5duuZdBls94BsZwmBbyExxvJev+wJoY7vD jgV2vx3ZEpMTrQwZJ8DrHL/HRfdJ7OaGjim8wmRz9ZUxhAB5MohqTDhUhravW9ubasSz qAShPkN8bBSAoOOkyI+oKN6T9rchb+1H5oYLFjDEUvoVZUOodA+Zn3zzs23Gnk7+Vssg 4eE14aNNr83cjjQPrPxsmWj6XsEh5Xf7yZ25BJbBeT5rWJxmJjaOIxKQ8CPa6fM8hG8s ZWxr18WJ7W7Tj8QEE1XTuw/hZCkWPVUTwY+N8XmlUuy+UYiz9t4Pziut3WQry+cmyjvz Mb3Q== MIME-Version: 1.0 X-Received: by 10.152.191.165 with SMTP id gz5mr1454773lac.37.1422327710765; Mon, 26 Jan 2015 19:01:50 -0800 (PST) Received: by 10.114.78.131 with HTTP; Mon, 26 Jan 2015 19:01:50 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Jan 2015 22:01:50 -0500 Message-ID: Subject: Re: Is anyone using the schedgraph.d script? From: Ryan Stone To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 03:01:53 -0000 Hm, there was one bug in that script. I uploaded a fixed version. The fix was: - printf("%d %d KTRGRAPH group:\"thread\", id:\"%s/%s tid %d\", state:\"runq add\", attributes: prio:%d, linkedto:\"%s/%s tid %d\"\n", cpu, timestamp, args[0]->td_proc->p_comm, args[0]->td_name, args[0]->td_tid, args[0]->td_priority, curthread->td_proc->p_comm, curthread->td_name, args[0]->td_tid); + printf("%d %d KTRGRAPH group:\"thread\", id:\"%s/%s tid %d\", state:\"runq add\", attributes: prio:%d, linkedto:\"%s/%s tid %d\"\n", cpu, timestamp, args[0]->td_proc->p_comm, args[0]->td_name, args[0]->td_tid, args[0]->td_priority, curthread->td_proc->p_comm, curthread->td_name, curthread->td_tid); Note that the last printf argument used args[0] instead of curthread as intended. One other thing that I have noticed with the schedgraph data gathering is that unlike KTR, in dtrace every CPU gathers its data into a CPU-local buffer. This can mean that a CPU that sees a large number of scheduler events will roll over its ring buffer much more quickly than a lightly loaded CPU. This can lead to a confusing or misleading schedgraph output at the beginning of the time period. You can mitigate this problem by allowing dtrace to allocate a larger ring buffer with: #pragma D option bufsize=32m (You can potentially tune it even higher than that, but that's a good place to start) Finally, I've noticed that schedgraph seems to have problems auto-detecting the clock frequency, so I tend to forcifully specify 1GHz (dtrace always outputs time in units of ns, so this is always correct to do with dtrace-gather data) From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 05:22:31 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8571F589; Tue, 27 Jan 2015 05:22:31 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F1B5E06; Tue, 27 Jan 2015 05:22:31 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id b6so11168496lbj.11; Mon, 26 Jan 2015 21:22:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=KNZXOT/St4qZagbNNgrGIex6F3mOnlXw8ET0tpAgPXk=; b=yhBdmMA1QGnb+3REtx72YGybYA8cG0GbISsk8gUOnV/kavwEM7LXrR5MgD07kqgtWH 6z+4DtEjTRqhxjArXKenYbHlfx6E1ME7K7IX+kKRotApCZFhjU9xDtKgZFShMGuPsRuP Z4xYtoxFfah1YynHlYU+IFeT5xwNdVFrHrmaz3FvylGiHVnyO9v6xNyiEVltJbqvH4D4 wrgM7n27a1jEo0upluFLaLHcmTlY7bO+ofTtdw6vMTJVQoRLmPQsmOnBQ35evYTZMxt7 Y0d2zzFyVm2xO2X0hMLzWnE+QxUuKKVI56TElBfX8/XrqdWbZsgojc5l+bKVVThY8SZp At/w== X-Received: by 10.152.161.168 with SMTP id xt8mr1931331lab.35.1422336148896; Mon, 26 Jan 2015 21:22:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.12.6 with HTTP; Mon, 26 Jan 2015 21:21:58 -0800 (PST) From: Yue Chen Date: Tue, 27 Jan 2015 00:21:58 -0500 Message-ID: Subject: Will all kernel functions be loaded into memory, in the same address space with kernel modules? To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 05:22:31 -0000 My purpose is to modify kernel function instructions directly through memory at runtime. First I use "objdump -S kernel" to see the function names and their addresses. And then I use pointers to peek into the content at certain function address area (.text segment). However, their content is different from the result from "objdump -S kernel". I use a FreeBSD 10.1 kernel, which has no ASLR supported as I know. Is it because that the kernel function addresses are relocated? Or some kernel functions are not loaded into memory? Or is it not suitable to peek kernel ".text" content from a kernel module? I only "objdump -S" the built "kernel" with debug symbols, not ".ko" files. From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 06:36:37 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7A53991 for ; Tue, 27 Jan 2015 06:36:37 +0000 (UTC) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD9D7756 for ; Tue, 27 Jan 2015 06:36:37 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id tr6so13411857ieb.4 for ; Mon, 26 Jan 2015 22:36:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tF21zNQN4K2n1JmtbGkNUVdAGwJMVfP6rYCpHhQrfgo=; b=WutdBsWbUdOHEisWLUMpDLR/1Vw/8cYZovhV4BdYYAl+3UBfADZcp6Oj6r6cz2eWVa lGp1Vk4+dZsvJ1xBlRJnFFwRTGnjSW04M6C+iq/rUSEwMhPnO+WiYg7MYVWBaV4lSFaf 5JDSMHbYZJMGtiMTv/Ql0ICjmJ1WngS8nKkoHoNQ+UZMDatMQYWqyN3AzZe57zdufcgz cmN+4BwVrMFdEfZGSo/uBhP12Eef10EUSZ4g/ESkwuocQyvdEn8CeDYF8beU/MbeyqVy VKCgvpbgC+lT66Mzwb3NOeRI/gl8dq3485PKAKOtM2RKmgJ4AWtywyNjDVeVp48T5tBs /XeQ== MIME-Version: 1.0 X-Received: by 10.42.62.71 with SMTP id x7mr1038628ich.61.1422340596912; Mon, 26 Jan 2015 22:36:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Mon, 26 Jan 2015 22:36:36 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Jan 2015 22:36:36 -0800 X-Google-Sender-Auth: fn_ZlS76KGZwzqysR9Yx92U6wjU Message-ID: Subject: Re: Is anyone using the schedgraph.d script? From: Adrian Chadd To: Ryan Stone Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 06:36:38 -0000 On 26 January 2015 at 19:01, Ryan Stone wrote: > Hm, there was one bug in that script. I uploaded a fixed version. The fix was: > > - printf("%d %d KTRGRAPH group:\"thread\", id:\"%s/%s tid %d\", > state:\"runq add\", attributes: prio:%d, linkedto:\"%s/%s tid %d\"\n", > cpu, timestamp, args[0]->td_proc->p_comm, args[0]->td_name, > args[0]->td_tid, args[0]->td_priority, curthread->td_proc->p_comm, > curthread->td_name, args[0]->td_tid); > + printf("%d %d KTRGRAPH group:\"thread\", id:\"%s/%s tid %d\", > state:\"runq add\", attributes: prio:%d, linkedto:\"%s/%s tid %d\"\n", > cpu, timestamp, args[0]->td_proc->p_comm, args[0]->td_name, > args[0]->td_tid, args[0]->td_priority, curthread->td_proc->p_comm, > curthread->td_name, curthread->td_tid); > > Note that the last printf argument used args[0] instead of curthread > as intended. Cool! Thanks! > One other thing that I have noticed with the schedgraph data gathering > is that unlike KTR, in dtrace every CPU gathers its data into a > CPU-local buffer. This can mean that a CPU that sees a large number > of scheduler events will roll over its ring buffer much more quickly > than a lightly loaded CPU. This can lead to a confusing or misleading > schedgraph output at the beginning of the time period. You can > mitigate this problem by allowing dtrace to allocate a larger ring > buffer with: > > #pragma D option bufsize=32m > > (You can potentially tune it even higher than that, but that's a good > place to start) > > > Finally, I've noticed that schedgraph seems to have problems > auto-detecting the clock frequency, so I tend to forcifully specify > 1GHz (dtrace always outputs time in units of ns, so this is always > correct to do with dtrace-gather data) Good to know. Is there any reason why this isn't just checked into -HEAD and -10? -adrian From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 06:38:16 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D642DABE for ; Tue, 27 Jan 2015 06:38:16 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DDAD790 for ; Tue, 27 Jan 2015 06:38:16 +0000 (UTC) Received: (qmail 12983 invoked from network); 27 Jan 2015 06:39:14 -0000 Received: from c-71-57-141-247.hsd1.fl.comcast.net (HELO Todd) (AWilcox@Wilcox-Tech.com@71.57.141.247) by mail.foxkit.us with ESMTPA; 27 Jan 2015 06:39:14 -0000 From: "Andrew Wilcox" To: "'Ranjan1018 .'" <214748mv@gmail.com>, "'Adrian Chadd'" , "'freebsd-current'" References: In-Reply-To: Subject: RE: drm2 regression: backlight adjustment on ivybridge no longer works Date: Tue, 27 Jan 2015 00:38:16 -0600 Message-ID: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIkD3QRswOKHk1/aLD21PpFfsdgwgGR9mCRnB9I4GA= Content-Language: en-gb Cc: 'Konstantin Belousov' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 06:38:16 -0000 Ranjan1018 . sent: 26 January 2015 06:19: > 2015-01-24 23:25 GMT+01:00 Adrian Chadd : > > The backlight adjustment doesn't work on my ivybridge mobile laptop=20 > > (Lenovo X230) after the dri update. > > > I have the same issue on my Samsung Ativ 2 laptop. I have a Sandy Bridge laptop (Apple MacBook Pro 8,2) - HD 3000: vgapci0@pci0:0:2:0: class=3D0x030000 card=3D0x00db106b = chip=3D0x01268086 rev=3D0x09 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '2nd Generation Core Processor Family Integrated = Graphics Controller' class =3D display subclass =3D VGA It is running: FreeBSD pwyll.foxkit.us 11.0-CURRENT #1 r277781M: Mon = Jan 26 18:41:15 CST 2015 = root@pwyll.foxkit.us:/usr/obj/usr/src/sys/GENERIC amd64 I have no issues using acpi_video's sysctls = (hw.acpi.video.lcd0.brightness) to adjust backlight, though it does not = have good granularity. The stepping is about 7, so it goes as = 13%..20%..27%..35%..etc. > > The "intel_backlight" program from intel-gpu-tools" also no longer=20 > > changes the backlight value. This program works fine for me on both an older kernel (r277523) and = this kernel (r277781), after applying some patches to allow the library = to build on FreeBSD. It also has better granularity (the stepping is = 2-3). If there is anything I can do/run to aide in debugging why it works for = me but not others, let me know. Best, Andrew -- Andrew Wilcox, C/C++/Python developer, kernel hacker Blog: http://blog.foxkit.us/ WWW: http://foxkit.us/=20 GitHub: https://github.com/awilfox From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 13:14:30 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52D74967 for ; Tue, 27 Jan 2015 13:14:30 +0000 (UTC) Received: from mail-yh0-f47.google.com (mail-yh0-f47.google.com [209.85.213.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1682F9C1 for ; Tue, 27 Jan 2015 13:14:29 +0000 (UTC) Received: by mail-yh0-f47.google.com with SMTP id z6so6009050yhz.6 for ; Tue, 27 Jan 2015 05:14:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=skaMVlzvIWMqBrhRBd1g9lM09Oj3E/pHPRnm1u3FmOQ=; b=BK7BcvDJ9/2Ll04bRfUI063VxYEyi92lS0z32e+5zGEm6Nht6qyWb27OENpQZkL42h PtJgLDHIBle7Z7FHJghPHvqBvDy1sLUN7wKRmrLzG5VEd1iJ0DNfAz8D3BxDKjWb7TaP 0H1JN2q4zr0q4i8s86i2aDi6ea8uE3tYKvlCXI94vrDbaF4AhxanrOJ43R89NRXSicOY tXDq8iGLU88PKxOzsZ1h5L0ZKXc5gw9pXTDI1VFoHUqWHPNVI7a4rWXDCWB/z479adUU gA8CCdV4YVDeaMYe9lWJY1mxDJ/qLeHGe9IIww6uo3CtwEwd8+TMRD+Uo5J5xYq3L308 UfCQ== X-Gm-Message-State: ALoCoQn9GEiKIKpvCpyn6N8fcuapK0wQKWAr5qyyhP4PHheIdtQj7zYOlb9qcDMpnbtRg8/aEMHi MIME-Version: 1.0 X-Received: by 10.170.174.197 with SMTP id q188mr800822ykd.110.1422364468705; Tue, 27 Jan 2015 05:14:28 -0800 (PST) Received: by 10.170.46.81 with HTTP; Tue, 27 Jan 2015 05:14:28 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Jan 2015 14:14:28 +0100 Message-ID: Subject: Re: Will all kernel functions be loaded into memory, in the same address space with kernel modules? From: Oliver Pinter To: Yue Chen Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 13:14:30 -0000 On Tue, Jan 27, 2015 at 6:21 AM, Yue Chen wrote: > My purpose is to modify kernel function instructions directly through > memory at runtime. > > First I use "objdump -S kernel" to see the function names and their > addresses. And then I use pointers to peek into the content at certain > function address area (.text segment). However, their content is different > from the result from "objdump -S kernel". I use a FreeBSD 10.1 kernel, > which has no ASLR supported as I know. > > Is it because that the kernel function addresses are relocated? Or some > kernel functions are not loaded into memory? Or is it not suitable to peek > kernel ".text" content from a kernel module? > > I only "objdump -S" the built "kernel" with debug symbols, not ".ko" files. Take a look at this branch: https://github.com/HardenedBSD/hardenedBSD/tree/hardened/current/intel-smap > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://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 Jan 27 18:04:20 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95B6136D for ; Tue, 27 Jan 2015 18:04:20 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DBCEEA5 for ; Tue, 27 Jan 2015 18:04:19 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1YGAUl-001KcY-Md>; Tue, 27 Jan 2015 19:04:11 +0100 Received: from g229052033.adsl.alicedsl.de ([92.229.52.33] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1YGAUl-002k0J-Hl>; Tue, 27 Jan 2015 19:04:11 +0100 Date: Tue, 27 Jan 2015 19:04:06 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: CURRENT fails to build: make_hash.c : error: indirection requires pointer operand Message-ID: <20150127190406.0a07da35.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/7SUeUuPaAkqSziSHEl88rWh"; protocol="application/pgp-signature" X-Originating-IP: 92.229.52.33 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 18:04:20 -0000 --Sig_/7SUeUuPaAkqSziSHEl88rWh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Somehow one of my boxes got a wrecked system during an update cycle. Now th= e system rejects building world with the error shown below. I also tried to cleanup = everything (/usr/obj deleting) and performing a "make toolchain" - without success. Is there a way to repair this mess? [...] cc -o make_hash -O2 -pipe -O3 -pipe -O3 -I. -I/usr/obj/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/..= /ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDE= BUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -Qunused-arguments -I/usr/obj/usr/src/tmp/legacy/usr/include -DMAIN_PROGRAM /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurs= es/tinfo/make_hash.c /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/= ncurses/tinfo/make_hash.c:100:25: error: indirection requires pointer operand ('int' invalid) return (int) (s= um % HASHTABSIZE); ^~~~~~~~~~~ ./hashsize.h:6:23: note: expanded from macro 'HAS= HTABSIZE' #define HASHTABSIZE ( * 2) ^ ~ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_= hash.c:111:21: error: indirection requires pointer operand ('int' invalid) for (i =3D 0; i= < HASHTABSIZE; i++) { ^~~~~~~~~~~ ./hashsize.h:6:23: note: expanded from macro 'HASHTABSIZ= E' #define HASHTABSIZE ( * 2) ^ ~ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_= hash.c:114:31: error: expected expression for (i =3D 0; i < CAPTABSIZE; i++) { ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/mak= e_hash.c:125:77: error: expected expression printf("/* %d collisions out of %d entries */\n"= , collisions, CAPTABSIZE); ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_= hash.c:194:43: error: expected expression struct name_table_entry *name_table =3D typeCall= oc(struct ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include/nc_alloc.h:10= 7:59: note: expanded from macro 'typeCalloc' #define typeCalloc(type,elts) (type *)calloc((size_t)(elts),sizeof(type)) ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:196:51: error: indirection requires pointer operand ('int' invalid) HashValue *hash= _table =3D typeCalloc(HashValue, HASHTABSIZE); ^~~~~~~~~~~ ./hashsize.h:6:23: note: expanded from macro 'HASHTABSIZE' #define HASHTABSIZE ( * 2) ^ ~ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include/nc_alloc.h:10= 7:55: note: expanded from macro 'typeCalloc' #define typeCalloc(type,elts) (type *)calloc((size_t)(elts),sizeof(type)) ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:227:32: error: expected expression for (n =3D 0; (n < CAPTABSIZE) && fgets(buffer, = BUFSIZ, stdin);) { ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:268:28: error: expected expression for (n =3D 0; n < CAPTABSIZE; n++) { ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:283:28: error: expected expression for (n =3D 0; n < CAPTABSIZE; n++) { ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:299:28: error: expected expression for (n =3D 0; n < CAPTABSIZE; n++) { ^ /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_ha= sh.c:314:5: error: indirection requires pointer operand ('int' invalid) HASHTABSIZE + 1= ); ^~~~~~~~~~~ ./hashsize.h:6:23: note: expanded from macro 'HASHTABSIZE' --Sig_/7SUeUuPaAkqSziSHEl88rWh Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUx9MWAAoJEOgBcD7A/5N8msAIAOWcbgGaPNWFzbp0ArBmpwIb Z2HKV1DB8QET6SAa9ZU5pVAdNJWF9tXTyemuR6Slr/7BxCnrlBrSyxIIAhAiAsb1 cQYzvJIdfezL7eLbh6svg2itpTZHkhG5A7o/SyrQrM80VsV7wwZGR/bGmGCyrgPP C0mKUOsRkf6L/xvy3rmboNeaQgyqLnt6ocTzn8uFWTLVs4aby7krxC/DY8F3AE9Q HFa2sZijYXv7Y8gSUgzBAi7tIAsqHCGNBvw3kOUh0+JInly05rhM/UiPwuT7Uaut 0LSS5fMxRfYHw8eGy4pXTtCLj+NitWBbJpd/GMZy9Vt38GDMbwR+alhdI5HlRq0= =FMEq -----END PGP SIGNATURE----- --Sig_/7SUeUuPaAkqSziSHEl88rWh-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 18:43:40 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80C3CC2A; Tue, 27 Jan 2015 18:43:40 +0000 (UTC) Received: from lakerest.net (lakerest.net [162.235.35.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "lakerest.net", Issuer "Stewart" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C0973D5; Tue, 27 Jan 2015 18:43:39 +0000 (UTC) Received: from rrss-air.corp.netflix.com ([69.53.237.72]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id t0RIh7k9022957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Jan 2015 13:43:08 -0500 (EST) (envelope-from rrs@freebsd.org) From: Randall Stewart Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Callout lockups and spin-lock held to long panic.. Date: Tue, 27 Jan 2015 10:43:25 -0800 Message-Id: <8334666F-AE31-4298-A6D7-11453A22DF41@freebsd.org> To: freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\)) X-Mailer: Apple Mail (2.2070.4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 18:43:40 -0000 All: I just wanted to send a note to let folks know I have finally dug to the bottom of the crashes that Sean Bruno has been seeing and will = shortly have a fix committed for it. The problem was related to two callout_reset=E2=80=99s being run with = migration happening and that callout was executing (or waiting to execute). The twin callout resets would in the end each remove the entry from the linked list (twice) thus corrupting the linked list. The software code would thus run, holding the CC_lock spinning forever going through the linked list.. causing the crash. I was able to reproduce this in a branch at netflix here so I can prove that the fix I have actually fixes the issue. It will be a couple more days of proving things out, followed by = hopefully getting interested reviewer=E2=80=99s to review the patch.. and then = from there I can commit it to head .. Best wishes R ------------------------------ Randall Stewart 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 20:21:58 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F0D92FC for ; Tue, 27 Jan 2015 20:21:58 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5F738F for ; Tue, 27 Jan 2015 20:21:58 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 2589FBAC for ; Tue, 27 Jan 2015 20:21:58 +0000 (UTC) Date: Tue, 27 Jan 2015 20:21:57 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build became unstable: FreeBSD_HEAD-tests2 #604 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 20:21:58 -0000 See From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 20:31:12 2015 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 287B774B for ; Tue, 27 Jan 2015 20:31:12 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AA042627 for ; Tue, 27 Jan 2015 20:31:10 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.9/8.14.9) with ESMTP id t0RKV3vr017216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 27 Jan 2015 23:31:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.9/8.14.9/Submit) id t0RKV3WP017215 for current@FreeBSD.org; Tue, 27 Jan 2015 23:31:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 27 Jan 2015 23:31:03 +0300 From: Gleb Smirnoff To: current@FreeBSD.org Subject: panic in softdep_slowdown() Message-ID: <20150127203103.GZ15484@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 20:31:12 -0000 Got this in bhyve VM on boot up and mount: Starting file system checks: /dev/vtbd0p3: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/vtbd0p3: clean, 1617700 free (222876 frags, 174353 blocks, 5.9% fragmentation) Fatal trap 18: integer divide fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0xffffffff80895d63 stack pointer = 0x28:0xfffffe001eb5f220 frame pointer = 0x28:0xfffffe001eb5f2b0 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 = 49 (mount) [ thread pid 49 tid 100045 ] Stopped at softdep_slowdown+0x1d3: idivl %ecx,%eax db> bt Tracing pid 49 tid 100045 td 0xfffff800026ee000 softdep_slowdown() at softdep_slowdown+0x1d3/frame 0xfffffe001eb5f2b0 ffs_truncate() at ffs_truncate+0x1be/frame 0xfffffe001eb5f640 ufs_setattr() at ufs_setattr+0x4e5/frame 0xfffffe001eb5f6a0 VOP_SETATTR_APV() at VOP_SETATTR_APV+0x22a/frame 0xfffffe001eb5f710 VOP_SETATTR() at VOP_SETATTR+0x45/frame 0xfffffe001eb5f760 vn_truncate() at vn_truncate+0x196/frame 0xfffffe001eb5f870 fo_truncate() at fo_truncate+0x41/frame 0xfffffe001eb5f8b0 kern_ftruncate() at kern_ftruncate+0x16d/frame 0xfffffe001eb5f920 sys_ftruncate() at sys_ftruncate+0x27/frame 0xfffffe001eb5f940 syscallenter() at syscallenter+0x46e/frame 0xfffffe001eb5f9b0 amd64_syscall() at amd64_syscall+0x1f/frame 0xfffffe001eb5fab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe001eb5fab0 --- syscall (480, FreeBSD ELF64, sys_ftruncate), rip = 0x800b511fa, rsp = 0x7fffffffe998, rbp = 0x7fffffffeb90 --- db> call doadump Dumping 60 out of 495 MB:..27%..54%..80% Dump complete = 0 db> I've got the core file. -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 21:31:49 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05440F9A; Tue, 27 Jan 2015 21:31:49 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77F5CDC9; Tue, 27 Jan 2015 21:31:48 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id f15so15444173lbj.0; Tue, 27 Jan 2015 13:31:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=l1bgkP4cITFZpydXL9SMn1BsCXDRsuEyJgF6faoKLPI=; b=ZsUh9LkjroTSAsFx97zbRzngYWC6XUrj0fe95Pshls18tMa97hRh6dWb87qrTtGeR0 cfSS+JCK6tupMWt6NNkWVs88MPRfYwAwMIQrve0iv7uTEf5oBYRn/Tdit9U3Cot2py6U lzEFgHBFy2/3m7IfUa04awiHVJbsl+0LKjyLZUXtfQuKpNzBzVHnVzVhCghBfQSy8ias plrMC2uPsL1U4pZazfUOL/bzcqRZ3Adckp+6iegiz0f/DG2ZBQcBkCwxa/GxYepxy8Fx pcYqOwEAuHM3yIbr+8iMTaN6bXj/Fv/0JMkAFLGATqhpai5Tn5Ed9lXRLOen+/AKIMy+ Xn8g== MIME-Version: 1.0 X-Received: by 10.112.125.41 with SMTP id mn9mr4238169lbb.80.1422394306609; Tue, 27 Jan 2015 13:31:46 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.129.3 with HTTP; Tue, 27 Jan 2015 13:31:46 -0800 (PST) In-Reply-To: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> References: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> Date: Tue, 27 Jan 2015 13:31:46 -0800 X-Google-Sender-Auth: jFz4Xd_TezbLi__q67pbPA8Yu-c Message-ID: Subject: Re: Jenkins build became unstable: FreeBSD_HEAD-tests2 #604 From: Craig Rodrigues To: Stefan Esser Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current Current , "jenkins-admin@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 21:31:49 -0000 On Tue, Jan 27, 2015 at 12:21 PM, wrote: > See > > One of the expr tests seems to have broken after this change: https://lists.freebsd.org/pipermail/svn-src-all/2015-January/098238.html Can you take a look? -- Craig From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:35:46 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3A3B205; Tue, 27 Jan 2015 22:35:46 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 899116B4; Tue, 27 Jan 2015 22:35:46 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id rd18so18155571iec.3; Tue, 27 Jan 2015 14:35:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WPE5iN3/behwP5k1NXKmJSkzz/voe2KUFn7jCJ/f+AM=; b=EAcKTGPIlTKuLNGsR2MMXS+gLHgdNBJwe7m5Ga2WsT87LItDBEAHWJ/uWzywrc96vK lP6J5P9aAmdujTPBJyKaqBcP827bx4fVQkQmlbDk1RKjHNtblY5Eas1e6uYoPTBb07ik iiMAgIL0FoIpshI8wW7/00In26rEzu3EflwigSX/NzAX4lAq+zPERbPUSvLgJWkqgtgT inhDEXqc6w+Y1xOYkRaF2f7mbAtuXQyBKfDaKju/PpJR/u5nLaIOTNIABE8g8qVPPK/y e34hSgokm5sMuOTLJVJgE4RJ2NsnFAGN3tMyxthYyzGxyvLjWbVISbMnD+ZlygzHF/P0 TCKw== MIME-Version: 1.0 X-Received: by 10.50.137.99 with SMTP id qh3mr255979igb.7.1422398145906; Tue, 27 Jan 2015 14:35:45 -0800 (PST) Received: by 10.50.182.233 with HTTP; Tue, 27 Jan 2015 14:35:45 -0800 (PST) In-Reply-To: References: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> Date: Tue, 27 Jan 2015 14:35:45 -0800 Message-ID: Subject: Re: Jenkins build became unstable: FreeBSD_HEAD-tests2 #604 From: NGie Cooper To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 Cc: "jenkins-admin@freebsd.org" , freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Jan 2015 22:35:46 -0000 On Tue, Jan 27, 2015 at 1:31 PM, Craig Rodrigues wrote: > On Tue, Jan 27, 2015 at 12:21 PM, wrote: > >> See >> >> > One of the expr tests seems to have broken after this change: > https://lists.freebsd.org/pipermail/svn-src-all/2015-January/098238.html > > Can you take a look? Stefan enhanced bin/expr to do better overflow detection, so r277357 can be reverted. This can be verified like so: cd bin/expr/tests make obj; make depend; make all; sudo make install (cd /usr/tests/bin/expr; kyua test) Thanks! From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 00:08:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E2CFD33 for ; Wed, 28 Jan 2015 00:08:01 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id F0EC06D for ; Wed, 28 Jan 2015 00:08:00 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 19B4BEE for ; Wed, 28 Jan 2015 00:08:00 +0000 (UTC) Date: Wed, 28 Jan 2015 00:08:00 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <1773849856.11.1422403680918.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> References: <922840668.10.1422390117941.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #605 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 00:08:01 -0000 See From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 02:23:15 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B749E0B for ; Wed, 28 Jan 2015 02:23:15 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 5A00F1B7 for ; Wed, 28 Jan 2015 02:23:15 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A4E8F4E8 for ; Wed, 28 Jan 2015 02:23:15 +0000 (UTC) Date: Wed, 28 Jan 2015 02:23:15 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <497363132.12.1422411795615.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1773849856.11.1422403680918.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1773849856.11.1422403680918.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #606 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 02:23:15 -0000 See From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 05:42:06 2015 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBF227EA; Wed, 28 Jan 2015 05:42:06 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 96DD1B6E; Wed, 28 Jan 2015 05:42:03 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-228-137.lns20.per1.internode.on.net [121.45.228.137]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t0S5fxhj006893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 27 Jan 2015 21:42:01 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54C876A1.20105@freebsd.org> Date: Wed, 28 Jan 2015 13:41:53 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "current@freebsd.org" , sjg@freebsd.org Subject: bmake and .USEBEFORE Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 05:42:07 -0000 If I try the following: bar: .USE @echo @ = $(@) all: bar @echo here is all I always get "bar is up to date" Does anyone know how this is supposed to work? From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 05:42:23 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5E2E901; Wed, 28 Jan 2015 05:42:22 +0000 (UTC) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73487B77; Wed, 28 Jan 2015 05:42:22 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id fb4so9393294wid.2; Tue, 27 Jan 2015 21:42:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zPHNWJV7rCgIuy0KsM+yjYHugOD3CzxMCipSCiZWURQ=; b=xu/0Q/IYCtqIWnPXEIJ0Vv6umyNnx6DaHiJpB4FdNDPxcWYAfQmgkvwQkFZve3dpxW Bz1ign3cUBNoXCTgQXfKBQN+iFYEAUQHAqkg9SdVLkX87EiDyFi7Z1KIl2y/Rxf/WQuq UEczSyrNl9gAIkhVbbGBMNUXnPgb7WqnvIQV5Ek7rmJWSWAN2fiADd71yac8UcTbcCoB +74ei8+xPH9lnf4B4mnh4JmVrBr+CLW8WDlHJM9eNtlMV0EsO2uDi4bu+ai2p2vgj+eW OxdFr3Lkgu8YRi0JOieNMHjWWnilGwH5qhf049suP/d+94qPIa+EMBS9xJvt9A1d8NLx 6VKg== MIME-Version: 1.0 X-Received: by 10.194.158.5 with SMTP id wq5mr3332759wjb.85.1422423740864; Tue, 27 Jan 2015 21:42:20 -0800 (PST) Received: by 10.217.64.10 with HTTP; Tue, 27 Jan 2015 21:42:20 -0800 (PST) In-Reply-To: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> Date: Wed, 28 Jan 2015 06:42:20 +0100 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: "Ranjan1018 ." <214748mv@gmail.com> To: Andrew Wilcox Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Adrian Chadd , freebsd-current , Konstantin Belousov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 05:42:23 -0000 2015-01-27 7:38 GMT+01:00 Andrew Wilcox : > Ranjan1018 . sent: 26 January 2015 06:19: > > 2015-01-24 23:25 GMT+01:00 Adrian Chadd : > > > The backlight adjustment doesn't work on my ivybridge mobile laptop > > > (Lenovo X230) after the dri update. > > > > > I have the same issue on my Samsung Ativ 2 laptop. > > I have a Sandy Bridge laptop (Apple MacBook Pro 8,2) - HD 3000: > > vgapci0@pci0:0:2:0: class=0x030000 card=0x00db106b chip=0x01268086 > rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = '2nd Generation Core Processor Family Integrated Graphics > Controller' > class = display > subclass = VGA > > It is running: FreeBSD pwyll.foxkit.us 11.0-CURRENT #1 r277781M: Mon Jan > 26 18:41:15 CST 2015 root@pwyll.foxkit.us:/usr/obj/usr/src/sys/GENERIC > amd64 > > I have no issues using acpi_video's sysctls > (hw.acpi.video.lcd0.brightness) to adjust backlight, though it does not > have good granularity. The stepping is about 7, so it goes as > 13%..20%..27%..35%..etc. > > > > The "intel_backlight" program from intel-gpu-tools" also no longer > > > changes the backlight value. > > This program works fine for me on both an older kernel (r277523) and this > kernel (r277781), after applying some patches to allow the library to build > on FreeBSD. It also has better granularity (the stepping is 2-3). > > If there is anything I can do/run to aide in debugging why it works for me > but not others, let me know. > > Best, > Andrew > -- > Andrew Wilcox, C/C++/Python developer, kernel hacker > Blog: http://blog.foxkit.us/ WWW: http://foxkit.us/ > GitHub: https://github.com/awilfox > > Hi, my Samsung laptop has an Intel IvyBridge: vgapci0@pci0:0:2:0: class=0x030000 card=0xc708144d chip=0x01668086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '3rd Gen Core processor Graphics Controller' class = display subclass = VGA The regression was introduced in r277487. The backlight adjustment works in FreeBSD 11.0-CURRENT r277395, r277486 but not in r277487, r277534 and r277639. Regards, Maurizio From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 05:51:03 2015 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F5B2A89; Wed, 28 Jan 2015 05:51:03 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 50559BCA; Wed, 28 Jan 2015 05:51:02 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-228-137.lns20.per1.internode.on.net [121.45.228.137]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t0S5oxQ2006947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 27 Jan 2015 21:51:01 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54C878BD.1090805@freebsd.org> Date: Wed, 28 Jan 2015 13:50:53 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "current@freebsd.org" , sjg@freebsd.org Subject: Re: bmake and .USEBEFORE References: <54C876A1.20105@freebsd.org> In-Reply-To: <54C876A1.20105@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 05:51:03 -0000 On 1/28/15 1:41 PM, Julian Elischer wrote: > If I try the following: > > bar: .USE > @echo @ = $(@) > all: bar > @echo here is all oops the failing example should be .USEBEFORE.. I pasted the wrong clip. > > > I always get "bar is up to date" > > > Does anyone know how this is supposed to work? > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 06:38:46 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 20E51FF8 for ; Wed, 28 Jan 2015 06:38:46 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B84FAFD5 for ; Wed, 28 Jan 2015 06:38:44 +0000 (UTC) Received: (qmail 2396 invoked from network); 28 Jan 2015 06:39:41 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 28 Jan 2015 06:39:41 -0000 Message-ID: <54C883E7.4000300@interlinked.me> Date: Wed, 28 Jan 2015 00:38:31 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Questions on adding backlight support for the i915 driver Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 06:38:46 -0000 Hello, I want to add backlight support to the i915 driver in FreeBSD. It seems that two magic addresses are read and wrote from to change the backlight itself. It supports rather fine-level granularity all the way down to zero. Right now I use a hacked-up userland program that reads from/writes to these addresses, which is far from an ideal solution. I am interested in this because the acpi_video(4) driver does not support my backlight on my Dell Inspiron 15 3521 (not terribly suprising, on Linux I needed a special Dell-specific driver, and I'm not sure even that really used ACPI, I never really checked). My questions are really twofold: 1) How can this be exposed appropriately? I would prefer this be exposed generally so upower could grok it. As far as I can tell upower uses hw.acpi.video.lcd0 to control backlight. I am not sure that upower is doing the "right" thing here, though. 2) Where would the code go for this? The dri2 driver seems the most "logical" place, but maybe it belongs in X and exposed via a program? Or something else entirely that I'm not thinking of? I have experience developing PCI drivers and doing other PCI related doodads, and some kernel development experience, as well as general C experience, but I'm not by any means an expert on the matter. Cheers, Elizabeth Myers From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 07:06:02 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 12CFE4CA for ; Wed, 28 Jan 2015 07:06:02 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A53FA34A for ; Wed, 28 Jan 2015 07:06:00 +0000 (UTC) Received: (qmail 13763 invoked from network); 28 Jan 2015 07:07:04 -0000 Received: from c-71-57-141-247.hsd1.fl.comcast.net (HELO Todd) (AWilcox@Wilcox-Tech.com@71.57.141.247) by mail.foxkit.us with ESMTPA; 28 Jan 2015 07:07:04 -0000 From: "Andrew Wilcox" To: "'Ranjan1018 .'" <214748mv@gmail.com> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> In-Reply-To: Subject: RE: drm2 regression: backlight adjustment on ivybridge no longer works Date: Wed, 28 Jan 2015 01:06:00 -0600 Message-ID: <009301d03ac8$dfa09e20$9ee1da60$@Wilcox-Tech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIkD3QRswOKHk1/aLD21PpFfsdgwgGR9mCRAv4GIYoBQ/0CWZv+0Ldg Content-Language: en-gb Cc: 'freebsd-current' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 07:06:02 -0000 Ranjan1018 . sent: 27 January 2015 23:42: > my Samsung laptop has an Intel IvyBridge: [snip] > The regression was introduced in r277487. > The backlight adjustment works in FreeBSD 11.0-CURRENT r277395, = r277486 > but not in r277487, r277534 and r277639. Hrm. That is interesting. A few questions I have then. - What happens if you set drm.i915.invert_brightness to -1 in kenv(1) or = /boot/loader.conf? - What happens if you set drm.i915.invert_brightness to 1 in kenv(1) or = /boot/loader.conf? - What version of graphics/libdrm do you have installed? Did you = rebuild it after installing the new kernel? (This shouldn't be = necessary, but I am trying to gather all details.) Let's start there and see if we can pin down a cause. Best, Andrew -- Andrew Wilcox, C/C++/Python developer, kernel hacker Blog: http://blog.foxkit.us/ WWW: http://foxkit.us/ GitHub: https://github.com/awilfox From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 07:23:28 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F3D87B5D for ; Wed, 28 Jan 2015 07:23:27 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 904FB787 for ; Wed, 28 Jan 2015 07:23:26 +0000 (UTC) Received: (qmail 21058 invoked from network); 28 Jan 2015 07:24:30 -0000 Received: from c-71-57-141-247.hsd1.fl.comcast.net (HELO Todd) (AWilcox@Wilcox-Tech.com@71.57.141.247) by mail.foxkit.us with ESMTPA; 28 Jan 2015 07:24:30 -0000 From: "Andrew Wilcox" To: "'Ranjan1018 .'" <214748mv@gmail.com> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> In-Reply-To: Subject: RE: drm2 regression: backlight adjustment on ivybridge no longer works Date: Wed, 28 Jan 2015 01:23:26 -0600 Message-ID: <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIkD3QRswOKHk1/aLD21PpFfsdgwgGR9mCRAv4GIYoBQ/0CWZv+1SDQ Content-Language: en-gb Cc: 'freebsd-current' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 07:23:28 -0000 Ranjan1018 . sent: 27 January 2015 23:42: > The regression was introduced in r277487. Looking closer at this revision, I believe I may see the issue. Most of = the new tunables introduced in dev/drm2/i915/i915_drv.c are = uninitialised and thus probably contain junk. It likely works for me = because the firmware of my laptop 0s memory on EFI boot. I have uploaded a diff here that I believe may fix this. Please test = and let me know: http://foxkit.us/FreeBSD/i915-uninitialised-var-fix.diff Best, Andrew -- Andrew Wilcox, C/C++/Python developer, kernel hacker Blog: http://blog.foxkit.us/ WWW: http://foxkit.us/ GitHub: https://github.com/awilfox From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 08:06:21 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 209279EA for ; Wed, 28 Jan 2015 08:06:21 +0000 (UTC) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7AE9BB5 for ; Wed, 28 Jan 2015 08:06:20 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id bj1so24061376pad.1 for ; Wed, 28 Jan 2015 00:06:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=i33DcGQL2etQHFnDbDaNonn1x4RoM44lcOH7+/Z0fw4=; b=pqfw55unDsqz9HMRb7bAlubBVgxk80k+Yyu/foruS7T1CVHH78Dt5olt4mtXcHCaks 8uLCCM7w3F+tomHstQMXfAOYrwruJzkPGfHb0AwbuYPt6sDsmG/f0blzR8YpS6+SZLpU meuU2JkWprrJf1RlmE8sSoGRJkdbd3PAY2/ZZE0n9vQecxeXxRmQlcfojDuA7f+5Gynn +CPEuF2QKHRoCXAvzx3OeaOV1o51gkzOurLSfyOHZR1041PLP3PjtUFeXky3JO/ASxhK zD5mnA6xLgQYsPP+X3WEAkzaTA/pChJ3dGc6C8isvxFiYb3toA9wTUTF5UUJnU338P1z 2Z/A== X-Received: by 10.67.8.2 with SMTP id dg2mr3729235pad.15.1422432380541; Wed, 28 Jan 2015 00:06:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.50.70 with HTTP; Wed, 28 Jan 2015 00:06:00 -0800 (PST) From: Eric Camachat Date: Wed, 28 Jan 2015 00:06:00 -0800 Message-ID: Subject: sd card on hp laptop doesn't work anymore on 11-current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 08:06:21 -0000 My SD card slot was working before, but it no longer works. looks like the mmc driver for hp laptop is gone. $ dmesg|grep -iE 'sdhc|mmc' sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated it was a mmc* there. $ pciconf -lv ... none1@pci0:35:0:0: class=0x0c0010 card=0x161c103c chip=0x2380197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'IEEE 1394 Host Controller' class = serial bus subclass = FireWire none2@pci0:35:0:1: class=0x088000 card=0x161c103c chip=0x2392197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'SD/MMC Host Controller' class = base peripheral sdhci_pci0@pci0:35:0:2: class=0x080501 card=0x161c103c chip=0x2391197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'Standard SD Host Controller' class = base peripheral subclass = SD host controller ... no driver attached to mmc Thanks, Eric From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 08:29:37 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6EFC9E48 for ; Wed, 28 Jan 2015 08:29:37 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 5D67FDA7 for ; Wed, 28 Jan 2015 08:29:37 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id B9470C6C for ; Wed, 28 Jan 2015 08:29:37 +0000 (UTC) Date: Wed, 28 Jan 2015 08:29:37 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <1536581234.13.1422433777201.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <497363132.12.1422411795615.JavaMail.jenkins@jenkins-9.freebsd.org> References: <497363132.12.1422411795615.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #607 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 08:29:37 -0000 See From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 08:46:02 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 56D87ABF for ; Wed, 28 Jan 2015 08:46:02 +0000 (UTC) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 179A7FDD for ; Wed, 28 Jan 2015 08:46:02 +0000 (UTC) Received: by mail-ig0-f182.google.com with SMTP id r10so9770838igi.3 for ; Wed, 28 Jan 2015 00:46:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=ugODhpq5uoseea2uOkuiZp+CjBChspKL+w3n0UcKJhI=; b=ySNwPRqQhHwltC7z1Ft4Ajz9uBCQv2uuqfzgyjWiq30rvTrhwOnH4H7w8zmf+AqGZs IpgaZI8x1Udni2o9AC5jjSHDwIXIZ5zMv9BKkWhZMQxOUGBfdx5DlK9ngv0TiK8H/w2Q H3LorD1kBxUf6FIK9S6xzhw3KjtEZHHq2gqsgTRPsOS+bBaLyVpm+tPcPEZYk85uIl8t /D4oZUx/lsNN+mzsrq7X7MPm9HVjnLQ/NDQEYjY1Zi1bwCtTplP4X5HFDsmkLieztQtA KJ0eNkoUWfgfVZK8NUMowlPQ4DVFJ3u9VqsfUwMA2TKz1VMH/QSlJlvjHq4wuImbnBFp 221w== MIME-Version: 1.0 X-Received: by 10.107.155.197 with SMTP id d188mr2472597ioe.29.1422434760343; Wed, 28 Jan 2015 00:46:00 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Wed, 28 Jan 2015 00:46:00 -0800 (PST) In-Reply-To: <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> Date: Wed, 28 Jan 2015 00:46:00 -0800 X-Google-Sender-Auth: uGPBJd03xgazF2EJxDrwFhR3dtc Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: Adrian Chadd To: Andrew Wilcox Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "Ranjan1018 ." <214748mv@gmail.com>, freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 08:46:02 -0000 Hi! Good catch! But nope, didn't fix it. -adrian On 27 January 2015 at 23:23, Andrew Wilcox wrote: > Ranjan1018 . sent: 27 January 2015 23:42: >> The regression was introduced in r277487. > > Looking closer at this revision, I believe I may see the issue. Most of = the new tunables introduced in dev/drm2/i915/i915_drv.c are uninitialised a= nd thus probably contain junk. It likely works for me because the firmware= of my laptop 0s memory on EFI boot. > > I have uploaded a diff here that I believe may fix this. Please test and= let me know: > > http://foxkit.us/FreeBSD/i915-uninitialised-var-fix.diff > > Best, > Andrew > > -- > Andrew Wilcox, C/C++/Python developer, kernel hacker > Blog: http://blog.foxkit.us/ WWW: http://foxkit.us/ > GitHub: https://github.com/awilfox > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 09:11:20 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1041B3D6; Wed, 28 Jan 2015 09:11:20 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C703C2E0; Wed, 28 Jan 2015 09:11:19 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id rl12so20493753iec.11; Wed, 28 Jan 2015 01:11:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Kz0yJt4BxUjL2fo8sVspENWK8TkyI/kG9SOCJRgGGQw=; b=kUtpQggXuBhjCcOw6mrScvuONGps2AN1oyQi7k4vMdbm6lSmWGiQTq17IPC0g3KdJH B7ZX2GTalSNHfxPfw7XPTA7GV/oV1bH5Zvwhl1KKWXcm1TUjgWtMKMdy6fIrZmk4BJVF 0QGBPiLX/WAgGmkJPRtavUs6PxM2YlB3za7kScvC5CghExjwTpe6gkIHWeoFoiZDKJ0w XjFNzmEPtqykD0/0RBg/ILzenl9o/mW3V+w4IFiyXR7eOVgPfsjgFfGc0qvypnO4Arzw 6A3lXpEVO/FiL7qTY7hbhJVv6r7gNKHTzuxVr1fbXh1+ecTw1aCzIQiDtrwHOZXMOhnA 0Piw== MIME-Version: 1.0 X-Received: by 10.42.62.71 with SMTP id x7mr2077704ich.61.1422436279139; Wed, 28 Jan 2015 01:11:19 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Wed, 28 Jan 2015 01:11:19 -0800 (PST) In-Reply-To: References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> Date: Wed, 28 Jan 2015 01:11:19 -0800 X-Google-Sender-Auth: JF7os7MLMMSHj9yK7B1AzREzfi4 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: Adrian Chadd To: Andrew Wilcox , Konstantin Belousov Content-Type: text/plain; charset=UTF-8 Cc: "Ranjan1018 ." <214748mv@gmail.com>, freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 09:11:20 -0000 ugh, so because i can't sleep, I read the Linux i915 history for backlight changes. Turns out if I disable bit 30 in ivb_pch_pwm_override() to register BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings still don't, but I'll worry about that later. Bit 30 in the linux drm code is: #define BLM_PCH_OVERRIDE_ENABLE (1 << 30) The linux dri code doesn't set that for ivybridge - only for broadwell. (also, the linux driver has POSTING_READ() which I'm guessing is to ensure things made it out to the device and have been flushed before doing another IO operation.) I have my (via sysctl) panel backlight control working again. -adrian From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 09:20:13 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 417D3691; Wed, 28 Jan 2015 09:20:13 +0000 (UTC) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 022093E6; Wed, 28 Jan 2015 09:20:13 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id rd18so20507241iec.7; Wed, 28 Jan 2015 01:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YWbfTQqDwG+po4S2GdTmlxSxAp3kCDMUatx9vQHfjRc=; b=aQFCsbznjZM9NDEtKPFCtZpae9LVsTcNaDcIL5mXHzRx+sRYGp7fOT6jDDuwZBUeVh /mtUVPdd9niVqq4c8v30EDqkMOrmGx4HmrCporyVZ7jGjVNv4/Y7GFnKs/T8MkqEDmZK GSriIEF+k4p3kh/BtvD5Dc12X3uC4nKaM4VnexLc5+FRNjfz8JEYcrIdg7Wje9vz+ZdO KPQn+KQXQEgusfg0taGi/r4Dsh18+N1mCMvlnVJlYArvymWoRp7ZeKzTN3+8HvyPLk3W jCWnBKBRjQHHxXAfNC8/kRdRz9JL5vDQY1rCsL1HUE7r+sYw6JbTWoIVWdzO5kwuHmIC K9fQ== MIME-Version: 1.0 X-Received: by 10.50.164.227 with SMTP id yt3mr2420600igb.32.1422436812407; Wed, 28 Jan 2015 01:20:12 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Wed, 28 Jan 2015 01:20:12 -0800 (PST) In-Reply-To: References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> Date: Wed, 28 Jan 2015 01:20:12 -0800 X-Google-Sender-Auth: CTg8tvfMWzEksrE67rYKgojYDs8 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: Adrian Chadd To: Andrew Wilcox , Konstantin Belousov Content-Type: text/plain; charset=UTF-8 Cc: "Ranjan1018 ." <214748mv@gmail.com>, freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 09:20:13 -0000 and the commit from linux: commit 7aa1e7f06d6ea1bce3b27630d50769d13da28b1a Author: Daniel Vetter Date: Wed Jun 27 16:43:36 2012 +0200 Revert "drm/i915: allow PCH PWM override on IVB" This reverts commit f82cfb6bcda164ef3a66b8c3fc549b1f9bdd09ad. This breaks the backlight controls on my IVB asus zenbook with an eDP panel. I guess the right fix would be to read this bit and use either the pch or the cpu register to frob the backlight values. But that is stuff for -next. Cc: Jesse Barnes Signed-Off-by: Daniel Vetter On 28 January 2015 at 01:11, Adrian Chadd wrote: > ugh, so because i can't sleep, I read the Linux i915 history for > backlight changes. > > Turns out if I disable bit 30 in ivb_pch_pwm_override() to register > BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings > still don't, but I'll worry about that later. > > Bit 30 in the linux drm code is: > > #define BLM_PCH_OVERRIDE_ENABLE (1 << 30) > > The linux dri code doesn't set that for ivybridge - only for broadwell. > > (also, the linux driver has POSTING_READ() which I'm guessing is to > ensure things made it out to the device and have been flushed before > doing another IO operation.) > > I have my (via sysctl) panel backlight control working again. > > > > -adrian From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 09:53:09 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7CA9D7C for ; Wed, 28 Jan 2015 09:53:08 +0000 (UTC) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B21379BE for ; Wed, 28 Jan 2015 09:53:08 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id rp18so20634630iec.9 for ; Wed, 28 Jan 2015 01:53:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=/Rs2TkL9cHEb50uaQSBjyl29v4HzbMIJ+4imVPSJYQc=; b=bBwXjL+qWnY6v2f5YpzMOuVnFiT+p/tpGDw64FnWjA4KLctyjSTcrTO6kvi3ko2EAW 1gPjmEPr+huXTo2mA5dGBY40oUKIZr9j3VCPWgn69gq7165zLm6g68zLTeHOlyymgdzc nxODIN9CrI0AwWlwvlUdJWPVi6++BmQPvtX4uQJgSBq9yRXSDGrvuu/6l/3SnQ3SDF7O 51NjSXeYSUwfnaqFeYvJ22v3t0FovfNHqX2a52iG4E4RbHio54KvqH86vHNy8aNUIe4L sBv2FJ85zXB5sGR3BvRrFKcGmS3hUQtlJRbFWgp8maL2wEBXxDYXhSVR8WR+KY7iuei5 Fs/Q== X-Gm-Message-State: ALoCoQl3Jznvuffi0EmdIAlqfyOBCZgEUXkGocRIVlWQoDXeiHagEo8goE1omoowtmfPxFul4BM33ZSB4krGIRIYvBu+7/E5gKxilulKHYTLmU3zpd825WQBvA1k+Fxsm5tPGtJ1MuIk X-Received: by 10.107.167.135 with SMTP id q129mr2754353ioe.23.1422438787373; Wed, 28 Jan 2015 01:53:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Wed, 28 Jan 2015 01:52:52 -0800 (PST) From: "Lundberg, Johannes" Date: Wed, 28 Jan 2015 18:52:52 +0900 Message-ID: Subject: System-On-Module To: "freebsd-arm@freebsd.org" , "freebsd-mobile@freebsd.org" , FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 09:53:09 -0000 SGkNCg0KT2YgYWxsIHRoZSBsb3cgcG93ZXIsIGhpZ2gtc3BlYyBzeXN0ZW0vY29tcHV0ZXItb24t bW9kdWxlcyBvdXQgdGhlcmUgd2hpY2gNCmhhdmUgYmVzdCBzdXBwb3J0IGZvciBGcmVlQlNEPw0K DQpNRU4NClZhcmlzY2l0ZQ0KVGVjaG5vbG9naWMgc3lzdGVtDQpBZGxpbmsNCmV0Yy4NCg0KV2hh dCBJIGFtIGxvb2tpbmcgZm9yIGlzIGEgc3lzdGVtIHdpdGggcm91Z2hseSB0aGlzIHNwZWNzDQpB Uk0gb3IgeDg2LCA2NGJpdCBpZiBwb3NzaWJsZS4NCjItNCBjb3Jlcw0KMS41LTIuMCBHSHoNCjIg R0IgUkFNDQp+MTYgR0IgU3RvcmFnZQ0KVVNCIDMuMA0KUENCIHNpemUgYWJvdXQgb25lIHRvIHR3 byBjcmVkaXQgY2FyZHMuDQoNCkkgd2lzaCB0byBtaW5pbWl6ZSB0aGUgYW1vdW50IG9mIHBvcnRp bmcgbmVlZGVkIHNvIEkgYW0gdmVyeSBncmF0ZWZ1bCBpZg0Kc29tZW9uZSBoYXMgZ29vZCBpbnNp Z2h0cyBpbiB0aGlzIGFyZWEuIEFuZCBvZiBjb3Vyc2UsIGl0IHdvdWxkIGhlbHAgYSBsb3QNCmlm IGl0IHdhcyBhIG1hbnVmYWN0dXJlciB3aG8gaXMgd2lsbGluZyB0byBwcm92aWRlIGRhdGFzaGVl dHMgdG8gbWFrZQ0KcG9ydGluZyBwb3NzaWJsZS4uDQoNClRoYW5rcyENCi0tDQpKb2hhbm5lcyBM dW5kYmVyZw0KCi0tIAo9LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09 LT0tPS09LT0tPS0K56eY5a+G5L+d5oyB44Gr44Gk44GE44Gm77ya44GT44Gu6Zu75a2Q44Oh44O8 44Or44Gv44CB5ZCN5a6b5Lq644Gr6YCB5L+h44GX44Gf44KC44Gu44Gn44GC44KK44CB56eY5Yy/ 54m55qip44Gu5a++6LGh44Go44Gq44KL5oOF5aCx44KS5ZCr44KT44Gn44GE44G+44GZ44CCCuOC guOBl+OAgeWQjeWum+S6uuS7peWkluOBruaWueOBjOWPl+S/oeOBleOCjOOBn+WgtOWQiOOAgeOB k+OBruODoeODvOODq+OBruegtOajhOOAgeOBiuOCiOOBs+OBk+OBruODoeODvOODq+OBq+mWouOB meOCi+S4gOWIh+OBrumWi+ekuuOAgQropIflhpnjgIHphY3luIPjgIHjgZ3jga7ku5bjga7liKnn lKjjgIHjgb7jgZ/jga/oqJjovInlhoXlrrnjgavln7rjgaXjgY/jgYTjgYvjgarjgovooYzli5Xj goLjgZXjgozjgarjgYTjgojjgYbjgYrpoZjjgYTnlLPjgZfkuIrjgZLjgb7jgZnjgIIKLS0tCkNP TkZJREVOVElBTElUWSBOT1RFOiBUaGUgaW5mb3JtYXRpb24gaW4gdGhpcyBlbWFpbCBpcyBjb25m aWRlbnRpYWwKYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIGFkZHJlc3NlZS4KRGlzY2xvc3Vy ZSwgY29weWluZywgZGlzdHJpYnV0aW9uIG9yIGFueSBvdGhlciBhY3Rpb24gb2YgdXNlIG9mIHRo aXMKZW1haWwgYnkgcGVyc29uIG90aGVyIHRoYW4gaW50ZW5kZWQgcmVjaXBpZW50LCBpcyBwcm9o aWJpdGVkLgpJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGFuZCBoYXZlIHJl Y2VpdmVkIHRoaXMgZW1haWwgaW4KZXJyb3IsIHBsZWFzZSBkZXN0cm95IHRoZSBvcmlnaW5hbCBt ZXNzYWdlLgo= From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 10:48:48 2015 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84FE3C71; Wed, 28 Jan 2015 10:48:48 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 EB394F14; Wed, 28 Jan 2015 10:48:47 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0SAmgdE025401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2015 12:48:43 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0SAmgdE025401 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0SAmg2p025400; Wed, 28 Jan 2015 12:48:42 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Jan 2015 12:48:42 +0200 From: Konstantin Belousov To: Gleb Smirnoff Subject: Re: panic in softdep_slowdown() Message-ID: <20150128104842.GL42409@kib.kiev.ua> References: <20150127203103.GZ15484@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150127203103.GZ15484@glebius.int.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 10:48:48 -0000 On Tue, Jan 27, 2015 at 11:31:03PM +0300, Gleb Smirnoff wrote: > Got this in bhyve VM on boot up and mount: > > Starting file system checks: > /dev/vtbd0p3: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/vtbd0p3: clean, 1617700 free (222876 frags, 174353 blocks, 5.9% fragmentation) > > > Fatal trap 18: integer divide fault while in kernel mode > cpuid = 1; apic id = 01 > instruction pointer = 0x20:0xffffffff80895d63 > stack pointer = 0x28:0xfffffe001eb5f220 > frame pointer = 0x28:0xfffffe001eb5f2b0 > 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 = 49 (mount) > [ thread pid 49 tid 100045 ] > Stopped at softdep_slowdown+0x1d3: idivl %ecx,%eax > db> bt > Tracing pid 49 tid 100045 td 0xfffff800026ee000 > softdep_slowdown() at softdep_slowdown+0x1d3/frame 0xfffffe001eb5f2b0 > ffs_truncate() at ffs_truncate+0x1be/frame 0xfffffe001eb5f640 > ufs_setattr() at ufs_setattr+0x4e5/frame 0xfffffe001eb5f6a0 > VOP_SETATTR_APV() at VOP_SETATTR_APV+0x22a/frame 0xfffffe001eb5f710 > VOP_SETATTR() at VOP_SETATTR+0x45/frame 0xfffffe001eb5f760 > vn_truncate() at vn_truncate+0x196/frame 0xfffffe001eb5f870 > fo_truncate() at fo_truncate+0x41/frame 0xfffffe001eb5f8b0 > kern_ftruncate() at kern_ftruncate+0x16d/frame 0xfffffe001eb5f920 > sys_ftruncate() at sys_ftruncate+0x27/frame 0xfffffe001eb5f940 > syscallenter() at syscallenter+0x46e/frame 0xfffffe001eb5f9b0 > amd64_syscall() at amd64_syscall+0x1f/frame 0xfffffe001eb5fab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe001eb5fab0 > --- syscall (480, FreeBSD ELF64, sys_ftruncate), rip = 0x800b511fa, rsp = 0x7fffffffe998, rbp = 0x7fffffffeb90 --- > db> call doadump > Dumping 60 out of 495 MB:..27%..54%..80% > Dump complete > = 0 > db> > > I've got the core file. At least the source line for the panic is needed. Also, print out the value of stat_flush_threads. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 11:22:41 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7040559 for ; Wed, 28 Jan 2015 11:22:41 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id A500638D for ; Wed, 28 Jan 2015 11:22:41 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 2C97E197 for ; Wed, 28 Jan 2015 11:22:42 +0000 (UTC) Date: Wed, 28 Jan 2015 11:22:42 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <1684404649.14.1422444162061.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1536581234.13.1422433777201.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1536581234.13.1422433777201.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is still unstable: FreeBSD_HEAD-tests2 #608 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 11:22:41 -0000 See From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 14:28:51 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F21F73EE for ; Wed, 28 Jan 2015 14:28:51 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id DCBE4ADE for ; Wed, 28 Jan 2015 14:28:51 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 22571573 for ; Wed, 28 Jan 2015 14:28:51 +0000 (UTC) Date: Wed, 28 Jan 2015 14:28:51 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <2051619358.15.1422455331860.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1684404649.14.1422444162061.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1684404649.14.1422444162061.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to stable : FreeBSD_HEAD-tests2 #609 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 14:28:52 -0000 See From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:22:35 2015 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FDF9CDD for ; Wed, 28 Jan 2015 18:22:35 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BFB78FF for ; Wed, 28 Jan 2015 18:22:34 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.9/8.14.9) with ESMTP id t0SIMUsw022596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Jan 2015 21:22:30 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.9/8.14.9/Submit) id t0SIMUKu022595; Wed, 28 Jan 2015 21:22:30 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 28 Jan 2015 21:22:30 +0300 From: Gleb Smirnoff To: Konstantin Belousov Subject: Re: panic in softdep_slowdown() Message-ID: <20150128182230.GB15484@glebius.int.ru> References: <20150127203103.GZ15484@glebius.int.ru> <20150128104842.GL42409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150128104842.GL42409@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 18:22:35 -0000 On Wed, Jan 28, 2015 at 12:48:42PM +0200, Konstantin Belousov wrote: K> > Stopped at softdep_slowdown+0x1d3: idivl %ecx,%eax K> > db> bt K> > Tracing pid 49 tid 100045 td 0xfffff800026ee000 K> > softdep_slowdown() at softdep_slowdown+0x1d3/frame 0xfffffe001eb5f2b0 K> > ffs_truncate() at ffs_truncate+0x1be/frame 0xfffffe001eb5f640 K> > ufs_setattr() at ufs_setattr+0x4e5/frame 0xfffffe001eb5f6a0 K> > VOP_SETATTR_APV() at VOP_SETATTR_APV+0x22a/frame 0xfffffe001eb5f710 K> > VOP_SETATTR() at VOP_SETATTR+0x45/frame 0xfffffe001eb5f760 K> > vn_truncate() at vn_truncate+0x196/frame 0xfffffe001eb5f870 K> > fo_truncate() at fo_truncate+0x41/frame 0xfffffe001eb5f8b0 K> > kern_ftruncate() at kern_ftruncate+0x16d/frame 0xfffffe001eb5f920 K> > sys_ftruncate() at sys_ftruncate+0x27/frame 0xfffffe001eb5f940 K> > syscallenter() at syscallenter+0x46e/frame 0xfffffe001eb5f9b0 K> > amd64_syscall() at amd64_syscall+0x1f/frame 0xfffffe001eb5fab0 K> > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe001eb5fab0 K> > --- syscall (480, FreeBSD ELF64, sys_ftruncate), rip = 0x800b511fa, rsp = 0x7fffffffe998, rbp = 0x7fffffffeb90 --- K> > db> call doadump K> > Dumping 60 out of 495 MB:..27%..54%..80% K> > Dump complete K> > = 0 K> > db> K> > K> > I've got the core file. K> K> At least the source line for the panic is needed. K> Also, print out the value of stat_flush_threads. (kgdb) fr 11 #11 0xffffffff80895d63 in softdep_slowdown (vp=0xfffff800028011d8) at /usr/src/ifnet/sys/ufs/ffs/ffs_softdep.c:13055 13055 if (dep_current[D_DIRREM] < max_softdeps_hard / 2 && (kgdb) p dep_current $1 = {1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0} (kgdb) p max_softdeps_hard $2 = 153357 (kgdb) p *ump $4 = {um_mountp = 0xfffff80002707330, um_dev = 0xfffff800026cbc00, um_cp = 0xfffff80002717480, um_bo = 0xfffff8000271edb8, um_devvp = 0xfffff8000271ece8, um_fstype = 2, um_fs = 0xfffff8000273b000, um_extattr = {uepm_lock = {lock_object = {lo_name = 0x0, lo_flags = 0, lo_data = 0, lo_witness = 0x0}, sx_lock = 0}, uepm_list = { lh_first = 0x0}, uepm_ucred = 0x0, uepm_flags = 0}, um_nindir = 4096, um_bptrtodb = 3, um_seqinc = 8, um_lock = {lock_object = { lo_name = 0xffffffff80a53d30 "FFS", lo_flags = 16973824, lo_data = 0, lo_witness = 0xfffffe00008e3400}, mtx_lock = 4}, um_fsckpid = 0, um_softdep = 0xfffff800027a0200, um_quotas = {0x0, 0x0}, um_cred = {0x0, 0x0}, um_btime = {0, 0}, um_itime = {0, 0}, um_qflags = "\000", um_savedmaxfilesize = 0, um_candelete = 0, um_writesuspended = 0, um_balloc = 0xffffffff8086eb90 , um_blkatoff = 0xffffffff808a8170 , um_truncate = 0xffffffff808717b0 , um_update = 0xffffffff80871090 , um_valloc = 0xffffffff808660c0 , um_vfree = 0xffffffff808677b0 , um_ifree = 0xffffffff808af420 , um_rdonly = 0xffffffff808741c0 , um_snapgone = 0xffffffff80879b70 } (kgdb) p stat_flush_threads $5 = 1 I can't see where integer divide fault can happen with stat_flush_threads=1 :( -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:01:35 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EA0A94B; Wed, 28 Jan 2015 19:01:35 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BA3BCCF7; Wed, 28 Jan 2015 19:01:34 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t0SIWZcN028386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 28 Jan 2015 19:32:35 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t0SIWWgS022671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2015 19:32:33 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t0SIWWPx073210; Wed, 28 Jan 2015 19:32:32 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t0SIWWBu073209; Wed, 28 Jan 2015 19:32:32 +0100 (CET) (envelope-from ticso) Date: Wed, 28 Jan 2015 19:32:32 +0100 From: Bernd Walter To: "Lundberg, Johannes" Subject: Re: System-On-Module Message-ID: <20150128183231.GI58886@cicely7.cicely.de> Reply-To: ticso@cicely.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:01:35 -0000 On Wed, Jan 28, 2015 at 06:52:52PM +0900, Lundberg, Johannes wrote: > Hi > > Of all the low power, high-spec system/computer-on-modules out there which > have best support for FreeBSD? > > MEN > Variscite > Technologic system > Adlink > etc. > > What I am looking for is a system with roughly this specs > ARM or x86, 64bit if possible. > 2-4 cores > 1.5-2.0 GHz > 2 GB RAM > ~16 GB Storage > USB 3.0 > PCB size about one to two credit cards. In that range I would go for a Wandboard. They are 1, 2 or 4 core iMX6 32bit with 512M, 1G or 2G RAM. The 4 core has SATA, which to my knowledge we don't support yet. They come with 2 useable SD-card slots - one on the module and one on a carrier board. Clock rate is 1GHz only IIRC and they only have high speed USB, although the newest carrier boards have some super speed wiring for future modules. TechNexion, the originator of that module system also has some x86 boards - some may fit your requirements, but those are at a higher price and bigger form factor. Tech Nexion also has iMX6 boards similar to the wandboard with different featuresets, but also at a higher price. > I wish to minimize the amount of porting needed so I am very grateful if > someone has good insights in this area. And of course, it would help a lot > if it was a manufacturer who is willing to provide datasheets to make > porting possible.. Freescale is producting the iMX6 and they supply a hughe PDF for them. Also the wandboard schematics are public available. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:04:54 2015 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14CE1B10; Wed, 28 Jan 2015 19:04:54 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 91D15D28; Wed, 28 Jan 2015 19:04:53 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0SJ4gaI046723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2015 21:04:42 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0SJ4gaI046723 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0SJ4gaE046722; Wed, 28 Jan 2015 21:04:42 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Jan 2015 21:04:42 +0200 From: Konstantin Belousov To: Gleb Smirnoff Subject: Re: panic in softdep_slowdown() Message-ID: <20150128190441.GO42409@kib.kiev.ua> References: <20150127203103.GZ15484@glebius.int.ru> <20150128104842.GL42409@kib.kiev.ua> <20150128182230.GB15484@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150128182230.GB15484@glebius.int.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:04:54 -0000 On Wed, Jan 28, 2015 at 09:22:30PM +0300, Gleb Smirnoff wrote: > On Wed, Jan 28, 2015 at 12:48:42PM +0200, Konstantin Belousov wrote: > K> > Stopped at softdep_slowdown+0x1d3: idivl %ecx,%eax > K> > db> bt > K> > Tracing pid 49 tid 100045 td 0xfffff800026ee000 > K> > softdep_slowdown() at softdep_slowdown+0x1d3/frame 0xfffffe001eb5f2b0 > K> > ffs_truncate() at ffs_truncate+0x1be/frame 0xfffffe001eb5f640 > K> > ufs_setattr() at ufs_setattr+0x4e5/frame 0xfffffe001eb5f6a0 > K> > VOP_SETATTR_APV() at VOP_SETATTR_APV+0x22a/frame 0xfffffe001eb5f710 > K> > VOP_SETATTR() at VOP_SETATTR+0x45/frame 0xfffffe001eb5f760 > K> > vn_truncate() at vn_truncate+0x196/frame 0xfffffe001eb5f870 > K> > fo_truncate() at fo_truncate+0x41/frame 0xfffffe001eb5f8b0 > K> > kern_ftruncate() at kern_ftruncate+0x16d/frame 0xfffffe001eb5f920 > K> > sys_ftruncate() at sys_ftruncate+0x27/frame 0xfffffe001eb5f940 > K> > syscallenter() at syscallenter+0x46e/frame 0xfffffe001eb5f9b0 > K> > amd64_syscall() at amd64_syscall+0x1f/frame 0xfffffe001eb5fab0 > K> > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe001eb5fab0 > K> > --- syscall (480, FreeBSD ELF64, sys_ftruncate), rip = 0x800b511fa, rsp = 0x7fffffffe998, rbp = 0x7fffffffeb90 --- > K> > db> call doadump > K> > Dumping 60 out of 495 MB:..27%..54%..80% > K> > Dump complete > K> > = 0 > K> > db> > K> > > K> > I've got the core file. > K> > K> At least the source line for the panic is needed. > K> Also, print out the value of stat_flush_threads. > > (kgdb) fr 11 > #11 0xffffffff80895d63 in softdep_slowdown (vp=0xfffff800028011d8) > at /usr/src/ifnet/sys/ufs/ffs/ffs_softdep.c:13055 > 13055 if (dep_current[D_DIRREM] < max_softdeps_hard / 2 && > (kgdb) p dep_current > $1 = {1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 1, > 0, 0, 0, 0} > (kgdb) p max_softdeps_hard > $2 = 153357 > (kgdb) p *ump > $4 = {um_mountp = 0xfffff80002707330, um_dev = 0xfffff800026cbc00, > um_cp = 0xfffff80002717480, um_bo = 0xfffff8000271edb8, > um_devvp = 0xfffff8000271ece8, um_fstype = 2, um_fs = 0xfffff8000273b000, > um_extattr = {uepm_lock = {lock_object = {lo_name = 0x0, lo_flags = 0, > lo_data = 0, lo_witness = 0x0}, sx_lock = 0}, uepm_list = { > lh_first = 0x0}, uepm_ucred = 0x0, uepm_flags = 0}, um_nindir = 4096, > um_bptrtodb = 3, um_seqinc = 8, um_lock = {lock_object = { > lo_name = 0xffffffff80a53d30 "FFS", lo_flags = 16973824, lo_data = 0, > lo_witness = 0xfffffe00008e3400}, mtx_lock = 4}, um_fsckpid = 0, > um_softdep = 0xfffff800027a0200, um_quotas = {0x0, 0x0}, um_cred = {0x0, > 0x0}, um_btime = {0, 0}, um_itime = {0, 0}, um_qflags = "\000", > um_savedmaxfilesize = 0, um_candelete = 0, um_writesuspended = 0, > um_balloc = 0xffffffff8086eb90 , > um_blkatoff = 0xffffffff808a8170 , > um_truncate = 0xffffffff808717b0 , > um_update = 0xffffffff80871090 , > um_valloc = 0xffffffff808660c0 , > um_vfree = 0xffffffff808677b0 , > um_ifree = 0xffffffff808af420 , > um_rdonly = 0xffffffff808741c0 , > um_snapgone = 0xffffffff80879b70 } > (kgdb) p stat_flush_threads > $5 = 1 > > I can't see where integer divide fault can happen with stat_flush_threads=1 :( Look at the exact asm instruction which faulted, also look at the registers content. It might be hypervisor bug, after all. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:10:29 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5183EE5; Wed, 28 Jan 2015 19:10:28 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65B3BD80; Wed, 28 Jan 2015 19:10:28 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id u14so20396557lbd.2; Wed, 28 Jan 2015 11:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eLRCncbjmn+VK/YtmSbahm5kVruXZyszq1uTIMVd3wc=; b=sJopDEYhUTMjNNsryoAxChstapkw0QFGg8LuT+JnMpC0iCs9STISuPeVtsLIoK+34c ro7B6tX47CLsP3cPX/GXp9JRdsaoXYROESQAJphsOjJb+DA23t4Xq2u//DAxCRUrsjBy rZxr7SDlVwCP7kzie9MWG5Z+qsKq3z66fmC2s13X1Qh+o2SGt4gvrzJdV0vlIOQ7IrtX YNLNiyjugiVlUL1Pgen/rTfEp4eo+cP/IU3YaOVlPlo2wUNp5B4Dw+VexMtownYmzkJn JUhfWr1kA6U76ubIZuZwIb/1dPBB4etpckoOZShcDT6/+bn0oCk99D7Ribn1ZgQ3xfDv KhzQ== MIME-Version: 1.0 X-Received: by 10.152.37.165 with SMTP id z5mr10120566laj.88.1422472226201; Wed, 28 Jan 2015 11:10:26 -0800 (PST) Received: by 10.25.198.131 with HTTP; Wed, 28 Jan 2015 11:10:26 -0800 (PST) In-Reply-To: References: Date: Wed, 28 Jan 2015 20:10:26 +0100 Message-ID: Subject: Re: System-On-Module From: Andreas Nilsson To: "Lundberg, Johannes" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:10:29 -0000 On Wed, Jan 28, 2015 at 10:52 AM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Hi > > Of all the low power, high-spec system/computer-on-modules out there which > have best support for FreeBSD? > > MEN > Variscite > Technologic system > Adlink > etc. > > What I am looking for is a system with roughly this specs > ARM or x86, 64bit if possible. > 2-4 cores > 1.5-2.0 GHz > 2 GB RAM > ~16 GB Storage > USB 3.0 > PCB size about one to two credit cards. > > I wish to minimize the amount of porting needed so I am very grateful if > someone has good insights in this area. And of course, it would help a lot > if it was a manufacturer who is willing to provide datasheets to make > porting possible.. > > Thanks! > -- > Johannes Lundberg > > Something like http://www.fit-pc.com/web/products/specifications/fitlet-models-specifications/ perhaps? Though I don't think it is available yet, so I don't know if it is supported in FreeBSD. Best regards Andreas From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:27:39 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9829DAB4; Wed, 28 Jan 2015 19:27:39 +0000 (UTC) Received: from smtp6.ore.mailhop.org (smtp6.ore.mailhop.org [54.149.35.133]) (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 77559FA7; Wed, 28 Jan 2015 19:27:39 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by smtp6.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YGYH4-0003wH-2d; Wed, 28 Jan 2015 19:27:38 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t0SJRVKY027010; Wed, 28 Jan 2015 12:27:31 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+8Y4mxWzyFMRy+35ix9/KC Message-ID: <1422473251.15718.70.camel@freebsd.org> Subject: Re: System-On-Module From: Ian Lepore To: ticso@cicely.de Date: Wed, 28 Jan 2015 12:27:31 -0700 In-Reply-To: <20150128183231.GI58886@cicely7.cicely.de> References: <20150128183231.GI58886@cicely7.cicely.de> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "Lundberg, Johannes" , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:27:39 -0000 On Wed, 2015-01-28 at 19:32 +0100, Bernd Walter wrote: > On Wed, Jan 28, 2015 at 06:52:52PM +0900, Lundberg, Johannes wrote: > > Hi > > > > Of all the low power, high-spec system/computer-on-modules out there which > > have best support for FreeBSD? > > > > MEN > > Variscite > > Technologic system > > Adlink > > etc. > > > > What I am looking for is a system with roughly this specs > > ARM or x86, 64bit if possible. > > 2-4 cores > > 1.5-2.0 GHz > > 2 GB RAM > > ~16 GB Storage > > USB 3.0 > > PCB size about one to two credit cards. > > In that range I would go for a Wandboard. > They are 1, 2 or 4 core iMX6 32bit with 512M, 1G or 2G RAM. > The 4 core has SATA, which to my knowledge we don't support yet. > They come with 2 useable SD-card slots - one on the module and one > on a carrier board. > Clock rate is 1GHz only IIRC and they only have high speed USB, although > the newest carrier boards have some super speed wiring for future modules. > > TechNexion, the originator of that module system also has some > x86 boards - some may fit your requirements, but those are at > a higher price and bigger form factor. > Tech Nexion also has iMX6 boards similar to the wandboard with > different featuresets, but also at a higher price. You do get more for that higher price with the Technexion EDM modules, namely 1.2ghz chips instead of 1.0, and parts that are industrial and/or automotive temperature-rated rather than consumer grade. On the other hand, you generally can't buy Technexion modules one at a time. Last time I checked they were minimum order 10 pieces even from resellers like Mouser and Digikey. Another small-board imx6 possibility is the Hummingboard from SolidRun. I now have freebsd running on a SolidRun Cubox-i4, so I expect no large drama in getting it working on other SolidRun imx6 products. Gonzo ordered a Hummingboard recently, so we should know for sure some time soon. -- Ian From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:33:20 2015 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DD6BE65 for ; Wed, 28 Jan 2015 19:33:20 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 80DD8F1 for ; Wed, 28 Jan 2015 19:33:18 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.9/8.14.9) with ESMTP id t0SJXF9k022963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Jan 2015 22:33:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.9/8.14.9/Submit) id t0SJXFo3022962; Wed, 28 Jan 2015 22:33:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 28 Jan 2015 22:33:15 +0300 From: Gleb Smirnoff To: Konstantin Belousov Subject: Re: panic in softdep_slowdown() Message-ID: <20150128193315.GC15484@glebius.int.ru> References: <20150127203103.GZ15484@glebius.int.ru> <20150128104842.GL42409@kib.kiev.ua> <20150128182230.GB15484@glebius.int.ru> <20150128190441.GO42409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150128190441.GO42409@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:33:20 -0000 On Wed, Jan 28, 2015 at 09:04:42PM +0200, Konstantin Belousov wrote: K> > I can't see where integer divide fault can happen with stat_flush_threads=1 :( K> K> Look at the exact asm instruction which faulted, also look at the registers K> content. K> K> It might be hypervisor bug, after all. Yes, for me it looks like it. %edx should be one as well as -0x44(%rbp). 0xffffffff80895d43 : mov -0x20(%rbp),%ecx 0xffffffff80895d46 : mov %ecx,%edx 0xffffffff80895d48 : shr $0x1f,%edx 0xffffffff80895d4b : add %edx,%ecx 0xffffffff80895d4d : sar %ecx 0xffffffff80895d4f : mov 0xffffffff80ee24c8,%edx 0xffffffff80895d56 : mov %rax,-0x40(%rbp) 0xffffffff80895d5a : mov %ecx,%eax 0xffffffff80895d5c : mov %edx,-0x44(%rbp) 0xffffffff80895d5f : cltd 0xffffffff80895d60 : mov -0x44(%rbp),%ecx 0xffffffff80895d63 : idiv %ecx (kgdb) p &stat_flush_threads $5 = (int *) 0xffffffff80ee24c8 (kgdb) info registers rax 0x12b86 76678 rbx 0x4 4 rcx 0x0 0 rdx 0x0 0 rsi 0x3e8 1000 rdi 0x99 153 rbp 0xfffffe001eb5f2b0 0xfffffe001eb5f2b0 ... (kgdb) p *(int *)($rbp - 0x44) $4 = 0 (kgdb) p *(int *)($rbp - 0x40) $8 = 0 (kgdb) p &max_softdeps_hard $11 = (int *) 0xfffffe001eb5f290 (kgdb) p (int *)($rbp - 0x20) $12 = (int *) 0xfffffe001eb5f290 (kgdb) p max_softdeps_hard $10 = 153357 -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:54:47 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2684CC42; Wed, 28 Jan 2015 19:54:47 +0000 (UTC) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD43838B; Wed, 28 Jan 2015 19:54:46 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id x12so22596900wgg.4; Wed, 28 Jan 2015 11:54:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IYmR3rQw/jhoTIGV+D8BrpIyfbwB5nzkSH4Pbd81vUY=; b=yNOZwHZPxtzpl8DRIanzhAYhOfy/afXdWhGxsgFUFvjOeuPqwVm9BsfjVIcqVTuUOQ bqfB0dw7fePWYJ7TU1lHeQVIwu0MmQbXkqSRUxFmZTMSve52UiotVTgcEBpN0PwlJO2z 5djZfu7fn8peJbeo2E5OFSndFYaoW0fwA2QDX16SU87qfVQhxZ1H35jpBnIL6eSmPNzF mpkym8RfCe+KqpXgBy0cv42REe+78YKNOMiSpLYd7fvoXzUk8R2iVAzJqHPFYdeElYCo rO5ejwbsp6rB9hQxIZrWITMaiQsbsdvrAl3P964dg95CccXJqzZc6hwBA4hHqP1J1ThG RLnw== MIME-Version: 1.0 X-Received: by 10.194.189.77 with SMTP id gg13mr10856718wjc.81.1422474884993; Wed, 28 Jan 2015 11:54:44 -0800 (PST) Received: by 10.27.5.207 with HTTP; Wed, 28 Jan 2015 11:54:44 -0800 (PST) In-Reply-To: <20150128193315.GC15484@glebius.int.ru> References: <20150127203103.GZ15484@glebius.int.ru> <20150128104842.GL42409@kib.kiev.ua> <20150128182230.GB15484@glebius.int.ru> <20150128190441.GO42409@kib.kiev.ua> <20150128193315.GC15484@glebius.int.ru> Date: Wed, 28 Jan 2015 11:54:44 -0800 Message-ID: Subject: Re: panic in softdep_slowdown() From: Neel Natu To: Gleb Smirnoff Content-Type: text/plain; charset=UTF-8 Cc: Konstantin Belousov , "current@freebsd.org" , Peter Grehan X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 19:54:47 -0000 Hi Gleb, On Wed, Jan 28, 2015 at 11:33 AM, Gleb Smirnoff wrote: > On Wed, Jan 28, 2015 at 09:04:42PM +0200, Konstantin Belousov wrote: > K> > I can't see where integer divide fault can happen with stat_flush_threads=1 :( > K> > K> Look at the exact asm instruction which faulted, also look at the registers > K> content. > K> > K> It might be hypervisor bug, after all. > > Yes, for me it looks like it. %edx should be one as well as -0x44(%rbp). > > 0xffffffff80895d43 : mov -0x20(%rbp),%ecx > 0xffffffff80895d46 : mov %ecx,%edx > 0xffffffff80895d48 : shr $0x1f,%edx > 0xffffffff80895d4b : add %edx,%ecx > 0xffffffff80895d4d : sar %ecx > 0xffffffff80895d4f : mov 0xffffffff80ee24c8,%edx > 0xffffffff80895d56 : mov %rax,-0x40(%rbp) > 0xffffffff80895d5a : mov %ecx,%eax > 0xffffffff80895d5c : mov %edx,-0x44(%rbp) > 0xffffffff80895d5f : cltd > 0xffffffff80895d60 : mov -0x44(%rbp),%ecx > 0xffffffff80895d63 : idiv %ecx > > (kgdb) p &stat_flush_threads > $5 = (int *) 0xffffffff80ee24c8 > (kgdb) info registers > rax 0x12b86 76678 > rbx 0x4 4 > rcx 0x0 0 > rdx 0x0 0 > rsi 0x3e8 1000 > rdi 0x99 153 > rbp 0xfffffe001eb5f2b0 0xfffffe001eb5f2b0 > ... > (kgdb) p *(int *)($rbp - 0x44) > $4 = 0 > (kgdb) p *(int *)($rbp - 0x40) > $8 = 0 > (kgdb) p &max_softdeps_hard > $11 = (int *) 0xfffffe001eb5f290 > (kgdb) p (int *)($rbp - 0x20) > $12 = (int *) 0xfffffe001eb5f290 > (kgdb) p max_softdeps_hard > $10 = 153357 > Can you upload the core file and the kernel someplace that I can access? best Neel > -- > Totus tuus, Glebius. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:15:11 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C456517; Wed, 28 Jan 2015 20:15:11 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ED584856; Wed, 28 Jan 2015 20:15:10 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t0SKEiQt029420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 28 Jan 2015 21:14:45 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t0SKEgAC023493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2015 21:14:42 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t0SKEgKX073792; Wed, 28 Jan 2015 21:14:42 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t0SKEef1073791; Wed, 28 Jan 2015 21:14:40 +0100 (CET) (envelope-from ticso) Date: Wed, 28 Jan 2015 21:14:40 +0100 From: Bernd Walter To: Ian Lepore Subject: Re: System-On-Module Message-ID: <20150128201440.GA73589@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1422473251.15718.70.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" , "Lundberg, Johannes" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 20:15:11 -0000 On Wed, Jan 28, 2015 at 12:27:31PM -0700, Ian Lepore wrote: > On Wed, 2015-01-28 at 19:32 +0100, Bernd Walter wrote: > > On Wed, Jan 28, 2015 at 06:52:52PM +0900, Lundberg, Johannes wrote: > > > Hi > > > > > > Of all the low power, high-spec system/computer-on-modules out there which > > > have best support for FreeBSD? > > > > > > MEN > > > Variscite > > > Technologic system > > > Adlink > > > etc. > > > > > > What I am looking for is a system with roughly this specs > > > ARM or x86, 64bit if possible. > > > 2-4 cores > > > 1.5-2.0 GHz > > > 2 GB RAM > > > ~16 GB Storage > > > USB 3.0 > > > PCB size about one to two credit cards. > > > > In that range I would go for a Wandboard. > > They are 1, 2 or 4 core iMX6 32bit with 512M, 1G or 2G RAM. > > The 4 core has SATA, which to my knowledge we don't support yet. > > They come with 2 useable SD-card slots - one on the module and one > > on a carrier board. > > Clock rate is 1GHz only IIRC and they only have high speed USB, although > > the newest carrier boards have some super speed wiring for future modules. > > > > TechNexion, the originator of that module system also has some > > x86 boards - some may fit your requirements, but those are at > > a higher price and bigger form factor. > > Tech Nexion also has iMX6 boards similar to the wandboard with > > different featuresets, but also at a higher price. > > You do get more for that higher price with the Technexion EDM modules, > namely 1.2ghz chips instead of 1.0, and parts that are industrial and/or > automotive temperature-rated rather than consumer grade. On the other > hand, you generally can't buy Technexion modules one at a time. Last > time I checked they were minimum order 10 pieces even from resellers > like Mouser and Digikey. Temperature rating - that can easily justify the higher price. > Another small-board imx6 possibility is the Hummingboard from SolidRun. > I now have freebsd running on a SolidRun Cubox-i4, so I expect no large > drama in getting it working on other SolidRun imx6 products. Gonzo > ordered a Hummingboard recently, so we should know for sure some time > soon. To my knowledge they come in 3 different sizes. I own the biggest two versions of them. Completely forgot that the Hummingboard uses modules as well and the modules are even very small. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:15:31 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09FAACCF; Wed, 28 Jan 2015 21:15:31 +0000 (UTC) Received: from smtpout7.timeweb.ru (smtpout7.timeweb.ru [92.53.117.21]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B006FFBF; Wed, 28 Jan 2015 21:15:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=g0fU6g7W+ldemdSCtp4FUf6Jq1ZppAxlBmpHgQn/2XE=; b=Gllw7WIp0zk7tp6DRXVvyKk0R2UDzm+WevLonhxO4ENRKmQxnQ5O0VmnrGnL/sXJyM/nW0PjnwfDUtCghC74LOTaZzQ9DLY6/aaO1YsKxV1W0Qe5ZQ/aK6ye33KLS2cHN+nCsQM78X5v773L8NOhRyn+pgDh5k9qUwrqOtHxGIA=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1YGZxO-000247-UG; Thu, 29 Jan 2015 00:15:26 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id BA57F8E5; Thu, 29 Jan 2015 00:14:46 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 237CF4AD8; Thu, 29 Jan 2015 00:15:04 +0300 (MSK) Date: Thu, 29 Jan 2015 00:15:04 +0300 From: Dmitry Marakasov To: freebsd-current@FreeBSD.org Subject: Re: OptionalObsoleteFiles.inc completeness improvement, try 2 Message-ID: <20150128211504.GB55246@hades.panopticon> References: <20150124002956.GI1101@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150124002956.GI1101@hades.panopticon> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Warner Losh , Nathan Whitehorn , Garrett Cooper X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 21:15:31 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: The patch is complete, see https://reviews.freebsd.org/D1600. - With it, for all knobs from src.conf(5) there are no difference in file tree contents between `KNOB make installworld` and `make installworld && KNOB make delete-old delete-old-libs` - Note that some OLD_DIRS were removed - they were incorrect as most directories are installed unconditionally by mtree. Since empty directores are not really needed, the install process should be probably improved - Some knobs which delete massive number of files (WITHOUT_MAN, WITHOUT_INCLUDES) were implemented with FILES!=find ... OLD_FILES+=${FILES} (similar construct was already used in WITHOUT_TESTS) I though of more effective implementation for this, such as introducing OLD_DIRS_RECURSIVE to fill from OptionalObsoleteFiles, in which delete-old will just call `find ... -delete` - Unneeded conditions such as .if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "powerpc64" OLD_FILES+=usr/lib32/... .else were not removed yet. Maybe with the next patch. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:53:33 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 844D74E1 for ; Wed, 28 Jan 2015 21:53:33 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 5548786F for ; Wed, 28 Jan 2015 21:53:33 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6DADA20E3F for ; Wed, 28 Jan 2015 16:53:26 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 28 Jan 2015 16:53:26 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=SAXf9k3rTZMOxXcqb0qq 7IuRA/I=; b=IsccDVHodcbim39rcztSsf+VbzLi3G5tB/6PoRxbAqs7rhRwGfAz F68noFEXNVe/MpdeMKN6ypZFZ6nAf0cWro5jhNqaR2A9gceAKVIEB7fAYw+O+SAU 8d1NZNKZ088VBIaPSY6AYYBJzFsP1EsqWcQLI+lr0d2h1an1EO0z06w= Received: by web3.nyi.internal (Postfix, from userid 99) id 28E5C112FCE; Wed, 28 Jan 2015 16:53:25 -0500 (EST) Message-Id: <1422482005.645595.220197745.53E86A68@webmail.messagingengine.com> X-Sasl-Enc: OeWG4DRjAk1fOL1ExoCPbXEHH8XTzGmPAODgDPz7hCMx 1422482005 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-46f3f2c7 Subject: Re: Memory corruption in a master perl process after child exits - only under FreeBSD 10.0 amd64 (not in 10.1 or 9.*) Date: Wed, 28 Jan 2015 15:53:25 -0600 In-Reply-To: <1ac9f02be1360da3969ddb9501d0375a@mailbox.ijs.si> References: <1ac9f02be1360da3969ddb9501d0375a@mailbox.ijs.si> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 21:53:33 -0000 On Mon, Jan 26, 2015, at 13:32, Mark Martinec wrote: > There is a problem report since July 2014 in a Perl bug tracker, > which seems to affect only FreeBSD 10.0 amd64 (regardless of a > version of Perl or usage of clang vs. gcc compiler): > > https://rt.perl.org/Ticket/Display.html?id=122199 > Given the ability to reproduce this 100% it seems perfect for using git bisect command to figure out which commit between 10.0 and 10.1 solves this. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:58:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3208365E; Wed, 28 Jan 2015 21:58:01 +0000 (UTC) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E754D8AF; Wed, 28 Jan 2015 21:58:00 +0000 (UTC) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id E80031F2; Wed, 28 Jan 2015 22:57:48 +0100 (CET) Date: Wed, 28 Jan 2015 22:57:48 +0100 From: Michael Moll To: Mark Felder Subject: Re: Memory corruption in a master perl process after child exits - only under FreeBSD 10.0 amd64 (not in 10.1 or 9.*) Message-ID: <20150128215748.GA53812@darkthrone.kvedulv.de> References: <1ac9f02be1360da3969ddb9501d0375a@mailbox.ijs.si> <1422482005.645595.220197745.53E86A68@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1422482005.645595.220197745.53E86A68@webmail.messagingengine.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 21:58:01 -0000 Hi, On Wed, Jan 28, 2015 at 03:53:25PM -0600, Mark Felder wrote: > > https://rt.perl.org/Ticket/Display.html?id=122199 > > Given the ability to reproduce this 100% it seems perfect for using git > bisect command to figure out which commit between 10.0 and 10.1 solves > this. Sorry for coming late to this thread, but depending on the CPU it might be worth a try if it's fixed on 10.0 with vm.pmap.pcid_enabled set to 0. Regards -- Michael Moll From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:21:49 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1BFC6C for ; Wed, 28 Jan 2015 23:21:49 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6C30269 for ; Wed, 28 Jan 2015 23:21:49 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id ar1so26507295iec.13 for ; Wed, 28 Jan 2015 15:21:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=zoVi1h5IwTx1KaasxCuR+b71fTM9wyZCXwTPISmQl20=; b=O3K+loXv58nYDaqQY25JJzdmmInRQooUYweIUPQ8hfZLFNs5K9VwnXi+fJN+yJh3O2 YVQSLoCQ8XC+rl08MhEJoRY6WCNojErV4f5oGgUe+8EZAjtKj4QlvNwR2z0ar7GBgWJg vK5dTumLTd1W7qxADB6eDLJQppQCtUQGuWFPnC6zvuyTps9D0q9Ni6XZSnN/D1VbUzbB nUA9sv9IsYCSFfwA7RcvPzdKmBdt/QZLq9fkPC/mF352a2oTpbyxE35bByf68u+IInaF gkxddwYLscvuz+efSW2woqZxa5SE+tad+8zAlsre8jJtJ15Y67dKsfW4hoHA14thCRmZ gclw== X-Gm-Message-State: ALoCoQna5CN6PeckJjpOg46mVdTP9CeHZjSWey5S3BiqUXremSPFrw1NjvXet/pqhkrNM/J1EaQNlIrSgE/F9awqzuIfnBmuD6J4lW2F9EIZl+StaslB3N+ZUvbBZhrMAA+HMzBGyT4h X-Received: by 10.50.78.202 with SMTP id d10mr6753918igx.30.1422487308338; Wed, 28 Jan 2015 15:21:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Wed, 28 Jan 2015 15:21:32 -0800 (PST) In-Reply-To: <20150128201440.GA73589@cicely7.cicely.de> References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> From: "Lundberg, Johannes" Date: Thu, 29 Jan 2015 08:21:32 +0900 Message-ID: Subject: Re: System-On-Module To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 23:21:50 -0000 Thanks a lot guys. I can specify a bit more details. We don't need any sd-card, sata or external storage. Just the internal eMMC is enough. Display output can be DSI, LVDS or something that can easily be serialized to transfer over 2 wires. If WiFi and Bluetooth 4.0 is on the board that'll also be great. And of course, it would be helpful if the said board also is available as development kit... If the first tests are ok (tests can be done using Linux if FreeBSD doesn't run out of the box) we're looking to buy a larger amount, at least >1000 to start with. We are flexible about prize and size of the board. Atom is preferable over imx6, but I'll check out what you recommended. Thanks again! Ps. Hopefully we can also provide development boards for anyone who wants to help with porting out of own interest. -- Johannes Lundberg On Thu, Jan 29, 2015 at 5:14 AM, Bernd Walter wrote: > On Wed, Jan 28, 2015 at 12:27:31PM -0700, Ian Lepore wrote: > > On Wed, 2015-01-28 at 19:32 +0100, Bernd Walter wrote: > > > On Wed, Jan 28, 2015 at 06:52:52PM +0900, Lundberg, Johannes wrote: > > > > Hi > > > > > > > > Of all the low power, high-spec system/computer-on-modules out ther= e > which > > > > have best support for FreeBSD? > > > > > > > > MEN > > > > Variscite > > > > Technologic system > > > > Adlink > > > > etc. > > > > > > > > What I am looking for is a system with roughly this specs > > > > ARM or x86, 64bit if possible. > > > > 2-4 cores > > > > 1.5-2.0 GHz > > > > 2 GB RAM > > > > ~16 GB Storage > > > > USB 3.0 > > > > PCB size about one to two credit cards. > > > > > > In that range I would go for a Wandboard. > > > They are 1, 2 or 4 core iMX6 32bit with 512M, 1G or 2G RAM. > > > The 4 core has SATA, which to my knowledge we don't support yet. > > > They come with 2 useable SD-card slots - one on the module and one > > > on a carrier board. > > > Clock rate is 1GHz only IIRC and they only have high speed USB, > although > > > the newest carrier boards have some super speed wiring for future > modules. > > > > > > TechNexion, the originator of that module system also has some > > > x86 boards - some may fit your requirements, but those are at > > > a higher price and bigger form factor. > > > Tech Nexion also has iMX6 boards similar to the wandboard with > > > different featuresets, but also at a higher price. > > > > You do get more for that higher price with the Technexion EDM modules, > > namely 1.2ghz chips instead of 1.0, and parts that are industrial and/o= r > > automotive temperature-rated rather than consumer grade. On the other > > hand, you generally can't buy Technexion modules one at a time. Last > > time I checked they were minimum order 10 pieces even from resellers > > like Mouser and Digikey. > > Temperature rating - that can easily justify the higher price. > > > Another small-board imx6 possibility is the Hummingboard from SolidRun. > > I now have freebsd running on a SolidRun Cubox-i4, so I expect no large > > drama in getting it working on other SolidRun imx6 products. Gonzo > > ordered a Hummingboard recently, so we should know for sure some time > > soon. > > To my knowledge they come in 3 different sizes. > I own the biggest two versions of them. > Completely forgot that the Hummingboard uses modules as well and the > modules are even very small. > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:29:14 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA7ED425 for ; Wed, 28 Jan 2015 23:29:14 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90C4C2E1 for ; Wed, 28 Jan 2015 23:29:14 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id ar1so26576625iec.13 for ; Wed, 28 Jan 2015 15:29:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=hJYlqxUbuMkwuzBDGQzzJH31ICMnM+4Dh1QSaC6EW38=; b=ReEc17WxElBAkzis+85F5ThquXKHlDMwAYKlyT0CBcxilRw9VLKb41yOko0x6f3WGi gYPzIOfY+/IsZUa4wkVJoPmj/RmU+PH1hQ2wMDaC3uWPdFHXj+JMmpRGdEMND2Tmb4d6 1oUlavuIO0yM4fbafkuJ9O87aENpI6fwm+q/NNzCwq4ilW6G8BeXMBCp1qX0ONzzLmxk abGk6REabAYL2zW3Jgg3xqEb2xQ5AU0QfN5+JWKtyBheBf4Q7jpI7aSSqRpJkXXTS/fa QajDg7SeT9gsNENKsGxv/s34BLw8orPbDhPNJS1MzgBzPgStozzthkUvvBeUj5EzIJvk cd4A== X-Gm-Message-State: ALoCoQnRODbuPn3Fc/+aV0SvEL61AldtZWChE++5LxhOakJpku6iNuSnn4cPkOeJI5Yosgou6O5MbSVmFJYsVediaChm7jCdTxiQP4Mx0byBd4OLB5jfQ7rQpf+xm6H1RmN0Lw1AfnhG X-Received: by 10.50.67.100 with SMTP id m4mr6887281igt.22.1422487754012; Wed, 28 Jan 2015 15:29:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Wed, 28 Jan 2015 15:28:58 -0800 (PST) In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> From: "Lundberg, Johannes" Date: Thu, 29 Jan 2015 08:28:58 +0900 Message-ID: Subject: Re: System-On-Module To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 23:29:14 -0000 By the way, this is for an embedded mobile device so we are looking for something more like http://www.kontron.com/products/computeronmodules/smarc/smarc-samx6i.html instead of Wandboard which has all the connectors that we won't use. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Jan 29, 2015 at 8:21 AM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Thanks a lot guys. > > I can specify a bit more details. > We don't need any sd-card, sata or external storage. Just the internal > eMMC is enough. > Display output can be DSI, LVDS or something that can easily be serialize= d > to transfer over 2 wires. > If WiFi and Bluetooth 4.0 is on the board that'll also be great. > And of course, it would be helpful if the said board also is available as > development kit... > > If the first tests are ok (tests can be done using Linux if FreeBSD > doesn't run out of the box) we're looking to buy a larger amount, at leas= t > >1000 to start with. > > We are flexible about prize and size of the board. > > Atom is preferable over imx6, but I'll check out what you recommended. > Thanks again! > > Ps. Hopefully we can also provide development boards for anyone who wants > to help with porting out of own interest. > > -- > Johannes Lundberg > > On Thu, Jan 29, 2015 at 5:14 AM, Bernd Walter > wrote: > >> On Wed, Jan 28, 2015 at 12:27:31PM -0700, Ian Lepore wrote: >> > On Wed, 2015-01-28 at 19:32 +0100, Bernd Walter wrote: >> > > On Wed, Jan 28, 2015 at 06:52:52PM +0900, Lundberg, Johannes wrote: >> > > > Hi >> > > > >> > > > Of all the low power, high-spec system/computer-on-modules out >> there which >> > > > have best support for FreeBSD? >> > > > >> > > > MEN >> > > > Variscite >> > > > Technologic system >> > > > Adlink >> > > > etc. >> > > > >> > > > What I am looking for is a system with roughly this specs >> > > > ARM or x86, 64bit if possible. >> > > > 2-4 cores >> > > > 1.5-2.0 GHz >> > > > 2 GB RAM >> > > > ~16 GB Storage >> > > > USB 3.0 >> > > > PCB size about one to two credit cards. >> > > >> > > In that range I would go for a Wandboard. >> > > They are 1, 2 or 4 core iMX6 32bit with 512M, 1G or 2G RAM. >> > > The 4 core has SATA, which to my knowledge we don't support yet. >> > > They come with 2 useable SD-card slots - one on the module and one >> > > on a carrier board. >> > > Clock rate is 1GHz only IIRC and they only have high speed USB, >> although >> > > the newest carrier boards have some super speed wiring for future >> modules. >> > > >> > > TechNexion, the originator of that module system also has some >> > > x86 boards - some may fit your requirements, but those are at >> > > a higher price and bigger form factor. >> > > Tech Nexion also has iMX6 boards similar to the wandboard with >> > > different featuresets, but also at a higher price. >> > >> > You do get more for that higher price with the Technexion EDM modules, >> > namely 1.2ghz chips instead of 1.0, and parts that are industrial and/= or >> > automotive temperature-rated rather than consumer grade. On the other >> > hand, you generally can't buy Technexion modules one at a time. Last >> > time I checked they were minimum order 10 pieces even from resellers >> > like Mouser and Digikey. >> >> Temperature rating - that can easily justify the higher price. >> >> > Another small-board imx6 possibility is the Hummingboard from SolidRun= . >> > I now have freebsd running on a SolidRun Cubox-i4, so I expect no larg= e >> > drama in getting it working on other SolidRun imx6 products. Gonzo >> > ordered a Hummingboard recently, so we should know for sure some time >> > soon. >> >> To my knowledge they come in 3 different sizes. >> I own the biggest two versions of them. >> Completely forgot that the Hummingboard uses modules as well and the >> modules are even very small. >> >> -- >> B.Walter http://www.bwct.de >> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. >> > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:46:27 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AFBC3725; Wed, 28 Jan 2015 23:46:27 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2186567D; Wed, 28 Jan 2015 23:46:26 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t0SNk1k8031475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 29 Jan 2015 00:46:01 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t0SNjxPv029002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2015 00:45:59 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t0SNjxqc074690; Thu, 29 Jan 2015 00:45:59 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t0SNjw4A074689; Thu, 29 Jan 2015 00:45:58 +0100 (CET) (envelope-from ticso) Date: Thu, 29 Jan 2015 00:45:58 +0100 From: Bernd Walter To: "Lundberg, Johannes" Subject: Re: System-On-Module Message-ID: <20150128234558.GE73589@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 28 Jan 2015 23:46:27 -0000 On Thu, Jan 29, 2015 at 08:28:58AM +0900, Lundberg, Johannes wrote: > By the way, this is for an embedded mobile device so we are looking for > something more like > > http://www.kontron.com/products/computeronmodules/smarc/smarc-samx6i.html > > instead of Wandboard which has all the connectors that we won't use. Don't get confused with the wandboard module+carrier board, which is the normal offer (and in small volumes often cheaper than the 10x module pack). The Wandboard module alone is extremly similar to the Kontron modules in your link. They don't have eMMC (maybe some of the TechNexion have), but they do have a micro-SD on the module itself, plus SDIO on the module header. eMMC can have a higher transport speed because it allows for 8bit instead of 4bit and as soldered chip it has different issued than a socketed card, but otherwise they are very similar in design. The 2 and 4 core Wandboards have BT/WLAN on module, but it is done by SDIO, for which FreeBSD (to my knowledge) has no support yet. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 00:07:07 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1359DD6D; Thu, 29 Jan 2015 00:07:07 +0000 (UTC) Received: from smtp5.ore.mailhop.org (smtp5.ore.mailhop.org [54.186.10.118]) (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 E20778B9; Thu, 29 Jan 2015 00:07:06 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YGcdP-0003GF-1k; Thu, 29 Jan 2015 00:06:59 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t0T06rPk029327; Wed, 28 Jan 2015 17:06:53 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19FuY4xdbtzhBpr88i4Mx/a Message-ID: <1422490013.15718.79.camel@freebsd.org> Subject: Re: System-On-Module From: Ian Lepore To: "Lundberg, Johannes" Date: Wed, 28 Jan 2015 17:06:53 -0700 In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 00:07:07 -0000 On Thu, 2015-01-29 at 08:28 +0900, Lundberg, Johannes wrote: > By the way, this is for an embedded mobile device so we are looking for > something more like > > http://www.kontron.com/products/computeronmodules/smarc/smarc-samx6i.html > > instead of Wandboard which has all the connectors that we won't use. That's similar to the EDM module that wandboards use: http://www.technexion.com/products/edm/edm-som/edm1-cf-imx6 You can buy the EDM modules directly from Technexion if you're willing to buy quantity, or through resellers like Digikey. The EDM modules from technexion are compatible with the wandboard carrier boards, so you can use a few cheap wandboards as devel and eval boards (or you can buy the overpriced "fairyboard" carrier from technexion that has PCIe connectors that wandboard lacks). We're using these modules at $work, and that's basically the path I took... I started with a wandboard and got freebsd running on it, and once it got past the proof of concept stage (the minimum set of drivers for the imx6 devices we need, and reasonable freebsd stability -- I had a board running a stress test with 2 months of uptime) we designed our own motherboards with EDM sockets on them. -- Ian From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 00:13:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 264CEA3 for ; Thu, 29 Jan 2015 00:13:01 +0000 (UTC) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF781993 for ; Thu, 29 Jan 2015 00:13:00 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id rl12so26919351iec.11 for ; Wed, 28 Jan 2015 16:13:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=/b3AfqRYl51nguM1b93b0FApNZGT45vpJTdVErkvhaE=; b=ZY4/4aQPQhF5309ZcVzMf+5l1Q5DGrwLw3DNhcDrCVQPj8ne8PgQTBeUrw9f5hMWXA Q9DK6hLgMHSDgBZFyC2FdDhT0Hm9yDPBzMym5WiGD+1yKjTQ/4we+N/2le0nn/bqkwle oWW3yc9g3Qb9FVTjgUobN6iALbtO0nQMOVfpE/dkGEPHZMhmvuU/5cu4DxzPWghONCH5 cZwJny75wvTYrvEtRzanvPcpkc+cS1QV6IqiD1O9Cefx3kxIeeCgrLddaoO8OYV0fV8g gAqlmZ/2wht60+uLVlESnMiabIoI6NtUwbDmmPfNGhJe+vA0s2OwyKlDghPvwqpqIl1J xOTQ== X-Gm-Message-State: ALoCoQnqvs/+Pq5zJiJ4UIXUNCswy9PNcHtGArd8/dIdMYrcWmS5R6Aaynw9khi4wPcl0aWUEp1dvGscBP4ca2ICCX52G6ZAwfV2eDS2IiDy+hsU0vIMJlgnnI8PZglSnsp3XXAfd6nE X-Received: by 10.42.239.1 with SMTP id ku1mr244696icb.45.1422490374144; Wed, 28 Jan 2015 16:12:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Wed, 28 Jan 2015 16:12:38 -0800 (PST) In-Reply-To: <1422490013.15718.79.camel@freebsd.org> References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> From: "Lundberg, Johannes" Date: Thu, 29 Jan 2015 09:12:38 +0900 Message-ID: Subject: Re: System-On-Module To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 00:13:01 -0000 Ah now I see it has EDM connection. I didn't look carefully enough. All the images are with the expansion board attached.. Spec-wise and portability-wise it seems like a good option but my hardware guy keeps warning me about Freescale that they often have hardware bugs and rather than fixing the bugs they pretend they are not there.. In other words, Freescale is good for software developers because of open documentation but not so for hardware manufactures. Any experiences with this? -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Jan 29, 2015 at 9:06 AM, Ian Lepore wrote: > On Thu, 2015-01-29 at 08:28 +0900, Lundberg, Johannes wrote: > > By the way, this is for an embedded mobile device so we are looking for > > something more like > > > > > http://www.kontron.com/products/computeronmodules/smarc/smarc-samx6i.html > > > > instead of Wandboard which has all the connectors that we won't use. > > That's similar to the EDM module that wandboards use: > > http://www.technexion.com/products/edm/edm-som/edm1-cf-imx6 > > You can buy the EDM modules directly from Technexion if you're willing > to buy quantity, or through resellers like Digikey. The EDM modules > from technexion are compatible with the wandboard carrier boards, so you > can use a few cheap wandboards as devel and eval boards (or you can buy > the overpriced "fairyboard" carrier from technexion that has PCIe > connectors that wandboard lacks). > > We're using these modules at $work, and that's basically the path I > took... I started with a wandboard and got freebsd running on it, and > once it got past the proof of concept stage (the minimum set of drivers > for the imx6 devices we need, and reasonable freebsd stability -- I had > a board running a stress test with 2 months of uptime) we designed our > own motherboards with EDM sockets on them. > > -- Ian > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 00:36:06 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 548B07BC; Thu, 29 Jan 2015 00:36:06 +0000 (UTC) Received: from smtp4.ore.mailhop.org (smtp4.ore.mailhop.org [54.149.240.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D923BCA; Thu, 29 Jan 2015 00:36:05 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by smtp4.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YGd5X-0005bH-QV; Thu, 29 Jan 2015 00:36:03 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t0T0a0SC029576; Wed, 28 Jan 2015 17:36:00 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19SQjhCnkSh9HOf2vDrL4cw Message-ID: <1422491760.15718.97.camel@freebsd.org> Subject: Re: System-On-Module From: Ian Lepore To: "Lundberg, Johannes" Date: Wed, 28 Jan 2015 17:36:00 -0700 In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 00:36:06 -0000 On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > Ah now I see it has EDM connection. I didn't look carefully enough. All the > images are with the expansion board attached.. > > Spec-wise and portability-wise it seems like a good option but my hardware > guy keeps warning me about Freescale that they often have hardware bugs and > rather than fixing the bugs they pretend they are not there.. In other > words, Freescale is good for software developers because of open > documentation but not so for hardware manufactures. Any experiences with > this? The imx6 manuals include an errata list, so it would be good to check that for anything specific that would matter to your projects. For the devices we use in our products everything is good so far with the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lots of gpio (inputs and outputs). The ethernet is gigabit but has a known limitation of 40MB/s due to the bus it's connected to in the chip. (But hey, it's documented so it's not a problem, right? :) You mentioned video, and we don't have that working on freebsd imx6 yet, but there's not a ton of work to do. There's a framebuffer driver for imx5 and it has pretty much the same framebuffer hardware. Getting video output to a TTL LCD is probably just hours of work. Getting it to an LVDS LCD or HDMI probably needs days of work (entire drivers written, potentially, I haven't looked into it). Some audio support was recently committed, but I don't know much about it yet. -- Ian From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 00:50:41 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC3E8B5E for ; Thu, 29 Jan 2015 00:50:41 +0000 (UTC) Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 702B1CCA for ; Thu, 29 Jan 2015 00:50:41 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id tr6so27230563ieb.2 for ; Wed, 28 Jan 2015 16:50:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=40MDe2PIsRNwj+hWVSNt/AHZHg2TAicCmffZXEw4AOU=; b=YEFfyi3xWQmSHrjUmyRrw6gBOBctoDp7PJ2yXJRjEibqtK4yiiEyVx11UGZGZzsQZa zUtlLLWKqj0jBNN8uWUCNmdnCpyAyfxYby9eOjwWAjKYVCcQz0M1EJieItm4gEZUnFcB niebm/xvEKgM+4+IbfkgJzANjwFj+CbciUJwe+tLhkER70UujBTJX4BTpqEclI7qcNAO mcyxj88ESp6WXTTHjujLXKpeXCd2+jLsAw72DKm5SI7wit6kPBlvr3cdlWHKVy+rxZsN Wjl+ahFOyhN9DU4ACrZAjRnNIoe6nK5GUsBOgwOU7yI0sShWUHREOQcJAu42EVoXqHy+ wIBw== X-Gm-Message-State: ALoCoQkb5bh8btxG+cl9Bzmv4zePvXrrjAhUpnc1HlQsjw6iTYWWJ53mu/RC0J8MD+zcqwsme+wTCztu4pfydctXApbxEqBbWYpKM6HNORbNf4HOBDT07Dnt6LNcCPZCSaaREts+OwEA X-Received: by 10.50.111.10 with SMTP id ie10mr6948696igb.15.1422492640625; Wed, 28 Jan 2015 16:50:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Wed, 28 Jan 2015 16:50:25 -0800 (PST) In-Reply-To: <1422491760.15718.97.camel@freebsd.org> References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> From: "Lundberg, Johannes" Date: Thu, 29 Jan 2015 09:50:25 +0900 Message-ID: Subject: Re: System-On-Module To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 00:50:41 -0000 How about these Tegra3 boards? https://www.toradex.com/computer-on-modules/apalis-arm-family/nvidia-tegra-= 3 -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Jan 29, 2015 at 9:36 AM, Ian Lepore wrote: > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > > Ah now I see it has EDM connection. I didn't look carefully enough. All > the > > images are with the expansion board attached.. > > > > Spec-wise and portability-wise it seems like a good option but my > hardware > > guy keeps warning me about Freescale that they often have hardware bugs > and > > rather than fixing the bugs they pretend they are not there.. In other > > words, Freescale is good for software developers because of open > > documentation but not so for hardware manufactures. Any experiences wit= h > > this? > > The imx6 manuals include an errata list, so it would be good to check > that for anything specific that would matter to your projects. > > For the devices we use in our products everything is good so far with > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lots > of gpio (inputs and outputs). The ethernet is gigabit but has a known > limitation of 40MB/s due to the bus it's connected to in the chip. (But > hey, it's documented so it's not a problem, right? :) > > You mentioned video, and we don't have that working on freebsd imx6 yet, > but there's not a ton of work to do. There's a framebuffer driver for > imx5 and it has pretty much the same framebuffer hardware. Getting > video output to a TTL LCD is probably just hours of work. Getting it to > an LVDS LCD or HDMI probably needs days of work (entire drivers written, > potentially, I haven't looked into it). > > Some audio support was recently committed, but I don't know much about > it yet. > > -- Ian > > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 00:55:10 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BEFED88; Thu, 29 Jan 2015 00:55:10 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F6FAD83; Thu, 29 Jan 2015 00:55:10 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id l4so22875183lbv.13; Wed, 28 Jan 2015 16:55:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=bzoMcUYfTkGKOyMkuYKUmfupYVP3069M2jKCcsOJM+U=; b=g+Rc7/LIjiM5hX2PFcrVgjmclKW85VNzVPTk9RgYme5CSLT0RdZy7ou3NQvixW//kU qY214ybC+NhffRl4Qg1K+yG88p/Xi8soAJ2q9ycPbRYYwHpfl1q+TgAC13w/7OgH1I1I 9pX0AxCdSDMbQuJC26w512XDhD/rdtVBPyUpZDRHvkK85xYWw/XNrZ7Jms9c1uaCRKLi Sen5Wwx4RAuMs1kseKL2ShkkH48NTnxhWze4oFdCQNzX8K3BKDoUIDEMWALEUiQe1uTC iiysewff88Atin1Epp1bF4EFleS1d4zV7F3/rA913Vy0RgP2Qvl6umakQ4TzEUJt4biL BY+w== X-Received: by 10.152.115.212 with SMTP id jq20mr11556287lab.36.1422492908177; Wed, 28 Jan 2015 16:55:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.12.6 with HTTP; Wed, 28 Jan 2015 16:54:37 -0800 (PST) From: Yue Chen Date: Wed, 28 Jan 2015 19:54:37 -0500 Message-ID: Subject: How to know the address ranges of kernel stacks, for user processes and kernel threads? To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 00:55:10 -0000 How can we know the kernel stack ranges for user process and kernel threads under FreeBSD x86_64? It seems that each kernel stack has two pages (IA-32) to use. Does x86_64 still have two pages or more? And how can we find the address of these two pages from a kernel module? From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:33:41 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7B03DDD; Thu, 29 Jan 2015 02:33:41 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 638F8B71; Thu, 29 Jan 2015 02:33:41 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t0T2XHMC033235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 29 Jan 2015 03:33:17 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t0T2XEux032088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2015 03:33:14 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t0T2XECV076173; Thu, 29 Jan 2015 03:33:14 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t0T2XE7s076172; Thu, 29 Jan 2015 03:33:14 +0100 (CET) (envelope-from ticso) Date: Thu, 29 Jan 2015 03:33:14 +0100 From: Bernd Walter To: Ian Lepore Subject: Re: System-On-Module Message-ID: <20150129023314.GH73589@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1422491760.15718.97.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "Lundberg, Johannes" , "freebsd-mobile@freebsd.org" , ticso@cicely.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 02:33:41 -0000 On Wed, Jan 28, 2015 at 05:36:00PM -0700, Ian Lepore wrote: > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > > Ah now I see it has EDM connection. I didn't look carefully enough. All the > > images are with the expansion board attached.. > > > > Spec-wise and portability-wise it seems like a good option but my hardware > > guy keeps warning me about Freescale that they often have hardware bugs and > > rather than fixing the bugs they pretend they are not there.. In other > > words, Freescale is good for software developers because of open > > documentation but not so for hardware manufactures. Any experiences with > > this? > > The imx6 manuals include an errata list, so it would be good to check > that for anything specific that would matter to your projects. If you use a prebuild module then you don't get much in touch with the freescale chip fropm the hardware side. On the other hand, there are countless iMX6 boards out there with schematics online. My recently bought Novena even came with printed schematics and they open sourced the HW design files as well. I don't think there are hidden surprises on the hardware side. > For the devices we use in our products everything is good so far with > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lots > of gpio (inputs and outputs). The ethernet is gigabit but has a known > limitation of 40MB/s due to the bus it's connected to in the chip. (But > hey, it's documented so it's not a problem, right? :) > > You mentioned video, and we don't have that working on freebsd imx6 yet, > but there's not a ton of work to do. There's a framebuffer driver for > imx5 and it has pretty much the same framebuffer hardware. Getting > video output to a TTL LCD is probably just hours of work. Getting it to > an LVDS LCD or HDMI probably needs days of work (entire drivers written, > potentially, I haven't looked into it). Sounds interesting for my Novena. The one I already got are board only (with some FPGA breakout, ...). They have HDMI though. But I'm also awaiting for the one with case and LCD panel. Not to forget that I have a fairy EDM carrier with LCD already. That said I'v always wondered how much work is it to get the camera interface running, since the Hummingboards can connect to the RPi camera modules. > Some audio support was recently committed, but I don't know much about > it yet. > > -- Ian > > -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 08:18:25 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3523A567 for ; Thu, 29 Jan 2015 08:18:25 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ECFF4197 for ; Thu, 29 Jan 2015 08:18:24 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id ar1so30696079iec.13 for ; Thu, 29 Jan 2015 00:18:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=awXFMSZLtjvB8uP+rLfmTX6AUtihxFqiT8585iJSY9s=; b=IT8StWlOJKdQUbJP/CmMaPOS5qC0jtKk7zWg+4RnOtOEo+T/jbXVb03hG9kPbqbyWq V4wOd7kRl3l6P6iNgNJ1ZSRDgXlgHVzuWYRzSf1ErzAzJLLVRf95QbEb+MqtjMiQX7PN 3RgT6iiCu/hIN2/XAZySv8i8fBhtFfCNoMaUkBH7yIh+leLo3wUP0AQevGoryR9JaqEN Zl2TpCDnhPxGknsUIEPbE/aHhdTL33nMx0zKAfxFsNHqGa+iekDOgpd9bQsHjrqCtP2w XuZRc3MdAG2F+l5A0/3n49l0MKy7kYT4Of3fSuIJ0vVRaVN8/yLeVKX8/qbUEfuziWp4 r0rA== X-Gm-Message-State: ALoCoQm9ZJP2ImJS80UYlhJ8qLsMtAZJ8oBjo98ZkeOdqeCPc4sFuGM97exfU0BArWpFfoYATILz/jnDXCIATpyuvnNaVZVPO3ulttNIkNlBteSnl4hXJgkyMailYPEKSpI6CvDa9Xgu X-Received: by 10.50.142.99 with SMTP id rv3mr908601igb.11.1422519503954; Thu, 29 Jan 2015 00:18:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Thu, 29 Jan 2015 00:18:08 -0800 (PST) In-Reply-To: <20150129023314.GH73589@cicely7.cicely.de> References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> From: "Lundberg, Johannes" Date: Thu, 29 Jan 2015 17:18:08 +0900 Message-ID: Subject: Re: System-On-Module To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 08:18:25 -0000 Hi All Thanks again for all the replies. How is the support for A15 and how is Qualcomm to work with when it comes to porting? Thinking about this guy which is closer to what I want spec-wise.. http://www.variscite.com/products/system-on-module-som/cortex-a15-krait/var= -som-sd600-cpu-qualcomm-snapdragon600 -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Jan 29, 2015 at 11:33 AM, Bernd Walter wrote: > On Wed, Jan 28, 2015 at 05:36:00PM -0700, Ian Lepore wrote: > > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > > > Ah now I see it has EDM connection. I didn't look carefully enough. > All the > > > images are with the expansion board attached.. > > > > > > Spec-wise and portability-wise it seems like a good option but my > hardware > > > guy keeps warning me about Freescale that they often have hardware > bugs and > > > rather than fixing the bugs they pretend they are not there.. In othe= r > > > words, Freescale is good for software developers because of open > > > documentation but not so for hardware manufactures. Any experiences > with > > > this? > > > > The imx6 manuals include an errata list, so it would be good to check > > that for anything specific that would matter to your projects. > > If you use a prebuild module then you don't get much in touch with > the freescale chip fropm the hardware side. > On the other hand, there are countless iMX6 boards out there with > schematics online. > My recently bought Novena even came with printed schematics and they > open sourced the HW design files as well. > I don't think there are hidden surprises on the hardware side. > > > For the devices we use in our products everything is good so far with > > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lots > > of gpio (inputs and outputs). The ethernet is gigabit but has a known > > limitation of 40MB/s due to the bus it's connected to in the chip. (Bu= t > > hey, it's documented so it's not a problem, right? :) > > > > You mentioned video, and we don't have that working on freebsd imx6 yet= , > > but there's not a ton of work to do. There's a framebuffer driver for > > imx5 and it has pretty much the same framebuffer hardware. Getting > > video output to a TTL LCD is probably just hours of work. Getting it t= o > > an LVDS LCD or HDMI probably needs days of work (entire drivers written= , > > potentially, I haven't looked into it). > > Sounds interesting for my Novena. > The one I already got are board only (with some FPGA breakout, ...). > They have HDMI though. > But I'm also awaiting for the one with case and LCD panel. > Not to forget that I have a fairy EDM carrier with LCD already. > That said I'v always wondered how much work is it to get the camera > interface running, since the Hummingboards can connect to the RPi > camera modules. > > > Some audio support was recently committed, but I don't know much about > > it yet. > > > > -- Ian > > > > > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 09:10:48 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DDD8D4C6; Thu, 29 Jan 2015 09:10:48 +0000 (UTC) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9566C9AB; Thu, 29 Jan 2015 09:10:48 +0000 (UTC) Received: by mail-oi0-f48.google.com with SMTP id v63so24739278oia.7; Thu, 29 Jan 2015 01:10:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vQa5TRA0i4Ffbh2TtodHT3Oc1tslCDfdK0bGy2VFl9I=; b=owRIF6Sf3xUGlT8ribGB1Pv9MPmg+cafFm4txJFVRbC7kFY7/bUDl1IcCfDmZbpDsw TXqbKNeqh7eG/4dUXG1Z/cZ2mocgki3bIsm7X8HLnps/ZxD4CPS0rPSOXnQc8ACE6px5 bHG9+ZoNegU+5N6sU9oCoNL29H/p5nMwyYg8DCyzkwx2OGziXkwNezW+tCzu/Z3ZM2cz PUzmHVIfLmHkjwEfaPS0+Z0zQQm118IT9QbR+6/GY6xx8ZOrok3Ft5o0mI4vhz1z5LIT XYxtEGHSWzrXEZhVLKjXHv9dkXbyVqSHmBk0T4Sa0asSAeP0u2+ho4V5fB5IuaiWKEBA YNFw== MIME-Version: 1.0 X-Received: by 10.60.144.135 with SMTP id sm7mr4963173oeb.28.1422522647921; Thu, 29 Jan 2015 01:10:47 -0800 (PST) Received: by 10.182.13.33 with HTTP; Thu, 29 Jan 2015 01:10:47 -0800 (PST) In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> Date: Thu, 29 Jan 2015 17:10:47 +0800 Message-ID: Subject: Re: System-On-Module From: Ganbold Tsagaankhuu To: "Lundberg, Johannes" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 09:10:49 -0000 On Thu, Jan 29, 2015 at 4:18 PM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Hi All > > Thanks again for all the replies. > > How is the support for A15 and how is Qualcomm to work with when it comes > to porting? > > Thinking about this guy which is closer to what I want spec-wise.. > > http://www.variscite.com/products/system-on-module-som/cortex-a15-krait/v= ar-som-sd600-cpu-qualcomm-snapdragon600 > > > I think IFC6410 has same SoC as above SoM and as for ifc6410 either mmc/sd or usb ehci driver needed in order to boot FreeBSD into multi user mode. Ganbold > > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. > > On Thu, Jan 29, 2015 at 11:33 AM, Bernd Walter > wrote: > > > On Wed, Jan 28, 2015 at 05:36:00PM -0700, Ian Lepore wrote: > > > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > > > > Ah now I see it has EDM connection. I didn't look carefully enough. > > All the > > > > images are with the expansion board attached.. > > > > > > > > Spec-wise and portability-wise it seems like a good option but my > > hardware > > > > guy keeps warning me about Freescale that they often have hardware > > bugs and > > > > rather than fixing the bugs they pretend they are not there.. In > other > > > > words, Freescale is good for software developers because of open > > > > documentation but not so for hardware manufactures. Any experiences > > with > > > > this? > > > > > > The imx6 manuals include an errata list, so it would be good to check > > > that for anything specific that would matter to your projects. > > > > If you use a prebuild module then you don't get much in touch with > > the freescale chip fropm the hardware side. > > On the other hand, there are countless iMX6 boards out there with > > schematics online. > > My recently bought Novena even came with printed schematics and they > > open sourced the HW design files as well. > > I don't think there are hidden surprises on the hardware side. > > > > > For the devices we use in our products everything is good so far with > > > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lo= ts > > > of gpio (inputs and outputs). The ethernet is gigabit but has a know= n > > > limitation of 40MB/s due to the bus it's connected to in the chip. > (But > > > hey, it's documented so it's not a problem, right? :) > > > > > > You mentioned video, and we don't have that working on freebsd imx6 > yet, > > > but there's not a ton of work to do. There's a framebuffer driver fo= r > > > imx5 and it has pretty much the same framebuffer hardware. Getting > > > video output to a TTL LCD is probably just hours of work. Getting it > to > > > an LVDS LCD or HDMI probably needs days of work (entire drivers > written, > > > potentially, I haven't looked into it). > > > > Sounds interesting for my Novena. > > The one I already got are board only (with some FPGA breakout, ...). > > They have HDMI though. > > But I'm also awaiting for the one with case and LCD panel. > > Not to forget that I have a fairy EDM carrier with LCD already. > > That said I'v always wondered how much work is it to get the camera > > interface running, since the Hummingboards can connect to the RPi > > camera modules. > > > > > Some audio support was recently committed, but I don't know much abou= t > > > it yet. > > > > > > -- Ian > > > > > > > > > > -- > > B.Walter http://www.bwct.de > > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > > > > -- > =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 > =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 > =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 > --- > CONFIDENTIALITY NOTE: The information in this email is confidential > and intended solely for the addressee. > Disclosure, copying, distribution or any other action of use of this > email by person other than intended recipient, is prohibited. > If you are not the intended recipient and have received this email in > error, please destroy the original message. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 09:27:10 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 439C4889 for ; Thu, 29 Jan 2015 09:27:10 +0000 (UTC) Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE1DCB8B for ; Thu, 29 Jan 2015 09:27:09 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id rl12so31373498iec.0 for ; Thu, 29 Jan 2015 01:27:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=YU2JI4lHiV2274Oj9l/xn0T1QCgzgzspdDQhLSQr+RY=; b=Xr6IsnCACtMmoRrKuZ04kJq8SC6U0W6V921PT0zdUYTdF7alHP8AmTASLmRycANhLS G8kAjzjy0k6veVGxb/oD5taQ/XImpbtO9Rk6BZDz3l8+yBEE1OhrgB/Tk90dpShPOtyh 7A4/Nao5MGnpR8hZfduyCBVVAibrXQ08ohiRceBAuMJwarDMsYpSkZ+50b6e2d+/iJPo 7HtLbuhe8j0oR5TC3b6E9dSOMoPVofnnXj2f5j+iv/yQp7FZYNsFdvvis7LnsiY46GLz s6HZdmKJlNnd1OtCZKBfCXTQaqKhyQOJM9YKGlGAxqdigocmhOvI/8P9oYOclPuf8yl0 KVUg== X-Gm-Message-State: ALoCoQnjGcjIJ3EbxhB69oRuDTxvjswfQKRxTJlwXz8WNZt3qpiBj9bA0eFmxs5HWPhYunmDcYMcS0vlUaG/RREJFhtRwEvMHQ2RS0iT5IDURkth6/HCSfWNSRjbzsuTmmN0be5ZaNT2 MIME-Version: 1.0 X-Received: by 10.50.109.228 with SMTP id hv4mr1131841igb.45.1422523628754; Thu, 29 Jan 2015 01:27:08 -0800 (PST) Received: by 10.43.5.136 with HTTP; Thu, 29 Jan 2015 01:27:08 -0800 (PST) In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> Date: Thu, 29 Jan 2015 18:27:08 +0900 Message-ID: Subject: Re: System-On-Module From: "Lundberg, Johannes" To: Ganbold Tsagaankhuu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "ticso@cicely.de" , Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 09:27:10 -0000 What I'm most worried about is the graphics stack.. Some companies don't seem so keen on handing out specs. On Thursday, January 29, 2015, Ganbold Tsagaankhuu wrote: > > > On Thu, Jan 29, 2015 at 4:18 PM, Lundberg, Johannes < > johannes@brilliantservice.co.jp > > wrote: > >> Hi All >> >> Thanks again for all the replies. >> >> How is the support for A15 and how is Qualcomm to work with when it come= s >> to porting? >> >> Thinking about this guy which is closer to what I want spec-wise.. >> >> http://www.variscite.com/products/system-on-module-som/cortex-a15-krait/= var-som-sd600-cpu-qualcomm-snapdragon600 >> >> >> > I think IFC6410 has same SoC as above SoM and as for ifc6410 either mmc/s= d > or usb ehci driver needed in order to boot FreeBSD into multi user mode. > > Ganbold > > > >> >> -- >> Johannes Lundberg >> BRILLIANTSERVICE CO., LTD. >> >> On Thu, Jan 29, 2015 at 11:33 AM, Bernd Walter > > >> wrote: >> >> > On Wed, Jan 28, 2015 at 05:36:00PM -0700, Ian Lepore wrote: >> > > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: >> > > > Ah now I see it has EDM connection. I didn't look carefully enough= . >> > All the >> > > > images are with the expansion board attached.. >> > > > >> > > > Spec-wise and portability-wise it seems like a good option but my >> > hardware >> > > > guy keeps warning me about Freescale that they often have hardware >> > bugs and >> > > > rather than fixing the bugs they pretend they are not there.. In >> other >> > > > words, Freescale is good for software developers because of open >> > > > documentation but not so for hardware manufactures. Any experience= s >> > with >> > > > this? >> > > >> > > The imx6 manuals include an errata list, so it would be good to chec= k >> > > that for anything specific that would matter to your projects. >> > >> > If you use a prebuild module then you don't get much in touch with >> > the freescale chip fropm the hardware side. >> > On the other hand, there are countless iMX6 boards out there with >> > schematics online. >> > My recently bought Novena even came with printed schematics and they >> > open sourced the HW design files as well. >> > I don't think there are hidden surprises on the hardware side. >> > >> > > For the devices we use in our products everything is good so far wit= h >> > > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and >> lots >> > > of gpio (inputs and outputs). The ethernet is gigabit but has a kno= wn >> > > limitation of 40MB/s due to the bus it's connected to in the chip. >> (But >> > > hey, it's documented so it's not a problem, right? :) >> > > >> > > You mentioned video, and we don't have that working on freebsd imx6 >> yet, >> > > but there's not a ton of work to do. There's a framebuffer driver f= or >> > > imx5 and it has pretty much the same framebuffer hardware. Getting >> > > video output to a TTL LCD is probably just hours of work. Getting i= t >> to >> > > an LVDS LCD or HDMI probably needs days of work (entire drivers >> written, >> > > potentially, I haven't looked into it). >> > >> > Sounds interesting for my Novena. >> > The one I already got are board only (with some FPGA breakout, ...). >> > They have HDMI though. >> > But I'm also awaiting for the one with case and LCD panel. >> > Not to forget that I have a fairy EDM carrier with LCD already. >> > That said I'v always wondered how much work is it to get the camera >> > interface running, since the Hummingboards can connect to the RPi >> > camera modules. >> > >> > > Some audio support was recently committed, but I don't know much abo= ut >> > > it yet. >> > > >> > > -- Ian >> > > >> > > >> > >> > -- >> > B.Walter > >> http://www.bwct.de >> > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. >> > >> >> -- >> =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >> =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 >> =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >> =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >> --- >> CONFIDENTIALITY NOTE: The information in this email is confidential >> and intended solely for the addressee. >> Disclosure, copying, distribution or any other action of use of this >> email by person other than intended recipient, is prohibited. >> If you are not the intended recipient and have received this email in >> error, please destroy the original message. >> _______________________________________________ >> freebsd-current@freebsd.org >> mailing >> list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> >> " > > > --=20 -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 10:46:23 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C95FE8F4; Thu, 29 Jan 2015 10:46:23 +0000 (UTC) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79F43699; Thu, 29 Jan 2015 10:46:23 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id h11so22660898wiw.1; Thu, 29 Jan 2015 02:46:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y4eorzrFocmXG1mQ0tpp1lkgQluIP6OX2TeByW0uBaY=; b=Iiz8kxQi3ThUWBPBNOb/faPp8NwGreMAcVfcNqCLMf2iEQIhDKpXf0OCTkW2TYhZKm +Fc65uqa9GYNZ+K6b+gqTJA0wHz+LEDnlVttPfDUd5NRMDL1cgo0kwWZRAc1WWRG+wjC rWzv9b6Edg0gnzhQL/1/+9l5HJGIYiYWhSaeFAb5WjY9gM4eisARb3sTDKw95QRfzw+j HtDuT9hg6tBdKJ9SAn8Khkm/nCTs2yr0HABvXlilPwazL7Nuk4+LCgEdzhDDyR0013SW QVq4MyL8iXt3r+wOp/FZItpMtAIghM5R1FUPAJ7U/ebHCXEEwutJE+dF3+eWFXAAcO4a JT+w== MIME-Version: 1.0 X-Received: by 10.194.175.102 with SMTP id bz6mr7751wjc.120.1422528381679; Thu, 29 Jan 2015 02:46:21 -0800 (PST) Received: by 10.217.64.10 with HTTP; Thu, 29 Jan 2015 02:46:21 -0800 (PST) In-Reply-To: References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> Date: Thu, 29 Jan 2015 11:46:21 +0100 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works From: "Ranjan1018 ." <214748mv@gmail.com> To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Andrew Wilcox , freebsd-current , Konstantin Belousov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 10:46:23 -0000 2015-01-28 10:11 GMT+01:00 Adrian Chadd : > ugh, so because i can't sleep, I read the Linux i915 history for > backlight changes. > > Turns out if I disable bit 30 in ivb_pch_pwm_override() to register > BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings > still don't, but I'll worry about that later. > > Bit 30 in the linux drm code is: > > #define BLM_PCH_OVERRIDE_ENABLE (1 << 30) > > The linux dri code doesn't set that for ivybridge - only for broadwell. > > (also, the linux driver has POSTING_READ() which I'm guessing is to > ensure things made it out to the device and have been flushed before > doing another IO operation.) > > I have my (via sysctl) panel backlight control working again. > > > > -adrian > Thank you guys, the backlight control works again on my laptop with this patch, suggested by Adrian : --- sys/dev/drm2/i915/intel_display.c.orig (revision 277487) +++ sys/dev/drm2/i915/intel_display.c (working copy) @@ -6995,7 +6995,7 @@ */ I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE); I915_WRITE(BLC_PWM_CPU_CTL, 0); - I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (1<<30)); + I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE); } void intel_modeset_init_hw(struct drm_device *dev) but the patch by Andrew does not hurts: http://foxkit.us/FreeBSD/i915-uninitialised-var-fix.diff I am running r277871 with both patches applied. Regards, Maurizio From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 11:39:40 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D6973F6; Thu, 29 Jan 2015 11:39:40 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id 45080C07; Thu, 29 Jan 2015 11:39:39 +0000 (UTC) Received: from bender (c101.sec.cl.cam.ac.uk [128.232.18.101]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id 1837C73000; Thu, 29 Jan 2015 11:39:36 +0000 (UTC) Date: Thu, 29 Jan 2015 11:39:30 +0000 From: Andrew Turner To: "Lundberg, Johannes" Subject: Re: System-On-Module Message-ID: <20150129113930.53cfc2ff@bender> In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Ganbold Tsagaankhuu , Ian Lepore , "freebsd-mobile@freebsd.org" , "freebsd-arm@freebsd.org" , FreeBSD Current , "ticso@cicely.de" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 11:39:40 -0000 On Thu, 29 Jan 2015 18:27:08 +0900 "Lundberg, Johannes" wrote: > What I'm most worried about is the graphics stack.. Some companies > don't seem so keen on handing out specs. The only ARM vendor I know that has released documentation on their 3D hardware is Broadcom [1]. The only options for this are the Raspberry Pi or one of the mobile phones with a Broadcom CPU. I neither option to be applicable for your requirements. Andrew [1] http://www.broadcom.com/docs/support/videocore/VideoCoreIV-AG100-R.pdf From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 12:35:46 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3DDADFC; Thu, 29 Jan 2015 12:35:46 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 44D6821C; Thu, 29 Jan 2015 12:35:45 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t0TCZ8OA048380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 29 Jan 2015 13:35:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t0TCZ6sH036624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2015 13:35:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t0TCZ6hH078644; Thu, 29 Jan 2015 13:35:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t0TCZ50N078643; Thu, 29 Jan 2015 13:35:05 +0100 (CET) (envelope-from ticso) Date: Thu, 29 Jan 2015 13:35:05 +0100 From: Bernd Walter To: Andrew Turner Subject: Re: System-On-Module Message-ID: <20150129123505.GJ73589@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> <20150129113930.53cfc2ff@bender> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150129113930.53cfc2ff@bender> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "Lundberg, Johannes" , Ian Lepore , "freebsd-mobile@freebsd.org" , "freebsd-arm@freebsd.org" , FreeBSD Current , "ticso@cicely.de" , Ganbold Tsagaankhuu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 12:35:46 -0000 On Thu, Jan 29, 2015 at 11:39:30AM +0000, Andrew Turner wrote: > On Thu, 29 Jan 2015 18:27:08 +0900 > "Lundberg, Johannes" wrote: > > > What I'm most worried about is the graphics stack.. Some companies > > don't seem so keen on handing out specs. > > The only ARM vendor I know that has released documentation on their 3D > hardware is Broadcom [1]. The only options for this are the Raspberry > Pi or one of the mobile phones with a Broadcom CPU. I neither option to > be applicable for your requirements. On the other hand people still struggle when it comes to CPI on RPi, because it is handled by the GPU. I'm still not so sure about this Broadcom SoC. This is the reason why I like that the RPi Camera header is also used on the Hummingboard and the BanannaPi. The Hummingboard is an iMX6. The BanannaPi unfortunately is an Allwinner and their datasheets are AFAIK chinese only and IIRC also under NDA. The Novena crown funding included iMX6 2D/3D driver development for Linux as a met stretch goal: https://www.crowdsupply.com/kosagi/novena-open-laptop/stretch-goals https://www.crowdsupply.com/kosagi/novena-open-laptop I don't know how much of the results will be useable for us, but at least some people seem to have access to enough documentation. > Andrew > > [1] > http://www.broadcom.com/docs/support/videocore/VideoCoreIV-AG100-R.pdf -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 13:00:48 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2EB7206; Thu, 29 Jan 2015 13:00:48 +0000 (UTC) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72B3468E; Thu, 29 Jan 2015 13:00:48 +0000 (UTC) Received: by mail-oi0-f43.google.com with SMTP id z81so26330594oif.2; Thu, 29 Jan 2015 05:00:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ehr11UifcJfdb4++jG7mwg9TRuuTaWVpcoR5FhjxbbU=; b=IURQcBrv0+zaEP1La0vwQWW+cuN0w/X4e+c46EZfKeP1uetW0KUc/2U8F4TQtjpyLE CxJJe7TYwVvsA3kpI0TPFZJgQ8GX1svvIQXX3d0bn7aVpLZ3RwwrCDPWK3crBwklH7lq ffKoQJDPFDj6UcBJ0DWeVBAvBIVTfgHfsVQziM35ZvfLiqjaeHZqUDw3rZGI6sVw/lyN W9ATs0eBI0t4WWzdZQneC8h1EejVdelCY90M/ySO05J4gS/B0gri2h9qae929MFEZd/5 rg1NMzh+cxnVAZzX9mWq7mO46oky6eW9mh9HGD0FSEWtgqA/TpROZXb3HLkZO5l6eIYO MZGg== MIME-Version: 1.0 X-Received: by 10.182.119.232 with SMTP id kx8mr252573obb.37.1422536447544; Thu, 29 Jan 2015 05:00:47 -0800 (PST) Received: by 10.182.13.33 with HTTP; Thu, 29 Jan 2015 05:00:47 -0800 (PST) In-Reply-To: References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> <20150129023314.GH73589@cicely7.cicely.de> Date: Thu, 29 Jan 2015 21:00:47 +0800 Message-ID: Subject: Re: System-On-Module From: Ganbold Tsagaankhuu To: "Lundberg, Johannes" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , "ticso@cicely.de" , Ian Lepore , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 13:00:48 -0000 On Thu, Jan 29, 2015 at 5:27 PM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > What I'm most worried about is the graphics stack.. Some companies don't > seem so keen on handing out specs. I think you can check some open source implementations for those GPU related things (only for linux maybe): For Vivante: https://github.com/laanwj/etna_viv/wiki For Adreno: http://freedreno.github.io For Mali: http://limadriver.org I guess they are mostly based on reverse engineering effort. I think you can even ask about the statuses directly from the authors/maintainers on some irc channel. Not sure about Tegra or PowerVR. Ganbold > > > On Thursday, January 29, 2015, Ganbold Tsagaankhuu > wrote: > >> >> >> On Thu, Jan 29, 2015 at 4:18 PM, Lundberg, Johannes < >> johannes@brilliantservice.co.jp> wrote: >> >>> Hi All >>> >>> Thanks again for all the replies. >>> >>> How is the support for A15 and how is Qualcomm to work with when it com= es >>> to porting? >>> >>> Thinking about this guy which is closer to what I want spec-wise.. >>> >>> http://www.variscite.com/products/system-on-module-som/cortex-a15-krait= /var-som-sd600-cpu-qualcomm-snapdragon600 >>> >>> >>> >> I think IFC6410 has same SoC as above SoM and as for ifc6410 either >> mmc/sd or usb ehci driver needed in order to boot FreeBSD into multi use= r >> mode. >> >> Ganbold >> >> >> >>> >>> -- >>> Johannes Lundberg >>> BRILLIANTSERVICE CO., LTD. >>> >>> On Thu, Jan 29, 2015 at 11:33 AM, Bernd Walter >>> wrote: >>> >>> > On Wed, Jan 28, 2015 at 05:36:00PM -0700, Ian Lepore wrote: >>> > > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: >>> > > > Ah now I see it has EDM connection. I didn't look carefully enoug= h. >>> > All the >>> > > > images are with the expansion board attached.. >>> > > > >>> > > > Spec-wise and portability-wise it seems like a good option but my >>> > hardware >>> > > > guy keeps warning me about Freescale that they often have hardwar= e >>> > bugs and >>> > > > rather than fixing the bugs they pretend they are not there.. In >>> other >>> > > > words, Freescale is good for software developers because of open >>> > > > documentation but not so for hardware manufactures. Any experienc= es >>> > with >>> > > > this? >>> > > >>> > > The imx6 manuals include an errata list, so it would be good to che= ck >>> > > that for anything specific that would matter to your projects. >>> > >>> > If you use a prebuild module then you don't get much in touch with >>> > the freescale chip fropm the hardware side. >>> > On the other hand, there are countless iMX6 boards out there with >>> > schematics online. >>> > My recently bought Novena even came with printed schematics and they >>> > open sourced the HW design files as well. >>> > I don't think there are hidden surprises on the hardware side. >>> > >>> > > For the devices we use in our products everything is good so far wi= th >>> > > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and >>> lots >>> > > of gpio (inputs and outputs). The ethernet is gigabit but has a >>> known >>> > > limitation of 40MB/s due to the bus it's connected to in the chip. >>> (But >>> > > hey, it's documented so it's not a problem, right? :) >>> > > >>> > > You mentioned video, and we don't have that working on freebsd imx6 >>> yet, >>> > > but there's not a ton of work to do. There's a framebuffer driver >>> for >>> > > imx5 and it has pretty much the same framebuffer hardware. Getting >>> > > video output to a TTL LCD is probably just hours of work. Getting >>> it to >>> > > an LVDS LCD or HDMI probably needs days of work (entire drivers >>> written, >>> > > potentially, I haven't looked into it). >>> > >>> > Sounds interesting for my Novena. >>> > The one I already got are board only (with some FPGA breakout, ...). >>> > They have HDMI though. >>> > But I'm also awaiting for the one with case and LCD panel. >>> > Not to forget that I have a fairy EDM carrier with LCD already. >>> > That said I'v always wondered how much work is it to get the camera >>> > interface running, since the Hummingboards can connect to the RPi >>> > camera modules. >>> > >>> > > Some audio support was recently committed, but I don't know much >>> about >>> > > it yet. >>> > > >>> > > -- Ian >>> > > >>> > > >>> > >>> > -- >>> > B.Walter http://www.bwct.de >>> > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. >>> > >>> >>> -- >>> =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >>> =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81= =A6=EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB= =E3=81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3= =81=97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7= =98=E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA= =E3=82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3= =81=BE=E3=81=99=E3=80=82 >>> =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4= =96=E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F= =E5=A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81= =AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80= =E5=88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >>> =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81= =AE=E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF= =E8=A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3= =81=84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82= =8C=E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3= =E3=81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >>> --- >>> CONFIDENTIALITY NOTE: The information in this email is confidential >>> and intended solely for the addressee. >>> Disclosure, copying, distribution or any other action of use of this >>> email by person other than intended recipient, is prohibited. >>> If you are not the intended recipient and have received this email in >>> error, please destroy the original message. >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to " >>> freebsd-current-unsubscribe@freebsd.org" >> >> >> > > -- > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. > > > =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 > =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 > =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 > --- > CONFIDENTIALITY NOTE: The information in this email is confidential > and intended solely for the addressee. > Disclosure, copying, distribution or any other action of use of this > email by person other than intended recipient, is prohibited. > If you are not the intended recipient and have received this email in > error, please destroy the original message. > From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 18:35:31 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 099DF749 for ; Thu, 29 Jan 2015 18:35:31 +0000 (UTC) Received: from graal.it-profi.org.ua (graal.shurik.kiev.ua [193.239.74.7]) (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 B01C62F7 for ; Thu, 29 Jan 2015 18:35:29 +0000 (UTC) Received: from [46.164.154.106] (helo=thinkpad.it-profi.org.ua) by graal.it-profi.org.ua with esmtpa (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YGtez-000EED-RN for freebsd-current@freebsd.org; Thu, 29 Jan 2015 20:17:45 +0200 Message-ID: <54CA7949.6060202@shurik.kiev.ua> Date: Thu, 29 Jan 2015 20:17:45 +0200 From: Alexandr Krivulya User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 46.164.154.106 X-SA-Exim-Mail-From: shuriku@shurik.kiev.ua X-SA-Exim-Scanned: No (on graal.it-profi.org.ua); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 18:35:31 -0000 29.01.2015 12:46, Ranjan1018 . пишет: > 2015-01-28 10:11 GMT+01:00 Adrian Chadd : > >> ugh, so because i can't sleep, I read the Linux i915 history for >> backlight changes. >> >> Turns out if I disable bit 30 in ivb_pch_pwm_override() to register >> BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings >> still don't, but I'll worry about that later. >> >> Bit 30 in the linux drm code is: >> >> #define BLM_PCH_OVERRIDE_ENABLE (1 << 30) >> >> The linux dri code doesn't set that for ivybridge - only for broadwell. >> >> (also, the linux driver has POSTING_READ() which I'm guessing is to >> ensure things made it out to the device and have been flushed before >> doing another IO operation.) >> >> I have my (via sysctl) panel backlight control working again. >> >> >> >> -adrian >> > Thank you guys, > the backlight control works again on my laptop with this patch, suggested > by Adrian : > > --- sys/dev/drm2/i915/intel_display.c.orig (revision 277487) > +++ sys/dev/drm2/i915/intel_display.c (working copy) > @@ -6995,7 +6995,7 @@ > */ > I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE); > I915_WRITE(BLC_PWM_CPU_CTL, 0); > - I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (1<<30)); > + I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE); > } > > void intel_modeset_init_hw(struct drm_device *dev) > This patch fixes problem for me too, but only when acpi_video module is not loaded. With acpi_video loaded I still see this errors (but it's probably another topic): Jan 29 19:02:27 thinkpad kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000FF) is beyond end of object (length 0x16) (20140926/exoparg2-452) Jan 29 19:02:27 thinkpad kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BRNS] (Node 0xfffff80007541b00), AE_AML_PACKAGE_LIMIT (20140926/psparse-552) Jan 29 19:02:27 thinkpad kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.VID_.LCD0._BCM] (Node 0xfffff80007550280), AE_AML_PACKAGE_LIMIT (20140926/psparse-552) Jan 29 19:02:27 thinkpad kernel: can't evaluate \_SB_.PCI0.VID_.LCD0._BCM - AE_AML_PACKAGE_LIMIT From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 18:52:45 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30AB4FEB for ; Thu, 29 Jan 2015 18:52:45 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE68D77A for ; Thu, 29 Jan 2015 18:52:44 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1YGuCi-001TsA-2o>; Thu, 29 Jan 2015 19:52:36 +0100 Received: from e179185229.adsl.alicedsl.de ([85.179.185.229] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1YGuCi-0015zl-08>; Thu, 29 Jan 2015 19:52:36 +0100 Date: Thu, 29 Jan 2015 19:52:30 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: i915kms.ko: when loaded with Haswell HD4600, display goes blank Message-ID: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/TrAZs2JAQMc_ySxa1HVXaeN"; protocol="application/pgp-signature" X-Originating-IP: 85.179.185.229 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 18:52:45 -0000 --Sig_/TrAZs2JAQMc_ySxa1HVXaeN Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Having trouble with loading i915kms.ko on a Haswell-based Lenovo ThinkPad E= 540. The laptop is equippted with a Intel i5-4200M CPU with integrated HD4600 iGPU. = Recent update of CURRENT and loading of i915kms.ko turns the display immediately blank. L= aptop is accessible via ssh and network. Only display is dead. I suppose this a bug? regards, oh=20 --Sig_/TrAZs2JAQMc_ySxa1HVXaeN Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUyoFvAAoJEOgBcD7A/5N8EvgH/iFz6mzYYnDvuoDQUwuQep5p dfg4rhHafAmmxaVcQCXDKxAj0DXllO9zruarZR6HHIsmXUaYYTgkfdAAjWSUHxqa rj4RiL+34lbUokQdD3hPYMYCTHp1agDHo3pxR2iK7zJzhkz03nRlYdG7yAjLWbsJ sLM9/JYSGqV4bUWU6d7jms8D7hAu7l2KU6PklgUXRoSYsdNG/cUhxyIsaCg6QE1n ppp4ruEpvFAgL/u/i4sZPwYGK5o/GcFNzIn1wEYpyo34FViD/YDGY/GEoRZPx4zX TudY1gWwyk6I4EZLP52bjDWrFwGJFR+41NbsO7Gu+puRAraZHsqQA1YOryNzTjs= =IM6J -----END PGP SIGNATURE----- --Sig_/TrAZs2JAQMc_ySxa1HVXaeN-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:18:48 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 991CC3E0 for ; Thu, 29 Jan 2015 19:18:48 +0000 (UTC) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36344A60 for ; Thu, 29 Jan 2015 19:18:48 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id rd18so37525622iec.7 for ; Thu, 29 Jan 2015 11:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qdzSQQW5/Xlffk5aqklerQkYXbJoovqNSNXmkH0tvBo=; b=JVTimz3FyzigHS9FK9l+eC4A8JaLKvqHLQeEkN0ZA1skk/Vb3aSSwSpKn8owTGp/Cg I6BhqBFqKQ9XdVy4LLFQ6nV89yX8qpK+Ts3YUyxGw6KckP9MLdMV5pKjvt7m7fA4d8+i Sw3wg9+BAgOTT3SqlFXBv68uJJSk3vqKfcQbseR0Dy2adlQMre035fipu15gsvzIUftM zDzFM5byaAp7GT3bAbI1rb+21sRlyERss7ul9w2sYRfpbHBsAJWKuvOsluWaZit48sM5 r7Xh5K+vr5bNJM6JKmLp7liXczqWN7cWP/BvKwVEbFD8kmqqLDDjqhuQDERxuqTKbqJU 6N9w== MIME-Version: 1.0 X-Received: by 10.107.15.138 with SMTP id 10mr2665641iop.57.1422559126594; Thu, 29 Jan 2015 11:18:46 -0800 (PST) Received: by 10.50.182.233 with HTTP; Thu, 29 Jan 2015 11:18:46 -0800 (PST) In-Reply-To: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> References: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> Date: Thu, 29 Jan 2015 11:18:46 -0800 Message-ID: Subject: Re: i915kms.ko: when loaded with Haswell HD4600, display goes blank From: NGie Cooper To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 19:18:48 -0000 On Thu, Jan 29, 2015 at 10:52 AM, O. Hartmann wrote: > > Having trouble with loading i915kms.ko on a Haswell-based Lenovo ThinkPad E540. The > laptop is equippted with a Intel i5-4200M CPU with integrated HD4600 iGPU. Recent update > of CURRENT and loading of i915kms.ko turns the display immediately blank. Laptop is > accessible via ssh and network. Only display is dead. > > I suppose this a bug? Yes, very much so. What's your svn revision and can you please create a bug for this issue? From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:19:39 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80DE1520 for ; Thu, 29 Jan 2015 19:19:39 +0000 (UTC) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48AD6A8E for ; Thu, 29 Jan 2015 19:19:39 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id ar1so37995518iec.6 for ; Thu, 29 Jan 2015 11:19:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UqNZ9u8am2aiyrOTEh3vU+RI6fGjpSqm5ms3IVIB+ac=; b=1H3rmlq12+j3erX2yeSg3VYqLg1LMq4OX9xTWkuTH5f4Ovs8Dg2CRIlJ/eME2H8VOK kzpJ8+RoU21m8yUbqUevtFRgBGUrA0PahHo/jIWcu0yxBv9ZO34q5GWrXCpaWiiLlgYX PCzQpmV0BxwjshOfv8EndMHuUYLx8dxiNwA3qqYG7HavueAaftNHUn0lgRw1401JHVkD p9d/xj88BKFBB/Jp3QmzaEtT1PguQqcmyp8btAuD2NvR+timUbB2GqrVXqbxH3cg4Kqo 1nqxHjX/t/rykiULxQS/Xlcz+aVhElJN6CKonOd4VjV+nia+16vADCEWOdO5h8LXv51Z OvLw== MIME-Version: 1.0 X-Received: by 10.43.66.9 with SMTP id xo9mr2203536icb.67.1422559178697; Thu, 29 Jan 2015 11:19:38 -0800 (PST) Received: by 10.50.182.233 with HTTP; Thu, 29 Jan 2015 11:19:38 -0800 (PST) In-Reply-To: References: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> Date: Thu, 29 Jan 2015 11:19:38 -0800 Message-ID: Subject: Re: i915kms.ko: when loaded with Haswell HD4600, display goes blank From: NGie Cooper To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 19:19:39 -0000 On Thu, Jan 29, 2015 at 11:18 AM, NGie Cooper wrote: > On Thu, Jan 29, 2015 at 10:52 AM, O. Hartmann > wrote: >> >> Having trouble with loading i915kms.ko on a Haswell-based Lenovo ThinkPad E540. The >> laptop is equippted with a Intel i5-4200M CPU with integrated HD4600 iGPU. Recent update >> of CURRENT and loading of i915kms.ko turns the display immediately blank. Laptop is >> accessible via ssh and network. Only display is dead. >> >> I suppose this a bug? > > Yes, very much so. What's your svn revision and can you please create > a bug for this issue? Please also read the thread titled "drm2 regression: backlight adjustment on ivybridge no longer works" first to see if the symptoms describe there match your's. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:56:17 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA62D14 for ; Thu, 29 Jan 2015 22:56:17 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6040075E for ; Thu, 29 Jan 2015 22:56:17 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1YGy0U-002ZId-Gr>; Thu, 29 Jan 2015 23:56:14 +0100 Received: from e179185229.adsl.alicedsl.de ([85.179.185.229] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1YGy0U-001ciN-Ca>; Thu, 29 Jan 2015 23:56:14 +0100 Date: Thu, 29 Jan 2015 23:56:13 +0100 From: "O. Hartmann" To: NGie Cooper Subject: Re: i915kms.ko: when loaded with Haswell HD4600, display goes blank Message-ID: <20150129235613.6abe495a.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Sa9QnHNF78rU2y_dEhbf4e3"; protocol="application/pgp-signature" X-Originating-IP: 85.179.185.229 X-ZEDAT-Hint: A Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 22:56:17 -0000 --Sig_/Sa9QnHNF78rU2y_dEhbf4e3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 29 Jan 2015 11:19:38 -0800 NGie Cooper schrieb: > On Thu, Jan 29, 2015 at 11:18 AM, NGie Cooper wro= te: > > On Thu, Jan 29, 2015 at 10:52 AM, O. Hartmann > > wrote: > >> > >> Having trouble with loading i915kms.ko on a Haswell-based Lenovo Think= Pad E540. The > >> laptop is equippted with a Intel i5-4200M CPU with integrated HD4600 i= GPU. Recent > >> update of CURRENT and loading of i915kms.ko turns the display immediat= ely blank. > >> Laptop is accessible via ssh and network. Only display is dead. > >> > >> I suppose this a bug? > > > > Yes, very much so. What's your svn revision and can you please create > > a bug for this issue? >=20 > Please also read the thread titled "drm2 regression: backlight > adjustment on ivybridge no longer works" first to see if the symptoms > describe there match your's. That is useless, since the reported symptomes do not apply to non-working H= aswell. Since the last update of the OS - today, CURRENT 277900, the high res conso= le is gone and has fallen back to the 800x600 pixel. The same with the X11 server's displa= y resolution. I can not use VESA driver on the Lenovo ThinkPad E540 with i5-4200M, since = it doesn't startup. I have to use xf86-video-scfb which is a pain in the ass. An alternative is to use Ubuntu on the Lenovo E540 and L540 we purchased. --Sig_/Sa9QnHNF78rU2y_dEhbf4e3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUyrqNAAoJEOgBcD7A/5N8SF0H/A0g+N7jyUay88JHb+AntT2Z bGyHM5xCiDdbEnbXkF1vzG1JdrAsfVtsG6ri7JqU2jFB2LTNwxQy2JT0iWQAwLiz zex5s1FVSaKfuSUtZB2nf3A8wyE/nfrXLUMvCTsa/pJO1g3SAsbeA+1ZK2WOAYA0 FtCtDzEb0dgOaZ+be9OEFTnu61/gNkWO+0HDTM0XU8r27xbJwbbfsISdnIoYxC6i 332JdCwXj4E9rpPB6YzBjq1vn9c7tmVyYLVf1xO+Jp++bh61VFclciig6+emeP4b mKVeRmmhAXMGMNge4LqUi6/4GcfC/vTtwWbJCJJxRLSuL/XB2ULKRubAh02/X30= =rGst -----END PGP SIGNATURE----- --Sig_/Sa9QnHNF78rU2y_dEhbf4e3-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 23:26:27 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50E2E5F5 for ; Thu, 29 Jan 2015 23:26:27 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13CBBA56 for ; Thu, 29 Jan 2015 23:26:27 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id vy18so892611iec.8 for ; Thu, 29 Jan 2015 15:26:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/gnZ8GI5UbYyZb/QI9MGkpGesn7pRJwoVKIF3uY4rTY=; b=lDc7hcuDqFzGzWCZksYEPxI3dL5Ffy5voRCEVNiN6jq8P09Mwt+zw3UYKgYy9CEd36 7X0DIs7Uno+eIf+HsWZw9mVhJbK7dv3tHGLukYD4UuXMvNs85G9R5PehMm/2Xu3SCNCs WG6ReYGzJC+69Y/m4ZQYW8T0aSYS1ObzhVwBQEmTrr2X/gYZD3kSGgv5Ea4+InaZqz5V 5OX6NuYxcUi6gu3gtN0GJRpJzrKphxD+GqTgLFoDfh47C1zlhHahChmydFlrAZDWjUjU sKtydpaLDC9x/MRSUVI3zUoPjYaQeRtjEs9KYPbGGWT2G73wUHuC0CcHBsci761D6gAQ ILiA== MIME-Version: 1.0 X-Received: by 10.42.54.5 with SMTP id p5mr3331845icg.37.1422573986511; Thu, 29 Jan 2015 15:26:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Thu, 29 Jan 2015 15:26:26 -0800 (PST) In-Reply-To: <20150129235613.6abe495a.ohartman@zedat.fu-berlin.de> References: <20150129195230.5dd7078f.ohartman@zedat.fu-berlin.de> <20150129235613.6abe495a.ohartman@zedat.fu-berlin.de> Date: Thu, 29 Jan 2015 15:26:26 -0800 X-Google-Sender-Auth: e4GuzGuainFEBza24MIganInCvE Message-ID: Subject: Re: i915kms.ko: when loaded with Haswell HD4600, display goes blank From: Adrian Chadd To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT , NGie Cooper X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 29 Jan 2015 23:26:27 -0000 wait a sec - before the dri2 update, what exactly were you doing? What happened when you loaded i915kms? Nothing should've been found and no i915 driver should've been running There's no haswell support for i915kms, so it shouldn't have worked /at all/. You should've just gotten either vt(4) or sc(4) + vesa as a console, and VESA graphics. As a workaround, you can just not load i915kms, or patch i915kms to not detect your haswell chipset. -adrian From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 02:45:16 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D61DD25E for ; Fri, 30 Jan 2015 02:45:16 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99D40F2B for ; Fri, 30 Jan 2015 02:45:16 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id at20so663814iec.7 for ; Thu, 29 Jan 2015 18:45:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+IqpC+EJ5sSZnowJ+Lafu+cCsyIzsxF4O+i00ire7W8=; b=dcp6psEsJvUl9EPCrLwWOpFl5XwA38pdlRf3liWBSJZv3OHarwngPnJa7JvmniKIAu /b9YbYUzY6849REtpRG81r5j8hQRCgLCPk5O6Rv0E0YVk+W0ib7e0ylI8zW/NfN9RjYB E4zaCWyU0mtOW5b9vzd0TR5quSt606ScA9J+TZnhAl0kS6qKwxVoG/7WvDNil2iZbtAp Lxyiihds+ZlGcLJHq1H70VqKMe4Os4doGlPemZY6Ef+vvUnmb8PShsigOJEhAmtSf0pj 0hJsikm2Pr96g5cyDCquhE7Uz0p9+M8FnbYDWWKItWNeDBV9pfa6o1cjnYOr/JSkODot Od8w== X-Gm-Message-State: ALoCoQlqBkpA+qeWgbTnGCQ/hXeVrBYeCrZbrrG6A7YhuFmp8NaQbRjwQ5ipUsY3xdDzG2X/lQzfJ00i+ZnRDQ3CRlpHFc53vKwgEYIL1F1NmOYbunVYA3y1atsPYsINceUcHqr6YwLm X-Received: by 10.107.12.88 with SMTP id w85mr4774996ioi.28.1422585915327; Thu, 29 Jan 2015 18:45:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.5.136 with HTTP; Thu, 29 Jan 2015 18:44:59 -0800 (PST) In-Reply-To: <1422491760.15718.97.camel@freebsd.org> References: <20150128183231.GI58886@cicely7.cicely.de> <1422473251.15718.70.camel@freebsd.org> <20150128201440.GA73589@cicely7.cicely.de> <1422490013.15718.79.camel@freebsd.org> <1422491760.15718.97.camel@freebsd.org> From: "Lundberg, Johannes" Date: Fri, 30 Jan 2015 11:44:59 +0900 Message-ID: Subject: Re: System-On-Module To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" , FreeBSD Current , ticso@cicely.de, "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 02:45:16 -0000 How about GPU 2D & 3D support for Vivante GC2000? There seem to be some open source driver out there but its GPL.... GPU acceleration for 2D and 3D is a must for us and if it is only a matter of a few programmers time and effort we can invest in it. Can there be any blocking things like proprietary software/hardware etc? -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Jan 29, 2015 at 9:36 AM, Ian Lepore wrote: > On Thu, 2015-01-29 at 09:12 +0900, Lundberg, Johannes wrote: > > Ah now I see it has EDM connection. I didn't look carefully enough. All > the > > images are with the expansion board attached.. > > > > Spec-wise and portability-wise it seems like a good option but my > hardware > > guy keeps warning me about Freescale that they often have hardware bugs > and > > rather than fixing the bugs they pretend they are not there.. In other > > words, Freescale is good for software developers because of open > > documentation but not so for hardware manufactures. Any experiences wit= h > > this? > > The imx6 manuals include an errata list, so it would be good to check > that for anything specific that would matter to your projects. > > For the devices we use in our products everything is good so far with > the hardware. That's emmc, sdcard, ethernet, i2c, uarts, usb, and lots > of gpio (inputs and outputs). The ethernet is gigabit but has a known > limitation of 40MB/s due to the bus it's connected to in the chip. (But > hey, it's documented so it's not a problem, right? :) > > You mentioned video, and we don't have that working on freebsd imx6 yet, > but there's not a ton of work to do. There's a framebuffer driver for > imx5 and it has pretty much the same framebuffer hardware. Getting > video output to a TTL LCD is probably just hours of work. Getting it to > an LVDS LCD or HDMI probably needs days of work (entire drivers written, > potentially, I haven't looked into it). > > Some audio support was recently committed, but I don't know much about > it yet. > > -- Ian > > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 15:17:53 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 584101F7 for ; Fri, 30 Jan 2015 15:17:53 +0000 (UTC) Received: from bigwig.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 3063394C for ; Fri, 30 Jan 2015 15:17:53 +0000 (UTC) Received: from new-host-3.home (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3A25CB913; Fri, 30 Jan 2015 10:17:52 -0500 (EST) Message-ID: <54CBA0A4.30708@FreeBSD.org> Date: Fri, 30 Jan 2015 10:17:56 -0500 From: John Baldwin User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Elizabeth Myers , freebsd-current@freebsd.org Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> In-Reply-To: <54C883E7.4000300@interlinked.me> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 30 Jan 2015 10:17:52 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 15:17:53 -0000 On 1/28/15 1:38 AM, Elizabeth Myers wrote: > Hello, > > I want to add backlight support to the i915 driver in FreeBSD. It seems > that two magic addresses are read and wrote from to change the backlight > itself. It supports rather fine-level granularity all the way down to > zero. Right now I use a hacked-up userland program that reads > from/writes to these addresses, which is far from an ideal solution. > > I am interested in this because the acpi_video(4) driver does not > support my backlight on my Dell Inspiron 15 3521 (not terribly > suprising, on Linux I needed a special Dell-specific driver, and I'm not > sure even that really used ACPI, I never really checked). > > My questions are really twofold: > > 1) How can this be exposed appropriately? I would prefer this be exposed > generally so upower could grok it. As far as I can tell upower uses > hw.acpi.video.lcd0 to control backlight. I am not sure that upower is > doing the "right" thing here, though. > 2) Where would the code go for this? The dri2 driver seems the most > "logical" place, but maybe it belongs in X and exposed via a program? Or > something else entirely that I'm not thinking of? > > I have experience developing PCI drivers and doing other PCI related > doodads, and some kernel development experience, as well as general C > experience, but I'm not by any means an expert on the matter. Humm. If the code is going to live in the drm driver, then I would start with hanging a sysctl off of the drm device itself. (Each new-bus device_t has a sysctl ctx you can get to hang new nodes off of the device's node.) -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 15:20:40 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7CD9D3FB; Fri, 30 Jan 2015 15:20:40 +0000 (UTC) Received: from bigwig.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 55726A22; Fri, 30 Jan 2015 15:20:40 +0000 (UTC) Received: from new-host-3.home (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 59D80B94E; Fri, 30 Jan 2015 10:20:39 -0500 (EST) Message-ID: <54CBA14B.7030608@FreeBSD.org> Date: Fri, 30 Jan 2015 10:20:43 -0500 From: John Baldwin User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Yue Chen , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: How to know the address ranges of kernel stacks, for user processes and kernel threads? References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 30 Jan 2015 10:20:39 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 15:20:40 -0000 On 1/28/15 7:54 PM, Yue Chen wrote: > How can we know the kernel stack ranges for user process and kernel threads > under FreeBSD x86_64? > > It seems that each kernel stack has two pages (IA-32) to use. Does x86_64 > still have two pages or more? And how can we find the address of these two > pages from a kernel module? In 'struct thread' there is td_kstack_pages and td_kstack. If you grep for those and see where they are initialized that will lead you to find in the source what the defaults are for amd64 (and you can also use those in your kernel module). Note that some kthreads have a different sized stack, so using the members in struct thread is probably what you want to do regardless. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 17:35:45 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1CE25B3; Fri, 30 Jan 2015 17:35:45 +0000 (UTC) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B330DA9; Fri, 30 Jan 2015 17:35:45 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id a108so39184786qge.12; Fri, 30 Jan 2015 09:35:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=ki9qHUHuVxZQdXpgdMvDsvsQANniGgvyCfhF8esY3Qo=; b=HALVAf47rYIwT1zlgHvZPgoHnWxQUNinmc+HFQYIxX2JpwMS8vy1pHMqamYiGiQG63 vyv2XTau1Kw8dYKwJtZoYgASXwPCIX2sNohtU6ZxC2cPrCE4H51JjLPRVtkuwaqPZald 2pEk0YY72GjKbTgdSJiVwzP5vE2upldFNq45OjngHcipWlAeVxebq5W8F7GpsH0lTsQZ WdWLBY922LkharsCq6XuycVYi4aXa/p4xJMsN9GaRoDnucBMtr88NDIrNnXxs/4U+PZZ AhgOUZMsSVLauqlUzIN32dWIDZ5kP7tymZllYy85nZvmOlRQJE1aSqIcKlOBRykRCVkk X3OA== X-Received: by 10.140.94.6 with SMTP id f6mr13801708qge.38.1422639344656; Fri, 30 Jan 2015 09:35:44 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.140.39.209 with HTTP; Fri, 30 Jan 2015 09:35:24 -0800 (PST) In-Reply-To: References: From: Ed Maste Date: Fri, 30 Jan 2015 12:35:24 -0500 X-Google-Sender-Auth: rkA2u2MKqJIO_DCb74QKiYhECWg Message-ID: Subject: Re: UEFI boot hangs with MINNOWBOARD To: Luca Pizzamiglio Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Hackers , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 17:35:46 -0000 On 30 January 2015 at 10:57, Luca Pizzamiglio wrote: > Hi, > I'm testing CURRENT on a MINNOWBOARD > (http://www.elinux.org/Minnowboard:MinnowMax): > > Dual-core atom E3825 CPU > EFI Version: 2.4.0 > EFI: EDK II > > boot1.efi starts, it can found the ufs partition with loader.efi > loader.efi fails at BT->ExitBootServices() (elf64_exec() of > sys/boot/amd64/efi/elf64_freebsd.c) Which revision are you testing, and do you have any local changes? I built a plain -current USB stick image a while back and had no trouble, when using the HDMI output. I don't recall the revision at the moment, but will try again soon. Serial console won't work because the UARTs are not quite 16550-compatible. We do need a GetMemoryMap() / ExitBootServices() retry though. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 15:58:04 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83C5A77; Fri, 30 Jan 2015 15:58:04 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F16ADA9; Fri, 30 Jan 2015 15:58:04 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id vy18so4249865iec.8; Fri, 30 Jan 2015 07:58:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=j51aJMmoaOznEmcl2tLJgKsqM3BoU8PlfHGN1X8AOQo=; b=E717DpIy0Z2m3qiYclNOKdaOvucYoiegPtTOFrOeAK0YBpO5yT9Hqk+j/QDnQaDcLM O/hQ/WLqeqLhd/yBxjKq/0DO9h6IwyBE1ThFvD3x1UuRK0XwOdjz5z0qNOdzKs0pZ7oR /o48bqu1qmRI8k/94zJfr8PanPsUbxdgQ/dBGzQ87GvWO2uk+/UhQtBCTiPs9NwCZdQD MMNgov86QqepKExULT1xzp9BauJ9NiGXionQo8zIoKJbKVkYSx5/BP9znCF1M0q82g+g LyRij/EoGeDBqKMgxGtQfsxrPWysg5Q3VPoDzJ+tGO0YMpEf4XPEuOAY1gt0OHUCCtjU hZpQ== X-Received: by 10.42.249.2 with SMTP id mi2mr6741516icb.36.1422633483782; Fri, 30 Jan 2015 07:58:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.91.193 with HTTP; Fri, 30 Jan 2015 07:57:43 -0800 (PST) From: Luca Pizzamiglio Date: Fri, 30 Jan 2015 16:57:43 +0100 Message-ID: Subject: UEFI boot hangs with MINNOWBOARD To: FreeBSD Hackers , freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Fri, 30 Jan 2015 18:17:34 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 15:58:04 -0000 Hi, I'm testing CURRENT on a MINNOWBOARD (http://www.elinux.org/Minnowboard:MinnowMax): Dual-core atom E3825 CPU EFI Version: 2.4.0 EFI: EDK II boot1.efi starts, it can found the ufs partition with loader.efi loader.efi fails at BT->ExitBootServices() (elf64_exec() of sys/boot/amd64/efi/elf64_freebsd.c) ExitBootServices() fails with error code 2 (INVALID_PARAMETER). The documentation of this function (http://wiki.phoenix.com/wiki/index.php/EFI_BOOT_SERVICES#ExitBootServices.28.29) states that the mapKey is wrong and GetMemoryMap() should be recall and then ExitBootServices() again. I've tried to implement it, but it fails again. My main problem is that I don't know which parameter should I pass to GetMemoryMap() I gave a look to this discussion (http://www.gossamer-threads.com/lists/linux/kernel/1733014) about "retry ExitBootServices() on failure" about eboot in Linux: they do a retry (only one) and they call also a FreePoll(). Do you have any tips, suggestions or something that could help to get FreeBSD boot on this apparently standard board? Best regards, Luca Pizzamiglio PS: should we implement the ExitBootServices() retry? From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 20:43:28 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 051D25AA for ; Fri, 30 Jan 2015 20:43:28 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B16A2617 for ; Fri, 30 Jan 2015 20:43:27 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id x12so21647400qac.11 for ; Fri, 30 Jan 2015 12:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=PX23GCK0mRHtIL1aeGiQqA3tC5gvCgCh2JZk9M7PU1U=; b=M2Sd+wDEBhE51iOMOGSIRq9gOamyeiLU2v8qK7HW+auvU3LHANzbS4O9roP0aj6c8n o240oRQnD4+hGueodPJiuo6VvjGXtbFkhdHT15vZlQYWjOyU43zfZ7GDyNUiDY5WpTZ7 w4tWEAUf0Nh734/Ddy2AxgY6b6faEbUFEGquM8nBYPDIxisLslmP2IFIcHCRHMbDTOeB IT2AHHCHB4Gv11HEVhsk5e5OZfxXKDGalY600LIbPRl9bR4oPRCrE6ehP2vQdg0nuURy vL6wJ6R7UGwytPJzjZaZdm9zSFHHHHuomLeQHdH5UVo63PtoFpmORx5Fb3JFCpbcIPx/ pGlg== X-Received: by 10.224.75.71 with SMTP id x7mr16299463qaj.90.1422650606795; Fri, 30 Jan 2015 12:43:26 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.140.39.209 with HTTP; Fri, 30 Jan 2015 12:43:06 -0800 (PST) In-Reply-To: References: From: Ed Maste Date: Fri, 30 Jan 2015 15:43:06 -0500 X-Google-Sender-Auth: wMG60uJTIPUU6Cu039eCquTKK_s Message-ID: Subject: Re: UEFI boot hangs with MINNOWBOARD To: Luca Pizzamiglio Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 20:43:28 -0000 On 30 January 2015 at 12:35, Ed Maste wrote: > > I built a plain -current USB stick image a while back and had no > trouble, when using the HDMI output. I don't recall the revision at > the moment, but will try again soon. Serial console won't work because > the UARTs are not quite 16550-compatible. I just checked on a build at r277612 (a week old) and had no trouble. For reference the not-yet-working UARTs are: none7@pci0:0:30:3: class=0x078000 card=0x72708086 chip-0x0f0a8086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'ValleyView LPIO1 HSUART Controller' class = simple comms none8@pci0:0:30:4: class=0x078000 card=0x72708086 chip-0x0f0c8086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'ValleyView LPIO1 HSUART Controller' class = simple comms From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:12:53 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70EEB6BA for ; Fri, 30 Jan 2015 22:12:53 +0000 (UTC) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F37AFEBD for ; Fri, 30 Jan 2015 22:12:52 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id w62so29513080wes.7 for ; Fri, 30 Jan 2015 14:12:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=YHNMV4DYbIJEr/hSjcRqPX7PnSb8oG3cwk9tPwhxtXw=; b=M15oNjYfTnaYVsbQLMuNsO4GEMcRVcuQhCv8QaRGiyn6UxpOLuiqyQPzX4xXr77pup sQ2loKZAZXkl+pHa3QO8BnYhNCSRN+EiFaeBKStxnt2z1uLI0JCw56KNIlIxcLWX+WVP DoHXTSGbh4m6m+FTtq4/Ad+wQdikvbmUP+NAy4+pIynl5n+/BSaYyQmpJSycE6w6V2MV J6ZrNAHmv+vCGGnYB3c8mumYYkI5Phz56c5a9/lsrVYAr5SdFsJVKrbmfN+hHzItk5th T+1jTc2s7PB1YUQ8UBK+u7m9gWlSiQOAQHcxb+kO9VWDt6orUY8toEL00wXFzq7n8eBJ Bhbg== X-Received: by 10.194.57.43 with SMTP id f11mr16314317wjq.6.1422655971347; Fri, 30 Jan 2015 14:12:51 -0800 (PST) Received: from brick.home (acui16.neoplus.adsl.tpnet.pl. [83.11.88.16]) by mx.google.com with ESMTPSA id hn2sm16706510wjc.5.2015.01.30.14.12.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 14:12:50 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 30 Jan 2015 23:12:48 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Konstantin Belousov Subject: Re: Suspend/resume with i915. Message-ID: <20150130221248.GA8489@brick.home> Mail-Followup-To: Konstantin Belousov , current@FreeBSD.org References: <20150122110201.GA3996@brick.home> <20150123084057.GD42409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150123084057.GD42409@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 22:12:53 -0000 On 0123T1040, Konstantin Belousov wrote: > On Thu, Jan 22, 2015 at 12:02:01PM +0100, Edward Tomasz Napiera??a wrote: > > I'm trying to fix resume on my T61, broken by some change several > > months ago; according to pciconf it's 'Mobile GM965/GL960 Integrated > > Graphics Controller (primary)'. It's running current CURRENT and > > up to date packages. > > > > Suspend and resume makes Xorg do something weird - there is screen > > corruption, or rather window corruption. The GNOME 3 desktop looks > > pretty normal, except that gnome-terminal (launched before suspend) > > window looks as if the buffer layout changed underneath it; for example, > > instead of one flashing cursor there are several, horizontally, across > > the window. New windows are simply black. No segv. > > > > Setting kern.vt.suspendswitch=0 makes the behaviour disappear, replaced > > by segmentation faults of gnome-shell. With stock gdb it looks like this: > > At least one big known issue with suspend is that userspace activity > is not stopped, which makes the driver suspend code operating on the > non-steady state of devices. > > I committed the facility to stop userspace before suspend, and avg promised > to integrate this into suspend path, but he did not. You might try to > search mailing lists for reference to his earlier patch. Unfortunately stuff was committed before I could test it. Fortunately, it's all fixed now, and works perfectly, on 11-CURRENT. Thanks! :-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:25:20 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A391D86F for ; Fri, 30 Jan 2015 22:25:20 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 66B30FAF for ; Fri, 30 Jan 2015 22:25:20 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id E28903B8B7 for ; Fri, 30 Jan 2015 22:25:11 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id t0UMOoiW002534 for ; Fri, 30 Jan 2015 22:25:09 GMT (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org Subject: Bug-report of sorts... From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2500.1422656498.1@critter.freebsd.dk> Date: Fri, 30 Jan 2015 22:24:50 +0000 Message-ID: <2533.1422656690@critter.freebsd.dk> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 22:25:20 -0000 I'm at a hotel in Bruxelles right now, and the cordially provided free wireless is a lot less useful than it can be, because my FreeBSD box can't seem to do DNS lookups on it. It's one of those "captive portal" kind of things where you get a DHCP reply with a DNS server which lies to you until you agree to the T&C on a web-page. But the point is I never get to the webpage, local_unbound just doesn't seem to be able to resolve anything through the DHCP appointed server, despite the fact that dig(1) does so just fine. I have no idea what goes wrong or why it goes wrong, local_unbound does not seem to record anything in syslog about failures. I'm here for a couple of days (as are, I belive, another couple of FreeBSD people) in case anybody has any ideas to try... Input welcome... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:42:52 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47485A93 for ; Fri, 30 Jan 2015 22:42:52 +0000 (UTC) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps.rulingia.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BBEC11C0 for ; Fri, 30 Jan 2015 22:42:51 +0000 (UTC) Received: from server.rulingia.com (c220-239-242-83.belrs5.nsw.optusnet.com.au [220.239.242.83]) by vps.rulingia.com (8.14.9/8.14.9) with ESMTP id t0UMggcX079709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 31 Jan 2015 09:42:48 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.9/8.14.9) with ESMTP id t0UMgaHt010963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 31 Jan 2015 09:42:36 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.9/8.14.9/Submit) id t0UMgadv010962; Sat, 31 Jan 2015 09:42:36 +1100 (AEDT) (envelope-from peter) Date: Sat, 31 Jan 2015 09:42:36 +1100 From: Peter Jeremy To: Poul-Henning Kamp Subject: Re: Bug-report of sorts... Message-ID: <20150130224236.GA8324@server.rulingia.com> References: <2533.1422656690@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <2533.1422656690@critter.freebsd.dk> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.23 (2014-03-12) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 22:42:52 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2015-Jan-30 22:24:50 +0000, Poul-Henning Kamp wrote: >But the point is I never get to the webpage, local_unbound just doesn't >seem to be able to resolve anything through the DHCP appointed server, >despite the fact that dig(1) does so just fine. How about some packet captures showing the request/response differences between dig(1) and local_unbound? --=20 Peter Jeremy --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUzAjbXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0MxIP/2LHPIrR6ce9PGEYeckGQlgN biJpg/jyKuYpiAPSFIjMV0nYz2nGu+MXC8J4YK6fkdqFVRe3q4iRUID/ntDYhaCW nkR1pSYiZQkBu/FPdBdO7BFvAocE9xHaconEfZ4ganjmAuK64cwZQcyyR73qrK4O aHoON/9B3DfzaYxkE1ZZ5QPbMaG5D2xMDNt71md/wHrTF+CRYBDjH7HSxeT8LFQm dJ7hMwbPOt1KwG9yY6PfylchA0pQ6l/oJVOETiRqQwi2tIVPnGcMsAztfYUnDbWW pv4D26xdTOn1rb7xmTru9gpEO5+fijyS5gh8ltfW/ZhsNofqjnKo7QiMHFz3UeUA TivSDm6jUEhVCgZUMxGMsu3ATNUE2pbrUiyy9WnYj6utGOXoJ2k+WigV/VRj8Jmd E3Z3xD9a7K8vjw6k+DESZ/rOwO3ETJzI4w8mQz5tH2MLfsI1uVh/NAJKVIMB9L6D 2NMEGxCibUyf02oPqKo1dQwQfafisqAro4IObYChdNkKStouYAi+bXQdVp6GzpB+ 28uXz3bu/qdz+2YIrNHaOrhXNa4O3B6ZRabtpZN4kMWznTzIg84EYNcvNwRHmoKQ I6NrH+qXoRpIrEnx8lTW8laZoaUywb2e9Icq3svBzZs0K5dZajMe63TddIfAU9Gd D2PaEFIzKevhxedZZ9FK =xDeQ -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:45:54 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECFC2BBC for ; Fri, 30 Jan 2015 22:45:54 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 897FD1E4 for ; Fri, 30 Jan 2015 22:45:53 +0000 (UTC) Received: (qmail 6068 invoked from network); 30 Jan 2015 22:47:03 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 30 Jan 2015 22:47:03 -0000 Message-ID: <54CC0999.90500@interlinked.me> Date: Fri, 30 Jan 2015 16:45:45 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: John Baldwin , freebsd-current@freebsd.org Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CBA0A4.30708@FreeBSD.org> In-Reply-To: <54CBA0A4.30708@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 22:45:55 -0000 On 01/30/15 09:17, John Baldwin wrote: > Humm. If the code is going to live in the drm driver, then I would > start with hanging a sysctl off of the drm device itself. (Each new-bus > device_t has a sysctl ctx you can get to hang new nodes off of the > device's node.) I'm wondering if that's the correct place for it to live. So far it's the only real place it *can* live that makes logical sense imho, unless anyone has better ideas. This is awesome. As for upower, it should probably be patched to know about other types of brightness sysctls if/when this is implemented. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:12:42 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D08316C; Fri, 30 Jan 2015 23:12:42 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 797FB697; Fri, 30 Jan 2015 23:12:42 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 2342EF32; Fri, 30 Jan 2015 23:12:41 +0000 (UTC) Date: Fri, 30 Jan 2015 23:12:40 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org, nwhitehorn@FreeBSD.org, pfg@FreeBSD.org, grembo@FreeBSD.org Message-ID: <26487026.16.1422659561748.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_HEAD #2282 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Jenkins-Job: FreeBSD_HEAD X-Jenkins-Result: FAILURE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 23:12:42 -0000 See Changes: [nwhitehorn] Use MBR by default on BIOS systems. An increasing number of mo= therboards assume that GPT means UEFI boot, resulting in the installation of uninstallable systems. This needs a little more work before MFC, in particular based on disk size (> 2 TB + BIOS + MBR is not workable). That will come soon. [grembo] New function smbios_match to detect BIOS versions during boot Motivation is to introduce BIOS specific quirks early in the boot process. smbios_match can be called before malloc is avaible, that's why parts of smbios_detect have been moved into a separate function smbios_probe that will be called by smbios_detect as well as smbios_match. Reviewed by:=09jhb Approved by:=09jhb Differential Revision: =09https://reviews.freebsd.org/D1679 [pfg] msun: use previously ignored value. This fixes evaluation of exceptional values in scalblnl(). While here, simplify the code as suggested by Bruce Evans. Reported by:=09clang static analyzer MFC after:=091 week ------------------------------------------ [...truncated 172127 lines...] cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_pad.po --- sys.all__D --- --- biosdisk.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o biosdisk.o --- secure.all__D --- --- kexecdh.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o kexecdh.po --- lib.all__D --- --- lib_printw.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_printw.po --- sys.all__D --- --- biosmem.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o biosmem.o --- secure.all__D --- --- kexecdhc.po --- --- lib.all__D --- --- lib_redrawln.po --- --- secure.all__D --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o kexecdhc.po --- lib.all__D --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_redrawln.po --- sys.all__D --- --- biospnp.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o biospnp.o --- biospci.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o biospci.o --- lib.all__D --- --- lib_refresh.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_refresh.po --- secure.all__D --- --- msg.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o msg.po --- sys.all__D --- --- biossmap.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o biossmap.o --- lib.all__D --- --- lib_restart.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_restart.po --- sys.all__D --- --- bootinfo.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o bootinfo.o --- lib.all__D --- --- lib_scanw.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_scanw.po --- secure.all__D --- --- progressmeter.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o progressmeter.po --- sys.all__D --- --- bootinfo32.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o bootinfo32.o --- lib.all__D --- --- lib_screen.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_screen.po --- sys.all__D --- --- bootinfo64.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o bootinfo64.o --- secure.all__D --- --- dns.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o dns.po --- lib.all__D --- --- lib_scroll.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_scroll.po --- sys.all__D --- --- comconsole.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o comconsole.o --- lib.all__D --- --- lib_scrollok.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_scrollok.po --- secure.all__D --- --- entropy.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o entropy.po --- sys.all__D --- --- devicename.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o devicename.o --- lib.all__D --- --- lib_scrreg.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_scrreg.po --- sys.all__D --- --- elf32_freebsd.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o elf32_freebsd.o --- secure.all__D --- --- umac.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o umac.po --- lib.all__D --- --- lib_set_term.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_set_term.po --- sys.all__D --- --- elf64_freebsd.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o elf64_freebsd.o --- multiboot.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o multiboot.o --- lib.all__D --- --- lib_slk.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_slk.po --- sys.all__D --- --- multiboot_tramp.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -D= SMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -I= -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx = -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 -= Qunused-arguments -no-integrated-as -m32 -c --- secure.all__D --- --- umac128.po --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o umac128.po --- sys.all__D --- --- i386_copy.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o i386_copy.o --- lib.all__D --- --- lib_slkatr_set.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_slkatr_set.po --- sys.all__D --- --- i386_module.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o i386_module.o --- nullconsole.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o nullconsole.o --- lib.all__D --- --- lib_slkatrof.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_slkatrof.po --- sys.all__D --- --- pxe.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o pxe.o --- lib.all__D --- --- lib_slkatron.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_slkatron.po --- lib_slkatrset.po --- cc -pg -O2 -pipe -I. -I/usr/obj -I -I -I -I -Wall -DNDEBUG -DHAVE_CONFIG_H -D= FREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -fstack-protector -Wsystem-headers -W= error -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -W= missing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wn= o-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologi= cal-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio= n -Wno-enum-conversion -Qunused-arguments -c -o lib_slkatrset.po --- sys.all__D --- --- pxetramp.o --- --- secure.all__D --- --- ssh-pkcs11.po --- --- sys.all__D --- as --32 -o pxetramp.o --- secure.all__D --- cc -pg -O2 -pipe -DHAVE_LDNS=3D1 -I -I -i= nclude ssh_namespace.h -include krb5_config.h -std=3Dgnu99 -fstack-protecto= r -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-= variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equal= ity -Wno-unused-function -Wno-enum-conversion -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c -o ssh-pkcs11.po --- sys.all__D --- --- smbios.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8 -DCOMSPEED=3D9600 -= DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_alloca -I -= I -I -I -I -I. -I -fformat-extensions -march=3Di386 -ffreestanding -mno-mmx= -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=3Dgnu99 = -Qunused-arguments -c -o smbios.o :360:9: warning: implicit declaration of function 'smbios_find_struct'= is invalid in C99 [-Wimplicit-function-declaration] info =3D smbios_find_struct(0x00); ^ :360:7: warning: incompatible integer to pointer conversion assigning = to 'caddr_t' (aka 'char *') from 'int' [-Wint-conversion] info =3D smbios_find_struct(0x00); ^ ~~~~~~~~~~~~~~~~~~~~~~~~ :364:7: warning: incompatible integer to pointer conversion assigning = to 'caddr_t' (aka 'char *') from 'int' [-Wint-conversion] info =3D smbios_find_struct(0x01); ^ ~~~~~~~~~~~~~~~~~~~~~~~~ :372:1: error: static declaration of 'smbios_find_struct' follows non-= static declaration smbios_find_struct(int type) ^ :360:9: note: previous implicit declaration is here info =3D smbios_find_struct(0x00); ^ 3 warnings and 1 error generated. *** [smbios.o] Error code 1 make[6]: stopped in 1 error make[6]: stopped in *** [_sub.all] Error code 2 make[5]: stopped in 1 error make[5]: stopped in *** [_sub.all] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [_sub.all] Error code 2 make[3]: stopped in 1 error make[3]: stopped in *** [sys.all__D] Error code 2 make[2]: stopped in --- lib.all__D --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [all_subdir_ncurses] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [all_subdir_ncurses] Error code 2 make[3]: stopped in 1 error make[3]: stopped in *** [lib.all__D] Error code 2 make[2]: stopped in --- secure.all__D --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [_sub.all] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [_sub.all] Error code 2 make[3]: stopped in 1 error make[3]: stopped in *** [secure.all__D] Error code 2 make[2]: stopped in --- usr.bin.all__D --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [all_subdir_clang] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [all_subdir_clang] Error code 2 make[3]: stopped in 1 error make[3]: stopped in *** [usr.bin.all__D] Error code 2 make[2]: stopped in 4 errors make[2]: stopped in *** [everything] Error code 2 make[1]: stopped in 1 error make[1]: stopped in *** [buildworld] Error code 2 make: stopped in 1 error make: stopped in Build step 'Execute shell' marked build as failure From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:16:32 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 563852BA for ; Fri, 30 Jan 2015 23:16:32 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C37F6C8 for ; Fri, 30 Jan 2015 23:16:32 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id b16so6968531igk.1 for ; Fri, 30 Jan 2015 15:16:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DXLdP2wkxhaQ9oUHGtEPuEuuhWIpM0ak6Ya19GTvXiM=; b=SnI/Y49Q5n8z59iwBRHKSjHHGQJQOaeYeG3g6oUzeDJEL3HEYIJdDxh3xItDAfgPlV s3NwtoSkOFOy2vwoitxDHY/shnmrftZ6/ZnoyUhypBTYc84aSesjx7WUiG9uy6f3S4+R TlDNUdkMra2ekBDq6l8Ukjb5Ohgf68QQMaBvCGlgkUaa+CFMxSO3YfGFMjrSbkG/GXBP UBzdVCVegSPho8wNQJSIudO1DKMkeGx3BD11Mm2qYIHwC4xk8nUH0iV334RhVEyNQAWu 3i1PoF6ZCI4SlWX1SaZaedf8zPQYZWzc1yrIVtonmoNcgP+7kJn7Vzrt9Ru3CE722wMF jTkA== MIME-Version: 1.0 X-Received: by 10.50.79.135 with SMTP id j7mr1549069igx.32.1422659791324; Fri, 30 Jan 2015 15:16:31 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Fri, 30 Jan 2015 15:16:31 -0800 (PST) In-Reply-To: <54C883E7.4000300@interlinked.me> References: <54C883E7.4000300@interlinked.me> Date: Fri, 30 Jan 2015 15:16:31 -0800 X-Google-Sender-Auth: miWApG5OxWizyZ3Vw0Iyfw0ef5c Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver From: Adrian Chadd To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 23:16:32 -0000 Hi, Which chipset is it? Loading acpi_video causes a handful of interconnected pieces to shift (as IIRC at that point acpi_video also states that it wishes to take control of video setting, not just leave it all up to ACPI to drive itself.) There's a bunch of discussion / code churn in the linux dri2/i915 code (/past/ the point in 2012 that our code is currently synced to) about how to manage backlights. A lot of it seems due to ridiculously large variations in how backlights are actually managed. So, if we're going to do this, I think we should actually have a generic backlight thing that figures out if the right thing to do is talk to the underlying device/panel, rather than hang backlight controls off of each driver. It may not always be off of drm. :( There's also stuff surrounding locking and state changes, as well as restoring backlight values after a suspend/resume cycle. That kind of weird crap. But I'd start with which chipset it is, which version of FreeBSD it is, and whether the ACPI stuff would work for you with a code update. But for a more general future thing, I'd rather we had a sysctl tree of actual display devices, each one mapping to the underlying "thing" it's controlling, so it's a generic API for both getting and setting values for the various displays that are hooked into things. -adrian On 27 January 2015 at 22:38, Elizabeth Myers wrote: > Hello, > > I want to add backlight support to the i915 driver in FreeBSD. It seems > that two magic addresses are read and wrote from to change the backlight > itself. It supports rather fine-level granularity all the way down to > zero. Right now I use a hacked-up userland program that reads > from/writes to these addresses, which is far from an ideal solution. > > I am interested in this because the acpi_video(4) driver does not > support my backlight on my Dell Inspiron 15 3521 (not terribly > suprising, on Linux I needed a special Dell-specific driver, and I'm not > sure even that really used ACPI, I never really checked). > > My questions are really twofold: > > 1) How can this be exposed appropriately? I would prefer this be exposed > generally so upower could grok it. As far as I can tell upower uses > hw.acpi.video.lcd0 to control backlight. I am not sure that upower is > doing the "right" thing here, though. > 2) Where would the code go for this? The dri2 driver seems the most > "logical" place, but maybe it belongs in X and exposed via a program? Or > something else entirely that I'm not thinking of? > > I have experience developing PCI drivers and doing other PCI related > doodads, and some kernel development experience, as well as general C > experience, but I'm not by any means an expert on the matter. > > Cheers, > Elizabeth Myers > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:25:46 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D61E4518; Fri, 30 Jan 2015 23:25:46 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 66606802; Fri, 30 Jan 2015 23:25:46 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id z12so38707975lbi.7; Fri, 30 Jan 2015 15:25:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=qCFLgApQATUsKWiMLUUaf0UVvEMWjqUp9BYUNp9O2cQ=; b=E8k33780HUEZMqL1dYLCUPwliSbI0/JRArp2IK87lYeER8tSG6zTYFZ4ssWAOM3xuE jbNUGcmLO9vWjQzmmIvAyMwnKlyMHMQxN9XA+RzGveJHLNvmXaGoDfyyhGxr+NEcpLdM NhDJBTjpuU56Qni88UjCP2D/hXipX2c/SQ1Xd7zCCvL05lKhiMKzXVBZ+D/J8kLmOLin FMsgexj9BVkQ0UlJD1wqpvCxOXYnvAz3oRsekL4cBgnu4/Kf14ti8Yt5S7wEkGBWtTx3 CXJqcNEFAEVPHyIzW2inRnvYn6YkZaX09E0Ka3s7MQtUbRgPSzitYhQBIOaAWtXl7ikK HFIQ== MIME-Version: 1.0 X-Received: by 10.152.180.35 with SMTP id dl3mr8983078lac.24.1422660344176; Fri, 30 Jan 2015 15:25:44 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.25.160.202 with HTTP; Fri, 30 Jan 2015 15:25:44 -0800 (PST) In-Reply-To: References: <54C883E7.4000300@interlinked.me> Date: Fri, 30 Jan 2015 15:25:44 -0800 X-Google-Sender-Auth: qKQLlUwbGMVxx8RXZ1GSqak5GHY Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver From: Justin Hibbits To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current , Elizabeth Myers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 23:25:46 -0000 Would it make sense to have a generic 'backlight' driver framework that we plug into? I wrote a backlight driver (well, 2, but both show up as dev.backlight in sysctl) for powerpc, but if we want to have even more individual backlight drivers, I think it makes sense to make them all look the same, with similar configuration properties. - Justin On Fri, Jan 30, 2015 at 3:16 PM, Adrian Chadd wrote: > Hi, > > Which chipset is it? > > Loading acpi_video causes a handful of interconnected pieces to shift > (as IIRC at that point acpi_video also states that it wishes to take > control of video setting, not just leave it all up to ACPI to drive > itself.) > > There's a bunch of discussion / code churn in the linux dri2/i915 code > (/past/ the point in 2012 that our code is currently synced to) about > how to manage backlights. A lot of it seems due to ridiculously large > variations in how backlights are actually managed. > > So, if we're going to do this, I think we should actually have a > generic backlight thing that figures out if the right thing to do is > talk to the underlying device/panel, rather than hang backlight > controls off of each driver. It may not always be off of drm. :( > There's also stuff surrounding locking and state changes, as well as > restoring backlight values after a suspend/resume cycle. That kind of > weird crap. > > But I'd start with which chipset it is, which version of FreeBSD it > is, and whether the ACPI stuff would work for you with a code update. > But for a more general future thing, I'd rather we had a sysctl tree > of actual display devices, each one mapping to the underlying "thing" > it's controlling, so it's a generic API for both getting and setting > values for the various displays that are hooked into things. > > > > -adrian > > On 27 January 2015 at 22:38, Elizabeth Myers wrote: >> Hello, >> >> I want to add backlight support to the i915 driver in FreeBSD. It seems >> that two magic addresses are read and wrote from to change the backlight >> itself. It supports rather fine-level granularity all the way down to >> zero. Right now I use a hacked-up userland program that reads >> from/writes to these addresses, which is far from an ideal solution. >> >> I am interested in this because the acpi_video(4) driver does not >> support my backlight on my Dell Inspiron 15 3521 (not terribly >> suprising, on Linux I needed a special Dell-specific driver, and I'm not >> sure even that really used ACPI, I never really checked). >> >> My questions are really twofold: >> >> 1) How can this be exposed appropriately? I would prefer this be exposed >> generally so upower could grok it. As far as I can tell upower uses >> hw.acpi.video.lcd0 to control backlight. I am not sure that upower is >> doing the "right" thing here, though. >> 2) Where would the code go for this? The dri2 driver seems the most >> "logical" place, but maybe it belongs in X and exposed via a program? Or >> something else entirely that I'm not thinking of? >> >> I have experience developing PCI drivers and doing other PCI related >> doodads, and some kernel development experience, as well as general C >> experience, but I'm not by any means an expert on the matter. >> >> Cheers, >> Elizabeth Myers >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:37:27 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7CDC58C0 for ; Fri, 30 Jan 2015 23:37:27 +0000 (UTC) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 11B8A91D for ; Fri, 30 Jan 2015 23:37:26 +0000 (UTC) Received: from m.saper.info (saper@localhost [127.0.0.1]) by m.saper.info (8.14.9/8.14.9) with ESMTP id t0UNbNRo060465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Jan 2015 23:37:23 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1422661043; bh=VrBa1GOTZD9LOqTMotCZ0qPZrDAYfgS+s6LrqATZsMQ=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=ZbTeRL8sCaLkSlbRZh0xPStI4drQ0cTXbBF/yDwq3Npbv7yccnvXGifdQYmACmBhB 6mqWJLqUAGup1ZC0ja9hpfBYUPBIpmpxLhwJP6xXSEXj9tWqZYwBRz4PBp8FKs8/vU +eppx5jKBFxJ02u7ESMcx9XuWR1cXmmZ43iAzR7c= Received: from localhost (saper@localhost) by m.saper.info (8.14.9/8.14.9/Submit) with ESMTP id t0UNbM3R060462; Fri, 30 Jan 2015 23:37:22 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Fri, 30 Jan 2015 23:37:22 +0000 From: Marcin Cieslak To: Poul-Henning Kamp Subject: Re: Bug-report of sorts... In-Reply-To: <2533.1422656690@critter.freebsd.dk> Message-ID: References: <2533.1422656690@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 23:37:27 -0000 On Fri, 30 Jan 2015, Poul-Henning Kamp wrote: > But the point is I never get to the webpage, local_unbound just doesn't > seem to be able to resolve anything through the DHCP appointed server, > despite the fact that dig(1) does so just fine. I kind of got used to having to restart local_unbound after wifi/ipsec failures on my network, but I think I am going straight to the rootservers and I don't have anything captive. Something got negatively cached for too long? //Marcin From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:46:16 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 426F3AF3 for ; Fri, 30 Jan 2015 23:46:16 +0000 (UTC) Received: from bigwig.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 1A2DB9E8 for ; Fri, 30 Jan 2015 23:46:16 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F1E81B915; Fri, 30 Jan 2015 18:46:12 -0500 (EST) From: John Baldwin To: Elizabeth Myers Subject: Re: Questions on adding backlight support for the i915 driver Date: Fri, 30 Jan 2015 18:45:56 -0500 Message-ID: <3595567.zVLW9tlg0N@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <54CC0999.90500@interlinked.me> References: <54C883E7.4000300@interlinked.me> <54CBA0A4.30708@FreeBSD.org> <54CC0999.90500@interlinked.me> 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.2.7 (bigwig.baldwin.cx); Fri, 30 Jan 2015 18:46:13 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Jan 2015 23:46:16 -0000 On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote: > On 01/30/15 09:17, John Baldwin wrote: > > Humm. If the code is going to live in the drm driver, then I would > > start with hanging a sysctl off of the drm device itself. (Each new-bus > > device_t has a sysctl ctx you can get to hang new nodes off of the > > device's node.) > > I'm wondering if that's the correct place for it to live. So far it's > the only real place it *can* live that makes logical sense imho, unless > anyone has better ideas. > > This is awesome. As for upower, it should probably be patched to know > about other types of brightness sysctls if/when this is implemented. For now I think hanging it off of the device_t is fine. It can be moved later if there is an urgent need. However, I suspect that tools like upower will need updating regardless of where it ends up living. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 00:07:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37E3C3FC for ; Sat, 31 Jan 2015 00:07:50 +0000 (UTC) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id E62AFBF9 for ; Sat, 31 Jan 2015 00:07:48 +0000 (UTC) Received: (qmail 46005 invoked by uid 89); 31 Jan 2015 00:07:46 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.180.225) by mail.grem.de with ESMTPA; 31 Jan 2015 00:07:46 -0000 Date: Sat, 31 Jan 2015 01:07:45 +0100 From: Michael Gmelin To: jenkins-admin@freebsd.org Subject: Re: Build failed in Jenkins: FreeBSD_HEAD #2282 Message-ID: <20150131010745.267f04a4@bsd64.grem.de> In-Reply-To: <26487026.16.1422659561748.JavaMail.jenkins@jenkins-9.freebsd.org> References: <26487026.16.1422659561748.JavaMail.jenkins@jenkins-9.freebsd.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.0) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, pfg@FreeBSD.org, nwhitehorn@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 00:07:50 -0000 That's my mistake, should be fixed in r277957, sorry. On Fri, 30 Jan 2015 23:12:40 +0000 (GMT) jenkins-admin@freebsd.org wrote: > See > > Changes: > > [nwhitehorn] Use MBR by default on BIOS systems. An increasing number > of motherboards assume that GPT means UEFI boot, resulting in the > installation of uninstallable systems. This needs a little more work > before MFC, in particular based on disk size (> 2 TB + BIOS + MBR is > not workable). That will come soon. > > [grembo] New function smbios_match to detect BIOS versions during boot > > Motivation is to introduce BIOS specific quirks early in the boot > process. smbios_match can be called before malloc is avaible, that's > why parts of smbios_detect have been moved into a separate function > smbios_probe that will be called by smbios_detect as well as > smbios_match. > > Reviewed by: jhb > Approved by: jhb > Differential Revision: https://reviews.freebsd.org/D1679 > > [pfg] msun: use previously ignored value. > > This fixes evaluation of exceptional values in scalblnl(). > While here, simplify the code as suggested by Bruce Evans. > > Reported by: clang static analyzer > MFC after: 1 week > > ------------------------------------------ > [...truncated 172127 lines...] > cc -pg -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_pad.po --- sys.all__D --- --- biosdisk.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o biosdisk.o --- secure.all__D --- --- kexecdh.po --- cc -pg -O2 > -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o kexecdh.po --- lib.all__D --- --- lib_printw.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_printw.po --- sys.all__D --- --- biosmem.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o biosmem.o --- secure.all__D --- --- kexecdhc.po --- --- lib.all__D > --- --- lib_redrawln.po --- --- secure.all__D --- cc -pg -O2 > -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o kexecdhc.po --- lib.all__D --- cc -pg -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_redrawln.po --- sys.all__D --- --- biospnp.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o biospnp.o --- biospci.o --- cc -O2 -pipe -DLOADER_NFS_SUPPORT > -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU > -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o biospci.o --- lib.all__D --- --- lib_refresh.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_refresh.po --- secure.all__D --- --- msg.po --- cc -pg -O2 > -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o msg.po --- sys.all__D --- --- biossmap.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o biossmap.o --- lib.all__D --- --- lib_restart.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_restart.po --- sys.all__D --- --- bootinfo.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o bootinfo.o --- lib.all__D --- --- lib_scanw.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_scanw.po --- secure.all__D --- --- progressmeter.po --- cc > -pg -O2 -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o progressmeter.po --- sys.all__D --- --- bootinfo32.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o bootinfo32.o --- lib.all__D --- --- lib_screen.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_screen.po --- sys.all__D --- --- bootinfo64.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o bootinfo64.o --- secure.all__D --- --- dns.po --- cc -pg -O2 > -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o dns.po --- lib.all__D --- --- lib_scroll.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_scroll.po --- sys.all__D --- --- comconsole.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o comconsole.o --- lib.all__D --- --- lib_scrollok.po --- cc -pg > -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_scrollok.po --- secure.all__D --- --- entropy.po --- cc -pg > -O2 -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o entropy.po --- sys.all__D --- --- devicename.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o devicename.o --- lib.all__D --- --- lib_scrreg.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_scrreg.po --- sys.all__D --- --- elf32_freebsd.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o elf32_freebsd.o --- secure.all__D --- --- umac.po --- cc -pg -O2 > -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o umac.po --- lib.all__D --- --- lib_set_term.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_set_term.po --- sys.all__D --- --- elf64_freebsd.o --- cc > -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o elf64_freebsd.o --- multiboot.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o multiboot.o --- lib.all__D --- --- lib_slk.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_slk.po --- sys.all__D --- --- multiboot_tramp.o --- cc -O2 > -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -no-integrated-as -m32 -c > > --- secure.all__D --- --- umac128.po --- cc -pg -O2 -pipe > -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o umac128.po --- sys.all__D --- --- i386_copy.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o i386_copy.o --- lib.all__D --- --- lib_slkatr_set.po --- cc -pg > -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_slkatr_set.po --- sys.all__D --- --- i386_module.o --- cc > -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o i386_module.o --- nullconsole.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o nullconsole.o --- lib.all__D --- --- lib_slkatrof.po --- cc -pg > -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_slkatrof.po --- sys.all__D --- --- pxe.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o pxe.o --- lib.all__D --- --- lib_slkatron.po --- cc -pg -O2 > -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_slkatron.po --- lib_slkatrset.po --- cc -pg -O2 -pipe -I. > -I/usr/obj > -I > -I > -I > -I > -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 > -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Qunused-arguments -c > > -o lib_slkatrset.po --- sys.all__D --- --- pxetramp.o --- --- > secure.all__D --- --- ssh-pkcs11.po --- --- sys.all__D --- as --32 > -o pxetramp.o > > --- secure.all__D --- cc -pg -O2 -pipe -DHAVE_LDNS=1 > -I > -I > -include ssh_namespace.h -include krb5_config.h -std=gnu99 > -fstack-protector -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-switch > -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -c > > -o ssh-pkcs11.po --- sys.all__D --- --- smbios.o --- cc -O2 -pipe > -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 > -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca > -I > -I > -I > -I > -I > -I. > -I > -fformat-extensions -march=i386 -ffreestanding -mno-mmx -mno-3dnow > -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 > -Qunused-arguments -c > > -o smbios.o > :360:9: > warning: implicit declaration of function 'smbios_find_struct' is > invalid in C99 [-Wimplicit-function-declaration] info = > smbios_find_struct(0x00); ^ > :360:7: > warning: incompatible integer to pointer conversion assigning to > 'caddr_t' (aka 'char *') from 'int' [-Wint-conversion] info = > smbios_find_struct(0x00); ^ ~~~~~~~~~~~~~~~~~~~~~~~~ > :364:7: > warning: incompatible integer to pointer conversion assigning to > 'caddr_t' (aka 'char *') from 'int' [-Wint-conversion] info = > smbios_find_struct(0x01); ^ ~~~~~~~~~~~~~~~~~~~~~~~~ > :372:1: > error: static declaration of 'smbios_find_struct' follows non-static > declaration smbios_find_struct(int type) ^ > :360:9: > note: previous implicit declaration is here info = > smbios_find_struct(0x00); ^ 3 warnings and 1 error generated. *** > [smbios.o] Error code 1 > > make[6]: stopped in > > 1 error > > make[6]: stopped in > > *** [_sub.all] Error code 2 > > make[5]: stopped in > 1 > error > > make[5]: stopped in > *** > [_sub.all] Error code 2 > > make[4]: stopped in > 1 error > > make[4]: stopped in > *** > [_sub.all] Error code 2 > > make[3]: stopped in > 1 error > > make[3]: stopped in > *** > [sys.all__D] Error code 2 > > make[2]: stopped in > --- lib.all__D --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in > > *** [all_subdir_ncurses] Error code 2 > > make[4]: stopped in > 1 error > > make[4]: stopped in > *** > [all_subdir_ncurses] Error code 2 > > make[3]: stopped in > 1 error > > make[3]: stopped in > *** > [lib.all__D] Error code 2 > > make[2]: stopped in > --- secure.all__D --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in > > *** [_sub.all] Error code 2 > > make[4]: stopped in > 1 error > > make[4]: stopped in > *** > [_sub.all] Error code 2 > > make[3]: stopped in > 1 error > > make[3]: stopped in > *** > [secure.all__D] Error code 2 > > make[2]: stopped in > --- usr.bin.all__D --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in > > *** [all_subdir_clang] Error code 2 > > make[4]: stopped in > 1 > error > > make[4]: stopped in > *** > [all_subdir_clang] Error code 2 > > make[3]: stopped in > 1 error > > make[3]: stopped in > *** > [usr.bin.all__D] Error code 2 > > make[2]: stopped in > 4 errors > > make[2]: stopped in > *** [everything] Error code 2 > > make[1]: stopped in > 1 error > > make[1]: stopped in > *** [buildworld] Error code 2 > > make: stopped in > 1 error > > make: stopped in > Build step 'Execute shell' marked build as failure -- Michael Gmelin From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 01:02:00 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1044DD09 for ; Sat, 31 Jan 2015 01:02:00 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A3E1B18F for ; Sat, 31 Jan 2015 01:01:58 +0000 (UTC) Received: (qmail 30335 invoked from network); 31 Jan 2015 01:03:15 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 01:03:15 -0000 Message-ID: <54CC2981.3040909@interlinked.me> Date: Fri, 30 Jan 2015 19:01:53 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: John Baldwin Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CBA0A4.30708@FreeBSD.org> <54CC0999.90500@interlinked.me> <3595567.zVLW9tlg0N@ralph.baldwin.cx> In-Reply-To: <3595567.zVLW9tlg0N@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 01:02:00 -0000 On 01/30/15 17:45, John Baldwin wrote: > On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote: >> On 01/30/15 09:17, John Baldwin wrote: >>> Humm. If the code is going to live in the drm driver, then I would >>> start with hanging a sysctl off of the drm device itself. (Each new-bus >>> device_t has a sysctl ctx you can get to hang new nodes off of the >>> device's node.) >> I'm wondering if that's the correct place for it to live. So far it's >> the only real place it *can* live that makes logical sense imho, unless >> anyone has better ideas. >> >> This is awesome. As for upower, it should probably be patched to know >> about other types of brightness sysctls if/when this is implemented. > For now I think hanging it off of the device_t is fine. It can be moved > later if there is an urgent need. However, I suspect that tools like upower > will need updating regardless of where it ends up living. > Now a more interesting question... the raw PCM backlight value used by the hardware means that one can set the backlight to anything between 0 and a specific number. On my system, it's 4882, and yes, there is a subtle difference between the values. Is it best to expose this as a percentage, or just have a read-only sysctl for max values? -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 01:31:04 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B0FEF66; Sat, 31 Jan 2015 01:31:04 +0000 (UTC) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4141337B; Sat, 31 Jan 2015 01:31:04 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id rl12so7367623iec.0; Fri, 30 Jan 2015 17:31:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JMihAEy8JctqAtzKGE3pbknAFU04WNjhW58WIiX8ta8=; b=tvF3oYDDlHLAIF6AzjhrpLjWMJhT9z/xbLkN0LDAb74lSqlciQj3QoCvolSBCskgpV 3je9hybdGMxCVsrlSpvy7duOaIFD8nv0U0XQ73A9EqqwWldqBfxmR2rFWpCKhFKIWP2k Q4jMHHcsfCfiA1SvQqfkwpa7rxmcnDQqYAF4q7Dt9EB60S/Xeyooylp5H3t9t40PDxiC 1VA0lWp147j7mGOp64YlWVn2UhT8s/tYIskb5INbdeVGfFpvYSmWQwF5doOxPizkHxoC mdUUqJ7x/qsvHaaJ0P0jOCMZlNTvETSJ5jN7sAfRdfXVoWpqsmYF4PqpmwRbbNlUA9RX PxHA== MIME-Version: 1.0 X-Received: by 10.50.79.135 with SMTP id j7mr83080igx.32.1422667863512; Fri, 30 Jan 2015 17:31:03 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Fri, 30 Jan 2015 17:31:03 -0800 (PST) In-Reply-To: <54CC2981.3040909@interlinked.me> References: <54C883E7.4000300@interlinked.me> <54CBA0A4.30708@FreeBSD.org> <54CC0999.90500@interlinked.me> <3595567.zVLW9tlg0N@ralph.baldwin.cx> <54CC2981.3040909@interlinked.me> Date: Fri, 30 Jan 2015 17:31:03 -0800 X-Google-Sender-Auth: 78LlTAlZnNBH6yDDNGajDP8PTWg Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver From: Adrian Chadd To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 01:31:04 -0000 On 30 January 2015 at 17:01, Elizabeth Myers wrote: > On 01/30/15 17:45, John Baldwin wrote: >> On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote: >>> On 01/30/15 09:17, John Baldwin wrote: >>>> Humm. If the code is going to live in the drm driver, then I would >>>> start with hanging a sysctl off of the drm device itself. (Each new-bus >>>> device_t has a sysctl ctx you can get to hang new nodes off of the >>>> device's node.) >>> I'm wondering if that's the correct place for it to live. So far it's >>> the only real place it *can* live that makes logical sense imho, unless >>> anyone has better ideas. >>> >>> This is awesome. As for upower, it should probably be patched to know >>> about other types of brightness sysctls if/when this is implemented. >> For now I think hanging it off of the device_t is fine. It can be moved >> later if there is an urgent need. However, I suspect that tools like upower >> will need updating regardless of where it ends up living. >> > > Now a more interesting question... the raw PCM backlight value used by > the hardware means that one can set the backlight to anything between 0 > and a specific number. On my system, it's 4882, and yes, there is a > subtle difference between the values. Is it best to expose this as a > percentage, or just have a read-only sysctl for max values? So, this is one of the discussions that popped up in the linux side of things, that we will end up eventually pulling into freebsd when the i915 code is updated. The raw value is (a) different per setup, and (b) may be inverted to work correctly. I also don't know if linear values along that spectrum map to linear brightness levels. So yeah, my suggestion we expose an ACPI/acpi_video like list of valid percentages, and let the user set them from 0-100%. That way the details of how the actual backlight values get derived are hidden from userland. -adrian From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 01:56:44 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7916318; Sat, 31 Jan 2015 01:56:44 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id B51F5825; Sat, 31 Jan 2015 01:56:44 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id B2F6D371; Sat, 31 Jan 2015 01:56:44 +0000 (UTC) Date: Sat, 31 Jan 2015 01:56:42 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org, dim@FreeBSD.org, nwhitehorn@FreeBSD.org, pfg@FreeBSD.org, cperciva@FreeBSD.org, grembo@FreeBSD.org Message-ID: <419202854.17.1422669404299.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <26487026.16.1422659561748.JavaMail.jenkins@jenkins-9.freebsd.org> References: <26487026.16.1422659561748.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : FreeBSD_HEAD #2283 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 01:56:44 -0000 See From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 03:59:21 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C178148F for ; Sat, 31 Jan 2015 03:59:21 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 71D02323 for ; Sat, 31 Jan 2015 03:59:20 +0000 (UTC) Received: (qmail 6594 invoked from network); 31 Jan 2015 04:00:37 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 04:00:37 -0000 Message-ID: <54CC5311.9070604@interlinked.me> Date: Fri, 30 Jan 2015 21:59:13 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CBA0A4.30708@FreeBSD.org> <54CC0999.90500@interlinked.me> <3595567.zVLW9tlg0N@ralph.baldwin.cx> <54CC2981.3040909@interlinked.me> In-Reply-To: Content-Type: multipart/mixed; boundary="------------000605020202050401070404" Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 03:59:21 -0000 This is a multi-part message in MIME format. --------------000605020202050401070404 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 01/30/15 19:31, Adrian Chadd wrote: > So, this is one of the discussions that popped up in the linux side of > things, that we will end up eventually pulling into freebsd when the > i915 code is updated. > > The raw value is (a) different per setup, and (b) may be inverted to > work correctly. > > I also don't know if linear values along that spectrum map to linear > brightness levels. > > So yeah, my suggestion we expose an ACPI/acpi_video like list of valid > percentages, and let the user set them from 0-100%. That way the > details of how the actual backlight values get derived are hidden from > userland. > > > > -adrian I have a sort of "rough draft" of this. I've tested all the percentages (Ivy Bridge) and they do seem to correlate linearly (and to the intel_backlight userland program used by a lot of people). I haven't been able to test on any other hardware as I don't have it, and I don't know what chipsets require the value to be inverted, so I've not implemented that. If anyone else would like to help test, it'd be nice. -- Cheers, Elizabeth --------------000605020202050401070404 Content-Type: text/x-patch; name="intel-i915-backlight.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="intel-i915-backlight.patch" Index: i915/i915_debug.c =================================================================== --- i915/i915_debug.c (revision 277875) +++ i915/i915_debug.c (working copy) @@ -724,7 +724,7 @@ for (i = 0; i < DRM_ARRAY_SIZE(error->ring); i++) { struct drm_i915_error_object *obj; - + if ((obj = error->ring[i].batchbuffer)) { sbuf_printf(m, "%s --- gtt_offset = 0x%08x\n", dev_priv->rings[i].name, @@ -1590,6 +1590,38 @@ return (0); } +// NB - only works when y != 0! +#define U_CEIL_DIV(x, y) ((x) + (y) - 1) / (y) + +static int +i915_backlight(SYSCTL_HANDLER_ARGS) +{ + struct drm_device *dev; + drm_i915_private_t *dev_priv; + int error; + u32 val, max; + + dev = arg1; + dev_priv = dev->dev_private; + if(dev_priv == NULL) + return (EBUSY); + DRM_LOCK(dev); + val = intel_panel_get_backlight(dev); + max = intel_panel_get_max_backlight(dev); + DRM_UNLOCK(dev); + + // XXX specific devices, works fine on ivy bridge though + val = (val * 100) / max; + error = sysctl_handle_int(oidp, &val, 0, req); + if (error || !req->newptr) + return (error); + val = U_CEIL_DIV(max * val, 100); + DRM_LOCK(dev); + intel_panel_set_backlight(dev, val); + DRM_UNLOCK(dev); + return (0); +} + static struct i915_info_sysctl_list { const char *name; int (*ptr)(struct drm_device *dev, struct sbuf *m, void *data); @@ -1753,6 +1785,11 @@ CTLFLAG_RW, &i915_intr_pf, 0, NULL); if (oid == NULL) return (ENOMEM); + oid = SYSCTL_ADD_PROC(ctx, SYSCTL_CHILDREN(top), OID_AUTO, + "i915_backlight", CTLTYPE_INT | CTLFLAG_RW | CTLFLAG_MPSAFE, dev, + 0, i915_backlight, "I", NULL); + if (oid == NULL) + return (ENOMEM); error = drm_add_busid_modesetting(dev, ctx, top); if (error != 0) @@ -1764,6 +1801,5 @@ void i915_sysctl_cleanup(struct drm_device *dev) { - free(dev->sysctl_private, DRM_MEM_DRIVER); } --------------000605020202050401070404-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 04:19:29 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7EAC7C1 for ; Sat, 31 Jan 2015 04:19:29 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 56B197C4 for ; Sat, 31 Jan 2015 04:19:28 +0000 (UTC) Received: (qmail 15030 invoked from network); 31 Jan 2015 04:20:46 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 04:20:46 -0000 Message-ID: <54CC57CE.2080001@interlinked.me> Date: Fri, 30 Jan 2015 22:19:26 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Justin Hibbits , Adrian Chadd Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 04:19:29 -0000 On 01/30/15 17:25, Justin Hibbits wrote: > Would it make sense to have a generic 'backlight' driver framework > that we plug into? I wrote a backlight driver (well, 2, but both show > up as dev.backlight in sysctl) for powerpc, but if we want to have > even more individual backlight drivers, I think it makes sense to make > them all look the same, with similar configuration properties. > > - Justin I was thinking the same thing myself. There's a lot of different backlights out there, and acpi_video(4) obviously can't cover them all, which seems to define the de facto "standard" MIB for brightness sysctls (which upower presently uses). I hate to bikeshed, but I would humbly suggest adding an MIB hierarchy such as hw.backlight...brightness (and maybe brightness_raw for advanced users who want/need more control). -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 05:20:06 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7AA98D83; Sat, 31 Jan 2015 05:20:06 +0000 (UTC) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F764C5B; Sat, 31 Jan 2015 05:20:06 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id rp18so7829963iec.12; Fri, 30 Jan 2015 21:20:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JPrJWQ12j9qZRQKBY4KL14NZzAMRJAW3G8Kmt1s2cxU=; b=g6vGGKBXCktKrJM3R/1TMnedjrp7qCdg9EujdIbHxiZjiORvLVPps1HWFQ5DTKrXx0 81ys2QyKeWvLI4Yw6uIcnDrN2ArIWAg6GSlg8o7pI9nM23tmUALS4Wd+cEa8oMgcuCoX u8zR4fK5TnvWl/A6KohOJ3XvgDgC4+4Lhniu1OR/R8XBr33+Z3yCtCrUC8j/nXmzzX/7 JdVXbESB1sYHJDHv2DVXMr9iJrjPkcBPnIFRUSxBPX7SKIvSVh7FScQ9zCsARzpO/d0y 5m4sldy9VUv7vjE/Hir8zv9PNmFV4E8EZaG5QWXyiqdTzZ6CAwujdBoHS40efeOqCk8b QZJw== MIME-Version: 1.0 X-Received: by 10.42.62.71 with SMTP id x7mr9368785ich.61.1422681605619; Fri, 30 Jan 2015 21:20:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Fri, 30 Jan 2015 21:20:05 -0800 (PST) In-Reply-To: <54CC57CE.2080001@interlinked.me> References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> Date: Fri, 30 Jan 2015 21:20:05 -0800 X-Google-Sender-Auth: ei8Bxej8R-l0PA3dHzJRiwy1qcU Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver From: Adrian Chadd To: Elizabeth Myers , Konstantin Belousov Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 05:20:06 -0000 On 30 January 2015 at 20:19, Elizabeth Myers wrote: > On 01/30/15 17:25, Justin Hibbits wrote: >> Would it make sense to have a generic 'backlight' driver framework >> that we plug into? I wrote a backlight driver (well, 2, but both show >> up as dev.backlight in sysctl) for powerpc, but if we want to have >> even more individual backlight drivers, I think it makes sense to make >> them all look the same, with similar configuration properties. >> >> - Justin > > I was thinking the same thing myself. There's a lot of different > backlights out there, and acpi_video(4) obviously can't cover them all, > which seems to define the de facto "standard" MIB for brightness sysctls > (which upower presently uses). > > I hate to bikeshed, but I would humbly suggest adding an MIB hierarchy > such as hw.backlight...brightness (and maybe > brightness_raw for advanced users who want/need more control). Woo! A patch! I'm happy with this, but you'll want to cc: kib at least who looks after the i915 code. Hi kib! I think this is fine for the short term and lets us experiment without committing to a fully public API for this for the short term. Do you have brightness buttons anywhere? What happens when you set it through this API and then you use the backlight buttons? -adrian From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 06:13:34 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3932D298 for ; Sat, 31 Jan 2015 06:13:34 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CA4F6F1 for ; Sat, 31 Jan 2015 06:13:32 +0000 (UTC) Received: (qmail 29860 invoked from network); 31 Jan 2015 06:14:48 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 06:14:48 -0000 Message-ID: <54CC7288.3040409@interlinked.me> Date: Sat, 31 Jan 2015 00:13:28 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Adrian Chadd , Konstantin Belousov Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 06:13:34 -0000 On 01/30/15 23:20, Adrian Chadd wrote: > Do you have brightness buttons anywhere? What happens when you set it > through this API and then you use the backlight buttons? I do, but FreeBSD doesn't have the needed WMI doodads to interact with this, nor do I have the needed Dell laptop doodads in the kernel to test otherwise. To get /those/ working will require something else entirely. I have been looking at the Linux drivers: https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-laptop.c I'll save those for another day though, this is a bit off-topic. If anyone else has laptop keys I'd like to see how they interact too. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 06:17:09 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB2EA415; Sat, 31 Jan 2015 06:17:09 +0000 (UTC) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90027119; Sat, 31 Jan 2015 06:17:09 +0000 (UTC) Received: by mail-ig0-f172.google.com with SMTP id l13so8131258iga.5; Fri, 30 Jan 2015 22:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5m55nEY29BNKPDaRPMjmVM+RH+czSWiTuVPf9TrPGuI=; b=gfj8vRFa6afcDpTjqqDL6ZFxcjdwq7ppT8EGTI0Pf68sawIKM6lEDq4LJTiEHCk1NW UBJ5cMUhC7z+7nNBr9A/wIYpFxlKYvtSdKFwA+dNqTgNrR2vpQiR8dVVZtJg2N6RSGKf NPtlRY5paMbnn4nMAhezz5V6yBEOQUgF2WFPxQAtU18KCexv3SPjKeCkwkMS7jh0DmaN jE7WgSHV5bOidceDqBBk/NBbyh+6Tv1sktRcXag2cChQyCIFlTsK9JRx+M9mlD+gZfSE zjojxiCEnFwfjV8VFmoNQ4Wl4xOuNgrsdky8ESbrU7UfiUrFoDau6li9CMlzrr6XqUoq M3gA== MIME-Version: 1.0 X-Received: by 10.107.31.16 with SMTP id f16mr6658120iof.88.1422685028960; Fri, 30 Jan 2015 22:17:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Fri, 30 Jan 2015 22:17:08 -0800 (PST) In-Reply-To: <54CC7288.3040409@interlinked.me> References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> <54CC7288.3040409@interlinked.me> Date: Fri, 30 Jan 2015 22:17:08 -0800 X-Google-Sender-Auth: ibnR7OW552ajWepWw4Ib7F5dDJc Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver From: Adrian Chadd To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current , Konstantin Belousov , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 06:17:09 -0000 On 30 January 2015 at 22:13, Elizabeth Myers wrote: > On 01/30/15 23:20, Adrian Chadd wrote: >> Do you have brightness buttons anywhere? What happens when you set it >> through this API and then you use the backlight buttons? > > > I do, but FreeBSD doesn't have the needed WMI doodads to interact with > this, nor do I have the needed Dell laptop doodads in the kernel to test > otherwise. > > To get /those/ working will require something else entirely. I have been > looking at the Linux drivers: > > https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c > https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-laptop.c > > I'll save those for another day though, this is a bit off-topic. If > anyone else has laptop keys I'd like to see how they interact too. *nod* cool. I don't have any Dell hardware and I have no idea how any of that holds together. :( I'll wait and see what kib/jhb say and if there aren't any issues I'll commit your i915 debug patch. -adrian From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 07:11:44 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 58907A47 for ; Sat, 31 Jan 2015 07:11:44 +0000 (UTC) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 187E380E for ; Sat, 31 Jan 2015 07:11:44 +0000 (UTC) Received: by mail-ig0-f172.google.com with SMTP id l13so8262583iga.5 for ; Fri, 30 Jan 2015 23:11:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CkD07OJrKwmzk6eU+gO1PwOD1Zdqci5unIaKAWsX7WE=; b=yOacUDIloCYaEW+wMIbYiqKUJrkMA6edEHleY1tDZ0uA4219+H/jhtlTgeFzG+q2Kv 9vuoDz1i2l0pyEnlgAGz9yB7m5IZGPGg3k88fsov36pX/CzDY22PfpXSDw7/lvfsTxy7 TN8DKZL2ZyIvfbNxoi8qrWfjahKB9DvJpuazQ5Lmrc9GhFcYNyrwIfBVxvDctBJMvcpy yxuJEYQXF8qV7CQ6YTndPtGmxlfna/PvnNFgXae27dASQXFXAlAZrGP3AgpbONRtTaTf UOwBOMmf7RAgHble3VQ1bVff965qge4g3WXlaaRJFvJyBQenL+5tbAi/zzqhY84KhO80 NiHw== X-Received: by 10.50.50.142 with SMTP id c14mr987393igo.42.1422688303511; Fri, 30 Jan 2015 23:11:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.236.106 with HTTP; Fri, 30 Jan 2015 23:11:23 -0800 (PST) In-Reply-To: <54CA7949.6060202@shurik.kiev.ua> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> From: Miguel Clara Date: Sat, 31 Jan 2015 07:11:23 +0000 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works To: Alexandr Krivulya Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 07:11:44 -0000 On the laptop I'm running current, if relevant Loading acpi_video doesn't do much.... I don't see any sysctl related to "lcd0" or "birightness", this is one of those computers with "hybrid" graphics, intel + ATI card, so not sure if that's somewhat related. Anyway, I've just tested the drm patches (both) and intelbacklight ( https://github.com/grembo/intel_backlight_fbsd) compiles, installs and runs fine! So thanks both for the patches. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 07:22:27 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E690DCF8 for ; Sat, 31 Jan 2015 07:22:27 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 993FF8DB for ; Sat, 31 Jan 2015 07:22:26 +0000 (UTC) Received: (qmail 26090 invoked from network); 31 Jan 2015 07:23:45 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 07:23:45 -0000 Message-ID: <54CC82AE.7060404@interlinked.me> Date: Sat, 31 Jan 2015 01:22:22 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miguel Clara , Alexandr Krivulya Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 07:22:28 -0000 On 01/31/15 01:11, Miguel Clara wrote: > On the laptop I'm running current, if relevant > > Loading acpi_video doesn't do much.... I don't see any sysctl related to > "lcd0" or "birightness", this is one of those computers with "hybrid" > graphics, intel + ATI card, so not sure if that's somewhat related. > > > Anyway, I've just tested the drm patches (both) and intelbacklight ( > https://github.com/grembo/intel_backlight_fbsd) compiles, installs and runs > fine! > > So thanks both for the patches. You might be interested in my newest patch to add backlight control to sysctl. It's probably better for everyone (imo) that backlight control is integrated into the driver and accessible via sysctl, so it works the same way for everyone. Look for the subject "Re: Questions on adding backlight support for the i915 driver" from me and you'll find the patch. I am curious if it works for you. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 07:28:38 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DD60F5C for ; Sat, 31 Jan 2015 07:28:38 +0000 (UTC) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B831901 for ; Sat, 31 Jan 2015 07:28:38 +0000 (UTC) Received: by mail-ig0-f169.google.com with SMTP id hl2so7781294igb.0 for ; Fri, 30 Jan 2015 23:28:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sEsfM00nM/mtSjyaw5dez6sOCyDwAGf44RV/fz2q/jU=; b=WPxjqrHRGJmLP1crwWmIDiUiqJZwaO46/CW6dML0m6QpX82gv6bPGPKdDTRfr+5mCe R1aI+gCUo1N7ateqmP1t/iSXrpsWTfyhpujXL44unvnfyvuDmPQ/w1FPsYVmwSeuuswO PmI6wcutd60yAWZDxlE16a+9IGVlJ6nolrnC7cUG3b7uaOuw9ESW/2vHHOHaJrC7LOHW rPQLRVeeZNeA/ZWUa5Dpv25beEOn/9ypNO/odWb417LUgUzhXWpt+2A6mcaJmIc3JkIg Rz3IG3CcvRLr9VJMjFny9g778UzAFayoJAM3r6rzQRRzc82yydAm5O08UevhB3z7C3Dd tg4A== X-Received: by 10.107.5.79 with SMTP id 76mr11869835iof.15.1422689317560; Fri, 30 Jan 2015 23:28:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.236.106 with HTTP; Fri, 30 Jan 2015 23:28:17 -0800 (PST) In-Reply-To: <54CC82AE.7060404@interlinked.me> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> <54CC82AE.7060404@interlinked.me> From: Miguel Clara Date: Sat, 31 Jan 2015 07:28:17 +0000 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Alexandr Krivulya , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 07:28:38 -0000 I saw the discussion about how to approach the issue, but totally missed the patch :D Thanks, I'll try that... I'm assuming it will make no difference on 10/stable yet? only current? On Sat, Jan 31, 2015 at 7:22 AM, Elizabeth Myers wrote: > On 01/31/15 01:11, Miguel Clara wrote: > > On the laptop I'm running current, if relevant > > > > Loading acpi_video doesn't do much.... I don't see any sysctl related to > > "lcd0" or "birightness", this is one of those computers with "hybrid" > > graphics, intel + ATI card, so not sure if that's somewhat related. > > > > > > Anyway, I've just tested the drm patches (both) and intelbacklight ( > > https://github.com/grembo/intel_backlight_fbsd) compiles, installs and > runs > > fine! > > > > So thanks both for the patches. > > You might be interested in my newest patch to add backlight control to > sysctl. It's probably better for everyone (imo) that backlight control > is integrated into the driver and accessible via sysctl, so it works the > same way for everyone. > > Look for the subject "Re: Questions on adding backlight support for the > i915 driver" from me and you'll find the patch. I am curious if it works > for you. > > -- > Cheers, > Elizabeth > From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 07:40:25 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3EA32EB for ; Sat, 31 Jan 2015 07:40:25 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B0349EB for ; Sat, 31 Jan 2015 07:40:24 +0000 (UTC) Received: (qmail 1120 invoked from network); 31 Jan 2015 07:41:43 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 07:41:43 -0000 Message-ID: <54CC86E6.40504@interlinked.me> Date: Sat, 31 Jan 2015 01:40:22 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> <54CC82AE.7060404@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Alexandr Krivulya , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 07:40:25 -0000 On 01/31/15 01:28, Miguel Clara wrote: > I saw the discussion about how to approach the issue, but totally missed > the patch :D > > Thanks, I'll try that... I'm assuming it will make no difference on > 10/stable yet? only current? Excellent question! I have absolutely no idea. I don't even think it applies cleanly. If you can get it to apply and it builds, it just might work. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:00:32 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B2B66B2 for ; Sat, 31 Jan 2015 08:00:32 +0000 (UTC) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33E83B7C for ; Sat, 31 Jan 2015 08:00:32 +0000 (UTC) Received: by mail-ig0-f182.google.com with SMTP id r10so7688509igi.3 for ; Sat, 31 Jan 2015 00:00:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=iA/+jkFwRttSChFoR4JIH+jEmvCKVqdXQBj+OzZhBIQ=; b=Le+0A1JRCxWLd6Cxpbaqx70BWGf2lqtSAMm0PWiqsVXRtUCDAlKP6NrjE54etM/s+4 awYhKwqkCuXVvHkSZjBi+3JZvoE1odg693FrhPE9xgHL5L6gqYsAcCw9s1/u5oBa8JHG VYHjJPz1sRVzeV8oE5ktT+qW0lWTC2f6LzOIxQ2Z4rYX2m0fB/2lbdSkJtFAfoFx7AhC cRn+ERhZ6WAnvKXyLg8OoYi0J8TtUgfPr1U7815/k15DPjAQ2VKDOLAgspsAREw5CEpB VaK0e0GnwvVeQLTRpp8D19Z/UGeUc6fZg+eoGByuPRG0V/P8bhai2n2apS44ONLCnZqw mJEg== X-Received: by 10.50.253.12 with SMTP id zw12mr1128571igc.24.1422691226338; Sat, 31 Jan 2015 00:00:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.236.106 with HTTP; Sat, 31 Jan 2015 00:00:06 -0800 (PST) In-Reply-To: <54CC86E6.40504@interlinked.me> References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> <54CC82AE.7060404@interlinked.me> <54CC86E6.40504@interlinked.me> From: Miguel Clara Date: Sat, 31 Jan 2015 08:00:06 +0000 Message-ID: Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Alexandr Krivulya , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 08:00:32 -0000 I had to patch manually, for some reason the diff was rejected, but I t compiled and I've instead on 10/stable... problem is this is the laptop where I am typing this :D Its also upgrading some ports, so not a good time to reboot, but I'll post results in the other thread, as for the HP, works perfect (for me at least... far better then what I had :) ) % intel_backlight 50 current backlight value: 100% (4882/4882) set backlight to 50% (2441/4882) % sysctl -a | grep backlig hw.dri.0.i915_backlight: 50 % kldstat |grep acpi 9 1 0xffffffff81fb1000 8708 acpi_video.ko % sudo sysctl hw.dri.0.i915_backlight=100 hw.dri.0.i915_backlight: 50 -> 100 % intel_backlight current backlight value: 100% (4882/4882 Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Sat, Jan 31, 2015 at 7:40 AM, Elizabeth Myers wrote: > On 01/31/15 01:28, Miguel Clara wrote: > > I saw the discussion about how to approach the issue, but totally missed > > the patch :D > > > > Thanks, I'll try that... I'm assuming it will make no difference on > > 10/stable yet? only current? > > Excellent question! I have absolutely no idea. I don't even think it > applies cleanly. If you can get it to apply and it builds, it just might > work. > > -- > Cheers, > Elizabeth > From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:02:37 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A96C57C6 for ; Sat, 31 Jan 2015 08:02:37 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F9DFC19 for ; Sat, 31 Jan 2015 08:02:35 +0000 (UTC) Received: (qmail 10381 invoked from network); 31 Jan 2015 08:03:54 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 08:03:54 -0000 Message-ID: <54CC8C19.2070008@interlinked.me> Date: Sat, 31 Jan 2015 02:02:33 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miguel Clara Subject: Re: drm2 regression: backlight adjustment on ivybridge no longer works References: <000e01d039fb$d5959930$80c0cb90$@Wilcox-Tech.com> <009501d03acb$4f380d70$eda82850$@Wilcox-Tech.com> <54CA7949.6060202@shurik.kiev.ua> <54CC82AE.7060404@interlinked.me> <54CC86E6.40504@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Alexandr Krivulya , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 08:02:37 -0000 On 01/31/15 02:00, Miguel Clara wrote: > I had to patch manually, for some reason the diff was rejected, but I t > compiled and I've instead on 10/stable... problem is this is the laptop > where I am typing this :D > > Its also upgrading some ports, so not a good time to reboot, but I'll > post results in the other thread, as for the HP, works perfect (for me > at least... far better then what I had :) ) Good to know! If this gets merged (even in modified form), you could ask about an MFC. I'm not the person to ask about this though, I'm just a humble peon. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:15:41 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 720C2A8B; Sat, 31 Jan 2015 08:15:41 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F79BCF4; Sat, 31 Jan 2015 08:15:41 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id at20so8313291iec.3; Sat, 31 Jan 2015 00:15:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OUmVgTf5rICQbahPfWfZDQmD6W464meV3Aq6r3vOl+0=; b=wmpsS1HLzUDJaQHR6i3yUt9Pdk5a0pJly9CuzHcyqZEWCSyv5KLTi4ohtEofAOb9+i FoBEgJHpGA9fP2rstT1XVyz+fxv7YKeZvMEkd9moInae6+Ju1/C9CGoceRakXusSwSPm fFIluglZQGE99jSCW6eA0o++TQ7aStEyAPprSIGNSKK6ZJ6qZzwr6n+/zvGibX8RZsCA VD7PrmDAuifYUdNhdpqx+Iu5zYb0FcAHvYhnp6/afWzOGBPrwyx4/pIERGa078lCnbqC TK8xuTV6yAs03T1wbnpffyK5rbDWp4ilmFRrohWyFvPenDx05OHdShVZ1AvoN/ZERvZD Me3g== X-Received: by 10.42.152.197 with SMTP id j5mr10071718icw.40.1422692140657; Sat, 31 Jan 2015 00:15:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.236.106 with HTTP; Sat, 31 Jan 2015 00:15:20 -0800 (PST) In-Reply-To: References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> <54CC7288.3040409@interlinked.me> From: Miguel Clara Date: Sat, 31 Jan 2015 08:15:20 +0000 Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-current , Konstantin Belousov , Justin Hibbits , Elizabeth Myers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 08:15:41 -0000 Working fine on a HP running current as I've noted in the other thread as for the keys. This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys, and my Acer (and I think not all are like this) use "Fn+<-/->" Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Sat, Jan 31, 2015 at 6:17 AM, Adrian Chadd wrote: > On 30 January 2015 at 22:13, Elizabeth Myers > wrote: > > On 01/30/15 23:20, Adrian Chadd wrote: > >> Do you have brightness buttons anywhere? What happens when you set it > >> through this API and then you use the backlight buttons? > > > > > > I do, but FreeBSD doesn't have the needed WMI doodads to interact with > > this, nor do I have the needed Dell laptop doodads in the kernel to test > > otherwise. > > > > To get /those/ working will require something else entirely. I have been > > looking at the Linux drivers: > > > > > https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c > > > https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-laptop.c > > > > I'll save those for another day though, this is a bit off-topic. If > > anyone else has laptop keys I'd like to see how they interact too. > > *nod* cool. I don't have any Dell hardware and I have no idea how any > of that holds together. :( > > I'll wait and see what kib/jhb say and if there aren't any issues I'll > commit your i915 debug patch. > > > > -adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:19:06 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94F25BA8 for ; Sat, 31 Jan 2015 08:19:06 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E4FFD15 for ; Sat, 31 Jan 2015 08:19:05 +0000 (UTC) Received: (qmail 17254 invoked from network); 31 Jan 2015 08:20:24 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 08:20:24 -0000 Message-ID: <54CC8FF7.4020507@interlinked.me> Date: Sat, 31 Jan 2015 02:19:03 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miguel Clara , Adrian Chadd Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> <54CC7288.3040409@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current , Konstantin Belousov , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 08:19:06 -0000 On 01/31/15 02:15, Miguel Clara wrote: > Working fine on a HP running current as I've noted in the other thread > as for the keys. > This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys, > and my Acer (and I think not all are like this) use "Fn+<-/->" If your keys work (as in, they do things in FreeBSD), does sysctl and the keys work together just fine with no weird effects? The only weird problem I could possibly think of that could come up is that the keys do a simple add/subtract to the PCM values, and so the brightness ends up wrong. See if that happens. -- Cheers, Elizabeth Myers From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:31:03 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B018D6A; Sat, 31 Jan 2015 08:31:03 +0000 (UTC) Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFB35DE5; Sat, 31 Jan 2015 08:31:02 +0000 (UTC) Received: by mail-ig0-f175.google.com with SMTP id hn18so8481567igb.2; Sat, 31 Jan 2015 00:31:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=z6yJ2zMONKX++CumOEcgAQniBw7NQT2HQkZmIKezYQM=; b=SKOuMdjXxeMP3T2NZIt2FWXCdEitIOSL5kEr4rrJx7j1wYYYY01+xnr9OC64atQiYk +ezUrxX2biKbwRKVaw0E9Iec0OxQQFMQgF5lcPI7Ji5KfkDH+u3Q+SikH2g4uTCA8aFI IkdLe+JijwcdU9qdcOR/v1vRrykvJP5YzOXvg8bpfLtJLPQe4+/Xm1PkoNxSxuf7kisX IVK80QFSuHAd299Qi2YSxhKdeae4WOT0Ci6bWta7oKq25sYncn2dEvk5P0cf/q+L3+8C H3HcWuwqyE5y6HLfApwp6AX3cT8Xa6oF/Gc+A1Ms94iryaFSBLWjj000n6jwudKtBQnO 0SoA== X-Received: by 10.50.176.196 with SMTP id ck4mr1228542igc.40.1422693062348; Sat, 31 Jan 2015 00:31:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.236.106 with HTTP; Sat, 31 Jan 2015 00:30:42 -0800 (PST) In-Reply-To: <54CC8FF7.4020507@interlinked.me> References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> <54CC7288.3040409@interlinked.me> <54CC8FF7.4020507@interlinked.me> From: Miguel Clara Date: Sat, 31 Jan 2015 08:30:42 +0000 Message-ID: Subject: Re: Questions on adding backlight support for the i915 driver To: Elizabeth Myers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Adrian Chadd , freebsd-current , Konstantin Belousov , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 08:31:03 -0000 On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers wrote: > On 01/31/15 02:15, Miguel Clara wrote: > > Working fine on a HP running current as I've noted in the other thread > > as for the keys. > > This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys, > > and my Acer (and I think not all are like this) use "Fn+<-/->" > > If your keys work (as in, they do things in FreeBSD), does sysctl and > the keys work together just fine with no weird effects? > > The only weird problem I could possibly think of that could come up is > that the keys do a simple add/subtract to the PCM values, and so the > brightness ends up wrong. See if that happens. > > Well, in the HP the keys don't do nothing it seems not even "xev" reports anything when I use them, but they could be wrongly mapped maybe... On the acer I do see keycodes from xev, but Im using lumina and If I try to map them to anything it doesn't work... I'll see what happens after reboot though. -- > Cheers, > Elizabeth Myers > > From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 09:05:12 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78FB3304 for ; Sat, 31 Jan 2015 09:05:12 +0000 (UTC) Received: from mail.wilcox-tech.com (mail.foxkit.us [192.99.209.192]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.wilcox-tech.com", Issuer "mail.wilcox-tech.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 318CF168 for ; Sat, 31 Jan 2015 09:05:11 +0000 (UTC) Received: (qmail 4017 invoked from network); 31 Jan 2015 09:06:30 -0000 Received: from ip68-13-243-137.ok.ok.cox.net (HELO ?192.168.1.253?) (emyers@wilcox-tech.com@68.13.243.137) by mail.foxkit.us with ESMTPA; 31 Jan 2015 09:06:30 -0000 Message-ID: <54CC9AC5.1050802@interlinked.me> Date: Sat, 31 Jan 2015 03:05:09 -0600 From: Elizabeth Myers User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 09:05:12 -0000 On 01/30/15 17:16, Adrian Chadd wrote: > Hi, > > Which chipset is it? Oh, I missed this, sorry. I have an Ivy Bridge chipset. > Loading acpi_video causes a handful of interconnected pieces to shift > (as IIRC at that point acpi_video also states that it wishes to take > control of video setting, not just leave it all up to ACPI to drive > itself.) My laptop doesn't have any ACPI calls for backlight stuff. Dell laptops seem to do it with SMI's. It's pretty lame (and exotic) stuff. > There's a bunch of discussion / code churn in the linux dri2/i915 code > (/past/ the point in 2012 that our code is currently synced to) about > how to manage backlights. A lot of it seems due to ridiculously large > variations in how backlights are actually managed. > > So, if we're going to do this, I think we should actually have a > generic backlight thing that figures out if the right thing to do is > talk to the underlying device/panel, rather than hang backlight > controls off of each driver. It may not always be off of drm. :( > There's also stuff surrounding locking and state changes, as well as > restoring backlight values after a suspend/resume cycle. That kind of > weird crap. A generic backlight module is probably ideal. Not everything uses ACPI to drive the backlight (my laptop doesn't). The way it could work is that drivers just provide the needed functions for changing the backlight and tell the driver "hey here's my functions for backlight change and query." That way anything can take advantage of it, including acpi_video, providing a nice and unified interface. > But I'd start with which chipset it is, which version of FreeBSD it > is, and whether the ACPI stuff would work for you with a code update. > But for a more general future thing, I'd rather we had a sysctl tree > of actual display devices, each one mapping to the underlying "thing" > it's controlling, so it's a generic API for both getting and setting > values for the various displays that are hooked into things. A code update won't do any good due to aforementioned issues. If anyone else has a Dell laptop and would be interested in helping to test, I will try to write a driver for them. In the meantime, I think there should be some other discussion elsewhere or in another thread about a generic backlight framework. -- Cheers, Elizabeth From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 15:12:29 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55080573 for ; Sat, 31 Jan 2015 15:12:29 +0000 (UTC) Received: from sasl.smtp.pobox.com (pb-smtp1.int.icgroup.com [208.72.237.35]) by mx1.freebsd.org (Postfix) with ESMTP id 242EB7BE for ; Sat, 31 Jan 2015 15:12:28 +0000 (UTC) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id B08492FFD6 for ; Sat, 31 Jan 2015 10:08:18 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=message-id :date:from:mime-version:to:subject:content-type; s=sasl; bh=Egm6 TEK3DezAtV5TAOq1jUFxO7A=; b=QowsyHwtspuPqoABzG4Z3OWdD05uQNZNrVy2 oVGn3fX6XydSCsxFrOSIcas2IAXDojY3M91g/o5xC3cOZtxbnYutXW4ZlQ65ouOG m0a+TsfiopHe854l1hVmKlX9zlzLCdEC31L19wlxLfzezEB/2GTKG5iOymalj/RX f8EVO5k= Received: from pb-smtp1.int.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id A7B8E2FFD5 for ; Sat, 31 Jan 2015 10:08:18 -0500 (EST) Received: from [192.168.1.103] (unknown [73.164.1.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 10D932FFD3 for ; Sat, 31 Jan 2015 10:08:17 -0500 (EST) Message-ID: <54CCEFAB.9040406@badgerio.us> Date: Sat, 31 Jan 2015 09:07:23 -0600 From: Eric Badger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Filepaths in VM map for tmpfs files Content-Type: multipart/mixed; boundary="------------010102060709010900020003" X-Pobox-Relay-ID: FCC92A3E-A95A-11E4-A4AA-7BA29F42C9D4-46178211!pb-smtp1.pobox.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 15:12:29 -0000 This is a multi-part message in MIME format. --------------010102060709010900020003 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit In FreeBSD 9, examining the VM map of a process (with e.g. 'procstat -v') with a tmpfs file mapped showed a VNODE type and displayed the file path. In 10.0 up to CURRENT (I believe this started at r250030), instead SWAP is shown without a filepath. This has some unfortunate consequences; I discovered this problem when trying to use dtrace's pid provider, which fails to find symbols for executables running from tmpfs. I've attached a patch which will repair procstat/dtrace. There are a few other places such a patch would be needed. I'm willing to put together such a patch, but would like to first hear some feedback that this seems like a reasonable approach, or if there's anything I've missed. Thoughts? Eric --------------010102060709010900020003 Content-Type: text/x-patch; name="tmpfs_vnode.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="tmpfs_vnode.diff" Index: sys/kern/kern_proc.c =================================================================== --- sys/kern/kern_proc.c (revision 277957) +++ sys/kern/kern_proc.c (working copy) @@ -2337,6 +2337,11 @@ break; case OBJT_SWAP: kve->kve_type = KVME_TYPE_SWAP; + if ((lobj->flags & OBJ_TMPFS) != 0) + { + vp = lobj->un_pager.swp.swp_tmpfs; + vref(vp); + } break; case OBJT_DEVICE: kve->kve_type = KVME_TYPE_DEVICE; --------------010102060709010900020003-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 15:36:32 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C4E6BD9F for ; Sat, 31 Jan 2015 15:36:32 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 37EC89C6 for ; Sat, 31 Jan 2015 15:36:32 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0VFaLhn048295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jan 2015 17:36:21 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0VFaLhn048295 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0VFaLss048294; Sat, 31 Jan 2015 17:36:21 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 31 Jan 2015 17:36:21 +0200 From: Konstantin Belousov To: Eric Badger Subject: Re: Filepaths in VM map for tmpfs files Message-ID: <20150131153621.GH42409@kib.kiev.ua> References: <54CCEFAB.9040406@badgerio.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54CCEFAB.9040406@badgerio.us> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 15:36:32 -0000 On Sat, Jan 31, 2015 at 09:07:23AM -0600, Eric Badger wrote: > In FreeBSD 9, examining the VM map of a process (with e.g. 'procstat > -v') with a tmpfs file mapped showed a VNODE type and displayed the file > path. In 10.0 up to CURRENT (I believe this started at r250030), instead > SWAP is shown without a filepath. > > This has some unfortunate consequences; I discovered this problem when > trying to use dtrace's pid provider, which fails to find symbols for > executables running from tmpfs. > > I've attached a patch which will repair procstat/dtrace. There are a few > other places such a patch would be needed. I'm willing to put together > such a patch, but would like to first hear some feedback that this seems > like a reasonable approach, or if there's anything I've missed. > > Thoughts? > > Eric > > > Index: sys/kern/kern_proc.c > =================================================================== > --- sys/kern/kern_proc.c (revision 277957) > +++ sys/kern/kern_proc.c (working copy) > @@ -2337,6 +2337,11 @@ > break; > case OBJT_SWAP: > kve->kve_type = KVME_TYPE_SWAP; > + if ((lobj->flags & OBJ_TMPFS) != 0) > + { > + vp = lobj->un_pager.swp.swp_tmpfs; > + vref(vp); > + } > break; > case OBJT_DEVICE: > kve->kve_type = KVME_TYPE_DEVICE; First, shouldn't the kve_type changed to KVME_TYPE_VNODE as well ? Second, note that it is possible that the vnode is recycled, so OBJ_TMPFS flag is cleared for tmpfs swap object. The OBJ_TMPFS_NODE flag is still set then. I am not sure what to do in this case, should the type changed to KVME_TYPE_VNODE still, but kve_vn_* fields left invalid ? From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 17:15:49 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1ECDC4D5; Sat, 31 Jan 2015 17:15:49 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAE72381; Sat, 31 Jan 2015 17:15:48 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id ar1so9732093iec.13; Sat, 31 Jan 2015 09:15:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pKG0I9Oxrj+z5js4PzZBT07o0rfAuApvHxXcBhysqzA=; b=L6E624j2ZjtYJ9S46UVBQE2If5C5cTqcZyuhYdOElpLVez/sCas5olGLYxq/z/82i1 TY5n9NKG09skh+xS3Q86MRqGtAusMql5D5PHe0lppI6kqG0J9TK9fow9vZblHPNdaZE0 nKTKlpfSVp3o4oGaPkdK+gWZ2qFUPsSFhZjNNkL9zoKlUGFWA3rN22xhklmo0JADvvbX QMLptoZlatiuy+MTvp/EkHmUEK4ef+JggQUxqgot3Vqkglb2wkwNMJ/GVRcDDW9g72p/ NbGMi83rIbSRgT/btNs/KGw+rm7wzuvUpr4o5QjKkSyttowYUuD+koQtoYQH0nLQg/2k Nfbw== MIME-Version: 1.0 X-Received: by 10.50.73.99 with SMTP id k3mr3099917igv.21.1422724548257; Sat, 31 Jan 2015 09:15:48 -0800 (PST) Received: by 10.64.91.193 with HTTP; Sat, 31 Jan 2015 09:15:48 -0800 (PST) In-Reply-To: References: Date: Sat, 31 Jan 2015 18:15:48 +0100 Message-ID: Subject: Re: UEFI boot hangs with MINNOWBOARD From: Luca Pizzamiglio To: Ed Maste Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 17:15:49 -0000 Hi Ed, thanks for the reply I tested the last available memstick (r277486) of CURRENT to install FreeBSD, but it didn't finish the boot process. The boot process hangs after showing the framebuffer information ( bi_load_efi_data() in bootinfo.c). I'm using a DVI monitor with a mini-HDMI<->DVI cable. With a very hold DVI monitor I cannot see anything. Then I moved to a recent DVI monitor, but it hanged as well. Then I recompiled CURRENT (updated to Thursday) and added several printf to the EFI section (both boot1.efi and loader.efi). I also updated the UEFI of the board to the most recent one, without luck. I'll come back on Wednesday, I'll recompile everything removing all my printf and let's see what happen. Is the display so relevant? Thanks again for the help, it's really appreciated! Best regards, pizzamig On 1/30/15, Ed Maste wrote: > On 30 January 2015 at 12:35, Ed Maste wrote: >> >> I built a plain -current USB stick image a while back and had no >> trouble, when using the HDMI output. I don't recall the revision at >> the moment, but will try again soon. Serial console won't work because >> the UARTs are not quite 16550-compatible. > > I just checked on a build at r277612 (a week old) and had no trouble. > > For reference the not-yet-working UARTs are: > > none7@pci0:0:30:3: class=0x078000 card=0x72708086 chip-0x0f0a8086 > rev=0x0c hdr=0x00 > vendor = 'Intel Corporation' > device = 'ValleyView LPIO1 HSUART Controller' > class = simple comms > none8@pci0:0:30:4: class=0x078000 card=0x72708086 chip-0x0f0c8086 > rev=0x0c hdr=0x00 > vendor = 'Intel Corporation' > device = 'ValleyView LPIO1 HSUART Controller' > class = simple comms > -- --------------------- From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 16:59:47 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3402E2AB; Sat, 31 Jan 2015 16:59:47 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0145.outbound.protection.outlook.com [157.56.110.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0125A1BD; Sat, 31 Jan 2015 16:59:45 +0000 (UTC) Received: from BY2PR05CA060.namprd05.prod.outlook.com (10.141.250.50) by DM2PR05MB448.namprd05.prod.outlook.com (10.141.104.152) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sat, 31 Jan 2015 16:59:42 +0000 Received: from BL2FFO11FD048.protection.gbl (2a01:111:f400:7c09::179) by BY2PR05CA060.outlook.office365.com (2a01:111:e400:2c5f::50) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Sat, 31 Jan 2015 16:59:42 +0000 Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by BL2FFO11FD048.mail.protection.outlook.com (10.173.161.210) with Microsoft SMTP Server (TLS) id 15.1.75.11 via Frontend Transport; Sat, 31 Jan 2015 16:59:41 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Sat, 31 Jan 2015 08:59:40 -0800 Received: from chaos.jnpr.net (chaos.jnpr.net [172.21.16.28]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id t0VGxeW30009; Sat, 31 Jan 2015 08:59:40 -0800 (PST) (envelope-from sjg@juniper.net) Received: from chaos (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id C3BD0580A3; Sat, 31 Jan 2015 08:59:39 -0800 (PST) To: Julian Elischer Subject: Re: bmake and .USEBEFORE In-Reply-To: <54C878BD.1090805@freebsd.org> References: <54C876A1.20105@freebsd.org> <54C878BD.1090805@freebsd.org> Comments: In-reply-to: Julian Elischer message dated "Wed, 28 Jan 2015 13:50:53 +0800." From: "Simon J. Gerraty" X-Mailer: MH-E 8.0.3; nmh 1.3; GNU Emacs 22.3.1 Date: Sat, 31 Jan 2015 08:59:39 -0800 Message-ID: <20656.1422723579@chaos> MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.16 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.16) smtp.mailfrom=sjg@juniper.net; freebsd.org; dkim=none (message not signed) header.d=none; X-Forefront-Antispam-Report: CIP:66.129.239.16; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(24454002)(377454003)(479174004)(52314003)(47776003)(57986006)(76506005)(33716001)(19580395003)(46102003)(6806004)(50226001)(19580405001)(86362001)(117636001)(110136001)(106466001)(92566002)(450100001)(77156002)(62966003)(76176999)(50986999)(105596002)(87936001)(77096005)(2950100001)(50466002)(48376002)(142923001)(42262002)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB448; H:P-EMF02-SAC.jnpr.net; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB448; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DM2PR05MB448; X-Forefront-PRVS: 0473A03F3F X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB448; X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Jan 2015 16:59:41.7004 (UTC) X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.16] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB448 X-Mailman-Approved-At: Sat, 31 Jan 2015 18:06:32 +0000 Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 16:59:47 -0000 Julian Elischer wrote: > On 1/28/15 1:41 PM, Julian Elischer wrote: > > If I try the following: > > > > bar: .USE > > @echo @ = $(@) > > all: bar > > @echo here is all > oops > the failing example should be .USEBEFORE.. I pasted the wrong clip. > > > > I always get "bar is up to date" If you put all: as the first target or add .MAIN: all or explicitly do make all you will get the output you expect. As is; 'bar' is the default target but it's .USEBEFORE which doesn't make a lot of sense (sort of being applied to itself ;-) It would probably make sense for .USE* to imply .NOTMAIN. Anyway, to illustrate the purpose of .USEBEFORE consider: --------------------8<-------------------- .MAIN: all u1: .USE @echo u1 $@ u2: .USE @echo u2 $@ ub: .USEBEFORE @echo; echo ub $@ all: foo1 foo2 foo3 foo1: u1 u2 ub foo2: u2 ub u1 foo3: u2 u1 ub --------------------8<-------------------- when this makefile is run the output is ub foo1 u1 foo1 u2 foo1 ub foo2 u2 foo2 u1 foo2 ub foo3 u2 foo3 u1 foo3 note that u1 and u2 are applied in the order given, but ub is always done first. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 22:21:32 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6EFEB4DF; Sat, 31 Jan 2015 22:21:32 +0000 (UTC) Received: from graal.it-profi.org.ua (graal.shurik.kiev.ua [193.239.74.7]) (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 2137520C; Sat, 31 Jan 2015 22:21:31 +0000 (UTC) Received: from [46.164.154.106] (helo=thinkpad.it-profi.org.ua) by graal.it-profi.org.ua with esmtpa (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YHgPm-0001HJ-JM; Sun, 01 Feb 2015 00:21:18 +0200 Message-ID: <54CD555E.9060101@shurik.kiev.ua> Date: Sun, 01 Feb 2015 00:21:18 +0200 From: Alexandr Krivulya User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miguel Clara , Elizabeth Myers Subject: Re: Questions on adding backlight support for the i915 driver References: <54C883E7.4000300@interlinked.me> <54CC57CE.2080001@interlinked.me> <54CC7288.3040409@interlinked.me> <54CC8FF7.4020507@interlinked.me> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 46.164.154.106 X-SA-Exim-Mail-From: shuriku@shurik.kiev.ua X-SA-Exim-Scanned: No (on graal.it-profi.org.ua); SAEximRunCond expanded to false Cc: Adrian Chadd , freebsd-current , Konstantin Belousov , Justin Hibbits X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2015 22:21:32 -0000 31.01.2015 10:30, Miguel Clara пишет: > On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers > wrote: > >> On 01/31/15 02:15, Miguel Clara wrote: >>> Working fine on a HP running current as I've noted in the other thread >>> as for the keys. >>> This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys, >>> and my Acer (and I think not all are like this) use "Fn+<-/->" >> If your keys work (as in, they do things in FreeBSD), does sysctl and >> the keys work together just fine with no weird effects? >> >> The only weird problem I could possibly think of that could come up is >> that the keys do a simple add/subtract to the PCM values, and so the >> brightness ends up wrong. See if that happens. >> >> > Well, in the HP the keys don't do nothing it seems not even "xev" reports > anything when I use them, but they could be wrongly mapped maybe... > > On the acer I do see keycodes from xev, but Im using lumina and If I try to > map them to anything it doesn't work... I'll see what happens after reboot > though. > > All works fine (sysctl and Fn-keys) on my Thinkpad E530 with IvyBridge!