From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 24 11:02:46 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DF2416A404 for ; Mon, 24 Apr 2006 11:02:46 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A31A243D70 for ; Mon, 24 Apr 2006 11:02:35 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3OB2ZZo035400 for ; Mon, 24 Apr 2006 11:02:35 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3OB2XEd035394 for freebsd-amd64@freebsd.org; Mon, 24 Apr 2006 11:02:33 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 24 Apr 2006 11:02:33 GMT Message-Id: <200604241102.k3OB2XEd035394@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 11:02:46 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing o [2006/03/01] amd64/93961 amd64 Problem in bounce buffer handling in sys/ 3 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMP o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/24] amd64/89501 amd64 System crashes on install using ftp on lo o [2005/11/24] amd64/89503 amd64 Cant Boot Installation Disk o [2005/11/25] amd64/89546 amd64 [geom] GEOM error o [2005/11/25] amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o [2005/11/25] amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o [2005/12/05] amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem o [2006/01/06] amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr o [2006/01/08] amd64/91492 amd64 BTX halted o [2006/01/26] amd64/92337 amd64 FreeBsd 6.0 Release Intel Pro 1000 MT em1 o [2006/02/06] amd64/92889 amd64 xdr double buffer overflow o [2006/02/07] amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk o [2006/02/08] amd64/93065 amd64 Running make depend on GENERIC kernel fai o [2006/02/14] amd64/93325 amd64 mount_ufs fails mounting Nero UFS DVD+RW o [2006/02/16] amd64/93413 amd64 lpd does not remove lock file from /var/s o [2006/02/17] amd64/93469 amd64 uninitialised struct stat in lpd prevents o [2006/03/19] amd64/94677 amd64 panic in amd64 install at non-root user c o [2006/03/24] amd64/94896 amd64 Where support VESA Modes for AMD64 kernel o [2006/03/27] amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 ( o [2006/03/28] amd64/95056 amd64 Nvidia Nforce ETH Driver -> Timeout Error o [2006/03/31] amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AI o [2006/04/06] amd64/95414 amd64 kernel crashes during install o [2006/04/06] amd64/95418 amd64 pthread segmentation fault o [2006/04/09] amd64/95554 amd64 undetected sata drive on 6.1, detected on o [2006/04/16] amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying 65 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins o [2006/01/02] amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP o [2006/01/30] amd64/92527 amd64 no driver for "CICADA VSC 8201 Gigabit LA o [2006/02/07] amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable ti o [2006/02/09] amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognize o [2006/02/28] amd64/93930 amd64 Page fault on `kldunload snd_driver` o [2006/04/03] amd64/95282 amd64 patch: fix ed for RELENG_5 amd64 so that o [2006/04/12] amd64/95651 amd64 CANT INSTALL 20 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 24 12:21:10 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD5B416A402 for ; Mon, 24 Apr 2006 12:21:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C75CE43D45 for ; Mon, 24 Apr 2006 12:21:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3OCL161052344; Mon, 24 Apr 2006 08:21:02 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 24 Apr 2006 08:10:40 -0400 User-Agent: KMail/1.8.3 References: <20060421155557.6f67d078@localhost> In-Reply-To: <20060421155557.6f67d078@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604240810.41689.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1423/Mon Apr 24 04:24:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: Erroneous COMPAT dependencies mentioned in NOTES X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 12:21:10 -0000 On Friday 21 April 2006 04:55 pm, Conrad J. Sabatier wrote: > In /sys/amd64/conf/NOTES: > > # Enable 32-bit Linux ABI emulation (requires COMPAT_43 and COMPAT_IA32) > options COMPAT_LINUX32 > > In fact, COMPAT_43 is *not* required. I'm currently running a > 7.0-CURRENT kernel whose only COMPAT options are: > > options COMPAT_IA32 > options COMPAT_LINUX32 > > Everything seems to be working fine, including Linux emulation. I think this was very recently fixed to not require COMPAT_43. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 24 12:21:19 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28A0916A43B for ; Mon, 24 Apr 2006 12:21:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A690443D45 for ; Mon, 24 Apr 2006 12:21:18 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3OCL162052344; Mon, 24 Apr 2006 08:21:02 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 24 Apr 2006 08:11:29 -0400 User-Agent: KMail/1.8.3 References: <20060422061508.GA730@faust.net> In-Reply-To: <20060422061508.GA730@faust.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604240811.30483.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1423/Mon Apr 24 04:24:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Zoran Kolic Subject: Re: irq question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 12:21:19 -0000 On Saturday 22 April 2006 02:15 am, Zoran Kolic wrote: > Dear all! > For next week or two, I'll get > cable net; for nforce3 mobo I > put "rl" card into the last > pci slot. At least I am aware > of some possible irq mess with > that. > Here is information from dmesg: > ehci0 irq 10 at device 2.2 on pci0 > atapci1 irq 10 at device 10.0 on pci0 > rl0 irq 10 at device 10.0 on pci2 > Does it mean that I should wait and > see? Or change the place in advance? > Motherboard has 5 pci slots (asus > k8n). > I would like to not be told by > service folks to install win to > have the system work properly. > Best regards What specific problem are you having? Does the rl0 card not work? =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 24 12:43:41 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.ORG Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D0B116A417 for ; Mon, 24 Apr 2006 12:43:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14DB443D5C for ; Mon, 24 Apr 2006 12:43:33 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (yjsbap@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k3OChQYA029341 for ; Mon, 24 Apr 2006 14:43:32 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k3OChQ46029340; Mon, 24 Apr 2006 14:43:26 +0200 (CEST) (envelope-from olli) Date: Mon, 24 Apr 2006 14:43:26 +0200 (CEST) Message-Id: <200604241243.k3OChQ46029340@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <200604240811.30483.jhb@freebsd.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 24 Apr 2006 14:43:32 +0200 (CEST) Cc: Subject: Re: irq question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 12:43:41 -0000 John Baldwin wrote: > Zoran Kolic wrote: > > Dear all! > > For next week or two, I'll get > > cable net; for nforce3 mobo I > > put "rl" card into the last > > pci slot. At least I am aware > > of some possible irq mess with > > that. > > Here is information from dmesg: > > ehci0 irq 10 at device 2.2 on pci0 > > atapci1 irq 10 at device 10.0 on pci0 > > rl0 irq 10 at device 10.0 on pci2 > > Does it mean that I should wait and > > see? Or change the place in advance? > > Motherboard has 5 pci slots (asus > > k8n). > > I would like to not be told by > > service folks to install win to > > have the system work properly. > > Best regards > > What specific problem are you having? Does the rl0 card not work? I think he is concerned about irq10 shared between three devices (ehci0, atapci1, rl0). While in theory irq sharing should work fine, it can come with a noticeable performance penalty. In particular, the ehci interrupt handler is pretty heavy-weight and might slow rl0 down. (rl(4) isn't one of the best performers anyway.) I've seen such cases in the i386 world, and the solution was to disable USB completely and not load the driver (USB wasn't needed on those machines). Another way is to have a look at the BIOS setup. Some of them still offer the ability to manually configure the interrupts. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python is executable pseudocode. Perl is executable line noise. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 09:46:50 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B52716A405 for ; Tue, 25 Apr 2006 09:46:50 +0000 (UTC) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5183743D60 for ; Tue, 25 Apr 2006 09:46:44 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 6A92A31221 for ; Tue, 25 Apr 2006 09:46:43 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 75323-03-2 for ; Tue, 25 Apr 2006 09:46:42 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 26E17224A6 for ; Tue, 25 Apr 2006 09:46:42 +0000 (GMT) Message-ID: <444DF001.7020305@jetnet.co.uk> Date: Tue, 25 Apr 2006 10:46:41 +0100 From: David Reid User-Agent: Thunderbird 1.5 (X11/20060406) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Subject: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 09:46:50 -0000 At present I have an ABIT AN-8 Ultra MB which features the nVidia nForce 4 chipset. Given nVidia's attitude to releasing information and the resultant lack of information/drivers on FreeBSD I've finally decided to change it. Requirements are SATA (ideally with raid) and PCI-e. ATX form. Anyone got any recommendations? Thanks, david From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 12:00:57 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ABDB16A607 for ; Tue, 25 Apr 2006 12:00:57 +0000 (UTC) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A80143D45 for ; Tue, 25 Apr 2006 12:00:56 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k3PC0qID066391; Tue, 25 Apr 2006 14:00:52 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.4/Submit) id k3PC0qNO066390; Tue, 25 Apr 2006 14:00:52 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 25 Apr 2006 14:00:52 +0200 From: Francois Tigeot To: David Reid Message-ID: <20060425120051.GA33020@aoi.wolfpond.org> References: <444DF001.7020305@jetnet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444DF001.7020305@jetnet.co.uk> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 12:00:57 -0000 On Tue, Apr 25, 2006 at 10:46:41AM +0100, David Reid wrote: > At present I have an ABIT AN-8 Ultra MB which features the nVidia nForce > 4 chipset. Given nVidia's attitude to releasing information and the > resultant lack of information/drivers on FreeBSD I've finally decided to > change it. Requirements are SATA (ideally with raid) and PCI-e. ATX > form. Anyone got any recommendations? Asus A8V-E-SE Socket 939, PCI-E. VIA chipset with a SATA pseudo-RAID implementation. Everything works perfectly (running an Opteron here) with the caveat that you can't use 4GB of memory. Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, this board is fine. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 12:49:53 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEA4416A400 for ; Tue, 25 Apr 2006 12:49:53 +0000 (UTC) (envelope-from work@ashleymoran.me.uk) Received: from mercureh.reacthosting.com (reacthosting.com [195.177.245.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 667A543D49 for ; Tue, 25 Apr 2006 12:49:53 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from hosta.jigsawfinance.com ([213.106.224.113] helo=alfie.jigsawhq.com) by mercureh.reacthosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FYMzG-000Oph-VC; Tue, 25 Apr 2006 13:49:51 +0100 From: Ashley Moran Organization: Codeweavers Ltd To: freebsd-amd64@freebsd.org Date: Tue, 25 Apr 2006 13:49:38 +0100 User-Agent: KMail/1.9.1 References: <444DF001.7020305@jetnet.co.uk> <20060425120051.GA33020@aoi.wolfpond.org> In-Reply-To: <20060425120051.GA33020@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604251349.38494.work@ashleymoran.me.uk> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mercureh.reacthosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - ashleymoran.me.uk X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 12:49:54 -0000 On Tuesday 25 April 2006 13:00, Francois Tigeot wrote: > Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, > this board is fine. Francois, When you say this - do you mean the system was unbootable with 4GB, or it crashed under high memory useage? I've got two servers with Tyan Tiger K8SSA boards, 2 Opteron 165s and 4GB RAM each. They aren't installed yet, but they booted the 6.0 and 6.1 BETA4 CDs fine. Ashley From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 12:50:39 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BD3A16A406 for ; Tue, 25 Apr 2006 12:50:39 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C7743D64 for ; Tue, 25 Apr 2006 12:50:37 +0000 (GMT) (envelope-from yuri.pankov@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so959327ugc for ; Tue, 25 Apr 2006 05:50:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=b85w7dl2qwlHTGOaq5nZYdg4B4u2MXaCwhaNwXSsHHdlcjb4Sm0BsnlC2VHAyY7xgFGf8oe+nGWDzIj44xEy7oRSoqyK2X9kE1c6/CjPfvNWDuVSff6tpjiBCMq5wSUKsPX+D0MMzIA+r+dsHfdnaY/qsbJXNKtTyNb0Y5ezWvY= Received: by 10.66.224.6 with SMTP id w6mr2217935ugg; Tue, 25 Apr 2006 05:26:33 -0700 (PDT) Received: from ?192.168.0.64? ( [85.118.141.6]) by mx.gmail.com with ESMTP id k1sm49422ugf.2006.04.25.05.26.31; Tue, 25 Apr 2006 05:26:33 -0700 (PDT) Message-ID: <444E1542.7040309@gmail.com> Date: Tue, 25 Apr 2006 16:25:38 +0400 From: Yuri Pankov User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: David Reid References: <444DF001.7020305@jetnet.co.uk> In-Reply-To: <444DF001.7020305@jetnet.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 12:50:39 -0000 David Reid wrote: > At present I have an ABIT AN-8 Ultra MB which features the nVidia nForce > 4 chipset. Given nVidia's attitude to releasing information and the > resultant lack of information/drivers on FreeBSD I've finally decided to > change it. Requirements are SATA (ideally with raid) and PCI-e. ATX > form. Anyone got any recommendations? > > Thanks, > > david Following URL http://www.freebsd.org/platforms/amd64/motherboards.html can provide some info on motherboards for amd64 platform. I'm using Gigabyte K8NXP-SLI. Onboard NForce4 SATA controller is working without issues, though RAID functionality is not tested. Yuri From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 13:07:34 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 731B316A407 for ; Tue, 25 Apr 2006 13:07:34 +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 E9B4043D46 for ; Tue, 25 Apr 2006 13:07:32 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k3PD7Ukc099090 for ; Tue, 25 Apr 2006 10:07:30 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Tue, 25 Apr 2006 10:07:27 -0300 User-Agent: KMail/1.9.1 References: <444DF001.7020305@jetnet.co.uk> <20060425120051.GA33020@aoi.wolfpond.org> In-Reply-To: <20060425120051.GA33020@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604251007.27344.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 13:07:35 -0000 On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: > > Asus A8V-E-SE > > Socket 939, PCI-E. > > VIA chipset with a SATA pseudo-RAID implementation. > > Everything works perfectly (running an Opteron here) with the caveat that > you can't use 4GB of memory. > > Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, > this board is fine. crashes under which condition? 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-amd64@FreeBSD.ORG Tue Apr 25 14:31:04 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A250916A402 for ; Tue, 25 Apr 2006 14:31:04 +0000 (UTC) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 037BF43D45 for ; Tue, 25 Apr 2006 14:31:03 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k3PEV0eW067243; Tue, 25 Apr 2006 16:31:00 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.4/Submit) id k3PEV0Rc067242; Tue, 25 Apr 2006 16:31:00 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 25 Apr 2006 16:30:59 +0200 From: Francois Tigeot To: JoaoBR Message-ID: <20060425143059.GA67229@aoi.wolfpond.org> References: <444DF001.7020305@jetnet.co.uk> <20060425120051.GA33020@aoi.wolfpond.org> <200604251007.27344.joao@matik.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604251007.27344.joao@matik.com.br> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 14:31:04 -0000 On Tue, Apr 25, 2006 at 10:07:27AM -0300, JoaoBR wrote: > On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: > > > > Asus A8V-E-SE > > > > Socket 939, PCI-E. > > > > VIA chipset with a SATA pseudo-RAID implementation. > > > > Everything works perfectly (running an Opteron here) with the caveat that > > you can't use 4GB of memory. > > > > Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, > > this board is fine. > > > crashes under which condition? 4 GB of memory (4x1GB Kingston ECC) and the option to remap memory > 4GB set to on in the BIOS. FreeBSD, Centos, SuSE, Ubuntu, etc... all crashed. AFAIK, it is a bug in the Asus A8V-E-SE BIOS. The same memory and processor worked fine in a real server board. See this thread for reference: http://lists.freebsd.org/pipermail/freebsd-stable/2006-April/024622.html -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 14:35:30 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CEBF16A401 for ; Tue, 25 Apr 2006 14:35:30 +0000 (UTC) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 716E643D46 for ; Tue, 25 Apr 2006 14:35:29 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k3PEZOWh067266; Tue, 25 Apr 2006 16:35:24 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.4/Submit) id k3PEZNHQ067265; Tue, 25 Apr 2006 16:35:23 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 25 Apr 2006 16:35:23 +0200 From: Francois Tigeot To: Ashley Moran Message-ID: <20060425143523.GB67229@aoi.wolfpond.org> References: <444DF001.7020305@jetnet.co.uk> <20060425120051.GA33020@aoi.wolfpond.org> <200604251349.38494.work@ashleymoran.me.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604251349.38494.work@ashleymoran.me.uk> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 14:35:30 -0000 On Tue, Apr 25, 2006 at 01:49:38PM +0100, Ashley Moran wrote: > On Tuesday 25 April 2006 13:00, Francois Tigeot wrote: > > Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, > > this board is fine. > > When you say this - do you mean the system was unbootable with 4GB, or it > crashed under high memory useage? Instant crash and reboot as soon as the kernel starts executing. > I've got two servers with Tyan Tiger K8SSA > boards, 2 Opteron 165s and 4GB RAM each. They aren't installed yet, but they > booted the 6.0 and 6.1 BETA4 CDs fine. Your servers should be fine, this experience is specific to the Asus A8V-E-SE mainboard. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 18:12:26 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF1DF16A402 for ; Tue, 25 Apr 2006 18:12:26 +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 1BFCE43D46 for ; Tue, 25 Apr 2006 18:12:25 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k3PICNqk012195; Tue, 25 Apr 2006 15:12:24 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: Francois Tigeot Date: Tue, 25 Apr 2006 15:12:15 -0300 User-Agent: KMail/1.9.1 References: <444DF001.7020305@jetnet.co.uk> <200604251007.27344.joao@matik.com.br> <20060425143059.GA67229@aoi.wolfpond.org> In-Reply-To: <20060425143059.GA67229@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604251512.17206.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 18:12:26 -0000 On Tuesday 25 April 2006 11:30, Francois Tigeot wrote: > On Tue, Apr 25, 2006 at 10:07:27AM -0300, JoaoBR wrote: > > On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: > > > Asus A8V-E-SE > > > > > > > crashes under which condition? > > 4 GB of memory (4x1GB Kingston ECC) and the option to remap memory > 4GB > set to on in the BIOS. > You should try without the memory remap option On other boards I know this options make the kernel crash, seems that some= =20 drivers are going to be allocated over 4GB and then they are not accessible 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-amd64@FreeBSD.ORG Tue Apr 25 20:09:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AEA216A403 for ; Tue, 25 Apr 2006 20:09:58 +0000 (UTC) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B0D943D53 for ; Tue, 25 Apr 2006 20:09:57 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k3PK9rfj069103; Tue, 25 Apr 2006 22:09:53 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.4/Submit) id k3PK9rEC069102; Tue, 25 Apr 2006 22:09:53 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 25 Apr 2006 22:09:52 +0200 From: Francois Tigeot To: JoaoBR Message-ID: <20060425200952.GA69092@aoi.wolfpond.org> References: <444DF001.7020305@jetnet.co.uk> <200604251007.27344.joao@matik.com.br> <20060425143059.GA67229@aoi.wolfpond.org> <200604251512.17206.joao@matik.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604251512.17206.joao@matik.com.br> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 20:09:59 -0000 On Tue, Apr 25, 2006 at 03:12:15PM -0300, JoaoBR wrote: > On Tuesday 25 April 2006 11:30, Francois Tigeot wrote: > > On Tue, Apr 25, 2006 at 10:07:27AM -0300, JoaoBR wrote: > > > On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: > > > > Asus A8V-E-SE > > > > > > crashes under which condition? > > > > 4 GB of memory (4x1GB Kingston ECC) and the option to remap memory > 4GB > > set to on in the BIOS. > > You should try without the memory remap option Without it, only 3GB of RAM are usable. > On other boards I know this options make the kernel crash, seems that some > drivers are going to be allocated over 4GB and then they are not accessible Every OS I tested was an amd64 one. Memory adresses > 4GB are not an issue with them. Besides, all other components (software and hardware) worked fine with Supermicro and Tyan mainboards, so clearly the Asus A8V-E-SE is at fault here. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 25 20:30:42 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4566E16A402 for ; Tue, 25 Apr 2006 20:30:42 +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 63A0043D48 for ; Tue, 25 Apr 2006 20:30:41 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k3PKUePS018137; Tue, 25 Apr 2006 17:30:40 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: Francois Tigeot Date: Tue, 25 Apr 2006 17:30:35 -0300 User-Agent: KMail/1.9.1 References: <444DF001.7020305@jetnet.co.uk> <200604251512.17206.joao@matik.com.br> <20060425200952.GA69092@aoi.wolfpond.org> In-Reply-To: <20060425200952.GA69092@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604251730.35506.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 20:30:42 -0000 On Tuesday 25 April 2006 17:09, Francois Tigeot wrote: > On Tue, Apr 25, 2006 at 03:12:15PM -0300, JoaoBR wrote: > > On Tuesday 25 April 2006 11:30, Francois Tigeot wrote: > > > On Tue, Apr 25, 2006 at 10:07:27AM -0300, JoaoBR wrote: > > > > On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: > > > > > Asus A8V-E-SE > > > > > > > > crashes under which condition? > > > > > > 4 GB of memory (4x1GB Kingston ECC) and the option to remap memory > > > > 4GB set to on in the BIOS. > > > > You should try without the memory remap option > > Without it, only 3GB of RAM are usable. > more or less 3.5 - 3.7, yes this is the southbridge limitation but your system does not crash anymore > > On other boards I know this options make the kernel crash, seems that > > some drivers are going to be allocated over 4GB and then they are not > > accessible > > Every OS I tested was an amd64 one. Memory adresses > 4GB are not an > issue with them. > this is not an OS problem but a driver problem if we can call it a problem > Besides, all other components (software and hardware) worked fine with > Supermicro and Tyan mainboards, so clearly the Asus A8V-E-SE is at fault > here. the memory hole setting is discussible but this is a normal issue on all MBs but even with the memory remap option enabled you do not get access to 4GB = of=20 RAM 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-amd64@FreeBSD.ORG Tue Apr 25 21:03:19 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E03A016A405 for ; Tue, 25 Apr 2006 21:03:19 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com [68.142.225.204]) by mx1.FreeBSD.org (Postfix) with SMTP id ACB0443D64 for ; Tue, 25 Apr 2006 21:03:12 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 95668 invoked from network); 25 Apr 2006 21:03:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=KEE2V3T7l3U0fiRrAVzq17UGhZkZBh6XkxedMJ2J3IFbP9BhtilCkipsUIGDdyKU2nbYPVM7vXYVZRoFLbNhDPTeV9Z0l2qUXftn8sy1HmDa7QR7Gx85n1KuY+T8G0CaQKcDceaZBk860SFRwiUM9e0DvRH+iOG3Lnw6kJgSpxI= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 25 Apr 2006 21:03:12 -0000 Message-ID: <444E8EB3.1090100@rogers.com> Date: Tue, 25 Apr 2006 17:03:47 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Francois Tigeot References: <444DF001.7020305@jetnet.co.uk> <20060425120051.GA33020@aoi.wolfpond.org> <200604251007.27344.joao@matik.com.br> <20060425143059.GA67229@aoi.wolfpond.org> In-Reply-To: <20060425143059.GA67229@aoi.wolfpond.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 21:03:20 -0000 Francois Tigeot wrote: > On Tue, Apr 25, 2006 at 10:07:27AM -0300, JoaoBR wrote: > >> On Tuesday 25 April 2006 09:00, Francois Tigeot wrote: >> >>> Asus A8V-E-SE >>> >>> Socket 939, PCI-E. >>> >>> VIA chipset with a SATA pseudo-RAID implementation. >>> >>> Everything works perfectly (running an Opteron here) with the caveat that >>> you can't use 4GB of memory. >>> >>> Every 64-bit OS I have tested crashed with 4GB populated. Up to three GB, >>> this board is fine. >>> >> crashes under which condition? >> > > 4 GB of memory (4x1GB Kingston ECC) and the option to remap memory > 4GB set > to on in the BIOS. > > FreeBSD, Centos, SuSE, Ubuntu, etc... all crashed. > Thats why we don't use desktop motherboards for servers. I would recommend you stick with Tyan or Supermicro. From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 06:58:31 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC51816A406 for ; Thu, 27 Apr 2006 06:58:31 +0000 (UTC) (envelope-from shigeaki@se.hiroshima-u.ac.jp) Received: from condor.se.hiroshima-u.ac.jp (condor.se.hiroshima-u.ac.jp [133.41.33.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0344443D8E for ; Thu, 27 Apr 2006 06:58:19 +0000 (GMT) (envelope-from shigeaki@se.hiroshima-u.ac.jp) Received: from [127.0.0.1] (maroon.se.hiroshima-u.ac.jp [192.168.128.148]) by condor.se.hiroshima-u.ac.jp with ESMTP id k3R6wFVr090586 for ; Thu, 27 Apr 2006 15:58:15 +0900 (JST) Message-ID: <44506B8B.4090605@se.hiroshima-u.ac.jp> Date: Thu, 27 Apr 2006 15:58:19 +0900 From: Shigeaki Tagashira User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=13.0 tests=AWL,CONTENT_TYPE_PRESENT, ISO2022JP_CHARSET autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on condor.se.hiroshima-u.ac.jp Subject: FreeBSD nfe driver for NVIDIA nForce network adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 06:58:31 -0000 I am providing a FreeBSD device driver of NVIDIA nForce network adapter. It is a native device driver and is based on the OpenBSD nfe driver. The latest driver was tested on FreeBSD 6.1-RC/amd64 and seems to work stably on my machine (ASUS A8N-SLI Premium). It can be downloaded at the following URL. http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html Best regards --- S. Tagashira From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 07:13:16 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F4CE16A403 for ; Thu, 27 Apr 2006 07:13:16 +0000 (UTC) (envelope-from geekout@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFAB643D45 for ; Thu, 27 Apr 2006 07:13:15 +0000 (GMT) (envelope-from geekout@gmail.com) Received: by nz-out-0102.google.com with SMTP id 9so1505673nzo for ; Thu, 27 Apr 2006 00:13:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=INJaBViFKA1axA82vHo/J8ltTMNBw/pvWwS9z9GLqAGOcg2wiTfuTt+/qrjHwzp41KpAcH3Zd9AMQJfvk7jwTua+fmGpWgjp1lEWsHJu5JU5sf+uGl2s9YUQJUijBwrfZpKVBkVFZunMTiLsdLWqn9YEI+hoA5h/X3oenf+wkx0= Received: by 10.65.235.7 with SMTP id m7mr2309916qbr; Thu, 27 Apr 2006 00:13:15 -0700 (PDT) Received: by 10.64.199.16 with HTTP; Thu, 27 Apr 2006 00:13:14 -0700 (PDT) Message-ID: <6e01203b0604270013w54ec1618g45b506e703edb71c@mail.gmail.com> Date: Wed, 26 Apr 2006 21:13:14 -1000 From: "Tyler Gee" To: "Shigeaki Tagashira" In-Reply-To: <44506B8B.4090605@se.hiroshima-u.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44506B8B.4090605@se.hiroshima-u.ac.jp> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD nfe driver for NVIDIA nForce network adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 07:13:16 -0000 Woohoo! I'll give it a try this evening. Now my cheap-o eMachine can shine! Thanks, Tyler On 4/26/06, Shigeaki Tagashira wrote: > I am providing a FreeBSD device driver of NVIDIA nForce network adapter. > It is a native device driver and is based on the OpenBSD nfe driver. > The latest driver was tested on FreeBSD 6.1-RC/amd64 and seems to work st= ably > on my machine (ASUS A8N-SLI Premium). > > It can be downloaded at the following URL. > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > Best regards > --- > S. Tagashira > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 08:00:37 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D172916A41A for ; Thu, 27 Apr 2006 08:00:37 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C342743D5D for ; Thu, 27 Apr 2006 08:00:36 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3R80ahg027115 for ; Thu, 27 Apr 2006 08:00:36 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3R80anS027112; Thu, 27 Apr 2006 08:00:36 GMT (envelope-from gnats) Resent-Date: Thu, 27 Apr 2006 08:00:36 GMT Resent-Message-Id: <200604270800.k3R80anS027112@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, York Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BB5A16A404 for ; Thu, 27 Apr 2006 07:59:01 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6569143D49 for ; Thu, 27 Apr 2006 07:59:01 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k3R7x0t1018838 for ; Thu, 27 Apr 2006 07:59:00 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k3R7x06x018827; Thu, 27 Apr 2006 07:59:00 GMT (envelope-from nobody) Message-Id: <200604270759.k3R7x06x018827@www.freebsd.org> Date: Thu, 27 Apr 2006 07:59:00 GMT From: York To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/96400: FreeBSD 6.0 Bootin Conflict between Broadcom on-broad NIC and Adaptec7902 storage chip X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 08:00:38 -0000 >Number: 96400 >Category: amd64 >Synopsis: FreeBSD 6.0 Bootin Conflict between Broadcom on-broad NIC and Adaptec7902 storage chip >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: maintainer-update >Submitter-Id: current-users >Arrival-Date: Thu Apr 27 08:00:35 GMT 2006 >Closed-Date: >Last-Modified: >Originator: York >Release: FreeBSD 6.0 and 6.1 >Organization: www.Inventecesc.com >Environment: System can boot from installation Boot CD. >Description: The related Hardware SPEC as below System Chipset nVIDIA CK8-04 Pro AMD-8131 Network Controllers 2 x Broadcom 5721 Gigabit Ethernet controller TCP/IP off-loading, load-balancing, autofailover. Support 10BASE-T, 100BASE-TX and 1000BASE-T Graphics ATI Rage XL PCI video controller 8MB of video memory Storage Chip SCSI Adaptec aic7902 Systen hang on Installation CD booting, The Screen as below -------------------------------------------------- (noperiph:ahd1:0:-1:-1): SCSI bus reset delivered. ) SCBs aborted. md0: Preloaded image 4194304 bytes at 0xffffffff80970f68 ata0-slave: pio=PI04 wdma=WDMA2 udma=UDMA33 cab;e-40 write ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 write ad0: setting PIO4 on nVidia nForce4 chip ad0: setting UDMA133 on nVIDIA nForce4 chip ad0: 117246MB at ata0-master UDMA133 CE0M: new disk ad0 ad0: nVidia check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed acd0: setting PIO4 on nVidia nForce4 chip acd0: CDROM drive at ata0 as slave acd0: read 8258KB/s (8258KB/s), 128KB buffer, UDMA33 acd0: Reads: CDR. CDRW. CDDA strea,. packet acd0: Writes: acd0: Audio: play, 256 volume levels acd0: MechanismL ejectsble tray, unlocked acd0: Medium: CD-ROM 128mm data disk ahd0: Selection Timeout on A:0, 0 SCBs aborted ------------------------------------------------------------------ Hang.............................Orz >How-To-Repeat: Happend on Installation, Verify. If disable Both on-broad NICs, installation will be OK >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 08:07:19 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D26116A400 for ; Thu, 27 Apr 2006 08:07:19 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5193D43D49 for ; Thu, 27 Apr 2006 08:07:18 +0000 (GMT) (envelope-from yuri.pankov@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so1306625ugc for ; Thu, 27 Apr 2006 01:07:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=bp4u3/fZl9qBaDQQys8/EsxwAijf1618xixWQTEC8Iwt6uyaFat8guExsG1GejUUpv/JuSrkpbijfPpMoYSQFL119R4Vaa9EAxhaOezbHpW9w7aKiuGWHk6SE9CJ+Iy9dWeu45AjSsReDjWmOTiq3pzL6XNTExoPCbvduqzHvDw= Received: by 10.67.19.14 with SMTP id w14mr4305097ugi; Thu, 27 Apr 2006 01:07:17 -0700 (PDT) Received: from ?192.168.0.64? ( [85.118.141.6]) by mx.gmail.com with ESMTP id q40sm411619ugc.2006.04.27.01.07.14; Thu, 27 Apr 2006 01:07:16 -0700 (PDT) Message-ID: <44507BAF.4070901@gmail.com> Date: Thu, 27 Apr 2006 12:07:11 +0400 From: Yuri Pankov User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: Shigeaki Tagashira References: <44506B8B.4090605@se.hiroshima-u.ac.jp> In-Reply-To: <44506B8B.4090605@se.hiroshima-u.ac.jp> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD nfe driver for NVIDIA nForce network adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 08:07:19 -0000 Shigeaki Tagashira wrote: > I am providing a FreeBSD device driver of NVIDIA nForce network adapter. > It is a native device driver and is based on the OpenBSD nfe driver. > The latest driver was tested on FreeBSD 6.1-RC/amd64 and seems to work stably > on my machine (ASUS A8N-SLI Premium). > > It can be downloaded at the following URL. > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > Best regards > --- > S. Tagashira > I've tried this driver on recent FreeBSD 7.0-CURRENT/amd64. Driver compiles, this is what I get after kldload if_nfe: nfe0: port 0xe800-0xe807 mem 0xf5102000-0xf5102fff irq 23 at device 10.0 on pci0 nfe0: bpf attached nfe0: Ethernet address: 00:0f:ea:7d:f3:20 nfe0: [MPSAFE] pci1: driver added miibus0: on nfe0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: link state changed to DOWN nfe0: gigabit link up nfe0: link state changed to UP ifconfig output: nfe0: flags=8843 mtu 1500 options=8 inet 10.10.10.1 netmask 0xffffff00 broadcast 10.10.10.255 inet6 fe80::20f:eaff:fe7d:f320%nfe0 prefixlen 64 scopeid 0x3 ether 00:0f:ea:7d:f3:20 media: Ethernet autoselect (1000baseTX ) status: active Looks ok, but when I try to ping 10.10.10.2 it says 'host is down'. Though it works OK with if_nve driver. Anyway, thanks for your work! Yuri From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 08:41:24 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDC1E16A400 for ; Thu, 27 Apr 2006 08:41:24 +0000 (UTC) (envelope-from geekout@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D6A43D46 for ; Thu, 27 Apr 2006 08:41:24 +0000 (GMT) (envelope-from geekout@gmail.com) Received: by nz-out-0102.google.com with SMTP id 9so1517398nzo for ; Thu, 27 Apr 2006 01:41:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=brt5DeP6LT24j8SdEW2hTCtDnvi13GRFRuyMOnQpGS6CL+m3tKWJkvzKhhYbNxE2N/HQyDGHhgKQua1447q+gPuTFUqyumNvgRGr8d/1LyJPkgvswMf5oZxRLnKueXHbN3ApuV2PrOpsRmaZkPIM05m0PgLTev6GFxvlc8jEM3M= Received: by 10.65.72.11 with SMTP id z11mr2284535qbk; Thu, 27 Apr 2006 01:41:23 -0700 (PDT) Received: by 10.64.199.16 with HTTP; Thu, 27 Apr 2006 01:41:23 -0700 (PDT) Message-ID: <6e01203b0604270141q34ff3137xb027ed8ed9420843@mail.gmail.com> Date: Wed, 26 Apr 2006 22:41:23 -1000 From: "Tyler Gee" To: "Yuri Pankov" In-Reply-To: <44507BAF.4070901@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44506B8B.4090605@se.hiroshima-u.ac.jp> <44507BAF.4070901@gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD nfe driver for NVIDIA nForce network adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 08:41:24 -0000 Working like a charm (with the 88E1111 patch ) FreeBSD xxx 6.1-RC FreeBSD 6.1-RC #3: Wed Apr 26 21:50:14 HST 2006 =20 root@so uth:/usr/obj/usr/src/sys/DESKBOT amd64 MS-7207 Motherboard Thanks! Tyler On 4/26/06, Yuri Pankov wrote: > Shigeaki Tagashira wrote: > > I am providing a FreeBSD device driver of NVIDIA nForce network adapter= . > > It is a native device driver and is based on the OpenBSD nfe driver. > > The latest driver was tested on FreeBSD 6.1-RC/amd64 and seems to work = stably > > on my machine (ASUS A8N-SLI Premium). > > > > It can be downloaded at the following URL. > > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > > > Best regards > > --- > > S. Tagashira > > > > I've tried this driver on recent FreeBSD 7.0-CURRENT/amd64. Driver > compiles, this is what I get after kldload if_nfe: > > nfe0: port 0xe800-0xe807 mem > 0xf5102000-0xf5102fff irq 23 at device 10.0 on pci0 > nfe0: bpf attached > nfe0: Ethernet address: 00:0f:ea:7d:f3:20 > nfe0: [MPSAFE] > pci1: driver added > miibus0: on nfe0 > ciphy0: on miibus0 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > nfe0: link state changed to DOWN > nfe0: gigabit link up > nfe0: link state changed to UP > > ifconfig output: > > nfe0: flags=3D8843 mtu 1500 > options=3D8 > inet 10.10.10.1 netmask 0xffffff00 broadcast 10.10.10.255 > inet6 fe80::20f:eaff:fe7d:f320%nfe0 prefixlen 64 scopeid 0x3 > ether 00:0f:ea:7d:f3:20 > media: Ethernet autoselect (1000baseTX ) > status: active > > Looks ok, but when I try to ping 10.10.10.2 it says 'host is down'. > Though it works OK with if_nve driver. > > Anyway, thanks for your work! > > Yuri > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 10:06:46 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 652C216A411 for ; Thu, 27 Apr 2006 10:06:46 +0000 (UTC) (envelope-from shigeaki@se.hiroshima-u.ac.jp) Received: from condor.se.hiroshima-u.ac.jp (condor.se.hiroshima-u.ac.jp [133.41.33.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id B630043D45 for ; Thu, 27 Apr 2006 10:06:45 +0000 (GMT) (envelope-from shigeaki@se.hiroshima-u.ac.jp) Received: from [127.0.0.1] (maroon.se.hiroshima-u.ac.jp [192.168.128.148]) by condor.se.hiroshima-u.ac.jp with ESMTP id k3RA6f83092856; Thu, 27 Apr 2006 19:06:41 +0900 (JST) Message-ID: <445097B4.1060400@se.hiroshima-u.ac.jp> Date: Thu, 27 Apr 2006 19:06:44 +0900 From: Shigeaki Tagashira User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Tyler Gee , Yuri Pankov References: <44506B8B.4090605@se.hiroshima-u.ac.jp> <44507BAF.4070901@gmail.com> <6e01203b0604270141q34ff3137xb027ed8ed9420843@mail.gmail.com> In-Reply-To: <6e01203b0604270141q34ff3137xb027ed8ed9420843@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.8 required=13.0 tests=AWL,CONTENT_TYPE_PRESENT, FAKEDWORD_ATMARK,QENCPTR1 autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on condor.se.hiroshima-u.ac.jp Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD nfe driver for NVIDIA nForce network adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 10:06:46 -0000 Thanks for your reports. I have not tested the driver on FreeBSD 7.0-CURRENT and on the Cicada phys. I'll try it on these platforms. --- S. Tagashira Tyler Gee wrote: > Working like a charm (with the 88E1111 patch ) > > FreeBSD xxx 6.1-RC FreeBSD 6.1-RC #3: Wed Apr 26 21:50:14 HST 2006 > root@so uth:/usr/obj/usr/src/sys/DESKBOT amd64 > > MS-7207 Motherboard > > Thanks! > Tyler > > On 4/26/06, Yuri Pankov wrote: >> Shigeaki Tagashira wrote: >>> I am providing a FreeBSD device driver of NVIDIA nForce network adapter. >>> It is a native device driver and is based on the OpenBSD nfe driver. >>> The latest driver was tested on FreeBSD 6.1-RC/amd64 and seems to work stably >>> on my machine (ASUS A8N-SLI Premium). >>> >>> It can be downloaded at the following URL. >>> http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html >>> >>> Best regards >>> --- >>> S. Tagashira >>> >> I've tried this driver on recent FreeBSD 7.0-CURRENT/amd64. Driver >> compiles, this is what I get after kldload if_nfe: >> >> nfe0: port 0xe800-0xe807 mem >> 0xf5102000-0xf5102fff irq 23 at device 10.0 on pci0 >> nfe0: bpf attached >> nfe0: Ethernet address: 00:0f:ea:7d:f3:20 >> nfe0: [MPSAFE] >> pci1: driver added >> miibus0: on nfe0 >> ciphy0: on miibus0 >> ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> nfe0: link state changed to DOWN >> nfe0: gigabit link up >> nfe0: link state changed to UP >> >> ifconfig output: >> >> nfe0: flags=8843 mtu 1500 >> options=8 >> inet 10.10.10.1 netmask 0xffffff00 broadcast 10.10.10.255 >> inet6 fe80::20f:eaff:fe7d:f320%nfe0 prefixlen 64 scopeid 0x3 >> ether 00:0f:ea:7d:f3:20 >> media: Ethernet autoselect (1000baseTX ) >> status: active >> >> Looks ok, but when I try to ping 10.10.10.2 it says 'host is down'. >> Though it works OK with if_nve driver. >> >> Anyway, thanks for your work! >> >> Yuri >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 13:59:16 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17BCC16A400 for ; Thu, 27 Apr 2006 13:59:16 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE80043D46 for ; Thu, 27 Apr 2006 13:59:15 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id B7A4DB829 for ; Thu, 27 Apr 2006 09:59:14 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <200604251730.35506.joao@matik.com.br> References: <444DF001.7020305@jetnet.co.uk> <200604251512.17206.joao@matik.com.br> <20060425200952.GA69092@aoi.wolfpond.org> <200604251730.35506.joao@matik.com.br> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 27 Apr 2006 09:59:13 -0400 To: FreeBSD AMD list X-Mailer: Apple Mail (2.749.3) Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 13:59:16 -0000 On Apr 25, 2006, at 4:30 PM, JoaoBR wrote: >> Without it, only 3GB of RAM are usable. >> > > more or less 3.5 - 3.7, yes On a SunFire X4100, with the default BIOS settings, 4GB RAM shows up as 3GB. When you turn on the software (or hardware if your configuration permits) remapping, you get to bump this up to about 3.7GB. Still lame, but what can ya do... From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 14:10:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33F5F16A404 for ; Thu, 27 Apr 2006 14:10:58 +0000 (UTC) (envelope-from nathanw@uchicago.edu) Received: from relay01.uchicago.edu (relay01.uchicago.edu [128.135.12.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD81B43D73 for ; Thu, 27 Apr 2006 14:10:57 +0000 (GMT) (envelope-from nathanw@uchicago.edu) Received: from [128.135.116.74] (stony-116-074.rh.uchicago.edu [128.135.116.74]) by relay01.uchicago.edu (8.12.10/8.12.9) with ESMTP id k3REAm8V007024 for ; Thu, 27 Apr 2006 09:10:56 -0500 (CDT) Message-ID: <4450D0E8.4000403@uchicago.edu> Date: Thu, 27 Apr 2006 09:10:48 -0500 From: Nathan Whitehorn User-Agent: Thunderbird 1.5.0.2 (X11/20060424) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20060427120035.D7FA016A43B@hub.freebsd.org> In-Reply-To: <20060427120035.D7FA016A43B@hub.freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 14:10:58 -0000 Also on the subject of nVidia NICs, I've fixed the device timeout problem on nve(4). It appears that some revisions of the hardware don't send interrupts on tx completion, which caused watchdog timeouts under low load. We should take this hardware quirk into account for the nfe port as well. -Nathan --- if_nve_original.c Wed Apr 26 22:23:14 2006 +++ if_nve.c Wed Apr 26 21:52:34 2006 @@ -1270,6 +1270,18 @@ nve_watchdog(struct ifnet *ifp) { struct nve_softc *sc = ifp->if_softc; + + NVE_LOCK(sc); + /* Check for lost interrupts -- happens on nForce4 */ + sc->hwapi->pfnDisableInterrupts(sc->hwapi->pADCX); + sc->hwapi->pfnHandleInterrupt(sc->hwapi->pADCX); + sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); + + if (sc->pending_txs == 0) { + NVE_UNLOCK(sc); + return; /* Problem went away */ + } + NVE_UNLOCK(sc); device_printf(sc->dev, "device timeout (%d)\n", sc->pending_txs); From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 14:40:30 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97B3216A444 for ; Thu, 27 Apr 2006 14:40:30 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF16B43D49 for ; Thu, 27 Apr 2006 14:40:29 +0000 (GMT) (envelope-from yuri.pankov@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so1407690nfc for ; Thu, 27 Apr 2006 07:40:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=oGWpiDnRYZUIxCzexuLzhOu7u3D9wwVgLidpIW3WBZAm/p5kFOExY61OjrXj3WnPlJ8m2zsfMGA4pNC+wlUI2k/B2YDYePCjuui2BTvVqMrDe6eU6PTB8zkOmOUfxKO/FpnejC42r77TFqESwBbjdu+9cutGiP0o0cBZXtQimJo= Received: by 10.49.21.12 with SMTP id y12mr5635268nfi; Thu, 27 Apr 2006 07:40:28 -0700 (PDT) Received: from ?192.168.0.64? ( [85.118.141.6]) by mx.gmail.com with ESMTP id p45sm729519nfa.2006.04.27.07.40.25; Thu, 27 Apr 2006 07:40:27 -0700 (PDT) Message-ID: <4450D7D7.9070108@gmail.com> Date: Thu, 27 Apr 2006 18:40:23 +0400 From: Yuri Pankov User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: Nathan Whitehorn References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> In-Reply-To: <4450D0E8.4000403@uchicago.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 14:40:30 -0000 Nathan Whitehorn wrote: > Also on the subject of nVidia NICs, I've fixed the device timeout > problem on nve(4). It appears that some revisions of the hardware don't > send interrupts on tx completion, which caused watchdog timeouts under > low load. We should take this hardware quirk into account for the nfe > port as well. > -Nathan > > --- if_nve_original.c Wed Apr 26 22:23:14 2006 > +++ if_nve.c Wed Apr 26 21:52:34 2006 > @@ -1270,6 +1270,18 @@ > nve_watchdog(struct ifnet *ifp) > { > struct nve_softc *sc = ifp->if_softc; > + > + NVE_LOCK(sc); > + /* Check for lost interrupts -- happens on nForce4 */ > + sc->hwapi->pfnDisableInterrupts(sc->hwapi->pADCX); > + sc->hwapi->pfnHandleInterrupt(sc->hwapi->pADCX); > + sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); > + > + if (sc->pending_txs == 0) { > + NVE_UNLOCK(sc); > + return; /* Problem went away */ > + } > + NVE_UNLOCK(sc); > > device_printf(sc->dev, "device timeout (%d)\n", sc->pending_txs); > Indeed, it seems to solve timeout() messages. Haven't got any so far. Thank you! one small correction - this patch doesn't apply cleanly to -current source, so I've patched source by hand and here's patch for -current: --- if_nve.c.orig Mon Dec 12 09:23:43 2005 +++ if_nve.c Thu Apr 27 18:23:48 2006 @@ -1277,6 +1277,18 @@ { struct nve_softc *sc = ifp->if_softc; + NVE_LOCK(sc); + /* Check for lost interrupts -- happens on nForce4 */ + sc->hwapi->pfnDisableInterrupts(sc->hwapi->pADCX); + sc->hwapi->pfnHandleInterrupt(sc->hwapi->pADCX); + sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); + + if (sc->pending_txs == 0) { + NVE_UNLOCK(sc); + return; /* Problem went away */ + } + NVE_UNLOCK(sc); + device_printf(sc->dev, "device timeout (%d)\n", c->pending_txs); NVE_LOCK(sc); Yuri From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 16:22:47 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A72416A400 for ; Thu, 27 Apr 2006 16:22:47 +0000 (UTC) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F9FF43D4C for ; Thu, 27 Apr 2006 16:22:38 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2501BF828 for ; Thu, 27 Apr 2006 10:23:44 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id D86BBF812 for ; Thu, 27 Apr 2006 10:23:43 -0600 (MDT) Date: Thu, 27 Apr 2006 10:22:35 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060427102235.71648702.kgunders@teamcool.net> In-Reply-To: <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> References: <444DF001.7020305@jetnet.co.uk> <200604251512.17206.joao@matik.com.br> <20060425200952.GA69092@aoi.wolfpond.org> <200604251730.35506.joao@matik.com.br> <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 16:22:47 -0000 On Thu, 27 Apr 2006 09:59:13 -0400 Vivek Khera wrote: > > On Apr 25, 2006, at 4:30 PM, JoaoBR wrote: > > >> Without it, only 3GB of RAM are usable. > >> > > > > more or less 3.5 - 3.7, yes > > On a SunFire X4100, with the default BIOS settings, 4GB RAM shows up > as 3GB. When you turn on the software (or hardware if your > configuration permits) remapping, you get to bump this up to about > 3.7GB. Still lame, but what can ya do... I thought the x4100 supported 16GB of memory? -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 21:34:56 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E399116A404 for ; Thu, 27 Apr 2006 21:34:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67A5043D46 for ; Thu, 27 Apr 2006 21:34:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3RLYrNZ085444; Thu, 27 Apr 2006 17:34:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Thu, 27 Apr 2006 17:28:57 -0400 User-Agent: KMail/1.9.1 References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> In-Reply-To: <4450D0E8.4000403@uchicago.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604271728.59430.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1428/Thu Apr 27 14:39:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 21:34:57 -0000 On Thursday 27 April 2006 10:10, Nathan Whitehorn wrote: > Also on the subject of nVidia NICs, I've fixed the device timeout > problem on nve(4). It appears that some revisions of the hardware don't > send interrupts on tx completion, which caused watchdog timeouts under > low load. We should take this hardware quirk into account for the nfe > port as well. > -Nathan > > --- if_nve_original.c Wed Apr 26 22:23:14 2006 > +++ if_nve.c Wed Apr 26 21:52:34 2006 > @@ -1270,6 +1270,18 @@ > nve_watchdog(struct ifnet *ifp) > { > struct nve_softc *sc = ifp->if_softc; > + > + NVE_LOCK(sc); > + /* Check for lost interrupts -- happens on nForce4 */ > + sc->hwapi->pfnDisableInterrupts(sc->hwapi->pADCX); > + sc->hwapi->pfnHandleInterrupt(sc->hwapi->pADCX); > + sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); > + > + if (sc->pending_txs == 0) { > + NVE_UNLOCK(sc); > + return; /* Problem went away */ > + } > + NVE_UNLOCK(sc); > > device_printf(sc->dev, "device timeout (%d)\n", sc->pending_txs); I would just remove the second NVE_UNLOCK and remove the NVE_LOCK right after the device_printf() so you don't unlock the mutex just to turn around and lock it again. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 27 22:24:09 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD38716A400 for ; Thu, 27 Apr 2006 22:24:09 +0000 (UTC) (envelope-from taob@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 693DD43D46 for ; Thu, 27 Apr 2006 22:24:08 +0000 (GMT) (envelope-from taob@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id AFB344B44; Thu, 27 Apr 2006 18:24:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id A1CFE4B3C; Thu, 27 Apr 2006 18:24:05 -0400 (EDT) Date: Thu, 27 Apr 2006 18:24:05 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: FreeBSD AMD list In-Reply-To: Message-ID: <20060427181602.F43350-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: Re: Disk I/O-related panics in 6.0-RELEASE? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 22:24:09 -0000 On Wed, 5 Apr 2006, Vivek Khera wrote: > > All hardware is not created the same.... Last year I went through 5 > motherboards, two full systems, lots of RAM sticks, yada yada yada, > all to get *one* stable server out of it. Needless to say, I don't > buy that vendor anymore. Just wanted to followup on this thread. I initially tried Kris Kennaway's software-based suggestions (don't use ULE, don't use QUOTAS, don't run bg fsck) before going the hardware route. Those had no effect. I suspected flakey RAM to be the most likely culprit, so I replaced the two sticks of OCZ DIMMs with equivalent ones from Kingston. Although I should not have been anywhere close to the capacity of the power supply (should have been plenty left on both the 5V and 12V rails), I took all but two drives offline, and also pulled out the Promise TX-4 SATA card, just in case. Now, so far so good with both 6.0p4 and 6.1-RC. The machine easily gets through a 48-hour period of continuous make buildworlds and buildkernels, whereas before it would panic during the first or second iteration. I'm fairly sure it is the RAM and not the TX-4 or power draw from the drives, but I'll have to schedule a maintenance window to test that. Thanks all for pointing me in the right direction! -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 06:46:33 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21C0316A401 for ; Fri, 28 Apr 2006 06:46:33 +0000 (UTC) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DAAF43D46 for ; Fri, 28 Apr 2006 06:46:31 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k3S6kOQs090194; Fri, 28 Apr 2006 08:46:24 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.4/Submit) id k3S6kLZx090193; Fri, 28 Apr 2006 08:46:21 +0200 (CEST) (envelope-from ftigeot) Date: Fri, 28 Apr 2006 08:46:21 +0200 From: Francois Tigeot To: Vivek Khera Message-ID: <20060428064621.GB90111@aoi.wolfpond.org> References: <444DF001.7020305@jetnet.co.uk> <200604251512.17206.joao@matik.com.br> <20060425200952.GA69092@aoi.wolfpond.org> <200604251730.35506.joao@matik.com.br> <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD AMD list Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 06:46:33 -0000 On Thu, Apr 27, 2006 at 09:59:13AM -0400, Vivek Khera wrote: > > On Apr 25, 2006, at 4:30 PM, JoaoBR wrote: > > >>Without it, only 3GB of RAM are usable. > >> > > > >more or less 3.5 - 3.7, yes > > On a SunFire X4100, with the default BIOS settings, 4GB RAM shows up > as 3GB. When you turn on the software (or hardware if your > configuration permits) remapping, you get to bump this up to about > 3.7GB. Still lame, but what can ya do... With the Supermicro H8-SSL-i, you get almost the full 4GB (3.9-3.95), forgot the exact value. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 14:31:03 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F09B316A401 for ; Fri, 28 Apr 2006 14:31:03 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7413D43D48 for ; Fri, 28 Apr 2006 14:31:03 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 062B4B826 for ; Fri, 28 Apr 2006 10:31:02 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <20060427102235.71648702.kgunders@teamcool.net> References: <444DF001.7020305@jetnet.co.uk> <200604251512.17206.joao@matik.com.br> <20060425200952.GA69092@aoi.wolfpond.org> <200604251730.35506.joao@matik.com.br> <4CD3F2C8-E8A6-4EDF-B4BE-9993839CA6EF@khera.org> <20060427102235.71648702.kgunders@teamcool.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Fri, 28 Apr 2006 10:31:01 -0400 To: FreeBSD AMD list X-Mailer: Apple Mail (2.749.3) Subject: Re: mb recommendation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 14:31:04 -0000 On Apr 27, 2006, at 12:22 PM, Ken Gunderson wrote: >> On a SunFire X4100, with the default BIOS settings, 4GB RAM shows up >> as 3GB. When you turn on the software (or hardware if your >> configuration permits) remapping, you get to bump this up to about >> 3.7GB. Still lame, but what can ya do... > > I thought the x4100 supported 16GB of memory? but I only have 4 in mine so I can't comment on what happens with more :-) From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 19:50:27 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FED516A407 for ; Fri, 28 Apr 2006 19:50:27 +0000 (UTC) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B7C643D62 for ; Fri, 28 Apr 2006 19:50:19 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FZYyZ-0008KP-AN for freebsd-amd64@freebsd.org; Fri, 28 Apr 2006 21:50:03 +0200 Received: from p5089e078.dip.t-dialin.net ([80.137.224.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Apr 2006 21:50:03 +0200 Received: from protagonist by p5089e078.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Apr 2006 21:50:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: freebsd-amd64@freebsd.org To: freebsd-amd64@freebsd.org From: Marcus Frings Date: Fri, 28 Apr 2006 20:32:40 +0200 Organization: Schismatrix Lines: 19 Message-ID: References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5089e078.dip.t-dialin.net Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEUtERpEIB1dPit3NimZ ZTm8WjeCaEzZAAACfUlEQVR42lVUQYLbIAwUpL0jnAeA7L2HlX1PbPyA1ub/X+mIZLNbDg5oGCEN Q4jew6VAP4awiKyJyGcR/JCX4DI5SrJO6+oslMi+ORF2eANkWsN3GkfEgZii1Lpmm8ozFcd8fQCW dZVtm5VzzoKw1usY2fgy1TofrZ1tbzYW1U+rRgzYKoLn+URWlJcdTVKnus4I1P3E9/hc05Rwhher V0YkMsJRImpN9IsoTiiHaTDCfgaXcqAYPMqV+xol01qxP5BfU/DBRVSFgX44THtLFJykEhMql+pl 3HiYKxh3PUregp8snRRxakVN+3m3ibAbwWBRGYeltb/Ted4Ha3ActrtpgIHG2yeCt07VeStMdDma LZteWyt9tqveIoWoixHajHRbZyzHxp4e7gUoZNGhyzhr9pAdR0CkY0K5WkA7D7XWZBp1MZFmaLIZ YDhnu8EPW+lYz/bgxc4uDACU1dooI1Jtt99IhWIT2xXKqJBbUdF2XBDPnA0IIqi4lQU01ctiJwQD WMasTW/DB7IUd7TK7FPs1kMa3Nx0tnJzx7yll8NCzOOxqHd1C6TL/AiwsZgzcwClhDD8IRpUH+Hp R+LkeLDaVYPTQfPLqEDYuVAixNfAfM3vlxCCc+ygxnKUgE091mkMDwxdsKNQTG/f9z1QfW+n3tyv H++K+wf+Pfm1eMUdzh+W3YS9cfzxKk2xiwLA6eS/KWzTwa77UCbv/wfoWmvVAukS1OuVucmEoUuW RwwdeHZBruPOnLeV0N8zd4av9/cZaN07w1y/D+DwtXnowAvBssfhEwAXIwBC65aqiyGTZXy6Fm8K Xgv9ePfVpv0zcMD1vULurf7XpP/Z/ANzQp7ApenyawAAAABJRU5ErkJggg== X-PGP-Key: 0xE10F502E X-PGP-Fingerprint: 53FC 5A87 27BE 1D30 FEB4 861A 948F D6A0 E10F 502E Mail-Copies-To: nobody X-Now-Playing: End Of Green - "Sick One" [Dead End Dreaming] User-Agent: Gnus/5.110005 (No Gnus v0.5) Emacs/22.0.50 (berkeley-unix) Cancel-Lock: sha1:PWcZ2wXj/+00FQL42XS3/YhIyYk= Sender: news Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: protagonist@gmx.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 19:50:27 -0000 * Nathan Whitehorn wrote: > Also on the subject of nVidia NICs, I've fixed the device timeout > problem on nve(4). It appears that some revisions of the hardware don't > send interrupts on tx completion, which caused watchdog timeouts under > low load. We should take this hardware quirk into account for the nfe > port as well. I also applied this patch to my FreeBSD 6.1RC (Asus A8N-E) for testing and it works perfectly. By now I don't have any timeouts anymore! Will it be added to the official release of 6.1 or CURRENT? Regards, Marcus -- "Erschießt du mich jetzt? Nein, machst du nicht, oder?" - "Nein, mache ich nicht, aber ich kann so zielen, dass du den Rest deines Lebens in Windeln rumläufst." From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 21:04:18 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DE2116A400 for ; Fri, 28 Apr 2006 21:04:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C07843D46 for ; Fri, 28 Apr 2006 21:04:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3SL4FCP094272; Fri, 28 Apr 2006 17:04:15 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, protagonist@gmx.net Date: Fri, 28 Apr 2006 16:46:44 -0400 User-Agent: KMail/1.9.1 References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604281646.46451.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1428/Thu Apr 27 14:39:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 21:04:18 -0000 On Friday 28 April 2006 14:32, Marcus Frings wrote: > * Nathan Whitehorn wrote: > > > Also on the subject of nVidia NICs, I've fixed the device timeout > > problem on nve(4). It appears that some revisions of the hardware don't > > send interrupts on tx completion, which caused watchdog timeouts under > > low load. We should take this hardware quirk into account for the nfe > > port as well. > > I also applied this patch to my FreeBSD 6.1RC (Asus A8N-E) for testing > and it works perfectly. By now I don't have any timeouts anymore! > > Will it be added to the official release of 6.1 or CURRENT? It's in current but is probably too late for 6.1. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 21:16:36 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D92416A40F for ; Fri, 28 Apr 2006 21:16:36 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id C1DA943D4C for ; Fri, 28 Apr 2006 21:16:34 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 65255 invoked from network); 28 Apr 2006 21:16:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TERvXp0vdtB8AuCdsAtqXSsXrkobZKCVYH6D+XdDb13zFn6s7uIzofYUhBFyIQNe7P4D9HpKe22xHxlkuoIzCm+i/ct/xstdbWPCyjFR+1UXN3OQnu7QCj2vIh/gV0A9o3eP6vOoWispf+wtPtgizhoKaFWFdJw9E9J6/9QU/Q4= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp104.rog.mail.re2.yahoo.com with SMTP; 28 Apr 2006 21:16:34 -0000 Message-ID: <44528643.4050103@rogers.com> Date: Fri, 28 Apr 2006 17:16:51 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: John Baldwin References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> In-Reply-To: <200604281646.46451.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: protagonist@gmx.net, freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 21:16:36 -0000 John Baldwin wrote: > On Friday 28 April 2006 14:32, Marcus Frings wrote: > >> * Nathan Whitehorn wrote: >> >> >>> Also on the subject of nVidia NICs, I've fixed the device timeout >>> problem on nve(4). It appears that some revisions of the hardware don't >>> send interrupts on tx completion, which caused watchdog timeouts under >>> low load. We should take this hardware quirk into account for the nfe >>> port as well. >>> >> I also applied this patch to my FreeBSD 6.1RC (Asus A8N-E) for testing >> and it works perfectly. By now I don't have any timeouts anymore! >> >> Will it be added to the official release of 6.1 or CURRENT? >> > > It's in current but is probably too late for 6.1. > > Why is it too late? If it fixes a known stability problem, then why cant it be commited? If no commits are allowed during the -RC phase, then what is 6.1-RELEASE waiting for? From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 28 23:47:27 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7610716A401; Fri, 28 Apr 2006 23:47:27 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D523843D45; Fri, 28 Apr 2006 23:47:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3SNlM7O011879; Fri, 28 Apr 2006 17:47:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4452A98E.8020501@samsco.org> Date: Fri, 28 Apr 2006 17:47:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> <44528643.4050103@rogers.com> In-Reply-To: <44528643.4050103@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: protagonist@gmx.net, freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 23:47:27 -0000 Mike Jakubik wrote: > John Baldwin wrote: > >> On Friday 28 April 2006 14:32, Marcus Frings wrote: >> >> >>> * Nathan Whitehorn wrote: >>> >>> >>> >>>> Also on the subject of nVidia NICs, I've fixed the device timeout >>>> problem on nve(4). It appears that some revisions of the hardware don't >>>> send interrupts on tx completion, which caused watchdog timeouts under >>>> low load. We should take this hardware quirk into account for the nfe >>>> port as well. >>>> >>> >>> I also applied this patch to my FreeBSD 6.1RC (Asus A8N-E) for testing >>> and it works perfectly. By now I don't have any timeouts anymore! >>> >>> Will it be added to the official release of 6.1 or CURRENT? >>> >> >> >> It's in current but is probably too late for 6.1. >> >> > > > Why is it too late? If it fixes a known stability problem, then why cant > it be commited? If no commits are allowed during the -RC phase, then > what is 6.1-RELEASE waiting for? > Because there is always a last minute stream of bug fixes, and when you wait for one, another one comes up that you wait for, then another, etc, etc. At some point we have to draw the line. Also, it's good to let changes shake out for a few days before cutting a release. It's not uncommon for serious problems to be exposed several days after a commit. SO again, we have to draw the line somewhere. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 29 14:10:21 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3907616A400 for ; Sat, 29 Apr 2006 14:10:21 +0000 (UTC) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5634E43D55 for ; Sat, 29 Apr 2006 14:10:19 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FZq93-0007lb-S3 for freebsd-amd64@freebsd.org; Sat, 29 Apr 2006 16:10:01 +0200 Received: from p5089d1f0.dip.t-dialin.net ([80.137.209.240]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Apr 2006 16:10:01 +0200 Received: from protagonist by p5089d1f0.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Apr 2006 16:10:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: freebsd-amd64@freebsd.org To: freebsd-amd64@freebsd.org From: Marcus Frings Date: Sat, 29 Apr 2006 16:07:46 +0200 Organization: Schismatrix Lines: 15 Message-ID: References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5089d1f0.dip.t-dialin.net Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEURISpYn6okYIJpUSv9 //wQEAujiEg2MB+MFuTQAAACaUlEQVR42nWSQW/bMAyFOQ2CrpHbIlfZQ5BrU6HSuf0FQg1W58KY fbVjyPz7oySn7QZMCeKYn997JGHo/nNgvzb7tf0bNF9PNv8oBH+6TnO5zchk0N6Qae8115tvClMe MZ1+aXVTJFVhoDufs1kGOvt1oigA3n498b97rRm86psVAKiPK5iuvW9EdtA7EAA0GCNE7urAzj+a Ak6zUnBnZ4BOv3asMaYqjqQAl2GGILoDCANg3grwUqnzZlOMdVBxClBAiorSNnqlOFWYNgDINwan hErhNtr52PBE0B5BQmBwJiSaaXR0feJcuB65DRQZpCDTT+fWy1UIaFkkgmSgEsYU4uas8yByV8gh nI9cpyh79ppA8BqCZK8CQlSRemeJlBENSBlmgWCQJTFacnRZFLGZlJFVBWAkOzhv/TGxPd8u3PGp gLSOg3cbycDZIc4MZAW0OrJLQpyL9w4icYXIk0TeBxcCAywKrjMOpcT3Su6A8pf4NxyqNw8pkW1S VnkWaV26RG43xVy88l6IjJ7MQwUBqGS4u0DerqtfcvucBRX01iWyluJyVyKQl5iKYvTJWusjHWs3 tWs+7jl6b6dEvoYzqXPY37335NMcuuoFN/BsefpLSrzd76C3jxN3sR1msS/vU+EnIuofr10Fas9A bokoxcdrY2QeI96WuNqY2MzrjrcU5GcG9gOh9dgvjSxA3qzWIUa3Yn/RKGv+Dt4Hnt75OGoWmK8B cRuwH0e7upcHke3DDsI4rZaBGz8ATvA1IG7ejTafCc8yF+Vn+Jq3i/iMil/fvSseCD3eDiR+CevL APj9EL+dPMkfpDkFOqu3+jcAAAAASUVORK5CYII= X-PGP-Key: 0xE10F502E X-PGP-Fingerprint: 53FC 5A87 27BE 1D30 FEB4 861A 948F D6A0 E10F 502E Mail-Copies-To: nobody X-Now-Playing: End Of Green - "Sick One" [Dead End Dreaming] User-Agent: Gnus/5.110005 (No Gnus v0.5) Emacs/22.0.50 (berkeley-unix) Cancel-Lock: sha1:o66OcatcF9VDHXOdnB2N4mf+8iU= Sender: news Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: protagonist@gmx.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2006 14:10:21 -0000 * John Baldwin wrote: [nve fix] >> Will it be added to the official release of 6.1 or CURRENT? > It's in current but is probably too late for 6.1. Okay, thanks for the information. Maybe I will switch to -CURRENT soon if this fix doesn't get into 6.1. Regards, Marcus -- I walk the line between good and evil While others have been thinking about it - I've been there and back From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 29 14:20:12 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EB0116A400 for ; Sat, 29 Apr 2006 14:20:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AFEE43D45 for ; Sat, 29 Apr 2006 14:20:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 1A1DE20017E; Sat, 29 Apr 2006 16:20:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 5418B20017D; Sat, 29 Apr 2006 16:20:06 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7E9F8444F41; Sat, 29 Apr 2006 14:20:01 +0000 (UTC) Date: Sat, 29 Apr 2006 14:20:01 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: protagonist@gmx.net In-Reply-To: Message-ID: <20060429141928.T13011@maildrop.int.zabbadoz.net> References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2006 14:20:12 -0000 On Sat, 29 Apr 2006, Marcus Frings wrote: > * John Baldwin wrote: > > [nve fix] >>> Will it be added to the official release of 6.1 or CURRENT? > >> It's in current but is probably too late for 6.1. > > Okay, thanks for the information. Maybe I will switch to -CURRENT soon > if this fix doesn't get into 6.1. you could also apply the patch to 6 by hand and rebuild. That shouldn't be a problem. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 29 14:50:22 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F22416A400 for ; Sat, 29 Apr 2006 14:50:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F29143D49 for ; Sat, 29 Apr 2006 14:50:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3TEoJgd048053 for ; Sat, 29 Apr 2006 14:50:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3TEoJ2H048052; Sat, 29 Apr 2006 14:50:19 GMT (envelope-from gnats) Resent-Date: Sat, 29 Apr 2006 14:50:19 GMT Resent-Message-Id: <200604291450.k3TEoJ2H048052@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ralf Folkerts Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A918216A402 for ; Sat, 29 Apr 2006 14:48:15 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AC2A43D45 for ; Sat, 29 Apr 2006 14:48:15 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k3TEmF3v001559 for ; Sat, 29 Apr 2006 14:48:15 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k3TEmFx0001558; Sat, 29 Apr 2006 14:48:15 GMT (envelope-from nobody) Message-Id: <200604291448.k3TEmFx0001558@www.freebsd.org> Date: Sat, 29 Apr 2006 14:48:15 GMT From: Ralf Folkerts To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/96516: FreeBSD/amd64 intermittent Network-Problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2006 14:50:22 -0000 >Number: 96516 >Category: amd64 >Synopsis: FreeBSD/amd64 intermittent Network-Problems >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 29 14:50:19 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Ralf Folkerts >Release: 6.1-PRERELEASE >Organization: >Environment: FreeBSD beaster.home.folkerts-net.de 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sun Apr 2 15:33:07 CEST 2006 toor@beaster.home.folkerts-net.de:/usr/obj/usr/src/sys/GENERIC amd64 >Description: On my System the Network stops intermittent from working. Unfortunately there is no way to definitely reproduce the Problem; it seems to happen mostly when downloading large Files (i.e. FreeBSD- or Gentoo-ISOs). The symptoms are always the same: Apr 29 15:07:05 beaster kernel: Interrupt storm detected on "irq21:"; throttling interrupt source Apr 29 15:07:17 beaster kernel: xl0: watchdog timeout Apr 29 15:07:17 beaster kernel: xl0: link state changed to DOWN Apr 29 15:07:18 beaster kernel: nfs server boss:/share: not responding Apr 29 15:07:19 beaster kernel: xl0: link state changed to UP Apr 29 15:07:20 beaster kernel: nfs server boss:/share: not responding i.e. first an Interrupt-Storm will be reported on irq21, then xl0 will stop working. I already tried: - First replaced the NIC (a Broadcom one) with the 3C905. Didn't help. - Took the Mainboard to the Dealer and had it exchanged. Didn't help. - Placed a fan in front of the NIC. - Exchanged the Soundcard and - Exchanged the Graphics Card. - Updated the Baord's BIOS and FreeBSD (tracked RELENG_6). Nothing helped. I also installed Gentoo-Linux/amd64 on a free Partition and had that running for while, however, that never ran into a Problem. Now, I know this is no "proof" for error-free Hardware; hwoever, it seems to me that there is a slight problem in FreeBSD. Please also note that, except for the Network-hangs (which are very painfull, as I use NIS and NFS which means I cannot do much while the Network is down excepttrying to bring the machine down somewhat gracefully) I really enjoy FreeBSD/amd64! The Mainboard is a ASRock 939Dual SATA 2. Here's the dmesg.today: --- Copyright (c) 1992-2006 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 6.1-PRERELEASE #0: Sun Apr 2 15:33:07 CEST 2006 toor@beaster.home.folkerts-net.de:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2000.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073414144 (1023 MB) avail memory = 1024503808 (977 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-39 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 29 at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 34 at device 2.0 on pci0 pci2: on pcib2 pcib3: irq 39 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0xbc00-0xbc07,0xb880-0xb883,0x b800-0xb807,0xb480-0xb483,0xb400-0xb40f mem 0xfc8fe000-0xfc8fffff irq 35 at devi ce 0.0 on pci3 ata2: on atapci0 agp0: mem 0xdc000000-0xdfffffff at device 4.0 on pci0 pcib4: at device 5.0 on pci0 pci4: on pcib4 pci4: at device 0.0 (no driver attached) pcib5: at device 6.0 on pci0 pci5: on pcib5 pcm0: port 0xcc00-0xcc3f irq 21 at device 6.0 on pci5 pcm0: pcm0: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xc880-0xc8ff mem 0xfeaffc00-0xfeaf fc7f irq 22 at device 7.0 on pci5 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:10:5a:36:f2:71 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 17.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177, 0x376,0xff00-0xff0f at device 18.0 on pci0 ata0: on atapci1 ata1: on atapci1 atapci2: port 0xec00-0xec07,0xe080-0xe083,0x e000-0xe007,0xdc00-0xdc03,0xd880-0xd88f irq 19 at device 18.1 on pci0 ata3: on atapci2 ata4: on atapci2 ohci0: mem 0xfebfd000-0xfebfdfff irq 20 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfebfc000-0xfebfcfff irq 21 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xfebfb000-0xfebfbfff irq 22 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered ehci0: mem 0xfebfe800-0xfebfe8ff irq 23 at device 19.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi 0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on ac pi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xcf7ff on isa0 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 uhub4: vendor 0x04cc product 0x1122, class 9/0, rev 1.10/1.10, addr 2 uhub4: 2 ports with 2 removable, self powered Timecounter "TSC" frequency 2000077459 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff805f1ce0, 0) error 6 ad0: 78167MB at ata0-master UDMA133 ad1: 58644MB at ata0-slave UDMA100 acd0: DVDR at ata1-master UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad0s1a --- Here's a somewhat larger window from /var/log/messages: Apr 29 15:07:05 beaster kernel: Interrupt storm detected on "irq21:"; throttling interrupt source Apr 29 15:07:17 beaster kernel: xl0: watchdog timeout Apr 29 15:07:17 beaster kernel: xl0: link state changed to DOWN Apr 29 15:07:18 beaster kernel: nfs server boss:/share: not responding Apr 29 15:07:19 beaster kernel: xl0: link state changed to UP Apr 29 15:07:20 beaster kernel: nfs server boss:/share: not responding Apr 29 15:07:28 beaster kernel: xl0: watchdog timeout Apr 29 15:07:28 beaster kernel: xl0: link state changed to DOWN Apr 29 15:07:28 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:07:28 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:07:31 beaster kernel: xl0: link state changed to UP Apr 29 15:07:39 beaster kernel: xl0: watchdog timeout Apr 29 15:07:39 beaster kernel: xl0: link state changed to DOWN Apr 29 15:07:41 beaster kernel: xl0: link state changed to UP Apr 29 15:07:49 beaster kernel: xl0: watchdog timeout Apr 29 15:07:49 beaster kernel: xl0: link state changed to DOWN Apr 29 15:07:51 beaster kernel: xl0: link state changed to UP Apr 29 15:07:55 beaster kernel: nfs server boss:/share: not responding Apr 29 15:08:12 beaster kernel: xl0: watchdog timeout Apr 29 15:08:12 beaster kernel: xl0: link state changed to DOWN Apr 29 15:08:12 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:08:13 beaster kernel: nfs server boss:/share: not responding Apr 29 15:08:15 beaster kernel: xl0: link state changed to UP Apr 29 15:08:21 beaster kernel: nfs server boss:/share: not responding Apr 29 15:08:26 beaster kernel: xl0: watchdog timeout Apr 29 15:08:26 beaster kernel: xl0: link state changed to DOWN Apr 29 15:08:26 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:08:26 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:08:26 beaster kernel: nfs server boss:/share: not responding Apr 29 15:08:28 beaster kernel: xl0: link state changed to UP Apr 29 15:08:38 beaster kernel: xl0: watchdog timeout Apr 29 15:08:38 beaster kernel: xl0: link state changed to DOWN Apr 29 15:08:38 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:08:40 beaster kernel: xl0: link state changed to UP Apr 29 15:08:44 beaster kernel: nfs server boss:/share: not responding Apr 29 15:08:57 beaster kernel: xl0: watchdog timeout Apr 29 15:08:57 beaster kernel: xl0: link state changed to DOWN Apr 29 15:08:57 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:08:58 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:00 beaster kernel: xl0: link state changed to UP Apr 29 15:09:08 beaster kernel: xl0: watchdog timeout Apr 29 15:09:08 beaster kernel: xl0: link state changed to DOWN Apr 29 15:09:08 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:10 beaster kernel: xl0: link state changed to UP Apr 29 15:09:14 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:19 beaster kernel: xl0: watchdog timeout Apr 29 15:09:19 beaster kernel: xl0: link state changed to DOWN Apr 29 15:09:19 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:20 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:21 beaster kernel: xl0: link state changed to UP Apr 29 15:09:28 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:32 beaster kernel: xl0: watchdog timeout Apr 29 15:09:32 beaster kernel: xl0: link state changed to DOWN Apr 29 15:09:32 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:32 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:33 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:35 beaster kernel: xl0: link state changed to UP Apr 29 15:09:41 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:46 beaster kernel: xl0: watchdog timeout Apr 29 15:09:46 beaster kernel: xl0: link state changed to DOWN Apr 29 15:09:46 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:46 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:47 beaster kernel: nfs server boss:/share: not responding Apr 29 15:09:48 beaster kernel: xl0: link state changed to UP Apr 29 15:09:57 beaster kernel: xl0: watchdog timeout Apr 29 15:09:57 beaster kernel: xl0: link state changed to DOWN Apr 29 15:09:57 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:09:59 beaster kernel: xl0: link state changed to UP Apr 29 15:10:06 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:09 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:17 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:10:26 beaster kernel: xl0: watchdog timeout Apr 29 15:10:26 beaster kernel: xl0: link state changed to DOWN Apr 29 15:10:26 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:10:26 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:10:26 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:10:27 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:29 beaster kernel: xl0: link state changed to UP Apr 29 15:10:37 beaster kernel: xl0: watchdog timeout Apr 29 15:10:37 beaster kernel: xl0: link state changed to DOWN Apr 29 15:10:37 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:10:39 beaster kernel: xl0: link state changed to UP Apr 29 15:10:43 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:48 beaster kernel: xl0: watchdog timeout Apr 29 15:10:48 beaster kernel: xl0: link state changed to DOWN Apr 29 15:10:48 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:10:49 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:50 beaster kernel: nfs server boss:/share: not responding Apr 29 15:10:50 beaster kernel: xl0: link state changed to UP Apr 29 15:10:57 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:11:09 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:11:19 beaster kernel: nfs server boss:/share: not responding Apr 29 15:11:21 beaster kernel: nfs server boss:/share: not responding Apr 29 15:11:21 beaster kernel: xl0: watchdog timeout Apr 29 15:11:21 beaster kernel: xl0: link state changed to DOWN Apr 29 15:11:21 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:11:21 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:11:21 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:11:21 beaster kernel: nfs server boss:/share: not responding Apr 29 15:11:23 beaster kernel: xl0: link state changed to UP Apr 29 15:11:42 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:11:51 beaster kernel: nfs server boss:/share: not responding Apr 29 15:11:54 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:12:06 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:12:17 beaster kernel: xl0: watchdog timeout Apr 29 15:12:17 beaster kernel: xl0: link state changed to DOWN Apr 29 15:12:17 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:12:17 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:12:19 beaster kernel: xl0: link state changed to UP Apr 29 15:12:23 beaster kernel: nfs server boss:/share: not responding Apr 29 15:12:28 beaster kernel: xl0: watchdog timeout Apr 29 15:12:28 beaster kernel: xl0: link state changed to DOWN Apr 29 15:12:28 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:12:29 beaster kernel: nfs server boss:/share: not responding Apr 29 15:12:30 beaster kernel: nfs server boss:/share: not responding Apr 29 15:12:30 beaster kernel: xl0: link state changed to UP Apr 29 15:12:37 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:12:49 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:13:01 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:01 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:01 beaster kernel: xl0: watchdog timeout Apr 29 15:13:01 beaster kernel: xl0: link state changed to DOWN Apr 29 15:13:01 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:01 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:01 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:13:01 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:03 beaster kernel: xl0: link state changed to UP Apr 29 15:13:11 beaster kernel: xl0: watchdog timeout Apr 29 15:13:11 beaster kernel: xl0: link state changed to DOWN Apr 29 15:13:11 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:13 beaster kernel: xl0: link state changed to UP Apr 29 15:13:17 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:22 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:13:23 beaster kernel: nfs server boss:/usr/ports/distfiles: not respon ding Apr 29 15:13:30 beaster kernel: xl0: watchdog timeout Apr 29 15:13:30 beaster kernel: xl0: link state changed to DOWN Apr 29 15:13:30 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:30 beaster kernel: nfs server boss:/usr/ports/distfiles: is alive a gain Apr 29 15:13:30 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:13:31 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:32 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:33 beaster kernel: xl0: link state changed to UP Apr 29 15:13:42 beaster kernel: xl0: watchdog timeout Apr 29 15:13:42 beaster kernel: xl0: link state changed to DOWN Apr 29 15:13:42 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:42 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:13:43 beaster kernel: nfs server boss:/share: not responding Apr 29 15:13:44 beaster kernel: xl0: link state changed to UP Apr 29 15:13:54 beaster kernel: nfs server boss:/share: not responding Apr 29 15:14:02 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:14:13 beaster kernel: nfs server boss:/share: not responding Apr 29 15:14:14 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:14:25 beaster kernel: nfs server boss:/share: not responding Apr 29 15:14:26 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:14:38 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:14:44 beaster kernel: nfs server boss:/share: not responding Apr 29 15:14:50 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:14:56 beaster kernel: nfs server boss:/share: not responding Apr 29 15:15:02 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:15:14 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:15:15 beaster kernel: nfs server boss:/share: not responding Apr 29 15:15:26 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:15:27 beaster kernel: nfs server boss:/share: not responding Apr 29 15:15:38 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:15:46 beaster kernel: nfs server boss:/share: not responding Apr 29 15:15:50 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:15:51 beaster login: ROOT LOGIN (toor) ON ttyv2 Apr 29 15:15:58 beaster kernel: nfs server boss:/share: not responding Apr 29 15:16:02 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:16:14 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:16:17 beaster kernel: nfs server boss:/share: not responding Apr 29 15:16:26 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:16:29 beaster kernel: nfs server boss:/share: not responding Apr 29 15:16:38 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:16:41 beaster kernel: xl0: watchdog timeout Apr 29 15:16:41 beaster kernel: xl0: link state changed to DOWN Apr 29 15:16:41 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:16:41 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:16:44 beaster kernel: xl0: link state changed to UP Apr 29 15:16:50 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:16:54 beaster kernel: nfs server boss:/share: not responding Apr 29 15:16:54 beaster kernel: nfs server boss:/share: not responding Apr 29 15:17:02 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:17:14 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:17:24 beaster kernel: xl0: watchdog timeout Apr 29 15:17:24 beaster kernel: xl0: link state changed to DOWN Apr 29 15:17:24 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:17:25 beaster kernel: nfs server boss:/share: not responding Apr 29 15:17:26 beaster kernel: xl0: link state changed to UP Apr 29 15:17:26 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:17:36 beaster kernel: nfs server boss:/usr/ports/distfiles: not respon ding Apr 29 15:17:38 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:17:50 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:17:56 beaster kernel: nfs server boss:/share: not responding Apr 29 15:18:01 beaster kernel: xl0: watchdog timeout Apr 29 15:18:01 beaster kernel: xl0: link state changed to DOWN Apr 29 15:18:01 beaster kernel: nfs server boss:/usr/ports/distfiles: is alive a gain Apr 29 15:18:01 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:18:01 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:18:03 beaster kernel: nfs server boss:/share: not responding Apr 29 15:18:03 beaster kernel: xl0: link state changed to UP Apr 29 15:18:04 beaster kernel: nfs server boss:/share: not responding Apr 29 15:18:22 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:18:32 beaster kernel: xl0: watchdog timeout Apr 29 15:18:32 beaster kernel: xl0: link state changed to DOWN Apr 29 15:18:32 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:18:32 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:18:32 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:18:33 beaster kernel: nfs server boss:/share: not responding Apr 29 15:18:34 beaster kernel: xl0: link state changed to UP Apr 29 15:18:34 beaster kernel: nfs server boss:/share: not responding Apr 29 15:18:52 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:19:03 beaster kernel: nfs server boss:/share: not responding Apr 29 15:19:04 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:19:04 beaster kernel: nfs server boss:/share: not responding Apr 29 15:19:16 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:19:28 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:19:34 beaster kernel: nfs server boss:/share: not responding Apr 29 15:19:35 beaster kernel: nfs server boss:/share: not responding Apr 29 15:19:40 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:20:04 beaster last message repeated 2 times Apr 29 15:20:05 beaster kernel: nfs server boss:/share: not responding Apr 29 15:20:06 beaster kernel: nfs server boss:/share: not responding Apr 29 15:20:16 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:20:28 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:20:36 beaster kernel: nfs server boss:/share: not responding Apr 29 15:20:37 beaster kernel: nfs server boss:/share: not responding Apr 29 15:20:40 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:21:04 beaster last message repeated 2 times Apr 29 15:21:07 beaster kernel: nfs server boss:/share: not responding Apr 29 15:21:08 beaster kernel: nfs server boss:/share: not responding Apr 29 15:21:13 beaster login: ROOT LOGIN (toor) ON ttyv3 Apr 29 15:21:16 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:21:25 beaster kernel: xl0: watchdog timeout Apr 29 15:21:25 beaster kernel: xl0: link state changed to DOWN Apr 29 15:21:27 beaster kernel: xl0: link state changed to UP Apr 29 15:21:28 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:21:37 beaster kernel: xl0: watchdog timeout Apr 29 15:21:37 beaster kernel: xl0: link state changed to DOWN Apr 29 15:21:37 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:21:38 beaster kernel: nfs server boss:/share: not responding Apr 29 15:21:39 beaster kernel: xl0: link state changed to UP Apr 29 15:21:39 beaster kernel: nfs server boss:/share: not responding Apr 29 15:21:57 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:22:06 beaster kernel: xl0: watchdog timeout Apr 29 15:22:06 beaster kernel: xl0: link state changed to DOWN Apr 29 15:22:06 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:22:06 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:22:06 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:22:07 beaster kernel: nfs server boss:/share: not responding Apr 29 15:22:08 beaster kernel: xl0: link state changed to UP Apr 29 15:22:08 beaster kernel: nfs server boss:/share: not responding Apr 29 15:22:25 beaster kernel: xl0: watchdog timeout Apr 29 15:22:25 beaster kernel: xl0: link state changed to DOWN Apr 29 15:22:25 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:22:25 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:22:25 beaster kernel: nfs server boss:/share: not responding Apr 29 15:22:27 beaster kernel: xl0: link state changed to UP Apr 29 15:22:34 beaster kernel: nfs server boss:/share: not responding Apr 29 15:22:45 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:22:56 beaster kernel: nfs server boss:/share: not responding Apr 29 15:22:57 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:23:04 beaster kernel: nfs server boss:/share: not responding Apr 29 15:23:09 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:23:17 beaster kernel: xl0: watchdog timeout Apr 29 15:23:17 beaster kernel: xl0: link state changed to DOWN Apr 29 15:23:17 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:23:17 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:23:17 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" OK Apr 29 15:23:19 beaster kernel: xl0: link state changed to UP Apr 29 15:23:30 beaster kernel: nfs server boss:/share: not responding Apr 29 15:23:38 beaster kernel: xl0: watchdog timeout Apr 29 15:23:38 beaster kernel: xl0: link state changed to DOWN Apr 29 15:23:38 beaster /usr/sbin/ypbind[444]: NIS server [10.0.0.10] for domain "wrz" not responding Apr 29 15:23:40 beaster kernel: xl0: link state changed to UP Apr 29 15:24:01 beaster kernel: nfs server boss:/share: not responding Apr 29 15:24:07 beaster kernel: xl0: watchdog timeout Apr 29 15:24:07 beaster kernel: xl0: link state changed to DOWN Apr 29 15:24:07 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:24:09 beaster kernel: xl0: link state changed to UP Apr 29 15:24:13 beaster kernel: nfs server boss:/share: not responding Apr 29 15:24:19 beaster kernel: nfs server boss:/usr/ports/distfiles: not respon ding Apr 29 15:24:27 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:24:39 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:24:43 beaster kernel: nfs server boss:/share: not responding Apr 29 15:24:50 beaster kernel: nfs server boss:/usr/ports/distfiles: not respon ding Apr 29 15:24:51 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:25:01 beaster shutdown: halt by toor: Apr 29 15:25:03 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:25:14 beaster kernel: nfs server boss:/share: not responding Apr 29 15:25:15 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:25:21 beaster kernel: nfs server boss:/usr/ports/distfiles: not respon ding Apr 29 15:25:27 beaster /usr/sbin/ypbind[3031]: NIS server [10.0.0.10] for domai n "wrz" not responding Apr 29 15:25:32 beaster sshd[1500]: fatal: login_init_entry: Cannot find user "r alf" Apr 29 15:25:33 beaster rc.shutdown: 30 second watchdog timeout expired. Shutdow n terminated. Apr 29 15:25:33 beaster init: /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user mode Apr 29 15:25:33 beaster syslogd: exiting on signal 15 Apr 29 15:31:45 beaster syslogd: kernel boot file is /boot/kernel/kernel Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/usr/ports/distfiles: is alive a gain Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: Waiting (max 60 seconds) for system process `vnl ru' to stop...done Apr 29 15:31:45 beaster kernel: Waiting (max 60 seconds) for system process `buf daemon' to stop...done Apr 29 15:31:45 beaster kernel: Waiting (max 60 seconds) for system process `syn cer' to stop...xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: Apr 29 15:31:45 beaster kernel: Syncing disks, vnodes remaining...22 Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: 15 Apr 29 15:31:45 beaster kernel: nfs server boss:/share: not responding Apr 29 15:31:45 beaster kernel: 14 10 10 4 0 1 1 0 0 xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: nfs server boss:/share: is alive again Apr 29 15:31:45 beaster kernel: 0 0 0 0 0 0 0 0 0 0 0 0 xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: 1 1 0 1 1 0 0 0 0 0 xl0: watchdog timeout Apr 29 15:31:45 beaster kernel: 0 0 0 0 0 0 0 0 0 timed out Apr 29 15:31:45 beaster kernel: All buffers synced. Apr 29 15:31:45 beaster kernel: Uptime: 1h12m11s --- Here's the pciconf -vl: hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x169510b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000040 chip=0x524b10b9 rev=0x00 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = PCI-PCI pcib2@pci0:2:0: class=0x060400 card=0x00000040 chip=0x524c10b9 rev=0x00 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = PCI-PCI pcib3@pci0:3:0: class=0x060400 card=0x00000040 chip=0x524d10b9 rev=0x00 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = PCI-PCI agp0@pci0:4:0: class=0x060000 card=0x00000000 chip=0x168910b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = HOST-PCI pcib4@pci0:5:0: class=0x060400 card=0x00000000 chip=0x524610b9 rev=0x00 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' class = bridge subclass = PCI-PCI pcib5@pci0:6:0: class=0x060401 card=0x00000000 chip=0x524910b9 rev=0x00 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' device = 'M5249 HyperTransport to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:7:0: class=0x060100 card=0x15631849 chip=0x156310b9 rev=0x70 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M1563 South Bridge with Hypertransport Support' class = bridge subclass = PCI-ISA none0@pci0:7:1: class=0x068000 card=0x71011849 chip=0x710110b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M7101 Power Management Controller' class = bridge none1@pci0:8:0: class=0x040100 card=0x08501849 chip=0x545510b9 rev=0x20 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1563M Southbridge AC'97 Audio Controller' class = multimedia subclass = audio none2@pci0:17:0: class=0x020000 card=0x52631849 chip=0x526310b9 rev=0x40 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' class = network subclass = ethernet atapci1@pci0:18:0: class=0x01018a card=0x52291849 chip=0x522910b9 rev=0xc7 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1543 Southbridge EIDE Controller' class = mass storage subclass = ATA atapci2@pci0:18:1: class=0x01018f card=0x52891849 chip=0x528910b9 rev=0x10 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' class = mass storage subclass = ATA ohci0@pci0:19:0: class=0x0c0310 card=0x52371849 chip=0x523710b9 rev=0x03 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M5237 OpenHCI 1.1 USB Controller' class = serial bus subclass = USB ohci1@pci0:19:1: class=0x0c0310 card=0x52371849 chip=0x523710b9 rev=0x03 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M5237 OpenHCI 1.1 USB Controller' class = serial bus subclass = USB ohci2@pci0:19:2: class=0x0c0310 card=0x52371849 chip=0x523710b9 rev=0x03 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M5237 OpenHCI 1.1 USB Controller' class = serial bus subclass = USB ehci0@pci0:19:3: class=0x0c0320 card=0x52391849 chip=0x523910b9 rev=0x01 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB hostb1@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI atapci0@pci3:0:0: class=0x010601 card=0x03601849 chip=0x2360197b rev=0x00 hdr=0x00 class = mass storage none3@pci4:0:0: class=0x030000 card=0x31031458 chip=0x032210de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce FX 5200 [NV34.3]' class = display subclass = VGA pcm0@pci5:6:0: class=0x040100 card=0x80011274 chip=0x58801274 rev=0x04 hdr=0x00 vendor = 'Creative (Was: Ensoniq)' device = '5880 AudioPci' class = multimedia subclass = audio xl0@pci5:7:0: class=0x020000 card=0x905510b7 chip=0x905510b7 rev=0x30 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC' class = network subclass = ethernet --- If you need more Info to track this down please just let me know! >How-To-Repeat: Unfortunately I didn't find a way to definitely reproduce the Problem :-( It seems to happen when there is haevy Network-Traffic. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 29 16:01:03 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD97916A401 for ; Sat, 29 Apr 2006 16:01:03 +0000 (UTC) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD4D143D49 for ; Sat, 29 Apr 2006 16:01:02 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FZrsP-00060U-CM for freebsd-amd64@freebsd.org; Sat, 29 Apr 2006 18:00:57 +0200 Received: from p5089d1f0.dip.t-dialin.net ([80.137.209.240]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Apr 2006 18:00:57 +0200 Received: from protagonist by p5089d1f0.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Apr 2006 18:00:57 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: freebsd-amd64@freebsd.org To: freebsd-amd64@freebsd.org From: Marcus Frings Date: Sat, 29 Apr 2006 18:00:49 +0200 Organization: Schismatrix Lines: 19 Message-ID: References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> <20060429141928.T13011@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5089d1f0.dip.t-dialin.net Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAADFBMVEUfHiNTUleFg4i6uLwf 9T0YAAACT0lEQVR42hWRzU/TAByG3w4oGZgQD0zX6U6GAMaPA/HipRMx4YaGLlmX6GIAbQniwRnA CI2JaOJlMxRsjVpNW+hvETwYI9VtoEcu00QS8LIDEtgS9YLizIbzH3jePO8D1WecerGKNiDqYMAx WpZLKvtliinAEXPtcG3b1XuaIQzkDhttO0PB2YINcUHxmmx2w8uSA5pXGu+De8XyB1RYNj/cXcco zBTSkETMsMQDrsohPMRMepYTwJiswZ672c0o1/RU0RAwbD65CpPL6KFMFfD8rsFk6W8lcWIR052d SwH5u7Rr1RUhXAS9x2ze45oRiE7t+CKOg2v1EdQb7TMPkqxq1luA7Ob83nFrlA+VtqHvoiPo50i0 JgiUY0z53pTQ59N0DPJHK/nlEp3jZQdq414lZwRkKiAMIftpXelDL3d+TQDN0gq4Xp+JMYIT7ZoM RaksOuESxJc1NSRbejlu+eGYAc9Tlp4lDnEahK4sc0eT02D5CMKpCpbedPXU7nf74cplkONOk8MR hMEtxOczo/MXVAHyzhZaVlN5T8HWQVETTbLEwxqwYNFlZyi+BEzYEsLdj1cenZxjw64qQspoybdH GiLvuHQEVB6JjQTPGMeYhU2kkmZHR1MFDUp1p5+7fjDG9gES348I/dwXY3uBINkQLuW9Cc96D0PJ 5mrGRP0G7NTe1z8aIr+UhgI4mou1V397yLd9MFCLVs9/Gq7wW2hFkG+GmPZpuHV2c9Ja1PHt9WmT +VEMpSxJhfj5o8Iyv8GsLWhVn5mEn78NGIHtf2pJ/rxyPK4SAAAAAElFTkSuQmCC X-PGP-Key: 0xE10F502E X-PGP-Fingerprint: 53FC 5A87 27BE 1D30 FEB4 861A 948F D6A0 E10F 502E Mail-Copies-To: nobody X-Now-Playing: Joy Division - "Dead Souls" [Heart And Soul. Four] User-Agent: Gnus/5.110005 (No Gnus v0.5) Emacs/22.0.50 (berkeley-unix) Cancel-Lock: sha1:5EoRelFinzsbTitHMwD3I90DVPo= Sender: news Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: protagonist@gmx.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2006 16:01:03 -0000 * "Bjoern A. Zeeb" wrote: >> Okay, thanks for the information. Maybe I will switch to -CURRENT soon >> if this fix doesn't get into 6.1. > you could also apply the patch to 6 by hand and rebuild. That > shouldn't be a problem. Yes, I know because that's how I did it this time but I'm just too lazy to apply the patch manually every time (between cvsup and make buildkernel). :-) Regards, Marcus -- Spook words for the NSA: President, Military Intelligence, PGP, Defense, SASR, CDC, DOE, FMS, HPCC, NTIS, SEL, USCODE, CISE, SIRC, CIM, ISN, DJC, SGC, CDA, M-14, Infowar, Attack, EloAufkl, Chemical, Activist, CRYPT, Lacrosse, Control, Communications, VX, Assassin, Sniper, Ingram, Industrial, Plutonium, Nuclear