From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:05:49 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0492F106566C;
Sun, 7 Mar 2010 05:05:49 +0000 (UTC)
(envelope-from marcus@marcuscom.com)
Received: from creme-brulee.marcuscom.com
(marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net
[IPv6:2001:470:1f00:ffff::1279])
by mx1.freebsd.org (Postfix) with ESMTP id 51AE98FC17;
Sun, 7 Mar 2010 05:05:48 +0000 (UTC)
Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com
[IPv6:2001:470:1f00:2464::4])
by creme-brulee.marcuscom.com (8.14.4/8.14.4) with ESMTP id
o27566UN077782; Sun, 7 Mar 2010 00:06:06 -0500 (EST)
(envelope-from marcus@marcuscom.com)
From: Joe Marcus Clarke <marcus@marcuscom.com>
To: Weongyo Jeong <weongyo@freebsd.org>
In-Reply-To: <20100306001656.GS1295@weongyo>
References: <1267388668.39569.2410.camel@shumai.marcuscom.com>
<20100301233706.GH1295@weongyo>
<1267505443.35639.9.camel@shumai.marcuscom.com>
<20100303220452.GL1295@weongyo> <4B8EE6B1.6030605@freebsd.org>
<20100303231416.GN1295@weongyo>
<1267679522.5324.20.camel@shumai.marcuscom.com>
<20100305205349.GR1295@weongyo> <4B917B42.1060900@freebsd.org>
<20100306001656.GS1295@weongyo>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-Y+8pNrll7JNQaHmZYowB"
Organization: MarcusCom, Inc.
Date: Sun, 07 Mar 2010 00:05:43 -0500
Message-ID: <1267938343.96436.9.camel@shumai.marcuscom.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,HELO_NO_DOMAIN
autolearn=no version=3.3.0
X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on
creme-brulee.marcuscom.com
Cc: current <current@freebsd.org>
Subject: Re: Problem with new bwn driver on -CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:05:49 -0000
--=-Y+8pNrll7JNQaHmZYowB
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
On Fri, 2010-03-05 at 16:16 -0800, Weongyo Jeong wrote:
> On Fri, Mar 05, 2010 at 04:44:34PM -0500, Joe Marcus Clarke wrote:
> > On 3/5/10 3:53 PM, Weongyo Jeong wrote:
> > > On Thu, Mar 04, 2010 at 12:12:02AM -0500, Joe Marcus Clarke wrote:
> > >> On Wed, 2010-03-03 at 15:14 -0800, Weongyo Jeong wrote:
> > >>>> When it occurs again, I will get you the details and the full dmes=
g. Do
> > >>>> you want a verbose dmesg, or a standard one?
> > >>>
> > >>> I think a standard one is enough. Thank you.
> > >>
> > >> Here you go. This is on -CURRENT from about 30 minutes ago. Thanks=
for
> > >> looking into this.
> > >>
> > >> http://www.marcuscom.com/downloads/salami.dmesg
> > >=20
> > > Thank you for dmesg. It looks using PIO mode is only a way to avoid
> > > this problem.
> > >=20
> > > I looked sources and problems of other Broadcom wireless driver for L=
P
> > > PHY users. They also encounters this issue and are trying to solve
> > > this but no luck and no perfect patch until now.
> > >=20
> > > Recently AFAIK wireless-test git of linux adopted a patch `gracefully
> > > convert DMA to PIO mode' to solve it.
> > >=20
> > > Additionally some guys tolds some success story when they disabled AC=
PI
> > > but it looks it's not a perfect solution.
> > >=20
> > > IIRC you said PIO worked for association with your AP but no further
> > > traffic. However I wonder that this is weird for me because paths of
> > > sending management frames and sending data frames are same. Could yo=
u
> > > please recheck whether PIO mode worked? I'll try to test PIO mode on=
my
> > > environment again.
> >=20
> > I can absolutely confirm PIO mode does NOT work with my card. I tested
> > on a clean power-up. The card associates, but does not pass any
> > traffic. I do not see the same decryption messages that I do with DMA =
mode.
>=20
> OK. I'd like to see some verbose message from bwn(4) after applying
> attached patch with email. Could you please test with it and show me
> dmesg?
>=20
> I tested 3 broadcom card whose revisions are 5 and 9 and it looks it's
> working.
>=20
> I have one LP PHY device, half MiniPCI-E for laptop, but could not test
> with this patch because I could not turn on RF; it's connected with
> desktop using converter MiniPCI-E to PCI-E though normally it looks
> MiniPCI-E devices are turned on using H/W RF switch.
Here are two dmesg outputs. Both were taken with this patch. One is
with PIO mode, and the other is with (working) DMA mode. The names
indicate which is which.
http://www.marcuscom.com/downloads/salami_pio.dmesg
http://www.marcuscom.com/downloads/salami_dma.dmesg
Joe
--=20
PGP Key : http://www.marcuscom.com/pgp.asc
--=-Y+8pNrll7JNQaHmZYowB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEABECAAYFAkuTNCYACgkQb2iPiv4Uz4c8KQCgn+DEXTQcyMygA4P40tcuccCe
ba0AoKrNiDVO89xtsbHOb740QCHD/Ic2
=xVdq
-----END PGP SIGNATURE-----
--=-Y+8pNrll7JNQaHmZYowB--
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:27:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D3B3C106564A
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:27:19 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id B326C8FC12
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:27:19 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.3/8.14.3) with ESMTP id o275RJSf088807;
Sat, 6 Mar 2010 21:27:19 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.3/8.14.3/Submit) id o275RIiJ088762;
Sat, 6 Mar 2010 21:27:18 -0800 (PST) (envelope-from obrien)
Date: Sat, 6 Mar 2010 21:27:18 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Doug Rabson <dfr@rabson.org>
Message-ID: <20100307052718.GA70613@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, Doug Rabson <dfr@rabson.org>,
freebsd-current@freebsd.org
References: <17035.1267786772@critter.freebsd.dk>
<4B90E6B3.9070906@lissyara.su>
<e3e25b34d9476c02d80919fe5d09a5c3@mail.rabson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e3e25b34d9476c02d80919fe5d09a5c3@mail.rabson.org>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: freebsd-current@freebsd.org
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:27:19 -0000
On Fri, Mar 05, 2010 at 11:16:41AM +0000, Doug Rabson wrote:
> I think you misunderstand. Some of us old-timers have been having this
> discussion repeatedly for well over ten years. It always ends up the same
> way - a re-org might make the source tree marginally prettier but the
> consequences for long-term maintenance and supporting downstream
> contributors outweigh any possible benefit. Having the same conversation
> every two years with the same outcome gets annoying.
To be fair - two years ago we were not using a source control system that
understood moves within the repository.
To do this two years ago, we had to make a choice between three poor
paths of how to do CVS moves - repo copy (breaks date-based checkout),
delete-add pairs (looses history), or copy the entire repository move
files and use new repo for new releases and existing repo for old
releases.
Juniper now also uses Subversion - so with sufficient warning and planning,
Juniper could consume a move of the CPU directories moving under arch/.
Juniper also had a CVS based tree reorg 1.5 years go - taking the third
path above.
Please don't use Juniper as an reason to not move forward with this
change.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:29:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 184D0106564A
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:29:50 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id D14F98FC1D
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:29:49 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.3/8.14.3) with ESMTP id o275TnXI092806;
Sat, 6 Mar 2010 21:29:49 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.3/8.14.3/Submit) id o275TncP092805;
Sat, 6 Mar 2010 21:29:49 -0800 (PST) (envelope-from obrien)
Date: Sat, 6 Mar 2010 21:29:49 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Garrett Cooper <yanefbsd@gmail.com>
Message-ID: <20100307052949.GB70613@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>,
freebsd-current@freebsd.org
References: <20100304191311.GE3171@lonesome.com>
<619814.37821.qm@web59102.mail.re1.yahoo.com>
<7d6fde3d1003060128r46403703k8cead7f37f80e83a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7d6fde3d1003060128r46403703k8cead7f37f80e83a@mail.gmail.com>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: freebsd-current@freebsd.org
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:29:50 -0000
On Sat, Mar 06, 2010 at 01:28:24AM -0800, Garrett Cooper wrote:
> FWIW, NetBSD's charter has been to run their OS on a number of
> architectures, not just a primary set of architectures; OpenBSD's
> charter differs -- if we all were NetBSD or OpenBSD, then we'd all be
> using the same thing. But we aren't and that's probably not going to
> change anytime soon [at least not without community backing and a
We aren't? At this point it seems any architecture an be brought into
FreeBSD without regard to critical mass or ability to support it to the
standards of our past. I do believe FreeBSD's character does not include
chasing every embedded platform where there is energy and talent for the
initial port.
--
-- David (obrien@FreeBSD.org)
Q: Because it reverses the logical flow of conversation.
A: Why is top-posting (putting a reply at the top of the message) frowned upon?
Let's not play "Jeopardy-style quoting"
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:37:48 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E96B4106566B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:37:48 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id AC4158FC1B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:37:48 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.3/8.14.3) with ESMTP id o275bmlZ009571;
Sat, 6 Mar 2010 21:37:48 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.3/8.14.3/Submit) id o275blkY009545;
Sat, 6 Mar 2010 21:37:47 -0800 (PST) (envelope-from obrien)
Date: Sat, 6 Mar 2010 21:37:47 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net>
Message-ID: <20100307053747.GC70613@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org,
"Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net>,
freebsd-current@freebsd.org
References: <619814.37821.qm@web59102.mail.re1.yahoo.com>
<alpine.BSF.2.00.1003050912340.5181@fledge.watson.org>
<4B90CF3E.2070508@lissyara.su>
<CF439450-14F1-4628-A012-CF6DD2A50670@rabson.org>
<4B90D557.90504@lissyara.su>
<94301EB5-4D6C-4324-93D1-4D5E8660734B@rabson.org>
<4B90E171.2040808@lissyara.su> <4B90E48A.6030100@stillbilde.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B90E48A.6030100@stillbilde.net>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: freebsd-current@freebsd.org
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:37:49 -0000
On Fri, Mar 05, 2010 at 12:01:30PM +0100, Svein Skogen (Listmail Account) wrote:
> Oh, so because a lot of the programmers behind it receive wages, and the
> project itself won't commit ritual suicide by basically blocking the
> companies using FreeBSD from returning improvements they make to the
> project itself, it should be renamed.
Svein,
A source layout change is the lest of the problems pushing code back from
companies using FreeBSD. When $WORK rearranged our FreeBSD-based tree, we
simply provided a perl script to run over patch files that fixed up the
patch.
sed -e 's,sys/amd64,sys/arch/amd64,g' patchfile > newpatchfile
isn't that hard to do...
The fact that we totally rototilled the bge and em drivers FreeBSD 6.1->6.2
is a MUCH bigger problem to the commercial users of FreeBSD and their
patch sets.
[medium seriousness bug fixes were done by a full MFC of the driver,
vs. just spot fixing the needed changes]
--
-- David (obrien@FreeBSD.org)
Q: Because it reverses the logical flow of conversation.
A: Why is top-posting (putting a reply at the top of the message) frowned upon?
Let's not play "Jeopardy-style quoting"
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:44:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E27A91065670
for <freebsd-current@FreeBSD.org>; Sun, 7 Mar 2010 05:44:24 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id A6A118FC08
for <freebsd-current@FreeBSD.org>; Sun, 7 Mar 2010 05:44:24 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.3/8.14.3) with ESMTP id o275iOd6035872;
Sat, 6 Mar 2010 21:44:24 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.3/Submit) id o275iNJl035870;
Sat, 6 Mar 2010 21:44:23 -0800 (PST) (envelope-from obrien)
Date: Sat, 6 Mar 2010 21:44:23 -0800
From: "David O'Brien" <obrien@FreeBSD.org>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20100307054423.GE70613@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, Robert Watson <rwatson@FreeBSD.org>,
Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@FreeBSD.org,
paradox <ddkprog@yahoo.com>
References: <3620.1267780989@critter.freebsd.dk>
<alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@FreeBSD.org,
paradox <ddkprog@yahoo.com>
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:44:25 -0000
On Fri, Mar 05, 2010 at 09:41:40AM +0000, Robert Watson wrote:
> On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
>> In message <alpine.BSF.2.00.1003050912340.5181@fledge.watson.org>, Robert
>> Watso n writes:
>>> Doing that kind of rearrangement [...] would be a nightmare for anyone
>>> with large [...] patches, so I'd say we could pretty much rule that out
>>> outright.
>>
>> I would say that we should do it occasionally, to encourage these FreeBSD
>> users to contribute as many of their local changes back to the project, as
>> possible :-)
>
> Absolutely -- and rearranging a tree is a good way to invalidate all those
> patches as well :-).
No, not it isn't. Provide a script to convert path's in the diff.
This is what $LARGE_FREEBSD_USER did when it rearranged it source tree.
It was done by creating a copy of the CVS repo and moved files around.
Old releases stayed in the old repo, and new releases done from the new
repo. 'diff | fixpatch | patch -p0' were used to move code between
sandboxes.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 05:56:47 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A16E9106564A
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:56:47 +0000 (UTC)
(envelope-from ehrmann@gmail.com)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182])
by mx1.freebsd.org (Postfix) with ESMTP id 7C4D48FC0C
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 05:56:47 +0000 (UTC)
Received: from exobytes-macbook-pro.local (unknown [64.9.233.134])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.mxes.net (Postfix) with ESMTPSA id 9234D22E1F1
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 00:56:46 -0500 (EST)
Message-ID: <4B934015.8000908@gmail.com>
Date: Sat, 06 Mar 2010 21:56:37 -0800
From: David Ehrmann <ehrmann@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 05:56:47 -0000
Does FreeBSD currently support cryptographic acceleration for AES on the
Core i5 CPU? I searched, but couldn't find anything, and the crypto(4)
manpage only lists these divers in "see also:"
glxsb(4),hifn(4), ipsec(4), padlock(4), safe(4), ubsec(4)
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 06:10:30 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CC5F0106564A
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 06:10:30 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (outp.internet-mail-service.net
[216.240.47.239])
by mx1.freebsd.org (Postfix) with ESMTP id B18DB8FC12
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 06:10:30 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o276AUwG020686; Sat, 6 Mar 2010 22:10:30 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id B74422D6015;
Sat, 6 Mar 2010 22:10:29 -0800 (PST)
Message-ID: <4B934354.4030002@elischer.org>
Date: Sat, 06 Mar 2010 22:10:28 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: David Ehrmann <ehrmann@gmail.com>
References: <4B934015.8000908@gmail.com>
In-Reply-To: <4B934015.8000908@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: freebsd-current@freebsd.org
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 06:10:30 -0000
David Ehrmann wrote:
> Does FreeBSD currently support cryptographic acceleration for AES on the
> Core i5 CPU? I searched, but couldn't find anything, and the crypto(4)
> manpage only lists these divers in "see also:"
no, but if you write a driver for it we will... :-)
(most things in open source happen because someone needs it.)
>
> glxsb(4),hifn(4), ipsec(4), padlock(4), safe(4), ubsec(4)
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 09:44:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from hub.freebsd.org (localhost [127.0.0.1])
by hub.freebsd.org (Postfix) with ESMTP id 9019B106566B;
Sun, 7 Mar 2010 09:44:23 +0000 (UTC)
(envelope-from nork@FreeBSD.org)
Date: Sun, 7 Mar 2010 18:44:22 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: David Ehrmann <ehrmann@gmail.com>, Julian Elischer <julian@elischer.org>
Message-Id: <20100307184422.7007747d.nork@FreeBSD.org>
In-Reply-To: <4B934354.4030002@elischer.org>
References: <4B934015.8000908@gmail.com>
<4B934354.4030002@elischer.org>
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.5; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Norikatsu Shigemura <nork@FreeBSD.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 09:44:24 -0000
Hi Devid and Julian.
On Sat, 06 Mar 2010 22:10:28 -0800
Julian Elischer <julian@elischer.org> wrote:
> David Ehrmann wrote:
> > Does FreeBSD currently support cryptographic acceleration for AES on the
> > Core i5 CPU? I searched, but couldn't find anything, and the crypto(4)
> > manpage only lists these divers in "see also:"
> no, but if you write a driver for it we will... :-)
> (most things in open source happen because someone needs it.)
I found Linux's code: http://lwn.net/Articles/311094/
I think that it looks too easy, maybe, we should implement aesni(4)
like padlock(4).
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 10:07:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C441C1065676;
Sun, 7 Mar 2010 10:07:19 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com
[209.85.160.54])
by mx1.freebsd.org (Postfix) with ESMTP id 97B828FC25;
Sun, 7 Mar 2010 10:07:19 +0000 (UTC)
Received: by pwj1 with SMTP id 1so3619626pwj.13
for <multiple recipients>; Sun, 07 Mar 2010 02:07:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:date:message-id:subject
:from:to:cc:content-type;
bh=7HrPbMQE3yJIUX31kX4mSL2l0zbCBq4OwC7Id+BvQo0=;
b=Of8vKvq+aIcBx5wrVlie2QQIMR1t3bTxIgmJ4NbiHPYKAyaxn8h99DbUO8n69zZbxI
K/epoqJObZ+3apSXGE5jGXGIqCz2F4ovF9gbehQjUVcTEJrf4hGE10KPJgAn1ehrQn+I
2IBszjSAEihYyNv0VQkAqpiD1yC9/5SX8l/UY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:cc:content-type;
b=dPSBZJqrR88s63uT0G6KgasYBegTvICyYox6CM9kW2MSjmzlYjtMd9g5bdfjpq37dJ
L8shmVUqTtc+DNN/WShM4wPdo6NggbUpdZ//l0a+T4iUrJGBSvyvRHE7gl8JeSvdSRyj
FGALz86Pw8exDt7NbyGI6PJ+hRfDMUk3Bov74=
MIME-Version: 1.0
Received: by 10.142.119.20 with SMTP id r20mr2259887wfc.96.1267956438851; Sun,
07 Mar 2010 02:07:18 -0800 (PST)
Date: Sun, 7 Mar 2010 02:07:18 -0800
Message-ID: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Alexander Motin <mav@freebsd.org>, Hans Petter Selasky <hselasky@c2i.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Removing USB keyboard after filesystems synced causes panic with
destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 10:07:19 -0000
Hi Alexander and Hans,
I recently did the following which generated a panic on a
9-CURRENT kernel compiled on the 26th:
1. Executed reboot
2. Removed keyboard.
3. Some time after `All buffers synced\nUptime: ...' was displayed,
the keyboard was registered disconnected.
4. The interrupt was delivered to my twa(4) enabled card and the
kernel panicked, like so:
ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
uhub8: at uhub2, port 1, addr 2 (disconnected)
ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
ukbd0: at uhub8, port 3, addr 3 (disconnected)
uhid0: at uhub8, port 3, addr 3 (disconnected)
panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_intr.c:88
cpuid = 1
KDB: enter: panic
[thread pid 12 tid 100025 ]
Stopped at kdb_enter+0x3d: movq $0,0x40289c(%rip)
db>
I wish I could provide you with more details, but unfortunately I
the USB bus isn't registering the fact that I'm reattaching the
keyboard right now and the box won't reboot automatically :( (didn't
set the right sysctl beforehand to panic automatically). I'll try and
reproduce the issue again, but I was just wondering whether or not you
guys had seen this problem before.
Thanks,
-Garrett
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 10:24:18 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 59048106566C;
Sun, 7 Mar 2010 10:24:18 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com
[209.85.160.54])
by mx1.freebsd.org (Postfix) with ESMTP id 2771F8FC08;
Sun, 7 Mar 2010 10:24:17 +0000 (UTC)
Received: by pwj1 with SMTP id 1so3623688pwj.13
for <multiple recipients>; Sun, 07 Mar 2010 02:24:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=RPyasE1LZGkmN/5FfnHqIvm5jn0wmuyXMLQsw7PNkGs=;
b=ix1ktyIXNvupRcU8LT4+KRIyP6ytp0FoLnrz8eJ5qb8pFgAixmD44Tf0Mv39dHZMao
pdFT/sB8pvq72qDy6ZmZz9t6wFuaaBIyTCNxXtaxcGP2EZ3yl7b8uFlkZzKpLmI8DEbC
qIvNVwf13zAvxtXKVvXtOMhk5KAAw/9uLCGSQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=pE/o3cK1IW/bYl07vOg2b9rbtGs1nRVPzqx47downpGVNFDtfQ5a1auqP/bUVfAVQS
fJmxTXnBDoLuwI8OQ3Linl5by52pX8YcxAMmFh5LZRreAH9q4J96z+1kYaF90JYOCBWQ
/niWH2VerbY0UKgxzIQHdhwijRfXapKn0f1ss=
MIME-Version: 1.0
Received: by 10.142.67.36 with SMTP id p36mr2230261wfa.167.1267957457053; Sun,
07 Mar 2010 02:24:17 -0800 (PST)
In-Reply-To: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
Date: Sun, 7 Mar 2010 02:24:17 -0800
Message-ID: <7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Alexander Motin <mav@freebsd.org>, Hans Petter Selasky <hselasky@c2i.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 10:24:18 -0000
On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> Hi Alexander and Hans,
> =A0 =A0I recently did the following which generated a panic on a
> 9-CURRENT kernel compiled on the 26th:
>
> 1. Executed reboot
> 2. Removed keyboard.
> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
> the keyboard was registered disconnected.
> 4. The interrupt was delivered to my twa(4) enabled card and the
> kernel panicked, like so:
>
> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
> uhub8: at uhub2, port 1, addr 2 (disconnected)
> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
> ukbd0: at uhub8, port 3, addr 3 (disconnected)
> uhid0: at uhub8, port 3, addr 3 (disconnected)
> panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_in=
tr.c:88
>
> cpuid =3D 1
> KDB: enter: panic
> [thread pid 12 tid 100025 ]
> Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%rip)
> db>
>
> =A0 =A0I wish I could provide you with more details, but unfortunately I
> the USB bus isn't registering the fact that I'm reattaching the
> keyboard right now and the box won't reboot automatically :( (didn't
> set the right sysctl beforehand to panic automatically). I'll try and
> reproduce the issue again, but I was just wondering whether or not you
> guys had seen this problem before.
Phew... it's reproducible with that kernel. Here's what I did
exactly (because my original directions were incorrect):
1. Hit power button (for S5).
2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
Kernel panicked on my system again. Now to figure out if it still
exists with a kernel compiled today, and also how to debug it if it
still does exist :/...
Thanks,
-Garrett
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 11:59:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 771B5106566B;
Sun, 7 Mar 2010 11:59:36 +0000 (UTC)
(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 549A48FC17;
Sun, 7 Mar 2010 11:59:36 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
by cyrus.watson.org (Postfix) with ESMTPS id CE53346B51;
Sun, 7 Mar 2010 06:59:35 -0500 (EST)
Date: Sun, 7 Mar 2010 11:59:35 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: current@FreeBSD.org, stable@FreeBSD.org
Message-ID: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc:
Subject: net.inet.tcp.timer_race: does anyone have a non-zero value?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 11:59:36 -0000
Dear all:
I'm embarking on some new network stack locking work, which requires me to
address a number of loose ends in the current model. A few years ago, my
attention was drawn to a largly theoretical race, which had existed in the BSD
code since inception. It is detected and handled in practice, but relies on
type stability of TCP connection data structures, which will need to change in
the future due to on-going virtualization work. I didn't fix it at the time,
but did add a counter so that we could see if it was happening in the field --
that counter, net.inet.tcp.timer_race, indicates whether or not the stack has
detected it happening (and then handled it). This e-mail is to collect the
results of that in-the-field survey.
Please check the results of the following command:
% sysctl net.inet.tcp.timer_race
net.inet.tcp.timer_race: 0
If your system shows a non-zero value, please send me a *private e-mail* with
the output of that command, plus also the output of "sysctl kern.smp",
"uptime", and a brief description of the workload and network interface
configuration. For example: it's a busy 8-core web server with roughly X
connections/second, and that has three em network interfaces used to load
balance from an upstream source. IPSEC is used for management purposes (but
not bulk traffic), and there's a local MySQL database.
I've already seen one non-zero report, but would be interested in knowing a
bit more about the kinds of situations where it's happening so that I can
prioritize fixing it appropriately, but also reason about the frequency at
which it happens so we can select a fix that avoids adding significant
overhead in the common case.
Thanks,
Robert N M Watson
Computer Laboratory
University of Cambridge
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 13:42:38 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D1B29106564A;
Sun, 7 Mar 2010 13:42:38 +0000 (UTC)
(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id ABB148FC16;
Sun, 7 Mar 2010 13:42:38 +0000 (UTC)
Received: from [192.168.2.102] (host86-181-230-35.range86-181.btcentralplus.com
[86.181.230.35])
by cyrus.watson.org (Postfix) with ESMTPSA id C0D9546B03;
Sun, 7 Mar 2010 08:42:37 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: "Robert N. M. Watson" <rwatson@FreeBSD.org>
In-Reply-To: <86d3zgcnvf.fsf@kopusha.onet>
Date: Sun, 7 Mar 2010 13:42:36 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAC4D7A1-AB5A-4842-822C-921200CB2F63@FreeBSD.org>
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
<86d3zgcnvf.fsf@kopusha.onet>
To: Mikolaj Golub <to.my.trociny@gmail.com>
X-Mailer: Apple Mail (2.1077)
Cc: stable@FreeBSD.org, current@FreeBSD.org
Subject: Re: net.inet.tcp.timer_race: does anyone have a non-zero value?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 13:42:38 -0000
On Mar 7, 2010, at 12:33 PM, Mikolaj Golub wrote:
> On Sun, 7 Mar 2010 11:59:35 +0000 (GMT) Robert Watson wrote:
>=20
>> Please check the results of the following command:
>>=20
>> % sysctl net.inet.tcp.timer_race
>> net.inet.tcp.timer_race: 0
>=20
> Are the results for FreeBSD7 look interesting for you? Because =
currently we
> have mostly FreeBSD7.1 hosts in production and I observe nonzero =
values on 8
> hosts (about 15%). I would send more details to you privately if you =
are
> interested.
Yes, 7.x is also of interest, thanks!
Robert=
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 12:59:05 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0CAC2106566C
for <current@freebsd.org>; Sun, 7 Mar 2010 12:59:05 +0000 (UTC)
(envelope-from to.my.trociny@gmail.com)
Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com
[209.85.219.227])
by mx1.freebsd.org (Postfix) with ESMTP id 9179C8FC13
for <current@freebsd.org>; Sun, 7 Mar 2010 12:59:04 +0000 (UTC)
Received: by ewy27 with SMTP id 27so2253564ewy.34
for <current@freebsd.org>; Sun, 07 Mar 2010 04:59:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:to:cc:subject:references
:organization:from:date:in-reply-to:message-id:user-agent
:mime-version:content-type;
bh=kKNIkVOPxR143+A1u2d9tHcanxXLh0RN/+EO8gisn3w=;
b=JWIsyueZ6pBTOBaeQaHYMEBBNv4y3T6BnmSjMBBnDYFc24dgTlpVLbc+JrEfxUztIj
oSEI7xGmeGyr6BzKsGv7G52n6LlH+WJ1rUA1NH9D75ZDKJjfLCNcr024W+7RwkIjV+RP
a/CNDQCBBzC4MxPopq7w45Pov2quNf3exeUew=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=to:cc:subject:references:organization:from:date:in-reply-to
:message-id:user-agent:mime-version:content-type;
b=MmkDl7Yb6XuqVInhEkvNVSL6beRgzy9wYmPi3LjElrFF3SRipaO9gvQ9L4sjRSqICX
w5f2GnRMEaiOxi79RZ+Rj50ehMO3f/0di1uWvcmmm4dParNWDXJ/Cz9w6SCQDtU71Que
elNnJWEvlLLe+JKdF1EpXtk20yijW0i4YlSa4=
Received: by 10.213.1.215 with SMTP id 23mr2100214ebg.52.1267965223741;
Sun, 07 Mar 2010 04:33:43 -0800 (PST)
Received: from localhost ([95.69.173.225])
by mx.google.com with ESMTPS id 14sm1852248ewy.2.2010.03.07.04.33.42
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sun, 07 Mar 2010 04:33:43 -0800 (PST)
To: Robert Watson <rwatson@FreeBSD.org>
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
Organization: TOA Ukraine
From: Mikolaj Golub <to.my.trociny@gmail.com>
Date: Sun, 07 Mar 2010 14:33:40 +0200
In-Reply-To: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org> (Robert
Watson's message of "Sun\, 7 Mar 2010 11\:59\:35 +0000 \(GMT\)")
Message-ID: <86d3zgcnvf.fsf@kopusha.onet>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Sun, 07 Mar 2010 14:09:47 +0000
Cc: stable@FreeBSD.org, current@FreeBSD.org
Subject: Re: net.inet.tcp.timer_race: does anyone have a non-zero value?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 12:59:05 -0000
On Sun, 7 Mar 2010 11:59:35 +0000 (GMT) Robert Watson wrote:
> Please check the results of the following command:
>
> % sysctl net.inet.tcp.timer_race
> net.inet.tcp.timer_race: 0
Are the results for FreeBSD7 look interesting for you? Because currently we
have mostly FreeBSD7.1 hosts in production and I observe nonzero values on 8
hosts (about 15%). I would send more details to you privately if you are
interested.
--
Mikolaj Golub
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 17:05:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 877CE1065673
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:05:58 +0000 (UTC)
(envelope-from quakerdoomer@fmguy.com)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com
[66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5BC078FC23
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:05:58 +0000 (UTC)
Received: from compute1.internal (compute1.internal [10.202.2.41])
by gateway1.messagingengine.com (Postfix) with ESMTP id 2AF23E31D8
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 11:47:37 -0500 (EST)
Received: from web6.messagingengine.com ([10.202.2.215])
by compute1.internal (MEProxy); Sun, 07 Mar 2010 11:47:37 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com;
h=message-id:from:to:mime-version:content-transfer-encoding:content-type:subject:date;
s=smtpout; bh=/9EdZQShT81E1Fo6ME5FFbal9tg=;
b=tFpsTSolQnWnDNDlIR1kzGdee1qD1/OZ+9T7Tz7IHAKn6GR5JUVPuMzSCYEd9ad7yEac77EalgrC4gK/fqLw1Cts4Qe5yqxrFeSQ3xZgL7SZjHpbfi69T3BZVrUnBA3e1k5gjHKj3g11fXIjSZZKtCjXTb3TOmn/cBPLziDlqcI=
Received: by web6.messagingengine.com (Postfix, from userid 99)
id 0D95811054A; Sun, 7 Mar 2010 11:47:37 -0500 (EST)
Message-Id: <1267980457.9617.1363547071@webmail.messagingengine.com>
X-Sasl-Enc: 0CHL+cYnXorWmW5S6pBOvA50k1JEAl4oufukWmUGt6VW 1267980457
From: "Azim" <quakerdoomer@fmguy.com>
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
Date: Sun, 07 Mar 2010 19:47:37 +0300
Subject: Re: Call for tester: VirtualBox 3.1.2 for FreeBSD (take 2)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 17:05:58 -0000
I am using FreeBSD 9.0 CURRENT (201002) as the host OS and I am trying
to run XP64-SP2 as Guest on VirtualBOX version 3.1.2_OSE r56127
I have vboxnet_enable="YES" in /etc/rc.conf and vboxdrv_load="YES" in
/boot/loader.conf for Networking support.
VirtualBox allows me to add an existing vhd but when I click Start the
Guest Windows appears and gets cloded and the status below the Guest OS
name is seen as "Aborted".
Below are the few end lines of the log file
XP64-SP2-2010-03-07-21-48-52.log :
============LOG FILE============
00:00:01.278
00:00:01.278 ********************* End of CFGM dump
**********************
00:00:01.278 MM: cbHyperHeap=0x140000 (1310720)
00:00:01.284
00:00:01.284 !!Assertion Failed!!
00:00:01.284 Expression: paPages[i].Phys != 0 && paPages[i].Phys !=
NIL_RTHCPHYS && !(paPages[i].Phys & PAGE_OFFSET_MASK)
00:00:01.284 Location :
/work/a/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*, const
char*, RTGCPTR64*)
00:00:01.284 i=0x0 Phys=0000000000000000 Heap
============LOG FILE============
Is this a known error ?
Regards,
--
Azim
http://my.opera.com/quakerdoomer
http://solidmecca.co.nr
http://winautopwn.co.nr
--
http://www.fastmail.fm - Accessible with your email software
or over the web
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 17:40:43 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 168761065670
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:40:43 +0000 (UTC)
(envelope-from decke@bluelife.at)
Received: from mail.itac.at (mail.itac.at [91.205.172.9])
by mx1.freebsd.org (Postfix) with ESMTP id 809318FC0C
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:40:42 +0000 (UTC)
Received: from [91.205.172.21] (helo=webmail.bluelife.at)
by mail.itac.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
(Exim 4.63) (envelope-from <decke@bluelife.at>)
id 1NoKT2-0005Fv-Hg; Sun, 07 Mar 2010 18:40:40 +0100
MIME-Version: 1.0
Date: Sun, 07 Mar 2010 18:40:41 +0100
From: Bernhard Froehlich <decke@bluelife.at>
To: Azim <quakerdoomer@fmguy.com>
In-Reply-To: <1267980457.9617.1363547071@webmail.messagingengine.com>
References: <1267980457.9617.1363547071@webmail.messagingengine.com>
Message-ID: <6f52f31a3ca39d57ac0dace7e809644e@bluelife.at>
X-Sender: decke@bluelife.at
User-Agent: RoundCube Webmail/0.3.1
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.8 (/)
X-Spam-Report: Spam detection software, running on the system "mail.itac.at",
has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or
label similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: On Sun, 07 Mar 2010 19:47:37 +0300,
"Azim" <quakerdoomer@fmguy.com>
wrote: > I am using FreeBSD 9.0 CURRENT (201002) as the host OS and I
am
trying > to run XP64-SP2 as Guest on VirtualBOX version 3.1.2_OSE
r56127 >
> I have vboxnet_enable="YES" in /etc/rc.conf and vboxdrv_load="YES" in
>
/boot/loader.conf for Networking support. > > VirtualBox allows me to
add
an existing vhd but when I click Start the > Guest Windows appears and
gets
cloded and the status below the Guest OS > name is seen as "Aborted". >
> Below are the few end lines of the log file >
XP64-SP2-2010-03-07-21-48-52.log
: > > ============LOG FILE============ > 00:00:01.278 > 00:00:01.278
End
of CFGM dump > > 00:00:01.278 MM: cbHyperHeap=0x140000 (1310720) >
00:00:01.284
> 00:00:01.284 !!Assertion Failed!! > 00:00:01.284 Expression:
paPages[i].Phys
!= 0 && paPages[i].Phys != > NIL_RTHCPHYS && !(paPages[i].Phys &
PAGE_OFFSET_MASK) > 00:00:01.284 Location : >
/work/a/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
> int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*,
const > char*,
RTGCPTR64*) > 00:00:01.284 i=0x0 Phys=0000000000000000 Heap >
============LOG
FILE============ > > Is this a known error ? [...]
Content analysis details: (0.8 points, 5.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
-1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
3.4 FH_DATE_PAST_20XX The date is grossly in the future.
-1.1 AWL AWL: From: address is in the auto white-list
Cc: freebsd-current@freebsd.org
Subject: Re: Call for tester: VirtualBox 3.1.2 for FreeBSD (take 2)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 17:40:43 -0000
On Sun, 07 Mar 2010 19:47:37 +0300, "Azim" <quakerdoomer@fmguy.com> wrote:
> I am using FreeBSD 9.0 CURRENT (201002) as the host OS and I am trying
> to run XP64-SP2 as Guest on VirtualBOX version 3.1.2_OSE r56127
>
> I have vboxnet_enable="YES" in /etc/rc.conf and vboxdrv_load="YES" in
> /boot/loader.conf for Networking support.
>
> VirtualBox allows me to add an existing vhd but when I click Start the
> Guest Windows appears and gets cloded and the status below the Guest OS
> name is seen as "Aborted".
>
> Below are the few end lines of the log file
> XP64-SP2-2010-03-07-21-48-52.log :
>
> ============LOG FILE============
> 00:00:01.278
> 00:00:01.278 ********************* End of CFGM dump
> **********************
> 00:00:01.278 MM: cbHyperHeap=0x140000 (1310720)
> 00:00:01.284
> 00:00:01.284 !!Assertion Failed!!
> 00:00:01.284 Expression: paPages[i].Phys != 0 && paPages[i].Phys !=
> NIL_RTHCPHYS && !(paPages[i].Phys & PAGE_OFFSET_MASK)
> 00:00:01.284 Location :
>
/work/a/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
> int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*, const
> char*, RTGCPTR64*)
> 00:00:01.284 i=0x0 Phys=0000000000000000 Heap
> ============LOG FILE============
>
> Is this a known error ?
Yes and it is already investigated. It only happens with current and
stable after beginning of February. A testing patch was send to
freebsd-emulators@ last week.
--
Bernhard Fröhlich
http://www.bluelife.at/
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 17:59:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0BF36106566C
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:59:19 +0000 (UTC)
(envelope-from ehrmann@gmail.com)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182])
by mx1.freebsd.org (Postfix) with ESMTP id D394E8FC1C
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 17:59:18 +0000 (UTC)
Received: from exobytes-macbook-pro.local (unknown [64.9.233.134])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.mxes.net (Postfix) with ESMTPSA id 9896522E253;
Sun, 7 Mar 2010 12:59:16 -0500 (EST)
Message-ID: <4B93E96B.8090002@gmail.com>
Date: Sun, 07 Mar 2010 09:59:07 -0800
From: David Ehrmann <ehrmann@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Norikatsu Shigemura <nork@FreeBSD.org>
References: <4B934015.8000908@gmail.com> <4B934354.4030002@elischer.org>
<20100307184422.7007747d.nork@FreeBSD.org>
In-Reply-To: <20100307184422.7007747d.nork@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Julian Elischer <julian@elischer.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 17:59:19 -0000
On 3/7/10 1:44 AM, Norikatsu Shigemura wrote:
> Hi Devid and Julian.
>
> On Sat, 06 Mar 2010 22:10:28 -0800
> Julian Elischer<julian@elischer.org> wrote:
>
>> David Ehrmann wrote:
>>
>>> Does FreeBSD currently support cryptographic acceleration for AES on the
>>> Core i5 CPU? I searched, but couldn't find anything, and the crypto(4)
>>> manpage only lists these divers in "see also:"
>>>
>> no, but if you write a driver for it we will... :-)
>> (most things in open source happen because someone needs it.)
>>
> I found Linux's code: http://lwn.net/Articles/311094/
> I think that it looks too easy, maybe, we should implement aesni(4)
> like padlock(4).
>
I was thinking that if I did do it, I'd start with padlock as a base.
It looks like there are maybe 6 new opcodes. Maybe we could ask the
contributor of the Linux code (an Intel employee) if he'd be willing to
also release the code under a BSD license.
My problem is that I don't have a Core i5 system--I was asking because
it's an option for my new system--and I'm far from an x86 assembly expert.
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 18:41:29 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E7748106566B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 18:41:28 +0000 (UTC)
(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe05.swip.net [212.247.154.129])
by mx1.freebsd.org (Postfix) with ESMTP id 4DD158FC25
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 18:41:27 +0000 (UTC)
X-Cloudmark-Score: 0.000000 []
X-Cloudmark-Analysis: v=1.0 c=1 a=ByZRc_aOPEEA:10 a=8nJEP1OIZ-IA:10
a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17
a=pGLkceISAAAA:8 a=gMUvyaaGakBy8VsOJykA:9
a=FL1iqKG-iFfMp8kTRAkA:7 a=FpEAc6FofNjtJOPcI4G7oc_FYhcA:4
a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10
Received: from [188.126.201.140] (account mc467741@c2i.net HELO
laptop002.hselasky.homeunix.org)
by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19)
with ESMTPA id 1278656755 for freebsd-current@freebsd.org;
Sun, 07 Mar 2010 19:41:26 +0100
To: freebsd-current@freebsd.org
From: Hans Petter Selasky <hselasky@c2i.net>
X-Face: +~\`s("[*<S!NI[0M*"FaghA8S>|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(
=?iso-8859-1?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=,
=?iso-8859-1?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?=
=?iso-8859-1?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L'
Date: Sun, 7 Mar 2010 19:39:51 +0100
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201003071939.51882.hselasky@c2i.net>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 18:41:29 -0000
On Sunday 07 March 2010 11:46:58 Garrett Cooper wrote:
> On Sun, Mar 7, 2010 at 2:24 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> >> Hi Alexander and Hans,
> >> I recently did the following which generated a panic on a
> >> 9-CURRENT kernel compiled on the 26th:
> >>
> >> 1. Executed reboot
> >> 2. Removed keyboard.
> >> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
> >> the keyboard was registered disconnected.
> >> 4. The interrupt was delivered to my twa(4) enabled card and the
> >> kernel panicked, like so:
> >>
> >> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
> >> uhub8: at uhub2, port 1, addr 2 (disconnected)
> >> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
> >> ukbd0: at uhub8, port 3, addr 3 (disconnected)
> >> uhid0: at uhub8, port 3, addr 3 (disconnected)
> >> panic: mtx_lock_spin() of destroyed mutex @
> >> /usr/src/sys/dev/twa/tw_cl_intr.c:88
> >>
> >> cpuid = 1
> >> KDB: enter: panic
> >> [thread pid 12 tid 100025 ]
> >> Stopped at kdb_enter+0x3d: movq $0,0x40289c(%rip)
> >> db>
> >>
> >> I wish I could provide you with more details, but unfortunately I
> >> the USB bus isn't registering the fact that I'm reattaching the
> >> keyboard right now and the box won't reboot automatically :( (didn't
> >> set the right sysctl beforehand to panic automatically). I'll try and
> >> reproduce the issue again, but I was just wondering whether or not you
> >> guys had seen this problem before.
> >
> > Phew... it's reproducible with that kernel. Here's what I did
> > exactly (because my original directions were incorrect):
> > 1. Hit power button (for S5).
> > 2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
> > Kernel panicked on my system again. Now to figure out if it still
> > exists with a kernel compiled today, and also how to debug it if it
> > still does exist :/...
>
> 1. It still does exist with today's kernel.
> 2. Here's the backtrace:
>
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> panic() at panic+0x17d
> _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x126
> tw_cl_interrupt() at tw_cl_interrupt+0x14c
> twa_pci_intr() at twa_pci_intr+0x11
> intr_event_execute_handlers() at intr_event_execute_handlers+0x67
> ithread_loop() at ithread_loop+0xae
> fork_exit() at fork_exit+0x12a
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xffffff80751d6d30, rbp = 0 ---
> KDB: enter: panic
> [ithread pid 12 tid 100025 ]
> Stopped at kdb_enter+0x3d: movq $0, 0x40289c(%rip)
>
> I'll have to wait until tomorrow to grab a PS/2 keyboard to get more
> helpful info :/...
> Thanks,
> -Garrett
>
Hi,
The reason you get this panic when you unplug the USB keyboard is probably
because the twa interrupt handler is shared with the USB one. It does not look
like a USB problem to me but rather a problem inside the twa_pci_intr() code.
--HPS
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 20:51:23 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 759B01065672;
Sun, 7 Mar 2010 20:51:23 +0000 (UTC)
(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 4E1328FC19;
Sun, 7 Mar 2010 20:51:23 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
by cyrus.watson.org (Postfix) with ESMTPS id E2A2E46B0D;
Sun, 7 Mar 2010 15:51:22 -0500 (EST)
Date: Sun, 7 Mar 2010 20:51:22 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: David O'Brien <obrien@FreeBSD.org>
In-Reply-To: <20100307054423.GE70613@dragon.NUXI.org>
Message-ID: <alpine.BSF.2.00.1003072043560.9729@fledge.watson.org>
References: <3620.1267780989@critter.freebsd.dk>
<alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
<20100307054423.GE70613@dragon.NUXI.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@FreeBSD.org,
paradox <ddkprog@yahoo.com>
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 20:51:23 -0000
On Sat, 6 Mar 2010, David O'Brien wrote:
> No, not it isn't. Provide a script to convert path's in the diff. This is
> what $LARGE_FREEBSD_USER did when it rearranged it source tree.
>
> It was done by creating a copy of the CVS repo and moved files around. Old
> releases stayed in the old repo, and new releases done from the new repo.
> 'diff | fixpatch | patch -p0' were used to move code between sandboxes.
Indeed, this is precisely the problem: rearranging the tree upstream means
that you most likely can't use the revision control system to manage your
local difference set downstream. Instead, you have to manually extract your
local changes, rework them to match arbitrary upstream rearrangement, and
re-apply them as a single changeset creating a discontinuity in your revision
history. This in turn creates problems with annotate, log, backing out
changes prior to the merge, etc. All the reasons we like to use revision
control for significant work.
What you describe may work OK(ish) if you have to do it once every 3-6 years
as a single massive merge and you were planning to do it by hand anyway (CVS
and patches). However, other downstream users (including our own development
branches in Subversion, P4, etc) reasonably expect to be able to use
contemporary tools to manage the merge on a more frequent basis.
As I said before: this isn't a vote not to rearrange things once in a while,
it's instead a caution to say: this has a significant cost beyond "svn mv"
that has to be taken into account when making the decision, so we should only
do it with significant forethought and where there is significant benefit.
Robert N M Watson
Computer Laboratory
University of Cambridge
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 21:50:38 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9658C106566B;
Sun, 7 Mar 2010 21:50:38 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 54ACD8FC14;
Sun, 7 Mar 2010 21:50:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o27LlDU2064062;
Sun, 7 Mar 2010 14:47:13 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Sun, 07 Mar 2010 14:47:36 -0700 (MST)
Message-Id: <20100307.144736.420173476735197890.imp@bsdimp.com>
To: obrien@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100307052949.GB70613@dragon.NUXI.org>
References: <619814.37821.qm@web59102.mail.re1.yahoo.com>
<7d6fde3d1003060128r46403703k8cead7f37f80e83a@mail.gmail.com>
<20100307052949.GB70613@dragon.NUXI.org>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: yanefbsd@gmail.com, freebsd-current@FreeBSD.org
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 21:50:38 -0000
In message: <20100307052949.GB70613@dragon.NUXI.org>
"David O'Brien" <obrien@freebsd.org> writes:
: On Sat, Mar 06, 2010 at 01:28:24AM -0800, Garrett Cooper wrote:
: > FWIW, NetBSD's charter has been to run their OS on a number of
: > architectures, not just a primary set of architectures; OpenBSD's
: > charter differs -- if we all were NetBSD or OpenBSD, then we'd all be
: > using the same thing. But we aren't and that's probably not going to
: > change anytime soon [at least not without community backing and a
:
: We aren't? At this point it seems any architecture an be brought into
: FreeBSD without regard to critical mass or ability to support it to the
: standards of our past. I do believe FreeBSD's character does not include
: chasing every embedded platform where there is energy and talent for the
: initial port.
FreeBSD's charter includes whatever people have the time and energy to
support. This means a lot more embedded platforms that I ever thought
possible because FreeBSD is getting easier to move to new embedded
platforms. This is a good thing, as it brings more people and energy
to the project and makes the base support for those platforms better.
We don't have quite as many problems as the NetBSD/OpenBSD crowd in
this respect. They tend to define a new MACHIINE more often then we
have (or will). The need for sys/arch is less severe here than there
because we don't have 40 different MACHINEs.
Warner
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 21:51:02 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 92F4B1065701;
Sun, 7 Mar 2010 21:51:02 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 393918FC1E;
Sun, 7 Mar 2010 21:51:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o27LgSVm063997;
Sun, 7 Mar 2010 14:42:28 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Sun, 07 Mar 2010 14:42:51 -0700 (MST)
Message-Id: <20100307.144251.1141490504074844420.imp@bsdimp.com>
To: miki.bsd@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <261c29701003040928h7aa70b3fm37611f974e0b9330@mail.gmail.com>
References: <261c29701003021108w1e6e3bbascf17102a3256e339@mail.gmail.com>
<201003030751.45158.jhb@freebsd.org>
<261c29701003040928h7aa70b3fm37611f974e0b9330@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org, weongyo@FreeBSD.org, jhb@FreeBSD.org
Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless
driver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 21:51:02 -0000
In message: <261c29701003040928h7aa70b3fm37611f974e0b9330@mail.gmail.com>
Miki <miki.bsd@gmail.com> writes:
: Rising FIRMWARE_MAX from 30 to 60 did the trick ! thanks !
: Are there any reasons to have such a "low" default value ?
I thought I'd committed this change already :)
Warner
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 21:51:04 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A772C1065703;
Sun, 7 Mar 2010 21:51:04 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 671518FC22;
Sun, 7 Mar 2010 21:51:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o27LmiMH064063;
Sun, 7 Mar 2010 14:48:44 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Sun, 07 Mar 2010 14:49:04 -0700 (MST)
Message-Id: <20100307.144904.1125936742922092260.imp@bsdimp.com>
To: obrien@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100307054423.GE70613@dragon.NUXI.org>
References: <3620.1267780989@critter.freebsd.dk>
<alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
<20100307054423.GE70613@dragon.NUXI.org>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: phk@phk.freebsd.dk, freebsd-current@FreeBSD.org, rwatson@FreeBSD.org,
ddkprog@yahoo.com
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 21:51:04 -0000
In message: <20100307054423.GE70613@dragon.NUXI.org>
"David O'Brien" <obrien@freebsd.org> writes:
: On Fri, Mar 05, 2010 at 09:41:40AM +0000, Robert Watson wrote:
: > On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
: >> In message <alpine.BSF.2.00.1003050912340.5181@fledge.watson.org>, Robert
: >> Watso n writes:
: >>> Doing that kind of rearrangement [...] would be a nightmare for anyone
: >>> with large [...] patches, so I'd say we could pretty much rule that out
: >>> outright.
: >>
: >> I would say that we should do it occasionally, to encourage these FreeBSD
: >> users to contribute as many of their local changes back to the project, as
: >> possible :-)
: >
: > Absolutely -- and rearranging a tree is a good way to invalidate all those
: > patches as well :-).
:
: No, not it isn't. Provide a script to convert path's in the diff.
: This is what $LARGE_FREEBSD_USER did when it rearranged it source tree.
You are joking, right? This would be a nightmare for people that
integrate early and often.
Warner
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 22:15:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3F642106566B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 22:15:25 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Received: from monday.kientzle.com (kientzle.com [66.166.149.50])
by mx1.freebsd.org (Postfix) with ESMTP id 189C78FC08
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 22:15:24 +0000 (UTC)
Received: (from root@localhost)
by monday.kientzle.com (8.14.3/8.14.3) id o27MFYtX098322
for freebsd-current@freebsd.org; Sun, 7 Mar 2010 22:15:34 GMT
(envelope-from kientzle@freebsd.org)
Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2])
by kientzle.com with SMTP id p84xqhe6hxz67p452is3kgetui;
for freebsd-current@freebsd.org;
Sun, 07 Mar 2010 22:15:34 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Message-ID: <4B9425C4.5060309@freebsd.org>
Date: Sun, 07 Mar 2010 14:16:36 -0800
From: Tim Kientzle <kientzle@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16
MIME-Version: 1.0
To: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 22:15:25 -0000
Using ssh and rsync to copy a lot of stuff from my
old desktop to my new laptop. The old desktop is using
a wired connection to an (admittedly crappy) D-Link router,
the new one is using an Atheros wireless connection to the
same router. I periodically see the transfer fail with
the following messages on the wireless side:
Corrupted MAC on input.
Disconnecting: Packet corrupt
rsync: connection unexpectedly closed ... [receiver]
and then the rsync session is dead.
It seems odd that a single corrupt packet would terminate
the TCP connection.
uname: FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 22:57:22 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 17C92106566B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 22:57:22 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com
[209.85.211.181])
by mx1.freebsd.org (Postfix) with ESMTP id B4EBD8FC0C
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 22:57:21 +0000 (UTC)
Received: by ywh11 with SMTP id 11so1491420ywh.13
for <multiple recipients>; Sun, 07 Mar 2010 14:57:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=OnIBMW0z7qamLiw6LxjCZBzdZv/tp+AtzrfSSq3uI5c=;
b=rBEmI3rx1v+qy0B+AcSATBPoK9fbAuTjESZosuaDgDWs436SULhBMKAYDp39Fd+Oaj
NZ3dZ5QeeNPVqASqZosfXxPOHGTiL31BGttTvxQNmryFKJmxRPXRvyTbRyz6ZJYN+eOC
JLJ3emcW+Z7ykbR03zHGaHVKLQsSX9yXWFgKQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=rtX0YEnf7958In/HrROAqSDPlzGtswBNJFqwNouCCXBLXcuyfGbcoJhXacjOqpFTps
jYe+mUp9WTzY5QkBzmvK486yi40BBI8LdOxOycLrllliMErhUw0lXGfijmv27fmpe4UT
6xPI7JYw97AcxtEHZ49mrdYTS5lantEOMSpJM=
Received: by 10.101.45.9 with SMTP id x9mr789683anj.187.1268002640559;
Sun, 07 Mar 2010 14:57:20 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 4sm1566820ywd.58.2010.03.07.14.57.18
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sun, 07 Mar 2010 14:57:19 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Sun, 7 Mar 2010 14:57:17 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Sun, 7 Mar 2010 14:57:17 -0800
To: Tim Kientzle <kientzle@freebsd.org>
Message-ID: <20100307225717.GB1218@michelle.cdnetworks.com>
References: <4B9425C4.5060309@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B9425C4.5060309@freebsd.org>
User-Agent: Mutt/1.4.2.3i
Cc: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Subject: Re: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 22:57:22 -0000
On Sun, Mar 07, 2010 at 02:16:36PM -0800, Tim Kientzle wrote:
> Using ssh and rsync to copy a lot of stuff from my
> old desktop to my new laptop. The old desktop is using
> a wired connection to an (admittedly crappy) D-Link router,
> the new one is using an Atheros wireless connection to the
> same router. I periodically see the transfer fail with
> the following messages on the wireless side:
>
> Corrupted MAC on input.
> Disconnecting: Packet corrupt
I guess this message came from ssh.
> rsync: connection unexpectedly closed ... [receiver]
>
> and then the rsync session is dead.
>
> It seems odd that a single corrupt packet would terminate
> the TCP connection.
>
I think it's default behavior of ssh if it detect malformed packet.
I used to see this forced disconnection of ssh when driver
incorrectly set RX checksum flag OK for corrupted packets which
were caused by hardware bug.
> uname: FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009
From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 23:08:40 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 28A1B106566B
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 23:08:40 +0000 (UTC)
(envelope-from cswiger@mac.com)
Received: from asmtpout028.mac.com (asmtpout028.mac.com [17.148.16.103])
by mx1.freebsd.org (Postfix) with ESMTP id 1132F8FC0A
for <freebsd-current@freebsd.org>; Sun, 7 Mar 2010 23:08:39 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.151.101.134] by asmtp028.mac.com
(Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008;
32bit)) with ESMTPSA id <0KYX0052JPMEDQ90@asmtp028.mac.com>; Sun,
07 Mar 2010 15:08:39 -0800 (PST)
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam
adjust=0
reason=mlx engine=5.0.0-0908210000 definitions=main-1003070221
From: Chuck Swiger <cswiger@mac.com>
In-reply-to: <4B9425C4.5060309@freebsd.org>
Date: Sun, 07 Mar 2010 15:08:38 -0800
Message-id: <07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
References: <4B9425C4.5060309@freebsd.org>
To: Tim Kientzle <kientzle@freebsd.org>
X-Mailer: Apple Mail (2.1077)
Cc: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Subject: Re: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 23:08:40 -0000
Hi, Tim--
On Mar 7, 2010, at 2:16 PM, Tim Kientzle wrote:
[ ... ]
> Corrupted MAC on input.
> Disconnecting: Packet corrupt
> rsync: connection unexpectedly closed ... [receiver]
>
> and then the rsync session is dead.
>
> It seems odd that a single corrupt packet would terminate the TCP connection.
It's not TCP itself which is closing the connection; if a garbage packet as far as TCP or IP layer checksums was seen, it would be dropped and normal resend mechanisms would compensate. However, SSH adds it's own layer of data integrity checking called HMAC, which uses block-based hashes like MD5 or SHA, and is much stronger than the 32-bit CRCs used at TCP/IP layers.
See:
/usr/src/crypto/openssh/packet.c
http://en.wikipedia.org/wiki/HMAC
The implication is that the data is being corrupted before it gets munged into network packets; failing memory is a likely cause, but bugs in the network stack, the NIC driver, or OpenSSL are also lower-order possibilities.
Regards,
--
-Chuck
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 00:02:12 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F1A451065673;
Mon, 8 Mar 2010 00:02:12 +0000 (UTC) (envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id B40BC8FC08;
Mon, 8 Mar 2010 00:02:12 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o28024Y0089676;
Sun, 7 Mar 2010 16:02:04 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o280235A089675;
Sun, 7 Mar 2010 16:02:03 -0800 (PST) (envelope-from obrien)
Date: Sun, 7 Mar 2010 16:02:03 -0800
From: "David O'Brien" <obrien@FreeBSD.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20100308000203.GA70486@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, "M. Warner Losh" <imp@bsdimp.com>,
phk@phk.freebsd.dk, freebsd-current@FreeBSD.org,
rwatson@FreeBSD.org, ddkprog@yahoo.com
References: <3620.1267780989@critter.freebsd.dk>
<alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
<20100307054423.GE70613@dragon.NUXI.org>
<20100307.144904.1125936742922092260.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100307.144904.1125936742922092260.imp@bsdimp.com>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: phk@phk.freebsd.dk, freebsd-current@FreeBSD.org, rwatson@FreeBSD.org,
ddkprog@yahoo.com
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 00:02:13 -0000
On Sun, Mar 07, 2010 at 02:49:04PM -0700, M. Warner Losh wrote:
> In message: <20100307054423.GE70613@dragon.NUXI.org>
> "David O'Brien" <obrien@freebsd.org> writes:
> : On Fri, Mar 05, 2010 at 09:41:40AM +0000, Robert Watson wrote:
> : > On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
> : >> In message <alpine.BSF.2.00.1003050912340.5181@fledge.watson.org>, Robert
> : >> Watso n writes:
> : >>> Doing that kind of rearrangement [...] would be a nightmare for anyone
> : >>> with large [...] patches, so I'd say we could pretty much rule that out
> : >>> outright.
> : >>
> : >> I would say that we should do it occasionally, to encourage these
> : >> FreeBSD users to contribute as many of their local changes back to
> : >> the project, as possible :-)
> : >
> : > Absolutely -- and rearranging a tree is a good way to invalidate
> : > all those patches as well :-).
> :
> : No, not it isn't. Provide a script to convert path's in the diff.
> : This is what $LARGE_FREEBSD_USER did when it rearranged it source tree.
>
> You are joking, right? This would be a nightmare for people that
> integrate early and often.
No I am not joking. I was responding to the point that a large patch
(that is a the output of running '$SCM diff') can be easily modified to
match a new directory layout. Thus patches in GNATS aren't "useless".
I'm not sure what operation you are specifically speaking to . But, if
FreeBSD were to move the CPU directories under 'arch/', at $WORK we would
do:
cd sys
mkdir arch
svn add arch
svn mv {list of dirs} arch
svn ci
and be done with it. Branches would merge that change - get a trivial
tree conflict, resolve it - and move on with life.
I would expect folks working in project branches to do the same.
For merging changes from FreeBSD HEAD to FreeBSD stable - that is
trivial:
cd sys
svn merge -c $GRN ^/head/sys/arch/amd64 amd64
svn ci
Subversion makes this a lot easier than CVS did.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 00:16:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 221C3106566C;
Mon, 8 Mar 2010 00:16:54 +0000 (UTC) (envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id EF5C48FC08;
Mon, 8 Mar 2010 00:16:53 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o280Grqq089846;
Sun, 7 Mar 2010 16:16:53 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o280GqES089845;
Sun, 7 Mar 2010 16:16:52 -0800 (PST) (envelope-from obrien)
Date: Sun, 7 Mar 2010 16:16:52 -0800
From: "David O'Brien" <obrien@FreeBSD.org>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20100308001652.GB70486@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, Robert Watson <rwatson@FreeBSD.org>,
Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@FreeBSD.org,
paradox <ddkprog@yahoo.com>
References: <3620.1267780989@critter.freebsd.dk>
<alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>
<20100307054423.GE70613@dragon.NUXI.org>
<alpine.BSF.2.00.1003072043560.9729@fledge.watson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1003072043560.9729@fledge.watson.org>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@FreeBSD.org,
paradox <ddkprog@yahoo.com>
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 00:16:54 -0000
On Sun, Mar 07, 2010 at 08:51:22PM +0000, Robert Watson wrote:
> On Sat, 6 Mar 2010, David O'Brien wrote:
>> No, not it isn't. Provide a script to convert path's in the diff. This is
>> what $LARGE_FREEBSD_USER did when it rearranged it source tree.
>>
>> It was done by creating a copy of the CVS repo and moved files around. Old
>> releases stayed in the old repo, and new releases done from the new repo.
>> 'diff | fixpatch | patch -p0' were used to move code between sandboxes.
>
> Indeed, this is precisely the problem: rearranging the tree upstream means
> that you most likely can't use the revision control system to manage your
> local difference set downstream.
It does not mean downstream users cannot their revision control system
manage changes - it only means those using CVS cannot easily.
Lets say I'm a 3rd party based on FreeBSD. One "vendor imports" the
FreeBSD sources for what ever version they are based on. When new
FreeBSD version comes out with 'sys/arch/' that would be reflected in
the SCM on that vendor branch. The SCM would track that directories
moved.
Now when the new FreeBSD import was merged into the working sources
branch, the SCM would track that the directory moves would need to
happen there also.
Done deal.
> Instead, you have to manually extract
> your local changes, rework them to match arbitrary upstream rearrangement,
> and re-apply them as a single changeset creating a discontinuity in your
> revision history.
No, you could use the SCM to do it. All modern SCM's that I'm familiar
with track directory moves. Resulting in a situation where there is not
lossage with "log", "blame", etc..
I am speaking as one of the downstream users of FreeBSD - $WORK could
consume such a move - so please don't hold them up as a reason to not
consider moving the CPU directories under arch/.
I know of two 3rd parties with product based on FreeBSD - one uses
subversion, and the other uses Perforce. Granted I don't know what
the others use - but we could query them.
> However, other downstream users (including our
> own development branches in Subversion, P4, etc) reasonably expect to
> be able to use contemporary tools to manage the merge on a more
> frequent basis.
Yes - have you had a bad experience with merging such changes from HEAD
to a project branch in our own subversion tree?
My experience is, given a HEADS UP to a directory move, it is not hard
to handle merges in subversion.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 00:54:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AFF311065670;
Mon, 8 Mar 2010 00:54:54 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 5003B8FC17;
Mon, 8 Mar 2010 00:54:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o280mhAt065321;
Sun, 7 Mar 2010 17:48:44 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Sun, 07 Mar 2010 17:49:06 -0700 (MST)
Message-Id: <20100307.174906.122313684076180456.imp@bsdimp.com>
To: obrien@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100308000203.GA70486@dragon.NUXI.org>
References: <20100307054423.GE70613@dragon.NUXI.org>
<20100307.144904.1125936742922092260.imp@bsdimp.com>
<20100308000203.GA70486@dragon.NUXI.org>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: phk@phk.freebsd.dk, freebsd-current@FreeBSD.org, rwatson@FreeBSD.org,
ddkprog@yahoo.com
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 00:54:54 -0000
In message: <20100308000203.GA70486@dragon.NUXI.org>
"David O'Brien" <obrien@FreeBSD.org> writes:
: On Sun, Mar 07, 2010 at 02:49:04PM -0700, M. Warner Losh wrote:
: > In message: <20100307054423.GE70613@dragon.NUXI.org>
: > "David O'Brien" <obrien@freebsd.org> writes:
: > : On Fri, Mar 05, 2010 at 09:41:40AM +0000, Robert Watson wrote:
: > : > On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
: > : >> In message <alpine.BSF.2.00.1003050912340.5181@fledge.watson.org>, Robert
: > : >> Watso n writes:
: > : >>> Doing that kind of rearrangement [...] would be a nightmare for anyone
: > : >>> with large [...] patches, so I'd say we could pretty much rule that out
: > : >>> outright.
: > : >>
: > : >> I would say that we should do it occasionally, to encourage these
: > : >> FreeBSD users to contribute as many of their local changes back to
: > : >> the project, as possible :-)
: > : >
: > : > Absolutely -- and rearranging a tree is a good way to invalidate
: > : > all those patches as well :-).
: > :
: > : No, not it isn't. Provide a script to convert path's in the diff.
: > : This is what $LARGE_FREEBSD_USER did when it rearranged it source tree.
: >
: > You are joking, right? This would be a nightmare for people that
: > integrate early and often.
:
:
: No I am not joking. I was responding to the point that a large patch
: (that is a the output of running '$SCM diff') can be easily modified to
: match a new directory layout. Thus patches in GNATS aren't "useless".
It seems like it would be a nightmare for anybody tracking the system
on a regular basis.
: I'm not sure what operation you are specifically speaking to . But, if
: FreeBSD were to move the CPU directories under 'arch/', at $WORK we would
: do:
:
: cd sys
: mkdir arch
: svn add arch
: svn mv {list of dirs} arch
: svn ci
:
: and be done with it. Branches would merge that change - get a trivial
: tree conflict, resolve it - and move on with life.
And everybody who was tracking FreeBSD with their own changes would
have to scramble. It wouldn't be trivial by any stretch of the
imagination. The project is much larger than svn, and svn doesn't
lend itself well to having external agents track it.
: I would expect folks working in project branches to do the same.
:
: For merging changes from FreeBSD HEAD to FreeBSD stable - that is
: trivial:
:
: cd sys
: svn merge -c $GRN ^/head/sys/arch/amd64 amd64
: svn ci
:
: Subversion makes this a lot easier than CVS did.
Just because the task is doable with svn, where it was impossible with
CVS doesn't mean there wouldn't be a significant amount of pain to the
folks using FreeBSD. It is cool that Juniper kinda has it worked out,
but even there I'm skeptical about your claims. Especially since
Juniper imports source rarely, where as other firms do it more often,
and there'd be more pain for them.
Warner
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 01:56:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 061541065670
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 01:56:57 +0000 (UTC)
(envelope-from dave@dogwood.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
[209.85.212.54])
by mx1.freebsd.org (Postfix) with ESMTP id 9D8E68FC08
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 01:56:56 +0000 (UTC)
Received: by vws14 with SMTP id 14so2829167vws.13
for <multiple recipients>; Sun, 07 Mar 2010 17:56:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.127.4 with SMTP id e4mr2534952vcs.79.1268013415516; Sun,
07 Mar 2010 17:56:55 -0800 (PST)
In-Reply-To: <07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
References: <4B9425C4.5060309@freebsd.org>
<07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
Date: Sun, 7 Mar 2010 15:56:55 -1000
Message-ID: <4ab61a81003071756p1d5b273coa59cb6c075cb56fb@mail.gmail.com>
From: David Cornejo <dave@dogwood.com>
To: Chuck Swiger <cswiger@mac.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Tim Kientzle <kientzle@freebsd.org>,
"freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject: Re: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 01:56:57 -0000
On Sun, Mar 7, 2010 at 1:08 PM, Chuck Swiger <cswiger@mac.com> wrote:
> Hi, Tim--
>
> On Mar 7, 2010, at 2:16 PM, Tim Kientzle wrote:
> [ ... ]
> > Corrupted MAC on input.
> > Disconnecting: Packet corrupt
> > rsync: connection unexpectedly closed ... [receiver]
> >
> > and then the rsync session is dead.
> >
> > It seems odd that a single corrupt packet would terminate the TCP
> connection.
>
> It's not TCP itself which is closing the connection; if a garbage packet as
> far as TCP or IP layer checksums was seen, it would be dropped and normal
> resend mechanisms would compensate. However, SSH adds it's own layer of
> data integrity checking called HMAC, which uses block-based hashes like MD5
> or SHA, and is much stronger than the 32-bit CRCs used at TCP/IP layers.
>
> See:
>
> /usr/src/crypto/openssh/packet.c
> http://en.wikipedia.org/wiki/HMAC
>
> The implication is that the data is being corrupted before it gets munged
> into network packets; failing memory is a likely cause, but bugs in the
> network stack, the NIC driver, or OpenSSL are also lower-order
> possibilities.
>
> Regards,
> --
> -Chuck
>
>
I have seen this same symptom many times with PCEngines ALIX boards but on
the vr interfaces. It seems to come and go as I update kernels and worse
yet, it seems to vary by board - have four boards all purchased at the same
time a couple of years ago and some seem more prone to it than others. All
have worked and failed at one time or another.
I had, at one point, thought it to be related to power problems, because a
high-power mini-PCI WiFi card seemed to exacerbate the problem, but removing
the card made no difference, and the problem cleared up with an update and
recompile of my source tree.
It's a very disconcerting problem because FTP'ed files were being silently
corrupted, so it's not just an SSH problem either.
dave c
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 06:16:02 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 87174106566B
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 06:16:02 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com
[74.125.83.182])
by mx1.freebsd.org (Postfix) with ESMTP id 4A2788FC08
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 06:16:02 +0000 (UTC)
Received: by pvg3 with SMTP id 3so1911535pvg.13
for <multiple recipients>; Sun, 07 Mar 2010 22:16:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=sNhVmNYOoDHWjqUexhqv+8Tw1EC/VxQk/d+smvU1oNk=;
b=pwDz0YHWRSs5P3QluDXPKOLYJXD9Z0eqkrkfJniVw0XVjzLEeECKEvOfAnVYwTIiVG
c0FuyKUSoR8bXlQUPMgONMFkSPOHSbNRyvk8f7kXDRr2+k4Z3cEa7LClfBRhUQofZwwQ
toMIi1jls8UHdCP9brpQbOtZIfkhIPIo6kcmM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=Sq1WG+jLL1swviFFPQwwrP+H6RL4BfBeYakZN/BeF2gbmDRseIICqxmQ5Y1MG1vnlk
wETQKrnOf5xdjH96D1PTGrtJFg4fdFyLJ10/f8pkJ9o2iUCnoX0q8PGLOWIzW48/ZepI
+31ODk2YQw4HM9kQAvgILgtzURcWm+2Dm0IvY=
MIME-Version: 1.0
Received: by 10.142.3.28 with SMTP id 28mr2948724wfc.106.1268028961658; Sun,
07 Mar 2010 22:16:01 -0800 (PST)
In-Reply-To: <20100307.174906.122313684076180456.imp@bsdimp.com>
References: <20100307054423.GE70613@dragon.NUXI.org>
<20100307.144904.1125936742922092260.imp@bsdimp.com>
<20100308000203.GA70486@dragon.NUXI.org>
<20100307.174906.122313684076180456.imp@bsdimp.com>
Date: Sun, 7 Mar 2010 22:16:01 -0800
Message-ID: <7d6fde3d1003072216s65b814f1s3ab04d2a6d626e57@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: "M. Warner Losh" <imp@bsdimp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: phk@phk.freebsd.dk, freebsd-current@freebsd.org, rwatson@freebsd.org,
ddkprog@yahoo.com
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 06:16:02 -0000
On Sun, Mar 7, 2010 at 4:49 PM, M. Warner Losh <imp@bsdimp.com> wrote:
> In message: <20100308000203.GA70486@dragon.NUXI.org>
> =A0 =A0 =A0 =A0 =A0 =A0"David O'Brien" <obrien@FreeBSD.org> writes:
> : On Sun, Mar 07, 2010 at 02:49:04PM -0700, M. Warner Losh wrote:
> : > In message: <20100307054423.GE70613@dragon.NUXI.org>
> : > =A0 =A0 =A0 =A0 =A0 =A0 "David O'Brien" <obrien@freebsd.org> writes:
> : > : On Fri, Mar 05, 2010 at 09:41:40AM +0000, Robert Watson wrote:
> : > : > On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
> : > : >> In message <alpine.BSF.2.00.1003050912340.5181@fledge.watson.org=
>, Robert
> : > : >> Watso n writes:
> : > : >>> Doing that kind of rearrangement [...] would be a nightmare for=
anyone
> : > : >>> with large [...] patches, so I'd say we could pretty much rule =
that out
> : > : >>> outright.
> : > : >>
> : > : >> I would say that we should do it occasionally, to encourage thes=
e
> : > : >> FreeBSD users to contribute as many of their local changes back =
to
> : > : >> the project, as possible :-)
> : > : >
> : > : > Absolutely -- and rearranging a tree is a good way to invalidate
> : > : > all those patches as well :-).
> : > :
> : > : No, not it isn't. =A0Provide a script to convert path's in the diff=
.
> : > : This is what $LARGE_FREEBSD_USER did when it rearranged it source t=
ree.
> : >
> : > You are joking, right? =A0This would be a nightmare for people that
> : > integrate early and often.
> :
> :
> : No I am not joking. =A0I was responding to the point that a large patch
> : (that is a the output of running '$SCM diff') can be easily modified to
> : match a new directory layout. =A0Thus patches in GNATS aren't "useless"=
.
>
> It seems like it would be a nightmare for anybody tracking the system
> on a regular basis.
>
> : I'm not sure what operation you are specifically speaking to . But, if
> : FreeBSD were to move the CPU directories under 'arch/', at $WORK we wou=
ld
> : do:
> :
> : =A0 =A0 cd sys
> : =A0 =A0 mkdir arch
> : =A0 =A0 svn add arch
> : =A0 =A0 svn mv {list of dirs} arch
> : =A0 =A0 svn ci
> :
> : and be done with it. =A0Branches would merge that change - get a trivia=
l
> : tree conflict, resolve it - and move on with life.
>
> And everybody who was tracking FreeBSD with their own changes would
> have to scramble. =A0It wouldn't be trivial by any stretch of the
> imagination. =A0The project is much larger than svn, and svn doesn't
> lend itself well to having external agents track it.
>
> : I would expect folks working in project branches to do the same.
> :
> : For merging changes from FreeBSD HEAD to FreeBSD stable - that is
> : trivial:
> :
> : =A0 =A0 cd sys
> : =A0 =A0 svn merge -c $GRN ^/head/sys/arch/amd64 amd64
> : =A0 =A0 svn ci
> :
> : Subversion makes this a lot easier than CVS did.
>
> Just because the task is doable with svn, where it was impossible with
> CVS doesn't mean there wouldn't be a significant amount of pain to the
> folks using FreeBSD. =A0It is cool that Juniper kinda has it worked out,
> but even there I'm skeptical about your claims. =A0Especially since
> Juniper imports source rarely, where as other firms do it more often,
> and there'd be more pain for them.
There are also folks (like Ironport) who don't import changes back
into the tree as often, and I'd rather not put more of a crimp on
folks' time for getting things back in because of this forced CVS ->
SVN upgrade (I'd rather convince others gradually over time to switch
to svn as opposed to using CVS).
As long as CVS continues to be in base, some folks will prefer it
over SVN (not saying because it's better, but just because it's there
and it's established).
Thanks,
-Garrett
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 07:48:03 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 50C3A106564A;
Mon, 8 Mar 2010 07:48:03 +0000 (UTC)
(envelope-from luigi@onelab2.iet.unipi.it)
Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238])
by mx1.freebsd.org (Postfix) with ESMTP id 12F2E8FC0C;
Mon, 8 Mar 2010 07:48:02 +0000 (UTC)
Received: by onelab2.iet.unipi.it (Postfix, from userid 275)
id D455C730A1; Mon, 8 Mar 2010 08:57:33 +0100 (CET)
Date: Mon, 8 Mar 2010 08:57:33 +0100
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: Chuck Swiger <cswiger@mac.com>, Tim Kientzle <kientzle@freebsd.org>,
"'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Message-ID: <20100308075733.GA24644@onelab2.iet.unipi.it>
References: <4B9425C4.5060309@freebsd.org>
<07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
User-Agent: Mutt/1.4.2.3i
Cc:
Subject: Re: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 07:48:03 -0000
On Sun, Mar 07, 2010 at 03:08:38PM -0800, Chuck Swiger wrote:
> Hi, Tim--
>
> On Mar 7, 2010, at 2:16 PM, Tim Kientzle wrote:
> [ ... ]
> > Corrupted MAC on input.
> > Disconnecting: Packet corrupt
> > rsync: connection unexpectedly closed ... [receiver]
> >
> > and then the rsync session is dead.
> >
> > It seems odd that a single corrupt packet would terminate the TCP connection.
>
> It's not TCP itself which is closing the connection; if a garbage packet as far as TCP or IP layer checksums was seen, it would be dropped and normal resend mechanisms would compensate. However, SSH adds it's own layer of data integrity checking called HMAC, which uses block-based hashes like MD5 or SHA, and is much stronger than the 32-bit CRCs used at TCP/IP layers.
>
> See:
>
> /usr/src/crypto/openssh/packet.c
> http://en.wikipedia.org/wiki/HMAC
>
> The implication is that the data is being corrupted before it gets munged into network packets; failing memory is a likely cause, but bugs in the network stack, the NIC driver, or OpenSSL are also lower-order possibilities.
long ago, with the 'iwi' driver, there was the following problem
leading the the sae problem you are seeing:
the driver was doing WEP in software, and wrote back the result to
the original mbuf (actually, cluster). As a result, the first
transmission of a segment was correct, but in case a rxmt, data
would be encrypted twice, and the remote ssh end detected the garbage
and dropped the connection. This was fixed with Sam's help
around early 2007 if i remember well.
An easy way to see if it is a similar problem is use ipfw to drop
some packets e.g.
ipfw add 100 prob 0.1 deny tcp out xmit wi0 // use your interface name
cheers
luigi
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 08:44:09 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D7193106564A;
Mon, 8 Mar 2010 08:44:09 +0000 (UTC)
(envelope-from c.jayachandran@gmail.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
[209.85.160.182])
by mx1.freebsd.org (Postfix) with ESMTP id 7ABEF8FC0C;
Mon, 8 Mar 2010 08:44:09 +0000 (UTC)
Received: by gyg8 with SMTP id 8so1325482gyg.13
for <multiple recipients>; Mon, 08 Mar 2010 00:44:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:to:cc:subject
:message-id:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent;
bh=xZGYM8h5FFYZlsCO3CFyt2lTrHnQCAMADHji4LlUvDE=;
b=Li1w61tg1d4WdMGx8c6dJOy+MJDMXfacOOoomencAUDCyGkhh1FQrOUrHJRBvfPyYC
4xmZERkw/J+7LiVafGypnXp+H2tueXffMWiSkKOx/Tkt7yTWB5fzdUyq1NT/6Ex5NZDi
nlLbBt8X4dntYd77gIu+Okdc7w/76C6mlJ89M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=F4DnOOLnnmf/QCdZX2TplsfprB0brDwDHtyCKyrPeNwCeNlUgFTIqJAcN560Qa69ZE
q0m2K052WMujo80NCshO7O8+3eHnU7F9bX/DPII0GquxO+m/0LR+cXeDe9ptuFWqWtbj
UCdObBWMAIz80HunvpBldRTyDBAAGRPOAM+n8=
Received: by 10.90.16.12 with SMTP id 12mr2666389agp.46.1268037848599;
Mon, 08 Mar 2010 00:44:08 -0800 (PST)
Received: from jayachandranc@netlogicmicro.com ([203.92.57.132])
by mx.google.com with ESMTPS id 5sm1368080yxd.71.2010.03.08.00.44.06
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 08 Mar 2010 00:44:08 -0800 (PST)
Date: Mon, 8 Mar 2010 14:17:17 +0530
From: "Jayachandran C." <c.jayachandran@gmail.com>
To: sobomax@freebsd.org
Message-ID: <4b94b8d8.c501be0a.4ce5.760a@mx.google.com>
References: <98a59be81003040504x6e97fbaeqeb10f8ea7bedb7b9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <98a59be81003040504x6e97fbaeqeb10f8ea7bedb7b9@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 08:44:09 -0000
On Thu, Mar 04, 2010 at 06:34:03PM +0530, C. Jayachandran wrote:
> I'm testing this on the mips platform, but I think there is an issue
> with change that made sectorsize int64_t, because the ioctl
> DIOCGSECTORSIZE used to read sector size seems to take u_int. This
> quick change fixes it for me (sample patch - may be whitespace
> damaged).
I'm trying this one more time, since the issue is still unresolved.
newfs(8) broke for big-endian systems since revision 204654. This change
made sectorsize variable int64_t, and now it cannot be passed to the ioctl
DIOCGSECTORSIZE.
The patch below (updated from the previous one) fixes it, please review and
apply if correct.
Thanks,
JC.
Index: sbin/newfs/newfs.c
===================================================================
--- sbin/newfs/newfs.c (revision 204701)
+++ sbin/newfs/newfs.c (working copy)
@@ -132,6 +132,7 @@
char *cp, *special;
intmax_t reserved;
int ch, i, rval;
+ u_int tsecsize;
off_t mediasize;
char part_name; /* partition name, default to full disk */
@@ -327,9 +328,12 @@
mediasize = st.st_size;
/* set fssize from the partition */
} else {
- if (sectorsize == 0)
- if (ioctl(disk.d_fd, DIOCGSECTORSIZE, §orsize) == -1)
+ if (sectorsize == 0) {
+ if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) == -1)
sectorsize = 0; /* back out on error for safety */
+ else
+ sectorsize = tsecsize;
+ }
if (sectorsize && ioctl(disk.d_fd, DIOCGMEDIASIZE, &mediasize) != -1)
getfssize(&fssize, special, mediasize / sectorsize, reserved);
}
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 10:27:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5FBB2106566B
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:27:00 +0000 (UTC)
(envelope-from bofh@redwerk.com)
Received: from redwerk.com (redwerk.com [89.105.196.9])
by mx1.freebsd.org (Postfix) with ESMTP id 212508FC15
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:26:59 +0000 (UTC)
Received: from 94-248-60-220.dynamic.peoplenet.ua ([94.248.60.220]
helo=localhost) by redwerk.com with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.71) (envelope-from <bofh@redwerk.com>) id 1NoaAr-0003Gc-6S
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 11:26:58 +0100
Received: from bofh by localhost with local (Exim 4.71 (FreeBSD))
(envelope-from <bofh@redwerk.com>) id 1NoaD8-0001W8-N2
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 12:29:18 +0200
Date: Mon, 8 Mar 2010 12:29:18 +0200
From: Eugeny N Dzhurinsky <bofh@redwerk.com>
To: freebsd-current@freebsd.org
Message-ID: <20100308102918.GA5485@localhost>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 10:27:00 -0000
--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hello, all!
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unread=
able (pending) sectors
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrec=
table sectors
smartctl did really show that something is wrong with my HDD, but still no
remaps - just read errors.
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)=
LBA_of_first_error
# 1 Extended offline Completed: read failure 60% 1198 =
222342559
# 2 Extended offline Completed: read failure 60% 1187 =
222342557
# 3 Extended offline Completed: read failure 60% 1180 =
222342559
# 4 Short offline Completed without error 00% 1178 =
-
# 5 Extended offline Aborted by host 90% 1178 =
-
and
ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN=
_FAILED RAW_VALUE
=2E..
Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always =
- 0
=2E..
Now can I find out which file owns the LBAs 222342557 and 222342559 ? How d=
o I
force remapping of these sectors? I assume that I have to write something
directly to the sectors?
Thank you all in advance!
--=20
Eugene N Dzhurinsky
--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAkuU0X0ACgkQy/i/DoZLbHz23wCgt1iEP0b9e94p9FEJLpJklbE6
Ce0Anje9o2riegYJgPrF/0JI7L5sDLEI
=SyaP
-----END PGP SIGNATURE-----
--SLDf9lqlvOQaIe6s--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 10:31:31 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2EBC5106564A
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:31:31 +0000 (UTC)
(envelope-from mavbsd@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id A9E828FC12
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:31:30 +0000 (UTC)
Received: by fxm23 with SMTP id 23so4604117fxm.3
for <freebsd-current@freebsd.org>; Mon, 08 Mar 2010 02:31:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:message-id:date:from
:user-agent:mime-version:to:subject:references:in-reply-to
:content-type:content-transfer-encoding;
bh=q8Dxk+JCgxrEKH2UbSYRSer8xisZ23rGx6mlFq47Hjc=;
b=t4QBFQtVTbqMd/WB6mTvNAD+qVp4QH8AXhA8whpJE76+39g1RiftmU8Lfw/hCs1yWU
oM2PUZauOinu44LS2/RWIGNv49qSppPs8wKFzVLShwilWyRCtCv2pIsweoVgG3xH62H+
tsta/l5q6s/H8carViRxYpEN44eEZCSwZJasg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:message-id:date:from:user-agent:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
b=IZqMPAvpLNSlUiT5I754sTGT1MY5ejdmR8wnd22PRxMY/kLznG7BIfkuNbpyAaF7DT
lga1qryUPALpEATmBu5dh9hAGIERaC6HzSj/jlPgQ//Tu+hOVWI0SoMHl6+N7LG3eaW/
ByoNBdtxvxX49A2xCSk+1hk0EjDDD1jjxfU+g=
Received: by 10.223.16.66 with SMTP id n2mr5351287faa.83.1268044287930;
Mon, 08 Mar 2010 02:31:27 -0800 (PST)
Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226])
by mx.google.com with ESMTPS id 16sm2836333fxm.11.2010.03.08.02.31.26
(version=SSLv3 cipher=RC4-MD5); Mon, 08 Mar 2010 02:31:27 -0800 (PST)
Sender: Alexander Motin <mavbsd@gmail.com>
Message-ID: <4B94D1FC.1050407@FreeBSD.org>
Date: Mon, 08 Mar 2010 12:31:24 +0200
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20091212)
MIME-Version: 1.0
To: Eugeny N Dzhurinsky <bofh@redwerk.com>,
FreeBSD-Current <freebsd-current@freebsd.org>
References: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
In-Reply-To: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 10:31:31 -0000
Eugeny N Dzhurinsky wrote:
> Recently I've started to see the following logs in messages:
>
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable (pending) sectors
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrectable sectors
>
> smartctl did really show that something is wrong with my HDD, but still no
> remaps - just read errors.
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed: read failure 60% 1198 222342559
> # 2 Extended offline Completed: read failure 60% 1187 222342557
> # 3 Extended offline Completed: read failure 60% 1180 222342559
> # 4 Short offline Completed without error 00% 1178 -
> # 5 Extended offline Aborted by host 90% 1178 -
>
> and
>
> ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> ...
> Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> ...
>
> Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do I
> force remapping of these sectors? I assume that I have to write something
> directly to the sectors?
You may try to overwrite these sectors with dd. It should trigger sector
reallocation. To be sure, you may read them before and after the write.
--
Alexander Motin
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 10:51:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3ED10106566B
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:51:24 +0000 (UTC)
(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
by mx1.freebsd.org (Postfix) with ESMTP id 032B88FC12
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:51:23 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
by phk.freebsd.dk (Postfix) with ESMTP id 8CE716415;
Mon, 8 Mar 2010 10:51:22 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id o28ApMbQ049423;
Mon, 8 Mar 2010 10:51:22 GMT (envelope-from phk@critter.freebsd.dk)
To: Eugeny N Dzhurinsky <bofh@redwerk.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 08 Mar 2010 12:29:18 +0200."
<20100308102918.GA5485@localhost>
Date: Mon, 08 Mar 2010 10:51:22 +0000
Message-ID: <49422.1268045482@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 10:51:24 -0000
In message <20100308102918.GA5485@localhost>, Eugeny N Dzhurinsky writes:
>Now can I find out which file owns the LBAs 222342557 and 222342559 ?
>How do I force remapping of these sectors? I assume that I have to write
>something directly to the sectors?
I would suggest you boot single-user and run
mdmfs -s 1m md /tmp
recoverdisk -w /tmp/_.wl /dev/ad4 /dev/ad4
That will find out how many bad sectors you have and try to recover
the contents of them if possible, leave it running as long as you
care for.
If you interrupt it, the /tmp/_.wl file will contain a list of areas
not yet successfully read/written.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 10:52:46 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0D042106566C
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:52:46 +0000 (UTC)
(envelope-from bofh@redwerk.com)
Received: from redwerk.com (redwerk.com [89.105.196.9])
by mx1.freebsd.org (Postfix) with ESMTP id C070B8FC12
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:52:45 +0000 (UTC)
Received: from [192.168.250.5] (helo=office.redwerk.com)
by redwerk.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71)
(envelope-from <bofh@redwerk.com>) id 1NoaZo-0003qM-Fo
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 11:52:44 +0100
Received: from bofh by office.redwerk.com with local (Exim 4.71 (FreeBSD))
(envelope-from <bofh@redwerk.com>) id 1NoaZn-0008CT-JF
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 12:52:43 +0200
Date: Mon, 8 Mar 2010 12:52:43 +0200
From: Eugene Dzhurinsky <bofh@redwerk.com>
To: freebsd-current@freebsd.org
Message-ID: <20100308105243.GA31468@office.redwerk.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
<4B94D1FC.1050407@FreeBSD.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS"
Content-Disposition: inline
In-Reply-To: <4B94D1FC.1050407@FreeBSD.org>
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 10:52:46 -0000
--qMm9M+Fa2AknHoGS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 08, 2010 at 12:31:24PM +0200, Alexander Motin wrote:
> You may try to overwrite these sectors with dd. It should trigger sector
> reallocation. To be sure, you may read them before and after the write.
dd if=3D/dev/ad4 of=3D/dev/null skip=3D222342559 bs=3D512 count=3D1
dd: /dev/ad4: Input/output error
0+0 records in
0+0 records out
0 bytes transferred in 2.351940 secs (0 bytes/sec)
dd if=3D/dev/zero of=3D/dev/ad4 seek=3D222342559 bs=3D512 count=3D1
dd: /dev/ad4: Operation not permitted
Should I do it in single mode?
--=20
Eugene N Dzhurinsky
--qMm9M+Fa2AknHoGS
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuU1vcACgkQy/i/DoZLbHwtkACgldhBvzuBxnkdRXzRoVj/a0pz
/REAn0i28RXhUpvGkomxFsPd+lg+b3yB
=5DBK
-----END PGP SIGNATURE-----
--qMm9M+Fa2AknHoGS--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 10:54:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 26BBE106568A
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:54:54 +0000 (UTC)
(envelope-from bofh@redwerk.com)
Received: from redwerk.com (redwerk.com [89.105.196.9])
by mx1.freebsd.org (Postfix) with ESMTP id DA77D8FC1C
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 10:54:53 +0000 (UTC)
Received: from [192.168.250.5] (helo=office.redwerk.com)
by redwerk.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71)
(envelope-from <bofh@redwerk.com>) id 1Noabs-0003u3-Ui
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 11:54:53 +0100
Received: from bofh by office.redwerk.com with local (Exim 4.71 (FreeBSD))
(envelope-from <bofh@redwerk.com>) id 1Noabs-0008Ci-9m
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 12:54:52 +0200
Date: Mon, 8 Mar 2010 12:54:52 +0200
From: Eugene Dzhurinsky <bofh@redwerk.com>
To: freebsd-current@freebsd.org
Message-ID: <20100308105452.GB31468@office.redwerk.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <20100308102918.GA5485@localhost>
<49422.1268045482@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK"
Content-Disposition: inline
In-Reply-To: <49422.1268045482@critter.freebsd.dk>
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 10:54:54 -0000
--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 08, 2010 at 10:51:22AM +0000, Poul-Henning Kamp wrote:
> I would suggest you boot single-user and run
>=20
> mdmfs -s 1m md /tmp
> recoverdisk -w /tmp/_.wl /dev/ad4 /dev/ad4
>=20
> That will find out how many bad sectors you have and try to recover
> the contents of them if possible, leave it running as long as you
> care for.
>=20
> If you interrupt it, the /tmp/_.wl file will contain a list of areas
> not yet successfully read/written.
Well, I just want to force IDE drive to remap things :)
--=20
Eugene N Dzhurinsky
--/NkBOFFp2J2Af1nK
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuU13oACgkQy/i/DoZLbHwu4ACgis5jSPBkQSMFvAZuu86Zy+S1
ZVwAoJbIMeBxY64V1/lAVyTXxtHRM3zn
=CnWk
-----END PGP SIGNATURE-----
--/NkBOFFp2J2Af1nK--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:09:21 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EE4B11065687
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:09:21 +0000 (UTC)
(envelope-from bofh@redwerk.com)
Received: from redwerk.com (redwerk.com [89.105.196.9])
by mx1.freebsd.org (Postfix) with ESMTP id ACED18FC08
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:09:21 +0000 (UTC)
Received: from [192.168.250.5] (helo=office.redwerk.com)
by redwerk.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71)
(envelope-from <bofh@redwerk.com>) id 1Noaps-0004Gu-CT
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 12:09:20 +0100
Received: from bofh by office.redwerk.com with local (Exim 4.71 (FreeBSD))
(envelope-from <bofh@redwerk.com>) id 1Noapr-0008Ed-Nf
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 13:09:19 +0200
Date: Mon, 8 Mar 2010 13:09:19 +0200
From: Eugene Dzhurinsky <bofh@redwerk.com>
To: freebsd-current@freebsd.org
Message-ID: <20100308110919.GA31573@office.redwerk.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
<4B94D1FC.1050407@FreeBSD.org>
<20100308105243.GA31468@office.redwerk.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO"
Content-Disposition: inline
In-Reply-To: <20100308105243.GA31468@office.redwerk.com>
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:09:22 -0000
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 08, 2010 at 12:52:43PM +0200, Eugene Dzhurinsky wrote:
> dd if=3D/dev/ad4 of=3D/dev/null skip=3D222342559 bs=3D512 count=3D1
> dd: /dev/ad4: Input/output error
> 0+0 records in
> 0+0 records out
> 0 bytes transferred in 2.351940 secs (0 bytes/sec)
>=20
> dd if=3D/dev/zero of=3D/dev/ad4 seek=3D222342559 bs=3D512 count=3D1
> dd: /dev/ad4: Operation not permitted
>=20
> Should I do it in single mode?
sysctl kern.geom.debugflags=3D0x10
Did the trick, I was able to write directly to the sector, and now it seems=
to
work well. No remaps recorded thus, but no errors so far.
Thanks a lot!
--=20
Eugene N Dzhurinsky
--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuU2t4ACgkQy/i/DoZLbHx5cQCePP0nFs1PcYXZ3x90VqcRyXD+
UkgAnjaifz6wNJGKMuGwnQYUR6qRyXJJ
=WBic
-----END PGP SIGNATURE-----
--M9NhX3UHpAaciwkO--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:21:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0BB4D1065674
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:21:50 +0000 (UTC)
(envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
by mx1.freebsd.org (Postfix) with ESMTP id BEDFF8FC14
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:21:49 +0000 (UTC)
Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1])
by elsa.codelab.cz (Postfix) with ESMTP id AC37219E02D;
Mon, 8 Mar 2010 12:21:47 +0100 (CET)
Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by elsa.codelab.cz (Postfix) with ESMTPSA id 62B7019E02A;
Mon, 8 Mar 2010 12:21:45 +0100 (CET)
Message-ID: <4B94DDC8.5080008@quip.cz>
Date: Mon, 08 Mar 2010 12:21:44 +0100
From: Miroslav Lachman <000.fbsd@quip.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3
MIME-Version: 1.0
To: Eugeny N Dzhurinsky <bofh@redwerk.com>
References: <20100308102918.GA5485@localhost>
In-Reply-To: <20100308102918.GA5485@localhost>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:21:50 -0000
Eugeny N Dzhurinsky wrote:
> Hello, all!
>
> Recently I've started to see the following logs in messages:
>
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable (pending) sectors
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrectable sectors
>
> smartctl did really show that something is wrong with my HDD, but still no
> remaps - just read errors.
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed: read failure 60% 1198 222342559
> # 2 Extended offline Completed: read failure 60% 1187 222342557
> # 3 Extended offline Completed: read failure 60% 1180 222342559
> # 4 Short offline Completed without error 00% 1178 -
> # 5 Extended offline Aborted by host 90% 1178 -
>
> and
>
> ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> ...
> Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> ...
>
> Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do I
> force remapping of these sectors? I assume that I have to write something
> directly to the sectors?
We have this problem from time to time on bunch of machines. As we are
using gmirror, the easiest way is to force re-synchronization (rewrite)
of the whole drive. The problem is when there are Pending unreadable
sectors on both drives - it ends up with read error and some file(s) are
corrupted, but there is no easy way (on FreeBSD) to find what file.
I tried it in the past with fsdb / findblk, but it does not work as I
expect or I do not fully understand the needed calculations with slices
+ partitions offsets / LBAs and right meaning of the term "block". It
seems there are several meaning in different contexts.
It would be nice if somebody with enough FS / GEOM knowledge can write
some HowTo or shell script to do the calculations and operations to find
file containing bad sector(s) and put it in FAQ, Handbook, or Wiki.
Miroslav Lachman
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:47:05 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 38CC3106566B
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:47:05 +0000 (UTC)
(envelope-from morganw@chemikals.org)
Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2])
by mx1.freebsd.org (Postfix) with ESMTP id 933BF8FC0C
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:47:04 +0000 (UTC)
Received: from volatile.chemikals.org (adsl-67-211-10.shv.bellsouth.net
[98.67.211.10])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by warped.bluecherry.net (Postfix) with ESMTPSA id D2EB3806DF7C;
Mon, 8 Mar 2010 05:47:02 -0600 (CST)
Received: from localhost (morganw@localhost [127.0.0.1])
by volatile.chemikals.org (8.14.4/8.14.4) with ESMTP id o28Bkv3m066839;
Mon, 8 Mar 2010 05:46:57 -0600 (CST)
(envelope-from morganw@chemikals.org)
Date: Mon, 8 Mar 2010 05:46:57 -0600 (CST)
From: Wes Morgan <morganw@chemikals.org>
X-X-Sender: morganw@volatile
To: Miroslav Lachman <000.fbsd@quip.cz>
In-Reply-To: <4B94DDC8.5080008@quip.cz>
Message-ID: <alpine.BSF.2.00.1003080540130.1526@ibyngvyr>
References: <20100308102918.GA5485@localhost> <4B94DDC8.5080008@quip.cz>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: clamav-milter 0.95.3 at warped
X-Virus-Status: Clean
Cc: Eugeny N Dzhurinsky <bofh@redwerk.com>, freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:47:05 -0000
On Mon, 8 Mar 2010, Miroslav Lachman wrote:
> Eugeny N Dzhurinsky wrote:
> > Hello, all!
> >
> > Recently I've started to see the following logs in messages:
> >
> > Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently
> > unreadable (pending) sectors
> > Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline
> > uncorrectable sectors
> >
> > smartctl did really show that something is wrong with my HDD, but still no
> > remaps - just read errors.
> >
> > SMART Self-test log structure revision number 1
> > Num Test_Description Status Remaining LifeTime(hours)
> > LBA_of_first_error
> > # 1 Extended offline Completed: read failure 60% 1198
> > 222342559
> > # 2 Extended offline Completed: read failure 60% 1187
> > 222342557
> > # 3 Extended offline Completed: read failure 60% 1180
> > 222342559
> > # 4 Short offline Completed without error 00% 1178
> > -
> > # 5 Extended offline Aborted by host 90% 1178
> > -
> >
> > and
> >
> > ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> > WHEN_FAILED RAW_VALUE
> > ...
> > Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always -
> > 0
> > ...
> >
> > Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do
> > I
> > force remapping of these sectors? I assume that I have to write something
> > directly to the sectors?
>
> We have this problem from time to time on bunch of machines. As we are using
> gmirror, the easiest way is to force re-synchronization (rewrite) of the whole
> drive. The problem is when there are Pending unreadable sectors on both drives
> - it ends up with read error and some file(s) are corrupted, but there is no
> easy way (on FreeBSD) to find what file.
*cough* zfs *cough*
I believe this kind of silent corruption is precisely what zfs was
designed to prevent. Even though you do have a mirror, how do you know
which copy is the correct one? If one drive re-allocates the sector
silently, what is the recovery method? If gmirror synchronizes, how do you
make sure that the *good* copy is the one synchronized? You'll notice it
eventually if you see it in a garbled file, but how does the filesystem
handle it?
> I tried it in the past with fsdb / findblk, but it does not work as I expect
> or I do not fully understand the needed calculations with slices + partitions
> offsets / LBAs and right meaning of the term "block". It seems there are
> several meaning in different contexts.
>
> It would be nice if somebody with enough FS / GEOM knowledge can write some
> HowTo or shell script to do the calculations and operations to find file
> containing bad sector(s) and put it in FAQ, Handbook, or Wiki.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:50:55 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D4BD61065673
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:50:55 +0000 (UTC)
(envelope-from bofh@redwerk.com)
Received: from redwerk.com (redwerk.com [89.105.196.9])
by mx1.freebsd.org (Postfix) with ESMTP id 950EB8FC2D
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:50:55 +0000 (UTC)
Received: from [192.168.250.5] (helo=office.redwerk.com)
by redwerk.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71)
(envelope-from <bofh@redwerk.com>) id 1NobU5-0005Nk-HG
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 12:50:53 +0100
Received: from bofh by office.redwerk.com with local (Exim 4.71 (FreeBSD))
(envelope-from <bofh@redwerk.com>) id 1NobU4-0008Ir-NN
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 13:50:52 +0200
Date: Mon, 8 Mar 2010 13:50:52 +0200
From: Eugene Dzhurinsky <bofh@redwerk.com>
To: freebsd-current@freebsd.org
Message-ID: <20100308115052.GA31896@office.redwerk.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <20100308102918.GA5485@localhost>
<4B94DDC8.5080008@quip.cz>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J"
Content-Disposition: inline
In-Reply-To: <4B94DDC8.5080008@quip.cz>
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:50:55 -0000
--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 08, 2010 at 12:21:44PM +0100, Miroslav Lachman wrote:
> Eugeny N Dzhurinsky wrote:
> We have this problem from time to time on bunch of machines. As we are=20
> using gmirror, the easiest way is to force re-synchronization (rewrite)=
=20
> of the whole drive. The problem is when there are Pending unreadable=20
> sectors on both drives - it ends up with read error and some file(s) are=
=20
> corrupted, but there is no easy way (on FreeBSD) to find what file.
>=20
> I tried it in the past with fsdb / findblk, but it does not work as I=20
> expect or I do not fully understand the needed calculations with slices=
=20
> + partitions offsets / LBAs and right meaning of the term "block". It=20
> seems there are several meaning in different contexts.
>=20
> It would be nice if somebody with enough FS / GEOM knowledge can write=20
> some HowTo or shell script to do the calculations and operations to find=
=20
> file containing bad sector(s) and put it in FAQ, Handbook, or Wiki.
Miroslav, thank you for the suggestion - but I am not using gmirror, that H=
DD
is the one on my laptop. However suggestions about using dd to write someth=
ing
into bad block to force IDE controller do it's service stuff about remapping
seems did the trick. And I was able to not calculate LBA but use it as block
offset, which seemed to be correct way :)
--=20
Eugene N Dzhurinsky
--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuU5JsACgkQy/i/DoZLbHyZZQCeNTq1Lxky1KI+QOrgWoPuoDLC
8N4AoJ/4Fo/wjD9cgEKumhkQvGRz0OzA
=+5ID
-----END PGP SIGNATURE-----
--VbJkn9YxBvnuCH5J--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:56:46 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9BC21106564A;
Mon, 8 Mar 2010 11:56:46 +0000 (UTC)
(envelope-from gary.jennejohn@freenet.de)
Received: from mout3.freenet.de (mout3.freenet.de [IPv6:2001:748:100:40::2:5])
by mx1.freebsd.org (Postfix) with ESMTP id 34B4A8FC15;
Mon, 8 Mar 2010 11:56:46 +0000 (UTC)
Received: from [195.4.92.22] (helo=12.mx.freenet.de)
by mout3.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
25) (Exim 4.72 #1)
id 1NobZk-0001RY-ME; Mon, 08 Mar 2010 12:56:44 +0100
Received: from p57ae2534.dip0.t-ipconnect.de ([87.174.37.52]:28190
helo=ernst.jennejohn.org)
by 12.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
25) (Exim 4.72 #2)
id 1NobZk-00011a-EE; Mon, 08 Mar 2010 12:56:44 +0100
Date: Mon, 8 Mar 2010 12:56:43 +0100
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: "Jayachandran C." <c.jayachandran@gmail.com>
Message-ID: <20100308125643.1ac0be0f@ernst.jennejohn.org>
In-Reply-To: <4b94b8d8.c501be0a.4ce5.760a@mx.google.com>
References: <98a59be81003040504x6e97fbaeqeb10f8ea7bedb7b9@mail.gmail.com>
<4b94b8d8.c501be0a.4ce5.760a@mx.google.com>
X-Mailer: Claws Mail 3.7.4 (GTK+ 2.16.2; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:56:46 -0000
On Mon, 8 Mar 2010 14:17:17 +0530
"Jayachandran C." <c.jayachandran@gmail.com> wrote:
> On Thu, Mar 04, 2010 at 06:34:03PM +0530, C. Jayachandran wrote:
> > I'm testing this on the mips platform, but I think there is an issue
> > with change that made sectorsize int64_t, because the ioctl
> > DIOCGSECTORSIZE used to read sector size seems to take u_int. This
> > quick change fixes it for me (sample patch - may be whitespace
> > damaged).
>
> I'm trying this one more time, since the issue is still unresolved.
>
> newfs(8) broke for big-endian systems since revision 204654. This change
> made sectorsize variable int64_t, and now it cannot be passed to the ioctl
> DIOCGSECTORSIZE.
>
> The patch below (updated from the previous one) fixes it, please review and
> apply if correct.
>
> Thanks,
> JC.
>
> Index: sbin/newfs/newfs.c
> ===================================================================
> --- sbin/newfs/newfs.c (revision 204701)
> +++ sbin/newfs/newfs.c (working copy)
> @@ -132,6 +132,7 @@
> char *cp, *special;
> intmax_t reserved;
> int ch, i, rval;
> + u_int tsecsize;
> off_t mediasize;
> char part_name; /* partition name, default to full disk */
>
> @@ -327,9 +328,12 @@
> mediasize = st.st_size;
> /* set fssize from the partition */
> } else {
> - if (sectorsize == 0)
> - if (ioctl(disk.d_fd, DIOCGSECTORSIZE, §orsize) == -1)
> + if (sectorsize == 0) {
> + if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) == -1)
> sectorsize = 0; /* back out on error for safety */
> + else
> + sectorsize = tsecsize;
> + }
> if (sectorsize && ioctl(disk.d_fd, DIOCGMEDIASIZE, &mediasize) != -1)
> getfssize(&fssize, special, mediasize / sectorsize, reserved);
> }
>
I can't say whether this is correct, but the logic could definitely be
simplified like this, since sectorsize is known to be 0 already:
if (sectorsize == 0)
if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) >= 0)
sectorsize = tsecsize;
---
Gary Jennejohn
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 11:58:41 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 64E151065677
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:58:41 +0000 (UTC)
(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
by mx1.freebsd.org (Postfix) with ESMTP id 2864A8FC1C
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 11:58:40 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
by phk.freebsd.dk (Postfix) with ESMTP id C314C643A;
Mon, 8 Mar 2010 11:58:39 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id o28BwdKo051126;
Mon, 8 Mar 2010 11:58:39 GMT (envelope-from phk@critter.freebsd.dk)
To: gary.jennejohn@freenet.de
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 08 Mar 2010 12:56:43 +0100."
<20100308125643.1ac0be0f@ernst.jennejohn.org>
Date: Mon, 08 Mar 2010 11:58:39 +0000
Message-ID: <51125.1268049519@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
"Jayachandran C." <c.jayachandran@gmail.com>
Subject: Re: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 11:58:41 -0000
In message <20100308125643.1ac0be0f@ernst.jennejohn.org>, Gary Jennejohn writes
:
>On Mon, 8 Mar 2010 14:17:17 +0530
>> I'm trying this one more time, since the issue is still unresolved.
>>
>> newfs(8) broke for big-endian systems since revision 204654. This change
>> made sectorsize variable int64_t, and now it cannot be passed to the ioctl
>> DIOCGSECTORSIZE.
This patch is correct, DIOCGSECTORSIZE takes an unsigned argument, see
<sys/disk.h>:
#define DIOCGSECTORSIZE _IOR('d', 128, u_int)
/*-
* Get the sectorsize of the device in bytes. The sectorsize is the
* smallest unit of data which can be transfered from this device.
* Usually this is a power of two but it may not be. (ie: CDROM audio)
*/
>I can't say whether this is correct, but the logic could definitely be
>simplified like this, since sectorsize is known to be 0 already:
> if (sectorsize == 0)
> if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) >= 0)
> sectorsize = tsecsize;
I'm not sure that is a valid assumption.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 03:29:31 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 188351065670
for <current@freebsd.org>; Mon, 8 Mar 2010 03:29:31 +0000 (UTC)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170])
by mx1.freebsd.org (Postfix) with ESMTP id C25CC8FC17
for <current@freebsd.org>; Mon, 8 Mar 2010 03:29:30 +0000 (UTC)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
by hergotha.csail.mit.edu (8.14.3/8.14.3) with ESMTP id o283TQV8011057;
Sun, 7 Mar 2010 22:29:26 -0500 (EST)
(envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
by hergotha.csail.mit.edu (8.14.3/8.14.3/Submit) id o283TQIc011056;
Sun, 7 Mar 2010 22:29:26 -0500 (EST) (envelope-from wollman)
Date: Sun, 7 Mar 2010 22:29:26 -0500 (EST)
From: Garrett Wollman <wollman@hergotha.csail.mit.edu>
Message-Id: <201003080329.o283TQIc011056@hergotha.csail.mit.edu>
To: imp@bsdimp.com
In-Reply-To: <20100307.144736.420173476735197890.imp@bsdimp.com>
References: <619814.37821.qm@web59102.mail.re1.yahoo.com>
<7d6fde3d1003060128r46403703k8cead7f37f80e83a@mail.gmail.com>
<20100307052949.GB70613@dragon.NUXI.org>
Organization:
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3
(hergotha.csail.mit.edu [127.0.0.1]);
Sun, 07 Mar 2010 22:29:27 -0500 (EST)
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED
autolearn=disabled version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
hergotha.csail.mit.edu
X-Mailman-Approved-At: Mon, 08 Mar 2010 12:13:29 +0000
Cc: current@freebsd.org
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 03:29:31 -0000
In article <20100307.144736.420173476735197890.imp@bsdimp.com>, Warner
Losh <imp@bsdimp.com> writes:
>We don't have quite as many problems as the NetBSD/OpenBSD crowd in
>this respect. They tend to define a new MACHIINE more often then we
>have (or will). The need for sys/arch is less severe here than there
>because we don't have 40 different MACHINEs.
Even if we did, I cannot think of any compelling reason to make such a
change (and I don't recall one ever being brought up in our entire
history). If we had forty architecture directories in /sys, so what?
Why should it matter to anyone?
If we were talking about 100 architectures, I might feel differently,
but in this universe, we have, what? eight? And there are how many
architectures currently in mass production? This whole discussion is
ridiculous.
-GAWollman
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 12:16:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C8737106566C
for <current@freebsd.org>; Mon, 8 Mar 2010 12:16:54 +0000 (UTC)
(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
by mx1.freebsd.org (Postfix) with ESMTP id 8D30B8FC1E
for <current@freebsd.org>; Mon, 8 Mar 2010 12:16:54 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
by phk.freebsd.dk (Postfix) with ESMTP id 68D3E63EA;
Mon, 8 Mar 2010 12:16:53 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id o28CGqDf051216;
Mon, 8 Mar 2010 12:16:52 GMT (envelope-from phk@critter.freebsd.dk)
To: Garrett Wollman <wollman@hergotha.csail.mit.edu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 07 Mar 2010 22:29:26 EST."
<201003080329.o283TQIc011056@hergotha.csail.mit.edu>
Date: Mon, 08 Mar 2010 12:16:52 +0000
Message-ID: <51215.1268050612@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: current@freebsd.org, imp@bsdimp.com
Subject: Re: propose: all arch move into a separate dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 12:16:54 -0000
In message <201003080329.o283TQIc011056@hergotha.csail.mit.edu>, Garrett Wollma
n writes:
>If we were talking about 100 architectures, I might feel differently,
>but in this universe, we have, what? eight? And there are how many
>architectures currently in mass production? This whole discussion is
>ridiculous.
Actually, that conclusion is probably premature.
The System-On-Chip concept is boiling over these days, and everybody
and his brother are designing CPUs for themselves.
100 is unlikely, but 8 may be 20 in two years time, depending on
the way the wind blows.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 12:24:13 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A40B11065670
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 12:24:13 +0000 (UTC)
(envelope-from gary.jennejohn@freenet.de)
Received: from mout5.freenet.de (mout5.freenet.de [IPv6:2001:748:100:40::2:7])
by mx1.freebsd.org (Postfix) with ESMTP id 3D7C78FC14
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 12:24:13 +0000 (UTC)
Received: from [195.4.92.18] (helo=8.mx.freenet.de)
by mout5.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
25) (Exim 4.72 #1)
id 1Noc0J-0004tI-KA; Mon, 08 Mar 2010 13:24:11 +0100
Received: from p57ae2534.dip0.t-ipconnect.de ([87.174.37.52]:44753
helo=ernst.jennejohn.org)
by 8.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25)
(Exim 4.72 #2) id 1Noc0J-00085W-CT; Mon, 08 Mar 2010 13:24:11 +0100
Date: Mon, 8 Mar 2010 13:24:10 +0100
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Message-ID: <20100308132410.0d99e0f3@ernst.jennejohn.org>
In-Reply-To: <51125.1268049519@critter.freebsd.dk>
References: <20100308125643.1ac0be0f@ernst.jennejohn.org>
<51125.1268049519@critter.freebsd.dk>
X-Mailer: Claws Mail 3.7.4 (GTK+ 2.16.2; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
"Jayachandran C." <c.jayachandran@gmail.com>
Subject: Re: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 12:24:13 -0000
On Mon, 08 Mar 2010 11:58:39 +0000
"Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote:
> In message <20100308125643.1ac0be0f@ernst.jennejohn.org>, Gary Jennejohn writes
> :
> >On Mon, 8 Mar 2010 14:17:17 +0530
>
> >> I'm trying this one more time, since the issue is still unresolved.
> >>
> >> newfs(8) broke for big-endian systems since revision 204654. This change
> >> made sectorsize variable int64_t, and now it cannot be passed to the ioctl
> >> DIOCGSECTORSIZE.
>
> This patch is correct, DIOCGSECTORSIZE takes an unsigned argument, see
> <sys/disk.h>:
>
> #define DIOCGSECTORSIZE _IOR('d', 128, u_int)
> /*-
> * Get the sectorsize of the device in bytes. The sectorsize is the
> * smallest unit of data which can be transfered from this device.
> * Usually this is a power of two but it may not be. (ie: CDROM audio)
> */
>
>
> >I can't say whether this is correct, but the logic could definitely be
> >simplified like this, since sectorsize is known to be 0 already:
> > if (sectorsize == 0)
> > if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) >= 0)
> > sectorsize = tsecsize;
>
> I'm not sure that is a valid assumption.
>
I disagree, but there's no reason to get into a bike-shed painting contest :) The
original patch is OK the way it is.
---
Gary Jennejohn
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 12:34:56 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 70EAB106564A
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 12:34:56 +0000 (UTC)
(envelope-from c.jayachandran@gmail.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
[209.85.160.182])
by mx1.freebsd.org (Postfix) with ESMTP id 28BD58FC17
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 12:34:55 +0000 (UTC)
Received: by gyg8 with SMTP id 8so1408560gyg.13
for <freebsd-current@freebsd.org>; Mon, 08 Mar 2010 04:34:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:to:cc:subject
:message-id:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent;
bh=UIMZZO4ueUW7QIE2hiVI4XB0YeRSFAUd4OerXr3IAyA=;
b=qR/yoo/JHgiCaLjNs7GpN9Nxf0DAZm2GxRhZNzli5+phU+0+SSAjY9ntl3+y/WlWAT
TIdUW+aoUr4JxjV/wmleNDhFWe3WHFAUPtgImQ7sQlX8VWE4RJIv/IM+vlkk27ShwIzf
YYs2Er3usQFLQZU65lq59mMxe/BbZq/SqHPXE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=cEXvTF/chZsU+hEvHb9mxY5JrqKad/r87TkoK4Tyq5SdY481nQWVBRNbx45FbwbcTd
pUrJbvDvPBKp0zZImt2655CXgdnrLAHRcD+al4NEMqTg7kMtEZMvx6x9fmOapLwKsQA2
5u8mvZrog+aqNDvD30EqZBhNXE5GcdmCBOXyY=
Received: by 10.150.169.1 with SMTP id r1mr4130681ybe.216.1268051695223;
Mon, 08 Mar 2010 04:34:55 -0800 (PST)
Received: from jayachandranc@netlogicmicro.com ([203.92.57.132])
by mx.google.com with ESMTPS id 21sm439840yxe.57.2010.03.08.04.34.52
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 08 Mar 2010 04:34:54 -0800 (PST)
Date: Mon, 8 Mar 2010 18:08:05 +0530
From: "Jayachandran C." <c.jayachandran@gmail.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <4b94eeee.1502be0a.2a7b.2a5c@mx.google.com>
References: <20100308125643.1ac0be0f@ernst.jennejohn.org>
<51125.1268049519@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51125.1268049519@critter.freebsd.dk>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 12:34:56 -0000
On Mon, Mar 08, 2010 at 11:58:39AM +0000, Poul-Henning Kamp wrote:
> In message <20100308125643.1ac0be0f@ernst.jennejohn.org>, Gary Jennejohn writes
> :
> >On Mon, 8 Mar 2010 14:17:17 +0530
>
> >> I'm trying this one more time, since the issue is still unresolved.
> >>
> >> newfs(8) broke for big-endian systems since revision 204654. This change
> >> made sectorsize variable int64_t, and now it cannot be passed to the ioctl
> >> DIOCGSECTORSIZE.
>
> This patch is correct, DIOCGSECTORSIZE takes an unsigned argument, see
> <sys/disk.h>:
>
> #define DIOCGSECTORSIZE _IOR('d', 128, u_int)
> /*-
> * Get the sectorsize of the device in bytes. The sectorsize is the
> * smallest unit of data which can be transfered from this device.
> * Usually this is a power of two but it may not be. (ie: CDROM audio)
> */
>
>
> >I can't say whether this is correct, but the logic could definitely be
> >simplified like this, since sectorsize is known to be 0 already:
> > if (sectorsize == 0)
> > if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) >= 0)
> > sectorsize = tsecsize;
>
> I'm not sure that is a valid assumption.
I think I missed this one. Probably we could do ioctl(...) != -1 and be equivalent.
Thanks for the comments. New patch below.
Index: sbin/newfs/newfs.c
===================================================================
--- sbin/newfs/newfs.c (revision 204858)
+++ sbin/newfs/newfs.c (working copy)
@@ -132,6 +132,7 @@
char *cp, *special;
intmax_t reserved;
int ch, i, rval;
+ u_int tsecsize;
off_t mediasize;
char part_name; /* partition name, default to full disk */
@@ -328,8 +329,8 @@
/* set fssize from the partition */
} else {
if (sectorsize == 0)
- if (ioctl(disk.d_fd, DIOCGSECTORSIZE, §orsize) == -1)
- sectorsize = 0; /* back out on error for safety */
+ if (ioctl(disk.d_fd, DIOCGSECTORSIZE, &tsecsize) != -1)
+ sectorsize = tsecsize;
if (sectorsize && ioctl(disk.d_fd, DIOCGMEDIASIZE, &mediasize) != -1)
getfssize(&fssize, special, mediasize / sectorsize, reserved);
}
Regards,
JC.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 13:29:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 675CE106564A
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 13:29:15 +0000 (UTC)
(envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
by mx1.freebsd.org (Postfix) with ESMTP id 23AA18FC12
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 13:29:14 +0000 (UTC)
Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1])
by elsa.codelab.cz (Postfix) with ESMTP id 8FDC719E02A
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 14:29:13 +0100 (CET)
Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by elsa.codelab.cz (Postfix) with ESMTPSA id 4746519E027
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 14:29:11 +0100 (CET)
Message-ID: <4B94FBA6.5090107@quip.cz>
Date: Mon, 08 Mar 2010 14:29:10 +0100
From: Miroslav Lachman <000.fbsd@quip.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <20100308102918.GA5485@localhost> <4B94DDC8.5080008@quip.cz>
<20100308115052.GA31896@office.redwerk.com>
In-Reply-To: <20100308115052.GA31896@office.redwerk.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 13:29:15 -0000
Eugene Dzhurinsky wrote:
> On Mon, Mar 08, 2010 at 12:21:44PM +0100, Miroslav Lachman wrote:
>> Eugeny N Dzhurinsky wrote:
>> We have this problem from time to time on bunch of machines. As we are
>> using gmirror, the easiest way is to force re-synchronization (rewrite)
>> of the whole drive. The problem is when there are Pending unreadable
>> sectors on both drives - it ends up with read error and some file(s) are
>> corrupted, but there is no easy way (on FreeBSD) to find what file.
>>
>> I tried it in the past with fsdb / findblk, but it does not work as I
>> expect or I do not fully understand the needed calculations with slices
>> + partitions offsets / LBAs and right meaning of the term "block". It
>> seems there are several meaning in different contexts.
>>
>> It would be nice if somebody with enough FS / GEOM knowledge can write
>> some HowTo or shell script to do the calculations and operations to find
>> file containing bad sector(s) and put it in FAQ, Handbook, or Wiki.
>
>
> Miroslav, thank you for the suggestion - but I am not using gmirror, that HDD
> is the one on my laptop. However suggestions about using dd to write something
> into bad block to force IDE controller do it's service stuff about remapping
> seems did the trick. And I was able to not calculate LBA but use it as block
> offset, which seemed to be correct way :)
Yes, rewriting by dd or any other way works for reallocating or clearing
pending sectors counter, but in server environment I need to know the
affected file, as it can be for example database file and then it is a
big problem! Rewriting the sector inside InnoDB ib_data file can cause
DB crash, data loss etc.
Miroslav Lachman
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 13:59:41 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1B4E51065670;
Mon, 8 Mar 2010 13:59:41 +0000 (UTC)
(envelope-from giovanni.trematerra@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 77BBB8FC14;
Mon, 8 Mar 2010 13:59:40 +0000 (UTC)
Received: by fxm23 with SMTP id 23so4785746fxm.3
for <multiple recipients>; Mon, 08 Mar 2010 05:59:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=pxMjNWa0CYaQM7ISYgE0ySI+RbCVv2uD6+FwYij4Vug=;
b=AqJSzm/PB2UVckXQwEVWRacOVqPbJMVMN491M3R2ePMTqg5AgLKunFq0vN3VPzIH8y
zItFiPebCGsnB4msFFWVqopVGqK2jCWKJGOPEMLEpc3oHp1iMjSZPTCiUGwulBwLxXlq
l/dMGkiyWRpFc90vwM7XpfIoFv5QeCa4gmiKE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=UArpe/4IS7OGSTan3Vpv3pILjWc42F0/DB7FY7YjrsKCeKMHwoapu/4HIoAjr2npeU
1LA3hnydpGrLJUgt8E0UPrieXQaffqJiEO0gWqXymej56gjHGD/XmFj+NTBib6kWTdQg
Sxnm7IFywf0+iam1SXfZW3U4BaGstrrBwMvEM=
MIME-Version: 1.0
Received: by 10.223.100.214 with SMTP id z22mr5569348fan.104.1268056779326;
Mon, 08 Mar 2010 05:59:39 -0800 (PST)
In-Reply-To: <7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
Date: Mon, 8 Mar 2010 14:59:39 +0100
Message-ID: <4e6cba831003080559p128e741em649030480a49153f@mail.gmail.com>
From: Giovanni Trematerra <giovanni.trematerra@gmail.com>
To: Garrett Cooper <yanefbsd@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Alexander Motin <mav@freebsd.org>,
FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 13:59:41 -0000
On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com> wrote=
:
>> Hi Alexander and Hans,
>> =A0 =A0I recently did the following which generated a panic on a
>> 9-CURRENT kernel compiled on the 26th:
>>
>> 1. Executed reboot
>> 2. Removed keyboard.
>> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
>> the keyboard was registered disconnected.
>> 4. The interrupt was delivered to my twa(4) enabled card and the
>> kernel panicked, like so:
>>
>> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
>> uhub8: at uhub2, port 1, addr 2 (disconnected)
>> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
>> ukbd0: at uhub8, port 3, addr 3 (disconnected)
>> uhid0: at uhub8, port 3, addr 3 (disconnected)
>> panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_i=
ntr.c:88
>>
>> cpuid =3D 1
>> KDB: enter: panic
>> [thread pid 12 tid 100025 ]
>> Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%rip=
)
>> db>
>>
>> =A0 =A0I wish I could provide you with more details, but unfortunately I
>> the USB bus isn't registering the fact that I'm reattaching the
>> keyboard right now and the box won't reboot automatically :( (didn't
>> set the right sysctl beforehand to panic automatically). I'll try and
>> reproduce the issue again, but I was just wondering whether or not you
>> guys had seen this problem before.
>
> =A0 =A0Phew... it's reproducible with that kernel. Here's what I did
> exactly (because my original directions were incorrect):
> =A0 =A01. Hit power button (for S5).
> =A0 =A02. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
> =A0 =A0Kernel panicked on my system again. Now to figure out if it still
> exists with a kernel compiled today, and also how to debug it if it
> still does exist :/...
I thinks that's a race in twa driver. You could unplug another USB
device different from your keyboard
and you should still got the panic.
If you get the panic again try to show at least the following information:
bt; show pcpu; show alllocks; show locks; ps
Thank you
--
Gianni
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 14:45:27 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 16CE7106566C
for <current@freebsd.org>; Mon, 8 Mar 2010 14:45:27 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 2D6E58FC12
for <current@freebsd.org>; Mon, 8 Mar 2010 14:45:25 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NoeCw-0004De-B7; Mon, 08 Mar 2010 16:45:22 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NoeCu-0006P9-12; Mon, 08 Mar 2010 16:45:20 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100305215539.GG14818@michelle.cdnetworks.com>
References: <20100305215539.GG14818@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
X-Attribution: BOFH
Date: Mon, 08 Mar 2010 16:45:20 +0200
Message-Id: <E1NoeCu-0006P9-12@clue.co.za>
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 14:45:27 -0000
Pyun YongHyeon wrote:
> On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > Pyun YongHyeon wrote:
> > > Thanks for the info. Frankly, I have no idea how to explain the
> > > issue given that you have no heavy load.
> >
> > How many cores would be involved in handling the traffic and runnig
> > PF rules on this machine? There are 4x
> > CPU: Quad-Core AMD Opteron(tm) Processor 8354 (2194.51-MHz K8-class CPU)
> > In this server. I'm also using carp extensively.
> >
>
> pf(4) uses a single lock for processing, number of core would have
> no much benefit.
What's interesting is the effect on CPU utilisation and interrupt
generation that net.inet.ip.fastforwarding has:
net.inet.ip.fastforwarding=1
interrupt rate is around 10000/s per bce interface
cpu 8.0% interrupt
net.inet.ip.fastforwarding=0
interrupt rate is around 5000/s per bce interface
cpu 13.0% interrupt
It also appears to not drop packets, but I'll have to watch it for longer.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 14:53:20 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 644D7106564A;
Mon, 8 Mar 2010 14:53:20 +0000 (UTC)
(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 3FDD38FC1A;
Mon, 8 Mar 2010 14:53:20 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
by cyrus.watson.org (Postfix) with ESMTPS id B9D3646B66;
Mon, 8 Mar 2010 09:53:19 -0500 (EST)
Date: Mon, 8 Mar 2010 14:53:19 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: current@FreeBSD.org, stable@FreeBSD.org
In-Reply-To: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
Message-ID: <alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc:
Subject: Survey results very helpful,
thanks! (was: Re: net.inet.tcp.timer_race:
does anyone have a non-zero value?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 14:53:20 -0000
On Sun, 7 Mar 2010, Robert Watson wrote:
> If your system shows a non-zero value, please send me a *private e-mail*
> with the output of that command, plus also the output of "sysctl kern.smp",
> "uptime", and a brief description of the workload and network interface
> configuration. For example: it's a busy 8-core web server with roughly X
> connections/second, and that has three em network interfaces used to load
> balance from an upstream source. IPSEC is used for management purposes (but
> not bulk traffic), and there's a local MySQL database.
I've now received a number of reports that confirm our suspicion that the race
does occur, albeit very rarely, and particularly on systems with many cores or
multiple network interfaces. Fixing it is definitely on the TODO for 9.0,
both to improve our ability to do multiple virtual network stacks, but with an
appropriately scalable fix in mind given our improved TCP scalability for 9.0
as well.
Thanks for all the responses,
Robert N M Watson
Computer Laboratory
University of Cambridge
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 16:58:17 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 514C21065670
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 16:58:17 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Received: from monday.kientzle.com (kientzle.com [66.166.149.50])
by mx1.freebsd.org (Postfix) with ESMTP id 051B78FC14
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 16:58:16 +0000 (UTC)
Received: (from root@localhost)
by monday.kientzle.com (8.14.3/8.14.3) id o28GwNwF007883;
Mon, 8 Mar 2010 16:58:23 GMT (envelope-from kientzle@freebsd.org)
Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2])
by kientzle.com with SMTP id ixf7bt487enwntw3f6vx7pkmf2;
Mon, 08 Mar 2010 16:58:22 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Message-ID: <4B952CEC.7000501@freebsd.org>
Date: Mon, 08 Mar 2010 08:59:24 -0800
From: Tim Kientzle <kientzle@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16
MIME-Version: 1.0
To: Luigi Rizzo <rizzo@iet.unipi.it>
References: <4B9425C4.5060309@freebsd.org>
<07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com>
<20100308075733.GA24644@onelab2.iet.unipi.it>
In-Reply-To: <20100308075733.GA24644@onelab2.iet.unipi.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Subject: Re: Wireless TCP aborts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 16:58:17 -0000
Luigi Rizzo wrote:
> On Sun, Mar 07, 2010 at 03:08:38PM -0800, Chuck Swiger wrote:
>> Hi, Tim--
>>
>> On Mar 7, 2010, at 2:16 PM, Tim Kientzle wrote:
>> [ ... ]
>>> Corrupted MAC on input.
>>> Disconnecting: Packet corrupt
>>> rsync: connection unexpectedly closed ... [receiver]
>>>
>>> and then the rsync session is dead.
>>>
>> It's not TCP ... SSH adds it's own layer of data integrity checking ...
>>
>
> long ago, with the 'iwi' driver, there was the following problem
> leading the the sae problem you are seeing:
>
> the driver was doing WEP in software, and wrote back the result to
> the original mbuf (actually, cluster). As a result, the first
> transmission of a segment was correct, but in case a rxmt, data
> would be encrypted twice, and the remote ssh end detected the garbage
> and dropped the connection. This was fixed with Sam's help
> around early 2007 if i remember well.
>
> An easy way to see if it is a similar problem is use ipfw to drop
> some packets e.g.
> ipfw add 100 prob 0.1 deny tcp out xmit wi0 // use your interface name
I'll do some experimenting. Here are some
more details on the current setup in case
this rings any bells for anyone:
* Sender: FreeBSD 8-CURRENT r193146, bge driver
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x6001>
mem 0xe0800000-0xe080ffff irq 17 at device 0.0 on pci63
* Router: D-Link 655
* Receiver: FreeBSD 9-CURRENT r201154, ath driver
ath0: <Atheros 5424/2424> mem 0x55200000-0x5520ffff irq 18 at device 0.0
on pci3
ath0: AR2425 mac 14.2 RF5424 phy 7.0
The wireless side is using WPA2-PSK. Tonight
I'll try hooking up a wired connection to the
receiver and see if that changes anything.
Tim
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 17:50:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9CD33106566B
for <current@freebsd.org>; Mon, 8 Mar 2010 17:50:00 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 2883D8FC18
for <current@freebsd.org>; Mon, 8 Mar 2010 17:49:59 +0000 (UTC)
Received: by fxm23 with SMTP id 23so5028505fxm.3
for <current@freebsd.org>; Mon, 08 Mar 2010 09:49:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=334g2wsQbw29WWPSBruXjuQfbWDVaIY6mr+SSzMW/bs=;
b=vHVwXjYHN3s6Pg27Eqe+l7VACDOXBFfk6n/mM10hqS2aW/ywcJ3GXnArBxsqWPiSWm
aOgUz/FazGltETrw+saZDLpiKvWX7K8fnwYXmG5g04xThc0aIYIC6AUVRskdVjWcFp5n
PqAWHlTsSAguXGG1SRJyU9wWDZF3e/5oMBAqA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=MqqkmA44Wd6codKB5VqWrjf2fs555wctxXOYSKVoaSdAd1RAX+sxxInwiRlfoFFokq
OZi3dDVFEEtruIcS/8C3+Kv6tbjoFdfcPCXsC/CaehRZMQt1Yv9Vy1wTexAjWb7wqcGS
xPFvOMMPYkSwa9t+adfwXka19cmVTxIBiKpxg=
Received: by 10.87.15.18 with SMTP id s18mr7284624fgi.18.1268070598913;
Mon, 08 Mar 2010 09:49:58 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 3sm5034334fge.0.2010.03.08.09.49.52
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 08 Mar 2010 09:49:54 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Mon, 8 Mar 2010 09:49:49 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Mon, 8 Mar 2010 09:49:49 -0800
To: Ian FREISLICH <ianf@clue.co.za>
Message-ID: <20100308174949.GA1311@michelle.cdnetworks.com>
References: <20100305215539.GG14818@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1NoeCu-0006P9-12@clue.co.za>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 17:50:00 -0000
On Mon, Mar 08, 2010 at 04:45:20PM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > > Pyun YongHyeon wrote:
> > > > Thanks for the info. Frankly, I have no idea how to explain the
> > > > issue given that you have no heavy load.
> > >
> > > How many cores would be involved in handling the traffic and runnig
> > > PF rules on this machine? There are 4x
> > > CPU: Quad-Core AMD Opteron(tm) Processor 8354 (2194.51-MHz K8-class CPU)
> > > In this server. I'm also using carp extensively.
> > >
> >
> > pf(4) uses a single lock for processing, number of core would have
> > no much benefit.
>
> What's interesting is the effect on CPU utilisation and interrupt
> generation that net.inet.ip.fastforwarding has:
>
> net.inet.ip.fastforwarding=1
> interrupt rate is around 10000/s per bce interface
> cpu 8.0% interrupt
>
Yes, this is one of intentional change of the patch. Stock bce(4)
seems to generate too much interrupts on BCM5709 so I rewrote
interrupt handling with the help of David. sysctl nodes are also
exported to control interrupt moderation so you can change them if
you want. Default value was tuned to generate interrupts less than
10k per second and try to minimize latencies.
> net.inet.ip.fastforwarding=0
> interrupt rate is around 5000/s per bce interface
> cpu 13.0% interrupt
> It also appears to not drop packets, but I'll have to watch it for longer.
>
Hmm, actually that's not what I originally expected. :-)
The patch replaced some suspicious memory barrier instructions with
bus_dmamap_sync(9) and you may see the effect.
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 20:15:47 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2DF0F1065674
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 20:15:47 +0000 (UTC)
(envelope-from admin@lissyara.su)
Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162])
by mx1.freebsd.org (Postfix) with ESMTP id 33A598FC15
for <freebsd-current@freebsd.org>; Mon, 8 Mar 2010 20:15:22 +0000 (UTC)
Received: from [77.41.106.132] (port=22125 helo=compaq.lissyara.su)
by hosting.lissyara.su with esmtpa (Exim 4.71 (FreeBSD))
(envelope-from <admin@lissyara.su>) id 1NojMG-0008yz-QB
for freebsd-current@freebsd.org; Mon, 08 Mar 2010 23:15:20 +0300
Message-ID: <4B955AD8.1020305@lissyara.su>
Date: Mon, 08 Mar 2010 23:15:20 +0300
From: Alex Keda <admin@lissyara.su>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <20100308102918.GA5485@localhost>
In-Reply-To: <20100308102918.GA5485@localhost>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Description: if spam count > 60 - this is spam
X-Spam-Count: 0
X-Descriptions: powered by www.lissyara.su
X-Bounce-ID: hosting.lissyara.su
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 20:15:47 -0000
08.03.2010 13:29, Eugeny N Dzhurinsky ïèøåò:
> Hello, all!
>
> Recently I've started to see the following logs in messages:
>
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable (pending) sectors
> Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrectable sectors
>
> smartctl did really show that something is wrong with my HDD, but still no
> remaps - just read errors.
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed: read failure 60% 1198 222342559
> # 2 Extended offline Completed: read failure 60% 1187 222342557
> # 3 Extended offline Completed: read failure 60% 1180 222342559
> # 4 Short offline Completed without error 00% 1178 -
> # 5 Extended offline Aborted by host 90% 1178 -
>
> and
>
> ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> ...
> Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> ...
>
> Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do I
> force remapping of these sectors? I assume that I have to write something
> directly to the sectors?
use mhdd
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 20:13:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9BB2C106566B;
Mon, 8 Mar 2010 20:13:32 +0000 (UTC) (envelope-from bc979@lafn.org)
Received: from zoom.lafn.org (zoom.lafn.ORG [206.117.18.8])
by mx1.freebsd.org (Postfix) with ESMTP id 70E1A8FC1D;
Mon, 8 Mar 2010 20:13:32 +0000 (UTC)
Received: from [10.0.1.4] (pool-71-109-144-133.lsanca.dsl-w.verizon.net
[71.109.144.133]) (authenticated bits=0)
by zoom.lafn.org (8.14.3/8.14.2) with ESMTP id o28JYvci070955
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Mon, 8 Mar 2010 11:34:58 -0800 (PST) (envelope-from bc979@lafn.org)
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
<alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
In-Reply-To: <alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
Content-Transfer-Encoding: quoted-printable
From: Doug Hardie <bc979@lafn.org>
Date: Mon, 8 Mar 2010 11:34:56 -0800
To: Robert Watson <rwatson@freebsd.org>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: clamav-milter 0.95.3 at zoom.lafn.org
X-Virus-Status: Clean
X-Mailman-Approved-At: Mon, 08 Mar 2010 20:20:03 +0000
Cc: stable@freebsd.org, current@freebsd.org
Subject: Re: Survey results very helpful,
thanks! (was: Re: net.inet.tcp.timer_race: does anyone have a
non-zero value?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 20:13:32 -0000
On 8 March 2010, at 06:53, Robert Watson wrote:
>=20
> On Sun, 7 Mar 2010, Robert Watson wrote:
>=20
>> If your system shows a non-zero value, please send me a *private =
e-mail* with the output of that command, plus also the output of "sysctl =
kern.smp", "uptime", and a brief description of the workload and network =
interface configuration. For example: it's a busy 8-core web server =
with roughly X connections/second, and that has three em network =
interfaces used to load balance from an upstream source. IPSEC is used =
for management purposes (but not bulk traffic), and there's a local =
MySQL database.
>=20
> I've now received a number of reports that confirm our suspicion that =
the race does occur, albeit very rarely, and particularly on systems =
with many cores or multiple network interfaces. Fixing it is definitely =
on the TODO for 9.0, both to improve our ability to do multiple virtual =
network stacks, but with an appropriately scalable fix in mind given our =
improved TCP scalability for 9.0 as well.
I run a number of 4 core systems with em interfaces. These are =
production systems that are unmanned and located a long way from me. =
Under unusual conditions it can take up to 6 hours to get there. I have =
been waiting to switch to 8.0 because of the discussions on the em =
device and now it sounds like I had better just skip 8.x and wait for 9. =
7.2 is working just fine.=
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 20:33:33 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2EACF1065672;
Mon, 8 Mar 2010 20:33:33 +0000 (UTC)
(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 0625F8FC12;
Mon, 8 Mar 2010 20:33:33 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
by cyrus.watson.org (Postfix) with ESMTPS id AD7F246B45;
Mon, 8 Mar 2010 15:33:32 -0500 (EST)
Date: Mon, 8 Mar 2010 20:33:32 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Doug Hardie <bc979@lafn.org>
In-Reply-To: <FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
Message-ID: <alpine.BSF.2.00.1003082020560.96747@fledge.watson.org>
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
<alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
<FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: stable@freebsd.org, current@freebsd.org
Subject: Re: Survey results very helpful,
thanks! (was: Re: net.inet.tcp.timer_race:
does anyone have a non-zero value?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 20:33:33 -0000
On Mon, 8 Mar 2010, Doug Hardie wrote:
> I run a number of 4 core systems with em interfaces. These are production
> systems that are unmanned and located a long way from me. Under unusual
> conditions it can take up to 6 hours to get there. I have been waiting to
> switch to 8.0 because of the discussions on the em device and now it sounds
> like I had better just skip 8.x and wait for 9. 7.2 is working just fine.
Not sure that any information in this survey thread should be relevant to that
decision. This race has existed since before FreeBSD, having appeared in the
original BSD network stack, and is just as present in FreeBSD 7.x as 8.x or
9.x. When I learned about the race during the early 7.x development cycle, I
added a counter/statistic to measure how much it happened in practice, but was
not able to exercise it in my testing, and so left the counter in to appear in
7.0 and later so that we could perform this survey as core counts/etc
increase.
The two likely outcomes were "it is never exercised" and "it is exercised but
only very infrequently", neither really justifying the quite complex change to
correct it given requirements at the time. On-going development work on the
virtual network stack is what justifies correcting the bug at this point,
moving from detecting and handling the race to preventing it from occuring as
an invariant. The motivation here, BTW, is that we'd like to eliminate the
type-stable storage requirement for connection state (which ensures that
memory once used for a connection block is only ever used for connection
blocks in the future), allowing memory to be fully freed when a virtual
network stack is destroyed. Using type-stable storage helped address this
bug, but was primarily present to reduce the overhead of monitoring using
netstat(1). We'll now need to use a slightly more expensive solution (true
reference counts) in that context, although in practice it will almost
certainly be an unmeasurable cost.
Which is to say that while there might be something in the em/altq/... thread
to reasonably lead you to avoid 8.0, nothing in the TCP timer race thread
should do so, since it affects 7.2 just as much as 8.0. Even if you do see a
non-zero counter, that's not a matter for operational concern, just useful
from the perspective of a network stack developer to understanding timing and
behaviors in the stack. :-)
Robert
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 21:06:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1528D1065674
for <current@freebsd.org>; Mon, 8 Mar 2010 21:06:57 +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 C6B078FC1E
for <current@freebsd.org>; Mon, 8 Mar 2010 21:06:56 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by FS.denninger.net (8.14.3/8.13.1) with SMTP id o28KUjXg012710
for <current@freebsd.org>; Mon, 8 Mar 2010 14:30:45 -0600 (CST)
(envelope-from karl@denninger.net)
Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL);
Mon Mar 8 14:30:45 2010
Message-ID: <4B955DF7.4010906@denninger.net>
Date: Mon, 08 Mar 2010 14:28:39 -0600
From: Karl Denninger <karl@denninger.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Doug Hardie <bc979@lafn.org>
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org> <alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
<FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
In-Reply-To: <FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/mixed; boundary="------------090403000808060305000607"
X-Antivirus: avast! (VPS 100308-1, 03/08/2010), Outbound message
X-Antivirus-Status: Clean
X-Mailman-Approved-At: Mon, 08 Mar 2010 21:42:39 +0000
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: stable@freebsd.org, Robert Watson <rwatson@freebsd.org>,
current@freebsd.org
Subject: Re: Survey results very helpful, thanks!
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 21:06:57 -0000
This is a multi-part message in MIME format.
--------------090403000808060305000607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Doug Hardie wrote:
> On 8 March 2010, at 06:53, Robert Watson wrote:
>
>
>> On Sun, 7 Mar 2010, Robert Watson wrote:
>>
>>
>>> If your system shows a non-zero value, please send me a *private e-mail* with the output of that command, plus also the output of "sysctl kern.smp", "uptime", and a brief description of the workload and network interface configuration. For example: it's a busy 8-core web server with roughly X connections/second, and that has three em network interfaces used to load balance from an upstream source. IPSEC is used for management purposes (but not bulk traffic), and there's a local MySQL database.
>>>
>> I've now received a number of reports that confirm our suspicion that the race does occur, albeit very rarely, and particularly on systems with many cores or multiple network interfaces. Fixing it is definitely on the TODO for 9.0, both to improve our ability to do multiple virtual network stacks, but with an appropriately scalable fix in mind given our improved TCP scalability for 9.0 as well.
>>
>
> I run a number of 4 core systems with em interfaces. These are production systems that are unmanned and located a long way from me. Under unusual conditions it can take up to 6 hours to get there. I have been waiting to switch to 8.0 because of the discussions on the em device and now it sounds like I had better just skip 8.x and wait for 9. 7.2 is working just fine._______________________________________________
>
I don't think its that simple.
I run a number of production systems with "em" interfaces, and they get
POUNDED.
None have had any trouble with 8.x.
$ ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
ether 00:30:48:d2:5a:24
inet 67.23.181.70 netmask 0xffffff00 broadcast 67.23.181.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
$ uptime
3:27PM up 61 days, 22:34, 1 user, load averages: 5.08, 4.48, 4.28
That's one of the busier ones; it's kinda loafing right now on network
I/O (running about 3mbps sustained) but typically operates in the
15-20mbps range to the wild wild net for 6-8 hours in the evening doing
what its doing now (handling a very busy forum) plus a few hundred
videocast streams....
The last reboot was to replace a power strip in the colo rack with one
that had remote management capability. It hasn't actually crashed
since, well, pretty much forever (it was running 7.x before 8.x went to
production status)
The box is a dual quad-core Xeon running the amd64 codebase.
-- Karl
--------------090403000808060305000607--
From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 23:09:53 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from hub.freebsd.org (localhost [127.0.0.1])
by hub.freebsd.org (Postfix) with ESMTP id 5D587106566B;
Mon, 8 Mar 2010 23:09:52 +0000 (UTC)
(envelope-from nork@FreeBSD.org)
Date: Tue, 9 Mar 2010 08:09:51 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: David Ehrmann <ehrmann@gmail.com>
Message-Id: <20100309080951.b1a37510.nork@FreeBSD.org>
In-Reply-To: <4B93E96B.8090002@gmail.com>
References: <4B934015.8000908@gmail.com> <4B934354.4030002@elischer.org>
<20100307184422.7007747d.nork@FreeBSD.org>
<4B93E96B.8090002@gmail.com>
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.5; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Norikatsu Shigemura <nork@freebsd.org>,
Julian Elischer <julian@elischer.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 23:09:53 -0000
Hi David.
On Sun, 07 Mar 2010 09:59:07 -0800
David Ehrmann <ehrmann@gmail.com> wrote:
> I was thinking that if I did do it, I'd start with padlock as a base.
> It looks like there are maybe 6 new opcodes. Maybe we could ask the
> contributor of the Linux code (an Intel employee) if he'd be willing to
> also release the code under a BSD license.
According to http://en.wikipedia.org/wiki/AES-NI , we can get
specification document: http://software.intel.com/file/20457 .
I saw it, and consider that we can release under BSDL. Because
of 'from specification'.
> My problem is that I don't have a Core i5 system--I was asking because
> it's an option for my new system--and I'm far from an x86 assembly expert.
I have a machine equipped with Core i7 640UM, so I'll be able
to test. But I'm far from an x86asm expert, too:-(.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 00:10:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A739A1065672
for <freebsd-current@FreeBSD.org>; Tue, 9 Mar 2010 00:10:58 +0000 (UTC)
(envelope-from james-freebsd-current@jrv.org)
Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106])
by mx1.freebsd.org (Postfix) with ESMTP id 6AAFE8FC1C
for <freebsd-current@FreeBSD.org>; Tue, 9 Mar 2010 00:10:58 +0000 (UTC)
Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124])
by mail.jrv.org (8.14.3/8.14.3) with ESMTP id o290AqVa020456;
Mon, 8 Mar 2010 18:10:52 -0600 (CST)
(envelope-from james-freebsd-current@jrv.org)
Authentication-Results: mail.jrv.org; domainkeys=pass (testing)
header.from=james-freebsd-current@jrv.org
DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns;
h=message-id:date:from:user-agent:mime-version:to:cc:subject:
references:in-reply-to:content-type:content-transfer-encoding;
b=KY3x1QoK0uchUMIB6ZleK5n9SecI0nhYMwdpx8JE/Y67SNK/Z+D4y0LNtQ2q5L7Hq
mbhNb+NJOySUksmYAicJHb/CJo7V8gKttg3QEl9H5yM/9dzm7e7ITJwVhe5osJy1rM2
SeWgOU6ciIrz6HJlQ6wRP9owHuUdvfEFVT34rfs=
Message-ID: <4B95920C.5000909@jrv.org>
Date: Mon, 08 Mar 2010 18:10:52 -0600
From: "James R. Van Artsdalen" <james-freebsd-current@jrv.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Norikatsu Shigemura <nork@FreeBSD.org>
References: <4B934015.8000908@gmail.com>
<4B934354.4030002@elischer.org> <20100307184422.7007747d.nork@FreeBSD.org> <4B93E96B.8090002@gmail.com>
<20100309080951.b1a37510.nork@FreeBSD.org>
In-Reply-To: <20100309080951.b1a37510.nork@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org, David Ehrmann <ehrmann@gmail.com>,
Julian Elischer <julian@elischer.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 00:10:58 -0000
Norikatsu Shigemura wrote:
> According to http://en.wikipedia.org/wiki/AES-NI , we can get
> specification document: http://software.intel.com/file/20457 .
>
> I saw it, and consider that we can release under BSDL. Because
> of 'from specification'.
That document is short on details, such as the opcodes and machine
implementation details (flags, etc).
The XMM registers are used. That may be a problem for kernel code.
When last I looked openssl did not use /dev/crypt - it's not clear how
big the benefit would be from doing this if nothing that uses openssl wins.
It might be more beneficial to FreeBSD to patch openssl to use
/dev/crypt. If it turns out to not be a significant win then that might
hint that the AES opcodes won't be significant win in general either.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 00:34:47 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9D733106564A
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 00:34:47 +0000 (UTC)
(envelope-from ehrmann@gmail.com)
Received: from mail-iw0-f185.google.com (mail-iw0-f185.google.com
[209.85.223.185])
by mx1.freebsd.org (Postfix) with ESMTP id 538208FC13
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 00:34:47 +0000 (UTC)
Received: by iwn15 with SMTP id 15so5731589iwn.7
for <multiple recipients>; Mon, 08 Mar 2010 16:34:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=vw5sVGtK9jj5tc4583DJxCIMTX/AHYNh36nccWjW3oI=;
b=wVYysgWyQH3MxjlvHrh2n5Jfx0/neqomBUOey7h/O52pTrFTwRJsb57h8954d8leW3
70eXG4ww1I08AihsqQXCEjz83jFzar5U6fNpp+u/+qVTaIUdqm0oVx24b7eqqEMsSipW
8l28+I3cFdiZFRU0vhVlzizA6jy1enDzE5Uwo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=FYI7k8RX+JyAv+VeM4zODDX1BnRfaOTqmw5nc1CeY1eCyIdaZSulL4OUKovtbY7RGO
G5VcN/RbgpAVGcltHijNjZxCtfx4t1bkxbxuVCnjbZ4QnEXxoHPYSmb2RaQ+vxJ0EGXc
Grw1dziyBl+erPImAJq1hpLNJXl0VC/fVpSKY=
MIME-Version: 1.0
Received: by 10.231.161.143 with SMTP id r15mr128597ibx.62.1268094886476; Mon,
08 Mar 2010 16:34:46 -0800 (PST)
In-Reply-To: <4B95920C.5000909@jrv.org>
References: <4B934015.8000908@gmail.com> <4B934354.4030002@elischer.org>
<20100307184422.7007747d.nork@FreeBSD.org>
<4B93E96B.8090002@gmail.com>
<20100309080951.b1a37510.nork@FreeBSD.org> <4B95920C.5000909@jrv.org>
Date: Mon, 8 Mar 2010 16:34:46 -0800
Message-ID: <6e0e5341003081634s2120a531u82b83f3de4f7e458@mail.gmail.com>
From: David Ehrmann <ehrmann@gmail.com>
To: "James R. Van Artsdalen" <james-freebsd-current@jrv.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-current@freebsd.org, Norikatsu Shigemura <nork@freebsd.org>,
Julian Elischer <julian@elischer.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 00:34:47 -0000
On Mon, Mar 8, 2010 at 4:10 PM, James R. Van Artsdalen <
james-freebsd-current@jrv.org> wrote:
>
> When last I looked openssl did not use /dev/crypt - it's not clear how
> big the benefit would be from doing this if nothing that uses openssl wins.
>
Geli uses the crypto framework.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 01:32:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4060B106566C
for <current@freebsd.org>; Tue, 9 Mar 2010 01:32:57 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
[209.85.160.182])
by mx1.freebsd.org (Postfix) with ESMTP id DFC6E8FC08
for <current@freebsd.org>; Tue, 9 Mar 2010 01:32:56 +0000 (UTC)
Received: by gyg8 with SMTP id 8so1763655gyg.13
for <current@freebsd.org>; Mon, 08 Mar 2010 17:32:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=7lgcl93L5rFGRFLsAbMMIbKt70DwUa4aWem77iUc1FU=;
b=wYPx/sc9IidHKtbIvUTYOkElgO+EAxK/Ceb+Geqzcm7QBeN9CAYajsckQ2uLNBQlqj
ty8vrc8cbLe/9xmLnuWRg/K6pRpy+vhf1rE+OT56obabou427YgC583Jn6dFWyTP4r84
EG/2L3FoHEnpoqUDnVz5x8zvDPDZCILHDm2pw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=RU9B/bxjL+/jndpsDZ0aWPtHt886wGCfj39lBJtcEvF1yjoO9MT4d3tkTpfejW53iL
AlpK1ccZgkZgymtGcL3wj/dDT8eoxCuSljWHEl8IjQQAPbHob8LppYVcSrGcFu98eVe2
bAZP5A76bQ+D/ZCV0xObwh2J4MLb4mkN9O7Bg=
Received: by 10.150.117.19 with SMTP id p19mr2349903ybc.275.1268098376224;
Mon, 08 Mar 2010 17:32:56 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id 9sm2001015ywf.8.2010.03.08.17.32.53
(version=SSLv3 cipher=RC4-MD5); Mon, 08 Mar 2010 17:32:55 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Mon, 8 Mar 2010 17:33:01 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Mon, 8 Mar 2010 17:33:01 -0800
To: Joe Marcus Clarke <marcus@marcuscom.com>
Message-ID: <20100309013301.GU1295@weongyo>
Mail-Followup-To: Joe Marcus Clarke <marcus@marcuscom.com>,
current <current@freebsd.org>
References: <20100301233706.GH1295@weongyo>
<1267505443.35639.9.camel@shumai.marcuscom.com>
<20100303220452.GL1295@weongyo> <4B8EE6B1.6030605@freebsd.org>
<20100303231416.GN1295@weongyo>
<1267679522.5324.20.camel@shumai.marcuscom.com>
<20100305205349.GR1295@weongyo> <4B917B42.1060900@freebsd.org>
<20100306001656.GS1295@weongyo>
<1267938343.96436.9.camel@shumai.marcuscom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1267938343.96436.9.camel@shumai.marcuscom.com>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: current <current@freebsd.org>
Subject: Re: Problem with new bwn driver on -CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 01:32:57 -0000
On Sun, Mar 07, 2010 at 12:05:43AM -0500, Joe Marcus Clarke wrote:
> On Fri, 2010-03-05 at 16:16 -0800, Weongyo Jeong wrote:
> > On Fri, Mar 05, 2010 at 04:44:34PM -0500, Joe Marcus Clarke wrote:
> > > On 3/5/10 3:53 PM, Weongyo Jeong wrote:
> > > > On Thu, Mar 04, 2010 at 12:12:02AM -0500, Joe Marcus Clarke wrote:
> > > >> On Wed, 2010-03-03 at 15:14 -0800, Weongyo Jeong wrote:
> > > >>>> When it occurs again, I will get you the details and the full dmesg. Do
> > > >>>> you want a verbose dmesg, or a standard one?
> > > >>>
> > > >>> I think a standard one is enough. Thank you.
> > > >>
> > > >> Here you go. This is on -CURRENT from about 30 minutes ago. Thanks for
> > > >> looking into this.
> > > >>
> > > >> http://www.marcuscom.com/downloads/salami.dmesg
> > > >
> > > > Thank you for dmesg. It looks using PIO mode is only a way to avoid
> > > > this problem.
> > > >
> > > > I looked sources and problems of other Broadcom wireless driver for LP
> > > > PHY users. They also encounters this issue and are trying to solve
> > > > this but no luck and no perfect patch until now.
> > > >
> > > > Recently AFAIK wireless-test git of linux adopted a patch `gracefully
> > > > convert DMA to PIO mode' to solve it.
> > > >
> > > > Additionally some guys tolds some success story when they disabled ACPI
> > > > but it looks it's not a perfect solution.
> > > >
> > > > IIRC you said PIO worked for association with your AP but no further
> > > > traffic. However I wonder that this is weird for me because paths of
> > > > sending management frames and sending data frames are same. Could you
> > > > please recheck whether PIO mode worked? I'll try to test PIO mode on my
> > > > environment again.
> > >
> > > I can absolutely confirm PIO mode does NOT work with my card. I tested
> > > on a clean power-up. The card associates, but does not pass any
> > > traffic. I do not see the same decryption messages that I do with DMA mode.
> >
> > OK. I'd like to see some verbose message from bwn(4) after applying
> > attached patch with email. Could you please test with it and show me
> > dmesg?
> >
> > I tested 3 broadcom card whose revisions are 5 and 9 and it looks it's
> > working.
> >
> > I have one LP PHY device, half MiniPCI-E for laptop, but could not test
> > with this patch because I could not turn on RF; it's connected with
> > desktop using converter MiniPCI-E to PCI-E though normally it looks
> > MiniPCI-E devices are turned on using H/W RF switch.
>
> Here are two dmesg outputs. Both were taken with this patch. One is
> with PIO mode, and the other is with (working) DMA mode. The names
> indicate which is which.
>
> http://www.marcuscom.com/downloads/salami_pio.dmesg
> http://www.marcuscom.com/downloads/salami_dma.dmesg
Thank you for dmesg. It looks you are right that your device in PIO
mode doesn't work. Specially RX path is weird that it was good until
the status is changed to RUN but after querying DHCP requests (or
another) there were no more RX events (seems no more frames ready).
I think it'd be better to file a PR because I could not test LP PHY
easily and it looks that it takes time to solve this problem. Could you
please do that?
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 08:26:35 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BB0D910656B2
for <current@freebsd.org>; Tue, 9 Mar 2010 08:26:35 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 4588C8FC1D
for <current@freebsd.org>; Tue, 9 Mar 2010 08:26:33 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1Noulr-0000q7-LF; Tue, 09 Mar 2010 10:26:31 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1Noulp-0007Rc-Ro; Tue, 09 Mar 2010 10:26:29 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100305210435.GF14818@michelle.cdnetworks.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za>
X-Attribution: BOFH
Date: Tue, 09 Mar 2010 10:26:29 +0200
Message-Id: <E1Noulp-0007Rc-Ro@clue.co.za>
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 08:26:35 -0000
Pyun YongHyeon wrote:
> patch can fix the RX issue you're suffering from. Anyway, would you
> give it try the patch at the following URL?
> http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> The patch was generated against CURRENT and you may see a message
> like "Disabling COAL_NOW timedout!" during interface up. You can
> ignore that message.
It's been running for about 1:23 on the patched driver. I'm still
seeing the com_no_buffers increase:
[firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
dev.bce.0.com_no_buffers: 5642
dev.bce.1.com_no_buffers: 497
dev.bce.2.com_no_buffers: 6260612
dev.bce.3.com_no_buffers: 4871338
Interupt rate is down now, at about 3500 per second per interface.
Interestingly setting net.inet.ip.fastforwarding=0 reduces CPU
consumption from 25% to 9% and less packet loss.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 09:07:55 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 890911065676
for <freebsd-current@FreeBSD.org>; Tue, 9 Mar 2010 09:07:55 +0000 (UTC)
(envelope-from dfr@rabson.org)
Received: from mail2.rabson.org (mail2.rabson.org [83.222.226.140])
by mx1.freebsd.org (Postfix) with ESMTP id 394A28FC16
for <freebsd-current@FreeBSD.org>; Tue, 9 Mar 2010 09:07:55 +0000 (UTC)
Received: from macpro.dyn.rabson.org (router.rabson.org [80.177.232.241])
by mail2.rabson.org (Postfix) with ESMTPSA id 1042236;
Tue, 9 Mar 2010 09:07:53 +0000 (GMT)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Doug Rabson <dfr@rabson.org>
In-Reply-To: <4B95920C.5000909@jrv.org>
Date: Tue, 9 Mar 2010 09:07:52 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <89BC6265-4DB4-46A2-A01E-80FDA6E7377B@rabson.org>
References: <4B934015.8000908@gmail.com>
<4B934354.4030002@elischer.org> <20100307184422.7007747d.nork@FreeBSD.org> <4B93E96B.8090002@gmail.com>
<20100309080951.b1a37510.nork@FreeBSD.org>
<4B95920C.5000909@jrv.org>
To: James R. Van Artsdalen <james-freebsd-current@jrv.org>
X-Mailer: Apple Mail (2.1077)
Cc: David Ehrmann <ehrmann@gmail.com>, freebsd-current@FreeBSD.org,
Norikatsu Shigemura <nork@FreeBSD.org>,
Julian Elischer <julian@elischer.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 09:07:55 -0000
On 9 Mar 2010, at 00:10, James R. Van Artsdalen wrote:
> Norikatsu Shigemura wrote:
>> According to http://en.wikipedia.org/wiki/AES-NI , we can get
>> specification document: http://software.intel.com/file/20457 .
>>=20
>> I saw it, and consider that we can release under BSDL. Because
>> of 'from specification'.
>=20
> That document is short on details, such as the opcodes and machine
> implementation details (flags, etc).
>=20
> The XMM registers are used. That may be a problem for kernel code.
>=20
> When last I looked openssl did not use /dev/crypt - it's not clear how
> big the benefit would be from doing this if nothing that uses openssl =
wins.
>=20
> It might be more beneficial to FreeBSD to patch openssl to use
> /dev/crypt. If it turns out to not be a significant win then that =
might
> hint that the AES opcodes won't be significant win in general either.
The in-kernel kerberos code for NFS would also benefit since it uses the =
crypto framework.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 08:53:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 103F21065675;
Tue, 9 Mar 2010 08:53:36 +0000 (UTC) (envelope-from bc979@lafn.org)
Received: from zoom.lafn.org (zoom.lafn.ORG [206.117.18.8])
by mx1.freebsd.org (Postfix) with ESMTP id CFB328FC21;
Tue, 9 Mar 2010 08:53:35 +0000 (UTC)
Received: from [10.0.1.4] (pool-71-109-144-133.lsanca.dsl-w.verizon.net
[71.109.144.133]) (authenticated bits=0)
by zoom.lafn.org (8.14.3/8.14.2) with ESMTP id o298rYvW093739
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Tue, 9 Mar 2010 00:53:35 -0800 (PST) (envelope-from bc979@lafn.org)
References: <alpine.BSF.2.00.1003071141050.9729@fledge.watson.org>
<alpine.BSF.2.00.1003081450310.23881@fledge.watson.org>
<FF1D92A1-89BD-457E-9A6C-089D20E4D175@lafn.org>
<alpine.BSF.2.00.1003082020560.96747@fledge.watson.org>
In-Reply-To: <alpine.BSF.2.00.1003082020560.96747@fledge.watson.org>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <80C9B3BA-C498-419B-BD5E-6C2111F24F64@lafn.org>
Content-Transfer-Encoding: quoted-printable
From: Doug Hardie <bc979@lafn.org>
Date: Tue, 9 Mar 2010 00:53:34 -0800
To: Robert Watson <rwatson@freebsd.org>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: clamav-milter 0.95.3 at zoom.lafn.org
X-Virus-Status: Clean
X-Mailman-Approved-At: Tue, 09 Mar 2010 12:32:26 +0000
Cc: stable@freebsd.org, current@freebsd.org
Subject: Re: Survey results very helpful,
thanks! (was: Re: net.inet.tcp.timer_race: does anyone have a
non-zero value?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 08:53:36 -0000
On 8 March 2010, at 12:33, Robert Watson wrote:
>=20
> On Mon, 8 Mar 2010, Doug Hardie wrote:
>=20
>> I run a number of 4 core systems with em interfaces. These are =
production systems that are unmanned and located a long way from me. =
Under unusual conditions it can take up to 6 hours to get there. I have =
been waiting to switch to 8.0 because of the discussions on the em =
device and now it sounds like I had better just skip 8.x and wait for 9. =
7.2 is working just fine.
>=20
> Not sure that any information in this survey thread should be relevant =
to that decision. This race has existed since before FreeBSD, having =
appeared in the original BSD network stack, and is just as present in =
FreeBSD 7.x as 8.x or 9.x. When I learned about the race during the =
early 7.x development cycle, I added a counter/statistic to measure how =
much it happened in practice, but was not able to exercise it in my =
testing, and so left the counter in to appear in 7.0 and later so that =
we could perform this survey as core counts/etc increase.
>=20
> The two likely outcomes were "it is never exercised" and "it is =
exercised but only very infrequently", neither really justifying the =
quite complex change to correct it given requirements at the time. =
On-going development work on the virtual network stack is what justifies =
correcting the bug at this point, moving from detecting and handling the =
race to preventing it from occuring as an invariant. The motivation =
here, BTW, is that we'd like to eliminate the type-stable storage =
requirement for connection state (which ensures that memory once used =
for a connection block is only ever used for connection blocks in the =
future), allowing memory to be fully freed when a virtual network stack =
is destroyed. Using type-stable storage helped address this bug, but =
was primarily present to reduce the overhead of monitoring using =
netstat(1). We'll now need to use a slightly more expensive solution =
(true reference counts) in that context, although in practice it will =
almost certainly be an unmeasurable cost.
>=20
> Which is to say that while there might be something in the em/altq/... =
thread to reasonably lead you to avoid 8.0, nothing in the TCP timer =
race thread should do so, since it affects 7.2 just as much as 8.0. =
Even if you do see a non-zero counter, that's not a matter for =
operational concern, just useful from the perspective of a network stack =
developer to understanding timing and behaviors in the stack. :-)
Thanks for the complete explanation. I don't believe the ALTQ issue =
will affect me. I am not currently using it and do not expect to in the =
near future. In addition, there was a posting that a fix for at least =
part of that will be added in a week or so. Given all that it appears =
its time to start the planning/testing process for 8.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 10:46:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 97C8C106566B
for <freebsd-current@FreeBSD.ORG>; Tue, 9 Mar 2010 10:46:50 +0000 (UTC)
(envelope-from sobomax@sippysoft.com)
Received: from sippysoft.com (gk1.360sip.com [72.236.70.240])
by mx1.freebsd.org (Postfix) with ESMTP id 50A098FC12
for <freebsd-current@FreeBSD.ORG>; Tue, 9 Mar 2010 10:46:50 +0000 (UTC)
Received: from [192.168.1.38] (S0106005004e13421.vs.shawcable.net
[70.71.175.212]) (authenticated bits=0)
by sippysoft.com (8.14.3/8.14.3) with ESMTP id o29AVQxE006707
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 9 Mar 2010 02:31:27 -0800 (PST)
(envelope-from sobomax@sippysoft.com)
Message-ID: <4B962381.2060300@sippysoft.com>
Date: Tue, 09 Mar 2010 02:31:29 -0800
From: Maxim Sobolev <sobomax@sippysoft.com>
Organization: Sippy Software, Inc.
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Jayachandran C." <c.jayachandran@gmail.com>
References: <98a59be81003040504x6e97fbaeqeb10f8ea7bedb7b9@mail.gmail.com>
<4b94b8d8.c501be0a.4ce5.760a@mx.google.com>
In-Reply-To: <4b94b8d8.c501be0a.4ce5.760a@mx.google.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 09 Mar 2010 12:32:41 +0000
Cc: FreeBSD Current <freebsd-current@FreeBSD.ORG>
Subject: Re: newfs broken in -CURRENT after 204654
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 10:46:50 -0000
Jayachandran C. wrote:
> On Thu, Mar 04, 2010 at 06:34:03PM +0530, C. Jayachandran wrote:
>> I'm testing this on the mips platform, but I think there is an issue
>> with change that made sectorsize int64_t, because the ioctl
>> DIOCGSECTORSIZE used to read sector size seems to take u_int. This
>> quick change fixes it for me (sample patch - may be whitespace
>> damaged).
>
> I'm trying this one more time, since the issue is still unresolved.
>
> newfs(8) broke for big-endian systems since revision 204654. This change
> made sectorsize variable int64_t, and now it cannot be passed to the ioctl
> DIOCGSECTORSIZE.
>
> The patch below (updated from the previous one) fixes it, please review and
> apply if correct.
Sorry about that, I've just applied a fix.
Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sales@sippysoft.com
Skype: SippySoft
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 13:32:16 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B62DC1065670
for <current@freebsd.org>; Tue, 9 Mar 2010 13:32:16 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 0FD1C8FC24
for <current@freebsd.org>; Tue, 9 Mar 2010 13:32:11 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NozXR-00074z-AL; Tue, 09 Mar 2010 15:31:57 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NozXP-000GGH-T9; Tue, 09 Mar 2010 15:31:55 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100308174949.GA1311@michelle.cdnetworks.com>
References: <20100308174949.GA1311@michelle.cdnetworks.com>
<20100305215539.GG14818@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za>
X-Attribution: BOFH
Date: Tue, 09 Mar 2010 15:31:55 +0200
Message-Id: <E1NozXP-000GGH-T9@clue.co.za>
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 13:32:16 -0000
Pyun YongHyeon wrote:
> On Mon, Mar 08, 2010 at 04:45:20PM +0200, Ian FREISLICH wrote:
> > Pyun YongHyeon wrote:
> > > On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > > > Pyun YongHyeon wrote:
> > > > > Thanks for the info. Frankly, I have no idea how to explain the
> > > > > issue given that you have no heavy load.
> > > >
> > > > How many cores would be involved in handling the traffic and runnig
> > > > PF rules on this machine? There are 4x
> > > > CPU: Quad-Core AMD Opteron(tm) Processor 8354 (2194.51-MHz K8-class CPU
)
> > > > In this server. I'm also using carp extensively.
> > > >
> > >
> > > pf(4) uses a single lock for processing, number of core would have
> > > no much benefit.
> >
> > What's interesting is the effect on CPU utilisation and interrupt
> > generation that net.inet.ip.fastforwarding has:
> >
> > net.inet.ip.fastforwarding=1
> > interrupt rate is around 10000/s per bce interface
> > cpu 8.0% interrupt
> >
>
> Yes, this is one of intentional change of the patch. Stock bce(4)
> seems to generate too much interrupts on BCM5709 so I rewrote
> interrupt handling with the help of David. sysctl nodes are also
> exported to control interrupt moderation so you can change them if
> you want. Default value was tuned to generate interrupts less than
> 10k per second and try to minimize latencies.
Can you explain the tunables please - I'm guessing it's these:
dev.bce.$i.tx_quick_cons_trip_int
dev.bce.$i.tx_quick_cons_trip
dev.bce.$i.tx_ticks_int
dev.bce.$i.tx_ticks
dev.bce.$i.rx_quick_cons_trip_int
dev.bce.$i.rx_quick_cons_trip
dev.bce.$i.rx_ticks_int
dev.bce.$i.rx_ticks
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 18:47:17 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4CBFC1065670
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 18:47:17 +0000 (UTC)
(envelope-from rbgarga@gmail.com)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com
[74.125.82.182])
by mx1.freebsd.org (Postfix) with ESMTP id DFAE38FC1F
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 18:47:16 +0000 (UTC)
Received: by wyb32 with SMTP id 32so4123901wyb.13
for <freebsd-current@freebsd.org>; Tue, 09 Mar 2010 10:47:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:from:date:message-id
:subject:to:content-type;
bh=eXB2QVa+sPK1br0qeqz9RERoH6ZKWGzZ51ptiFA5+Ak=;
b=cLfl7kiFowKwItUEKbv0Ao54CW/bP7OBR4okY6y+Wu/GmzRpMn7sj5HKBaeFA1HXRi
Col/cPYNM+Wsw33EarkLg6jaXR3zn8RQdMXXUNfrhy0rysyFD9lq06WpwaokLYeb9FSh
/439qbeNBy1VXyhI4Fxj4hkQLkM7ArZ48kjVo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:from:date:message-id:subject:to:content-type;
b=kkDntWDTd8f0nxDTYvxXAAdWgqN/npuBni9Sh616m7bouOFhY8IFThQutMzzuagUwe
ArXxl7FCNszYufQI8H5TFUYq7e8EjOAi5SJrnhI3khpodUSdbjQa7KixpGCopSt8wiEA
jTbggui05vp06g+z089Gk9osg+RFund9V/eKo=
MIME-Version: 1.0
Received: by 10.216.90.17 with SMTP id d17mr125802wef.175.1268160435783; Tue,
09 Mar 2010 10:47:15 -0800 (PST)
From: Renato Botelho <rbgarga@gmail.com>
Date: Tue, 9 Mar 2010 15:46:55 -0300
Message-ID: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
To: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 18:47:17 -0000
I updated my 9.0-current amd64 today on rev. 204915 and start
to get errors like this
127.0.0.1: no route to host
I boot using kernel.old and everything back to normal. I don't know
exactly revision of my kernel.old because last change made on
sys/conf/newvers.sh simply removed this information from my
uname, see:
FreeBSD botelhor.bplab.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Mon
Mar 8 15:52:59 BRT 2010
root@botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA amd64
I just know it was built yesterday about 18:00 UTC
Is there any other way to get this information?
Let me know if you need more information about my environment.
Regards
--
Renato Botelho
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 19:05:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E63B3106564A
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 19:05:19 +0000 (UTC)
(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
by mx1.freebsd.org (Postfix) with ESMTP id CED348FC0C
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 19:05:19 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o29J5JoD023313;
Tue, 9 Mar 2010 11:05:19 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Mar 2010 11:05:13 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: Acq/uQc/wuPE86eQQ36rnjvhdhd1LAAAl2Aw
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Renato Botelho" <rbgarga@gmail.com>,
"FreeBSD Current" <freebsd-current@freebsd.org>
Cc:
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 19:05:20 -0000
Thanks for the report, I am looking at it and will get back to you.
-- Qing
> -----Original Message-----
> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> current@freebsd.org] On Behalf Of Renato Botelho
> Sent: Tuesday, March 09, 2010 10:47 AM
> To: FreeBSD Current
> Subject: Error 127.0.0.1: no route to host
>=20
> I updated my 9.0-current amd64 today on rev. 204915 and start
> to get errors like this
>=20
> 127.0.0.1: no route to host
>=20
> I boot using kernel.old and everything back to normal. I don't know
> exactly revision of my kernel.old because last change made on
> sys/conf/newvers.sh simply removed this information from my
> uname, see:
>=20
> FreeBSD botelhor.bplab.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Mon
> Mar 8 15:52:59 BRT 2010
> root@botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA amd64
>=20
> I just know it was built yesterday about 18:00 UTC
>=20
> Is there any other way to get this information?
>=20
> Let me know if you need more information about my environment.
>=20
> Regards
> --
> Renato Botelho
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 20:14:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 834611065670
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:14:25 +0000 (UTC)
(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
by mx1.freebsd.org (Postfix) with ESMTP id 4D7BE8FC0C
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:14:25 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o29KEOf4005392;
Tue, 9 Mar 2010 12:14:24 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Mar 2010 12:14:19 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: Acq/uQc/wuPE86eQQ36rnjvhdhd1LAAAl2AwAAJbuMA=
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
<B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Renato Botelho" <rbgarga@gmail.com>,
"FreeBSD Current" <freebsd-current@freebsd.org>
Cc:
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 20:14:25 -0000
This error was caused by my commit r204902 from yesterday.
Please try patch at
http://people.freebsd.org/~qingli/route.h.diff
-- Qing
> -----Original Message-----
> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> current@freebsd.org] On Behalf Of Li, Qing
> Sent: Tuesday, March 09, 2010 11:05 AM
> To: Renato Botelho; FreeBSD Current
> Subject: RE: Error 127.0.0.1: no route to host
>=20
> Thanks for the report, I am looking at it and will get back to you.
>=20
> -- Qing
>=20
>=20
> > -----Original Message-----
> > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> > current@freebsd.org] On Behalf Of Renato Botelho
> > Sent: Tuesday, March 09, 2010 10:47 AM
> > To: FreeBSD Current
> > Subject: Error 127.0.0.1: no route to host
> >
> > I updated my 9.0-current amd64 today on rev. 204915 and start
> > to get errors like this
> >
> > 127.0.0.1: no route to host
> >
> > I boot using kernel.old and everything back to normal. I don't know
> > exactly revision of my kernel.old because last change made on
> > sys/conf/newvers.sh simply removed this information from my
> > uname, see:
> >
> > FreeBSD botelhor.bplab.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Mon
> > Mar 8 15:52:59 BRT 2010
> > root@botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA amd64
> >
> > I just know it was built yesterday about 18:00 UTC
> >
> > Is there any other way to get this information?
> >
> > Let me know if you need more information about my environment.
> >
> > Regards
> > --
> > Renato Botelho
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-
> > unsubscribe@freebsd.org"
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 20:35:02 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C3492106566B
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:35:02 +0000 (UTC)
(envelope-from rbgarga@gmail.com)
Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54])
by mx1.freebsd.org (Postfix) with ESMTP id 59BCA8FC35
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:35:02 +0000 (UTC)
Received: by wwb24 with SMTP id 24so774472wwb.13
for <freebsd-current@freebsd.org>; Tue, 09 Mar 2010 12:35:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:cc:content-type
:content-transfer-encoding;
bh=8wsXUls89wnJ4eSbK1qLh356vBncmOCU2RYjD66JOQ8=;
b=xphaK7dczckBCS4Jo140rubmrCTE3b7PzTy5yCafwxh/dgSJY/usV45zceff9K7/4D
cnrmnY0EYqUDUjjMMnYGauce/8163cC7deJ97Dw9R6sd2ZBn+ko3oI3PocH6opLJsezK
tBwbUIc0auGRmk1TwD42npoJaLVYX1Ni9Mdk4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type:content-transfer-encoding;
b=WQ88FEyw08YBxFNwXKC7/zSF5+RvDw1pLxuPdPp4n/dqSEgwlR3Bfgtx7/Wy1Kh71g
i0tthBc7U7x0/ErxwJ4ki3UBQQLcz+E/X6EvFy2IAwbnhNsHOlgFwJIbFEm02PzTaurD
W24fB/jktFqZZ9MUrqalc7jgs4d3BcV9+KhBU=
MIME-Version: 1.0
Received: by 10.216.86.7 with SMTP id v7mr229467wee.137.1268166901169; Tue, 09
Mar 2010 12:35:01 -0800 (PST)
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
<B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
From: Renato Botelho <rbgarga@gmail.com>
Date: Tue, 9 Mar 2010 17:34:41 -0300
Message-ID: <747dc8f31003091234s33305e87q756225f2f22fe6b5@mail.gmail.com>
To: "Li, Qing" <qing.li@bluecoat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 20:35:02 -0000
On Tue, Mar 9, 2010 at 5:14 PM, Li, Qing <qing.li@bluecoat.com> wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> =A0 =A0 =A0 =A0http://people.freebsd.org/~qingli/route.h.diff
Patch fixed the problem, thanks for the quick reply and fix.
--=20
Renato Botelho
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 20:49:33 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2F7EB106564A
for <current@freebsd.org>; Tue, 9 Mar 2010 20:49:33 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155])
by mx1.freebsd.org (Postfix) with ESMTP id AD01B8FC1B
for <current@freebsd.org>; Tue, 9 Mar 2010 20:49:32 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id 22so2381601fge.13
for <current@freebsd.org>; Tue, 09 Mar 2010 12:49:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=TiMF9qHnFmYvM/Iaf7o+TKUJN5MUH2kQB+Evw4h5HdE=;
b=k2LdWFKo2MX0AVnH7P9ymtVVYQ7cPFPtX8kX4KY/WYYSpzJyfoQyL8JttbyUtCOUd9
Qea5uziedJf8kB2wKCsd+i/I8oLsZ/7I0AVW+H+levOP6zMaTpOAzqftAkx9TZXWJxa/
c4WCd5wYgHPihYhNjeuuf6E1YQB1pnx6iXxXo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=HMsrG/KEcigV4tLomYVP0alyXtgu16fidDhP+TQ4SjiyWZ6a6YHNw7X5a0288SdrXR
o5AML/kUW02vZnGgJnaXV7qO5xqSwqSq3YngqFWFwWUuHvtGrKoveeNURxHXyRnWQE1w
C/A6A8eL0WiJYzeZQO4Ir+9NY6EA4K4uXgJr4=
Received: by 10.87.62.1 with SMTP id p1mr1101864fgk.42.1268167771571;
Tue, 09 Mar 2010 12:49:31 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 12sm280379fgg.19.2010.03.09.12.49.28
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Tue, 09 Mar 2010 12:49:30 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Tue, 9 Mar 2010 12:49:27 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Tue, 9 Mar 2010 12:49:27 -0800
To: Ian FREISLICH <ianf@clue.co.za>
Message-ID: <20100309204927.GN1311@michelle.cdnetworks.com>
References: <20100305215539.GG14818@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za> <E1NozXP-000GGH-T9@clue.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1NozXP-000GGH-T9@clue.co.za>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 20:49:33 -0000
On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > On Mon, Mar 08, 2010 at 04:45:20PM +0200, Ian FREISLICH wrote:
> > > Pyun YongHyeon wrote:
> > > > On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > > > > Pyun YongHyeon wrote:
> > > > > > Thanks for the info. Frankly, I have no idea how to explain the
> > > > > > issue given that you have no heavy load.
> > > > >
> > > > > How many cores would be involved in handling the traffic and runnig
> > > > > PF rules on this machine? There are 4x
> > > > > CPU: Quad-Core AMD Opteron(tm) Processor 8354 (2194.51-MHz K8-class CPU
> )
> > > > > In this server. I'm also using carp extensively.
> > > > >
> > > >
> > > > pf(4) uses a single lock for processing, number of core would have
> > > > no much benefit.
> > >
> > > What's interesting is the effect on CPU utilisation and interrupt
> > > generation that net.inet.ip.fastforwarding has:
> > >
> > > net.inet.ip.fastforwarding=1
> > > interrupt rate is around 10000/s per bce interface
> > > cpu 8.0% interrupt
> > >
> >
> > Yes, this is one of intentional change of the patch. Stock bce(4)
> > seems to generate too much interrupts on BCM5709 so I rewrote
> > interrupt handling with the help of David. sysctl nodes are also
> > exported to control interrupt moderation so you can change them if
> > you want. Default value was tuned to generate interrupts less than
> > 10k per second and try to minimize latencies.
>
> Can you explain the tunables please - I'm guessing it's these:
>
> dev.bce.$i.tx_quick_cons_trip_int
This value controls the number of TX Quick BD Chain entries that
must be completed before a status block is generated during an
interrupt.
> dev.bce.$i.tx_quick_cons_trip
This value controls the number of TX Quick BD Chain entries that
must be completed before a status block is generated. Setting this
to 0 disables TX Quick BD Chain consumption from generating status
blocks.
> dev.bce.$i.tx_ticks_int
This value controls the number of 1us ticks that will be counted
for status block updates generated due to TX activity during
interrupt processing. Setting this value to 0 disables the TX
timer feature during interrupts.
> dev.bce.$i.tx_ticks
This value controls the number of 1us ticks that will be counted
before a status block update is generated due to TX activity.
Setting this value to 0 disables the TX timer feature.
> dev.bce.$i.rx_quick_cons_trip_int
This value controls the number of RX Quick BD entries that must be
completed before a status block is generated during interrupt
processing.
> dev.bce.$i.rx_quick_cons_trip
This value controls the number of RX Quick BD Chain entries that
must be completed before a status block is generated. Setting this
to 0 disables RX Event consumption from generating status blocks.
> dev.bce.$i.rx_ticks_int
This value controls the number of 1us ticks that will be counted
for status block updates generated due to RX activity during
interrupt processing. Setting this value to 0 disables the RX
timer feature during interrupts.
> dev.bce.$i.rx_ticks
>
This value controls the number of 1us ticks that will be counted
before a status block update is generated due to RX activity.
Setting this value to 0 disables the RX timer feature.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 20:55:05 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id ABCF0106564A
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:55:05 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (outl.internet-mail-service.net
[216.240.47.235])
by mx1.freebsd.org (Postfix) with ESMTP id 861E28FC13
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:55:05 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o29Kt2e2001445; Tue, 9 Mar 2010 12:55:02 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id A91782D6019;
Tue, 9 Mar 2010 12:55:01 -0800 (PST)
Message-ID: <4B96B5A4.7070307@elischer.org>
Date: Tue, 09 Mar 2010 12:55:00 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Li, Qing" <qing.li@bluecoat.com>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: Renato Botelho <rbgarga@gmail.com>,
FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 20:55:05 -0000
Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
[...]
I remember saying "well the patch itself is basically ok but I don't
know about the side effects". (about the ARPv2 change in general)
I'm guessing you have had a rather interesting learning experience
about how much simple changes can become complicated. :-)
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 20:57:20 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E17BC106566B
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:57:20 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (outl.internet-mail-service.net
[216.240.47.235])
by mx1.freebsd.org (Postfix) with ESMTP id C1E578FC13
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 20:57:20 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o29KvH6k001607; Tue, 9 Mar 2010 12:57:17 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id 831DB2D6022;
Tue, 9 Mar 2010 12:57:16 -0800 (PST)
Message-ID: <4B96B62B.9070307@elischer.org>
Date: Tue, 09 Mar 2010 12:57:15 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Li, Qing" <qing.li@bluecoat.com>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
<4B96B5A4.7070307@elischer.org>
In-Reply-To: <4B96B5A4.7070307@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 20:57:21 -0000
Julian Elischer wrote:
> Li, Qing wrote:
>> This error was caused by my commit r204902 from yesterday.
>>
> [...]
>
>
> I remember saying "well the patch itself is basically ok but I don't
> know about the side effects". (about the ARPv2 change in general)
>
> I'm guessing you have had a rather interesting learning experience
> about how much simple changes can become complicated. :-)
oops this was meant to be a private email
Sorry Qing Li!
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 21:07:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AA9681065673
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 21:07:58 +0000 (UTC)
(envelope-from christof.schulze@gmx.com)
Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42])
by mx1.freebsd.org (Postfix) with SMTP id 0E4898FC0A
for <freebsd-current@freebsd.org>; Tue, 9 Mar 2010 21:07:57 +0000 (UTC)
Received: (qmail invoked by alias); 09 Mar 2010 21:07:56 -0000
Received: from e181223085.adsl.alicedsl.de (EHLO klausdieter0815.dyndns.org)
[85.181.223.85]
by mail.gmx.com (mp-eu002) with SMTP; 09 Mar 2010 22:07:56 +0100
X-Authenticated: #56306756
X-Provags-ID: V01U2FsdGVkX18vdJJHewkv9FfOX8P3I7nfVsAm1XPz4x0O8CoalD
5qdqbwyDjDsCqH
Received: by myhost.mydomain.de (Postfix, from userid 1001)
id 580591887; Tue, 9 Mar 2010 22:07:57 +0100 (CET)
From: Christof Schulze <christof.schulze@gmx.com>
To: freebsd-current@freebsd.org
Date: Tue, 9 Mar 2010 22:07:56 +0100
User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.5; amd64; ; )
References: <4B934015.8000908@gmail.com>
<20100307184422.7007747d.nork@FreeBSD.org>
<4B93E96B.8090002@gmail.com>
In-Reply-To: <4B93E96B.8090002@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1672159.SyiLE4VSCt";
protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201003092207.57252.christof.schulze@gmx.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.53000000000000003
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 21:07:58 -0000
--nextPart1672159.SyiLE4VSCt
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Am Sunday 07 March 2010 18:59:07 schrieb David Ehrmann:
> On 3/7/10 1:44 AM, Norikatsu Shigemura wrote:
> > Hi Devid and Julian.
> >
> > On Sat, 06 Mar 2010 22:10:28 -0800
> >
> > Julian Elischer<julian@elischer.org> wrote:
> >> David Ehrmann wrote:
> >>> Does FreeBSD currently support cryptographic acceleration for AES on
> >>> the Core i5 CPU? I searched, but couldn't find anything, and the
> >>> crypto(4) manpage only lists these divers in "see also:"
> >>
> >> no, but if you write a driver for it we will... :-)
> >> (most things in open source happen because someone needs it.)
> >
> > I found Linux's code: http://lwn.net/Articles/311094/
> > I think that it looks too easy, maybe, we should implement aesni(4)
> > like padlock(4).
>=20
> I was thinking that if I did do it, I'd start with padlock as a base.
> It looks like there are maybe 6 new opcodes. Maybe we could ask the
> contributor of the Linux code (an Intel employee) if he'd be willing to
> also release the code under a BSD license.
>=20
> My problem is that I don't have a Core i5 system--I was asking because
> it's an option for my new system--and I'm far from an x86 assembly expert.
I am willing to test - I have a p660
Christof
=2D-=20
() ascii ribbon campaign - against html e-mail=20
/\ www.asciiribbon.org - against proprietary attachments
--nextPart1672159.SyiLE4VSCt
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEABECAAYFAkuWuK0ACgkQpZfyPAmdZJnpbACfQ5ZmbrpiucqC5F/eZSt19srW
k5cAoI+TZEW/4q0CH3o5hUdtTxSjotNv
=ioUi
-----END PGP SIGNATURE-----
--nextPart1672159.SyiLE4VSCt--
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 21:21:45 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 628EE1065672;
Tue, 9 Mar 2010 21:21:45 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152])
by mx1.freebsd.org (Postfix) with ESMTP id B75068FC17;
Tue, 9 Mar 2010 21:21:44 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id d23so451299fga.13
for <multiple recipients>; Tue, 09 Mar 2010 13:21:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=w2uGspoMC1I6fCIIauokHZPXSsyZIx3qf19GDhvvGuA=;
b=F995oupBT3MFPgdrRG5odXO8qDnUWLmDG0jPjwDLleo7F3qoFn9yc4Cfb49WrzBi8R
aYLhjpDO55L58aXgv+53wLkMn5cf/+iq5wuAq76YxenrgXa6rsfYP6ttkksZWM/a9OVy
uURuRnthGxus7HlSIpVz4WRLxLGb0H4YpaQuc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=DVqkVQsQDZBUNG021t4rcWm/ybgtdyembyhAeiRs8atw2AkrvRsfjGughUBAgj3y/Y
JFbN3mpulzsjv2cQqz8HsdRbjgk40kZ/HA/2/YWnbE6mv6+u/Df10+PZ/FZGI4GQTq9b
tALkJQULAp73SbH+V73EIrosQBrzk/UF3ohx4=
Received: by 10.87.73.13 with SMTP id a13mr1150624fgl.44.1268169703322;
Tue, 09 Mar 2010 13:21:43 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id e11sm8761802fga.6.2010.03.09.13.21.40
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Tue, 09 Mar 2010 13:21:42 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Tue, 9 Mar 2010 13:21:39 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Tue, 9 Mar 2010 13:21:39 -0800
To: Ian FREISLICH <ianf@clue.co.za>
Message-ID: <20100309212139.GO1311@michelle.cdnetworks.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1Noulp-0007Rc-Ro@clue.co.za>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org, David Christensen <davidch@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 21:21:45 -0000
On Tue, Mar 09, 2010 at 10:26:29AM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > patch can fix the RX issue you're suffering from. Anyway, would you
> > give it try the patch at the following URL?
> > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > The patch was generated against CURRENT and you may see a message
> > like "Disabling COAL_NOW timedout!" during interface up. You can
> > ignore that message.
>
> It's been running for about 1:23 on the patched driver. I'm still
> seeing the com_no_buffers increase:
>
> [firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
> dev.bce.0.com_no_buffers: 5642
> dev.bce.1.com_no_buffers: 497
> dev.bce.2.com_no_buffers: 6260612
> dev.bce.3.com_no_buffers: 4871338
>
Still have no idea why these counters are increasing here.
Actually the counter is read from scratch pad of completion
processor. The datasheet does not even document the counter.
Maybe david know better what's happening here(CCed).
> Interupt rate is down now, at about 3500 per second per interface.
>
> Interestingly setting net.inet.ip.fastforwarding=0 reduces CPU
> consumption from 25% to 9% and less packet loss.
>
> Ian
>
> --
> Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 21:40:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 78E7E10656BC;
Tue, 9 Mar 2010 21:40:19 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155])
by mx1.freebsd.org (Postfix) with ESMTP id C9C9F8FC08;
Tue, 9 Mar 2010 21:40:18 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id d23so458404fga.13
for <multiple recipients>; Tue, 09 Mar 2010 13:40:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=CLnR4t5yHelh7sLyp37niy9S+u1I81d++Lp+eK/7v4s=;
b=XppaxkADOA0u++EQLdTFdw6QekJqoAwpQ6D9J3AaqdOZQGGnHdWzkATeR7Nm5KEDyj
T/zEdrtEL5pzukoajvMpldvu29X2l8q+mxx/Q2J8hj00wDtnqOiM2FCe1IwWhWafUgWK
HL5768vi30REuMXAF90f4Hmu4RkAUiY9S/VjY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=UQnBfP9CsIEP1m4nXsG7qJso7doXKNpKP+SEz5WIhpAyjtLmMDkyU31J5bdGoin9/E
kWuvEsRoATvIjY2I7pPtgn3w8NtKNVVtPfXEjl3iRSfH8jO0IcCwyyB6RYjOhp87cSgK
ejK0M7nIHLtuEUdQdjK3TGgi2UncpmWl+fljY=
Received: by 10.87.40.12 with SMTP id s12mr1203590fgj.38.1268170817061;
Tue, 09 Mar 2010 13:40:17 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id d8sm8792326fga.19.2010.03.09.13.40.14
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Tue, 09 Mar 2010 13:40:16 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Tue, 9 Mar 2010 13:40:13 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Tue, 9 Mar 2010 13:40:13 -0800
To: David Christensen <davidch@broadcom.com>
Message-ID: <20100309214012.GQ1311@michelle.cdnetworks.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
User-Agent: Mutt/1.4.2.3i
Cc: Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>,
David Christensen <davidch@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 21:40:19 -0000
On Tue, Mar 09, 2010 at 01:31:55PM -0800, David Christensen wrote:
> > > > patch can fix the RX issue you're suffering from. Anyway,
> > would you
> > > > give it try the patch at the following URL?
> > > > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > > > The patch was generated against CURRENT and you may see a message
> > > > like "Disabling COAL_NOW timedout!" during interface up. You can
> > > > ignore that message.
> > >
> > > It's been running for about 1:23 on the patched driver. I'm still
> > > seeing the com_no_buffers increase:
> > >
> > > [firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
> > > dev.bce.0.com_no_buffers: 5642
> > > dev.bce.1.com_no_buffers: 497
> > > dev.bce.2.com_no_buffers: 6260612
> > > dev.bce.3.com_no_buffers: 4871338
> > >
> >
> > Still have no idea why these counters are increasing here.
> > Actually the counter is read from scratch pad of completion
> > processor. The datasheet does not even document the counter.
> > Maybe david know better what's happening here(CCed).
> >
> > > Interupt rate is down now, at about 3500 per second per interface.
> > >
> > > Interestingly setting net.inet.ip.fastforwarding=0 reduces CPU
> > > consumption from 25% to 9% and less packet loss.
>
> The com_no_buffers statistic comes from firmware and indicates how
> many times a valid frame was received but could not be placed into
> the receive chain because there were no available RX buffers. The
> firmware will then drop the frame but that dropped frame won't be
> reflected in any of the hardware based statistics.
>
Yeah, but the question is why bce(4) has no available RX buffers.
The system has a lot of available mbufs so I don't see the root
cause here.
> Dave
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 21:46:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E79AE1065675;
Tue, 9 Mar 2010 21:46:19 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17])
by mx1.freebsd.org (Postfix) with ESMTP id B8B2B8FC13;
Tue, 9 Mar 2010 21:46:19 +0000 (UTC)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Tue, 09 Mar 2010 13:31:56 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Tue, 9
Mar 2010 13:31:56 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "pyunyh@gmail.com" <pyunyh@gmail.com>,
"Ian FREISLICH" <ianf@clue.co.za>
Date: Tue, 9 Mar 2010 13:31:55 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: Acq/zpF0ZHFVHAVzSZyaqLAYjZ2tvgAANqMQ
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
In-Reply-To: <20100309212139.GO1311@michelle.cdnetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 678861C620S53417274-01-01
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "current@freebsd.org" <current@freebsd.org>,
David Christensen <davidch@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 21:46:20 -0000
> > > patch can fix the RX issue you're suffering from. Anyway,=20
> would you=20
> > > give it try the patch at the following URL?
> > > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > > The patch was generated against CURRENT and you may see a message=20
> > > like "Disabling COAL_NOW timedout!" during interface up. You can=20
> > > ignore that message.
> >=20
> > It's been running for about 1:23 on the patched driver. I'm still=20
> > seeing the com_no_buffers increase:
> >=20
> > [firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
> > dev.bce.0.com_no_buffers: 5642
> > dev.bce.1.com_no_buffers: 497
> > dev.bce.2.com_no_buffers: 6260612
> > dev.bce.3.com_no_buffers: 4871338
> >=20
>=20
> Still have no idea why these counters are increasing here.
> Actually the counter is read from scratch pad of completion=20
> processor. The datasheet does not even document the counter.
> Maybe david know better what's happening here(CCed).
>=20
> > Interupt rate is down now, at about 3500 per second per interface.
> >=20
> > Interestingly setting net.inet.ip.fastforwarding=3D0 reduces CPU=20
> > consumption from 25% to 9% and less packet loss.
The com_no_buffers statistic comes from firmware and indicates how
many times a valid frame was received but could not be placed into
the receive chain because there were no available RX buffers. The
firmware will then drop the frame but that dropped frame won't be
reflected in any of the hardware based statistics.
Dave=
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 21:55:35 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 929951065676
for <current@freebsd.org>; Tue, 9 Mar 2010 21:55:35 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 1C4138FC13
for <current@freebsd.org>; Tue, 9 Mar 2010 21:55:34 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1Np7Ol-0008Ud-Hb; Tue, 09 Mar 2010 23:55:31 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1Np7Ok-000Gpl-FE; Tue, 09 Mar 2010 23:55:30 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100309204927.GN1311@michelle.cdnetworks.com>
References: <20100309204927.GN1311@michelle.cdnetworks.com>
<20100305215539.GG14818@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za> <E1NozXP-000GGH-T9@clue.co.za>
X-Attribution: BOFH
Date: Tue, 09 Mar 2010 23:55:30 +0200
Message-Id: <E1Np7Ok-000Gpl-FE@clue.co.za>
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 21:55:35 -0000
Pyun YongHyeon wrote:
> On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> > Can you explain the tunables please - I'm guessing it's these:
I think I asked the wrong question. What is a "Quick BD Chain"?
What relation should this number have to traffic rate. Is there a
maximum and what are reasonable numbers for setting this to?
I set the RX as high as 512 in 64 quanta but it made little difference
to the interrupt rate. At times where we experience the packet
loss and com_no_buffers increases, the interrupt rate on between 1
and 3 of the 4 bce interfaces fell from about 3200/s to 130/s.
We're wondering if the switches we're using could be causing this
problem - they're Dell PowerConnect 5448. I've seen complaints of
random packet loss caused by these switches on the Internet. We
have some new H3C 5100 series switches which we're planning on
swapping for the Dells tomorrow to see if it makes a difference.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 22:07:28 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 029ED106566B;
Tue, 9 Mar 2010 22:07:28 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17])
by mx1.freebsd.org (Postfix) with ESMTP id C5DA48FC18;
Tue, 9 Mar 2010 22:07:27 +0000 (UTC)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Tue, 09 Mar 2010 14:04:58 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Tue, 9
Mar 2010 14:04:57 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "pyunyh@gmail.com" <pyunyh@gmail.com>
Date: Tue, 9 Mar 2010 14:04:57 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: Acq/0SUjKGwie/fPR2uZKx1IeUMCyQAAD6Xg
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
In-Reply-To: <20100309214012.GQ1311@michelle.cdnetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6788198020S53434302-01-01
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>,
David Christensen <davidch@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 22:07:28 -0000
> > > > It's been running for about 1:23 on the patched driver.=20
> I'm still=20
> > > > seeing the com_no_buffers increase:
> > > >=20
> > > > [firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
> > > > dev.bce.0.com_no_buffers: 5642
> > > > dev.bce.1.com_no_buffers: 497
> > > > dev.bce.2.com_no_buffers: 6260612
> > > > dev.bce.3.com_no_buffers: 4871338
> > > >=20
> > >=20
> > > Still have no idea why these counters are increasing here.
> > > Actually the counter is read from scratch pad of completion=20
> > > processor. The datasheet does not even document the counter.
> > > Maybe david know better what's happening here(CCed).
> > >=20
> > > > Interupt rate is down now, at about 3500 per second per=20
> interface.
> > > >=20
> > > > Interestingly setting net.inet.ip.fastforwarding=3D0 reduces CPU=20
> > > > consumption from 25% to 9% and less packet loss.
> >=20
> > The com_no_buffers statistic comes from firmware and indicates how=20
> > many times a valid frame was received but could not be=20
> placed into the=20
> > receive chain because there were no available RX buffers. The=20
> > firmware will then drop the frame but that dropped frame won't be=20
> > reflected in any of the hardware based statistics.
> >=20
>=20
> Yeah, but the question is why bce(4) has no available RX buffers.
> The system has a lot of available mbufs so I don't see the=20
> root cause here.
What's the traffic look like? Jumbo, standard, short frames? Any=20
good ideas on profiling the code? I haven't figured out how to use
the CPU TSC but there is a free running timer on the device that
might be usable to calculate where the driver's time is spent.
Dave=
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 22:12:45 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BD0E91065670
for <current@freebsd.org>; Tue, 9 Mar 2010 22:12:45 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154])
by mx1.freebsd.org (Postfix) with ESMTP id 454C48FC1D
for <current@freebsd.org>; Tue, 9 Mar 2010 22:12:44 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id 22so2414583fge.13
for <current@freebsd.org>; Tue, 09 Mar 2010 14:12:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=qRInxI3uBxuYToIsvhp5NsFaabm64s4LODWNIYm81W8=;
b=MaqHlKH0oakWoYLL2oX6Z9mt/8sZ8jSAgbKJt5fqohiia73hHdQxM9kaqpMV9elPrW
0h9aObEv0ejrHMknDNUAGMNSsI/ye1L+hnxBX7sdNbtq3X4SrMIJD9RP5nDoQ176DGJn
Yl39j/MLn+3uosAW78A6f8FAYX4N1nV+Lp33A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=LuLcUq9O4fBmrhpm2/kZFJglogiI2ppT40kKX46g72HzYgCNlwmcDW2KuQlODkXQKa
xu5Y9MgKB4ywBXC6aatHUTCZIKD86w4VOD1KaNvhCJf2GIhhZxioU+E4kx03Xf5iJCmq
7GRC/Ru8RcEg5/ZuAvAK9CVhGWDPoTpfPrKDw=
Received: by 10.87.40.24 with SMTP id s24mr1242290fgj.48.1268172764110;
Tue, 09 Mar 2010 14:12:44 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id e20sm8882829fga.20.2010.03.09.14.12.41
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Tue, 09 Mar 2010 14:12:42 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Tue, 9 Mar 2010 14:12:40 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Tue, 9 Mar 2010 14:12:40 -0800
To: Ian FREISLICH <ianf@clue.co.za>
Message-ID: <20100309221240.GR1311@michelle.cdnetworks.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za> <E1NozXP-000GGH-T9@clue.co.za>
<E1Np7Ok-000Gpl-FE@clue.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1Np7Ok-000Gpl-FE@clue.co.za>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 22:12:45 -0000
On Tue, Mar 09, 2010 at 11:55:30PM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> > > Can you explain the tunables please - I'm guessing it's these:
>
> I think I asked the wrong question. What is a "Quick BD Chain"?
I don't know why Broadocom uses 'Quick'. It's a just buffer
descriptor chain for TX/RX.
> What relation should this number have to traffic rate. Is there a
> maximum and what are reasonable numbers for setting this to?
>
The maximum BD chain would be number of configured TX/RX descriptors.
And 1 would be minimum value as you have to want to get status block
for each TX/RX. Finding best value may depend on specific load.
> I set the RX as high as 512 in 64 quanta but it made little difference
> to the interrupt rate. At times where we experience the packet
> loss and com_no_buffers increases, the interrupt rate on between 1
> and 3 of the 4 bce interfaces fell from about 3200/s to 130/s.
>
BD chain is just one of parameters. bce(4) controllers also provide
more advanced features that fine control interrupt moderation(TX/RX
ticks). It's hard to explain all the details so you may want to
read public data sheet of bce(4).
http://www.broadcom.com/collateral/pg/NetXtremeII-PG203-R.pdf
See host coalescing registers(page 484).
> We're wondering if the switches we're using could be causing this
> problem - they're Dell PowerConnect 5448. I've seen complaints of
> random packet loss caused by these switches on the Internet. We
> have some new H3C 5100 series switches which we're planning on
> swapping for the Dells tomorrow to see if it makes a difference.
>
Not sure but it does not explain increasing
dev.bce.X.com_no_buffers counter.
> Ian
>
> --
> Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 22:30:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3D8E71065678
for <current@freebsd.org>; Tue, 9 Mar 2010 22:30:54 +0000 (UTC)
(envelope-from rysto32@gmail.com)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25])
by mx1.freebsd.org (Postfix) with ESMTP id BE2278FC1C
for <current@freebsd.org>; Tue, 9 Mar 2010 22:30:53 +0000 (UTC)
Received: by ey-out-2122.google.com with SMTP id 25so1018739eya.9
for <current@freebsd.org>; Tue, 09 Mar 2010 14:30:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=24I3KUzNMSaDnKvp1ygv44Yu54lZlb0IKpVetor0Zzs=;
b=mgVDZIl0JNAHuz8geOK5skqoOrN/JF5uOwMcFiSO03jIe43aHMb7gtFwQUObYJklue
CfN7P6gLNAPnTRTH/TE2LzzWRjGRKB4H/ZajvB0odvZOIQsyTi6v4yUnejgmJPlSYqq7
9Cv+eNclNuLmwj5AWsAiQinjwttZyhizPQ3+8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=J7VCpsarMFbBeEFHOK1ikxqFCx89AOlIFEGQ+riZK3FAzh4way4ntE00Gv84BeWz5B
Uf1JUSzow2cFyzRC3G/PQd+XG1BS5PevBb5Fu+eSbqvYR2Ax6sP2LskoU6WKWoKnuRpA
6nTOvTpe4zP/Ki32yumdZxdVG7WYxN296xCQI=
MIME-Version: 1.0
Received: by 10.213.57.10 with SMTP id a10mr289231ebh.92.1268173852234; Tue,
09 Mar 2010 14:30:52 -0800 (PST)
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
Date: Tue, 9 Mar 2010 17:30:52 -0500
Message-ID: <bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
From: Ryan Stone <rysto32@gmail.com>
To: David Christensen <davidch@broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 22:30:54 -0000
> What's the traffic look like? =A0Jumbo, standard, short frames? =A0Any
> good ideas on profiling the code? =A0I haven't figured out how to use
> the CPU TSC but there is a free running timer on the device that
> might be usable to calculate where the driver's time is spent.
>
> Dave
In my experience hwpmc is the best and easiest way to profile anything
on FreeBSD. Here's something I sent to a different thread a couple of
months ago explaining how to use it:
1) If device hwpmc is not compiled into your kernel, kldload hwpmc(you
will need the HWPMC_HOOKS option in either case)
2) Run pmcstat to begin taking samples(make sure that whatever you are
profiling is busy doing work first!):
pmcstat -S unhalted-cycles -O /tmp/samples.out
The -S option specifies what event you want to use to trigger
sampling. The unhalted-cycles is the best event to use if your
hardware supports it; pmc will take a sample every 64K non-idle CPU
cycles, which is basically equivalent to sampling based on time. If
the unhalted-cycles event is not supported by your hardware then the
instructions event will probably be the next best choice(although it's
nowhere near as good, as it will not be able to tell you, for example,
if a particular function is very expensive because it takes a lot of
cache misses compared to the rest of your program). One caveat with
the unhalted-cycles event is that time spent spinning on a spinlock or
adaptively spinning on a MTX_DEF mutex will not be counted by this
event, because most of the spinning time is spent executing an hlt
instruction that idles the CPU for a short period of time.
Modern Intel and AMD CPUs offer a dizzying array of events. They're
mostly only useful if you suspect that a particular kind of event is
hurting your performance and you would like to know what is causing
those events. For example, if you suspect that data cache misses are
causing you problems you can take samples on cache misses.
Unfortunately on some of the newer CPUs(namely the Core2 family,
because that's what I'm doing most of my profiling on nowadays) I find
it difficult to figure out just what event to use to profile based on
cache misses. man pmc will give you an overview of pmc, and there are
manpages for every CPU family supported(eg man pmc.core2)
3) After you've run pmcstat for "long enough"(a proper definition of
long enough requires a statistician, which I most certainly am not,
but I find that for a busy system 10 seconds is enough), Control-C it
to stop it*. You can use pmcstat to post-process the samples into
human-readable text:
pmcstat -R /tmp/samples.out -G /tmp/graph.txt
The graph.txt file will show leaf functions on the left and their
callers beneath them, indented to reflect the callchain. It's not too
easy to describe and I don't have sample output available right now.
Another interesting tool for post-processing the samples is
pmcannotate. I've never actually used the tool before but it will
annotate the program's source to show which lines are the most
expensive. This of course needs unstripped modules to work. I think
that it will also work if the GNU "debug link" is in the stripped
module pointing to the location of the file with symbols.
* Here's a tip I picked up from Joseph Koshy's blog: to collect
samples for a fixed period of time(say 1 minute), have pmcstat run the
sleep command:
pmcstat -S unhalted-cycles -O /tmp/samples.out sleep 60
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 23:00:54 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DF51410656C4
for <current@freebsd.org>; Tue, 9 Mar 2010 23:00:54 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19])
by mx1.freebsd.org (Postfix) with ESMTP id B5B338FC19
for <current@freebsd.org>; Tue, 9 Mar 2010 23:00:54 +0000 (UTC)
Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Tue, 09 Mar 2010 15:00:40 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Tue, 9
Mar 2010 15:02:04 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "Ryan Stone" <rysto32@gmail.com>
Date: Tue, 9 Mar 2010 15:00:39 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: Acq/2EehDutlU8bKSFe+fo5qyfRDxAAA29Dw
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933AF90EEE0E@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
<bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
In-Reply-To: <bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67880C9231G54894420-01-01
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 23:00:55 -0000
=20
> -----Original Message-----
> From: Ryan Stone [mailto:rysto32@gmail.com]=20
> Sent: Tuesday, March 09, 2010 2:31 PM
> To: David Christensen
> Cc: pyunyh@gmail.com; Ian FREISLICH; current@freebsd.org
> Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
>=20
> > What's the traffic look like? =A0Jumbo, standard, short frames? =A0Any=
=20
> > good ideas on profiling the code? =A0I haven't figured out how to use=20
> > the CPU TSC but there is a free running timer on the device=20
> that might=20
> > be usable to calculate where the driver's time is spent.
> >
> > Dave
>=20
> In my experience hwpmc is the best and easiest way to profile=20
> anything on FreeBSD. Here's something I sent to a different=20
> thread a couple of months ago explaining how to use it:
>=20
> 1) If device hwpmc is not compiled into your kernel, kldload=20
> hwpmc(you will need the HWPMC_HOOKS option in either case)
> 2) Run pmcstat to begin taking samples(make sure that=20
> whatever you are profiling is busy doing work first!):
>=20
> pmcstat -S unhalted-cycles -O /tmp/samples.out
>=20
> The -S option specifies what event you want to use to trigger=20
> sampling. The unhalted-cycles is the best event to use if=20
> 3) After you've run pmcstat for "long enough"(a proper=20
> definition of long enough requires a statistician, which I=20
> most certainly am not, but I find that for a busy system 10=20
> seconds is enough), Control-C it to stop it*. You can use=20
> pmcstat to post-process the samples into human-readable text:
>=20
> pmcstat -R /tmp/samples.out -G /tmp/graph.txt
>=20
> The graph.txt file will show leaf functions on the left and=20
> their callers beneath them, indented to reflect the=20
> callchain. It's not too easy to describe and I don't have=20
> sample output available right now.
Below is a quick sample I obtained running netperf. We're=20
interested in the bce(4) driver so I assume I'm interested
in the time spent in bce and the functions it calls. Looks
to me like memory allocation/freeing is a major source of
CPU cycles in this test. Am I reading this right?
@ CPU_CLK_UNHALTED_CORE [1091924 samples]
49.25% [537739] sched_idletd @ /boot/kernel/kernel
100.0% [537739] fork_exit
20.89% [228070] trash_dtor @ /boot/kernel/kernel
85.45% [194883] mb_dtor_clust
100.0% [194883] uma_zfree_arg
100.0% [194883] mb_free_ext
14.55% [33186] mb_dtor_mbuf
100.0% [33186] uma_zfree_arg
84.27% [27966] mb_free_ext
15.73% [5220] m_freem
00.00% [1] mb_dtor_pack
100.0% [1] uma_zfree_arg
100.0% [1] mb_free_ext
02.34% [25542] bce_intr @ /boot/kernel/if_bce.ko
100.0% [25542] intr_event_execute_handlers @ /boot/kernel/kernel
100.0% [25542] ithread_loop
100.0% [25542] fork_exit
02.20% [24055] trash_ctor @ /boot/kernel/kernel
96.41% [23192] mb_ctor_clust
100.0% [23192] uma_zalloc_arg
100.0% [23192] bce_fill_rx_chain @ /boot/kernel/if_bce.ko
03.39% [815] mb_ctor_mbuf @ /boot/kernel/kernel
100.0% [815] uma_zalloc_arg
99.39% [810] bce_fill_rx_chain @ /boot/kernel/if_bce.ko
00.49% [4] m_copym @ /boot/kernel/kernel
00.12% [1] tcp_output
00.20% [48] uma_zalloc_arg
100.0% [48] bce_fill_rx_chain @ /boot/kernel/if_bce.ko
100.0% [48] bce_intr
Dave=
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 23:08:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C8798106564A
for <current@freebsd.org>; Tue, 9 Mar 2010 23:08:15 +0000 (UTC)
(envelope-from rysto32@gmail.com)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com
[209.85.219.228])
by mx1.freebsd.org (Postfix) with ESMTP id 574AD8FC08
for <current@freebsd.org>; Tue, 9 Mar 2010 23:08:15 +0000 (UTC)
Received: by ewy28 with SMTP id 28so2085110ewy.13
for <current@freebsd.org>; Tue, 09 Mar 2010 15:08:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=IjhSRp1ujCL+salTXk8MVh+FW2j7WPGY3OBPrnsZQIc=;
b=LCZTSoHWTA6nmmvQjmGdMgD/eTjWIoV9xel4rVFtn0Kclo8gXrnMsTjB75EuLiyA1e
rxiP+NTdiusUDJgyHJnfy3s3+8QXSWLNFxbBvUxh8xeuCsURzifXO3t6f/IqpQpCXqKc
6ryfi8+Qqnh/5HUT2mjQyTcT7C7CiL4fSWNy4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=ELjKLB6DBfThcbKtKf3UH1Z+1fIAl0vlLKSOsj010I8n69gl4vEXTqz+uvHpPLl4a1
6eAi/1hmkG4f+AoRMG99bDnKy1PmGUWYZ5aYBr3l5QEMBV7W+AqxB+ZX1iY3I4CTY25e
u2Zm2UPE4SliVeiQKM2juCW52gwA34XoZEtrA=
MIME-Version: 1.0
Received: by 10.213.75.134 with SMTP id y6mr351087ebj.48.1268176093850; Tue,
09 Mar 2010 15:08:13 -0800 (PST)
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EEE0E@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<E1Nnc4d-0003mB-6e@clue.co.za> <E1Nne0Q-0003uZ-OR@clue.co.za>
<E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
<bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EEE0E@IRVEXCHCCR01.corp.ad.broadcom.com>
Date: Tue, 9 Mar 2010 18:08:13 -0500
Message-ID: <bc2d971003091508i5fbd0999p69476897abefcdbb@mail.gmail.com>
From: Ryan Stone <rysto32@gmail.com>
To: David Christensen <davidch@broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 23:08:15 -0000
trash_ctor and trash_dtor? You're running with INVARIANTS.
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 23:10:55 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9C67D106566B
for <current@freebsd.org>; Tue, 9 Mar 2010 23:10:55 +0000 (UTC)
(envelope-from fabien.thomas@netasq.com)
Received: from work.netasq.com (gateway.netasq.com [91.212.116.2])
by mx1.freebsd.org (Postfix) with ESMTP id 26A168FC19
for <current@freebsd.org>; Tue, 9 Mar 2010 23:10:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by work.netasq.com (Postfix) with ESMTP id 4948A32720C3;
Tue, 9 Mar 2010 23:55:10 +0100 (CET)
X-Virus-Scanned: amavisd-new at netasq.com
Received: from work.netasq.com ([127.0.0.1])
by localhost (work.netasq.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id wZpRUY8FATfd; Tue, 9 Mar 2010 23:55:09 +0100 (CET)
Received: from [192.168.0.1] (unknown [10.0.0.126])
by work.netasq.com (Postfix) with ESMTPSA id 7684232720B4;
Tue, 9 Mar 2010 23:55:09 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Fabien Thomas <fabien.thomas@netasq.com>
In-Reply-To: <bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
Date: Tue, 9 Mar 2010 23:55:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDAEC324-1741-4503-B94A-FE7551442E3A@netasq.com>
References: <20100305210435.GF14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
<bc2d971003091430g236806edy4cf3bb873665fc5@mail.gmail.com>
To: David Christensen <davidch@broadcom.com>
X-Mailer: Apple Mail (2.1077)
Cc: pyunyh@gmail.com, Ian FREISLICH <ianf@clue.co.za>,
Ryan Stone <rysto32@gmail.com>, current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 23:10:55 -0000
If you are on head/stable_7/stable_8 you can also do quick test with top =
mode pmcstat -S unhalted-cycles -T =
(http://wiki.freebsd.org/PmcTools/PmcTop).
For more in depth post processing with source code (c+asm) you can =
output to Kcachegrind (http://wiki.freebsd.org/PmcTools/PmcKcachegrind).
Fabien
>> What's the traffic look like? Jumbo, standard, short frames? Any
>> good ideas on profiling the code? I haven't figured out how to use
>> the CPU TSC but there is a free running timer on the device that
>> might be usable to calculate where the driver's time is spent.
>>=20
>> Dave
>=20
> In my experience hwpmc is the best and easiest way to profile anything
> on FreeBSD. Here's something I sent to a different thread a couple of
> months ago explaining how to use it:
>=20
> 1) If device hwpmc is not compiled into your kernel, kldload hwpmc(you
> will need the HWPMC_HOOKS option in either case)
> 2) Run pmcstat to begin taking samples(make sure that whatever you are
> profiling is busy doing work first!):
>=20
> pmcstat -S unhalted-cycles -O /tmp/samples.out
>=20
> The -S option specifies what event you want to use to trigger
> sampling. The unhalted-cycles is the best event to use if your
> hardware supports it; pmc will take a sample every 64K non-idle CPU
> cycles, which is basically equivalent to sampling based on time. If
> the unhalted-cycles event is not supported by your hardware then the
> instructions event will probably be the next best choice(although it's
> nowhere near as good, as it will not be able to tell you, for example,
> if a particular function is very expensive because it takes a lot of
> cache misses compared to the rest of your program). One caveat with
> the unhalted-cycles event is that time spent spinning on a spinlock or
> adaptively spinning on a MTX_DEF mutex will not be counted by this
> event, because most of the spinning time is spent executing an hlt
> instruction that idles the CPU for a short period of time.
>=20
> Modern Intel and AMD CPUs offer a dizzying array of events. They're
> mostly only useful if you suspect that a particular kind of event is
> hurting your performance and you would like to know what is causing
> those events. For example, if you suspect that data cache misses are
> causing you problems you can take samples on cache misses.
> Unfortunately on some of the newer CPUs(namely the Core2 family,
> because that's what I'm doing most of my profiling on nowadays) I find
> it difficult to figure out just what event to use to profile based on
> cache misses. man pmc will give you an overview of pmc, and there are
> manpages for every CPU family supported(eg man pmc.core2)
>=20
> 3) After you've run pmcstat for "long enough"(a proper definition of
> long enough requires a statistician, which I most certainly am not,
> but I find that for a busy system 10 seconds is enough), Control-C it
> to stop it*. You can use pmcstat to post-process the samples into
> human-readable text:
>=20
> pmcstat -R /tmp/samples.out -G /tmp/graph.txt
>=20
> The graph.txt file will show leaf functions on the left and their
> callers beneath them, indented to reflect the callchain. It's not too
> easy to describe and I don't have sample output available right now.
>=20
>=20
> Another interesting tool for post-processing the samples is
> pmcannotate. I've never actually used the tool before but it will
> annotate the program's source to show which lines are the most
> expensive. This of course needs unstripped modules to work. I think
> that it will also work if the GNU "debug link" is in the stripped
> module pointing to the location of the file with symbols.
>=20
>=20
> * Here's a tip I picked up from Joseph Koshy's blog: to collect
> samples for a fixed period of time(say 1 minute), have pmcstat run the
> sleep command:
>=20
> pmcstat -S unhalted-cycles -O /tmp/samples.out sleep 60
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 23:44:38 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DEBAC106566C;
Tue, 9 Mar 2010 23:44:38 +0000 (UTC)
(envelope-from adrenalinup@gmail.com)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id 72CB98FC1B;
Tue, 9 Mar 2010 23:44:37 +0000 (UTC)
Received: by fxm1 with SMTP id 1so4491254fxm.13
for <multiple recipients>; Tue, 09 Mar 2010 15:44:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:cc:content-type;
bh=F5XS+IKR9h0IVhVHDxxnzxBKcfdJl2BJrS1vdf36+1I=;
b=VRiVBt6wgAI1XAqm/Fk8hte8u8GDMHpR9MJ3CXKQXr++8jB6omTQjl82Ux2sgr4WS/
w5RadCd2gXuCWWpTPRGnABHlAno5AUl9brQooyU9uDSXR0QQL1F5DI3NnlWbkFS/THRm
ckhRzVe9xuoYjqbRWmGXVZw69Q95asuAdkCp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
b=IxX7h8dPKr5vxvepWwD7GmvX9YYdaXN6pOb9o7OyJktI87vSxE4YgI7aRGsn5fpCjR
nDAGSJ70u1NJBFnKosHJrFbb9zvkD3SpKkzdPnsm5suVUrXzvtTJ9ihq42ed307VjREl
LxX0yyV5OLD2mlX1U6HZs5fdyd+aXOO4HROWU=
MIME-Version: 1.0
Received: by 10.223.28.156 with SMTP id m28mr622108fac.41.1268176790300; Tue,
09 Mar 2010 15:19:50 -0800 (PST)
In-Reply-To: <Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
From: Adrenalin <adrenalinup@gmail.com>
Date: Wed, 10 Mar 2010 00:19:30 +0100
Message-ID: <f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 23:44:39 -0000
Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
since I got it 3 times already on a busy box that use heavily NFS (with lots
of files).
Unfortunately my processes are not compiled with debug symbols(so I cannot
get an backtrace), but I've got all the php-cgi stuck in the "rpccon" state
just like described here, I cannot kill them and I cannot cleanly reboot,
manual restart is required.
FreeBSD g4.torrentsmd.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21
15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64
4063 www 1 52 0 82576K 26320K rpccon 3 1:40 0.00% php-cgi
4078 www 1 48 0 83600K 26768K rpccon 1 1:37 0.00% php-cgi
4129 www 1 52 0 83600K 26740K rpccon 1 1:31 0.00% php-cgi
4159 www 1 55 0 82832K 26216K rpccon 0 1:24 0.00% php-cgi
4184 www 1 54 0 90768K 34104K rpccon 0 1:16 0.00% php-cgi
4174 www 1 50 0 82832K 23396K rpccon 0 1:15 0.00% php-cgi
4258 www 1 55 0 82064K 24224K rpccon 1 1:06 0.00% php-cgi
I belive the error was triggered when
Mar 9 20:00:31 sv kernel: nfs server s:/path/pah/paf: not responding
Mar 9 20:00:36 sv last message repeated 23 times
My fstab look like this, I use the -b flag
sv:/path/pah/paf /path/fap/hap/afh nfs rw,-b 0 0
Since it's a remote box and I'm afraid to screw up the kernel recompilation
of the "Stable", and I'm not even sure it will help, do you have any
suggestions ? Thank you.
Nicu.
On Mon, Jun 22, 2009 at 2:21 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>
> On Sun, 21 Jun 2009, Kris Kennaway wrote:
>
>
>> Got another deadlock after upgrading. Again, busy NFS volume, and ^C'ing
>> a recursive find hung in rpccon state:
>>
>> db> bt 89596
>> Tracing pid 89596 tid 102493 td 0xffffff0089260000
>> sched_switch() at sched_switch+0x17c
>> mi_switch() at mi_switch+0x21d
>> sleepq_switch() at sleepq_switch+0x123
>> sleepq_timedwait() at sleepq_timedwait+0x4d
>> _sleep() at _sleep+0x301
>> clnt_reconnect_call() at clnt_reconnect_call+0x5d3
>> nfs_request() at nfs_request+0x225
>> nfs_statfs() at nfs_statfs+0x197
>> __vfs_statfs() at __vfs_statfs+0x28
>> kern_fstatfs() at kern_fstatfs+0x286
>> fstatfs() at fstatfs+0x34
>> syscall() at syscall+0x1af
>> Xfast_syscall() at Xfast_syscall+0xd0
>> --- syscall (397, FreeBSD ELF64, fstatfs), rip = 0x800726dcc, rsp =
>> 0x7fffffffe1a8, rbp = 0x1000 ---
>>
>> These are mounted with intr, I'll try disabling that next.
>>
>> There are two sleeps in clnt_rc.c. One of them optionally does a PCATCH
> and returns when interrupted via ^C, but the other one (which it is
> sleeping on above), doesn't. I've emailed Kris a small patch that
> changes that for him to test.
>
> If anyone else wants to test the patch, just email me for a copy, rick
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 23:44:38 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DEBAC106566C;
Tue, 9 Mar 2010 23:44:38 +0000 (UTC)
(envelope-from adrenalinup@gmail.com)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id 72CB98FC1B;
Tue, 9 Mar 2010 23:44:37 +0000 (UTC)
Received: by fxm1 with SMTP id 1so4491254fxm.13
for <multiple recipients>; Tue, 09 Mar 2010 15:44:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:cc:content-type;
bh=F5XS+IKR9h0IVhVHDxxnzxBKcfdJl2BJrS1vdf36+1I=;
b=VRiVBt6wgAI1XAqm/Fk8hte8u8GDMHpR9MJ3CXKQXr++8jB6omTQjl82Ux2sgr4WS/
w5RadCd2gXuCWWpTPRGnABHlAno5AUl9brQooyU9uDSXR0QQL1F5DI3NnlWbkFS/THRm
ckhRzVe9xuoYjqbRWmGXVZw69Q95asuAdkCp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
b=IxX7h8dPKr5vxvepWwD7GmvX9YYdaXN6pOb9o7OyJktI87vSxE4YgI7aRGsn5fpCjR
nDAGSJ70u1NJBFnKosHJrFbb9zvkD3SpKkzdPnsm5suVUrXzvtTJ9ihq42ed307VjREl
LxX0yyV5OLD2mlX1U6HZs5fdyd+aXOO4HROWU=
MIME-Version: 1.0
Received: by 10.223.28.156 with SMTP id m28mr622108fac.41.1268176790300; Tue,
09 Mar 2010 15:19:50 -0800 (PST)
In-Reply-To: <Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
From: Adrenalin <adrenalinup@gmail.com>
Date: Wed, 10 Mar 2010 00:19:30 +0100
Message-ID: <f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2010 23:44:39 -0000
Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
since I got it 3 times already on a busy box that use heavily NFS (with lots
of files).
Unfortunately my processes are not compiled with debug symbols(so I cannot
get an backtrace), but I've got all the php-cgi stuck in the "rpccon" state
just like described here, I cannot kill them and I cannot cleanly reboot,
manual restart is required.
FreeBSD g4.torrentsmd.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21
15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64
4063 www 1 52 0 82576K 26320K rpccon 3 1:40 0.00% php-cgi
4078 www 1 48 0 83600K 26768K rpccon 1 1:37 0.00% php-cgi
4129 www 1 52 0 83600K 26740K rpccon 1 1:31 0.00% php-cgi
4159 www 1 55 0 82832K 26216K rpccon 0 1:24 0.00% php-cgi
4184 www 1 54 0 90768K 34104K rpccon 0 1:16 0.00% php-cgi
4174 www 1 50 0 82832K 23396K rpccon 0 1:15 0.00% php-cgi
4258 www 1 55 0 82064K 24224K rpccon 1 1:06 0.00% php-cgi
I belive the error was triggered when
Mar 9 20:00:31 sv kernel: nfs server s:/path/pah/paf: not responding
Mar 9 20:00:36 sv last message repeated 23 times
My fstab look like this, I use the -b flag
sv:/path/pah/paf /path/fap/hap/afh nfs rw,-b 0 0
Since it's a remote box and I'm afraid to screw up the kernel recompilation
of the "Stable", and I'm not even sure it will help, do you have any
suggestions ? Thank you.
Nicu.
On Mon, Jun 22, 2009 at 2:21 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>
> On Sun, 21 Jun 2009, Kris Kennaway wrote:
>
>
>> Got another deadlock after upgrading. Again, busy NFS volume, and ^C'ing
>> a recursive find hung in rpccon state:
>>
>> db> bt 89596
>> Tracing pid 89596 tid 102493 td 0xffffff0089260000
>> sched_switch() at sched_switch+0x17c
>> mi_switch() at mi_switch+0x21d
>> sleepq_switch() at sleepq_switch+0x123
>> sleepq_timedwait() at sleepq_timedwait+0x4d
>> _sleep() at _sleep+0x301
>> clnt_reconnect_call() at clnt_reconnect_call+0x5d3
>> nfs_request() at nfs_request+0x225
>> nfs_statfs() at nfs_statfs+0x197
>> __vfs_statfs() at __vfs_statfs+0x28
>> kern_fstatfs() at kern_fstatfs+0x286
>> fstatfs() at fstatfs+0x34
>> syscall() at syscall+0x1af
>> Xfast_syscall() at Xfast_syscall+0xd0
>> --- syscall (397, FreeBSD ELF64, fstatfs), rip = 0x800726dcc, rsp =
>> 0x7fffffffe1a8, rbp = 0x1000 ---
>>
>> These are mounted with intr, I'll try disabling that next.
>>
>> There are two sleeps in clnt_rc.c. One of them optionally does a PCATCH
> and returns when interrupted via ^C, but the other one (which it is
> sleeping on above), doesn't. I've emailed Kris a small patch that
> changes that for him to test.
>
> If anyone else wants to test the patch, just email me for a copy, rick
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:41:35 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E4FC6106564A;
Wed, 10 Mar 2010 00:41:35 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 925188FC13;
Wed, 10 Mar 2010 00:41:35 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0fY5t001829; Tue, 9 Mar 2010 19:41:34 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0fYSF001773;
Wed, 10 Mar 2010 00:41:34 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:41:34 GMT
Message-Id: <201003100041.o2A0fYSF001773@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<arm@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on arm/arm
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:41:36 -0000
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for arm/arm
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:16 - cvsupping the source tree
TB --- 2010-03-10 00:40:16 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile
TB --- 2010-03-10 00:40:34 - building world
TB --- 2010-03-10 00:40:34 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:40:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:40:34 - TARGET=arm
TB --- 2010-03-10 00:40:34 - TARGET_ARCH=arm
TB --- 2010-03-10 00:40:34 - TZ=UTC
TB --- 2010-03-10 00:40:34 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:40:34 - cd /src
TB --- 2010-03-10 00:40:34 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:40:34 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:41:34 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:41:34 - ERROR: failed to build world
TB --- 2010-03-10 00:41:34 - 34.23 user 20.68 system 93.66 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:41:40 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0780E106564A;
Wed, 10 Mar 2010 00:41:40 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id ABAAE8FC16;
Wed, 10 Mar 2010 00:41:39 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0fdTF003927; Tue, 9 Mar 2010 19:41:39 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0fdPN003905;
Wed, 10 Mar 2010 00:41:39 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:41:39 GMT
Message-Id: <201003100041.o2A0fdPN003905@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<i386@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on i386/i386
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:41:40 -0000
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for i386/i386
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:27 - cvsupping the source tree
TB --- 2010-03-10 00:40:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile
TB --- 2010-03-10 00:40:51 - building world
TB --- 2010-03-10 00:40:51 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:40:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:40:51 - TARGET=i386
TB --- 2010-03-10 00:40:51 - TARGET_ARCH=i386
TB --- 2010-03-10 00:40:51 - TZ=UTC
TB --- 2010-03-10 00:40:51 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:40:51 - cd /src
TB --- 2010-03-10 00:40:51 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:40:51 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:41:39 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:41:39 - ERROR: failed to build world
TB --- 2010-03-10 00:41:39 - 35.09 user 25.30 system 98.15 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:41:40 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2E52A106566C;
Wed, 10 Mar 2010 00:41:40 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id ECDD98FC12;
Wed, 10 Mar 2010 00:41:39 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0fdPK003969; Tue, 9 Mar 2010 19:41:39 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0fdcI003956;
Wed, 10 Mar 2010 00:41:39 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:41:39 GMT
Message-Id: <201003100041.o2A0fdcI003956@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<i386@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on i386/pc98
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:41:40 -0000
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:25 - cvsupping the source tree
TB --- 2010-03-10 00:40:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile
TB --- 2010-03-10 00:40:51 - building world
TB --- 2010-03-10 00:40:51 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:40:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:40:51 - TARGET=pc98
TB --- 2010-03-10 00:40:51 - TARGET_ARCH=i386
TB --- 2010-03-10 00:40:51 - TZ=UTC
TB --- 2010-03-10 00:40:51 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:40:51 - cd /src
TB --- 2010-03-10 00:40:51 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:40:51 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:41:39 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:41:39 - ERROR: failed to build world
TB --- 2010-03-10 00:41:39 - 34.60 user 24.94 system 98.23 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:41:42 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3F38C106564A;
Wed, 10 Mar 2010 00:41:42 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E32D58FC08;
Wed, 10 Mar 2010 00:41:41 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0ff72004387; Tue, 9 Mar 2010 19:41:41 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0ffiG004386;
Wed, 10 Mar 2010 00:41:41 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:41:41 GMT
Message-Id: <201003100041.o2A0ffiG004386@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<amd64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on amd64/amd64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:41:42 -0000
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:30 - cvsupping the source tree
TB --- 2010-03-10 00:40:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2010-03-10 00:40:53 - building world
TB --- 2010-03-10 00:40:53 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:40:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:40:53 - TARGET=amd64
TB --- 2010-03-10 00:40:53 - TARGET_ARCH=amd64
TB --- 2010-03-10 00:40:53 - TZ=UTC
TB --- 2010-03-10 00:40:53 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:40:53 - cd /src
TB --- 2010-03-10 00:40:53 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:40:54 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:41:41 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:41:41 - ERROR: failed to build world
TB --- 2010-03-10 00:41:41 - 34.98 user 26.48 system 100.39 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:43:05 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 12F181065670;
Wed, 10 Mar 2010 00:43:05 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id B6E548FC29;
Wed, 10 Mar 2010 00:43:04 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0h4sc018370; Tue, 9 Mar 2010 19:43:04 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0h4Mf018345;
Wed, 10 Mar 2010 00:43:04 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:43:04 GMT
Message-Id: <201003100043.o2A0h4Mf018345@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<mips@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on mips/mips
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:43:05 -0000
TB --- 2010-03-10 00:41:39 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:39 - starting HEAD tinderbox run for mips/mips
TB --- 2010-03-10 00:41:39 - cleaning the object tree
TB --- 2010-03-10 00:41:51 - cvsupping the source tree
TB --- 2010-03-10 00:41:51 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile
TB --- 2010-03-10 00:42:12 - building world
TB --- 2010-03-10 00:42:12 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:42:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:42:12 - TARGET=mips
TB --- 2010-03-10 00:42:12 - TARGET_ARCH=mips
TB --- 2010-03-10 00:42:12 - TZ=UTC
TB --- 2010-03-10 00:42:12 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:42:12 - cd /src
TB --- 2010-03-10 00:42:12 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:42:12 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:43:04 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:43:04 - ERROR: failed to build world
TB --- 2010-03-10 00:43:04 - 31.33 user 18.80 system 84.83 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:43:14 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 40DDE1065673;
Wed, 10 Mar 2010 00:43:14 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3008FC1C;
Wed, 10 Mar 2010 00:43:13 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0hDI3023793; Tue, 9 Mar 2010 19:43:13 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0hDY0023773;
Wed, 10 Mar 2010 00:43:13 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:43:13 GMT
Message-Id: <201003100043.o2A0hDY0023773@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<powerpc@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on powerpc/powerpc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:43:14 -0000
TB --- 2010-03-10 00:41:39 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:39 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-03-10 00:41:39 - cleaning the object tree
TB --- 2010-03-10 00:42:06 - cvsupping the source tree
TB --- 2010-03-10 00:42:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile
TB --- 2010-03-10 00:42:20 - building world
TB --- 2010-03-10 00:42:20 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:42:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:42:20 - TARGET=powerpc
TB --- 2010-03-10 00:42:20 - TARGET_ARCH=powerpc
TB --- 2010-03-10 00:42:20 - TZ=UTC
TB --- 2010-03-10 00:42:20 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:42:20 - cd /src
TB --- 2010-03-10 00:42:20 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:42:22 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:43:13 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:43:13 - ERROR: failed to build world
TB --- 2010-03-10 00:43:13 - 34.67 user 23.38 system 94.04 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:43:14 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8C6C7106564A;
Wed, 10 Mar 2010 00:43:14 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3C6738FC1D;
Wed, 10 Mar 2010 00:43:14 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0hDUP023871; Tue, 9 Mar 2010 19:43:13 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0hDD7023864;
Wed, 10 Mar 2010 00:43:13 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:43:13 GMT
Message-Id: <201003100043.o2A0hDD7023864@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<ia64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on ia64/ia64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:43:14 -0000
TB --- 2010-03-10 00:41:35 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:35 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-03-10 00:41:35 - cleaning the object tree
TB --- 2010-03-10 00:41:57 - cvsupping the source tree
TB --- 2010-03-10 00:41:57 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile
TB --- 2010-03-10 00:42:18 - building world
TB --- 2010-03-10 00:42:18 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:42:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:42:18 - TARGET=ia64
TB --- 2010-03-10 00:42:18 - TARGET_ARCH=ia64
TB --- 2010-03-10 00:42:18 - TZ=UTC
TB --- 2010-03-10 00:42:18 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:42:18 - cd /src
TB --- 2010-03-10 00:42:18 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:42:19 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:43:13 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:43:13 - ERROR: failed to build world
TB --- 2010-03-10 00:43:13 - 34.99 user 23.52 system 98.69 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:43:19 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D1317106566C;
Wed, 10 Mar 2010 00:43:19 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 815EC8FC08;
Wed, 10 Mar 2010 00:43:19 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0hJKE025087; Tue, 9 Mar 2010 19:43:19 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0hJl6025086;
Wed, 10 Mar 2010 00:43:19 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:43:19 GMT
Message-Id: <201003100043.o2A0hJl6025086@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<sparc64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on sparc64/sparc64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:43:19 -0000
TB --- 2010-03-10 00:41:41 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:41 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-03-10 00:41:41 - cleaning the object tree
TB --- 2010-03-10 00:42:10 - cvsupping the source tree
TB --- 2010-03-10 00:42:10 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile
TB --- 2010-03-10 00:42:25 - building world
TB --- 2010-03-10 00:42:25 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:42:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:42:25 - TARGET=sparc64
TB --- 2010-03-10 00:42:25 - TARGET_ARCH=sparc64
TB --- 2010-03-10 00:42:25 - TZ=UTC
TB --- 2010-03-10 00:42:25 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:42:25 - cd /src
TB --- 2010-03-10 00:42:25 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:42:26 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:43:18 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:43:18 - ERROR: failed to build world
TB --- 2010-03-10 00:43:18 - 35.17 user 22.98 system 97.35 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 00:44:13 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BFFB5106568E;
Wed, 10 Mar 2010 00:44:13 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 6EFBE8FC2B;
Wed, 10 Mar 2010 00:44:13 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2A0iCTp030504; Tue, 9 Mar 2010 19:44:12 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2A0iCL0030503;
Wed, 10 Mar 2010 00:44:12 GMT (envelope-from tinderbox@freebsd.org)
Date: Wed, 10 Mar 2010 00:44:12 GMT
Message-Id: <201003100044.o2A0iCL0030503@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<sparc64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on sparc64/sun4v
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:44:13 -0000
TB --- 2010-03-10 00:43:04 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:43:04 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-03-10 00:43:04 - cleaning the object tree
TB --- 2010-03-10 00:43:15 - cvsupping the source tree
TB --- 2010-03-10 00:43:15 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile
TB --- 2010-03-10 00:43:30 - building world
TB --- 2010-03-10 00:43:30 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-10 00:43:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-10 00:43:30 - TARGET=sun4v
TB --- 2010-03-10 00:43:30 - TARGET_ARCH=sparc64
TB --- 2010-03-10 00:43:30 - TZ=UTC
TB --- 2010-03-10 00:43:30 - __MAKE_CONF=/dev/null
TB --- 2010-03-10 00:43:30 - cd /src
TB --- 2010-03-10 00:43:30 - /usr/bin/make -B buildworld
>>> World build started on Wed Mar 10 00:43:30 UTC 2010
>>> 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
[...]
===> secure/libexec/sftp-server (cleandir)
rm -f sftp-server sftp-server.o sftp-common.o sftp-server-main.o roaming_dummy.o sftp-server.8.gz sftp-server.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-keysign (cleandir)
rm -f ssh-keysign ssh-keysign.o readconf.o roaming_dummy.o ssh-keysign.8.gz ssh-keysign.8.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/libexec/ssh-pkcs11-helper (cleandir)
cd: can't cd to /src/secure/libexec/ssh-pkcs11-helper
*** Error code 2
Stop in /src/secure/libexec.
*** Error code 1
Stop in /src/secure.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-10 00:44:12 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-10 00:44:12 - ERROR: failed to build world
TB --- 2010-03-10 00:44:12 - 35.91 user 18.12 system 68.53 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 02:00:46 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F2190106564A
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 02:00:46 +0000 (UTC)
(envelope-from dougb@FreeBSD.org)
Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4])
by mx1.freebsd.org (Postfix) with ESMTP id 81AA98FC1A
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 02:00:46 +0000 (UTC)
Received: (qmail 23512 invoked by uid 399); 10 Mar 2010 02:00:45 -0000
Received: from localhost (HELO foreign.dougb.net)
(dougb@dougbarton.us@127.0.0.1)
by localhost with ESMTPAM; 10 Mar 2010 02:00:45 -0000
X-Originating-IP: 127.0.0.1
X-Sender: dougb@dougbarton.us
Message-ID: <4B96FD4B.3090706@FreeBSD.org>
Date: Tue, 09 Mar 2010 18:00:43 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.9.1.7) Gecko/20100218 Thunderbird/3.0.1
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
X-Enigmail-Version: 1.0.1
OpenPGP: id=D5B2F0FB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 02:00:47 -0000
On 03/09/10 12:14, Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> http://people.freebsd.org/~qingli/route.h.diff
This doesn't appear to be committed yet, is it still the best fix?
Doug
--
... and that's just a little bit of history repeating.
-- Propellerheads
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 02:31:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C8BAC106566C;
Wed, 10 Mar 2010 02:31:50 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
[131.104.91.36])
by mx1.freebsd.org (Postfix) with ESMTP id E11308FC18;
Wed, 10 Mar 2010 02:31:49 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKyTlkuDaFvK/2dsb2JhbACbBXO8K4R5BIMX
X-IronPort-AV: E=Sophos;i="4.49,611,1262581200"; d="scan'208";a="68432161"
Received: from fraser.cs.uoguelph.ca ([131.104.91.202])
by esa-annu-pri.mail.uoguelph.ca with ESMTP; 09 Mar 2010 21:31:49 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 7CB74109C2DC;
Tue, 9 Mar 2010 21:31:48 -0500 (EST)
X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca
Received: from fraser.cs.uoguelph.ca ([127.0.0.1])
by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id Tr1OMIR1IjeE; Tue, 9 Mar 2010 21:31:47 -0500 (EST)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102])
by fraser.cs.uoguelph.ca (Postfix) with ESMTP id A4D3F109C2EB;
Tue, 9 Mar 2010 21:31:47 -0500 (EST)
Received: from localhost (rmacklem@localhost)
by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id
o2A2iEw13477; Tue, 9 Mar 2010 21:44:14 -0500 (EST)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing
-bs
Date: Tue, 9 Mar 2010 21:44:14 -0500 (EST)
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: Adrenalin <adrenalinup@gmail.com>
In-Reply-To: <f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 02:31:50 -0000
On Wed, 10 Mar 2010, Adrenalin wrote:
> Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
> since I got it 3 times already on a busy box that use heavily NFS (with lots
> of files).
> Unfortunately my processes are not compiled with debug symbols(so I cannot
> get an backtrace), but I've got all the php-cgi stuck in the "rpccon" state
> just like described here, I cannot kill them and I cannot cleanly reboot,
> manual restart is required.
>
I suspect that what you are seeing is fixed by:
http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch
It is in head and stable/8, but did not make the FreeBSD8.0 release.
I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
rick
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 02:31:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C8BAC106566C;
Wed, 10 Mar 2010 02:31:50 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
[131.104.91.36])
by mx1.freebsd.org (Postfix) with ESMTP id E11308FC18;
Wed, 10 Mar 2010 02:31:49 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKyTlkuDaFvK/2dsb2JhbACbBXO8K4R5BIMX
X-IronPort-AV: E=Sophos;i="4.49,611,1262581200"; d="scan'208";a="68432161"
Received: from fraser.cs.uoguelph.ca ([131.104.91.202])
by esa-annu-pri.mail.uoguelph.ca with ESMTP; 09 Mar 2010 21:31:49 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 7CB74109C2DC;
Tue, 9 Mar 2010 21:31:48 -0500 (EST)
X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca
Received: from fraser.cs.uoguelph.ca ([127.0.0.1])
by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id Tr1OMIR1IjeE; Tue, 9 Mar 2010 21:31:47 -0500 (EST)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102])
by fraser.cs.uoguelph.ca (Postfix) with ESMTP id A4D3F109C2EB;
Tue, 9 Mar 2010 21:31:47 -0500 (EST)
Received: from localhost (rmacklem@localhost)
by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id
o2A2iEw13477; Tue, 9 Mar 2010 21:44:14 -0500 (EST)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing
-bs
Date: Tue, 9 Mar 2010 21:44:14 -0500 (EST)
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: Adrenalin <adrenalinup@gmail.com>
In-Reply-To: <f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 02:31:50 -0000
On Wed, 10 Mar 2010, Adrenalin wrote:
> Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
> since I got it 3 times already on a busy box that use heavily NFS (with lots
> of files).
> Unfortunately my processes are not compiled with debug symbols(so I cannot
> get an backtrace), but I've got all the php-cgi stuck in the "rpccon" state
> just like described here, I cannot kill them and I cannot cleanly reboot,
> manual restart is required.
>
I suspect that what you are seeing is fixed by:
http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch
It is in head and stable/8, but did not make the FreeBSD8.0 release.
I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
rick
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 05:48:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4DB7F106564A
for <current@freebsd.org>; Wed, 10 Mar 2010 05:48:36 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id B39E98FC08
for <current@freebsd.org>; Wed, 10 Mar 2010 05:48:33 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NpEmM-0000cK-Jl; Wed, 10 Mar 2010 07:48:22 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NpEmB-000HID-HK; Wed, 10 Mar 2010 07:48:11 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100309221240.GR1311@michelle.cdnetworks.com>
References: <20100309221240.GR1311@michelle.cdnetworks.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Nnesz-00040L-AQ@clue.co.za>
<E1NoeCu-0006P9-12@clue.co.za> <E1NozXP-000GGH-T9@clue.co.za>
<E1Np7Ok-000Gpl-FE@clue.co.za>
X-Attribution: BOFH
Date: Wed, 10 Mar 2010 07:48:11 +0200
Message-Id: <E1NpEmB-000HID-HK@clue.co.za>
Cc: current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 05:48:36 -0000
Pyun YongHyeon wrote:
> On Tue, Mar 09, 2010 at 11:55:30PM +0200, Ian FREISLICH wrote:
> > I set the RX as high as 512 in 64 quanta but it made little difference
> > to the interrupt rate. At times where we experience the packet
> > loss and com_no_buffers increases, the interrupt rate on between 1
> > and 3 of the 4 bce interfaces fell from about 3200/s to 130/s.
> >
>
> BD chain is just one of parameters. bce(4) controllers also provide
> more advanced features that fine control interrupt moderation(TX/RX
> ticks). It's hard to explain all the details so you may want to
> read public data sheet of bce(4).
Thanks. I'll have a read over that.
I meant to state that above that whenever the interrupt rate on a
controller (or several) falls off, the interrupt CPU usage climbs
from about 4% to about 20%. So it seems like something is happening
on host that jams up interrupt processing.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 09:05:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5CF7F1065670
for <current@freebsd.org>; Wed, 10 Mar 2010 09:05:32 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id CFD5B8FC08
for <current@freebsd.org>; Wed, 10 Mar 2010 09:05:30 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NpHr5-0005nO-Ps; Wed, 10 Mar 2010 11:05:27 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NpHr0-000HWT-It; Wed, 10 Mar 2010 11:05:22 +0200
To: "David Christensen" <davidch@broadcom.com>
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
X-Attribution: BOFH
Date: Wed, 10 Mar 2010 11:05:22 +0200
Message-Id: <E1NpHr0-000HWT-It@clue.co.za>
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 09:05:32 -0000
"David Christensen" wrote:
> > Yeah, but the question is why bce(4) has no available RX buffers.
> > The system has a lot of available mbufs so I don't see the=20
> > root cause here.
>
> What's the traffic look like? Jumbo, standard, short frames? Any=20
> good ideas on profiling the code? I haven't figured out how to use
> the CPU TSC but there is a free running timer on the device that
> might be usable to calculate where the driver's time is spent.
It looks like the traffic that provoked it was this:
10:18:42.319370 IP X.4569 > X.4569: UDP, length 12
10:18:42.319402 IP X.4569 > X.4569: UDP, length 12
10:18:42.319438 IP X.4569 > X.4569: UDP, length 12
10:18:42.319484 IP X.4569 > X.4569: UDP, length 12
10:18:42.319517 IP X.4569 > X.4569: UDP, length 12
A flurry of UDP tinygrams on an IAX2 trunk. The packet rate isn't
spectacular at about 30kpps which on top of the base load of 60kpps
still isn't a fantastic packet rate. The interesting thing is that
while this storm was inprogress, it almost entirely excluded other
traffic on the network.
There have been reports of backplane congestion on the switches we
use when UDP packets smaller than 400 bytes arrive within 40us of
eachother. But that still doesn't explain the counter increases
and high interrupt CPU usage, unless the switch was producing garbage
output in response.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 11:38:40 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C0216106566C;
Wed, 10 Mar 2010 11:38:40 +0000 (UTC)
(envelope-from adrenalinup@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 4C5DE8FC1E;
Wed, 10 Mar 2010 11:38:38 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7044710fxm.3
for <multiple recipients>; Wed, 10 Mar 2010 03:38:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:cc:content-type;
bh=8yHYboIcCqFVsfE8zXh32VKlJFsYZRVbdWZoKymEQqc=;
b=kv7rUOVteJubmSC1dA0djd3OB6KgzNRPtNzm/rYF/1OPTRiAh314nur6KY5rleeKLe
estFTD2rAI9V3EwWZpAL4H+T+baUaxD6Z6q8n9I04yboRAdRseQqJpEZoE9t+ir/KyNA
skjZHfBC6cwhSQcFAxVfLb0nrw0sJQ72vC72Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
b=MWsZShpvngNwyB6bzMwHeSp8wj6GI84akWnu8yDQPpAThL8/ZYTeCiVZBazkfmxlaJ
HMNmaN1jp/y9Il/XJWGitwe+7/0XpqcQVF0vXzLUh+3x7QHyspUAllKOAMS4zZ7V+7MM
peutD2LHRWqQlEXXRLAI0qZZQIre+H+02/Vz4=
MIME-Version: 1.0
Received: by 10.223.5.71 with SMTP id 7mr1352657fau.48.1268221118260; Wed, 10
Mar 2010 03:38:38 -0800 (PST)
In-Reply-To: <Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
From: Adrenalin <adrenalinup@gmail.com>
Date: Wed, 10 Mar 2010 12:38:18 +0100
Message-ID: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 11:38:40 -0000
Rick thank you for the answer.
I'll "put my heart into the teeth" and will try to go for the stable.
This is kind of critical I guess, I think it should really go to the
release. It's the first time I got into a such a nasty bug with freebsd.
On Wed, Mar 10, 2010 at 3:44 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>
> On Wed, 10 Mar 2010, Adrenalin wrote:
>
> Hi, I would like to know if this bug has been fixed in the FreeBSD 8
>> Release
>> since I got it 3 times already on a busy box that use heavily NFS (with
>> lots
>> of files).
>> Unfortunately my processes are not compiled with debug symbols(so I cannot
>> get an backtrace), but I've got all the php-cgi stuck in the "rpccon"
>> state
>> just like described here, I cannot kill them and I cannot cleanly reboot,
>> manual restart is required.
>>
>> I suspect that what you are seeing is fixed by:
> http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch<http://people.freebsd.org/%7Ermacklem/patches/freebsd8-clntvc.patch>
>
> It is in head and stable/8, but did not make the FreeBSD8.0 release.
>
> I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
>
> rick
>
>
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 11:38:40 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C0216106566C;
Wed, 10 Mar 2010 11:38:40 +0000 (UTC)
(envelope-from adrenalinup@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 4C5DE8FC1E;
Wed, 10 Mar 2010 11:38:38 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7044710fxm.3
for <multiple recipients>; Wed, 10 Mar 2010 03:38:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:cc:content-type;
bh=8yHYboIcCqFVsfE8zXh32VKlJFsYZRVbdWZoKymEQqc=;
b=kv7rUOVteJubmSC1dA0djd3OB6KgzNRPtNzm/rYF/1OPTRiAh314nur6KY5rleeKLe
estFTD2rAI9V3EwWZpAL4H+T+baUaxD6Z6q8n9I04yboRAdRseQqJpEZoE9t+ir/KyNA
skjZHfBC6cwhSQcFAxVfLb0nrw0sJQ72vC72Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
b=MWsZShpvngNwyB6bzMwHeSp8wj6GI84akWnu8yDQPpAThL8/ZYTeCiVZBazkfmxlaJ
HMNmaN1jp/y9Il/XJWGitwe+7/0XpqcQVF0vXzLUh+3x7QHyspUAllKOAMS4zZ7V+7MM
peutD2LHRWqQlEXXRLAI0qZZQIre+H+02/Vz4=
MIME-Version: 1.0
Received: by 10.223.5.71 with SMTP id 7mr1352657fau.48.1268221118260; Wed, 10
Mar 2010 03:38:38 -0800 (PST)
In-Reply-To: <Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
From: Adrenalin <adrenalinup@gmail.com>
Date: Wed, 10 Mar 2010 12:38:18 +0100
Message-ID: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 11:38:40 -0000
Rick thank you for the answer.
I'll "put my heart into the teeth" and will try to go for the stable.
This is kind of critical I guess, I think it should really go to the
release. It's the first time I got into a such a nasty bug with freebsd.
On Wed, Mar 10, 2010 at 3:44 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>
> On Wed, 10 Mar 2010, Adrenalin wrote:
>
> Hi, I would like to know if this bug has been fixed in the FreeBSD 8
>> Release
>> since I got it 3 times already on a busy box that use heavily NFS (with
>> lots
>> of files).
>> Unfortunately my processes are not compiled with debug symbols(so I cannot
>> get an backtrace), but I've got all the php-cgi stuck in the "rpccon"
>> state
>> just like described here, I cannot kill them and I cannot cleanly reboot,
>> manual restart is required.
>>
>> I suspect that what you are seeing is fixed by:
> http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch<http://people.freebsd.org/%7Ermacklem/patches/freebsd8-clntvc.patch>
>
> It is in head and stable/8, but did not make the FreeBSD8.0 release.
>
> I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
>
> rick
>
>
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 12:19:18 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0AEDB1065672;
Wed, 10 Mar 2010 12:19:18 +0000 (UTC)
(envelope-from imb@protected-networks.net)
Received: from sarah.protected-networks.net (sarah.protected-networks.net
[IPv6:2001:470:1f07:4e1::1])
by mx1.freebsd.org (Postfix) with ESMTP id C78AF8FC1A;
Wed, 10 Mar 2010 12:19:17 +0000 (UTC)
Received: from toshi.auburn.protected-networks.net
(toshi.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::4])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(Client CN "Iain Butler",
Issuer "RSA Class 2 Personal CA" (verified OK))
(Authenticated sender: imb)
by sarah.protected-networks.net (Postfix) with ESMTPSA id D44C16172;
Wed, 10 Mar 2010 07:19:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
d=protected-networks.net; s=200705; t=1268223557;
bh=Hn+1aIWZur2Kl3EXJiz5HnxQCTOvoVQM9oIXlq0b4aU=;
h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:
In-Reply-To:Content-Type:Content-Transfer-Encoding;
b=MLcC1D0/rye4VsPXIJ+JxLTPejJbApt0HVaV6OgDXWr407EQplWAuUhTEnIj9zAFy
zJft5AXVXwUlLh/kKfKfsnbFYDpCis6J4CGNIvC81yfH7nCDThght+cYpQR5Xco
DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws;
q=dns;
h=message-id:date:from:user-agent:mime-version:to:cc:subject:
references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding;
b=V7CkmK3shCRkR/svHoslOzVDf9SHwMu3jm/Lp7jW2SJEK/RURWfFPQv/fO6BIR2nW
fSbz18prLneGlvO4X+CtYoiPjBYX6PgXcTdZZ9rT44cF19TbOIJSJFN2N5drgl9
Message-ID: <4B978E41.4010800@protected-networks.net>
Date: Wed, 10 Mar 2010 07:19:13 -0500
From: Michael Butler <imb@protected-networks.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: Doug Barton <dougb@FreeBSD.org>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
<4B96FD4B.3090706@FreeBSD.org>
In-Reply-To: <4B96FD4B.3090706@FreeBSD.org>
X-Enigmail-Version: 1.0.1
OpenPGP: id=0442D492
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 12:19:18 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/09/10 21:00, Doug Barton wrote:
> On 03/09/10 12:14, Li, Qing wrote:
>> This error was caused by my commit r204902 from yesterday.
>>
>> Please try patch at
>>
>> http://people.freebsd.org/~qingli/route.h.diff
>
> This doesn't appear to be committed yet, is it still the best fix?
Even with this patch, I can't ping the ipv4 address at the other end of
an openvpn tunnel :-(
imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuXjkAACgkQQv9rrgRC1JLSgwCeP1DbEdkiI4tLyteNhHS4q1yM
u4YAn0qdGCZLPDRsiRWlXRzyG1Wl4wlA
=L4+B
-----END PGP SIGNATURE-----
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 16:43:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0579D106566C
for <current@freebsd.org>; Wed, 10 Mar 2010 16:43:36 +0000 (UTC)
(envelope-from rfarmer@predatorlabs.net)
Received: from mail-qy0-f183.google.com (mail-qy0-f183.google.com
[209.85.221.183])
by mx1.freebsd.org (Postfix) with ESMTP id C4CE78FC29
for <current@freebsd.org>; Wed, 10 Mar 2010 16:43:35 +0000 (UTC)
Received: by qyk14 with SMTP id 14so3628386qyk.9
for <current@freebsd.org>; Wed, 10 Mar 2010 08:43:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.81.85 with SMTP id w21mr1246613qak.129.1268239408124; Wed,
10 Mar 2010 08:43:28 -0800 (PST)
X-Originating-IP: [128.95.133.64]
Date: Wed, 10 Mar 2010 08:43:28 -0800
Message-ID: <b025ceb71003100843u47f17478ya33472da7e6f798d@mail.gmail.com>
From: Rob Farmer <rfarmer@predatorlabs.net>
To: current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Cc:
Subject: PF not working, with lock order reversal
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 16:43:36 -0000
Hi,
I just updated a sparc64 Sun Netra X1 running current. I am using PF
(built into the kernel) and now I cannot connect to the machine while
PF is enabled (but outbound traffic from the machine works). The same
ruleset has worked fine for me for several years on this and other
systems. I'm getting the following LOR at boot and wonder if it is
related?
lock order reversal:
1st 0xc0424d28 pf task mtx (pf task mtx) @
/usr/src/sys/contrib/pf/net/pf.c:6929
2nd 0xfffff800011954f8 radix node head (radix node head) @
/usr/src/sys/net/route.c:360
KDB: stack backtrace:
_witness_debugger() at _witness_debugger+0x84
witness_checkorder() at witness_checkorder+0xafc
_rw_rlock() at _rw_rlock+0x44
rtalloc1_fib() at rtalloc1_fib+0x124
rtalloc_ign_fib() at rtalloc_ign_fib+0xac
pf_calc_mss() at pf_calc_mss+0xbc
pf_test_tcp() at pf_test_tcp+0xf04
pf_test() at pf_test+0x10e8
pf_check_in() at pf_check_in+0x14
pfil_run_hooks() at pfil_run_hooks+0xb8
ip_input() at ip_input+0x488
netisr_dispatch_src() at netisr_dispatch_src+0xf0
ether_demux() at ether_demux+0x2ac
ether_input() at ether_input+0x24c
dc_rxeof() at dc_rxeof+0x350
dc_intr() at dc_intr+0x310
intr_event_execute_handlers() at intr_event_execute_handlers+0xc4
ithread_loop() at ithread_loop+0xe4
fork_exit() at fork_exit+0x6c
fork_trampoline() at fork_trampoline+0x8
My pf.conf:
http://www.predatorlabs.net/dl/pf.conf
My kernel config:
http://www.predatorlabs.net/dl/NETRA
Thanks,
--
Rob Farmer
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 17:18:13 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2572F1065675
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 17:18:13 +0000 (UTC)
(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
by mx1.freebsd.org (Postfix) with ESMTP id 0B16F8FC13
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 17:18:12 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o2AHICKZ023621;
Wed, 10 Mar 2010 09:18:12 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Mar 2010 09:18:01 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <4B978E41.4010800@protected-networks.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: AcrAS/uiTbUBNEDATqm1YGbQlqMKKgAKXL9Q
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org>
<4B978E41.4010800@protected-networks.net>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Michael Butler" <imb@protected-networks.net>
Cc: freebsd-current@freebsd.org
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 17:18:13 -0000
Could you please provide me with more information, such as your
ifconfig and netstat output? What's the error message?
Asking the obvious question, you updated to r204902?
Thanks,
--Qing
> -----Original Message-----
> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> current@freebsd.org] On Behalf Of Michael Butler
> Sent: Wednesday, March 10, 2010 4:19 AM
> To: Doug Barton
> Cc: freebsd-current@freebsd.org
> Subject: Re: Error 127.0.0.1: no route to host
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 03/09/10 21:00, Doug Barton wrote:
> > On 03/09/10 12:14, Li, Qing wrote:
> >> This error was caused by my commit r204902 from yesterday.
> >>
> >> Please try patch at
> >>
> >> http://people.freebsd.org/~qingli/route.h.diff
> >
> > This doesn't appear to be committed yet, is it still the best fix?
>=20
> Even with this patch, I can't ping the ipv4 address at the other end
of
> an openvpn tunnel :-(
>=20
> imb
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (FreeBSD)
>=20
> iEYEARECAAYFAkuXjkAACgkQQv9rrgRC1JLSgwCeP1DbEdkiI4tLyteNhHS4q1yM
> u4YAn0qdGCZLPDRsiRWlXRzyG1Wl4wlA
> =3DL4+B
> -----END PGP SIGNATURE-----
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 18:31:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 65DBD1065674;
Wed, 10 Mar 2010 18:31:36 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (out-0-7.mx.aerioconnect.net
[216.240.47.67])
by mx1.freebsd.org (Postfix) with ESMTP id 1D48E8FC1D;
Wed, 10 Mar 2010 18:31:35 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o2AIVZ3U022662; Wed, 10 Mar 2010 10:31:35 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id 76EA52D6022;
Wed, 10 Mar 2010 10:31:34 -0800 (PST)
Message-ID: <4B97E585.20106@elischer.org>
Date: Wed, 10 Mar 2010 10:31:33 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Adrenalin <adrenalinup@gmail.com>
References: <1242075474.72992.118.camel@hood.oook.cz> <3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net>
<200906160812.04284.jhb@freebsd.org> <4A3E234F.6050403@FreeBSD.org> <Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
<f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
In-Reply-To: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: Doug Rabson <dfr@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca>,
current@freebsd.org, freebsd-current@freebsd.org,
pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 18:31:36 -0000
Adrenalin wrote:
> Rick thank you for the answer.
>
> I'll "put my heart into the teeth" and will try to go for the stable.
>
> This is kind of critical I guess, I think it should really go to the
> release. It's the first time I got into a such a nasty bug with freebsd.
Unfortunately the release has 'left the station', however I guess we
might be able to add a pointer in the erratum document.
I'm not sure who is in charge of that doc. (re?)
>
> On Wed, Mar 10, 2010 at 3:44 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>>
>> On Wed, 10 Mar 2010, Adrenalin wrote:
>>
>> Hi, I would like to know if this bug has been fixed in the FreeBSD 8
>>> Release
>>> since I got it 3 times already on a busy box that use heavily NFS (with
>>> lots
>>> of files).
>>> Unfortunately my processes are not compiled with debug symbols(so I cannot
>>> get an backtrace), but I've got all the php-cgi stuck in the "rpccon"
>>> state
>>> just like described here, I cannot kill them and I cannot cleanly reboot,
>>> manual restart is required.
>>>
>>> I suspect that what you are seeing is fixed by:
>> http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch<http://people.freebsd.org/%7Ermacklem/patches/freebsd8-clntvc.patch>
>>
>> It is in head and stable/8, but did not make the FreeBSD8.0 release.
>>
>> I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
>>
>> rick
>>
>>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 18:48:16 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E58FA106566B;
Wed, 10 Mar 2010 18:48:16 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (out-0-7.mx.aerioconnect.net
[216.240.47.67])
by mx1.freebsd.org (Postfix) with ESMTP id A3EBB8FC12;
Wed, 10 Mar 2010 18:48:16 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o2AIVZ3U022662; Wed, 10 Mar 2010 10:31:35 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id 76EA52D6022;
Wed, 10 Mar 2010 10:31:34 -0800 (PST)
Message-ID: <4B97E585.20106@elischer.org>
Date: Wed, 10 Mar 2010 10:31:33 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Adrenalin <adrenalinup@gmail.com>
References: <1242075474.72992.118.camel@hood.oook.cz> <3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net>
<200906160812.04284.jhb@freebsd.org> <4A3E234F.6050403@FreeBSD.org> <Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
<f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
In-Reply-To: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: Doug Rabson <dfr@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca>,
current@freebsd.org, freebsd-current@freebsd.org,
pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 18:48:17 -0000
Adrenalin wrote:
> Rick thank you for the answer.
>
> I'll "put my heart into the teeth" and will try to go for the stable.
>
> This is kind of critical I guess, I think it should really go to the
> release. It's the first time I got into a such a nasty bug with freebsd.
Unfortunately the release has 'left the station', however I guess we
might be able to add a pointer in the erratum document.
I'm not sure who is in charge of that doc. (re?)
>
> On Wed, Mar 10, 2010 at 3:44 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>>
>> On Wed, 10 Mar 2010, Adrenalin wrote:
>>
>> Hi, I would like to know if this bug has been fixed in the FreeBSD 8
>>> Release
>>> since I got it 3 times already on a busy box that use heavily NFS (with
>>> lots
>>> of files).
>>> Unfortunately my processes are not compiled with debug symbols(so I cannot
>>> get an backtrace), but I've got all the php-cgi stuck in the "rpccon"
>>> state
>>> just like described here, I cannot kill them and I cannot cleanly reboot,
>>> manual restart is required.
>>>
>>> I suspect that what you are seeing is fixed by:
>> http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch<http://people.freebsd.org/%7Ermacklem/patches/freebsd8-clntvc.patch>
>>
>> It is in head and stable/8, but did not make the FreeBSD8.0 release.
>>
>> I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
>>
>> rick
>>
>>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 19:11:22 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7BE7F106564A
for <current@freebsd.org>; Wed, 10 Mar 2010 19:11:22 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19])
by mx1.freebsd.org (Postfix) with ESMTP id 503038FC29
for <current@freebsd.org>; Wed, 10 Mar 2010 19:11:22 +0000 (UTC)
Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Wed, 10 Mar 2010 11:11:14 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Wed, 10
Mar 2010 11:11:14 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "Ian FREISLICH" <ianf@clue.co.za>
Date: Wed, 10 Mar 2010 11:11:13 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: AcrAMPUTon1v+XjlSqCBqmDnLEAN2wAUgwOQ
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <5D267A3F22FD854F8F48B3D2B52381933AF90EEDA7@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100305210435.GF14818@michelle.cdnetworks.com>
<20100305184046.GD14818@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
In-Reply-To: <E1NpHr0-000HWT-It@clue.co.za>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6789315831G55615605-01-01
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>,
"current@freebsd.org" <current@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 19:11:22 -0000
> > What's the traffic look like? Jumbo, standard, short=20
> frames? Any=3D20=20
> > good ideas on profiling the code? I haven't figured out how to use=20
> > the CPU TSC but there is a free running timer on the device=20
> that might=20
> > be usable to calculate where the driver's time is spent.
>=20
> It looks like the traffic that provoked it was this:
>=20
> 10:18:42.319370 IP X.4569 > X.4569: UDP, length 12
> 10:18:42.319402 IP X.4569 > X.4569: UDP, length 12
> 10:18:42.319438 IP X.4569 > X.4569: UDP, length 12
> 10:18:42.319484 IP X.4569 > X.4569: UDP, length 12
> 10:18:42.319517 IP X.4569 > X.4569: UDP, length 12
>=20
> A flurry of UDP tinygrams on an IAX2 trunk. The packet rate=20
> isn't spectacular at about 30kpps which on top of the base=20
> load of 60kpps still isn't a fantastic packet rate. The=20
> interesting thing is that while this storm was inprogress, it=20
> almost entirely excluded other traffic on the network.
Ok, small packet performance is involved, this narrows down
the range of problems. The current design of bce_rx_intr()
attempts to process all RX frames in the receive ring. After
all available frames have been processed then the function=20
will attempt to refill the ring with new buffers. It's
likely that there's a long gap between the time the last
receive buffer is consumed and the time the RX ring is=20
refilled and the buffers are posted to the hardware, causing
a burst of dropped frames and the com_no_buffers firmware
counter to increment.
Changing the high level design of bce_rx_intr() and
bce_rx_fill_chain() slightly to post a new buffer as each
frame is passed to the OS would likely avoid these gaps=20
during bursts of small frames but I'm not sure whether=20
they'll have a negative impact on the more common case of
streams of MTU sized frames. I've considered this in the
past but never coded the change and tested the resulting
performance.
Does anyone have some experience with one method over
the other?
Dave=
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 19:17:03 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E9E81106566C
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 19:17:02 +0000 (UTC)
(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
by mx1.freebsd.org (Postfix) with ESMTP id D14A78FC17
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 19:17:02 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o2AJH23K014892
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 11:17:02 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Mar 2010 11:16:51 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306CE20D8@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: Acq/uQc/wuPE86eQQ36rnjvhdhd1LAAAl2AwAAJbuMAAL3wXsA==
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com><B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "FreeBSD Current" <freebsd-current@freebsd.org>
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 19:17:03 -0000
>=20
> This error was caused by my commit r204902 from yesterday.
>=20
> Please try patch at
>=20
> http://people.freebsd.org/~qingli/route.h.diff
>=20
The route.h.diff patch warrants some explanation.
What I did here is basically excluding "if_link_state" checks
against loopback interfaces and point-to-point interfaces.
The loopback interface does not modify this variable and
conceptually it is always up. The bug was due to the check
was also performed on the loopback interface, and broke all
self destined traffic (127.0.0.1 and all local IPs).=20
The route.h.diff fixes this bug.
The story for the point-to-point interfaces is slightly
different. For example, if_tun interface updates the
if_link_state but I am not sure about the other ppp pseudo
interface.
By excluding the PPP interfaces from the link state check,=20
the behavior may be when ECMP is enabled and a PPP link is=20
actually down, traffic would go into blackhole, but that's=20
exactly the current behavior.
So with r204902 and ECMP enabled, you can failover and=20
load-balance across physical interfaces and those dependent
interface types such as if_vlan and if_lagg, but not PPP
link types (for now, which I will fix in time).
Your comments are welcome.
-- Qing
>=20
>=20
> > -----Original Message-----
> > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> > current@freebsd.org] On Behalf Of Li, Qing
> > Sent: Tuesday, March 09, 2010 11:05 AM
> > To: Renato Botelho; FreeBSD Current
> > Subject: RE: Error 127.0.0.1: no route to host
> >
> > Thanks for the report, I am looking at it and will get back to you.
> >
> > -- Qing
> >
> >
> > > -----Original Message-----
> > > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> > > current@freebsd.org] On Behalf Of Renato Botelho
> > > Sent: Tuesday, March 09, 2010 10:47 AM
> > > To: FreeBSD Current
> > > Subject: Error 127.0.0.1: no route to host
> > >
> > > I updated my 9.0-current amd64 today on rev. 204915 and start
> > > to get errors like this
> > >
> > > 127.0.0.1: no route to host
> > >
> > > I boot using kernel.old and everything back to normal. I don't
know
> > > exactly revision of my kernel.old because last change made on
> > > sys/conf/newvers.sh simply removed this information from my
> > > uname, see:
> > >
> > > FreeBSD botelhor.bplab.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1:
> Mon
> > > Mar 8 15:52:59 BRT 2010
> > > root@botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA amd64
> > >
> > > I just know it was built yesterday about 18:00 UTC
> > >
> > > Is there any other way to get this information?
> > >
> > > Let me know if you need more information about my environment.
> > >
> > > Regards
> > > --
> > > Renato Botelho
> > > _______________________________________________
> > > freebsd-current@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-
> > > unsubscribe@freebsd.org"
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-
> > unsubscribe@freebsd.org"
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 19:52:12 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3032D106564A
for <current@freebsd.org>; Wed, 10 Mar 2010 19:52:12 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id AC9248FC13
for <current@freebsd.org>; Wed, 10 Mar 2010 19:52:11 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7546494fxm.3
for <current@freebsd.org>; Wed, 10 Mar 2010 11:52:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=eefxUWtx02CNhv5UP0NWcOeXTipobIs9tlBZIlQ64zQ=;
b=Cmu5QfQVaC7Jt5CuejTH+rH7slYqDgxLg6donltYkMHd1kWlH4jSJsOjtp3ZL5TKoU
VJeQsXwJxY+jtMzKc1d1TgO0j8oHixEr4R7KyZGOyb7LQDWIstmkPglTsuPgbKDMIxK7
juwd1sdZZ3eBYK19iL5vPXwf/3dbZMUwSofK0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=lEOPjfanIElkmbzjp5IoXfYUf+DuxfIdUGIEk70KO2fg38CvuO3WkPIDQBkFOFK9bb
fZfmZvduRVBK7v4EnaBhYjLmXh+6Kdxo3QVNRbT3aj3b7ZAqnPcxU+R9gRIdN0EcTz9j
wpGY5DHHOVqBQQoJ1pUTpe4B/x1DRi/tdYHw4=
Received: by 10.87.67.10 with SMTP id u10mr3671895fgk.28.1268250730590;
Wed, 10 Mar 2010 11:52:10 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id d8sm10337213fga.4.2010.03.10.11.52.07
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 10 Mar 2010 11:52:09 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Wed, 10 Mar 2010 11:52:06 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Wed, 10 Mar 2010 11:52:06 -0800
To: David Christensen <davidch@broadcom.com>
Message-ID: <20100310195206.GB10657@michelle.cdnetworks.com>
References: <20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
User-Agent: Mutt/1.4.2.3i
Cc: Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 19:52:12 -0000
On Wed, Mar 10, 2010 at 11:11:13AM -0800, David Christensen wrote:
> > > What's the traffic look like? Jumbo, standard, short
> > frames? Any=20
> > > good ideas on profiling the code? I haven't figured out how to use
> > > the CPU TSC but there is a free running timer on the device
> > that might
> > > be usable to calculate where the driver's time is spent.
> >
> > It looks like the traffic that provoked it was this:
> >
> > 10:18:42.319370 IP X.4569 > X.4569: UDP, length 12
> > 10:18:42.319402 IP X.4569 > X.4569: UDP, length 12
> > 10:18:42.319438 IP X.4569 > X.4569: UDP, length 12
> > 10:18:42.319484 IP X.4569 > X.4569: UDP, length 12
> > 10:18:42.319517 IP X.4569 > X.4569: UDP, length 12
> >
> > A flurry of UDP tinygrams on an IAX2 trunk. The packet rate
> > isn't spectacular at about 30kpps which on top of the base
> > load of 60kpps still isn't a fantastic packet rate. The
> > interesting thing is that while this storm was inprogress, it
> > almost entirely excluded other traffic on the network.
>
> Ok, small packet performance is involved, this narrows down
> the range of problems. The current design of bce_rx_intr()
> attempts to process all RX frames in the receive ring. After
> all available frames have been processed then the function
> will attempt to refill the ring with new buffers. It's
> likely that there's a long gap between the time the last
> receive buffer is consumed and the time the RX ring is
> refilled and the buffers are posted to the hardware, causing
> a burst of dropped frames and the com_no_buffers firmware
> counter to increment.
>
I successfully reproduced the issue with netperf on BCM5709. You
can use UDP frame size 1 to trigger the issue.
> Changing the high level design of bce_rx_intr() and
> bce_rx_fill_chain() slightly to post a new buffer as each
> frame is passed to the OS would likely avoid these gaps
> during bursts of small frames but I'm not sure whether
> they'll have a negative impact on the more common case of
> streams of MTU sized frames. I've considered this in the
> past but never coded the change and tested the resulting
> performance.
>
I guess this may slightly increase performance with additional
bus_dma(9) overheads but I think one of reason of dropping frames
under heavy UDP frames may come from lack of free RX descriptors.
Because bce(4) just uses a single RX ring so the number of
available RX buffers would be 512. However it seems it's not
possible to increase the number of RX buffers per RX ring so the
next possible approach would be switching to use multiple RX rings
with RSS. Even though FreeBSD does not dynamically adjust loads
among CPUs I guess using RSS would be the way to go.
> Does anyone have some experience with one method over
> the other?
>
> Dave
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 20:38:38 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9AFE41065670
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 20:38:38 +0000 (UTC)
(envelope-from imb@protected-networks.net)
Received: from sarah.protected-networks.net (sarah.protected-networks.net
[IPv6:2001:470:1f07:4e1::1])
by mx1.freebsd.org (Postfix) with ESMTP id 5F3058FC13
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 20:38:38 +0000 (UTC)
Received: from toshi.auburn.protected-networks.net
(toshi.auburn.protected-networks.net [202.12.127.84])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(Client CN "Iain Butler",
Issuer "RSA Class 2 Personal CA" (verified OK))
(Authenticated sender: imb)
by sarah.protected-networks.net (Postfix) with ESMTPSA id 151746138;
Wed, 10 Mar 2010 15:38:37 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
d=protected-networks.net; s=200705; t=1268253517;
bh=dvmzQCCgUiq/U/jL4P688tFCaLokdtWTgiByziBsLv4=;
h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:
In-Reply-To:Content-Type:Content-Transfer-Encoding;
b=XzADz4AOpx199Ou4o7FPwzuyb/GCwKt3QxbNzgsahXA+t2NS/NHlcMxVkmRAI3dd6
k7+THEotb7BorEjW124wwl3vSzJ0rOxzcO/8YVkhr8FsSrrLjuNV0jGzWLjZhrj
DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws;
q=dns;
h=message-id:date:from:user-agent:mime-version:to:cc:subject:
references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding;
b=nvQpMAT0G5C6spURXzOn5K/c9epyZ/m7QYZdWaRzmz6FIrhVUGC+p2FnJf0nSXrYz
m0xmuz8dbnAv73cB/YJv4R3sROknkooz6JikqTK9pP5WBLRhRKotOr/pvfbC6uz
Message-ID: <4B980347.8020500@protected-networks.net>
Date: Wed, 10 Mar 2010 15:38:31 -0500
From: Michael Butler <imb@protected-networks.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: "Li, Qing" <qing.li@bluecoat.com>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org>
<4B978E41.4010800@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
X-Enigmail-Version: 1.0.1
OpenPGP: id=0442D492
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 20:38:38 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/10/10 12:18, Li, Qing wrote:
> Could you please provide me with more information, such as your
> ifconfig and netstat output? What's the error message?
With or without r204902, I do not see any difference in ifconfig or
netstat output. Addresses and routes are added as normal.
Without the route.h patch, I can't ping 127.0.0.1 or the local or remote
address of the OpenVPN tunnel (on tap0). In fact, you can't even build
OpenVPN from ports as it'll fail its self-test.
With the route.h patch, I can ping all local addresses but not the far
end of the tunnel.
Backing out r204902 restores normal operation of the tunnel.
> Asking the obvious question, you updated to r204902?
FreeBSD toshi.auburn.protected-networks.net 9.0-CURRENT FreeBSD
9.0-CURRENT #1 r204949M: Wed Mar 10 07:22:22 EST 2010
The 'M' signifies only that I've added my Nikon camera to the usbdev
list and added aquirk for it,
imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuYA0cACgkQQv9rrgRC1JL0bgCgqte+e7snRtr9uA/u0q5XaYLm
OvoAn0o6Att5R8I2da8HyNiZnDCT/NHQ
=BW8c
-----END PGP SIGNATURE-----
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 20:58:45 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E5F861065672;
Wed, 10 Mar 2010 20:58:45 +0000 (UTC)
(envelope-from andreast-list@fgznet.ch)
Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47])
by mx1.freebsd.org (Postfix) with ESMTP id 7F98B8FC70;
Wed, 10 Mar 2010 20:58:44 +0000 (UTC)
Received: from deuterium.andreas.nets (dhclient-91-190-8-131.flashcable.ch
[91.190.8.131])
by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id
o2AKwb9j042270; Wed, 10 Mar 2010 21:58:38 +0100 (CET)
(envelope-from andreast-list@fgznet.ch)
Message-ID: <4B9807FC.1020003@fgznet.ch>
Date: Wed, 10 Mar 2010 21:58:36 +0100
From: Andreas Tobler <andreast-list@fgznet.ch>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: Ed Schouten <ed@80386.nl>, nobutaka@FreeBSD.org,
Current <freebsd-current@FreeBSD.org>
References: <4B5227B6.40406@fgznet.ch> <20100117013602.GO64905@hoeg.nl>
<4B52FE83.9070705@fgznet.ch> <4B6F2895.4080802@fgznet.ch>
In-Reply-To: <4B6F2895.4080802@fgznet.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47
Cc:
Subject: Re: PING: Re: HEADS UP: <utmp.h> gone. All welcome <utmpx.h>.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 20:58:46 -0000
Ping again.
Tia,
Andreas
On 07.02.10 21:54, Andreas Tobler wrote:
> Hi all,
>
> On 17.01.10 13:11, Andreas Tobler wrote:
>
>> On 17.01.10 02:36, Ed Schouten wrote:
>>
>>> * Andreas Tobler<andreast-list@fgznet.ch> wrote:
>>>> So far everything went smooth. But one issue I have, I use mlterm
>>>> (/usr/ports/x11/mlterm) and here I fail to build it.
>>>>
>>>> kik_utmp_bsd.c:28:2: error: #error "UT_LINESIZE is not defined."
>>>> kik_utmp_bsd.c:32:2: error: #error "_PATH_UTMP is not defined."
>>>> kik_utmp_bsd.c:36:2: error: #error "_PATH_WTMP is not defined."
>>>> kik_utmp_bsd.c:40:2: error: #error "_PATH_LASTLOG is not defined."
>>>>
>>>> I see they where defined in utmp.h, but I do not see how to
>>>> handle/patch this with the current situation.
>>>>
>>>> Would you mind giving me a hand on how to fix this? I'm willing to
>>>> hack/test.
>>>
>>> Could you try the attached patch? Nobutaka, if the patch works properly,
>>> could you commit it to CVS, please?
>>
>> Thanks a lot!
>>
>> Works here so far.
>
> I use the patch you sent me with success. Everytime I sync the ports
> tree it is gone :(
>
> Is there something we forgot to test? Or why is this patch not committed
> to the ports tree?
>
> If you'd need some help/test from my side, please tell me.
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 21:27:09 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DFB16106566B
for <current@freebsd.org>; Wed, 10 Mar 2010 21:27:09 +0000 (UTC)
(envelope-from rhurlin@gwdg.de)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18])
by mx1.freebsd.org (Postfix) with ESMTP id A16BA8FC13
for <current@freebsd.org>; Wed, 10 Mar 2010 21:27:09 +0000 (UTC)
Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184]
helo=krabat.raven.hur)
by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69)
(envelope-from <rhurlin@gwdg.de>) id 1NpSRH-0003Gv-3K
for current@freebsd.org; Wed, 10 Mar 2010 21:23:31 +0100
Message-ID: <4B97FFBE.90504@gwdg.de>
Date: Wed, 10 Mar 2010 21:23:26 +0100
From: Rainer Hurling <rhurlin@gwdg.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-DE;
rv:1.9.1.8) Gecko/20100302 Thunderbird/3.0.3
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:rhurlin
X-Spam-Level: -
X-Virus-Scanned: (clean) by exiscan+sophie
Cc:
Subject: Kernel from today does not build any more
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 21:27:10 -0000
After cvsup my CURRENT amd64 systems today I am not able to build custom
kernel any more. Does anyone else observes the following breakage?
===> bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/RHURLIN/opt_global.h -I. -I@ -I@/contrib/altq
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -fno-common -fno-omit-frame-pointer
-I/usr/obj/usr/src/sys/RHURLIN -mcmodel=kernel -mno-red-zone
-mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions -c
/usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c
cc1: warnings being treated as errors
/usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c: In function 'bwn_tsf_read':
/usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c:10384: warning: unused
variable 'sc'
*** Error code 1
Stop in /usr/src/sys/modules/bwn.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
...
Thanks in advance,
Rainer Hurling
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 21:46:35 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6F1861065673
for <current@freebsd.org>; Wed, 10 Mar 2010 21:46:35 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156])
by mx1.freebsd.org (Postfix) with ESMTP id F1AC58FC13
for <current@freebsd.org>; Wed, 10 Mar 2010 21:46:34 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id 22so2859565fge.13
for <current@freebsd.org>; Wed, 10 Mar 2010 13:46:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=mgwGdyxqKWJIGBhSVe8B3X6VThtz4UrqRI93WaZnnVM=;
b=ns5vcRLQaAf+6Pjz0CAKkqiT/H5bUA/LnsX19jinTBhWbxBwFHY4AWCuB+YYDRrWIh
ezjBpOmmaD4OKc9SSidNtL/ep/M3M+mQ/FDXT0rEEH6D83eeT47j+/4B4QnUF8huIJrr
aYrUncLNbuAT31UFFyDmOcSl5GgUwGq5k6dKg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=eykZpF4mX3ghU6boyjRbx06vhoOZJKdHaGOwfNDvd7NYHSfTTgWT5kMHSTcAXlW0iF
BirIvRDzqwXPIVPl8RIZErvWIFinHzEi4aZDGaXZUIIsmClSjlkl+Wk2BHTcSrItOCRA
SKLe0sH6WQ0Ul5yOIYXtgn3HreUauHroWJlyk=
Received: by 10.87.68.35 with SMTP id v35mr205280fgk.25.1268257593843;
Wed, 10 Mar 2010 13:46:33 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id 12sm1537506fgg.29.2010.03.10.13.46.31
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 10 Mar 2010 13:46:32 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Wed, 10 Mar 2010 13:46:27 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Wed, 10 Mar 2010 13:46:27 -0800
To: Rainer Hurling <rhurlin@gwdg.de>
Message-ID: <20100310214627.GE10657@michelle.cdnetworks.com>
References: <4B97FFBE.90504@gwdg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B97FFBE.90504@gwdg.de>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org
Subject: Re: Kernel from today does not build any more
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 21:46:35 -0000
On Wed, Mar 10, 2010 at 09:23:26PM +0100, Rainer Hurling wrote:
> After cvsup my CURRENT amd64 systems today I am not able to build custom
> kernel any more. Does anyone else observes the following breakage?
>
Fixed in r204983.
> ===> bwn (all)
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
> -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include
> /usr/obj/usr/src/sys/RHURLIN/opt_global.h -I. -I@ -I@/contrib/altq
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -fno-common -fno-omit-frame-pointer
> -I/usr/obj/usr/src/sys/RHURLIN -mcmodel=kernel -mno-red-zone
> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
> -Wno-pointer-sign -fformat-extensions -c
> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c
> cc1: warnings being treated as errors
> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c: In function 'bwn_tsf_read':
> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c:10384: warning: unused
> variable 'sc'
> *** Error code 1
> Stop in /usr/src/sys/modules/bwn.
> *** Error code 1
> Stop in /usr/src/sys/modules.
> *** Error code 1
> ...
>
> Thanks in advance,
> Rainer Hurling
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 21:55:44 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3E7A6106564A
for <current@freebsd.org>; Wed, 10 Mar 2010 21:55:44 +0000 (UTC)
(envelope-from rhurlin@gwdg.de)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18])
by mx1.freebsd.org (Postfix) with ESMTP id F1A308FC12
for <current@freebsd.org>; Wed, 10 Mar 2010 21:55:43 +0000 (UTC)
Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184]
helo=krabat.raven.hur)
by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69)
(envelope-from <rhurlin@gwdg.de>)
id 1NpTsU-0001cv-7Z; Wed, 10 Mar 2010 22:55:42 +0100
Message-ID: <4B98155D.7080907@gwdg.de>
Date: Wed, 10 Mar 2010 22:55:41 +0100
From: Rainer Hurling <rhurlin@gwdg.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-DE;
rv:1.9.1.8) Gecko/20100302 Thunderbird/3.0.3
MIME-Version: 1.0
To: pyunyh@gmail.com
References: <4B97FFBE.90504@gwdg.de>
<20100310214627.GE10657@michelle.cdnetworks.com>
In-Reply-To: <20100310214627.GE10657@michelle.cdnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:rhurlin
X-Spam-Level: -
X-Virus-Scanned: (clean) by exiscan+sophie
Cc: current@freebsd.org
Subject: Re: Kernel from today does not build any more
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 21:55:44 -0000
On 10.03.2010 22:46 (UTC+1), Pyun YongHyeon wrote:
> On Wed, Mar 10, 2010 at 09:23:26PM +0100, Rainer Hurling wrote:
>> After cvsup my CURRENT amd64 systems today I am not able to build custom
>> kernel any more. Does anyone else observes the following breakage?
>>
>
> Fixed in r204983.
Thanks, will try it tomorrow.
Rainer
>> ===> bwn (all)
>> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
>> -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include
>> /usr/obj/usr/src/sys/RHURLIN/opt_global.h -I. -I@ -I@/contrib/altq
>> -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -fno-common -fno-omit-frame-pointer
>> -I/usr/obj/usr/src/sys/RHURLIN -mcmodel=kernel -mno-red-zone
>> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
>> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
>> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
>> -Wno-pointer-sign -fformat-extensions -c
>> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c
>> cc1: warnings being treated as errors
>> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c: In function 'bwn_tsf_read':
>> /usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c:10384: warning: unused
>> variable 'sc'
>> *** Error code 1
>> Stop in /usr/src/sys/modules/bwn.
>> *** Error code 1
>> Stop in /usr/src/sys/modules.
>> *** Error code 1
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 21:56:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BA9F11065670
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 21:56:58 +0000 (UTC)
(envelope-from giovanni.trematerra@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 4EB178FC1E
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 21:56:58 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7671259fxm.3
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 13:56:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=qmnpJ5cKQGpJEZ+xl3xuR4CDpFGZasq0r5hCO8eLGgE=;
b=acRvZlF8i6tDDDf8NV1sWargWRcSsx/fz9JCIv65NM53wdM7jzk0FJWDSFu8/uju2U
qkT9XSypMtZ/Bpm+YWlpohfHRXeLtIVmOa/D8OuF1dUk3iu93xoZh+h/2AO5Zx9knTtw
hkkM51R+zRGmw5QMWtlatE2NtgtOPkAnj5ZOc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=UBzKFXaE1wY7sew2oNpgBfQ6LmP0q0PosiZ7vEz8Mbm7rz7XFbdfe+ve0vt0m581Lq
vg0tllXuTBwHAm+imOn2Hq65w4zScXXZLd2422YJawNxpA3gU7kercMOQjlStxGkcLhE
9YccOa0QMO9q+kAGHD/E26XWyN1spGpOZpAZA=
MIME-Version: 1.0
Received: by 10.223.5.211 with SMTP id 19mr2355509faw.63.1268258217348; Wed,
10 Mar 2010 13:56:57 -0800 (PST)
In-Reply-To: <7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
Date: Wed, 10 Mar 2010 22:56:57 +0100
Message-ID: <4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
From: Giovanni Trematerra <giovanni.trematerra@gmail.com>
To: Garrett Cooper <yanefbsd@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 21:56:58 -0000
On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com> wrote=
:
>> Hi Alexander and Hans,
>> =A0 =A0I recently did the following which generated a panic on a
>> 9-CURRENT kernel compiled on the 26th:
>>
>> 1. Executed reboot
>> 2. Removed keyboard.
>> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
>> the keyboard was registered disconnected.
>> 4. The interrupt was delivered to my twa(4) enabled card and the
>> kernel panicked, like so:
>>
>> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
>> uhub8: at uhub2, port 1, addr 2 (disconnected)
>> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
>> ukbd0: at uhub8, port 3, addr 3 (disconnected)
>> uhid0: at uhub8, port 3, addr 3 (disconnected)
>> panic: mtx_lock_spin() of destroyed mutex @ /usr/src/sys/dev/twa/tw_cl_i=
ntr.c:88
>>
>> cpuid =3D 1
>> KDB: enter: panic
>> [thread pid 12 tid 100025 ]
>> Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%rip=
)
>> db>
>>
>> =A0 =A0I wish I could provide you with more details, but unfortunately I
>> the USB bus isn't registering the fact that I'm reattaching the
>> keyboard right now and the box won't reboot automatically :( (didn't
>> set the right sysctl beforehand to panic automatically). I'll try and
>> reproduce the issue again, but I was just wondering whether or not you
>> guys had seen this problem before.
>
> =A0 =A0Phew... it's reproducible with that kernel. Here's what I did
> exactly (because my original directions were incorrect):
> =A0 =A01. Hit power button (for S5).
> =A0 =A02. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
> =A0 =A0Kernel panicked on my system again. Now to figure out if it still
> exists with a kernel compiled today, and also how to debug it if it
> still does exist :/...
> Thanks,
> -Garrett
Hi Garrett,
Could you please try the patch below and report back?
Thank you
diff -r cab6489de66d sys/dev/twa/tw_cl_intr.c
--- a/sys/dev/twa/tw_cl_intr.c Wed Mar 03 04:51:13 2010 -0500
+++ b/sys/dev/twa/tw_cl_intr.c Wed Mar 10 06:29:05 2010 -0500
@@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle
if (ctlr =3D=3D NULL)
goto out;
- /* If we get an interrupt while resetting, it is a shared
- one for another device, so just bail */
- if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS)
+ /*
+ * If we get an interrupt while resetting or shutting down,
+ * it is a shared one for another device, so just bail
+ */
+ if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS ||
+ (ctrl->state & TW_CLI_CTLR_STATE_ACTIVE) =3D=3D 0)
goto out;
/*
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 22:36:34 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4D09C106564A
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 22:36:34 +0000 (UTC)
(envelope-from tom.couch.storage@gmail.com)
Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54])
by mx1.freebsd.org (Postfix) with ESMTP id CF96B8FC12
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 22:36:33 +0000 (UTC)
Received: by wwb24 with SMTP id 24so1670811wwb.13
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 14:36:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=s6cJKEESNvRn1kdXcdGoziiICKC6ZMggYwjs7YED2EA=;
b=V23d8R7lD3HU2o7s0TbE9g+tNctx0HWlypj4LFMezli0JKSJzpl+BEHPTVfi4FuAi3
15WUJa93sNDhvIXnLyROTGGl8R0NiYAO/Wbn+k7J/ulUdeDx+7DmlU/819cl1Jc9sovW
c8ZvEns7eDwE3zkR4yoLBOh7UFM0UjQhpxJfg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=McgHoZOBpIBtVDTVshC27WeRuim680sokolyK7CKaSARKHLQiZAUjjMbXeZGpm7Oou
7iuHQ//Ll2cr+CIJ+TSjZdlL4zIt0YF9tVJxPy1EqUAuscEKbBAa2A6JUDW3uFEORVZj
YmTilpZgyRb/KE4jaWrY5J1Zk53wL/XqYFkKY=
MIME-Version: 1.0
Received: by 10.216.91.9 with SMTP id g9mr1386131wef.194.1268258849890; Wed,
10 Mar 2010 14:07:29 -0800 (PST)
In-Reply-To: <4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
<4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
Date: Wed, 10 Mar 2010 14:07:29 -0800
Message-ID: <7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
From: Tom Couch <tom.couch.storage@gmail.com>
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 22:36:34 -0000
Hi FreeBSD-current,
My name is Tom Couch,
I am part of the 3ware driver team recently acquired by LSI.
I believe Giovanni's patch, below, is the correct fix for this bug.
I am available to maintain the twa driver, now that I am on this list.
Let me know how I can help,
Tom
On Wed, Mar 10, 2010 at 1:56 PM, Giovanni Trematerra <
giovanni.trematerra@gmail.com> wrote:
> On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper <yanefbsd@gmail.com>
> wrote:
> > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com>
> wrote:
> >> Hi Alexander and Hans,
> >> I recently did the following which generated a panic on a
> >> 9-CURRENT kernel compiled on the 26th:
> >>
> >> 1. Executed reboot
> >> 2. Removed keyboard.
> >> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
> >> the keyboard was registered disconnected.
> >> 4. The interrupt was delivered to my twa(4) enabled card and the
> >> kernel panicked, like so:
> >>
> >> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
> >> uhub8: at uhub2, port 1, addr 2 (disconnected)
> >> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
> >> ukbd0: at uhub8, port 3, addr 3 (disconnected)
> >> uhid0: at uhub8, port 3, addr 3 (disconnected)
> >> panic: mtx_lock_spin() of destroyed mutex @
> /usr/src/sys/dev/twa/tw_cl_intr.c:88
> >>
> >> cpuid = 1
> >> KDB: enter: panic
> >> [thread pid 12 tid 100025 ]
> >> Stopped at kdb_enter+0x3d: movq $0,0x40289c(%rip)
> >> db>
> >>
> >> I wish I could provide you with more details, but unfortunately I
> >> the USB bus isn't registering the fact that I'm reattaching the
> >> keyboard right now and the box won't reboot automatically :( (didn't
> >> set the right sysctl beforehand to panic automatically). I'll try and
> >> reproduce the issue again, but I was just wondering whether or not you
> >> guys had seen this problem before.
> >
> > Phew... it's reproducible with that kernel. Here's what I did
> > exactly (because my original directions were incorrect):
> > 1. Hit power button (for S5).
> > 2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
> > Kernel panicked on my system again. Now to figure out if it still
> > exists with a kernel compiled today, and also how to debug it if it
> > still does exist :/...
> > Thanks,
> > -Garrett
>
> Hi Garrett,
> Could you please try the patch below and report back?
>
> Thank you
>
> diff -r cab6489de66d sys/dev/twa/tw_cl_intr.c
> --- a/sys/dev/twa/tw_cl_intr.c Wed Mar 03 04:51:13 2010 -0500
> +++ b/sys/dev/twa/tw_cl_intr.c Wed Mar 10 06:29:05 2010 -0500
> @@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle
> if (ctlr == NULL)
> goto out;
>
> - /* If we get an interrupt while resetting, it is a shared
> - one for another device, so just bail */
> - if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS)
> + /*
> + * If we get an interrupt while resetting or shutting down,
> + * it is a shared one for another device, so just bail
> + */
> + if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS ||
> + (ctrl->state & TW_CLI_CTLR_STATE_ACTIVE) == 0)
> goto out;
>
> /*
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 22:47:07 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C81FB106566B
for <current@freebsd.org>; Wed, 10 Mar 2010 22:47:07 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18])
by mx1.freebsd.org (Postfix) with ESMTP id 9CDC08FC24
for <current@freebsd.org>; Wed, 10 Mar 2010 22:47:07 +0000 (UTC)
Received: from [10.9.200.133] by mms2.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Wed, 10 Mar 2010 14:45:48 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by
IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Wed, 10
Mar 2010 14:47:12 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "pyunyh@gmail.com" <pyunyh@gmail.com>
Date: Wed, 10 Mar 2010 14:45:47 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: AcrAizRkYmKmu4SaS3KppsIoJoOY8AAFrpRQ
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310195206.GB10657@michelle.cdnetworks.com>
In-Reply-To: <20100310195206.GB10657@michelle.cdnetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6786FE9638O137986979-01-01
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 22:47:07 -0000
> I successfully reproduced the issue with netperf on BCM5709.=20
> You can use UDP frame size 1 to trigger the issue.
>=20
> > Changing the high level design of bce_rx_intr() and
> > bce_rx_fill_chain() slightly to post a new buffer as each frame is=20
> > passed to the OS would likely avoid these gaps during=20
> bursts of small=20
> > frames but I'm not sure whether they'll have a negative=20
> impact on the=20
> > more common case of streams of MTU sized frames. I've=20
> considered this=20
> > in the past but never coded the change and tested the resulting=20
> > performance.
> >=20
>=20
> I guess this may slightly increase performance with additional
> bus_dma(9) overheads but I think one of reason of dropping=20
> frames under heavy UDP frames may come from lack of free RX=20
> descriptors.
> Because bce(4) just uses a single RX ring so the number of=20
> available RX buffers would be 512. However it seems it's not=20
> possible to increase the number of RX buffers per RX ring so=20
> the next possible approach would be switching to use multiple=20
> RX rings with RSS. Even though FreeBSD does not dynamically=20
> adjust loads among CPUs I guess using RSS would be the way to go.
The bce(4) hardware supports a linked list of pages for RX=20
buffer descriptors. The stock build supports 2 pages (RX_PAGES)
with a total of 511 BD's per page. The hardware can support a
maximum of 64K BD's but that would be an unnecessarily large
amount of mbufs for an infrequent problem.
The middle road would probably involve changing RX_PAGES from a
#define to a sysctl variable to allow tuning for specific
environments along with a change in bce_rx_intr() to fill the
ring after all frames have been processed or when more than
256 BDs have been consumed, whichever comes first.
RSS would be great as well though it wouldn't make a dent in
this case since RSS is only supported for TCP, not UDP.
Dave=
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 23:02:31 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D1E5F1065670
for <current@freebsd.org>; Wed, 10 Mar 2010 23:02:31 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
by mx1.freebsd.org (Postfix) with ESMTP id 4E8B78FC0C
for <current@freebsd.org>; Wed, 10 Mar 2010 23:02:30 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id 19so19038fgg.13
for <current@freebsd.org>; Wed, 10 Mar 2010 15:02:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=0413ZGRKWStMQxA26bu3JMKHFactAC5apKbmng7RpKg=;
b=xPc2m4wvzgWvf274nIAqpl5lH/oBTACMvXGVGyaNMSWUfltr3QVMX8/b9Hd+1QtKND
lUGYc6Fj3KDMcIrqAvV6MexO4W1Do0wud+z85kD1ChbRWm9ry21NtGCbrHhLDRZ3CCek
vQSChoRkjK9YA+rl6GdiP3gxTNK30XKPTMbOU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=D5pAR0jJa3iPv1YHNeTuR7gJxFKaYyxNVwlXZ2fa3dLiR9qJcO3fZmUpZTN0XWABxN
5DMTIR4TNJRdQBm+msVR44fC+aJUdFct8z4CC+v4nrUk12/zrvSY+8Sx18vPCJX9PzAA
Z5s54cq1wRREeURNAlZmINag86ePYdKI2cLwo=
Received: by 10.87.73.13 with SMTP id a13mr4006052fgl.44.1268262146525;
Wed, 10 Mar 2010 15:02:26 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id d4sm1579440fga.6.2010.03.10.15.02.23
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 10 Mar 2010 15:02:25 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Wed, 10 Mar 2010 15:02:20 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Wed, 10 Mar 2010 15:02:20 -0800
To: David Christensen <davidch@broadcom.com>
Message-ID: <20100310230220.GI10657@michelle.cdnetworks.com>
References: <E1Nnc4d-0003mB-6e@clue.co.za> <E1Nne0Q-0003uZ-OR@clue.co.za>
<E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310195206.GB10657@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
User-Agent: Mutt/1.4.2.3i
Cc: Ian FREISLICH <ianf@clue.co.za>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 23:02:32 -0000
On Wed, Mar 10, 2010 at 02:45:47PM -0800, David Christensen wrote:
>
> > I successfully reproduced the issue with netperf on BCM5709.
> > You can use UDP frame size 1 to trigger the issue.
> >
> > > Changing the high level design of bce_rx_intr() and
> > > bce_rx_fill_chain() slightly to post a new buffer as each frame is
> > > passed to the OS would likely avoid these gaps during
> > bursts of small
> > > frames but I'm not sure whether they'll have a negative
> > impact on the
> > > more common case of streams of MTU sized frames. I've
> > considered this
> > > in the past but never coded the change and tested the resulting
> > > performance.
> > >
> >
> > I guess this may slightly increase performance with additional
> > bus_dma(9) overheads but I think one of reason of dropping
> > frames under heavy UDP frames may come from lack of free RX
> > descriptors.
> > Because bce(4) just uses a single RX ring so the number of
> > available RX buffers would be 512. However it seems it's not
> > possible to increase the number of RX buffers per RX ring so
> > the next possible approach would be switching to use multiple
> > RX rings with RSS. Even though FreeBSD does not dynamically
> > adjust loads among CPUs I guess using RSS would be the way to go.
>
> The bce(4) hardware supports a linked list of pages for RX
> buffer descriptors. The stock build supports 2 pages (RX_PAGES)
> with a total of 511 BD's per page. The hardware can support a
> maximum of 64K BD's but that would be an unnecessarily large
> amount of mbufs for an infrequent problem.
>
Thanks for the info. I guess 2048 or 4096 BDs would be necessary to
get satisfactory Rx performance. I'll have to experiment this.
> The middle road would probably involve changing RX_PAGES from a
> #define to a sysctl variable to allow tuning for specific
> environments along with a change in bce_rx_intr() to fill the
> ring after all frames have been processed or when more than
> 256 BDs have been consumed, whichever comes first.
>
> RSS would be great as well though it wouldn't make a dent in
> this case since RSS is only supported for TCP, not UDP.
>
Even though UDP is not supported in RSS, RSS can handle IP. This
wouldn't distribute UDP load coming from a single host but if
source IP address is different it may help, I guess.
> Dave
From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 23:19:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5A276106566C
for <current@freebsd.org>; Wed, 10 Mar 2010 23:19:15 +0000 (UTC)
(envelope-from rfarmer@predatorlabs.net)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26])
by mx1.freebsd.org (Postfix) with ESMTP id 1D75E8FC22
for <current@freebsd.org>; Wed, 10 Mar 2010 23:19:14 +0000 (UTC)
Received: by qw-out-2122.google.com with SMTP id 5so546901qwi.7
for <multiple recipients>; Wed, 10 Mar 2010 15:19:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.59.96 with SMTP id k32mr352274qah.261.1268263150699; Wed,
10 Mar 2010 15:19:10 -0800 (PST)
X-Originating-IP: [128.95.133.64]
In-Reply-To: <b025ceb71003100843u47f17478ya33472da7e6f798d@mail.gmail.com>
References: <b025ceb71003100843u47f17478ya33472da7e6f798d@mail.gmail.com>
Date: Wed, 10 Mar 2010 15:19:10 -0800
Message-ID: <b025ceb71003101519h14a72b01s3d304e09f90ec75f@mail.gmail.com>
From: Rob Farmer <rfarmer@predatorlabs.net>
To: current@freebsd.org, qingli@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: Re: PF not working, with lock order reversal
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 23:19:15 -0000
On Wed, Mar 10, 2010 at 8:43 AM, Rob Farmer <rfarmer@predatorlabs.net> wrot=
e:
> Hi,
>
> I just updated a sparc64 Sun Netra X1 running current. I am using PF
> (built into the kernel) and now I cannot connect to the machine while
> PF is enabled (but outbound traffic from the machine works). The same
> ruleset has worked fine for me for several years on this and other
> systems. I'm getting the following LOR at boot and wonder if it is
> related?
>
> lock order reversal:
> =A01st 0xc0424d28 pf task mtx (pf task mtx) @
> /usr/src/sys/contrib/pf/net/pf.c:6929
> =A02nd 0xfffff800011954f8 radix node head (radix node head) @
> /usr/src/sys/net/route.c:360
> KDB: stack backtrace:
> _witness_debugger() at _witness_debugger+0x84
> witness_checkorder() at witness_checkorder+0xafc
> _rw_rlock() at _rw_rlock+0x44
> rtalloc1_fib() at rtalloc1_fib+0x124
> rtalloc_ign_fib() at rtalloc_ign_fib+0xac
> pf_calc_mss() at pf_calc_mss+0xbc
> pf_test_tcp() at pf_test_tcp+0xf04
> pf_test() at pf_test+0x10e8
> pf_check_in() at pf_check_in+0x14
> pfil_run_hooks() at pfil_run_hooks+0xb8
> ip_input() at ip_input+0x488
> netisr_dispatch_src() at netisr_dispatch_src+0xf0
> ether_demux() at ether_demux+0x2ac
> ether_input() at ether_input+0x24c
> dc_rxeof() at dc_rxeof+0x350
> dc_intr() at dc_intr+0x310
> intr_event_execute_handlers() at intr_event_execute_handlers+0xc4
> ithread_loop() at ithread_loop+0xe4
> fork_exit() at fork_exit+0x6c
> fork_trampoline() at fork_trampoline+0x8
>
> My pf.conf:
> http://www.predatorlabs.net/dl/pf.conf
> My kernel config:
> http://www.predatorlabs.net/dl/NETRA
>
> Thanks,
> --
> Rob Farmer
>
To follow up on this issue: I tried using the route.h patch Qing Li
posted in another thread and I can access the system now with PF
running. I still get the LOR but otherwise everything is working
normally.
--=20
Rob Farmer
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 00:38:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3AB8E1065674
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 00:38:00 +0000 (UTC)
(envelope-from imb@protected-networks.net)
Received: from sarah.protected-networks.net (sarah.protected-networks.net
[IPv6:2001:470:1f07:4e1::1])
by mx1.freebsd.org (Postfix) with ESMTP id EA9538FC28
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 00:37:59 +0000 (UTC)
Received: from toshi.auburn.protected-networks.net
(toshi.auburn.protected-networks.net [202.12.127.84])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(Client CN "Iain Butler",
Issuer "RSA Class 2 Personal CA" (verified OK))
(Authenticated sender: imb)
by sarah.protected-networks.net (Postfix) with ESMTPSA id EEB906172
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 19:37:58 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
d=protected-networks.net; s=200705; t=1268267879;
bh=w85ADRCRthNIuSAd7x1p1db9oUK/DHl6lmg4kuYfJ8g=;
h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type;
b=GyC14FNP3xSdUMfA8qIRvL2hcERi6T01K5DCO9uAzTQzFKTLS8ZejVYdK/fZaU8um
eBwTJvQ3K0RYpjbU44mLQps2uQkDWoN7Sy1zs6p1zQhzyuxhfo1KLh/F2E1XS7o
DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws;
q=dns;
h=message-id:date:from:user-agent:mime-version:to:subject:
x-enigmail-version:openpgp:content-type;
b=nfB7swucz444uQMyYPvDWOZqgg8wUbmjSjnUiOHmdtwbJeShNKfqzeEp0oq9o1R/j
tB9oMRJQtIe3CJVfDqLIhL3qxkjlWA411luW1cH9TGVdJwr1qCB6c/KCyeL6Z2r
Message-ID: <4B983B64.1040005@protected-networks.net>
Date: Wed, 10 Mar 2010 19:37:56 -0500
From: Michael Butler <imb@protected-networks.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-current <freebsd-current@freebsd.org>
X-Enigmail-Version: 1.0.1
OpenPGP: id=0442D492
Content-Type: multipart/mixed; boundary="------------050008090805050905060806"
Subject: sys/dev/siba/siba_core.c fails compilation
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 00:38:00 -0000
This is a multi-part message in MIME format.
--------------050008090805050905060806
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If compiling -current without debugging enabled, this module fails with
a warning about unused variables (warnings treated as errors).
The attached patch allows compilation to proceed although I'm not
convinced that it's entirely correct (duplicate evaluation of
device_get_ivars()),
imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuYO2QACgkQQv9rrgRC1JIuOQCfYzduyb55+itgjs7tLu4Y0EzE
u5oAoLu66AManNJuzvHl/B7eBECOVHfB
=wo8h
-----END PGP SIGNATURE-----
--------------050008090805050905060806
Content-Type: text/x-diff;
name="siba_core.c.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="siba_core.c.patch"
Index: sys/dev/siba/siba_core.c
===================================================================
--- sys/dev/siba/siba_core.c (revision 204990)
+++ sys/dev/siba/siba_core.c (working copy)
@@ -2031,11 +2031,8 @@
uint32_t
siba_dma_translation(device_t dev)
{
- struct siba_dev_softc *sd = device_get_ivars(dev);
- struct siba_softc *siba = sd->sd_bus;
-
- KASSERT(siba->siba_type == SIBA_TYPE_PCI,
- ("unsupported bustype %d\n", siba->siba_type));
+ KASSERT(device_get_ivars(dev)->sd_bus->siba_type == SIBA_TYPE_PCI,
+ ("unsupported bustype %d\n", device_get_ivars(dev)->sd_bus->siba_type));
return (SIBA_PCI_DMA);
}
--------------050008090805050905060806--
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 01:36:48 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 34C7F106566C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 01:36:48 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id B30AC8FC1C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 01:36:47 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7824060fxm.3
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 17:36:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=yIBAZGKzq4+NYtElnkOGxm0u+IA9/+B3hnemjFuBS54=;
b=ZsdkkGMQ2c9PApW714LEnan6U+NmLuHD7bYmc7wPLVu6Yhp6VKeBv4D4cLFVsJA4cC
vBL1jqDRuRH5JgLpkw58abB/La4LtmenWqrJDyxHkiuHHLYzfktYGD8Y3xm3ap7OxKPw
2VeiB2yNkWSQusFFGBRXDVpuCH1xVcqAnm0so=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=i6rBfVNupud5tIwazG0FxPDLsLwWrqSV9R9N2jfH7KRJ1jPiING112x0A6EiuUJdTF
wpdnjxdza/KY9DdSQ7YLzjZH8+1sHFoBnKWhWDS6etfPKAyfKpaM64tAdrMYU4MAnBHM
zySc1U/SOASOCirRjzx5jVGNH+4zpkLDYOYAY=
Received: by 10.223.6.150 with SMTP id 22mr2685763faz.12.1268271406327;
Wed, 10 Mar 2010 17:36:46 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id c28sm15268119fka.14.2010.03.10.17.36.44
(version=SSLv3 cipher=RC4-MD5); Wed, 10 Mar 2010 17:36:45 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Wed, 10 Mar 2010 17:36:57 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Wed, 10 Mar 2010 17:36:57 -0800
To: Michael Butler <imb@protected-networks.net>
Message-ID: <20100311013657.GX1295@weongyo>
Mail-Followup-To: Michael Butler <imb@protected-networks.net>,
freebsd-current <freebsd-current@freebsd.org>
References: <4B983B64.1040005@protected-networks.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B983B64.1040005@protected-networks.net>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: sys/dev/siba/siba_core.c fails compilation
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 01:36:48 -0000
On Wed, Mar 10, 2010 at 07:37:56PM -0500, Michael Butler wrote:
> If compiling -current without debugging enabled, this module fails with
> a warning about unused variables (warnings treated as errors).
>
> The attached patch allows compilation to proceed although I'm not
> convinced that it's entirely correct (duplicate evaluation of
> device_get_ivars()),
Your patch is committed at r204992. Thank you!
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 05:08:17 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3766B106566B;
Thu, 11 Mar 2010 05:08:17 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 102FD8FC17;
Thu, 11 Mar 2010 05:08:16 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B58Gdi099063; Thu, 11 Mar 2010 00:08:16 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B58Gis099056;
Thu, 11 Mar 2010 05:08:16 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 05:08:16 GMT
Message-Id: <201003110508.o2B58Gis099056@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<i386@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on i386/pc98
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 05:08:17 -0000
TB --- 2010-03-11 03:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 03:50:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-03-11 03:50:00 - cleaning the object tree
TB --- 2010-03-11 03:50:29 - cvsupping the source tree
TB --- 2010-03-11 03:50:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile
TB --- 2010-03-11 03:50:46 - building world
TB --- 2010-03-11 03:50:46 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 03:50:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 03:50:46 - TARGET=pc98
TB --- 2010-03-11 03:50:46 - TARGET_ARCH=i386
TB --- 2010-03-11 03:50:46 - TZ=UTC
TB --- 2010-03-11 03:50:46 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 03:50:46 - cd /src
TB --- 2010-03-11 03:50:46 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 03:50:47 UTC 2010
>>> 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 Thu Mar 11 04:49:31 UTC 2010
TB --- 2010-03-11 04:49:31 - generating LINT kernel config
TB --- 2010-03-11 04:49:31 - cd /src/sys/pc98/conf
TB --- 2010-03-11 04:49:31 - /usr/bin/make -B LINT
TB --- 2010-03-11 04:49:31 - building LINT kernel
TB --- 2010-03-11 04:49:31 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 04:49:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 04:49:31 - TARGET=pc98
TB --- 2010-03-11 04:49:31 - TARGET_ARCH=i386
TB --- 2010-03-11 04:49:31 - TZ=UTC
TB --- 2010-03-11 04:49:31 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 04:49:31 - cd /src
TB --- 2010-03-11 04:49:31 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 04:49:31 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -DPC98 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/pc98/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/pc98/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/pc98/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 05:08:16 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 05:08:16 - ERROR: failed to build lint kernel
TB --- 2010-03-11 05:08:16 - 3566.86 user 689.82 system 4695.30 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 05:11:26 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 06DB01065673;
Thu, 11 Mar 2010 05:11:26 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id D5B938FC0A;
Thu, 11 Mar 2010 05:11:25 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B5BPec025182; Thu, 11 Mar 2010 00:11:25 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B5BPxj025177;
Thu, 11 Mar 2010 05:11:25 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 05:11:25 GMT
Message-Id: <201003110511.o2B5BPxj025177@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<i386@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on i386/i386
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 05:11:26 -0000
TB --- 2010-03-11 03:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 03:50:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-03-11 03:50:00 - cleaning the object tree
TB --- 2010-03-11 03:50:30 - cvsupping the source tree
TB --- 2010-03-11 03:50:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile
TB --- 2010-03-11 03:50:46 - building world
TB --- 2010-03-11 03:50:46 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 03:50:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 03:50:46 - TARGET=i386
TB --- 2010-03-11 03:50:46 - TARGET_ARCH=i386
TB --- 2010-03-11 03:50:46 - TZ=UTC
TB --- 2010-03-11 03:50:46 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 03:50:46 - cd /src
TB --- 2010-03-11 03:50:46 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 03:50:47 UTC 2010
>>> 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 Thu Mar 11 04:49:37 UTC 2010
TB --- 2010-03-11 04:49:37 - generating LINT kernel config
TB --- 2010-03-11 04:49:37 - cd /src/sys/i386/conf
TB --- 2010-03-11 04:49:37 - /usr/bin/make -B LINT
TB --- 2010-03-11 04:49:38 - building LINT kernel
TB --- 2010-03-11 04:49:38 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 04:49:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 04:49:38 - TARGET=i386
TB --- 2010-03-11 04:49:38 - TARGET_ARCH=i386
TB --- 2010-03-11 04:49:38 - TZ=UTC
TB --- 2010-03-11 04:49:38 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 04:49:38 - cd /src
TB --- 2010-03-11 04:49:38 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 04:49:38 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/i386/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 05:11:25 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 05:11:25 - ERROR: failed to build lint kernel
TB --- 2010-03-11 05:11:25 - 3752.95 user 688.35 system 4884.32 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 05:36:17 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AD5C91065672;
Thu, 11 Mar 2010 05:36:17 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 880658FC14;
Thu, 11 Mar 2010 05:36:17 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B5aG1n018794; Thu, 11 Mar 2010 00:36:16 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B5aGTY018786;
Thu, 11 Mar 2010 05:36:16 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 05:36:16 GMT
Message-Id: <201003110536.o2B5aGTY018786@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<amd64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on amd64/amd64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 05:36:17 -0000
TB --- 2010-03-11 03:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 03:50:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-03-11 03:50:00 - cleaning the object tree
TB --- 2010-03-11 03:50:34 - cvsupping the source tree
TB --- 2010-03-11 03:50:34 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2010-03-11 03:50:49 - building world
TB --- 2010-03-11 03:50:49 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 03:50:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 03:50:49 - TARGET=amd64
TB --- 2010-03-11 03:50:49 - TARGET_ARCH=amd64
TB --- 2010-03-11 03:50:49 - TZ=UTC
TB --- 2010-03-11 03:50:49 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 03:50:49 - cd /src
TB --- 2010-03-11 03:50:49 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 03:50:54 UTC 2010
>>> 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
>>> stage 5.1: building 32 bit shim libraries
>>> World build completed on Thu Mar 11 05:16:16 UTC 2010
TB --- 2010-03-11 05:16:16 - generating LINT kernel config
TB --- 2010-03-11 05:16:16 - cd /src/sys/amd64/conf
TB --- 2010-03-11 05:16:16 - /usr/bin/make -B LINT
TB --- 2010-03-11 05:16:16 - building LINT kernel
TB --- 2010-03-11 05:16:16 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 05:16:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 05:16:16 - TARGET=amd64
TB --- 2010-03-11 05:16:16 - TARGET_ARCH=amd64
TB --- 2010-03-11 05:16:16 - TZ=UTC
TB --- 2010-03-11 05:16:16 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 05:16:16 - cd /src
TB --- 2010-03-11 05:16:16 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 05:16:16 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -I/obj/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 05:36:16 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 05:36:16 - ERROR: failed to build lint kernel
TB --- 2010-03-11 05:36:16 - 4836.40 user 932.40 system 6376.04 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 05:58:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9EEEB106566B
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 05:58:58 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com
[74.125.83.182])
by mx1.freebsd.org (Postfix) with ESMTP id 716488FC14
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 05:58:58 +0000 (UTC)
Received: by pvg3 with SMTP id 3so2967157pvg.13
for <freebsd-current@freebsd.org>; Wed, 10 Mar 2010 21:58:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=6MHbmtEJNQsMDPE1+5eciF1Q3RRzlUzuWMjgIucO4qE=;
b=gdEk8L19lf7ATqIx+UtnEB8e+KJLzyPiDWvmluYQGwXflul9x3tHir4F7M8czfRuBN
AnNthQrN9rHig6tjBEl7nto+mcn5RbWKncJXzpRwgDOrCStSfkExNZQF4dr35o5p8OXw
jhAESHczqM0wQmLJD4FPQwNaqKi/qPio8eHZk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=qiLDigVYjok0tljVtaRCFKAc7zh6GPIL0ftTyRGtJrQRGJm1wSngsQSQT0F+f1/9Q3
W8+AGuVpCQq6faJ4HW34O9ZSVzp56RWy7ogSLbxpYqNBQLhUOuNjw/pzQYDGSmm5Ou7o
haifEEal7M11WN03xDxm2r3P+xh1IWQ8YB5Jg=
MIME-Version: 1.0
Received: by 10.142.61.23 with SMTP id j23mr1181457wfa.77.1268287137918; Wed,
10 Mar 2010 21:58:57 -0800 (PST)
In-Reply-To: <7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
<4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
<7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
Date: Wed, 10 Mar 2010 21:58:57 -0800
Message-ID: <7d6fde3d1003102158o7834ca67lce3eca23aa723fd1@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Tom Couch <tom.couch.storage@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 05:58:58 -0000
On Wed, Mar 10, 2010 at 2:07 PM, Tom Couch <tom.couch.storage@gmail.com> wr=
ote:
> Hi FreeBSD-current,
> =A0 =A0 My name is Tom Couch,
> I am part of the 3ware driver team recently acquired by LSI.
> I believe Giovanni's patch, below, is the correct fix for this bug.
>
> I am available to maintain the twa driver, now that I am on this list.
> Let me know how I can help,
>
> Tom
>
>
> On Wed, Mar 10, 2010 at 1:56 PM, Giovanni Trematerra <
> giovanni.trematerra@gmail.com> wrote:
>
>> On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper <yanefbsd@gmail.com>
>> wrote:
>> > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com>
>> wrote:
>> >> Hi Alexander and Hans,
>> >> =A0 =A0I recently did the following which generated a panic on a
>> >> 9-CURRENT kernel compiled on the 26th:
>> >>
>> >> 1. Executed reboot
>> >> 2. Removed keyboard.
>> >> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
>> >> the keyboard was registered disconnected.
>> >> 4. The interrupt was delivered to my twa(4) enabled card and the
>> >> kernel panicked, like so:
>> >>
>> >> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
>> >> uhub8: at uhub2, port 1, addr 2 (disconnected)
>> >> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
>> >> ukbd0: at uhub8, port 3, addr 3 (disconnected)
>> >> uhid0: at uhub8, port 3, addr 3 (disconnected)
>> >> panic: mtx_lock_spin() of destroyed mutex @
>> /usr/src/sys/dev/twa/tw_cl_intr.c:88
>> >>
>> >> cpuid =3D 1
>> >> KDB: enter: panic
>> >> [thread pid 12 tid 100025 ]
>> >> Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(%=
rip)
>> >> db>
>> >>
>> >> =A0 =A0I wish I could provide you with more details, but unfortunatel=
y I
>> >> the USB bus isn't registering the fact that I'm reattaching the
>> >> keyboard right now and the box won't reboot automatically :( (didn't
>> >> set the right sysctl beforehand to panic automatically). I'll try and
>> >> reproduce the issue again, but I was just wondering whether or not yo=
u
>> >> guys had seen this problem before.
>> >
>> > =A0 =A0Phew... it's reproducible with that kernel. Here's what I did
>> > exactly (because my original directions were incorrect):
>> > =A0 =A01. Hit power button (for S5).
>> > =A0 =A02. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
>> > =A0 =A0Kernel panicked on my system again. Now to figure out if it sti=
ll
>> > exists with a kernel compiled today, and also how to debug it if it
>> > still does exist :/...
>> > Thanks,
>> > -Garrett
>>
>> Hi Garrett,
>> Could you please try the patch below and report back?
>>
>> Thank you
>>
>> diff -r cab6489de66d sys/dev/twa/tw_cl_intr.c
>> --- a/sys/dev/twa/tw_cl_intr.c =A0 =A0 =A0 =A0Wed Mar 03 04:51:13 2010 -=
0500
>> +++ b/sys/dev/twa/tw_cl_intr.c =A0 =A0 =A0 =A0Wed Mar 10 06:29:05 2010 -=
0500
>> @@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle
>> =A0 =A0 =A0if (ctlr =3D=3D NULL)
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 goto out;
>>
>> - =A0 =A0 /* If we get an interrupt while resetting, it is a shared
>> - =A0 =A0 =A0 =A0one for another device, so just bail */
>> - =A0 =A0 if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS)
>> + =A0 =A0 /*
>> + =A0 =A0 =A0* =A0If we get an interrupt while resetting or shutting dow=
n,
>> + =A0 =A0 =A0* =A0it is a shared one for another device, so just bail
>> + =A0 =A0 =A0*/
>> + =A0 =A0 if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS ||
>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (ctrl->state & TW_CLI_CTLR_STA=
TE_ACTIVE) =3D=3D 0)
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0goto out;
>>
>> =A0 =A0 =A0/*
I'll give the patch a try sometime before the weekend; I have a
critical deadline that I need to work through and the machine can't be
taken offline until then.
Thanks!
-Garrett
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:20:18 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2BCBB106564A;
Thu, 11 Mar 2010 06:20:18 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 066948FC0C;
Thu, 11 Mar 2010 06:20:17 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B6KH5W034572; Thu, 11 Mar 2010 01:20:17 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B6KHox034569;
Thu, 11 Mar 2010 06:20:17 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 06:20:17 GMT
Message-Id: <201003110620.o2B6KHox034569@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<ia64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on ia64/ia64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:20:18 -0000
TB --- 2010-03-11 04:38:57 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 04:38:57 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-03-11 04:38:57 - cleaning the object tree
TB --- 2010-03-11 04:39:14 - cvsupping the source tree
TB --- 2010-03-11 04:39:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile
TB --- 2010-03-11 04:39:45 - building world
TB --- 2010-03-11 04:39:45 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 04:39:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 04:39:45 - TARGET=ia64
TB --- 2010-03-11 04:39:45 - TARGET_ARCH=ia64
TB --- 2010-03-11 04:39:45 - TZ=UTC
TB --- 2010-03-11 04:39:45 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 04:39:45 - cd /src
TB --- 2010-03-11 04:39:45 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 04:39:45 UTC 2010
>>> 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 Thu Mar 11 05:55:40 UTC 2010
TB --- 2010-03-11 05:55:40 - generating LINT kernel config
TB --- 2010-03-11 05:55:40 - cd /src/sys/ia64/conf
TB --- 2010-03-11 05:55:40 - /usr/bin/make -B LINT
TB --- 2010-03-11 05:55:40 - building LINT kernel
TB --- 2010-03-11 05:55:40 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 05:55:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 05:55:40 - TARGET=ia64
TB --- 2010-03-11 05:55:40 - TARGET_ARCH=ia64
TB --- 2010-03-11 05:55:40 - TZ=UTC
TB --- 2010-03-11 05:55:40 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 05:55:40 - cd /src
TB --- 2010-03-11 05:55:40 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 05:55:40 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/ia64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/ia64/src/sys/LINT -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/ia64/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 06:20:17 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 06:20:17 - ERROR: failed to build lint kernel
TB --- 2010-03-11 06:20:17 - 4954.32 user 660.40 system 6079.48 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:29:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6B6291065670;
Thu, 11 Mar 2010 06:29:32 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 409738FC13;
Thu, 11 Mar 2010 06:29:31 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B6TVpa094219; Thu, 11 Mar 2010 01:29:31 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B6TVta094218;
Thu, 11 Mar 2010 06:29:31 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 06:29:31 GMT
Message-Id: <201003110629.o2B6TVta094218@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<powerpc@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on powerpc/powerpc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:29:32 -0000
TB --- 2010-03-11 05:11:25 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 05:11:25 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-03-11 05:11:25 - cleaning the object tree
TB --- 2010-03-11 05:11:41 - cvsupping the source tree
TB --- 2010-03-11 05:11:41 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile
TB --- 2010-03-11 05:12:22 - building world
TB --- 2010-03-11 05:12:22 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 05:12:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 05:12:22 - TARGET=powerpc
TB --- 2010-03-11 05:12:22 - TARGET_ARCH=powerpc
TB --- 2010-03-11 05:12:22 - TZ=UTC
TB --- 2010-03-11 05:12:22 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 05:12:22 - cd /src
TB --- 2010-03-11 05:12:22 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 05:12:23 UTC 2010
>>> 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 Thu Mar 11 06:12:41 UTC 2010
TB --- 2010-03-11 06:12:41 - generating LINT kernel config
TB --- 2010-03-11 06:12:41 - cd /src/sys/powerpc/conf
TB --- 2010-03-11 06:12:41 - /usr/bin/make -B LINT
TB --- 2010-03-11 06:12:41 - building LINT kernel
TB --- 2010-03-11 06:12:41 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 06:12:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 06:12:41 - TARGET=powerpc
TB --- 2010-03-11 06:12:41 - TARGET_ARCH=powerpc
TB --- 2010-03-11 06:12:41 - TZ=UTC
TB --- 2010-03-11 06:12:41 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 06:12:41 - cd /src
TB --- 2010-03-11 06:12:41 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 06:12:41 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -mno-altivec -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/powerpc/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 06:29:31 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 06:29:31 - ERROR: failed to build lint kernel
TB --- 2010-03-11 06:29:31 - 3629.47 user 614.12 system 4685.83 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:39:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 16679106566B
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 06:39:25 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Received: from monday.kientzle.com (kientzle.com [66.166.149.50])
by mx1.freebsd.org (Postfix) with ESMTP id DF9FE8FC14
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 06:39:24 +0000 (UTC)
Received: (from root@localhost)
by monday.kientzle.com (8.14.3/8.14.3) id o2B6dYNR039139
for freebsd-current@freebsd.org; Thu, 11 Mar 2010 06:39:34 GMT
(envelope-from kientzle@freebsd.org)
Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2])
by kientzle.com with SMTP id 2asud82b3iaacbydc7tty2c5i6;
for freebsd-current@freebsd.org;
Thu, 11 Mar 2010 06:39:34 +0000 (UTC)
(envelope-from kientzle@freebsd.org)
Message-ID: <4B989064.5030105@freebsd.org>
Date: Wed, 10 Mar 2010 22:40:36 -0800
From: Tim Kientzle <kientzle@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16
MIME-Version: 1.0
To: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: X11 crash on exit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:39:25 -0000
Trying to get X up and running on my Aspire One netbook
and having a couple of problems. Here's the first:
Whenever I exit, the server gets a Signal 11 and crashes,
corrupting the screen. So far, I've been able to just
tap the power button to get a clean reboot (in particular,
it's just X crashing, not the whole system).
FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009 GENERIC i386
xorg.conf is pretty vanilla except for the two monitors: 1600x1200
external on the VGA connector and 1024x600 LVDS display. This was
autoprobed by the server:
Section "Device"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GME Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
Option "monitor-LVDS" "LVDSMonitor"
Option "monitor-VGA" "VGAMonitor"
EndSection
A backtrace from the server core:
#0 0x08092402 in DeliverEventsToWindow ()
#1 0x0816e37e in ShouldFreeInputMasks ()
#2 0x081788e9 in SProcXListDeviceProperties ()
#3 0x0807ecf5 in DisableDevice ()
#4 0x0807edfa in DisableDevice ()
#5 0x080cbc5d in xf86PostMotionEvent ()
#6 0x0807eafb in ActivateDevice ()
#7 0x0812d168 in LogSetParameter ()
#8 0x0812d74f in AuditF ()
#9 0x080bc373 in xf86PrintBacktrace ()
#10 <signal handler called>
#11 0x081534d6 in ProcRRDeleteOutputProperty ()
#12 0x00000030 in ?? ()
#13 0x081534bb in ProcRRDeleteOutputProperty ()
#14 0x5a5a5a5a in ?? ()
#15 0x287367c0 in ?? ()
#16 0xbfbfecb8 in ?? ()
#17 0x0806ed9e in ProcSetSelectionOwner ()
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:45:27 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D2353106566C;
Thu, 11 Mar 2010 06:45:27 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com
[74.125.83.182])
by mx1.freebsd.org (Postfix) with ESMTP id 682858FC0C;
Thu, 11 Mar 2010 06:45:27 +0000 (UTC)
Received: by pvg3 with SMTP id 3so2979935pvg.13
for <multiple recipients>; Wed, 10 Mar 2010 22:45:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=DKK8WM6roiRfJXKIew9Vdm3UhGxrNZPECAvR1Vs44qc=;
b=IRkHHdzSEF2kYGf9mA/eDxQymeWyXnyANfiAU86B6dysFzdDMVqjSF8itU9PYCTbzN
hVWU7m8cu/qDBpT5Qdahyux2vbrMSf25r2BAuUMsRBxD/XebVgyyFyyLzYSzbs8Q5WvX
OpLTdZw/CE8bmMVz4QFRJpy2fn7ARriBGMWRw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=o4CU1ixFvyaHo2v6lfC1mVLgZnxQQUfU+yMLA4d+tXnAHYnZIBvLFWQ2MwnYCiixTT
A4UB6S+K46piALCoQ73jqt2E+YuGX1yWV+f0YySDzOltDXgDVw+xD9VjRmt5Z73kCc8v
r/HhliQ/fimA3sxvh9JFUmLgc1ZdEk8onf1ko=
MIME-Version: 1.0
Received: by 10.142.152.15 with SMTP id z15mr1157137wfd.341.1268289926889;
Wed, 10 Mar 2010 22:45:26 -0800 (PST)
In-Reply-To: <4B989064.5030105@freebsd.org>
References: <4B989064.5030105@freebsd.org>
Date: Wed, 10 Mar 2010 22:45:26 -0800
Message-ID: <7d6fde3d1003102245l41ab8287r81680aa40281d802@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Tim Kientzle <kientzle@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject: Re: X11 crash on exit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:45:28 -0000
On Wed, Mar 10, 2010 at 10:40 PM, Tim Kientzle <kientzle@freebsd.org> wrote=
:
> Trying to get X up and running on my Aspire One netbook
> and having a couple of problems. =A0Here's the first:
>
> Whenever I exit, the server gets a Signal 11 and crashes,
> corrupting the screen. =A0So far, I've been able to just
> tap the power button to get a clean reboot (in particular,
> it's just X crashing, not the whole system).
>
> FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009 GENERIC =A0i38=
6
>
> xorg.conf is pretty vanilla except for the two monitors: =A01600x1200 ext=
ernal
> on the VGA connector and 1024x600 LVDS display. =A0This was autoprobed by=
the
> server:
>
> Section "Device"
> =A0 =A0 =A0 =A0Identifier =A0"Card0"
> =A0 =A0 =A0 =A0Driver =A0 =A0 =A0"intel"
> =A0 =A0 =A0 =A0VendorName =A0"Intel Corporation"
> =A0 =A0 =A0 =A0BoardName =A0 "Mobile 945GME Express Integrated Graphics C=
ontroller"
> =A0 =A0 =A0 =A0BusID =A0 =A0 =A0 "PCI:0:2:0"
> =A0 =A0 =A0 =A0Option "monitor-LVDS" "LVDSMonitor"
> =A0 =A0 =A0 =A0Option "monitor-VGA" "VGAMonitor"
> EndSection
>
> A backtrace from the server core:
> #0 =A00x08092402 in DeliverEventsToWindow ()
> #1 =A00x0816e37e in ShouldFreeInputMasks ()
> #2 =A00x081788e9 in SProcXListDeviceProperties ()
> #3 =A00x0807ecf5 in DisableDevice ()
> #4 =A00x0807edfa in DisableDevice ()
> #5 =A00x080cbc5d in xf86PostMotionEvent ()
> #6 =A00x0807eafb in ActivateDevice ()
> #7 =A00x0812d168 in LogSetParameter ()
> #8 =A00x0812d74f in AuditF ()
> #9 =A00x080bc373 in xf86PrintBacktrace ()
> #10 <signal handler called>
> #11 0x081534d6 in ProcRRDeleteOutputProperty ()
> #12 0x00000030 in ?? ()
> #13 0x081534bb in ProcRRDeleteOutputProperty ()
> #14 0x5a5a5a5a in ?? ()
> #15 0x287367c0 in ?? ()
> #16 0xbfbfecb8 in ?? ()
> #17 0x0806ed9e in ProcSetSelectionOwner ()
Hi Tim!
X11 appears to crash a lot with SIGSEGV when something library or
application along the way breaks; I've run into this issue multiple
times lately trying to setup my PoC thin client from scratch over the
past couple of days.
Is this recently happening after an application upgrade, or is
this a new [pristine?] machine?
Thanks!
-Garrett
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:46:26 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A47791065675
for <current@freebsd.org>; Thu, 11 Mar 2010 06:46:26 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 24CF48FC1A
for <current@freebsd.org>; Thu, 11 Mar 2010 06:46:25 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NpcA3-0005l2-6a; Thu, 11 Mar 2010 08:46:23 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NpcA0-000ItK-5J; Thu, 11 Mar 2010 08:46:20 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100310195206.GB10657@michelle.cdnetworks.com>
References: <20100310195206.GB10657@michelle.cdnetworks.com>
<20100305175639.GB14818@michelle.cdnetworks.com>
<E1NnVaT-0003Ft-3p@clue.co.za> <E1Nnc4d-0003mB-6e@clue.co.za>
<E1Nne0Q-0003uZ-OR@clue.co.za> <E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
X-Attribution: BOFH
Date: Thu, 11 Mar 2010 08:46:20 +0200
Message-Id: <E1NpcA0-000ItK-5J@clue.co.za>
Cc: David Christensen <davidch@broadcom.com>, current@freebsd.org
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:46:26 -0000
Pyun YongHyeon wrote:
> I successfully reproduced the issue with netperf on BCM5709. You
> can use UDP frame size 1 to trigger the issue.
Now I wish I had paid closer attention ages ago. I actually saw
this when I benchmarked the system post purchase, but didn't
investigate further. I tested and specified the hardware and that
system was forwarding 1MPPS. Then the bean counters got interested
in Dell and they bought something entirely different.
Thanks very, very much for your interest. This is one of the reasons
I love FreeBSD - invariably, the right people are available and
interested.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:48:30 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 040EB106566C;
Thu, 11 Mar 2010 06:48:30 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com
[209.85.160.54])
by mx1.freebsd.org (Postfix) with ESMTP id C67CA8FC12;
Thu, 11 Mar 2010 06:48:29 +0000 (UTC)
Received: by pwj4 with SMTP id 4so44550pwj.13
for <multiple recipients>; Wed, 10 Mar 2010 22:48:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=biP5dTeoz/js2ygNO1pkeMOOtqjBRjDeG9iNR91PxDE=;
b=ssvgDzMopl7ByBdXPsD0gfOWjd4aH+H4CXI/n1GShn4tQoLzzB/rfeCrlUI404l0qG
kaJvtsoYyBDCoa1W+xMNuEwhtPEtoL+82Ix/ueBFM4VkcpwOK3LcORp4vTCsdrRzDjSb
is4X2MesfaCjsRB6EUMTku44jW+SZl6a2deOU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=XLZjY9aUbMu4t6m3zdbnDI+fDkxiAy1M7E5epGOZW+c40pJdrOTwBGeMTEA+LNhLsY
JvFL3VFUnOVB6OmiX9+LWnJnTWYe58uaFSDfcikEb2qR+WpGoNroADIT0T7kmlHyVTa1
TuHqnbMr5dVrS0Pc8RfIJDe4ZKAQHAJ3xhJAs=
MIME-Version: 1.0
Received: by 10.142.55.11 with SMTP id d11mr1215151wfa.1.1268290107983; Wed,
10 Mar 2010 22:48:27 -0800 (PST)
In-Reply-To: <201003110629.o2B6TVta094218@freebsd-current.sentex.ca>
References: <201003110629.o2B6TVta094218@freebsd-current.sentex.ca>
Date: Wed, 10 Mar 2010 22:48:27 -0800
Message-ID: <7d6fde3d1003102248g31b179f7u3bfe848408f91f2e@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: powerpc@freebsd.org, current@freebsd.org
Subject: Re: [head tinderbox] failure on powerpc/powerpc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:48:30 -0000
Weongyo, et all,
On Wed, Mar 10, 2010 at 10:29 PM, FreeBSD Tinderbox
<tinderbox@freebsd.org> wrote:
> TB --- 2010-03-11 05:11:25 - tinderbox 2.6 running on freebsd-current.sen=
tex.ca
> TB --- 2010-03-11 05:11:25 - starting HEAD tinderbox run for powerpc/powe=
rpc
> TB --- 2010-03-11 05:11:25 - cleaning the object tree
> TB --- 2010-03-11 05:11:41 - cvsupping the source tree
> TB --- 2010-03-11 05:11:41 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sente=
x.ca /tinderbox/HEAD/powerpc/powerpc/supfile
> TB --- 2010-03-11 05:12:22 - building world
> TB --- 2010-03-11 05:12:22 - MAKEOBJDIRPREFIX=3D/obj
> TB --- 2010-03-11 05:12:22 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin
> TB --- 2010-03-11 05:12:22 - TARGET=3Dpowerpc
> TB --- 2010-03-11 05:12:22 - TARGET_ARCH=3Dpowerpc
> TB --- 2010-03-11 05:12:22 - TZ=3DUTC
> TB --- 2010-03-11 05:12:22 - __MAKE_CONF=3D/dev/null
> TB --- 2010-03-11 05:12:22 - cd /src
> TB --- 2010-03-11 05:12:22 - /usr/bin/make -B buildworld
>>>> World build started on Thu Mar 11 05:12:23 UTC 2010
>>>> 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 Thu Mar 11 06:12:41 UTC 2010
> TB --- 2010-03-11 06:12:41 - generating LINT kernel config
> TB --- 2010-03-11 06:12:41 - cd /src/sys/powerpc/conf
> TB --- 2010-03-11 06:12:41 - /usr/bin/make -B LINT
> TB --- 2010-03-11 06:12:41 - building LINT kernel
> TB --- 2010-03-11 06:12:41 - MAKEOBJDIRPREFIX=3D/obj
> TB --- 2010-03-11 06:12:41 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin
> TB --- 2010-03-11 06:12:41 - TARGET=3Dpowerpc
> TB --- 2010-03-11 06:12:41 - TARGET_ARCH=3Dpowerpc
> TB --- 2010-03-11 06:12:41 - TZ=3DUTC
> TB --- 2010-03-11 06:12:41 - __MAKE_CONF=3D/dev/null
> TB --- 2010-03-11 06:12:41 - cd /src
> TB --- 2010-03-11 06:12:41 - /usr/bin/make -B buildkernel KERNCONF=3DLINT
>>>> Kernel build for LINT started on Thu Mar 11 06:12:41 UTC 2010
>>>> 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
> [...]
> =3D=3D=3D> siba_bwn (all)
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin=
c =A0 -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_g=
lobal.h -I. -I@ -I@/contrib/altq -finline-limit=3D15000 --param inline-unit=
-growth=3D100 --param large-function-growth=3D1000 -fno-common =A0-mlongcal=
l -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -mno-alt=
ivec -ffreestanding -fstack-protector -std=3Diso9899:1999 -fstack-protector=
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes =A0-Wmissing-=
prototypes -Wpointer-arith -Winline -Wcast-qual =A0-Wundef -Wno-pointer-sig=
n -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core=
.c
> cc1: warnings being treated as errors
> /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_d=
ma_translation':
> /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: deref=
erencing 'void *' pointer
> /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request=
for member 'sd_bus' in something not a structure or union
> /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: deref=
erencing 'void *' pointer
> /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request=
for member 'sd_bus' in something not a structure or union
> *** Error code 1
>
> Stop in /src/sys/modules/siba_bwn.
> *** Error code 1
>
> Stop in /src/sys/modules.
> *** Error code 1
>
> Stop in /obj/powerpc/src/sys/LINT.
> *** Error code 1
>
> Stop in /src.
> *** Error code 1
>
> Stop in /src.
> TB --- 2010-03-11 06:29:31 - WARNING: /usr/bin/make returned exit code =
=A01
> TB --- 2010-03-11 06:29:31 - ERROR: failed to build lint kernel
> TB --- 2010-03-11 06:29:31 - 3629.47 user 614.12 system 4685.83 real
Could someone please try this patch to see whether or not it fixes
the void* deref issue? I don't think it's style(9) correct, but it
might resolve the issue.
Thanks,
-Garrett
Index: siba_core.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- siba_core.c (revision 204996)
+++ siba_core.c (working copy)
@@ -2032,9 +2032,9 @@
siba_dma_translation(device_t dev)
{
- KASSERT(device_get_ivars(dev)->sd_bus->siba_type =3D=3D SIBA_TYPE_PCI,
- ("unsupported bustype %d\n",
- device_get_ivars(dev)->sd_bus->siba_type));
+ KASSERT(((struct siba_softc *) device_get_ivars(dev))->sd_bus->siba_type =
=3D=3D
+ SIBA_TYPE_PCI, ("unsupported bustype %d\n",
+ ((struct siba_softc*) device_get_ivars(dev))->sd_bus->siba_type));
return (SIBA_PCI_DMA);
}
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:49:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 169AC106567A;
Thu, 11 Mar 2010 06:49:57 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E54C78FC25;
Thu, 11 Mar 2010 06:49:56 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B6nu5q057768; Thu, 11 Mar 2010 01:49:56 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B6nuZA057767;
Thu, 11 Mar 2010 06:49:56 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 06:49:56 GMT
Message-Id: <201003110649.o2B6nuZA057767@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<sparc64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on sparc64/sparc64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 06:49:57 -0000
TB --- 2010-03-11 05:36:17 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 05:36:17 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-03-11 05:36:17 - cleaning the object tree
TB --- 2010-03-11 05:36:34 - cvsupping the source tree
TB --- 2010-03-11 05:36:34 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile
TB --- 2010-03-11 05:37:04 - building world
TB --- 2010-03-11 05:37:04 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 05:37:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 05:37:04 - TARGET=sparc64
TB --- 2010-03-11 05:37:04 - TARGET_ARCH=sparc64
TB --- 2010-03-11 05:37:04 - TZ=UTC
TB --- 2010-03-11 05:37:04 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 05:37:04 - cd /src
TB --- 2010-03-11 05:37:04 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 05:37:04 UTC 2010
>>> 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 Thu Mar 11 06:33:09 UTC 2010
TB --- 2010-03-11 06:33:09 - generating LINT kernel config
TB --- 2010-03-11 06:33:09 - cd /src/sys/sparc64/conf
TB --- 2010-03-11 06:33:09 - /usr/bin/make -B LINT
TB --- 2010-03-11 06:33:09 - building LINT kernel
TB --- 2010-03-11 06:33:09 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 06:33:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 06:33:09 - TARGET=sparc64
TB --- 2010-03-11 06:33:09 - TARGET_ARCH=sparc64
TB --- 2010-03-11 06:33:09 - TZ=UTC
TB --- 2010-03-11 06:33:09 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 06:33:09 - cd /src
TB --- 2010-03-11 06:33:09 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 06:33:09 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/sparc64/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 06:49:56 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 06:49:56 - ERROR: failed to build lint kernel
TB --- 2010-03-11 06:49:56 - 3495.35 user 600.04 system 4419.16 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 07:06:11 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C6A05106566B
for <current@freebsd.org>; Thu, 11 Mar 2010 07:06:11 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id 464FA8FC12
for <current@freebsd.org>; Thu, 11 Mar 2010 07:06:10 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NpcTA-0007k4-EV; Thu, 11 Mar 2010 09:06:08 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NpcT6-000IuH-FO; Thu, 11 Mar 2010 09:06:04 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20100310230220.GI10657@michelle.cdnetworks.com>
References: <20100310230220.GI10657@michelle.cdnetworks.com>
<E1Nnc4d-0003mB-6e@clue.co.za> <E1Nne0Q-0003uZ-OR@clue.co.za>
<E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310195206.GB10657@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
X-Attribution: BOFH
Date: Thu, 11 Mar 2010 09:06:04 +0200
Message-Id: <E1NpcT6-000IuH-FO@clue.co.za>
Cc: David Christensen <davidch@broadcom.com>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 07:06:11 -0000
Pyun YongHyeon wrote:
> On Wed, Mar 10, 2010 at 02:45:47PM -0800, David Christensen wrote:
> > The bce(4) hardware supports a linked list of pages for RX
> > buffer descriptors. The stock build supports 2 pages (RX_PAGES)
> > with a total of 511 BD's per page. The hardware can support a
> > maximum of 64K BD's but that would be an unnecessarily large
> > amount of mbufs for an infrequent problem.
I think that depends on how you define infrequent. Our use case
is a largish core router. It's highly likely that we'll see this
again and again in various packet storms on our network.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 07:08:46 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E7A821065672;
Thu, 11 Mar 2010 07:08:45 +0000 (UTC)
(envelope-from tinderbox@freebsd.org)
Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca
[64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id C23118FC1E;
Thu, 11 Mar 2010 07:08:45 +0000 (UTC)
Received: from freebsd-current.sentex.ca (localhost [127.0.0.1])
by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id
o2B78juT086803; Thu, 11 Mar 2010 02:08:45 -0500 (EST)
(envelope-from tinderbox@freebsd.org)
Received: (from tinderbox@localhost)
by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o2B78jkc086802;
Thu, 11 Mar 2010 07:08:45 GMT (envelope-from tinderbox@freebsd.org)
Date: Thu, 11 Mar 2010 07:08:45 GMT
Message-Id: <201003110708.o2B78jkc086802@freebsd-current.sentex.ca>
X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to
FreeBSD Tinderbox <tinderbox@freebsd.org> using -f
Sender: FreeBSD Tinderbox <tinderbox@freebsd.org>
From: FreeBSD Tinderbox <tinderbox@freebsd.org>
To: FreeBSD Tinderbox <tinderbox@freebsd.org>, <current@freebsd.org>,
<sparc64@freebsd.org>
Precedence: bulk
Cc:
Subject: [head tinderbox] failure on sparc64/sun4v
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 07:08:46 -0000
TB --- 2010-03-11 05:57:33 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-11 05:57:33 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-03-11 05:57:33 - cleaning the object tree
TB --- 2010-03-11 05:57:44 - cvsupping the source tree
TB --- 2010-03-11 05:57:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile
TB --- 2010-03-11 05:58:10 - building world
TB --- 2010-03-11 05:58:10 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 05:58:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 05:58:10 - TARGET=sun4v
TB --- 2010-03-11 05:58:10 - TARGET_ARCH=sparc64
TB --- 2010-03-11 05:58:10 - TZ=UTC
TB --- 2010-03-11 05:58:10 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 05:58:10 - cd /src
TB --- 2010-03-11 05:58:10 - /usr/bin/make -B buildworld
>>> World build started on Thu Mar 11 05:58:10 UTC 2010
>>> 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 Thu Mar 11 06:51:45 UTC 2010
TB --- 2010-03-11 06:51:45 - generating LINT kernel config
TB --- 2010-03-11 06:51:45 - cd /src/sys/sun4v/conf
TB --- 2010-03-11 06:51:45 - /usr/bin/make -B LINT
TB --- 2010-03-11 06:51:45 - building LINT kernel
TB --- 2010-03-11 06:51:45 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-03-11 06:51:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-03-11 06:51:45 - TARGET=sun4v
TB --- 2010-03-11 06:51:45 - TARGET_ARCH=sparc64
TB --- 2010-03-11 06:51:45 - TZ=UTC
TB --- 2010-03-11 06:51:45 - __MAKE_CONF=/dev/null
TB --- 2010-03-11 06:51:45 - cd /src
TB --- 2010-03-11 06:51:45 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Thu Mar 11 06:51:45 UTC 2010
>>> 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
[...]
===> siba_bwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sun4v/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/sun4v/src/sys/LINT -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c
cc1: warnings being treated as errors
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c: In function 'siba_dma_translation':
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: warning: dereferencing 'void *' pointer
/src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
*** Error code 1
Stop in /src/sys/modules/siba_bwn.
*** Error code 1
Stop in /src/sys/modules.
*** Error code 1
Stop in /obj/sun4v/src/sys/LINT.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2010-03-11 07:08:45 - WARNING: /usr/bin/make returned exit code 1
TB --- 2010-03-11 07:08:45 - ERROR: failed to build lint kernel
TB --- 2010-03-11 07:08:45 - 3499.16 user 582.64 system 4271.66 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 08:09:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 776D6106566C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 08:09:00 +0000 (UTC)
(envelope-from giovanni.trematerra@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 0A9DF8FC23
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 08:08:59 +0000 (UTC)
Received: by fxm23 with SMTP id 23so7995748fxm.3
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 00:08:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=99WC2LNo2OvAwJ5+NAk+RYcYR+aDtJTT5R23IBVOYtE=;
b=GzntK3OBksuOUMuAppByTfm9GgH/2VrVoVpl/HrGqBKuG29TJOZ2nWxZ48c3YZGQPc
fsoGTPeiNRpUD4xybJZaod1KhUkX0NA+yKuxmQyDDs36MN7fwIwo3oFJ56jr71viqQUO
Sri91dg7t+RjV1JS9LYOSSPBAdljaPDrWA/cs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=Sv3C4Q9UzWw0719qzNVKxRS1pCMGMkSI7FzaIHK+b2OQRjMKHoxP0Nxw8jN7R4N4a+
63XSEA4ALV7oIUCYjj/qHgPnS7/Q85oRYXtb/onoN42PTH2DnEspNic37/0M5oWVlRTW
iWRoSimawTnE02F7Ct2+2xqEgFc+Oq/tNJi2A=
MIME-Version: 1.0
Received: by 10.223.75.15 with SMTP id w15mr2989843faj.70.1268294935025; Thu,
11 Mar 2010 00:08:55 -0800 (PST)
In-Reply-To: <7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
<4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
<7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
Date: Thu, 11 Mar 2010 09:08:54 +0100
Message-ID: <4e6cba831003110008p41a573aah9233dcacc397ccb5@mail.gmail.com>
From: Giovanni Trematerra <giovanni.trematerra@gmail.com>
To: Tom Couch <tom.couch.storage@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-current@freebsd.org
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 08:09:00 -0000
On Wed, Mar 10, 2010 at 11:07 PM, Tom Couch <tom.couch.storage@gmail.com> wrote:
> Hi FreeBSD-current,
>
> I am available to maintain the twa driver, now that I am on this list.
> Let me know how I can help,
Hi Tom,
That's a good news to hear!
You could take a look at GNATS database where problems are reported by
the users and
find out if there are any PRs open for twa driver.
http://www.freebsd.org/cgi/query-pr-summary.cgi?query
Many users post problem report to the list too, so stay tuned!
Nonetheless you can post patches if you discover some bugs or if you'd
like to improve the driver code.
--
Gianni
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 08:10:43 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 76D89106564A;
Thu, 11 Mar 2010 08:10:43 +0000 (UTC)
(envelope-from thompsa@FreeBSD.org)
Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226])
by mx1.freebsd.org (Postfix) with ESMTP id 32CC48FC12;
Thu, 11 Mar 2010 08:10:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by pele.citylink.co.nz (Postfix) with ESMTP id 14C2A7B6CE;
Thu, 11 Mar 2010 21:10:42 +1300 (NZDT)
X-Virus-Scanned: Debian amavisd-new at citylink.co.nz
Received: from pele.citylink.co.nz ([127.0.0.1])
by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id MBbErbHA7fs0; Thu, 11 Mar 2010 21:10:36 +1300 (NZDT)
Received: from citylink.fud.org.nz (unknown [202.8.44.45])
by pele.citylink.co.nz (Postfix) with ESMTP;
Thu, 11 Mar 2010 21:10:36 +1300 (NZDT)
Received: by citylink.fud.org.nz (Postfix, from userid 1001)
id C92EA11434; Thu, 11 Mar 2010 21:10:35 +1300 (NZDT)
Date: Thu, 11 Mar 2010 21:10:35 +1300
From: Andrew Thompson <thompsa@FreeBSD.org>
To: Garrett Cooper <yanefbsd@gmail.com>
Message-ID: <20100311081035.GA45454@citylink.fud.org.nz>
References: <201003110629.o2B6TVta094218@freebsd-current.sentex.ca>
<7d6fde3d1003102248g31b179f7u3bfe848408f91f2e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7d6fde3d1003102248g31b179f7u3bfe848408f91f2e@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: powerpc@freebsd.org, Weongyo Jeong <weongyo@FreeBSD.org>,
FreeBSD Tinderbox <tinderbox@freebsd.org>, current@freebsd.org
Subject: Re: [head tinderbox] failure on powerpc/powerpc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 08:10:43 -0000
On Wed, Mar 10, 2010 at 10:48:27PM -0800, Garrett Cooper wrote:
> Weongyo, et all,
>
> On Wed, Mar 10, 2010 at 10:29 PM, FreeBSD Tinderbox
> > /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
> > *** Error code 1
> >
> > Stop in /src/sys/modules/siba_bwn.
> > *** Error code 1
> >
> > Stop in /src/sys/modules.
> > *** Error code 1
> >
> > Stop in /obj/powerpc/src/sys/LINT.
> > *** Error code 1
> >
> > Stop in /src.
> > *** Error code 1
> >
> > Stop in /src.
> > TB --- 2010-03-11 06:29:31 - WARNING: /usr/bin/make returned exit code ?1
> > TB --- 2010-03-11 06:29:31 - ERROR: failed to build lint kernel
> > TB --- 2010-03-11 06:29:31 - 3629.47 user 614.12 system 4685.83 real
>
> Could someone please try this patch to see whether or not it fixes
> the void* deref issue? I don't think it's style(9) correct, but it
> might resolve the issue.
> Thanks,
> -Garrett
>
> Index: siba_core.c
> ===================================================================
> --- siba_core.c (revision 204996)
> +++ siba_core.c (working copy)
> @@ -2032,9 +2032,9 @@
> siba_dma_translation(device_t dev)
> {
>
> - KASSERT(device_get_ivars(dev)->sd_bus->siba_type == SIBA_TYPE_PCI,
> - ("unsupported bustype %d\n",
> - device_get_ivars(dev)->sd_bus->siba_type));
> + KASSERT(((struct siba_softc *) device_get_ivars(dev))->sd_bus->siba_type ==
> + SIBA_TYPE_PCI, ("unsupported bustype %d\n",
> + ((struct siba_softc*) device_get_ivars(dev))->sd_bus->siba_type));
>
It was all getting a bit unwieldy, I committed a more simple fix in
r205003.
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 10:52:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1951F106566C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 10:52:56 +0000 (UTC)
(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
by mx1.freebsd.org (Postfix) with ESMTP id BB9D38FC0C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 10:52:56 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o2BAqtSA015296;
Thu, 11 Mar 2010 02:52:56 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Mar 2010 02:52:46 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <4B980347.8020500@protected-networks.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: AcrAkatm/dHl6mY/SOipMBL1JsGTBAAcHXvg
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org>
<4B978E41.4010800@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
<4B980347.8020500@protected-networks.net>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Michael Butler" <imb@protected-networks.net>
Cc: freebsd-current@freebsd.org
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 10:52:57 -0000
>=20
> Without the route.h patch, I can't ping 127.0.0.1 or the local or
> remote address of the OpenVPN tunnel (on tap0). In fact, you=20
> can't even build OpenVPN from ports as it'll fail its self-test.
>=20
Please see my previous clarification email on the what and the why
about the "route.h.diff" patch. =20
I spent some time looking into the issue and found the problem=20
is the if_tap interface turns out to be one of those interfaces=20
that claims to be of IFT_ETHER type, but does not touch the=20
"if_link_state" variable.
>
> With the route.h patch, I can ping all local addresses but not the=20
> far end of the tunnel.
>=20
Please try the new patch at
http://people.freebsd.org/~qingli/ecmp-tap.diff
Let me know how it works out for you.
-- Qing
P.S. You really just need the 2-line fix in the if_tap.c file.
route.h is slightly touch to be (ifp) instead of just ifp in
the macro.
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 13:47:26 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D6C1A1065673
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 13:47:26 +0000 (UTC)
(envelope-from uqs@spoerlein.net)
Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2001:470:9a47::1])
by mx1.freebsd.org (Postfix) with ESMTP id 93F648FC19
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 13:47:26 +0000 (UTC)
Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1])
by acme.spoerlein.net (Postfix) with ESMTPS id E307F5CA8
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 14:47:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net;
s=dkim200908; t=1268315246;
bh=7WLqooqLLJSctiE5z8Hg4eE0AfIU1e4qCqWjxu+0n98=;
h=Date:From:To:Subject:Message-ID:References:MIME-Version:
Content-Type:In-Reply-To;
b=JwHKiFuvXxMKwHVdxIVsSNyabUjaVZJqsYz1TyoEZwq+ZXHqD4tzpdXFr7rjDWEB2
EFIcgNYTbGjgyIyPbF1wcqkAfTIJ7alx26FCtwgZlmKDyxiJwA0u8swOdMlazJ1vNp
pmLOYQ5uNO4NsmuODlK1iLHWGQZ2BcRNXjhNsG0w=
Received: (from uqs@localhost)
by acme.spoerlein.net (8.14.4/8.14.4/Submit) id o2BDlPfH050862
for freebsd-current@freebsd.org; Thu, 11 Mar 2010 14:47:25 +0100 (CET)
(envelope-from uqs@spoerlein.net)
Date: Thu, 11 Mar 2010 14:47:25 +0100
From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@spoerlein.net>
To: freebsd-current@freebsd.org
Message-ID: <20100311134725.GU12229@acme.spoerlein.net>
Mail-Followup-To: freebsd-current@freebsd.org
References: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
<4B94D1FC.1050407@FreeBSD.org>
<20100308105243.GA31468@office.redwerk.com>
<20100308110919.GA31573@office.redwerk.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100308110919.GA31573@office.redwerk.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 13:47:26 -0000
On Mon, 08.03.2010 at 13:09:19 +0200, Eugene Dzhurinsky wrote:
> On Mon, Mar 08, 2010 at 12:52:43PM +0200, Eugene Dzhurinsky wrote:
> > dd if=/dev/ad4 of=/dev/null skip=222342559 bs=512 count=1
> > dd: /dev/ad4: Input/output error
> > 0+0 records in
> > 0+0 records out
> > 0 bytes transferred in 2.351940 secs (0 bytes/sec)
> >
> > dd if=/dev/zero of=/dev/ad4 seek=222342559 bs=512 count=1
> > dd: /dev/ad4: Operation not permitted
> >
> > Should I do it in single mode?
>
> sysctl kern.geom.debugflags=0x10
>
> Did the trick, I was able to write directly to the sector, and now it seems to
> work well. No remaps recorded thus, but no errors so far.
It's too late now, but you really should have gone with something like
# recoverdisk /dev/ad4 /dev/ad4
this will re-write all blocks on the disk, it may fail at reading block
222342559, but there's a chance that the disk error correction gets it
right after a couple of times.
Regards,
Uli
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 14:20:07 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3681A1065673
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 14:20:07 +0000 (UTC)
(envelope-from imb@protected-networks.net)
Received: from sarah.protected-networks.net (sarah.protected-networks.net
[IPv6:2001:470:1f07:4e1::1])
by mx1.freebsd.org (Postfix) with ESMTP id E94068FC1B
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 14:20:06 +0000 (UTC)
Received: from toshi.auburn.protected-networks.net
(toshi.auburn.protected-networks.net [202.12.127.84])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(Client CN "Iain Butler",
Issuer "RSA Class 2 Personal CA" (verified OK))
(Authenticated sender: imb)
by sarah.protected-networks.net (Postfix) with ESMTPSA id 89F87617B;
Thu, 11 Mar 2010 09:20:05 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
d=protected-networks.net; s=200705; t=1268317205;
bh=0P5L4muKXvePXplTcxk3EW9CcctAQPClpsCxi3SrVdg=;
h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:
In-Reply-To:Content-Type:Content-Transfer-Encoding;
b=P+JpwnqVEXe99s2dMOR6JXYEqkIeYDckjnLMn6ctom2QVeq1BBRM+G+MXgtGtWr5F
tUe6nOzgStB48BFoVgzuTkFDASx6Xu7p2E4cAz4oPz+4YxX46wQujKwFUX8sj0k
DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws;
q=dns;
h=message-id:date:from:user-agent:mime-version:to:cc:subject:
references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding;
b=KF9U824MQnYn2eZXpOLVJntzSzrWG2L0+0mWmiFlW/pmdf129cOdDReiYy9Ar4En4
XpsmqOW9SqqRlVtIYdqC7pEcV4Ja9UhBwiah+e61SjTqgwi7PAMruJMxIW+MLu8
Message-ID: <4B98FC10.6070700@protected-networks.net>
Date: Thu, 11 Mar 2010 09:20:00 -0500
From: Michael Butler <imb@protected-networks.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: "Li, Qing" <qing.li@bluecoat.com>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org>
<4B978E41.4010800@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
<4B980347.8020500@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com>
X-Enigmail-Version: 1.0.1
OpenPGP: id=0442D492
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 14:20:07 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/11/10 05:52, Li, Qing wrote:
> I spent some time looking into the issue and found the problem
> is the if_tap interface turns out to be one of those interfaces
> that claims to be of IFT_ETHER type, but does not touch the
> "if_link_state" variable.
[ .. ]
> Please try the new patch at
>
> http://people.freebsd.org/~qingli/ecmp-tap.diff
>
> Let me know how it works out for you.
This solves all the noted issues - thanks!
imb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
iEYEARECAAYFAkuY/BAACgkQQv9rrgRC1JLoxACeLApgw4GJzTpukzV4AHzp9ffm
4XwAn1GbXEojETUiXgAze7hIfgNcJSDF
=5iWa
-----END PGP SIGNATURE-----
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 14:50:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D3F401065700;
Thu, 11 Mar 2010 14:50:15 +0000 (UTC)
(envelope-from nwhitehorn@freebsd.org)
Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212])
by mx1.freebsd.org (Postfix) with ESMTP id A39FF8FC2A;
Thu, 11 Mar 2010 14:50:15 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by
smtpauth3.wiscmail.wisc.edu
(Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30
2009)) id <0KZ40030GH7QK900@smtpauth3.wiscmail.wisc.edu>; Thu,
11 Mar 2010 08:50:14 -0600 (CST)
Received: from comporellon.tachypleus.net
(adsl-76-233-145-10.dsl.mdsnwi.sbcglobal.net [76.233.145.10])
by smtpauth3.wiscmail.wisc.edu
(Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30
2009))
with ESMTPSA id <0KZ400MZ3H7IHK40@smtpauth3.wiscmail.wisc.edu>; Thu,
11 Mar 2010 08:50:07 -0600 (CST)
Date: Thu, 11 Mar 2010 08:50:05 -0600
From: Nathan Whitehorn <nwhitehorn@freebsd.org>
To: FreeBSD-CURRENT Mailing List <freebsd-current@freebsd.org>
Message-id: <4B99031D.3080308@freebsd.org>
X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.233.145.10
X-Spam-PmxInfo: Server=avs-9, Version=5.5.5.374460,
Antispam-Engine: 2.7.1.369594, Antispam-Data: 2010.3.11.143925,
SenderIP=76.233.145.10
User-Agent: Thunderbird 2.0.0.23 (X11/20100206)
Cc: freebsd-amd64@freebsd.org, freebsd-ia64@freebsd.org
Subject: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 14:50:15 -0000
As a result of importing 32-bit compatibility support for non-x86 64-bit
platforms, the kernel options COMPAT_IA32 has been renamed
COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
including this option must be modified accordingly.
-Nathan
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 15:05:27 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 587541065673;
Thu, 11 Mar 2010 15:05:27 +0000 (UTC)
(envelope-from ume@mahoroba.org)
Received: from mail.mahoroba.org (ent.mahoroba.org [IPv6:2001:2f0:104:8010::1])
by mx1.freebsd.org (Postfix) with ESMTP id D04008FC28;
Thu, 11 Mar 2010 15:05:26 +0000 (UTC)
Received: from ameno.mahoroba.org
(IDENT:Y2OeMvPqeoO0s4V6zKftHkUC5opXB9XOCCjoNMe85c5wFJ63/7vHQuLRoiDROjnw@ameno.mahoroba.org
[IPv6:2001:2f0:104:8010:20a:79ff:fe69:ee6b])
(user=ume mech=DIGEST-MD5 bits=0)
by mail.mahoroba.org (8.14.4/8.14.4) with ESMTP/inet6 id o2BF4fUs076566
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 12 Mar 2010 00:05:21 +0900 (JST)
(envelope-from ume@mahoroba.org)
Date: Fri, 12 Mar 2010 00:04:41 +0900
Message-ID: <ygepr3adhme.wl%ume@mahoroba.org>
From: Hajimu UMEMOTO <ume@freebsd.org>
To: Nathan Whitehorn <nwhitehorn@freebsd.org>
In-Reply-To: <4B99031D.3080308@freebsd.org>
References: <4B99031D.3080308@freebsd.org>
User-Agent: xcite1.58> Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6
(Maruoka) FLIM/1.14.9 (=?ISO-2022-JP-2?B?R29qGyQoRCtXGyhC?=) APEL/10.7
Emacs/23.1 (i386-portbld-freebsd8.0) MULE/6.0 (HANACHIRUSATO)
X-Operating-System: FreeBSD 8.0-RELEASE-p2
X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc
X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE
Organization: Internet Mutual Aid Society, YOKOHAMA
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3
(mail.mahoroba.org [IPv6:2001:2f0:104:8010::1]);
Fri, 12 Mar 2010 00:05:21 +0900 (JST)
X-Virus-Scanned: clamav-milter 0.95.3 at asuka.mahoroba.org
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00
autolearn=ham version=3.3.0
X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on asuka.mahoroba.org
Cc: FreeBSD-CURRENT Mailing List <freebsd-current@freebsd.org>,
freebsd-amd64@freebsd.org, freebsd-ia64@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:05:27 -0000
Hi,
>>>>> On Thu, 11 Mar 2010 08:50:05 -0600
>>>>> Nathan Whitehorn <nwhitehorn@freebsd.org> said:
nwhitehorn> As a result of importing 32-bit compatibility support for non-x86 64-bit
nwhitehorn> platforms, the kernel options COMPAT_IA32 has been renamed
nwhitehorn> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
nwhitehorn> including this option must be modified accordingly.
Doesn't this mean we cannot have FreeBSD version 32? :)
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 15:13:08 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8306E106566B;
Thu, 11 Mar 2010 15:13:08 +0000 (UTC) (envelope-from scf@FreeBSD.org)
Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f0f:20:2::11])
by mx1.freebsd.org (Postfix) with ESMTP id 48C9B8FC0C;
Thu, 11 Mar 2010 15:13:08 +0000 (UTC)
Received: from thor.farley.org (HPooka@thor.farley.org
[IPv6:2001:470:1f0f:20:1::5])
by mail.farley.org (8.14.4/8.14.4) with ESMTP id o2BFD2Ft076074;
Thu, 11 Mar 2010 09:13:02 -0600 (CST) (envelope-from scf@FreeBSD.org)
Date: Thu, 11 Mar 2010 09:13:02 -0600 (CST)
From: "Sean C. Farley" <scf@FreeBSD.org>
To: Hajimu UMEMOTO <ume@FreeBSD.org>
In-Reply-To: <ygepr3adhme.wl%ume@mahoroba.org>
Message-ID: <alpine.BSF.2.00.1003110911130.97972@thor.farley.org>
References: <4B99031D.3080308@freebsd.org> <ygepr3adhme.wl%ume@mahoroba.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Status: No, score=-2.4 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL
autolearn=no version=3.3.0
X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on mail.farley.org
Cc: FreeBSD-CURRENT Mailing List <freebsd-current@FreeBSD.org>,
Nathan Whitehorn <nwhitehorn@FreeBSD.org>,
freebsd-amd64@FreeBSD.org, freebsd-ia64@FreeBSD.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:13:08 -0000
On Fri, 12 Mar 2010, Hajimu UMEMOTO wrote:
> Hi,
>
>>>>>> On Thu, 11 Mar 2010 08:50:05 -0600
>>>>>> Nathan Whitehorn <nwhitehorn@freebsd.org> said:
>
> nwhitehorn> As a result of importing 32-bit compatibility support for non-x86 64-bit
> nwhitehorn> platforms, the kernel options COMPAT_IA32 has been renamed
> nwhitehorn> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
> nwhitehorn> including this option must be modified accordingly.
>
> Doesn't this mean we cannot have FreeBSD version 32? :)
Think like the U.S. government and push the problem off to the
great*N-grandchildren. ;)
Sean
--
scf@FreeBSD.org
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 15:21:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 11475106566B
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:21:15 +0000 (UTC)
(envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
by mx1.freebsd.org (Postfix) with ESMTP id C66D78FC16
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:21:14 +0000 (UTC)
Received: from ds4.des.no (des.no [84.49.246.2])
by smtp.des.no (Postfix) with ESMTP id CF9601FFC51;
Thu, 11 Mar 2010 15:21:13 +0000 (UTC)
Received: by ds4.des.no (Postfix, from userid 1001)
id B01ED8449F; Thu, 11 Mar 2010 16:21:13 +0100 (CET)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Miroslav Lachman <000.fbsd@quip.cz>
References: <20100308102918.GA5485@localhost> <4B94DDC8.5080008@quip.cz>
<20100308115052.GA31896@office.redwerk.com> <4B94FBA6.5090107@quip.cz>
Date: Thu, 11 Mar 2010 16:21:13 +0100
In-Reply-To: <4B94FBA6.5090107@quip.cz> (Miroslav Lachman's message of "Mon,
08 Mar 2010 14:29:10 +0100")
Message-ID: <861vfq995i.fsf@ds4.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:21:15 -0000
Miroslav Lachman <000.fbsd@quip.cz> writes:
> Yes, rewriting by dd or any other way works for reallocating or
> clearing pending sectors counter, but in server environment
In a server environment, you'd be a fool not to have some sort of
redundancy set up.
> I need to know the affected file, as it can be for example database
> file and then it is a big problem! Rewriting the sector inside InnoDB
> ib_data file can cause DB crash, data loss etc.
How is that different from *not* rewriting the sector? If there's a bad
sector somewhere in your data, your database is still going to crash.
DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 15:24:06 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E2B771065670
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:24:06 +0000 (UTC)
(envelope-from svein-listmail@stillbilde.net)
Received: from mail.stillbilde.net (unknown
[IPv6:2002:51af:3dc3:0:20c:29ff:fece:79f3])
by mx1.freebsd.org (Postfix) with ESMTP id 726E08FC1B
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:24:06 +0000 (UTC)
Received: from [IPv6:2002:51af:3dc3:0:79cc:a126:7e59:782f] (unknown
[IPv6:2002:51af:3dc3:0:79cc:a126:7e59:782f])
(Authenticated sender: svein-listmail)
by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id C5CB323
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 16:24:23 +0100 (CET)
Message-ID: <4B990B24.9080402@stillbilde.net>
Date: Thu, 11 Mar 2010 16:24:20 +0100
From: "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <20100308102918.GA5485@localhost>
<4B94DDC8.5080008@quip.cz> <20100308115052.GA31896@office.redwerk.com>
<4B94FBA6.5090107@quip.cz> <861vfq995i.fsf@ds4.des.no>
In-Reply-To: <861vfq995i.fsf@ds4.des.no>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:24:07 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11.03.2010 16:21, Dag-Erling Smørgrav wrote:
> Miroslav Lachman <000.fbsd@quip.cz> writes:
>> Yes, rewriting by dd or any other way works for reallocating or
>> clearing pending sectors counter, but in server environment
>
> In a server environment, you'd be a fool not to have some sort of
> redundancy set up.
>
>> I need to know the affected file, as it can be for example database
>> file and then it is a big problem! Rewriting the sector inside InnoDB
>> ib_data file can cause DB crash, data loss etc.
>
> How is that different from *not* rewriting the sector? If there's a bad
> sector somewhere in your data, your database is still going to crash.
Only if he hasn't listened to your first advice and set it up on a
non-redundant IO solution. If he's set it up on proper hardware, he'll
just get a friendly mail about replacing said disk next time he's in the
serverroom with a new fresh hostpare.
//Svein
- --
- --------+-------------------+-------------------------------
/"\ |Svein Skogen | svein@d80.iso100.no
\ / |Solberg Østli 9 | PGP Key: 0xE5E76831
X |2020 Skedsmokorset | svein@jernhuset.no
/ \ |Norway | PGP Key: 0xCE96CE13
| | svein@stillbilde.net
ascii | | PGP Key: 0x58CD33B6
ribbon |System Admin | svein-listmail@stillbilde.net
Campaign|stillbilde.net | PGP Key: 0x22D494A4
+-------------------+-------------------------------
|msn messenger: | Mobile Phone: +47 907 03 575
|svein@jernhuset.no | RIPE handle: SS16503-RIPE
- --------+-------------------+-------------------------------
If you really are in a hurry, mail me at
svein-mobile@stillbilde.net
This mailbox goes directly to my cellphone and is checked
even when I'm not in front of my computer.
- ------------------------------------------------------------
Picture Gallery:
https://gallery.stillbilde.net/v/svein/
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuZCyQACgkQODUnwSLUlKS2ngCgqF+bE4SqHC39lYAoMpQG1Ysb
IzcAoLusP1O4LV0CDoq3GSXjV3YGDLDk
=Ljac
-----END PGP SIGNATURE-----
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 15:46:33 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E8D86106564A
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:46:32 +0000 (UTC)
(envelope-from mexas@bristol.ac.uk)
Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78])
by mx1.freebsd.org (Postfix) with ESMTP id 328A78FC26
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 15:46:31 +0000 (UTC)
Received: from ncsc.bris.ac.uk ([137.222.10.41])
by dirj.bris.ac.uk with esmtp (Exim 4.69)
(envelope-from <mexas@bristol.ac.uk>)
id 1Npkaj-0007gS-Er; Thu, 11 Mar 2010 15:46:29 +0000
Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241])
by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67)
(envelope-from <mexas@bristol.ac.uk>)
id 1Npkai-0000RX-AI; Thu, 11 Mar 2010 15:46:28 +0000
Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1])
by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id
o2BFkSwU075041; Thu, 11 Mar 2010 15:46:28 GMT
(envelope-from mexas@bristol.ac.uk)
Received: (from mexas@localhost)
by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.3/Submit) id
o2BFkR3C075040; Thu, 11 Mar 2010 15:46:27 GMT
(envelope-from mexas@bristol.ac.uk)
X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to
mexas@bristol.ac.uk using -f
Date: Thu, 11 Mar 2010 15:46:27 +0000
From: Anton Shterenlikht <mexas@bristol.ac.uk>
To: Michael Butler <imb@protected-networks.net>
Message-ID: <20100311154627.GB75005@mech-cluster241.men.bris.ac.uk>
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>
<B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>
<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com>
<4B96FD4B.3090706@FreeBSD.org>
<4B978E41.4010800@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
<4B980347.8020500@protected-networks.net>
<B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com>
<4B98FC10.6070700@protected-networks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B98FC10.6070700@protected-networks.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "Li, Qing" <qing.li@bluecoat.com>, freebsd-current@freebsd.org
Subject: Re: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 15:46:34 -0000
On Thu, Mar 11, 2010 at 09:20:00AM -0500, Michael Butler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 03/11/10 05:52, Li, Qing wrote:
> > I spent some time looking into the issue and found the problem
> > is the if_tap interface turns out to be one of those interfaces
> > that claims to be of IFT_ETHER type, but does not touch the
> > "if_link_state" variable.
>
> [ .. ]
>
> > Please try the new patch at
> >
> > http://people.freebsd.org/~qingli/ecmp-tap.diff
> >
> > Let me know how it works out for you.
>
> This solves all the noted issues - thanks!
same here
many thanks
anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 16:53:42 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E7D19106566C
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 16:53:42 +0000 (UTC)
(envelope-from mike.jakubik@intertainservices.com)
Received: from mail.intertainservices.com (mail.intertainservices.com
[38.99.187.35]) by mx1.freebsd.org (Postfix) with ESMTP id BD5058FC14
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 16:53:42 +0000 (UTC)
Received: from [172.16.10.199] (unknown [172.16.10.199])
by mail.intertainservices.com (Postfix) with ESMTPA id 6645C56491
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 11:36:21 -0500 (EST)
Message-ID: <4B991C00.3010809@intertainservices.com>
Date: Thu, 11 Mar 2010 11:36:16 -0500
From: Mike Jakubik <mike.jakubik@intertainservices.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <4B99031D.3080308@freebsd.org>
In-Reply-To: <4B99031D.3080308@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-intertainservices-MailScanner-Information: Please contact the ISP for more
information
X-intertainservices-MailScanner-ID: 6645C56491.AE88A
X-intertainservices-MailScanner: Found to be clean
X-intertainservices-MailScanner-From: mike.jakubik@intertainservices.com
X-Spam-Status: No
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 16:53:43 -0000
On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> As a result of importing 32-bit compatibility support for non-x86
> 64-bit platforms, the kernel options COMPAT_IA32 has been renamed
> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
> including this option must be modified accordingly.
>
That sounds a bit confusing, compatibility with FreeBSD 3.2?
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 17:04:42 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C83C1106564A
for <current@freebsd.org>; Thu, 11 Mar 2010 17:04:42 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org
(adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122])
by mx1.freebsd.org (Postfix) with ESMTP id 3E9EE8FC25
for <current@freebsd.org>; Thu, 11 Mar 2010 17:04:40 +0000 (UTC)
Received: from bunrab.catwhisker.org (localhost [127.0.0.1])
by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id o2BH4euF002677
for <current@freebsd.org>; Thu, 11 Mar 2010 09:04:40 -0800 (PST)
(envelope-from david@bunrab.catwhisker.org)
Received: (from david@localhost)
by bunrab.catwhisker.org (8.13.3/8.13.3/Submit) id o2BH4eAv002676
for current@freebsd.org; Thu, 11 Mar 2010 09:04:40 -0800 (PST)
(envelope-from david)
Date: Thu, 11 Mar 2010 09:04:40 -0800
From: David Wolfskill <david@catwhisker.org>
To: current@freebsd.org
Message-ID: <20100311170440.GR57205@bunrab.catwhisker.org>
Mail-Followup-To: David Wolfskill <david@catwhisker.org>, current@freebsd.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="wOOEd1gxhwV8K3c+"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Cc:
Subject: SMP deadlock during multi-user mode transition after r204866
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 17:04:42 -0000
--wOOEd1gxhwV8K3c+
Content-Type: multipart/mixed; boundary="MgsldsnE3DYXgZCe"
Content-Disposition: inline
--MgsldsnE3DYXgZCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
My build machine (dmesg attached) is a dual CPU, single-core box; my
laptop is a single CPU, single-core box. I track head on each daily;
while the build machine has been locking up during the transition to
multi-user mode since Tuesday (when I had built CURRENT at r204909;
previous was r204866, on Monday) -- and it boots to single-user mode OK
-- the laptop has not exhibited the problem.
This build machine was deployed fairly recently, and since a GENERIC
kernel had been working OK, I had left it that way (so that's the kernel
config). I have a more customized config I had used on its predecessor;
I'm pretty sure I had that set up with DDB & assorted other "goodies" to
try to get something useful out of a misbehaviing system, and am willing
to set that up (but probably won't have time for several hours, at
least, as I need to give a presentation at a work meeting).
One of the more peculiar symptoms is that after such a lock-up, I
power-cycle the machine, then boot to single-user mode, at which point I
typically start with=20
fsck -p
However, since Tuesday, that attempt yields:
Enter full pathname of shell or RETURN for /bin/sh:=20
# fsck -p
/dev/aacd0s4a: LINK COUNT DIR I=3D2 OWNER=3Droot MODE=3D40755
/dev/aacd0s4a: SIZE=3D1024 MTIME=3DMar 11 08:30 2010 COUNT 26 SHOULD BE 27
/dev/aacd0s4a: LINK COUNT INCREASING
/dev/aacd0s4a: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
#=20
My circumvention of choice at the moment is:
# fsck -y / && fsck -p
as it appears that the root file system is the only one thus affected.
Is this sufficently well understood already that I should stop
disturbing folks who are trying to fix it? Would it be usful for me to
configure a kernel that supports DDB & provide a backtrace (and maybe
additional stuff)?
To clarify, it appears that something after r204866 but no later than
r204909 has caused the observed problem.
Thanks.
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--MgsldsnE3DYXgZCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="dmesg.boot"
Content-Transfer-Encoding: quoted-printable
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-CURRENT #92: Mon Mar 8 06:14:22 PST 2010
root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC i386
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.54-MHz 686-class CPU)
Origin =3D "GenuineIntel" Id =3D 0xf41 Stepping =3D 1
Features=3D0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PG=
E,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=3D0x659d<SSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR>
AMD Features=3D0x20100000<NX,LM>
TSC: P-state invariant
real memory =3D 2147483648 (2048 MB)
avail memory =3D 2086187008 (1989 MB)
ACPI APIC Table: <PTLTD APIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 2 package(s) x 1 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 6
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
ioapic2 <Version 2.0> irqs 48-71 on motherboard
kbd1 at kbdmux0
acpi0: <PTLTD RSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <unknown> at device 0.1 (no driver attached)
pci0: <base peripheral> at device 1.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
aac0: <Adaptec SCSI RAID 2200S> mem 0xdc000000-0xdfffffff irq 24 at device =
1.0 on pci2
aac0: Enable Raw I/O
aac0: New comm. interface enabled
aac0: [ITHREAD]
aac0: Adaptec 2200S, aac driver 2.1.9-1
aacp0: <SCSI Passthrough Bus> on aac0
aacp1: <SCSI Passthrough Bus> on aac0
pcib3: <ACPI PCI-PCI bridge> at device 0.2 on pci1
pci3: <ACPI PCI bus> on pcib3
em0: <Intel(R) PRO/1000 Network Connection 6.9.25> port 0x2000-0x203f mem 0=
xd8200000-0xd821ffff irq 54 at device 2.0 on pci3
em0: [FILTER]
em0: Ethernet address: 00:30:48:2d:32:6a
em1: <Intel(R) PRO/1000 Network Connection 6.9.25> port 0x2040-0x207f mem 0=
xd8220000-0xd823ffff irq 55 at device 2.1 on pci3
em1: [FILTER]
em1: Ethernet address: 00:30:48:2d:32:6b
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 4.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 16 at device 6.0 on pci0
pci5: <ACPI PCI bus> on pcib5
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0x1400-0x141f irq 1=
6 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0x1420-0x143f irq 1=
9 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
uhci2: <Intel 82801EB (ICH5) USB controller USB-C> port 0x1440-0x145f irq 1=
8 at device 29.2 on pci0
uhci2: [ITHREAD]
usbus2: <Intel 82801EB (ICH5) USB controller USB-C> on uhci2
uhci3: <Intel 82801EB (ICH5) USB controller USB-D> port 0x1460-0x147f irq 1=
6 at device 29.3 on pci0
uhci3: [ITHREAD]
usbus3: <Intel 82801EB (ICH5) USB controller USB-D> on uhci3
ehci0: <Intel 82801EB/R (ICH5) USB 2.0 controller> mem 0xd8001000-0xd80013f=
f irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus4: EHCI version 1.0
usbus4: <Intel 82801EB/R (ICH5) USB 2.0 controller> on ehci0
pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci6: <ACPI PCI bus> on pcib6
vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem 0xd9000000-0xd9fff=
fff,0xd8300000-0xd8300fff irq 17 at device 1.0 on pci6
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH5 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177=
,0x376,0x14a0-0x14af at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0x=
c9fff,0xca000-0xcafff,0xcb000-0xcf7ff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=3D0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: parallel port not found.
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 122d00000e24
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 122d00000e24
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
ata1: DMA limited to UDMA33, controller found non-ATA66 cable
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus4
acd0: DVDROM <MATSHITADVD-ROM SR-8178/PZ16> at ata1-slave UDMA33=20
aacd0: <RAID 1 (Mirror)> on aac0
aacd0: 34970MB (71619584 sectors)
aacd1: <RAID 1 (Mirror)> on aac0
aacd1: 69974MB (143307008 sectors)
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 8 ports with 8 removable, self powered
ses0 at aacp0 bus 0 scbus0 target 6 lun 0
ses0: <SUPER GEM318 0> Fixed Uninstalled SCSI-2 device=20
ses0: 3.300MB/s transfers
ses0: SAF-TE Compliant Device
pass0 at aacp0 bus 0 scbus0 target 0 lun 0
pass0: <SEAGATE ST336754LC 0003> Fixed Uninstalled SCSI-3 device=20
pass0: 3.300MB/s transfers
pass1 at aacp0 bus 0 scbus0 target 1 lun 0
pass1: <SEAGATE ST336754LC 0003> Fixed Uninstalled SCSI-3 device=20
pass1: 3.300MB/s transfers
pass2 at aacp0 bus 0 scbus0 target 2 lun 0
pass2: <SEAGATE ST373454LC 0005> Fixed Uninstalled SCSI-3 device=20
pass2: 3.300MB/s transfers
pass3 at aacp0 bus 0 scbus0 target 3 lun 0
pass3: <SEAGATE ST373454LC 0005> Fixed Uninstalled SCSI-3 device=20
pass3: 3.300MB/s transfers
SMP: AP CPU #1 Launched!
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/aacd0s4a
em0: link state changed to UP
--MgsldsnE3DYXgZCe--
--wOOEd1gxhwV8K3c+
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iEYEARECAAYFAkuZIqcACgkQmprOCmdXAD1H3gCfWK9zCdReRYUIfRN1ssEFa4r2
diEAn1/6oGuWVwWKnLCFkWGcHCYyg0ug
=xXp/
-----END PGP SIGNATURE-----
--wOOEd1gxhwV8K3c+--
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 20:56:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6E3C4106566B;
Thu, 11 Mar 2010 20:56:25 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
[131.104.91.36])
by mx1.freebsd.org (Postfix) with ESMTP id 7E4F68FC16;
Thu, 11 Mar 2010 20:56:24 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACfomEuDaFvH/2dsb2JhbACaYHO9F4R7BIMX
X-IronPort-AV: E=Sophos;i="4.49,622,1262581200"; d="scan'208";a="68694276"
Received: from danube.cs.uoguelph.ca ([131.104.91.199])
by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Mar 2010 15:56:14 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
by danube.cs.uoguelph.ca (Postfix) with ESMTP id EAC351084EAB;
Thu, 11 Mar 2010 15:56:13 -0500 (EST)
X-Virus-Scanned: amavisd-new at danube.cs.uoguelph.ca
Received: from danube.cs.uoguelph.ca ([127.0.0.1])
by localhost (danube.cs.uoguelph.ca [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id pQplkHYuLo-d; Thu, 11 Mar 2010 15:56:12 -0500 (EST)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102])
by danube.cs.uoguelph.ca (Postfix) with ESMTP id 8BD01318158;
Thu, 11 Mar 2010 15:48:39 -0500 (EST)
Received: from localhost (rmacklem@localhost)
by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id
o2BL1AM04195; Thu, 11 Mar 2010 16:01:10 -0500 (EST)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing
-bs
Date: Thu, 11 Mar 2010 16:01:10 -0500 (EST)
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: Adrenalin <adrenalinup@gmail.com>
In-Reply-To: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1003111558320.2969@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
<f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 20:56:25 -0000
On Wed, 10 Mar 2010, Adrenalin wrote:
>
> I'll "put my heart into the teeth" and will try to go for the stable.
>
You can just apply this one patch to your 8.0 kernel, there is no need
to go to stable/8 (at least for this fix).
> This is kind of critical I guess, I think it should really go to the
> release. It's the first time I got into a such a nasty bug with freebsd.
>
It wasn't identified until the release was headed out the door, so it
couldn't make it in, but will be in 8.1.
rick
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 20:56:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6E3C4106566B;
Thu, 11 Mar 2010 20:56:25 +0000 (UTC)
(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
[131.104.91.36])
by mx1.freebsd.org (Postfix) with ESMTP id 7E4F68FC16;
Thu, 11 Mar 2010 20:56:24 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACfomEuDaFvH/2dsb2JhbACaYHO9F4R7BIMX
X-IronPort-AV: E=Sophos;i="4.49,622,1262581200"; d="scan'208";a="68694276"
Received: from danube.cs.uoguelph.ca ([131.104.91.199])
by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Mar 2010 15:56:14 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
by danube.cs.uoguelph.ca (Postfix) with ESMTP id EAC351084EAB;
Thu, 11 Mar 2010 15:56:13 -0500 (EST)
X-Virus-Scanned: amavisd-new at danube.cs.uoguelph.ca
Received: from danube.cs.uoguelph.ca ([127.0.0.1])
by localhost (danube.cs.uoguelph.ca [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id pQplkHYuLo-d; Thu, 11 Mar 2010 15:56:12 -0500 (EST)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102])
by danube.cs.uoguelph.ca (Postfix) with ESMTP id 8BD01318158;
Thu, 11 Mar 2010 15:48:39 -0500 (EST)
Received: from localhost (rmacklem@localhost)
by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id
o2BL1AM04195; Thu, 11 Mar 2010 16:01:10 -0500 (EST)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing
-bs
Date: Thu, 11 Mar 2010 16:01:10 -0500 (EST)
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: Adrenalin <adrenalinup@gmail.com>
In-Reply-To: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1003111558320.2969@muncher.cs.uoguelph.ca>
References: <1242075474.72992.118.camel@hood.oook.cz>
<3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com>
<20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org>
<4A3E234F.6050403@FreeBSD.org>
<Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca>
<f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com>
<Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca>
<f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Doug Rabson <dfr@freebsd.org>, current@freebsd.org,
freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat
panic)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 20:56:25 -0000
On Wed, 10 Mar 2010, Adrenalin wrote:
>
> I'll "put my heart into the teeth" and will try to go for the stable.
>
You can just apply this one patch to your 8.0 kernel, there is no need
to go to stable/8 (at least for this fix).
> This is kind of critical I guess, I think it should really go to the
> release. It's the first time I got into a such a nasty bug with freebsd.
>
It wasn't identified until the release was headed out the door, so it
couldn't make it in, but will be in 8.1.
rick
From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 23:30:47 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D634C10656EF;
Thu, 11 Mar 2010 23:30:47 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id DB6AF8FC12;
Thu, 11 Mar 2010 23:30:46 +0000 (UTC)
Received: by fxm1 with SMTP id 1so672511fxm.13
for <multiple recipients>; Thu, 11 Mar 2010 15:30:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=wOVOvDkt7lylzFkV6ljoK65DM2vWqgHn356+lIMO9Zk=;
b=Z4E+UZd+/fqYQNiaFt5SOcYy47TQ9IVt7MrAMcul/tjiG6E2YjJRR6XJVufgsqjMew
lWiPqqKNdtODKD4rcJs2zKJwebSkhHZqWfbi84w+WddRK7DBmVNZXeHNOBbp9i5yLnFB
ELHmIl0dqBPntWTc+BEVfQZiBdMvRqsigclqY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=nv8+KACeI6kmeU9H84BOy3KcL62J9/fog9Jaa66GS3hTSIYb2wawjIPLPl4BcJ6JGl
efZdw+RnRxBTpsPQFibsXiyy9Dmaql94b2YcgxOWSa1b2/LaqQFSnDErXnQHRAduHNur
29YwzLIP6zTMc8Vq1pDs1/6WQ+iYPIcXmoUqE=
Received: by 10.102.164.10 with SMTP id m10mr2248519mue.52.1268350245605;
Thu, 11 Mar 2010 15:30:45 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id s10sm1846914muh.35.2010.03.11.15.30.42
(version=SSLv3 cipher=RC4-MD5); Thu, 11 Mar 2010 15:30:44 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Thu, 11 Mar 2010 15:30:53 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Thu, 11 Mar 2010 15:30:53 -0800
To: Andrew Thompson <thompsa@freebsd.org>
Message-ID: <20100311233053.GY1295@weongyo>
Mail-Followup-To: Andrew Thompson <thompsa@freebsd.org>,
Garrett Cooper <yanefbsd@gmail.com>,
FreeBSD Tinderbox <tinderbox@freebsd.org>, powerpc@freebsd.org,
current@freebsd.org
References: <201003110629.o2B6TVta094218@freebsd-current.sentex.ca>
<7d6fde3d1003102248g31b179f7u3bfe848408f91f2e@mail.gmail.com>
<20100311081035.GA45454@citylink.fud.org.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100311081035.GA45454@citylink.fud.org.nz>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: Garrett Cooper <yanefbsd@gmail.com>, powerpc@freebsd.org,
FreeBSD Tinderbox <tinderbox@freebsd.org>, current@freebsd.org
Subject: Re: [head tinderbox] failure on powerpc/powerpc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 23:30:48 -0000
On Thu, Mar 11, 2010 at 09:10:35PM +1300, Andrew Thompson wrote:
> On Wed, Mar 10, 2010 at 10:48:27PM -0800, Garrett Cooper wrote:
> > Weongyo, et all,
> >
> > On Wed, Mar 10, 2010 at 10:29 PM, FreeBSD Tinderbox
> > > /src/sys/modules/siba_bwn/../../dev/siba/siba_core.c:2035: error: request for member 'sd_bus' in something not a structure or union
> > > *** Error code 1
> > >
> > > Stop in /src/sys/modules/siba_bwn.
> > > *** Error code 1
> > >
> > > Stop in /src/sys/modules.
> > > *** Error code 1
> > >
> > > Stop in /obj/powerpc/src/sys/LINT.
> > > *** Error code 1
> > >
> > > Stop in /src.
> > > *** Error code 1
> > >
> > > Stop in /src.
> > > TB --- 2010-03-11 06:29:31 - WARNING: /usr/bin/make returned exit code ?1
> > > TB --- 2010-03-11 06:29:31 - ERROR: failed to build lint kernel
> > > TB --- 2010-03-11 06:29:31 - 3629.47 user 614.12 system 4685.83 real
> >
> > Could someone please try this patch to see whether or not it fixes
> > the void* deref issue? I don't think it's style(9) correct, but it
> > might resolve the issue.
> > Thanks,
> > -Garrett
> >
> > Index: siba_core.c
> > ===================================================================
> > --- siba_core.c (revision 204996)
> > +++ siba_core.c (working copy)
> > @@ -2032,9 +2032,9 @@
> > siba_dma_translation(device_t dev)
> > {
> >
> > - KASSERT(device_get_ivars(dev)->sd_bus->siba_type == SIBA_TYPE_PCI,
> > - ("unsupported bustype %d\n",
> > - device_get_ivars(dev)->sd_bus->siba_type));
> > + KASSERT(((struct siba_softc *) device_get_ivars(dev))->sd_bus->siba_type ==
> > + SIBA_TYPE_PCI, ("unsupported bustype %d\n",
> > + ((struct siba_softc*) device_get_ivars(dev))->sd_bus->siba_type));
> >
>
> It was all getting a bit unwieldy, I committed a more simple fix in
> r205003.
Thank you for fix and sorry for break build.
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 01:14:30 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 89877106566C
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 01:14:30 +0000 (UTC)
(envelope-from swhetzel@gmail.com)
Received: from mail-iw0-f199.google.com (mail-iw0-f199.google.com
[209.85.223.199])
by mx1.freebsd.org (Postfix) with ESMTP id 42C538FC21
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 01:14:30 +0000 (UTC)
Received: by iwn37 with SMTP id 37so724094iwn.27
for <multiple recipients>; Thu, 11 Mar 2010 17:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=dCFkoeoAoT1p/Nn2GA98pWGi+N5yBs/HuB/cKDmFoEQ=;
b=eKxqdNdtgAF69snJ/zJAarK4Z25hXDh1yQHb+KEa7iUVVx55LoWAy6YRNwjbzugKym
efnzo865VwjfFe8FCfOLh5/GUvS7FKjXPqubWcDt8fW2LrW0swZtIyQCBZ5dP7TU8//W
VJMB32Rpd2P8lxH8sbFLAvxowlzVKf6jhr978=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=f5nyn3kFZAnAxDlrc2Ze3bYq5TxDUX9C7fsA0/x5HhB3CC9vG6woThcDESUQdWJvjm
9mI8xcIhKcpgZlLiN4xsNwDCDgOjjxtpwuyGXAT+s1GboJ/GkN/hENz0+OpD2oi1h7Vc
hQtrxmlz3SPoVOHUOTor+X3TfJuRvik+u9QSU=
MIME-Version: 1.0
Received: by 10.231.151.197 with SMTP id d5mr410328ibw.73.1268356469586; Thu,
11 Mar 2010 17:14:29 -0800 (PST)
In-Reply-To: <4B991C00.3010809@intertainservices.com>
References: <4B99031D.3080308@freebsd.org>
<4B991C00.3010809@intertainservices.com>
Date: Thu, 11 Mar 2010 19:14:29 -0600
Message-ID: <790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
From: Scot Hetzel <swhetzel@gmail.com>
To: Nathan Whitehorn <nwhitehorn@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-current@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 01:14:30 -0000
On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
<mike.jakubik@intertainservices.com> wrote:
> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>
>> As a result of importing 32-bit compatibility support for non-x86 64-bit
>> platforms, the kernel options COMPAT_IA32 has been renamed COMPAT_FREEBSD32
>> in revision 205014, so all kernel configurations including this option must
>> be modified accordingly.
>>
>
> That sounds a bit confusing, compatibility with FreeBSD 3.2?
>
I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
Scot
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 01:20:09 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 698FC106566B;
Fri, 12 Mar 2010 01:20:09 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com
[209.85.160.54])
by mx1.freebsd.org (Postfix) with ESMTP id 357528FC13;
Fri, 12 Mar 2010 01:20:08 +0000 (UTC)
Received: by pwj4 with SMTP id 4so402875pwj.13
for <multiple recipients>; Thu, 11 Mar 2010 17:20:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=qanAUEj3NXjhbBv6/q5OKymZrkQ6U5uTSzbPivMXnmA=;
b=BfIGLJKQNSfZkgA194EN+MVLxVg2ixm4QzKHBPkUl7FRiu1GdT+E2CGyCnox3T259O
6yEJeNJXjoZEQQ5TujDU7tAzaClTmjqd86jj4RsdOQ+7MUXbrDszDEEqUe/xYyChKH++
hFCw+xApLnt99zLfnHqKMKJxBZYYzmV/Iy/P4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=IxUFSm5sn69zBG6TVojWSDrznU0OxenaPgnuL+N2+fMpWa2847sZuDY2Su57w6Vl2o
EAhVPXa9xmwcPVMyUreXILeNgp5S33+UTl8X7OsCFX9XMNN23rjM71A1qAcDDf9GkX04
pjKT+jtZKZC4LR4DhaOnT9PjZ9yGnpeFnrUq0=
MIME-Version: 1.0
Received: by 10.142.63.13 with SMTP id l13mr80723wfa.196.1268356808773; Thu,
11 Mar 2010 17:20:08 -0800 (PST)
In-Reply-To: <790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
References: <4B99031D.3080308@freebsd.org>
<4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
Date: Thu, 11 Mar 2010 17:20:08 -0800
Message-ID: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Scot Hetzel <swhetzel@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-current@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org>
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 01:20:09 -0000
On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote:
> On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> <mike.jakubik@intertainservices.com> wrote:
>> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>>
>>> As a result of importing 32-bit compatibility support for non-x86 64-bit
>>> platforms, the kernel options COMPAT_IA32 has been renamed COMPAT_FREEBSD32
>>> in revision 205014, so all kernel configurations including this option must
>>> be modified accordingly.
>>>
>>
>> That sounds a bit confusing, compatibility with FreeBSD 3.2?
>>
> I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
>
> A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
Agreed. Is it possible to change the name again because it really
hasn't gotten much traction yet?
Thanks,
-Garrett
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 02:29:06 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7A7F51065670;
Fri, 12 Mar 2010 02:29:06 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 37D308FC24;
Fri, 12 Mar 2010 02:29:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o2C2OH0c059532;
Thu, 11 Mar 2010 19:24:18 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Thu, 11 Mar 2010 19:24:23 -0700 (MST)
Message-Id: <20100311.192423.683591382013853731.imp@bsdimp.com>
To: yanefbsd@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org, swhetzel@gmail.com, nwhitehorn@FreeBSD.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 02:29:06 -0000
In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
Garrett Cooper <yanefbsd@gmail.com> writes:
: On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote:
: > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
: > <mike.jakubik@intertainservices.com> wrote:
: >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
: >>>
: >>> As a result of importing 32-bit compatibility support for non-x86 64-bit
: >>> platforms, the kernel options COMPAT_IA32 has been renamed COMPAT_FREEBSD32
: >>> in revision 205014, so all kernel configurations including this option must
: >>> be modified accordingly.
: >>>
: >>
: >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
: >>
: > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
: > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
: >
: > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
:
: Agreed. Is it possible to change the name again because it really
: hasn't gotten much traction yet?
What does the name matter, really?
This will be documented, and mirrors the kernel source
compat/freebsd32.
Put another way: if everybody that's going to comment on the name
would instead fix one bug from the PR database with the time they
spend commenting on it, would FreeBSD be better or worse off than
spending dozens of hours arguing over COMPAT_X32 vs COMPAT_Y32 vs
COMPAT_FLYING_MONKEYS?
Warner
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 02:44:26 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C090D106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 02:44:26 +0000 (UTC)
(envelope-from chmeeedalf@gmail.com)
Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com
[209.85.218.216])
by mx1.freebsd.org (Postfix) with ESMTP id 4D7038FC14
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 02:44:25 +0000 (UTC)
Received: by bwz8 with SMTP id 8so686857bwz.3
for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 18:44:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to
:content-type; bh=KIVHaNNmTJVCrqTppmBvmUK9DFaENJqNvHFl3CvTMIk=;
b=Oz8fldb+r/LnY9M+XvA76cQ5/RFboUCDcTdVUmECSH1hbW1Xravmg/VQpToG8s4TB7
Jj/NgBE9JQtpkqVB0+GCOtLRR6NZuFonP2gJf27JFZzGhGR4PysVV06x0AZg7aLei/WV
NwXRE9qjATcnt950T9te/Z1Clu99Gh6BukINk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type;
b=kgIcBACZZmaZe5/XuntuskukxCZ7+rbRmb1uEJqqREhfijhLEY37brXYCngJl67hat
0QnBUTHvzS+bTVzo4qOnvlocTpczebkLwmFKP6ClicvYiW4yXENSG3WM53spF8+gdthH
4epVU6csObsyPuhkuQsB0Vs8Zx3A0gNcTwM+E=
MIME-Version: 1.0
Sender: chmeeedalf@gmail.com
Received: by 10.204.131.85 with SMTP id w21mr205590bks.174.1268361864484; Thu,
11 Mar 2010 18:44:24 -0800 (PST)
In-Reply-To: <20100311.192423.683591382013853731.imp@bsdimp.com>
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
Date: Thu, 11 Mar 2010 21:44:24 -0500
X-Google-Sender-Auth: b3f2f27683f47eef
Message-ID: <fd9cd3451003111844t49c74ddev69d9e00e38789bbb@mail.gmail.com>
From: Justin Hibbits <jrh29@alumni.cwru.edu>
To: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 02:44:26 -0000
On Thu, Mar 11, 2010 at 9:24 PM, M. Warner Losh <imp@bsdimp.com> wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
> Garrett Cooper <yanefbsd@gmail.com> writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > <mike.jakubik@intertainservices.com> wrote:
> : >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> : >>>
> : >>> As a result of importing 32-bit compatibility support for non-x86
> 64-bit
> : >>> platforms, the kernel options COMPAT_IA32 has been renamed
> COMPAT_FREEBSD32
> : >>> in revision 205014, so all kernel configurations including this
> option must
> : >>> be modified accordingly.
> : >>>
> : >>
> : >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
> : >>
> : > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> : > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
> : >
> : > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
> :
> : Agreed. Is it possible to change the name again because it really
> : hasn't gotten much traction yet?
>
> What does the name matter, really?
>
> This will be documented, and mirrors the kernel source
> compat/freebsd32.
>
> Put another way: if everybody that's going to comment on the name
> would instead fix one bug from the PR database with the time they
> spend commenting on it, would FreeBSD be better or worse off than
> spending dozens of hours arguing over COMPAT_X32 vs COMPAT_Y32 vs
> COMPAT_FLYING_MONKEYS?
>
> Warner
>
Just for that, I nominate Nathan rename the option to
COMPAT_FLYING_MONKEYS32.
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 02:47:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DB26B106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 02:47:57 +0000 (UTC)
(envelope-from rrs@lakerest.net)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d])
by mx1.freebsd.org (Postfix) with ESMTP id 564118FC18
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 02:47:57 +0000 (UTC)
Received: from [192.168.11.44] (197.214.32.202.bf.2iij.net [202.32.214.197])
(authenticated bits=0)
by lakerest.net (8.14.3/8.14.3) with ESMTP id o2C2lef6077853
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Thu, 11 Mar 2010 21:47:45 -0500 (EST)
(envelope-from rrs@lakerest.net)
Message-Id: <F030DA98-F092-47B7-A083-C2536BB0068B@lakerest.net>
From: Randall Stewart <rrs@lakerest.net>
To: wooky@btconnect.com
Content-Type: multipart/mixed; boundary=Apple-Mail-6-144566907
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 12 Mar 2010 11:47:39 +0900
X-Mailer: Apple Mail (2.936)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: sctp ipv6 csum issue
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 02:47:57 -0000
--Apple-Mail-6-144566907
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Nigel:
Here is a patch for your issue I think.
Its off of a head machine but I think it should apply. If not
let me know.
See if this does not fix the issue.
Thanks
R
--Apple-Mail-6-144566907
Content-Disposition: attachment;
filename=patch.ip6_output.txt
Content-Type: text/plain;
x-unix-mode=0644;
name="patch.ip6_output.txt"
Content-Transfer-Encoding: 7bit
Index: ip6_output.c
===================================================================
--- ip6_output.c (revision 205059)
+++ ip6_output.c (working copy)
@@ -208,6 +208,9 @@
struct route_in6 *ro_pmtu = NULL;
int hdrsplit = 0;
int needipsec = 0;
+#ifdef SCTP
+ int sw_csum;
+#endif
#ifdef IPSEC
struct ipsec_output_state state;
struct ip6_rthdr *rh = NULL;
@@ -829,6 +832,10 @@
}
m->m_pkthdr.csum_flags |=
CSUM_IP_CHECKED | CSUM_IP_VALID;
+#ifdef SCTP
+ if (m->m_pkthdr.csum_flags & CSUM_SCTP)
+ m->m_pkthdr.csum_flags |= CSUM_SCTP_VALID;
+#endif
error = netisr_queue(NETISR_IPV6, m);
goto done;
} else
@@ -857,6 +864,13 @@
* 4: if dontfrag == 1 && alwaysfrag == 1
* error, as we cannot handle this conflicting request
*/
+#ifdef SCTP
+ sw_csum = m->m_pkthdr.csum_flags & ~ifp->if_hwassist;
+ if (sw_csum & CSUM_SCTP) {
+ sctp_delayed_cksum(m);
+ sw_csum &= ~CSUM_SCTP;
+ }
+#endif
tlen = m->m_pkthdr.len;
if (opt && (opt->ip6po_flags & IP6PO_DONTFRAG))
--Apple-Mail-6-144566907
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
------------------------------
Randall Stewart
803-317-4952 (cell)
803-345-0391(direct)
--Apple-Mail-6-144566907--
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 03:08:44 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CD2181065672
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 03:08:44 +0000 (UTC)
(envelope-from rrs@lakerest.net)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d])
by mx1.freebsd.org (Postfix) with ESMTP id 54E6D8FC0A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 03:08:44 +0000 (UTC)
Received: from [192.168.11.44] (197.214.32.202.bf.2iij.net [202.32.214.197])
(authenticated bits=0)
by lakerest.net (8.14.3/8.14.3) with ESMTP id o2C38X9q078762
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Thu, 11 Mar 2010 22:08:37 -0500 (EST)
(envelope-from rrs@lakerest.net)
Message-Id: <3F08B7D7-1056-4F7C-B023-BCEA75DBE970@lakerest.net>
From: Randall Stewart <rrs@lakerest.net>
To: wooky@btconnect.com
In-Reply-To: <F030DA98-F092-47B7-A083-C2536BB0068B@lakerest.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-8-145820530
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 12 Mar 2010 12:08:32 +0900
References: <F030DA98-F092-47B7-A083-C2536BB0068B@lakerest.net>
X-Mailer: Apple Mail (2.936)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: sctp ipv6 csum issue
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 03:08:44 -0000
--Apple-Mail-8-145820530
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Opps:
I was a little to quick, .. that one won't work.. but I
think this one will (need to have the right magic header
goo :-D)
Try this please (this one will build and actually do something :-D)
R
--Apple-Mail-8-145820530
Content-Disposition: attachment;
filename=patch.ip6_output.txt
Content-Type: text/plain;
x-unix-mode=0644;
name="patch.ip6_output.txt"
Content-Transfer-Encoding: 7bit
Index: ip6_output.c
===================================================================
--- ip6_output.c (revision 205059)
+++ ip6_output.c (working copy)
@@ -66,6 +66,7 @@
#include "opt_inet.h"
#include "opt_inet6.h"
#include "opt_ipsec.h"
+#include "opt_sctp.h"
#include <sys/param.h>
#include <sys/kernel.h>
@@ -102,6 +103,10 @@
#include <netipsec/key.h>
#include <netinet6/ip6_ipsec.h>
#endif /* IPSEC */
+#ifdef SCTP
+#include <netinet/sctp.h>
+#include <netinet/sctp_crc32.h>
+#endif
#include <netinet6/ip6protosw.h>
#include <netinet6/scope6_var.h>
@@ -208,6 +213,9 @@
struct route_in6 *ro_pmtu = NULL;
int hdrsplit = 0;
int needipsec = 0;
+#ifdef SCTP
+ int sw_csum;
+#endif
#ifdef IPSEC
struct ipsec_output_state state;
struct ip6_rthdr *rh = NULL;
@@ -829,6 +837,10 @@
}
m->m_pkthdr.csum_flags |=
CSUM_IP_CHECKED | CSUM_IP_VALID;
+#ifdef SCTP
+ if (m->m_pkthdr.csum_flags & CSUM_SCTP)
+ m->m_pkthdr.csum_flags |= CSUM_SCTP_VALID;
+#endif
error = netisr_queue(NETISR_IPV6, m);
goto done;
} else
@@ -857,6 +869,13 @@
* 4: if dontfrag == 1 && alwaysfrag == 1
* error, as we cannot handle this conflicting request
*/
+#ifdef SCTP
+ sw_csum = m->m_pkthdr.csum_flags & ~ifp->if_hwassist;
+ if (sw_csum & CSUM_SCTP) {
+ sctp_delayed_cksum(m);
+ sw_csum &= ~CSUM_SCTP;
+ }
+#endif
tlen = m->m_pkthdr.len;
if (opt && (opt->ip6po_flags & IP6PO_DONTFRAG))
--Apple-Mail-8-145820530
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
On Mar 12, 2010, at 11:47 AM, Randall Stewart wrote:
> Nigel:
>
> Here is a patch for your issue I think.
>
> Its off of a head machine but I think it should apply. If not
> let me know.
>
> See if this does not fix the issue.
>
> Thanks
>
> R
> <patch.ip6_output.txt>
> ------------------------------
> Randall Stewart
> 803-317-4952 (cell)
> 803-345-0391(direct)
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org
> "
------------------------------
Randall Stewart
803-317-4952 (cell)
803-345-0391(direct)
--Apple-Mail-8-145820530--
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 03:54:36 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1FBE8106566C
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 03:54:36 +0000 (UTC)
(envelope-from scottl@samsco.org)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
by mx1.freebsd.org (Postfix) with ESMTP id CE8228FC13
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 03:54:35 +0000 (UTC)
Received: from [IPv6:::1] (pooker.samsco.org [168.103.85.57])
by pooker.samsco.org (8.14.4/8.14.2) with ESMTP id o2C3sWLp001327;
Thu, 11 Mar 2010 20:54:32 -0700 (MST)
(envelope-from scottl@samsco.org)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Scott Long <scottl@samsco.org>
In-Reply-To: <790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
Date: Thu, 11 Mar 2010 20:54:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <077AD48E-76D1-459A-9493-8DCB297A98DF@samsco.org>
References: <4B99031D.3080308@freebsd.org>
<4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
To: Scot Hetzel <swhetzel@gmail.com>
X-Mailer: Apple Mail (2.1077)
X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00
autolearn=ham version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org
Cc: freebsd-current@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org>
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 03:54:36 -0000
On Mar 11, 2010, at 6:14 PM, Scot Hetzel wrote:
> On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> <mike.jakubik@intertainservices.com> wrote:
>> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
>>>=20
>>> As a result of importing 32-bit compatibility support for non-x86 =
64-bit
>>> platforms, the kernel options COMPAT_IA32 has been renamed =
COMPAT_FREEBSD32
>>> in revision 205014, so all kernel configurations including this =
option must
>>> be modified accordingly.
>>>=20
>>=20
>> That sounds a bit confusing, compatibility with FreeBSD 3.2?
>>=20
> I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
>=20
> A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
>=20
Seriously, this is being debated? FreeBSD 3.2? Is this a joke? I =
caught the humor in the first couple of replies, but you sound serious. =
Wow.
Scott
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 04:24:58 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2A69C106564A;
Fri, 12 Mar 2010 04:24:58 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pz0-f199.google.com (mail-pz0-f199.google.com
[209.85.222.199])
by mx1.freebsd.org (Postfix) with ESMTP id EBD868FC0C;
Fri, 12 Mar 2010 04:24:57 +0000 (UTC)
Received: by pzk37 with SMTP id 37so178127pzk.7
for <multiple recipients>; Thu, 11 Mar 2010 20:24:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=hQZ9KJCLjikSNLpgQNXdfN33B/HDShKWwcOvXDfIhEY=;
b=vAHM5dCI7lVdaEBCcL3fW8YYAQV5altsfzGQAn8HmiKkh6Jm/6xHbomjMzTtRtMrDM
sQekmU7RBhK7zfyBb3LZKficL+TqBzP1y3H57vhPgikIVYumvia9PZBO/Rx43R7IKy5o
7vQABeDQKQXxiBkOZ3crAg8LFUS+wby0kUmpc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=ZErlUPFT0q/Tqo44DyC93dE5sddH26IDXaGTeEg5YR/InEMNWKYKR46omGau7/fG8Y
5kNbpFeiv7LXWBE1n7m3YUSCBOZOOcy4uUZ1sfnfQcPXrB+YQZ2zq+5YafQ9Rk8Ni6FQ
aOkFPYImzx6GOZHrNxrtFVIyXkmkcboakuBEQ=
MIME-Version: 1.0
Received: by 10.143.21.5 with SMTP id y5mr2020865wfi.324.1268367897436; Thu,
11 Mar 2010 20:24:57 -0800 (PST)
In-Reply-To: <20100311.192423.683591382013853731.imp@bsdimp.com>
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
Date: Thu, 11 Mar 2010 20:24:57 -0800
Message-ID: <7d6fde3d1003112024o646afbf2w1ee4d81abae7e608@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: "M. Warner Losh" <imp@bsdimp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: swhetzel@gmail.com, nwhitehorn@freebsd.org, freebsd-current@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 04:24:58 -0000
On Thu, Mar 11, 2010 at 6:24 PM, M. Warner Losh <imp@bsdimp.com> wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
> =A0 =A0 =A0 =A0 =A0 =A0Garrett Cooper <yanefbsd@gmail.com> writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote=
:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > <mike.jakubik@intertainservices.com> wrote:
> : >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> : >>>
> : >>> As a result of importing 32-bit compatibility support for non-x86 6=
4-bit
> : >>> platforms, the kernel options COMPAT_IA32 has been renamed COMPAT_F=
REEBSD32
> : >>> in revision 205014, so all kernel configurations including this opt=
ion must
> : >>> be modified accordingly.
> : >>>
> : >>
> : >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
> : >>
> : > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> : > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
> : >
> : > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
> :
> : Agreed. Is it possible to change the name again because it really
> : hasn't gotten much traction yet?
>
> What does the name matter, really?
>
> This will be documented, and mirrors the kernel source
> compat/freebsd32.
>
> Put another way: if everybody that's going to comment on the name
> would instead fix one bug from the PR database with the time they
> spend commenting on it, would FreeBSD be better or worse off than
> spending dozens of hours arguing over COMPAT_X32 vs COMPAT_Y32 vs
> COMPAT_FLYING_MONKEYS?
I can haz PR review then? Here's an easy one :)...
http://www.freebsd.org/cgi/query-pr.cgi?pr=3D144644
Thanks,
-Garrett
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 10:36:29 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 19FC4106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 10:36:29 +0000 (UTC)
(envelope-from gary.jennejohn@freenet.de)
Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3])
by mx1.freebsd.org (Postfix) with ESMTP id A56B58FC13
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 10:36:28 +0000 (UTC)
Received: from [195.4.92.15] (helo=5.mx.freenet.de)
by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
25) (Exim 4.72 #1)
id 1Nq2EE-0002uv-KX; Fri, 12 Mar 2010 11:36:27 +0100
Received: from p57ae0ed7.dip0.t-ipconnect.de ([87.174.14.215]:29747
helo=ernst.jennejohn.org)
by 5.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25)
(Exim 4.72 #2) id 1Nq2ED-0005eI-Gw; Fri, 12 Mar 2010 11:36:25 +0100
Date: Fri, 12 Mar 2010 11:36:25 +0100
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: Garrett Cooper <yanefbsd@gmail.com>
Message-ID: <20100312113625.1b2b017f@ernst.jennejohn.org>
In-Reply-To: <7d6fde3d1003112024o646afbf2w1ee4d81abae7e608@mail.gmail.com>
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
<7d6fde3d1003112024o646afbf2w1ee4d81abae7e608@mail.gmail.com>
X-Mailer: Claws Mail 3.7.4 (GTK+ 2.16.2; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 10:36:29 -0000
On Thu, 11 Mar 2010 20:24:57 -0800
Garrett Cooper <yanefbsd@gmail.com> wrote:
> I can haz PR review then? Here's an easy one :)...
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
>
Looks OK to me except I don't like the
if (something) {
one-line-of-code();
}
constructs, but according to style(9) these are sort-of OK, viz
Closing and opening braces go on the same line as the else. Braces that
are not necessary may be left out.
^^^^^^^^^^^^^^^
if (test)
stmt;
else if (bar) {
stmt;
stmt;
} else
stmt;
Saved by the "may."
---
Gary Jennejohn (gj@)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 11:02:22 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6D6CC106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 11:02:22 +0000 (UTC)
(envelope-from uqs@spoerlein.net)
Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2001:470:9a47::1])
by mx1.freebsd.org (Postfix) with ESMTP id 27FEA8FC08
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 11:02:22 +0000 (UTC)
Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1])
by acme.spoerlein.net (Postfix) with ESMTPS id 6334F5CA9;
Fri, 12 Mar 2010 12:02:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net;
s=dkim200908; t=1268391741;
bh=HJoaB7NqNmgfhuFfoE7+CL0dobMJbbPN18QfNMnfFbE=;
h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
Content-Type:In-Reply-To;
b=fUPq3jWzDH6M/hUUPm3Sg4oIbcPvhlN5knEHBEPB4rItFetxT/1moIXdws8rtfJgv
Pcpp5kUuGHhimJh/DOcJSp/uaj3EQRGLgsBpjpzXMUY2LI2suyaA0ctTN0/jx0T3Sq
VWHSmSQuNkJ2GVi5RGBfQUFckPoez10De8U9LR3w=
Received: (from uqs@localhost)
by acme.spoerlein.net (8.14.4/8.14.4/Submit) id o2CB2L35003033;
Fri, 12 Mar 2010 12:02:21 +0100 (CET)
(envelope-from uqs@spoerlein.net)
Date: Fri, 12 Mar 2010 12:02:21 +0100
From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@spoerlein.net>
To: Gary Jennejohn <gary.jennejohn@freenet.de>
Message-ID: <20100312110221.GC99813@acme.spoerlein.net>
Mail-Followup-To: Gary Jennejohn <gary.jennejohn@freenet.de>,
Garrett Cooper <yanefbsd@gmail.com>, freebsd-current@freebsd.org
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
<7d6fde3d1003112024o646afbf2w1ee4d81abae7e608@mail.gmail.com>
<20100312113625.1b2b017f@ernst.jennejohn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100312113625.1b2b017f@ernst.jennejohn.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Garrett Cooper <yanefbsd@gmail.com>, freebsd-current@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 11:02:22 -0000
On Fri, 12.03.2010 at 11:36:25 +0100, Gary Jennejohn wrote:
> On Thu, 11 Mar 2010 20:24:57 -0800
> Garrett Cooper <yanefbsd@gmail.com> wrote:
>
> > I can haz PR review then? Here's an easy one :)...
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
> >
>
> Looks OK to me except I don't like the
> if (something) {
> one-line-of-code();
> }
> constructs, but according to style(9) these are sort-of OK, viz
>
> Closing and opening braces go on the same line as the else. Braces that
> are not necessary may be left out.
> ^^^^^^^^^^^^^^^
> if (test)
> stmt;
> else if (bar) {
> stmt;
> stmt;
> } else
> stmt;
>
> Saved by the "may."
True, but some folks (me included) really hate it, when different
bracing is used *within* the same statement. The example above really is
horrible. If one if/else-if clause needs braces, just brace them all. This
loses no vertical space (the dangling else excluded) and some folks find
it visually more pleasing/easier to read.
... hence begins the bikeshedding.
Bye,
Uli
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 16:32:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E92EC106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 16:32:32 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id B36048FC13
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 16:32:32 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o2CGWWeC030929
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 08:32:32 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o2CGWWSN030928
for freebsd-current@freebsd.org; Fri, 12 Mar 2010 08:32:32 -0800 (PST)
(envelope-from obrien)
Date: Fri, 12 Mar 2010 08:32:32 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <20100312163232.GA30632@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: PANIC w/head@r204957: fork->...->uma_dbg_alloc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 16:32:33 -0000
Details at
http://trang.nuxi.org:8080/panics/DSC_0070.JPG
Kernel sources at r203083 are stable for me.
Unfortunately, I cannot get a dump for this.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 16:32:42 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 37B061065761
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 16:32:42 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id 017F88FC17
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 16:32:41 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o2CGWfgf030950
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 08:32:41 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o2CGWfkG030949
for freebsd-current@freebsd.org; Fri, 12 Mar 2010 08:32:41 -0800 (PST)
(envelope-from obrien)
Date: Fri, 12 Mar 2010 08:32:41 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <20100312163241.GA30935@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: PANIC w/head@r204957: link_elf_lookup_symbol
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 16:32:42 -0000
Details at
http://trang.nuxi.org:8080/panics/DSC_0010.JPG
Kernel sources at r203083 are stable for me.
Unfortunately, I cannot get a dump for this.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 16:36:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 94B811065672
for <current@freebsd.org>; Fri, 12 Mar 2010 16:36:24 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org
(adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122])
by mx1.freebsd.org (Postfix) with ESMTP id 309BC8FC14
for <current@freebsd.org>; Fri, 12 Mar 2010 16:36:23 +0000 (UTC)
Received: from bunrab.catwhisker.org (localhost [127.0.0.1])
by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id o2CGaNhr008712
for <current@freebsd.org>; Fri, 12 Mar 2010 08:36:23 -0800 (PST)
(envelope-from david@bunrab.catwhisker.org)
Received: (from david@localhost)
by bunrab.catwhisker.org (8.13.3/8.13.3/Submit) id o2CGaN2B008711
for current@freebsd.org; Fri, 12 Mar 2010 08:36:23 -0800 (PST)
(envelope-from david)
Date: Fri, 12 Mar 2010 08:36:23 -0800
From: David Wolfskill <david@catwhisker.org>
To: current@freebsd.org
Message-ID: <20100312163623.GC57205@bunrab.catwhisker.org>
Mail-Followup-To: David Wolfskill <david@catwhisker.org>, current@freebsd.org
References: <20100311170440.GR57205@bunrab.catwhisker.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="8CV4j0YfZekXzr5F"
Content-Disposition: inline
In-Reply-To: <20100311170440.GR57205@bunrab.catwhisker.org>
User-Agent: Mutt/1.4.2.1i
Cc:
Subject: Re: SMP deadlock during multi-user mode transition after r204866
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 16:36:24 -0000
--8CV4j0YfZekXzr5F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Mar 11, 2010 at 09:04:40AM -0800, David Wolfskill wrote:
> My build machine (dmesg attached) is a dual CPU, single-core box; my
> laptop is a single CPU, single-core box. I track head on each daily;
> while the build machine has been locking up during the transition to
> multi-user mode since Tuesday (when I had built CURRENT at r204909;
> previous was r204866, on Monday) -- and it boots to single-user mode OK
> -- the laptop has not exhibited the problem.
> ...
This appears to be resolved as of r205078 -- thanks!
> ...
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--8CV4j0YfZekXzr5F
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iEYEARECAAYFAkuabYYACgkQmprOCmdXAD0jYgCeMh8wsruhqDnIc6DaPhiUsL2T
ySEAn1LxU5wLwzjb9GOaazkLX6xQ1e9m
=dvdV
-----END PGP SIGNATURE-----
--8CV4j0YfZekXzr5F--
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 17:12:07 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 64DD6106564A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 17:12:07 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id 2F4158FC0A
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 17:12:06 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o2CHC6Z8031783
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 09:12:06 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o2CHC6sJ031782
for freebsd-current@freebsd.org; Fri, 12 Mar 2010 09:12:06 -0800 (PST)
(envelope-from obrien)
Date: Fri, 12 Mar 2010 09:12:06 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <20100312171206.GA31761@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: [PATCH] newvers.sh
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 17:12:07 -0000
* Simplify SRCDIR calculation by directly finding the kernel sources
based directly on one of them.
Reviewed by: dhw
This change does not increase the kernel build time. It also continues
to restrict the revision to just the kernel sources, and not the whole
tree.
Timing tests by: dhw
Index: newvers.sh
===================================================================
--- newvers.sh (revision 204939)
+++ newvers.sh (working copy)
@@ -89,25 +89,21 @@ i=`${MAKE:-make} -V KERN_IDENT`
case "$d" in
*/sys/*)
- SRCDIR=${d##*obj}
- if [ -n "$MACHINE" ]; then
- SRCDIR=${SRCDIR##/$MACHINE}
- fi
- SRCDIR=${SRCDIR%%/sys/*}
+ SRCDIR=$(dirname $0)/..
for dir in /bin /usr/bin /usr/local/bin; do
- if [ -d "${SRCDIR}/sys/.svn" -a -x "${dir}/svnversion" ] ; then
+ if [ -d "${SRCDIR}/.svn" -a -x "${dir}/svnversion" ] ; then
svnversion=${dir}/svnversion
break
fi
- if [ -d "${SRCDIR}/.git" -a -x "${dir}/git" ] ; then
- git_cmd="${dir}/git --git-dir=${SRCDIR}/.git"
+ if [ -d "${SRCDIR}/../.git" -a -x "${dir}/git" ] ; then
+ git_cmd="${dir}/git --git-dir=${SRCDIR}/../.git"
break
fi
done
if [ -n "$svnversion" ] ; then
- svn=" r`cd ${SRCDIR}/sys && $svnversion`"
+ svn=" r`cd ${SRCDIR} && $svnversion`"
fi
if [ -n "$git_cmd" ] ; then
git=`$git_cmd rev-parse --verify --short HEAD 2>/dev/null`
@@ -125,7 +121,7 @@ case "$d" in
git=" ${git}"
fi
fi
- if $git_cmd --work-tree=${SRCDIR} diff-index \
+ if $git_cmd --work-tree=${SRCDIR}/.. diff-index \
--name-only HEAD | read dummy; then
git="${git}-dirty"
fi
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 17:18:11 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 493E31065670
for <freebsd-current@FreeBSD.org>; Fri, 12 Mar 2010 17:18:11 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id 0821B8FC0C
for <freebsd-current@FreeBSD.org>; Fri, 12 Mar 2010 17:18:10 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o2CHHxgT031882;
Fri, 12 Mar 2010 09:17:59 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o2CHHw8G031881;
Fri, 12 Mar 2010 09:17:58 -0800 (PST) (envelope-from obrien)
Date: Fri, 12 Mar 2010 09:17:58 -0800
From: "David O'Brien" <obrien@FreeBSD.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20100312171758.GB31089@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, "M. Warner Losh" <imp@bsdimp.com>,
yanefbsd@gmail.com, freebsd-current@FreeBSD.org, swhetzel@gmail.com,
nwhitehorn@FreeBSD.org
References: <4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100311.192423.683591382013853731.imp@bsdimp.com>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: yanefbsd@gmail.com, freebsd-current@FreeBSD.org, nwhitehorn@FreeBSD.org,
swhetzel@gmail.com
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 17:18:11 -0000
On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
> In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
> Garrett Cooper <yanefbsd@gmail.com> writes:
> : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote:
> : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> : > <mike.jakubik@intertainservices.com> wrote:
> : >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> : >>> As a result of importing 32-bit compatibility support for non-x86
> : >>> 64-bit platforms, the kernel options COMPAT_IA32 has been renamed
> : >>> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
> : >>> including this option must be modified accordingly.
> : >>
> : >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
> : >>
> : > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> : > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
> : >
> : > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
> :
> : Agreed. Is it possible to change the name again because it really
> : hasn't gotten much traction yet?
>
> What does the name matter, really?
Yes names matter. Otherwise we would have made it "DEF8931". #define
names are chosen to be self-documenting.
$ grep COMPAT_FREEBSD conf/*
conf/NOTES:# Note that as a general rule, COMPAT_FREEBSD<n> depends on
conf/NOTES:# COMPAT_FREEBSD<n+1>, COMPAT_FREEBSD<n+2>, etc.
conf/NOTES:options COMPAT_FREEBSD4
conf/NOTES:options COMPAT_FREEBSD5
conf/NOTES:options COMPAT_FREEBSD6
conf/NOTES:options COMPAT_FREEBSD7
conf/options:COMPAT_FREEBSD4 opt_compat.h
conf/options:COMPAT_FREEBSD5 opt_compat.h
conf/options:COMPAT_FREEBSD6 opt_compat.h
conf/options:COMPAT_FREEBSD7 opt_compat.h
COMPAT_FREEBSD32 is not the same as any of the other well established
"COMPAT_FREEBSD" macros. So I do see where this could lead to confusion
to users.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 17:22:56 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C70991065676
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 17:22:56 +0000 (UTC)
(envelope-from obrien@NUXI.org)
Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85])
by mx1.freebsd.org (Postfix) with ESMTP id 892188FC13
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 17:22:56 +0000 (UTC)
Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1])
by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o2CHMuBP031980;
Fri, 12 Mar 2010 09:22:56 -0800 (PST)
(envelope-from obrien@dragon.nuxi.org)
Received: (from obrien@localhost)
by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o2CHMtXg031979;
Fri, 12 Mar 2010 09:22:55 -0800 (PST) (envelope-from obrien)
Date: Fri, 12 Mar 2010 09:22:55 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Scott Long <scottl@samsco.org>
Message-ID: <20100312172255.GC31089@dragon.NUXI.org>
Mail-Followup-To: obrien@freebsd.org, Scott Long <scottl@samsco.org>,
Scot Hetzel <swhetzel@gmail.com>, freebsd-current@freebsd.org,
Nathan Whitehorn <nwhitehorn@freebsd.org>
References: <4B99031D.3080308@freebsd.org>
<4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<077AD48E-76D1-459A-9493-8DCB297A98DF@samsco.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <077AD48E-76D1-459A-9493-8DCB297A98DF@samsco.org>
X-Operating-System: FreeBSD 9.0-CURRENT
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN?
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: Scot Hetzel <swhetzel@gmail.com>, Nathan Whitehorn <nwhitehorn@freebsd.org>,
freebsd-current@freebsd.org
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: obrien@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 17:22:56 -0000
On Thu, Mar 11, 2010 at 08:54:32PM -0700, Scott Long wrote:
> On Mar 11, 2010, at 6:14 PM, Scot Hetzel wrote:
> > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
> > <mike.jakubik@intertainservices.com> wrote:
> >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
> >>>
> >>> As a result of importing 32-bit compatibility support for non-x86 64-bit
> >>> platforms, the kernel options COMPAT_IA32 has been renamed
> >>> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
> >>> including this option must be modified accordingly.
> >>
> >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
> >>
> > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
> > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
> >
> > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
>
> Seriously, this is being debated? FreeBSD 3.2? Is this a joke?
> I caught the humor in the first couple of replies, but you sound
> serious. Wow.
Yes it is. Where was it discussed first? I do not see anything in my
freebsd-arch or freebsd-current archive; or any other FreeBSD list.
If there wasn't already a well established meaning to "COMPAT_FREEBSD"
(grep for it in /usr/src/sys/conf/), there probably wouldn't be any real
complaints.
--
-- David (obrien@FreeBSD.org)
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 17:45:30 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6D06E106566B;
Fri, 12 Mar 2010 17:45:30 +0000 (UTC) (envelope-from john@baldwin.cx)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
by mx1.freebsd.org (Postfix) with ESMTP id 401F48FC08;
Fri, 12 Mar 2010 17:45:30 +0000 (UTC)
Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net
[66.111.2.69])
by cyrus.watson.org (Postfix) with ESMTPSA id E6E8946B45;
Fri, 12 Mar 2010 12:45:29 -0500 (EST)
Received: from zion.baldwin.cx (pool-98-109-181-99.nwrknj.fios.verizon.net
[98.109.181.99])
by bigwig.baldwin.cx (Postfix) with ESMTPA id 98BFD8A027;
Fri, 12 Mar 2010 12:45:27 -0500 (EST)
From: John Baldwin <john@baldwin.cx>
To: freebsd-current@freebsd.org,
obrien@freebsd.org
Date: Fri, 12 Mar 2010 12:28:54 -0500
User-Agent: KMail/1.12.4 (FreeBSD/7.3-PRERELEASE; KDE/4.3.4; i386; ; )
References: <20100312163241.GA30935@dragon.NUXI.org>
In-Reply-To: <20100312163241.GA30935@dragon.NUXI.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201003121228.54426.john@baldwin.cx>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
(bigwig.baldwin.cx); Fri, 12 Mar 2010 12:45:27 -0500 (EST)
X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.3 required=4.2 tests=AWL,BAYES_00,
FH_HOST_EQ_VERIZON_P,RDNS_DYNAMIC autolearn=no version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx
X-Mailman-Approved-At: Fri, 12 Mar 2010 17:59:59 +0000
Cc:
Subject: Re: PANIC w/head@r204957: link_elf_lookup_symbol
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 17:45:30 -0000
On Friday 12 March 2010 11:32:41 am David O'Brien wrote:
> Details at
> http://trang.nuxi.org:8080/panics/DSC_0010.JPG
>
> Kernel sources at r203083 are stable for me.
Unfortunately the other useful bits have scrolled off the screen (the faulting
VA for example). Both of these panics do not look familiar, and a page fault
in strcmp() of two pointers that both look like sane kernel addresses seems
dubious.
--
John Baldwin
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 18:45:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A02BE1065707
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 18:45:00 +0000 (UTC)
(envelope-from pyunyh@gmail.com)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 31BDC8FC27
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 18:45:00 +0000 (UTC)
Received: by fxm23 with SMTP id 23so1501847fxm.3
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 10:44:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:subject
:message-id:reply-to:references:mime-version:content-type
:content-disposition:in-reply-to:user-agent;
bh=Tu7OBGVx8k1e9XzzvD0jm7fXJmtXb8OdAyq4qYCNJUU=;
b=nWzudKK0f7+cUNftefcbWFJd30o19kwiqigsndcQPavCpa5010FB5IIyqgW0V9nfFy
hminVvkJ1lLsisWZAE8EKOcilUQqYprxjQHrjLRFBeWvJVbhP4aw6tN+pmx4AI/htRCq
uQVcgiWy15cQjtQLX2nVpATMedidB3qLRBNRE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
b=Ozi38bgIKMncJWr3cLImQMFrnyjCu6L10U34abP8aSoiPtQWN51etsRSeDr9Hqej75
MU/QkR0PtX9GGVhxwvbSjW5fJ77NDnjI54qiZbyP8T+7OBqF7KWBSHN1MIKlMCXxhJBO
HUjLaXdrT8gxJ3WRs38YSTooumeIO6rvGTQwc=
Received: by 10.87.62.39 with SMTP id p39mr4825580fgk.9.1268419499294;
Fri, 12 Mar 2010 10:44:59 -0800 (PST)
Received: from pyunyh@gmail.com ([174.35.1.224])
by mx.google.com with ESMTPS id d6sm1953073fga.22.2010.03.12.10.44.56
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Fri, 12 Mar 2010 10:44:57 -0800 (PST)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
Fri, 12 Mar 2010 10:44:55 -0800
From: Pyun YongHyeon <pyunyh@gmail.com>
Date: Fri, 12 Mar 2010 10:44:55 -0800
To: freebsd-current@FreeBSD.org
Message-ID: <20100312184455.GJ16314@michelle.cdnetworks.com>
References: <20100306225248.GA20677@michelle.cdnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100306225248.GA20677@michelle.cdnetworks.com>
User-Agent: Mutt/1.4.2.3i
Cc:
Subject: Re: CFT: msk(4) Rx checksum offloading support
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 18:45:00 -0000
On Sat, Mar 06, 2010 at 02:52:48PM -0800, Pyun YongHyeon wrote:
> Finally I managed to understand how Rx checksum offloading works on
> Yukon II controllers. The patch at the following URL will add Rx
> checksum offloading support to msk(4) controllers.
> http://people.freebsd.org/~yongari/msk/msk.csum.patch
> The patch was generated against HEAD.
>
> Controllers(Yukon Extreme and Yukon FE+) which use more matured Rx
> checksum offloading does not need this patch. msk(4) already
> supported Rx checksum offloading for these controllers. This patch
> is for old Yukon controllers(Yukon EC, Yukon EC Ultra, Yukon FE and
> Yukon Ultra2). Due to known issues, Rx checksum offloading for
> Yukon XL was still disabled.
> I did not see much differences with/without Rx checksum offloading
> on my box but I guess it may show some differences on notebook
> systems. The patch also includes some diagnostic message like
> "Rx checksum value mismatch!" to detect possible hardware checksum
> logic failure so if you see this message please let me know.
>
For the record, the patch committed to HEAD(r205091).
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 18:58:23 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7C49C106566C
for <current@freebsd.org>; Fri, 12 Mar 2010 18:58:23 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (outp.internet-mail-service.net
[216.240.47.239])
by mx1.freebsd.org (Postfix) with ESMTP id 5F4668FC33
for <current@freebsd.org>; Fri, 12 Mar 2010 18:58:23 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o2CIwMFp009739; Fri, 12 Mar 2010 10:58:22 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id 162022D6011;
Fri, 12 Mar 2010 10:58:21 -0800 (PST)
Message-ID: <4B9A8ECC.6040503@elischer.org>
Date: Fri, 12 Mar 2010 10:58:20 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: obrien@freebsd.org
References: <4B991C00.3010809@intertainservices.com> <790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com> <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com> <20100311.192423.683591382013853731.imp@bsdimp.com>
<20100312171758.GB31089@dragon.NUXI.org>
In-Reply-To: <20100312171758.GB31089@dragon.NUXI.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc: FreeBSD Current <current@freebsd.org>
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 18:58:23 -0000
David O'Brien wrote:
> Yes names matter. Otherwise we would have made it "DEF8931". #define
> names are chosen to be self-documenting.
>
> $ grep COMPAT_FREEBSD conf/*
> conf/NOTES:# Note that as a general rule, COMPAT_FREEBSD<n> depends on
> conf/NOTES:# COMPAT_FREEBSD<n+1>, COMPAT_FREEBSD<n+2>, etc.
> conf/NOTES:options COMPAT_FREEBSD4
> conf/NOTES:options COMPAT_FREEBSD5
> conf/NOTES:options COMPAT_FREEBSD6
> conf/NOTES:options COMPAT_FREEBSD7
> conf/options:COMPAT_FREEBSD4 opt_compat.h
> conf/options:COMPAT_FREEBSD5 opt_compat.h
> conf/options:COMPAT_FREEBSD6 opt_compat.h
> conf/options:COMPAT_FREEBSD7 opt_compat.h
>
> COMPAT_FREEBSD32 is not the same as any of the other well established
> "COMPAT_FREEBSD" macros. So I do see where this could lead to confusion
> to users.
>
just add BIT on the end..
COMPAT_FREEBSD32BIT
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 18:59:50 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 310A8106567A;
Fri, 12 Mar 2010 18:59:50 +0000 (UTC)
(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
by mx1.freebsd.org (Postfix) with ESMTP id 0DD528FC29;
Fri, 12 Mar 2010 18:59:49 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
id 763CB8C060; Fri, 12 Mar 2010 12:59:49 -0600 (CST)
Date: Fri, 12 Mar 2010 12:59:49 -0600
From: Mark Linimon <linimon@lonesome.com>
To: obrien@freebsd.org, Scott Long <scottl@samsco.org>,
Scot Hetzel <swhetzel@gmail.com>, freebsd-current@freebsd.org,
Nathan Whitehorn <nwhitehorn@freebsd.org>
Message-ID: <20100312185949.GA31744@lonesome.com>
References: <4B99031D.3080308@freebsd.org>
<4B991C00.3010809@intertainservices.com>
<790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com>
<077AD48E-76D1-459A-9493-8DCB297A98DF@samsco.org>
<20100312172255.GC31089@dragon.NUXI.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100312172255.GC31089@dragon.NUXI.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc:
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 18:59:50 -0000
On Fri, Mar 12, 2010 at 09:22:55AM -0800, David O'Brien wrote:
> Yes it is. Where was it discussed first? I do not see anything in my
> freebsd-arch or freebsd-current archive; or any other FreeBSD list.
http://docs.freebsd.org/cgi/mid.cgi?4B971CA3.9090301
crossposted on amd64@, ia64@, emulation@.
mcl
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 19:10:55 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E1AD51065672
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 19:10:55 +0000 (UTC)
(envelope-from julian@elischer.org)
Received: from out-0.mx.aerioconnect.net (outq.internet-mail-service.net
[216.240.47.240])
by mx1.freebsd.org (Postfix) with ESMTP id C178F8FC1B
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 19:10:55 +0000 (UTC)
Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160])
by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id
o2CJAs9F010514; Fri, 12 Mar 2010 11:10:54 -0800
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
X-Client-Authorized: MaGic Cook1e
Received: from julian-mac.elischer.org
(h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137])
by idiom.com (Postfix) with ESMTP id D48112D6011;
Fri, 12 Mar 2010 11:10:53 -0800 (PST)
Message-ID: <4B9A91BC.5050203@elischer.org>
Date: Fri, 12 Mar 2010 11:10:52 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Gary Jennejohn <gary.jennejohn@freenet.de>,
Garrett Cooper <yanefbsd@gmail.com>, freebsd-current@freebsd.org
References: <4B991C00.3010809@intertainservices.com> <790a9fff1003111714s58d9ee4bl6454d1d52bf705b8@mail.gmail.com> <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com> <20100311.192423.683591382013853731.imp@bsdimp.com> <7d6fde3d1003112024o646afbf2w1ee4d81abae7e608@mail.gmail.com> <20100312113625.1b2b017f@ernst.jennejohn.org>
<20100312110221.GC99813@acme.spoerlein.net>
In-Reply-To: <20100312110221.GC99813@acme.spoerlein.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51
Cc:
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 19:10:56 -0000
Ulrich Spörlein wrote:
> On Fri, 12.03.2010 at 11:36:25 +0100, Gary Jennejohn wrote:
>> On Thu, 11 Mar 2010 20:24:57 -0800
>> Garrett Cooper <yanefbsd@gmail.com> wrote:
>>
>>> I can haz PR review then? Here's an easy one :)...
>>>
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=144644
>>>
>> Looks OK to me except I don't like the
>> if (something) {
>> one-line-of-code();
>> }
>> constructs, but according to style(9) these are sort-of OK, viz
>>
>> Closing and opening braces go on the same line as the else. Braces that
>> are not necessary may be left out.
>> ^^^^^^^^^^^^^^^
>> if (test)
>> stmt;
>> else if (bar) {
>> stmt;
>> stmt;
>> } else
>> stmt;
>>
>> Saved by the "may."
>
> True, but some folks (me included) really hate it, when different
> bracing is used *within* the same statement. The example above really is
> horrible. If one if/else-if clause needs braces, just brace them all. This
> loses no vertical space (the dangling else excluded) and some folks find
> it visually more pleasing/easier to read.
>
> ... hence begins the bikeshedding.
"Green"
My personal preference is that if one clause requires braces,
they all get them so you would never see
"else {"
or
"} else"
just
"else"
or
"} else {"
I just find it helps keep everything correctly associated when reading.
>
> Bye,
> Uli
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 19:53:25 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5B2A6106566B;
Fri, 12 Mar 2010 19:53:25 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
by mx1.freebsd.org (Postfix) with ESMTP id 099498FC0C;
Fri, 12 Mar 2010 19:53:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o2CJoPZN071426;
Fri, 12 Mar 2010 12:50:25 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Fri, 12 Mar 2010 12:50:32 -0700 (MST)
Message-Id: <20100312.125032.270969355930630649.imp@bsdimp.com>
To: obrien@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100312171758.GB31089@dragon.NUXI.org>
References: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
<20100311.192423.683591382013853731.imp@bsdimp.com>
<20100312171758.GB31089@dragon.NUXI.org>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: yanefbsd@gmail.com, freebsd-current@freebsd.org, nwhitehorn@freebsd.org,
swhetzel@gmail.com
Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 19:53:25 -0000
In message: <20100312171758.GB31089@dragon.NUXI.org>
"David O'Brien" <obrien@freebsd.org> writes:
: On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
: > In message: <7d6fde3d1003111720g7dccf93w1f51db88758a5c4d@mail.gmail.com>
: > Garrett Cooper <yanefbsd@gmail.com> writes:
: > : On Thu, Mar 11, 2010 at 5:14 PM, Scot Hetzel <swhetzel@gmail.com> wrote:
: > : > On Thu, Mar 11, 2010 at 10:36 AM, Mike Jakubik
: > : > <mike.jakubik@intertainservices.com> wrote:
: > : >> On 3/11/2010 9:50 AM, Nathan Whitehorn wrote:
: > : >>> As a result of importing 32-bit compatibility support for non-x86
: > : >>> 64-bit platforms, the kernel options COMPAT_IA32 has been renamed
: > : >>> COMPAT_FREEBSD32 in revision 205014, so all kernel configurations
: > : >>> including this option must be modified accordingly.
: > : >>
: > : >> That sounds a bit confusing, compatibility with FreeBSD 3.2?
: > : >>
: > : > I agree that the name COMPAT_FREEBSD32 is confusing, does it mean
: > : > compatiblity with FreeBSD 3.2, FreeBSD 32 or 32-bit ARCH's.
: > : >
: > : > A better name would have been COMPAT_ARCH32 or COMPAT_32BIT_ARCH.
: > :
: > : Agreed. Is it possible to change the name again because it really
: > : hasn't gotten much traction yet?
: >
: > What does the name matter, really?
:
: Yes names matter. Otherwise we would have made it "DEF8931". #define
: names are chosen to be self-documenting.
I'd maintain that this name is self-documenting as well. Obviously
you can take the what does the name matter to an extreme. However,
for names that meet a minimum threshold of conformity, there reaches a
point where arguing over them is counter productive. I believe that
this name meets those minimum requirements.
: $ grep COMPAT_FREEBSD conf/*
: conf/NOTES:# Note that as a general rule, COMPAT_FREEBSD<n> depends on
: conf/NOTES:# COMPAT_FREEBSD<n+1>, COMPAT_FREEBSD<n+2>, etc.
: conf/NOTES:options COMPAT_FREEBSD4
: conf/NOTES:options COMPAT_FREEBSD5
: conf/NOTES:options COMPAT_FREEBSD6
: conf/NOTES:options COMPAT_FREEBSD7
: conf/options:COMPAT_FREEBSD4 opt_compat.h
: conf/options:COMPAT_FREEBSD5 opt_compat.h
: conf/options:COMPAT_FREEBSD6 opt_compat.h
: conf/options:COMPAT_FREEBSD7 opt_compat.h
:
: COMPAT_FREEBSD32 is not the same as any of the other well established
: "COMPAT_FREEBSD" macros. So I do see where this could lead to confusion
: to users.
This is where we disagree. Any confusion can be solved by
documentation.
See for example these other compat options:
COMPAT_LINUX brings in the files in sys/compat/linux
COMPAT_SVR4 brings in the files in sys/compat/svr4
and
COMPAT_LINUX32 compiles the 32-bit linux support on 64-bit
hosts.
So the issue isn't as cut and dried as you might think. There's
multiple different conventions used here in addition to your simple
example. Users of 64-bit systems that will be using COMPAT_FREEBSD32
are likely to find this a natural extension of the COMPAT_LINUX32 that
they are likely already using.
Warner
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 19:57:14 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D09421065670
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 19:57:14 +0000 (UTC)
(envelope-from scjamorim@bsd.com.br)
Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com
[209.85.220.223])
by mx1.freebsd.org (Postfix) with ESMTP id 76B818FC24
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 19:57:14 +0000 (UTC)
Received: by mail-fx0-f223.google.com with SMTP id 23so1569831fxm.3
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 11:57:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.64.83 with SMTP id d19mr3203618fai.15.1268423834057; Fri,
12 Mar 2010 11:57:14 -0800 (PST)
Date: Fri, 12 Mar 2010 16:57:14 -0300
Message-ID: <5859850b1003121157l7b7fd4e9i445fefc78bceac7a@mail.gmail.com>
From: =?ISO-8859-1?Q?Sylvio_C=E9sar?= <scjamorim@bsd.com.br>
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: variables http_proxy in current 9 and 7.3-rc2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 19:57:14 -0000
Hi,
I have tree VM, (8.0, 7.3RC2, 9-current), in release 8.0 I have
not problem with variables: HTTP_PROXY, http_proxy, but in 7.3 and
9-current, seems that the part of authentication is not exported.
I use shell tcsh, my variables:
setenv HTTP_PROXY http://user:pass@proxyserver.com:80
setenv http_proxy http://user:pass@proxyserver.com:80
This configuration is ok in 8.0, but in 7.3RC2 and 9 I get: "Proxy
Authentication Required"
Somebody have this problem?
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 23:13:46 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 67010106564A
for <current@freebsd.org>; Fri, 12 Mar 2010 23:13:46 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-qy0-f194.google.com (mail-qy0-f194.google.com
[209.85.221.194])
by mx1.freebsd.org (Postfix) with ESMTP id 129978FC1A
for <current@freebsd.org>; Fri, 12 Mar 2010 23:13:45 +0000 (UTC)
Received: by qyk32 with SMTP id 32so1728535qyk.28
for <current@freebsd.org>; Fri, 12 Mar 2010 15:13:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=sp2oeSp1l0suvnVT91OC9Ak/JSRwwsLM8aFPo0MZ93I=;
b=onBN/FVZamPtvsFHSNtXW86NULE11glPwyn8CkI1+nNvvaaIu7YXDRIZFDA9oSWJMc
kjxlVnv9TgjN2c0CWyqj8ZLMBXJSpRqBtyb6pvYE+VEuGHPIdi9WRIHXQjJZ5p7GoJeG
kZyqRCAe1jUzIj69Q5aPfk/59hh0wdjRTu78U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=mg4bTD4Eac3NfePlYZb6bzFGM4yhJr9uYIIzwffr9JcFAjsdwzWiBPU0xKMWTWowUr
ZPQr0PTiQjhYPQE1QPd6mlRVwiOEdm8DisI6b7ptiGdVP8AqpwUTiESHkdDoBIXbibOy
3KRikMxrZGapKLMevqvs2ZCZQs2nuWt7BTlAA=
Received: by 10.220.124.105 with SMTP id t41mr1955vcr.178.1268435603178;
Fri, 12 Mar 2010 15:13:23 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id 24sm13479166vws.7.2010.03.12.15.13.20
(version=SSLv3 cipher=RC4-MD5); Fri, 12 Mar 2010 15:13:21 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Fri, 12 Mar 2010 15:13:34 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Fri, 12 Mar 2010 15:13:34 -0800
To: Alexandr Rybalko <ray@dlink.ua>
Message-ID: <20100312231333.GZ1295@weongyo>
Mail-Followup-To: Alexandr Rybalko <ray@dlink.ua>,
Alex RAY <ray@ddteam.net>, current@freebsd.org
References: <20091223035331.GA1293@weongyo>
<4b31cb29.9413f30a.5f4a.ffff8382@mx.google.com>
<20100226005115.GP14937@weongyo>
<20100227011535.ed3f2486.ray@ddteam.net>
<20100228095259.GB3536@weongyo>
<20100301103240.3a4aac8a.ray@dlink.ua>
<20100303082833.GB22865@weongyo>
<20100303111014.6564ea1e.ray@dlink.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100303111014.6564ea1e.ray@dlink.ua>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: Alex RAY <ray@ddteam.net>, current@freebsd.org
Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless
driver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 23:13:46 -0000
On Wed, Mar 03, 2010 at 11:10:14AM +0200, Alexandr Rybalko wrote:
> On Wed, 3 Mar 2010 00:28:33 -0800
> Weongyo Jeong <weongyo.jeong@gmail.com> wrote:
>
> >> On Mon, Mar 01, 2010 at 10:32:40AM +0200, Alexandr Rybalko wrote:
> >> > On Sun, 28 Feb 2010 01:52:59 -0800
> >> > Weongyo Jeong <weongyo.jeong@gmail.com> wrote:
> >> >
> >> > Can You test your driver without siba_switchcore, I see the device
> >> > have mapping for all cores on SSB?
> >>
> >> I see what you mean. siba_core.c which depends on PCI code would be
> >> compiled when it builds on SENTRY5. So it looks currently it needs a
> >> patch to compile siba bus code without PCI code. I'll try to make a
> >> patch.
>
> I now trying to make bus independent interface, not done yet.
> When finish, I send to You for review and maybe test.
It's my pleasure to test your patch.
>
> >>
> >> > > ssb0: <Broadcom BCM4315 802.11b/g Wireless> mem 0xf4000000-0xf4003fff
> >> > Think thre is 4 cores.
> >> > When SSB on nexus, we don`t need core switching, maybe on PCI too.
> >>
> >> I think this is a difference between siba(4) and siba_bwn currently and
> >> it's one of TODOs we should solve to merge two codes.
> >>
> >> AFAIK approach to access each cores isn't same; it looks siba(4) creates
> >> devices for each cores so it'd not need to switch cores. But siba_bwn
> >> doesn't do it like siba(4) so it needs to switch cores because all are
> >> handled on one device.
>
> Look into this line:
> ssb0: <Broadcom BCM4315 802.11b/g Wireless> mem 0xf4000000-0xf4003fff
> There we see, device have 0x4000 memory window. Each core required 0x1000.
> Your code to call required core move PCI window to appropriate 0x1000 block
> (if core - second, move to 0xf4001000).
> Maybe we can map full window, and then access to required core without
> core switching.
I thought that your opinion was right and if mem is
0xf4000000-0xf4003fff (16 Kb) I thought the device has 4 cores. However
it looks this was wrong according to the below document:
http://voodoowarez.com/bcm5365p.pdf
Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that
16Kb, maybe 8 Kb in the old devices is core register region.
"Accesses to the lower half of the core register region are translated
into system backplane accesses using the PCIBAR0Window register"
"Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct
access to the external SPROM"
If we just access memory using offset + core and bus_space_read_x
interfaces it would actually not access core register region.
So without solving this problem it looks it could not remove coreswitch
routines.
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 23:58:48 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C0181106564A
for <current@freebsd.org>; Fri, 12 Mar 2010 23:58:48 +0000 (UTC)
(envelope-from davidch@broadcom.com)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19])
by mx1.freebsd.org (Postfix) with ESMTP id 936A88FC16
for <current@freebsd.org>; Fri, 12 Mar 2010 23:58:48 +0000 (UTC)
Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom
SMTP Relay (Email Firewall v6.3.2)); Fri, 12 Mar 2010 15:58:33 -0800
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by
IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Fri, 12
Mar 2010 15:59:57 -0800
From: "David Christensen" <davidch@broadcom.com>
To: "Ian FREISLICH" <ianf@clue.co.za>,
"pyunyh@gmail.com" <pyunyh@gmail.com>
Date: Fri, 12 Mar 2010 15:58:31 -0800
Thread-Topic: dev.bce.X.com_no_buffers increasing and packet loss
Thread-Index: AcrA6Vwt0ZDaUZGKRN2wvtRBpJh3wgBViJAg
Message-ID: <5D267A3F22FD854F8F48B3D2B52381933B0A21DB97@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <20100310230220.GI10657@michelle.cdnetworks.com>
<E1Nnc4d-0003mB-6e@clue.co.za> <E1Nne0Q-0003uZ-OR@clue.co.za>
<E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310195206.GB10657@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
<E1NpcT6-000IuH-FO@clue.co.za>
In-Reply-To: <E1NpcT6-000IuH-FO@clue.co.za>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67840AA331G58121710-01-01
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "current@freebsd.org" <current@freebsd.org>
Subject: RE: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 23:58:48 -0000
> Pyun YongHyeon wrote:
> > On Wed, Mar 10, 2010 at 02:45:47PM -0800, David Christensen wrote:
> > > The bce(4) hardware supports a linked list of pages for RX buffer=20
> > > descriptors. The stock build supports 2 pages (RX_PAGES) with a=20
> > > total of 511 BD's per page. The hardware can support a=20
> maximum of=20
> > > 64K BD's but that would be an unnecessarily large amount of mbufs=20
> > > for an infrequent problem.
>=20
> I think that depends on how you define infrequent. Our use=20
> case is a largish core router. It's highly likely that we'll=20
> see this again and again in various packet storms on our network.
>=20
Are the packet storms always always from the same host or do they come
from multiple hosts? The hardware supports RSS which can spread the
network load across multiple receive queues and multiple CPU cores, but
only when the traffic is spread across several hosts. (The current
bce(4) driver doesn't include support for RSS.) If a storm of
small frames comes from a single host then almost all adapters will be
challenged to handle the flow.
Dave=
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 00:18:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 152961065676
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 00:18:32 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com
[209.85.219.228])
by mx1.freebsd.org (Postfix) with ESMTP id 901F98FC0C
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 00:18:31 +0000 (UTC)
Received: by ewy28 with SMTP id 28so284519ewy.13
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 16:18:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=oe7OAhv4bUe46Gy/nzNs0+OF9NvPGvm/qvx0yougiIY=;
b=AfmDLqnwr611N/oDcEHKpENgwjN9gPHIp2PUR9YagpvnmXct+yc4solY3mxsgNACtw
NFWK05cBOPb7xmBw+wyNVLm9GFowWnqtE9npQ8MgFCfFL0Ujy37JliVeCWseS0uJVi+O
iZ+dzND/Z8N1O8npZHRGY04nZig7KSpk5azK4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=vlNHbuXd09zk1kKMoeNq44kdfXTuGHbB+bjr5svJEfHDS3DfHY2lpFec9PbmWxZQGk
uIbaI88FAxxTrGPWhHPi8S9PvYjfSfivoTS4fZeucUWpr2PxV5S/f6QSKk0KWmQOTbd3
es+HLIFxLBFgxuvHvfeN33JkL5QDzngDWxUbs=
Received: by 10.213.100.4 with SMTP id w4mr841850ebn.53.1268439510425;
Fri, 12 Mar 2010 16:18:30 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id 13sm1299523ewy.9.2010.03.12.16.18.27
(version=SSLv3 cipher=RC4-MD5); Fri, 12 Mar 2010 16:18:29 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Fri, 12 Mar 2010 16:18:42 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Fri, 12 Mar 2010 16:18:42 -0800
To: PseudoCylon <moonlightakkiy@yahoo.ca>
Message-ID: <20100313001842.GB1295@weongyo>
Mail-Followup-To: PseudoCylon <moonlightakkiy@yahoo.ca>,
freebsd-current@freebsd.org,
Alexander Egorenkov <egorenar@googlemail.com>
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16641.96608.qm@web51806.mail.re2.yahoo.com>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: Alexander Egorenkov <egorenar@googlemail.com>, freebsd-current@freebsd.org
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 00:18:32 -0000
On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote:
> Hello,
>
> Finally, I have fixed mysterious device lock out and run(4) works fine
> in HOSTAP mode. Up time is 80 hours and counting. I even filed tax
> though it.
>
> The device supports up to 253 stations. I only tested with 2 station.
> If you have resources, please hit it with bunch of STAs.
>
> As usual codes are posted at my git repository
> git://dev.nasreddine.com/run.git
> http://dev.nasreddine.com/gitweb/?p=run.git;a=summary
> Please fetch 'hostap_rc' branch not 'master' this time.
>
> or freebsd forums
> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e9805146e&t=7562
Out of curiosity, what's the difference between run(4) and rt2870 driver
written by Alexander Egorenkov? And why there are two drivers?
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 00:38:12 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 37F06106566B
for <current@freebsd.org>; Sat, 13 Mar 2010 00:38:12 +0000 (UTC)
(envelope-from weongyo.jeong@gmail.com)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com
[209.85.219.228])
by mx1.freebsd.org (Postfix) with ESMTP id B7E4F8FC13
for <current@freebsd.org>; Sat, 13 Mar 2010 00:38:11 +0000 (UTC)
Received: by ewy28 with SMTP id 28so286653ewy.13
for <current@freebsd.org>; Fri, 12 Mar 2010 16:38:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:from:date:to:cc
:subject:message-id:reply-to:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent:organization:x-operation-sytem;
bh=SJcEcaDzKNpCERfdkn9Lp3opGDlc62IoVvaEEZ3zfg8=;
b=Oty/Jmu0UUR6SldC430bZ/woofXWVzRD+iMhUfqksemiC7hlL38iWY1Zhpkotr7aIy
SySc8ONj8IK2AZkscyjjnfm1I7zpEUm5qBGgpOKd5S7RmvWKgQbrGZSpyDnADL956uKD
LzbVGKrF0mu/cJ5OdE8kPJnZmGmOwhRVBb/40=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to
:references:mime-version:content-type:content-disposition
:in-reply-to:user-agent:organization:x-operation-sytem;
b=N3wsUwGiUyogCFSwBacbb//+rLoboK7Z6doV+7zqFeGwgqQTHwrvZL23iTjxnaNpeI
2iT9KIRiuwrG9d9KI8uE9pipZYTG4/Z63nup5Z2SBNHkWjqjP2Jpd+MUbH3aoD0x/ogd
svjEOIIruWBvqyjLXy7jJBu2YoXPpcm7xFLwA=
Received: by 10.213.24.17 with SMTP id t17mr3401199ebb.19.1268440690567;
Fri, 12 Mar 2010 16:38:10 -0800 (PST)
Received: from weongyo ([174.35.1.224])
by mx.google.com with ESMTPS id 15sm1310481ewy.8.2010.03.12.16.38.06
(version=SSLv3 cipher=RC4-MD5); Fri, 12 Mar 2010 16:38:07 -0800 (PST)
Received: by weongyo (sSMTP sendmail emulation);
Fri, 12 Mar 2010 16:38:21 -0800
From: Weongyo Jeong <weongyo.jeong@gmail.com>
Date: Fri, 12 Mar 2010 16:38:21 -0800
To: Azim <quakerdoomer@fmguy.com>
Message-ID: <20100313003821.GC1295@weongyo>
Mail-Followup-To: Azim <quakerdoomer@fmguy.com>, current@freebsd.org
References: <1267855141.11829.1363396963@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1267855141.11829.1363396963@webmail.messagingengine.com>
User-Agent: Mutt/1.4.2.3i
Organization: CDNetworks.
X-Operation-Sytem: FreeBSD
Cc: current@freebsd.org
Subject: Re: ndisgen on FreeBSD-9.0-CURRENT-201002-i386
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Weongyo Jeong <weongyo@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 00:38:12 -0000
On Sat, Mar 06, 2010 at 08:59:01AM +0300, Azim wrote:
> I tried ndisgen to convert BCMWL564.SYS using FreeBSD-9.0-CURRENT
> FEB-2010(x86).
> The files I had were :
> It gave an error stating BCM43XX64.CAT(unrequired),
> BCM43XX.CAT(unrequired), bcmwl5.inf and BCMWL564.SYS
>
> I had successfully compiled the 32-bit and 64-bit driver on FreeBSD 8.0
> (the 64-BIT couldn't be used on FreeBSD amd64 though)
>
> This time on FreeBSD-9.0-CURRENT while trying ndisgen the following
> files got created:
> bus_if.h
> device_if.h
> windrv.h
> and windrv.o and ndisgen echoed an error
>
> ==============
> Generating Makefile... done
> Building kernel module.. "/usr/share/mk/bsd.kmod.mk", line 12: "can't
> find kernel source tree"
It looks it failed to search kernel source in standard places, for
example:
${.CURDIR}/../../kern
${.CURDIR}/../../../kern
${.CURDIR}/../../../../kern
${.CURDIR}/../../../../../kern
/sys/kern
/usr/src/sys/kern
Could you please check that one of above directories exists?
regards,
Weongyo Jeong
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 03:33:47 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 89F67106566C
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 03:33:47 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-px0-f200.google.com (mail-px0-f200.google.com
[209.85.216.200])
by mx1.freebsd.org (Postfix) with ESMTP id 5B3758FC2B
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 03:33:47 +0000 (UTC)
Received: by pxi38 with SMTP id 38so1023440pxi.27
for <freebsd-current@freebsd.org>; Fri, 12 Mar 2010 19:33:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=kmNBJ4krYIloamPYqE5StcTBpTJGUoLiDFYw0DGWqXQ=;
b=Te/sHitdvcwdlL24KUG4uy65M1wX79ntEqNuLQeqwA256jRBbjsf7xjF5P6AmgD2bB
Fltzi+PQbzbilCGLmph4/yzQvX6/LxFB0W5oJ19XVQNW+Zz3qofDsW299+JbAq38i6ij
VGUk8P71IOxIrQd1Ll9TOjKyVHC7HIhxJ7ubA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=NOEaR6smL17gzXpQgA7cmeaUlP4Lgb+cKrWn3I+HGvGeENzPqcg/u3CvUp6wHcrY4c
ooFOex5PwRWNqKP3jwnJ2vS9VlyaAKZl53B0eo9JRNTCW1tIxig/fVpPkWFVJvewPaGd
vM2GhZzRwGWkB35zOPcHIsYKwKX6mpFuD08oQ=
MIME-Version: 1.0
Received: by 10.143.27.20 with SMTP id e20mr3276657wfj.256.1268451226847; Fri,
12 Mar 2010 19:33:46 -0800 (PST)
In-Reply-To: <7d6fde3d1003102158o7834ca67lce3eca23aa723fd1@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
<4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
<7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
<7d6fde3d1003102158o7834ca67lce3eca23aa723fd1@mail.gmail.com>
Date: Fri, 12 Mar 2010 19:33:46 -0800
Message-ID: <7d6fde3d1003121933s4ba7b57fw6542628c16edf723@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Giovanni Trematerra <giovanni.trematerra@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Tom Couch <tom.couch.storage@gmail.com>,
FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 03:33:47 -0000
On Wed, Mar 10, 2010 at 9:58 PM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 2:07 PM, Tom Couch <tom.couch.storage@gmail.com> =
wrote:
>> Hi FreeBSD-current,
>> =A0 =A0 My name is Tom Couch,
>> I am part of the 3ware driver team recently acquired by LSI.
>> I believe Giovanni's patch, below, is the correct fix for this bug.
>>
>> I am available to maintain the twa driver, now that I am on this list.
>> Let me know how I can help,
>>
>> Tom
>>
>>
>> On Wed, Mar 10, 2010 at 1:56 PM, Giovanni Trematerra <
>> giovanni.trematerra@gmail.com> wrote:
>>
>>> On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper <yanefbsd@gmail.com>
>>> wrote:
>>> > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper <yanefbsd@gmail.com>
>>> wrote:
>>> >> Hi Alexander and Hans,
>>> >> =A0 =A0I recently did the following which generated a panic on a
>>> >> 9-CURRENT kernel compiled on the 26th:
>>> >>
>>> >> 1. Executed reboot
>>> >> 2. Removed keyboard.
>>> >> 3. Some time after `All buffers synced\nUptime: ...' was displayed,
>>> >> the keyboard was registered disconnected.
>>> >> 4. The interrupt was delivered to my twa(4) enabled card and the
>>> >> kernel panicked, like so:
>>> >>
>>> >> ugen2.2: <Mitsumi Electric> at usbus2 (disconnected)
>>> >> uhub8: at uhub2, port 1, addr 2 (disconnected)
>>> >> ugen2.3: <Mitsumi Electric> at usbus2 (disconnected)
>>> >> ukbd0: at uhub8, port 3, addr 3 (disconnected)
>>> >> uhid0: at uhub8, port 3, addr 3 (disconnected)
>>> >> panic: mtx_lock_spin() of destroyed mutex @
>>> /usr/src/sys/dev/twa/tw_cl_intr.c:88
>>> >>
>>> >> cpuid =3D 1
>>> >> KDB: enter: panic
>>> >> [thread pid 12 tid 100025 ]
>>> >> Stopped at =A0 =A0 =A0 =A0 kdb_enter+0x3d: movq =A0 =A0 $0,0x40289c(=
%rip)
>>> >> db>
>>> >>
>>> >> =A0 =A0I wish I could provide you with more details, but unfortunate=
ly I
>>> >> the USB bus isn't registering the fact that I'm reattaching the
>>> >> keyboard right now and the box won't reboot automatically :( (didn't
>>> >> set the right sysctl beforehand to panic automatically). I'll try an=
d
>>> >> reproduce the issue again, but I was just wondering whether or not y=
ou
>>> >> guys had seen this problem before.
>>> >
>>> > =A0 =A0Phew... it's reproducible with that kernel. Here's what I did
>>> > exactly (because my original directions were incorrect):
>>> > =A0 =A01. Hit power button (for S5).
>>> > =A0 =A02. Disconnect keyboard RIGHT as `Uptime: ...' is displayed.
>>> > =A0 =A0Kernel panicked on my system again. Now to figure out if it st=
ill
>>> > exists with a kernel compiled today, and also how to debug it if it
>>> > still does exist :/...
>>> > Thanks,
>>> > -Garrett
>>>
>>> Hi Garrett,
>>> Could you please try the patch below and report back?
>>>
>>> Thank you
>>>
>>> diff -r cab6489de66d sys/dev/twa/tw_cl_intr.c
>>> --- a/sys/dev/twa/tw_cl_intr.c =A0 =A0 =A0 =A0Wed Mar 03 04:51:13 2010 =
-0500
>>> +++ b/sys/dev/twa/tw_cl_intr.c =A0 =A0 =A0 =A0Wed Mar 10 06:29:05 2010 =
-0500
>>> @@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle
>>> =A0 =A0 =A0if (ctlr =3D=3D NULL)
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 goto out;
>>>
>>> - =A0 =A0 /* If we get an interrupt while resetting, it is a shared
>>> - =A0 =A0 =A0 =A0one for another device, so just bail */
>>> - =A0 =A0 if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS)
>>> + =A0 =A0 /*
>>> + =A0 =A0 =A0* =A0If we get an interrupt while resetting or shutting do=
wn,
>>> + =A0 =A0 =A0* =A0it is a shared one for another device, so just bail
>>> + =A0 =A0 =A0*/
>>> + =A0 =A0 if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS ||
>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (ctrl->state & TW_CLI_CTLR_ST=
ATE_ACTIVE) =3D=3D 0)
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0goto out;
>>>
>>> =A0 =A0 =A0/*
Apart from the typo above (s/ctrl/ctlr/), things work appropriately
now at reboot. The only problem is that bootup is really wonky now,
because the RAID had a LOT of issues attaching to cam(4) (failed in
2/3 cold boot attempts); an additional branch condition may need to be
added to the above if-statement if this change didn't take that into
account. However, if the old behavior was incorrect and the new
behavior is correct, s.t. the RAID controller demonstrating bus
detection timeout issue that is occurring with a lot of USB devices
and some RAID controllers today, this could be extremely problematic.
So, while it looks better than before at reboot, it's not ready yet
for prime time; I'd rather that the bug was filed with the patch you
provided after the typo fixed, with the caveat mentioned and NOT
committed, because the adverse affect(s) seem a bit more annoying than
the previous panic issue described.
> I'll give the patch a try sometime before the weekend; I have a
> critical deadline that I need to work through and the machine can't be
> taken offline until then.
Thanks :),
-Garrett
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 05:00:30 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 864B2106564A
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 05:00:30 +0000 (UTC)
(envelope-from moonlightakkiy@yahoo.ca)
Received: from web51803.mail.re2.yahoo.com (web51803.mail.re2.yahoo.com
[206.190.38.234])
by mx1.freebsd.org (Postfix) with SMTP id 2DCC48FC18
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 05:00:29 +0000 (UTC)
Received: (qmail 58799 invoked by uid 60001); 13 Mar 2010 05:00:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024;
t=1268456429; bh=aZGBVp3utwCxXn3c1AP2fFDf1loJPLvaucOa+5se6dE=;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
b=C4AIqFBVofRjSvWhMegI1M+7WjkuyOzKYn94c5xIMpwyZoRV0LF73dSRqjTq/6G6T43hck9+6BE5HAPvSwIEFdLSLV7DXzMRiCBVfQ3t4tNPtg4iCp4cG8vv9EBY6PSZsCUbCfw3Iw6GKigl/pqrt6AzT8UnAVTfniaegykdsKw=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
b=H7N+8aKqQU3ZwnAzMy+gJwJrxBGX4IxBcgNCZA/v/05vmhU8ThiF2Vt1YnKu5M6kvZQWSgknkgZrqB+PuXZ5VIWCHE18MNnh8NzcJerrGBA3F+GfoJ1Xjstda654dg32FuYqjEEBIEASbCdpjBjCOU9QkI7nlxSTLN+BUeueuzo=;
Message-ID: <181143.50535.qm@web51803.mail.re2.yahoo.com>
X-YMail-OSG: DWmLPlAVM1lToTLuFtPO2H3v_FvzmfDTuRQuMagbnYwy_YiJubr1cBZoa3708C0u7JftN2_SagRDZPN33.mC6AovrOe7rtI8KmMX5bCpNKlsC63XSCxqEXgSWIffu1DrLmwJJFDREo6u8aXX6kvwG_Eb2qXGacWDUYhGoeMsUhaKw04no6Cl2c_elidjlmwlX53VBLFivypIy.phudaG5apuQn9QBo3O_.elo4e4TUFUVpofq2.LGM9MrAK6U9a9Oe7tFsW3Fs6z_cccmROX.CnwZh.Efhydt7uqWYjJahOl2hJ9OMcyEQN.m2wJ98ufB.VVe_IrKX0.DHUOyoA6ZsATeJU8EJIJ_Ss2NRmxLTJDXtlik8Li.Gtv.KUSkXp11g--
Received: from [173.183.132.20] by web51803.mail.re2.yahoo.com via HTTP;
Fri, 12 Mar 2010 21:00:28 PST
X-Mailer: YahooMailRC/324.3 YahooMailWebService/0.8.100.260964
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
<7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
Date: Fri, 12 Mar 2010 21:00:28 -0800 (PST)
From: PseudoCylon <moonlightakkiy@yahoo.ca>
To: Rui Paulo <rpaulo@gmail.com>, Weongyo Jeong <weongyo@freebsd.org>
In-Reply-To: <7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Alexander Egorenkov <egorenar@googlemail.com>, freebsd-current@freebsd.org
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 05:00:30 -0000
----- Original Message ----
> From: Rui Paulo <rpaulo@gmail.com>
> To: Weongyo Jeong <weongyo@freebsd.org>
> Cc: PseudoCylon <moonlightakkiy@yahoo.ca>; Alexander Egorenkov <egorenar@googlemail.com>; freebsd-current@freebsd.org
> Sent: Fri, March 12, 2010 7:42:46 PM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
> Out of curiosity, what's the difference between run(4) and rt2870
> driver
> written by Alexander Egorenkov? And why there are two
> drivers?
The thread says it all. Just need to go though some pages. His user name is egorenar.
http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e9805146e&t=7562
> From what I understand, Alexander's driver supports 11n ann
> run(4) doesn't.
That's correct. Besides run(4) supports rt3XXX chipsets.
AK
__________________________________________________________________
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 02:43:08 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4F09E106564A;
Sat, 13 Mar 2010 02:43:08 +0000 (UTC)
(envelope-from rpaulo@gmail.com)
Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54])
by mx1.freebsd.org (Postfix) with ESMTP id B0CBC8FC14;
Sat, 13 Mar 2010 02:43:07 +0000 (UTC)
Received: by gwj15 with SMTP id 15so783905gwj.13
for <multiple recipients>; Fri, 12 Mar 2010 18:43:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:cc:message-id:from:to
:in-reply-to:content-type:content-transfer-encoding:mime-version
:subject:date:references:x-mailer;
bh=rNXokl4Qi8AfuKv2L+wfb4aE8sEi6O13SpqFwDjcto0=;
b=L2kkSZQuqVP/aOiSWcKitBS7KDYCmaMqv6xlERYUKAtUipIO7jSMtTZY6EdpO8au0c
VBwUkmJYeZamUurdJRsA6PmlWOt53f1CaG9LUWEH7HZcEZbgTwh+VYNCqX01U4m1AYgx
CWLgKoYEduFqcaYgUyof1JxyxRmvxz9P6VUH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=cc:message-id:from:to:in-reply-to:content-type
:content-transfer-encoding:mime-version:subject:date:references
:x-mailer;
b=XVHIexF7yDw2Dn71Qd3JDJfkdYQtFmGXmBgjtPzdjDPnLicLCSK6WJl+V122ZW3RBd
3fXJcyzoTMOW3ZjLffYnH81Yqw3z5Ml0sOdevMAhBLyvrSg0zV6HRnrOTF+lLYhhA/Gp
KecAWA0CZd39TfNXipXPMUcT94cxhrbdzESm0=
Received: by 10.150.213.10 with SMTP id l10mr983183ybg.292.1268448187017;
Fri, 12 Mar 2010 18:43:07 -0800 (PST)
Received: from [192.168.11.61] (197.214.32.202.bf.2iij.net [202.32.214.197])
by mx.google.com with ESMTPS id 21sm623387yxe.57.2010.03.12.18.43.04
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Fri, 12 Mar 2010 18:43:05 -0800 (PST)
Message-Id: <7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
From: Rui Paulo <rpaulo@gmail.com>
To: Weongyo Jeong <weongyo@freebsd.org>
In-Reply-To: <20100313001842.GB1295@weongyo>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 13 Mar 2010 11:42:46 +0900
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Sat, 13 Mar 2010 05:35:36 +0000
Cc: Alexander Egorenkov <egorenar@googlemail.com>,
PseudoCylon <moonlightakkiy@yahoo.ca>, freebsd-current@freebsd.org
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 02:43:08 -0000
On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
> On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote:
>> Hello,
>>
>> Finally, I have fixed mysterious device lock out and run(4) works
>> fine
>> in HOSTAP mode. Up time is 80 hours and counting. I even filed tax
>> though it.
>>
>> The device supports up to 253 stations. I only tested with 2 station.
>> If you have resources, please hit it with bunch of STAs.
>>
>> As usual codes are posted at my git repository
>> git://dev.nasreddine.com/run.git
>> http://dev.nasreddine.com/gitweb/?p=run.git;a=summary
>> Please fetch 'hostap_rc' branch not 'master' this time.
>>
>> or freebsd forums
>> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e9805146e&t=7562
>
> Out of curiosity, what's the difference between run(4) and rt2870
> driver
> written by Alexander Egorenkov? And why there are two drivers?
From what I understand, Alexander's driver supports 11n ann run(4)
doesn't.
--
Rui Paulo
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 07:38:20 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D7C16106566B;
Sat, 13 Mar 2010 07:38:20 +0000 (UTC)
(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe15.tele2.se [212.247.155.193])
by mx1.freebsd.org (Postfix) with ESMTP id 386378FC0A;
Sat, 13 Mar 2010 07:38:19 +0000 (UTC)
X-Cloudmark-Score: 0.000000 []
X-Cloudmark-Analysis: v=1.0 c=1 a=HEYnYNVUCg4A:10 a=8nJEP1OIZ-IA:10
a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17
a=Gi-K3LvrAAAA:8 a=6I5d2MoRAAAA:8 a=-Cy5jTvq0hLELnmmK6cA:9
a=kgumY2lOIJM9m4YpIBYA:7 a=LHiyRJuXErUZMuBgkRBfwzMXl5kA:4
a=wPNLvfGTeEIA:10 a=tlJW8gxtbz4A:10
Received: from [188.126.201.140] (account mc467741@c2i.net HELO
laptop002.hselasky.homeunix.org)
by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.19)
with ESMTPA id 638463213; Sat, 13 Mar 2010 08:38:18 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-current@freebsd.org
Date: Sat, 13 Mar 2010 08:36:41 +0100
User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; amd64; ; )
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
<7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
In-Reply-To: <7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
X-Face: +~\`s("[*<S!NI[0M*"FaghA8S>|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA:
hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR
Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L'
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201003130836.41718.hselasky@c2i.net>
Cc: Rui Paulo <rpaulo@gmail.com>, PseudoCylon <moonlightakkiy@yahoo.ca>,
Alexander Egorenkov <egorenar@googlemail.com>,
Weongyo Jeong <weongyo@freebsd.org>
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 07:38:20 -0000
On Saturday 13 March 2010 03:42:46 Rui Paulo wrote:
> On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
> > On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote:
> >> Hello,
> >>
> >> Finally, I have fixed mysterious device lock out and run(4) works
> >> fine
> >> in HOSTAP mode. Up time is 80 hours and counting. I even filed tax
> >> though it.
> >>
> >> The device supports up to 253 stations. I only tested with 2 station.
> >> If you have resources, please hit it with bunch of STAs.
> >>
> >> As usual codes are posted at my git repository
> >> git://dev.nasreddine.com/run.git
> >> http://dev.nasreddine.com/gitweb/?p=run.git;a=summary
> >> Please fetch 'hostap_rc' branch not 'master' this time.
> >>
> >> or freebsd forums
> >> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e98051
> >>46e&t=7562
> >
> > Out of curiosity, what's the difference between run(4) and rt2870
> > driver
> > written by Alexander Egorenkov? And why there are two drivers?
>
> From what I understand, Alexander's driver supports 11n ann run(4)
> doesn't.
Will this two drivers be merged then?
--HPS
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 08:24:52 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2DEAB106564A;
Sat, 13 Mar 2010 08:24:52 +0000 (UTC)
(envelope-from rpaulo@gmail.com)
Received: from mail-yx0-f201.google.com (mail-yx0-f201.google.com
[209.85.210.201])
by mx1.freebsd.org (Postfix) with ESMTP id C2BB48FC1C;
Sat, 13 Mar 2010 08:24:51 +0000 (UTC)
Received: by yxe39 with SMTP id 39so811192yxe.3
for <multiple recipients>; Sat, 13 Mar 2010 00:24:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:cc:message-id:from:to
:in-reply-to:content-type:content-transfer-encoding:mime-version
:subject:date:references:x-mailer;
bh=+ode/r9Z9zn6VCG9fdVm5QrxlhYK7bMKC6HsWLxZscM=;
b=PZAb9D3ToQI8Byorrhwf2w8oODoqfix5naZi2jTpRl+aJKOMR8ndnGv0rxwK8zRpd4
cPtGy/YfFvxvv5aKecVg2H+UGUVk5N1qR+sbdIuwisL06kvvUtGd42i2JoknLt89xRF3
WSMBI9LA1lbHuOtTpk8x59FlncJFPxtzWYgPw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=cc:message-id:from:to:in-reply-to:content-type
:content-transfer-encoding:mime-version:subject:date:references
:x-mailer;
b=AowP+YXSNovvKsxdFtyNbrJW7NFqaCmTBXhmSRFYAy+FxGP7NxxeVtQBhQbkPbgGqS
tq+lqAzrOWGqoxoQaClWIJV3qYbjnsTIy8QLSRHc2FYwqdicv7gPEopXSf2yasOMerLm
dVf6psMcduX8H6f9kzIXxacDfDRBwdJbvBtIE=
Received: by 10.151.133.14 with SMTP id k14mr1150756ybn.138.1268468690920;
Sat, 13 Mar 2010 00:24:50 -0800 (PST)
Received: from [192.168.10.20] (s224.GtokyoFL6.vectant.ne.jp [222.228.90.224])
by mx.google.com with ESMTPS id 21sm1634355iwn.3.2010.03.13.00.24.48
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sat, 13 Mar 2010 00:24:49 -0800 (PST)
Message-Id: <6E0360A9-A9D6-4739-8F26-B9BD4585D08B@gmail.com>
From: Rui Paulo <rpaulo@gmail.com>
To: PseudoCylon <moonlightakkiy@yahoo.ca>
In-Reply-To: <181143.50535.qm@web51803.mail.re2.yahoo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 13 Mar 2010 17:24:38 +0900
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
<7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
<181143.50535.qm@web51803.mail.re2.yahoo.com>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Sat, 13 Mar 2010 13:54:43 +0000
Cc: Alexander Egorenkov <egorenar@googlemail.com>,
Weongyo Jeong <weongyo@freebsd.org>, freebsd-current@freebsd.org
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 08:24:52 -0000
On 13 Mar 2010, at 14:00, PseudoCylon wrote:
> ----- Original Message ----
>
>> From: Rui Paulo <rpaulo@gmail.com>
>> To: Weongyo Jeong <weongyo@freebsd.org>
>> Cc: PseudoCylon <moonlightakkiy@yahoo.ca>; Alexander Egorenkov <egorenar@googlemail.com
>> >; freebsd-current@freebsd.org
>> Sent: Fri, March 12, 2010 7:42:46 PM
>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>
>> On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
>> Out of curiosity, what's the difference between run(4) and rt2870
>> driver
>> written by Alexander Egorenkov? And why there are two
>> drivers?
> The thread says it all. Just need to go though some pages. His user
> name is egorenar.
> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e9805146e&t=7562
>
>> From what I understand, Alexander's driver supports 11n ann
>> run(4) doesn't.
> That's correct. Besides run(4) supports rt3XXX chipsets.
Oh, I see. I think we really need to start working on merging the two...
--
Rui Paulo
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 08:24:59 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5F4061065670;
Sat, 13 Mar 2010 08:24:59 +0000 (UTC)
(envelope-from rpaulo@gmail.com)
Received: from mail-iw0-f185.google.com (mail-iw0-f185.google.com
[209.85.223.185])
by mx1.freebsd.org (Postfix) with ESMTP id 10BF18FC0A;
Sat, 13 Mar 2010 08:24:58 +0000 (UTC)
Received: by iwn15 with SMTP id 15so1877624iwn.7
for <multiple recipients>; Sat, 13 Mar 2010 00:24:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:cc:message-id:from:to
:in-reply-to:content-type:content-transfer-encoding:mime-version
:subject:date:references:x-mailer;
bh=Fbhx5vVN6bLCNRM2g/bbmKI/6lRHTqQcSHlV7SHZxmw=;
b=ebjaXo2ZaeADHcyY6kTLemVSpldnHSHUUn2q+gPasromHd4QCXUMQIXcRLwTY0BkqM
xWPtJ8yTSUNMSQckzJdIhIISQiqnzoe6Qzl64t7sbJN+960ZNf8V2oOO7UD1px6vzEBu
x7BIiPCdpaKmyOqHAQ0BwbF0PmBPBYfqb2Nt0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=cc:message-id:from:to:in-reply-to:content-type
:content-transfer-encoding:mime-version:subject:date:references
:x-mailer;
b=N+51imH+E90J9XlBsoCa4LFvNiF5VPqzPISUvRZRTn0Ecb6SXjTfoiWYnII5wE6u8a
/t5z9AoRkw+yfPV2NRDw2LFHm6kbaIKm3xC0DFOjYEHDmvNbzHrI6aTdPhj0nczl3dmR
NekEIbJ6P/Qaka0hgo7bu69MvAXKnWJvwg4RI=
Received: by 10.231.148.18 with SMTP id n18mr206532ibv.7.1268468698064;
Sat, 13 Mar 2010 00:24:58 -0800 (PST)
Received: from [192.168.10.20] (s224.GtokyoFL6.vectant.ne.jp [222.228.90.224])
by mx.google.com with ESMTPS id 21sm1634355iwn.3.2010.03.13.00.24.55
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sat, 13 Mar 2010 00:24:56 -0800 (PST)
Message-Id: <24969D86-092A-455F-89EA-F3DCA3035A21@gmail.com>
From: Rui Paulo <rpaulo@gmail.com>
To: Hans Petter Selasky <hselasky@c2i.net>
In-Reply-To: <201003130836.41718.hselasky@c2i.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 13 Mar 2010 17:24:55 +0900
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
<7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
<201003130836.41718.hselasky@c2i.net>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Sat, 13 Mar 2010 13:55:47 +0000
Cc: Alexander Egorenkov <egorenar@googlemail.com>,
PseudoCylon <moonlightakkiy@yahoo.ca>,
freebsd-current@freebsd.org, Weongyo Jeong <weongyo@freebsd.org>
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 08:24:59 -0000
On 13 Mar 2010, at 16:36, Hans Petter Selasky wrote:
> On Saturday 13 March 2010 03:42:46 Rui Paulo wrote:
>> On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
>>> On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote:
>>>> Hello,
>>>>
>>>> Finally, I have fixed mysterious device lock out and run(4) works
>>>> fine
>>>> in HOSTAP mode. Up time is 80 hours and counting. I even filed tax
>>>> though it.
>>>>
>>>> The device supports up to 253 stations. I only tested with 2
>>>> station.
>>>> If you have resources, please hit it with bunch of STAs.
>>>>
>>>> As usual codes are posted at my git repository
>>>> git://dev.nasreddine.com/run.git
>>>> http://dev.nasreddine.com/gitweb/?p=run.git;a=summary
>>>> Please fetch 'hostap_rc' branch not 'master' this time.
>>>>
>>>> or freebsd forums
>>>> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e98051
>>>> 46e&t=7562
>>>
>>> Out of curiosity, what's the difference between run(4) and rt2870
>>> driver
>>> written by Alexander Egorenkov? And why there are two drivers?
>>
>> From what I understand, Alexander's driver supports 11n ann run(4)
>> doesn't.
>
>
> Will this two drivers be merged then?
I hope so.
--
Rui Paulo
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 09:18:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 35944106566C;
Sat, 13 Mar 2010 09:18:32 +0000 (UTC)
(envelope-from egorenar@googlemail.com)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com
[209.85.219.228])
by mx1.freebsd.org (Postfix) with ESMTP id 91B968FC0A;
Sat, 13 Mar 2010 09:18:31 +0000 (UTC)
Received: by ewy28 with SMTP id 28so324326ewy.13
for <multiple recipients>; Sat, 13 Mar 2010 01:18:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=9duQR0Vf/myJIVdSNjEyM08KtS2m2xSPL1wiQ4xK0Y4=;
b=kVAoNYPzYAuqNCW8SVsPf4CIj8KW0uwQQYYA58PwAH/WMkduKgKGyXxzYHYqEUN9Bi
PsmB300mkfPCAkZvshkJ6ZyBDULvglkr1kW6HsaMaLSIGrIHXjl4e4IvR0JNktP0agW6
i6+HV06zveSVShAy6JInUu2K5cPl/g4Eue7jw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=pAPVKwmc8MaqutFo687kG04b6zdGr7ek5doeR2V3ll7FEPfJ4He618Q9QqWGowzDPb
Sfe+TG7F6RVIIZXpEWOjToCPMrLDfqquoflc8/J6BjfmRm3xaCzetmSwymt2lHPj/2k7
VCkgFvj4f+1kx+3FctTHc9A1VUlajCkU+AS2g=
MIME-Version: 1.0
Received: by 10.213.1.19 with SMTP id 19mr3549551ebd.21.1268470106540; Sat, 13
Mar 2010 00:48:26 -0800 (PST)
In-Reply-To: <24969D86-092A-455F-89EA-F3DCA3035A21@gmail.com>
References: <16641.96608.qm@web51806.mail.re2.yahoo.com>
<20100313001842.GB1295@weongyo>
<7FB39650-34E0-4375-B225-34D2E559CA81@gmail.com>
<201003130836.41718.hselasky@c2i.net>
<24969D86-092A-455F-89EA-F3DCA3035A21@gmail.com>
Date: Sat, 13 Mar 2010 09:48:26 +0100
Message-ID: <2d3b7e441003130048n6acb7a9bw1b1733345d75667f@mail.gmail.com>
From: Alexander Egorenkov <egorenar@googlemail.com>
To: Rui Paulo <rpaulo@gmail.com>
X-Mailman-Approved-At: Sat, 13 Mar 2010 13:56:05 +0000
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: PseudoCylon <moonlightakkiy@yahoo.ca>, freebsd-current@freebsd.org,
Weongyo Jeong <weongyo@freebsd.org>, Hans Petter Selasky <hselasky@c2i.net>
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 09:18:32 -0000
Later i also plan to add multi BSS support so upto 8 HOSTAPs, several STAs
and WDSs will be possible with rt2860 and rt2870 on FreeBSD 8.
On Sat, Mar 13, 2010 at 9:24 AM, Rui Paulo <rpaulo@gmail.com> wrote:
> On 13 Mar 2010, at 16:36, Hans Petter Selasky wrote:
>
> On Saturday 13 March 2010 03:42:46 Rui Paulo wrote:
>>
>>> On 13 Mar 2010, at 09:18, Weongyo Jeong wrote:
>>>
>>>> On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Finally, I have fixed mysterious device lock out and run(4) works
>>>>> fine
>>>>> in HOSTAP mode. Up time is 80 hours and counting. I even filed tax
>>>>> though it.
>>>>>
>>>>> The device supports up to 253 stations. I only tested with 2 station.
>>>>> If you have resources, please hit it with bunch of STAs.
>>>>>
>>>>> As usual codes are posted at my git repository
>>>>> git://dev.nasreddine.com/run.git
>>>>> http://dev.nasreddine.com/gitweb/?p=run.git;a=summary
>>>>> Please fetch 'hostap_rc' branch not 'master' this time.
>>>>>
>>>>> or freebsd forums
>>>>>
>>>>> http://forums.freebsd.org/showthread.php?s=1d3b01fbed80c61ff508e12e98051
>>>>> 46e&t=7562
>>>>>
>>>>
>>>> Out of curiosity, what's the difference between run(4) and rt2870
>>>> driver
>>>> written by Alexander Egorenkov? And why there are two drivers?
>>>>
>>>
>>> From what I understand, Alexander's driver supports 11n ann run(4)
>>> doesn't.
>>>
>>
>>
>> Will this two drivers be merged then?
>>
>
>
> I hope so.
>
> --
> Rui Paulo
>
>
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 15:57:35 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EBF43106566C;
Sat, 13 Mar 2010 15:57:34 +0000 (UTC)
(envelope-from svein-listmail@stillbilde.net)
Received: from mail.stillbilde.net (unknown
[IPv6:2002:51af:3dc3:0:20c:29ff:fece:79f3])
by mx1.freebsd.org (Postfix) with ESMTP id 629108FC12;
Sat, 13 Mar 2010 15:57:34 +0000 (UTC)
Received: from [IPv6:2002:51af:3dc3:0:79cc:a126:7e59:782f] (unknown
[IPv6:2002:51af:3dc3:0:79cc:a126:7e59:782f])
(Authenticated sender: svein-listmail)
by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id EE59F23;
Sat, 13 Mar 2010 16:57:53 +0100 (CET)
Message-ID: <4B9BB600.5080200@stillbilde.net>
Date: Sat, 13 Mar 2010 16:57:52 +0100
From: "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: freebsd-questions@freebsd.org,
"Stable, FreeBSD" <freebsd-stable@freebsd.org>, current@FreeBSD.org
References: <4B9A4D9D.6040805@stillbilde.net>
In-Reply-To: <4B9A4D9D.6040805@stillbilde.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc:
Subject: Re: Amanda, FreeBSD8, amtype, hairpulling, etc.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 15:57:35 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12.03.2010 15:20, Svein Skogen wrote:
> I'm having trouble getting Amanda (2.6.1p2 from ports) to play nicely
> with my hardware.
>
> Devices are:
> <HP Ultrium 3-SCSI Q25W> at scbus0 target 1 lun 0 (sa0,pass0)
> <HP 1x8 G2 AUTOLDR 2.80> at scbus0 target 1 lun 1 (pass1,ch0)
> connected via:
> mpt0: <LSILogic SAS/SATA Adapter> port 0x9000-0x90ff mem
> 0xfe4fc000-0xfe4fffff,0xfe4e0000-0xfe4effff irq 16 at device 0.0 on pci2
> mpt0: [ITHREAD]
> mpt0: MPI Version=1.5.20.0
>
> os and number in question is:
> FreeBSD storage.stillbilde.net 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Mar
> 9 07:01:59 UTC 2010
> svein@storage.stillbilde.net:/usr/obj/usr/src/sys/GENERIC amd64
>
> Tapes are regular LTO-3 (HP C7973A).
>
> amtapetype simply hangs (after writing 3-4 tps for 5 seconds, then
> simple silence both on sa0 and console)
>
> Has anybody run into this problem with FreeBSD8+mpt+autoloader?
>
> //Svein
>
I'm finally starting to make sense of what I'm seeing (hence the
crossposting)
Seems I've stumbled onto some strange incompatibility between my SAS
controller (LSI 3801E), Tape-library, and FreeBSD+Solaris.
The behavior I'm seeing is consistent with this solaris bug:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6894775
but luckily (?) for me, my disks are on an MFI controller. I'm seeing
the exact same behavior in both FreeBSD and OpenSolaris 133 and 134.
Linux and Windows installs on the box (this box is currently being set
up, so I'm rather liberated from reinstall-concerns) seems unaffected,
atleast the HP Software doesn't fail the way
tar/dump/dd/amanda/bacula/whatnot does at random intervals.
The errors only occur when the device I'm reading/writing from is 100%
laoded (reading or writing 56mb/sec + compression), which when fed from
a raid capable of more than 6 times that is quite likely to happen
during backups.
The Solaris bug seems to be around MSI handling, but there are several
reports "over there" about this error occuring even with MSI disabled.
Right now I'm dumbstruck about this, and might install Linux "just to
get backups up and running this year", because I'm too tired of this
entire process, but I'd REALLY rather run FreeBSD or OpenSolaris. This
is based on a personal preference and nothing else, but if anybody has
some blinding insights on how to get this working, I'm open for suggestions.
//Svein
- --
- --------+-------------------+-------------------------------
/"\ |Svein Skogen | svein@d80.iso100.no
\ / |Solberg Østli 9 | PGP Key: 0xE5E76831
X |2020 Skedsmokorset | svein@jernhuset.no
/ \ |Norway | PGP Key: 0xCE96CE13
| | svein@stillbilde.net
ascii | | PGP Key: 0x58CD33B6
ribbon |System Admin | svein-listmail@stillbilde.net
Campaign|stillbilde.net | PGP Key: 0x22D494A4
+-------------------+-------------------------------
|msn messenger: | Mobile Phone: +47 907 03 575
|svein@jernhuset.no | RIPE handle: SS16503-RIPE
- --------+-------------------+-------------------------------
If you really are in a hurry, mail me at
svein-mobile@stillbilde.net
This mailbox goes directly to my cellphone and is checked
even when I'm not in front of my computer.
- ------------------------------------------------------------
Picture Gallery:
https://gallery.stillbilde.net/v/svein/
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkubtf8ACgkQODUnwSLUlKTfGgCgndwhQdAjFjlUp2jCh5POr0jp
0rYAoKUsR2AjzlBCM/eqMfUjGfKtWXof
=2lnD
-----END PGP SIGNATURE-----
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 17:06:21 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B8F23106566C
for <current@freebsd.org>; Sat, 13 Mar 2010 17:06:21 +0000 (UTC)
(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
[41.161.16.135])
by mx1.freebsd.org (Postfix) with ESMTP id D93888FC14
for <current@freebsd.org>; Sat, 13 Mar 2010 17:06:20 +0000 (UTC)
Received: from [41.154.88.19] (helo=clue.co.za)
by inbound01.jnb1.gp-online.net with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
(envelope-from <ianf@clue.co.za>)
id 1NqUn3-00033C-EK; Sat, 13 Mar 2010 19:06:17 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
(envelope-from <ianf@clue.co.za>)
id 1NqUmz-000BCm-Fn; Sat, 13 Mar 2010 19:06:13 +0200
To: "David Christensen" <davidch@broadcom.com>
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933B0A21DB97@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <5D267A3F22FD854F8F48B3D2B52381933B0A21DB97@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310230220.GI10657@michelle.cdnetworks.com>
<E1Nnc4d-0003mB-6e@clue.co.za> <E1Nne0Q-0003uZ-OR@clue.co.za>
<E1Noulp-0007Rc-Ro@clue.co.za>
<20100309212139.GO1311@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EED69@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100309214012.GQ1311@michelle.cdnetworks.com>
<E1NpHr0-000HWT-It@clue.co.za>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF16F@IRVEXCHCCR01.corp.ad.broadcom.com>
<20100310195206.GB10657@michelle.cdnetworks.com>
<5D267A3F22FD854F8F48B3D2B52381933AF90EF25A@IRVEXCHCCR01.corp.ad.broadcom.com>
<E1NpcT6-000IuH-FO@clue.co.za>
X-Attribution: BOFH
Date: Sat, 13 Mar 2010 19:06:13 +0200
Message-Id: <E1NqUmz-000BCm-Fn@clue.co.za>
Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>,
"current@freebsd.org" <current@freebsd.org>
Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 17:06:21 -0000
"David Christensen" wrote:
> > Pyun YongHyeon wrote:
> > > On Wed, Mar 10, 2010 at 02:45:47PM -0800, David Christensen wrote:
> > > > The bce(4) hardware supports a linked list of pages for RX buffer=20
> > > > descriptors. The stock build supports 2 pages (RX_PAGES) with a=20
> > > > total of 511 BD's per page. The hardware can support a=20
> > maximum of=20
> > > > 64K BD's but that would be an unnecessarily large amount of mbufs=20
> > > > for an infrequent problem.
> >=20
> > I think that depends on how you define infrequent. Our use=20
> > case is a largish core router. It's highly likely that we'll=20
> > see this again and again in various packet storms on our network.
> >=20
>
> Are the packet storms always always from the same host or do they come
> from multiple hosts? The hardware supports RSS which can spread the
> network load across multiple receive queues and multiple CPU cores, but
> only when the traffic is spread across several hosts. (The current
> bce(4) driver doesn't include support for RSS.) If a storm of
> small frames comes from a single host then almost all adapters will be
> challenged to handle the flow.
In this case the storm only involved 2 hosts. While it's an
exceptional circumstance it isn't unusual in our environment (core
router in a datacenter). Fortuately we controlled both machines
in this instance. Perhaps if the load is spread across more CPUs,
then perhaps only those flows unlucky to hash to the CPU handling
the storm will be degraded. That is a marginally better situation
than all flows being degraded. From the sounds of it RSS isn't the
cure for this particular situation, but may improve performance in
general.
It does sound like reworking the buffer will solve the problem.
Perhaps having a 2 recieve rings so that once one ring is available
for processing, the other ready filled and clear ring can be used
for recieving frames.
Ian
--
Ian Freislich
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 18:05:21 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 23ED1106566B
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:05:21 +0000 (UTC)
(envelope-from sergey.dyatko@gmail.com)
Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com
[209.85.220.222])
by mx1.freebsd.org (Postfix) with ESMTP id ABCE68FC16
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:05:20 +0000 (UTC)
Received: by fxm22 with SMTP id 22so2044458fxm.14
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 10:05:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:to:subject
:message-id:x-mailer:mime-version:content-type
:content-transfer-encoding;
bh=+Bj+e812AdUJP17HKJIwG4dqBmuycKvYhi5ic5p3LEw=;
b=nhXNQ0a5LPKAVOGb4Od3bDGVYCGsXPtGxw9K+EH12rNM5Ii2qRSgGUQ8YjCm5N9d1e
+M5NJxymLtTDh23ekkLdd/RrwrwqLuaXfLM0QbQ/dcxaZ+6pqxb/0A8uroacL31YEN3O
rTb0Do/tXFIcw+I/bWydCHmOBDwfXS1BSW1HA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:to:subject:message-id:x-mailer:mime-version:content-type
:content-transfer-encoding;
b=aAJGETsWV2dVeO0TDijz8jHwHBtbSZ6BrSOI98zKZNkz+snGxm3m0aeEA6WePNYmkC
SHt6VUeJaosoHK+RTUZs7nOh0Fe+zoy8nU2QkWv6/v8rXVaKKLa5eQ2hLInOYFvwhMxy
JoWH8cJ5p3GMul2Avd2dCM6fZrClWr2hpe7dU=
Received: by 10.87.73.15 with SMTP id a15mr3727155fgl.50.1268501722670;
Sat, 13 Mar 2010 09:35:22 -0800 (PST)
Received: from notebook ([178.125.69.233])
by mx.google.com with ESMTPS id 16sm1885536fxm.3.2010.03.13.09.35.21
(version=SSLv3 cipher=RC4-MD5); Sat, 13 Mar 2010 09:35:22 -0800 (PST)
Date: Sat, 13 Mar 2010 19:35:49 +0200
From: "Sergey V. Dyatko" <sergey.dyatko@gmail.com>
To: freebsd-current@freebsd.org
Message-ID: <20100313193549.52d3c8a2@notebook>
X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; i386-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: buildkernel broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 18:05:21 -0000
Hi,
I'm trying to build kernel (update from 204272 to 205122) and
got following error:
===> drm/i915 (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -DHAVE_KERNEL_OPTION_HEADERS
-include /usr/obj/usr/src/sys/b450/opt_global.h -I. -I@
-I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
--param large-function-growth=1000 -fno-common -g
-fno-omit-frame-pointer -I/usr/obj/usr/src/sys/b450 -mcmodel=kernel
-mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
-mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions
-c /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:
In function
'i915_dma_cleanup': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
error: 'DEV' undeclared (first use in this
function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
error: (Each undeclared identifier is reported only
once /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
error: for each function it appears
in.) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In
function
'i915_set_status_page': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:807:
error: 'DEV' undeclared (first use in this
function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In
function
'i915_driver_load': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:847:
error: 'DEV' undeclared (first use in this function) *** Error code 1
Stop in /usr/src/sys/modules/drm/i915.
*** Error code 1
Stop in /usr/src/sys/modules/drm.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/obj/usr/src/sys/b450.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
--
wbr, tiger
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 18:16:01 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0FFA9106566C
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:16:01 +0000 (UTC)
(envelope-from rnoland@FreeBSD.org)
Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195])
by mx1.freebsd.org (Postfix) with ESMTP id B30068FC20
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:16:00 +0000 (UTC)
Received: from [192.168.1.4] (adsl-154-185-142.bna.bellsouth.net
[68.154.185.142]) (authenticated bits=0)
by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id o2DIFwwi066737
(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
Sat, 13 Mar 2010 13:15:58 -0500 (EST)
(envelope-from rnoland@FreeBSD.org)
From: Robert Noland <rnoland@FreeBSD.org>
To: "Sergey V. Dyatko" <sergey.dyatko@gmail.com>
In-Reply-To: <20100313193549.52d3c8a2@notebook>
References: <20100313193549.52d3c8a2@notebook>
Content-Type: text/plain
Organization: FreeBSD
Date: Sat, 13 Mar 2010 12:15:52 -0600
Message-Id: <1268504152.2608.311.camel@balrog.2hip.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=0.6 required=5.0 tests=AWL, BAYES_00,
FH_DATE_PAST_20XX,
RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no
version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net
Cc: freebsd-current@freebsd.org
Subject: Re: buildkernel broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 18:16:01 -0000
On Sat, 2010-03-13 at 19:35 +0200, Sergey V. Dyatko wrote:
> Hi,
> I'm trying to build kernel (update from 204272 to 205122) and
> got following error:
>
> ===> drm/i915 (all)
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
> -nostdinc -DHAVE_KERNEL_OPTION_HEADERS
> -include /usr/obj/usr/src/sys/b450/opt_global.h -I. -I@
> -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
> --param large-function-growth=1000 -fno-common -g
> -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/b450 -mcmodel=kernel
> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
> -Wno-pointer-sign -fformat-extensions
> -c /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:
> In function
> 'i915_dma_cleanup': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
> error: 'DEV' undeclared (first use in this
Typo, pointyhat to me... Fixed in rev 205126.
robert.
> function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
> error: (Each undeclared identifier is reported only
> once /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159:
> error: for each function it appears
> in.) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In
> function
> 'i915_set_status_page': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:807:
> error: 'DEV' undeclared (first use in this
> function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In
> function
> 'i915_driver_load': /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:847:
> error: 'DEV' undeclared (first use in this function) *** Error code 1
>
> Stop in /usr/src/sys/modules/drm/i915.
> *** Error code 1
>
> Stop in /usr/src/sys/modules/drm.
> *** Error code 1
>
> Stop in /usr/src/sys/modules.
> *** Error code 1
>
> Stop in /usr/obj/usr/src/sys/b450.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
> --
> wbr, tiger
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
--
Robert Noland <rnoland@FreeBSD.org>
FreeBSD
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 18:31:26 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5B1E0106564A
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:31:26 +0000 (UTC)
(envelope-from ken@mthelicon.com)
Received: from hercules.mthelicon.com (hercules.mthelicon.com
[IPv6:2001:49f0:2023::2])
by mx1.freebsd.org (Postfix) with ESMTP id 27FA98FC19
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:31:25 +0000 (UTC)
Received: from feathers.peganest.com (feathers.peganest.com [78.33.110.3])
(authenticated bits=0)
by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id o2DIVJha038430
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 18:31:20 GMT
(envelope-from ken@mthelicon.com)
From: Pegasus Mc Cleaft <ken@mthelicon.com>
Organization: Feathers
To: freebsd-current@freebsd.org
Date: Sat, 13 Mar 2010 18:31:19 +0000
User-Agent: KMail/1.12.4 (FreeBSD/9.0-CURRENT; KDE/4.3.5; amd64; ; )
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201003131831.19383.ken@mthelicon.com>
X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_50,FH_DATE_PAST_20XX
autolearn=no version=3.2.5
X-Spam-Level: ***
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
hercules.mthelicon.com
Subject: build failures after stdlib update
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 18:31:26 -0000
Hello Current,
I am wondering if someone could help me please.
I built the 9.0-current kernel and world while there was still a bug in
the updated strlen(). Unfortunately this rendered the machine unbootable as
gptzfsloader crashed and would just echo an endless stream of spaces across
the screen. After booting off another drive and reverting the gptzfsboot to
the .old version, I was able to being the machine back to life, but
applications were dieing left and right (Signal 10). I used dgb to find the
offending library /lib/libc.so.7 and had a copy of the library from 3 days
ago. After reverting that library, I was able to start all my applications OK
and the machine is working..
However.....
I am not able to build the latest world (I havent tried kernel yet).
Whenever I start gengtype dies with a signal 10. I have tried to use dgb to
examine the core file, but it gives me nonsense answers so I am not able to
locate what library it might be trying to use. I have also tried to blow away
the /usr/src and /usr/obj directories and recreate them from svn just incase
there was something hanging on from the previous build.
Can anyone give me advice on how to track this problem down or fix it? I
suspect I still have a lib that still trying to use the broken libc.so.7 or
something else depended on it, but I am not sure..
Thanks,
Peg
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 20:45:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EC48C1065678
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 20:45:15 +0000 (UTC)
(envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
by mx1.freebsd.org (Postfix) with ESMTP id AA1D88FC2F
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 20:45:15 +0000 (UTC)
Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1])
by elsa.codelab.cz (Postfix) with ESMTP id 4004A19E02A;
Sat, 13 Mar 2010 21:45:14 +0100 (CET)
Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by elsa.codelab.cz (Postfix) with ESMTPSA id DCF7B19E023;
Sat, 13 Mar 2010 21:45:11 +0100 (CET)
Message-ID: <4B9BF957.4060507@quip.cz>
Date: Sat, 13 Mar 2010 21:45:11 +0100
From: Miroslav Lachman <000.fbsd@quip.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3
MIME-Version: 1.0
To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no>
References: <20100308102918.GA5485@localhost>
<4B94DDC8.5080008@quip.cz> <20100308115052.GA31896@office.redwerk.com>
<4B94FBA6.5090107@quip.cz> <861vfq995i.fsf@ds4.des.no>
In-Reply-To: <861vfq995i.fsf@ds4.des.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 20:45:16 -0000
Dag-Erling Smørgrav wrote:
> Miroslav Lachman<000.fbsd@quip.cz> writes:
>> Yes, rewriting by dd or any other way works for reallocating or
>> clearing pending sectors counter, but in server environment
>
> In a server environment, you'd be a fool not to have some sort of
> redundancy set up.
I am using gmirror on low-end servers, so rewriting some sectors on one
disk drive is useless and in this case I prefer resync of the whole
gmirror (but it is log run - about 10 hours on busy server)
>> I need to know the affected file, as it can be for example database
>> file and then it is a big problem! Rewriting the sector inside InnoDB
>> ib_data file can cause DB crash, data loss etc.
>
> How is that different from *not* rewriting the sector? If there's a bad
> sector somewhere in your data, your database is still going to crash.
It is not about "different", it is about "I need to know the affected
file" to know what actions should be taken.
If it is some logfile, I can delete it and then rewrite the sector. If
it is some "normal" unchanged file, I can restore it from backup, if it
is database file, I must take some special action. For example, stop DB
engine, try to repair/fix the DB file, dump & restore etc.
So the first step is to find "what file is affected", then take some
action AND rewrite the sector by dd to reallocate the sector. (or
replace the drive)
So... can somebody with enough knowledge write some docs / script how to
find the affected file based on LBA read error from messages / SMART log?
Miroslav Lachman
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 20:50:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5517C106566C
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 20:50:15 +0000 (UTC)
(envelope-from yanefbsd@gmail.com)
Received: from mail-pz0-f196.google.com (mail-pz0-f196.google.com
[209.85.222.196])
by mx1.freebsd.org (Postfix) with ESMTP id 2A4DE8FC12
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 20:50:14 +0000 (UTC)
Received: by pzk34 with SMTP id 34so1324132pzk.3
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 12:50:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=1t8sj1pOe1aPIhxwAU+5LQFB7VOxW5WVpOJ51SkpMs0=;
b=qFDbj6TIW0nf2CdnJ9H53pXRHmoecCequoJsin8oNnNJlvSPVY/DVkN3JV5T/zgu55
VIfRxe8IXYoI7ZHHTR9VsZo5Vy4778DyqbHuVUd+oXxM5QAj+I6cO9vpy5dvdMFNhQnf
VkuB1rdeHaOz6HCUG6LjmLsSffVheQL+FKjDE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=Q4wUPCQFh0fS11homo5hsfBdnpdT62LbXGimNZYBoq99ivEToiKYUgh4Ov2BFIw2dQ
34aPg37pLmWAEQXxycp5FX1PubpXgxzQdMxigsBrVNdvIerkOPCfVhv17w0w0StuhJB8
aV6bjYDQjSdVJxEM83DBGvqbBVC+DzidgWwL4=
MIME-Version: 1.0
Received: by 10.143.27.20 with SMTP id e20mr3875730wfj.256.1268513414618; Sat,
13 Mar 2010 12:50:14 -0800 (PST)
In-Reply-To: <201003131831.19383.ken@mthelicon.com>
References: <201003131831.19383.ken@mthelicon.com>
Date: Sat, 13 Mar 2010 12:50:14 -0800
Message-ID: <7d6fde3d1003131250n42af0221w7a94bfc22f79c76f@mail.gmail.com>
From: Garrett Cooper <yanefbsd@gmail.com>
To: Pegasus Mc Cleaft <ken@mthelicon.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org
Subject: Re: build failures after stdlib update
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 20:50:15 -0000
On Sat, Mar 13, 2010 at 10:31 AM, Pegasus Mc Cleaft <ken@mthelicon.com> wro=
te:
> Hello Current,
>
> =A0 =A0 =A0 =A0I am wondering if someone could help me please.
>
> =A0 =A0 =A0 =A0I built the 9.0-current kernel and world while there was s=
till a bug in
> the updated strlen(). Unfortunately this rendered the machine unbootable =
as
> gptzfsloader crashed and would just echo an endless stream of spaces acro=
ss
> the screen. After booting off another drive and reverting the gptzfsboot =
to
> the .old version, I was able to being the machine back to life, but
> applications were dieing left and right (Signal 10). I used dgb to find t=
he
> offending library /lib/libc.so.7 and had a copy of the library from 3 day=
s
> ago. After reverting that library, I was able to start all my application=
s OK
> and the machine is working..
>
> =A0 =A0 =A0 =A0However.....
>
> =A0 =A0 =A0 =A0I am not able to build the latest world (I havent tried ke=
rnel yet).
> Whenever I start =A0gengtype dies with a signal 10. =A0I have tried to us=
e dgb to
> examine the core file, but it gives me nonsense answers so I am not able =
to
> locate what library it might be trying to use. I have also tried to blow =
away
> the /usr/src and /usr/obj directories and recreate them from svn just inc=
ase
> there was something hanging on from the previous build.
>
> =A0 =A0 =A0 =A0Can anyone give me advice on how to track this problem dow=
n or fix it? I
> suspect I still have a lib that still trying to use the broken libc.so.7 =
or
> something else depended on it, but I am not sure..
Some of the items in this commit may be causing the bad juju
you're seeing on the screen:
http://svn.freebsd.org/changeset/base/205021
Please try reverting that and see how things go.
Thanks!
-Garrett
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 21:13:21 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8C4DA106566C;
Sat, 13 Mar 2010 21:13:21 +0000 (UTC) (envelope-from ray@ddteam.net)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id BC9098FC24;
Sat, 13 Mar 2010 21:13:20 +0000 (UTC)
Received: by fxm1 with SMTP id 1so1631648fxm.13
for <multiple recipients>; Sat, 13 Mar 2010 13:13:17 -0800 (PST)
Received: by 10.223.5.211 with SMTP id 19mr3078110faw.63.1268514797448;
Sat, 13 Mar 2010 13:13:17 -0800 (PST)
Received: from localhost (153-123-133-95.pool.ukrtel.net [95.133.123.153])
by mx.google.com with ESMTPS id 15sm2007532fxm.12.2010.03.13.13.13.15
(version=SSLv3 cipher=RC4-MD5); Sat, 13 Mar 2010 13:13:16 -0800 (PST)
Date: Sat, 13 Mar 2010 23:12:05 +0200
From: Alex RAY <ray@ddteam.net>
To: Weongyo Jeong <weongyo@freebsd.org>
Message-Id: <20100313231205.5e68a89a.ray@ddteam.net>
In-Reply-To: <20100312231333.GZ1295@weongyo>
References: <20091223035331.GA1293@weongyo>
<4b31cb29.9413f30a.5f4a.ffff8382@mx.google.com>
<20100226005115.GP14937@weongyo>
<20100227011535.ed3f2486.ray@ddteam.net>
<20100228095259.GB3536@weongyo>
<20100301103240.3a4aac8a.ray@dlink.ua>
<20100303082833.GB22865@weongyo>
<20100303111014.6564ea1e.ray@dlink.ua>
<20100312231333.GZ1295@weongyo>
Organization: DDTeam.net
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Alexandr Rybalko <ray@dlink.ua>, current@freebsd.org,
Weongyo Jeong <weongyo.jeong@gmail.com>
Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless
driver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 21:13:21 -0000
On Fri, 12 Mar 2010 15:13:34 -0800
Weongyo Jeong <weongyo.jeong@gmail.com> wrote:
>
> I thought that your opinion was right and if mem is
> 0xf4000000-0xf4003fff (16 Kb) I thought the device has 4 cores. However
> it looks this was wrong according to the below document:
>
> http://voodoowarez.com/bcm5365p.pdf
>
> Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that
> 16Kb, maybe 8 Kb in the old devices is core register region.
>
> "Accesses to the lower half of the core register region are translated
> into system backplane accesses using the PCIBAR0Window register"
> "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct
> access to the external SPROM"
>
> If we just access memory using offset + core and bus_space_read_x
> interfaces it would actually not access core register region.
>
> So without solving this problem it looks it could not remove coreswitch
> routines.
>
> regards,
> Weongyo Jeong
>
Hi,
this document about SoC BCM5365P, not about PCI device with PCI to SSB bridge.
I know in SoC`s like BSM5365 (I test it in BCM5354 and BCM5836) core switching is not required.
BCM5354 - http://lists.freebsd.org/pipermail/freebsd-mips/2009-June/000421.html
BCM5836 - http://lists.freebsd.org/pipermail/freebsd-mips/2010-February/000635.html
With PCI device, when device report memory window 0xf4000000-0xf4003fff, why we can`t use full window?
May be You can test your code without core switching?
--
Alex RAY <ray@ddteam.net>
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 21:24:51 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 50A25106564A
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 21:24:51 +0000 (UTC)
(envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
by mx1.freebsd.org (Postfix) with ESMTP id 0CE8C8FC14
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 21:24:50 +0000 (UTC)
Received: from ds4.des.no (des.no [84.49.246.2])
by smtp.des.no (Postfix) with ESMTP id D1EF61FFC22;
Sat, 13 Mar 2010 21:24:49 +0000 (UTC)
Received: by ds4.des.no (Postfix, from userid 1001)
id 8F256844A7; Sat, 13 Mar 2010 22:24:49 +0100 (CET)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Miroslav Lachman <000.fbsd@quip.cz>
References: <20100308102918.GA5485@localhost> <4B94DDC8.5080008@quip.cz>
<20100308115052.GA31896@office.redwerk.com> <4B94FBA6.5090107@quip.cz>
<861vfq995i.fsf@ds4.des.no> <4B9BF957.4060507@quip.cz>
Date: Sat, 13 Mar 2010 22:24:49 +0100
In-Reply-To: <4B9BF957.4060507@quip.cz> (Miroslav Lachman's message of "Sat,
13 Mar 2010 21:45:11 +0100")
Message-ID: <86eijn3of2.fsf@ds4.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org
Subject: Re: A tool for remapping bad sectors in CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 21:24:51 -0000
Miroslav Lachman <000.fbsd@quip.cz> writes:
> So... can somebody with enough knowledge write some docs / script how
> to find the affected file based on LBA read error from messages /
> SMART log?
ZFS will tell you straight away, but I guess if you used ZFS, you
wouldn't be asking :)
For FFS, you can unmount the file system (boot from a CD or memory stick
or whatever if that file system is / or /usr), run fsdb on the failing
disk, use findblk to look up the inode number for the file that contains
the bad sector. Note that you have to convert the LBA to an offset
relative to the start of the partition.
Unfortunately, you can't easily go from inode to file name; you have to
mount the file system and use something like find -inum.
DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no
From owner-freebsd-current@FreeBSD.ORG Sat Mar 13 23:57:00 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4826A106566B
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 23:57:00 +0000 (UTC)
(envelope-from giovanni.trematerra@gmail.com)
Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com
[209.85.220.209])
by mx1.freebsd.org (Postfix) with ESMTP id BFABF8FC15
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 23:56:59 +0000 (UTC)
Received: by fxm1 with SMTP id 1so1686266fxm.13
for <freebsd-current@freebsd.org>; Sat, 13 Mar 2010 15:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type;
bh=VhUxpx5vwQ5l6Av4UWbSmB6MawLMqogXgxPKixlT1xk=;
b=aipYjv7Wgf48v6n3DzOxh2hkQRFa+z3lziEbB9HQtaEeHZkOBQh8lB2FnnZBTwIoV8
umzheYsK6j7AIS2y5G+EJ0xSCoMcZI0gZ6BVgJKCtPY4LoHOeYZOkt5N8DMtm2Gw4GjG
M7hSTYbFFdFfPTww0mXm/HfoZmoQbriAHuKAM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
b=d77dFyyUyFJurq1/VDX2oaeIEq5ufHCIghWveHZd5Nih9G0hscDWomEqVFXLE1axLx
LG+218SgfxencWPj4uK7ZwUCq7Opoi8B7tZKm9uNDOg/k12mRRxMIgHsok2YoZvejaFt
xmefhgJlQ+5silcmIpq8fGaI2QZzluB8NkLoQ=
MIME-Version: 1.0
Received: by 10.223.7.90 with SMTP id c26mr3171622fac.19.1268524618446; Sat,
13 Mar 2010 15:56:58 -0800 (PST)
In-Reply-To: <7d6fde3d1003121933s4ba7b57fw6542628c16edf723@mail.gmail.com>
References: <7d6fde3d1003070207q621e69ado2cb64e431feacd76@mail.gmail.com>
<7d6fde3d1003070224k3626a9b5y98c11a43eef1bed4@mail.gmail.com>
<4e6cba831003101356i534341ffr2961b983854ab788@mail.gmail.com>
<7dc40bd01003101407m605e41ey2d8ace0049cf5e61@mail.gmail.com>
<7d6fde3d1003102158o7834ca67lce3eca23aa723fd1@mail.gmail.com>
<7d6fde3d1003121933s4ba7b57fw6542628c16edf723@mail.gmail.com>
Date: Sun, 14 Mar 2010 00:56:58 +0100
Message-ID: <4e6cba831003131556t2cb787e0xc9e2d649320d6e59@mail.gmail.com>
From: Giovanni Trematerra <giovanni.trematerra@gmail.com>
To: Garrett Cooper <yanefbsd@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tom Couch <tom.couch.storage@gmail.com>,
FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Removing USB keyboard after filesystems synced causes panic
with destroyed mutex twa(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2010 23:57:00 -0000
On Sat, Mar 13, 2010 at 4:33 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 9:58 PM, Garrett Cooper <yanefbsd@gmail.c
>>>
>
> Apart from the typo above (s/ctrl/ctlr/), things work appropriately
Oopss I'm sorry.
> now at reboot. The only problem is that bootup is really wonky now,
> because the RAID had a LOT of issues attaching to cam(4) (failed in
> 2/3 cold boot attempts); an additional branch condition may need to be
> added to the above if-statement if this change didn't take that into
> account. However, if the old behavior was incorrect and the new
> behavior is correct, s.t. the RAID controller demonstrating bus
> detection timeout issue that is occurring with a lot of USB devices
> and some RAID controllers today, this could be extremely problematic.
>
if you don't mind could you try this patch? Less dirty but always quick :)
Thank you for your time.
--
Gianni
diff -r 69c84861a227 sys/dev/twa/tw_cl.h
--- a/sys/dev/twa/tw_cl.h Thu Mar 11 16:18:11 2010 -0500
+++ b/sys/dev/twa/tw_cl.h Sat Mar 13 18:50:16 2010 -0500
@@ -66,6 +66,8 @@
#define TW_CLI_CTLR_STATE_RESET_PHASE1_IN_PROGRESS (1<<5)
/* G66 register write access bug needs to be worked around. */
#define TW_CLI_CTLR_STATE_G66_WORKAROUND_NEEDED (1<<6)
+/* Controller is shutting down. */
+#define TW_CLI_CTLR_STATE_SHUTDOWN_IN_PROGRESS (1<<7)
/* Possible values of ctlr->ioctl_lock.lock. */
#define TW_CLI_LOCK_FREE 0x0 /* lock is free */
diff -r 69c84861a227 sys/dev/twa/tw_cl_init.c
--- a/sys/dev/twa/tw_cl_init.c Thu Mar 11 16:18:11 2010 -0500
+++ b/sys/dev/twa/tw_cl_init.c Sat Mar 13 18:50:16 2010 -0500
@@ -598,6 +598,7 @@ tw_cl_shutdown_ctlr(struct tw_cl_ctlr_ha
* and notify the controller that we are going down.
*/
ctlr->state &= ~TW_CLI_CTLR_STATE_ACTIVE;
+ ctlr->state |= TW_CLI_CTLR_STATE_SHUTDOWN_IN_PROGRESS;
tw_cli_disable_interrupts(ctlr);
diff -r 69c84861a227 sys/dev/twa/tw_cl_intr.c
--- a/sys/dev/twa/tw_cl_intr.c Thu Mar 11 16:18:11 2010 -0500
+++ b/sys/dev/twa/tw_cl_intr.c Sat Mar 13 18:50:16 2010 -0500
@@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle
if (ctlr == NULL)
goto out;
- /* If we get an interrupt while resetting, it is a shared
- one for another device, so just bail */
- if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS)
+ /*
+ * If we get an interrupt while resetting or shutting down,
+ * it is a shared one for another device, so just bail
+ */
+ if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS ||
+ ctlr->state & TW_CLI_CTLR_STATE_SHUTDOWN_IN_PROGRESS)
goto out;
/*