From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 15:05:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC4FD1065684; Sun, 22 Jun 2008 15:05:11 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id A34A08FC0A; Sun, 22 Jun 2008 15:05:11 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (15.10.87-79.rev.gaoland.net [79.87.10.15]) by smtp.lamaiziere.net (Postfix) with ESMTP id F13BF11805AA; Sun, 22 Jun 2008 17:05:09 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 81CD54F9961; Sun, 22 Jun 2008 17:05:08 +0200 (CEST) Date: Sun, 22 Jun 2008 17:05:07 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> In-Reply-To: <20080606234135.46144207@baby-jane-lamaiziere-net.local> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 15:05:12 -0000 Le Fri, 6 Jun 2008 23:41:35 +0200, Patrick Lamaizière a écrit : Hello, > I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE > (via the NetBSD port). > " The glxsb driver supports the security block of the Geode LX > series processors. The Geode LX is a member of the AMD Geode family > of integrated x86 system chips. > > Driven by periodic checks for available data from the generator, > glxsb supplies entropy to the random(4) driver for common usage. > > glxsb also supports acceleration of AES-128-CBC operations for > crypto(4)." Well, I hope this is the final version. http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz I added a patch for FreeBSD 6 but i'am not able to test it. On 7-STABLE, I've tested with hundred openssl encryptions and some flood pings under ipsec in the background. Looks good for me. If someone can test and review it, it would be cool. Thanks, Regards. From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 16:10:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE39B106566B for ; Sun, 22 Jun 2008 16:10:00 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id A65368FC12 for ; Sun, 22 Jun 2008 16:10:00 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (15.10.87-79.rev.gaoland.net [79.87.10.15]) by smtp.lamaiziere.net (Postfix) with ESMTP id 52DF0118059D; Sun, 22 Jun 2008 18:09:59 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 608F24F9D6A; Sun, 22 Jun 2008 18:09:58 +0200 (CEST) Date: Sun, 22 Jun 2008 18:09:57 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: freebsd-stable@freebsd.org, JoaoBR Message-ID: <20080622180957.32335a53@baby-jane-lamaiziere-net.local> In-Reply-To: <200806200734.35713.joao@matik.com.br> References: <200806200734.35713.joao@matik.com.br> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: Subject: Re: problem with nVidia nForce CK804 SATA300 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 16:10:01 -0000 Le Fri, 20 Jun 2008 07:34:35 -0300, JoaoBR a écrit : > my amd64 crashs under heavy disk i/o as each night at 0300 daily > cron, also often after some minutes when compiling world. Also with > kde and after some flash videos (youtube) or large file copying > > I do not see this problem with other sata controllers or same > hardware and a scsi adapter and this sata disabled what makes me > believe it is related to this specific sata controller > > this sata controller is part of some ASUS (M2N SLI Deluxe) or Epox > AM2 MBs > > there is no panic at all, some seconds of hard freeze, on desktop > machine the mouse still moves some seconds and reset, no log either, > no crash dump, nothing > > I have no irq conflict, latest bios onboard, I also exchanged other > hw parts with no success. > > Any idea? I've seen this kind of thing on the nvidia chipset, could you try without apic ? I'm not sure if you can disable the apic on amd64. It is just an idea! From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 17:26:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E241A106564A for ; Sun, 22 Jun 2008 17:26:51 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6F6378FC15 for ; Sun, 22 Jun 2008 17:26:51 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KATKy-0003bv-Eh for freebsd-stable@freebsd.org; Sun, 22 Jun 2008 17:26:48 +0000 Received: from 78-0-84-134.adsl.net.t-com.hr ([78.0.84.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 17:26:48 +0000 Received: from ivoras by 78-0-84-134.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 17:26:48 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Sun, 22 Jun 2008 19:26:34 +0200 Lines: 138 Message-ID: References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig06F260B25A370E73FBED6C1E" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-84-134.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) In-Reply-To: <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> X-Enigmail-Version: 0.95.6 Sender: news Cc: freebsd-hackers@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 17:26:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig06F260B25A370E73FBED6C1E Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Patrick Lamaizi=C3=A8re wrote: > Le Fri, 6 Jun 2008 23:41:35 +0200, > Patrick Lamaizi=C3=A8re a =C3=A9crit : >=20 > Hello, >=20 >> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >> (via the NetBSD port). >> " The glxsb driver supports the security block of the Geode LX >> series processors. The Geode LX is a member of the AMD Geode family >> of integrated x86 system chips. >> >> Driven by periodic checks for available data from the generator, >> glxsb supplies entropy to the random(4) driver for common usage. >> >> glxsb also supports acceleration of AES-128-CBC operations for >> crypto(4)." >=20 > Well, I hope this is the final version. >=20 > http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz >=20 > I added a patch for FreeBSD 6 but i'am not able to test it. >=20 > On 7-STABLE, I've tested with hundred openssl encryptions and some floo= d > pings under ipsec in the background. Looks good for me. >=20 > If someone can test and review it, it would be cool. Hi, I'm having trouble testing it. My CPU is Geode LX: CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU)= Origin =3D "AuthenticAMD" Id =3D 0x5a2 Stepping =3D 2 Features=3D0x88a93d AMD Features=3D0xc0400000 When loading the driver, it attaches: Jun 22 18:49:41 ursaminor kernel: cryptosoft0: on=20 motherboard Jun 22 18:49:41 ursaminor kernel: glxsb0: mem 0xe0210000-0xe0213fff irq 11 at device 1.2 on pci0= I have the following klds loaded: 7 1 0xc3819000 4000 glxsb.ko 8 2 0xc389d000 23000 crypto.ko 9 2 0xc38c0000 a000 zlib.ko 10 1 0xc381e000 4000 cryptodev.ko Running openssl speed without cryptodev gives: > openssl speed aes-128-cbc To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 1005506 aes-128 cbc's in 0.98= s Doing aes-128 cbc for 3s on 64 size blocks: 262185 aes-128 cbc's in 0.98s= Doing aes-128 cbc for 3s on 256 size blocks: 66055 aes-128 cbc's in 0.97s= Doing aes-128 cbc for 3s on 1024 size blocks: 16680 aes-128 cbc's in 0.98= s Doing aes-128 cbc for 3s on 8192 size blocks: 2086 aes-128 cbc's in 0.98s= OpenSSL 0.9.8e 23 Feb 2007 built on: Tue Apr 15 19:40:37 CEST 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)=20 aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=3D128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192=20 bytes aes-128 cbc 16465.91k 17171.01k 17422.55k 17486.30k=20 17485.16k But running it with cryptodev gives: > openssl speed aes-128-cbc -engine cryptodev engine "cryptodev" set. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 1007404 aes-128 cbc's in 0.97= s Doing aes-128 cbc for 3s on 64 size blocks: 262177 aes-128 cbc's in 0.98s= Doing aes-128 cbc for 3s on 256 size blocks: 66500 aes-128 cbc's in 0.98s= Doing aes-128 cbc for 3s on 1024 size blocks: 16564 aes-128 cbc's in 0.97= s Doing aes-128 cbc for 3s on 8192 size blocks: 2087 aes-128 cbc's in 0.98s= OpenSSL 0.9.8e 23 Feb 2007 built on: Tue Apr 15 19:40:37 CEST 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)=20 aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=3D128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192=20 bytes aes-128 cbc 16545.20k 17173.92k 17417.71k 17476.48k=20 17485.82k The results are practically the same. This is on 7-STABLE from April. --------------enig06F260B25A370E73FBED6C1E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIXotLldnAQVacBcgRAhZ9AKCxMMmGoDsLTNDd0JNRUYhQkM807QCg1fAm N5r6ix4mTBMQjbJ+UEKh1vE= =esYz -----END PGP SIGNATURE----- --------------enig06F260B25A370E73FBED6C1E-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 17:40:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EFE4106564A for ; Sun, 22 Jun 2008 17:40:28 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 49ABE8FC1D for ; Sun, 22 Jun 2008 17:40:28 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KATY6-00043m-Sm for freebsd-stable@freebsd.org; Sun, 22 Jun 2008 17:40:22 +0000 Received: from 78-0-84-134.adsl.net.t-com.hr ([78.0.84.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 17:40:22 +0000 Received: from ivoras by 78-0-84-134.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 17:40:22 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Sun, 22 Jun 2008 19:40:04 +0200 Lines: 46 Message-ID: References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig35AA10426ED069159B986369" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-84-134.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) In-Reply-To: X-Enigmail-Version: 0.95.6 Sender: news Cc: freebsd-hackers@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 17:40:28 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig35AA10426ED069159B986369 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Ivan Voras wrote: > The results are practically the same. On the other hand: ursaminor:~/admin/glxsb> dd if=3D/dev/zero bs=3D4k count=3D100000 | opens= sl=20 enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij 100000+0 records in 100000+0 records out 409600000 bytes transferred in 77.653939 secs (5274684 bytes/sec) ursaminor:~/admin/glxsb> dd if=3D/dev/zero bs=3D4k count=3D100000 | opens= sl=20 enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij -engine cryptodev= engine "cryptodev" set. 100000+0 records in 100000+0 records out 409600000 bytes transferred in 21.486846 secs (19062826 bytes/sec) So I guess it works. Any idea why "openssl speed" doesn't show it? --------------enig35AA10426ED069159B986369 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIXo50ldnAQVacBcgRAhOBAKDeb3mHnco+e58NuPdAxoQoJFjYRACdET2r vB0XFJzo6fxxGCzPaQiHPis= =apUI -----END PGP SIGNATURE----- --------------enig35AA10426ED069159B986369-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 18:20:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E3E51065675; Sun, 22 Jun 2008 18:20:44 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id D5D738FC1C; Sun, 22 Jun 2008 18:20:43 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (15.10.87-79.rev.gaoland.net [79.87.10.15]) by smtp.lamaiziere.net (Postfix) with ESMTP id 96E3911805AA; Sun, 22 Jun 2008 20:20:42 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 2490E4FA29D; Sun, 22 Jun 2008 20:20:42 +0200 (CEST) Date: Sun, 22 Jun 2008 20:20:41 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: Ivan Voras Message-ID: <20080622202041.07f85145@baby-jane-lamaiziere-net.local> In-Reply-To: References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 18:20:44 -0000 Le Sun, 22 Jun 2008 19:40:04 +0200, Ivan Voras a écrit : > Ivan Voras wrote: > > > The results are practically the same. > > On the other hand: > > ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=100000 | openssl > enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij > 100000+0 records in > 100000+0 records out > 409600000 bytes transferred in 77.653939 secs (5274684 bytes/sec) > > ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=100000 | openssl > enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij -engine > cryptodev engine "cryptodev" set. > 100000+0 records in > 100000+0 records out > 409600000 bytes transferred in 21.486846 secs (19062826 bytes/sec) > > So I guess it works. Any idea why "openssl speed" doesn't show it? On FreeBSD 7, OpenSSL does not use the cryptodev engine by default. This is a known problem. See http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-06/msg00076.html openssl speed -evp aes-128-cbc -elapsed -engine cryptodev From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 18:29:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C9361065710 for ; Sun, 22 Jun 2008 18:29:15 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id 63DB58FC1D for ; Sun, 22 Jun 2008 18:29:15 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so8972471rvf.43 for ; Sun, 22 Jun 2008 11:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=yMH3BBnsPTK5mFz1KHUOmyrnxZ3Il3CUIom9askwbYo=; b=R5YiQxglZRW1senGFKkchvgA+xHclIHAj0E4+PPWLm1VMJQNIQU7Bi3vjQOEMdbm/M bgtt83w2tO1Q9+x9OrAUvVYGQeh9835s3FDqvVBNmqeC/RKpx6rdZC8ptJjZyRRod2mY 4bjNBWJenFmlTkOckqxdF8uTjhGVXzZB712yo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=NAOmTdyNFvpNh/diUlcL+AGAQriIlVlkJUrNJN/nZlnV5QLBDYWsAABShv4g1A75UT /JIP9C8cAHYzp4WHamPmRYR1nQSiapZ361+TLItqESxzXcZPIJ+XnZYd0pNkDHPuF/6R eZGMXsvxhjIwr2nTfZaKkxTy1nvJYVCtjk2wI= Received: by 10.141.128.19 with SMTP id f19mr11221382rvn.257.1214157715477; Sun, 22 Jun 2008 11:01:55 -0700 (PDT) Received: by 10.114.161.7 with HTTP; Sun, 22 Jun 2008 11:01:55 -0700 (PDT) Message-ID: <2e77fc10806221101q684baf47r9ee7208a676f59e@mail.gmail.com> Date: Sun, 22 Jun 2008 21:01:55 +0300 From: "Niki Denev" To: "=?ISO-8859-1?Q?Patrick_Lamaizi=E8re?=" In-Reply-To: <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 18:29:15 -0000 On Sun, Jun 22, 2008 at 6:05 PM, Patrick Lamaizi=E8re wrote: > Le Fri, 6 Jun 2008 23:41:35 +0200, > Patrick Lamaizi=E8re a =E9crit : > > Hello, > >> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >> (via the NetBSD port). >> " The glxsb driver supports the security block of the Geode LX >> series processors. The Geode LX is a member of the AMD Geode family >> of integrated x86 system chips. >> >> Driven by periodic checks for available data from the generator, >> glxsb supplies entropy to the random(4) driver for common usage. >> >> glxsb also supports acceleration of AES-128-CBC operations for >> crypto(4)." > > Well, I hope this is the final version. > > http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz > > I added a patch for FreeBSD 6 but i'am not able to test it. > > On 7-STABLE, I've tested with hundred openssl encryptions and some flood > pings under ipsec in the background. Looks good for me. > > If someone can test and review it, it would be cool. > > Thanks, Regards. It compiles on without a problem on 6.2 and loads on my Soekris Net5501-70 running pfSense (6.2-RELEASE-p11) glxsb0: mem 0xa0000000-0xa0003fff irq 10 at device 1.2 on pci0 Thanks!, Niki From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 19:48:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 591821065680 for ; Sun, 22 Jun 2008 19:48:30 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 07FAE8FC1A for ; Sun, 22 Jun 2008 19:48:29 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so811272pyb.10 for ; Sun, 22 Jun 2008 12:48:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=tLLTQi6YbpmG7JCw8gPe4pHK9gXotSUPDjnT6vRaOVw=; b=fAcUHjrmSGz+73Rx1/X8YvhDYByzbecRbrOnf9slLO4vG2UOSuSTLxEuw2txLCf5o+ tOJLTzusXPALMlc/pvXwKEb9R/AkI1xLcf9VqwBaMM8lngHULAd2m1QynM6D4ZOhWykx GjawlujR6NRYE/GfHYaAzD8vXvRIf7gmDj4so= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ah9l+wTswVEhCC9nXwLkSbh2haQGLVp9Z4QoSRJgjGaYJfwekBLg2ha4ckbkB2wIGo xOS55EqprjqIf/slq+PeLl7V9hHFucUMWQKvpJlh+3zAGyUyNoDRNVVtw1L4vwM+3NnO stcaxFQSrDqb+VIKg4sahlmGWI47FJ6rjmj7A= Received: by 10.141.20.7 with SMTP id x7mr11361074rvi.82.1214162402394; Sun, 22 Jun 2008 12:20:02 -0700 (PDT) Received: by 10.141.159.2 with HTTP; Sun, 22 Jun 2008 12:20:02 -0700 (PDT) Message-ID: <9bbcef730806221220u4f8a3f45q305a927efdf5e16f@mail.gmail.com> Date: Sun, 22 Jun 2008 21:20:02 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "=?UTF-8?Q?Patrick_Lamaizi=C3=A8re?=" In-Reply-To: <20080622202041.07f85145@baby-jane-lamaiziere-net.local> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> <20080622202041.07f85145@baby-jane-lamaiziere-net.local> X-Google-Sender-Auth: 79b95abe786fd131 Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 19:48:30 -0000 MjAwOC82LzIyIFBhdHJpY2sgTGFtYWl6acOocmUgPHBhdGZic2RAZGF2ZW51bGxlLm9yZz46Cgo+ IG9wZW5zc2wgc3BlZWQgLWV2cCBhZXMtMTI4LWNiYyAtZWxhcHNlZCAtZW5naW5lIGNyeXB0b2Rl dgoKSSBzZWUgdGhlICItZXZwIiBwYXJhbWV0ZXIgbWFrZXMgdGhlIGRpZmZlcmVuY2UgaW4gIm9w ZW5zc2wgc3BlZWQiOgoKPiBvcGVuc3NsIHNwZWVkIC1lbmdpbmUgY3J5cHRvZGV2IC1lbGFwc2Vk IC1ldnAgYWVzLTEyOC1jYmMgYWVzLTEyOC1jYmMKZW5naW5lICJjcnlwdG9kZXYiIHNldC4KWW91 IGhhdmUgY2hvc2VuIHRvIG1lYXN1cmUgZWxhcHNlZCB0aW1lIGluc3RlYWQgb2YgdXNlciBDUFUg dGltZS4KVG8gZ2V0IHRoZSBtb3N0IGFjY3VyYXRlIHJlc3VsdHMsIHRyeSB0byBydW4gdGhpcwpw cm9ncmFtIHdoZW4gdGhpcyBjb21wdXRlciBpcyBpZGxlLgpEb2luZyBhZXMtMTI4IGNiYyBmb3Ig M3Mgb24gMTYgc2l6ZSBibG9ja3M6IDEwMDU5OTIgYWVzLTEyOCBjYmMncyBpbiAzLjAwcwpEb2lu ZyBhZXMtMTI4IGNiYyBmb3IgM3Mgb24gNjQgc2l6ZSBibG9ja3M6IDI2MjI1NiBhZXMtMTI4IGNi YydzIGluIDMuMDFzCkRvaW5nIGFlcy0xMjggY2JjIGZvciAzcyBvbiAyNTYgc2l6ZSBibG9ja3M6 IDY2NDcwIGFlcy0xMjggY2JjJ3MgaW4gMy4wMXMKRG9pbmcgYWVzLTEyOCBjYmMgZm9yIDNzIG9u IDEwMjQgc2l6ZSBibG9ja3M6IDE2NTc1IGFlcy0xMjggY2JjJ3MgaW4gMy4wMXMKRG9pbmcgYWVz LTEyOCBjYmMgZm9yIDNzIG9uIDgxOTIgc2l6ZSBibG9ja3M6IDIwODcgYWVzLTEyOCBjYmMncyBp biAzLjAxcwpEb2luZyBhZXMtMTI4LWNiYyBmb3IgM3Mgb24gMTYgc2l6ZSBibG9ja3M6IDc0MTk1 IGFlcy0xMjgtY2JjJ3MgaW4gMy4wMXMKRG9pbmcgYWVzLTEyOC1jYmMgZm9yIDNzIG9uIDY0IHNp emUgYmxvY2tzOiA2OTIwOCBhZXMtMTI4LWNiYydzIGluIDMuMDFzCkRvaW5nIGFlcy0xMjgtY2Jj IGZvciAzcyBvbiAyNTYgc2l6ZSBibG9ja3M6IDY0MTU0IGFlcy0xMjgtY2JjJ3MgaW4gMy4wMXMK RG9pbmcgYWVzLTEyOC1jYmMgZm9yIDNzIG9uIDEwMjQgc2l6ZSBibG9ja3M6IDQ0MzY5IGFlcy0x MjgtY2JjJ3MgaW4gMy4wMXMKRG9pbmcgYWVzLTEyOC1jYmMgZm9yIDNzIG9uIDgxOTIgc2l6ZSBi bG9ja3M6IDk1MTIgYWVzLTEyOC1jYmMncyBpbiAzLjAxcwpPcGVuU1NMIDAuOS44ZSAyMyBGZWIg MjAwNwpidWlsdCBvbjogVHVlIEFwciAxNSAxOTo0MDozNyBDRVNUIDIwMDgKb3B0aW9uczpibig2 NCwzMikgbWQyKGludCkgcmM0KGlkeCxpbnQpIGRlcyhwdHIscmlzYzEsMTYsbG9uZykKYWVzKHBh cnRpYWwpIGJsb3dmaXNoKGlkeCkKY29tcGlsZXI6IGNjCmF2YWlsYWJsZSB0aW1pbmcgb3B0aW9u czogVVNFX1RPRCBIWj0xMjggW3N5c2NvbmYgdmFsdWVdCnRpbWluZyBmdW5jdGlvbiB1c2VkOiBn ZXR0aW1lb2ZkYXkKVGhlICdudW1iZXJzJyBhcmUgaW4gMTAwMHMgb2YgYnl0ZXMgcGVyIHNlY29u ZCBwcm9jZXNzZWQuCnR5cGUgICAgICAgICAgICAgMTYgYnl0ZXMgICAgIDY0IGJ5dGVzICAgIDI1 NiBieXRlcyAgIDEwMjQgYnl0ZXMgICA4MTkyIGJ5dGVzCmFlcy0xMjggY2JjICAgICAgIDUzNTku NTdrICAgICA1NTc3LjQ5ayAgICAgNTY1NC41M2sgICAgIDU2MzkuODFrICAgICA1Njc5LjY1awph ZXMtMTI4LWNiYyAgICAgICAgMzk0LjYyayAgICAgMTQ3MS45N2sgICAgIDU0NTcuODlrICAgIDE1 MDk3LjIxayAgICAyNTg5NS43MmsK From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 21:26:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FC041065674 for ; Sun, 22 Jun 2008 21:26:54 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id D3CD68FC2C for ; Sun, 22 Jun 2008 21:26:53 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so551998ana.13 for ; Sun, 22 Jun 2008 14:26:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=ADi85S+bjvf8qfHlYT74FbItF1btlmXYzqvZ0PiGnvk=; b=Fs5YzOqZl4kUi3Hv5HTDM7YAJIoPNRQrdGenp7+XBMb6rVCu2oDg8De3H7+3vtsrHV imQfOlWnLGk3tiypvO1YvSne+cupRIaYNJEaxT2SDWRn6l/I3IBbz3zNY+k9D4IZku/N pBLFcYPlh1mdJlfbnqQPey7ReuHGC+TnfZpO4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=vcSVNO1erXR3BDjQp5NI9Xa8deyru/1Ma3w2fxG1XemIFStJtM9+TKsBonKdFMAvnz mzn/NFdIxWqAYtbY43lqjN0mvRPiezeTBE9vrY32GMPraeIf5lQSpXlglqqutmeQYITP Z2nB7I0qkv98YPz58goxca2FIe4NoNq+SRLow= Received: by 10.101.71.9 with SMTP id y9mr11454126ank.145.1214168365835; Sun, 22 Jun 2008 13:59:25 -0700 (PDT) Received: by 10.100.216.4 with HTTP; Sun, 22 Jun 2008 13:59:25 -0700 (PDT) Message-ID: Date: Sun, 22 Jun 2008 13:59:25 -0700 From: "Mike Derouen" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 21:26:54 -0000 Hello All, I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: motherboard: ASUS P5N-EM-HDMI chipset: GeForce 7100 / nForce 630i processor: intel core2 quad Q6600 I have installed from the release ISO image, and everything seems to install fine. However, I can't seem to get the network card to be recognized. I have tried using both nfe and nve kernel modules, but neither one seems to identify with the onboard network card. dmesg reports: pci0: at device 15.0 (no driver attached) Is there another module that uses the drivers listed here?: http://www.nvidia.com/object/linux_nforce_1.25.html Or another way to get the network card working? I have also considered going the ndisgen route and trying to use the windows drivers that came w/ the motherboard, but I'm thinking that there's a better solution to this problem out there. Any Ideas? Thanks, Mike From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 21:37:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D33AB106566B for ; Sun, 22 Jun 2008 21:37:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id C3F398FC1C for ; Sun, 22 Jun 2008 21:37:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 9BD451CC031; Sun, 22 Jun 2008 14:37:00 -0700 (PDT) Date: Sun, 22 Jun 2008 14:37:00 -0700 From: Jeremy Chadwick To: Mike Derouen Message-ID: <20080622213700.GA83859@eos.sc1.parodius.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: pyunyh@gmail.com, freebsd-stable@freebsd.org Subject: Re: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 21:37:00 -0000 On Sun, Jun 22, 2008 at 01:59:25PM -0700, Mike Derouen wrote: > I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: > > motherboard: ASUS P5N-EM-HDMI > chipset: GeForce 7100 / nForce 630i > processor: intel core2 quad Q6600 > > I have installed from the release ISO image, and everything seems to install > fine. However, I can't seem to get the network card to be recognized. I > have tried using both nfe and nve kernel modules, but neither one seems to > identify with the onboard network card. dmesg reports: > > pci0: at device 15.0 (no driver attached) > > Is there another module that uses the drivers listed here?: > http://www.nvidia.com/object/linux_nforce_1.25.html Or another way to get > the network card working? I have also considered going the ndisgen route > and trying to use the windows drivers that came w/ the motherboard, but I'm > thinking that there's a better solution to this problem out there. > > Any Ideas? Provide the output from pciconf -lv. By the way, finding specification details for that motherboard appears to be difficult. Asus's own site has empty fields for each spec. detail, and all you can find on Google are vendors selling it. The closest thing I can find is the Windows driver page for the board: http://support.asus.com/download/download.aspx?SLanguage=en-us&model=P5N-EM%20HDMI The User Manual lists the NIC as "Gb LAN". Wow, thanks Asus. The BIOS listing in the Manual (which isn't 100% accurate, but it's the best we've got) shows a "Onboard nVidia LAN" item. I can't find any other details about the board. CC'ing PYUN YongHyeon, who should be able to help, since he assists in maintaining these drivers for FreeBSD. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 22 23:28:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6AC1106564A for ; Sun, 22 Jun 2008 23:28:33 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 94AF58FC0A for ; Sun, 22 Jun 2008 23:28:33 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so561732ana.13 for ; Sun, 22 Jun 2008 16:28:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=it7JMVNCqxiSAr9vWZxouBYAey2iZyKwYNqmJowpQdw=; b=mwkJAalj82TjgRLRZt4DUOr7VZ/1E3Jqx3U6b4Dp0JkuZ1X7WHWTJNEM/j0PhJkpyx AycXmWwEO9OwxreurJFNepJUnBLd6TkAW8kbHAptJOHYfVr9tsACpdFhHLq0P3qQ0aDs 8DxR1thCFruWbKYYA0a1Ik5jEPSAAIp/pN6J4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=uSYLQvJG9dN5DgtUUgiC7Fb6E0L26AyGVr9xOKrxkDesYecw6rhsyIKbYKhUIcI+h3 IyOyGgdNB9EfjGKBN4Kat0oG/46MEt2RCbgWqZciVSSAJZEyToWyXAPVnoTvZiIw3WfI shstRTlLYOzQKw+i3fA1yIZFIKfJyhDfuq30o= Received: by 10.100.228.17 with SMTP id a17mr11753678anh.116.1214177312806; Sun, 22 Jun 2008 16:28:32 -0700 (PDT) Received: by 10.100.216.4 with HTTP; Sun, 22 Jun 2008 16:28:32 -0700 (PDT) Message-ID: Date: Sun, 22 Jun 2008 16:28:32 -0700 From: "Mike Derouen" To: freebsd-stable@freebsd.org In-Reply-To: <20080622213700.GA83859@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080622213700.GA83859@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: pyunyh@gmail.com Subject: Re: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 23:28:34 -0000 Jeremy, Thanks for your reply. I wasn't able to find out much from the ASUS site either. Here is the pciconf output: hostb0@pci0:0:0:0: class=0x060000 card=0x00000000 chip=0x07c110de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = bridge subclass = HOST-PCI none0@pci0:0:0:1: class=0x050000 card=0x00000000 chip=0x07cb10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none1@pci0:0:1:0: class=0x050000 card=0x00000000 chip=0x07cd10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none2@pci0:0:1:1: class=0x050000 card=0x00000000 chip=0x07ce10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none3@pci0:0:1:2: class=0x050000 card=0x00000000 chip=0x07cf10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none4@pci0:0:1:3: class=0x050000 card=0x00000000 chip=0x07d010de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none5@pci0:0:1:4: class=0x050000 card=0x00000000 chip=0x07d110de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none6@pci0:0:1:5: class=0x050000 card=0x00000000 chip=0x07d210de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none7@pci0:0:1:6: class=0x050000 card=0x00000000 chip=0x07d310de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none8@pci0:0:2:0: class=0x050000 card=0x00000000 chip=0x07d610de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM isab0@pci0:0:3:0: class=0x060100 card=0x82ae1043 chip=0x07d710de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = bridge subclass = PCI-ISA none9@pci0:0:3:1: class=0x0c0500 card=0x82ae1043 chip=0x07d810de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = SMBus none10@pci0:0:3:2: class=0x050000 card=0x00000000 chip=0x07d910de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM none11@pci0:0:3:4: class=0x050000 card=0x00000000 chip=0x07c810de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM ohci0@pci0:0:4:0: class=0x0c0310 card=0x82ae1043 chip=0x07fe10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = USB ehci0@pci0:0:4:1: class=0x0c0320 card=0x82ae1043 chip=0x056a10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = USB atapci0@pci0:0:8:0: class=0x01018a card=0x82ae1043 chip=0x056c10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = mass storage subclass = ATA none12@pci0:0:9:0: class=0x040300 card=0x829f1043 chip=0x07fc10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = multimedia pcib1@pci0:0:10:0: class=0x060401 card=0xcb7310de chip=0x056d10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI pcib2@pci0:0:11:0: class=0x060400 card=0x000010de chip=0x056e10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI pcib3@pci0:0:12:0: class=0x060400 card=0x000010de chip=0x056f10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI pcib4@pci0:0:13:0: class=0x060400 card=0x000010de chip=0x056f10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI atapci1@pci0:0:14:0: class=0x010185 card=0x82ae1043 chip=0x07f010de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = mass storage subclass = ATA none13@pci0:0:15:0: class=0x020000 card=0x82ae1043 chip=0x07dc10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = network subclass = ethernet vgapci0@pci0:0:16:0: class=0x030000 card=0x82ae1043 chip=0x07e110de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = display subclass = VGA twe0@pci0:1:6:0: class=0x010400 card=0x100113c1 chip=0x100113c1 rev=0x01 hdr=0x00 vendor = '3ware Inc.' device = '7000/8000 series ATA-133 Storage Controller' class = mass storage subclass = RAID Mike On Sun, Jun 22, 2008 at 2:37 PM, Jeremy Chadwick wrote: > On Sun, Jun 22, 2008 at 01:59:25PM -0700, Mike Derouen wrote: > > I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: > > > > motherboard: ASUS P5N-EM-HDMI > > chipset: GeForce 7100 / nForce 630i > > processor: intel core2 quad Q6600 > > > > I have installed from the release ISO image, and everything seems to > install > > fine. However, I can't seem to get the network card to be recognized. I > > have tried using both nfe and nve kernel modules, but neither one seems > to > > identify with the onboard network card. dmesg reports: > > > > pci0: at device 15.0 (no driver attached) > > > > Is there another module that uses the drivers listed here?: > > http://www.nvidia.com/object/linux_nforce_1.25.html Or another way to > get > > the network card working? I have also considered going the ndisgen route > > and trying to use the windows drivers that came w/ the motherboard, but > I'm > > thinking that there's a better solution to this problem out there. > > > > Any Ideas? > > Provide the output from pciconf -lv. > > By the way, finding specification details for that motherboard appears > to be difficult. Asus's own site has empty fields for each spec. > detail, and all you can find on Google are vendors selling it. The > closest thing I can find is the Windows driver page for the board: > > > http://support.asus.com/download/download.aspx?SLanguage=en-us&model=P5N-EM%20HDMI > > The User Manual lists the NIC as "Gb LAN". Wow, thanks Asus. The BIOS > listing in the Manual (which isn't 100% accurate, but it's the best > we've got) shows a "Onboard nVidia LAN" item. I can't find any other > details about the board. > > CC'ing PYUN YongHyeon, who should be able to help, since he assists in > maintaining these drivers for FreeBSD. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 01:43:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A09891065670 for ; Mon, 23 Jun 2008 01:43:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4AE4F8FC1E for ; Mon, 23 Jun 2008 01:43:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so826796pyb.10 for ; Sun, 22 Jun 2008 18:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=K6VqX6WvtwH+e+krRTcWdcMM5I1Iun+HYG6ScQCTSuk=; b=rbtk9H9N8kKs9Vm0I/d+cKX2UPb/CPVOgFOYE7KoV67pmDryPZuruW9dX4+t+0BZzM 4pgTWdXw39NiO7djZM1NLbxwETw0hJPVsuCj2ahYeSWjT2+fK8AVsF+Btkk4zC48s6Of Dhm8A0Ih82cZdqF6kK6FM/LtX82H2U4gwiXtg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=L7/9ze6x9tmnJQDKUQoUi4K4L/g2lB4BaRFSEtLzipixVkxlskBPCHQkaAGeUB/Via Wmij8sl4xatYtCKQTs5rV5oVy8WkKwIe5udOHCaa+He5GLiL5vnTjVq6WIrykH2DH8gL L45uwNauBIaNh5Jk1AgP/ayMDBIcoFShtU1f4= Received: by 10.140.226.13 with SMTP id y13mr11816707rvg.2.1214185431103; Sun, 22 Jun 2008 18:43:51 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id y11sm6744148pod.5.2008.06.22.18.43.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 22 Jun 2008 18:43:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m5N1fglx051834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jun 2008 10:41:42 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5N1fgEf051833; Mon, 23 Jun 2008 10:41:42 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 23 Jun 2008 10:41:42 +0900 From: Pyun YongHyeon To: Mike Derouen Message-ID: <20080623014142.GE51356@cdnetworks.co.kr> References: <20080622213700.GA83859@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 01:43:52 -0000 On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > Jeremy, > > Thanks for your reply. I wasn't able to find out much from the ASUS site > either. Here is the pciconf output: > [...] > none13@pci0:0:15:0: class=0x020000 card=0x82ae1043 chip=0x07dc10de > rev=0xa2 hdr=0x00 > vendor = 'Nvidia Corp' > class = network > subclass = ethernet This looks like MCP73 ethernet controller. It's supported in 7-stable so you may have to update to latest 7-stable to use the ethernet controller. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 04:20:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66F6D1065676 for ; Mon, 23 Jun 2008 04:20:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 545DA8FC0A for ; Mon, 23 Jun 2008 04:20:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2A4CE1CC031; Sun, 22 Jun 2008 21:20:25 -0700 (PDT) Date: Sun, 22 Jun 2008 21:20:25 -0700 From: Jeremy Chadwick To: Mike Derouen Message-ID: <20080623042025.GA7684@eos.sc1.parodius.com> References: <20080622213700.GA83859@eos.sc1.parodius.com> <20080623014142.GE51356@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080623014142.GE51356@cdnetworks.co.kr> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Pyun YongHyeon , freebsd-stable@freebsd.org Subject: Re: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 04:20:25 -0000 On Mon, Jun 23, 2008 at 10:41:42AM +0900, Pyun YongHyeon wrote: > On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > > Jeremy, > > > > Thanks for your reply. I wasn't able to find out much from the ASUS site > > either. Here is the pciconf output: > > > > [...] > > > none13@pci0:0:15:0: class=0x020000 card=0x82ae1043 chip=0x07dc10de > > rev=0xa2 hdr=0x00 > > vendor = 'Nvidia Corp' > > class = network > > subclass = ethernet > > This looks like MCP73 ethernet controller. It's supported in > 7-stable so you may have to update to latest 7-stable to use the > ethernet controller. Mike, you can download one of the RELENG_7 (7.0-STABLE) ISO snapshots from here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806/ You probably want 7.0-STABLE-200806-i386-disc1.iso or amd64-disc1.iso depending upon if you want a 32-bit or 64-bit OS. (I'd recommend going with amd64, if at all possible.) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 05:07:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33C98106564A for ; Mon, 23 Jun 2008 05:07:27 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id D38CE8FC18 for ; Mon, 23 Jun 2008 05:07:26 +0000 (UTC) (envelope-from mike.derouen@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so586830ana.13 for ; Sun, 22 Jun 2008 22:07:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=ZgVIRbZCcaCcrEDFoMBvx+GQ5wDwArYPtESJ7jAWKzI=; b=XjgexYoQzgg7H3cP6acAjTZ8uaYoamjwU3jUjPr6F4baDl8fb/nCfVZ6aTWjvhPN+A 8kpalYntSvEalJVfpIBEPJ9mQvvqbo3fTLFZ/cwDr954aNtBmmKdTcPws950M+ZJpL6f kyX4c9SHLDJltaaPUaJI4OAbxxxgavI2mNxX8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=HSgAq6RJBmF1MISzBgH4QNd+ZpqQLqybsWrouWToePygRWhyOSr/DAQ0iopSubVMIw r2SCrBBLi1MstNYI6nRZVMLUNEusXJ3hm2o3Wvo6u2jEBFm1o/FB358hGjYj5RGmnt8E s6u/kjsm5CiW+3QHkd5jkV9PZIJ09edvx9pXI= Received: by 10.100.41.15 with SMTP id o15mr12303983ano.48.1214197645927; Sun, 22 Jun 2008 22:07:25 -0700 (PDT) Received: by 10.100.216.4 with HTTP; Sun, 22 Jun 2008 22:07:25 -0700 (PDT) Message-ID: Date: Sun, 22 Jun 2008 22:07:25 -0700 From: "Mike Derouen" To: "Jeremy Chadwick" In-Reply-To: <20080623042025.GA7684@eos.sc1.parodius.com> MIME-Version: 1.0 References: <20080622213700.GA83859@eos.sc1.parodius.com> <20080623014142.GE51356@cdnetworks.co.kr> <20080623042025.GA7684@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Pyun YongHyeon , freebsd-stable@freebsd.org Subject: Re: NIC compatibility X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 05:07:27 -0000 That did the trick! Thanks guys. Sorry for the n00b questions :). I was under the impression that I had the "latest" FreeBSD7 with the RELEASE build, but I was getting the RELEASE and STABLE meanings mixed up. Thanks! Mike On Sun, Jun 22, 2008 at 9:20 PM, Jeremy Chadwick wrote: > On Mon, Jun 23, 2008 at 10:41:42AM +0900, Pyun YongHyeon wrote: > > On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > > > Jeremy, > > > > > > Thanks for your reply. I wasn't able to find out much from the ASUS > site > > > either. Here is the pciconf output: > > > > > > > [...] > > > > > none13@pci0:0:15:0: class=0x020000 card=0x82ae1043 chip=0x07dc10de > > > rev=0xa2 hdr=0x00 > > > vendor = 'Nvidia Corp' > > > class = network > > > subclass = ethernet > > > > This looks like MCP73 ethernet controller. It's supported in > > 7-stable so you may have to update to latest 7-stable to use the > > ethernet controller. > > Mike, you can download one of the RELENG_7 (7.0-STABLE) ISO snapshots > from here: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806/ > > You probably want 7.0-STABLE-200806-i386-disc1.iso or amd64-disc1.iso > depending upon if you want a 32-bit or 64-bit OS. (I'd recommend going > with amd64, if at all possible.) > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 06:42:10 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 876611065674 for ; Mon, 23 Jun 2008 06:42:10 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3FD938FC19 for ; Mon, 23 Jun 2008 06:42:10 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 0C5D821145; Mon, 23 Jun 2008 09:42:08 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23047-06; Mon, 23 Jun 2008 09:42:07 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 236A12114A; Mon, 23 Jun 2008 09:42:06 +0300 (EEST) Message-ID: <485F45BE.3030204@bulinfo.net> Date: Mon, 23 Jun 2008 09:42:06 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Oliver Fromme References: <200806202048.m5KKmgo6073726@lurza.secnetix.de> In-Reply-To: <200806202048.m5KKmgo6073726@lurza.secnetix.de> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 06:42:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Fromme wrote: > Ivan Voras wrote: > > Rink Springer wrote: > > > The 'vscan' user leads me assume this is SpamAssassin - I've seen this > > > behaviour at work, where our scripts were trying to backup a 1TB file > > > (which actually was ~vscan/.spamassassin/auto-whitelist). The result was > > > that the backup script died due to lack of disk space on the backup > > > server (as we don't use compression). > > > > > > When I was investigating why the file could be so large it, it turned > > > out the file was only a few hunderd 'real' MB's, so that is why I assume > > > this person is having the same issue as we do. The file is a Berkeley DB > > > file, by the way, so there's nothing textfile about it ;-) > > > > I learn something every day :) > > Didn't know BDB was smart enough to create sparse files. > > BTW, you can use "ls -ls" to display the number of physical > blocks allocated to the file, so you can easily see whether > a file is sparse or not: > > $ dd if=/dev/zero of=foo1 bs=1m count=1 > $ truncate -s 1m foo2 > $ ls -ls foo1 foo2 > 1040 -rw------- 1 olli olli 1048576 Jun 20 22:43 foo1 > 32 -rw------- 1 olli olli 1048576 Jun 20 22:43 foo2 # ls -lsk total 1247288 664064 -rw------- 1 vscan vscan 4398199488512 Jun 23 09:39 auto-whitelist 88 -rw------- 1 vscan vscan 89976 Jun 23 09:39 bayes_journal 566704 -rw------- 1 vscan vscan 1099639861248 Jun 23 09:39 bayes_seen 16432 -rw------- 1 vscan vscan 21454848 Jun 23 09:39 bayes_toks > > As you can see, the file size is the same, but the block > counts are different (I have BLOCKSIZE=K in my environment, > so the blocks are displayed in 1KB units). > > I've written a small script that can be used to detect > sparse files (it even displays the "sparseness" percentage): > > http://www.secnetix.de/olli/scripts/sparsecheck > > Best regards > Oliver > > PS: Of course it is still possible that a file system is > corrupt and needs fsck, no matter whether those files are > sparse or not. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX0W+xJBWvpalMpkRAqrdAJ47eLQ+WMp6zBrme5gNyCSvzBtdUwCffYwT +37ul1gPqmk7rVKXRrha7fU= =uSGe -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 06:56:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DC00106564A for ; Mon, 23 Jun 2008 06:56:52 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id E25F78FC1B for ; Mon, 23 Jun 2008 06:56:51 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 25F47211EC; Mon, 23 Jun 2008 09:56:50 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24787-06; Mon, 23 Jun 2008 09:56:49 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 2FB5B211EB; Mon, 23 Jun 2008 09:56:49 +0300 (EEST) Message-ID: <485F4930.601@bulinfo.net> Date: Mon, 23 Jun 2008 09:56:48 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Ivan Voras References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@freebsd.org Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 06:56:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Ivan Voras wrote: > Rink Springer wrote: >> On Fri, Jun 20, 2008 at 03:54:22PM +0200, Ivan Voras wrote: >>> Except that the file in question should be, judging by the filename, a >>> simple text file. I don't really see how a whitelist could grow to such >>> monstrous sizes :) Most likely it's a file system corruption - fsck >>> should be the first thing to try. >> The 'vscan' user leads me assume this is SpamAssassin - I've seen this >> behaviour at work, where our scripts were trying to backup a 1TB file >> (which actually was ~vscan/.spamassassin/auto-whitelist). The result was >> that the backup script died due to lack of disk space on the backup >> server (as we don't use compression). Yes, it is SpamAssassin and I have the same problem with the backups. The Amanda complains with: xxxxxxxxxxx / lev 1 FAILED [dump larger than available tape space, 307256178 KB, skipping incremental] yyyyyyyyyyyy / lev 4 FAILED [dump larger than tape, 354005617 KB, skipping incremental] I don't think this is a file system corruption because there are no reasons for this. Also I have seen this on different machines. Any ideas how to fix this? >> >> When I was investigating why the file could be so large it, it turned >> out the file was only a few hunderd 'real' MB's, so that is why I assume >> this person is having the same issue as we do. The file is a Berkeley DB >> file, by the way, so there's nothing textfile about it ;-) > > I learn something every day :) > Didn't know BDB was smart enough to create sparse files. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX0kwxJBWvpalMpkRAjkaAKCbF7sylsDyI2umCAoneqBqAYCNqwCgnQjA 9FkgJiVhqNI2NGCAlWpqfbg= =PQZ1 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 07:07:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73BDD106564A; Mon, 23 Jun 2008 07:07:26 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id B36348FC16; Mon, 23 Jun 2008 07:07:25 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m5N77EGv070194; Mon, 23 Jun 2008 15:07:14 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m5N77Ejq070193; Mon, 23 Jun 2008 15:07:14 +0800 (KRAST) (envelope-from eugen) Date: Mon, 23 Jun 2008 15:07:14 +0800 From: Eugene Grosbein To: Krassimir Slavchev Message-ID: <20080623070714.GA68058@svzserv.kemerovo.su> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> <485F4930.601@bulinfo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <485F4930.601@bulinfo.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 07:07:26 -0000 On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote: > I don't think this is a file system corruption because there are no > reasons for this. Also I have seen this on different machines. > > Any ideas how to fix this? Either use backup software that is aware of sparse files or eliminate sofrware that uses such files :-) Eugene From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 07:19:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80EC7106564A; Mon, 23 Jun 2008 07:19:28 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6FBF28FC27; Mon, 23 Jun 2008 07:19:28 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 25C671CC031; Mon, 23 Jun 2008 00:19:28 -0700 (PDT) Date: Mon, 23 Jun 2008 00:19:28 -0700 From: Jeremy Chadwick To: Krassimir Slavchev Message-ID: <20080623071928.GA13020@eos.sc1.parodius.com> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> <485F4930.601@bulinfo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <485F4930.601@bulinfo.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 07:19:28 -0000 On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote: > Ivan Voras wrote: > > Rink Springer wrote: > >> On Fri, Jun 20, 2008 at 03:54:22PM +0200, Ivan Voras wrote: > >>> Except that the file in question should be, judging by the filename, a > >>> simple text file. I don't really see how a whitelist could grow to such > >>> monstrous sizes :) Most likely it's a file system corruption - fsck > >>> should be the first thing to try. > >> The 'vscan' user leads me assume this is SpamAssassin - I've seen this > >> behaviour at work, where our scripts were trying to backup a 1TB file > >> (which actually was ~vscan/.spamassassin/auto-whitelist). The result was > >> that the backup script died due to lack of disk space on the backup > >> server (as we don't use compression). I've used SpamAssassin for a few years now, and I've never seen this happen (including during migration from RELENG_6 to RELENG_7, and between SpamAssassin versions (from 3.0 to 3.2.x). I cannot even begin to imagine how that file reached such a size, which is why I believe the issue may be filesystem corruption. I will take a moment to point out something I do whenever SpamAssassin gets upgraded, though: I always delete bayes_* and auto-whitelist files from .spamassassin, on every account. I do this because there have been cases in the past where the data format has changed in the DB, and SA hasn't done a good job of seamlessly migrating them. > Yes, it is SpamAssassin and I have the same problem with the backups. > The Amanda complains with: > xxxxxxxxxxx / lev 1 FAILED [dump larger than available tape space, > 307256178 KB, skipping incremental] > yyyyyyyyyyyy / lev 4 FAILED [dump larger than tape, 354005617 KB, > skipping incremental] There isn't any way to solve this problem. The file, as far as dump is concerned, is indeed 3TB. > I don't think this is a file system corruption because there are no > reasons for this. Also I have seen this on different machines. I can point you to all of the threads in the past year where users have had mysterious problems with their filesystems, which have been fixed by booting single-user and fsck'ing. That may not be the problem here, but it doesn't hurt for you to do it "just in case" now does it? If it happens on multiple machines, I've only two recommendations: 1) Try what I said above (delete the bayes_* and auto-whitelist files). If SpamAssassin recreates them as 3TB, then there is indeed a problem with your system(s), because mine do not do that. 2) Consider migrating to dspam instead, which supposedly has a much greater success rate of blocking spam. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 07:25:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A31FA1065670 for ; Mon, 23 Jun 2008 07:25:57 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.freebsd.org (Postfix) with ESMTP id 2CAE98FC12 for ; Mon, 23 Jun 2008 07:25:56 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from [10.0.2.3] (c122-106-190-227.belrs3.nsw.optusnet.com.au [122.106.190.227]) by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5N7PrnT001543 for ; Mon, 23 Jun 2008 17:25:54 +1000 Message-Id: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> From: Jerahmy Pocott To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 17:25:49 +1000 X-Mailer: Apple Mail (2.924) Subject: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 07:25:57 -0000 Hi, I'm wondering if anything exists to set this.. When you create an INET socket without the 'TCP_NODELAY' flag the network layer does 'naggling' on your transmitted data. Sometimes with hosts that use Delayed_ACK (net.inet.tcp. delayed_ack) it creates a dead-lock where the host will not ACK until it gets another packet and the client will not send another packet until it gets an ACK.. The dead-lock gets broken by a time-out, which I think is around 200ms? But I would like to change that time-out if possible to something lower, yet I can't really see any sysctl knobs that have a name that suggests they do that.. So does anyone know IF this can be tuned and if so by what? Cheers, Jerahmy. (And yes you could solve it by setting the TCP_NODELAY flag on the socket, but not everything has programmed in options to set it and you don't always have access to the source, besides setting a sysctl value would be much simpler than recompiling stuff) From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 07:50:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F20941065672 for ; Mon, 23 Jun 2008 07:50:02 +0000 (UTC) (envelope-from shinjii@maydias.com) Received: from mail5.tpgi.com.au (smtp-out5.tpgi.com.au [220.244.226.115]) by mx1.freebsd.org (Postfix) with ESMTP id 7BA1C8FC19 for ; Mon, 23 Jun 2008 07:50:02 +0000 (UTC) (envelope-from shinjii@maydias.com) X-TPG-Antivirus: Passed Received: from [192.168.1.66] (123-243-239-97.static.tpgi.com.au [123.243.239.97]) by mail5.tpgi.com.au (envelope-from shinjii@maydias.com) (8.14.3/8.14.3) with ESMTP id m5N7TxJH014495 for ; Mon, 23 Jun 2008 17:30:01 +1000 From: Warren Liddell To: freebsd-stable@freebsd.org User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Disposition: inline Date: Mon, 23 Jun 2008 17:30:01 +1000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200806231730.01130.shinjii@maydias.com> Subject: Patch Failures during Portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 07:50:03 -0000 Below is the hunk of ports that continually fail to upgrade due to problems with patching. i use the command portupgrade -aDkp -m BATCH=yes Any assistance with this greatly appreciated. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! lang/ruby18 (ruby-1.8.6.111_1,1) (patch error) ! databases/mysql50-client (mysql-client-5.0.45_1) (patch error) ! graphics/OpenEXR (OpenEXR-1.6.0) (patch error) ! devel/libvolume_id (libvolume_id-0.75.0_1) (patch error) ! graphics/dri (dri-7.0.1,2) (install error) ! net/samba-libsmbclient (samba-libsmbclient-3.0.28) (patch error) ! graphics/libGLU (libGLU-7.0.1) (patch error) ! x11-fonts/xfs (xfs-1.0.5,1) (patch error) ! x11/xorg-libraries (xorg-libraries-7.3_1) (unknown build error) ! x11-toolkits/gtk20 (gtk-2.12.1_1) (patch error) ! irc/xchat (xchat-2.8.4_3) (patch error) ! sysutils/hal (hal-0.5.8.20070909) (configure error) ! x11/kdebase3 (kdebase-3.5.8) (patch error) ! x11-servers/xorg-server (xorg-server-1.4_3,1) (patch error) ! x11-drivers/xorg-drivers (xorg-drivers-7.3) (uninstall error) ---------------------------- ===> Patching for ruby-1.8.6.111_2,1 ===> Applying FreeBSD patches for ruby-1.8.6.111_2,1 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to ext/tk/tkutil/extconf.rb.rej => Patch patch-ext_tk_tkutil_extconf.rb failed to apply cleanly. *** Error code 1 Stop in /usr/ports/lang/ruby18. *** Error code 1 Stop in /usr/ports/lang/ruby18. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 08:27:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FDB2106567D for ; Mon, 23 Jun 2008 08:27:12 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1B4928FC22 for ; Mon, 23 Jun 2008 08:27:11 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m5N8RBEO085476; Mon, 23 Jun 2008 01:27:11 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m5N8RBlW085475; Mon, 23 Jun 2008 01:27:11 -0700 (PDT) Date: Mon, 23 Jun 2008 01:27:11 -0700 (PDT) From: Matthew Dillon Message-Id: <200806230827.m5N8RBlW085475@apollo.backplane.com> To: Jerahmy Pocott References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 08:27:12 -0000 :Hi, : :I'm wondering if anything exists to set this.. When you create an INET :socket :without the 'TCP_NODELAY' flag the network layer does 'naggling' on your :transmitted data. Sometimes with hosts that use Delayed_ACK :(net.inet.tcp. :delayed_ack) it creates a dead-lock where the host will not ACK until :it gets :another packet and the client will not send another packet until it :gets an ACK.. : :The dead-lock gets broken by a time-out, which I think is around 200ms? : :But I would like to change that time-out if possible to something :lower, yet :I can't really see any sysctl knobs that have a name that suggests :they do :that.. : :So does anyone know IF this can be tuned and if so by what? : :Cheers, :Jerahmy. : :(And yes you could solve it by setting the TCP_NODELAY flag on the :socket, :but not everything has programmed in options to set it and you don't :always :have access to the source, besides setting a sysctl value would be much :simpler than recompiling stuff) There is a sysctl which adjusts the delayed-ack timing, its called net.inet.tcp.delacktime. The default is 1/10 of a second (100 == 100 ms = 1/10 of a second). BUT, it shouldn't be possible for nagle to deadlock against delayed acks unless the TCP implementation is broken somehow. A delayed ack is simply that... the ack is delayed 100 ms in order to improve its chances of being piggy-backed on return data. The ack is not blocked completely, just delayed, and certain events (such as the receiving end turning around and sending data back, which is typical for an interactive connection)... certain events will cause the delayed ack to be aborted and for the ack to be immediately sent with the return data. Can it break down and cause excessive lag? Yes, it can. Interactive games almost universally have to disable Nagle because the lag is actually due to the data relay from client 1 -> server then relaying the interactive event to client 2. Without an immediate interactive response to client 1 the ack gets delayed and the next event from client 1 hits Nagle and stops dead in the water until the first event reaches client 2 and client 2 reacts to it (then client 2 -> server -> (abort delayed ack and send) -> client 1 (client 1's nagle now allows the second event to be transmitted). That isn't a deadlock, just really poor interactive performance in that particular situation. Delayed acks also have a safety valve. The spec says that an ack cannot be delayed more then two packets. In a batch link when the second (unacked) packet is received, the delayed ack is aborted and an ack is immediately returned to the sender. This is to prevent congestion control (which is based on acks) from getting completely out of whack and also to prevent the TCP window from getting exhausted. In anycase, the usual solution is to disable Nagle rather then mess with delayed acks. What we need is a new Nagle that understands the new reality for interactive connections... something that doesn't break performance in the 'server in the middle' data relaying case. -Matt From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 08:27:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56B2C1065670; Mon, 23 Jun 2008 08:27:38 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id DA1908FC1F; Mon, 23 Jun 2008 08:27:37 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 443B7216FA; Mon, 23 Jun 2008 11:27:36 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38398-05; Mon, 23 Jun 2008 11:27:35 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 77026216D0; Mon, 23 Jun 2008 11:27:35 +0300 (EEST) Message-ID: <485F5E76.5080401@bulinfo.net> Date: Mon, 23 Jun 2008 11:27:34 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Jeremy Chadwick References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> <485F4930.601@bulinfo.net> <20080623071928.GA13020@eos.sc1.parodius.com> In-Reply-To: <20080623071928.GA13020@eos.sc1.parodius.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 08:27:38 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Chadwick wrote: > On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote: >> Ivan Voras wrote: >>> Rink Springer wrote: >>>> On Fri, Jun 20, 2008 at 03:54:22PM +0200, Ivan Voras wrote: >>>>> Except that the file in question should be, judging by the filename, a >>>>> simple text file. I don't really see how a whitelist could grow to such >>>>> monstrous sizes :) Most likely it's a file system corruption - fsck >>>>> should be the first thing to try. >>>> The 'vscan' user leads me assume this is SpamAssassin - I've seen this >>>> behaviour at work, where our scripts were trying to backup a 1TB file >>>> (which actually was ~vscan/.spamassassin/auto-whitelist). The result was >>>> that the backup script died due to lack of disk space on the backup >>>> server (as we don't use compression). > > I've used SpamAssassin for a few years now, and I've never seen this > happen (including during migration from RELENG_6 to RELENG_7, and > between SpamAssassin versions (from 3.0 to 3.2.x). I cannot even begin > to imagine how that file reached such a size, which is why I believe the > issue may be filesystem corruption. > > I will take a moment to point out something I do whenever SpamAssassin > gets upgraded, though: I always delete bayes_* and auto-whitelist files > from .spamassassin, on every account. I do this because there have been > cases in the past where the data format has changed in the DB, and SA > hasn't done a good job of seamlessly migrating them. I have made several upgrades but have never deleted these files. > >> Yes, it is SpamAssassin and I have the same problem with the backups. >> The Amanda complains with: >> xxxxxxxxxxx / lev 1 FAILED [dump larger than available tape space, >> 307256178 KB, skipping incremental] >> yyyyyyyyyyyy / lev 4 FAILED [dump larger than tape, 354005617 KB, >> skipping incremental] > > There isn't any way to solve this problem. The file, as far as dump is > concerned, is indeed 3TB. > >> I don't think this is a file system corruption because there are no >> reasons for this. Also I have seen this on different machines. > > I can point you to all of the threads in the past year where users have > had mysterious problems with their filesystems, which have been fixed by > booting single-user and fsck'ing. That may not be the problem here, > but it doesn't hurt for you to do it "just in case" now does it? > > If it happens on multiple machines, I've only two recommendations: > > 1) Try what I said above (delete the bayes_* and auto-whitelist files). > If SpamAssassin recreates them as 3TB, then there is indeed a problem > with your system(s), because mine do not do that. I have deleted these files and the SpammAssassin recreated them correctly (16384 bytes initial size). > > 2) Consider migrating to dspam instead, which supposedly has a much > greater success rate of blocking spam. Yes, I will do this ASAP. Thanks for the point. > Thanks for all responses! Best Regards -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX152xJBWvpalMpkRAlHbAJ4vkHJp2gVW4MWm+lC8ECuEuQGStQCdGPNX 50dC+RS0B0SD9tWCZsHPtKA= =JPA9 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 08:55:29 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 106741065672; Mon, 23 Jun 2008 08:55:29 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id E156B8FC2A; Mon, 23 Jun 2008 08:55:27 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 23 Jun 2008 09:55:26 +0100 (BST) Date: Mon, 23 Jun 2008 09:55:25 +0100 From: David Malone To: Jeremy Chadwick Message-ID: <20080623085525.GA95600@walton.maths.tcd.ie> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> <485F4930.601@bulinfo.net> <20080623071928.GA13020@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080623071928.GA13020@eos.sc1.parodius.com> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-stable@FreeBSD.org, Ivan Voras Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 08:55:29 -0000 On Mon, Jun 23, 2008 at 12:19:28AM -0700, Jeremy Chadwick wrote: > I've used SpamAssassin for a few years now, and I've never seen this > happen (including during migration from RELENG_6 to RELENG_7, and > between SpamAssassin versions (from 3.0 to 3.2.x). I cannot even begin > to imagine how that file reached such a size, which is why I believe the > issue may be filesystem corruption. I've seen spamassassin creating large sparse file regurally and do other strang things like get the database into a state where it spins if it trys to clean it out. That's even starting with a clean database. > There isn't any way to solve this problem. The file, as far as dump is > concerned, is indeed 3TB. Dump does understand sparse files, but doesn't store them in the most efficient way possible. Dumping a filesystem with a 1TB file seems to use about 2GB. David. # truncate -s 1T /var/tmp/bigfile # dump 0Lf - /var | wc -c DUMP: Date of this level 0 dump: Mon Jun 23 09:50:50 2008 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/ad4s3d (/var) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 2212849 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 2212776 tape blocks DUMP: finished in 59 seconds, throughput 37504 KBytes/sec DUMP: DUMP IS DONE 2265876480 From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 09:00:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE8E61065688 for ; Mon, 23 Jun 2008 09:00:19 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 910468FC13 for ; Mon, 23 Jun 2008 09:00:19 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 23 Jun 2008 10:00:18 +0100 (BST) Date: Mon, 23 Jun 2008 10:00:17 +0100 From: David Malone To: Jerahmy Pocott Message-ID: <20080623090017.GB95600@walton.maths.tcd.ie> References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 09:00:20 -0000 On Mon, Jun 23, 2008 at 05:25:49PM +1000, Jerahmy Pocott wrote: > So does anyone know IF this can be tuned and if so by what? You can tune it with net.inet.tcp.delacktime - it should be is ms. David. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 09:14:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E701B1065673 for ; Mon, 23 Jun 2008 09:14:06 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.freebsd.org (Postfix) with ESMTP id 86F838FC15 for ; Mon, 23 Jun 2008 09:14:06 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from [10.0.2.3] (c122-106-190-227.belrs3.nsw.optusnet.com.au [122.106.190.227]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5N9E06t008014; Mon, 23 Jun 2008 19:14:00 +1000 Message-Id: From: Jerahmy Pocott To: Matthew Dillon In-Reply-To: <200806230827.m5N8RBlW085475@apollo.backplane.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 19:13:55 +1000 References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> <200806230827.m5N8RBlW085475@apollo.backplane.com> X-Mailer: Apple Mail (2.924) Cc: freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 09:14:07 -0000 On 23/06/2008, at 6:27 PM, Matthew Dillon wrote: > Can it break down and cause excessive lag? Yes, it can. > Interactive > games almost universally have to disable Nagle because the lag is > actually due to the data relay from client 1 -> server then > relaying > the interactive event to client 2. Without an immediate > interactive > response to client 1 the ack gets delayed and the next event from > client 1 hits Nagle and stops dead in the water until the first > event > reaches client 2 and client 2 reacts to it (then client 2 -> > server -> > (abort delayed ack and send) -> client 1 (client 1's nagle now > allows > the second event to be transmitted). That isn't a deadlock, just > really poor interactive performance in that particular situation. Yeah, that's what I'm talking about. True, it's not really a dead-lock, but it's terribly slow! The interaction can cause a 200ms delay on a LAN, as can be seen with samba if you disable tcp_nodelay.. > In anycase, the usual solution is to disable Nagle rather then mess > with delayed acks. What we need is a new Nagle that understands > the > new reality for interactive connections... something that doesn't > break > performance in the 'server in the middle' data relaying case. Exactly, there is nothing really wrong with delayed acks.. But with sysctl I CAN disable and mess with the delayed acks, but I can't seem to do anything to Nagle. That's why I was thinking if I could change the Nagle time-out to 0ms it would effectively disable it.. Cheers. J. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 09:22:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EAEB1065671 for ; Mon, 23 Jun 2008 09:22:39 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.freebsd.org (Postfix) with ESMTP id A9C2D8FC0A for ; Mon, 23 Jun 2008 09:22:38 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from [10.0.2.3] (c122-106-190-227.belrs3.nsw.optusnet.com.au [122.106.190.227]) by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5N9MUl3019023; Mon, 23 Jun 2008 19:22:31 +1000 Message-Id: <302BA5BC-FD6C-4554-8291-D6539C297383@optusnet.com.au> From: Jerahmy Pocott To: David Malone In-Reply-To: <20080623090017.GB95600@walton.maths.tcd.ie> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 19:22:26 +1000 References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> <20080623090017.GB95600@walton.maths.tcd.ie> X-Mailer: Apple Mail (2.924) Cc: freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 09:22:39 -0000 On 23/06/2008, at 7:00 PM, David Malone wrote: > On Mon, Jun 23, 2008 at 05:25:49PM +1000, Jerahmy Pocott wrote: >> So does anyone know IF this can be tuned and if so by what? > > You can tune it with net.inet.tcp.delacktime - it should be is ms. Yeah I saw that one. But that only changes the delayed ack... The default value of 100ms seems fairly reasonable unless you're talking about a LAN.. I guess what I really want to do is disable Nagle in the tcp stack, but since you do that with the sockopts call on a per socket basis I'm guessing there isn't any system wide tunable for it.. Thanks, Jerahmy. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 10:23:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55F4F106564A for ; Mon, 23 Jun 2008 10:23:08 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mail.atsec.com (mail.atsec.com [195.30.249.153]) by mx1.freebsd.org (Postfix) with ESMTP id DB9DE8FC16 for ; Mon, 23 Jun 2008 10:23:07 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mail.atsec.com (localhost [127.0.0.1]) by mail.atsec.com (Postfix) with ESMTP id 193BB58015 for ; Mon, 23 Jun 2008 12:05:51 +0200 (CEST) Received: from [10.2.2.68] (frueh.atsec.com [217.110.13.170]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id D106958008; Mon, 23 Jun 2008 12:05:50 +0200 (CEST) Message-ID: <485F7576.5070104@freebsd.org> Date: Mon, 23 Jun 2008 12:05:42 +0200 From: =?ISO-8859-15?Q?Stefan_E=DFer?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.14) Gecko/20080421 Lightning/0.9pre Thunderbird/2.0.0.14 ThunderBrowse/3.2.1.7 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Matthew Dillon References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> <200806230827.m5N8RBlW085475@apollo.backplane.com> In-Reply-To: <200806230827.m5N8RBlW085475@apollo.backplane.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 10:23:08 -0000 Matthew Dillon wrote: > In anycase, the usual solution is to disable Nagle rather then mess > with delayed acks. What we need is a new Nagle that understands the > new reality for interactive connections... something that doesn't break > performance in the 'server in the middle' data relaying case. One possibility I see is a statistic about DelACKs per TCP connection, counting those that were rightfully delayed (with hindsight). I.e., if an ACK is delayed, but there was no chance to piggy-back it or to combine it with another ACK, it could have been sent without delay. Only those delayed ACKs that reduce load are "good", all others cause additional state to be maintained and may increase latencies for no good reason. Therefore, I thought about starting with Nagle enabled, but give up on delaying ACKs, when doing so is found to be ineffective. The only problem with this approach is that once TCP_NODELAY is implicitly set due to measured behavior of the communication, a situation that would benefit from delayed ACKs can no longer be detected. (Well, you could measure the delay between an ACK and the next data sent to the same destination; disable TCP_NODELAY if ACKs could have been piggy-backed on data packets without too much delay. May be we could really have TCP auto-tune with respect to use of delayed ACKs ... I had suggested this years back, when the issue was discussed, but consensus was, that you should just set TCP_NODELAY. But automatic adjustment could also (implicitly) take RTT, window size into consideration. And to me, automatic setting of TCP_NODELAY seems more useful than automatic clearing (after delayed ACKs had been found to be of no use for a window of say 8 or 16 ACKs). The implementation would be quite simple: Whenever a delayed ACK is sent, check whether it is sent on its own (bad) or whether it could be piggy-backed (good). If, say, 7 of 8 delayed ACKs had to be sent as ACK-only packets, anyway, set TCP_NODELAY and do not bother to keep on deciding whether delayed ACKs had become useful in a different phase of the communication. If you want to be able to automatically disable TCP_NODELAY, then just set a time-stamp whenever an ACK is sent and when the next data is sent through this same socket, check whether delaying the ACK had allowed to send it with that data packet (i.e. the delay was less than the maximum hold time of the delayed ACK). If it had been beneficial to delay ACKs (say 3 out of a window of 4) then clear TCP_NODELAY. I have no idea, whether SMP locking would be problematic, but I guess the checks and counter updates could be put in sections that are appropriately locked, anyway. Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:30:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D899F1065677; Mon, 23 Jun 2008 15:30:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 73FC68FC21; Mon, 23 Jun 2008 15:30:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5NFU8cC034447; Mon, 23 Jun 2008 11:30:08 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 23 Jun 2008 10:47:33 -0400 User-Agent: KMail/1.9.7 References: <372651116.20080615162317@serebryakov.spb.ru> <485612AD.2000301@FreeBSD.org> <48564CAB.4030102@FreeBSD.org> In-Reply-To: <48564CAB.4030102@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806231047.33494.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Mon, 23 Jun 2008 11:30:08 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7541/Mon Jun 23 10:21:03 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Lev Serebryakov Subject: Re: FreeBSD 7-STABLE deadlock! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:30:14 -0000 On Monday 16 June 2008 07:21:15 am Lev Serebryakov wrote: > Lev Serebryakov wrote: > > It seems to be ATA/SATA or UFS2 problem: now I have computer in state, > > when 4 iozone processes are hanged in "Disk wait" state, and I can not > > "cd" to filesystem, which is tested by "iozone". > > But I can create processes, work on system, etc., if I don't touch this > > filesystem. > > I can reproduce it, creating gmirror on 5 disks (yes, not very useful > configuration, but I've started from non-base-system RAID5 and need to > exclude it), FS with 64Kb blocks, and 4 threads of iozone with mixed > workload (-i 8 -+p 70). > > All 5 disks are ICH9DO-based, SATA-II WD5000AAKS HDDs. Try getting the 'ps' output from ddb. Also, get a crash dump if you can. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:30:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 062661065670 for ; Mon, 23 Jun 2008 15:30:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 986928FC1D for ; Mon, 23 Jun 2008 15:30:21 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5NFU8cD034447; Mon, 23 Jun 2008 11:30:14 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 23 Jun 2008 10:50:03 -0400 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> In-Reply-To: <200806172120.41978.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806231050.03856.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Mon, 23 Jun 2008 11:30:15 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7541/Mon Jun 23 10:21:03 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:30:22 -0000 On Tuesday 17 June 2008 07:50:34 am Daniel O'Connor wrote: > Hi, > I have an Epox 8HDAIPRO motherboard - > http://www.epox.com/usA/product.asp?ID=EP-8HDAIPRO and its AGP slot is > detected as pcib rather than agp as I would expect. I do have agp in the > kernel -> In 7.0 agp0 will be a child device of the hostbX device. pciconf -lcv might be useful. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:30:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89A0A1065685 for ; Mon, 23 Jun 2008 15:30:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 253918FC15 for ; Mon, 23 Jun 2008 15:30:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5NFU8cE034447; Mon, 23 Jun 2008 11:30:21 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 23 Jun 2008 10:51:03 -0400 User-Agent: KMail/1.9.7 References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> In-Reply-To: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200806231051.03685.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Mon, 23 Jun 2008 11:30:21 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7541/Mon Jun 23 10:21:03 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Andy Kosela Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:30:27 -0000 On Sunday 08 June 2008 07:49:35 am Andy Kosela wrote: [ much snippage.. ] > there is time to rethink FreeBSD overall strategy and goals. Major > companies using FreeBSD in their infrastructure like Yahoo! or Juniper > Networks would definetly benefit from such moves focused on long term > support of stable releases. I honestly think it is in their interest to > support, even financially FWIW, Yahoo! tracks -stable branches, not point releases. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:34:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4D2D1065670; Mon, 23 Jun 2008 15:34:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 64A8D8FC19; Mon, 23 Jun 2008 15:34:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (unknown [89.163.10.141]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 0760413DF64; Mon, 23 Jun 2008 19:34:14 +0400 (MSD) Date: Mon, 23 Jun 2008 19:34:24 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v3.99.3) Professional X-Priority: 3 (Normal) Message-ID: <168637165.20080623193424@serebryakov.spb.ru> To: John Baldwin In-Reply-To: <200806231047.33494.jhb@freebsd.org> References: <372651116.20080615162317@serebryakov.spb.ru> <485612AD.2000301@FreeBSD.org> <48564CAB.4030102@FreeBSD.org> <200806231047.33494.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Lev Serebryakov , freebsd-stable@freebsd.org Subject: Re[2]: FreeBSD 7-STABLE deadlock! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:34:15 -0000 Hello, John. You wrote 23 =E8=FE=ED=FF 2008 =E3., 18:47:33: > On Monday 16 June 2008 07:21:15 am Lev Serebryakov wrote: >> Lev Serebryakov wrote: >> > It seems to be ATA/SATA or UFS2 problem: now I have computer in state, >> > when 4 iozone processes are hanged in "Disk wait" state, and I can not >> > "cd" to filesystem, which is tested by "iozone". >> > But I can create processes, work on system, etc., if I don't touch th= is >> > filesystem. >> >> I can reproduce it, creating gmirror on 5 disks (yes, not very useful >> configuration, but I've started from non-base-system RAID5 and need to >> exclude it), FS with 64Kb blocks, and 4 threads of iozone with mixed >> workload (-i 8 -+p 70). >> >> All 5 disks are ICH9DO-based, SATA-II WD5000AAKS HDDs. > Try getting the 'ps' output from ddb. Also, get a crash dump if you can. It was tracked douwn to known deadlock in buffer allocator when buffer map is fragmented (thnx to kib@!). Workaround is known: don't use FSes with 16Kb and 64Kb blocks on same system in one time. 16/32 mixture works well :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:44:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 960571065679 for ; Mon, 23 Jun 2008 15:44:44 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from mail1.psrk.com (64.147.114.45.static.nyinternet.net [64.147.114.45]) by mx1.freebsd.org (Postfix) with ESMTP id 53DB98FC18 for ; Mon, 23 Jun 2008 15:44:44 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from [82.77.123.155] (port=55199) by mail1.psrk.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1KAoDY-0007CL-Bw for freebsd-stable@freebsd.org; Mon, 23 Jun 2008 11:44:33 -0400 Message-ID: <485FC488.7050105@psrk.com> Date: Mon, 23 Jun 2008 18:43:04 +0300 From: =?UTF-8?B?U29yaW4gUMOibmNh?= User-Agent: Thunderbird 2.0.0.14 (X11/20080619) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus Subject: Failure building apache22 and mysql51 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:44:44 -0000 Hello people! I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to FreeBSD-7.0-RELEASE-p2 using the tutorial found at http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html All went well with the base system. Now with the ports... mysql51-server was installed and I noticed it fails to start (I mean it dies within a few seconds after the restart). First I tried doing portupgrade -af for a couple of times but after compiling everything, I'm still unlucky. Then I tried portupgrade -aPPR, also to no avail. Then: # cd /usr/ports/databases/mysql51-server # portupgrade -f ---> Reinstalling 'mysql-server-5.1.25' (databases/mysql51-server) ---> Building '/usr/ports/databases/mysql51-server' ===> Cleaning for mysql-server-5.1.25 ===> Vulnerability check disabled, database not found You may use the following build options: WITH_CHARSET=charset Define the primary built-in charset (latin1). WITH_XCHARSET=list Define other built-in charsets (may be 'all'). WITH_COLLATION=collate Define default collation (latin1_swedish_ci). WITH_OPENSSL=yes Enable secure connections. WITH_LINUXTHREADS=yes Use the linuxthreads pthread library. WITH_PROC_SCOPE_PTH=yes Use process scope threads (try it if you use libpthread). BUILD_OPTIMIZED=yes Enable compiler optimizations (use it if you need speed). BUILD_STATIC=yes Build a static version of mysqld. (use it if you need even more speed). WITH_NDB=yes Enable support for NDB Cluster. ===> Extracting for mysql-server-5.1.25 => MD5 Checksum OK for mysql-5.1.25-rc.tar.gz. => SHA256 Checksum OK for mysql-5.1.25-rc.tar.gz. [ ... ] (cd .libs && rm -f libndb.la && ln -s ../libndb.la libndb.la) if /usr/local/bin/libtool --preserve-dup-deps --tag=CC --mode=compile cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\"" -DPLUGINDIR="\"/usr/local/lib/mysql/plugin\"" -DHAVE_EVENT_SCHEDULER -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../regex -I. -O2 -fno-strict-aliasing -pipe -MT udf_example.lo -MD -MP -MF ".deps/udf_example.Tpo" -c -o udf_example.lo udf_example.c; \ then mv -f ".deps/udf_example.Tpo" ".deps/udf_example.Plo"; else rm -f ".deps/udf_example.Tpo"; exit 1; fi cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\"/usr/local\" -DDATADIR=\"/var/db/mysql\" -DSHAREDIR=\"/usr/local/share/mysql\" -DPLUGINDIR=\"/usr/local/lib/mysql/plugin\" -DHAVE_EVENT_SCHEDULER -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../regex -I. -O2 -fno-strict-aliasing -pipe -MT udf_example.lo -MD -MP -MF .deps/udf_example.Tpo -c udf_example.c -fPIC -DPIC -o .libs/udf_example.o cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\"/usr/local\" -DDATADIR=\"/var/db/mysql\" -DSHAREDIR=\"/usr/local/share/mysql\" -DPLUGINDIR=\"/usr/local/lib/mysql/plugin\" -DHAVE_EVENT_SCHEDULER -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../regex -I. -O2 -fno-strict-aliasing -pipe -MT udf_example.lo -MD -MP -MF .deps/udf_example.Tpo -c udf_example.c -o udf_example.o >/dev/null 2>&1 /usr/local/bin/libtool --preserve-dup-deps --tag=CC --mode=link cc -O2 -fno-strict-aliasing -pipe -o udf_example.la -module -rpath /usr/local/lib/mysql udf_example.lo -pthread -lcrypt -lm -pthread cc -shared .libs/udf_example.o -pthread -lcrypt -lm -pthread -pthread -pthread -pthread -pthread -pthread -pthread -Wl,-soname -Wl,udf_example.so.0 -o .libs/udf_example.so.0 /usr/bin/ld: /usr/lib/libpthread.a(thr_mutex.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/libpthread.a: could not read symbols: Bad value gmake[3]: *** [udf_example.la] Error 1 gmake[3]: Leaving directory `/usr/ports/databases/mysql51-server/work/mysql-5.1.25-rc/sql' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/databases/mysql51-server/work/mysql-5.1.25-rc/sql' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/usr/ports/databases/mysql51-server/work/mysql-5.1.25-rc/sql' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/databases/mysql51-server. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.94200.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=mysql-server-5.1.25 UPGRADE_PORT_VER=5.1.25 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! databases/mysql51-server (mysql-server-5.1.25) (new compiler error) and again, with portupgrade -N www/apache22 this time: [ ... ] /bin/sh /usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/libtool --silent --mode=compile cc -O2 -fno-strict-aliasing -pipe -I/usr/local/include/mysql -DHAVE_MYSQL_H -I/usr/include -DHAVE_CONFIG_H -I./include -I/usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/include/arch/unix -I./include/arch/unix -I/usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/include -o user/unix/userinfo.lo -c user/unix/userinfo.c && touch user/unix/userinfo.lo /bin/sh /usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/libtool --silent --mode=link cc -O2 -fno-strict-aliasing -pipe -I/usr/local/include/mysql -DHAVE_MYSQL_H -I/usr/include -DHAVE_CONFIG_H -I./include -I/usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/include/arch/unix -I./include/arch/unix -I/usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr/include -version-info 2:12:2 -L/usr/local/lib/mysql -pthread -rpath=/usr/lib:/usr/local/lib -L/usr/lib -o libapr-1.la -rpath /usr/local/lib passwd/apr_getpass.lo strings/apr_cpystrn.lo strings/apr_fnmatch.lo strings/apr_snprintf.lo strings/apr_strings.lo strings/apr_strnatcmp.lo strings/apr_strtok.lo tables/apr_hash.lo tables/apr_tables.lo atomic/unix/apr_atomic.lo dso/unix/dso.lo file_io/unix/copy.lo file_io/unix/dir.lo file_io/unix/fileacc.lo file_io/unix/filedup.lo file_io/unix/filepath.lo file_io/unix/filepath_util.lo file_io/unix/filestat.lo file_io/unix/flock.lo file_io/unix/fullrw.lo file_io/unix/mktemp.lo file_io/unix/open.lo file_io/unix/pipe.lo file_io/unix/readwrite.lo file_io/unix/seek.lo file_io/unix/tempdir.lo locks/unix/global_mutex.lo locks/unix/proc_mutex.lo locks/unix/thread_cond.lo locks/unix/thread_mutex.lo locks/unix/thread_rwlock.lo memory/unix/apr_pools.lo misc/unix/charset.lo misc/unix/env.lo misc/unix/errorcodes.lo misc/unix/getopt.lo misc/unix/otherchild.lo misc/unix/rand.lo misc/unix/start.lo misc/unix/version.lo mmap/unix/common.lo mmap/unix/mmap.lo network_io/unix/inet_ntop.lo network_io/unix/inet_pton.lo network_io/unix/multicast.lo network_io/unix/sendrecv.lo network_io/unix/sockaddr.lo network_io/unix/sockets.lo network_io/unix/sockopt.lo poll/unix/epoll.lo poll/unix/kqueue.lo poll/unix/poll.lo poll/unix/port.lo poll/unix/select.lo random/unix/apr_random.lo random/unix/sha2.lo random/unix/sha2_glue.lo shmem/unix/shm.lo support/unix/waitio.lo threadproc/unix/proc.lo threadproc/unix/procsup.lo threadproc/unix/signals.lo threadproc/unix/thread.lo threadproc/unix/threadpriv.lo time/unix/time.lo time/unix/timestr.lo user/unix/groupinfo.lo user/unix/userinfo.lo -lcrypt -lpthread /usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC /usr/lib/libpthread.a: could not read symbols: Bad value *** Error code 1 Stop in /usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr. *** Error code 1 Stop in /usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr. *** Error code 1 Stop in /usr/ports/www/apache22/work/httpd-2.2.8/srclib. *** Error code 1 Stop in /usr/ports/www/apache22/work/httpd-2.2.8. *** Error code 1 Stop in /usr/ports/www/apache22. *** Error code 1 Stop in /usr/ports/www/apache22. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.65103.0 env make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache22 (coredump) I thought devel/linuxthreads was using some old library so I tried to rebuild it: # cd ../../devel/linuxthreads && make install clean # portupgrade -f wouldn't do anything ===> linuxthreads-2.2.3_23 is only for i386, while you are running amd64. *** Error code 1 Stop in /usr/ports/devel/linuxthreads. Any ideas what to do next? Thank you! Sorin. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 15:56:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 958901065675; Mon, 23 Jun 2008 15:56:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 175808FC14; Mon, 23 Jun 2008 15:56:14 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <485FC79E.603@FreeBSD.org> Date: Mon, 23 Jun 2008 17:56:14 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Lev Serebryakov References: <372651116.20080615162317@serebryakov.spb.ru> <485612AD.2000301@FreeBSD.org> <48564CAB.4030102@FreeBSD.org> <200806231047.33494.jhb@freebsd.org> <168637165.20080623193424@serebryakov.spb.ru> In-Reply-To: <168637165.20080623193424@serebryakov.spb.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: FreeBSD 7-STABLE deadlock! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 15:56:16 -0000 Lev Serebryakov wrote: > Hello, John. > You wrote 23 èþíÿ 2008 ã., 18:47:33: > >> On Monday 16 June 2008 07:21:15 am Lev Serebryakov wrote: >>> Lev Serebryakov wrote: >>>> It seems to be ATA/SATA or UFS2 problem: now I have computer in state, >>>> when 4 iozone processes are hanged in "Disk wait" state, and I can not >>>> "cd" to filesystem, which is tested by "iozone". >>>> But I can create processes, work on system, etc., if I don't touch this >>>> filesystem. >>> I can reproduce it, creating gmirror on 5 disks (yes, not very useful >>> configuration, but I've started from non-base-system RAID5 and need to >>> exclude it), FS with 64Kb blocks, and 4 threads of iozone with mixed >>> workload (-i 8 -+p 70). >>> >>> All 5 disks are ICH9DO-based, SATA-II WD5000AAKS HDDs. >> Try getting the 'ps' output from ddb. Also, get a crash dump if you can. > It was tracked douwn to known deadlock in buffer allocator when > buffer map is fragmented (thnx to kib@!). Workaround is known: don't > use FSes with 16Kb and 64Kb blocks on same system in one time. 16/32 > mixture works well :) > > Is there a PR filed with this bug? Having the specific information recorded will be very useful. Kris From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 16:06:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49A99106568A; Mon, 23 Jun 2008 16:06:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id F00448FC2C; Mon, 23 Jun 2008 16:06:14 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (unknown [89.163.10.141]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id C79A313DF4A; Mon, 23 Jun 2008 20:06:13 +0400 (MSD) Date: Mon, 23 Jun 2008 20:06:13 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v3.99.3) Professional X-Priority: 3 (Normal) Message-ID: <787938878.20080623200613@serebryakov.spb.ru> To: Kris Kennaway In-Reply-To: <485FC79E.603@FreeBSD.org> References: <372651116.20080615162317@serebryakov.spb.ru> <485612AD.2000301@FreeBSD.org> <48564CAB.4030102@FreeBSD.org> <200806231047.33494.jhb@freebsd.org> <168637165.20080623193424@serebryakov.spb.ru> <485FC79E.603@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Lev Serebryakov , freebsd-stable@freebsd.org, John Baldwin Subject: Re[2]: FreeBSD 7-STABLE deadlock! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 16:06:15 -0000 Hello, Kris. You wrote 23 =E8=FE=ED=FF 2008 =E3., 19:56:14: > Is there a PR filed with this bug? Having the specific information > recorded will be very useful. Kostik (kib@) says, that I don't need to fill PR for this issue... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 16:42:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 499151065676; Mon, 23 Jun 2008 16:42:44 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id D4B5C8FC23; Mon, 23 Jun 2008 16:42:43 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m5NGghCO089159; Mon, 23 Jun 2008 09:42:43 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m5NGggV8089156; Mon, 23 Jun 2008 09:42:42 -0700 (PDT) Date: Mon, 23 Jun 2008 09:42:42 -0700 (PDT) From: Matthew Dillon Message-Id: <200806231642.m5NGggV8089156@apollo.backplane.com> To: =?ISO-8859-15?Q?Stefan_E=DFer?= References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> <200806230827.m5N8RBlW085475@apollo.backplane.com> <485F7576.5070104@freebsd.org> Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 16:42:44 -0000 :One possibility I see is a statistic about DelACKs per TCP connection, :counting those that were rightfully delayed (with hindsight). I.e., :if an ACK is delayed, but there was no chance to piggy-back it or to :combine it with another ACK, it could have been sent without delay. :Only those delayed ACKs that reduce load are "good", all others cause :additional state to be maintained and may increase latencies for no :good reason. : :... :consideration. And to me, automatic setting of TCP_NODELAY seems :more useful than automatic clearing (after delayed ACKs had been :found to be of no use for a window of say 8 or 16 ACKs). : :The implementation would be quite simple: Whenever a delayed ACK :is sent, check whether it is sent on its own (bad) or whether it :could be piggy-backed (good). If, say, 7 of 8 delayed ACKs had to :be sent as ACK-only packets, anyway, set TCP_NODELAY and do not :bother to keep on deciding whether delayed ACKs had become useful :in a different phase of the communication. If you want to be able :to automatically disable TCP_NODELAY, then just set a time-stamp :... :Regards, STefan That's an interesting approach. I think it would catch some of the cases, but not enough of them. If the round-trip in the server-relaying case is less then the delayed-ack, the acks will still wind up piggy-backed on return traffic but the latency will also still remain horrible. It should be noted that Nagle can cause high latencies even when delayed acks are turned off. Nagle's delay is not timed... in its simplest description it prevents packets from being transmitted for new data coming from userland if the data already in the sockbuf (and presumably already transmitted) has not yet been acknowledged. For interactive traffic this means that Nagle is putting the screws on the packet stream even if the acks aren't delayed, simply from the ack latency. With delayed acks turned off the latency is lower, but not 0, so interactive traffic is still being held up by Nagle. The effect is noticeable even on a LAN. Jerahmy brought up Samba... that is an excellent example. NFS-over-TCP would be another good example. Any protocol which multiplexes multiple commands from different sources over the same connection gets really messed up (slowed down) by Nagle. On the flip side, Nagle can't just be turned off by default because it would cause streaming connections from user programs which do tiny writes to generate a lot of unnecessarily tiny packets. This can become apparent when using SSH over a slow link. Numerous programs run from a shell generate fairly ineffcient packets which could have easily been batched when operating over SSH. The result can be sludgy performance for output which ought be batched up by TCP but isn't because SSH turns off Nagle unconditionally. -Matt Matthew Dillon From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 16:44:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC285106567A; Mon, 23 Jun 2008 16:44:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C52BF8FC15; Mon, 23 Jun 2008 16:44:04 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <485FD2D3.3020003@FreeBSD.org> Date: Mon, 23 Jun 2008 18:44:03 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Lev Serebryakov References: <372651116.20080615162317@serebryakov.spb.ru> <485612AD.2000301@FreeBSD.org> <48564CAB.4030102@FreeBSD.org> <200806231047.33494.jhb@freebsd.org> <168637165.20080623193424@serebryakov.spb.ru> <485FC79E.603@FreeBSD.org> <787938878.20080623200613@serebryakov.spb.ru> In-Reply-To: <787938878.20080623200613@serebryakov.spb.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: FreeBSD 7-STABLE deadlock! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 16:44:05 -0000 Lev Serebryakov wrote: > Hello, Kris. > You wrote 23 Ð¸ÑŽÐ½Ñ 2008 г., 19:56:14: > >> Is there a PR filed with this bug? Having the specific information >> recorded will be very useful. > Kostik (kib@) says, that I don't need to fill PR for this issue... > OK, that is good enough for me :) Kris From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 17:06:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C8511065672 for ; Mon, 23 Jun 2008 17:06:10 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 778CD8FC14 for ; Mon, 23 Jun 2008 17:06:10 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 221231CC031; Mon, 23 Jun 2008 10:06:10 -0700 (PDT) Date: Mon, 23 Jun 2008 10:06:10 -0700 From: Jeremy Chadwick To: Sorin =?iso-8859-1?Q?P=E2nca?= Message-ID: <20080623170609.GA39224@eos.sc1.parodius.com> References: <485FC488.7050105@psrk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <485FC488.7050105@psrk.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Failure building apache22 and mysql51 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 17:06:10 -0000 On Mon, Jun 23, 2008 at 06:43:04PM +0300, Sorin Pânca wrote: > Hello people! > I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to > FreeBSD-7.0-RELEASE-p2 using the tutorial found at > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > All went well with the base system. I'm doubting that greatly. Both ports you're trying to build rely on pthread, and both die in the same way: > /usr/bin/ld: /usr/lib/libpthread.a(thr_mutex.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC > /usr/lib/libpthread.a: could not read symbols: Bad value > > /usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC > /usr/lib/libpthread.a: could not read symbols: Bad value -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 17:42:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C3151065673 for ; Mon, 23 Jun 2008 17:42:09 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from mail1.psrk.com (64.147.114.45.static.nyinternet.net [64.147.114.45]) by mx1.freebsd.org (Postfix) with ESMTP id D45058FC0C for ; Mon, 23 Jun 2008 17:42:08 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from [82.77.123.155] (port=57361) by mail1.psrk.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1KAq3B-0007rh-MA for freebsd-stable@freebsd.org; Mon, 23 Jun 2008 13:41:58 -0400 Message-ID: <485FE00E.6060106@psrk.com> Date: Mon, 23 Jun 2008 20:40:30 +0300 From: =?UTF-8?B?U29yaW4gUMOibmNh?= User-Agent: Thunderbird 2.0.0.14 (X11/20080619) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <485FC488.7050105@psrk.com> <20080623170609.GA39224@eos.sc1.parodius.com> In-Reply-To: <20080623170609.GA39224@eos.sc1.parodius.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus Subject: Re: Failure building apache22 and mysql51 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 17:42:09 -0000 Jeremy Chadwick wrote: > On Mon, Jun 23, 2008 at 06:43:04PM +0300, Sorin P�nca wrote: >> Hello people! >> I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to >> FreeBSD-7.0-RELEASE-p2 using the tutorial found at >> http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html >> All went well with the base system. > > I'm doubting that greatly. > Well... they compiled successfully twice (once by doing portupgrade -a, and once by doing portupgrade -af - there were some complaines about some perl modules that we installed by cpan) and then a portupgrade -aPPR finished successfully... Anyway, how do I check everything is clean and working or how do I recompile the pthread part (library) of the system to ensure it's linked against the proper libraries? > Both ports you're trying to build rely on pthread, and both die in the > same way: > >> /usr/bin/ld: /usr/lib/libpthread.a(thr_mutex.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC >> /usr/lib/libpthread.a: could not read symbols: Bad value >> >> /usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC >> /usr/lib/libpthread.a: could not read symbols: Bad value > I agree. That's why I posted both of them. Is my question good or bad? I'm not a programmer, so I really try hard to understand what is happening... Sorin. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 17:48:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4E601065686; Mon, 23 Jun 2008 17:48:02 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id 9B7C68FC2A; Mon, 23 Jun 2008 17:48:02 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (15.10.87-79.rev.gaoland.net [79.87.10.15]) by smtp.lamaiziere.net (Postfix) with ESMTP id 0FF27118059D; Mon, 23 Jun 2008 19:48:01 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id F140F4FAEDC; Mon, 23 Jun 2008 19:47:59 +0200 (CEST) Date: Mon, 23 Jun 2008 19:47:58 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: "Ivan Voras" Message-ID: <20080623194758.6df9cafc@baby-jane-lamaiziere-net.local> In-Reply-To: <9bbcef730806221220u4f8a3f45q305a927efdf5e16f@mail.gmail.com> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> <20080622202041.07f85145@baby-jane-lamaiziere-net.local> <9bbcef730806221220u4f8a3f45q305a927efdf5e16f@mail.gmail.com> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 17:48:03 -0000 Le Sun, 22 Jun 2008 21:20:02 +0200, "Ivan Voras" a écrit : Hi, > The 'numbers' are in 1000s of bytes per second processed. > type 16 bytes 64 bytes 256 bytes 1024 bytes > 8192 bytes aes-128 cbc 5359.57k 5577.49k 5654.53k > 5639.81k 5679.65k aes-128-cbc 394.62k 1471.97k > 5457.89k 15097.21k 25895.72k I've got the same results. The encryption of a file of 360 MBytes takes around 20s with the hardware and 1m10s by software. I am playing to overload my box (a soekris net5501) with ping floods on ipsec (hmac-md5 and rijndael) by a modern computer. With four 'ping -f -s 3000', 'top' reports CPU "0.4% user 0.0 nice 1.6% system, 90.3% interrupt, 7.8% idle". With five 'ping', top does not run, and the kernel does not display the message 'limiting icmp ping response to 300 to 200' anymore too (on the serial console). With the hardware, i can use 8 flood pings without any problem. Top shows CPU: 0.0% user, 0.0% nice, 33.5% system, 12.5% interrupt, 54.1% idle And the kernel displays "limiting icmp ping response from 900 to 200 packets/s.", instead '300 to 200'. So it seems there is a real improvement. Regards. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 17:53:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0D89106566B for ; Mon, 23 Jun 2008 17:53:36 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [198.145.180.174]) by mx1.freebsd.org (Postfix) with ESMTP id 8622F8FC1A for ; Mon, 23 Jun 2008 17:53:36 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: by vexbert.mr-paradox.net (Postfix, from userid 16139) id 4AA74844BD; Mon, 23 Jun 2008 13:53:36 -0400 (EDT) Date: Mon, 23 Jun 2008 13:53:35 -0400 From: Jeff Blank To: freebsd-stable@freebsd.org Message-ID: <20080623175335.GB58577@mr-happy.com> References: <20080617154342.GB49490@mr-happy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080617154342.GB49490@mr-happy.com> X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e Subject: Re: bus_dmamem_alloc failed to align memory properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 17:53:36 -0000 On Tue, Jun 17, 2008 at 11:43:42AM -0400, Jeff Blank wrote: > I've installed a PCI (not PCIE) video card in a FreeBSD 7-STABLE > (20080616 ~19:00 UTC) amd64 system, and when Xorg starts, the kernel > logs the message in the subject. Context: > > Jun 17 11:27:30 bender kernel: drm0: on vgapci0 > Jun 17 11:27:30 bender kernel: info: [drm] Initialized radeon 1.25.0 20060524 > Jun 17 11:27:33 bender kernel: info: [drm] Setting GART location based on new memory map > Jun 17 11:27:33 bender kernel: bus_dmamem_alloc failed to align memory properly. > Jun 17 11:27:33 bender kernel: info: [drm] Loading R200 Microcode > Jun 17 11:27:33 bender kernel: info: [drm] writeback test succeeded in 2 usecs > Jun 17 11:27:33 bender kernel: drm0: [ITHREAD] > > Is this anything to worry about? Part of the reason I ask is that the > machine locked up hard (had to cut power) the first time I hit > ctrl-alt-bs to kill Xorg, though I can't reproduce that reliably (or, > really, at all just yet). Still hoping for an answer, as the PC locked up hard a few more times, always when trying to exit the X server (normal logout/all clients terminated, ctl-alt-bs, init 6). The PC is a Dell Optiplex 740. Its onboard video is NVidia NVS 210S nVidia GForce 6150, but that is disabled when an add-in video card is present (wasn't present in the 'pciconf -lv' I posted last week). What can I do to determine whether the X11 problem is "bus_dmamem_alloc failed to align memory properly" or something else with the card? thanks, Jeff From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 18:52:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001951065680; Mon, 23 Jun 2008 18:52:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5268D8FC12; Mon, 23 Jun 2008 18:52:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5NIqN7A036036; Mon, 23 Jun 2008 14:52:24 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: James Gritton Date: Mon, 23 Jun 2008 14:51:52 -0400 User-Agent: KMail/1.9.7 References: <20080615112318.146C1F18512@mx.npubs.com> <200806180917.05689.jhb@freebsd.org> <485A81FF.1000000@gritton.org> In-Reply-To: <485A81FF.1000000@gritton.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200806231451.52340.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 23 Jun 2008 14:52:24 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7542/Mon Jun 23 12:42:14 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 18:52:32 -0000 On Thursday 19 June 2008 11:57:51 am James Gritton wrote: > John Baldwin wrote: > > On Sunday 15 June 2008 07:23:19 am Stef Walter wrote: > > > >> I've been trying to track down a deadlock on some newish production > >> servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a > >> specific (although mundane) hardware configuration, and each of several > >> servers running this hardware deadlock about once per week. > >> > >> Although I suspect that this is not hardware related, from a (naive) > >> perusal of the attached stack traces. > >> > >> Forgive me if my interpretation of this is all wrong, but I'm pretty > >> desperate for help. So here's my basic understanding of the deadlock: > >> > >> These processes seem to be waiting on the page queue mutex: > >> sendmail (in vm_mmap > vm_map_find > vm_map_insert > vm_map_pmap_enter) > >> bsnmpd (in malloc, uma_large_malloc > page_alloc > kmem_malloc) > >> httpd (in trap > trap_pfault > vm_fault) > >> [g_up] (in g_vfs_done > bufdone) > >> > >> The page queue mutex is held by rsync process: > >> rsync (in trap > trap_pfault > vm_fault > pmap_enter) > >> > >> Rsync kernel process (in pmap_enter) was interrupted while holding the > >> page queue lock? > >> > >> > >> Giant is enabled in loader.conf due to the needs of the pf firewall when > >> dealing with user credentials lookups. I do not believe that Giant plays > >> into this deadlock. Kernel config attached. > >> > >> Any and all help or info is welcome. Thanks in advance. > >> > > > > Try this change: > > > > jhb 2007-10-27 22:07:40 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/kern sched_4bsd.c > > Log: > > Change the roundrobin implementation in the 4BSD scheduler to trigger a > > userland preemption directly from hardclock() via sched_clock() when a > > thread uses up a full quantum instead of using a periodic timeout to cause > > a userland preemption every so often. This fixes a potential deadlock > > when IPI_PREEMPTION isn't enabled where softclock blocks on a lock held > > by a thread pinned or bound to another CPU. The current thread on that > > CPU will never be preempted while softclock is blocked. > > > > Note that ULE already drives its round-robin userland preemption from > > sched_clock() as well and always enables IPI_PREEMPT. > > > > MFC after: 1 week > > > > Revision Changes Path > > 1.108 +8 -29 src/sys/kern/sched_4bsd.c > > > > We use it at work on 6.x. W/o this fix, round-robin stops working on 4BSD > > when softclock() (swi4: clock) blocks on a lock like Giant. > > > > I've been seeing similar troubles on 6.2 and I'll have to give this a > try as we upgrade to 6.3. I notice "MFC after: 1 week" in the log; it's > been a week - any chance of seeing this fix rolled into 6.x? If people confirm it fixes issues I will MFC it. There was some pushback when I first committed it so I waited on the MFC. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 19:06:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6CA71065687 for ; Mon, 23 Jun 2008 19:06:33 +0000 (UTC) (envelope-from handle-globus-admin@cnri.reston.va.us) Received: from cnriweb.cnri.reston.va.us (cnriweb.cnri.reston.va.us [132.151.9.10]) by mx1.freebsd.org (Postfix) with ESMTP id AEA478FC1E for ; Mon, 23 Jun 2008 19:06:33 +0000 (UTC) (envelope-from handle-globus-admin@cnri.reston.va.us) Received: from localhost ([127.0.0.1] helo=cnriweb.cnri.reston.va.us) by cnriweb.cnri.reston.va.us with esmtp (Exim 4.20) id 1KAr77-0003oP-A4 for freebsd-stable@freebsd.org; Mon, 23 Jun 2008 14:50:05 -0400 Date: Mon, 23 Jun 2008 14:50:03 -0400 Message-ID: <20080623185003.14655.97500.Mailman@cnriweb.cnri.reston.va.us> From: handle-globus-request@cnri.reston.va.us To: freebsd-stable@freebsd.org X-Ack: no Sender: handle-globus-admin@cnri.reston.va.us Errors-To: handle-globus-admin@cnri.reston.va.us X-BeenThere: handle-globus@cnri.reston.va.us X-Mailman-Version: 2.0.13 Precedence: bulk Subject: Mailman results for Handle-globus X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 19:06:34 -0000 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address . To obtain instructions on valid Mailman email commands, send email to with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to . The following is a detailed description of the problems. >>>>> Subject line ignored: >>>>> Mail System Error - Returned Mail Command? This is a multi-part message in MIME format. Command? ------=_NextPart_000_0001_B09F961C.9B9F6ED9 Command? Content-Type: text/plain; Command? charset="us-ascii" >>>>> >>>>> Too many errors encountered; the rest of the message is ignored: > Content-Transfer-Encoding: 7bit > > *********************** > InterScan VirusWall 6 has detected an item that contains a virus in this message. > > Please contact the administrator for further information. > *********************** > > The message was undeliverable due to the following reason(s): > > Your message could not be delivered because the destination server was > not reachable within the allowed queue period. The amount of time > a message is queued before it is returned depends on local configura- > tion parameters. > > Most likely there is a network problem that prevented delivery, but > it is also possible that the computer is turned off, or does not > have a mail system running right now. > > Your message could not be delivered within 7 days: > Host 41.121.57.72 is not responding. > > The following recipients could not receive this message: > > > Please reply to postmaster@cnri.reston.va.us > if you feel this message to be in error. > > ------=_NextPart_000_0001_B09F961C.9B9F6ED9 > Content-Type: application/octet-stream; > name="yjt.zip" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename="yjt.zip" > > UEsFBgAAAAAAAAAAAAAAAAAAAAAAAA== > ------=_NextPart_000_0001_B09F961C.9B9F6ED9-- > > > > From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 19:16:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DC73106567F; Mon, 23 Jun 2008 19:16:47 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from gritton.org (gritton.org [161.58.222.4]) by mx1.freebsd.org (Postfix) with ESMTP id 433F38FC18; Mon, 23 Jun 2008 19:16:47 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by gritton.org (8.13.6.20060614/8.13.6) with ESMTP id m5NJGj0t056021; Mon, 23 Jun 2008 13:16:46 -0600 (MDT) Message-ID: <485FF698.103@gritton.org> Date: Mon, 23 Jun 2008 13:16:40 -0600 From: James Gritton User-Agent: Thunderbird 2.0.0.9 (X11/20080228) MIME-Version: 1.0 To: John Baldwin References: <20080615112318.146C1F18512@mx.npubs.com> <200806180917.05689.jhb@freebsd.org> <485A81FF.1000000@gritton.org> <200806231451.52340.jhb@freebsd.org> In-Reply-To: <200806231451.52340.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on gritton.org X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 19:16:47 -0000 John Baldwin wrote: > On Thursday 19 June 2008 11:57:51 am James Gritton wrote: > >> John Baldwin wrote: >> >>> On Sunday 15 June 2008 07:23:19 am Stef Walter wrote: >>> >>> >>>> I've been trying to track down a deadlock on some newish production >>>> servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a >>>> specific (although mundane) hardware configuration, and each of several >>>> servers running this hardware deadlock about once per week. >>>> >>>> Although I suspect that this is not hardware related, from a (naive) >>>> perusal of the attached stack traces. >>>> >>>> Forgive me if my interpretation of this is all wrong, but I'm pretty >>>> desperate for help. So here's my basic understanding of the deadlock: >>>> >>>> These processes seem to be waiting on the page queue mutex: >>>> sendmail (in vm_mmap > vm_map_find > vm_map_insert > vm_map_pmap_enter) >>>> bsnmpd (in malloc, uma_large_malloc > page_alloc > kmem_malloc) >>>> httpd (in trap > trap_pfault > vm_fault) >>>> [g_up] (in g_vfs_done > bufdone) >>>> >>>> The page queue mutex is held by rsync process: >>>> rsync (in trap > trap_pfault > vm_fault > pmap_enter) >>>> >>>> Rsync kernel process (in pmap_enter) was interrupted while holding the >>>> page queue lock? >>>> >>>> >>>> Giant is enabled in loader.conf due to the needs of the pf firewall when >>>> dealing with user credentials lookups. I do not believe that Giant plays >>>> into this deadlock. Kernel config attached. >>>> >>>> Any and all help or info is welcome. Thanks in advance. >>>> >>>> >>> Try this change: >>> >>> jhb 2007-10-27 22:07:40 UTC >>> >>> FreeBSD src repository >>> >>> Modified files: >>> sys/kern sched_4bsd.c >>> Log: >>> Change the roundrobin implementation in the 4BSD scheduler to trigger a >>> userland preemption directly from hardclock() via sched_clock() when a >>> thread uses up a full quantum instead of using a periodic timeout to >>> > cause > >>> a userland preemption every so often. This fixes a potential deadlock >>> when IPI_PREEMPTION isn't enabled where softclock blocks on a lock held >>> by a thread pinned or bound to another CPU. The current thread on that >>> CPU will never be preempted while softclock is blocked. >>> >>> Note that ULE already drives its round-robin userland preemption from >>> sched_clock() as well and always enables IPI_PREEMPT. >>> >>> MFC after: 1 week >>> >>> Revision Changes Path >>> 1.108 +8 -29 src/sys/kern/sched_4bsd.c >>> >>> We use it at work on 6.x. W/o this fix, round-robin stops working on 4BSD >>> when softclock() (swi4: clock) blocks on a lock like Giant. >>> >>> >> I've been seeing similar troubles on 6.2 and I'll have to give this a >> try as we upgrade to 6.3. I notice "MFC after: 1 week" in the log; it's >> been a week - any chance of seeing this fix rolled into 6.x? >> > > If people confirm it fixes issues I will MFC it. There was some pushback when > I first committed it so I waited on the MFC. I can confirm that on 6.3 I can recreate the deadlock without the patch, and can't recreate it with the patch. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 20:26:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A275E1065710 for ; Mon, 23 Jun 2008 20:26:45 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 6FDE28FC27 for ; Mon, 23 Jun 2008 20:26:45 +0000 (UTC) (envelope-from vivek@khera.org) Received: from host-121.int.kcilink.com (host-121.int.kcilink.com [192.168.7.121]) by yertle.kcilink.com (Postfix) with ESMTP id C81FD8A250; Mon, 23 Jun 2008 16:26:44 -0400 (EDT) Message-Id: <8E125C79-9B13-4ECB-A5F7-95049FEDC6DC@khera.org> From: Vivek Khera To: Karl Denninger In-Reply-To: <20080618041530.GA81315@FS.denninger.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 16:26:44 -0400 References: <20080508050550.GA76170@FS.denninger.net> <20080617012053.GA82316@FS.denninger.net> <20080618041530.GA81315@FS.denninger.net> X-Mailer: Apple Mail (2.924) Cc: freebsd-stable@freebsd.org Subject: Re: Management interface for cards powered by the "mfi" driver? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 20:26:45 -0000 On Jun 18, 2008, at 12:15 AM, Karl Denninger wrote: > No management tool = el-sucko, because you can't rebuild a failed > disk or > even shut the alarm on the board off! This is precisely the reason I have dropped using Adaptec controllers. The most recent ones cannot be managed with the FreeBSD tools. What I've ended up using is LSI Fibre Channel 4Gb cards (PCI-e for newer servers, but I have two with PCI-x) attached to an external RAID box. My external RAIDs are custom built by Partners Data Systems and use an Areca controller. All configuration and monitoring is done via web interface over ethernet so no proprietary software is needed. They fully support FreeBSD too. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 20:50:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65D731065671 for ; Mon, 23 Jun 2008 20:50:42 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id 16D8D8FC19 for ; Mon, 23 Jun 2008 20:50:42 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 8B85ED02AF; Mon, 23 Jun 2008 10:50:41 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id C5DE8153882; Mon, 23 Jun 2008 10:50:40 -1000 (HST) Date: Mon, 23 Jun 2008 10:50:40 -1000 From: Clifton Royston To: Jeff Blank Message-ID: <20080623205039.GC10644@lava.net> Mail-Followup-To: Jeff Blank , freebsd-stable@freebsd.org References: <20080617154342.GB49490@mr-happy.com> <20080623175335.GB58577@mr-happy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080623175335.GB58577@mr-happy.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: bus_dmamem_alloc failed to align memory properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 20:50:42 -0000 On Mon, Jun 23, 2008 at 01:53:35PM -0400, Jeff Blank wrote: > On Tue, Jun 17, 2008 at 11:43:42AM -0400, Jeff Blank wrote: > > I've installed a PCI (not PCIE) video card in a FreeBSD 7-STABLE > > (20080616 ~19:00 UTC) amd64 system, and when Xorg starts, the kernel > > logs the message in the subject. Context: > > > > Jun 17 11:27:30 bender kernel: drm0: on vgapci0 > > Jun 17 11:27:30 bender kernel: info: [drm] Initialized radeon 1.25.0 20060524 > > Jun 17 11:27:33 bender kernel: info: [drm] Setting GART location based on new memory map > > Jun 17 11:27:33 bender kernel: bus_dmamem_alloc failed to align memory properly. > > Jun 17 11:27:33 bender kernel: info: [drm] Loading R200 Microcode > > Jun 17 11:27:33 bender kernel: info: [drm] writeback test succeeded in 2 usecs > > Jun 17 11:27:33 bender kernel: drm0: [ITHREAD] > > > > Is this anything to worry about? Part of the reason I ask is that the > > machine locked up hard (had to cut power) the first time I hit > > ctrl-alt-bs to kill Xorg, though I can't reproduce that reliably (or, > > really, at all just yet). > > Still hoping for an answer, as the PC locked up hard a few more times, > always when trying to exit the X server (normal logout/all clients > terminated, ctl-alt-bs, init 6). The PC is a Dell Optiplex 740. Its > onboard video is NVidia NVS 210S nVidia GForce 6150, but that is > disabled when an add-in video card is present (wasn't present in the > 'pciconf -lv' I posted last week). > > What can I do to determine whether the X11 problem is > "bus_dmamem_alloc failed to align memory properly" or something > else with the card? I can not be completely sure, but believe this may be a cross-OS problem with Xorg support of this specific ATI card family. I have had a nearly identical problem with X lockups on a Debian server using the ATI Radeon 9200 Pro (PCI) which uses the same RV280 processor and the same X driver, with similar startup messages: $ dmesg | grep drm [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.25.0 20060524 on minor 0 [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test succeeded in 2 usecs Next time it appears to freeze, see if you can ssh into it; my experience on the Debian box was that this continued to work even though the console was completely unresponsive following the freeze. If you don't want to spend a lot of time on this, I'd try a different video card; I have a strong suspicion that your problems are not FreeBSD related and would go away with that change. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 21:40:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5128C106564A for ; Mon, 23 Jun 2008 21:40:39 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id BF8C18FC23 for ; Mon, 23 Jun 2008 21:40:38 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5N7EPQK014636 for ; Mon, 23 Jun 2008 17:14:25 +1000 Received: from [10.0.2.3] (c122-106-190-227.belrs3.nsw.optusnet.com.au [122.106.190.227]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5N7ELFb014843 for ; Mon, 23 Jun 2008 17:14:21 +1000 Message-Id: <407284EC-EE50-47F5-B7C7-38699B59B814@optusnet.com.au> From: Jerahmy Pocott To: freebsd-stable@freebsd.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 17:14:16 +1000 References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> X-Mailer: Apple Mail (2.924) Subject: Re: DVD-RW doesn't write X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 21:40:39 -0000 On 11/06/2008, at 3:28 AM, Sean C. Farley wrote: > had problems with burncd and my DVD drive when burning CD-RW's. When > I tried atapicam and cdrecord, it gave me problems. I believe it was > using burncd prior to atapicam that caused it because it works now > if I > do not use burncd first. You could try a reboot and use atapicam > first; > the DVD drive may be in a funny state. Just a guess. Yes, I'v noticed that too. But using atacontrol to reset the channel that the drive is on seems to return it to a working state. Trying to reset the device doesn't fix it (maybe it locks up the whole channel?). I'v managed to get the drive working with cdrecord, it still reports device errors to the console and seems slower than it should be, but it *does* produce readable dvds, which is the main thing! However growisofs (well mkisofs part) won't write files over 2gb? But I'v seen single archives written to span the whole dvd.. Do you need to use -iso-level 3 or 4 to get this functionality? How well supported is reading from disks created with level 4? (level 4 equates to ISO-9660:1999 or version 2 according to the man page). Cheers. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 00:17:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E8BF106567B for ; Tue, 24 Jun 2008 00:17:10 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3A5138FC1F for ; Tue, 24 Jun 2008 00:17:08 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-156-46.lns11.adl6.internode.on.net [121.45.156.46]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5O0H3A4044158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 24 Jun 2008 09:47:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: John Baldwin Date: Tue, 24 Jun 2008 09:46:50 +0930 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806231050.03856.jhb@freebsd.org> In-Reply-To: <200806231050.03856.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1278611.FfBNYpm1L0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806240946.58289.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 00:17:10 -0000 --nextPart1278611.FfBNYpm1L0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 24 Jun 2008, John Baldwin wrote: > On Tuesday 17 June 2008 07:50:34 am Daniel O'Connor wrote: > > Hi, > > I have an Epox 8HDAIPRO motherboard - > > http://www.epox.com/usA/product.asp?ID=3DEP-8HDAIPRO and its AGP slot > > is detected as pcib rather than agp as I would expect. I do have > > agp in the kernel -> > > In 7.0 agp0 will be a child device of the hostbX device. pciconf > -lcv might be useful. Here you go! hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x02821106 chip=3D0x0282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI cap 02[80] =3D AGP v3 SBA disabled cap 01[50] =3D powerspec 2 supports D0 D3 current D0 cap 08[60] =3D HT slave cap 08[58] =3D HT interrupt hostb1@pci0:0:0:1: class=3D0x060000 card=3D0x00000000 chip=3D0x1282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI hostb2@pci0:0:0:2: class=3D0x060000 card=3D0x00000000 chip=3D0x2282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI hostb3@pci0:0:0:3: class=3D0x060000 card=3D0x00000000 chip=3D0x3282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI hostb4@pci0:0:0:4: class=3D0x060000 card=3D0x00000000 chip=3D0x4282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI hostb5@pci0:0:0:7: class=3D0x060000 card=3D0x00000000 chip=3D0x7282110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'K8T880Pro CPU to PCI Bridge' class =3D bridge subclass =3D HOST-PCI pcib1@pci0:0:1:0: class=3D0x060400 card=3D0x00000000 chip=3D0xb188110= 6 rev=3D0x00 hdr=3D0x01 vendor =3D 'VIA Technologies Inc' device =3D 'VT8237 K8HTB CPU to AGP 2.0/3.0 Bridge' class =3D bridge subclass =3D PCI-PCI cap 01[80] =3D powerspec 2 supports D0 D1 D3 current D0 fwohci0@pci0:0:8:0: class=3D0x0c0010 card=3D0x581111c1 chip=3D0x581111c= 1 rev=3D0x61 hdr=3D0x00 vendor =3D 'Lucent/Agere Systems (Was: AT&T MicroElectronics)' device =3D 'FW322 1394A PCI PHY/Link Open Host Ctrlr I/F' class =3D serial bus subclass =3D FireWire cap 01[44] =3D powerspec 2 supports D0 D1 D2 D3 current D0 bktr0@pci0:0:9:0: class=3D0x040000 card=3D0x00000000 chip=3D0x036e109= e rev=3D0x11 hdr=3D0x00 vendor =3D 'Conexant (Was: Brooktree Corp)' device =3D 'Bt878/Fusion 878A Mediastream Controller' class =3D multimedia subclass =3D video cap 03[44] =3D VPD cap 01[4c] =3D powerspec 2 supports D0 D3 current D0 none0@pci0:0:9:1: class=3D0x048000 card=3D0x00000000 chip=3D0x0878109= e rev=3D0x11 hdr=3D0x00 vendor =3D 'Conexant (Was: Brooktree Corp)' device =3D '7610144D&REV_02\4&1F7DBC9F&0&09F0 TV Video Capture' class =3D multimedia cap 03[44] =3D VPD cap 01[4c] =3D powerspec 2 supports D0 D3 current D0 twe0@pci0:0:10:0: class=3D0x010400 card=3D0x100113c1 chip=3D0x100113c= 1 rev=3D0x01 hdr=3D0x00 vendor =3D '3ware Inc.' device =3D '7000/8000 series ATA-133 Storage Controller' class =3D mass storage subclass =3D RAID cap 01[40] =3D powerspec 1 supports D0 D1 D3 current D0 fxp0@pci0:0:11:0: class=3D0x020000 card=3D0x00408086 chip=3D0x1229808= 6 rev=3D0x0c hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class =3D network subclass =3D ethernet cap 01[dc] =3D powerspec 2 supports D0 D1 D2 D3 current D0 rl0@pci0:0:13:0: class=3D0x020000 card=3D0x90011695 chip=3D0x813910e= c rev=3D0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor' device =3D 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class =3D network subclass =3D ethernet cap 01[50] =3D powerspec 2 supports D0 D1 D2 D3 current D0 atapci0@pci0:0:15:0: class=3D0x01018f card=3D0x300c1695 chip=3D0x3149110= 6 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT8237 VT6410 SATA RAID Controller' class =3D mass storage subclass =3D ATA cap 01[c0] =3D powerspec 2 supports D0 D3 current D0 atapci1@pci0:0:15:1: class=3D0x01018a card=3D0x300c1695 chip=3D0x0571110= 6 rev=3D0x06 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT82C586A/B/VT82C686/A/B/VT823x/A/C Bus Master IDE Cont= roller' class =3D mass storage subclass =3D ATA cap 01[c0] =3D powerspec 2 supports D0 D3 current D0 uhci0@pci0:0:16:0: class=3D0x0c0300 card=3D0x300c1695 chip=3D0x3038110= 6 rev=3D0x81 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host = Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci1@pci0:0:16:1: class=3D0x0c0300 card=3D0x300c1695 chip=3D0x3038110= 6 rev=3D0x81 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host = Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci2@pci0:0:16:2: class=3D0x0c0300 card=3D0x300c1695 chip=3D0x3038110= 6 rev=3D0x81 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host = Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 uhci3@pci0:0:16:3: class=3D0x0c0300 card=3D0x300c1695 chip=3D0x3038110= 6 rev=3D0x81 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host = Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 ehci0@pci0:0:16:4: class=3D0x0c0320 card=3D0x300c1695 chip=3D0x3104110= 6 rev=3D0x86 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT6202/12 USB 2.0 Enhanced Host Controller' class =3D serial bus subclass =3D USB cap 01[80] =3D powerspec 2 supports D0 D1 D2 D3 current D0 isab0@pci0:0:17:0: class=3D0x060100 card=3D0x32271106 chip=3D0x3227110= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT8237 PCI-to-ISA Bridge' class =3D bridge subclass =3D PCI-ISA cap 01[c0] =3D powerspec 2 supports D0 D3 current D0 pcm0@pci0:0:17:5: class=3D0x040100 card=3D0x300c1695 chip=3D0x3059110= 6 rev=3D0x60 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT8237 AC97 Enhanced Audio Controller - the 8251 contro= ller is different' class =3D multimedia subclass =3D audio cap 01[c0] =3D powerspec 2 supports D0 D1 D2 D3 current D0 hostb6@pci0:0:24:0: class=3D0x060000 card=3D0x00000000 chip=3D0x1100102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D '(K8) Athlon 64/Opteron HyperTransport Technology Config= uration' class =3D bridge subclass =3D HOST-PCI cap 08[80] =3D HT host hostb7@pci0:0:24:1: class=3D0x060000 card=3D0x00000000 chip=3D0x1101102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D '(K8) Athlon 64/Opteron Address Map' class =3D bridge subclass =3D HOST-PCI hostb8@pci0:0:24:2: class=3D0x060000 card=3D0x00000000 chip=3D0x1102102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D '(K8) Athlon 64/Opteron DRAM Controller' class =3D bridge subclass =3D HOST-PCI hostb9@pci0:0:24:3: class=3D0x060000 card=3D0x00000000 chip=3D0x1103102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D '(K8) Athlon 64/Opteron Miscellaneous Control' class =3D bridge subclass =3D HOST-PCI nvidia0@pci0:1:0:0: class=3D0x030000 card=3D0x13511682 chip=3D0x032210d= e rev=3D0xa1 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'GeForce FX 5200 [NV34.3]' class =3D display subclass =3D VGA cap 01[60] =3D powerspec 2 supports D0 D3 current D0 cap 02[44] =3D AGP v3 8x 4x SBA disabled =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1278611.FfBNYpm1L0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIYDz65ZPcIHs/zowRArICAJ9Q9tDXr+0TeeqHmPm7M+7WUkGGoACePChu hGVWW/CUsLZ51RcUQj7rsqI= =TBpK -----END PGP SIGNATURE----- --nextPart1278611.FfBNYpm1L0-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 08:19:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B53B3106564A; Tue, 24 Jun 2008 08:19:36 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.freebsd.org (Postfix) with ESMTP id 33F798FC19; Tue, 24 Jun 2008 08:19:35 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from [10.0.2.3] (c122-106-190-227.belrs3.nsw.optusnet.com.au [122.106.190.227]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5O8JSWQ008928; Tue, 24 Jun 2008 18:19:29 +1000 Message-Id: <25CC6491-DB3F-4B06-A17F-E6C93A3CAD5D@optusnet.com.au> From: Jerahmy Pocott To: freebsd-stable@freebsd.org In-Reply-To: <200806231642.m5NGggV8089156@apollo.backplane.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Tue, 24 Jun 2008 18:19:26 +1000 References: <0222EAC1-A278-41D2-9566-C9CF19811068@optusnet.com.au> <200806230827.m5N8RBlW085475@apollo.backplane.com> <485F7576.5070104@freebsd.org> <200806231642.m5NGggV8089156@apollo.backplane.com> X-Mailer: Apple Mail (2.924) Cc: Subject: Re: Sysctl knob(s) to set TCP 'nagle' time-out? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 08:19:36 -0000 On 24/06/2008, at 2:42 AM, Matthew Dillon wrote: > It should be noted that Nagle can cause high latencies even when > delayed acks are turned off. Nagle's delay is not timed... in its > simplest description it prevents packets from being transmitted > for new data coming from userland if the data already in the > sockbuf (and presumably already transmitted) has not yet been > acknowledged. Assuming that a full data packet can't be constructed in the time it takes for the acknowledgement. If you CAN construct a whole packet in that time then Nagle is either doing a good job or you're sending large amounts of data.. Perhaps nagle a) needs a time out, though I don't really think that would help, or b) uses a dynamic 'in-flight' count where it tries to maintain x packets in-flight and only holds packets up when that value is reached.. The idea being that you get the ack on your first packet at the same time as the host should be getting your second packet.. That way you still get to concatenate lots of small packets being generated in a short space of time, but don't hold up sending data because of the ack latency. It should also be possible to detect if the remote host is using delayed acks and compensate for that? Though I'v not considered it in much detail.. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 10:12:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 481471065681 for ; Tue, 24 Jun 2008 10:12:52 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.158]) by mx1.freebsd.org (Postfix) with ESMTP id 2B07A8FC21 for ; Tue, 24 Jun 2008 10:12:52 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by po-out-1718.google.com with SMTP id c31so651843poi.3 for ; Tue, 24 Jun 2008 03:12:51 -0700 (PDT) Received: by 10.140.208.17 with SMTP id f17mr14453320rvg.218.1214301397230; Tue, 24 Jun 2008 02:56:37 -0700 (PDT) Received: by 10.115.46.11 with HTTP; Tue, 24 Jun 2008 02:56:37 -0700 (PDT) Message-ID: Date: Tue, 24 Jun 2008 17:56:37 +0800 From: "Mars G Miro" To: "Ruslan Ermilov" , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: no more src/compat and install.sh X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 10:12:52 -0000 Greetz, src/compat was repocopied to src/cddl/compat about > 2months ago. I think we need to remove for good 'compat' in src/release/scripts/src-install.sh. Thanks. -- cheers mars From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 11:18:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1564B1065674; Tue, 24 Jun 2008 11:18:22 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id C4B3E8FC19; Tue, 24 Jun 2008 11:18:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KB67y-000Fhf-QP; Tue, 24 Jun 2008 13:51:58 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 24 Jun 2008 13:51:58 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: ata on alix/geode stopped being detcted. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 11:18:22 -0000 hi, latest changes in dev/ata broke this, on older -stable ... ata0-master: pio=3DPIO4 wdma=3DUNSUPPORTED udma=3DUNSUPPORTED cable=3D40 = wire ad0: success setting PIO4 on National chip ad0: 977MB at ata0-master PIO4 on latest -stable: ata0-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUNSUPPORTED cable=3D40 wire and no disk. cheers, danny From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 12:24:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D937106564A for ; Tue, 24 Jun 2008 12:24:08 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id E0B938FC22 for ; Tue, 24 Jun 2008 12:24:07 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by yw-out-2324.google.com with SMTP id 9so859991ywe.13 for ; Tue, 24 Jun 2008 05:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=eDgTTziJ2oa8G5bYcKMdR6xoOFW6Cehetc+5yGJNMKM=; b=LeEniBR4yZ/Eb7Q3QF61d+diLkSdDNh7N4rOFaZZxV85otrs3NotIMszRd9Ok66hCM FkHggmJNRY8Tgg3y6wr5NUSVjsrXBA6usjkXr9UZePjZPLdOl+kLJThSJ4lomCcQTxLF AhgSzlPc0LXKME/6T0npThG2iDqoUIAseKI04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:mime-version :content-type:content-transfer-encoding:content-disposition; b=rN3GIZmwee2HcKsoVPyS6I2RSPF53mcl1umBCDEE4l/kXc4A2wUybsi1TBoplXUjwO EjwrGAbYZ8rcDnNQRC1Uhrng/HOLjqAJObIuDNJOHnNT+e7PwX10k9im6uQWbi/90oCY gbJM5C/B/YWqJii3CXTdZWf8M4YoF4jV5R4hY= Received: by 10.142.223.4 with SMTP id v4mr5406990wfg.172.1214310242136; Tue, 24 Jun 2008 05:24:02 -0700 (PDT) Received: by 10.150.53.16 with HTTP; Tue, 24 Jun 2008 05:24:02 -0700 (PDT) Message-ID: Date: Tue, 24 Jun 2008 13:24:02 +0100 From: "Chris Rees" To: sorin.panca@psrk.com, koitsu@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-stable@freebsd.org Subject: Re: Failure building apache22 and mysql51 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 12:24:08 -0000 > Date: Mon, 23 Jun 2008 18:43:04 +0300 > From: Sorin P?nca > Hello people! > I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to > FreeBSD-7.0-RELEASE-p2 using the tutorial found at > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > All went well with the base system. I don't want to patronise, but are you sure you were running FreeBSD/amd64-6.2 before? Looks kinda like you've tried to upgrade from 6.2/i386 to 7.0/amd64. In case you have, you can't do that. Check you haven't disabled and processor-specific extensions in your BIOS, like SSE, that would also create problems if you have optimised your ports. Chris > I thought devel/linuxthreads was using some old library so I tried to > rebuild it: > > # cd ../../devel/linuxthreads && make install clean # portupgrade -f > wouldn't do anything > ===> linuxthreads-2.2.3_23 is only for i386, while you are running amd64. > *** Error code 1 > > Stop in /usr/ports/devel/linuxthreads. > > > Any ideas what to do next? > Thank you! > > Sorin. > From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 12:53:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59F1C106567F for ; Tue, 24 Jun 2008 12:53:31 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail3.secureworks.net (mail3.secureworks.net [65.114.32.155]) by mx1.freebsd.org (Postfix) with ESMTP id 23BFB8FC18 for ; Tue, 24 Jun 2008 12:53:30 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from localhost (localhost [127.0.0.1]) by mail3.secureworks.net (Postfix) with ESMTP id 526EF19E201; Tue, 24 Jun 2008 12:53:30 +0000 (GMT) X-Virus-Scanned: amavisd-new at secureworks.net Received: from mail3.secureworks.net ([127.0.0.1]) by localhost (mail3.secureworks.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHSU8v0b1g6O; Tue, 24 Jun 2008 12:53:30 +0000 (GMT) Received: from [192.168.23.35] (mole1.secureworks.net [63.239.86.3]) by mail3.secureworks.net (Postfix) with ESMTP id 0A81F19E1FF; Tue, 24 Jun 2008 12:53:30 +0000 (GMT) Message-ID: <4860EE49.1080706@jellydonut.org> Date: Tue, 24 Jun 2008 08:53:29 -0400 From: Michael Proto User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080502 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Patrick_Lamaizi=E8re?= References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> In-Reply-To: <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "freebsd-hackers@freebsd.org" , "freebsd-stable@freebsd.org" Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 12:53:31 -0000 Patrick Lamaizière wrote: > Le Fri, 6 Jun 2008 23:41:35 +0200, > Patrick Lamaizière a écrit : > > Hello, > >> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >> (via the NetBSD port). >> " The glxsb driver supports the security block of the Geode LX >> series processors. The Geode LX is a member of the AMD Geode family >> of integrated x86 system chips. >> >> Driven by periodic checks for available data from the generator, >> glxsb supplies entropy to the random(4) driver for common usage. >> >> glxsb also supports acceleration of AES-128-CBC operations for >> crypto(4)." > > Well, I hope this is the final version. > > http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz > > I added a patch for FreeBSD 6 but i'am not able to test it. > > On 7-STABLE, I've tested with hundred openssl encryptions and some flood > pings under ipsec in the background. Looks good for me. > > If someone can test and review it, it would be cool. I don't know if you built it for this or not, but I just tested your module on 8-CURRENT (last supped May 19) and its working beautifully on an ALIX.3c1 (GeodeLX 700): Copyright (c) 1992-2008 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 8.0-CURRENT #0: Thu Jun 5 22:44:20 EDT 2008 root@minibsd8-dev.localnet:/usr/obj/usr/src/sys/MINIBSD8 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Geode(TM) Integrated Processor by AMD PCS (431.65-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 Features=0x88a93d AMD Features=0xc0400000 real memory = 134217728 (128 MB) avail memory = 126152704 (120 MB) pnpbios: Bad PnP BIOS data checksum wlan: mac acl policy registered K6-family MTRR support enabled (2 registers) ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cryptosoft0: on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 Geode LX: PC Engines ALIX.2 v0.98 tinyBIOS V1.4a (C)1997-2007 glxsb0: mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 Output from "openssl speed -engine cryptodev -elapsed -evp aes-128-cbc aes-128-cbc" engine "cryptodev" set. You have chosen to measure elapsed time instead of user CPU time. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 668161 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 64 size blocks: 178842 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 256 size blocks: 45510 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 1024 size blocks: 11435 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 8192 size blocks: 1429 aes-128 cbc's in 3.00s Doing aes-128-cbc for 3s on 16 size blocks: 61055 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 64 size blocks: 59430 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 53475 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 37812 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 9323 aes-128-cbc's in 3.00s OpenSSL 0.9.8e 23 Feb 2007 built on: Thu Jun 5 21:15:55 EDT 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: gettimeofday The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 3563.35k 3815.11k 3883.37k 3901.80k 3900.02k aes-128-cbc 325.65k 1267.73k 4562.72k 12904.84k 25453.89k Thanks for that, hopefully it can/will be committed soon! -Proto From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 13:05:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98CC510656AA for ; Tue, 24 Jun 2008 13:05:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3BA8C8FC1B for ; Tue, 24 Jun 2008 13:05:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5OD55Kn045459; Tue, 24 Jun 2008 09:05:05 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 24 Jun 2008 08:58:30 -0400 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806231050.03856.jhb@freebsd.org> <200806240946.58289.doconnor@gsoft.com.au> In-Reply-To: <200806240946.58289.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806240858.30701.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Tue, 24 Jun 2008 09:05:06 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7542/Mon Jun 23 12:42:14 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 13:05:13 -0000 On Monday 23 June 2008 08:16:50 pm Daniel O'Connor wrote: > On Tue, 24 Jun 2008, John Baldwin wrote: > > On Tuesday 17 June 2008 07:50:34 am Daniel O'Connor wrote: > > > Hi, > > > I have an Epox 8HDAIPRO motherboard - > > > http://www.epox.com/usA/product.asp?ID=EP-8HDAIPRO and its AGP slot > > > is detected as pcib rather than agp as I would expect. I do have > > > agp in the kernel -> > > > > In 7.0 agp0 will be a child device of the hostbX device. pciconf > > -lcv might be useful. > > Here you go! > > hostb0@pci0:0:0:0: class=0x060000 card=0x02821106 chip=0x02821106 > rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' > device = 'K8T880Pro CPU to PCI Bridge' > class = bridge > subclass = HOST-PCI > cap 02[80] = AGP v3 SBA disabled > cap 01[50] = powerspec 2 supports D0 D3 current D0 > cap 08[60] = HT slave > cap 08[58] = HT interrupt Ok, so this is the host side of AGP. Do you see any agpX devices in devinfo -v output? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 13:36:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA3651065671; Tue, 24 Jun 2008 13:36:48 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id E82518FC2D; Tue, 24 Jun 2008 13:36:47 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-123-141.lns11.adl6.internode.on.net [121.45.123.141]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5ODajpK095717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 24 Jun 2008 23:06:45 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: John Baldwin Date: Tue, 24 Jun 2008 23:05:52 +0930 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806240946.58289.doconnor@gsoft.com.au> <200806240858.30701.jhb@freebsd.org> In-Reply-To: <200806240858.30701.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3022486.i9WRG70V65"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806242305.58996.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 13:36:48 -0000 --nextPart3022486.i9WRG70V65 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 24 Jun 2008, John Baldwin wrote: > > hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x02821106 > > chip=3D0x02821106 rev=3D0x00 hdr=3D0x00 vendor =3D 'VIA Technologies > > Inc' > > device =3D 'K8T880Pro CPU to PCI Bridge' > > class =3D bridge > > subclass =3D HOST-PCI > > cap 02[80] =3D AGP v3 SBA disabled > > cap 01[50] =3D powerspec 2 supports D0 D3 current D0 > > cap 08[60] =3D HT slave > > cap 08[58] =3D HT interrupt > > Ok, so this is the host side of AGP. Do you see any agpX devices in > devinfo -v output? Hmm yes I do.. pcib0 pnpinfo _HID=3DPNP0A03 _UID=3D1 at handle=3D\_SB_.PCI0 pci0 hostb0 pnpinfo vendor=3D0x1106 device=3D0x0282 subvendor=3D0x1106 s= ubdevice=3D0x0282 class=3D0x060000 at slot=3D0 function=3D0 agp0 hostb1 pnpinfo vendor=3D0x1106 device=3D0x1282 subvendor=3D0x0000 s= ubdevice=3D0x0000 class=3D0x060000 at slot=3D0 function=3D1 hostb2 pnpinfo vendor=3D0x1106 device=3D0x2282 subvendor=3D0x0000 s= ubdevice=3D0x0000 class=3D0x060000 at slot=3D0 function=3D2 hostb3 pnpinfo vendor=3D0x1106 device=3D0x3282 subvendor=3D0x0000 s= ubdevice=3D0x0000 class=3D0x060000 at slot=3D0 function=3D3 hostb4 pnpinfo vendor=3D0x1106 device=3D0x4282 subvendor=3D0x0000 s= ubdevice=3D0x0000 class=3D0x060000 at slot=3D0 function=3D4 hostb5 pnpinfo vendor=3D0x1106 device=3D0x7282 subvendor=3D0x0000 s= ubdevice=3D0x0000 class=3D0x060000 at slot=3D0 function=3D7 Nothing in /dev though.. [midget 22:56] ~ >ls -la /dev/agp* zsh: no match =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3022486.i9WRG70V65 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIYPg+5ZPcIHs/zowRAqZcAKCQqsTbqq4Uu2MnrtPr5vewk01x3gCeO3HC kDiXd1ZgSHNOsh+aIKCVBS0= =NqFq -----END PGP SIGNATURE----- --nextPart3022486.i9WRG70V65-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 14:43:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 725FB1065671 for ; Tue, 24 Jun 2008 14:43:39 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.freebsd.org (Postfix) with ESMTP id 37DE08FC18 for ; Tue, 24 Jun 2008 14:43:39 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from fw.publishing.hu ([82.131.181.62] helo=twoflower.in.publishing.hu) by marvin.harmless.hu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KB9k9-000LPU-OR for freebsd-stable@freebsd.org; Tue, 24 Jun 2008 16:43:37 +0200 Date: Tue, 24 Jun 2008 16:43:36 +0200 From: CZUCZY Gergely To: freebsd-stable@freebsd.org Message-ID: <20080624164336.0b717ce9@twoflower.in.publishing.hu> Organization: Harmless Digital X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/WOmC6NJMt3m4Llsp6WxYPe/"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: unable to installworld 7-STABLE: annot open unsorted21610: No such file or directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 14:43:39 -0000 --Sig_/WOmC6NJMt3m4Llsp6WxYPe/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I'm trying to build a 2-hour-ago csupped 7-STABLE, and I've got this error message during an installworld: cat /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/man/ncurses.3x > ncurses.3 sh /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/man/MKterminfo.sh = /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/man/terminfo.head /u= sr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include/Caps /usr/src/l= ib/ncurses/ncurses/../../../contrib/ncurses/man/terminfo.tail >terminfo.5 tr: not >found /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/man/MKterminfo= .sh: >cannot open unsorted21610: No such file or directory *** Error code 2 Stop in /usr/src/lib/ncurses/ncurses. *** Error code 1 I've tried to grep around, but haven't found anything near. What did I do wrong, what's the issue? How can I make this work? I've only got WITHOUT_IPV6 in my src.conf, and the KERNCONF=3DMYCONF variab= le set. It used to work with RELENG_7_0. --=20 Sincerely, Gergely CZUCZY --Sig_/WOmC6NJMt3m4Llsp6WxYPe/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFIYQgYzrC0WyuMkpsRAqDZAJ9ncj4V4AJxYNshjVzWz77xMhEg0ACfbyhU +NMx96J01tGnGhbaHPNHu58= =lUqg -----END PGP SIGNATURE----- --Sig_/WOmC6NJMt3m4Llsp6WxYPe/-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 17:39:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6AC31065672 for ; Tue, 24 Jun 2008 17:39:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 71C1B8FC29 for ; Tue, 24 Jun 2008 17:39:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5OHchRU047499; Tue, 24 Jun 2008 13:39:17 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Daniel O'Connor" Date: Tue, 24 Jun 2008 11:14:16 -0400 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806240858.30701.jhb@freebsd.org> <200806242305.58996.doconnor@gsoft.com.au> In-Reply-To: <200806242305.58996.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806241114.17140.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Tue, 24 Jun 2008 13:39:17 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7542/Mon Jun 23 12:42:14 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 17:39:24 -0000 On Tuesday 24 June 2008 09:35:52 am Daniel O'Connor wrote: > On Tue, 24 Jun 2008, John Baldwin wrote: > > > hostb0@pci0:0:0:0: class=0x060000 card=0x02821106 > > > chip=0x02821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies > > > Inc' > > > device = 'K8T880Pro CPU to PCI Bridge' > > > class = bridge > > > subclass = HOST-PCI > > > cap 02[80] = AGP v3 SBA disabled > > > cap 01[50] = powerspec 2 supports D0 D3 current D0 > > > cap 08[60] = HT slave > > > cap 08[58] = HT interrupt > > > > Ok, so this is the host side of AGP. Do you see any agpX devices in > > devinfo -v output? > > Hmm yes I do.. > pcib0 pnpinfo _HID=PNP0A03 _UID=1 at handle=\_SB_.PCI0 > pci0 > hostb0 pnpinfo vendor=0x1106 device=0x0282 subvendor=0x1106 subdevice=0x0282 class=0x060000 at slot=0 function=0 > agp0 > hostb1 pnpinfo vendor=0x1106 device=0x1282 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=1 > hostb2 pnpinfo vendor=0x1106 device=0x2282 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=2 > hostb3 pnpinfo vendor=0x1106 device=0x3282 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=3 > hostb4 pnpinfo vendor=0x1106 device=0x4282 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=4 > hostb5 pnpinfo vendor=0x1106 device=0x7282 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=7 > > Nothing in /dev though.. > [midget 22:56] ~ >ls -la /dev/agp* > zsh: no match And does kldstat -vv | grep agp show anything? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 21:53:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDCCD1065679; Tue, 24 Jun 2008 21:53:50 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9D9458FC0C; Tue, 24 Jun 2008 21:53:50 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5OLrhMF049681; Tue, 24 Jun 2008 17:53:44 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: James Gritton Date: Tue, 24 Jun 2008 15:55:48 -0400 User-Agent: KMail/1.9.7 References: <20080615112318.146C1F18512@mx.npubs.com> <200806231451.52340.jhb@freebsd.org> <485FF698.103@gritton.org> In-Reply-To: <485FF698.103@gritton.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806241555.48280.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Tue, 24 Jun 2008 17:53:44 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7542/Mon Jun 23 12:42:14 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 21:53:51 -0000 On Monday 23 June 2008 03:16:40 pm James Gritton wrote: > John Baldwin wrote: > > On Thursday 19 June 2008 11:57:51 am James Gritton wrote: > > > >> John Baldwin wrote: > >> > >>> On Sunday 15 June 2008 07:23:19 am Stef Walter wrote: > >>> > >>> > >>>> I've been trying to track down a deadlock on some newish production > >>>> servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a > >>>> specific (although mundane) hardware configuration, and each of several > >>>> servers running this hardware deadlock about once per week. > >>>> > >>>> Although I suspect that this is not hardware related, from a (naive) > >>>> perusal of the attached stack traces. > >>>> > >>>> Forgive me if my interpretation of this is all wrong, but I'm pretty > >>>> desperate for help. So here's my basic understanding of the deadlock: > >>>> > >>>> These processes seem to be waiting on the page queue mutex: > >>>> sendmail (in vm_mmap > vm_map_find > vm_map_insert > vm_map_pmap_enter) > >>>> bsnmpd (in malloc, uma_large_malloc > page_alloc > kmem_malloc) > >>>> httpd (in trap > trap_pfault > vm_fault) > >>>> [g_up] (in g_vfs_done > bufdone) > >>>> > >>>> The page queue mutex is held by rsync process: > >>>> rsync (in trap > trap_pfault > vm_fault > pmap_enter) > >>>> > >>>> Rsync kernel process (in pmap_enter) was interrupted while holding the > >>>> page queue lock? > >>>> > >>>> > >>>> Giant is enabled in loader.conf due to the needs of the pf firewall when > >>>> dealing with user credentials lookups. I do not believe that Giant plays > >>>> into this deadlock. Kernel config attached. > >>>> > >>>> Any and all help or info is welcome. Thanks in advance. > >>>> > >>>> > >>> Try this change: > >>> > >>> jhb 2007-10-27 22:07:40 UTC > >>> > >>> FreeBSD src repository > >>> > >>> Modified files: > >>> sys/kern sched_4bsd.c > >>> Log: > >>> Change the roundrobin implementation in the 4BSD scheduler to trigger a > >>> userland preemption directly from hardclock() via sched_clock() when a > >>> thread uses up a full quantum instead of using a periodic timeout to > >>> > > cause > > > >>> a userland preemption every so often. This fixes a potential deadlock > >>> when IPI_PREEMPTION isn't enabled where softclock blocks on a lock held > >>> by a thread pinned or bound to another CPU. The current thread on that > >>> CPU will never be preempted while softclock is blocked. > >>> > >>> Note that ULE already drives its round-robin userland preemption from > >>> sched_clock() as well and always enables IPI_PREEMPT. > >>> > >>> MFC after: 1 week > >>> > >>> Revision Changes Path > >>> 1.108 +8 -29 src/sys/kern/sched_4bsd.c > >>> > >>> We use it at work on 6.x. W/o this fix, round-robin stops working on 4BSD > >>> when softclock() (swi4: clock) blocks on a lock like Giant. > >>> > >>> > >> I've been seeing similar troubles on 6.2 and I'll have to give this a > >> try as we upgrade to 6.3. I notice "MFC after: 1 week" in the log; it's > >> been a week - any chance of seeing this fix rolled into 6.x? > >> > > > > If people confirm it fixes issues I will MFC it. There was some pushback when > > I first committed it so I waited on the MFC. > > I can confirm that on 6.3 I can recreate the deadlock without the patch, > and can't recreate it with the patch. Ok, I've merged it to RELENG_[67]. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 23:40:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 192DF106567E; Tue, 24 Jun 2008 23:40:20 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 60BAD8FC25; Tue, 24 Jun 2008 23:40:18 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-25-67.lns10.adl2.internode.on.net [121.45.25.67]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5ONe4Te047637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 25 Jun 2008 09:10:08 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: John Baldwin Date: Wed, 25 Jun 2008 09:09:20 +0930 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806242305.58996.doconnor@gsoft.com.au> <200806241114.17140.jhb@freebsd.org> In-Reply-To: <200806241114.17140.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart15373736.jLB9VpiEfz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806250909.48119.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2008 23:40:20 -0000 --nextPart15373736.jLB9VpiEfz Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 25 Jun 2008, John Baldwin wrote: > > Nothing in /dev though.. > > [midget 22:56] ~ >ls -la /dev/agp* > > zsh: no match > > And does kldstat -vv | grep agp show anything? Yes. [midget 9:01] ~ >kldstat -vv| grep agp 438 hostb/agp_ali 439 hostb/agp_amd 440 hostb/agp_amd64 441 hostb/agp_ati 442 vgapci/agp_i810 443 hostb/agp_intel 444 hostb/agp_nvidia 445 hostb/agp_sis 446 hostb/agp_via The nvidia kld doesn't seem to 'see' the AGP either, ie.. hw.nvidia.agp.status.status: disabled hw.nvidia.agp.status.driver: n/a (unused) hw.nvidia.agp.status.rate: n/a (disabled) hw.nvidia.agp.status.fw: n/a (disabled) hw.nvidia.agp.status.sba: n/a (disabled) hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 15:42:= 45 PST 2008 Although maybe that relates to the NVIDIA AGP code, rather that code that uses it. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart15373736.jLB9VpiEfz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIYYXD5ZPcIHs/zowRAvcLAJkBxpIOmcMYBcjS29EGxYA7eJTKGACggNeJ M6XkKbnlERsYRrU2h8kPeuw= =t5bJ -----END PGP SIGNATURE----- --nextPart15373736.jLB9VpiEfz-- From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 01:06:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82644106567E for ; Wed, 25 Jun 2008 01:06:46 +0000 (UTC) (envelope-from baigsabeeh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7628FC18 for ; Wed, 25 Jun 2008 01:06:46 +0000 (UTC) (envelope-from baigsabeeh@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1547779pyb.10 for ; Tue, 24 Jun 2008 18:06:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=XyD9Sx+Sdnd6GuqKeNvAdNn2EdrZLnRog0gtnL3qqrk=; b=eCfYOLvu9QHXSehsk6qrRq6qYhSFlVF6/bmF9/KF5bqJJbIl9laft4QpzfqCrblaCd Ry32NVJXb3CXyRJhgA9oE38Ut5hdbxj7yjdYJwyxCOzw2/CcL1i3G3UBM+MLH5yIvdsL 09U+mZf7pco8gnpD09DCTRNYQUJwnNLBa2Vmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=bluvpnZ2YiPbn09bnxytVXpdVsE1OskjoSGL19bZ1Y9GVo2PfApQytXWYyaykseOby 52iEBedax6fKOKvBLW/bfhbr5fo0UQNx9k/3hQIgIMGYLPI53HXgZr1jmFIv6Hv+4EbB mHNFVkYLV7na7w2THMdl07dmcooAORVnT52YM= Received: by 10.141.23.7 with SMTP id a7mr15745750rvj.58.1214354425264; Tue, 24 Jun 2008 17:40:25 -0700 (PDT) Received: by 10.114.58.13 with HTTP; Tue, 24 Jun 2008 17:40:25 -0700 (PDT) Message-ID: Date: Tue, 24 Jun 2008 20:40:25 -0400 From: "Sabeeh Baig" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: bus_dmamem_alloc failed to align memory properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 01:06:46 -0000 >Still hoping for an answer, as the PC locked up hard a few more times, >always when trying to exit the X server (normal logout/all clients >terminated, ctl-alt-bs, init 6). The PC is a Dell Optiplex 740. Its >onboard video is NVidia NVS 210S nVidia GForce 6150, but that is >disabled when an add-in video card is present (wasn't present in the >'pciconf -lv' I posted last week). >What can I do to determine whether the X11 problem is >"bus_dmamem_alloc failed to align memory properly" or something >else with the card? What driver are you using? Radeons don't exactly play well with FreeBSD at the moment. They hardly ever have. Have you tried using just the Vesa driver to see if it really is a driver issue? The driver might be the root of the problems because the radeonhd doesn't support older cards. Sabeeh Ahmed Baig From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 09:23:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 172CA1065678; Wed, 25 Jun 2008 09:23:54 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 08F428FC1E; Wed, 25 Jun 2008 09:23:53 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [172.16.12.8] (covad-jrhett.meer.net [209.157.140.144]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m5P9NnNI049720; Wed, 25 Jun 2008 02:23:51 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -3.427 X-Spam-Level: X-Spam-Status: No, score=-3.427 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=-1.987] Message-Id: From: Jo Rhett To: John Baldwin In-Reply-To: <200806231051.03685.jhb@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Wed, 25 Jun 2008 02:23:48 -0700 References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> X-Mailer: Apple Mail (2.924) Cc: FreeBSD Stable Subject: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 09:23:54 -0000 On Jun 23, 2008, at 7:51 AM, John Baldwin wrote: > FWIW, Yahoo! tracks -stable branches, not point releases. I'm curious about this (and stealing the dead thread). How does one track -stable in an enterprise environment? I assume that what you mean is "we pick points in -stable that we believe are stable enough and create a snapshot from this point that we test and roll out to production" ...? Am I wrong? I mean, I guess Yahoo has enough resources to literally run every commit to -stable through a full test cycle and push it out to every machine, but my mind boggles to imagine the manpower cost of doing so. (and to justify the manpower cost versus the gain from doing so...) -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 11:01:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27B3B1065672 for ; Wed, 25 Jun 2008 11:01:23 +0000 (UTC) (envelope-from peter@wemm.org) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.240]) by mx1.freebsd.org (Postfix) with ESMTP id E6A638FC1C for ; Wed, 25 Jun 2008 11:01:22 +0000 (UTC) (envelope-from peter@wemm.org) Received: by ag-out-0708.google.com with SMTP id 8so24309551agc.3 for ; Wed, 25 Jun 2008 04:01:22 -0700 (PDT) Received: by 10.100.201.9 with SMTP id y9mr18160094anf.60.1214390771488; Wed, 25 Jun 2008 03:46:11 -0700 (PDT) Received: by 10.100.154.11 with HTTP; Wed, 25 Jun 2008 03:46:11 -0700 (PDT) Message-ID: Date: Wed, 25 Jun 2008 03:46:11 -0700 From: "Peter Wemm" To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> Cc: FreeBSD Stable , John Baldwin Subject: Re: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 11:01:23 -0000 On Wed, Jun 25, 2008 at 2:23 AM, Jo Rhett wrote: > On Jun 23, 2008, at 7:51 AM, John Baldwin wrote: >> >> FWIW, Yahoo! tracks -stable branches, not point releases. > > > I'm curious about this (and stealing the dead thread). > > How does one track -stable in an enterprise environment? I assume that what > you mean is "we pick points in -stable that we believe are stable enough and > create a snapshot from this point that we test and roll out to production" > ...? Am I wrong? Correct. We roll our own build snapshots periodically, but we also keep a pretty careful eye on what's going on in the -stable branches. When I say "we", I mostly mean John does it. :) Quite often the biggest factor that tells us when to roll a new internal release is when there's something that has gone into -stable that we want. We have many local modifications, so freebsd.org's concept of a "release" is pretty much meaningless to us. However, we do quietly help in freebsd.org's release process. We make a point of trying to run some recent snapshots in production in the leadup to a freebsd.org release. This helps shake out silly problems that might not get noticed in time. > I mean, I guess Yahoo has enough resources to literally run every commit to > -stable through a full test cycle and push it out to every machine, but my > mind boggles to imagine the manpower cost of doing so. (and to justify the > manpower cost versus the gain from doing so...) No. Why on earth would we do that? if we wanted to cause ourselves that much pain for no good reason, we'd go get a pencil and stab ourselves in the eye. We don't upgrade machines that have been deployed unless there is a good reason to. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 11:07:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99EA4106567A for ; Wed, 25 Jun 2008 11:07:15 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB278FC14 for ; Wed, 25 Jun 2008 11:07:14 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1639088fgb.35 for ; Wed, 25 Jun 2008 04:07:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=F5MYLYEm8j8BvCN7ymTNdtujGX68K8ROs2+J/gMkc2g=; b=eyO5QinKt8YTkdISm0RWrg4VPhKkns+DhVEbBXtdum7KNtibZrjqCTCUVGb/ohMids hZvki4y4xupRCY1b92NlIzPDkykkXK0uHdo6RAr8F8wEzsto4vsCXCPL9kdRq9AgtFRv QD1X8tgaLvMapMDvRW7SQxp8hYhSO5ngp1G0w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MBj/STXcTDgbwujjjbD5erZ4CE/bYb+uv4xJQo/yCR0moPazyYTBqurO/8l0qPT4rj iSakHTVNPHxImXXVNegZAw9y0zJkieWvMMb8ljzXU+lv5T2XR+n+oHQzZye+85B+bM1+ KRoxMv7juVB7WWU5bwAKnp8m9rwoAH1u8DIZ4= Received: by 10.86.36.11 with SMTP id j11mr10294126fgj.7.1214392033839; Wed, 25 Jun 2008 04:07:13 -0700 (PDT) Received: by 10.86.79.5 with HTTP; Wed, 25 Jun 2008 04:07:13 -0700 (PDT) Message-ID: Date: Wed, 25 Jun 2008 13:07:13 +0200 From: "Claus Guttesen" To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> Cc: FreeBSD Stable , John Baldwin Subject: Re: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 11:07:15 -0000 >> FWIW, Yahoo! tracks -stable branches, not point releases. > > I'm curious about this (and stealing the dead thread). > > How does one track -stable in an enterprise environment? I assume that what > you mean is "we pick points in -stable that we believe are stable enough and > create a snapshot from this point that we test and roll out to production" > ...? Am I wrong? > > I mean, I guess Yahoo has enough resources to literally run every commit to > -stable through a full test cycle and push it out to every machine, but my > mind boggles to imagine the manpower cost of doing so. (and to justify the > manpower cost versus the gain from doing so...) I only have a handfull of web-servers so I do a 'make buildworld' and -kernel on one server and then nfs-mount it from the other servers (remember mount-root-option if doing this). I don't have any problems running stable if it works. So I usually just upgrade one server to whatever stable is at that moment and if it runs without problems for a while I upgrade the remaining servers a few days apart. When it comes to our db-server I usually track release, but since my web-servers and db-server is the same hardware I'm somewhat confident that an upgrade to stable will work if the need to do so arises. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 13:40:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1CB01065674 for ; Wed, 25 Jun 2008 13:40:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 974638FC18 for ; Wed, 25 Jun 2008 13:40:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5PDedo4058508; Wed, 25 Jun 2008 09:40:40 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Daniel O'Connor" Date: Wed, 25 Jun 2008 09:19:04 -0400 User-Agent: KMail/1.9.7 References: <200806172120.41978.doconnor@gsoft.com.au> <200806241114.17140.jhb@freebsd.org> <200806250909.48119.doconnor@gsoft.com.au> In-Reply-To: <200806250909.48119.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806250919.04669.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Wed, 25 Jun 2008 09:40:40 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7542/Mon Jun 23 12:42:14 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: AGP bridge detected as pcib X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 13:40:47 -0000 On Tuesday 24 June 2008 07:39:20 pm Daniel O'Connor wrote: > On Wed, 25 Jun 2008, John Baldwin wrote: > > > Nothing in /dev though.. > > > [midget 22:56] ~ >ls -la /dev/agp* > > > zsh: no match > > > > And does kldstat -vv | grep agp show anything? > > Yes. > [midget 9:01] ~ >kldstat -vv| grep agp > 438 hostb/agp_ali > 439 hostb/agp_amd > 440 hostb/agp_amd64 > 441 hostb/agp_ati > 442 vgapci/agp_i810 > 443 hostb/agp_intel > 444 hostb/agp_nvidia > 445 hostb/agp_sis > 446 hostb/agp_via I would add start adding printfs to the amd64 probe adn attach routines. Note that in 7.0 because of the hostb changes you can now kldload agp after boot which may aid in testing. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 15:03:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EC40106567A for ; Wed, 25 Jun 2008 15:03:36 +0000 (UTC) (envelope-from kjblack@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182]) by mx1.freebsd.org (Postfix) with ESMTP id C3D6A8FC1F for ; Wed, 25 Jun 2008 15:03:35 +0000 (UTC) (envelope-from kjblack@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so361143ele.13 for ; Wed, 25 Jun 2008 08:03:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=VMji0Y+n3DZPtfCuRMKUruxeDI4by7NL+yE7wnahvqk=; b=GssmegyU4YjlfM5dn4lzCx7ARjRHWc+XMbJtk7hqa+Au4b4al6owadsxhS2yyN85x3 aP0euRLGYQ0aEl6L+4I1jATvdsqhD5zzitOOnuutSBJVry8wD0Ixu6NUqMpodBS4Gjcg TUZKHy2C3NSnS/ucQX1SOuxBWTjz2ZHh/Y5AU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=r7M22U94Jq0qTS3GlcqLF6MD5U4JfdnebovjAsSRfvKtKYXMua3w9Ad2HeEbkRpmbX O1qBiHQ2QIGYG+Xi95mJxpEAZQ4ZhlwpaoTxURbLXfeGNtx9HWmXUBI2oRfTOTr20I0y dIK8zB03DgOOoSdMo6Elf9I4zM1hMQzHjwwmw= Received: by 10.143.11.15 with SMTP id o15mr6875526wfi.227.1214404712861; Wed, 25 Jun 2008 07:38:32 -0700 (PDT) Received: by 10.151.154.9 with HTTP; Wed, 25 Jun 2008 07:38:32 -0700 (PDT) Message-ID: <1b1b33f10806250738y55fc8437l8e26c9c1698ea364@mail.gmail.com> Date: Wed, 25 Jun 2008 10:38:32 -0400 From: "Kelly Black" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 15:03:36 -0000 Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make installworld mergemaster Now when I reboot there is a problem. I get an error that the system cannot boot. Part of it looks like this: Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: If I boot from a live disk and replace /boot/loader with /boot/loader.old it boots up fine and everything looks good. A new world and a new kernel. I would be grateful for any help or any pointers. Sincerely, Kel PS I do not do anything special with my loader config files: $ cat loader.conf snd_ich_load="YES" $ cat loader.rc \ Loader.rc \ $FreeBSD: src/sys/boot/i386/loader/loader.rc,v 1.4 2005/10/30 05:41:42 scottl Exp $ \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.conf variables start \ Tests for password -- executes autoboot first if a password was defined check-password \ Load in the boot menu include /boot/beastie.4th \ Start the boot menu beastie-start -- _______________________________________________________ Kelly Black Phone: (518) 388-8727 Department of Mathematics FAX: (603) 388-6005 Union College e-mail: kelly.black@union.edu Schenectady NY 12308 (USA) WWW: http://blackk.union.edu/~black From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 15:09:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4051E1065675; Wed, 25 Jun 2008 15:09:29 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id F22238FC1D; Wed, 25 Jun 2008 15:09:28 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KBWch-000CvG-NU; Wed, 25 Jun 2008 18:09:27 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: =?iso-8859-1?Q?S=F8ren?= Schmidt In-reply-to: Your message of Tue, 24 Jun 2008 13:51:58 +0300 . Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jun 2008 18:09:27 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: ata on alix/geode stopped being detcted. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 15:09:29 -0000 > hi, > latest changes in dev/ata broke this, on older -stable> ... > ata0-master: pio=3DPIO4 wdma=3DUNSUPPORTED udma=3DUNSUPPORTED cable=3D4= 0 =3Dwire > ad0: success setting PIO4 on National chip > ad0: 977MB at ata0-master PIO4 >=20 > on latest -stable: > ata0-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUNSUPPORTED cable=3D40 wire= >=20 > and no disk. >=20 > cheers, > danny problem solved: somehow 'device atadisk' was lost from the kernel configuration file ata0-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUNSUPPORTED cable=3D40 wire ad0: setting PIO4 on CS5536 chip ad0: setting WDMA2 on CS5536 chip ad0: 1953MB at ata0-master WDMA2 ad0: 4001760 sectors =5B3970C/16H/63S=5D 4 sectors/interrupt 1 depth queu= e danny From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 16:16:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41290106564A for ; Wed, 25 Jun 2008 16:16:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.188]) by mx1.freebsd.org (Postfix) with ESMTP id F3C548FC1E for ; Wed, 25 Jun 2008 16:16:54 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so840071rne.12 for ; Wed, 25 Jun 2008 09:16:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=OxzxYJ8FLNvBatP21cx1kEhYEcbRBHvjBCX0kz51zEE=; b=n0PJ5PeENxvJcBNVxMBQ4GQmiacx1pOEN7wDjt9xIq8gmt4reLrk2Z70slEAfFs8Ou BzXmRUXeAMQG1Ua8wkNThsI5Oi305aWdbnOW6VQrscKiKtY6MS6sb0s46i0wBJiXi6e1 VV8jmFWK50/x2+Ko5uEWl30Wkp1c/4vrpfpIU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Vfaz02kK6E9NVLiDB6IWzuY+80uZmueZXocTKcNw3xN6LvzsWU5EXAy9qqUgPgQxyY uqQOqrKbUZsxLGGH+cgPcZjc3ibvJaguH/jOfVuxZRY9LZYa8J2jQZMI0GGE/3+xuYXO i9f6EWgikMPCipuIYMao4RaT+dsY/vNn06tXU= Received: by 10.142.128.6 with SMTP id a6mr7032566wfd.68.1214410612564; Wed, 25 Jun 2008 09:16:52 -0700 (PDT) Received: by 10.151.51.5 with HTTP; Wed, 25 Jun 2008 09:16:52 -0700 (PDT) Message-ID: Date: Wed, 25 Jun 2008 09:16:52 -0700 From: "Freddie Cash" To: "FreeBSD Stable" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> Subject: Re: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 16:16:55 -0000 On Wed, Jun 25, 2008 at 4:07 AM, Claus Guttesen wrote: >>> FWIW, Yahoo! tracks -stable branches, not point releases. >> >> I'm curious about this (and stealing the dead thread). >> >> How does one track -stable in an enterprise environment? I assume that what >> you mean is "we pick points in -stable that we believe are stable enough and >> create a snapshot from this point that we test and roll out to production" >> ...? Am I wrong? >> [snip] > > I only have a handfull of web-servers so I do a 'make buildworld' and > -kernel on one server and then nfs-mount it from the other servers > (remember mount-root-option if doing this). I don't have any problems > running stable if it works. So I usually just upgrade one server to > whatever stable is at that moment and if it runs without problems for > a while I upgrade the remaining servers a few days apart. That's pretty much what we do as well, here in the local school district. We track the -stable and -current mailing lists, read all the Head's Up messages, and read through cvsweb logs for the devices/apps we're interested in. When there's a commit that interests us, we update the source tree to after that commit, run through the buildworld cycle on a test box, make sure everything works over a few days/weeks, and then export /usr/obj and /usr/src to the systems we want to upgrade. It's not all that time consuming, even though it's just me doing the work. > When it comes to our db-server I usually track release, but since my > web-servers and db-server is the same hardware I'm somewhat confident > that an upgrade to stable will work if the need to do so arises. We keep all our server hardware as identical as possible, which greatly simplifies things. We have four hardware profiles that run FreeBSD, and only two of those track -STABLE. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 16:19:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB69A1065671 for ; Wed, 25 Jun 2008 16:19:47 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.186]) by mx1.freebsd.org (Postfix) with ESMTP id 6A2348FC20 for ; Wed, 25 Jun 2008 16:19:47 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so841509rne.12 for ; Wed, 25 Jun 2008 09:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cwy1gj8V59S5cEBKCZwP8t39Q+DR18ggJ1LV0zESQyM=; b=euIAoJZ4HZRnOzc4n1VEwjxzS8gCZJjrsr8zfo3mEW+tFTtbfvrpSbpZTOZvI0pQFe 1XYGY7cN6WALyCWkaFs61j5f/yKG4A6WLoauUHx3gZeQgPmk5V0AEDQRiIUU8dTHBUNV d96KlI6kNhUkEF0hlqdRbMekWQ23xuo+8DWrc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=jWVk8+cSw9hFurJZUHq2vJ3uGC0T+lLjsZMkKe76zXbxUd1RGkWisi/QhsmeJ2Xyez lj9ngiEF4m8IznO78IlXcthJ5Wajdz+GjmArZdNc9dgZRp98iO0vSVicnnPvIwJ5smWG c9Djn326FXVtCfW1zMr1E4VqTGvnFIPacFAzM= Received: by 10.142.212.19 with SMTP id k19mr7005723wfg.142.1214410786027; Wed, 25 Jun 2008 09:19:46 -0700 (PDT) Received: by 10.151.51.5 with HTTP; Wed, 25 Jun 2008 09:19:45 -0700 (PDT) Message-ID: Date: Wed, 25 Jun 2008 09:19:45 -0700 From: "Freddie Cash" To: "FreeBSD Stable" In-Reply-To: <1b1b33f10806250738y55fc8437l8e26c9c1698ea364@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1b1b33f10806250738y55fc8437l8e26c9c1698ea364@mail.gmail.com> Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 16:19:47 -0000 On Wed, Jun 25, 2008 at 7:38 AM, Kelly Black wrote: > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > Now when I install world there is a problem booting. > > Here is what I do: [snip] > Now when I reboot there is a problem. I get an error that the system > cannot boot. Part of it looks like this: > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > If I boot from a live disk and replace /boot/loader with > /boot/loader.old it boots up fine and everything looks good. A new > world and a new kernel. I would be grateful for any help or any > pointers. What do you have in /etc/make.conf? I recall there being a point in time where incorrect CFLAGS options could build a broken loader. Try renaming /etc/make.conf (or just commenting out all CFLAGS/CXXFLAGS options) and rebuilding either just the loader or the whole world, and see if that makes a difference. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 18:58:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DC131065670 for ; Wed, 25 Jun 2008 18:58:52 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from a.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0D8CC8FC12 for ; Wed, 25 Jun 2008 18:58:51 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from [127.0.0.1] (localhost [127.0.0.1]) by a.cs.okstate.edu (Postfix) with ESMTP id 82C27154CE9 for ; Wed, 25 Jun 2008 13:27:54 -0500 (CDT) Message-ID: <48628E28.7080004@cs.okstate.edu> Date: Wed, 25 Jun 2008 13:27:52 -0500 From: Reid Linnemann User-Agent: Thunderbird 2.0.0.6 (X11/20070926) MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: READ_DMA timeouts, etc. on FreeBSD 7-STABLE SATA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 18:58:52 -0000 Hi guys, I'm running 7-STABLE, last synced early June (June 7 I think). I have two SATA disks, identical 160G Western Digital WD1600AAJS on a SiS 180 SATA controller that are gmirrored, and the mirror provides all of my individual filesystems. After I built the mirror in single user mode and rebooted, I started getting DMA errors such as: Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2830976 Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2901888 Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2995328 The LBA is apparently random. Most of the time this just makes the machine crawl and is annoying, but if, say, a filesystem were removed uncleanly from a power failure, the combined activity of the mirror rebuilding and the fsck cause much more disconcerting errors, eg: Jun 21 11:48:46 hautlos kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=196200751 Jun 21 11:49:02 hautlos kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=196442127 But, now for the weird part... I tried booting in single user mode, disabling DMA, and disabling ACPI, to no avail. Soft boot, hard boot, doesn't matter. But - if I power the machine down, cut power to the power supply, and cycle the remaining juice through the system by hitting the ATX power on, and then boot up, the DMA errors completely or nearly completely vanish. Since I did this on Jun 21 I have logged only 2 READ_DMA timeouts: messages:Jun 22 03:02:15 hautlos kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=56884207 messages:Jun 24 10:52:41 hautlos kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=243514511 Does anyone have any ideas? I've googled but can't find any solutions. I'm not currently subscribed to stable@, so please cc: me in responses. My uname -a and dmesg follows. FreeBSD hautlos 7.0-STABLE FreeBSD 7.0-STABLE #7: Sat Jun 7 10:46:48 CDT 2008 root@:/usr/obj/usr/src/sys/HAUTLOS i386 Copyright (c) 1992-2008 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 7.0-STABLE #7: Sat Jun 7 10:46:48 CDT 2008 root@:/usr/obj/usr/src/sys/HAUTLOS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1999.44-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 real memory = 1073676288 (1023 MB) avail memory = 1037291520 (989 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3fef0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10df,0x10e0-0x10ff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xd000-0xd0ff mem 0xd0000000-0xd7ffffff,0xe8020000-0xe802ffff irq 16 at device 0.0 on pci1 vgapci1: mem 0xd8000000-0xdfffffff,0xe8030000-0xe803ffff at device 0.1 on pci1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f at device 2.5 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcm0: port 0xe000-0xe0ff,0xe100-0xe17f irq 18 at device 2.7 on pci0 pcm0: [ITHREAD] pcm0: ohci0: mem 0xe8124000-0xe8124fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe8120000-0xe8120fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] hci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xe8121000-0xe8121fff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xe8122000-0xe8122fff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 8 ports with 8 removable, self powered umass0: on uhub3 sis0: port 0xe200-0xe2ff mem 0xe8123000-0xe8123fff irq 19 at device 4.0 on pci0 miibus0: on sis0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:14:2a:68:cf:ff sis0: [ITHREAD] atapci1: port 0xe300-0xe307,0xe400-0xe403,0xe500-0xe507,0xe600-0xe603,0xe700-0xe70f irq 17 at device 5.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ahc0: port 0xe800-0xe8ff mem 0xe8125000-0xe8125fff irq 16 at device 12.0 on pci0 ahc0: [ITHREAD] aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xccfff,0xd0000-0xd7fff,0xd8000-0xd87ff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 ppc0: at port 0x378-0x37f on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: on uhub0 kbd2 at ukbd0 uhid0: on uhub0 ugen0: on uhub2 Timecounter "TSC" frequency 1999440640 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDRW at ata0-master UDMA33 ad4: 152627MB at ata2-master SATA150 ad6: 152627MB at ata3-master SATA150 GEOM_MIRROR: Device mirror/gm0 launched (2/2). Waiting 2 seconds for SCSI devices to settle da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1936MB (991232 2048 byte sectors: 255H 63S/T 61C) GEOM_LABEL: Label for provider da0 is label/ipod. GEOM_LABEL: Label for provider da0s2 is msdosfs/IPOD. Trying to mount root from ufs:/dev/mirror/gm0s1a drm0: on vgapci0 info: [drm] AGP at 0xe0000000 128MB info: [drm] Initialized radeon 1.25.0 20060524 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] powernow0: on cpu0 From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 19:21:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D3EE106567B; Wed, 25 Jun 2008 19:21:29 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 26C498FC2C; Wed, 25 Jun 2008 19:21:28 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m5PJLQT7078362; Wed, 25 Jun 2008 12:21:26 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -0.898 X-Spam-Level: X-Spam-Status: No, score=-0.898 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.542] Message-Id: <15C7C9E0-7F99-4FAC-941A-9BBCC3600E55@netconsonance.com> From: Jo Rhett To: Peter Wemm In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Wed, 25 Jun 2008 12:21:21 -0700 References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> X-Mailer: Apple Mail (2.924) Cc: FreeBSD Stable , John Baldwin Subject: Re: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 19:21:29 -0000 On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: > Correct. We roll our own build snapshots periodically, but we also > keep a pretty careful eye on what's going on in the -stable branches. Okay, that makes sense to me ;-) >> I mean, I guess Yahoo has enough resources to literally run every >> commit to >> -stable through a full test cycle and push it out to every machine, >> but my > No. Why on earth would we do that? if we wanted to cause ourselves > that much pain for no good reason, we'd go get a pencil and stab > ourselves in the eye. Yes, we are definitely on the same page. Thanks for the clarification ;-) > We don't upgrade machines that have been deployed unless there is a > good reason to. Do you deploy machines for longer than 1 year? How do you deal with security patches in the longer term? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 20:35:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DED9E106566B for ; Wed, 25 Jun 2008 20:35:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id D2CE48FC14 for ; Wed, 25 Jun 2008 20:35:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id B62641CC038; Wed, 25 Jun 2008 13:35:25 -0700 (PDT) Date: Wed, 25 Jun 2008 13:35:25 -0700 From: Jeremy Chadwick To: Reid Linnemann Message-ID: <20080625203525.GA52663@eos.sc1.parodius.com> References: <48628E28.7080004@cs.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48628E28.7080004@cs.okstate.edu> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: "freebsd-stable@freebsd.org" Subject: Re: READ_DMA timeouts, etc. on FreeBSD 7-STABLE SATA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 20:35:26 -0000 On Wed, Jun 25, 2008 at 01:27:52PM -0500, Reid Linnemann wrote: > Does anyone have any ideas? I've googled but can't find any solutions. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues And I've begun to make a separate page solely for ATA/SATA issues, which is still *very* much under development. The DMA and timeout issues you see are listed on that page. http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting If the LBA changes, then chances are it's not your disks. SMART stats might help validate/refute that. Otherwise, sorry that there's no solution, but rest assured, you're not alone. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 20:55:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81701106567D for ; Wed, 25 Jun 2008 20:55:21 +0000 (UTC) (envelope-from ru@freebsd.org) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3E0178FC15 for ; Wed, 25 Jun 2008 20:55:20 +0000 (UTC) (envelope-from ru@freebsd.org) Received: from [87.242.97.68] (port=60808 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1KBbjw-0007aL-RR; Wed, 25 Jun 2008 20:37:16 +0000 Date: Thu, 26 Jun 2008 00:36:59 +0400 From: Ruslan Ermilov To: Mars G Miro Message-ID: <20080625203659.GC69011@edoofus.dev.vega.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-stable@freebsd.org Subject: Re: no more src/compat and install.sh X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 20:55:21 -0000 On Tue, Jun 24, 2008 at 05:56:37PM +0800, Mars G Miro wrote: > Greetz, > > src/compat was repocopied to src/cddl/compat about > 2months ago. I > think we need to remove for good 'compat' in > src/release/scripts/src-install.sh. > Fixed, thanks. -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 00:33:10 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3130106566B for ; Thu, 26 Jun 2008 00:33:10 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (angel.ticketswitch.com [87.224.29.78]) by mx1.freebsd.org (Postfix) with ESMTP id 7BCD08FC18 for ; Thu, 26 Jun 2008 00:33:10 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KBeza-0000v2-Ne for stable@freebsd.org; Thu, 26 Jun 2008 01:05:38 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KBeza-000NBE-9m for stable@freebsd.org; Thu, 26 Jun 2008 01:05:38 +0100 To: stable@freebsd.org Message-Id: From: Pete French Date: Thu, 26 Jun 2008 01:05:38 +0100 Cc: Subject: 6to4 suddenly stopped working to 2001: addresses X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 00:33:10 -0000 I've got three installations of FreeBSD using 6to4 in three different physical locations, attached to three different ISPs. Sometime in the last few days all of them have stopped talking to IPv6 addesse which are not also 6to4. I can still talk to 2002: addresses, but not to 2001: addresses. This all worked fine a few days ago, and nothing has changed in the config of any of these machines. I can ping 192.88.99.1 under IPv4, so I should have a route to 2002:c390:806::, but traceroute6 to anything not in 2002: doesnt show any hops, and I cannot connect to any of these sites. Can anyone shed any light on this ? It hardly seems likely that theres been some massive failure of 6to4 in the London area, but I can't see any reason why all of this would have suddenly stopped working. -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 01:02:32 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 332C5106567E for ; Thu, 26 Jun 2008 01:02:32 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by mx1.freebsd.org (Postfix) with ESMTP id E32878FC12 for ; Thu, 26 Jun 2008 01:02:31 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m5Q12UUq003879; Thu, 26 Jun 2008 11:02:30 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200806260102.m5Q12UUq003879@drugs.dv.isc.org> To: Pete French From: Mark Andrews In-reply-to: Your message of "Thu, 26 Jun 2008 01:05:38 +0100." Date: Thu, 26 Jun 2008 11:02:30 +1000 Sender: marka@isc.org Cc: stable@freebsd.org Subject: Re: 6to4 suddenly stopped working to 2001: addresses X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 01:02:32 -0000 > I've got three installations of FreeBSD using 6to4 in three different > physical locations, attached to three different ISPs. Sometime in the last > few days all of them have stopped talking to IPv6 addesse which are > not also 6to4. I can still talk to 2002: addresses, but not to 2001: > addresses. > > This all worked fine a few days ago, and nothing has changed in the config of > any of these machines. I can ping 192.88.99.1 under IPv4, so I should > have a route to 2002:c390:806::, but traceroute6 to anything not in > 2002: doesnt show any hops, and I cannot connect to any of these sites. You need to talk to the operators of the last hop before 192.88.99.1 in the traceroute. > Can anyone shed any light on this ? It hardly seems likely that theres > been some massive failure of 6to4 in the London area, but I can't > see any reason why all of this would have suddenly stopped working. > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 07:59:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A562106564A for ; Thu, 26 Jun 2008 07:59:14 +0000 (UTC) (envelope-from peter@wemm.org) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 24B878FC1E for ; Thu, 26 Jun 2008 07:59:14 +0000 (UTC) (envelope-from peter@wemm.org) Received: by an-out-0708.google.com with SMTP id b33so970897ana.13 for ; Thu, 26 Jun 2008 00:59:13 -0700 (PDT) Received: by 10.100.31.3 with SMTP id e3mr20023763ane.64.1214467153673; Thu, 26 Jun 2008 00:59:13 -0700 (PDT) Received: by 10.100.154.11 with HTTP; Thu, 26 Jun 2008 00:59:13 -0700 (PDT) Message-ID: Date: Thu, 26 Jun 2008 00:59:13 -0700 From: "Peter Wemm" To: "Jo Rhett" In-Reply-To: <15C7C9E0-7F99-4FAC-941A-9BBCC3600E55@netconsonance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> <15C7C9E0-7F99-4FAC-941A-9BBCC3600E55@netconsonance.com> Cc: FreeBSD Stable , John Baldwin Subject: Re: tracking -stable in the enterprise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 07:59:14 -0000 On Wed, Jun 25, 2008 at 12:21 PM, Jo Rhett wrote: > On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: >> >> Correct. We roll our own build snapshots periodically, but we also >> keep a pretty careful eye on what's going on in the -stable branches. > > Okay, that makes sense to me ;-) > >>> I mean, I guess Yahoo has enough resources to literally run every commit >>> to >>> -stable through a full test cycle and push it out to every machine, but >>> my > >> No. Why on earth would we do that? if we wanted to cause ourselves >> that much pain for no good reason, we'd go get a pencil and stab >> ourselves in the eye. > > Yes, we are definitely on the same page. Thanks for the clarification ;-) > >> We don't upgrade machines that have been deployed unless there is a >> good reason to. > > Do you deploy machines for longer than 1 year? How do you deal with > security patches in the longer term? I think we still have FreeBSD-3.x machines in production. I know we have FreeBSD-4.3. 99.9% of security issues don't affect us. We have our own package system built on top of FreeBSD's pkg_add format and have the ability to push packages to machines. If circumstances warrant it, we can push a fix for something. It'll either push a new binary or be a source patch that is compiled directly on the machines in question. The machines run a custom software stack. More often we push fixes for driver or performance fixes or things like timezone updates. The important thing is that we don't disturb machines that are running happily. Hardware vendors are constantly messing with firmware, bugs in silicon, etc etc. This is an issue for NEW installs, usually not existing machines. Usually. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 08:35:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 168C11065670 for ; Thu, 26 Jun 2008 08:35:42 +0000 (UTC) (envelope-from rajkumars@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id BF8948FC19 for ; Thu, 26 Jun 2008 08:35:41 +0000 (UTC) (envelope-from rajkumars@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1088796ywe.13 for ; Thu, 26 Jun 2008 01:35:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=rkflUbw3vFOjpMkht0wvSJlumY+toBLw5dDXU6jL6k8=; b=Ys1TYzolpKVwXhm7wyi2EK2bMCccbUAcbN5J04aSJgHgDytpnAtkcuNrINMu4x58b2 +5xj7Ds8YPrXugK0u98WbXxUpDw6GHqlyJe/TVY8urX2zD3WOsDwgUdj6U9JrheZptOc kJooAtJrntxbgeM0VmwPT2Ygq2pMJ901eKrcU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=GD0XNXgT3CodOeJnyn246QqcKW7WV71aAppswB/3OYC37kd5VM7dlN4r0m4XWLaepk 1+YjN9tdC1Od8RHdLsqRGpf+KJfZ8NwSzLqz5hqcUcjQtJuHn06/PDaZKXJPWser0c6X h+LjQ1cww5gvKPQJbosxAwt3FSZGsxogGrz4E= Received: by 10.151.99.17 with SMTP id b17mr1386143ybm.190.1214467851396; Thu, 26 Jun 2008 01:10:51 -0700 (PDT) Received: by 10.150.190.8 with HTTP; Thu, 26 Jun 2008 01:10:51 -0700 (PDT) Message-ID: <64de5c8b0806260110k72470558gbbf237f42308e06d@mail.gmail.com> Date: Thu, 26 Jun 2008 13:40:51 +0530 From: "Rajkumar S" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: make buildworld fails on a RELENG_7_0 machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 08:35:42 -0000 Hi, I have a fresh freebsd 7.0 box, installed from CD. I have src cvsupd with following supfile. *default host=cvsup.de.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_7_0 *default delete use-rel-suffix *default compress src-all after csup when I cd to /usr/src and issue a make buildworld It stops with following error: ===> gnu/usr.bin/cvs/contrib (cleandir) sed -e 's,@CSH@,/bin/csh,' -e 's,@PERL@,/usr/bin/perl,' /usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/Makefile.in > Makefile "Makefile", line 15: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. The line in question ( /usr/src/contrib/cvs/contrib/Makefile.in:15 )has the following text. @SET_MAKE@ If I do a csup after a comple just one file get's updated every time: Parsing supfile "src-supfile" Connecting to cvsup.de.FreeBSD.org Connected to 212.19.57.134 Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs Checkout src/gnu/usr.bin/cvs/contrib/Makefile Shutting down connection to server Finished successfully Any idea what could be wrong here? raj From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 11:59:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 906901065681 for ; Thu, 26 Jun 2008 11:59:28 +0000 (UTC) (envelope-from MichaelHarris@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id CF0CE8FC15 for ; Thu, 26 Jun 2008 11:59:27 +0000 (UTC) (envelope-from MichaelHarris@gmx.de) Received: (qmail 22404 invoked by uid 0); 26 Jun 2008 11:32:44 -0000 Received: from 85.181.22.173 by www108.gmx.net with HTTP; Thu, 26 Jun 2008 13:32:44 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 26 Jun 2008 13:32:44 +0200 From: "Michael Harris" Message-ID: <20080626113244.201570@gmx.net> MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Authenticated: #48440519 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX18UmVMg6w4UmdoJC2bB4HzSxkAEmqCM3gB6pX1ew9 bywbtha471NRqsp9dSmffovQ94PUIslaCeqQ== Content-Transfer-Encoding: 8bit X-GMX-UID: b0lReYlmIydmPeJBl2VrHvJSa2FkZpUI Subject: gmirror+gjournal: unable to boot after crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 11:59:28 -0000 Hi, after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. This is what I get with kernel.geom.mirror.debug=2: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB at ata2-master SATA300 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed GEOM_MIRROR[2]: Tasting ad4. ad4: LSI (v2) check1 failed magic: GEOM::MIRROR version: 4 name: gm0 mid: 2403671335 did: 1321347210 all: 2 genid: 0 syncid: 1 priority: 0 slice: 4096 balance: round-robin mediasize: 500107861504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: DIRTY hcprovider: provsize: 500107862016 MD5 hash: fd8b1cfa1aeb685da9b4228f5be3dc41 GEOM_MIRROR[1]: Creating device gm0 (id=2403671335). GEOM_MIRROR[1]: Device gm0 created (2 components, id=2403671335). GEOM_MIRROR[1]: root_mount_hold 0xffffff0001318040 GEOM_MIRROR[1]: Adding disk ad4 to gm0. GEOM_MIRROR[2]: Adding disk ad4. GEOM_MIRROR[2]: Disk ad4 connected. ad4: FreeBSD check1 failed GEOM_MIRROR[1]: Disk ad4 state changed from NONE to NEW (device gm0). GEOM_MIRROR[1]: Device gm0: provider ad4 detected. ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 476940MB at ata4-master SATA300 ad8: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM_MIRROR[2]: Tasting ad4s1. GEOM_MIRROR[2]: Tasting ad4a. GEOM_MIRROR[2]: Tasting ad4c. GEOM: new disk ad8 ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed GEOM_MIRROR[2]: Tasting ad8. ad8: LSI (v2) check1 failed magic: GEOM::MIRROR version: 4 name: gm0 mid: 2403671335 did: 3638214596 all: 2 genid: 0 syncid: 1 priority: 0 slice: 4096 balance: round-robin mediasize: 500107861504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: NONE hcprovider: provsize: 500107862016 MD5 hash: 6a44a256f5a29312f9632d22785dadce GEOM_MIRROR[1]: Adding disk ad8 to gm0. GEOM_MIRROR[2]: Adding disk ad8. GEOM_MIRROR[2]: Disk ad8 connected. GEOM_MIRROR[1]: Disk ad8 state changed from NONE to NEW (device gm0). GEOM_MIRROR[1]: Device gm0: provider ad8 detected. GEOM_MIRROR[1]: Device gm0 state changed from STARTING to RUNNING. GEOM_MIRROR[1]: Disk ad8 state changed from NEW to ACTIVE (device gm0). ad8: FreeBSD check1 failed GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Device gm0: provider ad8 activated. GEOM_MIRROR[1]: Disk ad4 state changed from NEW to SYNCHRONIZING (device gm0). GEOM_MIRROR[0]: Device mirror/gm0 launched (1/2). GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. GEOM_MIRROR[0]: Device gm0: rebuilding provider ad4. GEOM_MIRROR[1]: root_mount_rel[2379] 0xffffff0001318040 ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad10: 476940MB at ata5-master SATA300 ad10: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue ad10: nVidia check1 failed ad10: Adaptec check1 failed GEOM_MIRROR[2]: Tasting ad8s1. GEOM_MIRROR[2]: Tasting ad8a. GEOM_MIRROR[2]: Tasting ad8c. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. ad10: LSI (v3) check1 failed GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. ad10: LSI (v2) check1 failed GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains data. GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains journal. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w1e1. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. ad10: FreeBSD check1 failed GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. ATA PseudoRAID loaded GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. GEOM: new disk ad10 GEOM_MIRROR[2]: Tasting mirror/gm0s1. GEOM_MIRROR[2]: Tasting mirror/gm0a. GEOM_MIRROR[2]: Tasting mirror/gm0c. GEOM_MIRROR[2]: Tasting ad10. GEOM_MIRROR[2]: Tasting ad10s1. GEOM_MIRROR[2]: Tasting ad10s1a. GEOM_MIRROR[2]: Tasting ad10s1c. Trying to mount root from ufs:/dev/mirror/gm0.journals1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> With kernel.geom.journal.debug set to 2 I get: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB at ata2-master SATA300 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 476940MB at ata4-master SATA300 ad8: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad8 ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed ad8: LSI (v2) check1 failed ad8: FreeBSD check1 failed GEOM_MIRROR: Device mirror/gm0 launched (1/2). GEOM_MIRROR: Device gm0: rebuilding provider ad4. ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad10: 476940MB at ata5-master SATA300 ad10: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue ad10: nVidia check1 failed GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains data. GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains journal. ad10: Adaptec check1 failed ad10: LSI (v3) check1 failed ad10: LSI (v2) check1 failed ad10: FreeBSD check1 failed ATA PseudoRAID loaded GEOM: new disk ad10 Trying to mount root from ufs:/dev/mirror/gm0.journals1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> The 3rd boot loader lists directories. Any idea how this could be fixed via a remote serial line? Any chance to boot this without GEOM? Best regards. -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 14:25:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63C3C106566B for ; Thu, 26 Jun 2008 14:25:11 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out1.tiscali.nl (smtp-out1.tiscali.nl [195.241.79.176]) by mx1.freebsd.org (Postfix) with ESMTP id D9E638FC0C for ; Thu, 26 Jun 2008 14:25:10 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [212.123.145.58] (helo=guido.klop.ws) by smtp-out1.tiscali.nl with smtp id 1KBsA7-0003Ca-58 for ; Thu, 26 Jun 2008 16:09:23 +0200 Received: (qmail 2719 invoked from network); 26 Jun 2008 14:09:22 -0000 Received: from localhost (HELO guido.klop.ws) (127.0.0.1) by localhost with SMTP; 26 Jun 2008 14:09:22 -0000 Date: Thu, 26 Jun 2008 16:09:21 +0200 To: "freebsd-stable@freebsd.org" From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <20080616102144.4E3312844C@ronald.office.base.nl> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <20080616102144.4E3312844C@ronald.office.base.nl> User-Agent: Opera Mail/9.50 (FreeBSD) Subject: panic in drm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 14:25:11 -0000 Hello, At my work I see a panic if I do this. Leaf my computer on screensaver (don't no if that is necessary) and come back the next morning. My monitor is than black, but the light is green, so DPMS didn't kick in. Keys or mouse don't wake up the system. CTRL-ALT-F1 switches to the console and immediately triggers this panic. I'm running latest x.org with xf86-video-i810-1.7.4_1. The newer xf86-video-intel also crashes my system sometimes when I'm working on it, so a downgraded. Any ideas, suggestions or fixes available? Cheers, Ronald. FreeBSD ronald.office.base.nl 7.0-STABLE FreeBSD 7.0-STABLE #: Mon May 19 12:12:58 CEST 2008 root@ronald.office.base.nl:/usr/obj/usr/src/sys/SMP-RONALD i386 kgdb kernel.debug /var/crash/vmcore.2 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04faee4 stack pointer = 0x28:0xe7b25a94 frame pointer = 0x28:0xe7b25aac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 58549 (xlock) trap number = 12 panic: page fault cpuid = 1 Uptime: 20d18h31m44s Physical memory: 2037 MB Dumping 251 MB: 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc050867f in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc050893a in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc067a080 in trap_fatal (frame=0xe7b25a54, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc067a2d0 in trap_pfault (frame=0xe7b25a54, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc067ab81 in trap (frame=0xe7b25a54) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc066277b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc04faee4 in _mtx_lock_sleep (m=0xc4ddfcc0, tid=3321921536, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:335 #8 0xc04fb005 in lock_mtx (lock=0xc4ddfcc0, how=0) at /usr/src/sys/kern/kern_mutex.c:141 #9 0xc05102b8 in _sleep (ident=0xc4ddfe64, lock=0xc4ddfcc0, priority=340, wmesg=0xc58007e7 "drmwtq", timo=3000) at /usr/src/sys/kern/kern_synch.c:237 #10 0xc57fefa7 in i915_driver_vblank_wait (dev=0xc4ddfc00, sequence=0xe7b25b48) at /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_irq.c:141 #11 0xc580bf06 in drm_wait_vblank (kdev=0xc570b600, cmd=Variable "cmd" is not available. ) at /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_irq.c:254 #12 0xc580a8e4 in drm_ioctl (kdev=0xc570b600, cmd=3222299706, data=0xc72790b0 "", flags=3, p=0xc6008000) at /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c:911 #13 0xc04d58e0 in giant_ioctl (dev=0xc570b600, cmd=3222299706, data=0xc72790b0 "", fflag=3, td=0xc6008000) at /usr/src/sys/kern/kern_conf.c:405 #14 0xc04b0998 in devfs_ioctl_f (fp=0xc87f0c18, com=3222299706, data=0xc72790b0, cred=0xc81ea000, td=0xc6008000) at /usr/src/sys/fs/devfs/devfs_vnops.c:494 #15 0xc053bbb5 in kern_ioctl (td=0xc6008000, fd=5, com=3222299706, data=0xc72790b0 "") at file.h:266 #16 0xc053bcfa in ioctl (td=0xc6008000, uap=0xe7b25cfc) at /usr/src/sys/kern/sys_generic.c:570 #17 0xc067a5c1 in syscall (frame=0xe7b25d38) at /usr/src/sys/i386/i386/trap.c:1035 #18 0xc06627e0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #19 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) list *0xc04faee4 0xc04faee4 is in _mtx_lock_sleep (/usr/src/sys/kern/kern_mutex.c:337). 332 */ 333 v = m->mtx_lock; 334 if (v != MTX_UNOWNED) { 335 owner = (struct thread *)(v & ~MTX_FLAGMASK); 336 #ifdef ADAPTIVE_GIANT 337 if (TD_IS_RUNNING(owner)) { 338 #else 339 if (m != &Giant && TD_IS_RUNNING(owner)) { 340 #endif 341 if (LOCK_LOG_TEST(&m->lock_object, 0)) --- dmesg output --- Copyright (c) 1992-2008 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 7.0-STABLE #: Mon Jun 16 14:05:07 CEST 2008 root@ronald.office.base.nl:/usr/obj/usr/src/sys/SMP-RONALD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 2145845248 (2046 MB) avail memory = 2094579712 (1997 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, f00000 (3) failed acpi0: reservation of 1000000, 7ee70000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 cpu1: on acpi0 p4tcc1: on cpu1 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xed98-0xed9f mem 0xe8000000-0xefffffff,0xfeb80000-0xfebfffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 892k stolen memory agp0: aperture size is 128M uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered uhub5: on uhub4 uhub5: single transaction translator uhub5: 4 ports with 4 removable, self powered ums0: on uhub5 ums0: 8 buttons and Z dir. pcib1: at device 30.0 on pci0 pci1: on pcib1 em0: port 0xdf40-0xdf7f mem 0xfeae0000-0xfeafffff irq 18 at device 12.0 on pci1 em0: [FILTER] em0: Ethernet address: 00:0f:1f:83:6e:fb isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7ffff irq 18 at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq 18 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ichsmb0: port 0xeda0-0xedbf irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: on ichsmb0 pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 pcm0: [ITHREAD] pcm0: atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xca800-0xcbfff,0xcc000-0xd87ff,0xd8800-0xdbfff pnpid ORM0000 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ubt0: on uhub3 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 Timecounters tick every 1.000 msec ad0: 76293MB at ata0-master UDMA100 acd0: CDROM at ata1-master UDMA33 SMP: AP CPU #1 Launched! GEOM_LABEL: Label for provider ad0s1 is msdosfs/DellUtility. GEOM_LABEL: Label for provider ad0s2 is ufs/test. Trying to mount root from ufs:/dev/ad0s3a WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() WARNING: attempt to net_add_domain(netgraph) after domainfinalize() ipfw2 initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled netsmb_dev: loaded drm0: on vgapci0 info: [drm] AGP at 0xe8000000 128MB info: [drm] Initialized i915 1.5.0 20060119 drm0: [ITHREAD] pid 3421 (fstat), uid 0: exited on signal 6 encode_long: negative value -633 in accounting record -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 15:22:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ADF61065686 for ; Thu, 26 Jun 2008 15:22:52 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [198.145.180.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF8A8FC20 for ; Thu, 26 Jun 2008 15:22:52 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: by vexbert.mr-paradox.net (Postfix, from userid 16139) id 90585844C3; Thu, 26 Jun 2008 11:22:51 -0400 (EDT) Date: Thu, 26 Jun 2008 11:22:50 -0400 From: Jeff Blank To: freebsd-stable@freebsd.org Message-ID: <20080626152250.GA15433@mr-happy.com> References: <20080617154342.GB49490@mr-happy.com> <20080623175335.GB58577@mr-happy.com> <20080623205039.GC10644@lava.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080623205039.GC10644@lava.net> X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e Subject: Re: bus_dmamem_alloc failed to align memory properly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 15:22:52 -0000 On Mon, Jun 23, 2008 at 10:50:40AM -1000, Clifton Royston wrote: > I can not be completely sure, but believe this may be a cross-OS > problem with Xorg support of this specific ATI card family. Interesting. Thanks for the tip. > If you don't want to spend a lot of time on this, I'd try a different > video card; I have a strong suspicion that your problems are not > FreeBSD related and would go away with that change. Cool, I'll try a Radeon X1550 on Monday. thanks, Jeff From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 16:32:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D5001065675 for ; Thu, 26 Jun 2008 16:32:15 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id 255658FC19 for ; Thu, 26 Jun 2008 16:32:13 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id m5QG18M4002353; Thu, 26 Jun 2008 17:01:08 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1KBtuG-0000bl-BP; Thu, 26 Jun 2008 17:01:08 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m5QG17Hr090255; Thu, 26 Jun 2008 17:01:08 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m5QG17oH090254; Thu, 26 Jun 2008 17:01:07 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Ronald Klop In-Reply-To: References: <20080616102144.4E3312844C@ronald.office.base.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 26 Jun 2008 17:01:07 +0100 Message-Id: <1214496067.23553.42.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: "freebsd-stable@freebsd.org" Subject: Re: panic in drm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 16:32:15 -0000 On Thu, 2008-06-26 at 16:09 +0200, Ronald Klop wrote: > Hello, > > At my work I see a panic if I do this. > Leaf my computer on screensaver (don't no if that is necessary) and come > back the next morning. My monitor is than black, but the light is green, > so DPMS didn't kick in. > Keys or mouse don't wake up the system. CTRL-ALT-F1 switches to the > console and immediately triggers this panic. > > I'm running latest x.org with xf86-video-i810-1.7.4_1. The newer > xf86-video-intel also crashes my system sometimes when I'm working on it, > so a downgraded. > > Any ideas, suggestions or fixes available? This sounds very familiar to me. I think I was seeing the same panic in 2006... http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-12/msg00344.html Can you add this to src/sys/dev/drm/i915_irq.c if (!dev->irqr) { return DRM_ERR(EINVAL); } just above the DRM_WAIT_ON in i915_driver_vblank_wait() (around line 140), and see if that prevents the panic? Note that I believe this to be a workaround, and not really the correct fix. (sorry for not supplying patches, I'm not in a position to right now) Gavin From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 18:34:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C862106564A for ; Thu, 26 Jun 2008 18:34:45 +0000 (UTC) (envelope-from kjblack@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3B7A28FC1C for ; Thu, 26 Jun 2008 18:34:44 +0000 (UTC) (envelope-from kjblack@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so148932rvf.43 for ; Thu, 26 Jun 2008 11:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=+hlDs91z5zp+PhvtYrpcs3gZTP2Z+CzDOTCNTyMU02w=; b=jYy4n1gNZ9MGXKgpTW1iVKMpXig1B8ZA07sva6dUEtZnBy93wYEEHjLR18GvZ2Y3OL XtR5BYVIhMHrhhb/VOmygYUBhqEPog+XHaXZ1ePgFEhSaGZINT3rlR5TKIitV9mD82v3 cru5EHZUKiOujS2Pv4iCD/bEfYk7ZRh/zFTI4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=R2RjkZAjykhHX8fhGM8hH9TXfjSyzZt8gtyZkcy7gfkb+UuJ44/tZtyC2ahSrFgu6g 8mtv6md3UK40UVzUPOjGhCOnnPYhVH4vEZs4jGrVCFMs42YOxawR8y9xr2f/dYUOC5Z0 4tXnmaUNVchI4XXB97OjRDCLainVneNzUTCtY= Received: by 10.141.137.6 with SMTP id p6mr189821rvn.279.1214505284113; Thu, 26 Jun 2008 11:34:44 -0700 (PDT) Received: by 10.140.136.10 with HTTP; Thu, 26 Jun 2008 11:34:44 -0700 (PDT) Message-ID: <1b1b33f10806261134v7ce1750ek17d8985fc7263141@mail.gmail.com> Date: Thu, 26 Jun 2008 14:34:44 -0400 From: "Kelly Black" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 18:34:45 -0000 > >On Wed, Jun 25, 2008 at 7:38 AM, Kelly Black wrote: >> I have a problem with loader. I recently upgraded from 6_rel to 7_rel. >> Now when I install world there is a problem booting. >> >> Here is what I do: >[snip] >> Now when I reboot there is a problem. I get an error that the system >> cannot boot. Part of it looks like this: >> Can't work out which disk we are booting from. >> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: >> >> If I boot from a live disk and replace /boot/loader with >> /boot/loader.old it boots up fine and everything looks good. A new >> world and a new kernel. I would be grateful for any help or any >> pointers. > >What do you have in /etc/make.conf? I recall there being a point in >time where incorrect CFLAGS options could build a broken loader. > >Try renaming /etc/make.conf (or just commenting out all >CFLAGS/CXXFLAGS options) and rebuilding either just the loader or the >whole world, and see if that makes a difference. > >-- >Freddie Cash >fjwcash@gmail.com > Hello, Thank you for the reply. I put my make.conf file back to its default when I first did the upgrade to avoid other kinds of problems: make.conf # added by use.perl 2008-04-07 11:54:35 PERL_VER=5.8.8 PERL_VERSION=5.8.8 And it still produced the loader that does not load. Sincerely, Kel -- _______________________________________________________ Kelly Black Phone: (518) 388-8727 Department of Mathematics FAX: (603) 388-6005 Union College e-mail: kelly.black@union.edu Schenectady NY 12308 (USA) WWW: http://blackk.union.edu/~black From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 19:54:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F90B106564A; Thu, 26 Jun 2008 19:54:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 457CC8FC16; Thu, 26 Jun 2008 19:54:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 137ED1CC031; Thu, 26 Jun 2008 12:54:41 -0700 (PDT) Date: Thu, 26 Jun 2008 12:54:41 -0700 From: Jeremy Chadwick To: Kelly Black Message-ID: <20080626195441.GA2608@eos.sc1.parodius.com> References: <1b1b33f10806261134v7ce1750ek17d8985fc7263141@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1b1b33f10806261134v7ce1750ek17d8985fc7263141@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, jhb@freebsd.org Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 19:54:41 -0000 On Thu, Jun 26, 2008 at 02:34:44PM -0400, Kelly Black wrote: > >On Wed, Jun 25, 2008 at 7:38 AM, Kelly Black wrote: > >> I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > >> Now when I install world there is a problem booting. > >> > >> Here is what I do: > >[snip] > >> Now when I reboot there is a problem. I get an error that the system > >> cannot boot. Part of it looks like this: > >> Can't work out which disk we are booting from. > >> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > >> > >> If I boot from a live disk and replace /boot/loader with > >> /boot/loader.old it boots up fine and everything looks good. A new > >> world and a new kernel. I would be grateful for any help or any > >> pointers. > > > >What do you have in /etc/make.conf? I recall there being a point in > >time where incorrect CFLAGS options could build a broken loader. > > > >Try renaming /etc/make.conf (or just commenting out all > >CFLAGS/CXXFLAGS options) and rebuilding either just the loader or the > >whole world, and see if that makes a difference. > > Hello, > > Thank you for the reply. I put my make.conf file back to its default > when I first did the upgrade to avoid other kinds of problems: > > make.conf > # added by use.perl 2008-04-07 11:54:35 > PERL_VER=5.8.8 > PERL_VERSION=5.8.8 > > And it still produced the loader that does not load. Kelly, A couple things: I'm wondering if you're getting bit by changes made to loader(8) by John Baldwin last year. Those changes were positive and increased compatibility with systems greatly, but there were a couple reports of users whose systems preferred the old "method" used. Those changes are documented here; and yes, I realise you don't get a screen full of continual register dumps, but different people saw different behaviour: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Also see these mailing list threads: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078755.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/038214.html Secondly, you said you migrated from "6_rel to 7_rel". Do you mean 7.0-RELEASE, or are you referring to the RELENG_7 tag? What tag are you following when doing csup/cvsup? CC'ing John as well. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 20:23:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E61AF1065684 for ; Thu, 26 Jun 2008 20:23:25 +0000 (UTC) (envelope-from baigsabeeh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 8C1C58FC2B for ; Thu, 26 Jun 2008 20:23:25 +0000 (UTC) (envelope-from baigsabeeh@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so59599pyb.10 for ; Thu, 26 Jun 2008 13:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZCgjRHnfGjm+rRg9m3YdfE+EP7g46NcAMhp0bTBFHyI=; b=GBKBGi58ob8H5DA4ObktD54Tefy2ZAbp0eRj81AlxYHc8ovOKnZ8QZJGg7yqv//408 Ld0GClMkmuym8pWbeoeoJ6v5zv9RHFuLIja7FbOD/hw4+qtFxQz+y47pDYk7HJ/zrcTi 6M1M2SMkzFYBmPAIvTq5FVUwquxba6L9qV4zs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=kV11MkXN5fiqpQrghSVXHymqS/Vd0pMJ0fnZH0n2VCA46zePK4JHas/XDyBFMsPZ7E CpH4C137UNuiNf2Tf8p9DcLed33z0HjQrpvLMkQ25ybhqnW/s4opeo14h90F1lx3Dqhw y4ZL6DSVzJ83LjvBTI9Mr60t/bkCRpibTaQQI= Received: by 10.114.12.10 with SMTP id 10mr518544wal.190.1214511803976; Thu, 26 Jun 2008 13:23:23 -0700 (PDT) Received: by 10.114.58.13 with HTTP; Thu, 26 Jun 2008 13:23:23 -0700 (PDT) Message-ID: Date: Thu, 26 Jun 2008 16:23:23 -0400 From: "Sabeeh Baig" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: jdk16 web plugin on FreeBSD 7 AMD64 Issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 20:23:26 -0000 I recently installed jdk16 from ports on my FreeBSD 7-Stable AMD64 home server. When I try to access websites that use the Java web plugin, the applets don't load. Checking on about:plugins in Firefox shows the Java plugin listed and enabled. Does jdk16 web plugin work on FreeBSD 7 AMD64? I saw on previous mailing list entries mentioned that the plugins from jdk16 and jdk15 on AMD64 worked. Sabeeh Ahmed Baig From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 20:38:55 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 90ACF1065676; Thu, 26 Jun 2008 20:38:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Thu, 26 Jun 2008 16:38:36 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200806261638.39168.jkim@FreeBSD.org> Cc: Sabeeh Baig Subject: Re: jdk16 web plugin on FreeBSD 7 AMD64 Issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 20:38:55 -0000 On Thursday 26 June 2008 04:23 pm, Sabeeh Baig wrote: > I recently installed jdk16 from ports on my FreeBSD 7-Stable AMD64 > home server. When I try to access websites that use the Java web > plugin, the applets don't load. Checking on about:plugins in > Firefox shows the Java plugin listed and enabled. Does jdk16 web > plugin work on FreeBSD 7 AMD64? I saw on previous mailing list > entries mentioned that the plugins from jdk16 and jdk15 on AMD64 > worked. Try: env JAVAVM_DRYRUN=yes java It will print something like the following: JAVA_HOME=/usr/local/jdk1.6.0 JAVAVM_CONF=/usr/local/etc/javavms JAVAVM_OPTS_CONF=/usr/local/etc/javavm_opts.conf JAVAVM_PROG=/usr/local/jdk1.6.0/bin/java JAVAVM_OPTS= JAVAVM_COMMAND=/usr/local/jdk1.6.0/bin/java If ${JAVA_HOME} does not match the installed plugin, it will not work. If it matches, remove ~/.java directory and try again. Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 21:53:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D348F1065677 for ; Thu, 26 Jun 2008 21:53:59 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 5BB9F8FC32 for ; Thu, 26 Jun 2008 21:53:59 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7db4.q.ppp-pool.de [89.53.125.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 9B73512883F; Thu, 26 Jun 2008 23:53:52 +0200 (CEST) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 498C12E823; Thu, 26 Jun 2008 23:53:06 +0200 (CEST) Message-ID: <48640FE8.9080501@vwsoft.com> Date: Thu, 26 Jun 2008 23:53:44 +0200 From: Volker User-Agent: Thunderbird 2.0.0.14 (X11/20080615) MIME-Version: 1.0 To: Kelly Black References: <1b1b33f10806250738y55fc8437l8e26c9c1698ea364@mail.gmail.com> In-Reply-To: <1b1b33f10806250738y55fc8437l8e26c9c1698ea364@mail.gmail.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1215121988.0128@5U4wceZKTLlOTC2RxYO/hw X-MailScanner-ID: 498C12E823.4A704 X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-stable@freebsd.org Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 21:53:59 -0000 On 12/23/-58 20:59, Kelly Black wrote: > Hello, > > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > Now when I install world there is a problem booting. > > Here is what I do: > cd /usr/src > make buildworld > make buildkernel KERNCONF=BLACK > make installkernel KERNCONF=BLACK > > At this point I can reboot and all is good. After boot I install the new world: > > cd /usr/src > mergemaster -p > reboot into single user mode > cd /usr/src > make installworld > mergemaster > > Now when I reboot there is a problem. I get an error that the system > cannot boot. Part of it looks like this: > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > If I boot from a live disk and replace /boot/loader with > /boot/loader.old it boots up fine and everything looks good. A new > world and a new kernel. I would be grateful for any help or any > pointers. > > Sincerely, > Kel > > PS I do not do anything special with my loader config files: > > $ cat loader.conf >... Kelly, the /boot/loader.conf file does not come into play at that stage. Early in the loader code, loader needs to figure out, which disk (BIOS device) has been booted from. Until loader knows which device was booted up, it's unable to access any files (even loader.conf) on your boot device. As I've never seen such a problem while upgrading any system, I suspect your problem must be settings specific. Can you show me your kernel config or are you using a plain vanilla GENERIC? Which arch are we talking about? As I'm currently investigating another boot problem (but earlier in the boot chain), I'll check boot logic in the source code and may check for your issue, too, at that time, so it's just one effort. But please stay patient for some days, as I'm currently too busy. Volker From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 22:31:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A8171065670 for ; Thu, 26 Jun 2008 22:31:37 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 85EFB8FC0A for ; Thu, 26 Jun 2008 22:31:36 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7db4.q.ppp-pool.de [89.53.125.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 1095612883F; Fri, 27 Jun 2008 00:31:29 +0200 (CEST) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 13E062E823; Fri, 27 Jun 2008 00:30:33 +0200 (CEST) Message-ID: <486418AF.5000204@vwsoft.com> Date: Fri, 27 Jun 2008 00:31:11 +0200 From: Volker User-Agent: Thunderbird 2.0.0.14 (X11/20080615) MIME-Version: 1.0 To: Michael Harris References: <20080626113244.201570@gmx.net> In-Reply-To: <20080626113244.201570@gmx.net> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1215124243.87443@qVseSCwYMN60vbTAUJqTkQ X-MailScanner-ID: 13E062E823.8CECE X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-stable@freebsd.org Subject: Re: gmirror+gjournal: unable to boot after crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2008 22:31:37 -0000 On 12/23/-58 20:59, Michael Harris wrote: > Hi, > > after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. > > This is what I get with kernel.geom.mirror.debug=2: > > ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad4: 476940MB at ata2-master SATA300 > ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue > GEOM: new disk ad4 > ad4: nVidia check1 failed > ad4: Adaptec check1 failed > ad4: LSI (v3) check1 failed > GEOM_MIRROR[2]: Tasting ad4. > ad4: LSI (v2) check1 failed > magic: GEOM::MIRROR > version: 4 > name: gm0 > mid: 2403671335 > did: 1321347210 > all: 2 > genid: 0 > syncid: 1 > priority: 0 > slice: 4096 > balance: round-robin > mediasize: 500107861504 > sectorsize: 512 > syncoffset: 0 > mflags: NONE > dflags: DIRTY > hcprovider: > provsize: 500107862016 > MD5 hash: fd8b1cfa1aeb685da9b4228f5be3dc41 > GEOM_MIRROR[1]: Creating device gm0 (id=2403671335). > GEOM_MIRROR[1]: Device gm0 created (2 components, id=2403671335). > GEOM_MIRROR[1]: root_mount_hold 0xffffff0001318040 > GEOM_MIRROR[1]: Adding disk ad4 to gm0. > GEOM_MIRROR[2]: Adding disk ad4. > GEOM_MIRROR[2]: Disk ad4 connected. > ad4: FreeBSD check1 failed > GEOM_MIRROR[1]: Disk ad4 state changed from NONE to NEW (device gm0). > GEOM_MIRROR[1]: Device gm0: provider ad4 detected. > ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad8: 476940MB at ata4-master SATA300 > ad8: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue > GEOM_MIRROR[2]: Tasting ad4s1. > GEOM_MIRROR[2]: Tasting ad4a. > GEOM_MIRROR[2]: Tasting ad4c. > GEOM: new disk ad8 > ad8: nVidia check1 failed > ad8: Adaptec check1 failed > ad8: LSI (v3) check1 failed > GEOM_MIRROR[2]: Tasting ad8. > ad8: LSI (v2) check1 failed > magic: GEOM::MIRROR > version: 4 > name: gm0 > mid: 2403671335 > did: 3638214596 > all: 2 > genid: 0 > syncid: 1 > priority: 0 > slice: 4096 > balance: round-robin > mediasize: 500107861504 > sectorsize: 512 > syncoffset: 0 > mflags: NONE > dflags: NONE > hcprovider: > provsize: 500107862016 > MD5 hash: 6a44a256f5a29312f9632d22785dadce > GEOM_MIRROR[1]: Adding disk ad8 to gm0. > GEOM_MIRROR[2]: Adding disk ad8. > GEOM_MIRROR[2]: Disk ad8 connected. > GEOM_MIRROR[1]: Disk ad8 state changed from NONE to NEW (device gm0). > GEOM_MIRROR[1]: Device gm0: provider ad8 detected. > GEOM_MIRROR[1]: Device gm0 state changed from STARTING to RUNNING. > GEOM_MIRROR[1]: Disk ad8 state changed from NEW to ACTIVE (device gm0). > ad8: FreeBSD check1 failed > GEOM_MIRROR[2]: Metadata on ad8 updated. > GEOM_MIRROR[1]: Device gm0: provider ad8 activated. > GEOM_MIRROR[1]: Disk ad4 state changed from NEW to SYNCHRONIZING (device gm0). > GEOM_MIRROR[0]: Device mirror/gm0 launched (1/2). > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > GEOM_MIRROR[0]: Device gm0: rebuilding provider ad4. > GEOM_MIRROR[1]: root_mount_rel[2379] 0xffffff0001318040 > ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad10: 476940MB at ata5-master SATA300 > ad10: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue > ad10: nVidia check1 failed > ad10: Adaptec check1 failed > GEOM_MIRROR[2]: Tasting ad8s1. > GEOM_MIRROR[2]: Tasting ad8a. > GEOM_MIRROR[2]: Tasting ad8c. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > ad10: LSI (v3) check1 failed > GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > ad10: LSI (v2) check1 failed > GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. > GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains data. > GEOM_JOURNAL: Journal 2550245011: mirror/gm0 contains journal. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w1e1. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > ad10: FreeBSD check1 failed > GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > ATA PseudoRAID loaded > GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. > GEOM_MIRROR[2]: Access request for mirror/gm0: r1w0e0. > GEOM_MIRROR[2]: Access request for mirror/gm0: r-1w0e0. > GEOM: new disk ad10 > GEOM_MIRROR[2]: Tasting mirror/gm0s1. > GEOM_MIRROR[2]: Tasting mirror/gm0a. > GEOM_MIRROR[2]: Tasting mirror/gm0c. > GEOM_MIRROR[2]: Tasting ad10. > GEOM_MIRROR[2]: Tasting ad10s1. > GEOM_MIRROR[2]: Tasting ad10s1a. > GEOM_MIRROR[2]: Tasting ad10s1c. > Trying to mount root from ufs:/dev/mirror/gm0.journals1a > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > mountroot> > This line: > Trying to mount root from ufs:/dev/mirror/gm0.journals1a does not look very promising. Have you really created a journaling geom provider and created bsd partitions in it? > The 3rd boot loader lists directories. boot1/2 is accessing the device under BIOS control and does not know anything GEOM like, so as long as the boot device / boot-fs can be figured out and the on-disk filesystem structure is valid, it can list files. > Any idea how this could be fixed via a remote serial line? Any chance to boot this without GEOM? If I got it right, you've done something really, really bad while organizing your disk / filesystem layout. If I'm not mistaken with that assumption, I don't see much hope to get the system up by a remote console only. At least, you may try to see if you're able to mount root from "ufs:adXs1a" (assuming root is at S/ATA disk 0, first slice) and get it at least into single user mode. You may also want to try to unload geom modules at the loader prompt. You should try to safe your valuable data, fix your disk partitioning as soon as you're able to get single user access again (again, if I'm not mistaken while assuming you've created partitions within the journaling provider). Volker From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 00:11:36 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE7BD1065679 for ; Fri, 27 Jun 2008 00:11:36 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.freebsd.org (Postfix) with SMTP id ADA408FC16 for ; Fri, 27 Jun 2008 00:11:36 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: (qmail 91186 invoked by uid 503); 26 Jun 2008 23:44:55 -0000 Date: Thu, 26 Jun 2008 16:44:55 -0700 From: Marcus Reid To: freebsd-stable@FreeBSD.org Message-ID: <20080626234455.GA77263@blazingdot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.6i Cc: Subject: Performance of madvise / msync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 00:11:36 -0000 Hi, I'm using py-rrdtool 0.2.1 with rrdtool 1.3.0 under 7.0-STABLE, and there's a couple of things about this new version of rrdtool that hurt performance under FreeBSD, but apparently help on whatever they tested on. For every update, the database file is opened, mapped into memory, madvise() is called, contents are modified, msync() is called, and the file is unmapped and closed: 65074 python 0.000009 CALL open(0x831a1b4,O_RDWR,0) 65074 python 0.000013 NAMI "rg2.rrd" 65074 python 0.000024 RET open 7 65074 python 0.000007 CALL fstat(0x7,0xbfbfe428) 65074 python 0.000011 RET fstat 0 65074 python 0.000008 CALL mmap(0,0x453b7618,PROT_READ|PROT_WRITE,MAP_SHARED,0x7,0,0) 65074 python 0.000018 RET mmap 679235584/0x287c5000 65074 python 0.000007 CALL madvise(0x287c5000,0x453b7618,_MADV_RANDOM) 65074 python 0.000008 RET madvise 0 65074 python 0.000006 CALL madvise(0x287c5000,0x70,_MADV_WILLNEED) 65074 python 0.027455 RET madvise 0 65074 python 0.000058 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) 65074 python 0.016904 RET madvise 0 65074 python 0.000179 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) 65074 python 0.008629 RET madvise 0 65074 python 0.000040 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) 65074 python 0.004173 RET madvise 0 65074 python 0.000048 CALL gettimeofday(0xbfbfe554,0) 65074 python 0.000009 RET gettimeofday 0 65074 python 0.000012 CALL fcntl(0x7,,0xbfbfe478) 65074 python 0.000024 RET fcntl 0 65074 python 0.006084 CALL msync(0x287c5000,0x453b7618,MS_ASYNC) 65074 python 0.106284 RET msync 0 65074 python 0.000483 CALL munmap(0x287c5000,0x453b7618) 65074 python 0.000356 RET munmap 0 65074 python 0.000012 CALL close(0x7) 65074 python 0.000046 RET close 0 65074 python 0.000173 CALL __sysctl(0xbfbfe388,0x2,0xbfbfe394,0xbfbfe398,0,0) 65074 python 0.000016 RET __sysctl 0 Here's a similar update without the calls to madvise and msync: 96372 python 0.000011 CALL open(0x831aa34,O_RDWR,0) 96372 python 0.000016 NAMI "rg2.rrd" 96372 python 0.000025 RET open 7 96372 python 0.000009 CALL fstat(0x7,0xbfbfe428) 96372 python 0.000014 RET fstat 0 96372 python 0.000010 CALL mmap(0,0x453b7618,PROT_READ|PROT_WRITE,MAP_SHARED,0x7,0,0) 96372 python 0.000021 RET mmap 679235584/0x287c5000 96372 python 0.000101 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) 96372 python 0.000013 RET madvise 0 96372 python 0.000010 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) 96372 python 0.000010 RET madvise 0 96372 python 0.000009 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) 96372 python 0.000009 RET madvise 0 96372 python 0.000010 CALL gettimeofday(0xbfbfe554,0) 96372 python 0.000009 RET gettimeofday 0 96372 python 0.000011 CALL fcntl(0x7,,0xbfbfe478) 96372 python 0.000016 RET fcntl 0 96372 python 0.002024 CALL munmap(0x287c5000,0x453b7618) 96372 python 0.000366 RET munmap 0 96372 python 0.000016 CALL close(0x7) 96372 python 0.000046 RET close 0 96372 python 0.000108 CALL __sysctl(0xbfbfe388,0x2,0xbfbfe394,0xbfbfe398,0,0) 96372 python 0.000017 RET __sysctl 0 As you can see, it's quite a bit faster. I know that msync is necessary under Linux but obsolete under FreeBSD, but it's still funny that it takes a tenth of a second to return even with MS_ASYNC specified. Also, why is it that the madvise() calls take so much longer when the program does a couple of its own madvise() calls? Was madvise() never intended to be run so frequently and is therefore a little slower than it could be? Here's the diff between the code for the first kdump above and the second one. *** src/rrd_open.c.orig Tue Jun 10 23:12:55 2008 --- src/rrd_open.c Wed Jun 25 21:43:54 2008 *************** *** 175,191 **** #endif if (rdwr & RRD_CREAT) goto out_done; - #ifdef USE_MADVISE - if (rdwr & RRD_COPY) { - /* We will read everything in a moment (copying) */ - madvise(data, rrd_file->file_len, MADV_WILLNEED | MADV_SEQUENTIAL); - } else { - /* We do not need to read anything in for the moment */ - madvise(data, rrd_file->file_len, MADV_RANDOM); - /* the stat_head will be needed soonish, so hint accordingly */ - madvise(data, sizeof(stat_head_t), MADV_WILLNEED | MADV_RANDOM); - } - #endif __rrd_read(rrd->stat_head, stat_head_t, 1); --- 175,180 ---- *************** *** 388,396 **** int ret; #ifdef HAVE_MMAP - ret = msync(rrd_file->file_start, rrd_file->file_len, MS_ASYNC); - if (ret != 0) - rrd_set_error("msync rrd_file: %s", rrd_strerror(errno)); ret = munmap(rrd_file->file_start, rrd_file->file_len); if (ret != 0) rrd_set_error("munmap rrd_file: %s", rrd_strerror(errno)); --- 377,382 ---- Thanks, Marcus From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 00:36:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C8971065679; Fri, 27 Jun 2008 00:36:24 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id B90348FC13; Fri, 27 Jun 2008 00:36:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id BBD0E28449; Fri, 27 Jun 2008 08:36:22 +0800 (CST) Received: from localhost (tarsier.geekcn.org [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id 70FE4EB9469; Fri, 27 Jun 2008 08:36:21 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id MR4P3X2YL07e; Fri, 27 Jun 2008 08:36:16 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 3D553EDD5C9; Fri, 27 Jun 2008 08:36:15 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=Qx8po/zr21ydt7k0mNsWqtDAevdppBKCHscSwefqlqEdo7DgDbP25isSvnSvsWjai 8oRr0P0K/rfTHDw6We2NA== Message-ID: <486435FC.2000100@delphij.net> Date: Thu, 26 Jun 2008 17:36:12 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Ivan Voras References: <47713ee10806061443v3e44576am2facb75df031f47e@mail.gmail.com> <47713ee10806062148l4a4c4550hcd8c70a422343c2a@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: TMPFS: File System is Full X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 00:36:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ivan Voras wrote: | Lin Jui-Nan Eric wrote: | |> I think there should be a "lower bound" size limit. Does TMPFS use |> kernel-space memory? | | Yes, tmpfs does use kmem and competes with ZFS. Yes and no. tmpfs makes use of some kernel memory but most of data is stored in swappable memory. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhkNfsACgkQi+vbBBjt66Ad8ACfYD1Yq09oY7iIjxq353iMFKKp FGYAnjA3I8V2cN1s1EW2NuwfhilaJBMe =vnM3 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 00:48:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19372106566C for ; Fri, 27 Jun 2008 00:48:16 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id E90298FC14 for ; Fri, 27 Jun 2008 00:48:15 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m5R0mDWC024173; Thu, 26 Jun 2008 17:48:13 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m5R0mDIU024172; Thu, 26 Jun 2008 17:48:13 -0700 (PDT) Date: Thu, 26 Jun 2008 17:48:13 -0700 (PDT) From: Matthew Dillon Message-Id: <200806270048.m5R0mDIU024172@apollo.backplane.com> To: Marcus Reid References: <20080626234455.GA77263@blazingdot.com> Cc: freebsd-stable@freebsd.org Subject: Re: Performance of madvise / msync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 00:48:16 -0000 : 65074 python 0.000006 CALL madvise(0x287c5000,0x70,_MADV_WILLNEED) : 65074 python 0.027455 RET madvise 0 : 65074 python 0.000058 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) : 65074 python 0.016904 RET madvise 0 : 65074 python 0.000179 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) : 65074 python 0.008629 RET madvise 0 : 65074 python 0.000040 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) : 65074 python 0.004173 RET madvise 0 :... : 65074 python 0.006084 CALL msync(0x287c5000,0x453b7618,MS_ASYNC) : 65074 python 0.106284 RET msync 0 :... :As you can see, it's quite a bit faster. : :I know that msync is necessary under Linux but obsolete under FreeBSD, but :it's still funny that it takes a tenth of a second to return even with :MS_ASYNC specified. : :Also, why is it that the madvise() calls take so much longer when the :program does a couple of its own madvise() calls? Was madvise() never :intended to be run so frequently and is therefore a little slower than :it could be? : :Here's the diff between the code for the first kdump above and the :second one. Those times are way way too large, even with other running threads in the system. madvise() should not take that long unless it is being forced to wait on a busied page, and neither should msync(). madvise() doesn't even do any I/O (or shouldn't anyhow). Try removing just the msync() but keep the madvise() calls and see if the madvise() calls continue to take horrendous amounts of time. Then try the vise-versa. It kinda feels like a prior msync() is initiating physical I/O on pages and a later mmap/madvise or page fault is being forced to wait on the prior pages for the I/O to finish. The size_t argument to msync() (0x453b7618) is highly questionable. It could be ktrace reporting the wrong value, but maybe not. On any sort of random writing test, particularly if multiple threads are involved, specifying a size that large could result in very large latencies. -Matt From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 02:34:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D014A1065678 for ; Fri, 27 Jun 2008 02:34:58 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.freebsd.org (Postfix) with SMTP id C17D28FC15 for ; Fri, 27 Jun 2008 02:34:58 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: (qmail 74552 invoked by uid 503); 27 Jun 2008 02:34:55 -0000 Date: Thu, 26 Jun 2008 19:34:55 -0700 From: Marcus Reid To: Matthew Dillon Message-ID: <20080627023455.GA34022@blazingdot.com> References: <20080626234455.GA77263@blazingdot.com> <200806270048.m5R0mDIU024172@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200806270048.m5R0mDIU024172@apollo.backplane.com> X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.6i Cc: freebsd-stable@freebsd.org Subject: Re: Performance of madvise / msync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 02:34:58 -0000 On Thu, Jun 26, 2008 at 05:48:13PM -0700, Matthew Dillon wrote: > : 65074 python 0.000006 CALL madvise(0x287c5000,0x70,_MADV_WILLNEED) > : 65074 python 0.027455 RET madvise 0 > : 65074 python 0.000058 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) > : 65074 python 0.016904 RET madvise 0 > : 65074 python 0.000179 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) > : 65074 python 0.008629 RET madvise 0 > : 65074 python 0.000040 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) > : 65074 python 0.004173 RET madvise 0 > :... > : 65074 python 0.006084 CALL msync(0x287c5000,0x453b7618,MS_ASYNC) > : 65074 python 0.106284 RET msync 0 > :... > :As you can see, it's quite a bit faster. > : > :I know that msync is necessary under Linux but obsolete under FreeBSD, but > :it's still funny that it takes a tenth of a second to return even with > :MS_ASYNC specified. > : > :Also, why is it that the madvise() calls take so much longer when the > :program does a couple of its own madvise() calls? Was madvise() never > :intended to be run so frequently and is therefore a little slower than > :it could be? > : > :Here's the diff between the code for the first kdump above and the > :second one. > > Those times are way way too large, even with other running threads > in the system. madvise() should not take that long unless it is > being forced to wait on a busied page, and neither should msync(). > madvise() doesn't even do any I/O (or shouldn't anyhow). > > Try removing just the msync() but keep the madvise() calls and see > if the madvise() calls continue to take horrendous amounts of time. > Then try the vise-versa. Ok, first off, I'm noticing that of the 4 other files that this is doing the same operations on, sized 569, 940, 116 and 116mB, all of the msync() and madvise() calls are nice and fast. It's only with the 1161524760 byte file that msync is much, much slower. It's not linear -- it hits a wall somewhere between 940 and 1161 million bytes. With madvise() and without msync(), there are high numbers of faults, which matches the number of disk io operations. It goes through cycles, every once in a while stalling while about 60MB of data is dumped to disk at 20MB/s or so (buffers flushing?) At the beginning of each cycle it's fast, with 140 faults/s or so, and slows as the number of faults climbs to 180/s or so before stalling and flusing again. It never gets _really_ slow though. 36286 python 0.000016 NAMI "rg2.rrd" 36286 python 0.000025 RET open 7 36286 python 0.000009 CALL fstat(0x7,0xbfbfe428) 36286 python 0.000014 RET fstat 0 36286 python 0.000010 CALL mmap(0,0x453b7618,PROT_READ|PROT_WRITE,MAP_SHARED,0x7,0,0) 36286 python 0.000020 RET mmap 679235584/0x287c5000 36286 python 0.000010 CALL madvise(0x287c5000,0x453b7618,_MADV_RANDOM) 36286 python 0.000010 RET madvise 0 36286 python 0.000009 CALL madvise(0x287c5000,0x70,_MADV_WILLNEED) 36286 python 0.000067 RET madvise 0 36286 python 0.000016 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) 36286 python 0.000015 RET madvise 0 36286 python 0.000019 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) 36286 python 0.000013 RET madvise 0 36286 python 0.000010 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) 36286 python 0.000010 RET madvise 0 36286 python 0.000012 CALL gettimeofday(0xbfbfe554,0) 36286 python 0.000010 RET gettimeofday 0 36286 python 0.000014 CALL fcntl(0x7,,0xbfbfe478) 36286 python 0.000021 RET fcntl 0 36286 python 0.040061 CALL munmap(0x287c5000,0x453b7618) 36286 python 0.000324 RET munmap 0 36286 python 0.000016 CALL close(0x7) 36286 python 0.000044 RET close 0 36286 python 0.000113 CALL __sysctl(0xbfbfe388,0x2,0xbfbfe394,0xbfbfe398,0,0) 36286 python 0.000018 RET __sysctl 0 With msync() and without madvise(), things are very slow, and there are no faults, just writes. 61609 python 0.000016 NAMI "rg2.rrd" 61609 python 0.000024 RET open 7 61609 python 0.000010 CALL fstat(0x7,0xbfbfe428) 61609 python 0.000013 RET fstat 0 61609 python 0.000010 CALL mmap(0,0x453b7618,PROT_READ|PROT_WRITE,MAP_SHARED,0x7,0,0) 61609 python 0.000021 RET mmap 679235584/0x287c5000 61609 python 0.066603 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED) 61609 python 0.000057 RET madvise 0 61609 python 0.000009 CALL madvise(0x287c6000,0x1950,_MADV_WILLNEED) 61609 python 0.000010 RET madvise 0 61609 python 0.000009 CALL madvise(0x287c8000,0x8,_MADV_WILLNEED) 61609 python 0.000009 RET madvise 0 61609 python 0.000010 CALL gettimeofday(0xbfbfe554,0) 61609 python 0.000018 RET gettimeofday 0 61609 python 0.000014 CALL fcntl(0x7,,0xbfbfe478) 61609 python 0.000026 RET fcntl 0 61609 python 0.004044 CALL msync(0x287c5000,0x453b7618,MS_ASYNC) 61609 python 0.117374 RET msync 0 61609 python 0.000294 CALL munmap(0x287c5000,0x453b7618) 61609 python 0.000356 RET munmap 0 61609 python 0.000016 CALL close(0x7) 61609 python 0.000049 RET close 0 61609 python 0.000125 CALL __sysctl(0xbfbfe388,0x2,0xbfbfe394,0xbfbfe398,0,0) 61609 python 0.000018 RET __sysctl 0 > It kinda feels like a prior msync() is initiating physical I/O on > pages and a later mmap/madvise or page fault is being forced to > wait on the prior pages for the I/O to finish. > The size_t argument to msync() (0x453b7618) is highly questionable. > It could be ktrace reporting the wrong value, but maybe not. That's the size of rg2.rrd. It's 1161524760 bytes long. > On any sort of random writing test, particularly if multiple threads > are involved, specifying a size that large could result in very large > latencies. Looks like the source of my problem is very slow msync() on the file when the file is over a certain size. It's still fastest without either madvise or msync. Thanks for your time, Marcus From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 03:22:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79B1D1065685 for ; Fri, 27 Jun 2008 03:22:43 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id 63B5C8FC17 for ; Fri, 27 Jun 2008 03:22:43 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id HJN85633; Thu, 26 Jun 2008 20:12:33 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9DC4945047; Thu, 26 Jun 2008 20:12:33 -0700 (PDT) To: Volker In-Reply-To: Your message of "Thu, 26 Jun 2008 23:53:44 +0200." <48640FE8.9080501@vwsoft.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1214536353_60492P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 26 Jun 2008 20:12:33 -0700 From: "Kevin Oberman" Message-Id: <20080627031233.9DC4945047@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: Volker X-To_Domain: vwsoft.com X-To: Volker X-To_Email: volker@vwsoft.com X-To_Alias: volker Cc: freebsd-stable@freebsd.org, Kelly Black Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 03:22:43 -0000 --==_Exmh_1214536353_60492P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 26 Jun 2008 23:53:44 +0200 > From: Volker > Sender: owner-freebsd-stable@freebsd.org > > On 12/23/-58 20:59, Kelly Black wrote: > > Hello, > > > > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > > Now when I install world there is a problem booting. > > > > Here is what I do: > > cd /usr/src > > make buildworld > > make buildkernel KERNCONF=BLACK > > make installkernel KERNCONF=BLACK > > > > At this point I can reboot and all is good. After boot I install the new world: > > > > cd /usr/src > > mergemaster -p > > reboot into single user mode > > cd /usr/src > > make installworld > > mergemaster > > > > Now when I reboot there is a problem. I get an error that the system > > cannot boot. Part of it looks like this: > > Can't work out which disk we are booting from. > > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > > > If I boot from a live disk and replace /boot/loader with > > /boot/loader.old it boots up fine and everything looks good. A new > > world and a new kernel. I would be grateful for any help or any > > pointers. > > > > Sincerely, > > Kel > > > > PS I do not do anything special with my loader config files: > > > > $ cat loader.conf > >... > > Kelly, > > the /boot/loader.conf file does not come into play at that stage. Early > in the loader code, loader needs to figure out, which disk (BIOS device) > has been booted from. Until loader knows which device was booted up, > it's unable to access any files (even loader.conf) on your boot device. > > As I've never seen such a problem while upgrading any system, I suspect > your problem must be settings specific. Can you show me your kernel > config or are you using a plain vanilla GENERIC? Which arch are we > talking about? > > As I'm currently investigating another boot problem (but earlier in the > boot chain), I'll check boot logic in the source code and may check for > your issue, too, at that time, so it's just one effort. But please stay > patient for some days, as I'm currently too busy. We just got hit by this. The loader never loads and nothing boots. But a system admin discovered that the problem disappeared if the /boot.conf file was deleted. It just contained '-P'. Once this file was removed, the system just booted up as expected. When he changed it to -D or -h, the boot still locked up. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1214536353_60492P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIZFqhkn3rs5h7N1ERAn9+AJ99VWwmjA0qw6nB6HMj95Jr/bTjbwCeMIWi pTW8OGjfmTF9TaZ54Q1+mfw= =Tquw -----END PGP SIGNATURE----- --==_Exmh_1214536353_60492P-- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 03:55:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DED106567B for ; Fri, 27 Jun 2008 03:55:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FF578FC16 for ; Fri, 27 Jun 2008 03:55:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E6A781CC03E; Thu, 26 Jun 2008 20:55:40 -0700 (PDT) Date: Thu, 26 Jun 2008 20:55:40 -0700 From: Jeremy Chadwick To: Kevin Oberman Message-ID: <20080627035540.GA21710@eos.sc1.parodius.com> References: <48640FE8.9080501@vwsoft.com> <20080627031233.9DC4945047@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080627031233.9DC4945047@ptavv.es.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Volker , freebsd-stable@freebsd.org, Kelly Black Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 03:55:41 -0000 On Thu, Jun 26, 2008 at 08:12:33PM -0700, Kevin Oberman wrote: > > Date: Thu, 26 Jun 2008 23:53:44 +0200 > > From: Volker > > Sender: owner-freebsd-stable@freebsd.org > > > > On 12/23/-58 20:59, Kelly Black wrote: > > > Hello, > > > > > > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > > > Now when I install world there is a problem booting. > > > > > > Here is what I do: > > > cd /usr/src > > > make buildworld > > > make buildkernel KERNCONF=BLACK > > > make installkernel KERNCONF=BLACK > > > > > > At this point I can reboot and all is good. After boot I install the new world: > > > > > > cd /usr/src > > > mergemaster -p > > > reboot into single user mode > > > cd /usr/src > > > make installworld > > > mergemaster > > > > > > Now when I reboot there is a problem. I get an error that the system > > > cannot boot. Part of it looks like this: > > > Can't work out which disk we are booting from. > > > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > > > > > If I boot from a live disk and replace /boot/loader with > > > /boot/loader.old it boots up fine and everything looks good. A new > > > world and a new kernel. I would be grateful for any help or any > > > pointers. > > > > > > Sincerely, > > > Kel > > > > > > PS I do not do anything special with my loader config files: > > > > > > $ cat loader.conf > > >... > > > > Kelly, > > > > the /boot/loader.conf file does not come into play at that stage. Early > > in the loader code, loader needs to figure out, which disk (BIOS device) > > has been booted from. Until loader knows which device was booted up, > > it's unable to access any files (even loader.conf) on your boot device. > > > > As I've never seen such a problem while upgrading any system, I suspect > > your problem must be settings specific. Can you show me your kernel > > config or are you using a plain vanilla GENERIC? Which arch are we > > talking about? > > > > As I'm currently investigating another boot problem (but earlier in the > > boot chain), I'll check boot logic in the source code and may check for > > your issue, too, at that time, so it's just one effort. But please stay > > patient for some days, as I'm currently too busy. > > We just got hit by this. The loader never loads and nothing boots. But a > system admin discovered that the problem disappeared if the /boot.conf > file was deleted. It just contained '-P'. > > Once this file was removed, the system just booted up as expected. When > he changed it to -D or -h, the boot still locked up. I believe you mean /boot.config. :-) -P set the console to the serial port assuming no AT/PS2 keyboard is connected to the machine. -D and -h are described in more detail in the Handbook. Even with -P, -D, -h, or -Dh, the system *should* still actually boot up, you just won't see anything on the VGA console until the system is fully up and getty/login is run against ttyv0 (VGA console login). If Kelly has no /boot.config, then I'd say the issue you're reporting is a different bug/problem, but should still be investigated. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 04:17:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 130481065680 for ; Fri, 27 Jun 2008 04:17:14 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [198.124.252.66]) by mx1.freebsd.org (Postfix) with ESMTP id CA4C88FC15 for ; Fri, 27 Jun 2008 04:17:13 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal3.es.net [198.128.3.207]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id HKS46611; Thu, 26 Jun 2008 21:17:11 -0700 Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id HKS80008; Thu, 26 Jun 2008 21:17:08 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9609B45047; Thu, 26 Jun 2008 21:17:08 -0700 (PDT) To: Jeremy Chadwick In-Reply-To: Your message of "Thu, 26 Jun 2008 20:55:40 PDT." <20080627035540.GA21710@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1214540228_60492P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 26 Jun 2008 21:17:08 -0700 From: "Kevin Oberman" Message-Id: <20080627041708.9609B45047@ptavv.es.net> X-Sender-IP: 198.128.3.207 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: Jeremy Chadwick X-To_Domain: freebsd.org X-To: Jeremy Chadwick X-To_Email: koitsu@FreeBSD.org X-To_Alias: koitsu Cc: Volker , freebsd-stable@freebsd.org, Kelly Black Subject: Re: Problem with /boot/loader X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 04:17:14 -0000 --==_Exmh_1214540228_60492P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 26 Jun 2008 20:55:40 -0700 > From: Jeremy Chadwick > > On Thu, Jun 26, 2008 at 08:12:33PM -0700, Kevin Oberman wrote: > > > Date: Thu, 26 Jun 2008 23:53:44 +0200 > > > From: Volker > > > Sender: owner-freebsd-stable@freebsd.org > > > > > > On 12/23/-58 20:59, Kelly Black wrote: > > > > Hello, > > > > > > > > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > > > > Now when I install world there is a problem booting. > > > > > > > > Here is what I do: > > > > cd /usr/src > > > > make buildworld > > > > make buildkernel KERNCONF=BLACK > > > > make installkernel KERNCONF=BLACK > > > > > > > > At this point I can reboot and all is good. After boot I install the new world: > > > > > > > > cd /usr/src > > > > mergemaster -p > > > > reboot into single user mode > > > > cd /usr/src > > > > make installworld > > > > mergemaster > > > > > > > > Now when I reboot there is a problem. I get an error that the system > > > > cannot boot. Part of it looks like this: > > > > Can't work out which disk we are booting from. > > > > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > > > > > > > If I boot from a live disk and replace /boot/loader with > > > > /boot/loader.old it boots up fine and everything looks good. A new > > > > world and a new kernel. I would be grateful for any help or any > > > > pointers. > > > > > > > > Sincerely, > > > > Kel > > > > > > > > PS I do not do anything special with my loader config files: > > > > > > > > $ cat loader.conf > > > >... > > > > > > Kelly, > > > > > > the /boot/loader.conf file does not come into play at that stage. Early > > > in the loader code, loader needs to figure out, which disk (BIOS device) > > > has been booted from. Until loader knows which device was booted up, > > > it's unable to access any files (even loader.conf) on your boot device. > > > > > > As I've never seen such a problem while upgrading any system, I suspect > > > your problem must be settings specific. Can you show me your kernel > > > config or are you using a plain vanilla GENERIC? Which arch are we > > > talking about? > > > > > > As I'm currently investigating another boot problem (but earlier in the > > > boot chain), I'll check boot logic in the source code and may check for > > > your issue, too, at that time, so it's just one effort. But please stay > > > patient for some days, as I'm currently too busy. > > > > We just got hit by this. The loader never loads and nothing boots. But a > > system admin discovered that the problem disappeared if the /boot.conf > > file was deleted. It just contained '-P'. > > > > Once this file was removed, the system just booted up as expected. When > > he changed it to -D or -h, the boot still locked up. > > I believe you mean /boot.config. :-)] Fingers faster than brain. Sorry. > -P set the console to the serial port assuming no AT/PS2 keyboard is > connected to the machine. -D and -h are described in more detail in the > Handbook. man boot describes that pretty well, to0. > > Even with -P, -D, -h, or -Dh, the system *should* still actually boot > up, you just won't see anything on the VGA console until the system is > fully up and getty/login is run against ttyv0 (VGA console login). The system in question are servers and have no VGA console. They just hung without any sign of the loader, but when he used the old loader, the system booted normally. I thought that /boot.config was read by boot2, so it should be over an done with before loader is even started. All I can think is that the result of having set any of these flags, all of which are related, causes loader(8) to go off the deep end. I think I'll suggest that he try just -s in /boot.config > If Kelly has no /boot.config, then I'd say the issue you're reporting is > a different bug/problem, but should still be investigated. It may be different or it may be a different manifestation of the same one. Rather hard to tell at this point. I am very busy with preparation for a major upgrade to our Chicago hubs and may not get much chance to play with these now, but I'll ask the admin to give it a shot, along with an empty /boot.config. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1214540228_60492P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIZGnEkn3rs5h7N1ERAoHGAKCuruBQDWrH3+kWkKBY75rTITuD7QCfSb8p EqMeVmpP13RrR02uGmDC2fU= =59bS -----END PGP SIGNATURE----- --==_Exmh_1214540228_60492P-- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 06:21:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 651F11065675 for ; Fri, 27 Jun 2008 06:21:32 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 42DD38FC14 for ; Fri, 27 Jun 2008 06:21:32 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m5R6LTAR026413; Thu, 26 Jun 2008 23:21:29 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m5R6LTum026412; Thu, 26 Jun 2008 23:21:29 -0700 (PDT) Date: Thu, 26 Jun 2008 23:21:29 -0700 (PDT) From: Matthew Dillon Message-Id: <200806270621.m5R6LTum026412@apollo.backplane.com> To: Marcus Reid References: <20080626234455.GA77263@blazingdot.com> <200806270048.m5R0mDIU024172@apollo.backplane.com> <20080627023455.GA34022@blazingdot.com> Cc: freebsd-stable@freebsd.org Subject: Re: Performance of madvise / msync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 06:21:32 -0000 :With madvise() and without msync(), there are high numbers of :faults, which matches the number of disk io operations. It :goes through cycles, every once in a while stalling while about :60MB of data is dumped to disk at 20MB/s or so (buffers flushing?) :At the beginning of each cycle it's fast, with 140 faults/s or so, :and slows as the number of faults climbs to 180/s or so before :stalling and flusing again. It never gets _really_ slow though. Yah, without the msync() the dirty pages build up in the kernel's VM page cache. A flush should happen automatically every 30-60 seconds, or sooner if the buffer cache builds up too many dirty pages. The activity you are seeing sounds like the 30-60 second filesystem sync the kernel does periodically. Either NetBSD or OpenBSD, I forget which, implemented a partial sync feature to prevent long stalls when the filesystem syncer hits a file with a lot of dirty pages. FreeBSD could borrow that optimization if they want to reduce stalls from the filesytem sync. I ported it to DFly a while back myself. :With msync() and without madvise(), things are very slow, and :there are no faults, just writes. :... :> The size_t argument to msync() (0x453b7618) is highly questionable. :> It could be ktrace reporting the wrong value, but maybe not. : :That's the size of rg2.rrd. It's 1161524760 bytes long. :... :Looks like the source of my problem is very slow msync() on the :file when the file is over a certain size. It's still fastest :without either madvise or msync. : :Thanks for your time, : :Marcus The msync() is clearly the problem. There are numerous optimizations in the kernel but msync() is frankly a rather nasty critter even with the optimizations work. Nobody using msync() in real life ever tries to run it over the entirety of such a large mapping... usually it is just run on explicit sub-ranges that the program wishes to sync. One reason why msync() is so nasty is that the kernel must physically check the page table(s) to determine whether a page has been marked dirty by the MMU, so it can't just iterate the pages it knows are dirty in the VM object. It's nasty whether it scans the VM object and iterates the page tables, or scans the page tables and looks up the related VM pages. The only way to optimize this is to force write-faults by mapping clean pages read-only, in order to track whether a page is actually dirty in real time instead of lazily. Then msync() would only have to do a ranged-scan of the VM object's dirty-page list and would not have to actually check the page tables for clean pages. A secondary effect of the msync() is that it is initiating asynchronous I/O for what sounds like hundreds of VM pages, or even more. All those pages are locked and busied from the point they are queued to the point the I/O finishes, which for some of the pages can be a very, very long time (into the multiples of seconds). Pages locked that long will interfere with madvise() calls made after the msync(), and probably even interfere with the follow msync(). It used to be that msync() only synced VM pages to the underlying file, making them consistent with read()'s and write()'s against the underlying file. Since FreeBSD uses a unified VM page cache this is always true. However, the Open Group specification now requires that the dirty pages actually be written out to the underlying media... i.e. issue real I/O. So msync() can't be a NOP if you go by the OpenGroup specification. -Matt Matthew Dillon From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 07:28:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08904106564A for ; Fri, 27 Jun 2008 07:28:58 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by mx1.freebsd.org (Postfix) with ESMTP id 8309A8FC1A for ; Fri, 27 Jun 2008 07:28:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5R7SsNA022913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jun 2008 17:28:55 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m5R7SsMs022863; Fri, 27 Jun 2008 17:28:54 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m5R7SshC022862; Fri, 27 Jun 2008 17:28:54 +1000 (EST) (envelope-from peter) Date: Fri, 27 Jun 2008 17:28:54 +1000 From: Peter Jeremy To: Sabeeh Baig Message-ID: <20080627072853.GB50631@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vmttodhTwj0NAgWp" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: jdk16 web plugin on FreeBSD 7 AMD64 Issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 07:28:58 -0000 --vmttodhTwj0NAgWp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-26 16:23:23 -0400, Sabeeh Baig wrote: >that the plugins from jdk16 and jdk15 on AMD64 worked. I can't comment on jdk16 but the jdk15 plugin does not work on amd64. There is a patch for jdk15 at ports/122904 that works for me. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --vmttodhTwj0NAgWp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhklrUACgkQ/opHv/APuIdo5wCbBbSA0Gr+aGr5FNMu+DKyNQZ7 7JgAn3pAtEAP2omP4hM/Og7VHkKfwAI6 =/JmZ -----END PGP SIGNATURE----- --vmttodhTwj0NAgWp-- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 09:55:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CB631065678 for ; Fri, 27 Jun 2008 09:55:50 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.freebsd.org (Postfix) with ESMTP id 69F738FC36 for ; Fri, 27 Jun 2008 09:55:50 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [212.123.145.58] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp id 1KCAgG-0005bo-MM for ; Fri, 27 Jun 2008 11:55:48 +0200 Received: (qmail 1652 invoked from network); 27 Jun 2008 09:55:46 -0000 Received: from localhost (HELO guido.klop.ws) (127.0.0.1) by localhost with SMTP; 27 Jun 2008 09:55:46 -0000 Date: Fri, 27 Jun 2008 11:55:45 +0200 To: "Gavin Atkinson" , "Ronald Klop" From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <20080616102144.4E3312844C@ronald.office.base.nl> <1214496067.23553.42.camel@buffy.york.ac.uk> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <1214496067.23553.42.camel@buffy.york.ac.uk> User-Agent: Opera Mail/9.50 (FreeBSD) Cc: "freebsd-stable@freebsd.org" Subject: Re: panic in drm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 09:55:50 -0000 On Thu, 26 Jun 2008 18:01:07 +0200, Gavin Atkinson wrote: > On Thu, 2008-06-26 at 16:09 +0200, Ronald Klop wrote: >> Hello, >> >> At my work I see a panic if I do this. >> Leaf my computer on screensaver (don't no if that is necessary) and come >> back the next morning. My monitor is than black, but the light is green, >> so DPMS didn't kick in. >> Keys or mouse don't wake up the system. CTRL-ALT-F1 switches to the >> console and immediately triggers this panic. >> >> I'm running latest x.org with xf86-video-i810-1.7.4_1. The newer >> xf86-video-intel also crashes my system sometimes when I'm working on >> it, >> so a downgraded. >> >> Any ideas, suggestions or fixes available? > > This sounds very familiar to me. I think I was seeing the same panic in > 2006... > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-12/msg00344.html > > Can you add this to src/sys/dev/drm/i915_irq.c > > if (!dev->irqr) { > return DRM_ERR(EINVAL); > } > > just above the DRM_WAIT_ON in i915_driver_vblank_wait() (around line > 140), and see if that prevents the panic? Note that I believe this to > be a workaround, and not really the correct fix. > > (sorry for not supplying patches, I'm not in a position to right now) > > Gavin Thanks, I'll try this next week. Ronald. From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 11:47:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63BF91065671 for ; Fri, 27 Jun 2008 11:47:13 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mx1.freebsd.org (Postfix) with ESMTP id 407DB8FC17 for ; Fri, 27 Jun 2008 11:47:13 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so519281rvf.43 for ; Fri, 27 Jun 2008 04:47:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=2WKLMABHWx02dYiB2eA7j3d33sDwUGckN7IUwiuNMGo=; b=eAHlykcvJo49XCqCVQlTD5IRXwWeqAoz7f7IiWCP1wyyodMGx7wrUdSKj51DDuyILt C2XOEkj1/ZwWkRFPH125lS2tsXaA93qpAAKC5tqmR3Z8dYCQBV0riPv+HzaWJg1+LUMZ 2MyPrxAXMWrh4Em3Y1WzFX3MVuH+sqagY0jvQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=iWDWSCup0pND1XePud0aDEVFooUFfT6BOwKL9qU4r2sXRrzc0mAgruUs4Z3OzN2dzv AhazAFIOF3ZFOvH+HRvocsrBi4bCeLf5MdWHGny7efWaLmfDQld9SZyhEHSb3A4/DJfd 38BbhiRupPN8FqU/xh8/cS/WG/QKVzwhbwjg0= Received: by 10.141.20.7 with SMTP id x7mr730094rvi.61.1214567232689; Fri, 27 Jun 2008 04:47:12 -0700 (PDT) Received: by 10.141.159.2 with HTTP; Fri, 27 Jun 2008 04:47:12 -0700 (PDT) Message-ID: <9bbcef730806270447k45d5f0ack872d0574e2baaa1a@mail.gmail.com> Date: Fri, 27 Jun 2008 13:47:12 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: d@delphij.net, freebsd-stable@freebsd.org In-Reply-To: <486435FC.2000100@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10806061443v3e44576am2facb75df031f47e@mail.gmail.com> <47713ee10806062148l4a4c4550hcd8c70a422343c2a@mail.gmail.com> <486435FC.2000100@delphij.net> X-Google-Sender-Auth: 7ce00b45617e7bdb Cc: Subject: Re: TMPFS: File System is Full X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 11:47:13 -0000 Thanks for the clarification! In the context of this thread my answer was wrong - I thought tmpfs allocates from kmem for bulk storage, like one mode of mdmfs does. In this light, it shouldn't compete with zfs nearly as much as I assumed. On the bright side, and a bit offtopic, amd64 will get the ability to allocate a lot more of memory for kmem soon, so people having problems with zfs will be relieved. On 6/27/08, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ivan Voras wrote: > | Lin Jui-Nan Eric wrote: > | > |> I think there should be a "lower bound" size limit. Does TMPFS use > |> kernel-space memory? > | > | Yes, tmpfs does use kmem and competes with ZFS. > > Yes and no. tmpfs makes use of some kernel memory but most of data is > stored in swappable memory. > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkhkNfsACgkQi+vbBBjt66Ad8ACfYD1Yq09oY7iIjxq353iMFKKp > FGYAnjA3I8V2cN1s1EW2NuwfhilaJBMe > =vnM3 > -----END PGP SIGNATURE----- > -- Sent from Gmail for mobile | mobile.google.com From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 20:37:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 808CC1065671 for ; Fri, 27 Jun 2008 20:37:27 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by mx1.freebsd.org (Postfix) with ESMTP id 4AD858FC1B for ; Fri, 27 Jun 2008 20:37:27 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ItFe5Q6PLV8Y9I1/0Wa0ilUtNdmqNG1F23kiqza0VLqunFC4AGbnMqwMuAm9bBXc; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [24.144.77.185] (helo=joker.seclark.com) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KCKh9-0006oB-2P; Fri, 27 Jun 2008 16:37:23 -0400 Message-ID: <48654F81.6010500@earthlink.net> Date: Fri, 27 Jun 2008 16:37:21 -0400 From: Stephen Clark User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Niki Denev References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> <2e77fc10806221101q684baf47r9ee7208a676f59e@mail.gmail.com> In-Reply-To: <2e77fc10806221101q684baf47r9ee7208a676f59e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec791b32a657581f72633fffca373294f6fd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.144.77.185 Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, =?ISO-8859-1?Q?Patrick_Lamaizi=E8re?= Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 20:37:27 -0000 Niki Denev wrote: > On Sun, Jun 22, 2008 at 6:05 PM, Patrick Lamaizière > wrote: >> Le Fri, 6 Jun 2008 23:41:35 +0200, >> Patrick Lamaizière a écrit : >> >> Hello, >> >>> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >>> (via the NetBSD port). >>> " The glxsb driver supports the security block of the Geode LX >>> series processors. The Geode LX is a member of the AMD Geode family >>> of integrated x86 system chips. >>> >>> Driven by periodic checks for available data from the generator, >>> glxsb supplies entropy to the random(4) driver for common usage. >>> >>> glxsb also supports acceleration of AES-128-CBC operations for >>> crypto(4)." >> Well, I hope this is the final version. >> >> http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz >> >> I added a patch for FreeBSD 6 but i'am not able to test it. >> >> On 7-STABLE, I've tested with hundred openssl encryptions and some flood >> pings under ipsec in the background. Looks good for me. >> >> If someone can test and review it, it would be cool. >> >> Thanks, Regards. > > It compiles on without a problem on 6.2 and loads on my Soekris > Net5501-70 running pfSense (6.2-RELEASE-p11) > > glxsb0: mem > 0xa0000000-0xa0003fff irq 10 at device 1.2 on pci0 > > Thanks!, > Niki > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Hi, I am trying to compile it on 6.2 and get make: don't know how to make cryptodev_if.h. Stop ??? where is this file? Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 21:11:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DDD51065670 for ; Fri, 27 Jun 2008 21:11:00 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id E43908FC1D for ; Fri, 27 Jun 2008 21:10:59 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so401777wah.3 for ; Fri, 27 Jun 2008 14:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=01JYop0RbRaLaGq//WHSc10twMbu3pLOteP+j3sv/jE=; b=H95YAcSPGKCgzGprh9Wwr5R9pAGrG95Iovv2IXZZB8rKsyOe9gOx083JDCDdwRfPAZ vDUdFHL4lpgGlCowKAvYAROTtKyczm7BN2CYfwBX1IukADb8OIeGIaUXgeSl6MYZ3ZCr Y8Gl6iK2Y4dtHaGXtLkxJgMrf5+LsK5OhDmsk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xX5eQuhj2iOACzhq8soFKgvq6Bq77qS14cA4tcVBahnGYM6V5Ihp5aRdakmLqSsFuP qUNGAfqaCJzb1sZ9CzyR42KTdCYwTxjZ8OZs0Gp0hBA2Drezi7wQqTsmy0WtFpef/z2l IG2e8QKBjl+YJ3yAHHEQ4Pe9IlDC9zePkJlTE= Received: by 10.114.171.1 with SMTP id t1mr2014860wae.120.1214601059600; Fri, 27 Jun 2008 14:10:59 -0700 (PDT) Received: by 10.114.80.5 with HTTP; Fri, 27 Jun 2008 14:10:59 -0700 (PDT) Message-ID: <2e77fc10806271410q3205fb21r9aed15ec8b035401@mail.gmail.com> Date: Sat, 28 Jun 2008 00:10:59 +0300 From: "Niki Denev" To: sclark46@earthlink.net In-Reply-To: <48654F81.6010500@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080622170507.5ac469d2@baby-jane-lamaiziere-net.local> <2e77fc10806221101q684baf47r9ee7208a676f59e@mail.gmail.com> <48654F81.6010500@earthlink.net> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 21:11:00 -0000 On Fri, Jun 27, 2008 at 11:37 PM, Stephen Clark wrote: > Hi, > > I am trying to compile it on 6.2 and get > make: don't know how to make cryptodev_if.h. Stop > > ??? > where is this file? > > Thanks, > Steve > Have you applied the 6.2 patch included in the latest tgz that Patrick posted? Regards, Niki From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 21:49:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 973081065673; Fri, 27 Jun 2008 21:49:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.freebsd.org (Postfix) with ESMTP id 3486C8FC0C; Fri, 27 Jun 2008 21:49:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail18.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5RLnFa5018555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Jun 2008 07:49:16 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m5RLnCic027077; Sat, 28 Jun 2008 07:49:12 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m5RLnCNl027076; Sat, 28 Jun 2008 07:49:12 +1000 (EST) (envelope-from peter) Date: Sat, 28 Jun 2008 07:49:12 +1000 From: Peter Jeremy To: freebsd-stable@freebsd.org Message-ID: <20080627214912.GB50631@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TeJTyD9hb8KJN2Jy" Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: pjd@freebsd.org Subject: GEOM gotcha upgrading from 6.x to 7.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 21:49:18 -0000 --TeJTyD9hb8KJN2Jy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yesterday, I planned to try an upgrade from 6.x to 7.x on one of the servers at work, on the assumption that I could reasonably easily revert to 6.x if things went bad. My confidence in being able to do that was severely shaken when I saw "Upgrading metadata" messages for both geom_mirror disks when the 7.x kernel booted. Whilst I did not need to revert, some examination of the geom_mirror source shows that (as I feared), a 6.x kernel will choke on a 7.x geom_mirror. I've looked through the various geom man pages, UPDATING, the relevant commit message and various mailing lists and am unable to find any mention of this. Having the kernel automatically alter persistent state on the host in a way that is incompatible with earlier kernels is bad enough. Doing so without any mechanism to revert the change and with no "heads-up" warning of the change is, IMO, unacceptable. I accept that it's sometimes necessary to make changes that are not backward compatible or that are difficult to revert, such changes are normally discussed in advance and come with heads-up warnings. I can't think of any previous case where simply test booting a kernel is enough to render your system unusable with an older kernel. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --TeJTyD9hb8KJN2Jy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhlYFgACgkQ/opHv/APuIfZiACgo0EFnN62byDhlOqSzRpI9LSM IdMAoJh616q1aTqMl4ToyB2eoQvyMyog =6Kp/ -----END PGP SIGNATURE----- --TeJTyD9hb8KJN2Jy-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 28 04:18:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1FDF1065677; Sat, 28 Jun 2008 04:18:41 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 482B78FC16; Sat, 28 Jun 2008 04:18:41 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from nbc.matik.com.br (nbc.matik.com.br [200.152.88.34] (may be forged)) by msrv.matik.com.br (8.14.2/8.14.2) with ESMTP id m5S4IL8B082926; Sat, 28 Jun 2008 01:18:21 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Sat, 28 Jun 2008 01:17:15 -0300 User-Agent: KMail/1.9.7 References: <200805180956.18211.joao@matik.com.br> <200805181220.33599.joao@matik.com.br> <20080518153911.GA22300@eos.sc1.parodius.com> In-Reply-To: <20080518153911.GA22300@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200806280117.16057.joao@matik.com.br> X-Virus-Scanned: ClamAV 0.93.1/7579/Fri Jun 27 16:52:12 2008 on msrv.matik.com.br X-Virus-Status: Clean Cc: Torfinn Ingolfsen , Jeremy Chadwick , freebsd-bugs@freebsd.org, Greg Byshenk Subject: Re: possible zfs bug? lost all pools X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 04:18:42 -0000 On Sunday 18 May 2008 12:39:11 Jeremy Chadwick wrote: =2E.. >>> and if necessary /etc/rc.d/zfs should start hostid or at least set REQU= IRE=20 >>> different and warn =2E.. >> >> I've been in the same boat you are, and I was told the same thing. I've >> documented the situation on my Wiki, and the necessary workarounds. >> >> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issue > so I changed the rcorder as you can see in the attached filesile > http://suporte.matik.com.br/jm/zfs.rcfiles.tar.gz i'm coming back on this because I am convicted to zfs each day more and mo= re=20 and like to express my gratitude not only to whom made zfs but also and=20 specially to the people who brought it to FBSD - and: thank you guys making= =20 it public, this is really a step forward! my zfs related rc files changes(above) made my problems go away and like to= =20 share some other experience here as on Jeremie's page explained I had similare problems with zfs but seems I= =20 could get around them with (depending on machine's load) setting either to= =20 500, 1000 or 1500k vm.kmem_size* ... but seems main problem on FBSD is zfs= =20 recordsize, on ufs like partitions I set it to 64k and I never got panics a= ny=20 more, even with several zpools (as said as dangerous), cache_dirs for squid= =20 or mysql partitions might need lower values to get to there new and=20 impressive peaks.=20 this even seems to solve panics when copying large files from nfs|ufs to or= =20 from zfs ... so seems that FBSD do not like recordsize>64k ... I have now a mail server running, for almost two month, with N zfs volumes= =20 (one per user) in order simulating quotas (-/+ 1000 users) with success and= =20 completely stable and performance is outstanding under all loads web server, apache/php/mysql, gave up maior stability problems but=20 distributing depending on workload to zpools with different recordsizes and= =20 never >64k solved my problems and I am appearently panic free now I run almost scsi-only, only my test machines are sata, lowest conf is X2/4= G,=20 rest is X4 or opterons with 8g or more and I am extremely satisfied and hap= py=20 with zfs my backups are running twice as fast as on ufs, mirroring in comparims to=20 gmirror is fucking-incredible fast and the zfs snapshot thing deserves an=20 Oscar! ... and the zfs send|receive another so thank you all who had fingers in/on zfs! (sometimes I press reset at my= =20 home server only to see how fast it comes up) .. just kidding but true is:= =20 thank's again! zfs is thE fs. =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Sat Jun 28 06:04:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E99B6106564A for ; Sat, 28 Jun 2008 06:04:00 +0000 (UTC) (envelope-from ob@gruft.de) Received: from obh.snafu.de (v6.gruft.de [IPv6:2001:1560:2342::2]) by mx1.freebsd.org (Postfix) with ESMTP id 271BB8FC0C for ; Sat, 28 Jun 2008 06:03:55 +0000 (UTC) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KCTXM-0007NM-It; Sat, 28 Jun 2008 08:03:52 +0200 Date: Sat, 28 Jun 2008 08:03:52 +0200 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20080628060352.GZ6902@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org, Peter Jeremy References: <20080627214912.GB50631@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gvF4niNJ+uBMJnEh" Content-Disposition: inline In-Reply-To: <20080627214912.GB50631@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: Oliver Brandmueller Cc: Peter Jeremy Subject: Re: GEOM gotcha upgrading from 6.x to 7.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 06:04:01 -0000 --gvF4niNJ+uBMJnEh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, On Sat, Jun 28, 2008 at 07:49:12AM +1000, Peter Jeremy wrote: > Yesterday, I planned to try an upgrade from 6.x to 7.x on one of the > servers at work, on the assumption that I could reasonably easily > revert to 6.x if things went bad. My confidence in being able to > do that was severely shaken when I saw "Upgrading metadata" messages > for both geom_mirror disks when the 7.x kernel booted. >=20 > Whilst I did not need to revert, some examination of the geom_mirror > source shows that (as I feared), a 6.x kernel will choke on a 7.x > geom_mirror. I didn't try now, but from my experience it should be fairly easy to=20 revert: Boot without gmirror from one the disks with the old kernel.=20 Have an old world available (CD, not yet installworld'ed) an write=20 gmirror label from single user mode with old metadata, add the other=20 disk and rebuild (more or less just go the way you go to setup a=20 bootable gmirror from an existing system). You would be in more trouble if you had some kind of real RAID format=20 (like a RAID 5 or something) on the disk, but gmirror is basically a set=20 of metadata whilst any single disk of the mirror is actually in a=20 format, that can be used without gmirror. I agree, that this is not actually straigt forward (as downgrading isn't=20 anyhow), but for the case "I see my 7.x kernel choking when upgrading=20 =66rom 6.x to 7.x" it should still be easy enough for an experienced=20 admin. Greetings, Oliver --=20 | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | --gvF4niNJ+uBMJnEh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhl1EgACgkQiqtMdzjafymHmACgvd+e/GolQSBgj03FC42XY0p+ 2IoAnAs3MqOetiyELVP+kQ3pncRNwUaq =yrAY -----END PGP SIGNATURE----- --gvF4niNJ+uBMJnEh-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 28 10:35:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DDA41065686 for ; Sat, 28 Jun 2008 10:35:51 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id C92C98FC19 for ; Sat, 28 Jun 2008 10:35:50 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m5SAKB72007979; Sat, 28 Jun 2008 14:20:11 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 28 Jun 2008 14:20:11 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <485243BB.7050604@FreeBSD.org> Message-ID: <20080628141905.I89957@woozle.rinet.ru> References: <485243BB.7050604@FreeBSD.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sat, 28 Jun 2008 14:20:11 +0400 (MSD) Cc: Timothy Wilson , freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 10:35:51 -0000 On Fri, 13 Jun 2008, Kris Kennaway wrote: KK> It is planned to update to a newer ZFS release in HEAD, but this has not KK> happened yet (let alone in 7.x). I don't know if it is possible to KK> downgrade a pool - you should check the ZFS documentation/support materials. It seems there is no such way; what is worse, it also seems there's no way to create a pool with lower pool version. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Jun 28 22:43:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD23A1065673 for ; Sat, 28 Jun 2008 22:43:28 +0000 (UTC) (envelope-from dillon@terranova.net) Received: from loveturtle.net (loveturtle.net [216.89.228.174]) by mx1.freebsd.org (Postfix) with ESMTP id 7F1178FC19 for ; Sat, 28 Jun 2008 22:43:28 +0000 (UTC) (envelope-from dillon@terranova.net) Received: from localhost (localhost [127.0.0.1]) by loveturtle.net (Postfix) with ESMTP id B4BA13E76 for ; Sat, 28 Jun 2008 18:26:21 -0400 (EDT) X-Virus-Scanned: amavisd-new at loveturtle.net Received: from loveturtle.net ([127.0.0.1]) by localhost (loveturtle.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ijNa6aBhyMS for ; Sat, 28 Jun 2008 18:26:19 -0400 (EDT) Received: from vier.loveturtle.net (vier.loveturtle.net [216.182.254.140]) by loveturtle.net (Postfix) with ESMTP id 764283E6A for ; Sat, 28 Jun 2008 18:26:19 -0400 (EDT) Message-ID: <4866BA8B.9030004@terranova.net> Date: Sat, 28 Jun 2008 18:26:19 -0400 From: Dillon User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <485243BB.7050604@FreeBSD.org> <20080628141905.I89957@woozle.rinet.ru> In-Reply-To: <20080628141905.I89957@woozle.rinet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS version 8 on stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 22:43:28 -0000 ZFS On Mac OSX creates zfs v6 pools by default (in order to retain compat with the stock read-only zfs v6 module in 10.5) which work fine with FreeBSD. Just don't upgrade the pool on OS-X after creating it. Dmitry Morozovsky wrote: > On Fri, 13 Jun 2008, Kris Kennaway wrote: > > KK> It is planned to update to a newer ZFS release in HEAD, but this has not > KK> happened yet (let alone in 7.x). I don't know if it is possible to > KK> downgrade a pool - you should check the ZFS documentation/support materials. > > It seems there is no such way; what is worse, it also seems there's no way to > create a pool with lower pool version. > > > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > [ FreeBSD committer: marck@FreeBSD.org ] > ------------------------------------------------------------------------ > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > ------------------------------------------------------------------------ > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >