From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 30 02:50:55 2014 Return-Path: Delivered-To: freebsd-hackers@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 9DD99C12 for ; Sun, 30 Nov 2014 02:50:55 +0000 (UTC) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001: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 681DD86D for ; Sun, 30 Nov 2014 02:50:55 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id rl12so7678049iec.16 for ; Sat, 29 Nov 2014 18:50:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1S8kaWn9OVJEU7ImliyKI08BeAuOQsfa1/3STlxH5Wg=; b=cNz8uJUXEYzJBymEaKCwq3pDJVsyz1KQvYmR0mKoFutCa0hFBryHU0k2L5Se1jPZ2i gbK9wGueOfZ+NGbTysUb9t0I8uG3EnNJzXpxG/zC7ccjdVEtKjgsb3XUvRvf1kFs/MWw 2w7BSUZt7vpzp/dIjPCIO5d8BkAoviCDqQgzmzX3nFZ6QGbxlSBxrG8F8L/ZCX9URAR4 gHopfl9wQukgbMTECtl1C6b0OM497mA3oHCpdeEo5/S3KiAoEy73Hw9H8xJu2argxyWR /S2spkLV53mTIlU0gmH16nUJJa7dMZyKSOMRHdeyF01RjY2R8s4tNqS6vSU/wLEWl/UL y3uQ== MIME-Version: 1.0 X-Received: by 10.43.66.9 with SMTP id xo9mr41103852icb.67.1417315854930; Sat, 29 Nov 2014 18:50:54 -0800 (PST) Received: by 10.64.147.164 with HTTP; Sat, 29 Nov 2014 18:50:54 -0800 (PST) Date: Sat, 29 Nov 2014 18:50:54 -0800 Message-ID: Subject: klang refuses to compile kernel From: Dieter BSD To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 02:50:55 -0000 10.1 on amd64 Attempting to compile a kernel, but klang throws up: >>> stage 3.1: making dependencies ... cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector /usr/src/sys/amd64/amd64/genassym.c cc: error: unknown argument: '-frename-registers' cc: error: unknown argument: '-finline-limit=8000' *** Error code 1 The mighty google found 7 hits, none of which are useful. Find(1) did not find gcc. The source of -frename-registers must be: /usr/src/sys/conf/kern.pre.mk .if ${COMPILER_TYPE} != "clang" COPTFLAGS?=-O2 -frename-registers -pipe .else COPTFLAGS?=-O2 -pipe .endif So it looks like make doesn't know what compiler it is using? find /usr/src/ | xargs grep "inline-limit=8000" didn't find anything. From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 30 12:52:54 2014 Return-Path: Delivered-To: hackers@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 D868DF47 for ; Sun, 30 Nov 2014 12:52:54 +0000 (UTC) Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) (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 98F35FDB for ; Sun, 30 Nov 2014 12:52:53 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 10so4027038ykt.19 for ; Sun, 30 Nov 2014 04:52:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:message-id:date:to :mime-version; bh=lHMrGiwKbyvS/chf/xl1Nlwi8pWEPZt5tB4Vhs1XumI=; b=CEHyfkfdMDKzodM9GBpdRPUuzYNLiuQv/iuYe/hHM2VPsdjEYNMiF7M5Pb/UX7xolt zd3/fS46g2ytHBItnGd9OTiJs7SONHn3K0jjZYfIdK+1jWAHsa8QEx65NiNHNw0naTJt BUYow1Hr/B1eYUd1R1j6q+tPjhkUWQa6yVLARobC84MTt+QT58U5vLsWTjq6NTq13hk/ VJAiX97o5xqa2eQQ0E8CjgP6ANm8Eur25z9ak94ZH6drcLB2U1ze10xZhxBCIb3jBK5S +md+Z7SbfyPP/oDKEVf+dr7JhPFq1QmdhEL6SSDuyaPRivc4x9Pn+AKOYF6Q9DRojDE1 BnQA== X-Gm-Message-State: ALoCoQkFT+DAfmHXuXGVxIWR3N3VE33fSGCsybHh0iik9ury8UooJKU7myR3S9XmgvQN8xXhprGO X-Received: by 10.170.113.23 with SMTP id f23mr60494187ykb.79.1417351967346; Sun, 30 Nov 2014 04:52:47 -0800 (PST) Received: from [192.168.1.71] (107-207-39-13.lightspeed.sntcca.sbcglobal.net. [107.207.39.13]) by mx.google.com with ESMTPSA id f71sm9004854yha.42.2014.11.30.04.52.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Nov 2014 04:52:46 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Subject: 10.1 hangs during boot on Intel DP35DP board Message-Id: Date: Sun, 30 Nov 2014 04:52:45 -0800 To: hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-Mailman-Approved-At: Sun, 30 Nov 2014 13:18:15 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 12:52:55 -0000 I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and the = latest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. = However neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond = the =E2=80=9CTimecounters tick every 1.000 msec=E2=80=9C section of = probing. It wedges hard after that line and you have to pus the reset = button. I=E2=80=99ve tried turning off ACPI in the boot loader. That = does not work. I=E2=80=99ve tried turning on and off most of the = options in the BIOS that seem like they might impact things and none of = those have worked. Does anyone have any suggestions? Is anyone running = this board under 9.x or 10.x? I can make this system available to = anyone in the bay area if you=E2=80=99re looking for a project. Any = help you can offer will be greatly appreciated. If I=E2=80=99ve sent = this to the wrong list, please let me know privately. Thank you Christopher -------- Christopher R. Bowman From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 30 14:29:27 2014 Return-Path: Delivered-To: freebsd-hackers@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 26BA6346 for ; Sun, 30 Nov 2014 14:29:27 +0000 (UTC) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 B1EB59DA for ; Sun, 30 Nov 2014 14:29:25 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id r20so22220697wiv.6 for ; Sun, 30 Nov 2014 06:29:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rjB0G2MkDElPAz/6Kb7TFCSsEn7m0yyxADZHoyVj0Qk=; b=bsXuSP74Paizkr4Ins+bvr6DRi6oD6fcIAviee9SWnPTWfh8aBSr9uiy+B4MmxxWNY DfdaWhO0UvlYTAsgqWJLydXwG4Yph0pYvBDkWB+qeLCDIyGYlOrTvAAl2mhRxlgcPppH P8sSoA29BOb3VCkOt9LMdMC5soc4omjZ7gCO0pSuDlzyqmLOhAreTXntxKOW9ULnOBuS pWGRafv3ISgUH66oWcCt8S1tFoiSSESrGeDOujfqhusKklBTJciKfF8pRdlN5LqsHZg+ +a4BuskiM9yr4N9ZUWJd7neadM26S5KZzop9cI60/Q9oHmbt037sUP0N9nF2U3v0Bx3s baOw== X-Gm-Message-State: ALoCoQlMWNn//lxiSsnttV8j/3WWTFdN6UYG9Y4nLw/t347H1Ms72i2ymkZcYDdsmBHcBNfuiSsa X-Received: by 10.180.91.201 with SMTP id cg9mr78318955wib.63.1417357757988; Sun, 30 Nov 2014 06:29:17 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id a2sm24348972wiy.11.2014.11.30.06.29.17 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Nov 2014 06:29:17 -0800 (PST) Message-ID: <547B2A20.6040708@multiplay.co.uk> Date: Sun, 30 Nov 2014 14:30:56 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: 10.1 hangs during boot on Intel DP35DP board References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 14:29:27 -0000 Not sure if is the same board but we've had to use the following to avoid a stall at a similar point on some machines: set hint.atkbdc.0.disabled=1 set hint.atkbd.0.disabled=1 boot On 30/11/2014 12:52, Christopher R. Bowman wrote: > I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and the latest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. However neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond the “Timecounters tick every 1.000 msec“ section of probing. It wedges hard after that line and you have to pus the reset button. I’ve tried turning off ACPI in the boot loader. That does not work. I’ve tried turning on and off most of the options in the BIOS that seem like they might impact things and none of those have worked. Does anyone have any suggestions? Is anyone running this board under 9.x or 10.x? I can make this system available to anyone in the bay area if you’re looking for a project. Any help you can offer will be greatly appreciated. If I’ve sent this to the wrong list, please let me know privately. > Thank you > Christopher > > -------- > Christopher R. Bowman > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 30 15:52:33 2014 Return-Path: Delivered-To: freebsd-hackers@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 B6639137 for ; Sun, 30 Nov 2014 15:52:33 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (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 64A3A156 for ; Sun, 30 Nov 2014 15:52:32 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::15d8:6c6:e17b:d806] (unknown [IPv6:2001:7b8:3a7:0:15d8:6c6:e17b:d806]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 2A4C0B80A; Sun, 30 Nov 2014 16:52:23 +0100 (CET) Subject: Re: klang refuses to compile kernel Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_8DE02723-0B40-4504-8868-80CFA69BEE23"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b1 From: Dimitry Andric In-Reply-To: Date: Sun, 30 Nov 2014 16:52:21 +0100 Message-Id: <29EC5C12-3304-4A00-8A22-0A3DB0221122@FreeBSD.org> References: To: Dieter BSD X-Mailer: Apple Mail (2.1993) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 15:52:33 -0000 --Apple-Mail=_8DE02723-0B40-4504-8868-80CFA69BEE23 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 30 Nov 2014, at 03:50, Dieter BSD wrote: >=20 > 10.1 on amd64 > Attempting to compile a kernel, but klang throws up: >=20 >>>> stage 3.1: making dependencies > ... > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=3Dc99 -g = -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes = -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa = -I/usr/src/sys/dev/cxgb > -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=3D8000= > --param inline-unit-growth=3D100 --param large-function-growth=3D1000 > -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=3Dkernel > -mno-red-zone -mno-mmx -mno-sse -msoft-float = -fno-asynchronous-unwind-tables > -ffreestanding -fstack-protector /usr/src/sys/amd64/amd64/genassym.c > cc: error: unknown argument: '-frename-registers' > cc: error: unknown argument: '-finline-limit=3D8000' > *** Error code 1 >=20 > The mighty google found 7 hits, none of which are useful. Well, Google will most likely not be able to find that clang just does not support those options. > Find(1) did not find gcc. >=20 > The source of -frename-registers must be: >=20 > /usr/src/sys/conf/kern.pre.mk >=20 > .if ${COMPILER_TYPE} !=3D "clang" > COPTFLAGS?=3D-O2 -frename-registers -pipe > .else > COPTFLAGS?=3D-O2 -pipe > .endif >=20 > So it looks like make doesn't know what compiler it is using? Maybe you are forcing COMPILER_TYPE in your build environment? Please post your full make.conf, src.conf and other relevant configuration files. -Dimitry --Apple-Mail=_8DE02723-0B40-4504-8868-80CFA69BEE23 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 iEYEARECAAYFAlR7PTgACgkQsF6jCi4glqOmdACg4ebo1+dmA2gD/Be1woK0v6P8 bRUAoK/w02+c1C/12D1BD5NmMUJ3Dcz8 =puXE -----END PGP SIGNATURE----- --Apple-Mail=_8DE02723-0B40-4504-8868-80CFA69BEE23-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 1 06:42:33 2014 Return-Path: Delivered-To: hackers@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 BDDAFE22 for ; Mon, 1 Dec 2014 06:42:33 +0000 (UTC) Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) (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 90039986 for ; Mon, 1 Dec 2014 06:42:33 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id rd3so10467875pab.21 for ; Sun, 30 Nov 2014 22:42:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:message-id:date:to :mime-version; bh=ZnN/hSnAdBQdBGO/KkU027ILt6Hb5982UxnrHUnBDCQ=; b=BcETEeN2njc4po4Es7LPkLeoPRAWi9665+CSljhzKLL6eC5eOsGyszNLX/wdroExMJ 7TzwFCogSV+jnkUqmUyt+lFA+Eoo6cd1jYh4sJF2DTx4Y0v3NDp2uGRoIj6HSkj8y/5r tSB/qmNhUmZA/akvmLYFQo4pJERitKK8n6+yNnPdiLHZLS5bj2bjbHdcR/z6fW+aYqUG geJ0nqkOJ/QQUTo3mmwVyGEy8esR48MiebA4JbZs7SkEpQHssFJS092sZL7XcGDaUNWx himQWXj6Gb0b2Hb5MW/dlD5ITKke4HKvTi3n542HJiz906oLC7u2+sgd2PP6FbRwHMfH eyCw== X-Gm-Message-State: ALoCoQnwbwcXptlV6lU0bKh7DaFZ9vgbnwLr/5Efpopnd0wdpr4glsLkhHpp6tlurHNCqO+anZPz X-Received: by 10.70.89.129 with SMTP id bo1mr99005054pdb.23.1417416146773; Sun, 30 Nov 2014 22:42:26 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id oz7sm3065546pbb.14.2014.11.30.22.42.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Nov 2014 22:42:26 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Subject: 10.1 hangs during boot on Intel DP35DP board Message-Id: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> Date: Sun, 30 Nov 2014 22:42:24 -0800 To: hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-Mailman-Approved-At: Mon, 01 Dec 2014 12:29:08 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 06:42:33 -0000 I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and the = latest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. = However neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond = the =E2=80=9CTimecounters tick every 1.000 msec=E2=80=9C section of = probing. It wedges hard after that line and you have to pus the reset = button. I=E2=80=99ve tried turning off ACPI in the boot loader. That = does not work. I=E2=80=99ve tried turning on and off most of the = options in the BIOS that seem like they might impact things and none of = those have worked. Does anyone have any suggestions? Is anyone running = this board under 9.x or 10.x? I can make this system available to = anyone in the bay area if you=E2=80=99re looking for a project. Any = help you can offer will be greatly appreciated. If I=E2=80=99ve sent = this to the wrong list, please let me know privately. Thank you Christopher -------- Christopher R. Bowman= From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 1 16:32:00 2014 Return-Path: Delivered-To: hackers@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 06693B58 for ; Mon, 1 Dec 2014 16:32:00 +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 8B48D6C8 for ; Mon, 1 Dec 2014 16:31:59 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id b13so14654870wgh.32 for ; Mon, 01 Dec 2014 08:31:58 -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=u9WKOc8uvxSM4H+ChcfeqgR2+mUvTL82zZXebibBINM=; b=SLSGpjIhIH+cVEPkg7pIWsFzYDIK1Q3MC7BK8kveXkrO49/IAy2hmWcFHWzWV64Kjt D+W16kGZimriL0+F778ppkGQofTdVY6Agu/8PehY99ZriB2pteEvsng52Z+6Ec2ziAZE 0hymu2qFwwbllURpdthhDxU2++mxR4SoJNs6cUtR93IWlQRn577P/SjUNRRU/txB8QNb JH5Qtv3pudkTG3audJlfpK1X5UyBzK9QXzvc4JJQFau5xXOHv28d1ybVUiq/zpZlmHpR ygATJC2u6hAKWr3lkcHAGDDTO4JQjkXKSV7pqZwkFciXykuvJp2K+SF6MgFDXoENtzQJ BelQ== MIME-Version: 1.0 X-Received: by 10.180.91.193 with SMTP id cg1mr3759996wib.26.1417451517611; Mon, 01 Dec 2014 08:31:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Mon, 1 Dec 2014 08:31:57 -0800 (PST) In-Reply-To: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> References: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> Date: Mon, 1 Dec 2014 08:31:57 -0800 X-Google-Sender-Auth: sM0NibxGTdNwHN3cj_QWGqXKB7U Message-ID: Subject: Re: 10.1 hangs during boot on Intel DP35DP board From: Adrian Chadd To: "Christopher R. Bowman" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 16:32:00 -0000 Hi! Does a boot verbose (set in the menu options) give more information? -a On 30 November 2014 at 22:42, Christopher R. Bowman w= rote: > I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and the = latest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. Howe= ver neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond the =E2= =80=9CTimecounters tick every 1.000 msec=E2=80=9C section of probing. It w= edges hard after that line and you have to pus the reset button. I=E2=80= =99ve tried turning off ACPI in the boot loader. That does not work. I=E2= =80=99ve tried turning on and off most of the options in the BIOS that seem= like they might impact things and none of those have worked. Does anyone = have any suggestions? Is anyone running this board under 9.x or 10.x? I c= an make this system available to anyone in the bay area if you=E2=80=99re l= ooking for a project. Any help you can offer will be greatly appreciated. = If I=E2=80=99ve sent this to the wrong list, please let me know privately. > Thank you > Christopher > > -------- > Christopher R. Bowman > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 1 22:48:55 2014 Return-Path: Delivered-To: hackers@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 AFD2ECC1 for ; Mon, 1 Dec 2014 22:48:55 +0000 (UTC) Received: from mail110.syd.optusnet.com.au (mail110.syd.optusnet.com.au [211.29.132.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5C75F346 for ; Mon, 1 Dec 2014 22:48:55 +0000 (UTC) Received: from localhost (webmail22.syd.optusnet.com.au [211.29.132.176]) (Authenticated sender: tonymaher@optusnet.com.au) by mail110.syd.optusnet.com.au (Postfix) with ESMTPSA id 90ADE783143; Tue, 2 Dec 2014 09:48:43 +1100 (AEDT) Message-Id: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> From: tonymaher@optusnet.com.au To: "Christopher R. Bowman" , hackers@freebsd.org X-Mailer: Optus 7.4.0.0 X-Originating-IP: 130.155.199.148 in-reply-to: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Tue, 02 Dec 2014 09:48:43 +1100 MIME-Version: 1.0 X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=dMCfxopb c=1 sm=1 tr=0 a=eC0xq+xrPzhqsFyNUFkSzA==:117 a=eC0xq+xrPzhqsFyNUFkSzA==:17 a=PO7r1zJSAAAA:8 a=Dp1o8jKmOSwA:10 a=TJnnowFgAAAA:8 a=tmzCbaEMAAAA:8 a=6I5d2MoRAAAA:8 a=shtTBE7RVXEpuHXS838A:9 a=QEXdDO2ut3YA:10 a=tCoh8EeFUQXLEKSlHoEA:9 a=Zd-MzZZmgfF2iqR3:21 a=_W_S_7VecoQA:10 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 22:48:55 -0000 Hello,=0A=0Athis board runs fine under 9.1, 9.2 and 9.3 (and previously= 8.x).=0AHave not tried 10.x=0A=0Auname -r=0A9.3-RELEASE-p5=0A=0Admideco= de -t baseboard=0A# dmidecode 2.12=0ASMBIOS 2.4 present.=0A=0AHandle 0x0= 006, DMI type 2, 20 bytes=0ABase Board Information=0A=C2=A0=C2=A0=C2=A0= Manufacturer: Intel Corporation=0A=C2=A0=C2=A0=C2=A0 Product Name: DP35= DP=0A=C2=A0=C2=A0=C2=A0 Version: AAD81073-207=0A...=0A=0Admidecode -t bi= os=0A# dmidecode 2.12=0ASMBIOS 2.4 present.=0A=0AHandle 0x0004, DMI type= 0, 24 bytes=0ABIOS Information=0A=C2=A0=C2=A0=C2=A0 Vendor: Intel Corp.= =0A=C2=A0=C2=A0=C2=A0 Version: DPP3510J.86A.0572.2009.0715.2346=0A=C2=A0= =C2=A0=C2=A0 Release Date: 07/15/2009=0A=C2=A0=C2=A0=C2=A0 Address: 0xF0= 000=0A=C2=A0=C2=A0=C2=A0 Runtime Size: 64 kB=0A=C2=A0=C2=A0=C2=A0 ROM Si= ze: 1024 kB=0A=C2=A0=C2=A0=C2=A0 Characteristics:=0A=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 PCI is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0= =C2=A0 BIOS is upgradeable=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 BIOS= shadowing is allowed=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Boot from= CD is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Selectable boot= is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 EDD is supported= =0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 8042 keyboard services are supp= orted (int 9h)=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Serial services a= re supported (int 14h)=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Printer s= ervices are supported (int 17h)=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0= CGA/mono video services are supported (int 10h)=0A=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 ACPI is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0= =C2=A0 USB legacy is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 A= TAPI Zip drive boot is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0= BIOS boot specification is supported=0A=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0= =C2=A0 Function key-initiated network boot is supported=0A=C2=A0=C2=A0= =C2=A0 =C2=A0=C2=A0=C2=A0 Targeted content distribution is supported=0A= =C2=A0=C2=A0=C2=A0 BIOS Revision: 0.0=0A=C2=A0=C2=A0=C2=A0 Firmware Revi= sion: 0.0=0A=0Admidecode -t processor=0A# dmidecode 2.12=0ASMBIOS 2.4 pr= esent.=0A=0AHandle 0x0000, DMI type 4, 35 bytes=0AProcessor Information= =0A=C2=A0=C2=A0=C2=A0 Socket Designation: CPU1=0A=C2=A0=C2=A0=C2=A0 Type= : Central Processor=0A=C2=A0=C2=A0=C2=A0 Family: Core 2 Duo=0A=C2=A0=C2= =A0=C2=A0 Manufacturer: Intel(R) Corporation=0A=C2=A0=C2=A0=C2=A0 ID: FB= 06 00 00 FF FB EB BF=0A=C2=A0=C2=A0=C2=A0 Signature: Type 0, Family 6,= Model 15, Stepping 11=0A=C2=A0=C2=A0=C2=A0 Flags:=0A=C2=A0=C2=A0 ...=0A= =C2=A0=C2=A0=C2=A0 Version: Intel(R) Core(TM)2 Duo CPU=C2=A0=C2=A0=C2=A0= =C2=A0 E6750=C2=A0 @ 2.66GHz=0A=C2=A0=C2=A0=C2=A0 Voltage: 1.6 V=0A=C2= =A0=C2=A0=C2=A0 External Clock: 333 MHz=0A=C2=A0=C2=A0=C2=A0 Max Speed:= 4000 MHz=0A=C2=A0=C2=A0=C2=A0 Current Speed: 2666 MHz=0A=C2=A0=C2=A0=C2= =A0 Status: Populated, Enabled=0A=C2=A0=C2=A0=C2=A0 Upgrade: Socket LGA7= 75=0A=C2=A0 ...=0A=0A----- Original Message -----=0AFrom: "Christopher R= . Bowman" =0ATo:=0ACc:=0ASent:= Sun, 30 Nov 2014 22:42:24 -0800=0ASubject:10.1 hangs during boot on Inte= l DP35DP board=0A=0A I have a pretty stock Intel DP35DP board with and E= 8400 Core2Duo and=0Athe latest BIOS off the Intel website. This board ru= ns 7.1 and 8.4=0Afine. However neither 9.1 nor 10.1 will boot the AMD64= memstick kernel=0Abeyond the =E2=80=9CTimecounters tick every 1.000 mse= c=E2=80=9C section of=0Aprobing. It wedges hard after that line and you= have to pus the reset=0Abutton. I=E2=80=99ve tried turning off ACPI in= the boot loader. That does=0Anot work. I=E2=80=99ve tried turning on an= d off most of the options in the=0ABIOS that seem like they might impact= things and none of those have=0Aworked. Does anyone have any suggestion= s? Is anyone running this board=0Aunder 9.x or 10.x? I can make this sys= tem available to anyone in the=0Abay area if you=E2=80=99re looking for= a project. Any help you can offer=0Awill be greatly appreciated. If I= =E2=80=99ve sent this to the wrong list,=0Aplease let me know privately.= =0A Thank you=0A Christopher=0A=0A --------=0A Christopher R. Bowman=0A= _______________________________________________=0A freebsd-hackers@free= bsd.org mailing list=0A http://lists.freebsd.org/mailman/listinfo/freebs= d-hackers=0A To unsubscribe, send any mail to=0A"freebsd-hackers-unsubsc= ribe@freebsd.org"=0A-------------------------=0AEmail sent using Optus W= ebmail From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 09:03:37 2014 Return-Path: Delivered-To: hackers@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 606B5DA2 for ; Tue, 2 Dec 2014 09:03:37 +0000 (UTC) Received: from mail109.syd.optusnet.com.au (mail109.syd.optusnet.com.au [211.29.132.80]) by mx1.freebsd.org (Postfix) with ESMTP id 22F01A2E for ; Tue, 2 Dec 2014 09:03:36 +0000 (UTC) Received: from zen.home (c211-30-203-218.thorn2.nsw.optusnet.com.au [211.30.203.218]) (Authenticated sender: tonymaher@optusnet.com.au) by mail109.syd.optusnet.com.au (Postfix) with ESMTPA id C8064D61311; Tue, 2 Dec 2014 19:38:35 +1100 (AEDT) Message-ID: <547D7A8B.3090803@optusnet.com.au> Date: Tue, 02 Dec 2014 19:38:35 +1100 From: Tony Maher User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "Christopher R. Bowman" Subject: Re: 10.1 hangs during boot on Intel DP35DP board References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=BdjhjNd2 c=1 sm=1 tr=0 a=MQ6uhdTv3FoGARDo7fdH2w==:117 a=MQ6uhdTv3FoGARDo7fdH2w==:17 a=PO7r1zJSAAAA:8 a=_M8H_RHeOCMA:10 a=IkcTkHD0fZMA:10 a=8VOBirz-hs5gHyCHR08A:9 a=QEXdDO2ut3YA:10 a=xXYpSUSE7EsA:10 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 09:03:37 -0000 Hello Christopher, On 12/02/14 16:39, Christopher R. Bowman wrote: > Tony, Thank you so much for your response. We do indeed appear to > have the same board and BIOS revision. How odd that yours boots the > 9.x series and mine will not despite running fine in 8.4. It is at > least helpful to know that it can boot later kernels even if I don=E2=80= =99t > know how to get it to do it yet. IF you have any suggestions I would > be grateful, again thank you for your response. Christopher Perhaps it is just the booting from memstick that is the issue? I would try a USB memory stick but do not have one here but if can get one I will give it a try. Does booting from an installation CD work? cheers --=20 Tony Maher email: tonymaher@optusnet.com.au From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 05:39:36 2014 Return-Path: Delivered-To: hackers@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 2D80B344 for ; Tue, 2 Dec 2014 05:39:36 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (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 F18791C1 for ; Tue, 2 Dec 2014 05:39:35 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ey11so12595164pad.24 for ; Mon, 01 Dec 2014 21:39:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:message-id:references:to; bh=ZFnB4nlXBWjAFVHg9OYJKDrtxw8285856N8keB9ZsMs=; b=Drpc0FQaZD0r9rK3/IuQ6nvaKlBWwXMYzR5bW9dvibdpPqjopLciczOYe4gd0MzpfY pnUWuY52dcbQc57rWsmuSiYhFUgwPzdmWZCaS3t6DlLY55AJAwVErAtibiMA96gJ4YkO 2o6j1K3PF7y0hnDWtuYCGD5+aeGxKb/UaetrnUga1sx8K2uX8MeRNf5dvdKx13YkTOQa NH1xK0Q/q/eXUcxqhjKmr/Ca7vcYqzFGWt1HW2/t6kAeL/RQBY6qo6Qana19uez1LCjK hzC+pgB1pS6led7G9KgT651dc+F5YKlIHruFAYgEG5S7tJorgHLaUri7yL8nadWkdQbd yacA== X-Gm-Message-State: ALoCoQllT/gQSX/cuNfOB8aNkJYfJUhMiGf79r17A/J1AQ+WXgXgb/urVUbv7R76fOCZbYdLKZr2 X-Received: by 10.68.65.79 with SMTP id v15mr2766596pbs.56.1417498769634; Mon, 01 Dec 2014 21:39:29 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id m3sm18504200pda.75.2014.12.01.21.39.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Dec 2014 21:39:28 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> Date: Mon, 1 Dec 2014 21:39:27 -0800 Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> To: tonymaher@optusnet.com.au X-Mailer: Apple Mail (2.1993) X-Mailman-Approved-At: Tue, 02 Dec 2014 12:19:03 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 05:39:36 -0000 Tony, Thank you so much for your response. We do indeed appear to = have the same board and BIOS revision. How odd that yours boots the 9.x = series and mine will not despite running fine in 8.4. It is at least = helpful to know that it can boot later kernels even if I don=E2=80=99t = know how to get it to do it yet. IF you have any suggestions I would be = grateful, again thank you for your response. Christopher > On Dec 1, 2014, at 2:48 PM, tonymaher@optusnet.com.au wrote: >=20 > Hello, >=20 > this board runs fine under 9.1, 9.2 and 9.3 (and previously 8.x). > Have not tried 10.x >=20 > uname -r > 9.3-RELEASE-p5 >=20 > dmidecode -t baseboard > # dmidecode 2.12 > SMBIOS 2.4 present. >=20 > Handle 0x0006, DMI type 2, 20 bytes > Base Board Information > Manufacturer: Intel Corporation > Product Name: DP35DP > Version: AAD81073-207 > ... >=20 >=20 > dmidecode -t bios > # dmidecode 2.12 > SMBIOS 2.4 present. >=20 > Handle 0x0004, DMI type 0, 24 bytes > BIOS Information > Vendor: Intel Corp. > Version: DPP3510J.86A.0572.2009.0715.2346 > Release Date: 07/15/2009 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 1024 kB > Characteristics: > PCI is supported > BIOS is upgradeable > BIOS shadowing is allowed > Boot from CD is supported > Selectable boot is supported > EDD is supported > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > CGA/mono video services are supported (int 10h) > ACPI is supported > USB legacy is supported > ATAPI Zip drive boot is supported > BIOS boot specification is supported > Function key-initiated network boot is supported > Targeted content distribution is supported > BIOS Revision: 0.0 > Firmware Revision: 0.0 >=20 > dmidecode -t processor > # dmidecode 2.12 > SMBIOS 2.4 present. >=20 > Handle 0x0000, DMI type 4, 35 bytes > Processor Information > Socket Designation: CPU1 > Type: Central Processor > Family: Core 2 Duo > Manufacturer: Intel(R) Corporation > ID: FB 06 00 00 FF FB EB BF > Signature: Type 0, Family 6, Model 15, Stepping 11 > Flags: > ... > Version: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz > Voltage: 1.6 V > External Clock: 333 MHz > Max Speed: 4000 MHz > Current Speed: 2666 MHz > Status: Populated, Enabled > Upgrade: Socket LGA775 > ... >=20 >=20 >=20 > ----- Original Message ----- > From: > "Christopher R. Bowman" >=20 > To: > > Cc: >=20 > Sent: > Sun, 30 Nov 2014 22:42:24 -0800 > Subject: > 10.1 hangs during boot on Intel DP35DP board >=20 >=20 > I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and = the latest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. = However neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond = the =E2=80=9CTimecounters tick every 1.000 msec=E2=80=9C section of = probing. It wedges hard after that line and you have to pus the reset = button. I=E2=80=99ve tried turning off ACPI in the boot loader. That = does not work. I=E2=80=99ve tried turning on and off most of the options = in the BIOS that seem like they might impact things and none of those = have worked. Does anyone have any suggestions? Is anyone running this = board under 9.x or 10.x? I can make this system available to anyone in = the bay area if you=E2=80=99re looking for a project. Any help you can = offer will be greatly appreciated. If I=E2=80=99ve sent this to the = wrong list, please let me know privately. > Thank you > Christopher >=20 > -------- > Christopher R. Bowman > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" > Email sent using Optus Webmail From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 05:58:01 2014 Return-Path: Delivered-To: hackers@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 AD2DE747 for ; Tue, 2 Dec 2014 05:58:01 +0000 (UTC) Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) (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 7C0A73A7 for ; Tue, 2 Dec 2014 05:58:01 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id eu11so12730806pac.11 for ; Mon, 01 Dec 2014 21:58: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:from:content-type:mime-version:subject :in-reply-to:date:cc:message-id:references:to; bh=0nJT+PJJmE6l5r+6ZX4QYJvEo+lE+sMyzl3jU0tlTPo=; b=mGbjNEY+OIXtPHfG6zSbme35wPoNNCisNWGDrUoRgnAFt8zq2rddR8aa1lzwrB8lOv TEU9myWB8i6Gb6LV0VriChAN8N293Rc1Wl3yRPv7udKdgJmKI6BWQw0O3x+26Pvbrat0 7yzjuBB5MB0RmUDnzR6Lv0iAy7AivR3Qc2xvTsPj9cMQVHlgr+jR6a68pnlp0lixNk9I S90u5um16jxUn0cZlLjAVUHhWzr7/o0X6DkhUX/7pVfKpN3/9GM5OmY2L1KFsi0V2jWF lzjjgorWnM4cWhnstIVpfQNDtFw2HkFiEI5PNgrNe5JvhP9xSXUBT6tUw60oQLPYMLVu I1PQ== X-Gm-Message-State: ALoCoQki9I0V7rkIHgI3TmSyB8MsBXs55wSSS95RlD4ry1yck97Aj/HUL/hbdFoXKvYBgI+lyuIO X-Received: by 10.67.14.71 with SMTP id fe7mr107447888pad.27.1417499473507; Mon, 01 Dec 2014 21:51:13 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id kj9sm19067345pbc.37.2014.12.01.21.51.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Dec 2014 21:51:12 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: Date: Mon, 1 Dec 2014 21:51:11 -0800 Message-Id: <5208EB1C-0AC4-4893-915E-20F8D847C273@ChrisBowman.com> References: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> To: Adrian Chadd X-Mailer: Apple Mail (2.1993) X-Mailman-Approved-At: Tue, 02 Dec 2014 12:26:38 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 05:58:01 -0000 Adrian, Hi! Thank you for your response. Booting verbose does indeed = produce more information. It still reaches the Timecounters line but = now also produces the following output after that: vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcphashsize auto tuned to 16384 lo0: bpf attached hpt27xx: no controller detected. hptrr: no controller detected. hptnr: no controller detected. And then it hangs again with no indication of why and you have to push = reset as the keyboard is non responsive. Any suggestions? Again I=E2=80=99= m happy to try and suggestion or even loan out the machine to someone = who=E2=80=99s looking for a puzzle to solve. (You=E2=80=99re here in = the bay area aren=E2=80=99t you? I think we met at a meetBSD year = before last, was that you?) Again, thanks for the response and don=E2=80=99t hesitate if you have = more questions or suggestions. Christopher > On Dec 1, 2014, at 8:31 AM, Adrian Chadd wrote: >=20 > Hi! >=20 > Does a boot verbose (set in the menu options) give more information? >=20 >=20 >=20 > -a >=20 >=20 > On 30 November 2014 at 22:42, Christopher R. Bowman = wrote: >> I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and = the latest BIOS off the Intel website. This board runs 7.1 and 8.4 = fine. However neither 9.1 nor 10.1 will boot the AMD64 memstick kernel = beyond the =E2=80=9CTimecounters tick every 1.000 msec=E2=80=9C section = of probing. It wedges hard after that line and you have to pus the = reset button. I=E2=80=99ve tried turning off ACPI in the boot loader. = That does not work. I=E2=80=99ve tried turning on and off most of the = options in the BIOS that seem like they might impact things and none of = those have worked. Does anyone have any suggestions? Is anyone running = this board under 9.x or 10.x? I can make this system available to = anyone in the bay area if you=E2=80=99re looking for a project. Any = help you can offer will be greatly appreciated. If I=E2=80=99ve sent = this to the wrong list, please let me know privately. >> Thank you >> Christopher >>=20 >> -------- >> Christopher R. Bowman >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 15:32:26 2014 Return-Path: Delivered-To: hackers@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 DC426F5C for ; Tue, 2 Dec 2014 15:32:26 +0000 (UTC) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::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 7B7EC95B for ; Tue, 2 Dec 2014 15:32:26 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id l2so17333564wgh.13 for ; Tue, 02 Dec 2014 07:32:24 -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=aCl9SFwpMXenFObCHd8hskAaovmJDgpADrU9UPAe7To=; b=XEPrMmoGhrcWY+Ghr4aJfKDCdLB0BqCvG4DooA+dymferMZQlOrgmKIMx996+iY9/j la4pn+hU7IS/YySvUJ05x1eHm/eVSTE3eClb+0yjjgG/1gEWQTsQPyB1cexxSNaN8JuV bNbMuQI7TwWXNEXX9Js6nYeHwOKhfNhoSR83ntDwQ42v3P7mS+X1YzUjGbFJLtuj/HaH vqD6tXJqfVV7Ltvg3rIlETxQhvHGkWuOFSXA8qi/pscxZwqrPWiyMt87QSiAuELgmihS pRey82qnAw5CkgnTxorhfmbGd++K9MEes2MFqn5alHQAQO2y3RhZMZgSC/F24jqZ35Ip WI+g== MIME-Version: 1.0 X-Received: by 10.180.91.193 with SMTP id cg1mr11953069wib.26.1417534344836; Tue, 02 Dec 2014 07:32:24 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Tue, 2 Dec 2014 07:32:24 -0800 (PST) In-Reply-To: <547D7A8B.3090803@optusnet.com.au> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> Date: Tue, 2 Dec 2014 07:32:24 -0800 X-Google-Sender-Auth: zfzQfrWp6ikc_U0bfKpiYDODxnM Message-ID: Subject: Re: 10.1 hangs during boot on Intel DP35DP board From: Adrian Chadd To: Tony Maher Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "Christopher R. Bowman" , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 15:32:27 -0000 Hi! Would you try booting a freebsd-head snapshot, just to compare? -a On 2 December 2014 at 00:38, Tony Maher wrote: > Hello Christopher, > > On 12/02/14 16:39, Christopher R. Bowman wrote: >> >> Tony, Thank you so much for your response. We do indeed appear to >> have the same board and BIOS revision. How odd that yours boots the >> 9.x series and mine will not despite running fine in 8.4. It is at >> least helpful to know that it can boot later kernels even if I don=E2=80= =99t >> know how to get it to do it yet. IF you have any suggestions I would >> be grateful, again thank you for your response. Christopher > > > Perhaps it is just the booting from memstick that is the issue? > I would try a USB memory stick but do not have one here but if can get > one I will give it a try. > Does booting from an installation CD work? > > cheers > -- > Tony Maher email: tonymaher@optusnet.com.au > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 20:40:00 2014 Return-Path: Delivered-To: freebsd-hackers@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 52FFE935 for ; Tue, 2 Dec 2014 20:40:00 +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 1A6CCEFE for ; Tue, 2 Dec 2014 20:40:00 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id tp5so12379326ieb.12 for ; Tue, 02 Dec 2014 12:39:59 -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=Yxt6pBD3u76ggQKZlzPowzT4YfyEaU5JemJB6JDY29o=; b=pOAmbkspDh0Yn4I/UWxTuhc6u5ZuzCOQ2CPqJfkt3umf8UofbPFqLNAzr2IN4Va4Vq VI0qMNRSD6FNY2s0oSgScYuMgtc3/4CIH/AgQyeIBotqzON2b8rYW0v4TlU+4UtaaDMn KerYV0QQNMsJj095FdIfr6zPPZIR7hYAlM+0WC7Rq/9/c9ybuLIR/mzOrYSi6Gn83hav 61W5G3JQB1n5XmRe0IIwyHPWLXiAO2bTZSSwvhIiUd/bNr9P9ZdkYhBtOmXa5EEExfnU cSxL92vnd7TmamyyTJvkrtfbZFqDd62na9s4yBJwrfGesFdK+mn40iof4rmJJLz+0JTI 0d/g== X-Received: by 10.43.2.4 with SMTP id ns4mr4269651icb.13.1417552799530; Tue, 02 Dec 2014 12:39:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.214 with HTTP; Tue, 2 Dec 2014 12:39:29 -0800 (PST) From: arrowdodger <6yearold@gmail.com> Date: Wed, 3 Dec 2014 00:39:29 +0400 Message-ID: Subject: Mapping SCSI driver to USB one. To: freebsd-hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 20:40:00 -0000 Hello. I'm playing around with sysutils/hal sources and can't find a way to obtain a SCSI driver to the corresponding USB device. In other words, knowing "umass0" i want to get "da0" for it. >From what i can tell, HAL uses CAM API's (/dev/xpt0 stuff), but working with it requires elevated privileges. Probably, because of that hald-runner is running under root. Is there any way to perform such mapping as regular user? From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 20:54:33 2014 Return-Path: Delivered-To: freebsd-hackers@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 6D01BC2F for ; Tue, 2 Dec 2014 20:54:33 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E3BF12D for ; Tue, 2 Dec 2014 20:54:32 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0529C1FE022; Tue, 2 Dec 2014 21:54:23 +0100 (CET) Message-ID: <547E271A.6070005@selasky.org> Date: Tue, 02 Dec 2014 21:54:50 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: arrowdodger <6yearold@gmail.com>, freebsd-hackers Subject: Re: Mapping SCSI driver to USB one. References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 20:54:33 -0000 On 12/02/14 21:39, arrowdodger wrote: > Hello. > I'm playing around with sysutils/hal sources and can't find a way to obtain > a SCSI driver to the corresponding USB device. In other words, knowing > "umass0" i want to get "da0" for it. >>From what i can tell, HAL uses CAM API's (/dev/xpt0 stuff), but working > with it requires elevated privileges. Probably, because of that hald-runner > is running under root. > Is there any way to perform such mapping as regular user? Hi, Maybe "devinfo" will give you the answer. --HPS From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 2 23:20:22 2014 Return-Path: Delivered-To: hackers@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 C388234C for ; Tue, 2 Dec 2014 23:20:22 +0000 (UTC) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) (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 953C6314 for ; Tue, 2 Dec 2014 23:20:22 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id kx10so14478213pab.30 for ; Tue, 02 Dec 2014 15:20:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=O2SXoxIXIEHaSGggDTqW6Q6NR21yYIlar7Nj/519Kj0=; b=F5uXx2zsYwQjACkkspFsTMYz0t+0uZC5ouGyi7wBfaomd8Fpz68yuApA4F0Cwsmk03 IoO5uNJWw3srCT9BI8qyxdJLTN669+zVSaLRzKGzYQWHsmqynz6q133l7gIZcXy+dwMS 44r5O6GkAASY7kJrojMDcGPLRV1ivE3jQG915buhis4OGwBEBfqH9oRUgzEBu0qqBpCq 5ICXwphd0gfCxF5ZrJ4TI/xv8fGlb2bUFWlNXARu+LBBKC3f4KpfdhGASC9pxctC8WqW Clf6QhxHgR21MIJovum+NtaNGNvIknddjbth0tiElYE2zuANUugs/bFfQOrEr6CsfjVh bVUg== X-Gm-Message-State: ALoCoQlbOlL/iIGwayB9tVaTt+qjr/jb+zYfgK6+hOXNjBdTx87pO4xcX0LgE5B6P7qWBxUYRaqR X-Received: by 10.70.102.77 with SMTP id fm13mr3219858pdb.96.1417562416254; Tue, 02 Dec 2014 15:20:16 -0800 (PST) Received: from [10.49.190.188] ([166.170.37.180]) by mx.google.com with ESMTPSA id xo4sm21197116pbc.45.2014.12.02.15.20.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Dec 2014 15:20:15 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: 10.1 hangs during boot on Intel DP35DP board X-Mailer: iPhone Mail (11D257) In-Reply-To: Date: Tue, 2 Dec 2014 15:20:12 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> To: Adrian Chadd Cc: Tony Maher , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 23:20:23 -0000 Adrian, Absolutely, it will take me a bit to download it and get it on a stick. 10 s= table or 11 current? Christopher > On Dec 2, 2014, at 7:32 AM, Adrian Chadd wrote: >=20 > Hi! >=20 > Would you try booting a freebsd-head snapshot, just to compare? >=20 >=20 > -a >=20 >=20 >> On 2 December 2014 at 00:38, Tony Maher wrote= : >> Hello Christopher, >>=20 >>> On 12/02/14 16:39, Christopher R. Bowman wrote: >>>=20 >>> Tony, Thank you so much for your response. We do indeed appear to >>> have the same board and BIOS revision. How odd that yours boots the >>> 9.x series and mine will not despite running fine in 8.4. It is at >>> least helpful to know that it can boot later kernels even if I don=E2=80= =99t >>> know how to get it to do it yet. IF you have any suggestions I would >>> be grateful, again thank you for your response. Christopher >>=20 >>=20 >> Perhaps it is just the booting from memstick that is the issue? >> I would try a USB memory stick but do not have one here but if can get >> one I will give it a try. >> Does booting from an installation CD work? >>=20 >> cheers >> -- >> Tony Maher email: tonymaher@optusnet.com.au >>=20 >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 00:26:29 2014 Return-Path: Delivered-To: freebsd-hackers@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 B97612A5 for ; Wed, 3 Dec 2014 00:26:29 +0000 (UTC) Received: from fallback.quonix.net (fallback.quonix.net [208.82.128.208]) (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 903FAC06 for ; Wed, 3 Dec 2014 00:26:29 +0000 (UTC) Received: from c.smtp.quonix.net (c.smtp.quonix.net [208.82.128.207]) by fallback.quonix.net (8.14.4/8.14.4) with ESMTP id sB2IIqKE004974 for ; Tue, 2 Dec 2014 18:18:52 GMT (envelope-from john@quonix.net) Received: from CORSAIR (pool-108-2-133-139.phlapa.fios.verizon.net [108.2.133.139]) by c.smtp.quonix.net (8.14.4/8.14.4) with ESMTP id sB300YbR089548 for ; Tue, 2 Dec 2014 19:00:34 -0500 (EST) (envelope-from john@quonix.net) From: "John Von Essen" To: Subject: Bind, DNS, and Denial of Service Date: Tue, 2 Dec 2014 19:00:06 -0500 Message-ID: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AdAOizL7eQ65amWvTISxcm41iPPnQQ== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 00:26:29 -0000 I figure this might be the best place to start this discussion. I've been using FreeBSD for ages for some core systems, one of those being Auth and public caching DNS. Lately I've been getting hit hard by reflective DDoS on DNS, so my old systems need some updating. Question is, what's the best/simplest solution moving forward? FreeBSD 9.3 or 10.1? Do I continue to use BIND with the rate-limiting feature, or go with something else? I will say, I tried to get a FreeBSD 10.1 instance running with BIND 10 - no luck, so I did BIND 9.9 with the RRL feature. It sort of worked, but was weird. I was getting a ton of weird responses on the server the moment I turned BIND on. Its been so long since I've worked on this stuff, my old 8.X machines have been running for years. I am open to using something else for the caching, but for the Auth I really want to stay with Bind. Its just really hard to implement BIND with RRL on newer freebsd distro's, I get the feeling that the FreeBSD folks want to move on from BIND. Any help would be appreciated. -John From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 01:50:16 2014 Return-Path: Delivered-To: hackers@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 370DF2E9 for ; Wed, 3 Dec 2014 01:50:16 +0000 (UTC) Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.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 080725E2 for ; Wed, 3 Dec 2014 01:50:15 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id y13so14412577pdi.30 for ; Tue, 02 Dec 2014 17:50: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:from:references:mime-version:in-reply-to :content-type:content-transfer-encoding:message-id:cc:subject:date :to; bh=oLDaZTIurs70fZj6u1VEF5NB1LaPbOylE4Ko+OGVtkE=; b=fth1RXeIa2NaI+x0a3bFJpuHD33xd5eCHPKJDHkf8FcUqbITn+ij3jp4pMWop+bNkw OFXveH90k8LeFkCnI+OVoFg+BtLBjZjn6thFCpNJtIa5jqn4EWzjwt8Q06++ODqDBOW2 O95bnZiwxgEgfRKwODYMEKOJJiwJWnWVu+DtIuxwN5FrVjcZwnyRA+O1SOVdvTktua5K G5aeXBYDXsELrjDGGx64ne3AAgyf13qJdqMF8jXZYyio2NRR9MzqC+OGXLTpYFCc/Ldq LuSDgxhBifqYmX1VHh0NFTI9FWtahUR9Dl3PuFAr333Q2XQs/a4HB3D8O51tuuQp23r/ VL6A== X-Gm-Message-State: ALoCoQk6eKii1qpsCGJtPWrWfX7vHszmwBtVQS3X8doyBLp6gBciREwZIAmKt+CbrB6p3VderFS6 X-Received: by 10.68.190.103 with SMTP id gp7mr11133416pbc.55.1417571414914; Tue, 02 Dec 2014 17:50:14 -0800 (PST) Received: from [10.0.0.30] (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id v4sm21398845pbs.10.2014.12.02.17.50.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Dec 2014 17:50:12 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> Mime-Version: 1.0 (1.0) In-Reply-To: <547D7A8B.3090803@optusnet.com.au> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPad Mail (11D257) Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Tue, 2 Dec 2014 17:50:14 -0800 To: Tony Maher Cc: "Christopher R. Bowman" , "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 01:50:16 -0000 Tony, Thanks again for the response 9.1 hangs in the way I described when boot= ing from DVD or USB stick. But the 8.4. Install went fine using a USB stick= . Christopher Sent from my iPad > On Dec 2, 2014, at 12:38 AM, Tony Maher wrote:= >=20 > Hello Christopher, >=20 >> On 12/02/14 16:39, Christopher R. Bowman wrote: >> Tony, Thank you so much for your response. We do indeed appear to >> have the same board and BIOS revision. How odd that yours boots the >> 9.x series and mine will not despite running fine in 8.4. It is at >> least helpful to know that it can boot later kernels even if I don=E2=80=99= t >> know how to get it to do it yet. IF you have any suggestions I would >> be grateful, again thank you for your response. Christopher >=20 > Perhaps it is just the booting from memstick that is the issue? > I would try a USB memory stick but do not have one here but if can get > one I will give it a try. > Does booting from an installation CD work? >=20 > cheers > --=20 > Tony Maher email: tonymaher@optusnet.com.au >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 02:17:54 2014 Return-Path: Delivered-To: freebsd-hackers@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 F229374E for ; Wed, 3 Dec 2014 02:17:54 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (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 C7FC791C for ; Wed, 3 Dec 2014 02:17:54 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id sB32I6gC064870; Tue, 2 Dec 2014 18:18:06 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: , "John Von Essen" In-Reply-To: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> References: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> From: "Chris H" Subject: Re: Bind, DNS, and Denial of Service Date: Tue, 02 Dec 2014 18:18:06 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 02:17:55 -0000 On Tue, 2 Dec 2014 19:00:06 -0500 "John Von Essen" wrote > I figure this might be the best place to start this discussion. > > > > I've been using FreeBSD for ages for some core systems, one of those being > Auth and public caching DNS. > > > > Lately I've been getting hit hard by reflective DDoS on DNS, so my old > systems need some updating. > > > > Question is, what's the best/simplest solution moving forward? FreeBSD 9.3 > or 10.1? Do I continue to use BIND with the rate-limiting feature, or go > with something else? > > > > I will say, I tried to get a FreeBSD 10.1 instance running with BIND 10 - no > luck, so I did BIND 9.9 with the RRL feature. It sort of worked, but was > weird. I was getting a ton of weird responses on the server the moment I > turned BIND on. > > > > Its been so long since I've worked on this stuff, my old 8.X machines have > been running for years. > > > > I am open to using something else for the caching, but for the Auth I really > want to stay with Bind. Its just really hard to implement BIND with RRL on > newer freebsd distro's, I get the feeling that the FreeBSD folks want to > move on from BIND. > > > > Any help would be appreciated. Hello, John. FWIW You might find dns/nsd a good fit. It's even possible to get it to output "Bind like" log messages. I've replaced the Bind on all, but one of our servers with it. In an effort to evaluate it for being a replacement. I'm finding it difficult to keep the last server still running the Bind going. So I'll probably have to replace it with something soon. Just haven't *yet* determined *what* other DNS to evaluate. I only ran into one issue with it (NSD). It was NSD itself, and the reaction time is extremely good (less than a week), and a new (fixed) version was out. Anyway. Just thought I'd share my experience. In case it helps. --Chris > > > > -John > > > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 02:40:22 2014 Return-Path: Delivered-To: freebsd-hackers@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 8E99DA78 for ; Wed, 3 Dec 2014 02:40:22 +0000 (UTC) Received: from a.smtp.quonix.net (a.smtp.quonix.net [208.82.128.205]) (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 3907BB79 for ; Wed, 3 Dec 2014 02:40:21 +0000 (UTC) Received: from CORSAIR (pool-108-2-133-139.phlapa.fios.verizon.net [108.2.133.139]) by a.smtp.quonix.net (8.14.4/8.14.4) with ESMTP id sB32PwcR017801 for ; Tue, 2 Dec 2014 21:25:58 -0500 (EST) (envelope-from john@quonix.net) From: "John Von Essen" To: References: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> In-Reply-To: <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> Subject: RE: Bind, DNS, and Denial of Service Date: Tue, 2 Dec 2014 21:25:30 -0500 Message-ID: <004e01d00ea0$6b7c7860$42756920$@quonix.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AQIiVaX5sQQmCKXYgP76APFhH9lhjgE5aAZTm87JC9A= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 02:40:22 -0000 Thanks... Right now I have a FreeBSD 9.3 system, after a clean install I = went in and built Bind99 from ports with the RRL option. Question is how do I force /etc/rc.d/named to use the new bind9.9 that I = built from ports and now resides in /usr/local/sbin? Do I just edit /etc/defaults/rc.conf and tell it to use = /usr/local/sbin/named instead of /usr/sbin/named? I thought there might be a cleaner way to do this, just curious. -John -----Original Message----- From: Chris H [mailto:bsd-lists@bsdforge.com]=20 Sent: Tuesday, December 02, 2014 9:18 PM To: freebsd-hackers@freebsd.org; John Von Essen Subject: Re: Bind, DNS, and Denial of Service On Tue, 2 Dec 2014 19:00:06 -0500 "John Von Essen" = wrote > I figure this might be the best place to start this discussion. >=20 > =20 >=20 > I've been using FreeBSD for ages for some core systems, one of those=20 > being Auth and public caching DNS. >=20 > =20 >=20 > Lately I've been getting hit hard by reflective DDoS on DNS, so my old = > systems need some updating. >=20 > =20 >=20 > Question is, what's the best/simplest solution moving forward? FreeBSD = > 9.3 or 10.1? Do I continue to use BIND with the rate-limiting feature, = > or go with something else? >=20 > =20 >=20 > I will say, I tried to get a FreeBSD 10.1 instance running with BIND=20 > 10 - no luck, so I did BIND 9.9 with the RRL feature. It sort of=20 > worked, but was weird. I was getting a ton of weird responses on the=20 > server the moment I turned BIND on. >=20 > =20 >=20 > Its been so long since I've worked on this stuff, my old 8.X machines=20 > have been running for years. >=20 > =20 >=20 > I am open to using something else for the caching, but for the Auth I=20 > really want to stay with Bind. Its just really hard to implement BIND=20 > with RRL on newer freebsd distro's, I get the feeling that the FreeBSD = > folks want to move on from BIND. >=20 > =20 >=20 > Any help would be appreciated. Hello, John. FWIW You might find dns/nsd a good fit. It's even possible to get it to = output "Bind like" log messages. I've replaced the Bind on all, but one = of our servers with it. In an effort to evaluate it for being a = replacement. I'm finding it difficult to keep the last server still = running the Bind going. So I'll probably have to replace it with something soon. Just haven't = *yet* determined *what* other DNS to evaluate. I only ran into one issue = with it (NSD). It was NSD itself, and the reaction time is extremely = good (less than a week), and a new (fixed) version was out. Anyway. Just thought I'd share my experience. In case it helps. --Chris >=20 > =20 >=20 > -John >=20 > =20 >=20 > =20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list=20 > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 02:58:09 2014 Return-Path: Delivered-To: freebsd-hackers@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 BC2F5D91 for ; Wed, 3 Dec 2014 02:58:09 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.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 8E01ECB3 for ; Wed, 3 Dec 2014 02:58:09 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id r10so14563213pdi.27 for ; Tue, 02 Dec 2014 18:58: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:from:references:mime-version:in-reply-to :content-type:content-transfer-encoding:message-id:cc:subject:date :to; bh=WJu04ERidSVXZyNTRDstqV6Z4oYUjkP+yQQmEOBoZ6w=; b=OgRojyZSz04CUT8LxF6FJ+Tzgh1BKYp/tMGoEiaPD9S4/3+lQm6VmDLnjfGvOwk4Oj B++ybacT3vDh5Zy09fzK4n4AmjM/bsGcfRSz/xZu0Kpd8qQs9mCEQUYqMzN1FcvUFG0q krl0SHYRj5iZGn1MNakAkQMtYRHMUt5zjBpIYskT3A0SZZY7snvN34T9jGdCnVyjxKjW uzm8xksYn57c5kcSDYIHb1wlKcChC06kKgNZIpT7UAMnvt6QXwlor+iFBbIIzN9P8heh gkxcqKsmepl/+OUfmGJCJEZdCqQoukuWmLx++fcgN5cr0m65TYIODpjyyRtRy+hJc2RY 7OVQ== X-Gm-Message-State: ALoCoQmIxB7xaZg6dO1GwltmsbevQZNBamj42Ha1VJdG8CMvAJKIUZvUw/YNGn91Lm4I9oy2KlN0 X-Received: by 10.68.170.130 with SMTP id am2mr11378433pbc.156.1417575488553; Tue, 02 Dec 2014 18:58:08 -0800 (PST) Received: from [10.0.0.30] (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id he1sm433177pac.29.2014.12.02.18.58.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Dec 2014 18:58:07 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" References: <547B2A20.6040708@multiplay.co.uk> Mime-Version: 1.0 (1.0) In-Reply-To: <547B2A20.6040708@multiplay.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <65CC52D9-455D-4141-865F-061E27E8223C@ChrisBowman.com> X-Mailer: iPad Mail (11D257) Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Tue, 2 Dec 2014 18:58:10 -0800 To: Steven Hartland Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 02:58:09 -0000 Steven, Thank you for the response. This had no discernible impact. Booting hung at= the same exact point.=20 Christopher Sent from my iPad > On Nov 30, 2014, at 6:30 AM, Steven Hartland wro= te: >=20 > Not sure if is the same board but we've had to use the following to avoid a= stall at a similar point on some machines: >=20 > set hint.atkbdc.0.disabled=3D1 > set hint.atkbd.0.disabled=3D1 > boot >=20 >=20 >> On 30/11/2014 12:52, Christopher R. Bowman wrote: >> I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and the l= atest BIOS off the Intel website. This board runs 7.1 and 8.4 fine. Howeve= r neither 9.1 nor 10.1 will boot the AMD64 memstick kernel beyond the =E2=80= =9CTimecounters tick every 1.000 msec=E2=80=9C section of probing. It wedge= s hard after that line and you have to pus the reset button. I=E2=80=99ve t= ried turning off ACPI in the boot loader. That does not work. I=E2=80=99ve= tried turning on and off most of the options in the BIOS that seem like the= y might impact things and none of those have worked. Does anyone have any s= uggestions? Is anyone running this board under 9.x or 10.x? I can make thi= s system available to anyone in the bay area if you=E2=80=99re looking for a= project. Any help you can offer will be greatly appreciated. If I=E2=80=99= ve sent this to the wrong list, please let me know privately. >> Thank you >> Christopher >>=20 >> -------- >> Christopher R. Bowman >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 03:35:04 2014 Return-Path: Delivered-To: freebsd-hackers@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 532DEA39 for ; Wed, 3 Dec 2014 03:35:04 +0000 (UTC) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 182801BA for ; Wed, 3 Dec 2014 03:35:03 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id AFD883056F for ; Tue, 2 Dec 2014 22:26:05 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0O2NiTI3Omx9 for ; Tue, 2 Dec 2014 22:26:05 -0500 (EST) Received: from EGR authenticated sender Message-ID: <547E82CC.3040007@egr.msu.edu> Date: Tue, 02 Dec 2014 22:26:04 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Bind, DNS, and Denial of Service References: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> <004e01d00ea0$6b7c7860$42756920$@quonix.net> In-Reply-To: <004e01d00ea0$6b7c7860$42756920$@quonix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 03:35:04 -0000 On 12/02/2014 21:25, John Von Essen wrote: > Thanks... Right now I have a FreeBSD 9.3 system, after a clean install I went in and built Bind99 from ports with the RRL option. You may want to consider bind910 which is 9.10 and newer. > > Question is how do I force /etc/rc.d/named to use the new bind9.9 that I built from ports and now resides in /usr/local/sbin? On FreeBSD 10+, /etc/rc.d/named is gone but the bind ports install a named script in /usr/local/etc/rc.d/. I'm doing this and all I need is named_enable="YES" in /etc/rc.conf. > > Do I just edit /etc/defaults/rc.conf and tell it to use /usr/local/sbin/named instead of /usr/sbin/named? Never edit /etc/defaults/*. Always edit the /etc/rc.conf equivalent (copy lines from /etc/defaults) or even /etc/rc.conf.local or files in /etc/rc.conf.d/. See the rc.conf manpage for more info. If you do use /etc/rc.d/named, you can edit these in your own rc.conf: named_program="/usr/sbin/named" # Path to named, if you want a different one. named_conf="/etc/namedb/named.conf" # Path to the configuration file > > I thought there might be a cleaner way to do this, just curious. > > -John > > -----Original Message----- > From: Chris H [mailto:bsd-lists@bsdforge.com] > Sent: Tuesday, December 02, 2014 9:18 PM > To: freebsd-hackers@freebsd.org; John Von Essen > Subject: Re: Bind, DNS, and Denial of Service > > On Tue, 2 Dec 2014 19:00:06 -0500 "John Von Essen" wrote > >> I figure this might be the best place to start this discussion. >> >> >> >> I've been using FreeBSD for ages for some core systems, one of those >> being Auth and public caching DNS. >> >> >> >> Lately I've been getting hit hard by reflective DDoS on DNS, so my old >> systems need some updating. >> >> >> >> Question is, what's the best/simplest solution moving forward? FreeBSD >> 9.3 or 10.1? Do I continue to use BIND with the rate-limiting feature, >> or go with something else? >> >> >> >> I will say, I tried to get a FreeBSD 10.1 instance running with BIND >> 10 - no luck, so I did BIND 9.9 with the RRL feature. It sort of >> worked, but was weird. I was getting a ton of weird responses on the >> server the moment I turned BIND on. >> >> >> >> Its been so long since I've worked on this stuff, my old 8.X machines >> have been running for years. >> >> >> >> I am open to using something else for the caching, but for the Auth I >> really want to stay with Bind. Its just really hard to implement BIND >> with RRL on newer freebsd distro's, I get the feeling that the FreeBSD >> folks want to move on from BIND. >> >> >> >> Any help would be appreciated. > > Hello, John. > > FWIW You might find dns/nsd a good fit. It's even possible to get it to output "Bind like" log messages. I've replaced the Bind on all, but one of our servers with it. In an effort to evaluate it for being a replacement. I'm finding it difficult to keep the last server still running the Bind going. > So I'll probably have to replace it with something soon. Just haven't *yet* determined *what* other DNS to evaluate. I only ran into one issue with it (NSD). It was NSD itself, and the reaction time is extremely good (less than a week), and a new > (fixed) version was out. > > Anyway. Just thought I'd share my experience. In case it helps. > > --Chris > >> >> >> >> -John >> >> >> >> >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 03:56:07 2014 Return-Path: Delivered-To: freebsd-hackers@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 5F200CC for ; Wed, 3 Dec 2014 03:56:07 +0000 (UTC) Received: from a.smtp.quonix.net (a.smtp.quonix.net [208.82.128.205]) (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 238223BB for ; Wed, 3 Dec 2014 03:56:06 +0000 (UTC) Received: from CORSAIR (pool-108-2-133-139.phlapa.fios.verizon.net [108.2.133.139]) by a.smtp.quonix.net (8.14.4/8.14.4) with ESMTP id sB33u2v5018620 for ; Tue, 2 Dec 2014 22:56:02 -0500 (EST) (envelope-from john@quonix.net) From: "John Von Essen" To: References: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> <004e01d00ea0$6b7c7860$42756920$@quonix.net> <547E82CC.3040007@egr.msu.edu> In-Reply-To: <547E82CC.3040007@egr.msu.edu> Subject: RE: Bind, DNS, and Denial of Service Date: Tue, 2 Dec 2014 22:55:34 -0500 Message-ID: <005d01d00ead$00d56320$02802960$@quonix.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AQIiVaX5sQQmCKXYgP76APFhH9lhjgE5aAZTA2S28DsCs1IkM5ueILSg X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 03:56:07 -0000 The base bind99 port did not behave nicely even when I set named_program="/usr/local/sbin/named" because the port is built with a sysconfdir of /usr/local/etc which through everything out of whack. Even when I tried to override the startup scrip to explicitly pass -c /etc/namedb things were all weird. Rndc also didn't work because it kept looking in the wrong dir's, etc.,. So this is what I had to in order to get it to work cleanly on FreeBSD 9.3: 1. I edited the bind99 ports Makefile and set the sysconfdir to /etc/namedb instead of /usr/local/etc and I also set the BIND_ETC_DEST to /etc/namedb 2. I then re-did the make && make install 3. I still have to set named_program="/usr/local/sbin/named" in rc.conf That did it. Everything starts cleanly from /etc/rc.d/named, the RRL options now work, rndc works, etc,. I get the feeling that the bind99 port is setup to behave correctly in FreeBSD 10.X where the init script goes into /usr/local/etc/rc.d and the config goes into /usr/local/etc, but the problem is 9.3 is different, so you sort of have to tweak it like I did. -John -----Original Message----- From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Adam McDougall Sent: Tuesday, December 02, 2014 10:26 PM To: freebsd-hackers@freebsd.org Subject: Re: Bind, DNS, and Denial of Service On 12/02/2014 21:25, John Von Essen wrote: > Thanks... Right now I have a FreeBSD 9.3 system, after a clean install I went in and built Bind99 from ports with the RRL option. You may want to consider bind910 which is 9.10 and newer. > > Question is how do I force /etc/rc.d/named to use the new bind9.9 that I built from ports and now resides in /usr/local/sbin? On FreeBSD 10+, /etc/rc.d/named is gone but the bind ports install a named script in /usr/local/etc/rc.d/. I'm doing this and all I need is named_enable="YES" in /etc/rc.conf. > > Do I just edit /etc/defaults/rc.conf and tell it to use /usr/local/sbin/named instead of /usr/sbin/named? Never edit /etc/defaults/*. Always edit the /etc/rc.conf equivalent (copy lines from /etc/defaults) or even /etc/rc.conf.local or files in /etc/rc.conf.d/. See the rc.conf manpage for more info. If you do use /etc/rc.d/named, you can edit these in your own rc.conf: named_program="/usr/sbin/named" # Path to named, if you want a different one. named_conf="/etc/namedb/named.conf" # Path to the configuration file > > I thought there might be a cleaner way to do this, just curious. > > -John > > -----Original Message----- > From: Chris H [mailto:bsd-lists@bsdforge.com] > Sent: Tuesday, December 02, 2014 9:18 PM > To: freebsd-hackers@freebsd.org; John Von Essen > Subject: Re: Bind, DNS, and Denial of Service > > On Tue, 2 Dec 2014 19:00:06 -0500 "John Von Essen" > wrote > >> I figure this might be the best place to start this discussion. >> >> >> >> I've been using FreeBSD for ages for some core systems, one of those >> being Auth and public caching DNS. >> >> >> >> Lately I've been getting hit hard by reflective DDoS on DNS, so my >> old systems need some updating. >> >> >> >> Question is, what's the best/simplest solution moving forward? >> FreeBSD >> 9.3 or 10.1? Do I continue to use BIND with the rate-limiting >> feature, or go with something else? >> >> >> >> I will say, I tried to get a FreeBSD 10.1 instance running with BIND >> 10 - no luck, so I did BIND 9.9 with the RRL feature. It sort of >> worked, but was weird. I was getting a ton of weird responses on the >> server the moment I turned BIND on. >> >> >> >> Its been so long since I've worked on this stuff, my old 8.X machines >> have been running for years. >> >> >> >> I am open to using something else for the caching, but for the Auth I >> really want to stay with Bind. Its just really hard to implement BIND >> with RRL on newer freebsd distro's, I get the feeling that the >> FreeBSD folks want to move on from BIND. >> >> >> >> Any help would be appreciated. > > Hello, John. > > FWIW You might find dns/nsd a good fit. It's even possible to get it to output "Bind like" log messages. I've replaced the Bind on all, but one of our servers with it. In an effort to evaluate it for being a replacement. I'm finding it difficult to keep the last server still running the Bind going. > So I'll probably have to replace it with something soon. Just haven't > *yet* determined *what* other DNS to evaluate. I only ran into one > issue with it (NSD). It was NSD itself, and the reaction time is > extremely good (less than a week), and a new > (fixed) version was out. > > Anyway. Just thought I'd share my experience. In case it helps. > > --Chris > >> >> >> >> -John >> >> >> >> >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 08:44:53 2014 Return-Path: Delivered-To: hackers@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 CCA749EE for ; Wed, 3 Dec 2014 08:44:53 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.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 9A6101E8 for ; Wed, 3 Dec 2014 08:44:53 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id kq14so15358409pab.34 for ; Wed, 03 Dec 2014 00:44:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:message-id:references:to; bh=gtIb2L5RkubhUgpN6ce8xE9v0sACaWo4O7waq4pLcKU=; b=XRW3s1kZ5ZppNBpIfjdatPi+V6qRR81eQ0/bPZImCEXN3YWd+/Yco++JUvVy1+/KnE JmXMlDht5jqw4I0zwnoPo4HZKZOQF8K/7T0Onom4F1swvZUw4SuiGcnqzYtWYaF8xwLB UDWhs2b7uVyVTpV/VOA6JBN7VMDqFxNfuwDRRJZE0px4/yrksgXn6XqduML7YHW/tOOH 4FwUth+WAIoGr03rcsHK9PpCaWrfnnsUYeGYcsF2vlXhPJ4wx10OqmRqW5I4DcsRvqa/ S4qQXb0j8nmN2AuZi6tLluwaf2JAko2uvYKRKOmGB9e8vtOwVZP93gPSjI4rvKKUPVWW InmQ== X-Gm-Message-State: ALoCoQlmdY5lYd7iQsuOndTjXsHdMEECFcqqMPB/J/9WzlWWyyZRqJ7rs4OqiVM9918QxWw1txyg X-Received: by 10.66.165.70 with SMTP id yw6mr6225764pab.97.1417596292478; Wed, 03 Dec 2014 00:44:52 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id fn7sm22538367pad.38.2014.12.03.00.44.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Dec 2014 00:44:51 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: Date: Wed, 3 Dec 2014 00:44:50 -0800 Message-Id: <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> To: Adrian Chadd X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tony Maher , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 08:44:53 -0000 Adrian, I downloaded and booted an FreeBSD 11 snapshot. Booting from = DVD or memory stick image both resulted in a hang during the probing = process at the exact same spot as I reported before. I=E2=80=99m not = sure where to go from here. I=E2=80=99ve tried fiddling with the bios = options. I=E2=80=99ve tried removing all cards and devices save the = keyboard mouse, ATAPI DVD, ata disk and video card. I=E2=80=99ve tried = booting DVDs and USB sticks of 9.1, 10.1 and 11-snapshot. I=E2=80=99ve = disable the keyboard with loader commands per someone else suggestion. = I=E2=80=99ve tried turning of ACPI. I can=E2=80=99t think of what to = try next. Christopher > On Dec 2, 2014, at 7:32 AM, Adrian Chadd wrote: >=20 > Hi! >=20 > Would you try booting a freebsd-head snapshot, just to compare? >=20 >=20 > -a >=20 >=20 > On 2 December 2014 at 00:38, Tony Maher = wrote: >> Hello Christopher, >>=20 >> On 12/02/14 16:39, Christopher R. Bowman wrote: >>>=20 >>> Tony, Thank you so much for your response. We do indeed appear to >>> have the same board and BIOS revision. How odd that yours boots the >>> 9.x series and mine will not despite running fine in 8.4. It is at >>> least helpful to know that it can boot later kernels even if I = don=E2=80=99t >>> know how to get it to do it yet. IF you have any suggestions I = would >>> be grateful, again thank you for your response. Christopher >>=20 >>=20 >> Perhaps it is just the booting from memstick that is the issue? >> I would try a USB memory stick but do not have one here but if can = get >> one I will give it a try. >> Does booting from an installation CD work? >>=20 >> cheers >> -- >> Tony Maher email: tonymaher@optusnet.com.au >>=20 >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 11:58:25 2014 Return-Path: Delivered-To: freebsd-hackers@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 619A6234 for ; Wed, 3 Dec 2014 11:58:25 +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 21514A9E for ; Wed, 3 Dec 2014 11:58:25 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id x19so8504026ier.20 for ; Wed, 03 Dec 2014 03:58:24 -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=wgsSys0Wgf6uDE2aFHiTnRET34un0uqQnezfN5BhYpQ=; b=wSD/Uc1cxhNidnM0/fZmFIq3DMiwh91SVslX/bgPHa0S9RNpgrZooOj1oBNSBq2yz/ UKnCpC6vVEV24V2a/u0Ki7EsqdAZ/3PrZt3VpuhYP8l07x1uypjUgfcSMD1MDTsuMzZt EbmqzR8RuxCjIVFBxgeV3EpSJwA5hakPc+YmHnKkyvmleS3EMtrzHcKISfBn8HwlC2r6 JBTxiVdglJLNmjbvUecIZBVhV8o6obFsWDgodCrLjVS5NV8ox4kUx1+tvdUDPIs2Ynv8 LBOdfxbkDcCVaZwUzX5K8uiIxS3ZvKeiNYr8EmaCV6RlNyFfxMyPISQOadWcT1K5681e C59w== X-Received: by 10.50.3.8 with SMTP id 8mr57143938igy.45.1417607904517; Wed, 03 Dec 2014 03:58:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.214 with HTTP; Wed, 3 Dec 2014 03:57:54 -0800 (PST) In-Reply-To: <547E271A.6070005@selasky.org> References: <547E271A.6070005@selasky.org> From: arrowdodger <6yearold@gmail.com> Date: Wed, 3 Dec 2014 15:57:54 +0400 Message-ID: Subject: Re: Mapping SCSI driver to USB one. To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 11:58:25 -0000 On Tue, Dec 2, 2014 at 11:54 PM, Hans Petter Selasky wrote: > On 12/02/14 21:39, arrowdodger wrote: > >> Hello. >> I'm playing around with sysutils/hal sources and can't find a way to >> obtain >> a SCSI driver to the corresponding USB device. In other words, knowing >> "umass0" i want to get "da0" for it. >> >>> From what i can tell, HAL uses CAM API's (/dev/xpt0 stuff), but working >>> >> with it requires elevated privileges. Probably, because of that >> hald-runner >> is running under root. >> Is there any way to perform such mapping as regular user? >> > > Hi, > > Maybe "devinfo" will give you the answer. > > --HPS > > Nope, unfortunately devinfo gives ehci0 usbus1 uhub1 umass0 for my flash drive. From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 12:51:22 2014 Return-Path: Delivered-To: freebsd-hackers@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 E7226162; Wed, 3 Dec 2014 12:51:22 +0000 (UTC) Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8DE9116; Wed, 3 Dec 2014 12:51:22 +0000 (UTC) Received: from fwd26.aul.t-online.de (fwd26.aul.t-online.de [172.20.26.131]) by mailout03.t-online.de (Postfix) with SMTP id 3502E8CF33; Wed, 3 Dec 2014 13:51:14 +0100 (CET) Received: from [192.168.119.11] (JOMvUmZVrh4b9zlthkYwFYPROTLKO3ndXkFr8lRrq1Klb6ItYCGcs8bm4lwqGQcZ-l@[84.154.125.71]) by fwd26.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1Xw9Oh-1XM7VY0; Wed, 3 Dec 2014 13:51:11 +0100 Message-ID: <547F073A.2090502@freebsd.org> Date: Wed, 03 Dec 2014 13:51:06 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Subject: [Review] pciconf converted to use libxo [D1206] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-ID: JOMvUmZVrh4b9zlthkYwFYPROTLKO3ndXkFr8lRrq1Klb6ItYCGcs8bm4lwqGQcZ-l X-TOI-MSGID: 1ee32d57-af6a-4c71-8294-ac956104ae95 Cc: phil Shafer , "Simon J. Gerraty" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 12:51:23 -0000 Hi all, the following review URL shows my proposed changes to make pciconf optionally output XML or JSON formatted data via libxo: https://reviews.freebsd.org/D1206 I wanted to see how much effort the conversion of a utility that was not written with libxo in mind makes - and I'm pleased by the possibility to mostly mechanically replace printf/err/warn calls with their libxo counterparts. The documentation of libxo seems incomplete (e.g. no mention of xo_error() that I could find), and some functions do not seem to produce the expected result (xo_err() prints the message as given in the format string, but does not automatically append strerror() as err() does ...). A FreeBSD man-page that lists all functions and that can be used as a reference when libxo principles are already known would be really great. ;-) Since the behaviour of pciconf has not changed unless invoked with "--libxo", I could check in this version without worrying about a violation of POLA. But I thought I might learn how to use Phabricator and offer an opportunity to comment on proposed XML/JSON tags or my general use of libxo features ... Please let me know whether these is something wrong in the XML or JSON output (bad tags names, bad use of xo_ functions to generate the output, ...). The HTML-Output looks ugly if directly viewed in a web browser, but that's not different than what other utilities converted to use libxo produce ... Regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 13:01:52 2014 Return-Path: Delivered-To: freebsd-hackers@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 C20883E6 for ; Wed, 3 Dec 2014 13:01:52 +0000 (UTC) Received: from nm29-vm8.bullet.mail.ir2.yahoo.com (nm29-vm8.bullet.mail.ir2.yahoo.com [212.82.97.77]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 19F4B1B3 for ; Wed, 3 Dec 2014 13:01:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1417611709; bh=VOkFhdoJ14pE25fBaXMZ9GifrXYzxru58pGqDC1TAno=; h=Date:From:To:Subject:In-Reply-To:References:From:Subject; b=Id4h8PSBs9GRAequbhY14LNPQUhvA2aUizsmmvle3zBt67RVNXt9jswmYWATrRMm6JUSRapFbDhbyMWS/FsupfsX4V98LFNkhIcNkrneMwgZE4N8z8P0jUYmpyW0Hwp+nRRsTmNFtwB4QevtE94GAkVsUAXUQDwU09+hv3xAwJUtnDr700ZTfF8A+cJFXJDULGNm+mgCAzUPyef3z5j4PNq93f+O5v3xTwx54h18PAK7JRU24BlAJ93eij4yDDHcN3GL8WhLcRoi5m4BCulwOBth98npf6sufDPiYbQWndx1lwSMcCyS7f1S89jGY12PLqh2tzsX8k0dH5qgxadBLg== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.es; b=ks0aixYYXehj5dAk3nt7DyxNeDBUgr14amoZf0FqOTUq0+KQNr89irQMznCAyq2rJKrNER2y953Iimt98Tm+d2zwoVyLa1A3fxXmfoUscstWghoONYo3pvin0CZrRa1finOysHNkoF9A+LT62nwL3vUwC+JZiMfvz5rKcVH7RTeay376gOa3p8EHLpR/ghZG1N0CZI9piH36bt71f/umoOYieWZzqZsOoe31w8rJ/hVlNDdVdvsSfuAtM9+rYb528+ZgP+ALVVOcmOrgXnB3IlMKjapcd708FkyFYocS2saBGztfsfEDR5r9AZraesLJRKCn/2mS1uFTj4kHiISUtQ==; Received: from [212.82.98.60] by nm29.bullet.mail.ir2.yahoo.com with NNFMP; 03 Dec 2014 13:01:49 -0000 Received: from [46.228.39.67] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 03 Dec 2014 13:01:49 -0000 Received: from [127.0.0.1] by smtp104.mail.ir2.yahoo.com with NNFMP; 03 Dec 2014 13:01:49 -0000 X-Yahoo-Newman-Id: 779314.29083.bm@smtp104.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0UWXWIQVM1ncSR9eZnxVt7CcNP7z5sK2uAjCKy3ZSG1ttIw Nugc6CxB.jllifGrH4KJZn.9YpVhnmERIea8UwtWpbGuAsDLMYTR7VrzcTfS MPcnLcXSxhoZvVCohfe1ZuzB4AAYxNwgYVTu7iXXxVopXxfjGhM8wz4ZK9n5 eBEd3qhM7GeFP4vCb_kown7ggDQOSCkAWFxXJkJ0wrhIIYzFJ.H2CiZZxPlm O82LLwGmvoAhhED1MNpXfzn4SwrnnJmlmCQ6ckcKe7OzjY61HY7QBxONSMVY YddVoEvV8G61kyJFMwaCdJtnFw2OrVxSwrfbEQa1mpzepnmXG5EH00R4zS8h qouuEp3Id.lzysQwTpMXSE1UFw4tHB23IO_UXe_CwA_SN9_U7EsmI_iV7cCN RVQZWhG.Gv66imeDKVabO2CrI4INzGAzQ_tTW60HnPIpXHiT8R.tDBJmsp1D HdAtlU1joEKf1JevculNnFRiuDvTChsnO_BHcFjdyysQdZgqbWtxgqmz4D70 - X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Wed, 3 Dec 2014 14:01:52 +0100 From: Eduardo Morras To: freebsd-hackers@freebsd.org Subject: Re: 10.1 hangs during boot on Intel DP35DP board Message-Id: <20141203140152.17f90a63edca81bed54310dd@yahoo.es> In-Reply-To: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> References: <05096144-E292-4D04-B53A-BD0C5127EC7D@ChrisBowman.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 13:01:52 -0000 On Sun, 30 Nov 2014 22:42:24 -0800 "Christopher R. Bowman" wrote: > I have a pretty stock Intel DP35DP board with and E8400 Core2Duo and > the latest BIOS off the Intel website. This board runs 7.1 and 8.4 > fine. However neither 9.1 nor 10.1 will boot the AMD64 memstick > kernel beyond the “Timecounters tick every 1.000 msec“ section of > probing. It wedges hard after that line and you have to pus the > reset button. I’ve tried turning off ACPI in the boot loader. That > does not work. I’ve tried turning on and off most of the options in > the BIOS that seem like they might impact things and none of those > have worked. Does anyone have any suggestions? Is anyone running > this board under 9.x or 10.x? I can make this system available to > anyone in the bay area if you’re looking for a project. Any help you > can offer will be greatly appreciated. If I’ve sent this to the > wrong list, please let me know privately. Thank you Christopher What's the output of #sysctl kern.timecounter In particular, the kern.timecounter.choice > > -------- > Christopher R. Bowman --- --- Eduardo Morras From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 14:36:04 2014 Return-Path: Delivered-To: hackers@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 0E7CEE4B for ; Wed, 3 Dec 2014 14:36:04 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::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 A40F27F for ; Wed, 3 Dec 2014 14:36:03 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id r20so33239400wiv.2 for ; Wed, 03 Dec 2014 06:36:02 -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=MJO7v753A+Ju4MQ865QhuCDPqm4/QY7i6Yyr/JWKnig=; b=wMU3Sqv6GT7gNo+ljiJ1LXVS7OuRd4yhtg1/zfCSKGTb1zRAuyiPFzJ+Mwendg1f4S 47BPhZeN1hEkJDwFmElIlxKXsZvBgCYKYEEgcY6h802M7Gr9rjPtbnRYMnywDNDonNl7 nSpi9ZJgNDOacF/SpKdLLUazrSSagFIIUuGmt219dD666GbNJfBhzIpeD5rJliG4QdrS Iao7BjJBL0O8noVi/MB8RhAEw1+nzGoiyOqGoQKzVUjRd3usMJHj6XHyy51rQ58rFTun S0EcrU89oNF6as/0BqGYyMPvzaGzTfp26m6h+hoinNStNg9uxBoUG9h2bAmDxXLPd62Q ghyA== MIME-Version: 1.0 X-Received: by 10.194.85.83 with SMTP id f19mr8289175wjz.20.1417617361996; Wed, 03 Dec 2014 06:36:01 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Wed, 3 Dec 2014 06:36:01 -0800 (PST) In-Reply-To: <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> Date: Wed, 3 Dec 2014 06:36:01 -0800 X-Google-Sender-Auth: 11mRh3kT3PyL6fHEEdELjW0pnQY Message-ID: Subject: Re: 10.1 hangs during boot on Intel DP35DP board From: Adrian Chadd To: "Christopher R. Bowman" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Tony Maher , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 14:36:04 -0000 Hi, I'm not sure - it may be that the timekeeping stuff is a bit confused. Maybe it's now time to file a bug and see if we can loop the timekeeping folk into it. -a On 3 December 2014 at 00:44, Christopher R. Bowman wr= ote: > Adrian, > I downloaded and booted an FreeBSD 11 snapshot. Booting from DVD or memo= ry > stick image both resulted in a hang during the probing process at the exa= ct > same spot as I reported before. I=E2=80=99m not sure where to go from he= re. I=E2=80=99ve > tried fiddling with the bios options. I=E2=80=99ve tried removing all ca= rds and > devices save the keyboard mouse, ATAPI DVD, ata disk and video card. I= =E2=80=99ve > tried booting DVDs and USB sticks of 9.1, 10.1 and 11-snapshot. I=E2=80= =99ve > disable the keyboard with loader commands per someone else suggestion. I= =E2=80=99ve > tried turning of ACPI. I can=E2=80=99t think of what to try next. > Christopher > > On Dec 2, 2014, at 7:32 AM, Adrian Chadd wrote: > > Hi! > > Would you try booting a freebsd-head snapshot, just to compare? > > > -a > > > On 2 December 2014 at 00:38, Tony Maher wrote= : > > Hello Christopher, > > On 12/02/14 16:39, Christopher R. Bowman wrote: > > > Tony, Thank you so much for your response. We do indeed appear to > have the same board and BIOS revision. How odd that yours boots the > 9.x series and mine will not despite running fine in 8.4. It is at > least helpful to know that it can boot later kernels even if I don=E2=80= =99t > know how to get it to do it yet. IF you have any suggestions I would > be grateful, again thank you for your response. Christopher > > > > Perhaps it is just the booting from memstick that is the issue? > I would try a USB memory stick but do not have one here but if can get > one I will give it a try. > Does booting from an installation CD work? > > cheers > -- > Tony Maher email: tonymaher@optusnet.com.au > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > > From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 14:47:18 2014 Return-Path: Delivered-To: freebsd-hackers@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 8088529D for ; Wed, 3 Dec 2014 14:47:18 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DBA81B7 for ; Wed, 3 Dec 2014 14:47:17 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id sB3ElGJu093529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Dec 2014 07:47:16 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sB3ElGZh093523; Wed, 3 Dec 2014 07:47:16 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 3 Dec 2014 07:47:16 -0700 (MST) From: Warren Block To: John Von Essen Subject: RE: Bind, DNS, and Denial of Service In-Reply-To: <005d01d00ead$00d56320$02802960$@quonix.net> Message-ID: References: <002e01d00e8c$1b7d6f40$52784dc0$@quonix.net> <381c25e1046453b9f7a5c94809e7d7fb@ultimatedns.net> <004e01d00ea0$6b7c7860$42756920$@quonix.net> <547E82CC.3040007@egr.msu.edu> <005d01d00ead$00d56320$02802960$@quonix.net> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 03 Dec 2014 07:47:16 -0700 (MST) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 14:47:18 -0000 On Tue, 2 Dec 2014, John Von Essen wrote: > The base bind99 port did not behave nicely even when I set > named_program="/usr/local/sbin/named" because the port is built with a > sysconfdir of /usr/local/etc which through everything out of whack. Even > when I tried to override the startup scrip to explicitly pass -c /etc/namedb > things were all weird. Rndc also didn't work because it kept looking in the > wrong dir's, etc.,. The port used to have an option to overwrite the base BIND. There is an example of installing dns/bind99 in a 10.X jail in the Handbook: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html#jails-ezjail-example-bind From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 4 04:10:33 2014 Return-Path: Delivered-To: hackers@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 8C1309C7 for ; Thu, 4 Dec 2014 04:10:33 +0000 (UTC) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (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 580CD6B for ; Thu, 4 Dec 2014 04:10:33 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id lj1so17186163pab.33 for ; Wed, 03 Dec 2014 20:10:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:message-id:references:to; bh=YVgI+JaE23RMP5i6XbwyWo7byrBgnGDnKQXBQ2Cba3w=; b=lLXaDap7nYlA2KHisIO5c4HKCesmad65fBxbCxezDtynERAdCRYfz5ey4bOIaVym48 OMI9o5R/dOahOXtNDfQ0uzTPp8L0oRAC3iz7KoQJ4c0ii4P+GY8halThxx/xyjOGWDxx pY386Tc89fuJLhm6mQNIf8NFxjTpGXHLgbGW1VsadxcFGPbWokz1++omYFYsPnY36tX9 qTjVT030V4c02wNRVUtvZKrR8Jv/pGYn6FBygx7FUaagi7AnPoX87Fg03lRBI3ZxbTeX ZbcqTgcS4iucgRKD/XZKG1LTmS+ZlG08hAlNGacAS/H64xTtjlFpt4F0q/bMYY4zetuw ENkg== X-Gm-Message-State: ALoCoQnr3wCMUkPYsA66k9IYN3mpqrkPjcL1s3DkI4vwM7S86PT4SPP01WTq0UUcBM1yYZ8zUntG X-Received: by 10.70.109.174 with SMTP id ht14mr15239231pdb.74.1417666227072; Wed, 03 Dec 2014 20:10:27 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id dk5sm24428979pbc.9.2014.12.03.20.10.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Dec 2014 20:10:26 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: Date: Wed, 3 Dec 2014 20:10:24 -0800 Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <547D7A8B.3090803@optusnet.com.au> <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> To: Adrian Chadd X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tony Maher , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 04:10:33 -0000 > On Dec 3, 2014, at 6:36 AM, Adrian Chadd wrote: >=20 > Hi, >=20 > I'm not sure - it may be that the timekeeping stuff is a bit confused. > Maybe it's now time to file a bug and see if we can loop the > timekeeping folk into it. >=20 >=20 > -a >=20 >=20 > On 3 December 2014 at 00:44, Christopher R. Bowman = wrote: >> Adrian, >> I downloaded and booted an FreeBSD 11 snapshot. Booting from DVD or = memory >> stick image both resulted in a hang during the probing process at the = exact >> same spot as I reported before. I=E2=80=99m not sure where to go = from here. I=E2=80=99ve >> tried fiddling with the bios options. I=E2=80=99ve tried removing = all cards and >> devices save the keyboard mouse, ATAPI DVD, ata disk and video card. = I=E2=80=99ve >> tried booting DVDs and USB sticks of 9.1, 10.1 and 11-snapshot. = I=E2=80=99ve >> disable the keyboard with loader commands per someone else = suggestion. I=E2=80=99ve >> tried turning of ACPI. I can=E2=80=99t think of what to try next. >> Christopher >>=20 >> On Dec 2, 2014, at 7:32 AM, Adrian Chadd wrote: >>=20 >> Hi! >>=20 >> Would you try booting a freebsd-head snapshot, just to compare? >>=20 >>=20 >> -a >>=20 >>=20 >> On 2 December 2014 at 00:38, Tony Maher = wrote: >>=20 >> Hello Christopher, >>=20 >> On 12/02/14 16:39, Christopher R. Bowman wrote: >>=20 >>=20 >> Tony, Thank you so much for your response. We do indeed appear to >> have the same board and BIOS revision. How odd that yours boots the >> 9.x series and mine will not despite running fine in 8.4. It is at >> least helpful to know that it can boot later kernels even if I = don=E2=80=99t >> know how to get it to do it yet. IF you have any suggestions I would >> be grateful, again thank you for your response. Christopher >>=20 >>=20 >>=20 >> Perhaps it is just the booting from memstick that is the issue? >> I would try a USB memory stick but do not have one here but if can = get >> one I will give it a try. >> Does booting from an installation CD work? >>=20 >> cheers >> -- >> Tony Maher email: tonymaher@optusnet.com.au >>=20 >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>=20 >>=20 Adrian, Thank you for your help. I have filed a bug report Bug=C2=A019566= 9 (I think = I accidentally created a duplicate: Bug=C2=A0195670 = which I = imagine someone will close). Please let me know if you have any other = thoughts or suggestions. Christopher=20 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 4 12:26:26 2014 Return-Path: Delivered-To: freebsd-hackers@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 51FBC4F2 for ; Thu, 4 Dec 2014 12:26:26 +0000 (UTC) Received: from kerio.tuxis.nl (alcyone.saas.tuxis.net [31.3.111.19]) (using TLSv1.1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF3A7B60 for ; Thu, 4 Dec 2014 12:26:24 +0000 (UTC) X-Footer: dHV4aXMubmw= Received: from [31.3.104.222] ([31.3.104.222]) by kerio.tuxis.nl (Kerio Connect 8.4.0) for freebsd-hackers@freebsd.org; Thu, 4 Dec 2014 13:26:15 +0100 From: "Mark Schouten" Subject: Re: Slow nfsd write performance, tweaks needed To: freebsd-hackers@freebsd.org Organization: Tuxis Internet Engineering In-Reply-To: <2826701214-10966@kerio.tuxis.nl> Message-ID: <20141204122615.b85ad6cf@kerio.tuxis.nl> Date: Thu, 04 Dec 2014 13:26:15 +0100 X-Mailer: Kerio Connect 8.4.0 WebMail X-User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 12:26:26 -0000 Hi, > The box is stable, but performs terribly. Surely, I'm doing something = wrong, > but I would like some tips and tricks to speed things up. I thought it would be nice to update you on this issue. I performed an upgrade to 10.1 on the productionbox, which helped in my = test-setup. But it didn't in my productionsetup. However, it did show an= other issue: da4p1 ONLINE 0 0 0 block size: 512B configured, 4096B= native Which I now fixed with a new pool and ashift=3D12. That fixed a lot. I c= an now write to the box, filling the gigabit with NFS traffic and not sh= owing an enormous delay in replies. I'm also quite sure that the testbox= had ashift=3D12... All other changes did not influence performance much. Now, there's only one issue left: Enabling cache-devices activates a mem= oryleak (I think)... --=C2=A0 Kerio Operator in de Cloud=3F https://www.kerioindecloud.nl/ Mark Schouten | Tuxis Internet Engineering KvK:=C2=A061527076=C2=A0| http://www.tuxis.nl/ T: 0318 200208 | info@tuxis.nl From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 4 16:54:35 2014 Return-Path: Delivered-To: freebsd-hackers@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 AB0445DE; Thu, 4 Dec 2014 16:54:35 +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 81D791F5; Thu, 4 Dec 2014 16:54:35 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 25880B926; Thu, 4 Dec 2014 11:54:34 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Thu, 4 Dec 2014 11:39:31 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201412041139.31416.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 04 Dec 2014 11:54:34 -0500 (EST) Cc: "Christopher R. Bowman" , Tony Maher , Adrian Chadd , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 16:54:35 -0000 On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: > Hi, > > I'm not sure - it may be that the timekeeping stuff is a bit confused. > Maybe it's now time to file a bug and see if we can loop the > timekeeping folk into it. This is probably not timekeeping. That message is just the last thing printed before the interrupt-driven hooks are run. If you booted a HEAD snapshot the kernel should have DDB compiled in. Please drop into DDB using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with the output please. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 03:42:56 2014 Return-Path: Delivered-To: freebsd-hackers@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 A202A123 for ; Fri, 5 Dec 2014 03:42:56 +0000 (UTC) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (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 7157B7D2 for ; Fri, 5 Dec 2014 03:42:56 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id v10so13703576pde.12 for ; Thu, 04 Dec 2014 19:42:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DZT7oj5YWz3ScV/02t2hGISf/TXt/+NdbWFLF491pmk=; b=jx3+Dfxy2AJK7zzQKwe3pZ8PQavqERuwuf22/20p9p6VyUM9Ps0vZxuXSmOamUoDM8 8A0XleCS+BHXNAaFpAiMtIwQ1Os9x+9wVJ8NtJyxqTcxLi4sarcMhp0gdJMUELXpGW3e OBYBT49dLTAJIMJW0UpfL1HSdogbpUuI8b8Cat9ZYngmqywG09/SMFJsNCQFIt03mqA9 miV7AeOuwrobvp1Snpf4sJBCMHyYW/WAU1/27Oso9iHqfEBvG5uLAMm0UO3EMqrwGTMB IJoYjVBKWr3WzpOm6OhqAU8z7c9+oXi1futUl0eFLPVloXuuUE+mZykgWkSW4fo9+3ZA mZnw== X-Gm-Message-State: ALoCoQmJueKjZ7b4PBuvU5Jt0D201kmpfjLVMClzInsjy8jUxtyOa/nIAexMeZNU6iZQFjuTcQ3S X-Received: by 10.66.65.202 with SMTP id z10mr20774845pas.104.1417750970210; Thu, 04 Dec 2014 19:42:50 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id gh6sm6545113pbd.28.2014.12.04.19.42.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Dec 2014 19:42:49 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <201412041139.31416.jhb@freebsd.org> Date: Thu, 4 Dec 2014 19:42:48 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <366F5C20-E685-4C8F-82CB-237E5E102C78@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <158FFB73-7AE2-4AAF-B483-9228E0C2C491@ChrisBowman.com> <201412041139.31416.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1993) Cc: freebsd-hackers@freebsd.org, Adrian Chadd , "freebsd-hackers@freebsd.org" , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 03:42:56 -0000 > On Dec 4, 2014, at 8:39 AM, John Baldwin wrote: >=20 > On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: >> Hi, >>=20 >> I'm not sure - it may be that the timekeeping stuff is a bit = confused. >> Maybe it's now time to file a bug and see if we can loop the >> timekeeping folk into it. >=20 > This is probably not timekeeping. That message is just the last thing = printed=20 > before the interrupt-driven hooks are run. If you booted a HEAD = snapshot the=20 > kernel should have DDB compiled in. Please drop into DDB using = Ctrl-Alt-Esc=20 > and then run 'show conifhk' and reply here with the output please. >=20 > --=20 > John Baldwin John, Thank you for responding. I tried that but the machine seemed = wedged at that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc = nor can I do Ctrl-Alt-Del to reboot. All I can do it push the reset = button. Christopher From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 11:46:40 2014 Return-Path: Delivered-To: hackers@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 D80CBC14 for ; Fri, 5 Dec 2014 11:46:40 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::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 694BDE55 for ; Fri, 5 Dec 2014 11:46:40 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id bs8so1133546wib.5 for ; Fri, 05 Dec 2014 03:46:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=P79dBKdNAB84mfP7Me2A9F5IdnsCHBRTee7fK8hRf5Q=; b=fFIOYjmXP7fbg6iHq3tdHHUnD6RjZDhU71wfZTV/uK3qi0B8zi6t5IVTkQSxtbRQHp oKITq7ZQyKur4dRoK9Eqof8l2V7VStesRmfIlu6/xcyPjXft7Wv4zyRscRJRqHKopE9L m9Tjy5rVRZITG5K3CN3Jr5wPwf/Buzga4YNAG5BUrZohDu+hohLzoiY8jDTB5OO+lHQY 3llikXa4SJe4hjEJ1oCT2FE/1Qe8jRXvI3zAiDLQZcsJkS3mdtxH99kCqmFT1JHds9wK kj0l2AzaKhusN6vks2BKNk56sOXlcGJ5/JTvNLgtpW+DRF1mndJv1uKoMWp6xzWBeeh/ 7Dww== X-Received: by 10.180.12.75 with SMTP id w11mr3621176wib.9.1417779998718; Fri, 05 Dec 2014 03:46:38 -0800 (PST) Received: from brick.home (adbi100.neoplus.adsl.tpnet.pl. [79.184.8.100]) by mx.google.com with ESMTPSA id n3sm1965785wiw.5.2014.12.05.03.46.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Dec 2014 03:46:37 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 5 Dec 2014 12:46:35 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: hackers@FreeBSD.org Subject: fstyp(8) Message-ID: <20141205114635.GA12557@brick.home> 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-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 11:46:40 -0000 I'm slowly working on making autofs suitable for mounting removable media, and one of the things required is filesystem detection. It's kind of possible to use file(1), but it's, well, "suboptimal" for this task. So, I went and wrote fstyp(8). This utility, named after SVR4 command with same weird name, detects filesystems. It's mostly based on glabel code. The output is machine parseable, it can print out filesystem labels, and runs capsicated. You can join the review at https://reviews.freebsd.org/D1255. From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 11:56:13 2014 Return-Path: Delivered-To: hackers@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 4CA21F61 for ; Fri, 5 Dec 2014 11:56:13 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0090.outbound.protection.outlook.com [65.55.169.90]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (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 D8FEDF57 for ; Fri, 5 Dec 2014 11:56:12 +0000 (UTC) Received: from DM2PR04MB480.namprd04.prod.outlook.com (10.141.105.25) by DM2PR04MB541.namprd04.prod.outlook.com (10.141.100.12) with Microsoft SMTP Server (TLS) id 15.1.31.17; Fri, 5 Dec 2014 11:56:03 +0000 Received: from DM2PR04MB477.namprd04.prod.outlook.com (10.141.105.13) by DM2PR04MB480.namprd04.prod.outlook.com (10.141.105.25) with Microsoft SMTP Server (TLS) id 15.1.26.15; Fri, 5 Dec 2014 11:55:55 +0000 Received: from DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) by DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) with mapi id 15.01.0026.003; Fri, 5 Dec 2014 11:55:55 +0000 From: Mike Gelfand To: "hackers@freebsd.org" Subject: Re: [BUG] Getting path to program binary sometimes fails Thread-Topic: [BUG] Getting path to program binary sometimes fails Thread-Index: AQHP/y1OF6HbydE23kCBwyNP5wFRKZxeymWAgAEZIgCAAAgTAIAhGtwA Date: Fri, 5 Dec 2014 11:55:54 +0000 Message-ID: <2A50A149-E1E8-4EBD-A6A1-013687CF0648@logicnow.com> References: <91809230-5E81-4A6E-BFD6-BE8815A06BB2@logicnow.com> <20141113170758.GY17068@kib.kiev.ua> <20141114102306.GE17068@kib.kiev.ua> In-Reply-To: <20141114102306.GE17068@kib.kiev.ua> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [128.140.241.14] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB480;UriScan:; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB480; x-forefront-prvs: 04163EF38A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(377454003)(189002)(24454002)(46102003)(21056001)(92566001)(40100003)(122556002)(99396003)(2501002)(97736003)(83716003)(93886004)(120916001)(87936001)(4396001)(19580395003)(19580405001)(2656002)(64706001)(20776003)(86362001)(66066001)(33656002)(101416001)(76176999)(54356999)(68736005)(50986999)(110136001)(62966003)(106356001)(99286002)(77156002)(105586002)(106116001)(36756003)(82746002)(31966008)(2351001)(107046002)(102836002)(85282002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR04MB480; H:DM2PR04MB477.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB541; X-OriginatorOrg: logicnow.com X-Mailman-Approved-At: Fri, 05 Dec 2014 12:51:50 +0000 Cc: Konstantin Belousov X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 11:56:13 -0000 Hello, Sorry for late reply. On Nov 14, 2014, at 1:23 PM, Konstantin Belousov wrot= e: >> error condition, what should I do to get the path reliably? Should I >> retry (and how many times)? You?re saying cache is being purged; does >> it mean that when I ask for path then cache is populated again? Does >> it guarantee then that I?ll be able to get the path on next call? >> Could you guarantee that I?ll be able to get the path at all if I fail >> two or more times? Should I rely on ENOENT specifically when retrying? > After the path resolution failed, it can only succeed later if the cache > is populated again. Cache cannot be populated by the vnode->path > request, just think where to get the data ? The cache is populated > when lookup is performed, so if nothing accessed the file by name > between your two calls, second translation fails as well. Still no answer to the very first question: how do I get path to current or= any other process binary reliably? The fact that this sysctl is not guaran= teed to work and there's no way to make it work if all I know is process ID= makes it quite useless for programs which need this information. Are you s= aying that this information cannot at all be reliably retrieved in FreeBSD?= Is there a way to at least prolong cache entry lifetime or increase cache = size so that eviction happens as rarely as possible (if at all)? Regards, Mike= From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 12:01:27 2014 Return-Path: Delivered-To: hackers@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 8E6633C8; Fri, 5 Dec 2014 12:01:27 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0098.outbound.protection.outlook.com [157.56.110.98]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (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 E30DE99; Fri, 5 Dec 2014 12:01:26 +0000 (UTC) Received: from DM2PR04MB477.namprd04.prod.outlook.com (10.141.105.13) by DM2PR04MB478.namprd04.prod.outlook.com (10.141.105.16) with Microsoft SMTP Server (TLS) id 15.1.26.15; Fri, 5 Dec 2014 12:01:16 +0000 Received: from DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) by DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) with mapi id 15.01.0026.003; Fri, 5 Dec 2014 12:01:15 +0000 From: Mike Gelfand To: "freebsd-hackers@freebsd.org" Subject: Re: [BUG] Getting path to program binary sometimes fails Thread-Topic: [BUG] Getting path to program binary sometimes fails Thread-Index: AQHP/y1OF6HbydE23kCBwyNP5wFRKZxeymWAgAEZIgCACdtQgIAXSR6A Date: Fri, 5 Dec 2014 12:01:15 +0000 Message-ID: References: <91809230-5E81-4A6E-BFD6-BE8815A06BB2@logicnow.com> <20141113170758.GY17068@kib.kiev.ua> <201411201125.30087.jhb@freebsd.org> In-Reply-To: <201411201125.30087.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [128.140.241.14] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB478; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB478; x-forefront-prvs: 04163EF38A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(51704005)(24454002)(377454003)(199003)(2351001)(105586002)(107046002)(77156002)(99286002)(83716003)(106116001)(20776003)(102836002)(62966003)(106356001)(68736005)(64706001)(66066001)(93886004)(36756003)(46102003)(99396003)(2656002)(101416001)(120916001)(21056001)(4396001)(50986999)(76176999)(54356999)(40100003)(122556002)(19580395003)(92566001)(31966008)(86362001)(97736003)(19580405001)(87936001)(82746002)(33656002)(110136001)(104396002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR04MB478; H:DM2PR04MB477.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="Windows-1252" Content-ID: <7791A140A95D7C42921E4887978CDBEA@namprd04.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: logicnow.com X-Mailman-Approved-At: Fri, 05 Dec 2014 12:52:03 +0000 Cc: Konstantin Belousov , "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 12:01:27 -0000 John, Sorry for late reply. On Nov 20, 2014, at 7:25 PM, John Baldwin wrote: >=20 >> Since you=92re saying that current behavior is not a defect, maybe=20 >> documentation is wrong (incomplete, misleading) then? I will readily acc= ept=20 >> the =93not a defect=94 explanation, but only if one wouldn=92t have to a= sk you every=20 >> time this oddity is met. If this is the expected error condition, what s= hould=20 >> I do to get the path reliably? Should I retry (and how many times)? You= =92re=20 >> saying cache is being purged; does it mean that when I ask for path then= cache=20 >> is populated again? Does it guarantee then that I=92ll be able to get th= e path=20 >> on next call? Could you guarantee that I=92ll be able to get the path at= all if=20 >> I fail two or more times? Should I rely on ENOENT specifically when retr= ying? >=20 > Is this over NFS? NFS is more aggressive than local filesystems in purgi= ng > name cache entries because there are inherent races in NFS with certain=20 > fileservers (ones that don't use sub-second timestamps), so by default en= tries=20 > always expire after about a minute. You can change that via the 'nametim= eo'=20 > mount option (takes a count in seconds). No, not NFS but ZFS. Could that be an issue? The FreeBSD 8 machine I mentio= ned before has UFS. Also, as you can see from the video I recorded (and from the code I provide= d), path resolution succeeds and fails within fractions of a second after p= rocess startup. Regards, Mike= From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 15:33:03 2014 Return-Path: Delivered-To: freebsd-hackers@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 E1A0F228; Fri, 5 Dec 2014 15:33:03 +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 B8352BFB; Fri, 5 Dec 2014 15:33:03 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1875FB987; Fri, 5 Dec 2014 10:33:02 -0500 (EST) From: John Baldwin To: "Christopher R. Bowman" Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Fri, 05 Dec 2014 10:20:48 -0500 Message-ID: <4750778.kghJ8KRE21@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <366F5C20-E685-4C8F-82CB-237E5E102C78@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <201412041139.31416.jhb@freebsd.org> <366F5C20-E685-4C8F-82CB-237E5E102C78@ChrisBowman.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 05 Dec 2014 10:33:02 -0500 (EST) Cc: freebsd-hackers@freebsd.org, Adrian Chadd , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 15:33:04 -0000 On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman wrote:= > > On Dec 4, 2014, at 8:39 AM, John Baldwin wrote: > >=20 > > On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: > >> Hi, > >>=20 > >> I'm not sure - it may be that the timekeeping stuff is a bit confu= sed. > >> Maybe it's now time to file a bug and see if we can loop the > >> timekeeping folk into it. > >=20 > > This is probably not timekeeping. That message is just the last th= ing > > printed before the interrupt-driven hooks are run. If you booted a= HEAD > > snapshot the kernel should have DDB compiled in. Please drop into = DDB > > using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with = the > > output please. > John, > =09Thank you for responding. I tried that but the machine seemed wed= ged at > that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc nor can= I do > Ctrl-Alt-Del to reboot. All I can do it push the reset button. Chris= topher If you let it sit for 60 seconds it should print out a message telling = you=20 what it is waiting on. --=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 15:33:04 2014 Return-Path: Delivered-To: freebsd-hackers@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 4BD1B22A; Fri, 5 Dec 2014 15:33:04 +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 22F07BFC; Fri, 5 Dec 2014 15:33:04 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D9753B9A8; Fri, 5 Dec 2014 10:33:02 -0500 (EST) From: John Baldwin To: Mike Gelfand Subject: Re: [BUG] Getting path to program binary sometimes fails Date: Fri, 05 Dec 2014 10:19:01 -0500 Message-ID: <2066750.N3TZpYSHCy@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: References: <91809230-5E81-4A6E-BFD6-BE8815A06BB2@logicnow.com> <201411201125.30087.jhb@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 05 Dec 2014 10:33:02 -0500 (EST) Cc: Konstantin Belousov , "freebsd-hackers@freebsd.org" , "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 15:33:04 -0000 On Friday, December 05, 2014 12:01:15 PM Mike Gelfand wrote: > John, >=20 > Sorry for late reply. >=20 > On Nov 20, 2014, at 7:25 PM, John Baldwin wrote: > >> Since you=E2=80=99re saying that current behavior is not a defect,= maybe > >> documentation is wrong (incomplete, misleading) then? I will readi= ly > >> accept > >> the =E2=80=9Cnot a defect=E2=80=9D explanation, but only if one wo= uldn=E2=80=99t have to ask you > >> every time this oddity is met. If this is the expected error condi= tion, > >> what should I do to get the path reliably? Should I retry (and how= many > >> times)? You=E2=80=99re saying cache is being purged; does it mean = that when I > >> ask for path then cache is populated again? Does it guarantee then= that > >> I=E2=80=99ll be able to get the path on next call? Could you guara= ntee that I=E2=80=99ll > >> be able to get the path at all if I fail two or more times? Should= I > >> rely on ENOENT specifically when retrying?>=20 > > Is this over NFS? NFS is more aggressive than local filesystems in= > > purging > > name cache entries because there are inherent races in NFS with cer= tain > > fileservers (ones that don't use sub-second timestamps), so by defa= ult > > entries always expire after about a minute. You can change that vi= a the > > 'nametimeo' mount option (takes a count in seconds). >=20 > No, not NFS but ZFS. Could that be an issue? The FreeBSD 8 machine I > mentioned before has UFS. >=20 > Also, as you can see from the video I recorded (and from the code I > provided), path resolution succeeds and fails within fractions of a s= econd > after process startup. Are you seeing vnodes being actively recycled? In particular, do you s= ee=20 vfs.numvnodes close to kern.maxvnodes? You can try raising kern.maxvno= des. =20 If vfs.numvnodes grows up to the limit then as long as you can stomach = the RAM=20 of having more vnodes around that would increase the changes of your pa= ths=20 remaining valid. --=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 15:52:54 2014 Return-Path: Delivered-To: hackers@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 AFE951DB; Fri, 5 Dec 2014 15:52:54 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0060.outbound.protection.outlook.com [157.56.111.60]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (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 DCA60E42; Fri, 5 Dec 2014 15:52:53 +0000 (UTC) Received: from DM2PR04MB477.namprd04.prod.outlook.com (10.141.105.13) by DM2PR04MB478.namprd04.prod.outlook.com (10.141.105.16) with Microsoft SMTP Server (TLS) id 15.1.26.15; Fri, 5 Dec 2014 15:52:42 +0000 Received: from DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) by DM2PR04MB477.namprd04.prod.outlook.com ([169.254.15.29]) with mapi id 15.01.0026.003; Fri, 5 Dec 2014 15:52:41 +0000 From: Mike Gelfand To: "freebsd-hackers@freebsd.org" Subject: Re: [BUG] Getting path to program binary sometimes fails Thread-Topic: [BUG] Getting path to program binary sometimes fails Thread-Index: AQHP/y1OF6HbydE23kCBwyNP5wFRKZxeymWAgAEZIgCACdtQgIAXSR6AgAA3SICAAAlgAA== Date: Fri, 5 Dec 2014 15:52:41 +0000 Message-ID: <27C465FC-E8C7-44CB-A812-65213BB8AC9F@logicnow.com> References: <91809230-5E81-4A6E-BFD6-BE8815A06BB2@logicnow.com> <201411201125.30087.jhb@freebsd.org> <2066750.N3TZpYSHCy@ralph.baldwin.cx> In-Reply-To: <2066750.N3TZpYSHCy@ralph.baldwin.cx> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [128.140.241.14] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB478; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR04MB478; x-forefront-prvs: 04163EF38A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51704005)(24454002)(199003)(377454003)(189002)(122556002)(19580395003)(4396001)(21056001)(76176999)(50986999)(40100003)(54356999)(82746002)(110136001)(87936001)(19580405001)(33656002)(31966008)(92566001)(86362001)(97736003)(106116001)(83716003)(20776003)(105586002)(107046002)(2351001)(99286002)(77156002)(93886004)(36756003)(66066001)(101416001)(120916001)(99396003)(46102003)(2656002)(62966003)(64706001)(106356001)(68736005)(102836002)(85282002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR04MB478; H:DM2PR04MB477.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="Windows-1252" Content-ID: <4B435E7CE4C74B45851B7A335ADC3626@namprd04.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: logicnow.com X-Mailman-Approved-At: Fri, 05 Dec 2014 16:11:07 +0000 Cc: Konstantin Belousov , "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 15:52:54 -0000 On Dec 5, 2014, at 6:19 PM, John Baldwin wrote: > On Friday, December 05, 2014 12:01:15 PM Mike Gelfand wrote: >> John, >>=20 >> Sorry for late reply. >>=20 >> On Nov 20, 2014, at 7:25 PM, John Baldwin wrote: >>>> Since you=92re saying that current behavior is not a defect, maybe >>>> documentation is wrong (incomplete, misleading) then? I will readily >>>> accept >>>> the =93not a defect=94 explanation, but only if one wouldn=92t have to= ask you >>>> every time this oddity is met. If this is the expected error condition= , >>>> what should I do to get the path reliably? Should I retry (and how man= y >>>> times)? You=92re saying cache is being purged; does it mean that when = I >>>> ask for path then cache is populated again? Does it guarantee then tha= t >>>> I=92ll be able to get the path on next call? Could you guarantee that = I=92ll >>>> be able to get the path at all if I fail two or more times? Should I >>>> rely on ENOENT specifically when retrying?>=20 >>> Is this over NFS? NFS is more aggressive than local filesystems in >>> purging >>> name cache entries because there are inherent races in NFS with certain >>> fileservers (ones that don't use sub-second timestamps), so by default >>> entries always expire after about a minute. You can change that via th= e >>> 'nametimeo' mount option (takes a count in seconds). >>=20 >> No, not NFS but ZFS. Could that be an issue? The FreeBSD 8 machine I >> mentioned before has UFS. >>=20 >> Also, as you can see from the video I recorded (and from the code I >> provided), path resolution succeeds and fails within fractions of a seco= nd >> after process startup. >=20 > Are you seeing vnodes being actively recycled? In particular, do you see= =20 > vfs.numvnodes close to kern.maxvnodes? You can try raising kern.maxvnode= s. =20 > If vfs.numvnodes grows up to the limit then as long as you can stomach th= e RAM=20 > of having more vnodes around that would increase the changes of your path= s=20 > remaining valid. When the call works, sysctl returns: vfs.numvnodes: 59638 kern.maxvnodes: 204723 The times it doesn't, the output is: vfs.numvnodes: 60017 kern.maxvnodes: 204723 I've selected maximum numbers. Monitoring was made with while sysctl vfs.numvnodes kern.maxvnodes; do sleep 0.1; done So it seems that's not related, correct? 60K is much less than 200K.= From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 6 08:02:23 2014 Return-Path: Delivered-To: hackers@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 599D99EA for ; Sat, 6 Dec 2014 08:02:23 +0000 (UTC) Received: from mail104.syd.optusnet.com.au (mail104.syd.optusnet.com.au [211.29.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 1BA4C6D for ; Sat, 6 Dec 2014 08:02:22 +0000 (UTC) Received: from zen.home (c211-30-203-218.thorn2.nsw.optusnet.com.au [211.30.203.218]) (Authenticated sender: tonymaher@optusnet.com.au) by mail104.syd.optusnet.com.au (Postfix) with ESMTPA id AAB09427AB8; Sat, 6 Dec 2014 19:02:13 +1100 (AEDT) Message-ID: <5482B805.3020602@optusnet.com.au> Date: Sat, 06 Dec 2014 19:02:13 +1100 From: Tony Maher User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "Christopher R. Bowman" , hackers@freebsd.org Subject: Re: 10.1 hangs during boot on Intel DP35DP board References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> In-Reply-To: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=dMCfxopb c=1 sm=1 tr=0 a=MQ6uhdTv3FoGARDo7fdH2w==:117 a=MQ6uhdTv3FoGARDo7fdH2w==:17 a=PO7r1zJSAAAA:8 a=_M8H_RHeOCMA:10 a=IkcTkHD0fZMA:10 a=cw05NTwktiMzpfJWm-UA:9 a=QEXdDO2ut3YA:10 a=zS7aEKoigL4A:10 a=xXYpSUSE7EsA:10 a=orrfKppWePsA:10 a=TGm2L-IbwjAA:10 a=XLPQ4plS_DgA:10 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 08:02:23 -0000 I finally got a chance to try USB memstick with 10.1. It failed with BTX halted. I tried various BIOS options related to USB booting but same result everytime. I could Ctrl-Alt-Del to reboot. Not much help I am afraid. cheers -- Tony Maher email: tonymaher@optusnet.com.au From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 6 14:43:43 2014 Return-Path: Delivered-To: freebsd-hackers@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 F2A9CE1F; Sat, 6 Dec 2014 14:43:42 +0000 (UTC) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 993B4A77; Sat, 6 Dec 2014 14:43:42 +0000 (UTC) Received: from fwd41.aul.t-online.de (fwd41.aul.t-online.de [172.20.27.139]) by mailout01.t-online.de (Postfix) with SMTP id D5CD35F7DE4; Sat, 6 Dec 2014 15:34:24 +0100 (CET) Received: from [192.168.119.11] (rAOQ8qZlQhBXdVYDX5Ei7ZINu5EqJyXaOtOmowGeISv5hu8Bzj3HraxISFDGD9eg5T@[84.154.99.91]) by fwd41.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XxGR8-3r7OnA0; Sat, 6 Dec 2014 15:34:18 +0100 Message-ID: <548313E1.1040701@freebsd.org> Date: Sat, 06 Dec 2014 15:34:09 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Phil Shafer Subject: Re: [Review] pciconf converted to use libxo [D1206] References: <201412042056.sB4KubEC029247@idle.juniper.net> In-Reply-To: <201412042056.sB4KubEC029247@idle.juniper.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-ID: rAOQ8qZlQhBXdVYDX5Ei7ZINu5EqJyXaOtOmowGeISv5hu8Bzj3HraxISFDGD9eg5T X-TOI-MSGID: 56e01945-6294-470b-91d6-a92e96d77ed4 Cc: "freebsd-hackers@freebsd.org" , "Simon J. Gerraty" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 14:43:43 -0000 Am 04.12.2014 um 21:56 schrieb Phil Shafer: > Stefan Esser writes: >> the following review URL shows my proposed changes to make pciconf >> optionally output XML or JSON formatted data via libxo: >> https://reviews.freebsd.org/D1206 > > Looks good. some nits: Hi Phil, thank you *very* much for your review and the valuable hints! > Remove the call to xo_create(), which creates a new handle. All > your calls are using the default handle, and since you're not saving > the returned handle, it's pointless. OK. > Use "revision" for "rev" and "header" instead of "hdr". See the > notes re: full words in xo_format(5). Yes, I see. I have fixed the names in my local working copy ... (AFAIR, the man-pages did not exist in -CURRENT when I started to work on libxo support for pciconf in early October. I used the information from http://juniper.github.io/libxo/libxo-manual.html as reference. The man-pages look well structured and I appreciate them.) BTW: Any reason that xolint.1 ist not installed? And another BTW: The man-page for xo(1) does only mention xo_emit(3) and lacks reference to other xo man-pages. The same applies to the man-page for xo_create(3), which has "SEE ALSO xo_emit(3) and" and stops there. (I did not check all man-pages for missing references, but many of the others seem to have a reasonable SEE ALSO list.) > The xo_open_list, xo_open_instance, and xo_container functions > are needed to frame the calls to xo_emit. xo_open_list is used > before starting a list, and xo_open_instance before each instance > in that list: > > xo_open_list("device"); > for (p = conf; p < &conf[pc.num_matches]; p++) { > xo_open_instance("device"); > xo_emit(...); > xo_close_instance("device"); > } > xo_close_list("device"); > > These calls are needed to marshall data correctly into the various > output formats. Each xo_open_xxx needs a matching xo_close_xxx > call. I wondered about correct use of the different xo_open_XXX calls. Seems they do not make any difference for XML and HTML, but are important for correct JSON output. > Does that make sense? You'll need to redo these calls in your code. > Please let me know what can be done in the docs to make this more > clear. The xo_open_list man-page seems reasonably clear, I just did not know it existed ;-) > If "device-id" is the key for this list, use the "k" > modifier: > > xo_emit("{k:device-id/%s%d}..."); > > This will allow the use of that key in XPath expressions. This does not seem to work for me, for example: xo_emit("{k:device-id/%s%d}@{:bus-id/pci%d:%d:%d:%d}:\t..." generates e.g. re0 pci0:4:0:0 0x020000 0x84321043 0x816810ec 0x06 0x00 which is identical to the output without the "k". What am I doing wrong? > + xo_destroy(NULL); > > You don't need to destroy the default handle. xo_finish is sufficient. OK. > You have: > > + xo_emit(" VPD ident = '{:ident/%s}'\n", pve_str); > > and: > > + xo_emit(" VPD {:mode/ro} {:keyword/CP} = ID {:id/%02x} in map {:addr/0x%x}[{:size/0x%x}]\n", > > I'm not sure what the contents are but it seems like the former > might have "VPD {:mode/indent}" to be consistent. The problem is, that I do not know much about VPD and have no device that has it. I had been hoping for a review of these particular lines from somebody who knows VPD. Guess it's best to directly ask jhb for a review of this part, since he added VPD printing in January ... > - printf("%0*x", width*2, read_config(fd, sel, reg, width)); > + char buf[11]; > + snprintf(buf, sizeof(buf), "%0*x", width*2, read_config(fd, sel, reg, width)); > + xo_emit("{:cfgdata/%s}", buf); > > libxo should be able to handle this directly, without the need for 'buf': The information in the HTML docs on GitHub made me think, that this format was not supported. > xo_emit("{:data/%0*x}", width*2, read_config(fd, sel, reg, width)); This results in better output, for example with JSON: "cfgdata": d001 instead of with the string buffer: "cfgdata": "0000d001" But it appears, that xo_emit adds blanks to the left of the value, while I'd expect the padding to use zeroes. I changed the format to "{:data/0x%0*x}" and now I get "cfgdata": "0x0000d001" <-- xo_emit("{:data/0x%s}", ...) "cfgdata": 0x0000d001 <-- xo_emit("{:data/0x%0*x}", ...) I.e. it seems that the leading zeroes are replaced by blanks, but non-leading zeroes are kept (' d001' vs. '0x0000d001'). Not sure whether that is expected behaviour - at least it differs from printf ... I found a few more nits in the version of pciconf that I uploaded to the reviews server (e.g. with printing of config space data), and the printing of VPD might be broken if different record types are not grouped together (see the xo_close_list() functions that are not strictly matching the corresponding open functions). I'll probably have to split the VPD output into three distinct loops, two for lists (capabilities and items) and one for the remaining record types. It'll take me a few days to prepare a new version and I'm still open for further comments. >> I wanted to see how much effort the conversion of a utility that >> was not written with libxo in mind makes - and I'm pleased by the >> possibility to mostly mechanically replace printf/err/warn calls >> with their libxo counterparts. > > I tried to make it plug compatible. I noticed that and appreciate it. >> The documentation of libxo seems incomplete (e.g. no mention of >> xo_error() that I could find), and some functions do not seem to >> produce the expected result (xo_err() prints the message as given >> in the format string, but does not automatically append strerror() >> as err() does ...). > > Looks like I missed xo_error completely. I'll add docs for it. > > xo_err() should be identical to err(), but it's broken. I'll take > a look. Thanks. >> A FreeBSD man-page that lists all functions and that can be used >> as a reference when libxo principles are already known would be >> really great. ;-) > > A libxo(3) page? I'll cook one up. I have noticed the commit that added lots of MLINKS and expecially the libxo(3) and it is a good introduction to the library. BTW: Another man-page that lacks references: xo(1) mentions xo_emit(3), but should probably point to libxo(3) instead ... >> The HTML-Output looks ugly if directly viewed in a web browser, >> but that's not different than what other utilities converted to >> use libxo produce ... > > I'm working on a utility called "xohtml" that adds a css file to the > output to make it viewable. It doesn't install yet, but you can > run it by hand using something like: OK, that seems like a good addition to the whole package. > sh ./xohtml/xohtml.sh -b $PWD/../xohtml -c './tests/core/test_01.test --libxo:HPx' > /tmp/foo.html > > -b gives the base directory to find css and js files > -c gives the command to run > > These options will likely change before it's finished. > > I've opened issues for all these on github. I'm afraid there might have mentioned a few more (minor) issues in this mail ;-) Thanks again for this valuable addition to FreeBSD. I've been wondering whether it might be a good idea to create a "wish list" on a Wiki page, where utilities that might benefit from libxo could be listed (for example fstat, pstat, ps, ls, ifconfig, ...). Adding libxo support could be a good Junior Hackers task and might even attract a few people to work on FreeBSD ... Best regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 6 21:37:19 2014 Return-Path: Delivered-To: freebsd-hackers@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 DEBE6FBD for ; Sat, 6 Dec 2014 21:37:19 +0000 (UTC) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) (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 ACFEF3D2 for ; Sat, 6 Dec 2014 21:37:19 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id kx10so2833856pab.30 for ; Sat, 06 Dec 2014 13:37:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=RSibqsNtw5sm1qieRz93Z0wKkSuFS6n/ur+u8hYc728=; b=a+ROtvQl8lYyhVknf/ugZwv6iODEINdApZn2wGz1R2MuBcjI48bqDqWP/IK9dVOt/t 4fFdnrp38JTOcaEsWnRjZ0eklnaEuoA43aRq8aH2aFyQmWFMkqlRWs/3hjRVqJHGwHlF sehBcnoyOTraXN/z/fY+YuPMmBCw7QC3GdbRtNfZJ4U84nqpsyE6CPqrdktQqCvbqOzu m2WqCfR6P4eSc/8cEbdAijGcSmOJHkPxPrGyChkjXAiwRt9OHYwK66UGoZ/HICVNFH2s 2tAS0+/nIm7YkjNjmS2HNhKYx+H1xe4tqwgu1QIqOqNCwQWyBfeZ9aap7ewqg3Bpbq3p 8ZZw== X-Gm-Message-State: ALoCoQlxDkhpjLXz7dqTkJD0H6oDpEn/MzK4MvQ4e7HDRPU2jQaUnwiYRDcJjPAwcK6iH+77bkwe X-Received: by 10.66.102.41 with SMTP id fl9mr40189883pab.7.1417901832896; Sat, 06 Dec 2014 13:37:12 -0800 (PST) Received: from [10.0.0.201] (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id w5sm32538389pds.25.2014.12.06.13.37.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Dec 2014 13:37:10 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: 10.1 hangs during boot on Intel DP35DP board X-Mailer: iPhone Mail (11D257) In-Reply-To: <4750778.kghJ8KRE21@ralph.baldwin.cx> Date: Sat, 6 Dec 2014 13:37:09 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <201412041139.31416.jhb@freebsd.org> <366F5C20-E685-4C8F-82CB-237E5E102C78@ChrisBowman.com> <4750778.kghJ8KRE21@ralph.baldwin.cx> To: John Baldwin Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 21:37:20 -0000 John, Its still sitting but I turned on verbose output and it's been sitting for 1= 0 minutes so far without any further output.=20 Christopher.=20 -- Christopher R. Bowman > On Dec 5, 2014, at 7:20 AM, John Baldwin wrote: >=20 > On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman wrote: >>> On Dec 4, 2014, at 8:39 AM, John Baldwin wrote: >>>=20 >>>> On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: >>>> Hi, >>>>=20 >>>> I'm not sure - it may be that the timekeeping stuff is a bit confused. >>>> Maybe it's now time to file a bug and see if we can loop the >>>> timekeeping folk into it. >>>=20 >>> This is probably not timekeeping. That message is just the last thing >>> printed before the interrupt-driven hooks are run. If you booted a HEAD= >>> snapshot the kernel should have DDB compiled in. Please drop into DDB >>> using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with the >>> output please. >> John, >> Thank you for responding. I tried that but the machine seemed wedged a= t >> that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc nor can I d= o >> Ctrl-Alt-Del to reboot. All I can do it push the reset button. Christoph= er >=20 > If you let it sit for 60 seconds it should print out a message telling you= =20 > what it is waiting on. >=20 > --=20 > John Baldwin