From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 02:06:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 70E95FAE; Sun, 3 Feb 2013 02:06:23 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 358D1F48; Sun, 3 Feb 2013 02:06:22 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id EACDA6001; Sat, 2 Feb 2013 20:06:13 -0600 (CST) Date: Sat, 2 Feb 2013 20:06:13 -0600 From: Mark Linimon To: Brooks Davis Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 Message-ID: <20130203020613.GB3441@lonesome.com> References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130201175303.GA5914@lor.one-eyed-alien.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Kimmo Paasiala , freebsd-stable@freebsd.org, Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 02:06:23 -0000 On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: > I'm not sure why I'm being jumped on in this weeks old report of a > now-fixed problem. I'm sorry, I'm that far behind in email. I did not realize the problem had already been solved. More often than not the problem is simply "thrown over the fence" for the ports team to deal with. mcl From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 03:55:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8E463152; Sun, 3 Feb 2013 03:55:10 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id CDFC134F; Sun, 3 Feb 2013 03:55:09 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so1845284wib.9 for ; Sat, 02 Feb 2013 19:55:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/1Rv/8z8swo0t1Bya2hFsmtSdvOdeGuHuHWnlvK/82Q=; b=INYzdLKeNzsQyvt9dHlar6GpSSi3F2CXqyWE8OM7N6523LHfzS0RUcu0F3owjJqMee nz6cgsUMycu63ZmMZNSuoKTMczIzmsIgZfdBVx52J/CKYPyxI3anfsrsg9UHIblHXu97 NrMurSZw/qRA+mwuxoFSqU8RQ5vCD83R63+gJXnUZAp/uPlvTAncweqZqsQWxlAmw2VN Np5ms6A0eW2ky8vyMR8iegXy9TEMp0hSK6atyVVejMvAJnHZRZjPXYYe5bNFpRpqko1H Zy5IxUtUg0l07z/K7kPsEv7q1nVwGkn5oQxrrUBuc4PxMzMoN71exT3xQsKOZMYM6wR5 cvVw== MIME-Version: 1.0 X-Received: by 10.194.21.70 with SMTP id t6mr28792741wje.42.1359863703150; Sat, 02 Feb 2013 19:55:03 -0800 (PST) Received: by 10.216.172.197 with HTTP; Sat, 2 Feb 2013 19:55:02 -0800 (PST) In-Reply-To: <20130203020613.GB3441@lonesome.com> References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> <20130203020613.GB3441@lonesome.com> Date: Sun, 3 Feb 2013 05:55:02 +0200 Message-ID: Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 From: Kimmo Paasiala To: Mark Linimon Content-Type: text/plain; charset=UTF-8 Cc: Dimitry Andric , Brooks Davis , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 03:55:10 -0000 On Sun, Feb 3, 2013 at 4:06 AM, Mark Linimon wrote: > On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: >> I'm not sure why I'm being jumped on in this weeks old report of a >> now-fixed problem. > > I'm sorry, I'm that far behind in email. I did not realize the problem > had already been solved. > > More often than not the problem is simply "thrown over the fence" for > the ports team to deal with. > > mcl There is no PR yet with my fix and therefor no commit to ports tree that would fix the problem. I'll file a PR soon (TM). -Kimmo From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 09:44:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C13DCFDE for ; Sun, 3 Feb 2013 09:44:54 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay.exonetric.net (relay0.exonetric.net [178.250.72.161]) by mx1.freebsd.org (Postfix) with ESMTP id 89EEEF07 for ; Sun, 3 Feb 2013 09:44:53 +0000 (UTC) Received: from [192.168.0.13] (186.211.187.81.in-addr.arpa [81.187.211.186]) by relay.exonetric.net (Postfix) with ESMTPSA id 772BE2C7E1; Sun, 3 Feb 2013 09:44:47 +0000 (GMT) From: Mark Blackman Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 3 Feb 2013 09:44:46 +0000 Subject: unofficial pkgng repository at http://mirror.exonetric.net/pub/pkgng To: freebsd-stable@freebsd.org Message-Id: <09084C71-F028-4E7A-BCDC-7BFF7F275A1D@exonetric.com> Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 09:44:54 -0000 Hi, I'm just writing to let anyone know, who might find it useful, that we=20= have set-up an unofficial but public pkgng repository available at http://mirror.exonetric.net/pub/pkgng until official pkgng format packages are available. With the able assistance of Gavin Atkinson, who managed all the package building for us, we currently have pkgng format packages for FreeBSD-8 and FreeBSD-9, for both i386 and amd64 kernels. These packages have no particular blessing from the FreeBSD project, but as far as we know, they don't mind either. To use these packages, just set your PACKAGESITE variable in = /usr/local/etc/pkg.conf like so,=20 PACKAGESITE : = http://mirror.exonetric.net/pub/pkgng/${ABI}/latest Gavin is also working on a FreeBSD-10 set of packages, but those are a few days or so away at this point. Please let us know about any issues you find as well, of course. Cheers, Mark Blackman=20 From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 09:58:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A7439445; Sun, 3 Feb 2013 09:58:09 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x234.google.com (ie-in-x0234.1e100.net [IPv6:2607:f8b0:4001:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 5F400F6E; Sun, 3 Feb 2013 09:58:09 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id bn7so3696425ieb.39 for ; Sun, 03 Feb 2013 01:58:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=CK8jPKWDBUOp3L1KtWv31NyVFfvlVPIHEziiv3+pTLM=; b=s7zM0eFLSgCrsJnZYT+wnWXbeSgovm2fp6lDRVrfQxunE8zxj/M0ZWGR+LFIkjAF6h Aicwh4TaZWWQVwkzOjCpO48DfKnGFG9BFRxy7UA7UNGJuV74Y5Nc/xX8itWYD+NXfACA Mp/8hgWba1aOGxwj8N9j5SUQOCxLee9/Id6lIJX1J5ScfpPuM+kCmBxVofWt3Gnjns9R zR1EzsTwFjR77/E8dA85PmFK5WmHmWFJRE5ddRm0W1/C7dd4BpcKgHDNVNksCu6/YcHn sG9tgDRESEZSwi5dpLyLj7CEfQypPIPycIGzI7PNVjlnU6vW3KjQdtriCdxsE1jJcjVq zELg== X-Received: by 10.50.178.10 with SMTP id cu10mr2706824igc.75.1359885489128; Sun, 03 Feb 2013 01:58:09 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.64.16.73 with HTTP; Sun, 3 Feb 2013 01:57:39 -0800 (PST) In-Reply-To: References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> <20130203020613.GB3441@lonesome.com> From: Chris Rees Date: Sun, 3 Feb 2013 09:57:39 +0000 X-Google-Sender-Auth: ZN3y6PRSnn5PZOwLpaVERsMZaJ0 Message-ID: Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 To: Kimmo Paasiala Content-Type: text/plain; charset=ISO-8859-1 Cc: Mark Linimon , Brooks Davis , Dimitry Andric , FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 09:58:09 -0000 On 3 February 2013 03:55, Kimmo Paasiala wrote: > On Sun, Feb 3, 2013 at 4:06 AM, Mark Linimon wrote: >> On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: >>> I'm not sure why I'm being jumped on in this weeks old report of a >>> now-fixed problem. >> >> I'm sorry, I'm that far behind in email. I did not realize the problem >> had already been solved. >> >> More often than not the problem is simply "thrown over the fence" for >> the ports team to deal with. >> >> mcl > > There is no PR yet with my fix and therefor no commit to ports tree > that would fix the problem. I'll file a PR soon (TM). The problem was in base, and is fixed there. Chris From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 10:39:26 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EA9E6139 for ; Sun, 3 Feb 2013 10:39:26 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 8FCB916D for ; Sun, 3 Feb 2013 10:39:26 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id l10so5688156oag.30 for ; Sun, 03 Feb 2013 02:39:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UUe9wsuJJs1VsF5GUDS1hHcepWg6fiGrydudKUUHrGs=; b=IF+qEpzwgJuDTrkTUSNctXSgFSU17vGBxUn11qvukfIuqflnri528ZVgRyInyWp4nd mR1x+TiHcRUtjEE/jGZEjgqRqTKiKaKAnzf8RRfFyiSdXLfK7aus2C5f3S0xA+XOxbtC otRhSpGh8T4D9g/i3/KoCg4K51HT13DCARTBXR7wUHulTdMONyviaWnOpVQYX08eVXrO B0nPFSPhoxlXtFJhH75QFHfGg92VGRkQSnj4uUyo9nmKBRTGn1FMwzgemnrkB1NnI9m8 65PW0wcDTXR7fyjn1XMx24m8teorae32pJIe4hjG+HEb6lP4IAyGmyljvpGM7fQRW7hr pYXA== MIME-Version: 1.0 X-Received: by 10.182.54.46 with SMTP id g14mr12199756obp.55.1359887960638; Sun, 03 Feb 2013 02:39:20 -0800 (PST) Received: by 10.76.10.105 with HTTP; Sun, 3 Feb 2013 02:39:20 -0800 (PST) Date: Sun, 3 Feb 2013 11:39:20 +0100 Message-ID: Subject: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 10:39:27 -0000 Hello, I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in libmap.conf ), and started to build my normal set of packages ( see desktop.list ). Please note that I also have WITH_NEW_XORG=yes and WITH_KMS=yes, as well as using the devel xorg repo. First Great work for moving FreeBSD towards a more modern c++ world! Results: Some stuff works, some don't ;) Some may be due to clang and not just libc++. Here is a list of packages that fails: audio/libofa databases/akonadi devel/binutils devel/kBuild devel/libftdi devel/libplist devel/qca devel/qt4-qdbusviewer devel/qt4-script emulators/qemu-devel graphics/cairo graphics/graphite2 graphics/libfpx graphics/opencv-core graphics/podofo graphics/vigra lang/sbcl math/cln net-im/libmsn net-p2p/libtorrent net/hupnp net/ns3 net/xmlrpc-c-devel science/openbabel security/pinentry sysutils/fusefs-kmod sysutils/synergy textproc/clucene x11/nvidia-driver where at least ns3 can be ignored ( I created that port myself ). I think nvidia-driver and fusefs-kmod now fails due to -stdlib=libc++ in LDFLAGS, normally fusefs-kmod just fails install-phase due to missing pkg-message file. I saved the workdirs for poudriere, and they are available at http://benriach.widell.net/~andrnils/libc++/ , both as individual tarballs and one tarball that includes all the others. There is also the lists of packages I try to build, as well as the ones that fails. One general question: How am I supposed to include -stdlib=libc++ in LDFLAGS just for c++? Having -stdlib=libc++ in LDFLAGS causes c compiles to fail linking with "ld: unrecognized option '-stdlib=libc++'" Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 13:28:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 10C845DE for ; Sun, 3 Feb 2013 13:28:29 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id CDF267D8 for ; Sun, 3 Feb 2013 13:28:28 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:a952:1158:bfb6:380] (unknown [IPv6:2001:7b8:3a7:0:a952:1158:bfb6:380]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 4028C5C5A; Sun, 3 Feb 2013 14:28:26 +0100 (CET) Message-ID: <510E65FA.4040900@FreeBSD.org> Date: Sun, 03 Feb 2013 14:28:26 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: Andreas Nilsson , FreeBSD Stable Mailing List Subject: Re: Ports and WITH_LIBCPLUSPLUS References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 13:28:29 -0000 On 2013-02-03 11:39, Andreas Nilsson wrote: > I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I > used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in > src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in > libmap.conf ), and started to build my normal set of packages ( see > desktop.list ). Please note that I also have WITH_NEW_XORG=yes and > WITH_KMS=yes, as well as using the devel xorg repo. > > First Great work for moving FreeBSD towards a more modern c++ world! > > Results: > Some stuff works, some don't ;) Some may be due to clang and not just > libc++. Here is a list of packages that fails: > > audio/libofa > databases/akonadi > devel/binutils > devel/kBuild > devel/libftdi > devel/libplist > devel/qca > devel/qt4-qdbusviewer > devel/qt4-script > emulators/qemu-devel > graphics/cairo > graphics/graphite2 > graphics/libfpx > graphics/opencv-core > graphics/podofo > graphics/vigra > lang/sbcl > math/cln > net-im/libmsn > net-p2p/libtorrent > net/hupnp > net/ns3 > net/xmlrpc-c-devel > science/openbabel > security/pinentry > sysutils/fusefs-kmod > sysutils/synergy > textproc/clucene > x11/nvidia-driver Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I expect there will be quite a few ports that are very difficult to get building and running properly with libc++. Some programs rely on undocumented (or half-documented) libstdc++ internals, or on behaviour specific to libstdc++. Also, it would not suprise me if there are programs that even depend on a very specific version of libstdc++, and its accompanying version of gcc. In short, we need some sort of system to specify the general C++ library to use by default (e.g. in make.conf or ports.conf), and for ports that only work with a very specific version, a variable similar to USE_GCC, for example: USE_LIBSTDCXX=4.6+ > where at least ns3 can be ignored ( I created that port myself ). I think > nvidia-driver and fusefs-kmod now fails due to -stdlib=libc++ in LDFLAGS, > normally fusefs-kmod just fails install-phase due to missing pkg-message > file. > > I saved the workdirs for poudriere, and they are available at > http://benriach.widell.net/~andrnils/libc++/ , both as individual tarballs > and one tarball that includes all the others. There is also the lists of > packages I try to build, as well as the ones that fails. > > > One general question: How am I supposed to include -stdlib=libc++ in > LDFLAGS just for c++? Having -stdlib=libc++ in LDFLAGS causes c compiles to > fail linking with "ld: unrecognized option '-stdlib=libc++'" This is as yet an unsolved problem, as LDFLAGS is the same for both C and C++ link jobs. I think the easiest way would be to set your CXX variable to: CXX=cc -stdlib=libc++ The -std=c++11 flag should only have to be specified in CXXFLAGS. I don't think it has any influence on linking. From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 13:56:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CCF95936; Sun, 3 Feb 2013 13:56:43 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by mx1.freebsd.org (Postfix) with ESMTP id 7C55789D; Sun, 3 Feb 2013 13:56:43 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id lz20so5554565obb.30 for ; Sun, 03 Feb 2013 05:56:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gML96W8TDmyZDUjNXjHWHNbcYxXr854mBpv11F8v3no=; b=mBVdqn1uB3QA3hy3uvOXOmEje5lJccCHrZPqia7ZxaLwyJYIwM5jvZqDXGMI0yG+VY N8D/zszQKL/1ve9D8d9EM1NH8g/bsaoSXvtKnI1ZDX1/ZdDK4bhT4eG+6OdcAwZhrQGb iashNMOJGhINlTfchiDcTTG6EHfv89ZQHa5vvBkKXYZaLb1SKabfqC8lUxrtVvowv2H8 t+cql+Bd5H5YX+2z8JmHjbaMxgr8u+E5P0zhNoEpQdwMCg2lFHxeGF3UMoQ/Up7JAA+7 gkn1burTgTC/A8Oq1quwhasXL2IgFxfw9Rnq5eV3LWyTrMwuq2HarzTq3iRqZRPOAZ2c bZUw== MIME-Version: 1.0 X-Received: by 10.60.8.134 with SMTP id r6mr14284873oea.53.1359899797066; Sun, 03 Feb 2013 05:56:37 -0800 (PST) Received: by 10.76.10.105 with HTTP; Sun, 3 Feb 2013 05:56:36 -0800 (PST) In-Reply-To: <510E65FA.4040900@FreeBSD.org> References: <510E65FA.4040900@FreeBSD.org> Date: Sun, 3 Feb 2013 14:56:36 +0100 Message-ID: Subject: Re: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 13:56:43 -0000 On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric wrote: > On 2013-02-03 11:39, Andreas Nilsson wrote: > >> I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I >> used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in >> src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in >> libmap.conf ), and started to build my normal set of packages ( see >> desktop.list ). Please note that I also have WITH_NEW_XORG=yes and >> WITH_KMS=yes, as well as using the devel xorg repo. >> >> First Great work for moving FreeBSD towards a more modern c++ world! >> >> Results: >> Some stuff works, some don't ;) Some may be due to clang and not just >> libc++. Here is a list of packages that fails: >> >> audio/libofa >> databases/akonadi >> devel/binutils >> devel/kBuild >> devel/libftdi >> devel/libplist >> devel/qca >> devel/qt4-qdbusviewer >> devel/qt4-script >> emulators/qemu-devel >> graphics/cairo >> graphics/graphite2 >> graphics/libfpx >> graphics/opencv-core >> graphics/podofo >> graphics/vigra >> lang/sbcl >> math/cln >> net-im/libmsn >> net-p2p/libtorrent >> net/hupnp >> net/ns3 >> net/xmlrpc-c-devel >> science/openbabel >> security/pinentry >> sysutils/fusefs-kmod >> sysutils/synergy >> textproc/clucene >> x11/nvidia-driver >> > > Thanks for trying this out. Is there also a list of ports that *do* > compile (and hopefully run) successfully? :-) > I didn't save the output for successful packages, but looking through just the files gives libcpp.built at same URL. > > I expect there will be quite a few ports that are very difficult to get > building and running properly with libc++. Some programs rely on > undocumented (or half-documented) libstdc++ internals, or on behaviour > specific to libstdc++. > > Also, it would not suprise me if there are programs that even depend on > a very specific version of libstdc++, and its accompanying version of > gcc. > > In short, we need some sort of system to specify the general C++ library > to use by default (e.g. in make.conf or ports.conf), and for ports that > only work with a very specific version, a variable similar to USE_GCC, > for example: > > USE_LIBSTDCXX=4.6+ Sounds good :) Perhaps something like if (( CLANG_IS_CC || CC==clang ) && WITH_LIBCPLUSPLUS ) CXXFLAGS+=-stdlib=libc++ endif could be added to correct mk-file > > > > where at least ns3 can be ignored ( I created that port myself ). I think >> nvidia-driver and fusefs-kmod now fails due to -stdlib=libc++ in LDFLAGS, >> normally fusefs-kmod just fails install-phase due to missing pkg-message >> file. >> >> I saved the workdirs for poudriere, and they are available at >> http://benriach.widell.net/~**andrnils/libc++/, both as individual tarballs >> and one tarball that includes all the others. There is also the lists of >> packages I try to build, as well as the ones that fails. >> >> >> One general question: How am I supposed to include -stdlib=libc++ in >> LDFLAGS just for c++? Having -stdlib=libc++ in LDFLAGS causes c compiles >> to >> fail linking with "ld: unrecognized option '-stdlib=libc++'" >> > > This is as yet an unsolved problem, as LDFLAGS is the same for both C > and C++ link jobs. I think the easiest way would be to set your CXX > variable to: > > CXX=cc -stdlib=libc++ > Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and CC for c++, or have that convention gone away? > > The -std=c++11 flag should only have to be specified in CXXFLAGS. I > don't think it has any influence on linking. > My adding them to LDFLAGS comes from https://wiki.freebsd.org/NewC++Stackwhere it says "Add -stdlib=libc++ to your compile and link flags..." It actually made a bunch of the qt4- packages build, they wouldn't without it. I guess a wiki page tracking the failing packages would be good, but I couldn't get the hang of creating a page there :( Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 14:25:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CAC5672 for ; Sun, 3 Feb 2013 14:25:49 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 910C19A2 for ; Sun, 3 Feb 2013 14:25:49 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:a952:1158:bfb6:380] (unknown [IPv6:2001:7b8:3a7:0:a952:1158:bfb6:380]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8C5AA5C5A; Sun, 3 Feb 2013 15:25:41 +0100 (CET) Message-ID: <510E7365.3060807@FreeBSD.org> Date: Sun, 03 Feb 2013 15:25:41 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: Andreas Nilsson Subject: Re: Ports and WITH_LIBCPLUSPLUS References: <510E65FA.4040900@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 14:25:49 -0000 On 2013-02-03 14:56, Andreas Nilsson wrote: > On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric wrote: ... >> This is as yet an unsolved problem, as LDFLAGS is the same for both C >> and C++ link jobs. I think the easiest way would be to set your CXX >> variable to: >> >> CXX=cc -stdlib=libc++ >> > Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and CC > for c++, or have that convention gone away? Sorry, I should have taken one more cup of coffee. :-) 'CC' is not really recommended anymore, just use: CXX=c++ -stdlib=libc++ > My adding them to LDFLAGS comes from > https://wiki.freebsd.org/NewC++Stackwhere it says "Add -stdlib=libc++ > to your compile and link flags..." Yes, that advice is just fine, but in some cases you cannot influence the link flags used only for C++ linking. In those cases, you will have to trick the build system into doing so. In most cases (but probably not all), this can be done by adding the required flags to ${CXX}. > It > actually made a bunch of the qt4- packages build, they wouldn't without it. > > I guess a wiki page tracking the failing packages would be good, but I > couldn't get the hang of creating a page there :( This would better be done by a normal exp-run procedure, but those are offline for the time being. From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 14:33:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A3732FB; Sun, 3 Feb 2013 14:33:41 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7439F5; Sun, 3 Feb 2013 14:33:41 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id wd20so5546622obb.37 for ; Sun, 03 Feb 2013 06:33:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dCWFRlq0aUgqWEs5IUvW8ztRiuO/uiTdZJMJIlX3RQk=; b=Tjyyv6SiBAxfuFwPum8NJIWkcHAkMv022I+mPfmdZQCqpWZ73GAf7ncPBeLV/qJ5cq nl3kxeYYLjSNvS7+BBAsj1+ou4ahvLwS03NwpcWwowsHs6GaHo7uQkS6R6erpK2AG69B jb//Kc20au0imrOxNR/emmOoY9tLIfDUPdXDJP1zGe50Jhe0alxWkjinFTue11omNE3H sxhOK22xhowWCHxKL5cwa/2Z7VCGIJcTJo6Gpw8o2v1swS75UfBzbsXy5YntbX7FLyHP cPsyzozzySIUNnMnvv7mznQ27G2pg4x/i2eWIvKfc8RXvAUXtnwWDTwkTJHKWvrXlR0S 2qAg== MIME-Version: 1.0 X-Received: by 10.182.40.71 with SMTP id v7mr12892929obk.85.1359902020732; Sun, 03 Feb 2013 06:33:40 -0800 (PST) Received: by 10.76.10.105 with HTTP; Sun, 3 Feb 2013 06:33:40 -0800 (PST) In-Reply-To: <510E7365.3060807@FreeBSD.org> References: <510E65FA.4040900@FreeBSD.org> <510E7365.3060807@FreeBSD.org> Date: Sun, 3 Feb 2013 15:33:40 +0100 Message-ID: Subject: Re: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 14:33:41 -0000 On Sun, Feb 3, 2013 at 3:25 PM, Dimitry Andric wrote: > On 2013-02-03 14:56, Andreas Nilsson wrote: > >> On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric wrote: >> > ... > > This is as yet an unsolved problem, as LDFLAGS is the same for both C >>> and C++ link jobs. I think the easiest way would be to set your CXX >>> variable to: >>> >>> CXX=cc -stdlib=libc++ >>> >>> Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and >> CC >> for c++, or have that convention gone away? >> > > Sorry, I should have taken one more cup of coffee. :-) 'CC' is not > really recommended anymore, just use: > > CXX=c++ -stdlib=libc++ > Ah, yes. To little coffee here as well. > > My adding them to LDFLAGS comes from >> https://wiki.freebsd.org/NewC+**+Stackwhereit says "Add -stdlib=libc++ >> >> to your compile and link flags..." >> > > Yes, that advice is just fine, but in some cases you cannot influence > the link flags used only for C++ linking. In those cases, you will have > to trick the build system into doing so. > > In most cases (but probably not all), this can be done by adding the > required flags to ${CXX}. Good point. > > > > It >> actually made a bunch of the qt4- packages build, they wouldn't without >> it. >> >> I guess a wiki page tracking the failing packages would be good, but I >> couldn't get the hang of creating a page there :( >> > > This would better be done by a normal exp-run procedure, but those are > offline for the time being. > On a side note: I forget the actual logs. They are now available as logs.tgz at same base URL. Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 14:59:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7F1AB840; Sun, 3 Feb 2013 14:59:03 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-we0-x22f.google.com (we-in-x022f.1e100.net [IPv6:2a00:1450:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 8895AAE1; Sun, 3 Feb 2013 14:59:02 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id x8so4197062wey.20 for ; Sun, 03 Feb 2013 06:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=KNYF0G6o/GA6mNrvtNkA7VWTWIKtR0GzIfrxA8MdkoA=; b=n+uzD1zEYgkz4Rs5cSgf0TTrgy4ehZB2nx+JxtICWpw40f8YCEULmHHKGZmD71RLdl UOS4nYSoz1AVIm609F0ThuVV5ENUqcnLuk0FoV79uFDolGcTymexzl0uswPXDi0GKdRA S1O5qoEbHr83BCLTZ6p4WMuHnHKM26VoawTHb4kRZ84SAGKB26AvN62cMT9FrTdWiaMT cQz5wlLPYKsdzHIPE+PTeEy5zRdxW/0dZWHfkNlyDT9MeDgQ0h12fX+zlU09yK1CAQEq tjjFImWMox2xjmCY+EEKkQ3UfT0pt5WCFW8l/bAsyKO9lqC785aWexSoRCDF8pJBzj7T EchA== MIME-Version: 1.0 X-Received: by 10.180.93.40 with SMTP id cr8mr6077619wib.15.1359903540801; Sun, 03 Feb 2013 06:59:00 -0800 (PST) Received: by 10.216.172.197 with HTTP; Sun, 3 Feb 2013 06:59:00 -0800 (PST) In-Reply-To: References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> <20130203020613.GB3441@lonesome.com> Date: Sun, 3 Feb 2013 16:59:00 +0200 Message-ID: Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 From: Kimmo Paasiala To: Chris Rees Content-Type: text/plain; charset=UTF-8 Cc: Mark Linimon , Brooks Davis , Dimitry Andric , FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 14:59:03 -0000 On Sun, Feb 3, 2013 at 11:57 AM, Chris Rees wrote: > On 3 February 2013 03:55, Kimmo Paasiala wrote: >> On Sun, Feb 3, 2013 at 4:06 AM, Mark Linimon wrote: >>> On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: >>>> I'm not sure why I'm being jumped on in this weeks old report of a >>>> now-fixed problem. >>> >>> I'm sorry, I'm that far behind in email. I did not realize the problem >>> had already been solved. >>> >>> More often than not the problem is simply "thrown over the fence" for >>> the ports team to deal with. >>> >>> mcl >> >> There is no PR yet with my fix and therefor no commit to ports tree >> that would fix the problem. I'll file a PR soon (TM). > > The problem was in base, and is fixed there. > > Chris I missed that fix if it was posted here, can someone point me to the commit that fixed the issue? -Kimmo From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 17:01:32 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 20FC9373; Sun, 3 Feb 2013 17:01:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2CA81DC; Sun, 3 Feb 2013 17:01:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA09311; Sun, 03 Feb 2013 19:01:20 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U22wR-0006ke-II; Sun, 03 Feb 2013 19:01:19 +0200 Message-ID: <510E97DC.2010701@FreeBSD.org> Date: Sun, 03 Feb 2013 19:01:16 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: Hiroki Sato Subject: Re: NFS-exported ZFS instability References: <1914428061.1617223.1357133079421.JavaMail.root@erie.cs.uoguelph.ca> <20130102174044.GB82219@kib.kiev.ua> <20130104.023244.472910818423317661.hrs@allbsd.org> <20130130.064459.2572086065267072.hrs@allbsd.org> <510850D1.3090700@FreeBSD.org> In-Reply-To: <510850D1.3090700@FreeBSD.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kostikbel@gmail.com, alc@FreeBSD.org, stable@FreeBSD.org, rmacklem@uoguelph.ca X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:01:32 -0000 on 30/01/2013 00:44 Andriy Gapon said the following: > on 29/01/2013 23:44 Hiroki Sato said the following: >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt > [snip] > See tid 100153 (arc reclaim thread), tid 100105 (pagedaemon) and tid 100639 > (nfsd in kmem_back). > I decided to write a few more words about this issue. I think that the root cause of the problem is that ZFS ARC code performs memory allocations with M_WAITOK while holding some ARC lock(s). If a thread runs into such an allocation when a system is very low on memory (even for a very short period of time), then the thread is going to be blocked (to sleep in more exact terms) in VM_WAIT until a certain amount of memory is freed. To be more precise until v_free_count + v_cache_count goes above v_free_min. And quoting from the report: db> show page cnt.v_free_count: 8842 cnt.v_cache_count: 0 cnt.v_inactive_count: 0 cnt.v_active_count: 169 cnt.v_wire_count: 6081952 cnt.v_free_reserved: 7981 cnt.v_free_min: 38435 cnt.v_free_target: 161721 cnt.v_cache_min: 161721 cnt.v_inactive_target: 242581 In this case tid 100639 is the thread: Tracing command nfsd pid 961 tid 100639 td 0xfffffe0027038920 sched_switch() at sched_switch+0x17a/frame 0xffffff86ca5c9c80 mi_switch() at mi_switch+0x1f8/frame 0xffffff86ca5c9cd0 sleepq_switch() at sleepq_switch+0x123/frame 0xffffff86ca5c9d00 sleepq_wait() at sleepq_wait+0x4d/frame 0xffffff86ca5c9d30 _sleep() at _sleep+0x3d4/frame 0xffffff86ca5c9dc0 kmem_back() at kmem_back+0x1a3/frame 0xffffff86ca5c9e50 kmem_malloc() at kmem_malloc+0x1f8/frame 0xffffff86ca5c9ea0 uma_large_malloc() at uma_large_malloc+0x4a/frame 0xffffff86ca5c9ee0 malloc() at malloc+0x14d/frame 0xffffff86ca5c9f20 arc_get_data_buf() at arc_get_data_buf+0x1f4/frame 0xffffff86ca5c9f60 arc_read_nolock() at arc_read_nolock+0x208/frame 0xffffff86ca5ca010 arc_read() at arc_read+0x93/frame 0xffffff86ca5ca090 dbuf_read() at dbuf_read+0x452/frame 0xffffff86ca5ca150 dmu_buf_hold_array_by_dnode() at dmu_buf_hold_array_by_dnode+0x16a/frame 0xffffff86ca5ca1e0 dmu_buf_hold_array() at dmu_buf_hold_array+0x67/frame 0xffffff86ca5ca240 dmu_read_uio() at dmu_read_uio+0x3f/frame 0xffffff86ca5ca2a0 zfs_freebsd_read() at zfs_freebsd_read+0x3e9/frame 0xffffff86ca5ca3b0 nfsvno_read() at nfsvno_read+0x2db/frame 0xffffff86ca5ca490 nfsrvd_read() at nfsrvd_read+0x3ff/frame 0xffffff86ca5ca710 nfsrvd_dorpc() at nfsrvd_dorpc+0xc9/frame 0xffffff86ca5ca910 nfssvc_program() at nfssvc_program+0x5da/frame 0xffffff86ca5caaa0 svc_run_internal() at svc_run_internal+0x5fb/frame 0xffffff86ca5cabd0 svc_thread_start() at svc_thread_start+0xb/frame 0xffffff86ca5cabe0 Sleeping in VM_WAIT while holding the ARC lock(s) means that other ARC operations may get blocked. And pretty much all ZFS I/O goes through the ARC. So that's why we see all those stuck nfsd threads. Another factor greatly contributing to the problem is that currently the page daemon blocks (sleeps) in arc_lowmem (a vm_lowmem hook) waiting for the ARC reclaim thread to make a pass. This happens before the page daemon makes its own pageout pass. But because tid 100639 holds the ARC lock(s), ARC reclaim thread gets blocked and can not make any forward progress. Thus the page daemon also gets blocked. And thus the page daemon can not free up any pages. So, this situation is not a true deadlock. E.g. it is theoretically possible that some other threads would free some memory at their own will and the condition would clear up. But in practice this is highly unlikely. Some possible resolutions that I can think of. The best one is probably doing ARC memory allocations without holding any locks. Also, maybe we should make a rule that no vm_lowmem hooks should sleep. That is, arc_lowmem should signal the ARC reclaim thread to do some work, but should not wait on it. Perhaps we could also provide a mechanism to mark certain memory allocations as "special" and use that mechanism for ARC allocations. So that VM_WAIT unblocks sooner: in this case we had 8842 free pages (~35MB), but thread 100639 was not waken up. I think that ideally we should do something about all the three directions. But even one of them might turn out to be sufficient. As I've said, the first one seems to be the most promising, but it would require some tricky programming (flags and retries?) to move memory allocations out of locked sections. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 17:15:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 081C3777; Sun, 3 Feb 2013 17:15:27 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [212.12.50.234]) by mx1.freebsd.org (Postfix) with ESMTP id ADF08181; Sun, 3 Feb 2013 17:15:26 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id A823011E69A; Sun, 3 Feb 2013 17:15:24 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 From: Stefan Bethke In-Reply-To: Date: Sun, 3 Feb 2013 18:15:23 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <25440DC0-FCDE-45DC-9CBE-B44DC7646C6F@lassitu.de> References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> <20130203020613.GB3441@lonesome.com> To: Chris Rees X-Mailer: Apple Mail (2.1499) Cc: Kimmo Paasiala , Brooks Davis , Dimitry Andric , FreeBSD , Mark Linimon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:15:27 -0000 Am 03.02.2013 um 10:57 schrieb Chris Rees : > On 3 February 2013 03:55, Kimmo Paasiala wrote: >>=20 >> There is no PR yet with my fix and therefor no commit to ports tree >> that would fix the problem. I'll file a PR soon (TM). >=20 > The problem was in base, and is fixed there. Huh? With -current r246283, I still get a segfault from sudo unless I = have Kimmo's patch. Is there some confusion about which problem is addressed by Kimmo's = patch? Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 17:22:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 24BF7CD2; Sun, 3 Feb 2013 17:22:56 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ia0-x22b.google.com (mail-ia0-x22b.google.com [IPv6:2607:f8b0:4001:c02::22b]) by mx1.freebsd.org (Postfix) with ESMTP id BCC9D1DC; Sun, 3 Feb 2013 17:22:55 +0000 (UTC) Received: by mail-ia0-f171.google.com with SMTP id z13so7268124iaz.16 for ; Sun, 03 Feb 2013 09:22:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=zshPORSaHC9DSBzrVoT1so1ueWWIf38jblXNl+wbUY4=; b=DvbjDOJbT6n+FJHDUHlVxxoTfwMcJc4BGOl85MJngLQDaZlPWpqnmrWhS1EW5vtJ6i bE4fXKoGsqKyX1fdCOQrgNQogAeQ8DxFSQNC68hBB3M1k5srqSbA1FGtH7u8bGFzkgll D+XrfXS3SqqxK9Pdm9batytXQJEKQxN1qlKhAsw1HF/BlxH5gvdOrIIO38fstNE8fiAv 1at/kr8KrtelmrkBNELJ+0Ycgm4vfPoqz9f/h16yrX0eGp2ws4hrqsZPSSWfMSR3b/PP aLaRBQ2soFQm2atjsVU54pMszXTk0C2FThQBL7KQjMSJzAlLcXQq7cSX9VqnXpOyG30g lpEg== X-Received: by 10.50.161.169 with SMTP id xt9mr3183360igb.62.1359912175120; Sun, 03 Feb 2013 09:22:55 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.64.16.73 with HTTP; Sun, 3 Feb 2013 09:22:24 -0800 (PST) In-Reply-To: <25440DC0-FCDE-45DC-9CBE-B44DC7646C6F@lassitu.de> References: <50F6D20A.6070306@FreeBSD.org> <20130117151502.GF29437@lor.one-eyed-alien.net> <20130201042244.GC20772@lonesome.com> <20130201175303.GA5914@lor.one-eyed-alien.net> <20130203020613.GB3441@lonesome.com> <25440DC0-FCDE-45DC-9CBE-B44DC7646C6F@lassitu.de> From: Chris Rees Date: Sun, 3 Feb 2013 17:22:24 +0000 X-Google-Sender-Auth: YAnGR6KdAPSUu5eXl31H9JRTkk8 Message-ID: Subject: Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9 To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 Cc: Kimmo Paasiala , Brooks Davis , Dimitry Andric , FreeBSD , Mark Linimon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:22:56 -0000 On 3 February 2013 17:15, Stefan Bethke wrote: > > Am 03.02.2013 um 10:57 schrieb Chris Rees : > >> On 3 February 2013 03:55, Kimmo Paasiala wrote: >>> >>> There is no PR yet with my fix and therefor no commit to ports tree >>> that would fix the problem. I'll file a PR soon (TM). >> >> The problem was in base, and is fixed there. > > Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. > > Is there some confusion about which problem is addressed by Kimmo's patch? > Hm, perhaps it might be necessary then. Kimmo, please would you submit the patch you had as a PR? I'm sure Wesley would appreciate the hint. Chris From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 00:48:44 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EFDC8D49; Mon, 4 Feb 2013 00:48:43 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 553A01CD; Mon, 4 Feb 2013 00:48:42 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEALcED1GDaFvO/2dsb2JhbAA8CBaGMrkCc4IfAQEBBAEBASArIAsbDgoCAg0ZAikBCSYGCAcEARwEh3AMrR6RVIEjjAMEgxWBEwOIZosHgjKBHY80gxqBUTU X-IronPort-AV: E=Sophos;i="4.84,596,1355115600"; d="scan'208";a="12246802" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 03 Feb 2013 19:48:41 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 72A15B3F2B; Sun, 3 Feb 2013 19:48:41 -0500 (EST) Date: Sun, 3 Feb 2013 19:48:41 -0500 (EST) From: Rick Macklem To: Andriy Gapon Message-ID: <2084936125.2640101.1359938921410.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <510E97DC.2010701@FreeBSD.org> Subject: Re: NFS-exported ZFS instability MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: kostikbel@gmail.com, alc@FreeBSD.org, stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 00:48:44 -0000 Andriy Gapon wrote: > on 30/01/2013 00:44 Andriy Gapon said the following: > > on 29/01/2013 23:44 Hiroki Sato said the following: > >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt > >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt > > > [snip] > > See tid 100153 (arc reclaim thread), tid 100105 (pagedaemon) and tid > > 100639 > > (nfsd in kmem_back). > > > > I decided to write a few more words about this issue. > > I think that the root cause of the problem is that ZFS ARC code > performs memory > allocations with M_WAITOK while holding some ARC lock(s). > > If a thread runs into such an allocation when a system is very low on > memory > (even for a very short period of time), then the thread is going to be > blocked > (to sleep in more exact terms) in VM_WAIT until a certain amount of > memory is > freed. To be more precise until v_free_count + v_cache_count goes > above v_free_min. > And quoting from the report: > db> show page > cnt.v_free_count: 8842 > cnt.v_cache_count: 0 > cnt.v_inactive_count: 0 > cnt.v_active_count: 169 > cnt.v_wire_count: 6081952 > cnt.v_free_reserved: 7981 > cnt.v_free_min: 38435 > cnt.v_free_target: 161721 > cnt.v_cache_min: 161721 > cnt.v_inactive_target: 242581 > > In this case tid 100639 is the thread: > Tracing command nfsd pid 961 tid 100639 td 0xfffffe0027038920 > sched_switch() at sched_switch+0x17a/frame 0xffffff86ca5c9c80 > mi_switch() at mi_switch+0x1f8/frame 0xffffff86ca5c9cd0 > sleepq_switch() at sleepq_switch+0x123/frame 0xffffff86ca5c9d00 > sleepq_wait() at sleepq_wait+0x4d/frame 0xffffff86ca5c9d30 > _sleep() at _sleep+0x3d4/frame 0xffffff86ca5c9dc0 > kmem_back() at kmem_back+0x1a3/frame 0xffffff86ca5c9e50 > kmem_malloc() at kmem_malloc+0x1f8/frame 0xffffff86ca5c9ea0 > uma_large_malloc() at uma_large_malloc+0x4a/frame 0xffffff86ca5c9ee0 > malloc() at malloc+0x14d/frame 0xffffff86ca5c9f20 > arc_get_data_buf() at arc_get_data_buf+0x1f4/frame 0xffffff86ca5c9f60 > arc_read_nolock() at arc_read_nolock+0x208/frame 0xffffff86ca5ca010 > arc_read() at arc_read+0x93/frame 0xffffff86ca5ca090 > dbuf_read() at dbuf_read+0x452/frame 0xffffff86ca5ca150 > dmu_buf_hold_array_by_dnode() at > dmu_buf_hold_array_by_dnode+0x16a/frame > 0xffffff86ca5ca1e0 > dmu_buf_hold_array() at dmu_buf_hold_array+0x67/frame > 0xffffff86ca5ca240 > dmu_read_uio() at dmu_read_uio+0x3f/frame 0xffffff86ca5ca2a0 > zfs_freebsd_read() at zfs_freebsd_read+0x3e9/frame 0xffffff86ca5ca3b0 > nfsvno_read() at nfsvno_read+0x2db/frame 0xffffff86ca5ca490 > nfsrvd_read() at nfsrvd_read+0x3ff/frame 0xffffff86ca5ca710 > nfsrvd_dorpc() at nfsrvd_dorpc+0xc9/frame 0xffffff86ca5ca910 > nfssvc_program() at nfssvc_program+0x5da/frame 0xffffff86ca5caaa0 > svc_run_internal() at svc_run_internal+0x5fb/frame 0xffffff86ca5cabd0 > svc_thread_start() at svc_thread_start+0xb/frame 0xffffff86ca5cabe0 > > Sleeping in VM_WAIT while holding the ARC lock(s) means that other ARC > operations may get blocked. And pretty much all ZFS I/O goes through > the ARC. > So that's why we see all those stuck nfsd threads. > > Another factor greatly contributing to the problem is that currently > the page > daemon blocks (sleeps) in arc_lowmem (a vm_lowmem hook) waiting for > the ARC > reclaim thread to make a pass. This happens before the page daemon > makes its > own pageout pass. > > But because tid 100639 holds the ARC lock(s), ARC reclaim thread gets > blocked > and can not make any forward progress. Thus the page daemon also gets > blocked. > And thus the page daemon can not free up any pages. > > > So, this situation is not a true deadlock. E.g. it is theoretically > possible > that some other threads would free some memory at their own will and > the > condition would clear up. But in practice this is highly unlikely. > > Some possible resolutions that I can think of. > > The best one is probably doing ARC memory allocations without holding > any locks. > > Also, maybe we should make a rule that no vm_lowmem hooks should > sleep. That > is, arc_lowmem should signal the ARC reclaim thread to do some work, > but should > not wait on it. > > Perhaps we could also provide a mechanism to mark certain memory > allocations as > "special" and use that mechanism for ARC allocations. So that VM_WAIT > unblocks > sooner: in this case we had 8842 free pages (~35MB), but thread 100639 > was not > waken up. > > I think that ideally we should do something about all the three > directions. > But even one of them might turn out to be sufficient. > As I've said, the first one seems to be the most promising, but it > would require > some tricky programming (flags and retries?) to move memory > allocations out of > locked sections. For the NFSv4 stuff, I pre-allocate any structures that I might need using malloc(..M_WAITOK) before going into the locked region. If I don't need them, I just free() them at the end. (I assign "newp" the allocation and set "newp" NULL if it is used. If "newp" != NULL at the end, then free(newp..);) This avoids all the "go back and retry after doing an allocation" complexity. (One of the big names, maybe Dykstra, had a name for this approach, but I can't remember.;-) It won't work for cases where the locked region needs K allocations, where K varies and has no fixed upper bound (malloc() in a loop of no fixed number of iterations). Thought I'd mention it, just in case the technique would be useful in this case. (I have no idea what this code looks like;-) Good luck with it, rick > -- > Andriy Gapon > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 13:40:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A670C717; Mon, 4 Feb 2013 13:40:50 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by mx1.freebsd.org (Postfix) with ESMTP id C51C11C6E; Mon, 4 Feb 2013 13:40:49 +0000 (UTC) Received: by mail-lb0-f172.google.com with SMTP id n8so6668833lbj.3 for ; Mon, 04 Feb 2013 05:40:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tC3/LOflLMm4Olt3zhHzNabqtJr1BaK5kFbWjVP9u4k=; b=gk4fdGHPZuBI3laLtNO8taDe+bp6tIIfCEnwBD0Yl1IAkLrxtf6pAEYP9Ruv6oartn Mx1Q7i/z9eJTSgNtlUW5vUZNDbPYeYfQcmLGEkhPDvfU0X6WkECKpAkT7fk1qbcd0EIz vK2caC5cLRsy1nygoj4ACM2duDe4x+S+p1zTBnJbm9gzEwtoiSMWIT9AQ+XMd9enGWKP 5Putn5pqhp+Sn6TFhJXZypsLbzLcK7o9QD1jL1JQtfxnrBFo9IRRB7Gjd9eMHUmv3xWi qRGT3pxp+DXS2/3WyXePsHyXte0bgX0VZK4c2yOAcvHjRfjhpzYkUi14BiQMSUEGauu1 Of8g== X-Received: by 10.152.105.38 with SMTP id gj6mr19176344lab.25.1359985242466; Mon, 04 Feb 2013 05:40:42 -0800 (PST) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id h6sm2341948lbm.3.2013.02.04.05.40.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Feb 2013 05:40:40 -0800 (PST) Message-ID: <510FBA51.9090806@gmail.com> Date: Mon, 04 Feb 2013 15:40:33 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: Ports and WITH_LIBCPLUSPLUS References: <510E65FA.4040900@FreeBSD.org> In-Reply-To: <510E65FA.4040900@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List , Andreas Nilsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 13:40:50 -0000 03.02.2013 15:28, Dimitry Andric: > Thanks for trying this out. Is there also a list of ports that *do* > compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS Currently I have working seamonkey and slim built this way. > ldd `which seamonkey` /usr/local/bin/seamonkey: libm.so.5 => /lib/libm.so.5 (0x800846000) libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x800a65000) libc++.so.1 => /usr/lib/libc++.so.1 (0x800c7e000) libthr.so.3 => /lib/libthr.so.3 (0x800f34000) libc.so.7 => /lib/libc.so.7 (0x801156000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x8014a5000) I can post whole list of packages if anyone is interested. Everything looks even better then when clang was introduced to ports - almost any package works, the ones that doesn't just have a complicated build/install process. No painful glitches yet. -- Sphinx of black quartz, judge my vow. From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 17:40:15 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 292BE303; Mon, 4 Feb 2013 17:40:15 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id A6B49E0D; Mon, 4 Feb 2013 17:40:14 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r14He48D005878; Mon, 4 Feb 2013 18:40:06 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r14He4fM005877; Mon, 4 Feb 2013 18:40:04 +0100 (CET) (envelope-from olli) Date: Mon, 4 Feb 2013 18:40:04 +0100 (CET) Message-Id: <201302041740.r14He4fM005877@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, Ian Lepore Subject: Re: stable/9: Force ada1 to UDMA-33 In-Reply-To: <1359746407.93359.346.camel@revolution.hippie.lan> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 17:40:15 -0000 Ian Lepore wrote: > On Fri, 2013-02-01 at 19:52 +0100, Oliver Fromme wrote: > > What is the proper way with ATA_CAM and ada(4) to force a > > P-ATA disk to a lower UDMA mode? > > You probably want one of these... > > hint.ata.X.devX.mode > limits initial ATA mode for specified device on specified channel. > > hint.ata.X.mode > limits initial ATA mode for every device on specified channel. > > These are from ata(4) manpage, there are some others there as well. Thank you! It's embarassing I didn't check ata(4) ... I looked at ada(4), atacontrol, camcontrol and a few others, even Google didn't reveal anything. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "C++ is to C as Lung Cancer is to Lung." -- Thomas Funke From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 18:16:01 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 43637D89 for ; Mon, 4 Feb 2013 18:16:01 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id D2530128 for ; Mon, 4 Feb 2013 18:16:00 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r14IFpHV007606; Mon, 4 Feb 2013 19:15:59 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r14IFpD5007605; Mon, 4 Feb 2013 19:15:51 +0100 (CET) (envelope-from olli) Date: Mon, 4 Feb 2013 19:15:51 +0100 (CET) Message-Id: <201302041815.r14IFpD5007605@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Subject: re(4) problems with GA-H77N-WIFI X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 18:16:01 -0000 Hello, I need some advice how to debug this issue ... Recently I got a new mainboard for a router, it's a Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. The problem is that re0 works fine and re1 doesn't: It doesn't receive any packets. Tcpdump displays all outgoing packets, but no incoming ones on re1. Ifconfig shows the link correctly (100 or 1000 Mbit, depending on where I plug the cable in). I also swapped cables just to be sure, but it made no difference. I'm running a recent stable/9 (about 14 days old). What's the best way to debug this problem? At the moment I'm not even sure if it's the hardware, or if it's FreeBSD's fault (or my fault) ... Best regards Oliver PS: dmesg ... pcib2: irq 16 at device 28.4 on pci0 pci2: on pcib2 re0: port 0xe000-0xe0ff mem 0xf0104000-0xf0104fff,0xf0100000-0xf0103fff irq 16 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c800000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 90:2b:34:5f:bd:21 pcib3: irq 17 at device 28.5 on pci0 pci3: on pcib3 re1: port 0xd000-0xd0ff mem 0xf0004000-0xf0004fff,0xf0000000-0xf0003fff irq 17 at device 0.0 on pci3 re1: Using 1 MSI-X message re1: Chip rev. 0x2c800000 re1: MAC rev. 0x00000000 miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re1: Ethernet address: 90:2b:34:5f:bd:11 ifconfig ... re0: flags=8843 metric 0 mtu 1500 options=8209b ether 90:2b:34:5f:bd:21 inet ... nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active re1: flags=8843 metric 0 mtu 1500 options=8209b ether 90:2b:34:5f:bd:11 inet ... nd6 options=21 media: Ethernet autoselect (100baseTX ) status: active -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible." -- John William Chambless From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 18:19:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5B0C9FFE for ; Mon, 4 Feb 2013 18:19:13 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 1F712166 for ; Mon, 4 Feb 2013 18:19:12 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r14IJ6lf035929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Feb 2013 10:19:06 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r14IJ6r6035928; Mon, 4 Feb 2013 10:19:06 -0800 (PST) (envelope-from jmg) Date: Mon, 4 Feb 2013 10:19:05 -0800 From: John-Mark Gurney To: Oliver Fromme Subject: Re: re(4) problems with GA-H77N-WIFI Message-ID: <20130204181905.GT1410@funkthat.com> Mail-Followup-To: Oliver Fromme , freebsd-stable@freebsd.org References: <201302041815.r14IFpD5007605@grabthar.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302041815.r14IFpD5007605@grabthar.secnetix.de> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 04 Feb 2013 10:19:06 -0800 (PST) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 18:19:13 -0000 Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: > I'm running a recent stable/9 (about 14 days old). > What's the best way to debug this problem? At the > moment I'm not even sure if it's the hardware, or if > it's FreeBSD's fault (or my fault) ... Have you tried to disable msi and msix? hw.pci.enable_msix: 1 hw.pci.enable_msi: 1 It could be your motherboard doesn't handle MSI and/or MSI-X properly... [...] > re0: Using 1 MSI-X message [...] > re1: Using 1 MSI-X message -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 19:01:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D8C47404 for ; Mon, 4 Feb 2013 19:01:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 833946B1 for ; Mon, 4 Feb 2013 19:01:05 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r14IvqZN049614 for ; Mon, 4 Feb 2013 12:57:52 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 12:57:52 2013 Message-ID: <511004AA.3060201@denninger.net> Date: Mon, 04 Feb 2013 12:57:46 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: So I whip out a FTDI-based multiport Serial USB Adapter.... X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-0, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 19:01:05 -0000 ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD 9.1-STABLE #16 r244942 and it returns.... ugen4.4: at usbus4 uhub6: on usbus4 uhub_attach: port 1 power on failed, USB_ERR_STALLED uhub_attach: port 2 power on failed, USB_ERR_STALLED uhub_attach: port 3 power on failed, USB_ERR_STALLED uhub_attach: port 4 power on failed, USB_ERR_STALLED uhub_attach: port 5 power on failed, USB_ERR_STALLED uhub_attach: port 6 power on failed, USB_ERR_STALLED uhub_attach: port 7 power on failed, USB_ERR_STALLED uhub6: 7 ports with 7 removable, self powered Yuck. The last time it was working was on a FreeBSD 7 box (yeah, I know, rather old) but I never had problems there. And it appears that all of the device declarations that I used to have to put in the kernel as non-standard stuff are now in GENERIC, so I would expect it to work. Ideas as to what may have gotten hosed up here? -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 20:06:08 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 26A375AE for ; Mon, 4 Feb 2013 20:06:08 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 8B8DDA0C for ; Mon, 4 Feb 2013 20:06:07 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14K66SE089168 for ; Mon, 4 Feb 2013 13:06:06 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14K62BZ029745; Mon, 4 Feb 2013 13:06:02 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: Karl Denninger In-Reply-To: <511004AA.3060201@denninger.net> References: <511004AA.3060201@denninger.net> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Feb 2013 13:06:02 -0700 Message-ID: <1360008362.93359.485.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 20:06:08 -0000 On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: > ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD > 9.1-STABLE #16 r244942 > > and it returns.... > > ugen4.4: at usbus4 > uhub6: > on usbus4 > uhub_attach: port 1 power on failed, USB_ERR_STALLED > uhub_attach: port 2 power on failed, USB_ERR_STALLED > uhub_attach: port 3 power on failed, USB_ERR_STALLED > uhub_attach: port 4 power on failed, USB_ERR_STALLED > uhub_attach: port 5 power on failed, USB_ERR_STALLED > uhub_attach: port 6 power on failed, USB_ERR_STALLED > uhub_attach: port 7 power on failed, USB_ERR_STALLED > uhub6: 7 ports with 7 removable, self powered > > Yuck. > > The last time it was working was on a FreeBSD 7 box (yeah, I know, > rather old) but I never had problems there. And it appears that all of > the device declarations that I used to have to put in the kernel as > non-standard stuff are now in GENERIC, so I would expect it to work. > > Ideas as to what may have gotten hosed up here? > Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's parts program different vendor/product info and IDs have to be added to code to recognize them, that's the only trouble one usually encounters. -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 20:13:45 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7A6F78D8 for ; Mon, 4 Feb 2013 20:13:45 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 0FEF3A8E for ; Mon, 4 Feb 2013 20:13:44 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r14KDi9H020530 for ; Mon, 4 Feb 2013 14:13:44 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 14:13:44 2013 Message-ID: <51101673.8050800@denninger.net> Date: Mon, 04 Feb 2013 14:13:39 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> In-Reply-To: <1360008362.93359.485.camel@revolution.hippie.lan> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-0, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 20:13:45 -0000 On 2/4/2013 2:06 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >> 9.1-STABLE #16 r244942 >> >> and it returns.... >> >> ugen4.4: at usbus4 >> uhub6: >> on usbus4 >> uhub_attach: port 1 power on failed, USB_ERR_STALLED >> uhub_attach: port 2 power on failed, USB_ERR_STALLED >> uhub_attach: port 3 power on failed, USB_ERR_STALLED >> uhub_attach: port 4 power on failed, USB_ERR_STALLED >> uhub_attach: port 5 power on failed, USB_ERR_STALLED >> uhub_attach: port 6 power on failed, USB_ERR_STALLED >> uhub_attach: port 7 power on failed, USB_ERR_STALLED >> uhub6: 7 ports with 7 removable, self powered >> >> Yuck. >> >> The last time it was working was on a FreeBSD 7 box (yeah, I know, >> rather old) but I never had problems there. And it appears that all of >> the device declarations that I used to have to put in the kernel as >> non-standard stuff are now in GENERIC, so I would expect it to work. >> >> Ideas as to what may have gotten hosed up here? >> > Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > parts program different vendor/product info and IDs have to be added to > code to recognize them, that's the only trouble one usually encounters. > > -- Ian It appears there is no declaration in any of the NEC constants in any of the source or header files (other than usbdevs) in the /usr/src/sys/dev/usb tree, so I'm unsure where it's getting the "7" ports it is trying to attach, since there are 8 in the box and I can't find a use of the tuple that it IDs under from the usbdevs declarations..... Am I correct that if I was to add this pair to the serial/uftdi.c file where the structure is set up it should (might?) recognize it? There's no way to do this on a runtime basis, yes? -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 20:58:08 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EFA28DF6 for ; Mon, 4 Feb 2013 20:58:08 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id A1383E41 for ; Mon, 4 Feb 2013 20:58:08 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r14Kw8DQ010049 for ; Mon, 4 Feb 2013 14:58:08 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 14:58:08 2013 Message-ID: <511020DB.3050302@denninger.net> Date: Mon, 04 Feb 2013 14:58:03 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> In-Reply-To: <1360008362.93359.485.camel@revolution.hippie.lan> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-0, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 20:58:09 -0000 On 2/4/2013 2:06 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >> 9.1-STABLE #16 r244942 >> >> and it returns.... >> >> ugen4.4: at usbus4 >> uhub6: >> on usbus4 >> uhub_attach: port 1 power on failed, USB_ERR_STALLED >> uhub_attach: port 2 power on failed, USB_ERR_STALLED >> uhub_attach: port 3 power on failed, USB_ERR_STALLED >> uhub_attach: port 4 power on failed, USB_ERR_STALLED >> uhub_attach: port 5 power on failed, USB_ERR_STALLED >> uhub_attach: port 6 power on failed, USB_ERR_STALLED >> uhub_attach: port 7 power on failed, USB_ERR_STALLED >> uhub6: 7 ports with 7 removable, self powered >> >> Yuck. >> >> The last time it was working was on a FreeBSD 7 box (yeah, I know, >> rather old) but I never had problems there. And it appears that all of >> the device declarations that I used to have to put in the kernel as >> non-standard stuff are now in GENERIC, so I would expect it to work. >> >> Ideas as to what may have gotten hosed up here? >> > Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > parts program different vendor/product info and IDs have to be added to > code to recognize them, that's the only trouble one usually encounters. > > -- Ian Well, that sorta kinda worked. Except that it still is identifying it as a hub too, and the two collide and crash the stack. But I can't find anything that is looking at the PID (0x0050) or the definition (HUB_0050) anywhere in the code. I'll go pull the NEC defs and set up something else instead of simply adding it to the FTDI probe list. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:05:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D96C6399; Mon, 4 Feb 2013 21:05:38 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7D8D1EF0; Mon, 4 Feb 2013 21:05:38 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id a11so3091410qen.31 for ; Mon, 04 Feb 2013 13:05:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ki3Kppgx5wGf4B31+7rRzs6cF3QVBN23R1r/aeSo3K4=; b=iMAwvd+jKGwqrlhTOrVFQmG240T8UrbFvuFPJni9uCX690XQl/6I33JTJXbqXeKpFe eP3Gb/P/2qfCCBwUw8Au4OCL2EWxjkggHyTQTkIk6riVD1H+FGvIOK7F5JOLHZwK9WP6 0Oyglda74LIyCaks7dANQ+ZXckg/BRBau+BGyYpFy1D+534P522/HImi5dlasezHCOK+ dZj8InjFfElhv/fYBLRlj5TdnnjydBKjC6Y+VKfxAyzYtcQCez0oMbDl0GohUv96pP1N 5geLNMLPk9zpWDCOd8U+38hp0qLC/IPY6Drg0eV7M3DC3siAVPsuK41q+3j/YP81L/VK PqeA== MIME-Version: 1.0 X-Received: by 10.49.14.202 with SMTP id r10mr22198554qec.10.1360011931984; Mon, 04 Feb 2013 13:05:31 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Mon, 4 Feb 2013 13:05:31 -0800 (PST) In-Reply-To: <1360008362.93359.485.camel@revolution.hippie.lan> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> Date: Mon, 4 Feb 2013 22:05:31 +0100 X-Google-Sender-Auth: 3u0mIyOv3V0ON1rzw9lgOWX6fZg Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: CeDeROM To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org, Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:05:38 -0000 On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore wrote: > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > parts program different vendor/product info and IDs have to be added to > code to recognize them, that's the only trouble one usually encounters. I also want to use my KT-LINK multipurpose low-level embedded access multitool based on FT2232H with RS232 port and I was worried there is no driver - right now I will add the PID and recompile sources to see if it works - happy to catch this thread :-) Some questions as you Ian seem to already have experience with this devices: 1. Is it possible to compile only uftdi driver and load it into existing kernel that have this driver compiled-in so I don't have to recompile whole kernel and all of the modules? 2. Is it possible to pass VID/PID and/or RS232 channel as kernel loadable option? This would again spare some build/runtime time for me :-) 3. Do you know a good method on kernel module testing other than rebuilding/rebooting all the time? VirtualBox + USB Attach? Any hints appreciated! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:13:12 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C7673892 for ; Mon, 4 Feb 2013 21:13:12 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 47F73F85 for ; Mon, 4 Feb 2013 21:13:12 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14LD5SJ089939 for ; Mon, 4 Feb 2013 14:13:05 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14LD2jI029813; Mon, 4 Feb 2013 14:13:02 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: Karl Denninger In-Reply-To: <511020DB.3050302@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Feb 2013 14:13:02 -0700 Message-ID: <1360012382.93359.489.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:13:12 -0000 On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: > On 2/4/2013 2:06 PM, Ian Lepore wrote: > > On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: > >> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD > >> 9.1-STABLE #16 r244942 > >> > >> and it returns.... > >> > >> ugen4.4: at usbus4 > >> uhub6: > >> on usbus4 > >> uhub_attach: port 1 power on failed, USB_ERR_STALLED > >> uhub_attach: port 2 power on failed, USB_ERR_STALLED > >> uhub_attach: port 3 power on failed, USB_ERR_STALLED > >> uhub_attach: port 4 power on failed, USB_ERR_STALLED > >> uhub_attach: port 5 power on failed, USB_ERR_STALLED > >> uhub_attach: port 6 power on failed, USB_ERR_STALLED > >> uhub_attach: port 7 power on failed, USB_ERR_STALLED > >> uhub6: 7 ports with 7 removable, self powered > >> > >> Yuck. > >> > >> The last time it was working was on a FreeBSD 7 box (yeah, I know, > >> rather old) but I never had problems there. And it appears that all of > >> the device declarations that I used to have to put in the kernel as > >> non-standard stuff are now in GENERIC, so I would expect it to work. > >> > >> Ideas as to what may have gotten hosed up here? > >> > > Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. > > > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > > parts program different vendor/product info and IDs have to be added to > > code to recognize them, that's the only trouble one usually encounters. > > > > -- Ian > Well, that sorta kinda worked. > > Except that it still is identifying it as a hub too, and the two collide > and crash the stack. > > But I can't find anything that is looking at the PID (0x0050) or the > definition (HUB_0050) anywhere in the code. > > I'll go pull the NEC defs and set up something else instead of simply > adding it to the FTDI probe list. > It seems to me you have a problem with a hub (perhaps the root hub or a motherboard hub if you don't have an external one) and this has nothing to do with the ftdi device at all. Or the usb serial device is damaged somehow so that the vendor and product ID are reading as garbage and being mistaken for a hub. Have you tried the ftdi adapter on another port/hub/computer? Have you tried plugging something else into the port you're trying to use for the ftdi adapter, like a thumb drive or something? -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:15:09 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5A31BA90 for ; Mon, 4 Feb 2013 21:15:09 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 2BFD3FB4 for ; Mon, 4 Feb 2013 21:15:05 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14LF4mx089972 for ; Mon, 4 Feb 2013 14:15:04 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14LF2kh029826; Mon, 4 Feb 2013 14:15:02 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: CeDeROM In-Reply-To: References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Feb 2013 14:15:02 -0700 Message-ID: <1360012502.93359.491.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:15:09 -0000 On Mon, 2013-02-04 at 22:05 +0100, CeDeROM wrote: > On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore wrote: > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > > parts program different vendor/product info and IDs have to be added to > > code to recognize them, that's the only trouble one usually encounters. > > I also want to use my KT-LINK multipurpose low-level embedded access > multitool based on FT2232H with RS232 port and I was worried there is > no driver - right now I will add the PID and recompile sources to see > if it works - happy to catch this thread :-) > > Some questions as you Ian seem to already have experience with this devices: > 1. Is it possible to compile only uftdi driver and load it into > existing kernel that have this driver compiled-in so I don't have to > recompile whole kernel and all of the modules? > 2. Is it possible to pass VID/PID and/or RS232 channel as kernel > loadable option? This would again spare some build/runtime time for me > :-) > 3. Do you know a good method on kernel module testing other than > rebuilding/rebooting all the time? VirtualBox + USB Attach? > > Any hints appreciated! :-) > Tomek > If you don't already have the right devices compiled in, just build the usb/ucom and usb/uftdi modules and kldload uftdi and you should be good to go. -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:20:53 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D1E39EAA for ; Mon, 4 Feb 2013 21:20:53 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 8672E8A for ; Mon, 4 Feb 2013 21:20:53 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r14LKrcW002228 for ; Mon, 4 Feb 2013 15:20:53 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 15:20:53 2013 Message-ID: <51102630.9030509@denninger.net> Date: Mon, 04 Feb 2013 15:20:48 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> In-Reply-To: <1360012382.93359.489.camel@revolution.hippie.lan> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-1, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:20:53 -0000 On 2/4/2013 3:13 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>> 9.1-STABLE #16 r244942 >>>> >>>> and it returns.... >>>> >>>> ugen4.4: at usbus4 >>>> uhub6: >>>> on usbus4 >>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>> uhub6: 7 ports with 7 removable, self powered >>>> >>>> Yuck. >>>> >>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>> rather old) but I never had problems there. And it appears that all of >>>> the device declarations that I used to have to put in the kernel as >>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>> >>>> Ideas as to what may have gotten hosed up here? >>>> >>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>> >>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>> parts program different vendor/product info and IDs have to be added to >>> code to recognize them, that's the only trouble one usually encounters. >>> >>> -- Ian >> Well, that sorta kinda worked. >> >> Except that it still is identifying it as a hub too, and the two collide >> and crash the stack. >> >> But I can't find anything that is looking at the PID (0x0050) or the >> definition (HUB_0050) anywhere in the code. >> >> I'll go pull the NEC defs and set up something else instead of simply >> adding it to the FTDI probe list. >> > It seems to me you have a problem with a hub (perhaps the root hub or a > motherboard hub if you don't have an external one) and this has nothing > to do with the ftdi device at all. Or the usb serial device is damaged > somehow so that the vendor and product ID are reading as garbage and > being mistaken for a hub. > > Have you tried the ftdi adapter on another port/hub/computer? Have you > tried plugging something else into the port you're trying to use for the > ftdi adapter, like a thumb drive or something? > > -- Ian The machine is fine. The adapter is fine too -- I powered up the old machine and it works too, and recognizes the adapter immediately (on FreeBSD-Stable 7.) No problems with either. I get identical behavior on multiple ports on the back of the machine and the machine itself is known to be ok and has a USB KVM attached to it which is working, along with a USB-communicating UPS which is also working. When I added the definition it picked it up as an 8-port adapter with 8 FTDI ports on it, but then it ALSO tried to attach it as a 7-port hub (which is what usbdevs says it is) -- although I cannot find ANYWHERE in the code under that directory that references that VID/PID tuple. The second attachment attempt blew up the first (which makes sense.) Since the code obviously does know how to find hubs, there has to be something else going on -- digging through it now to see if I can isolate how it determines something is a "hub" without having a structure with all the hubs defined in it, which I cannot find. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:29:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B2A76481 for ; Mon, 4 Feb 2013 21:29:53 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) by mx1.freebsd.org (Postfix) with ESMTP id 79E4714A for ; Mon, 4 Feb 2013 21:29:53 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so3110912qeb.27 for ; Mon, 04 Feb 2013 13:29:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=W17gXVZJt2emgN6A09vniAxIxJ/FDxIa8V823yf2/zo=; b=VVsqBxb97FtoRaakaho/+Kgro7B2ekmzsptk303b4i2PIz3UKSsfqjx/gfOD+4t34N piP26casLuzJP5xjotf13vuWkImv5orec3CeNq1YWTuSRzUkmdCxc/1NrCT9eaOPCJBA el+zP56eUOlnovyjOwi9GytZVKKTz3Sk0+ysNzVmPbh+MqdX376cWROg0wpqfxHT1nM8 DyneWRE449Ts8V2N523h+J3YymgR7aLDYyu8vZGRZJeLn5VJxiWccOvZozDHylSGqy+I 8fCLjvlv6355r+HNjLX3mw/YwcxcH29MdOcKsRv9U75LUy+WiRimkxc7ZoTp/mXOZFwI NaqQ== MIME-Version: 1.0 X-Received: by 10.49.127.238 with SMTP id nj14mr22281082qeb.9.1360013387643; Mon, 04 Feb 2013 13:29:47 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Mon, 4 Feb 2013 13:29:47 -0800 (PST) In-Reply-To: <51102630.9030509@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <51102630.9030509@denninger.net> Date: Mon, 4 Feb 2013 22:29:47 +0100 X-Google-Sender-Auth: N_D0c0lbc4pF-XQLhwLkHSaVMc4 Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: CeDeROM To: Karl Denninger Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:29:53 -0000 On Mon, Feb 4, 2013 at 10:20 PM, Karl Denninger wrote: > The machine is fine. The adapter is fine too -- I powered up the old > machine and it works too, and recognizes the adapter immediately (on > FreeBSD-Stable 7.) No problems with either. Hello Karl :-) Is VID/PID the same after attach to both machines? Does "usbconfig dump_all_config_desc" returns the same values on both machines for this adapter? Are you sure that adapter does not contain any hub inside? FTDI should have VID 0x0403... -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:33:22 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 49E0667A for ; Mon, 4 Feb 2013 21:33:22 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 191E5182 for ; Mon, 4 Feb 2013 21:33:21 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14LXL4P090156 for ; Mon, 4 Feb 2013 14:33:21 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14LXJiq029841; Mon, 4 Feb 2013 14:33:19 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: Karl Denninger In-Reply-To: <51102630.9030509@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <51102630.9030509@denninger.net> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Feb 2013 14:33:19 -0700 Message-ID: <1360013599.93359.493.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:33:22 -0000 On Mon, 2013-02-04 at 15:20 -0600, Karl Denninger wrote: > On 2/4/2013 3:13 PM, Ian Lepore wrote: > > On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: > >> On 2/4/2013 2:06 PM, Ian Lepore wrote: > >>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: > >>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD > >>>> 9.1-STABLE #16 r244942 > >>>> > >>>> and it returns.... > >>>> > >>>> ugen4.4: at usbus4 > >>>> uhub6: > >>>> on usbus4 > >>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED > >>>> uhub6: 7 ports with 7 removable, self powered > >>>> > >>>> Yuck. > >>>> > >>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, > >>>> rather old) but I never had problems there. And it appears that all of > >>>> the device declarations that I used to have to put in the kernel as > >>>> non-standard stuff are now in GENERIC, so I would expect it to work. > >>>> > >>>> Ideas as to what may have gotten hosed up here? > >>>> > >>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. > >>> > >>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > >>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > >>> parts program different vendor/product info and IDs have to be added to > >>> code to recognize them, that's the only trouble one usually encounters. > >>> > >>> -- Ian > >> Well, that sorta kinda worked. > >> > >> Except that it still is identifying it as a hub too, and the two collide > >> and crash the stack. > >> > >> But I can't find anything that is looking at the PID (0x0050) or the > >> definition (HUB_0050) anywhere in the code. > >> > >> I'll go pull the NEC defs and set up something else instead of simply > >> adding it to the FTDI probe list. > >> > > It seems to me you have a problem with a hub (perhaps the root hub or a > > motherboard hub if you don't have an external one) and this has nothing > > to do with the ftdi device at all. Or the usb serial device is damaged > > somehow so that the vendor and product ID are reading as garbage and > > being mistaken for a hub. > > > > Have you tried the ftdi adapter on another port/hub/computer? Have you > > tried plugging something else into the port you're trying to use for the > > ftdi adapter, like a thumb drive or something? > > > > -- Ian > > The machine is fine. The adapter is fine too -- I powered up the old > machine and it works too, and recognizes the adapter immediately (on > FreeBSD-Stable 7.) No problems with either. > > I get identical behavior on multiple ports on the back of the machine > and the machine itself is known to be ok and has a USB KVM attached to > it which is working, along with a USB-communicating UPS which is also > working. > > When I added the definition it picked it up as an 8-port adapter with 8 > FTDI ports on it, but then it ALSO tried to attach it as a 7-port hub > (which is what usbdevs says it is) -- although I cannot find ANYWHERE in > the code under that directory that references that VID/PID tuple. The > second attachment attempt blew up the first (which makes sense.) > > Since the code obviously does know how to find hubs, there has to be > something else going on -- digging through it now to see if I can > isolate how it determines something is a "hub" without having a > structure with all the hubs defined in it, which I cannot find. > Ahh, I misunderstood what you said earlier. This is where HPS normally shows up and starts asking for usbconfig output using usbconfig options I have no idea how to use. :) -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:37:06 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AE0857A7; Mon, 4 Feb 2013 21:37:06 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp2.bway.net (smtp2.bway.net [216.220.96.28]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0611B6; Mon, 4 Feb 2013 21:37:06 +0000 (UTC) Received: from frankentosh.sporklab.com (foon.sporktines.com [96.57.144.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp2.bway.net (Postfix) with ESMTPSA id 15C9E95887; Mon, 4 Feb 2013 16:31:44 -0500 (EST) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Charles Sprickman In-Reply-To: <1360012382.93359.489.camel@revolution.hippie.lan> Date: Mon, 4 Feb 2013 16:31:43 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) Cc: freebsd-stable@FreeBSD.org, Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:37:06 -0000 On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>> 9.1-STABLE #16 r244942 >>>>=20 >>>> and it returns.... >>>>=20 >>>> ugen4.4: at usbus4 >>>> uhub6: >>>> on usbus4 >>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>> uhub6: 7 ports with 7 removable, self powered >>>>=20 >>>> Yuck. >>>>=20 >>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>> rather old) but I never had problems there. And it appears that = all of >>>> the device declarations that I used to have to put in the kernel as >>>> non-standard stuff are now in GENERIC, so I would expect it to = work. >>>>=20 >>>> Ideas as to what may have gotten hosed up here? >>>>=20 >>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is = NEC. >>>=20 >>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 = and >>> 10; I use it all the time. Sometimes aftermarket vendors who use = FTDI's >>> parts program different vendor/product info and IDs have to be added = to >>> code to recognize them, that's the only trouble one usually = encounters. >>>=20 >>> -- Ian >> Well, that sorta kinda worked.=20 >>=20 >> Except that it still is identifying it as a hub too, and the two = collide >> and crash the stack. >>=20 >> But I can't find anything that is looking at the PID (0x0050) or the >> definition (HUB_0050) anywhere in the code.=20 >>=20 >> I'll go pull the NEC defs and set up something else instead of simply >> adding it to the FTDI probe list. >>=20 >=20 > It seems to me you have a problem with a hub (perhaps the root hub or = a > motherboard hub if you don't have an external one) and this has = nothing > to do with the ftdi device at all. I assume we're talking about a multi-port usb to serial adapter, = correct? If so, they generally do have a hub included in the device. Example: ugen1.3: at usbus1 uhub4: = on usbus1 uhub4: 7 ports with 7 removable, self powered Then the individual ports look like this: ugen1.4: at usbus1 uftdi0: on usbus1 ugen1.5: at usbus1 uftdi1: on usbus1 (etc.) We use these for serial console ports, they're (relatively) cheap and = have generally been well supported. The above info is from an 8.3 box. Just wanted to clarify that there is likely a hub in the serial box Karl = is working with=85 Charles > Or the usb serial device is damaged > somehow so that the vendor and product ID are reading as garbage and > being mistaken for a hub. >=20 > Have you tried the ftdi adapter on another port/hub/computer? Have = you > tried plugging something else into the port you're trying to use for = the > ftdi adapter, like a thumb drive or something? >=20 > -- Ian >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:00:29 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 576471B5 for ; Mon, 4 Feb 2013 22:00:29 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id D77CE2B2 for ; Mon, 4 Feb 2013 22:00:28 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14M0Sc1090490 for ; Mon, 4 Feb 2013 15:00:28 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14M0QQD029880; Mon, 4 Feb 2013 15:00:26 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: Charles Sprickman In-Reply-To: <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> Content-Type: text/plain; charset="windows-1251" Date: Mon, 04 Feb 2013 15:00:26 -0700 Message-ID: <1360015226.93359.502.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-stable@FreeBSD.org, Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:00:29 -0000 On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: > On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: > > > On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: > >> On 2/4/2013 2:06 PM, Ian Lepore wrote: > >>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: > >>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD > >>>> 9.1-STABLE #16 r244942 > >>>> > >>>> and it returns.... > >>>> > >>>> ugen4.4: at usbus4 > >>>> uhub6: > >>>> on usbus4 > >>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED > >>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED > >>>> uhub6: 7 ports with 7 removable, self powered > >>>> > >>>> Yuck. > >>>> > >>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, > >>>> rather old) but I never had problems there. And it appears that all of > >>>> the device declarations that I used to have to put in the kernel as > >>>> non-standard stuff are now in GENERIC, so I would expect it to work. > >>>> > >>>> Ideas as to what may have gotten hosed up here? > >>>> > >>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. > >>> > >>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > >>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > >>> parts program different vendor/product info and IDs have to be added to > >>> code to recognize them, that's the only trouble one usually encounters. > >>> > >>> -- Ian > >> Well, that sorta kinda worked. > >> > >> Except that it still is identifying it as a hub too, and the two collide > >> and crash the stack. > >> > >> But I can't find anything that is looking at the PID (0x0050) or the > >> definition (HUB_0050) anywhere in the code. > >> > >> I'll go pull the NEC defs and set up something else instead of simply > >> adding it to the FTDI probe list. > >> > > > > It seems to me you have a problem with a hub (perhaps the root hub or a > > motherboard hub if you don't have an external one) and this has nothing > > to do with the ftdi device at all. > > I assume we're talking about a multi-port usb to serial adapter, correct? > > If so, they generally do have a hub included in the device. > > Example: > > ugen1.3: at usbus1 > uhub4: on usbus1 > uhub4: 7 ports with 7 removable, self powered > > Then the individual ports look like this: > > ugen1.4: at usbus1 > uftdi0: on usbus1 > ugen1.5: at usbus1 > uftdi1: on usbus1 > (etc.) > > We use these for serial console ports, they're (relatively) cheap and have generally been well supported. > > The above info is from an 8.3 box. > > Just wanted to clarify that there is likely a hub in the serial box Karl is working with… > > Charles Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the ftdi 4232 chip. I guess to get more ports than that, folks are now using an internal hub and multiple ftdi chips. So for some reason there's a problem with the hub, and that's probably preventing it from getting as far as seeing the ftdi parts that are downstream of that. -- Ian From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:04:06 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 656E5578 for ; Mon, 4 Feb 2013 22:04:06 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id EFA71313 for ; Mon, 4 Feb 2013 22:04:05 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r14M43xp020950; Mon, 4 Feb 2013 23:04:03 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r14M43Ls020949; Mon, 4 Feb 2013 23:04:03 +0100 (CET) (envelope-from olli) Date: Mon, 4 Feb 2013 23:04:03 +0100 (CET) Message-Id: <201302042204.r14M43Ls020949@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, John-Mark Gurney Subject: Re: re(4) problems with GA-H77N-WIFI In-Reply-To: <20130204181905.GT1410@funkthat.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:04:06 -0000 John-Mark Gurney wrote: > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: > > I'm running a recent stable/9 (about 14 days old). > > What's the best way to debug this problem? At the > > moment I'm not even sure if it's the hardware, or if > > it's FreeBSD's fault (or my fault) ... > > Have you tried to disable msi and msix? > > hw.pci.enable_msix: 1 > hw.pci.enable_msi: 1 I tried these entries in /boot/loader.conf, according to the re(4) manual page: hw.re.msi_disable="1" hw.re.msix_disable="1" Unfortunately it didn't make a difference. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "The scanf() function is a large and complex beast that often does something almost but not quite entirely unlike what you desired." -- Chris Torek From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:10:45 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3236594A for ; Mon, 4 Feb 2013 22:10:45 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id DD43136E for ; Mon, 4 Feb 2013 22:10:44 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r14MAh6Z038852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Feb 2013 14:10:43 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r14MAhiT038851; Mon, 4 Feb 2013 14:10:43 -0800 (PST) (envelope-from jmg) Date: Mon, 4 Feb 2013 14:10:43 -0800 From: John-Mark Gurney To: Oliver Fromme Subject: Re: re(4) problems with GA-H77N-WIFI Message-ID: <20130204221043.GU1410@funkthat.com> Mail-Followup-To: Oliver Fromme , freebsd-stable@FreeBSD.ORG References: <20130204181905.GT1410@funkthat.com> <201302042204.r14M43Ls020949@grabthar.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302042204.r14M43Ls020949@grabthar.secnetix.de> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 04 Feb 2013 14:10:44 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:10:45 -0000 Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100: > John-Mark Gurney wrote: > > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: > > > I'm running a recent stable/9 (about 14 days old). > > > What's the best way to debug this problem? At the > > > moment I'm not even sure if it's the hardware, or if > > > it's FreeBSD's fault (or my fault) ... > > > > Have you tried to disable msi and msix? > > > > hw.pci.enable_msix: 1 > > hw.pci.enable_msi: 1 > > I tried these entries in /boot/loader.conf, according to > the re(4) manual page: > > hw.re.msi_disable="1" > hw.re.msix_disable="1" > > Unfortunately it didn't make a difference. Did you try in loader.conf: hw.pci.enable_msix="0" hw.pci.enable_msi="0" To disable MSI for the whole system? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:29:47 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD911ED4 for ; Mon, 4 Feb 2013 22:29:47 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 51BE9661 for ; Mon, 4 Feb 2013 22:29:46 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r14MTkHP013472 for ; Mon, 4 Feb 2013 16:29:46 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 16:29:46 2013 Message-ID: <51103655.2080300@denninger.net> Date: Mon, 04 Feb 2013 16:29:41 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> In-Reply-To: <1360015226.93359.502.camel@revolution.hippie.lan> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-1, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:29:47 -0000 On 2/4/2013 4:00 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >> >>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>> 9.1-STABLE #16 r244942 >>>>>> >>>>>> and it returns.... >>>>>> >>>>>> ugen4.4: at usbus4 >>>>>> uhub6: >>>>>> on usbus4 >>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>> >>>>>> Yuck. >>>>>> >>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>>>> rather old) but I never had problems there. And it appears that all of >>>>>> the device declarations that I used to have to put in the kernel as >>>>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>>>> >>>>>> Ideas as to what may have gotten hosed up here? >>>>>> >>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>>>> >>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>>>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>>>> parts program different vendor/product info and IDs have to be added to >>>>> code to recognize them, that's the only trouble one usually encounters. >>>>> >>>>> -- Ian >>>> Well, that sorta kinda worked. >>>> >>>> Except that it still is identifying it as a hub too, and the two collide >>>> and crash the stack. >>>> >>>> But I can't find anything that is looking at the PID (0x0050) or the >>>> definition (HUB_0050) anywhere in the code. >>>> >>>> I'll go pull the NEC defs and set up something else instead of simply >>>> adding it to the FTDI probe list. >>>> >>> It seems to me you have a problem with a hub (perhaps the root hub or a >>> motherboard hub if you don't have an external one) and this has nothing >>> to do with the ftdi device at all. >> I assume we're talking about a multi-port usb to serial adapter, correct? >> >> If so, they generally do have a hub included in the device. >> >> Example: >> >> ugen1.3: at usbus1 >> uhub4: on usbus1 >> uhub4: 7 ports with 7 removable, self powered >> >> Then the individual ports look like this: >> >> ugen1.4: at usbus1 >> uftdi0: on usbus1 >> ugen1.5: at usbus1 >> uftdi1: on usbus1 >> (etc.) >> >> We use these for serial console ports, they're (relatively) cheap and have generally been well supported. >> >> The above info is from an 8.3 box. >> >> Just wanted to clarify that there is likely a hub in the serial box Karl is working with… >> >> Charles > Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the > ftdi 4232 chip. I guess to get more ports than that, folks are now > using an internal hub and multiple ftdi chips. > > So for some reason there's a problem with the hub, and that's probably > preventing it from getting as far as seeing the ftdi parts that are > downstream of that. > > -- Ian > Ah, well then yuck. Will put things back where they were and play some more -- I'll probe this with the other box and see if I can find the difference. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:32:31 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 86E5399; Mon, 4 Feb 2013 22:32:31 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp2.bway.net (smtp2.bway.net [216.220.96.28]) by mx1.freebsd.org (Postfix) with ESMTP id 4B46D68C; Mon, 4 Feb 2013 22:32:31 +0000 (UTC) Received: from frankentosh.sporklab.com (foon.sporktines.com [96.57.144.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp2.bway.net (Postfix) with ESMTPSA id 50A6195887; Mon, 4 Feb 2013 17:32:27 -0500 (EST) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Charles Sprickman In-Reply-To: <1360015226.93359.502.camel@revolution.hippie.lan> Date: Mon, 4 Feb 2013 17:32:26 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) Cc: freebsd-stable@FreeBSD.org, Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:32:31 -0000 On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: > On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >>=20 >>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>> 9.1-STABLE #16 r244942 >>>>>>=20 >>>>>> and it returns.... >>>>>>=20 >>>>>> ugen4.4: at usbus4 >>>>>> uhub6: >>>>>> on usbus4 >>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>>=20 >>>>>> Yuck. >>>>>>=20 >>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I = know, >>>>>> rather old) but I never had problems there. And it appears that = all of >>>>>> the device declarations that I used to have to put in the kernel = as >>>>>> non-standard stuff are now in GENERIC, so I would expect it to = work. >>>>>>=20 >>>>>> Ideas as to what may have gotten hosed up here? >>>>>>=20 >>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 = is NEC. >>>>>=20 >>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 = and >>>>> 10; I use it all the time. Sometimes aftermarket vendors who use = FTDI's >>>>> parts program different vendor/product info and IDs have to be = added to >>>>> code to recognize them, that's the only trouble one usually = encounters. >>>>>=20 >>>>> -- Ian >>>> Well, that sorta kinda worked.=20 >>>>=20 >>>> Except that it still is identifying it as a hub too, and the two = collide >>>> and crash the stack. >>>>=20 >>>> But I can't find anything that is looking at the PID (0x0050) or = the >>>> definition (HUB_0050) anywhere in the code.=20 >>>>=20 >>>> I'll go pull the NEC defs and set up something else instead of = simply >>>> adding it to the FTDI probe list. >>>>=20 >>>=20 >>> It seems to me you have a problem with a hub (perhaps the root hub = or a >>> motherboard hub if you don't have an external one) and this has = nothing >>> to do with the ftdi device at all. >>=20 >> I assume we're talking about a multi-port usb to serial adapter, = correct? >>=20 >> If so, they generally do have a hub included in the device. >>=20 >> Example: >>=20 >> ugen1.3: at usbus1 >> uhub4: on usbus1 >> uhub4: 7 ports with 7 removable, self powered >>=20 >> Then the individual ports look like this: >>=20 >> ugen1.4: at usbus1 >> uftdi0: on usbus1 >> ugen1.5: at usbus1 >> uftdi1: on usbus1 >> (etc.) >>=20 >> We use these for serial console ports, they're (relatively) cheap and = have generally been well supported. >>=20 >> The above info is from an 8.3 box. >>=20 >> Just wanted to clarify that there is likely a hub in the serial box = Karl is working with=85 >>=20 >> Charles >=20 > Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the > ftdi 4232 chip. I guess to get more ports than that, folks are now > using an internal hub and multiple ftdi chips. These multiport things have been around for a long time. Someone at ISC = recommended them when we were looking to replace some unsupported = RocketPort cards. Not affiliated with this place, but it's the largest = collection of USB to serial stuff I've ever seen (and they document for = the most part what chips are involved): http://usbgear.com/USB-Serial.html Our first 16 ports are on one of these: = http://usbgear.com/computer_cable_details.cfm?sku=3DUSB-16COM-RM&cats=3D19= 9&catid=3D493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 (the tx/rx blinky lights are handy in troubleshooting) Then the rest on this cheaper model: = http://usbgear.com/computer_cable_details.cfm?sku=3DUSBG-8COM-M&cats=3D199= &catid=3D494%2C199%2C474%2C2345%2C1009 > So for some reason there's a problem with the hub, and that's probably > preventing it from getting as far as seeing the ftdi parts that are > downstream of that. My dmesg snippet is from the latter box. Note that the vendor and = product ID are the same as Karl's. Perhaps there is a regression, as I = am running 8.3 and have had no issues there (previously it was on a 4.11 = box). Charles >=20 > -- Ian >=20 From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 22:36:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B499A451; Mon, 4 Feb 2013 22:36:36 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id D0EB36CF; Mon, 4 Feb 2013 22:36:35 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so5085807wey.2 for ; Mon, 04 Feb 2013 14:36:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=gIOyC/nZKOQUEQGDCOP0rCItTtyFHvCVbqU0/ZTgbcU=; b=zUGqJD0AaueoOnLJbUSNhMXN5fxouAYjU+GN2SCQyQLKJZsh2h7C7tEfGCSyHJAk4k 2I3K69+rLqxVfmJP9yrgmGQBvBmiSEqFVoaQx9ytepHwvCi9zGvvG7VDDeXHpfawWq4r tE4iI4PUO5xt2ygIp3UK/GuMzpNMfrIJlGgupG2lJLzUK09D4yZ+p7p5lcJ+Ae8FNhWe 8TxOZFqn2Z7DitILrE2pymNi+LMSr3NhW87393E0o0qHAMUdiNKWu2UFy/uaWy/0dO3D C6pDr73qfdLt6cmTUq8Hk96WTEsD8Sm4BbhpFybDag8QQiFSBWUfoLKhb+9dsin1hjSJ GAyQ== MIME-Version: 1.0 X-Received: by 10.180.8.197 with SMTP id t5mr12641591wia.27.1360017394300; Mon, 04 Feb 2013 14:36:34 -0800 (PST) Received: by 10.216.172.197 with HTTP; Mon, 4 Feb 2013 14:36:34 -0800 (PST) Date: Tue, 5 Feb 2013 00:36:34 +0200 Message-ID: Subject: Re: stable/9 r245439 breaks security/pam_ssh_agent_auth on stable/9 (WAS: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9) From: Kimmo Paasiala To: Chris Rees Content-Type: text/plain; charset=UTF-8 Cc: Mark Linimon , Brooks Davis , Dimitry Andric , Stefan Bethke , FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:36:36 -0000 On Sun, Feb 3, 2013 at 7:22 PM, Chris Rees wrote: > On 3 February 2013 17:15, Stefan Bethke wrote: >> >> Am 03.02.2013 um 10:57 schrieb Chris Rees : >> >>> On 3 February 2013 03:55, Kimmo Paasiala wrote: >>>> >>>> There is no PR yet with my fix and therefor no commit to ports tree >>>> that would fix the problem. I'll file a PR soon (TM). >>> >>> The problem was in base, and is fixed there. >> >> Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. >> >> Is there some confusion about which problem is addressed by Kimmo's patch? >> > > Hm, perhaps it might be necessary then. > > Kimmo, please would you submit the patch you had as a PR? I'm sure > Wesley would appreciate the hint. > > Chris I'll file a PR when I have recovered from a nasty flu. Right now I'm not fit for thinking... I changed the title of this thread to a better one. -Kimmo From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 02:47:23 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D54E962B; Tue, 5 Feb 2013 02:47:23 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 9C6CDFAD; Tue, 5 Feb 2013 02:47:23 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r152lM1K061444; Tue, 5 Feb 2013 02:47:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r152lMZF061439; Tue, 5 Feb 2013 02:47:22 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 5 Feb 2013 02:47:22 GMT Message-Id: <201302050247.r152lMZF061439@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 02:47:24 -0000 TB --- 2013-02-04 23:59:00 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-04 23:59:00 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-04 23:59:00 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2013-02-04 23:59:00 - cleaning the object tree TB --- 2013-02-04 23:59:00 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-04 23:59:00 - cd /tinderbox/RELENG_9/ia64/ia64 TB --- 2013-02-04 23:59:00 - /usr/local/bin/svn cleanup /src TB --- 2013-02-05 00:00:13 - /usr/local/bin/svn update /src TB --- 2013-02-05 00:00:21 - building world TB --- 2013-02-05 00:00:21 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 00:00:21 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 00:00:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 00:00:21 - SRCCONF=/dev/null TB --- 2013-02-05 00:00:21 - TARGET=ia64 TB --- 2013-02-05 00:00:21 - TARGET_ARCH=ia64 TB --- 2013-02-05 00:00:21 - TZ=UTC TB --- 2013-02-05 00:00:21 - __MAKE_CONF=/dev/null TB --- 2013-02-05 00:00:21 - cd /src TB --- 2013-02-05 00:00:21 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 5 00:00:22 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Feb 5 01:53:19 UTC 2013 TB --- 2013-02-05 01:53:19 - generating LINT kernel config TB --- 2013-02-05 01:53:19 - cd /src/sys/ia64/conf TB --- 2013-02-05 01:53:19 - /usr/bin/make -B LINT TB --- 2013-02-05 01:53:19 - cd /src/sys/ia64/conf TB --- 2013-02-05 01:53:19 - /usr/sbin/config -m LINT TB --- 2013-02-05 01:53:19 - building LINT kernel TB --- 2013-02-05 01:53:19 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 01:53:19 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 01:53:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 01:53:19 - SRCCONF=/dev/null TB --- 2013-02-05 01:53:19 - TARGET=ia64 TB --- 2013-02-05 01:53:19 - TARGET_ARCH=ia64 TB --- 2013-02-05 01:53:19 - TZ=UTC TB --- 2013-02-05 01:53:19 - __MAKE_CONF=/dev/null TB --- 2013-02-05 01:53:19 - cd /src TB --- 2013-02-05 01:53:19 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Feb 5 01:53:20 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Tue Feb 5 02:37:05 UTC 2013 TB --- 2013-02-05 02:37:05 - cd /src/sys/ia64/conf TB --- 2013-02-05 02:37:05 - /usr/sbin/config -m GENERIC TB --- 2013-02-05 02:37:05 - building GENERIC kernel TB --- 2013-02-05 02:37:05 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 02:37:05 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 02:37:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 02:37:05 - SRCCONF=/dev/null TB --- 2013-02-05 02:37:05 - TARGET=ia64 TB --- 2013-02-05 02:37:05 - TARGET_ARCH=ia64 TB --- 2013-02-05 02:37:05 - TZ=UTC TB --- 2013-02-05 02:37:05 - __MAKE_CONF=/dev/null TB --- 2013-02-05 02:37:05 - cd /src TB --- 2013-02-05 02:37:05 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Feb 5 02:37:05 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/firewire/if_fwip.c:499: undefined reference to `crom_add_simple_text' /src/sys/dev/firewire/if_fwip.c:500: undefined reference to `crom_add_entry' /src/sys/dev/firewire/if_fwip.c:501: undefined reference to `crom_add_simple_text' if_fwip.o: In function `fwip_stream_input': /src/sys/dev/firewire/if_fwip.c:840: undefined reference to `fw_noderesolve_nodeid' if_fwip.o: In function `fwip_unicast_input': /src/sys/dev/firewire/if_fwip.c:939: undefined reference to `fw_noderesolve_nodeid' if_fwip.o:(.data.rel+0x80): undefined reference to `sysctl__hw_firewire_children' *** Error code 1 Stop in /obj/ia64.ia64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-02-05 02:47:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-02-05 02:47:22 - ERROR: failed to build GENERIC kernel TB --- 2013-02-05 02:47:22 - 7168.30 user 858.03 system 10102.42 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 03:03:05 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 28564D67 for ; Tue, 5 Feb 2013 03:03:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id A56A8154 for ; Tue, 5 Feb 2013 03:03:03 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r15333Qd020824 for ; Mon, 4 Feb 2013 21:03:03 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 21:03:03 2013 Message-ID: <51107662.8050708@denninger.net> Date: Mon, 04 Feb 2013 21:02:58 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> In-Reply-To: X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-1, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 03:03:05 -0000 On 2/4/2013 4:32 PM, Charles Sprickman wrote: > On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: > >> On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >>> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >>> >>>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>>> 9.1-STABLE #16 r244942 >>>>>>> >>>>>>> and it returns.... >>>>>>> >>>>>>> ugen4.4: at usbus4 >>>>>>> uhub6: >>>>>>> on usbus4 >>>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>>> >>>>>>> Yuck. >>>>>>> >>>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>>>>> rather old) but I never had problems there. And it appears that all of >>>>>>> the device declarations that I used to have to put in the kernel as >>>>>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>>>>> >>>>>>> Ideas as to what may have gotten hosed up here? >>>>>>> >>>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>>>>> >>>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>>>>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>>>>> parts program different vendor/product info and IDs have to be added to >>>>>> code to recognize them, that's the only trouble one usually encounters. >>>>>> >>>>>> -- Ian >>>>> Well, that sorta kinda worked. >>>>> >>>>> Except that it still is identifying it as a hub too, and the two collide >>>>> and crash the stack. >>>>> >>>>> But I can't find anything that is looking at the PID (0x0050) or the >>>>> definition (HUB_0050) anywhere in the code. >>>>> >>>>> I'll go pull the NEC defs and set up something else instead of simply >>>>> adding it to the FTDI probe list. >>>>> >>>> It seems to me you have a problem with a hub (perhaps the root hub or a >>>> motherboard hub if you don't have an external one) and this has nothing >>>> to do with the ftdi device at all. >>> I assume we're talking about a multi-port usb to serial adapter, correct? >>> >>> If so, they generally do have a hub included in the device. >>> >>> Example: >>> >>> ugen1.3: at usbus1 >>> uhub4: on usbus1 >>> uhub4: 7 ports with 7 removable, self powered >>> >>> Then the individual ports look like this: >>> >>> ugen1.4: at usbus1 >>> uftdi0: on usbus1 >>> ugen1.5: at usbus1 >>> uftdi1: on usbus1 >>> (etc.) >>> >>> We use these for serial console ports, they're (relatively) cheap and have generally been well supported. >>> >>> The above info is from an 8.3 box. >>> >>> Just wanted to clarify that there is likely a hub in the serial box Karl is working with… >>> >>> Charles >> Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the >> ftdi 4232 chip. I guess to get more ports than that, folks are now >> using an internal hub and multiple ftdi chips. > These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): > > http://usbgear.com/USB-Serial.html > > Our first 16 ports are on one of these: > > http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 > (the tx/rx blinky lights are handy in troubleshooting) > > Then the rest on this cheaper model: > > http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 > >> So for some reason there's a problem with the hub, and that's probably >> preventing it from getting as far as seeing the ftdi parts that are >> downstream of that. > My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). > > Charles > That's the EXACT box. I've used them for a VERY long time on FreeBSD and they have always worked perfectly well, but never on 9.x until now -- and it doesn't work on 9.x. Had to run out for a while -- continuing testing. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 03:33:29 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 08D01C91 for ; Tue, 5 Feb 2013 03:33:29 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 813D72C4 for ; Tue, 5 Feb 2013 03:33:27 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r153XRWO004049 for ; Mon, 4 Feb 2013 21:33:27 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 21:33:27 2013 Message-ID: <51107D82.8040605@denninger.net> Date: Mon, 04 Feb 2013 21:33:22 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> In-Reply-To: <51107662.8050708@denninger.net> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-1, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 03:33:29 -0000 On 2/4/2013 9:02 PM, Karl Denninger wrote: > On 2/4/2013 4:32 PM, Charles Sprickman wrote: >> On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: >> >>> On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >>>> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >>>> >>>>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>>>> 9.1-STABLE #16 r244942 >>>>>>>> >>>>>>>> and it returns.... >>>>>>>> >>>>>>>> ugen4.4: at usbus4 >>>>>>>> uhub6: >>>>>>>> on usbus4 >>>>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>>>> >>>>>>>> Yuck. >>>>>>>> >>>>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>>>>>> rather old) but I never had problems there. And it appears that all of >>>>>>>> the device declarations that I used to have to put in the kernel as >>>>>>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>>>>>> >>>>>>>> Ideas as to what may have gotten hosed up here? >>>>>>>> >>>>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>>>>>> >>>>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>>>>>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>>>>>> parts program different vendor/product info and IDs have to be added to >>>>>>> code to recognize them, that's the only trouble one usually encounters. >>>>>>> >>>>>>> -- Ian >>>>>> Well, that sorta kinda worked. >>>>>> >>>>>> Except that it still is identifying it as a hub too, and the two collide >>>>>> and crash the stack. >>>>>> >>>>>> But I can't find anything that is looking at the PID (0x0050) or the >>>>>> definition (HUB_0050) anywhere in the code. >>>>>> >>>>>> I'll go pull the NEC defs and set up something else instead of simply >>>>>> adding it to the FTDI probe list. >>>>>> >>>>> It seems to me you have a problem with a hub (perhaps the root hub or a >>>>> motherboard hub if you don't have an external one) and this has nothing >>>>> to do with the ftdi device at all. >>>> I assume we're talking about a multi-port usb to serial adapter, correct? >>>> >>>> If so, they generally do have a hub included in the device. >>>> >>>> Example: >>>> >>>> ugen1.3: at usbus1 >>>> uhub4: on usbus1 >>>> uhub4: 7 ports with 7 removable, self powered >>>> >>>> Then the individual ports look like this: >>>> >>>> ugen1.4: at usbus1 >>>> uftdi0: on usbus1 >>>> ugen1.5: at usbus1 >>>> uftdi1: on usbus1 >>>> (etc.) >>>> >>>> We use these for serial console ports, they're (relatively) cheap and have generally been well supported. >>>> >>>> The above info is from an 8.3 box. >>>> >>>> Just wanted to clarify that there is likely a hub in the serial box Karl is working with… >>>> >>>> Charles >>> Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the >>> ftdi 4232 chip. I guess to get more ports than that, folks are now >>> using an internal hub and multiple ftdi chips. >> These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): >> >> http://usbgear.com/USB-Serial.html >> >> Our first 16 ports are on one of these: >> >> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >> (the tx/rx blinky lights are handy in troubleshooting) >> >> Then the rest on this cheaper model: >> >> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >> >>> So for some reason there's a problem with the hub, and that's probably >>> preventing it from getting as far as seeing the ftdi parts that are >>> downstream of that. >> My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). >> >> Charles >> > That's the EXACT box. > > I've used them for a VERY long time on FreeBSD and they have always > worked perfectly well, but never on 9.x until now -- and it doesn't work > on 9.x. > > Had to run out for a while -- continuing testing. OK, with the kernel back the way it was, this is what I got: I plug in and get: Feb 4 21:17:46 FS kernel: uhub6: on usbus4 Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc ugen4.4: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x0000 iProduct = 0x0000 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 I then issue and get: FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc ugen4.4: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x0000 iProduct = 0x0000 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 And if I turn it off and back on (power_off then power_on) the cycle repeats. An attempt to reset is also futile, although the command is accepted. If I turn on hw.usb.uhub.debug I get a never-ending string of these: Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Until the power is turned off on the device (with "usbconfig -u 4 -a 4 power_off"), when it settles down to this once in a while: Feb 4 21:29:26 FS kernel: usb_needs_explore: Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks Feb 4 21:29:26 FS kernel: usb_needs_explore: Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 04:42:31 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A95E94BA for ; Tue, 5 Feb 2013 04:42:31 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 3803E6A2 for ; Tue, 5 Feb 2013 04:42:30 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r154gTVY008021 for ; Mon, 4 Feb 2013 22:42:29 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Mon Feb 4 22:42:29 2013 Message-ID: <51108DB0.7050403@denninger.net> Date: Mon, 04 Feb 2013 22:42:24 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> In-Reply-To: <51107D82.8040605@denninger.net> X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130204-1, 02/04/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 04:42:31 -0000 On 2/4/2013 9:33 PM, Karl Denninger wrote: > On 2/4/2013 9:02 PM, Karl Denninger wrote: >> On 2/4/2013 4:32 PM, Charles Sprickman wrote: >>> On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: >>> >>>> On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >>>>> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >>>>> >>>>>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>>>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>>>>> 9.1-STABLE #16 r244942 >>>>>>>>> >>>>>>>>> and it returns.... >>>>>>>>> >>>>>>>>> ugen4.4: at usbus4 >>>>>>>>> uhub6: >>>>>>>>> on usbus4 >>>>>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>>>>> >>>>>>>>> Yuck. >>>>>>>>> >>>>>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>>>>>>> rather old) but I never had problems there. And it appears that all of >>>>>>>>> the device declarations that I used to have to put in the kernel as >>>>>>>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>>>>>>> >>>>>>>>> Ideas as to what may have gotten hosed up here? >>>>>>>>> >>>>>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>>>>>>> >>>>>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>>>>>>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>>>>>>> parts program different vendor/product info and IDs have to be added to >>>>>>>> code to recognize them, that's the only trouble one usually encounters. >>>>>>>> >>>>>>>> -- Ian >>>>>>> Well, that sorta kinda worked. >>>>>>> >>>>>>> Except that it still is identifying it as a hub too, and the two collide >>>>>>> and crash the stack. >>>>>>> >>>>>>> But I can't find anything that is looking at the PID (0x0050) or the >>>>>>> definition (HUB_0050) anywhere in the code. >>>>>>> >>>>>>> I'll go pull the NEC defs and set up something else instead of simply >>>>>>> adding it to the FTDI probe list. >>>>>>> >>>>>> It seems to me you have a problem with a hub (perhaps the root hub or a >>>>>> motherboard hub if you don't have an external one) and this has nothing >>>>>> to do with the ftdi device at all. >>>>> I assume we're talking about a multi-port usb to serial adapter, correct? >>>>> >>>>> If so, they generally do have a hub included in the device. >>>>> >>>>> Example: >>>>> >>>>> ugen1.3: at usbus1 >>>>> uhub4: on usbus1 >>>>> uhub4: 7 ports with 7 removable, self powered >>>>> >>>>> Then the individual ports look like this: >>>>> >>>>> ugen1.4: at usbus1 >>>>> uftdi0: on usbus1 >>>>> ugen1.5: at usbus1 >>>>> uftdi1: on usbus1 >>>>> (etc.) >>>>> >>>>> We use these for serial console ports, they're (relatively) cheap and have generally been well supported. >>>>> >>>>> The above info is from an 8.3 box. >>>>> >>>>> Just wanted to clarify that there is likely a hub in the serial box Karl is working with… >>>>> >>>>> Charles >>>> Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the >>>> ftdi 4232 chip. I guess to get more ports than that, folks are now >>>> using an internal hub and multiple ftdi chips. >>> These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): >>> >>> http://usbgear.com/USB-Serial.html >>> >>> Our first 16 ports are on one of these: >>> >>> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >>> (the tx/rx blinky lights are handy in troubleshooting) >>> >>> Then the rest on this cheaper model: >>> >>> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >>> >>>> So for some reason there's a problem with the hub, and that's probably >>>> preventing it from getting as far as seeing the ftdi parts that are >>>> downstream of that. >>> My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). >>> >>> Charles >>> >> That's the EXACT box. >> >> I've used them for a VERY long time on FreeBSD and they have always >> worked perfectly well, but never on 9.x until now -- and it doesn't work >> on 9.x. >> >> Had to run out for a while -- continuing testing. > OK, with the kernel back the way it was, this is what I got: > > I plug in and get: > > Feb 4 21:17:46 FS kernel: uhub6: 9/0, rev 2.00/1.00, addr 4> on usbus4 > Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, > USB_ERR_STALLED > Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, > USB_ERR_STALLED > Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, > USB_ERR_STALLED > Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, > USB_ERR_STALLED > Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, > USB_ERR_STALLED > Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, > USB_ERR_STALLED > Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, > USB_ERR_STALLED > Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered > > FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc > ugen4.4: at usbus4, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=SAVE > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0009 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0001 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0409 > idProduct = 0x0050 > bcdDevice = 0x0100 > iManufacturer = 0x0000 > iProduct = 0x0000 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > I then issue and get: > FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on > FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc > ugen4.4: at usbus4, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0009 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0001 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0409 > idProduct = 0x0050 > bcdDevice = 0x0100 > iManufacturer = 0x0000 > iProduct = 0x0000 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > And if I turn it off and back on (power_off then power_on) the cycle > repeats. An attempt to reset is also futile, although the command is > accepted. > > If I turn on hw.usb.uhub.debug I get a never-ending string of these: > > Feb 4 21:29:12 FS kernel: usb_needs_explore: > Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:12 FS kernel: usb_needs_explore: > Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:12 FS kernel: usb_needs_explore: > Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:12 FS kernel: usb_needs_explore: > Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:12 FS kernel: usb_needs_explore: > Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:13 FS kernel: usb_needs_explore: > Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:13 FS kernel: usb_needs_explore: > Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:13 FS kernel: usb_needs_explore: > Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 > Feb 4 21:29:13 FS kernel: usb_needs_explore: > Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 > > Until the power is turned off on the device (with "usbconfig -u 4 -a 4 > power_off"), when it settles down to this once in a while: > > Feb 4 21:29:26 FS kernel: usb_needs_explore: > Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 > Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks > Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks > Feb 4 21:29:26 FS kernel: usb_needs_explore: > Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 > Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks > Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 > Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks > Ok, bizarro-land update. The KVM (which talks to the box over USB for keyboard and mouse) interferes with the FTDI adapter! I have absolutely NO idea why, but if it's not plugged in the FTDI adapter comes up instantly. Of course then I can't KVM into the box, which creates its own set of problems. ARGH. Ok, now to figure out how to run this down. There has to be a way..... ideas? -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 08:48:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8A49986D for ; Tue, 5 Feb 2013 08:48:36 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 45204F42 for ; Tue, 5 Feb 2013 08:48:36 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by kabab.cs.huji.ac.il with esmtp id 1U2eCa-0007TS-HS for freebsd-stable@freebsd.org; Tue, 05 Feb 2013 10:48:28 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: FreeBSD Stable Mailing List Subject: problems with the mfi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Feb 2013 10:48:28 +0200 From: Daniel Braniss Message-ID: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 08:48:36 -0000 after rebooting I get very often: ... mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS ... another reboot usualy fixes this. danny From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 09:50:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 276D8B1C for ; Tue, 5 Feb 2013 09:50:20 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by mx1.freebsd.org (Postfix) with ESMTP id E1547901 for ; Tue, 5 Feb 2013 09:50:19 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id o13so33209qaj.1 for ; Tue, 05 Feb 2013 01:50:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=U4z/VBBQWnFs82d7buB1A98Uq7x6bbJYFB8EVkpe6XU=; b=N0ZV81+468lXSuRSYII8V3nEEoGxdLUIL6cCqRj/7gepOpknxhqbSOBjg23+N6Giv9 ginevWRLvywJXYP+RTcTgiEGlKLNdZd8HRgXS9DToGDhVUCr29bHOB78EkZrSpLa5iiY 82hJCHQq7TnB8fkM9gHB+fskjl6cKK3LvmJZXYda8aE0pEz56WMB4b+5aKnCuaRrXDbz B/6TBl483Xo32m9mJfujRpZ/zpPw3FoiId9K5vMyUMEauntH/JESt7DL+N1YcPQQpI4x iVQp9uOmscwG8he9Z5Kuc3ha8fZHoLVPoC2GlhbSmGS5jId4bVhZ+/q7ikhbj5hinbKf SyMQ== MIME-Version: 1.0 X-Received: by 10.224.58.147 with SMTP id g19mr19559144qah.22.1360057813629; Tue, 05 Feb 2013 01:50:13 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Tue, 5 Feb 2013 01:50:13 -0800 (PST) In-Reply-To: <51108DB0.7050403@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> Date: Tue, 5 Feb 2013 10:50:13 +0100 X-Google-Sender-Auth: yS-ZolUl1huvmujpryWcbK530l0 Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: CeDeROM To: Karl Denninger Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 09:50:20 -0000 Just an idea - do you use "certified usb 2.0 cable" ? I had some problems many times using non-standard cables.. Try using "certified cable". Try using different keyboard/mouse, maybe they drain too much power from a single USB port that connects all those equipment... try to see how much power do they drain alone... it looks like a power problem.. but Im not an expert here and dont know the USB internals in FreeBSD sorry :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 11:59:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1B8BF67; Tue, 5 Feb 2013 11:59:59 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f177.google.com (mail-ob0-f177.google.com [209.85.214.177]) by mx1.freebsd.org (Postfix) with ESMTP id 888C5195; Tue, 5 Feb 2013 11:59:59 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id wc18so44941obb.36 for ; Tue, 05 Feb 2013 03:59:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VPGWAC0C2WRpwELWL7hbr/wg89lViGJTOZ4a6EcD6lU=; b=a4pNzFCUyTg7+74d32ZyDf63QQF3H/rXSHga465oDlz1RNBn9CFsF/1rX6TRmmwIqw 1tfS6WQ2eiUTDT0MBZrkuPSC9MYCGbj0E34fhIRU0/1rvVtnpOZ25oSRt1A6Pgift1Yf Hm35VeorxqSQxBtU+A3TLHzOA2SlxpaJW2Z26ArzNT4z3rw9+H96VxTZc+og19lnRXOw 4tHfzXF1w+iPLZxBr2uqR5YNBJX8ZJeSduhpSKDXhciw5qQd74J8CbNIzlsupY7Me4vx We4KQ/XmcWPExxLsNkT56//e2r4hCW7wkfi4SeYb7GADbwvNhMufjQYWou6ml+O72Mqg 3dhw== MIME-Version: 1.0 X-Received: by 10.60.32.200 with SMTP id l8mr19793805oei.43.1360065593775; Tue, 05 Feb 2013 03:59:53 -0800 (PST) Received: by 10.76.10.105 with HTTP; Tue, 5 Feb 2013 03:59:53 -0800 (PST) In-Reply-To: <510FBA51.9090806@gmail.com> References: <510E65FA.4040900@FreeBSD.org> <510FBA51.9090806@gmail.com> Date: Tue, 5 Feb 2013 12:59:53 +0100 Message-ID: Subject: Re: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: Volodymyr Kostyrko Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 12:00:00 -0000 On Mon, Feb 4, 2013 at 2:40 PM, Volodymyr Kostyrko wrote: > 03.02.2013 15:28, Dimitry Andric: > > Thanks for trying this out. Is there also a list of ports that *do* >> compile (and hopefully run) successfully? :-) >> > > I already switched to libc++ on my unstable STABLE-9 machines. Currently > I'm using this config: > > *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ > > audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer > devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw > graphics/tesseract lang/gcc multimedia/phonon-gstreamer > net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools > textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: > !CXXFLAGS | !LDFLAGS > > databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: > USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS > > www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS > snip > -- > Sphinx of black quartz, judge my vow. > Could you clarify where you have these settings? Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 12:07:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6B9D6D31; Tue, 5 Feb 2013 12:07:09 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by mx1.freebsd.org (Postfix) with ESMTP id B09F2282; Tue, 5 Feb 2013 12:07:08 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id go11so154631lbb.8 for ; Tue, 05 Feb 2013 04:07:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dhcs3YBr14Hdf7rka4VQHPuVaXAI8EobLXYMBXiZzOI=; b=sPh1nqfshgRzelpvzC87VBE9Vet0iFra0qo9IPjx6rxtwvoAy3Y+RhxyPkkxOSCwGg VT/hNgzx06YhEX1QKhar2wxoqWIIgUsyYxvzhkyfJAzvqFRiN5pDwioEvFHo47HvE+A/ eb7rFys0j/Oe4pP3cyay6IkoBUPJ8w4DNcgqfUDD7cfKw2rt2H2dkcR9/hCxI0oTTYJV Xl2/9t58nsPClCN4VWJL+yFcdOGHX932ftBuFz7Hqpd0KNqn5Yar0UT2NJvbiQQIN1Bd 0mPoTQwcQuOies3AvZ4igmiD5890xlpcvnW6836M6ziexnmgGaH2VCW3iam6sUksq185 Gqjw== X-Received: by 10.112.44.103 with SMTP id d7mr9800788lbm.101.1360066022287; Tue, 05 Feb 2013 04:07:02 -0800 (PST) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id v7sm2037050lbg.13.2013.02.05.04.07.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Feb 2013 04:07:01 -0800 (PST) Message-ID: <5110F5DE.9030204@gmail.com> Date: Tue, 05 Feb 2013 14:06:54 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: Andreas Nilsson Subject: Re: Ports and WITH_LIBCPLUSPLUS References: <510E65FA.4040900@FreeBSD.org> <510FBA51.9090806@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 12:07:09 -0000 05.02.2013 13:59, Andreas Nilsson: > Thanks for trying this out. Is there also a list of ports that *do* > compile (and hopefully run) successfully? :-) > > > I already switched to libc++ on my unstable STABLE-9 machines. > Currently I'm using this config: > > *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ > > audio/flac databases/db5 devel/binutils devel/doxygen > devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm > graphics/libopenraw graphics/tesseract lang/gcc > multimedia/phonon-gstreamer net-p2p/transmission-cli > net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell > www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS > > databases/mariadb-client emulators/pearpc www/libxul > x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS > > www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS > > snip > Could you clarify where you have these settings? This is my desktops that I use @home and @work. I'm not going that experimental on any production machine. -- Sphinx of black quartz, judge my vow. From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 13:06:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 470FEDEC; Tue, 5 Feb 2013 13:06:04 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id D110B7DB; Tue, 5 Feb 2013 13:06:03 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id l10so114403oag.16 for ; Tue, 05 Feb 2013 05:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qb+wI1P0VfzNBPpT2BlcpYOEP8ivQO/XOaThDXiJGIA=; b=b/Kum5WuRBf9xQyu92hbHpQhwey1WXW9ZruiVidSA89hJCFEdnrNDCvg1C/D7QMoGq ew3pNUTphK/aoLlxwODBH/rF/pcnbvhay2nfIZUnrFnCkCwwhgrp09mqlCaFjRKlxMUF c6pzFV/N7jKwlJIuJIq9dfD2KYJpzidsW03d7FfMt6UOaWm8XM4hxdKLsdpBZKkBVzt8 3lpdK06KJQHWWKHZLgtsuDkJqUDNL4Uz7rfUGJC1HtotthDmY9xeweC6uz5soJ27kaBk DbhcEukUhn/rqC1XP9qOzTa7otKeRmAyEzpjuJpoNgvFPLCH9fEePoeQuQzJ/Ux5FR4P S3UA== MIME-Version: 1.0 X-Received: by 10.182.54.46 with SMTP id g14mr17324929obp.55.1360069563130; Tue, 05 Feb 2013 05:06:03 -0800 (PST) Received: by 10.76.10.105 with HTTP; Tue, 5 Feb 2013 05:06:03 -0800 (PST) In-Reply-To: <5110F5DE.9030204@gmail.com> References: <510E65FA.4040900@FreeBSD.org> <510FBA51.9090806@gmail.com> <5110F5DE.9030204@gmail.com> Date: Tue, 5 Feb 2013 14:06:03 +0100 Message-ID: Subject: Re: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: Volodymyr Kostyrko Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 13:06:04 -0000 On Tue, Feb 5, 2013 at 1:06 PM, Volodymyr Kostyrko wrote: > 05.02.2013 13:59, Andreas Nilsson: > > > Thanks for trying this out. Is there also a list of ports that >> *do* >> compile (and hopefully run) successfully? :-) >> >> >> I already switched to libc++ on my unstable STABLE-9 machines. >> Currently I'm using this config: >> >> *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ >> >> audio/flac databases/db5 devel/binutils devel/doxygen >> devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm >> graphics/libopenraw graphics/tesseract lang/gcc >> multimedia/phonon-gstreamer net-p2p/transmission-cli >> net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell >> www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS >> >> databases/mariadb-client emulators/pearpc www/libxul >> x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS >> >> www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS >> >> snip >> > > Could you clarify where you have these settings? >> > > This is my desktops that I use @home and @work. I'm not going that > experimental on any production machine. > > > -- > Sphinx of black quartz, judge my vow. > Ah, sorry for being unclear. I meant which config files :) Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 13:35:02 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 387C06D8 for ; Tue, 5 Feb 2013 13:35:02 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id C0A84953 for ; Tue, 5 Feb 2013 13:35:01 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r15DYxR3070739; Tue, 5 Feb 2013 14:34:59 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r15DYwmf070738; Tue, 5 Feb 2013 14:34:58 +0100 (CET) (envelope-from olli) Date: Tue, 5 Feb 2013 14:34:58 +0100 (CET) Message-Id: <201302051334.r15DYwmf070738@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, John-Mark Gurney Subject: Re: re(4) problems with GA-H77N-WIFI In-Reply-To: <20130204221043.GU1410@funkthat.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 13:35:02 -0000 John-Mark Gurney wrote: > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100: > > John-Mark Gurney wrote: > > > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: > > > > I'm running a recent stable/9 (about 14 days old). > > > > What's the best way to debug this problem? At the > > > > moment I'm not even sure if it's the hardware, or if > > > > it's FreeBSD's fault (or my fault) ... > > > > > > Have you tried to disable msi and msix? > > > > > > hw.pci.enable_msix: 1 > > > hw.pci.enable_msi: 1 > > > > I tried these entries in /boot/loader.conf, according to > > the re(4) manual page: > > > > hw.re.msi_disable="1" > > hw.re.msix_disable="1" > > > > Unfortunately it didn't make a difference. > > Did you try in loader.conf: > hw.pci.enable_msix="0" > hw.pci.enable_msi="0" > > To disable MSI for the whole system? No, I haven't ... Will do that ASAP. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 14:54:15 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9E71CFAE; Tue, 5 Feb 2013 14:54:15 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id D97ACE4D; Tue, 5 Feb 2013 14:54:14 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id er20so244865lab.18 for ; Tue, 05 Feb 2013 06:54:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hfOjt4rNSURYTr1YDTou2C3V48/Sz3pHfM7AQ3Qgoh0=; b=EHkZg46wRqVZ4S6eeE0CKqlS7enWeGmqq1IjEf8UyBvP1TVjbDNhE/hPBESgwJoD8J PkPB7bfsIjhV4+mPdj2L462mxXoWLRUt+7fSgaYJs9xpfDiZ6Soo/jatdPVXuI12Aa/W 373f5Xw1dfgZK6SA66ZvmL4tBIl0b4LlgScQ9tk8q/DOMebnNAobrhYLCH8j08ykSnsE U7OtSDxoh5wgOFx0C8IPPvwJr8fLkGChBacFdn3B1pc/YEJfJTa215p+4W52Q/V+3MXe f7VUYw852fEEtC9PHxNqJIrNiZD/ITH2cTfEiXso9WCj+ujgOo8EJgVHrcnCZ1Ob/zwV aGNw== X-Received: by 10.112.42.37 with SMTP id k5mr9937032lbl.49.1360076053898; Tue, 05 Feb 2013 06:54:13 -0800 (PST) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id u5sm6724253lbm.8.2013.02.05.06.54.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Feb 2013 06:54:12 -0800 (PST) Message-ID: <51111D13.1020507@gmail.com> Date: Tue, 05 Feb 2013 16:54:11 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: Andreas Nilsson Subject: Re: Ports and WITH_LIBCPLUSPLUS References: <510E65FA.4040900@FreeBSD.org> <510FBA51.9090806@gmail.com> <5110F5DE.9030204@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 14:54:15 -0000 05.02.2013 15:06, Andreas Nilsson: > Ah, sorry for being unclear. I meant which config files :) I'm using ports-mgmt/portconf to keep track of all knobs. -- Sphinx of black quartz, judge my vow. From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 15:20:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5966A90B; Tue, 5 Feb 2013 15:20:00 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) by mx1.freebsd.org (Postfix) with ESMTP id 1A188FE2; Tue, 5 Feb 2013 15:19:59 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id ni5so260900obc.12 for ; Tue, 05 Feb 2013 07:19:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pEsXrwTpYJSU1kd9HurLJEhFTTisD1RTnPsuBzSw66w=; b=JCQPG1V5Gd4Rizn0htCrEjLL8Bb96IXyue4BzbY9zS77e4Dv/1VhD4impEGqbBJ9SZ 7qFHnuLSjTMaat77rYPwvgbXsdWEKrWiKx9KwoS2jVTVj1T2exopoGXdKsDQ4EgCBfmk +y0awiLP6VOr1sPIDbM71Pv2reCYG92a+b3JRDtG9YzzdelJ/IE8u55mJhbk1KBE2YLx 7KkzkZbiGgIt2EqPW3Aj6TGtP48rT/zRVsILDSqTzTEeK3ZajfhJH8dsj7mjlm/CCTQu QIw8l0a+Q5ahb7BblvXzvFpQPGcZAg6ZDpPTHhGljrGl9yHfBJSFmcXnsVdgju9MUvCx r8Rg== MIME-Version: 1.0 X-Received: by 10.60.8.134 with SMTP id r6mr19549767oea.53.1360077599393; Tue, 05 Feb 2013 07:19:59 -0800 (PST) Received: by 10.76.10.105 with HTTP; Tue, 5 Feb 2013 07:19:59 -0800 (PST) In-Reply-To: <51111D13.1020507@gmail.com> References: <510E65FA.4040900@FreeBSD.org> <510FBA51.9090806@gmail.com> <5110F5DE.9030204@gmail.com> <51111D13.1020507@gmail.com> Date: Tue, 5 Feb 2013 16:19:59 +0100 Message-ID: Subject: Re: Ports and WITH_LIBCPLUSPLUS From: Andreas Nilsson To: Volodymyr Kostyrko Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 15:20:00 -0000 On Tue, Feb 5, 2013 at 3:54 PM, Volodymyr Kostyrko wrote: > 05.02.2013 15:06, Andreas Nilsson: > > Ah, sorry for being unclear. I meant which config files :) >> > > I'm using ports-mgmt/portconf to keep track of all knobs. > > > -- > Sphinx of black quartz, judge my vow. > Thanks. I'll look into that, and how it will fit in with poudriere. Regards Andreas From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 16:19:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 040D4C8D for ; Tue, 5 Feb 2013 16:19:56 +0000 (UTC) (envelope-from chris#@1command.com) Received: from udns.ultimateDNS.NET (24-113-166-192.wavecable.com [24.113.166.192]) by mx1.freebsd.org (Postfix) with ESMTP id D2F25661 for ; Tue, 5 Feb 2013 16:19:54 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r15GFatV030613; Tue, 5 Feb 2013 08:15:42 -0800 (PST) (envelope-from chris#@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r15GFUtq030607; Tue, 5 Feb 2013 08:15:30 -0800 (PST) (envelope-from chris#@1command.com) Received: from udns.ultimatedns.net ([24.113.166.192]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Tue, 5 Feb 2013 08:15:30 -0800 (PST) Message-ID: In-Reply-To: <51108DB0.7050403@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> Date: Tue, 5 Feb 2013 08:15:30 -0800 (PST) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: "Chris H" To: "Karl Denninger" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 16:19:56 -0000 > On 2/4/2013 9:33 PM, Karl Denninger wrote: >> On 2/4/2013 9:02 PM, Karl Denninger wrote: >>> On 2/4/2013 4:32 PM, Charles Sprickman wrote: >>>> On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: >>>> >>>>> On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: >>>>>> On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: >>>>>> >>>>>>> On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: >>>>>>>> On 2/4/2013 2:06 PM, Ian Lepore wrote: >>>>>>>>> On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: >>>>>>>>>> ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD >>>>>>>>>> 9.1-STABLE #16 r244942 >>>>>>>>>> >>>>>>>>>> and it returns.... >>>>>>>>>> >>>>>>>>>> ugen4.4: at usbus4 >>>>>>>>>> uhub6: >>>>>>>>>> on usbus4 >>>>>>>>>> uhub_attach: port 1 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 2 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 3 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 4 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 5 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 6 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub_attach: port 7 power on failed, USB_ERR_STALLED >>>>>>>>>> uhub6: 7 ports with 7 removable, self powered >>>>>>>>>> >>>>>>>>>> Yuck. >>>>>>>>>> >>>>>>>>>> The last time it was working was on a FreeBSD 7 box (yeah, I know, >>>>>>>>>> rather old) but I never had problems there. And it appears that all of >>>>>>>>>> the device declarations that I used to have to put in the kernel as >>>>>>>>>> non-standard stuff are now in GENERIC, so I would expect it to work. >>>>>>>>>> >>>>>>>>>> Ideas as to what may have gotten hosed up here? >>>>>>>>>> >>>>>>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. >>>>>>>>> >>>>>>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and >>>>>>>>> 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's >>>>>>>>> parts program different vendor/product info and IDs have to be added to >>>>>>>>> code to recognize them, that's the only trouble one usually encounters. >>>>>>>>> >>>>>>>>> -- Ian >>>>>>>> Well, that sorta kinda worked. >>>>>>>> >>>>>>>> Except that it still is identifying it as a hub too, and the two collide >>>>>>>> and crash the stack. >>>>>>>> >>>>>>>> But I can't find anything that is looking at the PID (0x0050) or the >>>>>>>> definition (HUB_0050) anywhere in the code. >>>>>>>> >>>>>>>> I'll go pull the NEC defs and set up something else instead of simply >>>>>>>> adding it to the FTDI probe list. >>>>>>>> >>>>>>> It seems to me you have a problem with a hub (perhaps the root hub or a >>>>>>> motherboard hub if you don't have an external one) and this has nothing >>>>>>> to do with the ftdi device at all. >>>>>> I assume we're talking about a multi-port usb to serial adapter, correct? >>>>>> >>>>>> If so, they generally do have a hub included in the device. >>>>>> >>>>>> Example: >>>>>> >>>>>> ugen1.3: at usbus1 >>>>>> uhub4: on usbus1 >>>>>> uhub4: 7 ports with 7 removable, self powered >>>>>> >>>>>> Then the individual ports look like this: >>>>>> >>>>>> ugen1.4: at usbus1 >>>>>> uftdi0: on usbus1 >>>>>> ugen1.5: at usbus1 >>>>>> uftdi1: on usbus1 >>>>>> (etc.) >>>>>> >>>>>> We use these for serial console ports, they're (relatively) cheap and have generally >>>>>> been well supported. >>>>>> >>>>>> The above info is from an 8.3 box. >>>>>> >>>>>> Just wanted to clarify that there is likely a hub in the serial box Karl is working >>>>>> with… >>>>>> >>>>>> Charles >>>>> Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the >>>>> ftdi 4232 chip. I guess to get more ports than that, folks are now >>>>> using an internal hub and multiple ftdi chips. >>>> These multiport things have been around for a long time. Someone at ISC recommended >>>> them when we were looking to replace some unsupported RocketPort cards. Not affiliated >>>> with this place, but it's the largest collection of USB to serial stuff I've ever seen >>>> (and they document for the most part what chips are involved): >>>> >>>> http://usbgear.com/USB-Serial.html >>>> >>>> Our first 16 ports are on one of these: >>>> >>>> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >>>> (the tx/rx blinky lights are handy in troubleshooting) >>>> >>>> Then the rest on this cheaper model: >>>> >>>> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >>>> >>>>> So for some reason there's a problem with the hub, and that's probably >>>>> preventing it from getting as far as seeing the ftdi parts that are >>>>> downstream of that. >>>> My dmesg snippet is from the latter box. Note that the vendor and product ID are the >>>> same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no >>>> issues there (previously it was on a 4.11 box). >>>> >>>> Charles >>>> >>> That's the EXACT box. >>> >>> I've used them for a VERY long time on FreeBSD and they have always >>> worked perfectly well, but never on 9.x until now -- and it doesn't work >>> on 9.x. >>> >>> Had to run out for a while -- continuing testing. >> OK, with the kernel back the way it was, this is what I got: >> >> I plug in and get: >> >> Feb 4 21:17:46 FS kernel: uhub6: > 9/0, rev 2.00/1.00, addr 4> on usbus4 >> Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, >> USB_ERR_STALLED >> Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered >> >> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >> ugen4.4: at usbus4, cfg=0 md=HOST >> spd=HIGH (480Mbps) pwr=SAVE >> >> bLength = 0x0012 >> bDescriptorType = 0x0001 >> bcdUSB = 0x0200 >> bDeviceClass = 0x0009 >> bDeviceSubClass = 0x0000 >> bDeviceProtocol = 0x0001 >> bMaxPacketSize0 = 0x0040 >> idVendor = 0x0409 >> idProduct = 0x0050 >> bcdDevice = 0x0100 >> iManufacturer = 0x0000 >> iProduct = 0x0000 >> iSerialNumber = 0x0000 >> bNumConfigurations = 0x0001 >> >> I then issue and get: >> FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on >> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >> ugen4.4: at usbus4, cfg=0 md=HOST >> spd=HIGH (480Mbps) pwr=ON >> >> bLength = 0x0012 >> bDescriptorType = 0x0001 >> bcdUSB = 0x0200 >> bDeviceClass = 0x0009 >> bDeviceSubClass = 0x0000 >> bDeviceProtocol = 0x0001 >> bMaxPacketSize0 = 0x0040 >> idVendor = 0x0409 >> idProduct = 0x0050 >> bcdDevice = 0x0100 >> iManufacturer = 0x0000 >> iProduct = 0x0000 >> iSerialNumber = 0x0000 >> bNumConfigurations = 0x0001 >> >> And if I turn it off and back on (power_off then power_on) the cycle >> repeats. An attempt to reset is also futile, although the command is >> accepted. >> >> If I turn on hw.usb.uhub.debug I get a never-ending string of these: >> >> Feb 4 21:29:12 FS kernel: usb_needs_explore: >> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:12 FS kernel: usb_needs_explore: >> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:12 FS kernel: usb_needs_explore: >> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:12 FS kernel: usb_needs_explore: >> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:12 FS kernel: usb_needs_explore: >> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:13 FS kernel: usb_needs_explore: >> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:13 FS kernel: usb_needs_explore: >> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:13 FS kernel: usb_needs_explore: >> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> Feb 4 21:29:13 FS kernel: usb_needs_explore: >> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >> >> Until the power is turned off on the device (with "usbconfig -u 4 -a 4 >> power_off"), when it settles down to this once in a while: >> >> Feb 4 21:29:26 FS kernel: usb_needs_explore: >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >> Feb 4 21:29:26 FS kernel: usb_needs_explore: >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 >> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >> > Ok, bizarro-land update. > > The KVM (which talks to the box over USB for keyboard and mouse) > interferes with the FTDI adapter! > > I have absolutely NO idea why, but if it's not plugged in the FTDI > adapter comes up instantly. Of course then I can't KVM into the box, > which creates its own set of problems. > > ARGH. > > Ok, now to figure out how to run this down. There has to be a way..... > ideas? Smells like power supply, to me. Consider trying a different one, or better; use one with a higher output rating. :) --Chris > > -- > -- Karl Denninger > /The Market Ticker ®/ > Cuda Systems LLC > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 16:24:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9AB00E34 for ; Tue, 5 Feb 2013 16:24:41 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 2BB2B6BC for ; Tue, 5 Feb 2013 16:24:40 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r15GOd55034138 for ; Tue, 5 Feb 2013 10:24:40 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Tue Feb 5 10:24:40 2013 Message-ID: <51113242.4060003@denninger.net> Date: Tue, 05 Feb 2013 10:24:34 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> In-Reply-To: X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130205-0, 02/05/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 16:24:41 -0000 On 2/5/2013 10:15 AM, Chris H wrote: >> On 2/4/2013 9:33 PM, Karl Denninger wrote: >>> On 2/4/2013 9:02 PM, Karl Denninger wrote: >>>> On 2/4/2013 4:32 PM, Charles Sprickman wrote: >>>>> These multiport things have been around for a long time. Someone at ISC recommended >>>>> them when we were looking to replace some unsupported RocketPort cards. Not affiliated >>>>> with this place, but it's the largest collection of USB to serial stuff I've ever seen >>>>> (and they document for the most part what chips are involved): >>>>> >>>>> http://usbgear.com/USB-Serial.html >>>>> >>>>> Our first 16 ports are on one of these: >>>>> >>>>> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >>>>> (the tx/rx blinky lights are handy in troubleshooting) >>>>> >>>>> Then the rest on this cheaper model: >>>>> >>>>> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >>>>> >>>>>> So for some reason there's a problem with the hub, and that's probably >>>>>> preventing it from getting as far as seeing the ftdi parts that are >>>>>> downstream of that. >>>>> My dmesg snippet is from the latter box. Note that the vendor and product ID are the >>>>> same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no >>>>> issues there (previously it was on a 4.11 box). >>>>> >>>>> Charles >>>>> >>>> That's the EXACT box. >>>> >>>> I've used them for a VERY long time on FreeBSD and they have always >>>> worked perfectly well, but never on 9.x until now -- and it doesn't work >>>> on 9.x. >>>> >>>> Had to run out for a while -- continuing testing. >>> OK, with the kernel back the way it was, this is what I got: >>> >>> I plug in and get: >>> >>> Feb 4 21:17:46 FS kernel: uhub6: >> 9/0, rev 2.00/1.00, addr 4> on usbus4 >>> Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, >>> USB_ERR_STALLED >>> Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered >>> >>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>> ugen4.4: at usbus4, cfg=0 md=HOST >>> spd=HIGH (480Mbps) pwr=SAVE >>> >>> bLength = 0x0012 >>> bDescriptorType = 0x0001 >>> bcdUSB = 0x0200 >>> bDeviceClass = 0x0009 >>> bDeviceSubClass = 0x0000 >>> bDeviceProtocol = 0x0001 >>> bMaxPacketSize0 = 0x0040 >>> idVendor = 0x0409 >>> idProduct = 0x0050 >>> bcdDevice = 0x0100 >>> iManufacturer = 0x0000 >>> iProduct = 0x0000 >>> iSerialNumber = 0x0000 >>> bNumConfigurations = 0x0001 >>> >>> I then issue and get: >>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on >>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>> ugen4.4: at usbus4, cfg=0 md=HOST >>> spd=HIGH (480Mbps) pwr=ON >>> >>> bLength = 0x0012 >>> bDescriptorType = 0x0001 >>> bcdUSB = 0x0200 >>> bDeviceClass = 0x0009 >>> bDeviceSubClass = 0x0000 >>> bDeviceProtocol = 0x0001 >>> bMaxPacketSize0 = 0x0040 >>> idVendor = 0x0409 >>> idProduct = 0x0050 >>> bcdDevice = 0x0100 >>> iManufacturer = 0x0000 >>> iProduct = 0x0000 >>> iSerialNumber = 0x0000 >>> bNumConfigurations = 0x0001 >>> >>> And if I turn it off and back on (power_off then power_on) the cycle >>> repeats. An attempt to reset is also futile, although the command is >>> accepted. >>> >>> If I turn on hw.usb.uhub.debug I get a never-ending string of these: >>> >>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>> >>> Until the power is turned off on the device (with "usbconfig -u 4 -a 4 >>> power_off"), when it settles down to this once in a while: >>> >>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 >>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>> >> Ok, bizarro-land update. >> >> The KVM (which talks to the box over USB for keyboard and mouse) >> interferes with the FTDI adapter! >> >> I have absolutely NO idea why, but if it's not plugged in the FTDI >> adapter comes up instantly. Of course then I can't KVM into the box, >> which creates its own set of problems. >> >> ARGH. >> >> Ok, now to figure out how to run this down. There has to be a way..... >> ideas? > Smells like power supply, to me. Consider trying a different one, or better; > use one with a higher output rating. :) > > --Chris Uh, definitely not. Confirmed on multiple boxes now, all running 9.1-Stable. The KVM, if connected, zorches the FTDI box. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 16:27:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 71FC9F68 for ; Tue, 5 Feb 2013 16:27:18 +0000 (UTC) (envelope-from chrish@UltimateDNS.NET) Received: from udns.ultimateDNS.NET (24-113-166-192.wavecable.com [24.113.166.192]) by mx1.freebsd.org (Postfix) with ESMTP id 23E286E6 for ; Tue, 5 Feb 2013 16:27:17 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r15GR6HP031244; Tue, 5 Feb 2013 08:27:12 -0800 (PST) (envelope-from chrish@UltimateDNS.NET) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r15GR1o3031241; Tue, 5 Feb 2013 08:27:01 -0800 (PST) (envelope-from chrish@UltimateDNS.NET) Received: from udns.ultimatedns.net ([24.113.166.192]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Tue, 5 Feb 2013 08:27:01 -0800 (PST) Message-ID: <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> In-Reply-To: <51113242.4060003@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> Date: Tue, 5 Feb 2013 08:27:01 -0800 (PST) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] From: chrish@UltimateDNS.NET To: "Karl Denninger" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 16:27:18 -0000 > > On 2/5/2013 10:15 AM, Chris H wrote: >>> On 2/4/2013 9:33 PM, Karl Denninger wrote: >>>> On 2/4/2013 9:02 PM, Karl Denninger wrote: >>>>> On 2/4/2013 4:32 PM, Charles Sprickman wrote: >>>>>> These multiport things have been around for a long time. Someone at ISC recommended >>>>>> them when we were looking to replace some unsupported RocketPort cards. Not >>>>>> affiliated >>>>>> with this place, but it's the largest collection of USB to serial stuff I've ever seen >>>>>> (and they document for the most part what chips are involved): >>>>>> >>>>>> http://usbgear.com/USB-Serial.html >>>>>> >>>>>> Our first 16 ports are on one of these: >>>>>> >>>>>> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >>>>>> (the tx/rx blinky lights are handy in troubleshooting) >>>>>> >>>>>> Then the rest on this cheaper model: >>>>>> >>>>>> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >>>>>> >>>>>>> So for some reason there's a problem with the hub, and that's probably >>>>>>> preventing it from getting as far as seeing the ftdi parts that are >>>>>>> downstream of that. >>>>>> My dmesg snippet is from the latter box. Note that the vendor and product ID are the >>>>>> same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no >>>>>> issues there (previously it was on a 4.11 box). >>>>>> >>>>>> Charles >>>>>> >>>>> That's the EXACT box. >>>>> >>>>> I've used them for a VERY long time on FreeBSD and they have always >>>>> worked perfectly well, but never on 9.x until now -- and it doesn't work >>>>> on 9.x. >>>>> >>>>> Had to run out for a while -- continuing testing. >>>> OK, with the kernel back the way it was, this is what I got: >>>> >>>> I plug in and get: >>>> >>>> Feb 4 21:17:46 FS kernel: uhub6: >>> 9/0, rev 2.00/1.00, addr 4> on usbus4 >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered >>>> >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>>> ugen4.4: at usbus4, cfg=0 md=HOST >>>> spd=HIGH (480Mbps) pwr=SAVE >>>> >>>> bLength = 0x0012 >>>> bDescriptorType = 0x0001 >>>> bcdUSB = 0x0200 >>>> bDeviceClass = 0x0009 >>>> bDeviceSubClass = 0x0000 >>>> bDeviceProtocol = 0x0001 >>>> bMaxPacketSize0 = 0x0040 >>>> idVendor = 0x0409 >>>> idProduct = 0x0050 >>>> bcdDevice = 0x0100 >>>> iManufacturer = 0x0000 >>>> iProduct = 0x0000 >>>> iSerialNumber = 0x0000 >>>> bNumConfigurations = 0x0001 >>>> >>>> I then issue and get: >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>>> ugen4.4: at usbus4, cfg=0 md=HOST >>>> spd=HIGH (480Mbps) pwr=ON >>>> >>>> bLength = 0x0012 >>>> bDescriptorType = 0x0001 >>>> bcdUSB = 0x0200 >>>> bDeviceClass = 0x0009 >>>> bDeviceSubClass = 0x0000 >>>> bDeviceProtocol = 0x0001 >>>> bMaxPacketSize0 = 0x0040 >>>> idVendor = 0x0409 >>>> idProduct = 0x0050 >>>> bcdDevice = 0x0100 >>>> iManufacturer = 0x0000 >>>> iProduct = 0x0000 >>>> iSerialNumber = 0x0000 >>>> bNumConfigurations = 0x0001 >>>> >>>> And if I turn it off and back on (power_off then power_on) the cycle >>>> repeats. An attempt to reset is also futile, although the command is >>>> accepted. >>>> >>>> If I turn on hw.usb.uhub.debug I get a never-ending string of these: >>>> >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> >>>> Until the power is turned off on the device (with "usbconfig -u 4 -a 4 >>>> power_off"), when it settles down to this once in a while: >>>> >>>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> >>> Ok, bizarro-land update. >>> >>> The KVM (which talks to the box over USB for keyboard and mouse) >>> interferes with the FTDI adapter! >>> >>> I have absolutely NO idea why, but if it's not plugged in the FTDI >>> adapter comes up instantly. Of course then I can't KVM into the box, >>> which creates its own set of problems. >>> >>> ARGH. >>> >>> Ok, now to figure out how to run this down. There has to be a way..... >>> ideas? >> Smells like power supply, to me. Consider trying a different one, or better; >> use one with a higher output rating. :) >> >> --Chris > Uh, definitely not. > > Confirmed on multiple boxes now, all running 9.1-Stable. The KVM, if > connected, zorches the FTDI box. Understood. I was referring to the _computers_ power supply. :) --Chris > > -- > -- Karl Denninger > /The Market Ticker ®/ > Cuda Systems LLC > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 16:28:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3AC69114 for ; Tue, 5 Feb 2013 16:28:57 +0000 (UTC) (envelope-from chris#@1command.com) Received: from udns.ultimateDNS.NET (24-113-166-192.wavecable.com [24.113.166.192]) by mx1.freebsd.org (Postfix) with ESMTP id 06047710 for ; Tue, 5 Feb 2013 16:28:56 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r15GSj6g031332; Tue, 5 Feb 2013 08:28:51 -0800 (PST) (envelope-from chris#@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r15GSds7031326; Tue, 5 Feb 2013 08:28:39 -0800 (PST) (envelope-from chris#@1command.com) Received: from udns.ultimatedns.net ([24.113.166.192]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Tue, 5 Feb 2013 08:28:40 -0800 (PST) Message-ID: In-Reply-To: <51113242.4060003@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> Date: Tue, 5 Feb 2013 08:28:40 -0800 (PST) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] From: "Chris H" To: "Karl Denninger" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 16:28:57 -0000 > > On 2/5/2013 10:15 AM, Chris H wrote: >>> On 2/4/2013 9:33 PM, Karl Denninger wrote: >>>> On 2/4/2013 9:02 PM, Karl Denninger wrote: >>>>> On 2/4/2013 4:32 PM, Charles Sprickman wrote: >>>>>> These multiport things have been around for a long time. Someone at ISC recommended >>>>>> them when we were looking to replace some unsupported RocketPort cards. Not >>>>>> affiliated >>>>>> with this place, but it's the largest collection of USB to serial stuff I've ever seen >>>>>> (and they document for the most part what chips are involved): >>>>>> >>>>>> http://usbgear.com/USB-Serial.html >>>>>> >>>>>> Our first 16 ports are on one of these: >>>>>> >>>>>> http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 >>>>>> (the tx/rx blinky lights are handy in troubleshooting) >>>>>> >>>>>> Then the rest on this cheaper model: >>>>>> >>>>>> http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-M&cats=199&catid=494%2C199%2C474%2C2345%2C1009 >>>>>> >>>>>>> So for some reason there's a problem with the hub, and that's probably >>>>>>> preventing it from getting as far as seeing the ftdi parts that are >>>>>>> downstream of that. >>>>>> My dmesg snippet is from the latter box. Note that the vendor and product ID are the >>>>>> same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no >>>>>> issues there (previously it was on a 4.11 box). >>>>>> >>>>>> Charles >>>>>> >>>>> That's the EXACT box. >>>>> >>>>> I've used them for a VERY long time on FreeBSD and they have always >>>>> worked perfectly well, but never on 9.x until now -- and it doesn't work >>>>> on 9.x. >>>>> >>>>> Had to run out for a while -- continuing testing. >>>> OK, with the kernel back the way it was, this is what I got: >>>> >>>> I plug in and get: >>>> >>>> Feb 4 21:17:46 FS kernel: uhub6: >>> 9/0, rev 2.00/1.00, addr 4> on usbus4 >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, >>>> USB_ERR_STALLED >>>> Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered >>>> >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>>> ugen4.4: at usbus4, cfg=0 md=HOST >>>> spd=HIGH (480Mbps) pwr=SAVE >>>> >>>> bLength = 0x0012 >>>> bDescriptorType = 0x0001 >>>> bcdUSB = 0x0200 >>>> bDeviceClass = 0x0009 >>>> bDeviceSubClass = 0x0000 >>>> bDeviceProtocol = 0x0001 >>>> bMaxPacketSize0 = 0x0040 >>>> idVendor = 0x0409 >>>> idProduct = 0x0050 >>>> bcdDevice = 0x0100 >>>> iManufacturer = 0x0000 >>>> iProduct = 0x0000 >>>> iSerialNumber = 0x0000 >>>> bNumConfigurations = 0x0001 >>>> >>>> I then issue and get: >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 power_on >>>> FS/karl:/disk/karl> usbconfig -u 4 -a 4 dump_device_desc >>>> ugen4.4: at usbus4, cfg=0 md=HOST >>>> spd=HIGH (480Mbps) pwr=ON >>>> >>>> bLength = 0x0012 >>>> bDescriptorType = 0x0001 >>>> bcdUSB = 0x0200 >>>> bDeviceClass = 0x0009 >>>> bDeviceSubClass = 0x0000 >>>> bDeviceProtocol = 0x0001 >>>> bMaxPacketSize0 = 0x0040 >>>> idVendor = 0x0409 >>>> idProduct = 0x0050 >>>> bcdDevice = 0x0100 >>>> iManufacturer = 0x0000 >>>> iProduct = 0x0000 >>>> iSerialNumber = 0x0000 >>>> bNumConfigurations = 0x0001 >>>> >>>> And if I turn it off and back on (power_off then power_on) the cycle >>>> repeats. An attempt to reset is also futile, although the command is >>>> accepted. >>>> >>>> If I turn on hw.usb.uhub.debug I get a never-ending string of these: >>>> >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:12 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> Feb 4 21:29:13 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 >>>> >>>> Until the power is turned off on the device (with "usbconfig -u 4 -a 4 >>>> power_off"), when it settles down to this once in a while: >>>> >>>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_needs_explore: >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6440cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6451cf0 >>>> Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks >>>> >>> Ok, bizarro-land update. >>> >>> The KVM (which talks to the box over USB for keyboard and mouse) >>> interferes with the FTDI adapter! >>> >>> I have absolutely NO idea why, but if it's not plugged in the FTDI >>> adapter comes up instantly. Of course then I can't KVM into the box, >>> which creates its own set of problems. >>> >>> ARGH. >>> >>> Ok, now to figure out how to run this down. There has to be a way..... >>> ideas? >> Smells like power supply, to me. Consider trying a different one, or better; >> use one with a higher output rating. :) >> >> --Chris > Uh, definitely not. > > Confirmed on multiple boxes now, all running 9.1-Stable. The KVM, if > connected, zorches the FTDI box. Understood. I was referring to the _computers_ power supply. :) --Chris P.S. sorry for the duplicate, I used the wrong _from_address in the other. :/ > > -- > -- Karl Denninger > /The Market Ticker ®/ > Cuda Systems LLC > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 16:44:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 32E897EB for ; Tue, 5 Feb 2013 16:44:22 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id DE42A819 for ; Tue, 5 Feb 2013 16:44:21 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id b4so177921qen.18 for ; Tue, 05 Feb 2013 08:44:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=v9Pr2/g9rZSv0mRUG2Fvl02FsipLmKpewxP2MagdtUs=; b=GClamxbwkSFYeqCBar3WdynrQkTLXnWmAte5H5aLSzzXM9Bvxe+aecxPkPN1Q/GZQH tFnobbwnxIaoxMf24UYRObg8YjIREmiGigMiy60/X1g57OqgX2L/W3KhMa8RS1k5/Gb4 t39hy5wFOXC3qgVTTXN24Moyazfas6fDi8elJm8z0k23RY2VXlFQkGdN4E4+lGpPzyyy Rkao/7usUolP73vYnQLcAV8WULejTyoltX00lDWQ5wsln3NQX1fOJhMW5FkG4N4gYwSl c4wki2Uagi4Ss+dpdkcKMIGwsE4YEL6UqeDfYm5hANFCcBEMElCa5BayIQ2xkLAK33rP 6SjQ== MIME-Version: 1.0 X-Received: by 10.229.177.14 with SMTP id bg14mr4789423qcb.51.1360082661054; Tue, 05 Feb 2013 08:44:21 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Tue, 5 Feb 2013 08:44:20 -0800 (PST) In-Reply-To: <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> Date: Tue, 5 Feb 2013 17:44:20 +0100 X-Google-Sender-Auth: watNmcRyUIupq7kCNRcuI2ecgOw Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] From: CeDeROM To: chrish@ultimatedns.net Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org, Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 16:44:22 -0000 On Tue, Feb 5, 2013 at 5:27 PM, wrote: > Understood. I was referring to the _computers_ power supply. :) Still it may be caused by some issued on the USB bus power management. Normally an USB port can supply 500mA of current. Above that port should be disabled by the host if I remember correctly. If there is a hub inside the serial port adapter it would be good to know it it is powered directly from the USB port or does it have its own power supply... There could be too much power drain from the USB port by external devices attached to the hub/adapter. But this would be rather obvious. There may be some misunderstanding between USB Host and the self powered USB device, so they cannot agree on the power supply level, which seems more probable :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 17:09:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51EBEA22 for ; Tue, 5 Feb 2013 17:09:43 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 0242D9A8 for ; Tue, 5 Feb 2013 17:09:42 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r15H9gG6036738 for ; Tue, 5 Feb 2013 11:09:43 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Tue Feb 5 11:09:43 2013 Message-ID: <51113CD1.40104@denninger.net> Date: Tue, 05 Feb 2013 11:09:37 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> In-Reply-To: X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130205-0, 02/05/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 17:09:43 -0000 On 2/5/2013 10:44 AM, CeDeROM wrote: > On Tue, Feb 5, 2013 at 5:27 PM, wrote: >> Understood. I was referring to the _computers_ power supply. :) > Still it may be caused by some issued on the USB bus power management. > Normally an USB port can supply 500mA of current. Above that port > should be disabled by the host if I remember correctly. If there is a > hub inside the serial port adapter it would be good to know it it is > powered directly from the USB port or does it have its own power > supply... > > There could be too much power drain from the USB port by external > devices attached to the hub/adapter. But this would be rather obvious. > > There may be some misunderstanding between USB Host and the self > powered USB device, so they cannot agree on the power supply level, > which seems more probable :-) The FTDI adapter has the provision for an external power supply (+5V) but it does not require it unless you're running off an unpowered bus, which is not normally the case. 500ma is quite a bit of available energy. I suspect the issue is found in the KVM, which attaches as a "low" speed device; I'm going to see if I have the same issue with other USB devices connected while the KVM is on the box. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 17:24:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3A6CF249 for ; Tue, 5 Feb 2013 17:24:49 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1772AA7A for ; Tue, 5 Feb 2013 17:24:49 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 67211B9BA; Tue, 5 Feb 2013 12:24:48 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: problems with the mfi Date: Tue, 5 Feb 2013 12:24:33 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201302051224.33779.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 05 Feb 2013 12:24:48 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 17:24:49 -0000 On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: > after rebooting I get very often: > ... > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS > ... > > another reboot usualy fixes this. Does it have the latest firmware? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 17:31:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 031A85C4 for ; Tue, 5 Feb 2013 17:31:54 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qa0-f43.google.com (mail-qa0-f43.google.com [209.85.216.43]) by mx1.freebsd.org (Postfix) with ESMTP id 89CB8AEC for ; Tue, 5 Feb 2013 17:31:53 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id dx4so1902617qab.2 for ; Tue, 05 Feb 2013 09:31:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XheTZKhqbSUUi3PTYHx3DwkQJJrkn1nxBDOVE7iH9lo=; b=FmU5aN2i4UAGJfSbnSUXMMKsYE0q07ORFyJOuN9eAMgKJqpVP3wExcoAO8hAAhomkI R324ao1SvJBOq6Egc9L+HRNgy5cDmCAkX0fz84pP8kndOREZQeYe7PzDZVX4cAXKzZte LNVRqgFrUwDv8btIbCixqkgv19RkWSyJ/tnhx/yezfni2Yy0GacHVM+JZsJg0mnfpeBD bv+SwUCioGPs3EI88h7ApXoLLHpVLWNgYLh3TEL1eAM4Ou9M5dhhrqTcm2mdfmJHNkLo Pub/t0a8fEzpI1JkmlxytRyPrHOBpOqSPj86lrTiDwwxJp4Gv951+FloQMHOQsN1Ob4E gk3A== MIME-Version: 1.0 X-Received: by 10.224.209.193 with SMTP id gh1mr20058347qab.86.1360085112781; Tue, 05 Feb 2013 09:25:12 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Tue, 5 Feb 2013 09:25:12 -0800 (PST) In-Reply-To: <51113CD1.40104@denninger.net> References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> <51113CD1.40104@denninger.net> Date: Tue, 5 Feb 2013 18:25:12 +0100 X-Google-Sender-Auth: mUlOsQF54V1ptwiGNhYxhaSrkhU Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] From: CeDeROM To: Karl Denninger Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 17:31:54 -0000 On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger wrote: > The FTDI adapter has the provision for an external power supply (+5V) > but it does not require it unless you're running off an unpowered bus, > which is not normally the case. 500ma is quite a bit of available energy. Karl, can you please use external power supply to power up the adapter - with and without the additional devices step by step - this way we will eliminate one of the possible causes :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 18:10:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 37E25FE9; Tue, 5 Feb 2013 18:10:04 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 2C303DB5; Tue, 5 Feb 2013 18:10:03 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so393744wey.30 for ; Tue, 05 Feb 2013 10:10:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=X5OMAZIQ/75vo4nbQQQWrCqgYOb1UvyrKNbnecSn6Do=; b=A8TZMljhfnInDUiXjlxkIaoGIsxvBehOJ5YesGNv7lNmkjEz3h1eDpeX3BcrMb1aqo DO3cMxCsQZh81xYve5wDprGFfrxU7/lgHioZbWQO4mdrGZiKXjKnzjt0Snm0V1rggwLv EHo7FK5XPSHaSwBhZhGdLJ/codLpJyguKpWZCjstekrI62agd16eIUN0FE+2YenHlAxA IzcXBhMvK8+nnS5h1AQmKTnDdxBbcRNgiSKsIT0slaemtYLf3u80cC4LFhpmOaF4l8Q/ /dCiOKN+GOGCHvYxrMSO/OKOWxsTp9oAM6lWFwV1QbqmZpvXdbhYo4Y67Tpstava+ctt WeNA== MIME-Version: 1.0 X-Received: by 10.180.101.98 with SMTP id ff2mr258382wib.0.1360087799306; Tue, 05 Feb 2013 10:09:59 -0800 (PST) Received: by 10.216.172.197 with HTTP; Tue, 5 Feb 2013 10:09:59 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Feb 2013 20:09:59 +0200 Message-ID: Subject: Re: stable/9 r245439 breaks security/pam_ssh_agent_auth on stable/9 (WAS: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9) From: Kimmo Paasiala To: Chris Rees Content-Type: text/plain; charset=UTF-8 Cc: Brooks Davis , FreeBSD , Stefan Bethke , Dimitry Andric , FreeBSD Ports , Mark Linimon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 18:10:04 -0000 On Tue, Feb 5, 2013 at 12:36 AM, Kimmo Paasiala wrote: > On Sun, Feb 3, 2013 at 7:22 PM, Chris Rees wrote: >> On 3 February 2013 17:15, Stefan Bethke wrote: >>> >>> Am 03.02.2013 um 10:57 schrieb Chris Rees : >>> >>>> On 3 February 2013 03:55, Kimmo Paasiala wrote: >>>>> >>>>> There is no PR yet with my fix and therefor no commit to ports tree >>>>> that would fix the problem. I'll file a PR soon (TM). >>>> >>>> The problem was in base, and is fixed there. >>> >>> Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. >>> >>> Is there some confusion about which problem is addressed by Kimmo's patch? >>> >> >> Hm, perhaps it might be necessary then. >> >> Kimmo, please would you submit the patch you had as a PR? I'm sure >> Wesley would appreciate the hint. >> >> Chris > > I'll file a PR when I have recovered from a nasty flu. Right now I'm > not fit for thinking... > > I changed the title of this thread to a better one. > > -Kimmo It looks like the port was updated just recently to a new version that has its own problems that are no longer related strnvis(3). I'll have to give up for now. (freebsd-ports added to cc:) -Kimmo From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 19:38:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 89780741 for ; Tue, 5 Feb 2013 19:38:38 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by mx1.freebsd.org (Postfix) with ESMTP id 5FE39276 for ; Tue, 5 Feb 2013 19:38:38 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id bh2so323953pad.16 for ; Tue, 05 Feb 2013 11:38:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:from:to:cc:references:in-reply-to:subject :date:organization:mime-version:content-type :content-transfer-encoding:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole:x-gm-message-state; bh=0aYwFLvNQoijSAA1+AH/uA0fEDvEOMDpv22CuAvrwAE=; b=K4FLyO3Cj5pf7Dwe2AMSFKBD5PUnoATgERBnApLMlH43Wap9W1KxT3J+2wpgBNopn7 Gp0GtzFVZekU+rAZSv4q/W3rmSGz2zeWyz3rxuZIHdQOTHOc9zb5kicicSJxRwrqy+nW tA1Rz6vnJH0nXlYn14e2M3FMPfkFZYmg61EZMYhFVOHaBplcG0J++GK66GNNvT5CdKfq vbkUCBfySpUILMOA1u/CqLpsXKo6crTPDKrGKy8vlSlDDSicAJGlkeTQSEZWfng/5oAg WHiVlm5sRzDY13vfVMoMGdGAogIX34WKWYWSG0omCBbnWyqco0mUxa3Ydxo5nEI5ZVgR SqEw== X-Received: by 10.66.81.199 with SMTP id c7mr67236296pay.39.1360093111781; Tue, 05 Feb 2013 11:38:31 -0800 (PST) Received: from CMOTUM25PC ([187.210.81.114]) by mx.google.com with ESMTPS id t7sm28051142pax.17.2013.02.05.11.38.29 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 11:38:30 -0800 (PST) Message-ID: From: =?iso-8859-1?Q?Efra=EDn_D=E9ctor?= To: "Kubilay Kocak" References: <5108E720.70705@gmail.com> <510A65F5.9070706@gmail.com> In-Reply-To: <510A65F5.9070706@gmail.com> Subject: Re: About kern.ipc.somaxconn and netstat Date: Tue, 5 Feb 2013 13:38:28 -0600 Organization: =?iso-8859-1?Q?HESA_T=E9cnica?= MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-Gm-Message-State: ALoCoQmuhYU0BS2hHZsy1e+QgPQP8C4P2xwkydezRKiMF3wtolOTvKglx6MemmDJ0Z3KR6f6WGYg Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 19:38:38 -0000 Hello. Sorry for the very late answer. That is a very good command, thank you for your recommendation. All the time that I have executed it it shows "0 listen queue overflows" so I guess our configuration is working. Thank you so much. -----Mensaje original----- From: Kubilay Kocak Sent: Thursday, January 31, 2013 6:39 AM To: Efraín Déctor Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat On 31/01/2013 4:54 AM, Efraín Déctor wrote: > -----Mensaje original----- From: Kubilay Kocak > Sent: Wednesday, January 30, 2013 3:25 AM > To: Efraín Déctor > Cc: freebsd-stable@freebsd.org > Subject: Re: About kern.ipc.somaxconn and netstat > > On 30/01/2013 12:26 PM, Efraín Déctor wrote: >> Hello. >> >> We have a webserver using FreeBSD, we read about tunning >> kern.ipc.somaxconn >> (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html) >> so the OS can handle all the connections. Is there a way to know how >> many connections are established in a certain moment?. I know about >> netstat(1) but is there any other command that we can use to know the >> exact amount of how many connections are established?. >> > This one might help: > > kern.ipc.numopensockets: Number of open sockets > > It's usefulness will depend on the granularity you require (in only, out > only, established only, etc) but it's always represented system-wide > resource consumption very well (matching observed workloads - baseline value>) > > > Thank you, it is very helpfull, using kern.ipc.numopensockets with > sockstat(1) and netstat(1) will give me a clue to tune kern.ipc.somaxconn > > Thank you all. Also, if you haven't already come across this one in your netstat travels, this one directly reports listen queue overflows: netstat -s -p tcp |grep listen -- Ta, Koobs From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 21:36:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 10FABF1 for ; Tue, 5 Feb 2013 21:36:00 +0000 (UTC) (envelope-from contatoshark@gmail.com) Received: from mail-gh0-f177.google.com (mail-gh0-f177.google.com [209.85.160.177]) by mx1.freebsd.org (Postfix) with ESMTP id 954B1961 for ; Tue, 5 Feb 2013 21:35:59 +0000 (UTC) Received: by mail-gh0-f177.google.com with SMTP id g22so204452ghb.36 for ; Tue, 05 Feb 2013 13:35:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:mime-version:subject:from:to:message-id :original-recipient:content-type; bh=AfVJzhbxcsBtzWez6brv5kNEQusV+ZtcI/hHiHKO0yA=; b=QCNwLBwH637BoVAarnpyhmEklcPTuG/t9PP6zw9YsxfFlagnFgZLl0IHK7AO9b2KZ8 dTltc/pFMTPnJwg4MZe5cllJlVx0znWEal7Y4JsVrB7LLw5p2vvHGbpcLnMtkh3Qizaf bwuoaVaHM6Otm3kGvXlu9R3FEUz9C1LSBTy4KpsXJUTcFARdbRouTWMgYtsJtn0zXsQa EQcHFaGZvn+OdlTelnBroyjCcgAIaPjrpSf6mLzum+5Y+jkpWVDgp3P0cSaAYxg51kiq ufaPx20yUXiIe+0z9OFl9Amd2vMHE6xvvo/jYRd0epi5A1bqPwlxJf83Twb8MF5GQozo mENg== X-Received: by 10.101.27.34 with SMTP id e34mr9122616anj.25.1360100153659; Tue, 05 Feb 2013 13:35:53 -0800 (PST) Received: from [192.168.1.7] (200-97-241-165.user.veloxzone.com.br. [200.97.241.165]) by mx.google.com with ESMTPS id r17sm20104185ani.8.2013.02.05.13.35.40 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 13:35:52 -0800 (PST) Date: Tue, 5 Feb 2013 19:35:38 -0200 Mime-version: 1.0 Subject: =?ISO-8859-1?Q?Lan=E7amento_-_Ferramentas_ETramontina?= From: =?ISO-8859-1?Q?Tubar=E3o_El=E9trico?= To: Message-Id: <251935.XRXUFVLP@gmail.com> Original-recipient: rfc822;freebsd-stable@freebsd.org Content-Type: multipart/mixed; Boundary="--=BOUNDARY_251935_FSVP_PXGS_UYUG_BVCS" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 21:36:00 -0000 Esta mensagem está em formato MIME. Uma vez que seu cliente de e-mail não entende este formato, algumas partes ou toda a mensagem podem ser ilegíveis. ----=BOUNDARY_251935_FSVP_PXGS_UYUG_BVCS Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-transfer-encoding: quoted-printable Confira em nosso site! http://www.tubaraoeletrico.com.br/ ----=BOUNDARY_251935_FSVP_PXGS_UYUG_BVCS-- From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 21:41:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1A420309 for ; Tue, 5 Feb 2013 21:41:10 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mail-da0-f45.google.com (mail-da0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id C13639B4 for ; Tue, 5 Feb 2013 21:41:09 +0000 (UTC) Received: by mail-da0-f45.google.com with SMTP id w4so258485dam.32 for ; Tue, 05 Feb 2013 13:41:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:from:to:subject:date:organization :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole:x-gm-message-state; bh=YG1Ivb4SS7FD/Z+E0AcHUYpRNRYICVnfvzfhAiw1jJs=; b=KgdPyfyQjEja9ObVnJhLcgmTfcT1PFo6p+V+SInO1UxMqtSoWDmiYWVt4/UYfCSyFz 0h25HsCKr92pmh1lR+X/glZ4XnZGLXR4aQ1sr0+BSv35zOsc6LvtLFaQWDVVNsA8WDG4 5EQWELCNMxlcz8IyUEh+ixUMB9ZzGGownXcS26JoLV10OrSrHxGyuoRxIL5m1BTL9rrv ty6Qd0hKC6H4/hH4noSpXKnIutzvPsypRHA4VtiBVYBrllw9RPI7I6yDXEX5B3nbImhD UBY6e8BjSyysNVaOgNviJAXX50NmmS8tviuzEZL9jAopHeXIk6QQ841k9qKPTRjNaYPy fYhQ== X-Received: by 10.66.79.202 with SMTP id l10mr67833765pax.36.1360100468867; Tue, 05 Feb 2013 13:41:08 -0800 (PST) Received: from CMOTUM25PC ([187.210.81.114]) by mx.google.com with ESMTPS id l5sm32267272pax.10.2013.02.05.13.41.06 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 13:41:07 -0800 (PST) Message-ID: <2E88E4C03BB743A598B3CE6BC8107158@CMOTUM25PC> From: =?iso-8859-1?Q?Efra=EDn_D=E9ctor?= To: Subject: Test network capabilities Date: Tue, 5 Feb 2013 15:41:04 -0600 Organization: =?iso-8859-1?Q?HESA_T=E9cnica?= MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-Gm-Message-State: ALoCoQk8T+OLzpJex0R4LCCydU41jEz+C8OROusJAYBM57cvP6V3H/NG8gEyglFAMFsrRYNbxa/Y Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 21:41:10 -0000 Hello. Is there a way to test the network capabilities of FreeBSD?, currently = we are tunning our server to achieve the best performance for the socket = connections. Using this = http://rerepi.wordpress.com/2008/04/19/tuning-freebsd-sysoev-rit/ and = this https://calomel.org/freebsd_network_tuning.html guides we see that = we are on the right path, however we want to conduct a test to see if = what we have configured meets our needs. Is there a way to send connections to a opened port of FreeBSD? = Something like Apache Bench but for a socket server based on Apache = Mina? Thanks in advance. From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 22:18:19 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C97BAB52; Tue, 5 Feb 2013 22:18:19 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB91B4B; Tue, 5 Feb 2013 22:18:19 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r15MIHWx008555; Tue, 5 Feb 2013 22:18:17 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r15MIH3Y008538; Tue, 5 Feb 2013 22:18:17 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 5 Feb 2013 22:18:17 GMT Message-Id: <201302052218.r15MIH3Y008538@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 22:18:19 -0000 TB --- 2013-02-05 19:29:45 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-05 19:29:45 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-05 19:29:45 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2013-02-05 19:29:45 - cleaning the object tree TB --- 2013-02-05 19:30:12 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-05 19:30:12 - cd /tinderbox/RELENG_9/ia64/ia64 TB --- 2013-02-05 19:30:12 - /usr/local/bin/svn cleanup /src TB --- 2013-02-05 19:31:29 - /usr/local/bin/svn update /src TB --- 2013-02-05 19:31:38 - building world TB --- 2013-02-05 19:31:38 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 19:31:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 19:31:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 19:31:38 - SRCCONF=/dev/null TB --- 2013-02-05 19:31:38 - TARGET=ia64 TB --- 2013-02-05 19:31:38 - TARGET_ARCH=ia64 TB --- 2013-02-05 19:31:38 - TZ=UTC TB --- 2013-02-05 19:31:38 - __MAKE_CONF=/dev/null TB --- 2013-02-05 19:31:38 - cd /src TB --- 2013-02-05 19:31:38 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 5 19:31:39 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Feb 5 21:24:13 UTC 2013 TB --- 2013-02-05 21:24:13 - generating LINT kernel config TB --- 2013-02-05 21:24:13 - cd /src/sys/ia64/conf TB --- 2013-02-05 21:24:13 - /usr/bin/make -B LINT TB --- 2013-02-05 21:24:13 - cd /src/sys/ia64/conf TB --- 2013-02-05 21:24:13 - /usr/sbin/config -m LINT TB --- 2013-02-05 21:24:13 - building LINT kernel TB --- 2013-02-05 21:24:13 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 21:24:13 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 21:24:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 21:24:13 - SRCCONF=/dev/null TB --- 2013-02-05 21:24:13 - TARGET=ia64 TB --- 2013-02-05 21:24:13 - TARGET_ARCH=ia64 TB --- 2013-02-05 21:24:13 - TZ=UTC TB --- 2013-02-05 21:24:13 - __MAKE_CONF=/dev/null TB --- 2013-02-05 21:24:13 - cd /src TB --- 2013-02-05 21:24:13 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Feb 5 21:24:14 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Tue Feb 5 22:08:11 UTC 2013 TB --- 2013-02-05 22:08:11 - cd /src/sys/ia64/conf TB --- 2013-02-05 22:08:11 - /usr/sbin/config -m GENERIC TB --- 2013-02-05 22:08:11 - building GENERIC kernel TB --- 2013-02-05 22:08:11 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 22:08:11 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 22:08:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 22:08:11 - SRCCONF=/dev/null TB --- 2013-02-05 22:08:11 - TARGET=ia64 TB --- 2013-02-05 22:08:11 - TARGET_ARCH=ia64 TB --- 2013-02-05 22:08:11 - TZ=UTC TB --- 2013-02-05 22:08:11 - __MAKE_CONF=/dev/null TB --- 2013-02-05 22:08:11 - cd /src TB --- 2013-02-05 22:08:11 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Feb 5 22:08:11 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/firewire/if_fwip.c:499: undefined reference to `crom_add_simple_text' /src/sys/dev/firewire/if_fwip.c:500: undefined reference to `crom_add_entry' /src/sys/dev/firewire/if_fwip.c:501: undefined reference to `crom_add_simple_text' if_fwip.o: In function `fwip_stream_input': /src/sys/dev/firewire/if_fwip.c:840: undefined reference to `fw_noderesolve_nodeid' if_fwip.o: In function `fwip_unicast_input': /src/sys/dev/firewire/if_fwip.c:939: undefined reference to `fw_noderesolve_nodeid' if_fwip.o:(.data.rel+0x80): undefined reference to `sysctl__hw_firewire_children' *** Error code 1 Stop in /obj/ia64.ia64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-02-05 22:18:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-02-05 22:18:17 - ERROR: failed to build GENERIC kernel TB --- 2013-02-05 22:18:17 - 7184.44 user 859.13 system 10111.94 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 01:10:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6EE80BD1 for ; Wed, 6 Feb 2013 01:10:09 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:40]) by mx1.freebsd.org (Postfix) with ESMTP id 56B10256 for ; Wed, 6 Feb 2013 01:10:09 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta04.emeryville.ca.mail.comcast.net with comcast id woKw1k0021afHeLA4pA8RM; Wed, 06 Feb 2013 01:10:08 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta17.emeryville.ca.mail.comcast.net with comcast id wpA71k00J1t3BNj8dpA89P; Wed, 06 Feb 2013 01:10:08 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BBF1E73A31; Tue, 5 Feb 2013 17:10:07 -0800 (PST) Date: Tue, 5 Feb 2013 17:10:07 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Subject: csh/tcsh: odd %~ prompt variable behaviour Message-ID: <20130206011007.GA72256@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360113008; bh=hNx6uzv/2yO5hWBcH/033jMVD8leb9TTZ65netiVj90=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=Snq19SJnaHF0HjFEdVmLsd4qTzteIB9Fs4PYM0mMHDLNM+O7dJUpfuXJS+szrAXup wv5RH+73F+yi2fyfLtIq5uP1fKaURBwgC5DMxPKAtcgbQaLZna+8CGaEb9JRsXSEci rB24ufkD7d5tNZ5X+iIodtE2Tqe+oIkWGumN0OXU//wpnvPtm3ZMAdrgPh0hPRlqZ7 NDYh09b7IkSI/kvrNeE3YiU57LM6SILHVrRjVnfv9/V5IWfCWSO6sEKxB9jzmoGmC7 wjpgLug2BD0vqwg5t2tIJlhWWIVvMYGQAvnUbF/w+bN6doWN0H9/UrjIGVDLrTT//d IGmfwgFPmp+BQ== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 01:10:09 -0000 (Please keep me CC'd as I'm not subscribed to the list) System is base/stable/9, r245697. tcsh version is 6.18.01: $ sudo -i root@icarus:~ # sfdjsdj sfdjsdj: Command not found. root@icarus:~ # cd ~root root@icarus:~ # dsjfdsfdsf dsjfdsfdsf: Command not found. root@icarus:~ # cd ~jdc root@icarus:~jdc # sdjfdjkfjdsk sdjfdjkfjdsk: Command not found. root@icarus:/home/jdc # <---- notice sudden prompt change root@icarus:/home/jdc # cd ~root root@icarus:~ # dsfjjdskdfs dsfjjdskdfs: Command not found. root@icarus:~ # logout This only happens when an invalid command is issued (e.g. had I used "ls" instead of "blah" the prompt would not have changed). $prompt is the standard /root/.cshrc (r244005) value: set prompt = "%N@%m:%~ %# " I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02: $ ssh jdc@192.168.1.161 Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan jdc@debian:~$ sudo -i root@debian:~# /bin/tcsh debian:~# set prompt = "%N@%m:%~ %# " root@debian:~ # sdfsdf sdfsdf: Command not found. root@debian:~ # cd ~jdc root@debian:~jdc # sdfssgsgjsj sdfssgsgjsj: Command not found. root@debian:~jdc # exit root@debian:~# logout The number of changes between 6.17.02 and 6.18.01 seem quite large (looking at src/contrib/tcsh/Fixes). Does anyone have a non-FreeBSD system with tcsh 6.18.01 available to determine if this is a FreeBSD-centric issue or an actual issue with tcsh that needs to be reported upstream? Thanks. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 04:38:30 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2A64D69 for ; Wed, 6 Feb 2013 04:38:30 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id CB892BDA for ; Wed, 6 Feb 2013 04:38:29 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 05 Feb 2013 23:38:28 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BXO83736; Tue, 5 Feb 2013 23:38:28 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp01.lnh.mail.rcn.net with ESMTP; 05 Feb 2013 23:38:29 -0500 Message-ID: <5111DE44.7040008@aldan.algebra.com> Date: Tue, 05 Feb 2013 23:38:28 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: stable@FreeBSD.org Subject: FreeBSD-9.1 would not boot on pentium3 laptop Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 04:38:30 -0000 Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I screwed-up the build, but the official CD would not boot either, so here I am. Flipping through the old CDs I have, the 7.3 hangs at boot similarly (after reporting loading the memory image and warning me about "dangerously low battery"). The 3.2-STABLE (September 1999) boots fine -- and goes into sysinstall. Freesbie-2.0.1 (which is based on FreeBSD-6.2) booted too. What happened between 6.x and 7.x? Any ideas? Thanks! -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 04:50:28 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9025E8C9 for ; Wed, 6 Feb 2013 04:50:28 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 58C6CCC7 for ; Wed, 6 Feb 2013 04:50:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=nJ9VXDMCfBYQRCUiAyaEtLCwpCBxhtr1AoLyGnD87e0=; b=yL9seoD6utVzqTRda47llUnj13VU7KLM6jHWMPSOj27owbM1a634ON34SM7nVo/SmUTv0yYdJnPiMc/lLozbOjPawQYpsHvRggM+mO44/ff2LbRPU1Yuv77KaLIdDNXZ; Received: from [122.129.203.50] (port=51510 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1U2wxf-002StN-Ou; Tue, 05 Feb 2013 21:50:20 -0700 Date: Wed, 6 Feb 2013 11:50:16 +0700 From: Erich Dollansky To: "Mikhail T." Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop Message-ID: <20130206115016.51f927ca@X220.ovitrap.com> In-Reply-To: <5111DE44.7040008@aldan.algebra.com> References: <5111DE44.7040008@aldan.algebra.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 04:50:28 -0000 Hi, On Tue, 05 Feb 2013 23:38:28 -0500 "Mikhail T." wrote: > Hello! > > I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). > FreeBSD 6.3-STABLE was running fine on it, but I decided to update > the machine to 9.1-STABLE. > > Well, neither my own custom kernel, nor even the official 9.1-RELEASE > CD1 would boot... In both cases the boot process runs up to detecting > uhub0, then either hangs forever or shuts off after a short while. > USB? I have had a Fujitsu LifeBook which I only could use with 7.x out for the same reason. Erich From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 05:11:37 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BFA8ED00 for ; Wed, 6 Feb 2013 05:11:37 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC06D7A for ; Wed, 6 Feb 2013 05:11:37 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 00:11:37 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CFP33852; Wed, 6 Feb 2013 00:11:29 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp01.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 00:11:29 -0500 Message-ID: <5111E600.4020703@aldan.algebra.com> Date: Wed, 06 Feb 2013 00:11:28 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: Erich Dollansky Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <20130206115016.51f927ca@X220.ovitrap.com> In-Reply-To: <20130206115016.51f927ca@X220.ovitrap.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 05:11:37 -0000 On 05.02.2013 23:50, Erich Dollansky wrote: > USB? That would be a shame -- I'm dressing up this old machine to be used with a couple of USB-devices. > I have had a Fujitsu LifeBook which I only could use with 7.x out for > the same reason. Is there a PR? Thanks, -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 05:53:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A34D619A for ; Wed, 6 Feb 2013 05:53:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-da0-f43.google.com (mail-da0-f43.google.com [209.85.210.43]) by mx1.freebsd.org (Postfix) with ESMTP id 758FCE7B for ; Wed, 6 Feb 2013 05:53:36 +0000 (UTC) Received: by mail-da0-f43.google.com with SMTP id u36so446071dak.2 for ; Tue, 05 Feb 2013 21:53:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=xdb5w00+uK2Nl1Z2x+aeLO1TvvHGH1iXyXtluOj4jnU=; b=E//FPiHVaIEMl+85L9u8kHm/V+lyfnYwfXZnqCAuZEx7NBBve+LXQBNHdXwhlAFu0f HOfcRchf0wHsvumVVERh9m8+WUIbGYenauJE4oB7H9OYiAzw2Ku7ht3GonbAnRt6EVmC pUwQI5tP4OEU0yW6lULQhsY5RdmqNYTCxVPg5aSjyuevNWHym6OCmpqFbEzEL26kFg+O NQZ+VmN9jEocf44636vl4Tv9o/FsByIdZSB7aYcJnfxdUMqw1MrU3o6RrXMl6wM6w3rz xuFlJxCUn7rP1Zv9nhqRIbY9U+C4qVJzzoiIXjQbqalBe9sSdlSAUr3Mw8qgOHKGXhIM To4g== X-Received: by 10.66.74.42 with SMTP id q10mr72180981pav.71.1360130010121; Tue, 05 Feb 2013 21:53:30 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id x2sm35004057paw.8.2013.02.05.21.53.27 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 21:53:29 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 06 Feb 2013 14:53:22 +0900 From: YongHyeon PYUN Date: Wed, 6 Feb 2013 14:53:22 +0900 To: Oliver Fromme Subject: Re: re(4) problems with GA-H77N-WIFI Message-ID: <20130206055322.GA1442@michelle.cdnetworks.com> References: <201302041815.r14IFpD5007605@grabthar.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302041815.r14IFpD5007605@grabthar.secnetix.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 05:53:36 -0000 On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver Fromme wrote: > Hello, > > I need some advice how to debug this issue ... > > Recently I got a new mainboard for a router, it's a > Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. > > The problem is that re0 works fine and re1 doesn't: > It doesn't receive any packets. Tcpdump displays all > outgoing packets, but no incoming ones on re1. Can you see the packets sent from re1 on other box? If not, it probably indicates GMAC is in weird state which in turn indicates initialization was not complete for the controller. > Ifconfig shows the link correctly (100 or 1000 Mbit, > depending on where I plug the cable in). > I also swapped cables just to be sure, but it made no > difference. > If you cold-boot the box with UTP cable plugged in to re1 does it make any difference? > I'm running a recent stable/9 (about 14 days old). > What's the best way to debug this problem? At the I would check whether GMAC is active when driver detects a valid link. Add a code like the following to re_miibus_statchg() to get the status of RL_COMMAND register. You would get the status whenever a link is established with link partner. Index: if_re.c =================================================================== --- if_re.c (revision 246338) +++ if_re.c (working copy) @@ -626,6 +626,9 @@ default: break; } + if (sc->rl_flags & RL_FLAG_LINK) + device_printf(sc->rl_dev, "CMD 0x%02x\n", + CSR_READ_1(sc, RL_COMMAND)); } /* * RealTek controllers does not provide any interface to > moment I'm not even sure if it's the hardware, or if > it's FreeBSD's fault (or my fault) ... > > Best regards > Oliver > > PS: dmesg ... > > pcib2: irq 16 at device 28.4 on pci0 > pci2: on pcib2 > re0: port 0xe000-0xe0ff mem 0xf0104000-0xf0104fff,0xf0100000-0xf0103fff irq 16 at device 0.0 on pci2 > re0: Using 1 MSI-X message > re0: Chip rev. 0x2c800000 > re0: MAC rev. 0x00000000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow > re0: Ethernet address: 90:2b:34:5f:bd:21 > pcib3: irq 17 at device 28.5 on pci0 > pci3: on pcib3 > re1: port 0xd000-0xd0ff mem 0xf0004000-0xf0004fff,0xf0000000-0xf0003fff irq 17 at device 0.0 on pci3 > re1: Using 1 MSI-X message > re1: Chip rev. 0x2c800000 > re1: MAC rev. 0x00000000 > miibus1: on re1 > rgephy1: PHY 1 on miibus1 > rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow > re1: Ethernet address: 90:2b:34:5f:bd:11 > > ifconfig ... > > re0: flags=8843 metric 0 mtu 1500 > options=8209b > ether 90:2b:34:5f:bd:21 > inet ... > nd6 options=21 > media: Ethernet autoselect (1000baseT ) > status: active > re1: flags=8843 metric 0 mtu 1500 > options=8209b > ether 90:2b:34:5f:bd:11 > inet ... > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 06:06:15 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5791D355 for ; Wed, 6 Feb 2013 06:06:15 +0000 (UTC) (envelope-from mcg@sulfegate.org) Received: from mail-ie0-x22a.google.com (ie-in-x022a.1e100.net [IPv6:2607:f8b0:4001:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 1B599EE3 for ; Wed, 6 Feb 2013 06:06:15 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id c11so1430347ieb.1 for ; Tue, 05 Feb 2013 22:06:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sulfegate.org; s=google; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=VljClXnIjal/HjeJNwJrFyne5Z2NVdzwkjzUpaQwpzI=; b=A4M2lckDVxr4Xdf6Kpidc0ZafjrRmMJU+dDqm59SJzQlpx0mPJ92GHv4qyuade1So9 SQb7QSzdsRf0Mi1PW6q2216Qr5RYrcZKAA6ythBwtYeKmmdyzvxhM6J7i3Y7sTOSRefe BaNA3U4nxYTBJWU10IwCojBpWb7Mv8wUlFWuw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:x-gm-message-state; bh=VljClXnIjal/HjeJNwJrFyne5Z2NVdzwkjzUpaQwpzI=; b=cEhhKLZjytQNHT7D7d8s9P2slFER2tsjGqgFzd4IwjoQJRnaLPwDT60N1jCBIn0BaD 5TQr5oL3B1agf2LBGlvMimsVgtwELtdLzwpO0wxE8ftDOtyzSyTRDFd4hJDnGR29ZsfO GuPM1fbaKSqYB2MfVBL6KKKjwC8gB45HXDUGKVaUwyACCWMOMKHV9yZBtqXdPA+SE5EI l1V+vkVmb3Ax0YhljLsu5CN6bDJ5Av8vT2wYaSUhaikf3jlLc6GhZKpm0PfEIwz0cLXZ 9FIZlYfsYs1xqgslVYlvFO1vkw/gw5VHD3RhSrtVU0yCr84/5pssVQj8NBxgW+stdBWN nkNw== X-Received: by 10.50.151.227 with SMTP id ut3mr3872388igb.5.1360130774682; Tue, 05 Feb 2013 22:06:14 -0800 (PST) MIME-Version: 1.0 Sender: mcg@sulfegate.org Received: by 10.50.192.137 with HTTP; Tue, 5 Feb 2013 22:05:44 -0800 (PST) X-Originating-IP: [2001:470:1f05:6c6::100] In-Reply-To: <20130206011007.GA72256@icarus.home.lan> References: <20130206011007.GA72256@icarus.home.lan> From: "Galati, Michael" Date: Tue, 5 Feb 2013 22:05:44 -0800 X-Google-Sender-Auth: uA9dmJr6zC4M8pxSp1Smo4vqFhc Message-ID: Subject: Re: csh/tcsh: odd %~ prompt variable behaviour To: Jeremy Chadwick X-Gm-Message-State: ALoCoQnQ3OxS9Blv7g0AoPBexVLqvCMXZ7N6NDcpwTztjgJryM1kFLmP94ssZ5PoBb8CORHNR6cP Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 06:06:15 -0000 Looks like it could be FreeBSD specific... I very rarely use {,t}csh myself. user@host:~$ uname -a Linux host 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux user@host:~$ sudo -i [sudo] password for user: root@host:~# tcsh host:~# set prompt = "%N@%m:%~ %# " root@host:~ # asdfasdf asdfasdf: Command not found. root@host:~ # cd ~user root@host:~user # asdfasdf asdfasdf: Command not found. root@host:~user # exit root@host:~# logout On Tue, Feb 5, 2013 at 5:10 PM, Jeremy Chadwick wrote: > (Please keep me CC'd as I'm not subscribed to the list) > > > System is base/stable/9, r245697. tcsh version is 6.18.01: > > $ sudo -i > root@icarus:~ # sfdjsdj > sfdjsdj: Command not found. > root@icarus:~ # cd ~root > root@icarus:~ # dsjfdsfdsf > dsjfdsfdsf: Command not found. > root@icarus:~ # cd ~jdc > root@icarus:~jdc # sdjfdjkfjdsk > sdjfdjkfjdsk: Command not found. > root@icarus:/home/jdc # <---- notice sudden prompt change > root@icarus:/home/jdc # cd ~root > root@icarus:~ # dsfjjdskdfs > dsfjjdskdfs: Command not found. > root@icarus:~ # logout > > This only happens when an invalid command is issued (e.g. had I used > "ls" instead of "blah" the prompt would not have changed). > > $prompt is the standard /root/.cshrc (r244005) value: > > set prompt = "%N@%m:%~ %# " > > I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02: > > $ ssh jdc@192.168.1.161 > Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 > > Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan > jdc@debian:~$ sudo -i > root@debian:~# /bin/tcsh > debian:~# set prompt = "%N@%m:%~ %# " > root@debian:~ # sdfsdf > sdfsdf: Command not found. > root@debian:~ # cd ~jdc > root@debian:~jdc # sdfssgsgjsj > sdfssgsgjsj: Command not found. > root@debian:~jdc # exit > root@debian:~# logout > > The number of changes between 6.17.02 and 6.18.01 seem quite large > (looking at src/contrib/tcsh/Fixes). > > Does anyone have a non-FreeBSD system with tcsh 6.18.01 available > to determine if this is a FreeBSD-centric issue or an actual issue with > tcsh that needs to be reported upstream? > > Thanks. > > -- > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 06:24:58 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B2CED64F for ; Wed, 6 Feb 2013 06:24:58 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 62E6FF86 for ; Wed, 6 Feb 2013 06:24:57 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 01:24:59 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CFP36235; Wed, 6 Feb 2013 01:24:57 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp04.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 01:24:57 -0500 Message-ID: <5111F739.7070607@aldan.algebra.com> Date: Wed, 06 Feb 2013 01:24:57 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> In-Reply-To: <5111DE44.7040008@aldan.algebra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 06:24:58 -0000 On 05.02.2013 23:38, Mikhail T. wrote: > What happened between 6.x and 7.x? Ok, what happened is that "device cpufreq" is now in GENERIC and the ichss0 along with it. Setting set hint.ichss.0.disabled=1 on the loader prompt allows me to boot -- both my own kernel as well as the 9.1-RELEASE from CD. Solved... Annoying beyond belief, but solved. Now, if only I could figure out, why my network card (3COM's 3C556 Mini PCI) is not seen by the 9.1... It was working perfectly fine with 6.3 -- and still works with the FreeSBIE-2.0.1 -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 06:25:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF3A9748 for ; Wed, 6 Feb 2013 06:25:23 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by mx1.freebsd.org (Postfix) with ESMTP id A4F83F95 for ; Wed, 6 Feb 2013 06:25:23 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta13.emeryville.ca.mail.comcast.net with comcast id wuFZ1k0041afHeLADuRMtj; Wed, 06 Feb 2013 06:25:21 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta17.emeryville.ca.mail.comcast.net with comcast id wuRL1k00E1t3BNj8duRLAC; Wed, 06 Feb 2013 06:25:21 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 979DF73A31; Tue, 5 Feb 2013 22:25:20 -0800 (PST) Date: Tue, 5 Feb 2013 22:25:20 -0800 From: Jeremy Chadwick To: "Galati, Michael" Subject: Re: csh/tcsh: odd %~ prompt variable behaviour Message-ID: <20130206062520.GA79498@icarus.home.lan> References: <20130206011007.GA72256@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360131921; bh=oXR+2vPCpp0zJrNxW6CAYsCPrCkZ1UvXgTlUOYpIqfY=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=kejbgNQ2PTCZvuvRawfqWs1uuMFR3PmfzEC218DzgOubfEM1jE2ZAKu+MwqX570d+ jpU1MAflbZ0ASSf8vT6+Cu+mzAsnRJDaSahQeGAceKUYmyhsqi5kYAuIycfLYd8jLT xtkCBRE44ag0alVrFpksObXWggfna36ZfsFGfP7vzqqETQirpKBo88Bc8i/ema1gqK oIbmJmoAqAFygWcop/hBaANaRbmzFA9E0FkCuD1AVxOIGeqcA0mRaVLQpogVWAIWc/ fWbR/zIqC8xUlJnC1+DCs8u91+8icubeOJwT+TXso9VfbJNR6RL1H5YS2q8ebzGAJn CEylr/rITVUKA== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 06:25:23 -0000 Michael, Thank you very much! What tcsh version is that? "echo $version" should say. :-) -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Tue, Feb 05, 2013 at 10:05:44PM -0800, Galati, Michael wrote: > Looks like it could be FreeBSD specific... I very rarely use {,t}csh > myself. > > user@host:~$ uname -a > Linux host 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 > x86_64 x86_64 x86_64 GNU/Linux > user@host:~$ sudo -i > [sudo] password for user: > root@host:~# tcsh > host:~# set prompt = "%N@%m:%~ %# " > root@host:~ # asdfasdf > asdfasdf: Command not found. > root@host:~ # cd ~user > root@host:~user # asdfasdf > asdfasdf: Command not found. > root@host:~user # exit > root@host:~# logout > > > > On Tue, Feb 5, 2013 at 5:10 PM, Jeremy Chadwick wrote: > > > (Please keep me CC'd as I'm not subscribed to the list) > > > > > > System is base/stable/9, r245697. tcsh version is 6.18.01: > > > > $ sudo -i > > root@icarus:~ # sfdjsdj > > sfdjsdj: Command not found. > > root@icarus:~ # cd ~root > > root@icarus:~ # dsjfdsfdsf > > dsjfdsfdsf: Command not found. > > root@icarus:~ # cd ~jdc > > root@icarus:~jdc # sdjfdjkfjdsk > > sdjfdjkfjdsk: Command not found. > > root@icarus:/home/jdc # <---- notice sudden prompt change > > root@icarus:/home/jdc # cd ~root > > root@icarus:~ # dsfjjdskdfs > > dsfjjdskdfs: Command not found. > > root@icarus:~ # logout > > > > This only happens when an invalid command is issued (e.g. had I used > > "ls" instead of "blah" the prompt would not have changed). > > > > $prompt is the standard /root/.cshrc (r244005) value: > > > > set prompt = "%N@%m:%~ %# " > > > > I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02: > > > > $ ssh jdc@192.168.1.161 > > Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 > > > > Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan > > jdc@debian:~$ sudo -i > > root@debian:~# /bin/tcsh > > debian:~# set prompt = "%N@%m:%~ %# " > > root@debian:~ # sdfsdf > > sdfsdf: Command not found. > > root@debian:~ # cd ~jdc > > root@debian:~jdc # sdfssgsgjsj > > sdfssgsgjsj: Command not found. > > root@debian:~jdc # exit > > root@debian:~# logout > > > > The number of changes between 6.17.02 and 6.18.01 seem quite large > > (looking at src/contrib/tcsh/Fixes). > > > > Does anyone have a non-FreeBSD system with tcsh 6.18.01 available > > to determine if this is a FreeBSD-centric issue or an actual issue with > > tcsh that needs to be reported upstream? > > > > Thanks. > > > > -- > > | Jeremy Chadwick jdc@koitsu.org | > > | UNIX Systems Administrator http://jdc.koitsu.org/ | > > | Mountain View, CA, US | > > | Making life hard for others since 1977. PGP 4BD6C0CB | > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 06:40:12 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 85DFAAD3 for ; Wed, 6 Feb 2013 06:40:12 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2C658BF for ; Wed, 6 Feb 2013 06:40:11 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 01:40:11 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BXO87157; Wed, 6 Feb 2013 01:40:11 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp04.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 01:40:11 -0500 Message-ID: <5111FACB.5040104@aldan.algebra.com> Date: Wed, 06 Feb 2013 01:40:11 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> In-Reply-To: <5111F739.7070607@aldan.algebra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 06:40:12 -0000 On 06.02.2013 01:24, Mikhail T. wrote: > Now, if only I could figure out, why my network card (3COM's 3C556 > Mini PCI) is not seen by the 9.1... Disabling "Wake on LAN" in the BIOS solved this problem. Now xl0 is seen and functional. Solved. I struggle to understand, how a less seasoned user could be expected to figure these two issues out... -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 06:57:36 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9C85E261 for ; Wed, 6 Feb 2013 06:57:36 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 59C9F190 for ; Wed, 6 Feb 2013 06:57:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=MkK6uiLz6dPHSm72LVIz5DLMMjpLtstz0EeQjS71yas=; b=VsvacQsDPhOCgUawblBiC76DayPn1Vt/FQ0w/bCQ36U1Sbc5KQhw3WtMqXw2JDGVfqdYINZ8WZYXHn2sibO4TgGuiStwJtOLzxSShpnBNX396WBq3cmq7miBXT6hdapO; Received: from [122.129.203.50] (port=64198 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1U2ywo-002y0c-LV; Tue, 05 Feb 2013 23:57:35 -0700 Date: Wed, 6 Feb 2013 13:57:31 +0700 From: Erich Dollansky To: "Mikhail T." Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop Message-ID: <20130206135731.2d4dce9e@X220.ovitrap.com> In-Reply-To: <5111E600.4020703@aldan.algebra.com> References: <5111DE44.7040008@aldan.algebra.com> <20130206115016.51f927ca@X220.ovitrap.com> <5111E600.4020703@aldan.algebra.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 06:57:36 -0000 Hi, On Wed, 06 Feb 2013 00:11:28 -0500 "Mikhail T." wrote: > On 05.02.2013 23:50, Erich Dollansky wrote: > > USB? > That would be a shame -- I'm dressing up this old machine to be used > with a couple of USB-devices. try 7.4. This worked for me until a lightning came. > > I have had a Fujitsu LifeBook which I only could use with 7.x out > > for the same reason. > Is there a PR? Thanks, No. I did not want to bother people for such an old device. Erich From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 07:05:44 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3D3863AE for ; Wed, 6 Feb 2013 07:05:44 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 00B7F1C5 for ; Wed, 6 Feb 2013 07:05:43 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 02:05:44 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BXO87941; Wed, 6 Feb 2013 02:05:43 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp01.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 02:05:44 -0500 Message-ID: <511200C6.8070602@aldan.algebra.com> Date: Wed, 06 Feb 2013 02:05:42 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: Erich Dollansky Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <20130206115016.51f927ca@X220.ovitrap.com> <5111E600.4020703@aldan.algebra.com> <20130206135731.2d4dce9e@X220.ovitrap.com> In-Reply-To: <20130206135731.2d4dce9e@X220.ovitrap.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 07:05:44 -0000 On 06.02.2013 01:57, Erich Dollansky wrote: >>> I have had a Fujitsu LifeBook which I only could use with 7.x out >>> > >for the same reason. >> >Is there a PR? Thanks, > No. I did not want to bother people for such an old device. You should have. If it is listed as "supported", it should be working. And FreeBSD still supports 486 CPUs (though not the 386). Testing old devices is difficult for developers, so they'd rely on users like yourself to tell them about regressions... -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 07:13:32 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B6C3A4F9 for ; Wed, 6 Feb 2013 07:13:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-da0-f46.google.com (mail-da0-f46.google.com [209.85.210.46]) by mx1.freebsd.org (Postfix) with ESMTP id 62D6A1F9 for ; Wed, 6 Feb 2013 07:13:32 +0000 (UTC) Received: by mail-da0-f46.google.com with SMTP id p5so480415dak.19 for ; Tue, 05 Feb 2013 23:13:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=l72LjCBiWefhk/3tzky0jVqVXc3kkpRd05EyUUbhDVY=; b=EsjpNwylWwme4lS9/OqF0k2AxfMYQjRzXfejJvsLUhVyRX+G9AjWPeaMUaBUFc/I4k ovXmTSKM5bhzp8KxXwprJGxqfJNZMCCn+/u9iY73SQNQx22O0zTUH1v6aOxIbPs0u/4Y oWmmflfgxtlIFSZPftVDuTBq7O3epJqMhzmobp5dChYbEpgEP/iWnOMAkSlvRuvVhh+H pXu5gyItEUKsZkLjPPAI4kSa1WALQGY5hy2eVWsRYdDvN12TFJpX2+vl9V6K67R2S/Fm oUQAYvD518HBgMxGAbfGUt9xXFLQ3Lxqxmyg2AaQe1iBSV8s93AiNJ+U13yakSjGtJ5Z t/7Q== X-Received: by 10.66.89.226 with SMTP id br2mr19393789pab.57.1360134811798; Tue, 05 Feb 2013 23:13:31 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id l5sm35494141pax.10.2013.02.05.23.13.28 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 23:13:30 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 06 Feb 2013 16:13:24 +0900 From: YongHyeon PYUN Date: Wed, 6 Feb 2013 16:13:24 +0900 To: "Mikhail T." Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop Message-ID: <20130206071324.GB1442@michelle.cdnetworks.com> References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> <5111FACB.5040104@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5111FACB.5040104@aldan.algebra.com> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 07:13:32 -0000 On Wed, Feb 06, 2013 at 01:40:11AM -0500, Mikhail T. wrote: > On 06.02.2013 01:24, Mikhail T. wrote: > >Now, if only I could figure out, why my network card (3COM's 3C556 > >Mini PCI) is not seen by the 9.1... > Disabling "Wake on LAN" in the BIOS solved this problem. Now xl0 is seen > and functional. Solved. Because I added WOL support xl(4) in the past I'm interested in knowing whether that change broke your controller when BIOS enables WOL. If you boot with bootverbose, do you see a message like "No auxiliary remote wakeup connector!" from xl(4)? (of course, WOL should be enabled in BIOS before boot) Also show the output of 'pciconf -lcbv". > > I struggle to understand, how a less seasoned user could be expected to > figure these two issues out... > > -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 08:29:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5155FB86 for ; Wed, 6 Feb 2013 08:29:44 +0000 (UTC) (envelope-from jan0sch@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1.freebsd.org (Postfix) with ESMTP id E4C767C5 for ; Wed, 6 Feb 2013 08:29:43 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M84ER-1UprqJ47ij-00vcJQ for ; Wed, 06 Feb 2013 09:29:42 +0100 Received: (qmail invoked by alias); 06 Feb 2013 08:29:42 -0000 Received: from dslb-088-074-034-053.pools.arcor-ip.net (EHLO magni.rostock.home) [88.74.34.53] by mail.gmx.net (mp017) with SMTP; 06 Feb 2013 09:29:42 +0100 X-Authenticated: #1545395 X-Provags-ID: V01U2FsdGVkX19xBS0DTUdxPTynLk/OdQsVNQdHCtdTbrNA1CaEva 4YuEVP+2dx+7DV Date: Wed, 6 Feb 2013 09:29:08 +0100 From: Jens Jahnke To: freebsd-stable@freebsd.org Subject: FreeBSD 9.1 occasional kernel panic Message-Id: <20130206092908.d773cfde61f35347f32f6c47@gmx.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) X-Face: &?!P`87-36gaG)/K:yi&ixw=uy]y'?$vrc Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Wed__6_Feb_2013_09_29_08_+0100_RWy1pWfW5SEkSX1e" X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 08:29:44 -0000 --Signature=_Wed__6_Feb_2013_09_29_08_+0100_RWy1pWfW5SEkSX1e Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, recently I've switched from 8.3 to 9.1 on my home box and are quite pleased but occasionally I get a kernel panic like this: Feb 5 19:55:45 magni kernel: /dev: got error 6 while accessing filesystem Feb 5 19:55:45 magni kernel: panic: softdep_deallocate_dependencies: unrec= overed I/O error Feb 5 19:55:45 magni kernel: cpuid =3D 1 Feb 5 19:55:45 magni kernel: KDB: stack backtrace: Feb 5 19:55:45 magni kernel: #0 0xffffffff809208a6 at kdb_backtrace+0x66 Feb 5 19:55:45 magni kernel: #1 0xffffffff808ea8be at panic+0x1ce Feb 5 19:55:45 magni kernel: #2 0xffffffff80b08d30 at clear_remove+0 Feb 5 19:55:45 magni kernel: #3 0xffffffff80966cd0 at brelse+0x60 Feb 5 19:55:45 magni kernel: #4 0xffffffff8096a14c at bufwrite+0xfc Feb 5 19:55:45 magni kernel: #5 0xffffffff80b0bd47 at softdep_process_jour= nal+0x867 Feb 5 19:55:45 magni kernel: #6 0xffffffff80b0bf0a at jwait+0x9a Feb 5 19:55:45 magni kernel: #7 0xffffffff80b0c2b0 at flush_deplist+0x80 Feb 5 19:55:45 magni kernel: #8 0xffffffff80b0d531 at softdep_sync_metadat= a+0x1b1 Feb 5 19:55:45 magni kernel: #9 0xffffffff80b2236b at ffs_syncvnode+0x44b Feb 5 19:55:45 magni kernel: #10 0xffffffff80b22f91 at ffs_fsync+0x41 Feb 5 19:55:45 magni kernel: #11 0xffffffff8098c600 at sys_fsync+0x160 Feb 5 19:55:45 magni kernel: #12 0xffffffff80bd7ae6 at amd64_syscall+0x546 Feb 5 19:55:45 magni kernel: #13 0xffffffff80bc3447 at Xfast_syscall+0xf7 It does not happen very often but when it happens it mostly happens=20 several times in a row. When I'm booting into single user while within=20 such a "series" I seem to be able to reproduce the panic. If I mount my partitions one at a time the panic occurs several seconds=20 after I mount my geli encrypted home partition. System specs: Gigabyte GA-EP35-DS3P Intel Core 2 Duo E8500 4 GB DDR2-800 3 HDDs (2x SATA, 1 SATA (Intel SSD)) System is installed on the SSD. Any ideas where this could be originating from? Regards, Jens --=20 06. Hornung 2013, 09:20 Homepage : http://www.jan0sch.de Why don't you fix your little problem... and light this candle? -- Alan Shepard, the first American into space, Gemini program --Signature=_Wed__6_Feb_2013_09_29_08_+0100_RWy1pWfW5SEkSX1e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQG8BAEBCgAGBQJREhR1AAoJED2+SXzzbciGHL8M/0iPH3Ho1GkQQzFWgxuVOtDC 5pvIDcz7UBid1QCt9OBZQ3KOUF6uYwnbSIYe+WCsESuCQg5eOf4sT1W09ZrcIAM4 8GIVsStL4eM5J1K/QUlIChPUUfjVL779Fg3ZcMuT3lPTgILMts1696C9diXstGzl lYanFvOnQ+V5CGH5p0agWakl4yGtFGxlP3TzFMB8rZaCqTl99MYDuBtbBNPG+/g4 Fpeu/lAGKA3cK/8pa/VvzjEALOtI58RLkYq5RI1Rqj0GhRp5goxZEDtCcad7elEV tBxphAiKWoGprOoHYnLqGVYV3iw/+qQdpNH4Xy51iy+Vj4q2P2OwXoBA0eZNLvMi ZJJ30UO8YCRPQ+b5kHgV7ETYpRgTpTi7FRIDdgiMc4EDAv7z4fGu3PY5ZM3rycuq b8hw5Qnr2YIYhCWMD97wWDAixw9MMOd1f78sEWleBUAqxqXbkUaEk4EORskgU0xV hf8E4iCfDjCXXZMd1OyZKfkIdgKb+rtojnoqeWA5d67Fa0QGSjcgKFv1S3XIcb5e HFTt8xj35eyNKVYKSqoJ =jfQQ -----END PGP SIGNATURE----- --Signature=_Wed__6_Feb_2013_09_29_08_+0100_RWy1pWfW5SEkSX1e-- From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 09:20:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3438E752; Wed, 6 Feb 2013 09:20:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id DCBE5B66; Wed, 6 Feb 2013 09:20:38 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by kabab.cs.huji.ac.il with esmtp id 1U31BA-000C50-6a; Wed, 06 Feb 2013 11:20:32 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: John Baldwin Subject: Re: problems with the mfi In-reply-to: <201302051224.33779.jhb@freebsd.org> References: <201302051224.33779.jhb@freebsd.org> Comments: In-reply-to John Baldwin message dated "Tue, 05 Feb 2013 12:24:33 -0500." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Feb 2013 11:20:32 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 09:20:39 -0000 > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: > > after rebooting I get very often: > > ... > > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS > > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS > > mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS > > ... > > > > another reboot usualy fixes this. > > Does it have the latest firmware? it happened on several boxes, this one just arrived a week ago, and I will check, but most probably has the latest firmaware. cheers danny > > -- > John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 09:57:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3FB7292; Wed, 6 Feb 2013 09:57:45 +0000 (UTC) (envelope-from prvs=174982bc16=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B60B5DB4; Wed, 6 Feb 2013 09:57:44 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50002044827.msg; Wed, 06 Feb 2013 09:56:55 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 06 Feb 2013 09:56:55 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=174982bc16=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: "John Baldwin" , References: <201302051224.33779.jhb@freebsd.org> Subject: Re: problems with the mfi Date: Wed, 6 Feb 2013 09:46:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 09:57:45 -0000 ----- Original Message ----- From: "John Baldwin" > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: >> after rebooting I get very often: >> ... >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS >> ... >> >> another reboot usualy fixes this. > > Does it have the latest firmware? Be aware that the current code for mfi timeout's never abort so if you get a command stuck it will moan forever. This is one of the issues fixed in a patch that's in testing. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 10:01:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id ACFF81F6 for ; Wed, 6 Feb 2013 10:01:20 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177]) by mx1.freebsd.org (Postfix) with ESMTP id 733AADFA for ; Wed, 6 Feb 2013 10:01:20 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id u28so437647qcs.8 for ; Wed, 06 Feb 2013 02:01:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=0Xk+y0KyV/JA/n5y2EPgf9PKqVXZWCqJ4ASpW4P7fkE=; b=D/ITO1nOUE0ru3EJEqDbK7epHv64mzBmZboPB135k6s9E59q1x4AYt2Hgq7OZmvR8O kiTUeyLeJ/bALbqEpzGpg6cOJxAqKaD4uM8x7T+Idk8bIVdjV1+0wnpmB2+AO48jpjFx ZGjHVsNOnI07NomgsPLl/Rtpx7XAyGrvbIW+klc+Gl507D5iqXaYrh3jn0f6mKNDbCL0 TdAwRrOYgmW1TgwsR1WwLlIT/Wti305WdUw+05HBpegu5B0CeYA1bXnnA2EJYLzMzDyD 6w1WVX4QJdj9EBZ33twHSIWYwOprGdzGi+gS64EN0FnAHRbeeZGaXjXveQi0IgDndw97 3+Gg== MIME-Version: 1.0 X-Received: by 10.224.186.81 with SMTP id cr17mr20666521qab.99.1360144874509; Wed, 06 Feb 2013 02:01:14 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Wed, 6 Feb 2013 02:01:14 -0800 (PST) In-Reply-To: References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> Date: Wed, 6 Feb 2013 11:01:14 +0100 X-Google-Sender-Auth: W3nY7qbxFEGuqHZwuTwg0S03Ilg Message-ID: Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 10:01:20 -0000 On Mon, Feb 4, 2013 at 10:05 PM, CeDeROM wrote: > I also want to use my KT-LINK multipurpose low-level embedded access > multitool based on FT2232H with RS232 port and I was worried there is > no driver - right now I will add the PID and recompile sources to see > if it works - happy to catch this thread :-) Glad to announce I made my KT-LINK RS232/JTAG/SWD/* interface working on FreeBSD with just a little driver modification and kernel/modules rebuild - I will send patches soon, just need to test how it works with both RS2232 and JTAG running if there are no glitches :-) Best regards :-) Tomek Cedro -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 10:35:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2608B89D; Wed, 6 Feb 2013 10:35:30 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id CD647F3F; Wed, 6 Feb 2013 10:35:29 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by kabab.cs.huji.ac.il with esmtp id 1U32LX-000DgS-Kv; Wed, 06 Feb 2013 12:35:19 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: "Steven Hartland" Subject: Re: problems with the mfi In-reply-to: References: <201302051224.33779.jhb@freebsd.org> Comments: In-reply-to "Steven Hartland" message dated "Wed, 06 Feb 2013 09:46:38 +0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Feb 2013 12:35:19 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 10:35:30 -0000 > ----- Original Message ----- > From: "John Baldwin" > > > > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: > >> after rebooting I get very often: > >> ... > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS > >> ... > >> > >> another reboot usualy fixes this. > > > > Does it have the latest firmware? > > Be aware that the current code for mfi timeout's never abort so > if you get a command stuck it will moan forever. > > This is one of the issues fixed in a patch that's in testing. > > Regards > Steve i know :-), I caught this one because the machine was not rebooting. can you shed some light as to what command timed out? cheers, danny From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 11:44:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F0F3CB1B for ; Wed, 6 Feb 2013 11:44:56 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [186.193.48.13]) by mx1.freebsd.org (Postfix) with ESMTP id 6B9792A9 for ; Wed, 6 Feb 2013 11:44:55 +0000 (UTC) Received: from zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [127.0.0.1]) by zeus.linuxinfo.com.br (Postfix) with ESMTP id 7F8FB466A474 for ; Wed, 6 Feb 2013 09:43:23 -0200 (BRST) X-Virus-Scanned: amavisd-new at zeus.linuxinfo.com.br Received: from zeus.linuxinfo.com.br ([127.0.0.1]) by zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_Wkt1v6gnZF for ; Wed, 6 Feb 2013 09:43:20 -0200 (BRST) Received: from MacBook-de-Gondim-2.local (unknown [186.193.54.69]) by zeus.linuxinfo.com.br (Postfix) with ESMTPSA id 79621466A458 for ; Wed, 6 Feb 2013 09:43:17 -0200 (BRST) Message-ID: <5112422B.70109@bsdinfo.com.br> Date: Wed, 06 Feb 2013 09:44:43 -0200 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> In-Reply-To: <5111F739.7070607@aldan.algebra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 11:44:57 -0000 Em 06/02/13 04:24, Mikhail T. escreveu: > On 05.02.2013 23:38, Mikhail T. wrote: >> What happened between 6.x and 7.x? > Ok, what happened is that "device cpufreq" is now in GENERIC and the > ichss0 along with it. > > Setting > > set hint.ichss.0.disabled=1 > > on the loader prompt allows me to boot -- both my own kernel as well > as the 9.1-RELEASE from CD. Solved... Annoying beyond belief, but solved. > > Now, if only I could figure out, why my network card (3COM's 3C556 > Mini PCI) is not seen by the 9.1... > > It was working perfectly fine with 6.3 -- and still works with the > FreeSBIE-2.0.1 Hi, 3c556 is supported by xl driver but xl driver need "device miibus" in kernel. http://www.freebsd.org/releases/9.1R/hardware.html The xl(4) driver supports the following hardware: * 3Com 3c900-TPO * 3Com 3c900-COMBO * 3Com 3c905-TX * 3Com 3c905-T4 * 3Com 3c900B-TPO * 3Com 3c900B-TPC * 3Com 3c900B-FL * 3Com 3c900B-COMBO * 3Com 3c905B-T4 * 3Com 3c905B-TX * 3Com 3c905B-FX * 3Com 3c905B-COMBO * 3Com 3c905C-TX * 3Com 3c980, 3c980B, and 3c980C server adapters * 3Com 3cSOHO100-TX OfficeConnect adapters * 3Com 3c450 HomeConnect adapters * 3Com 3c555, 3c556 and 3c556B mini-PCI adapters * 3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, 3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters * 3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded adapters best regards, Gondim From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 11:59:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A2826E2F for ; Wed, 6 Feb 2013 11:59:24 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id 152C9337 for ; Wed, 6 Feb 2013 11:59:23 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 7637 invoked from network); 6 Feb 2013 12:59:19 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a; t=1360151962; bh=S9IhuALuQp2Tj+z3tVMD56i4POI89Cw8k9yLysloBl0=; h=From:To:Subject; b=PmxlqP6QW3eQeB7r5aTiBOTHzAs+8LkGM8RtvOC95l12frj64o/9CR0dmVRWoXOWj y2cfe4kfUuyGtaDwNmEIYztbrmtqRjUpy+rb6GH64dNOjjQZU8WbYlr2Q6ZqYyL8D1 TRzAd401E3aFA4JgPgc6JVOLWJLPIeTSxR3ir7Mg= Received: from 089144192052.atnat0001.highway.a1.net (HELO [127.0.0.1]) (marek_sal@[89.144.192.52]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with CAMELLIA256-SHA encrypted SMTP for ; 6 Feb 2013 12:59:19 +0100 Message-ID: <51124589.7080800@wp.pl> Date: Wed, 06 Feb 2013 12:59:05 +0100 From: Marek Salwerowicz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: pkg can't access pkgbeta.freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [MRPk] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 11:59:24 -0000 Hi, On freshly installed FreeBSD-9.1-Release amd64 (from ISO) I am trying to migrate to new generation of packages: arch1% sudo pkg The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg please wait pkg: Error fetching http://pkgbeta.FreeBSD.org/freebsd:9:x86:64/latest/Latest/pkg.txz: No route to host arch1% arch1% traceroute pkgbeta.freebsd.org traceroute to bwwwdyn.freebsd.org (69.147.83.39), 64 hops max, 52 byte packets 1 172.16.30.1 (172.16.30.1) 1.215 ms 1.106 ms 1.107 ms 2 192.168.0.99 (192.168.0.99) 2.337 ms 2.474 ms 1.933 ms 3 pw-gw-gi3-0-558.warman.nask.pl (194.181.61.225) 3.978 ms 5.550 ms 4.799 ms 4 172.27.27.2 (172.27.27.2) 5.524 ms 5.292 ms 6.841 ms 5 frankfurt-gw-ae1-100.core.nask.pl (195.187.255.183) 29.989 ms 39.843 ms 28.430 ms 6 ge-1-3-0.pat2.dee.yahoo.com (80.81.193.115) 28.565 ms 28.384 ms 28.221 ms 7 as-1.pat2.dcp.yahoo.com (66.196.65.129) 119.239 ms 119.011 ms 118.605 ms 8 as-0.pat2.da3.yahoo.com (216.115.101.155) 193.173 ms 198.485 ms ae-7.pat2.che.yahoo.com (216.115.100.137) 224.062 ms 9 ae-6.pat1.dnx.yahoo.com (216.115.96.207) 191.784 ms as-1.pat2.sjc.yahoo.com (216.115.101.151) 194.342 ms ae-5.pat2.dnx.yahoo.com (216.115.96.55) 186.775 ms 10 ae-7.pat1.sjc.yahoo.com (216.115.101.149) 189.467 ms ae-7.pat1.pao.yahoo.com (216.115.101.128) 183.305 ms ae-7.pat1.sjc.yahoo.com (216.115.101.149) 192.312 ms 11 ae-0-d141.msr1.sp1.yahoo.com (216.115.107.51) 186.679 ms ae-1-d170.msr2.sp1.yahoo.com (216.115.107.85) 221.705 ms ae-1-d160.msr1.sp1.yahoo.com (216.115.107.61) 185.266 ms 12 * gi-1-47.bas-b1.sp1.yahoo.com (209.131.32.45) 187.202 ms gi-1-33.bas-b2.sp1.yahoo.com (98.136.16.33) 184.560 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * *^C arch1% ping pkgbeta.freebsd.org PING bwwwdyn.freebsd.org (69.147.83.39): 56 data bytes and no answer... Regards, -- Marek Salwerowicz From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 12:34:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2E70A8EE; Wed, 6 Feb 2013 12:34:24 +0000 (UTC) (envelope-from prvs=174982bc16=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4D972D; Wed, 6 Feb 2013 12:34:23 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50002046088.msg; Wed, 06 Feb 2013 12:34:21 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 06 Feb 2013 12:34:21 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=174982bc16=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> From: "Steven Hartland" To: "Daniel Braniss" References: <201302051224.33779.jhb@freebsd.org> Subject: Re: problems with the mfi Date: Wed, 6 Feb 2013 12:30:04 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:34:24 -0000 ----- Original Message ----- From: "Daniel Braniss" >> > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: >> >> after rebooting I get very often: >> >> ... >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS >> >> ... >> >> >> >> another reboot usualy fixes this. >> > >> > Does it have the latest firmware? >> >> Be aware that the current code for mfi timeout's never abort so >> if you get a command stuck it will moan forever. >> >> This is one of the issues fixed in a patch that's in testing. > > i know :-), I caught this one because the machine was not rebooting. > can you shed some light as to what command timed out? Unfortunately not it was a generic issue any command which timeout would get stuck for ever. What FreeBSD version are using and what controller are you using? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 12:38:45 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9E36AA34 for ; Wed, 6 Feb 2013 12:38:45 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CD9B9765 for ; Wed, 6 Feb 2013 12:38:44 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA15984; Wed, 06 Feb 2013 14:38:04 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <51124EAB.7060407@FreeBSD.org> Date: Wed, 06 Feb 2013 14:38:03 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130113 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Mikhail T." Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> <5111FACB.5040104@aldan.algebra.com> In-Reply-To: <5111FACB.5040104@aldan.algebra.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:38:45 -0000 on 06/02/2013 08:40 Mikhail T. said the following: > I struggle to understand, how a less seasoned user could be expected to figure > these two issues out... Nobody expects that. These two bugs are just bugs, there is no drama. People change code, something gets broken for some very rarely used hardware, it goes unnoticed. Then someone notices, reports. From that point, all depends on that someone and on the developers. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 12:40:50 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C456EB61 for ; Wed, 6 Feb 2013 12:40:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1C41A796 for ; Wed, 6 Feb 2013 12:40:49 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA16019; Wed, 06 Feb 2013 14:40:47 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <51124F4F.4050902@FreeBSD.org> Date: Wed, 06 Feb 2013 14:40:47 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130113 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jens Jahnke Subject: Re: FreeBSD 9.1 occasional kernel panic References: <20130206092908.d773cfde61f35347f32f6c47@gmx.net> In-Reply-To: <20130206092908.d773cfde61f35347f32f6c47@gmx.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:40:50 -0000 on 06/02/2013 10:29 Jens Jahnke said the following: > Hi, > > recently I've switched from 8.3 to 9.1 on my home box and are quite pleased > but occasionally I get a kernel panic like this: > > Feb 5 19:55:45 magni kernel: /dev: got error 6 while accessing filesystem > Feb 5 19:55:45 magni kernel: panic: softdep_deallocate_dependencies: > unrecovered I/O error Feb 5 19:55:45 magni kernel: cpuid = 1 Feb 5 19:55:45 > magni kernel: KDB: stack backtrace: Feb 5 19:55:45 magni kernel: #0 > 0xffffffff809208a6 at kdb_backtrace+0x66 Feb 5 19:55:45 magni kernel: #1 > 0xffffffff808ea8be at panic+0x1ce Feb 5 19:55:45 magni kernel: #2 > 0xffffffff80b08d30 at clear_remove+0 Feb 5 19:55:45 magni kernel: #3 > 0xffffffff80966cd0 at brelse+0x60 Feb 5 19:55:45 magni kernel: #4 > 0xffffffff8096a14c at bufwrite+0xfc Feb 5 19:55:45 magni kernel: #5 > 0xffffffff80b0bd47 at softdep_process_journal+0x867 Feb 5 19:55:45 magni > kernel: #6 0xffffffff80b0bf0a at jwait+0x9a Feb 5 19:55:45 magni kernel: #7 > 0xffffffff80b0c2b0 at flush_deplist+0x80 Feb 5 19:55:45 magni kernel: #8 > 0xffffffff80b0d531 at softdep_sync_metadata+0x1b1 Feb 5 19:55:45 magni > kernel: #9 0xffffffff80b2236b at ffs_syncvnode+0x44b Feb 5 19:55:45 magni > kernel: #10 0xffffffff80b22f91 at ffs_fsync+0x41 Feb 5 19:55:45 magni > kernel: #11 0xffffffff8098c600 at sys_fsync+0x160 Feb 5 19:55:45 magni > kernel: #12 0xffffffff80bd7ae6 at amd64_syscall+0x546 Feb 5 19:55:45 magni > kernel: #13 0xffffffff80bc3447 at Xfast_syscall+0xf7 > > It does not happen very often but when it happens it mostly happens several > times in a row. When I'm booting into single user while within such a > "series" I seem to be able to reproduce the panic. If I mount my partitions > one at a time the panic occurs several seconds after I mount my geli > encrypted home partition. > > System specs: Gigabyte GA-EP35-DS3P Intel Core 2 Duo E8500 4 GB DDR2-800 3 > HDDs (2x SATA, 1 SATA (Intel SSD)) > > System is installed on the SSD. > > Any ideas where this could be originating from? "error 6" is ENXIO, which usually corresponds to a disappearing device or some such. Do you get anything in logs (or other objective experience) that could look like that? -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 12:55:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5C50EAE for ; Wed, 6 Feb 2013 12:55:13 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 34FBB827 for ; Wed, 6 Feb 2013 12:55:12 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id ez12so5491573wid.11 for ; Wed, 06 Feb 2013 04:55:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to:x-gm-message-state; bh=O+oszdWx/GGA2IT91MaEGKai9aEhPUtGK+JHsHxrIKs=; b=RWG3yzzJgnWKmG53XEhFZIbqX+Bzvjem3czJ8642YHpBtARqhOGI2zokZ6LBdpNhSq OGmI0KcYUp6bU3MBcfeesKMwsCoxzR8MOuSeg/ZJ9mK2l8aT32/PQIt9t4qhLpMRzIHk uP/vn0LFNCXrjXMEZK0maQmt9YFMNnImsujICKqnO1gS4ivLNnY3ZwU8fYZ4fzJEefqq +XnbOZTy4lvYkP9AJWUTbDalarmYukPp+Iv/L9nUBxdIvUmhGUcrUR4ZJVVbLRM2GURG w+RIhG/PVgto4MZhsLcKDBdaM6UT71VEEDU4fLm7MORpDOYPSfbEOdSOpjTnKinY8N1N cJZQ== X-Received: by 10.194.242.69 with SMTP id wo5mr49615513wjc.10.1360155311819; Wed, 06 Feb 2013 04:55:11 -0800 (PST) Received: from [10.186.92.149] ([92.90.16.78]) by mx.google.com with ESMTPS id ec3sm2824852wib.1.2013.02.06.04.55.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Feb 2013 04:55:10 -0800 (PST) References: <51124589.7080800@wp.pl> In-Reply-To: <51124589.7080800@wp.pl> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> X-Mailer: iPhone Mail (9A405) From: Damien Fleuriot Subject: Re: pkg can't access pkgbeta.freebsd.org Date: Wed, 6 Feb 2013 13:53:58 +0100 To: Marek Salwerowicz X-Gm-Message-State: ALoCoQkrVQaEZC/gsjr9tbZBAlmNv7wOT2JbPYoMcshKp5UUL/8VFRbByi+I1+i8kVL+bhcx3KUe Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 12:55:13 -0000 ":" in the URL instead of "/" , possibly ? I find it strange that there should be ":" in the URL, it is only acceptable= when denoting the destination port to connect to. Try replacing them with slashes. -- Sent from my [insert random phone here] On 6 Feb 2013, at 12:59, Marek Salwerowicz wrote: > Hi, >=20 > On freshly installed FreeBSD-9.1-Release amd64 (from ISO) I am trying to m= igrate to new generation of packages: >=20 > arch1% sudo pkg > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping pkg please wait > pkg: Error fetching http://pkgbeta.FreeBSD.org/freebsd:9:x86:64/latest/Lat= est/pkg.txz: No route to host > arch1% >=20 > arch1% traceroute pkgbeta.freebsd.org > traceroute to bwwwdyn.freebsd.org (69.147.83.39), 64 hops max, 52 byte pac= kets > 1 172.16.30.1 (172.16.30.1) 1.215 ms 1.106 ms 1.107 ms > 2 192.168.0.99 (192.168.0.99) 2.337 ms 2.474 ms 1.933 ms > 3 pw-gw-gi3-0-558.warman.nask.pl (194.181.61.225) 3.978 ms 5.550 ms 4.= 799 ms > 4 172.27.27.2 (172.27.27.2) 5.524 ms 5.292 ms 6.841 ms > 5 frankfurt-gw-ae1-100.core.nask.pl (195.187.255.183) 29.989 ms 39.843 m= s 28.430 ms > 6 ge-1-3-0.pat2.dee.yahoo.com (80.81.193.115) 28.565 ms 28.384 ms 28.2= 21 ms > 7 as-1.pat2.dcp.yahoo.com (66.196.65.129) 119.239 ms 119.011 ms 118.605= ms > 8 as-0.pat2.da3.yahoo.com (216.115.101.155) 193.173 ms 198.485 ms > ae-7.pat2.che.yahoo.com (216.115.100.137) 224.062 ms > 9 ae-6.pat1.dnx.yahoo.com (216.115.96.207) 191.784 ms > as-1.pat2.sjc.yahoo.com (216.115.101.151) 194.342 ms > ae-5.pat2.dnx.yahoo.com (216.115.96.55) 186.775 ms > 10 ae-7.pat1.sjc.yahoo.com (216.115.101.149) 189.467 ms > ae-7.pat1.pao.yahoo.com (216.115.101.128) 183.305 ms > ae-7.pat1.sjc.yahoo.com (216.115.101.149) 192.312 ms > 11 ae-0-d141.msr1.sp1.yahoo.com (216.115.107.51) 186.679 ms > ae-1-d170.msr2.sp1.yahoo.com (216.115.107.85) 221.705 ms > ae-1-d160.msr1.sp1.yahoo.com (216.115.107.61) 185.266 ms > 12 * gi-1-47.bas-b1.sp1.yahoo.com (209.131.32.45) 187.202 ms > gi-1-33.bas-b2.sp1.yahoo.com (98.136.16.33) 184.560 ms > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * *^C > arch1% ping pkgbeta.freebsd.org > PING bwwwdyn.freebsd.org (69.147.83.39): 56 data bytes >=20 > and no answer... >=20 > Regards, >=20 > --=20 > Marek Salwerowicz >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 13:03:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2B4281E2 for ; Wed, 6 Feb 2013 13:03:23 +0000 (UTC) (envelope-from jan0sch@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id A3483899 for ; Wed, 6 Feb 2013 13:03:22 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MckDn-1UKsem30Dp-00HtvK for ; Wed, 06 Feb 2013 14:03:21 +0100 Received: (qmail invoked by alias); 06 Feb 2013 13:03:21 -0000 Received: from dslb-088-074-034-053.pools.arcor-ip.net (EHLO magni.rostock.home) [88.74.34.53] by mail.gmx.net (mp028) with SMTP; 06 Feb 2013 14:03:21 +0100 X-Authenticated: #1545395 X-Provags-ID: V01U2FsdGVkX1/PWageDFTPPeHg7i6/YC9fKpv+4MSFtAxs70nd6P SksryYjTNCZOzx Date: Wed, 6 Feb 2013 14:02:44 +0100 From: Jens Jahnke To: Andriy Gapon Subject: Re: FreeBSD 9.1 occasional kernel panic Message-Id: <20130206140244.6b9f549568fc42a2e1063713@gmx.net> In-Reply-To: <51124F4F.4050902@FreeBSD.org> References: <20130206092908.d773cfde61f35347f32f6c47@gmx.net> <51124F4F.4050902@FreeBSD.org> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) X-Face: &?!P`87-36gaG)/K:yi&ixw=uy]y'?$vrc Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Wed__6_Feb_2013_14_02_44_+0100_Otcd.upgJCKx5WVO" X-Y-GMX-Trusted: 0 Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 13:03:23 -0000 --Signature=_Wed__6_Feb_2013_14_02_44_+0100_Otcd.upgJCKx5WVO Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 06 Feb 2013 14:40:47 +0200 Andriy Gapon wrote: AG> "error 6" is ENXIO, which usually corresponds to a disappearing AG> device or some such. Do you get anything in logs (or other AG> objective experience) that could look like that? Nothing found so far. System ran stable for the last 18 hours through. I'll look if the error occurs again. Regards, Jens --=20 06. Hornung 2013, 14:00 Homepage : http://www.jan0sch.de "Virtual" means never knowing where your next byte is coming from. --Signature=_Wed__6_Feb_2013_14_02_44_+0100_Otcd.upgJCKx5WVO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQG8BAEBCgAGBQJRElSXAAoJED2+SXzzbciGB8YM/jKjR+oR14O98qB4lxxcgP8g 02kSRGgUvsKW6k4NrBbNTTRfQ35XA8gSgBmtVJba3bdUSoaD1/qoHAcqYPKRsFbP 71BGtsmApgdlV3i9qIUk1hfD57V4javR8SsqW2dNhwVwO/IHGYSIDzMygub/vdUe GtsUu62odtiXQA/Pq3tMel6SGl0ttYGjrq56cex9XYPx8yduwCwhlWECkuZhaegL c5ewXbIAf1FvAKkIow5/vfovJIMfZUJcG9ngaMR1ZsFWiBp9DlCyJNtBqd2v/5RZ V/5ix8MTCj1hklmkG9GDqJ7qxLupDa2aCXt1GrOxxzuyoQoczeVsO1gXbZFPqEMP QWZkPXWvdjupPOr3x1u28Xhu12VnXdaEUbULNYiRV8VvYBdOL/rSzgfGOqlBvr60 jgaezT1+TPmYR6JwvqvPzyzRFMYJaFI+8CylDLtPPcN+xyZbr97bnm+TU7EWxVQy TFui3a0e/zPam9nSWGp3x36/JzNnYaQudGu5IGxU0t+U57DsFmeCu2EuO+EOTGHi oGmtKaSJgwqsbkYTBWNg =I0c4 -----END PGP SIGNATURE----- --Signature=_Wed__6_Feb_2013_14_02_44_+0100_Otcd.upgJCKx5WVO-- From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 13:24:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2165635B; Wed, 6 Feb 2013 13:24:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id BF5409B4; Wed, 6 Feb 2013 13:24:41 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by kabab.cs.huji.ac.il with esmtp id 1U34zP-000MUr-Sq; Wed, 06 Feb 2013 15:24:40 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: "Steven Hartland" Subject: Re: problems with the mfi In-reply-to: <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> References: <201302051224.33779.jhb@freebsd.org> <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> Comments: In-reply-to "Steven Hartland" message dated "Wed, 06 Feb 2013 12:30:04 +0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Feb 2013 15:24:39 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 13:24:42 -0000 > ----- Original Message ----- > From: "Daniel Braniss" > >> > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: > >> >> after rebooting I get very often: > >> >> ... > >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS > >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS > >> >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS > >> >> ... > >> >> > >> >> another reboot usualy fixes this. > >> > > >> > Does it have the latest firmware? > >> > >> Be aware that the current code for mfi timeout's never abort so > >> if you get a command stuck it will moan forever. > >> > >> This is one of the issues fixed in a patch that's in testing. > > > > i know :-), I caught this one because the machine was not rebooting. > > can you shed some light as to what command timed out? > > Unfortunately not it was a generic issue any command which timeout > would get stuck for ever. > > What FreeBSD version are using and what controller are you using? > freebsd-9.1-stable as of last Friday the last one that did this is: mfi1: port 0xdc00-0xdcff mem 0xd4ffc000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 66 at device 0.0 on pci65 but I saw this on older PERCs too. cheers, danny From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 14:23:41 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D03CFDEC for ; Wed, 6 Feb 2013 14:23:41 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 9904AE07 for ; Wed, 6 Feb 2013 14:23:41 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 09:23:41 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CFP65958; Wed, 6 Feb 2013 09:23:40 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp04.lnh.mail.rcn.net with ESMTP; 06 Feb 2013 09:23:40 -0500 Message-ID: <5112676B.7070202@aldan.algebra.com> Date: Wed, 06 Feb 2013 09:23:39 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: pyunyh@gmail.com Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> <5111FACB.5040104@aldan.algebra.com> <20130206071324.GB1442@michelle.cdnetworks.com> In-Reply-To: <20130206071324.GB1442@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 14:23:41 -0000 On 06.02.2013 02:13, YongHyeon PYUN wrote: >> Disabling "Wake on LAN" in the BIOS solved this problem. Now xl0 is seen >> >and functional. Solved. > Because I added WOL support xl(4) in the past I'm interested in > knowing whether that change broke your controller when BIOS enables > WOL. I can not reproduce this -- after enabling WOL in BIOS, both kernels (mine and 9.1-R GENERIC) still see xl0 now. Maybe, it is a BIOS issue -- I'm using Lattitude's BIOS version A02, but the last update from Dell before they stopped supporting the laptop is A23. Yours, -mi From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 15:20:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6F416FA2 for ; Wed, 6 Feb 2013 15:20:38 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 23D4F1EE for ; Wed, 6 Feb 2013 15:20:37 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.6/8.13.1) with ESMTP id r16FKVUd007641 for ; Wed, 6 Feb 2013 09:20:31 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Wed Feb 6 09:20:31 2013 Message-ID: <511274BA.3020604@denninger.net> Date: Wed, 06 Feb 2013 09:20:26 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013] References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> <511020DB.3050302@denninger.net> <1360012382.93359.489.camel@revolution.hippie.lan> <66CBAB45-621B-47F8-AC67-64F816AFE837@bway.net> <1360015226.93359.502.camel@revolution.hippie.lan> <51107662.8050708@denninger.net> <51107D82.8040605@denninger.net> <51108DB0.7050403@denninger.net> <51113242.4060003@denninger.net> <3af8b2a2d655b0ed501c01e30d00ff0a.authenticated@ultimatedns.net> <51113CD1.40104@denninger.net> In-Reply-To: X-Enigmail-Version: 1.5 X-Antivirus: avast! (VPS 130206-0, 02/06/2013), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 15:20:38 -0000 On 2/5/2013 11:25 AM, CeDeROM wrote: > On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger wrote: >> The FTDI adapter has the provision for an external power supply (+5V) >> but it does not require it unless you're running off an unpowered bus, >> which is not normally the case. 500ma is quite a bit of available energy. > Karl, can you please use external power supply to power up the adapter > - with and without the additional devices step by step - this way we > will eliminate one of the possible causes :-) > That's pretty-clearly not the problem -- I have removed the KVM from the system and added a couple other USB devices, including switching the UPS attached to it from serial communication to USB, and it's fine. Whatever is going on here it's KVM-related, not the FTDI box. That's an interesting issue all on its own but one that may be rather difficult to solve -- let's toss this thread and I'll start a new one when I can start chasing the KVM issue -- that's one that's not good as well, but I will check across OS revisions and see if it's limited to 9.x or whether it shows up on other, older releases as well first. -- -- Karl Denninger /The Market Ticker ®/ Cuda Systems LLC From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 15:32:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 94DA0706 for ; Wed, 6 Feb 2013 15:32:29 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-we0-x233.google.com (we-in-x0233.1e100.net [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 3200A2D5 for ; Wed, 6 Feb 2013 15:32:29 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id x43so1216946wey.24 for ; Wed, 06 Feb 2013 07:32:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=nuX9NxWsqQS/vMZbjAbJQDrvvsvluHDZzJ//07qK01o=; b=vDP863E7RuUMiLFsUIvBSIZtMGjHJF3sKCw488umAtyMa2NWzVW5D2KQXV5UtT7wJt dJ+tNncMSKYegu8yHetwsFckR7ZLeqP1Q3VwN2ZD8csk8a1OirJSFEtm6FY4Ec9TY2jE F5geUTSPndVk9Db3IvS4Scvbx4vlBTnARDdbMVFlL6teFGGEjTlOUL72cQEiN2phE1iM OBTmSDRRZ3cqC0WgOCXoW9i8eMBDfbhUxg1VHP878qzS68hBfZDmaU1AOPSxb+V758HI uLX9qbAGX4EPGqxgrql8GiITOWwOphuUrFTIRWSaqBcZIOx1MlDoNOu3z3s7CBrN82xo dmKA== X-Received: by 10.180.14.166 with SMTP id q6mr5845574wic.22.1360164748398; Wed, 06 Feb 2013 07:32:28 -0800 (PST) Received: from Melon.malikania.fr (177.33.91.91.rev.sfr.net. [91.91.33.177]) by mx.google.com with ESMTPS id fx5sm3932428wib.11.2013.02.06.07.32.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Feb 2013 07:32:27 -0800 (PST) Message-ID: <51127767.1030007@gmail.com> Date: Wed, 06 Feb 2013 16:31:51 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130115 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Panic at shutdown Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 15:32:29 -0000 Hello there, I recently had a panic at shutdown in 9.1-STABLE, there's the backtrace: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: <118>. <118>Feb 5 23:30:31 Melon syslogd: exiting on signal 15 <5>wlan0: link state changed to DOWN <5>lagg0: link state changed to DOWN Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...7 1 1 0 done All buffers synced. ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfffffe0001807678 (20110527/exresop-443) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.SMAB] (Node 0xfffffe00017edc08), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._TMP] (Node 0xfffffe00017d3280), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.INTM] (Node 0xfffffe00017d4168), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.DTSZ._TMP] (Node 0xfffffe00017d4500), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfffffe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.CPUZ._TMP] (Node 0xfffffe00017d41e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfffffe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.SKNZ._TMP] (Node 0xfffffe00017d8258), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfffffe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.BATZ._TMP] (Node 0xfffffe00017d8118), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.KRFS] (Node 0xfffffe00017e71e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.GRFS] (Node 0xfffffe00017f37f8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.FDTZ._TMP] (Node 0xfffffe00017d8078), AE_AML_OPERAND_TYPE (20110527/psparse-560) Uptime: 2h1m59s ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEGP.DGFX._DOS] (Node 0xfffffe00017d9528), AE_AML_OPERAND_TYPE (20110527/psparse-560) can't evaluate \_SB_.PCI0.PEGP.DGFX._DOS - AE_AML_OPERAND_TYPE usbus0: Controller shutdown uhub0: at usbus0, port 1, addr 1 (disconnected) ugen0.2: at usbus0 (disconnected) ubt0: at uhub0, port 1, addr 2 (disconnected) usbus0: Controller shutdown complete usbus1: Controller shutdown uhub1: at usbus1, port 1, addr 1 (disconnected) usbus1: Controller shutdown complete usbus2: Controller shutdown uhub2: at usbus2, port 1, addr 1 (disconnected) usbus2: Controller shutdown complete usbus3: Controller shutdown uhub3: at usbus3, port 1, addr 1 (disconnected) ugen3.2: at usbus3 (disconnected) usbus3: Controller shutdown complete usbus4: Controller shutdown uhub4: at usbus4, port 1, addr 1 (disconnected) usbus4: Controller shutdown complete usbus5: Controller shutdown uhub5: at usbus5, port 1, addr 1 (disconnected) usbus5: Controller shutdown complete usbus6: Controller shutdown uhub6: at usbus6, port 1, addr 1 (disconnected) usbus6: Controller shutdown complete usbus7: Controller shutdown uhub7: at usbus7, port 1, addr 1 (disconnected) usbus7: Controller shutdown complete Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff802abefe stack pointer = 0x28:0xffffff80002154a0 frame pointer = 0x28:0xfffffe00108ba7b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1 (init) trap number = 12 panic: page fault cpuid = 0 Uptime: 2h2m5s Dumping 352 out of 3054 MB:..5%..14%..23%..32%..41%..55%..64%..73%..82%..91% Reading symbols from /boot/kernel/vboxdrv.ko...done. Loaded symbols for /boot/kernel/vboxdrv.ko #0 doadump (textdump=) at pcpu.h:229 229 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) bt #0 doadump (textdump=) at pcpu.h:229 #1 0x0000000000000000 in ?? () (kgdb) bt full #0 doadump (textdump=) at pcpu.h:229 No locals. #1 0x0000000000000000 in ?? () No symbol table info available. (kgdb) Cheers, From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 15:51:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 788D02CA; Wed, 6 Feb 2013 15:51:50 +0000 (UTC) (envelope-from prvs=174982bc16=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id CB8CB3CE; Wed, 6 Feb 2013 15:51:49 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50002047832.msg; Wed, 06 Feb 2013 15:51:46 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 06 Feb 2013 15:51:46 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=174982bc16=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <2575007EB16D444D9DA90D903BA7299A@multiplay.co.uk> From: "Steven Hartland" To: "Daniel Braniss" References: <201302051224.33779.jhb@freebsd.org> <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> Subject: Re: problems with the mfi Date: Wed, 6 Feb 2013 15:51:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 15:51:50 -0000 ----- Original Message ----- From: "Daniel Braniss" >> Unfortunately not it was a generic issue any command which timeout >> would get stuck for ever. >> >> What FreeBSD version are using and what controller are you using? >> > freebsd-9.1-stable as of last Friday > > the last one that did this is: > mfi1: port 0xdc00-0xdcff mem 0xd4ffc000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 66 at device 0.0 on pci65 > > but I saw this on older PERCs too. I've got a set of patches which should definitely stop the continuous moaning, but also may prevent the issue as it has significant fixes for tbolt cards which the H810 is. Would you would like try them? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 16:38:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B370342A for ; Wed, 6 Feb 2013 16:38:49 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by mx1.freebsd.org (Postfix) with ESMTP id 4E0F17F5 for ; Wed, 6 Feb 2013 16:38:49 +0000 (UTC) Received: by mail-ee0-f47.google.com with SMTP id e52so916269eek.34 for ; Wed, 06 Feb 2013 08:38:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=gVR087fOP3X5SFlq3cGTGx5/DUFozEQaSYPxByCTY9g=; b=QtoS75SBC2ax0XsWf9M4kecb+YbUHwMmI7e0bCCqydghkzPYw0OBfYVaJ4OJyNkLM2 dxm3tsTD4zDubpWHjuB1OygIifYasyN7h8ISb0edH0xLtw6R4mXk/WWZT9RKBCSAq/sf fvc0THmXDBXdIX4e0lA6fuK/XD/pobuxQeqGIbTKu6rEY/m5CH6yrQG81iKTH2FUBNfQ +UIZUEOzoMVfGVyrh9ZXpoONVK8B5XGua3zt6hwk5dZXHTdGll0U4Bg+5Bh51Gd6Tl5P hE6/J0NlV8VIqf8I7tPppdY+lOVnLhdVLmOxF+U4OVFwexty2FifQwszZpasXeehaqbd zdAg== X-Received: by 10.14.178.196 with SMTP id f44mr98773085eem.14.1360168728265; Wed, 06 Feb 2013 08:38:48 -0800 (PST) Received: from Melon.malikania.fr (177.33.91.91.rev.sfr.net. [91.91.33.177]) by mx.google.com with ESMTPS id b2sm37647063eep.9.2013.02.06.08.38.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Feb 2013 08:38:47 -0800 (PST) Message-ID: <511286F4.5020208@gmail.com> Date: Wed, 06 Feb 2013 17:38:12 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130115 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Panic at shutdown References: <51127767.1030007@gmail.com> In-Reply-To: <51127767.1030007@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 16:38:49 -0000 On 06/02/2013 16:31, David Demelier wrote: > Hello there, > > I recently had a panic at shutdown in 9.1-STABLE, there's the backtrace: > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > <118>. > <118>Feb 5 23:30:31 Melon syslogd: exiting on signal 15 > <5>wlan0: link state changed to DOWN > <5>lagg0: link state changed to DOWN > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...7 1 1 0 done > All buffers synced. > ACPI Error: Needed [Integer/String/Buffer], found [Reference] > 0xfffffe0001807678 (20110527/exresop-443) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.SMAB] (Node > 0xfffffe00017edc08), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._TMP] (Node > 0xfffffe00017d3280), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 > (20110527/exresop-116) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_TZ_.INTM] (Node > 0xfffffe00017d4168), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.DTSZ._TMP] (Node > 0xfffffe00017d4500), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Needed [Integer/String/Buffer], found [Reference] > 0xfffffe0001807678 (20110527/exresop-533) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node > 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.CPUZ._TMP] (Node > 0xfffffe00017d41e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Needed [Integer/String/Buffer], found [Reference] > 0xfffffe0001807678 (20110527/exresop-533) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node > 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.SKNZ._TMP] (Node > 0xfffffe00017d8258), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Needed [Integer/String/Buffer], found [Reference] > 0xfffffe0001807678 (20110527/exresop-533) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node > 0xfffffe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.BATZ._TMP] (Node > 0xfffffe00017d8118), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 > (20110527/exresop-116) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.KRFS] > (Node 0xfffffe00017e71e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_SB_.GRFS] (Node > 0xfffffe00017f37f8), AE_AML_OPERAND_TYPE (20110527/psparse-560) > ACPI Error: Method parse/execution failed [\_TZ_.FDTZ._TMP] (Node > 0xfffffe00017d8078), AE_AML_OPERAND_TYPE (20110527/psparse-560) > Uptime: 2h1m59s > ACPI Error: Needed type [Reference], found [Integer] 0xfffffe0001807678 > (20110527/exresop-116) > ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for > [OpcodeName unavailable] (20110527/dswexec-498) > ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEGP.DGFX._DOS] > (Node 0xfffffe00017d9528), AE_AML_OPERAND_TYPE (20110527/psparse-560) > can't evaluate \_SB_.PCI0.PEGP.DGFX._DOS - AE_AML_OPERAND_TYPE > usbus0: Controller shutdown > uhub0: at usbus0, port 1, addr 1 (disconnected) > ugen0.2: at usbus0 (disconnected) > ubt0: at uhub0, port 1, addr 2 (disconnected) > usbus0: Controller shutdown complete > usbus1: Controller shutdown > uhub1: at usbus1, port 1, addr 1 (disconnected) > usbus1: Controller shutdown complete > usbus2: Controller shutdown > uhub2: at usbus2, port 1, addr 1 (disconnected) > usbus2: Controller shutdown complete > usbus3: Controller shutdown > uhub3: at usbus3, port 1, addr 1 (disconnected) > ugen3.2: at usbus3 (disconnected) > usbus3: Controller shutdown complete > usbus4: Controller shutdown > uhub4: at usbus4, port 1, addr 1 (disconnected) > usbus4: Controller shutdown complete > usbus5: Controller shutdown > uhub5: at usbus5, port 1, addr 1 (disconnected) > usbus5: Controller shutdown complete > usbus6: Controller shutdown > uhub6: at usbus6, port 1, addr 1 (disconnected) > usbus6: Controller shutdown complete > usbus7: Controller shutdown > uhub7: at usbus7, port 1, addr 1 (disconnected) > usbus7: Controller shutdown complete > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x8 > fault code = supervisor write data, page not present > instruction pointer = 0x20:0xffffffff802abefe > stack pointer = 0x28:0xffffff80002154a0 > frame pointer = 0x28:0xfffffe00108ba7b0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1 (init) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 2h2m5s > Dumping 352 out of 3054 MB:..5%..14%..23%..32%..41%..55%..64%..73%..82%..91% > > Reading symbols from /boot/kernel/vboxdrv.ko...done. > Loaded symbols for /boot/kernel/vboxdrv.ko > #0 doadump (textdump=) at pcpu.h:229 > 229 __asm("movq %%gs:%1,%0" : "=r" (td) > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:229 > #1 0x0000000000000000 in ?? () > (kgdb) bt full > #0 doadump (textdump=) at pcpu.h:229 > No locals. > #1 0x0000000000000000 in ?? () > No symbol table info available. > (kgdb) > > Cheers, > My other machine (9.1-RELEASE) just had exactly the same panic but at runtime without doing anything. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 23:20:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B577F797 for ; Wed, 6 Feb 2013 23:20:33 +0000 (UTC) (envelope-from dustinwenz@ebureau.com) Received: from internet02.ebureau.com (internet02.tru-signal.biz [65.127.24.21]) by mx1.freebsd.org (Postfix) with ESMTP id 85415260 for ; Wed, 6 Feb 2013 23:20:33 +0000 (UTC) Received: from internet06.ebureau.com (internet06.ebureau.com [65.127.24.25]) by internet02.ebureau.com (Postfix) with ESMTP id ADCCDE52295 for ; Wed, 6 Feb 2013 17:15:10 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by internet06.ebureau.com (Postfix) with ESMTP id 86F481A5A19C for ; Wed, 6 Feb 2013 17:15:10 -0600 (CST) X-Virus-Scanned: amavisd-new at ebureau.com Received: from internet06.ebureau.com ([127.0.0.1]) by localhost (internet06.ebureau.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpJhUPLt7KAo for ; Wed, 6 Feb 2013 17:15:09 -0600 (CST) Received: from square.office.ebureau.com (square.office.ebureau.com [10.10.20.22]) by internet06.ebureau.com (Postfix) with ESMTPSA id F10BD1A5A186 for ; Wed, 6 Feb 2013 17:15:09 -0600 (CST) From: Dustin Wenz Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: I/O hanging while hosting Postgres database Message-Id: Date: Wed, 6 Feb 2013 17:15:09 -0600 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 23:20:33 -0000 I'm seeing a condition on FreeBSD 9.1 (built October 24th) where I/O = seems to hang on any local zpools after several hours of hosting a = large-ish Postgres database. The database occupies about 14TB of a 38TB = zpool with a single SSD ZIL. The OS is on a ZFS boot disk. The system = also has 24GB of physical memory. Smartmon tools reports no errors on = any disks attached to the system, and IPMI reports all temperatures, CPU = voltages, and fan speeds are normal. The database has been gradually increasing in size since it was first = deployed on FreeBSD 9.1 this fall. There were no problems until last = night, when the database became unresponsive. Attempts to interact with = the shell would block (specifically, any interaction with the disk), and = no error messages were logged to the console. I restarted the system at = that time, and brought the database back up. Everything seemed normal = until this morning, where the database had become unresponsive again. = Fortunately, I was able to grab some system statistics before the shell = and console went AWOL. The only finding that I thought was suspicious were the kmem_map = numbers: vm.kmem_map_free: 655360 vm.kmem_map_size: 17141383168 It's something like 0.004% free. I haven't been able to find much = documentation on what to expect here, but I don't see anything like that = for other databases that I've monitored. It is possible that kmem_map = can become exhausted without generating a kernel panic? Could it be = indicative of severe memory fragmentation? - .Dustin From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 08:18:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7A18EA99 for ; Thu, 7 Feb 2013 08:18:12 +0000 (UTC) (envelope-from mcg@sulfegate.org) Received: from mail-ie0-x22c.google.com (ie-in-x022c.1e100.net [IPv6:2607:f8b0:4001:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 1B8CA817 for ; Thu, 7 Feb 2013 08:18:11 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id c10so3163755ieb.3 for ; Thu, 07 Feb 2013 00:18:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sulfegate.org; s=google; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=R65506cVZHBAY1UaZ8Zm8HqRIFpzzr54xcOPAyHp4/U=; b=Ei5Co4CBT+QxqWVRheyuAwi1kiLUMnaqx4XzeyWwBH7L1h9wlj19f65PZfntp3pUP9 PFeNv8HB5w9T+Kz4C3rEgOxU19VLQ9okaNVxUgD1W2EiSH6jhXXKnzVYq1r0U4e/z3wN IiHeRjGRTX09QcznsdLlQJkUdkBvOA7VLJ/os= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:x-gm-message-state; bh=R65506cVZHBAY1UaZ8Zm8HqRIFpzzr54xcOPAyHp4/U=; b=eoIUETmy/H2ezg6NeR+m67KDawRgawJ7I24qP6PIRMl7mDI8lL12+Tj9jY2l/KgZBx 4FjDNIYHRwsByJKu0DsR5OjkLoAhU4KHUFiZI2fOoIUAD+5z+q1gOK351aJg8m3kvvyp URifllZOtwON2h2Kh/fDadYmMDrfhPHfPtx9h8S/tPSbocVT75JVe5WI8Na+kEG5vauQ PWCGo8kRt6tT/j3lGLcMgHXYYsdU/DxDJaU6ck994UPmNsZdszZL3mCMjSJX2BU/TFan O5paJ6MoHJAYN9B5V0DGV7l4M4oSCM8gxlrEp+NHJnlAhXkNOCGRwb8hz18fBoLPd8m4 3DvQ== X-Received: by 10.42.98.76 with SMTP id r12mr802450icn.10.1360225091498; Thu, 07 Feb 2013 00:18:11 -0800 (PST) MIME-Version: 1.0 Sender: mcg@sulfegate.org Received: by 10.50.158.161 with HTTP; Thu, 7 Feb 2013 00:17:41 -0800 (PST) X-Originating-IP: [2001:470:1f05:6c6::100] In-Reply-To: <20130206062520.GA79498@icarus.home.lan> References: <20130206011007.GA72256@icarus.home.lan> <20130206062520.GA79498@icarus.home.lan> From: "Galati, Michael" Date: Thu, 7 Feb 2013 00:17:41 -0800 X-Google-Sender-Auth: KvwRv_GWuoflQFDp7wzkEwq5UFU Message-ID: Subject: Re: csh/tcsh: odd %~ prompt variable behaviour To: Jeremy Chadwick X-Gm-Message-State: ALoCoQnnIqWa2M9bA5ZIHhwRPC0xYRq9Dl6vsjfsoIcl0pxh7l4LBEXwMzzIUuGEGTjDR32XNgiW Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 08:18:12 -0000 Sorry, I meant to include that with my previous mail. echo $version tcsh 6.18.01 (Astron) 2012-02-14 (x86_64-unknown-linux) options wide,nls,dl,al,kan,rh,nd,color,filec Let me know if you need any more info. On Tue, Feb 5, 2013 at 10:25 PM, Jeremy Chadwick wrote: > Michael, > > Thank you very much! What tcsh version is that? "echo $version" should > say. :-) > > -- > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > On Tue, Feb 05, 2013 at 10:05:44PM -0800, Galati, Michael wrote: > > Looks like it could be FreeBSD specific... I very rarely use {,t}csh > > myself. > > > > user@host:~$ uname -a > > Linux host 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 > > x86_64 x86_64 x86_64 GNU/Linux > > user@host:~$ sudo -i > > [sudo] password for user: > > root@host:~# tcsh > > host:~# set prompt = "%N@%m:%~ %# " > > root@host:~ # asdfasdf > > asdfasdf: Command not found. > > root@host:~ # cd ~user > > root@host:~user # asdfasdf > > asdfasdf: Command not found. > > root@host:~user # exit > > root@host:~# logout > > > > > > > > On Tue, Feb 5, 2013 at 5:10 PM, Jeremy Chadwick wrote: > > > > > (Please keep me CC'd as I'm not subscribed to the list) > > > > > > > > > System is base/stable/9, r245697. tcsh version is 6.18.01: > > > > > > $ sudo -i > > > root@icarus:~ # sfdjsdj > > > sfdjsdj: Command not found. > > > root@icarus:~ # cd ~root > > > root@icarus:~ # dsjfdsfdsf > > > dsjfdsfdsf: Command not found. > > > root@icarus:~ # cd ~jdc > > > root@icarus:~jdc # sdjfdjkfjdsk > > > sdjfdjkfjdsk: Command not found. > > > root@icarus:/home/jdc # <---- notice sudden prompt change > > > root@icarus:/home/jdc # cd ~root > > > root@icarus:~ # dsfjjdskdfs > > > dsfjjdskdfs: Command not found. > > > root@icarus:~ # logout > > > > > > This only happens when an invalid command is issued (e.g. had I used > > > "ls" instead of "blah" the prompt would not have changed). > > > > > > $prompt is the standard /root/.cshrc (r244005) value: > > > > > > set prompt = "%N@%m:%~ %# " > > > > > > I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02: > > > > > > $ ssh jdc@192.168.1.161 > > > Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 > > > > > > Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan > > > jdc@debian:~$ sudo -i > > > root@debian:~# /bin/tcsh > > > debian:~# set prompt = "%N@%m:%~ %# " > > > root@debian:~ # sdfsdf > > > sdfsdf: Command not found. > > > root@debian:~ # cd ~jdc > > > root@debian:~jdc # sdfssgsgjsj > > > sdfssgsgjsj: Command not found. > > > root@debian:~jdc # exit > > > root@debian:~# logout > > > > > > The number of changes between 6.17.02 and 6.18.01 seem quite large > > > (looking at src/contrib/tcsh/Fixes). > > > > > > Does anyone have a non-FreeBSD system with tcsh 6.18.01 available > > > to determine if this is a FreeBSD-centric issue or an actual issue with > > > tcsh that needs to be reported upstream? > > > > > > Thanks. > > > > > > -- > > > | Jeremy Chadwick jdc@koitsu.org | > > > | UNIX Systems Administrator http://jdc.koitsu.org/ | > > > | Mountain View, CA, US | > > > | Making life hard for others since 1977. PGP 4BD6C0CB | > > > > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to " > freebsd-stable-unsubscribe@freebsd.org" > > > > From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 08:55:14 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A32842B4 for ; Thu, 7 Feb 2013 08:55:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BBEFEE40 for ; Thu, 7 Feb 2013 08:55:12 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA26686; Thu, 07 Feb 2013 10:55:10 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U3NG9-000Nah-SO; Thu, 07 Feb 2013 10:55:09 +0200 Message-ID: <51136BED.2040607@FreeBSD.org> Date: Thu, 07 Feb 2013 10:55:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: David Demelier Subject: Re: Panic at shutdown References: <51127767.1030007@gmail.com> <511286F4.5020208@gmail.com> In-Reply-To: <511286F4.5020208@gmail.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 08:55:14 -0000 Without so much as a stack trace there is nothing to chew on. A useable vmcore would be better. Did you perhaps use kgdb with a mismatching kernel? -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 09:06:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96618773; Thu, 7 Feb 2013 09:06:39 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id EA46AEE7; Thu, 7 Feb 2013 09:06:38 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id es5so1775359wgb.17 for ; Thu, 07 Feb 2013 01:06:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CpLk7tFXZJG+E/CO5mB0mLaXWPf97Oq+hb43uXJ1VNI=; b=NutjdHqQ/QiufJgq4nJXf9syeJzJdy+yuc3orSbRQvT/wYwuEm75rFJR+2cvov2jcC wEr4ypu5y4XjQrr/efATBx5g67nop56UTFzykQtllxiAxJCpBpBZWTKYYzsMl1SCFuWi ns7ltGmIwMG8gBPmhV/MtNKq35uaQkOP9RHzVJNbOxIFm7nDVT6Sf2tQNXigTKm1A/Zl ZRN+Kg1AjptX3NIcpblLXLqpCotNSPZc6cxBBrCJjziMb3Mlpuvh1Uk34CXqeRAIaamR 0ZYQ+cPEfoPmoDuL/7XKygELPqX/pSFC90sNGlSidp3IkftvIBjrjRvhr2rZL0GxLJ0v Sh/g== X-Received: by 10.180.8.4 with SMTP id n4mr1036786wia.13.1360227989565; Thu, 07 Feb 2013 01:06:29 -0800 (PST) Received: from Melon.malikania.fr (wifi-osiris-sec-183-18.u-strasbg.fr. [130.79.183.18]) by mx.google.com with ESMTPS id j9sm7342996wia.5.2013.02.07.01.06.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Feb 2013 01:06:28 -0800 (PST) Message-ID: <51136E70.5050901@gmail.com> Date: Thu, 07 Feb 2013 10:05:52 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130115 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: Panic at shutdown References: <51127767.1030007@gmail.com> <511286F4.5020208@gmail.com> <51136BED.2040607@FreeBSD.org> In-Reply-To: <51136BED.2040607@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 09:06:39 -0000 On 07/02/2013 09:55, Andriy Gapon wrote: > > Without so much as a stack trace there is nothing to chew on. > A useable vmcore would be better. > > Did you perhaps use kgdb with a mismatching kernel? > I don't remember, I just rebuild a new kernel and will provide more info if panic occurs again! From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 12:02:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DBF21C67 for ; Thu, 7 Feb 2013 12:02:41 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCD695A for ; Thu, 7 Feb 2013 12:02:41 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id a22so957194qcs.12 for ; Thu, 07 Feb 2013 04:02:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=saTAu/FcWNC3T0gYRk6toX2ALETDjtfx9xt/vwsKgrw=; b=U9b6ORNjhBHKsp6mMpOyxdPWBqYxs2Emusfl65zXcubf0rCPTTv7HCYRRMorvgVi8k mMuHLY4pTIi8ROUyqS55C3wv/Q83HFlk6ZKihtQZtOnfcSxyOpwRp9aK3kRRXdB9cIFU LKPXd6vSwryvwqtjOSIQYXtkfVFn3a3gF0NFa8XRm5/hgZZ7JycauXIlg/pH5u8b1Fqz SdC7rnp6W8jwfl1lavWd8obBAtanuP1wtYSDIYpwmHG+rGzoP0BMrLTbX6tuQQ/KIiif ExT2l8j8q7whvSXtAfmlbFcYZUnblV9DIhalAmJ8468u2JkuewWsrIG6Y+hJPfk92w1h lBOw== MIME-Version: 1.0 X-Received: by 10.49.72.136 with SMTP id d8mr428300qev.62.1360238560753; Thu, 07 Feb 2013 04:02:40 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Thu, 7 Feb 2013 04:02:40 -0800 (PST) Date: Thu, 7 Feb 2013 13:02:40 +0100 X-Google-Sender-Auth: wtXKpb2WSzjWOSeNt2OnTPyeuXs Message-ID: Subject: usb mass storage problem From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 12:02:41 -0000 Hello :-) I have a problem with HP USB Pendrive 8GB memory - it works on Windows and Linux but it does not detect on FreeBSD 9.1(-RC3): ugen1.7: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:5:0:-1: Attached to scbus5 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:0): Retrying command (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:0): Retrying command (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:0): Retrying command Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 12:16:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3DF9714E for ; Thu, 7 Feb 2013 12:16:30 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id C99889FF for ; Thu, 7 Feb 2013 12:16:29 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::726]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r17CGN6E020724 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 7 Feb 2013 18:16:24 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <51139B17.9000004@norma.perm.ru> Date: Thu, 07 Feb 2013 18:16:23 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: zfs v28 solaris compatibility Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Thu, 07 Feb 2013 18:16:24 +0600 (YEKT) X-Spam-Status: No hits=-95.3 bayes=0.5 testhits RDNS_NONE=1.274, SPF_SOFTFAIL=0.972,TO_NO_BRKTS_DIRECT=2.455,USER_IN_WHITELIST=-100 autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 12:16:30 -0000 Hi. Is the FreeBSD v28 zfs fully compatible with solaris zfs ? I need to switch disks between servers, these disks are SAN disks, and it's about 20T of data. I don't want to lose them. I am aware that our zfs is compatible with Solaris, but I just want to be sure, like really really sure. Of course I can switch back at any moment, but only if the data won't become corrupted. Thanks. Eugene. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 13:38:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2DD85C86 for ; Thu, 7 Feb 2013 13:38:43 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by mx1.freebsd.org (Postfix) with ESMTP id A8C6BEAD for ; Thu, 7 Feb 2013 13:38:42 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id gf7so2092979lbb.4 for ; Thu, 07 Feb 2013 05:38:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+UHT8ed/ixLAsgbzYPjgJSdOnyr+iRi/vLuD41EDkVo=; b=d2GBH+IXZlFGuGGJ9jtjULfmY3ZYnIJxmBLAOyvBzem3JzfeOZ0b0LVki+l59J8UBN irRakB18Lm/lLEi884ZzTndPOSMEDRynQr6aL+hXtXXaFt3WT4pMSJI4R3646O2aq6IP U6d51X/hFxxYL16b8slU5tcpEg0VMIlRqnKNx1tJjNSslK1cwCbSMYuJU2H2PdjS3tb4 U6YT7PRnCsP7lveNj01oZa/CCOCMD75rFFSMtyxdw5XwUfEKSawQ5aeM+KbHf9UAF/9E +CXX+Y7giOpsh40n8T9A3HJAsnMCezasLiN0LiTpYGnJf8zbBppLVNIrs4pQDOhI2oI1 Ao8g== X-Received: by 10.152.136.20 with SMTP id pw20mr1348986lab.16.1360243909686; Thu, 07 Feb 2013 05:31:49 -0800 (PST) Received: from [192.168.1.128] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id ns7sm14836414lab.5.2013.02.07.05.31.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Feb 2013 05:31:48 -0800 (PST) Message-ID: <5113ACBA.9080502@gmail.com> Date: Thu, 07 Feb 2013 15:31:38 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: "Eugene M. Zheganin" Subject: Re: zfs v28 solaris compatibility References: <51139B17.9000004@norma.perm.ru> In-Reply-To: <51139B17.9000004@norma.perm.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 13:38:43 -0000 07.02.2013 14:16, Eugene M. Zheganin: > Hi. > > Is the FreeBSD v28 zfs fully compatible with solaris zfs ? I need to > switch disks between servers, these disks are SAN disks, and it's about > 20T of data. I don't want to lose them. I am aware that our zfs is > compatible with Solaris, but I just want to be sure, like really really > sure. Of course I can switch back at any moment, but only if the data > won't become corrupted. I think one simple way to test that is to create a replication stream for some filesystem with `zfs send` on first machine and check whether this stream is received correctly on the second machine. I'm mostly sure that you wouldn't lose your data, however Solaris is staying with ZFS v28 since the last release and FreeBSD is progressing slowly with Illumos. I'm pretty sure that 9-STABLE is already using ZFS feats and any pool created with current STABLE would not become writable for Solaris. -- Sphinx of black quartz, judge my vow. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 14:05:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EE2873FC for ; Thu, 7 Feb 2013 14:05:54 +0000 (UTC) (envelope-from januszbulik@googlemail.com) Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by mx1.freebsd.org (Postfix) with ESMTP id 65A7E29 for ; Thu, 7 Feb 2013 14:05:54 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id 16so2045214wgi.27 for ; Thu, 07 Feb 2013 06:05:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=GAAPYVn/K8gThhYj72tPbgPH/f6/Gd+hO4dw1+wPeLw=; b=qfwUedDvfvDI+Z3RmYnF/jkpyjhNGrmwJBNxZNXsEarh+G/sBkDj6Xrd/9xs60BYca Nn4GR6ApobBdJghz3HjtjqVC2TnpHqOiMFwqUvCa4PbinDQ40Uj4ZOfuwj2Rdv6/Y05Z JzylRnGTQzBM3t7WaaIvHB9cw/8Ysgau5h7vvk2epmOOlkI57e7b9jdU1Q6Z3EshKTyy FyuEJ4TSsW3qoftVyqzx6QNRvTEGQGxypEtIM2KfNCNZrEPMm1VH+U1UPI7y6ZFKMxjg ctnuqaOWcCpSGBri78Yfhzh/hBzd81Rt8vf66Bj7TvP2edDp/iwVO6/+3EdXVWX0vx/b vY9Q== MIME-Version: 1.0 X-Received: by 10.180.92.100 with SMTP id cl4mr11994971wib.24.1360245953280; Thu, 07 Feb 2013 06:05:53 -0800 (PST) Received: by 10.180.126.97 with HTTP; Thu, 7 Feb 2013 06:05:53 -0800 (PST) Date: Thu, 7 Feb 2013 15:05:53 +0100 Message-ID: Subject: NFSv4 + Kerberos permission denied From: Janusz Bulik To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 14:05:55 -0000 Hello, I've got a little problem with NFSv4 + Kerberos. I can do a mount with Kerberos with a valid ticket, but read-only. After the mount -vvv -t nfs -o nfsv4,sec=krb5 nfsserver:/ /mount_test/ I can see: #klist: Feb 6 07:22:47 Feb 6 17:22:43 nfs/nfsserver@my.domain #/var/heimdal/kdc.log: 2013-02-06T07:28:26 TGS-REQ clientnfs@my.domain from IPv4:192.168.0.23 for nfs/nfsserver@my.domain tcpdump: 14:59:36.140272 IP nfsclient.61011 > 192.168.0.21.kerberos-sec: 14:59:36.142301 IP 192.168.0.21.kerberos-sec > nfsclient.61011: I got "Permission denied" message when I try to mkdir or rm. As a root mount and as a user mount (sysctl vfs.usermounts=1). With -sec=sys it works read-write, but with -sec=krb5 read-only.. my /etc/exports: V4: /export_test -sec=krb5:krb5i:krb5p -network 192.168.0.0 -mask 255.255.255.0 /export_test -sec=krb5:krb5i:krb5p -network 192.168.0.0 -mask 255.255.255.0 -maproot=root -alldirs tried with V4: / .... as well. Added all the principals needed. Tried also with full qualified domain names. SSH works fine with Kerberos Do I need rpcsec_gss.patch? (according to http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup) or can I make it work somehow else? I used FreeBSD-9.1-RELEASE-i386-disc1 and FreeBSD-10.0-CURRENT-i386-20130202-r246254-release -- Greets Janusz From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 14:10:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3B35254F for ; Thu, 7 Feb 2013 14:10:33 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id E6E8AAD for ; Thu, 7 Feb 2013 14:10:32 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1U3SBM-000ILd-8U for freebsd-stable@freebsd.org; Thu, 07 Feb 2013 15:10:32 +0100 Date: Thu, 7 Feb 2013 15:10:32 +0100 From: Kurt Jaeger To: freebsd-stable@freebsd.org Subject: ethtool-like utility for FreeBSD ? Message-ID: <20130207141032.GT8239@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 14:10:33 -0000 Hi! There is a posting public about Intel ethernet adapters and their packets of death: http://blog.krisk.org/2013/02/packets-of-death.html Now, how can we test the EEPROM from FreeBSD, similar to the ethtool of Linux ? Thanks for any pointer! -- pi@opsec.eu +49 171 3101372 7 years to go ! From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 16:20:15 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B997C444 for ; Thu, 7 Feb 2013 16:20:15 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by mx1.freebsd.org (Postfix) with ESMTP id 82FEAB29 for ; Thu, 7 Feb 2013 16:20:15 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id cr7so2901834qab.15 for ; Thu, 07 Feb 2013 08:20:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6DUsAJNixpOZDyKTMmNkNTCRFO3zB/aXu1d4rC5Gzsw=; b=F8RzFnbQH65y6iFYX9XPJ5aQO0BM+N9kLBiw2Eb98GXbjz55Q0AopsSQe2SioNZXF3 WTsep9WG/4wEGrBVg5kaXkHL/1iyEp/Qw2rZJNb3k6CD/rx9tmEpOKv9M1KBHQ7Q5DDb t+u6hhXi+HNIBiE/GGFwyCmnR2HLQK3omn0RJFAyIIhKN7LGvwwTxs3JkfWnc14malXC t6urnlnVdGdHGgEcfkKDIjqX5JqgV0HvtGu6fIJ8qxIDsrpZ9nw6sILRHE8dxf7/bUnp OuYzy6Q3tZpFjPmtduPlHanCy94HkGqUajeiDAGrxLi8FnN5WuIOQzIlx9x0Xy83p3lG aj2A== MIME-Version: 1.0 X-Received: by 10.49.34.146 with SMTP id z18mr845282qei.29.1360254009573; Thu, 07 Feb 2013 08:20:09 -0800 (PST) Received: by 10.49.106.233 with HTTP; Thu, 7 Feb 2013 08:20:09 -0800 (PST) In-Reply-To: <51139B17.9000004@norma.perm.ru> References: <51139B17.9000004@norma.perm.ru> Date: Thu, 7 Feb 2013 08:20:09 -0800 Message-ID: Subject: Re: zfs v28 solaris compatibility From: Freddie Cash To: "Eugene M. Zheganin" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 16:20:15 -0000 If the pool is created as v28 in FreeBSD, then you will be able to import the pool into Solaris 10 or 11 without any issues. Just be sure to ignore all the "your pool is outdated messages", and do *NOT* upgrade your pool to ZFSv32 in Solaris. If you do that, you will not be able to import the pool in FreeBSD again. On Thu, Feb 7, 2013 at 4:16 AM, Eugene M. Zheganin wrote: > Hi. > > Is the FreeBSD v28 zfs fully compatible with solaris zfs ? I need to > switch disks between servers, these disks are SAN disks, and it's about > 20T of data. I don't want to lose them. I am aware that our zfs is > compatible with Solaris, but I just want to be sure, like really really > sure. Of course I can switch back at any moment, but only if the data > won't become corrupted. > > Thanks. > Eugene. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 18:22:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BAA7E773 for ; Thu, 7 Feb 2013 18:22:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 99A8D2BD for ; Thu, 7 Feb 2013 18:22:58 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CBC8AB924; Thu, 7 Feb 2013 13:22:57 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop Date: Thu, 7 Feb 2013 13:16:29 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> In-Reply-To: <5111F739.7070607@aldan.algebra.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201302071316.29898.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 07 Feb 2013 13:22:57 -0500 (EST) Cc: "Mikhail T." X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 18:22:58 -0000 On Wednesday, February 06, 2013 1:24:57 am Mikhail T. wrote: > On 05.02.2013 23:38, Mikhail T. wrote: > > What happened between 6.x and 7.x? > Ok, what happened is that "device cpufreq" is now in GENERIC and the > ichss0 along with it. > > Setting > > set hint.ichss.0.disabled=1 > > on the loader prompt allows me to boot -- both my own kernel as well as > the 9.1-RELEASE from CD. Solved... Annoying beyond belief, but solved. I wonder if your system falls into this: /* * ICH2/3/4-M I/O Controller Hub is at bus 0, slot 1F, function 0. * E.g. see Section 6.1 "PCI Devices and Functions" and table 6.1 of * Intel(r) 82801BA I/O Controller Hub 2 (ICH2) and Intel(r) 82801BAM * I/O Controller Hub 2 Mobile (ICH2-M). * * TODO: add a quirk to disable if we see the 82815_MC along * with the 82801BA and revision < 5. */ ich_device = pci_find_bsf(0, 0x1f, 0); if (ich_device == NULL || pci_get_vendor(ich_device) != PCI_VENDOR_INTEL || (pci_get_device(ich_device) != PCI_DEV_82801BA && pci_get_device(ich_device) != PCI_DEV_82801CA && pci_get_device(ich_device) != PCI_DEV_82801DB)) return; Can you get pciconf -lc output? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 18:28:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CEF1CB0B; Thu, 7 Feb 2013 18:28:33 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 82C7336E; Thu, 7 Feb 2013 18:28:33 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 07 Feb 2013 13:28:33 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BXQ96141; Thu, 7 Feb 2013 13:28:31 -0500 X-Auth-ID: anat Received: from pool-71-187-31-131.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([71.187.31.131]) by smtp01.lnh.mail.rcn.net with ESMTP; 07 Feb 2013 13:28:31 -0500 Message-ID: <5113F24E.3070207@aldan.algebra.com> Date: Thu, 07 Feb 2013 13:28:30 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop References: <5111DE44.7040008@aldan.algebra.com> <5111F739.7070607@aldan.algebra.com> <201302071316.29898.jhb@freebsd.org> In-Reply-To: <201302071316.29898.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 18:28:33 -0000 On 07.02.2013 13:16, John Baldwin wrote: > Can you get pciconf -lc output? Here: hostb0@pci0:0:0:0: class=0x060000 card=0x00000000 chip=0x11308086 rev=0x02 hdr=0x00 cap 09[88] = vendor (length 4) Intel cap 15 version 1 cap 02[a0] = AGP 4x 2x 1x SBA disabled pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0x11318086 rev=0x02 hdr=0x01 pcib2@pci0:0:30:0: class=0x060400 card=0x00000000 chip=0x24488086 rev=0x02 hdr=0x01 isab0@pci0:0:31:0: class=0x060100 card=0x00000000 chip=0x244c8086 rev=0x02 hdr=0x00 atapci0@pci0:0:31:1: class=0x010180 card=0x45418086 chip=0x244a8086 rev=0x02 hdr=0x00 uhci0@pci0:0:31:2: class=0x0c0300 card=0x45418086 chip=0x24428086 rev=0x02 hdr=0x00 vgapci0@pci0:1:0:0: class=0x030000 card=0x00a31028 chip=0x4d461002 rev=0x00 hdr=0x00 cap 02[50] = AGP 4x 2x 1x SBA disabled cap 01[5c] = powerspec 2 supports D0 D1 D2 D3 current D0 pcm0@pci0:2:3:0: class=0x040100 card=0x00a31028 chip=0x1998125d rev=0x10 hdr=0x00 cap 01[c0] = powerspec 2 supports D0 D1 D2 D3 current D0 xl0@pci0:2:6:0: class=0x020000 card=0x645610b7 chip=0x605510b7 rev=0x10 hdr=0x00 cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 none0@pci0:2:6:1: class=0x078000 card=0x615b10b7 chip=0x100710b7 rev=0x10 hdr=0x00 cap 01[50] = powerspec 2 supports D0 D2 D3 current D0 cbb0@pci0:2:15:0: class=0x060700 card=0x00a31028 chip=0xac42104c rev=0x00 hdr=0x02 cap 01[a0] = powerspec 2 supports D0 D1 D2 D3 current D0 cbb1@pci0:2:15:1: class=0x060700 card=0x00a31028 chip=0xac42104c rev=0x00 hdr=0x02 cap 01[a0] = powerspec 2 supports D0 D1 D2 D3 current D0 none1@pci0:2:15:2: class=0x0c0010 card=0x00a31028 chip=0x8027104c rev=0x00 hdr=0x00 cap 01[44] = powerspec 2 supports D0 D2 D3 current D0 Thanks! Yours, -mi From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 19:25:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2FF5EB66 for ; Thu, 7 Feb 2013 19:25:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0E388854 for ; Thu, 7 Feb 2013 19:25:19 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5BD84B915; Thu, 7 Feb 2013 14:25:18 -0500 (EST) From: John Baldwin To: "Mikhail T." Subject: Re: FreeBSD-9.1 would not boot on pentium3 laptop Date: Thu, 7 Feb 2013 14:25:17 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <5111DE44.7040008@aldan.algebra.com> <201302071316.29898.jhb@freebsd.org> <5113F24E.3070207@aldan.algebra.com> In-Reply-To: <5113F24E.3070207@aldan.algebra.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201302071425.17064.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 07 Feb 2013 14:25:18 -0500 (EST) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 19:25:19 -0000 On Thursday, February 07, 2013 1:28:30 pm Mikhail T. wrote: > On 07.02.2013 13:16, John Baldwin wrote: > > Can you get pciconf -lc output? > Here: > > hostb0@pci0:0:0:0: class=0x060000 card=0x00000000 > chip=0x11308086 rev=0x02 hdr=0x00 > cap 09[88] = vendor (length 4) Intel cap 15 version 1 > cap 02[a0] = AGP 4x 2x 1x SBA disabled Looks like you have one of the systems the comment mentions. Try this patch to see if ichss is disabled automatically for you: Index: ichss.c =================================================================== --- ichss.c (revision 246122) +++ ichss.c (working copy) @@ -67,7 +67,7 @@ struct ichss_softc { #define PCI_DEV_82801BA 0x244c /* ICH2M */ #define PCI_DEV_82801CA 0x248c /* ICH3M */ #define PCI_DEV_82801DB 0x24cc /* ICH4M */ -#define PCI_DEV_82815BA 0x1130 /* Unsupported/buggy part */ +#define PCI_DEV_82815_MC 0x1130 /* Unsupported/buggy part */ /* PCI config registers for finding PMBASE and enabling SpeedStep. */ #define ICHSS_PMBASE_OFFSET 0x40 @@ -155,9 +155,6 @@ ichss_identify(driver_t *driver, device_t parent) * E.g. see Section 6.1 "PCI Devices and Functions" and table 6.1 of * Intel(r) 82801BA I/O Controller Hub 2 (ICH2) and Intel(r) 82801BAM * I/O Controller Hub 2 Mobile (ICH2-M). - * - * TODO: add a quirk to disable if we see the 82815_MC along - * with the 82801BA and revision < 5. */ ich_device = pci_find_bsf(0, 0x1f, 0); if (ich_device == NULL || @@ -167,6 +164,22 @@ ichss_identify(driver_t *driver, device_t parent) pci_get_device(ich_device) != PCI_DEV_82801DB)) return; + /* + * Certain systems with ICH2 and an Intel 82815_MC host bridge + * where the host bridge's revision is < 5 lockup if SpeedStep + * is used. + */ + if (pci_get_device(ich_device) == PCI_DEV_82801BA) { + device_t hostb; + + hostb = pci_find_bsf(0, 0, 0); + if (hostb != NULL && + pci_get_vendor(hostb) == PCI_VENDOR_INTEL && + pci_get_device(hostb) == PCI_DEV_82815_MC && + pci_get_revid(hostb) < 5) + return; + } + /* Find the PMBASE register from our PCI config header. */ pmbase = pci_read_config(ich_device, ICHSS_PMBASE_OFFSET, sizeof(pmbase)); -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 19:42:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 563A115F; Thu, 7 Feb 2013 19:42:55 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id A5594930; Thu, 7 Feb 2013 19:42:54 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id k14so2373195wer.39 for ; Thu, 07 Feb 2013 11:42:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=cfMfmsYGLIoG3VEcdwOLgP8dYB+BhDw6zQiRC4DCdMw=; b=MQxeAbfYPWrxHQI53DwxeNuAPE5ZZlsqKzlHzyTwx4LKzsXEGLpy8IZdf/zstj17VM KwTPzzAqg29i52YwsRG4xsfp+274W70OY3MUD3ZIHDODDWsNrcT72x10TObgPBt6JLUt TyJto2ayPTfBgBzM00AkQpOyn20zgAoWge/pZJuXkD4zPY4FJcR3d8ekJWEfdXDIXOtX iP687sT/eT5UgNVEXMVlo9/bDmuVsATGj/StklnrY3X9DNG+pJz+eLyMQDGqRSXP3WXu wXjq87I+xzKpQBzJcuqBTj6ozwxlXBSb6SHXZGioomUC+twBcyGMpXEdm0UXVvkYLipo H9sw== MIME-Version: 1.0 X-Received: by 10.180.102.7 with SMTP id fk7mr5064963wib.27.1360266173810; Thu, 07 Feb 2013 11:42:53 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 7 Feb 2013 11:42:53 -0800 (PST) Date: Thu, 7 Feb 2013 21:42:53 +0200 Message-ID: Subject: CLANG and -fstack-protector From: Kimmo Paasiala To: freebsd-stable@freebsd.org, FreeBSD current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 19:42:55 -0000 Hello, Does the -fstack-protector option work on CLANG 3.1 and 3.2? There is thread on FreeBSD forums about the stack protector and ports and I'm wondering if it's possible to use the -fstack-protector option with CLANG. http://forums.freebsd.org/showthread.php?t=36927 -Kimmo From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 21:06:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 249B03FE; Thu, 7 Feb 2013 21:06:54 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id DDB1ADA9; Thu, 7 Feb 2013 21:06:53 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a] (spaceball.andric.com [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id E718D5C43; Thu, 7 Feb 2013 22:06:51 +0100 (CET) Message-ID: <51141769.5060905@FreeBSD.org> Date: Thu, 07 Feb 2013 22:06:49 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: Kimmo Paasiala , freebsd-stable@freebsd.org, FreeBSD current Subject: Re: CLANG and -fstack-protector References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 21:06:54 -0000 On 2013-02-07 20:42, Kimmo Paasiala wrote: > Does the -fstack-protector option work on CLANG 3.1 and 3.2? Yes, it works with both clang and gcc. > There is thread on FreeBSD forums about the stack protector and ports > and I'm wondering if it's possible to use the -fstack-protector option > with CLANG. > > http://forums.freebsd.org/showthread.php?t=36927 That thread seems to be full of confusion. :-) The base system is mostly built with -fstack-protector, except for the ia64, arm and mips arches, and for some specific cases where it is not necessary, or unwanted. Ports are largely independent of the base system, and their compilation flags are different from port to port. You could set -fstack-protector for your ports in either make.conf or ports.conf, if you wanted. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 22:52:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BDFA232B; Thu, 7 Feb 2013 22:52:55 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id 4A20F34E; Thu, 7 Feb 2013 22:52:52 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id 435FED48098; Thu, 7 Feb 2013 23:52:44 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 2998E278; Thu, 7 Feb 2013 23:52:43 +0100 (CET) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 02CDE13096; Thu, 7 Feb 2013 22:52:42 +0000 (UTC) Date: Thu, 7 Feb 2013 23:52:42 +0100 From: Jeremie Le Hen To: Dimitry Andric Subject: Re: CLANG and -fstack-protector Message-ID: <20130207225242.GA5900@felucia.tataz.chchile.org> Mail-Followup-To: Dimitry Andric , Kimmo Paasiala , freebsd-stable@freebsd.org, FreeBSD current References: <51141769.5060905@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51141769.5060905@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kimmo Paasiala , FreeBSD current , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 22:52:55 -0000 Hi Kimmo, On Thu, Feb 07, 2013 at 10:06:49PM +0100, Dimitry Andric wrote: > On 2013-02-07 20:42, Kimmo Paasiala wrote: > > Does the -fstack-protector option work on CLANG 3.1 and 3.2? > > Yes, it works with both clang and gcc. > > > > There is thread on FreeBSD forums about the stack protector and ports > > and I'm wondering if it's possible to use the -fstack-protector option > > with CLANG. > > > > http://forums.freebsd.org/showthread.php?t=36927 > > That thread seems to be full of confusion. :-) The base system is mostly > built with -fstack-protector, except for the ia64, arm and mips arches, > and for some specific cases where it is not necessary, or unwanted. > > Ports are largely independent of the base system, and their compilation > flags are different from port to port. You could set -fstack-protector > for your ports in either make.conf or ports.conf, if you wanted. You can do this, it will work for most of the ports but some ports do not honor CFLAGS. If those ports happen to be linked againsst libraries that were compiled with -fstack-protector, you will get a missing symbol error. Well, to be honest, I don't remember enough details, they faded from my memory, I need to check this. So if you care about security enough, go for it! If you meet weird error like a missing "stack_chk_fail" symbol for some ports (lang/perl might be a candidate in my memory), then look at the PR below, it will probably solve your problem. Time has passed and I am interested in your feedback without the patch (and then with, if relevant). Basically the following PR contains a patch that waits for an exp run to be committed into the base system. This just turns libc.so into an ld script that pulls in libssp_nonshared.a. You just have to run "make all install" in src/lib/libc after applying it. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168010 I run it on my servers with -fstack-protector enabled for ports without any problem. Cheers! -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 23:40:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1671EFC; Thu, 7 Feb 2013 23:40:02 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by mx1.freebsd.org (Postfix) with ESMTP id F2D7577E; Thu, 7 Feb 2013 23:40:01 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id ez12so219425wid.6 for ; Thu, 07 Feb 2013 15:40:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=denVb4VY8GZoHyzmxs5P+cwN4N515gPQDzAuynArfAQ=; b=qjon24ct1j4S6ztTjKH4lSUVSBjbDJZ0uSLTNnAvL/Pn3mjn7xntHLCd5V7ZH9NLx6 Z/lDweQkhThSYp+pAlUIp6hZ0bmpeXssy2kFdWdlPqmesVKuDCBWOQfX8+KqeIymBRlz PGoep5iT17woJz94Qcakq6CxVx1lK7vSkNlqCbtilNTLrEhXbda3HZ9xn35ZVm6aSpCf s8Z2JYUymYSa72SSLQ4NagFeDu9DmmstS+iI7fstR1flWoYOvtlpMBEuo4YW50y6ktI5 9JYoGKAIrgT7hiIuWhLecsT+LH5ixptzd9Rbkbfx5Yd1KzGNX96gE/vmXOP322YnAXhL 4noA== MIME-Version: 1.0 X-Received: by 10.194.122.199 with SMTP id lu7mr6088083wjb.42.1360280400722; Thu, 07 Feb 2013 15:40:00 -0800 (PST) Received: by 10.216.120.193 with HTTP; Thu, 7 Feb 2013 15:40:00 -0800 (PST) In-Reply-To: <51141769.5060905@FreeBSD.org> References: <51141769.5060905@FreeBSD.org> Date: Fri, 8 Feb 2013 01:40:00 +0200 Message-ID: Subject: Re: CLANG and -fstack-protector From: Kimmo Paasiala To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD current , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 23:40:02 -0000 On Thu, Feb 7, 2013 at 11:06 PM, Dimitry Andric wrote: > On 2013-02-07 20:42, Kimmo Paasiala wrote: >> >> Does the -fstack-protector option work on CLANG 3.1 and 3.2? > > > Yes, it works with both clang and gcc. > Good to know thank you! > >> There is thread on FreeBSD forums about the stack protector and ports >> and I'm wondering if it's possible to use the -fstack-protector option >> with CLANG. >> >> http://forums.freebsd.org/showthread.php?t=36927 > > > That thread seems to be full of confusion. :-) The base system is mostly > built with -fstack-protector, except for the ia64, arm and mips arches, > and for some specific cases where it is not necessary, or unwanted. I was aware of the base system being built with the stack protector on systems where it makes sense. > > Ports are largely independent of the base system, and their compilation > flags are different from port to port. You could set -fstack-protector > for your ports in either make.conf or ports.conf, if you wanted. Is there any work being done to provide an optional Makefile knob (WITH_STACK_PROTECTOR ?) to turn on -fstack-protector for ports that install network services (or other critical code)? I'd bet such feature would be popular. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 7 23:45:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F3A0D431 for ; Thu, 7 Feb 2013 23:45:19 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:64]) by mx1.freebsd.org (Postfix) with ESMTP id D1D587EF for ; Thu, 7 Feb 2013 23:45:19 +0000 (UTC) Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta07.emeryville.ca.mail.comcast.net with comcast id xUCg1k0060x6nqcA7blKjt; Thu, 07 Feb 2013 23:45:19 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta12.emeryville.ca.mail.comcast.net with comcast id xblH1k00u1t3BNj8YblJzg; Thu, 07 Feb 2013 23:45:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id A7FCD73A31; Thu, 7 Feb 2013 15:45:17 -0800 (PST) Date: Thu, 7 Feb 2013 15:45:17 -0800 From: Jeremy Chadwick To: Kurt Jaeger Subject: Re: ethtool-like utility for FreeBSD Message-ID: <20130207234517.GA23075@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360280719; bh=SfqIv2hFKstjdTe5o6RJOBunsy1Tz93Z11lPg0cbiQU=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=c277jYvpQtiCeFVIhU4Bqyje0QdELI+Ls6UWl/5Lfq20pKJhaARRKcrQRwKTOT84R Og5sC/3Vmsxhosp8GVM2He5Vzr60hjyHOg7n5HzK6M8lbroGlCy0zrp+xQMkdWDuXQ +4JrKsJqS8PGyWZFqpKKY+p1sOWSxfke3INIV4awwyy0k4RImJJkVJo8T2PQP12Q/Y p11XY6SO+dfWYd9nh/WE193gsCfS50YpB+Bd4r3T6it9ffUCX9vO10A1MUg0j61xAE RvOnCN3DwKInWTQR6wBZI32CwdmtCgScTNzzvTbzO/cnA9LVY3KfjLQpGzQqgnja/X +p6afxDzob+8w== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 23:45:20 -0000 > There is a posting public about Intel ethernet adapters and their > packets of death: > > http://blog.krisk.org/2013/02/packets-of-death.html > > Now, how can we test the EEPROM from FreeBSD, similar to the > ethtool of Linux ? There is no such tool. If you want to dump EEPROM contents, you can do so via one of the following ways for em(4) NICs or igb(4) NICs, as root: sysctl dev.XXX.Y.nvm=1 (for recent/newer FreeBSD) sysctl dev.XXX.Y.debug=2 (for older FreeBSD) Where XXX is either "em" or "igb" depending on your NIC and Y is the interface number (e.g. 0 = em0, 1 = em1, etc.). After this, run "dmesg" and look at the output at the bottom. You will see something like this: Interface EEPROM Dump: Offset 0x0000 3000 d248 d022 0d30 f746 00f5 ffff ffff 0x0010 0100 ffff 026b 108c 15d9 108c 8086 83df 0x0020 0008 2000 7e14 0048 1000 00d8 0000 2700 0x0030 6cc9 3150 0722 040b 0984 0000 c000 0706 Please see this page, search for "EEPROM", which documents a different bug pertaining the Intel 82573 where some EEPROMs were shipped with a power-saving bit enabled. Read it, do not skim it, because it explains the EEPROM dump endian difference WRT Linux ethtool vs. FreeBSD's driver: https://wiki.freebsd.org/BugBusting/Commonly_reported_issues There is no way on FreeBSD to change EEPROM contents. You will need to use Linux ethtool for this, or -- strongly recommended -- ask Intel for their DOS-based utility that fixes the "packet of death" setting in the EEPROM and follow their instructions. You can also ask your NIC (or motherboard) vendor and make it their problem (I'm willing to bet a lot of them aren't aware of it). To whom it may concern: these sysctls really need to be documented. They have sysctl -d descriptions but they need to be documented in man pages. I can write the man page updates if need be. Now, as far as the "packet of death" thing is concerned: cry me a river. Why is it people today think that hardware devices are immune to bugs? Is it because they're solid-state, thus give off the impression "there can be no problems?" I don't get it. *sighs* This sort of stuff seems to come as a surprise to younger generations or people who really do believe "chips never have problems". It seems to me that it stems from, as the generations have progressed, less and less people actually understanding how things work (all the way down to th bare metal). All this bloody abstracted programming and abstracted ideas do nothing but hide how things work. Really pisses me off. It might be more of a "wow, I didn't expect this to be a problem so low-level" surprise, which just further fuels my point -- people seem to think things Just Work(tm) today, when in my experience things today ***do not*** Just Work(tm). Most things are Extremely Broken(tm). Just be glad the issue is with an EEPROM setting and not silicon-level, otherwise you'd be flat out screwed barring driver-level workarounds. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 00:07:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D617C9B2 for ; Fri, 8 Feb 2013 00:07:23 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9FB168C1 for ; Fri, 8 Feb 2013 00:07:23 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAJRAFFGDaFvO/2dsb2JhbABFFoYzukhzgh8BAQEDAQEBASArIAsFFhgCAg0ZAikBCSYGCAcEARwEh2oGDK1akkyBI4wBCoMbgRMDiGaLCYIygR2PNYMegVE1 X-IronPort-AV: E=Sophos;i="4.84,625,1355115600"; d="scan'208";a="15674285" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 07 Feb 2013 19:07:22 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 87429B3F2E; Thu, 7 Feb 2013 19:07:22 -0500 (EST) Date: Thu, 7 Feb 2013 19:07:22 -0500 (EST) From: Rick Macklem To: Janusz Bulik Message-ID: <332773957.2815149.1360282042526.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NFSv4 + Kerberos permission denied MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 00:07:23 -0000 Janusz Bulik wrote: > Hello, > I've got a little problem with NFSv4 + Kerberos. I can do a mount with > Kerberos with a valid ticket, but read-only. > After the mount -vvv -t nfs -o nfsv4,sec=krb5 nfsserver:/ /mount_test/ > I can see: > > #klist: > Feb 6 07:22:47 Feb 6 17:22:43 nfs/nfsserver@my.domain > > #/var/heimdal/kdc.log: > 2013-02-06T07:28:26 TGS-REQ clientnfs@my.domain from IPv4:192.168.0.23 > for nfs/nfsserver@my.domain > > tcpdump: > 14:59:36.140272 IP nfsclient.61011 > 192.168.0.21.kerberos-sec: > 14:59:36.142301 IP 192.168.0.21.kerberos-sec > nfsclient.61011: > > I got "Permission denied" message when I try to mkdir or rm. As a root > mount and as a user mount (sysctl vfs.usermounts=1). > With -sec=sys it works read-write, but with -sec=krb5 read-only.. > Did you successfully read files under /mount_test? (I suspect no access would be closer to the truth than read-only, unless the non-root user with a valid TGT only has read access. Although I think it is technically possible to do so, typically "root" does not exist in a KDC as a user principal and, as such, "root" cannot do a kinit to get a TGT and that means "no access" to the kerberized mount point.) > my /etc/exports: > V4: /export_test -sec=krb5:krb5i:krb5p -network 192.168.0.0 -mask > 255.255.255.0 > /export_test -sec=krb5:krb5i:krb5p -network 192.168.0.0 -mask > 255.255.255.0 -maproot=root -alldirs > > tried with V4: / .... as well. > Added all the principals needed. > Tried also with full qualified domain names. > SSH works fine with Kerberos > > > Do I need rpcsec_gss.patch? (according to > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup) > or can I make it work somehow else? > > I used FreeBSD-9.1-RELEASE-i386-disc1 > and > FreeBSD-10.0-CURRENT-i386-20130202-r246254-release > Well, without the patch, the only kind of NFSv4 kerberized mount that will work is (NFSv3 is a different story): # sysctl vfs.usermount=1 - logged in as non-root user that has kinit'd and, therefore, has a valid TGT % mount -t nfs -o nfsv4,sec=krb5 nfsserver:/ /mount_test - then this user (or any other non-root user with a valid TGT) should be able to access /mount_test with whatever permissions the server has on the directories. (ie. If these users are supposed to create files/directories under /export_test, they will need write access to /export_test.) Note that "root" does not normally have any access to a kerberized mount point, since the KDC doesn't normally have a user principal for "root", as above. This mount will only work as long as the non-root user that did the mount holds a valid TGT. - To do an NFSv4 kerberized mount as root (which will keep working until unmount), you need to patch the system so that it can use a host based credential in the default keytab file as an initiator credential. If you use current/10.0 sources, I have a better patch to do this. It is at: http://people.freebsd.org/~rmacklem/rpcsec_gss-hostbased-initiator.patch After applying the patch, you need to build both the kernel and the gssd daemon from sources. You do not need to set the sysctl to the correct encryption type for the keytab entry to get it to work. After putting an entry in the client's /etc/keytab, rebooting the patched kernel with the rebuilt gssd daemon running on it, the mount looks like: # mount -t nfs -o nfsv4,sec=krb5,gssname=nfs nfsserver:/ /mount_test (Assuming that the keytab entry is for nfs/client-host.domain@YOUR_REALM.) This mount will still not give "root" access to the file system, for the same reasons as above, but can be done by "root" and doesn't need any valid TGT to keep working. At this time, there is no way to give "root" access to a kerberized mount unless you put a user principal for "root" (root@YOUR_REALM) in you KDC and then do a kinit when logged in as root. (This is not recommended from a security point of view.) If you can't get things to work: - try and use des-cbc-crc encryption for the keytab entries (you can try other ones after you have it working, so long as they result in an 8byte session key) - make sure the gssd is working on both client and server (it has to be running before the nfsd is started on the server) - check /var/log/messages for any messages from the gssd - check the log file on your KDC for hints of problems - capture packets of the mount and look at them in wireshark (use something like a "host" filter, so you get more than the NFS packets) Good luck with it, rick > -- > Greets > Janusz > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 01:37:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BAAA11CE for ; Fri, 8 Feb 2013 01:37:41 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail4.riverwillow.net.au (mail4.riverwillow.net.au [202.125.45.59]) by mx1.freebsd.org (Postfix) with ESMTP id D637DCF6 for ; Fri, 8 Feb 2013 01:37:39 +0000 (UTC) Received: from [172.25.24.201] (riverw1.lnk.telstra.net [165.228.239.138]) (authenticated bits=0) by mail4.riverwillow.net.au (8.14.6/8.14.6) with ESMTP id r181MJrx075946 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 8 Feb 2013 11:22:20 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=m4001; t=1360286541; bh=ZKam8KdOE/zNqX07JYSEIMmnFKmC/ZoImB1h6oXmaY4=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=6EAtP/cYj5KYWzxHj/lz7OTd5WM3iljIIXYc5l/54xacHNUtcL1JneZ7I2cmipQ5z u2WTJbxZGAHQMS4UkyWfyuojc18UGvyk29yHWDcYVOFIzrYGSlYSOVmxApPwBXo/pj 5vs0FcRYYD90OpF6EibbXk90JkFuP+XjDKpY77JU= Message-ID: <51145342.5090809@riverwillow.com.au> Date: Fri, 08 Feb 2013 12:22:10 +1100 From: John Marshall Organization: Riverwillow Pty Ltd User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130205 Thunderbird/17.0.2 MIME-Version: 1.0 To: Janusz Bulik Subject: Re: NFSv4 + Kerberos permission denied References: In-Reply-To: X-Enigmail-Version: 1.4.6 OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig72B2A21D8F8BB4EA1336D655" Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 01:37:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig72B2A21D8F8BB4EA1336D655 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On 08/02/2013 01:05, Janusz Bulik wrote: > Hello, > I've got a little problem with NFSv4 + Kerberos. I can do a mount with > Kerberos with a valid ticket, but read-only. > After the mount -vvv -t nfs -o nfsv4,sec=3Dkrb5 nfsserver:/ /mount_test= / > I got "Permission denied" message when I try to mkdir or rm. As a root > mount and as a user mount (sysctl vfs.usermounts=3D1). > With -sec=3Dsys it works read-write, but with -sec=3Dkrb5 read-only.. Am I right in supposing that you have never had this working? What you describe sounds symptomatic of nfsuserd not running - see nfsv4(4). sec=3Dsys doesn't need nfsuserd to "work" but sec=3Dkrb5 does. = If you mount with sec=3Dkrb5 and "ls -l /mount_test/" do you see in the listing the user and group names you expect, or just a bunch of numbers? The read-only access is probably what the filesystem permissions allow to "other" because, without nfsuserd, it can't map your kerberos principal to a uid. Of course, I could be wrong... --=20 John Marshall --------------enig72B2A21D8F8BB4EA1336D655 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEUU0sACgkQw/tAaKKahKLtEgCeNdCZMo3GeBCJuGXdwNh1tcYi vuUAn0+jQsvinuNOLj6jb1mgKB49S0td =Cdtz -----END PGP SIGNATURE----- --------------enig72B2A21D8F8BB4EA1336D655-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 03:01:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6F179716 for ; Fri, 8 Feb 2013 03:01:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 48789F9E for ; Fri, 8 Feb 2013 03:01:03 +0000 (UTC) Received: by mail-da0-f44.google.com with SMTP id z20so1532047dae.3 for ; Thu, 07 Feb 2013 19:01:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=3rNxy1C8i1YIkOqBO9HkiqvSlCfnKD4qJ0zEFioThDQ=; b=bUEDBEo7cAt8ScDpXwLS9bf0WMvVWq6HvtsDdBwHPzag5YsRxOSTczYhSPaHZ2iwFa qqR6CDC8zg3hNRIw2n1qlPY95hqnDAwWpeUY7jI+qwyCGWz0Go7dwt90+TexTy8ldZU5 yknx0EPwaI6kMSNBkLOsFpyl5wcqzu7gZ+9BU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=3rNxy1C8i1YIkOqBO9HkiqvSlCfnKD4qJ0zEFioThDQ=; b=WbtFdc/skpa85NxoP3MR1PyCnpLWaPMnkz9ACmQpdk15mRIYyHkoWqCYS/pI4G26rl /g85TxVvmusv6dbT+dRvn6qiW3RndF5rYpd0/En8qn1VUt9Cm+QD91Zz3elLQdKNXD5h 2Ib8UCdBD6TnXWZPIgY2vKPpEHwr02fInthaISnv6OcXcNXz4w7FigApzH1OnFzk0jj8 TQlQUKzluO7/JQejK2XBCI8AcZHxNDJoBy1zmwEPrdiI/+2FWFm91zCuxQcBKurc4Cgr t1wycL/3e7aU5gwcakagAnDnt2J/VFgql0dSBkZPR6qNYf/1jOiAeswS+GuWTBBFVdxF QZbg== X-Received: by 10.66.74.234 with SMTP id x10mr12482564pav.10.1360292463250; Thu, 07 Feb 2013 19:01:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.66.148.10 with HTTP; Thu, 7 Feb 2013 19:00:33 -0800 (PST) In-Reply-To: References: <51141769.5060905@FreeBSD.org> From: Eitan Adler Date: Thu, 7 Feb 2013 22:00:33 -0500 Message-ID: Subject: Re: CLANG and -fstack-protector To: Kimmo Paasiala Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQm33PXSbYHvCPj/ackGxG4Uq0sjp5WlRUbmcilE+GEt49e+ABXYH/WCulN508dMu96jog61 Cc: freebsd-stable@freebsd.org, FreeBSD current , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 03:01:04 -0000 On 7 February 2013 18:40, Kimmo Paasiala wrote: >> Ports are largely independent of the base system, and their compilation >> flags are different from port to port. You could set -fstack-protector >> for your ports in either make.conf or ports.conf, if you wanted. > > Is there any work being done to provide an optional Makefile knob > (WITH_STACK_PROTECTOR ?) to turn on -fstack-protector for ports that > install network services (or other critical code)? I'd bet such > feature would be popular. As far as I am aware no such feature exists. In any case it would be subject to the same problem of many ports ignoring CFLAGS and friends. -- Eitan Adler From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 12:02:48 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A91A976 for ; Fri, 8 Feb 2013 12:02:48 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id 39B3080 for ; Fri, 8 Feb 2013 12:02:47 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 31484 invoked from network); 8 Feb 2013 13:02:46 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a; t=1360324966; bh=UczJVcCwizTYmjUpgvBpT+1RqWy0qF/oL3aAGjdallM=; h=From:To:CC:Subject; b=alqFsA0Ut+xgWijZQ31MMoI+coHlvq80SkXdXwrigLt37rwk8/eWNrrnkHmsAf8Eh wRyN24DwYfHyTlbgjCFIUDCNo/EMYSDXLdhdr1PenhZB7hUUWxqJarnG8B+k05qrce C0yAEmyGjICg8y8mWDOKUg8pvOHczI1HT8v1fGtE= Received: from nat.misal.pl (HELO [127.0.0.1]) (marek_sal@[83.19.131.171]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 8 Feb 2013 13:02:46 +0100 Message-ID: <5114E961.70706@wp.pl> Date: Fri, 08 Feb 2013 13:02:41 +0100 From: Marek Salwerowicz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Damien Fleuriot Subject: Re: pkg can't access pkgbeta.freebsd.org References: <51124589.7080800@wp.pl> <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> In-Reply-To: <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130208-0, 2013-02-08), Outbound message X-Antivirus-Status: Clean X-WP-DKIM-Status: good (id: wp.pl) X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [QaPU] Cc: Marek Salwerowicz , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 12:02:48 -0000 W dniu 2013-02-06 13:53, Damien Fleuriot pisze: > ":" in the URL instead of "/" , possibly ? > > I find it strange that there should be ":" in the URL, it is only acceptable when denoting the destination port to connect to. > > Try replacing them with slashes. after few hours it started working... probably some connection issues.. regards, -- Marek Salwerowicz From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 12:19:14 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D4CBE458 for ; Fri, 8 Feb 2013 12:19:14 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 72E16157 for ; Fri, 8 Feb 2013 12:19:14 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1U3mv3-0004c6-40; Fri, 08 Feb 2013 13:19:06 +0100 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U3mv3-0003TJ-6X; Fri, 08 Feb 2013 13:19:05 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Damien Fleuriot" , "Marek Salwerowicz" Subject: Re: pkg can't access pkgbeta.freebsd.org References: <51124589.7080800@wp.pl> <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> <5114E961.70706@wp.pl> Date: Fri, 08 Feb 2013 13:19:04 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <5114E961.70706@wp.pl> User-Agent: Opera Mail/12.14 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.5 X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05 autolearn=disabled version=3.3.1 X-Scan-Signature: 739ba1b2be5fabc1cc6069058737919f Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 12:19:14 -0000 On Fri, 08 Feb 2013 13:02:41 +0100, Marek Salwerowicz wrote: > W dniu 2013-02-06 13:53, Damien Fleuriot pisze: >> ":" in the URL instead of "/" , possibly ? >> >> I find it strange that there should be ":" in the URL, it is only >> acceptable when denoting the destination port to connect to. >> >> Try replacing them with slashes. > after few hours it started working... probably some connection issues.. > > regards, > I saw the same. So probably there was an issue at the pkgbeta server. But as you say, it works again. Cheers, Ronald. From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 15:13:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8B70D953 for ; Fri, 8 Feb 2013 15:13:49 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (s1.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 16978B57 for ; Fri, 8 Feb 2013 15:13:48 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id r18FDthG092166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Feb 2013 16:13:55 +0100 (CET) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <511514F5.4010504@omnilan.de> Date: Fri, 08 Feb 2013 16:08:37 +0100 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: setfacl man page states "d=delete_child" and "D=delete" X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5CF0A444F77C183B6F4F11CB" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 15:13:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5CF0A444F77C183B6F4F11CB Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, I think there's a confusion in the man page setfacl(1). In my tests, "D" means "delete_child" and "d" "delete"; like it's true for other NFSv4 implementations. But manpage tells the other way around. Since things didn't work as expected when I followed the man page I checked the following as a member of group "intern": 1st test, following the man page, this acl should prevent users of group "intern" to delete anything inside "testdir": >: getfacl testdir # file: testdir/ # owner: root # group: intern owner@:rwxp--aARWcCos:------:allow group@:rwxp--a-R-c--s:------:allow group@:-----d--------:------:deny everyone@:------a-R-c--s:------:allow >: ls -l testdir total 3 drwxr-xr-x 2 root intern 2 8 Feb 15:38 2nd -rw-r--r-- 1 root intern 0 8 Feb 15:44 testfile But: >: rm testdir/testfile override rw-r--r-- root/intern for testdir/testfile? y >: ls -l testdir total 2 drwxr-xr-x 2 root intern 2 8 Feb 15:38 2nd *pow* "testfile" of directory testdir got unlinked, since write permission to "testdir" has overridden group-readonly of "testfile" and no "delete_child" restriction took place. 2nd test, using "D" instead of "d": #: setfacl -m group@:D::deny shared/testdir >: getfacl testdir # file: testdir # owner: root # group: intern owner@:rwxp--aARWcCos:------:allow group@:rwxp--a-R-c--s:------:allow group@:----D---------:------:deny everyone@:------a-R-c--s:------:allow >: ls -l testdir total 3 drwxr-xr-x 2 root intern 2 8 Feb 15:38 2nd -rw-r--r-- 1 root intern 0 8 Feb 15:55 testfile >: rm testdir/testfile override rw-r--r-- root/intern for testdir/testfile? y rm: testdir/testfile: Operation not permitted >: ls -l testdir total 3 drwxr-xr-x 2 root intern 2 8 Feb 15:38 2nd -rw-r--r-- 1 root intern 0 8 Feb 15:55 testfile Shall I file a PR? Or do I completely misunderstand things? Thanks, -Harry P.S.: Btw., can anybody explain me why (at some time, someone decided that) write permission to a directory does override file permissions inside the directory? I can't get the sense. Of course, there's the sticky bit, but that's not inheritable. I can't imagine why the stick bit doesn't work inverted. The default behaviour should be like with sticky bit set, and by setting something like the sticky bit, optionally, one can empower the directory write permitted users/groups to override file-permissions inside. That's the only thing I'd ever neede= d. --------------enig5CF0A444F77C183B6F4F11CB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlEVFQEACgkQLDqVQ9VXb8gLtgCgkbXc69OnQH06p8H7f1kVW7oj HSMAn1i4NMkH/y8s6HB4mSmI6xPSJE/B =Otz+ -----END PGP SIGNATURE----- --------------enig5CF0A444F77C183B6F4F11CB-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 16:52:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 46CD918A for ; Fri, 8 Feb 2013 16:52:49 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by mx1.freebsd.org (Postfix) with ESMTP id 078F7DF for ; Fri, 8 Feb 2013 16:52:48 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta13.emeryville.ca.mail.comcast.net with comcast id xpli1k0041u4NiLADssnSe; Fri, 08 Feb 2013 16:52:47 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta21.emeryville.ca.mail.comcast.net with comcast id xssm1k00C1t3BNj8hssmWd; Fri, 08 Feb 2013 16:52:47 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0195C73A31; Fri, 8 Feb 2013 08:52:46 -0800 (PST) Date: Fri, 8 Feb 2013 08:52:45 -0800 From: Jeremy Chadwick To: Ronald Klop Subject: Re: pkg can't access pkgbeta.freebsd.org Message-ID: <20130208165245.GA39423@icarus.home.lan> References: <51124589.7080800@wp.pl> <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> <5114E961.70706@wp.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360342367; bh=rZbOj/OvFnwyNK+gLnXtpxMbqXpsD8g3piNFBvAI+jY=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=bvG2+/2N7kPCr1JyFvYEY3gq+1fFtnPZfNim51UjZ53x6ydBchX0d30/UuoDzmLr3 kRKKBktPmGohs96T5mn8Z8p+mn0YGjzbMsEHjQHq6rxIbxDyAU43E2EjxA3DQ2rmJJ 7Ck+hYU3kPClzAA4IbEyEYxDgaRYyMwMndMry/R8YCuqr9ZRNhnZuuaFFTlLvwEoix XQh4fairtRDPK+3di3fuIZanp0zgnLC6ORQpOcuAOvb0rQvC+5YoVzavZWb+ILZNqv Gp54ojw+l3ukksJkjfDqINYAxW/v2GSQYPeJ01I/BMEVLk903UlQV6hveBIkrop5Gz LbmFs3qUyHejA== Cc: Marek Salwerowicz , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 16:52:49 -0000 On Fri, Feb 08, 2013 at 01:19:04PM +0100, Ronald Klop wrote: > On Fri, 08 Feb 2013 13:02:41 +0100, Marek Salwerowicz > wrote: > > >W dniu 2013-02-06 13:53, Damien Fleuriot pisze: > >>":" in the URL instead of "/" , possibly ? > >> > >>I find it strange that there should be ":" in the URL, it is > >>only acceptable when denoting the destination port to connect > >>to. > >> > >>Try replacing them with slashes. > >after few hours it started working... probably some connection issues.. > > > >regards, > > > > I saw the same. So probably there was an issue at the pkgbeta server. > But as you say, it works again. Not "probably": http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/000001.html Five hours later (read closely): http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/000002.html Folks should be subscribing to freebsd-ops-announce for this kind of stuff, as it's the mailing list for problems with freebsd.org services. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 16:54:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 85B102A4; Fri, 8 Feb 2013 16:54:18 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (s1.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 1F58E11C; Fri, 8 Feb 2013 16:54:17 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id r18GxNG5094435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Feb 2013 17:59:23 +0100 (CET) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <51152DB8.4060703@omnilan.de> Date: Fri, 08 Feb 2013 17:54:16 +0100 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: multiple ACEs with the same ACL qualifier X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig196DCE617D00358E8030002E" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 16:54:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig196DCE617D00358E8030002E Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, I'd like to duplicate the following ACL: # file: /data/shared/ # owner: harry # group: harry group:1stgroup:r-x---a-R-c--s:fd----:allow group:2ndgroup:rwxp--a-R-c--s:-d----:allow group:2ndgroup:----D---------:-d----:deny group:2ndgroup:r-----a-R-c--s:f-i---:allow owner@:rwxpDdaARWcCos:fd----:allow group@:r-xp--a-R-c--s:fd----:allow everyone@:--------------:fd----:allow So there are two "group:2ndgroup:::allow" entries. While it's annoying that I can't modify one specific of these with "-m" (both get altered without warning/confirmation reques), I also can't use "-M" to apply it read from file. Are there any workarrounds? Intention is to make sure newly created files can only be deleted/altered by owner, while two other groups need to access files and directories read-only, but one of them also needs write access. But must'nt delete foreign files/directories. Never had so many problems applying real-world needs... Done such setup hundred times without effort, but on other FS... Thanks, -Harry --------------enig196DCE617D00358E8030002E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlEVLbgACgkQLDqVQ9VXb8hvCACfQyczYTUj2t3lnamlHrgwMhIq nb0An3B9OsOW6mr1gDdJ9q7hSsIKKdKH =lBoY -----END PGP SIGNATURE----- --------------enig196DCE617D00358E8030002E-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 17:50:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BBFA4E64; Fri, 8 Feb 2013 17:50:38 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ea0-f174.google.com (mail-ea0-f174.google.com [209.85.215.174]) by mx1.freebsd.org (Postfix) with ESMTP id 233A3348; Fri, 8 Feb 2013 17:50:37 +0000 (UTC) Received: by mail-ea0-f174.google.com with SMTP id 1so1782649eaa.5 for ; Fri, 08 Feb 2013 09:50:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=22uDRZOM2arZZtaj+um4QCfy45OTo5vJBX9c9uRYJgI=; b=p125DmYpY1fZr4cqOdC0I1VJBCz42Fz+SjA/yDPl73BnYH/BVuSrnCJ3ARV32Y4Sfx 7kt8yqnhfOsvWKFj7lizvW0/xkQUBcqButFKrQfEpt4K3ob2i29/CFl5gHqhpnMdwnng TfovCDu/I5iAOcSrjbpZM9kGiGAGrjmEmGCriuT1WTNJJrUiyVM7axo6YpJRzidh/vnE 0RZq+oO7NlP3WPoLInSuSI6Qf/DvoIJkQQ9W4GBMZ0J0Kd+MlcTisBC6fa9kVqLpBn8V Yevki/I+mgCmAimDFh4/32HTNNhajhJjJ9bSAF2qO6AA6p2R39iF32biA5JBoCcMsLmU gvpQ== X-Received: by 10.14.182.5 with SMTP id n5mr17823044eem.9.1360345836189; Fri, 08 Feb 2013 09:50:36 -0800 (PST) Received: from [192.168.1.104] (45.81.datacomsa.pl. [195.34.81.45]) by mx.google.com with ESMTPS id h5sm48492044eem.1.2013.02.08.09.50.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 09:50:35 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: multiple ACEs with the same ACL qualifier Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <51152DB8.4060703@omnilan.de> Date: Fri, 8 Feb 2013 18:50:33 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <578FD1DA-8D68-446F-9443-4D8E0220BD31@FreeBSD.org> References: <51152DB8.4060703@omnilan.de> To: Harald Schmalzbauer X-Mailer: Apple Mail (2.1283) Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 17:50:38 -0000 Wiadomo=B6=E6 napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o = godz. 17:54: > Hello, >=20 > I'd like to duplicate the following ACL: > # file: /data/shared/ > # owner: harry > # group: harry > group:1stgroup:r-x---a-R-c--s:fd----:allow > group:2ndgroup:rwxp--a-R-c--s:-d----:allow > group:2ndgroup:----D---------:-d----:deny > group:2ndgroup:r-----a-R-c--s:f-i---:allow > owner@:rwxpDdaARWcCos:fd----:allow > group@:r-xp--a-R-c--s:fd----:allow > everyone@:--------------:fd----:allow >=20 > So there are two "group:2ndgroup:::allow" entries. > While it's annoying that I can't modify one specific of these with = "-m" > (both get altered without warning/confirmation reques), I also can't = use > "-M" to apply it read from file. >=20 > Are there any workarrounds? Please use "-a" and "-x" instead. The "-m" was fine for POSIX.1e ACLs, where you never have more than one entry per principal and the ordering doesn't matter. --=20 If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 18:16:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 16390941; Fri, 8 Feb 2013 18:16:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by mx1.freebsd.org (Postfix) with ESMTP id A93716E0; Fri, 8 Feb 2013 18:16:57 +0000 (UTC) Received: by mail-ve0-f176.google.com with SMTP id cz10so3548090veb.21 for ; Fri, 08 Feb 2013 10:16:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=/HWKFgz9ZwkiIxlnuu1o7XRIvTSkuVs3bQva9h97swI=; b=cRpzOlHfJOoNMeQHaRLycuqq/MdFZph7Ag1sMD0Q9pkjTIFqoKiCPUFf9t+3jZYdm7 SNolqxT2lGw4tCy85YjurATp8B97qX3gG6FVnXDk/W/xEhwrOorPKeXsf4uw5mJOgyos dli1NHcEw5PhjSfcL23+zACjmLHTBwjnZfn8pnWpZ0Fs0x2VsctWJAEoPBBEceziV7Nc tCskHB5KoakPq6fb+vp5iU6mAUpZvpnpfz3h61cHySnzAdYghotJvZDsOJW7TW8JU7Ue UljccQZE8A8Ac7RV3aXLpPmGOqFa7FoQ2UE1bovSROmap+07DYOL3LqUEgN/8/SfKxGw NU/w== MIME-Version: 1.0 X-Received: by 10.52.29.109 with SMTP id j13mr6919204vdh.111.1360347409285; Fri, 08 Feb 2013 10:16:49 -0800 (PST) Received: by 10.220.191.132 with HTTP; Fri, 8 Feb 2013 10:16:49 -0800 (PST) Date: Fri, 8 Feb 2013 10:16:49 -0800 Message-ID: Subject: Intel 82574 issue reported on Slashdot From: Jack Vogel To: FreeBSD Net , FreeBSD Current , FreeBSD stable Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Pieper, Jeffrey E" , "Hearn, James R" , "Ronciak, John" , "Vogel, Jack" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 18:16:58 -0000 For those that may have run across the story on Slashdot about this NIC, here is our statement: Recently there were a few stories published, based on a blog post by an end-user, suggesting specific network packets may cause the Intel=AE 82574L Gigabit Ethernet Controller to become unresponsive until corrected by a full platform power cycle. Intel was made aware of this issue in September 2012 by the blogs author. Intel worked with the author as well as the original motherboard manufacturer to investigate and determine root cause. Intel root caused the issue to the specific vendor=92s mother board design where an incorrect EEPROM image was programmed during manufacturing. We communicated the findings and recommended corrections to the motherboard manufacturer. It is Intel=92s belief that this is an implementation issue isolated to a specific manufacturer, not a design problem with the Intel 82574L Gigabit Ethernet controller. Intel has not observed this issue with any implementations which follow Intel=92s published design guidelines. Intel recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-g= igabit-ethernet-controller-statement Any questions or concerns may be sent to me. Cheers, Jack From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 18:23:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3EDDAEFB for ; Fri, 8 Feb 2013 18:23:01 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id C16BE759 for ; Fri, 8 Feb 2013 18:23:00 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 30846 invoked from network); 8 Feb 2013 19:22:59 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a; t=1360347779; bh=s67W7mgkCHwZqJNF7sit5RCSxmEaJnF2p4o1Kg868d8=; h=From:To:CC:Subject; b=M8L5+hL+gGJ8+QWb8kOCX2RAf14iniN0ojev8Ri0UGpSYa4CDF17ZkjonYhSa4ir3 gyjrZq0sG1eamw6D7/5I8oGVCojfyvfCCCthdHHWlNiHPtEyhKq/DAblgu/aesovH0 pS/95VF/dBc4miXyBRJWQYhVqCrD2+lv94LVolEU= Received: from nat.misal.pl (HELO [127.0.0.1]) (marek_sal@[83.19.131.171]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 8 Feb 2013 19:22:59 +0100 Message-ID: <5115427E.6000603@wp.pl> Date: Fri, 08 Feb 2013 19:22:54 +0100 From: Marek Salwerowicz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jeremy Chadwick Subject: Re: pkg can't access pkgbeta.freebsd.org References: <51124589.7080800@wp.pl> <8A470115-70FC-4E82-B9C2-97595FFAE73B@my.gd> <5114E961.70706@wp.pl> <20130208165245.GA39423@icarus.home.lan> In-Reply-To: <20130208165245.GA39423@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130208-0, 2013-02-08), Outbound message X-Antivirus-Status: Clean X-WP-DKIM-Status: good (id: wp.pl) X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [cZN0] Cc: Marek Salwerowicz , "freebsd-stable@freebsd.org" , Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 18:23:01 -0000 W dniu 2013-02-08 17:52, Jeremy Chadwick pisze: > Not "probably": > > http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/000001.html > > Five hours later (read closely): > > http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/000002.html > > Folks should be subscribing to freebsd-ops-announce for this kind of > stuff, as it's the mailing list for problems with freebsd.org services. Thanks for hints ! Already subscribed! -- Marek Salwerowicz From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 18:46:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 816FCA4B for ; Fri, 8 Feb 2013 18:46:41 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ee0-f45.google.com (mail-ee0-f45.google.com [74.125.83.45]) by mx1.freebsd.org (Postfix) with ESMTP id 04ACA8AD for ; Fri, 8 Feb 2013 18:46:40 +0000 (UTC) Received: by mail-ee0-f45.google.com with SMTP id b57so2165352eek.4 for ; Fri, 08 Feb 2013 10:46:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=SjT8TFg8RY26yRY/Oytec1l6gobb3ovCMbXVHdmKqlc=; b=uoOFUif5ru4vba1AqnFs+SwSi3oc5aUi80jm4qeBoDJSYaCZ215GFk7GA+BeMyT/h7 oohMKA9Hq0vE5Eejgb4MSY+nLW2o2T4NVhg+jPNEOgfKa4/GvGdTh7/Q/6KBTO+9f9wy 5I1s1K1cNHYuhdK4btMP3Ri4UBXRJsOoHKC1fS3W42Zl78Gh+k8KQrvDYc6q2kfwfk4s K99NYPWxzZ1wkuNueC5GaShj4FluPuS+SDPWiljlO8hs/sdw6ogVxT3KR+I/0mr2vU1r YAs9lBA/czdYdMHDHNYtCfb9POc8tnXbJwglVhAuucj+cMf+dtNgImztOsTUP0AGnV41 tD+A== X-Received: by 10.14.183.67 with SMTP id p43mr18693652eem.10.1360349194264; Fri, 08 Feb 2013 10:46:34 -0800 (PST) Received: from [192.168.1.104] (45.81.datacomsa.pl. [195.34.81.45]) by mx.google.com with ESMTPS id f6sm48711267eeo.7.2013.02.08.10.46.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 10:46:33 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: setfacl man page states "d=delete_child" and "D=delete" Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <511514F5.4010504@omnilan.de> Date: Fri, 8 Feb 2013 19:46:24 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <511514F5.4010504@omnilan.de> To: Harald Schmalzbauer X-Mailer: Apple Mail (2.1283) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 18:46:41 -0000 Wiadomo=B6=E6 napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o = godz. 16:08: > Hello, >=20 > I think there's a confusion in the man page setfacl(1). >=20 > In my tests, "D" means "delete_child" and "d" "delete"; like it's true > for other NFSv4 implementations. But manpage tells the other way = around. Fixed the man page, thanks! [..] > P.S.: Btw., can anybody explain me why (at some time, someone decided > that) write permission to a directory does override file permissions > inside the directory? Not sure what you mean here. If you're asking why having write = permission to the directory gives the ability to remove files inside that = directory, despite not having write permission to the files themselves - well, = that's how it always worked. I guess the rationale is that when you remove a = file, you're modifying (writing) the directory, not the file contents. --=20 If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 19:05:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A642FE69 for ; Fri, 8 Feb 2013 19:05:44 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-da0-f53.google.com (mail-da0-f53.google.com [209.85.210.53]) by mx1.freebsd.org (Postfix) with ESMTP id 7FBEE971 for ; Fri, 8 Feb 2013 19:05:44 +0000 (UTC) Received: by mail-da0-f53.google.com with SMTP id r13so479978daj.26 for ; Fri, 08 Feb 2013 11:05:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=1joC+Eo5NrnrXiz6Zrv6lvyB8AGtuIyadol9/Lw6z0M=; b=f/VQPCmqP70g4EN00ylQJgdOxtrfKyl1zJW0sDic7gbK/OHFsPO6ZkAhyMsTU5FXXj kiDBQG0m+SwxJLHLBRRQLk+tNqY6ZJdTwYxTgekcuqf541p7D/7XaIT7gJtl3ia0MCUL TM4loePIdFnRsz6t+rgplyyIhSGQssL93/Sns= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=1joC+Eo5NrnrXiz6Zrv6lvyB8AGtuIyadol9/Lw6z0M=; b=eV5uO0+d6VTW0jYf2zMS4MPZeDIh9w4d1zSU7GKPpUGbj4T9g8zxTQ9ob5C+CFEjIR hFNTPocI+f8p/m3+hC4H4L8La4iXeAQqvbmV0o3FumnU2aKQpBWxXTj/Lc8xw8WuO3wz CyUO5KynJnp3393kT5ZvRq7fBwi/TfDZ9S7Ztiv35urCQ73RkgnoTQLd3521+iJz/fUL 9jK6wYOfvv/Nr1HnugGsnKdowLSXVFPsn1r47YWHelDjHMsYgtKPheBePGjyRtmNAUWp QzSuPxhwIaf/eQB5UuSZulXmWXurEJ1WsztiQUdakY2CTkGcsUnU0g4VIQy5/Q8ig+kI H8Cg== X-Received: by 10.66.72.97 with SMTP id c1mr19929641pav.48.1360350343443; Fri, 08 Feb 2013 11:05:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.66.148.10 with HTTP; Fri, 8 Feb 2013 11:05:13 -0800 (PST) In-Reply-To: References: <511514F5.4010504@omnilan.de> From: Eitan Adler Date: Fri, 8 Feb 2013 14:05:13 -0500 Message-ID: Subject: Re: setfacl man page states "d=delete_child" and "D=delete" To: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmpaitDytJ6KXgCkd7Cq4oU4D+R1wDLYqbpzITCocL3aVWacK9TmgnA/biq5uv2LHyCsn2O Cc: Harald Schmalzbauer , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 19:05:44 -0000 On 8 February 2013 13:46, Edward Tomasz Napiera=C5=82a = wrote: > Wiadomo=C5=9B=C4=87 napisana przez Harald Schmalzbauer w dniu 8 lut 2013,= o godz. 16:08: >> Hello, >> >> I think there's a confusion in the man page setfacl(1). >> >> In my tests, "D" means "delete_child" and "d" "delete"; like it's true >> for other NFSv4 implementations. But manpage tells the other way around. > > Fixed the man page, thanks! There are more errors. Please see the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Ddocs/174433 --=20 Eitan Adler From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 19:21:56 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 75C7A468 for ; Fri, 8 Feb 2013 19:21:56 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id F121BA1C for ; Fri, 8 Feb 2013 19:21:55 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r18JLrLH016889; Fri, 8 Feb 2013 20:21:53 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r18JLrGP016888; Fri, 8 Feb 2013 20:21:53 +0100 (CET) (envelope-from olli) Date: Fri, 8 Feb 2013 20:21:53 +0100 (CET) Message-Id: <201302081921.r18JLrGP016888@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, jmg@funkthat.com Subject: Re: re(4) problems with GA-H77N-WIFI In-Reply-To: <20130204221043.GU1410@funkthat.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 19:21:56 -0000 John-Mark Gurney wrote: > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100: > > John-Mark Gurney wrote: > > > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: > > > > I'm running a recent stable/9 (about 14 days old). > > > > What's the best way to debug this problem? At the > > > > moment I'm not even sure if it's the hardware, or if > > > > it's FreeBSD's fault (or my fault) ... > > > > > > Have you tried to disable msi and msix? > > > > > > hw.pci.enable_msix: 1 > > > hw.pci.enable_msi: 1 > > > > I tried these entries in /boot/loader.conf, according to > > the re(4) manual page: > > > > hw.re.msi_disable="1" > > hw.re.msix_disable="1" > > > > Unfortunately it didn't make a difference. > > Did you try in loader.conf: > hw.pci.enable_msix="0" > hw.pci.enable_msi="0" > > To disable MSI for the whole system? Ok, today I got a few minutes, so I booted and tested with all of these lines in loader.conf: hw.re.msi_disable="1" hw.re.msix_disable="1" hw.pci.enable_msix="0" hw.pci.enable_msi="0" Unfortunately it didn't make any difference. I also tried to enable polling on re1, just in case that something is wrong with interrupts (I assume that polling mode doesn't require any interrupts), but it didn't help either. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "The last good thing written in C was Franz Schubert's Symphony number 9." -- Erwin Dieterich From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 19:27:57 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30E4464E for ; Fri, 8 Feb 2013 19:27:57 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id 9DD5EA65 for ; Fri, 8 Feb 2013 19:27:56 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r18JRtEx017320; Fri, 8 Feb 2013 20:27:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r18JRtYk017319; Fri, 8 Feb 2013 20:27:55 +0100 (CET) (envelope-from olli) Date: Fri, 8 Feb 2013 20:27:55 +0100 (CET) Message-Id: <201302081927.r18JRtYk017319@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, pyunyh@gmail.com Subject: Re: re(4) problems with GA-H77N-WIFI In-Reply-To: <20130206055322.GA1442@michelle.cdnetworks.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 19:27:57 -0000 I'm sorry for the late reply. I didn't have much time this week to investigate this issue. At the moment I implemented a work-around with an additional switch using VLANs, but I'd really like to get the second NIC working. YongHyeon PYUN wrote: > On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver Fromme wrote: > > Recently I got a new mainboard for a router, it's a > > Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. > > > > The problem is that re0 works fine and re1 doesn't: > > It doesn't receive any packets. Tcpdump displays all > > outgoing packets, but no incoming ones on re1. > > Can you see the packets sent from re1 on other box? No. I can only see them locally in tcpdump, but they never hit the wire. > If not, it probably indicates GMAC is in weird state which in turn > indicates initialization was not complete for the controller. > > > Ifconfig shows the link correctly (100 or 1000 Mbit, > > depending on where I plug the cable in). > > I also swapped cables just to be sure, but it made no > > difference. > > If you cold-boot the box with UTP cable plugged in to re1 does it > make any difference? No, it doesn't. > > I'm running a recent stable/9 (about 14 days old). > > What's the best way to debug this problem? At the > > I would check whether GMAC is active when driver detects a valid > link. Add a code like the following to re_miibus_statchg() to get > the status of RL_COMMAND register. You would get the status > whenever a link is established with link partner. re0: CMD 0x0c re0: link state changed to UP re0: link state changed to DOWN re1: link state changed to UP re1: link state changed to DOWN re1: CMD 0x0c re1: link state changed to UP re0: CMD 0x0c re0: link state changed to UP re1: link state changed to DOWN I always seem to get 0x0c for both re0 and re1. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 20:42:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 55C52BC2 for ; Fri, 8 Feb 2013 20:42:35 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ea0-f177.google.com (mail-ea0-f177.google.com [209.85.215.177]) by mx1.freebsd.org (Postfix) with ESMTP id D674EEC7 for ; Fri, 8 Feb 2013 20:42:34 +0000 (UTC) Received: by mail-ea0-f177.google.com with SMTP id n13so1843011eaa.8 for ; Fri, 08 Feb 2013 12:42:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=8PLJ8gk4HnLQjpX+S/SrLSMU112sLbYcSSpJYaXPEUE=; b=X7cp3R6bLMQ15+XOM5sgpEg7z9zOcMZo+rCygH6W8nVJ0CJD6uRkoCb9ps5iHftnXZ EYQTmKYNn1V8ztnac9nkHEYT648CSv+x7vxZf0U3zzrh6g/bm5zdY/GmNUqHu2cuFccz Xy1FJhMFemu8MvMgEKQXVFsx86ONrzlaleSW+cDYA0++dDLcbIyl/mT4MAAU0dpWmDH2 gBpgwpPXwdkGbCoQkdOIWBa/vfrC1w6HzqI5ItbWZAl2QaWpv3SeIqukY4zgG9ustGJX oXdbfiGkKHsStczZg1ntlmZP/2hZCS82v43C7wMI3LlY+fBckizSI2qW3GJnb9Y3fdrH TQHQ== X-Received: by 10.14.214.67 with SMTP id b43mr19499840eep.33.1360356148254; Fri, 08 Feb 2013 12:42:28 -0800 (PST) Received: from [192.168.1.104] (45.81.datacomsa.pl. [195.34.81.45]) by mx.google.com with ESMTPS id o3sm49163579eem.15.2013.02.08.12.42.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 12:42:27 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: setfacl man page states "d=delete_child" and "D=delete" Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: Date: Fri, 8 Feb 2013 21:42:25 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8911987F-2572-4722-9E0F-06820DD5EAA2@freebsd.org> References: <511514F5.4010504@omnilan.de> To: Eitan Adler X-Mailer: Apple Mail (2.1283) Cc: Harald Schmalzbauer , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 20:42:35 -0000 Wiadomo=B6=E6 napisana przez Eitan Adler w dniu 8 lut 2013, o godz. = 20:05: > On 8 February 2013 13:46, Edward Tomasz Napiera=B3a = wrote: >> Wiadomo=B6=E6 napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o = godz. 16:08: >>> Hello, >>>=20 >>> I think there's a confusion in the man page setfacl(1). >>>=20 >>> In my tests, "D" means "delete_child" and "d" "delete"; like it's = true >>> for other NFSv4 implementations. But manpage tells the other way = around. >>=20 >> Fixed the man page, thanks! >=20 > There are more errors. Please see the PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Ddocs/174433 The 'S' issue was fixed earlier. Thanks for pointing out this PR. I _really_ wish we had a bugtracker that would allow me to subscribe to keywords such as "acl", "growfs" or "iscsi". ;-/ --=20 If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 21:22:46 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4F749E37; Fri, 8 Feb 2013 21:22:46 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 1A57C1A9; Fri, 8 Feb 2013 21:22:46 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id k11so5517763iea.38 for ; Fri, 08 Feb 2013 13:22:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=57IIWrrVqaObkwG/g0OOrmfRz/OV6FgzzNeNZlMtQsI=; b=Vz+uR1umtxp11n+C2B8yHk+dBGda0sYWxKlw3CnT5YvNFiBcT7FwnXr8uBBrwbMDPQ lT3xEbX8j5LLfYrny4Xmt+u14X1/NVo1+tqsx/M075+EwTXOaEHneCIg1stCMJ/6/Ard Q/KxQ5eW1s+KN2GGNnq9AsB0QcsfSgzvv8zntOn1tbyX9l8d63QkyqWn/gECoMwA3dXq 5QqmMdWAmyEHWg1dWsupmdEiqS2XJTQBZvS812XZ8V2z0Mwqn0kXQrpSc8MNiWf7m7MH h4OHqyFMZsUkQQr6rJIZnYVbd1YlmAH8WOPSF+wP5Qd7Mf5mSbSkceSCKUx1kttU7OhC 5Zpw== X-Received: by 10.50.197.170 with SMTP id iv10mr2241472igc.62.1360358565568; Fri, 08 Feb 2013 13:22:45 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.64.16.73 with HTTP; Fri, 8 Feb 2013 13:22:15 -0800 (PST) In-Reply-To: <8911987F-2572-4722-9E0F-06820DD5EAA2@freebsd.org> References: <511514F5.4010504@omnilan.de> <8911987F-2572-4722-9E0F-06820DD5EAA2@freebsd.org> From: Chris Rees Date: Fri, 8 Feb 2013 21:22:15 +0000 X-Google-Sender-Auth: 6c4KiCzIGHCOggANnLSJjX92tx4 Message-ID: Subject: Re: setfacl man page states "d=delete_child" and "D=delete" To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Cc: Eitan Adler , FreeBSD , Harald Schmalzbauer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 21:22:46 -0000 On 8 February 2013 20:42, Edward Tomasz Napiera=B3a wro= te: > Wiadomo=B6=E6 napisana przez Eitan Adler w dniu 8 lut 2013, o godz. 20:05= : >> On 8 February 2013 13:46, Edward Tomasz Napiera=B3a = wrote: >>> Wiadomo=B6=E6 napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o g= odz. 16:08: >>>> Hello, >>>> >>>> I think there's a confusion in the man page setfacl(1). >>>> >>>> In my tests, "D" means "delete_child" and "d" "delete"; like it's true >>>> for other NFSv4 implementations. But manpage tells the other way aroun= d. >>> >>> Fixed the man page, thanks! >> >> There are more errors. Please see the PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Ddocs/174433 > > The 'S' issue was fixed earlier. Thanks for pointing out this PR. > > I _really_ wish we had a bugtracker that would allow me to subscribe > to keywords such as "acl", "growfs" or "iscsi". ;-/ Have a look in /g/hubgnats/gnats-aa/incoming-PRs/bin/lookups.txt on hub.freebsd.org. Just don't be too greedy with your keywords ;) Chris From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 22:29:31 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 30BC139C for ; Fri, 8 Feb 2013 22:29:31 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id E24826AB for ; Fri, 8 Feb 2013 22:29:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 552FB5097A for ; Fri, 8 Feb 2013 22:29:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1m5BTwAYGPRH for ; Fri, 8 Feb 2013 22:29:24 +0000 (UTC) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 135CB50979 for ; Fri, 8 Feb 2013 22:29:24 +0000 (UTC) From: Dan Langille Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: patch which implements ZFS LZ4 compression Date: Fri, 8 Feb 2013 17:29:22 -0500 Message-Id: To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 22:29:31 -0000 Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 = compression. https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM short link: http://bpaste.net/show/76095 HTH --=20 Dan Langille - http://langille.org From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 22:53:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 99C5CEB for ; Fri, 8 Feb 2013 22:53:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) by mx1.freebsd.org (Postfix) with ESMTP id 1568F7E7 for ; Fri, 8 Feb 2013 22:52:59 +0000 (UTC) Received: from epsilon.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id D98B41CEA6; Fri, 8 Feb 2013 14:52:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1360363979; bh=1hQ1E3eskhRQpRI2Ra4UgErPFD+H9+m93rV7bTUzv7o=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=B3QISdXZEaG47lGFJwuMguHZ7PmGy/aPXAAWfbtG4815HBeTQ/51mjwHIy2BbWNxc cxlHi1ZYnChOPptiYEL8YDn8zx6Jfrqd+fWyV0uQyMo8ptG0J3GvCKVGdZiWzSDg1H LExgA/H2u2r7JIPKwX3kHYa7RgduJd2gt9Xqzyrk= Message-ID: <511581C9.5040608@delphij.net> Date: Fri, 08 Feb 2013 14:52:57 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Dan Langille Subject: Re: patch which implements ZFS LZ4 compression References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 22:53:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/08/13 14:29, Dan Langille wrote: > Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 > compression. > > https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM > > short link: http://bpaste.net/show/76095 Please DO NOT use this patch! It will ruin your data silently. As I already posted on Ivan's Google+ post, I'm doing final universe builds to make sure that there is no regression and will merge my changes to -HEAD later today. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJRFYHJAAoJEG80Jeu8UPuz3e8IALAcbjZo063casLry/zyBjLe jbat7AmmWTQ5ndBtfx5PxAV1of6ePCiQQS/RQVd001c5M32hzfoqb7524th3giyx q4RRuVPIc6YswJOe3Gz/vRyHdBRfJlownxZy1Glv480qK9dzeUtd2ziZhoi+FZ1X PfigRwg/9OtyDbmUhEqDvq2qeyAakuiE6yL9NVlGGKSe8GysYWPQFisVfDWn3WYH a+Rt+O3P/QHK0mTWBYTs/r92AU9J0Sv4plhNNQZSZWpAlQLuWRhMit/2e2W/0TPx XnXXuzdr01/cE/+ou3MMnq+uvO1FiqKBUXN6/oJzZnl/VkvvL795iT/C5KGq+2s= =mVAM -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 23:01:37 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2EF4A2A4 for ; Fri, 8 Feb 2013 23:01:37 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0B5E0845 for ; Fri, 8 Feb 2013 23:01:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id E78C35097A; Fri, 8 Feb 2013 23:01:35 +0000 (UTC) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcxlGTDzKIGR; Fri, 8 Feb 2013 23:01:35 +0000 (UTC) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 5796850979 ; Fri, 8 Feb 2013 23:01:35 +0000 (UTC) Subject: Re: patch which implements ZFS LZ4 compression Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-1 From: Dan Langille In-Reply-To: <511581C9.5040608@delphij.net> Date: Fri, 8 Feb 2013 18:01:33 -0500 Content-Transfer-Encoding: 7bit Message-Id: References: <511581C9.5040608@delphij.net> To: d@delphij.net, Xin Li X-Mailer: Apple Mail (2.1283) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 23:01:37 -0000 On Feb 8, 2013, at 5:52 PM, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 02/08/13 14:29, Dan Langille wrote: >> Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 >> compression. >> >> https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM >> >> short link: http://bpaste.net/show/76095 > > Please DO NOT use this patch! It will ruin your data silently. I'm sorry, I will remove the post. > > As I already posted on Ivan's Google+ post, I'm doing final universe > builds to make sure that there is no regression and will merge my > changes to -HEAD later today. My apologies. :) Thank you. -- Dan Langille - http://langille.org From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 23:09:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E40255CB for ; Fri, 8 Feb 2013 23:09:32 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:64]) by mx1.freebsd.org (Postfix) with ESMTP id C98F589B for ; Fri, 8 Feb 2013 23:09:32 +0000 (UTC) Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta07.emeryville.ca.mail.comcast.net with comcast id xqAz1k0010x6nqcA7z9Y7G; Fri, 08 Feb 2013 23:09:32 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta12.emeryville.ca.mail.comcast.net with comcast id xz8W1k00d1t3BNj8Yz8Wmh; Fri, 08 Feb 2013 23:08:31 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8FD4273A31; Fri, 8 Feb 2013 15:08:30 -0800 (PST) Date: Fri, 8 Feb 2013 15:08:30 -0800 From: Jeremy Chadwick To: d@delphij.net Subject: Re: patch which implements ZFS LZ4 compression Message-ID: <20130208230830.GA45081@icarus.home.lan> References: <511581C9.5040608@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <511581C9.5040608@delphij.net> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360364972; bh=PxOf/5ZgtrJtqpapSXU0YkT5ao/2tlXRH/oaeKSMEog=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=NXSkUdJXTWJkGV6+R4QTr7V2QafjouVi4BAAMFqkFUUY5XHGRw3+EPAe3wO0A4+Br cr+IEPTU7zpkIhlLQsUitm9hz2NWXJfVU9yyws3jJ0Xj8FSLdm89m3M7yO4PdYmoUz KAgp1rEvFyTvczEL/EyOzHD1TOGNbxrvaSFoPCV7fmfTefzTvOkxgBkT6FD7Etnk1X xiKlnLXGAvc/+MicxRTz/4h7ENXAbgHfTVj+GnGWoyIFTt8Lh+GJbqEIhE30ehKVky PYpmA7VaDM2tVqdrwsKrTo9oPmxv8ZRdE4GsqIwS7Q9lC8AkWV1xjXtXyYa4Jzfbrl 6UKvtDlmO5u4A== Cc: freebsd-stable@freebsd.org, Dan Langille X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 23:09:32 -0000 On Fri, Feb 08, 2013 at 02:52:57PM -0800, Xin Li wrote: > On 02/08/13 14:29, Dan Langille wrote: > > Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 > > compression. > > > > https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM > > > > short link: http://bpaste.net/show/76095 > > Please DO NOT use this patch! It will ruin your data silently. > > As I already posted on Ivan's Google+ post, I'm doing final universe > builds to make sure that there is no regression and will merge my > changes to -HEAD later today. Another compression algorithm, this time 50%+ faster than lzjb. Great, fine, wonderful, awesome, kudos, huzzah, blah blah blah. So when is someone going to step up to the plate and fix how compression (as well as dedup) destroys interactivity on FreeBSD? Do I need to remind folks of this issue once again? Here you have it, dated October 2011, including the root cause and how it was fixed in Solaris et al: Description: http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012718.html Explanation and how Solaris et al fixed it, and how on Solaris the problem was major enough that it even caused NFS timeouts (sound familiar to anyone?): http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012726.html Further testing showing gzip-1 vs. lzjb and interactivity stalls: http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012752.html This is still a problem with base/stable/9. And as I have said elsewhere on lists, do not ask me to run CURRENT -- it will be a cold day in hell before I ever do that. I assume this same problem exists in CURRENT unless I have some key developer/committer say "I backported this fix in CURRENT, absolutely 100% sure". I'm also wondering why iXSystems hasn't stepped up to the plate to contribute to making this happen, given their business focus. I do not have the knowledge of the kernel (or of threading) to fix this myself, and for that I do apologise. But every time I see compression or dedup mentioned, I use the opportunity to bring up this subject. STOP ADDING FEATURES AND FIX STUFF LIKE THIS INSTEAD -- while new algorithms are neat/fun toys, they do not truly fix issues like this. How this problem has continually gotten overlooked is beyond me. If you want a PR for it, I'll file one, but all it's going to contain is the contents of this Email. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 00:38:25 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 050EFF81; Sat, 9 Feb 2013 00:38:25 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7F730CC8; Sat, 9 Feb 2013 00:38:23 +0000 (UTC) Received: from [10.138.22.220] ([1.124.113.155]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r190bqro039647 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Feb 2013 11:07:59 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Intel 82574 issue reported on Slashdot Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=windows-1252 From: "Daniel O'Connor" In-Reply-To: Date: Sat, 9 Feb 2013 11:07:51 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Jack Vogel X-Mailer: Apple Mail (2.1499) X-Spam-Score: -0.023 () BAYES_00,HELO_MISC_IP,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD stable , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , FreeBSD Current X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 00:38:25 -0000 On 09/02/2013, at 4:46, Jack Vogel wrote: > recommends contacting your motherboard manufacturer if you have = continued > concerns or questions whether your products are impacted. > Here is the link: >=20 > = http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-= gigabit-ethernet-controller-statement >=20 > Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically = information free, they don't name names and provide no script or = downloadable code that will allow end users to check if they are = affected. "Contact your motherboard manufacturer" is much more time consuming than = "Run sysctl... | grep foo | awk ..." to see if your system is affected. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 07:34:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DC747D8D for ; Sat, 9 Feb 2013 07:34:57 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id C2965CF2 for ; Sat, 9 Feb 2013 07:34:57 +0000 (UTC) Received: from Xins-MacBook-Pro-2.local (unknown [IPv6:2001:470:83bf:0:549b:8e16:4f47:4e5b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 749861C952; Fri, 8 Feb 2013 23:34:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1360395297; bh=EhKSC2q/Nm/N66HvgqJkL4EIvs/a0uryLmXxkWVqFk0=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=SRFkVSFew2KMC903hSjC60CLQI+P7y0w7G/WtgVX5xk3YpBA8pd0aURaExXTEsAzv 4ZqH1aDdxB6VC3wssjmEBurwmI91musgqu7hJlswdfuSKeqGdNmpAIG5DxJ8YtWQZs +QlTJIa+xSW4GZj6gVXjJvS1HLw7JZ1sjp6BJx+U= Message-ID: <5115FC20.7060906@delphij.net> Date: Fri, 08 Feb 2013 23:34:56 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: patch which implements ZFS LZ4 compression References: <511581C9.5040608@delphij.net> In-Reply-To: <511581C9.5040608@delphij.net> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 07:34:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 For those who are inpatient, here is an overlay for LZ4 for 9-STABLE. http://people.freebsd.org/~delphij/misc/lz4.tar.xz Overwrite /usr/src and recompile ZFS module. Note: before using this in any serious environment, please be sure to test if there is any data corruption by comparing the files copied to a LZ4 dataset after export and re-import the pool, or reboot. I have only tested the code on amd64 and would like to see if it works on big endian environment, etc. Cheers, -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJRFfwgAAoJEG80Jeu8UPuzjKgH/0i+PShTX3kyLvEjORHjmEp+ T0YxLiTEssmpz8IhUwbjN+FLoQZlV+DCL5MUBzIsA5kM3p1aUgffrNnO1RvZmbhT y+pnKxEDay30QhMs48jWLO6oyHA07bb8q5xyut+noK6X1y4epqwrWid44nqlzPZQ w6XKhCuz8DXm4TIKQpeB4ncFNfUv+rlImmn5XToC6DaKn/2XtYVLVE73pjP3qANL mxZA/RqJNQy1cBp0gougDcw6AoNMBkjfxaNe0V073nEffyXgI/1BeCWsxKmWFNWb VNGGjxLzmpP4MGz2SAABfaUvRb306pHJtfYWtoeIxpZLM0A9h9wnDGUWo9w+lLo= =eVP8 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 08:20:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C7E1A43E for ; Sat, 9 Feb 2013 08:20:01 +0000 (UTC) (envelope-from jan0sch@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC16E03 for ; Sat, 9 Feb 2013 08:20:00 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.32]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MfCFw-1UJ230090s-00OkxU for ; Sat, 09 Feb 2013 09:20:00 +0100 Received: (qmail invoked by alias); 09 Feb 2013 08:19:59 -0000 Received: from dslb-088-072-251-217.pools.arcor-ip.net (EHLO magni.rostock.home) [88.72.251.217] by mail.gmx.net (mp032) with SMTP; 09 Feb 2013 09:19:59 +0100 X-Authenticated: #1545395 X-Provags-ID: V01U2FsdGVkX1/yo0psmmXy67OBJMp4zdv5Q4ETwBBJTc+zdJWzKe kKkSa1l5sWU7j1 Date: Sat, 9 Feb 2013 09:19:15 +0100 From: Jens Jahnke To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1 occasional kernel panic Message-Id: <20130209091915.dfca70e96e1e6b4590eda6a3@gmx.net> In-Reply-To: <20130206140244.6b9f549568fc42a2e1063713@gmx.net> References: <20130206092908.d773cfde61f35347f32f6c47@gmx.net> <51124F4F.4050902@FreeBSD.org> <20130206140244.6b9f549568fc42a2e1063713@gmx.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) X-Face: &?!P`87-36gaG)/K:yi&ixw=uy]y'?$vrc Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Sat__9_Feb_2013_09_19_15_+0100_90GnJiJkjPoEhlOy" X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 08:20:01 -0000 --Signature=_Sat__9_Feb_2013_09_19_15_+0100_90GnJiJkjPoEhlOy Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 6 Feb 2013 14:02:44 +0100 Jens Jahnke wrote: JJ> On Wed, 06 Feb 2013 14:40:47 +0200 JJ> Andriy Gapon wrote: JJ>=20 JJ> AG> "error 6" is ENXIO, which usually corresponds to a disappearing JJ> AG> device or some such. Do you get anything in logs (or other JJ> AG> objective experience) that could look like that? JJ>=20 JJ> Nothing found so far. System ran stable for the last 18 hours JJ> through. JJ>=20 JJ> I'll look if the error occurs again. It seems that the error is somewhat hardware or bios related. If the machine has been powered off for at least some hours the error occurs on the first boot. It reoccurs if the machine is reset but does not if the machine is powered off and powered on again after a minute. If I set the board controller to ide mode everything is fine but my ssd is not recognized. Another option that seems to work is powering on the machine enter bios and let it run for some minutes. Afterwards I can boot without errors. So maybe the controller needs I "warmup phase". ;) Anyway, I can live with that and thanks for all your answers. Regards, Jens --=20 09. Hornung 2013, 09:08 Homepage : http://www.jan0sch.de Fremen add life to spice! --Signature=_Sat__9_Feb_2013_09_19_15_+0100_90GnJiJkjPoEhlOy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQG8BAEBCgAGBQJRFganAAoJED2+SXzzbciGO7wNAKfWDlNns+dazZqxO54kOUr4 7EoWZMDEfNY0FaVdkTcQfvIb3/pfB8zuWuZMYcNVzo5qywIY+bGb/k+mhvzAB7oG BogMD0dM7WCcmV5PFbKuhbOmKPjS0JJqKvSQuBIPGga0eGbwwGB7PbaWeFkcxlXu DENEYbYH9SGxJeFwsZVB9oybdNYEE8TkmvvF+YtPNRYcb3qecK4itFbcFGWqbp37 CAFo97MKtosn2TyZj1BNCOA1lBX3fwNyoOowaPnCDNbzfGrMEdC0yhwDc9qCJi8Q 91vYiz0bcErHv6K48E/4wDyn3GkhuLatC1X9WM4607H0lKzNN44DRtXE2TYzJDQf KyeNeWl/xV4T7y2r1nXw//BdsZiOEADS4upj0PY/xFMCPaoZhyx/wXTzSkujcMCH orcXVgyzO8V8TAhhMG0jWp/iryWo+6Zjy4D/AN4RzdKL1P/pleZCskIyCE0FsJET uol22GCQnc2OpyF/+3ORdhvI+Kh2QNKlRLAU9mI+iSJgXS4sGrmgWTobVBZZrPTO MxOE/0yPJhiyuZ9Ew8/o =Jb6D -----END PGP SIGNATURE----- --Signature=_Sat__9_Feb_2013_09_19_15_+0100_90GnJiJkjPoEhlOy-- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 10:12:26 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 97EE3EAD; Sat, 9 Feb 2013 10:12:26 +0000 (UTC) (envelope-from parv@pair.com) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 18E1E191; Sat, 9 Feb 2013 10:12:24 +0000 (UTC) X-Authority-Analysis: v=2.0 cv=bJmU0YCZ c=1 sm=0 a=lLOF/jpPrR0dcgWXP1EvZg==:17 a=xCuMbNp8hPoA:10 a=dLZphiicA4cA:10 a=R5FhY6rjjCMA:10 a=kj9zAlcOel0A:10 a=Ymsr-CWnAAAA:8 a=LDrFwfghZz0A:10 a=iReALljSAAAA:8 a=pGLkceISAAAA:8 a=QyXUC8HyAAAA:8 a=RaItmienAAAA:8 a=E70Ph-o_AAAA:8 a=WxxYND6mw3PQpSCbB8QA:9 a=CjuIK1q_8ugA:10 a=4elu-xP5etcA:10 a=MSl-tDqOz04A:10 a=lLOF/jpPrR0dcgWXP1EvZg==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 204.210.114.114 Received: from [204.210.114.114] ([204.210.114.114:49924] helo=localhost.hawaii.res.rr.com) by hrndva-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 59/B5-06157-10126115; Sat, 09 Feb 2013 10:12:18 +0000 Received: by localhost.hawaii.res.rr.com (Postfix, from userid 1000) id AFE745CAD; Sat, 9 Feb 2013 00:12:19 -1000 (HST) Date: Sat, 9 Feb 2013 00:12:19 -1000 From: Parv To: Daniel O'Connor Subject: Re: Intel 82574 issue reported on Slashdot Message-ID: <20130209101219.GA2133@holstein.holy.cow> Mail-Followup-To: Daniel O'Connor , Jack Vogel , FreeBSD stable , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , FreeBSD Current References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: FreeBSD stable , FreeBSD Current , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , Jack Vogel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 10:12:26 -0000 in message , wrote Daniel O'Connor thusly... > > > On 09/02/2013, at 4:46, Jack Vogel wrote: > > > recommends contacting your motherboard manufacturer if you have > > continued concerns or questions whether your products are > > impacted. Here is the link: > > > > http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement > > > > Any questions or concerns may be sent to me. > > In all honesty.. The blog post (and your email) are basically > information free, they don't name names and provide no script or > downloadable code that will allow end users to check if they are > affected. > "Contact your motherboard manufacturer" is much more time > consuming than "Run sysctl... | grep foo | awk ..." to see if your > system is affected. Gift^WStraight from horse's mouth ... http://blog.krisk.org/2013/02/packets-of-death.html http://www.kriskinc.com/intel-pod - parv -- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 10:15:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB5D12D3; Sat, 9 Feb 2013 10:15:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 420451D2; Sat, 9 Feb 2013 10:15:40 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-73-50.lns20.adl2.internode.on.net [118.210.73.50]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r19AFQce071839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Feb 2013 20:45:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Intel 82574 issue reported on Slashdot Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20130209101219.GA2133@holstein.holy.cow> Date: Sat, 9 Feb 2013 20:45:26 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: <1D962264-6DF6-4192-8190-34E22AADE843@gsoft.com.au> References: <20130209101219.GA2133@holstein.holy.cow> To: Parv X-Mailer: Apple Mail (2.1499) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD stable , FreeBSD Current , "Pieper, Jeffrey E" , FreeBSD Net , "Hearn, James R" , "Vogel, Jack" , "Ronciak, John" , Jack Vogel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 10:15:41 -0000 On 09/02/2013, at 20:42, Parv wrote: >> "Contact your motherboard manufacturer" is much more time >> consuming than "Run sysctl... | grep foo | awk ..." to see if your >> system is affected. >=20 > Gift^WStraight from horse's mouth ... >=20 > http://blog.krisk.org/2013/02/packets-of-death.html I've already read this. > http://www.kriskinc.com/intel-pod I'd really rather a test which reads the EEPROM and tells me if it's a = problem rather than hang the interface on a machine :) In any case that isn't the point - this may be a "vendor issue" but it = reflects poorly on Intel that they didn't take proper ownership of the = issue. It would be far, far better for their image to say "some systems = may have the fault, go to http://.... to find a way to test for your = operating system". -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 10:22:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1574E61D for ; Sat, 9 Feb 2013 10:22:21 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id B69C8216 for ; Sat, 9 Feb 2013 10:22:19 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 35CDB6A6003; Sat, 9 Feb 2013 11:22:18 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id r19AMHO8092871; Sat, 9 Feb 2013 11:22:17 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id r19AMH0w092515; Sat, 9 Feb 2013 11:22:17 +0100 (CET) (envelope-from lars) Date: Sat, 9 Feb 2013 11:22:17 +0100 From: Lars Engels To: Kurt Jaeger Subject: Re: ethtool-like utility for FreeBSD ? Message-ID: <20130209102216.GR55167@e-new.0x20.net> References: <20130207141032.GT8239@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3mpYglQ0MpZscA/H" Content-Disposition: inline In-Reply-To: <20130207141032.GT8239@home.opsec.eu> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p4 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 10:22:21 -0000 --3mpYglQ0MpZscA/H Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 2013 at 03:10:32PM +0100, Kurt Jaeger wrote: > Hi! >=20 > There is a posting public about Intel ethernet adapters and their > packets of death: >=20 > http://blog.krisk.org/2013/02/packets-of-death.html >=20 > Now, how can we test the EEPROM from FreeBSD, similar to the > ethtool of Linux ? >=20 > Thanks for any pointer! See this forum posting: http://www.bsdforen.de/showpost.php?p=3D248107&postcount=3D3 --3mpYglQ0MpZscA/H Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEWI1gACgkQKc512sD3afj4mwCfV69ly+6VMNIRtcTPOzjiktNE sCEAnjIboxy3o+uoWIuo5PiiWOo3NZZa =mjIl -----END PGP SIGNATURE----- --3mpYglQ0MpZscA/H-- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 14:24:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8E472108 for ; Sat, 9 Feb 2013 14:24:41 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.38]) by mx1.freebsd.org (Postfix) with ESMTP id 23667CF9 for ; Sat, 9 Feb 2013 14:24:40 +0000 (UTC) Received: from [78.35.140.200] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1U4BL0-0002lA-5A; Sat, 09 Feb 2013 15:23:30 +0100 Date: Sat, 9 Feb 2013 15:19:18 +0100 From: Fabian Keil To: Jeremy Chadwick Subject: Re: patch which implements ZFS LZ4 compression Message-ID: <20130209151918.221176cd@fabiankeil.de> In-Reply-To: <20130208230830.GA45081@icarus.home.lan> References: <511581C9.5040608@delphij.net> <20130208230830.GA45081@icarus.home.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/0wf6BJH=Iy9Q=Ew31ac7O62"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: freebsd-stable@freebsd.org, d@delphij.net, Dan Langille X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 14:24:41 -0000 --Sig_/0wf6BJH=Iy9Q=Ew31ac7O62 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Jeremy Chadwick wrote: > On Fri, Feb 08, 2013 at 02:52:57PM -0800, Xin Li wrote: > > On 02/08/13 14:29, Dan Langille wrote: > > > Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 > > > compression. > > >=20 > > > https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM > > >=20 > > > short link: http://bpaste.net/show/76095 > >=20 > > Please DO NOT use this patch! It will ruin your data silently. > >=20 > > As I already posted on Ivan's Google+ post, I'm doing final universe > > builds to make sure that there is no regression and will merge my > > changes to -HEAD later today. >=20 > Another compression algorithm, this time 50%+ faster than lzjb. Great, > fine, wonderful, awesome, kudos, huzzah, blah blah blah. >=20 > So when is someone going to step up to the plate and fix how compression > (as well as dedup) destroys interactivity on FreeBSD? Do I need to > remind folks of this issue once again? Here you have it, dated October > 2011, including the root cause and how it was fixed in Solaris et al: >=20 > Description: >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012718.html >=20 > Explanation and how Solaris et al fixed it, and how on Solaris the > problem was major enough that it even caused NFS timeouts (sound > familiar to anyone?): >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012726.html >=20 > Further testing showing gzip-1 vs. lzjb and interactivity stalls: >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012752.html >=20 > This is still a problem with base/stable/9. And as I have said > elsewhere on lists, do not ask me to run CURRENT -- it will be a cold > day in hell before I ever do that. I assume this same problem exists in > CURRENT unless I have some key developer/committer say "I backported > this fix in CURRENT, absolutely 100% sure". >=20 > I'm also wondering why iXSystems hasn't stepped up to the plate to > contribute to making this happen, given their business focus. I do not > have the knowledge of the kernel (or of threading) to fix this myself, > and for that I do apologise. >=20 > But every time I see compression or dedup mentioned, I use the > opportunity to bring up this subject. STOP ADDING FEATURES AND FIX > STUFF LIKE THIS INSTEAD -- while new algorithms are neat/fun toys, they > do not truly fix issues like this. How this problem has continually > gotten overlooked is beyond me. Did you consider that other people may have different priorities than you do? > If you want a PR for it, I'll file one, but all it's going to contain is > the contents of this Email. My impression is that your emails describe symptoms and contain some speculation about what the cause might be. I didn't see any sched traces, so it's unclear (to me) that priorities are actual the problem. It's also unclear to me why the dedup and compression issues should be related. There are lots of dedup performance issues reported for Solaris as well and I doubt that they can be fixed for FreeBSD without significantly deviating from the ZFS upstream. I'm not saying a PR would be useless, but in my experience PRs with insufficient information just stay open and if the problem isn't important enough for you to provide additional information filing a PR is unlikely to have a great impact: http://www.freebsd.org/cgi/query-pr-summary.cgi?category=3D&text=3Dzfs Fabian --Sig_/0wf6BJH=Iy9Q=Ew31ac7O62 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEWWuoACgkQBYqIVf93VJ2/1wCfYDJA25qIwfK0sIGAoa64pNEh WW4Ani7iAFn6BtDgiu2xNGr51/qsRDU9 =YXec -----END PGP SIGNATURE----- --Sig_/0wf6BJH=Iy9Q=Ew31ac7O62-- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 20:44:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2ABCD379 for ; Sat, 9 Feb 2013 20:44:39 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:96]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF7D6CD for ; Sat, 9 Feb 2013 20:44:39 +0000 (UTC) Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta09.emeryville.ca.mail.comcast.net with comcast id yLSX1k0061ZMdJ4A9LkeG9; Sat, 09 Feb 2013 20:44:38 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta16.emeryville.ca.mail.comcast.net with comcast id yLkc1k00v1t3BNj8cLkd9Z; Sat, 09 Feb 2013 20:44:37 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BE2BA73A31; Sat, 9 Feb 2013 12:44:36 -0800 (PST) Date: Sat, 9 Feb 2013 12:44:36 -0800 From: Jeremy Chadwick To: Fabian Keil Subject: Re: patch which implements ZFS LZ4 compression Message-ID: <20130209204436.GA67890@icarus.home.lan> References: <511581C9.5040608@delphij.net> <20130208230830.GA45081@icarus.home.lan> <20130209151918.221176cd@fabiankeil.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130209151918.221176cd@fabiankeil.de> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360442678; bh=M+23mrTI6eXnIzfo9uLuSehKPFdkWGrJ6Thm/gsQKs4=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=M3wfog4uVn4nkw9DVksPWl1oCYYVwwBUxTN6mYttftMhRfL5DfkY+2H37wIp+hTe5 ydaR8sIAvWRk83oZYpYz1FWyYLxYZ1sfrjIlwHA+xJVZcC7aQ3jeu8fIkLLijmCTg6 hPQoSQrYiyASMQOJgVxZbRpnJ3AZOYSwOCfD+euPrNLhQMgL6on6JcDdHQl1I/PFEh 2jKrozIjKWzr+gaCjPf+afi8V/iS3HjG5kKIL44+I0oRH/nphmX+32AHBkgNTzXXhV JTRfzFgHf0XueMwrngtev8WT3q2H44SyrqtzZzi4JpRtA1KlA3ny1PCVlC+L+4TkXF KxBiTi/DPLISA== Cc: freebsd-stable@freebsd.org, d@delphij.net, Dan Langille X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 20:44:39 -0000 On Sat, Feb 09, 2013 at 03:19:18PM +0100, Fabian Keil wrote: > Jeremy Chadwick wrote: > > > On Fri, Feb 08, 2013 at 02:52:57PM -0800, Xin Li wrote: > > > On 02/08/13 14:29, Dan Langille wrote: > > > > Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 > > > > compression. > > > > > > > > https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM > > > > > > > > short link: http://bpaste.net/show/76095 > > > > > > Please DO NOT use this patch! It will ruin your data silently. > > > > > > As I already posted on Ivan's Google+ post, I'm doing final universe > > > builds to make sure that there is no regression and will merge my > > > changes to -HEAD later today. > > > > Another compression algorithm, this time 50%+ faster than lzjb. Great, > > fine, wonderful, awesome, kudos, huzzah, blah blah blah. > > > > So when is someone going to step up to the plate and fix how compression > > (as well as dedup) destroys interactivity on FreeBSD? Do I need to > > remind folks of this issue once again? Here you have it, dated October > > 2011, including the root cause and how it was fixed in Solaris et al: > > > > Description: > > > > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012718.html > > > > Explanation and how Solaris et al fixed it, and how on Solaris the > > problem was major enough that it even caused NFS timeouts (sound > > familiar to anyone?): > > > > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012726.html > > > > Further testing showing gzip-1 vs. lzjb and interactivity stalls: > > > > http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012752.html > > > > This is still a problem with base/stable/9. And as I have said > > elsewhere on lists, do not ask me to run CURRENT -- it will be a cold > > day in hell before I ever do that. I assume this same problem exists in > > CURRENT unless I have some key developer/committer say "I backported > > this fix in CURRENT, absolutely 100% sure". > > > > I'm also wondering why iXSystems hasn't stepped up to the plate to > > contribute to making this happen, given their business focus. I do not > > have the knowledge of the kernel (or of threading) to fix this myself, > > and for that I do apologise. > > > > But every time I see compression or dedup mentioned, I use the > > opportunity to bring up this subject. STOP ADDING FEATURES AND FIX > > STUFF LIKE THIS INSTEAD -- while new algorithms are neat/fun toys, they > > do not truly fix issues like this. How this problem has continually > > gotten overlooked is beyond me. > > Did you consider that other people may have different priorities > than you do? I see what you did there. > > If you want a PR for it, I'll file one, but all it's going to contain is > > the contents of this Email. > > My impression is that your emails describe symptoms and contain > some speculation about what the cause might be. I didn't see any > sched traces, so it's unclear (to me) that priorities are actual > the problem. They contain no speculation. Bob Friesenhahn, who has a lot of experience and familiarity with ZFS on Solaris, seemed to know exactly the behaviour I described. Others on FreeBSD have reported the same behaviour as well, just not in that thread circa 2011. Regarding "sched traces", please expand and include instructions. > It's also unclear to me why the dedup and compression issues should > be related. There are lots of dedup performance issues reported for > Solaris as well and I doubt that they can be fixed for FreeBSD without > significantly deviating from the ZFS upstream. What part of Bob's statement did you not understand? Here, let me repeat it verbatim: "Solaris solved the problem by putting the zfs writer threads into a special scheduling class so that they are usually lower priority than normal processing. Before this change, a desktop system would become almost unusable (intermittent loss of keyboard/mouse) while writing lots of data with compression enabled. Some NFS servers encountered severe enough issues that NFS clients reported NFS timeouts." > I'm not saying a PR would be useless, but in my experience PRs > with insufficient information just stay open and if the problem > isn't important enough for you to provide additional information > filing a PR is unlikely to have a great impact: > http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&text=zfs Then someone in the know needs to explain exactly *what* data would help and (more importantly) *how* to go about providing it (i.e. what to enable in the kernel, what commands to issue, etc.). Eidan has repeatedly insisted that PRs are a Good Thing(tm) because they allow for an official way to track issues vs. mailing list threads that start and turn into tumbleweeds (just like the one I've referenced). Without those necessary instructions, in effect what you're asking me to do is "prove" that the problem exists, which I have already done so. You just don't like the data I've provided. Bottom line: people enable compression on an fs, issue large amounts of write I/O to that fs (say hundreds of megabytes, or gigabytes), and start to see the entire system intermittently stalling hard (for multiple seconds at a time). This affects everything from switching VTs on physical console to packets going across SSH. The stalls vary in duration depending on what compression type is used (lzjb vs. gzip-1 -- I cannot even imagine what gzip-9 would be like). I described it as verbosely as I could, including going back and "re-testing" because people felt the "ZFSv28 import might have addressed it" (it did not): http://lists.freebsd.org/pipermail/freebsd-fs/2011-October/012752.html The exact same behaviour happens if dedup is used. There is no relation between compression (the feature) and dedup (the feature), obviously, but the symptom I've described matches Bob's explanation perfectly. If you want to provide the aforementioned instructions, I'll happily follow them. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Feb 9 21:06:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 68149C9D for ; Sat, 9 Feb 2013 21:06:00 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id EF937844 for ; Sat, 9 Feb 2013 21:05:59 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hi8so2014022wib.7 for ; Sat, 09 Feb 2013 13:05:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=nUONOKoE3vbf0gXe8FpYLQOZdLcoIOoS4oVMPCssUrQ=; b=vOsjD0vmdwpSdUKdjBFzriwEfEeeUsyDeX1aE7NjILwtOf2UN8ae/7CNsKjjwKFBF+ 9pZ1Jwwmrr3o85YT2hZ6jCkewXLGHSLMmgEtPw6QF9KpoQdbptT3ZnEDgoCxSGZt6kAD 6R0cFVnyNpF2m6eBIPKrWWUW/fIhqArnvGzrMixnZUsN8xxMWF4zc8Z+qz/8oNiLiQCt l+Y2NBWrf2HD5uxWZnkmGtZFKiyVn+mV3g4QYtoq5DcLbm6JtjR0WaQ6uEZ/3C1deait MvPbp5/h+YrH9EaPSx32TKXNcO/G5jSF4sdkSuk6nA//6LaOA3AnPLD72Rjej56yCkm6 7paA== MIME-Version: 1.0 X-Received: by 10.194.109.102 with SMTP id hr6mr16254708wjb.24.1360443953376; Sat, 09 Feb 2013 13:05:53 -0800 (PST) Received: by 10.180.91.168 with HTTP; Sat, 9 Feb 2013 13:05:53 -0800 (PST) Date: Sun, 10 Feb 2013 01:05:53 +0400 Message-ID: Subject: ath patch from the head From: Michael BlackHeart To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 21:06:00 -0000 Hello there, May be I've missed something or just can't find in the web, but As I see in HEAD there're some movement around ath driver and it seems to me that there's driver for AR93xx, especially AR938x, chip 0030. Is there any patches to stable to check this driver out, 'cause I just can't compile in this driver from the HEAD on 9.stable?