From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 4 19:50:19 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 524E916A407 for ; Sun, 4 Feb 2007 19:50:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0066913C4A5 for ; Sun, 4 Feb 2007 19:50:18 +0000 (UTC) (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 l14JoIa9050171 for ; Sun, 4 Feb 2007 19:50:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l14JoIHq050170; Sun, 4 Feb 2007 19:50:18 GMT (envelope-from gnats) Resent-Date: Sun, 4 Feb 2007 19:50:18 GMT Resent-Message-Id: <200702041950.l14JoIHq050170@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, Justin James Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5632716A402 for ; Sun, 4 Feb 2007 19:41:32 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id 2D3EC13C4A7 for ; Sun, 4 Feb 2007 19:41:32 +0000 (UTC) (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 l14JfW75027518 for ; Sun, 4 Feb 2007 19:41:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l14JfVLn027517; Sun, 4 Feb 2007 19:41:31 GMT (envelope-from nobody) Message-Id: <200702041941.l14JfVLn027517@www.freebsd.org> Date: Sun, 4 Feb 2007 19:41:31 GMT From: Justin James To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/108774: Reboots/seizes during compiles 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: Sun, 04 Feb 2007 19:50:19 -0000 >Number: 108774 >Category: amd64 >Synopsis: Reboots/seizes during compiles >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 04 19:50:18 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Justin James >Release: 62.-RELEASE >Organization: >Environment: FreeBSD stantz.titaniumcrowbar.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 08:32:24 UTC 2007 root@portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When compiling ports, or using portupgrade, system freezes or reboots itself. This happens at random, but it usually seems to happen during "make clean". This also occured on 6.1-RELEASE. >How-To-Repeat: Try compiling from source. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 4 23:01:45 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 42E6516A401 for ; Sun, 4 Feb 2007 23:01:45 +0000 (UTC) (envelope-from neil@mpfspromotions.com) Received: from svr2.16o.com (svr2.16o.com [83.149.104.131]) by mx1.freebsd.org (Postfix) with SMTP id A761613C467 for ; Sun, 4 Feb 2007 23:01:44 +0000 (UTC) (envelope-from neil@mpfspromotions.com) Received: (qmail 63674 invoked from network); 4 Feb 2007 22:34:59 -0000 Received: from svr1.16o.com (69.50.175.34) by svr2.16o.com with SMTP; 4 Feb 2007 22:34:59 -0000 Received: (qmail 4073 invoked from network); 4 Feb 2007 22:35:00 -0000 Received: from i-195-137-35-72.freedom2surf.net (HELO NEILPC) (195.137.35.72) by 0 with SMTP; 4 Feb 2007 22:35:00 -0000 From: "Neil Doody" To: Date: Sun, 4 Feb 2007 22:38:11 -0000 Message-ID: <048b01c748ad$316c1f20$94445d60$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcdIrSPaEjfz9wueRCW0m6V/6uw1eg== Content-Language: en-gb x-cr-hashedpuzzle: ALN7 ANmM Cm3N DxL6 EBLo Ec6B G+Vh H48/ H76J Iyrz JAgA JOdW JvgI J3/Q KPgL LlBq; 1; YQBtAGQANgA0AEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {D054E693-E5E3-4FF4-8165-DE81008E2C98}; bgBlAGkAbABAAG0AcABmAHMAcAByAG8AbQBvAHQAaQBvAG4AcwAuAGMAbwBtAA==; Sun, 04 Feb 2007 22:38:07 GMT; SQBuAHMAcABlAGMAdABpAG4AZwAgAHAAcgBvAGMAZQBzAHMAZQBzAA== x-cr-puzzleid: {D054E693-E5E3-4FF4-8165-DE81008E2C98} Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Inspecting processes 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: Sun, 04 Feb 2007 23:01:45 -0000 I am having a problem in which apache processes are slowly going off on some sort of rampage and I cant trace what is causing it. Basically over time httpd processes start hogging 100% cpu and new processes are spawned, until the apache server is shutdown these remain at 100% and they increase until they bring the server down. I was wondering what tools I can use to see exactly what these processes are doing, why they are stuck and what are they waiting for? I am running 6.2-STABLE FreeBSD 6.2-STABLE #5 it is on the AMD64 platform. From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 4 23:05:24 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BB2916A401; Sun, 4 Feb 2007 23:05:24 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D6F3513C442; Sun, 4 Feb 2007 23:05:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l14N5NR6068112; Sun, 4 Feb 2007 23:05:23 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l14N5N2t068108; Sun, 4 Feb 2007 23:05:23 GMT (envelope-from kris) Date: Sun, 4 Feb 2007 23:05:23 GMT From: Kris Kennaway Message-Id: <200702042305.l14N5N2t068108@freefall.freebsd.org> To: j_james@mindspring.com, kris@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/108774: Reboots/seizes during compiles 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: Sun, 04 Feb 2007 23:05:24 -0000 Synopsis: Reboots/seizes during compiles State-Changed-From-To: open->closed State-Changed-By: kris State-Changed-When: Sun Feb 4 23:04:49 UTC 2007 State-Changed-Why: You have failing hardware. Check RAMk, power supply, cooling, cabling, etc. http://www.freebsd.org/cgi/query-pr.cgi?pr=108774 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 00:43:56 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED88A16A400; Mon, 5 Feb 2007 00:43:56 +0000 (UTC) (envelope-from j_james@mindspring.com) Received: from ms-smtp-04.southeast.rr.com (ms-smtp-04.southeast.rr.com [24.25.9.103]) by mx1.freebsd.org (Postfix) with ESMTP id B358313C441; Mon, 5 Feb 2007 00:43:56 +0000 (UTC) (envelope-from j_james@mindspring.com) Received: from Venkman (rrcs-24-199-191-178.midsouth.biz.rr.com [24.199.191.178]) by ms-smtp-04.southeast.rr.com (8.13.6/8.13.6) with ESMTP id l14NoH4R008030; Sun, 4 Feb 2007 18:50:17 -0500 (EST) From: "Justin James" To: "'Kris Kennaway'" , References: <200702042305.l14N5N2t068108@freefall.freebsd.org> In-Reply-To: <200702042305.l14N5N2t068108@freefall.freebsd.org> Date: Sun, 4 Feb 2007 18:50:18 -0500 Message-ID: <035501c748b7$3a3a9000$aeafb000$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcdIsPN/qTQGRN2HQ3e32tnGdqFtggABePGA Content-Language: en-us X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: RE: amd64/108774: Reboots/seizes during compiles 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, 05 Feb 2007 00:43:57 -0000 It is all new hardware. PSU has been swapped and behavior persists. All drive and drive power cables were swapped as well. RAM passes Memtest86 with flying colors. System runs like a top except for during compilation. Amount of uptime is irrelevant. Hardware monitors do not indicate overheating condition. Have any similar errors been reported with a Core 2 Duo E6300 system with amd64? - Justin -----Original Message----- From: Kris Kennaway [mailto:kris@FreeBSD.org] Sent: Sunday, February 04, 2007 6:05 PM To: j_james@mindspring.com; kris@FreeBSD.org; freebsd-amd64@FreeBSD.org Subject: Re: amd64/108774: Reboots/seizes during compiles Synopsis: Reboots/seizes during compiles State-Changed-From-To: open->closed State-Changed-By: kris State-Changed-When: Sun Feb 4 23:04:49 UTC 2007 State-Changed-Why: You have failing hardware. Check RAMk, power supply, cooling, cabling, etc. http://www.freebsd.org/cgi/query-pr.cgi?pr=108774 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 06:12:12 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4065616A401 for ; Mon, 5 Feb 2007 06:12:12 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id CE02F13C441 for ; Mon, 5 Feb 2007 06:12:11 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1969662nfc for ; Sun, 04 Feb 2007 22:12:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=JwBmfUZyCBoAXo7tWeZx0hZFXiF0RffofEYw06OjawTI25yNtC48GN0ETSxXk2ywgK3/ONQu/Eg8qT2L8P2NQnBXu9tJSzmN8K16T2TStyiaX61iwd2kJCECX+1q5vyXCE8S+dWDG10wH+bIw9yNaig9ydwhQ6a14V65Jvi2r5Q= Received: by 10.48.14.4 with SMTP id 4mr1808552nfn.1170655930188; Sun, 04 Feb 2007 22:12:10 -0800 (PST) Received: by 10.49.63.7 with HTTP; Sun, 4 Feb 2007 22:12:10 -0800 (PST) Message-ID: <346a80220702042212l43d1add7re9c59a961aa375bd@mail.gmail.com> Date: Sun, 4 Feb 2007 23:12:10 -0700 From: "Coleman Kane" To: "Justin James" In-Reply-To: <035501c748b7$3a3a9000$aeafb000$@com> MIME-Version: 1.0 References: <200702042305.l14N5N2t068108@freefall.freebsd.org> <035501c748b7$3a3a9000$aeafb000$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/108774: Reboots/seizes during compiles X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 06:12:12 -0000 On 2/4/07, Justin James wrote: > > It is all new hardware. PSU has been swapped and behavior persists. All > drive and drive power cables were swapped as well. RAM passes Memtest86 > with > flying colors. System runs like a top except for during compilation. > Amount > of uptime is irrelevant. Hardware monitors do not indicate overheating > condition. Have any similar errors been reported with a Core 2 Duo E6300 > system with amd64? > > - Justin > > -----Original Message----- > From: Kris Kennaway [mailto:kris@FreeBSD.org] > Sent: Sunday, February 04, 2007 6:05 PM > To: j_james@mindspring.com; kris@FreeBSD.org; freebsd-amd64@FreeBSD.org > Subject: Re: amd64/108774: Reboots/seizes during compiles > > Synopsis: Reboots/seizes during compiles > > State-Changed-From-To: open->closed > State-Changed-By: kris > State-Changed-When: Sun Feb 4 23:04:49 UTC 2007 > State-Changed-Why: > You have failing hardware. Check RAMk, power supply, cooling, > cabling, etc. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=108774 I have had similar problems with an amd64 laptop (Athlon64 Mobile). If it is running full-bore (2.2GHz), then it will shut itself off or reboot itself while compiling or doing heavy processing of data. If I knock the speed down to 1.6GHz, the system is perfectly stable. I am guessing that the system (under Windows) was not meant to be run at full-speed all the time. -- Coleman Kane From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 11:10:48 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9992716A40E for ; Mon, 5 Feb 2007 11:10:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id F01C913C4BA for ; Mon, 5 Feb 2007 11:10:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l15BAjpW025735 for ; Mon, 5 Feb 2007 11:10:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l15BAf8u025722 for freebsd-amd64@FreeBSD.org; Mon, 5 Feb 2007 11:10:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Feb 2007 11:10:41 GMT Message-Id: <200702051110.l15BAf8u025722@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 05 Feb 2007 11:10:48 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/73775 amd64 Kernel panic (trap 12) when booting with (not from!) P o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Trap 12: Page fa o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not work on amd64 o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88299 amd64 swapcontext fails with errno 0 f amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 o amd64/105187 amd64 make -j2 buildworld renders FreeBSD 6.2-PRE/AMD64 unus o amd64/105207 amd64 nVidia MCP55 drivers fail to boot on 6.2B3 amd64 o amd64/105513 amd64 Kernel Panic during package installation on 6.2 beta3 o amd64/105531 amd64 gigabyte GA-M51GM-S2G / nVidia nForce 430 - does not d o amd64/105629 amd64 [re] Issue with re driver p amd64/106109 amd64 amd64: si_addr is not set when sending a signal o amd64/106604 amd64 saslauthd crashes with signal 6 on FreeBSD 6.2-PREREL o amd64/106918 amd64 Asus P5B with internal RealTek PCIe Ethernet o amd64/107345 amd64 Kernel Panic/Crash on dd if=/dev/ad4 of=/dev/ad6 bs=1m o amd64/107433 amd64 i can't install FreeBSD Release 6.1 on HP Pavillion dv o amd64/108172 amd64 Installation fails on new Intel 965 motherboards. o amd64/108328 amd64 FreeBSD-6.2: CD does not boot o amd64/108673 amd64 kgdb doesn't work very well very long 71 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu s amd64/85273 amd64 FreeBSD (NetBSD or OpenBSD) not install on laptop Comp o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/92527 amd64 [ciphy.c] ][patch] no driver for "CICADA VSC 8201 Giga o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 o amd64/104875 amd64 unsupported intel Desktop Board DG965WH o amd64/105129 amd64 Compatibility with Intel D o amd64/106186 amd64 panic in swap_pager_swap_init (amd64/smp/6.2-pre) o amd64/107858 amd64 amd64 motherboard project - none working sound and gra o amd64/108345 amd64 6.2-* GENERIC will not boot Intel PD EMT64 w/ ACPI 27 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 21:49:41 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6652F16A564; Mon, 5 Feb 2007 21:49:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id BEA9013C4BA; Mon, 5 Feb 2007 21:49:34 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (jhb@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l15LnYad078360; Mon, 5 Feb 2007 21:49:34 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l15LnY85078356; Mon, 5 Feb 2007 21:49:34 GMT (envelope-from jhb) Date: Mon, 5 Feb 2007 21:49:34 GMT From: John Baldwin Message-Id: <200702052149.l15LnY85078356@freefall.freebsd.org> To: ravi.murty@intel.com, jhb@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/108673: kgdb doesn't work very well very long 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, 05 Feb 2007 21:49:41 -0000 Synopsis: kgdb doesn't work very well very long State-Changed-From-To: open->patched State-Changed-By: jhb State-Changed-When: Mon Feb 5 21:49:19 UTC 2007 State-Changed-Why: Fix applied to HEAD. http://www.freebsd.org/cgi/query-pr.cgi?pr=108673 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 21:50:32 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B8B716A403 for ; Mon, 5 Feb 2007 21:50:32 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD6B13C4A7 for ; Mon, 5 Feb 2007 21:50:32 +0000 (UTC) (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 l15LoWWc078491 for ; Mon, 5 Feb 2007 21:50:32 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l15LoWLJ078490; Mon, 5 Feb 2007 21:50:32 GMT (envelope-from gnats) Date: Mon, 5 Feb 2007 21:50:32 GMT Message-Id: <200702052150.l15LoWLJ078490@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: amd64/108673: commit references a PR X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 21:50:32 -0000 The following reply was made to PR amd64/108673; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/108673: commit references a PR Date: Mon, 5 Feb 2007 21:48:43 +0000 (UTC) jhb 2007-02-05 21:48:32 UTC FreeBSD src repository Modified files: sys/amd64/include gdb_machdep.h Log: Change GDB_BUFSZ to be large enough to hold a register dump where each register takes 16 characters (64-bit register in hex). In practice this is a slight bit of overkill as 7 of the 56 registers are only 32-bit, but having the buffer too small results in remote kgdb trashing kernel memory when it connects. PR: amd64/108673 Submitted by: Ravi Murty, Nikhil Rao @ Intel MFC after: 3 days Revision Changes Path 1.6 +1 -1 src/sys/amd64/include/gdb_machdep.h _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 21:50:42 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7518316A402; Mon, 5 Feb 2007 21:50:41 +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 66DD913C47E; Mon, 5 Feb 2007 21:50:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l15LoX3p064131; Mon, 5 Feb 2007 16:50:38 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 5 Feb 2007 16:49:37 -0500 User-Agent: KMail/1.9.1 References: <200702020125.l121Pw1I079198@www.freebsd.org> In-Reply-To: <200702020125.l121Pw1I079198@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702051649.38456.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 05 Feb 2007 16:50:38 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2525/Mon Feb 5 11:11:08 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-gnats-submit@freebsd.org, Ravi Murty Subject: Re: amd64/108673: kgdb doesn't work very well very long 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, 05 Feb 2007 21:50:42 -0000 I've just fixed this and it should be in RELENG_6 in a couple of days. Thanks. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 22:00:52 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56E9B16A400 for ; Mon, 5 Feb 2007 22:00:52 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 05A9313C48D for ; Mon, 5 Feb 2007 22:00:52 +0000 (UTC) (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 l15M0pZ4078960 for ; Mon, 5 Feb 2007 22:00:51 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l15M0p72078959; Mon, 5 Feb 2007 22:00:51 GMT (envelope-from gnats) Date: Mon, 5 Feb 2007 22:00:51 GMT Message-Id: <200702052200.l15M0p72078959@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/108673: kgdb doesn't work very well very long X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 22:00:52 -0000 The following reply was made to PR amd64/108673; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: Ravi Murty , freebsd-gnats-submit@freebsd.org, "Rao, Nikhil" Subject: Re: amd64/108673: kgdb doesn't work very well very long Date: Mon, 5 Feb 2007 16:49:37 -0500 I've just fixed this and it should be in RELENG_6 in a couple of days. Thanks. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 5 22:05:33 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6921916A403 for ; Mon, 5 Feb 2007 22:05:33 +0000 (UTC) (envelope-from neil@mpfspromotions.com) Received: from svr2.16o.com (svr2.16o.com [83.149.104.131]) by mx1.freebsd.org (Postfix) with SMTP id 28BFB13C48E for ; Mon, 5 Feb 2007 22:05:25 +0000 (UTC) (envelope-from neil@mpfspromotions.com) Received: (qmail 81248 invoked from network); 5 Feb 2007 22:05:23 -0000 Received: from svr1.16o.com (69.50.175.34) by svr2.16o.com with SMTP; 5 Feb 2007 22:05:23 -0000 Received: (qmail 10780 invoked from network); 5 Feb 2007 22:05:30 -0000 Received: from i-195-137-35-72.freedom2surf.net (HELO NEILPC) (195.137.35.72) by 0 with SMTP; 5 Feb 2007 22:05:30 -0000 From: "Neil Doody" To: Date: Mon, 5 Feb 2007 22:08:33 -0000 Message-ID: <04d601c74972$37e5b990$a7b12cb0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcdIrSPaEjfz9wueRCW0m6V/6uw1eg== Content-Language: en-gb x-cr-hashedpuzzle: ALN7 ANmM Cm3N DxL6 EBLo Ec6B G+Vh H48/ H76J Iyrz JAgA JOdW JvgI J3/Q KPgL LlBq; 1; YQBtAGQANgA0AEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {D054E693-E5E3-4FF4-8165-DE81008E2C98}; bgBlAGkAbABAAG0AcABmAHMAcAByAG8AbQBvAHQAaQBvAG4AcwAuAGMAbwBtAA==; Sun, 04 Feb 2007 22:38:07 GMT; SQBuAHMAcABlAGMAdABpAG4AZwAgAHAAcgBvAGMAZQBzAHMAZQBzAA== x-cr-puzzleid: {D054E693-E5E3-4FF4-8165-DE81008E2C98} Cc: Subject: Inspecting processes 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, 05 Feb 2007 22:05:33 -0000 I am having a problem in which apache processes are slowly going off on = some sort of rampage and I cant trace what is causing it.=A0 Basically over = time httpd processes start hogging 100% cpu and new processes are spawned, = until the apache server is shutdown these remain at 100% and they increase = until they bring the server down. I was wondering what tools I can use to see exactly what these processes = are doing, why they are stuck and what are they waiting for? I am running 6.2-STABLE FreeBSD 6.2-STABLE #5 it is on the AMD64 = platform. P.S. Sorry if this gets posted twice, I didnt appear to work the first time! From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 08:26:34 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3653316A405 for ; Tue, 6 Feb 2007 08:26:34 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id E666113C4B2 for ; Tue, 6 Feb 2007 08:26:33 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.66) for freebsd-amd64@freebsd.org with esmtp (envelope-from ) id <1HELQ4-00014P-TD>; Tue, 06 Feb 2007 09:11:16 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.66) for freebsd-amd64@freebsd.org with esmtpsa (envelope-from ) id <1HELQ4-0000og-Rr>; Tue, 06 Feb 2007 09:11:16 +0100 Message-ID: <45C83821.9090805@zedat.fu-berlin.de> Date: Tue, 06 Feb 2007 09:11:13 +0100 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Subject: amd64/105187 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, 06 Feb 2007 08:26:34 -0000 Hello. I made the above mentioned PR. Due to I'm building very often a week world on amd64, I do not further recognize the in the PR mentioned problems. I would appreciate closing this PR, so we can get rid of one. Oliver From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 08:37:44 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BDB616A401; Tue, 6 Feb 2007 08:37:44 +0000 (UTC) (envelope-from jkoshy@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 10EB113C478; Tue, 6 Feb 2007 08:37:44 +0000 (UTC) (envelope-from jkoshy@FreeBSD.org) Received: from freefall.freebsd.org (jkoshy@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l168bh7c027929; Tue, 6 Feb 2007 08:37:43 GMT (envelope-from jkoshy@freefall.freebsd.org) Received: (from jkoshy@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l168bhNi027925; Tue, 6 Feb 2007 08:37:43 GMT (envelope-from jkoshy) Date: Tue, 6 Feb 2007 08:37:43 GMT From: Joseph Koshy Message-Id: <200702060837.l168bhNi027925@freefall.freebsd.org> To: ohartman@zedat.fu-berlin.de, jkoshy@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/105187: make -j2 buildworld renders FreeBSD 6.2-PRE/AMD64 unusuable 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, 06 Feb 2007 08:37:44 -0000 Synopsis: make -j2 buildworld renders FreeBSD 6.2-PRE/AMD64 unusuable State-Changed-From-To: open->closed State-Changed-By: jkoshy State-Changed-When: Tue Feb 6 08:34:32 UTC 2007 State-Changed-Why: In Message-ID <45C83821.9090805@zedat.fu-berlin.de> sent to freebsd-amd64@, the submitter states that problem is no longer present. http://www.freebsd.org/cgi/query-pr.cgi?pr=105187 From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 17:00:36 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEA5716A408 for ; Tue, 6 Feb 2007 17:00:36 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 75C9D13C474 for ; Tue, 6 Feb 2007 17:00:36 +0000 (UTC) (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 l16H0aHq069014 for ; Tue, 6 Feb 2007 17: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 l16H0ao0069013; Tue, 6 Feb 2007 17:00:36 GMT (envelope-from gnats) Resent-Date: Tue, 6 Feb 2007 17:00:36 GMT Resent-Message-Id: <200702061700.l16H0ao0069013@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, Derek Tattersall Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC91E16A401 for ; Tue, 6 Feb 2007 16:52:00 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id DDF2C13C4AA for ; Tue, 6 Feb 2007 16:52:00 +0000 (UTC) (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 l16Gq0OF097336 for ; Tue, 6 Feb 2007 16:52:00 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l16Gq0TU097335; Tue, 6 Feb 2007 16:52:00 GMT (envelope-from nobody) Message-Id: <200702061652.l16Gq0TU097335@www.freebsd.org> Date: Tue, 6 Feb 2007 16:52:00 GMT From: Derek Tattersall To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/108841: Zdump prints bad information and hangs 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, 06 Feb 2007 17:00:36 -0000 >Number: 108841 >Category: amd64 >Synopsis: Zdump prints bad information and hangs >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 06 17:00:35 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Derek Tattersall >Release: 7.0-current >Organization: >Environment: FreeBSD nebbish.arm.org 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Feb 2 13:23:47 EST 2007 root@nebbish.arm.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: zdump -v EST5EDT prints 4 records as follows: [dlt@nebbish 536 zdump]$ zdump -v EST5EDT EST5EDT Sun Jan 26 08:29:52 -219 UTC = Sun Jan 26 03:29:52 -219 EST isdst=0 gmtoff=-18000 EST5EDT Mon Jan 27 08:29:52 -219 UTC = Mon Jan 27 03:29:52 -219 EST isdst=0 gmtoff=-18000 EST5EDT Fri Jan 1 04:59:59 -219 UTC = Thu Dec 30 23:59:59 -219 EST isdst=0 gmtoff=-18000 EST5EDT Fri Jan 1 05:00:00 -219 UTC = Fri Jan 1 00:00:00 -219 EST isdst=0 gmtoff=-18000 Then hangs. Can be killed by ctrl-c. I found that the localtime() call in show() returns incorrect information in at least the year field. >How-To-Repeat: execute from a command prompt "zdump -v EST5EDT" >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 17:10:00 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F3E216A402; Tue, 6 Feb 2007 17:10:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id C625713C4B6; Tue, 6 Feb 2007 17:09:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l16H9wIJ040165; Tue, 6 Feb 2007 12:09:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id l16H9wmI096781; Tue, 6 Feb 2007 12:09:58 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 607A873034; Tue, 6 Feb 2007 12:09:58 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070206170958.607A873034@freebsd-current.sentex.ca> Date: Tue, 6 Feb 2007 12:09:58 -0500 (EST) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner3 X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 17:10:00 -0000 TB --- 2007-02-06 15:30:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-02-06 15:30:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-02-06 15:30:00 - cleaning the object tree TB --- 2007-02-06 15:30:52 - checking out the source tree TB --- 2007-02-06 15:30:52 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-02-06 15:30:52 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-02-06 15:41:55 - building world (CFLAGS=-O2 -pipe) TB --- 2007-02-06 15:41:55 - cd /src TB --- 2007-02-06 15:41:55 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 6 15:41:57 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Tue Feb 6 16:59:01 UTC 2007 TB --- 2007-02-06 16:59:01 - generating LINT kernel config TB --- 2007-02-06 16:59:01 - cd /src/sys/amd64/conf TB --- 2007-02-06 16:59:01 - /usr/bin/make -B LINT TB --- 2007-02-06 16:59:01 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-02-06 16:59:01 - cd /src TB --- 2007-02-06 16:59:01 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Feb 6 16:59:01 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_bsdextended/mac_bsdextended.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_ifoff/mac_ifoff.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_lomac/mac_lomac.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_mls/mac_mls.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_none/mac_none.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/security/mac_partition/mac_partition.c /src/sys/security/mac_partition/mac_partition.c: In function `mac_partition_externalize_label': /src/sys/security/mac_partition/mac_partition.c:122: warning: int format, different type arg (arg 3) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-02-06 17:09:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-02-06 17:09:58 - ERROR: failed to build lint kernel TB --- 2007-02-06 17:09:58 - tinderbox aborted TB --- 0.98 user 3.39 system 5997.59 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 21:20:22 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D07FB16A40B for ; Tue, 6 Feb 2007 21:20:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B188113C481 for ; Tue, 6 Feb 2007 21:20:21 +0000 (UTC) (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 l16LKL2Q090453 for ; Tue, 6 Feb 2007 21:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l16LKLpP090452; Tue, 6 Feb 2007 21:20:21 GMT (envelope-from gnats) Resent-Date: Tue, 6 Feb 2007 21:20:21 GMT Resent-Message-Id: <200702062120.l16LKLpP090452@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, "Ruslan A. Afanasiev" Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4BB916A401 for ; Tue, 6 Feb 2007 21:17:48 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id 8E72013C467 for ; Tue, 6 Feb 2007 21:17:48 +0000 (UTC) (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 l16LHmp6056880 for ; Tue, 6 Feb 2007 21:17:48 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l16LHmhC056879; Tue, 6 Feb 2007 21:17:48 GMT (envelope-from nobody) Message-Id: <200702062117.l16LHmhC056879@www.freebsd.org> Date: Tue, 6 Feb 2007 21:17:48 GMT From: "Ruslan A. Afanasiev" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/108848: Motherboard MSI K9NGM-L 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, 06 Feb 2007 21:20:22 -0000 >Number: 108848 >Category: amd64 >Synopsis: Motherboard MSI K9NGM-L >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 06 21:20:21 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Ruslan A. Afanasiev >Release: FreeBSD 6.2-RELEASE #3 >Organization: Indigo >Environment: FreeBSD indigo-odessa 6.2-RELEASE FreeBSD 6.2-RELEASE #3: Tue Feb 6 18:21:50 UTC 2007 root@indigo-odessa:/usr/src/sys/i386/compile/ROUTER i386 >Description: Today has established system FreeBSD 6.2-RELEASE #3 on motherboard by MSI MSI K9NGM-L with CPU(AM2) - AMD Sempron(tm) Processor 2800+. The LAN and SATA - works perfectly. The sound card - was not tested. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 6 23:53:08 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA6E716A407 for ; Tue, 6 Feb 2007 23:53:08 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34510.mail.mud.yahoo.com (web34510.mail.mud.yahoo.com [66.163.178.176]) by mx1.freebsd.org (Postfix) with SMTP id 7774413C4A5 for ; Tue, 6 Feb 2007 23:53:08 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 11609 invoked by uid 60001); 6 Feb 2007 23:26:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ZO0lvYfU8lx2rBgcD+zTK8rOfn3Q+a2+TLdWv99UwzxpbWHfT8sIGY1a602zFDek9xnPUSmiGqJmv10sNZ8m+RDtUil1vs47S1q3M2b0UrHeopAzmOFbZ/ZAMwcvEhTBfu6p73MQj7O2LWMXNsxK6NLhZquUB5YePapujs+Rq6s=; X-YMail-OSG: 9H9L8LcVM1n3G1X4v_Cx4J5sW5B568hRuUcK8CK6ql1vDDGbtYgvMjTvX08CJpqKlEF0idQNMDbaknZ96cuxR4L.rzPwYc47EHAn5ycsa4EpDxXRdTfLz8DPDjao73HzPhfvuHx3B_ZphwiM20Ox0xqBnvnUGnZSudXr88VuXmgjMG8XRAqUcliVhGgKa63.USg- Received: from [67.112.21.26] by web34510.mail.mud.yahoo.com via HTTP; Tue, 06 Feb 2007 15:26:27 PST Date: Tue, 6 Feb 2007 15:26:27 -0800 (PST) From: "N. Harrington" To: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <932351.10276.qm@web34510.mail.mud.yahoo.com> Cc: Subject: Problem with Serverworks HT1000 serial ATA support - Tyan S3992 Motherboard 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, 06 Feb 2007 23:53:08 -0000 Hello I am testing out a new tyan motherboard that uses the next generation of AMD chips and the Serverworks Chipset. It seems that I can reliably crash it with a simple bonnie++ test if I set: /boot/loader.conf - Used for DiskD for Squid kern.ipc.msgtql=2048 I am using FreeBSD 6.1-STABLE amd64. This all works just fine on a non Serverworks Chipset Tyan Board. (literaly I unplug the drive and move it to another system and it works and works in production) If I run: bonnie++ -d /home -u root s1g The system reboots. I have tried this is both S-ATA and P-ATA emulation. Any ideas on why this setting, which works on non Serverworks boards, would make the Serverworks so twitchy? Thanks Nicole atapci0: port 0xb080-0xb087,0xb000-0xb003,0xac00-0xac07 ,0xa880-0xa883,0xa800-0xa81f mem 0xff4fe000-0xff4fffff irq 11 at device 14.0 on pci1 S-ATA: ad4: 70911MB at ata2-master SATA150 OR P-ATA: ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 70911MB at ata2-master UDMA33 /boot/loader.conf kern.ipc.msgtql=2048 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 03:20:20 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3569B16A40F for ; Wed, 7 Feb 2007 03:20:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B5D2213C4B5 for ; Wed, 7 Feb 2007 03:20:18 +0000 (UTC) (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 l173KI8c014954 for ; Wed, 7 Feb 2007 03:20:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l173KIOT014953; Wed, 7 Feb 2007 03:20:18 GMT (envelope-from gnats) Resent-Date: Wed, 7 Feb 2007 03:20:18 GMT Resent-Message-Id: <200702070320.l173KIOT014953@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, Lawrence Stewart Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC82216A400 for ; Wed, 7 Feb 2007 03:15:30 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id CC63113C441 for ; Wed, 7 Feb 2007 03:15:30 +0000 (UTC) (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 l173FUjS007730 for ; Wed, 7 Feb 2007 03:15:30 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l173FUhi007729; Wed, 7 Feb 2007 03:15:30 GMT (envelope-from nobody) Message-Id: <200702070315.l173FUhi007729@www.freebsd.org> Date: Wed, 7 Feb 2007 03:15:30 GMT From: Lawrence Stewart To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC 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: Wed, 07 Feb 2007 03:20:20 -0000 >Number: 108861 >Category: amd64 >Synopsis: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 07 03:20:18 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Lawrence Stewart >Release: 6.2 >Organization: Swinburne University >Environment: raidserv2# uname -a FreeBSD raidserv2.caia.swin.edu.au 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Wed Feb 7 11:30:15 EST 2007 root@raidserv2.caia.swin.edu.au:/usr/src/sys/amd64/compile/GENERIC+SMP amd64 >Description: The research centre I work at recently purchased a new file server, built from commodity hardware that FreeBSD claimed to have support for. Motherboard is an Asus A8N-E Rev 2.00 (listed as supported here: http://www.freebsd.org/platforms/amd64/motherboards.html). I clean installed FreeBSD 6.2 from ISO 6.2-RELEASE-amd64-disc1.iso. The onboard nVidia nForce4 nve(4) based NIC was plugged into the university's Cisco based gigabit ethernet LAN via CAT5e straight-through patch lead. An Intel 82540EM em(4) based PCI NIC was also installed in the server, but was not plugged into a network point (we previously tried installing FreeBSD 6.1 which had no support for the onboard NIC, so we put the Intel card in to use. We left it in for the new test with FreeBSD 6.2). The install completed successfully. We didn't configure either NIC during install at all (well... that's not entriely true the first time through... but I'll save the details of that crazy story for later as it will confuse things for the moment). After reboot, we bought the NIC up using "ifconfig nve0 up" and it synced at 1000baseTX full-duplex. Tcpdumping on the interface shows no activity at all (even though the uni network is VERY chatty, multiple packets per second should have been showing). Running "dhclient nve0" shows outbound DHCP requests, but not any return packets. Forcibly syncing the interface to 1000baseTX using "ifconfig nve0 media 1000baseTX mediaopt full-duplex" resulted in same behaviour i.e. doesn't "see" inbound packets. Forcibly syncing the interface to 100baseTX all of a sudden shows packets being received in tcpdump, and we can use the interface, though it only achieves about 80kb/sec on transfers i.e. is severely restricted for some reason. Intrigued, I installed a small 5 port 100baseTX switch between the server and network port and set the interface back to autoselect using "ifconfig nve0 media autoselect". The nve(4) interface synced at 100baseTX, and could then transfer at full 100Mbps speed (scp @ 11MB/sec from another local computer). I tried resolving the issue by setting "hw.pci.enable_msi=0" and "hw.pci.enable_msix=0" in /boot/loader.conf as suggested for fixing em(4) related problems. It had no effect from what I could see. I also tried rebuilding and installing a GENERIC kernel, GENERIC kernel without nve driver and kldloading it after startup, GENERIC+SMP kernel... none of the different kernel configs seemd to change anything. I also might add that I tried getting the em(4) Intel NIC working when I realised the nve(4) NIC was going to be a pain, and I had no luck, even with the disabling of MSI in /boot/loader.conf. I didn't try any harder than that though because my main focus was seeing if the nve driver was fixed. >How-To-Repeat: Patch the onboard ethernet NIC on an Asus A8N-E Rev 2.00 motherboard into a 1GBps switch port. Install FreeBSD 6.2 from ISO 6.2-RELEASE-amd64-disc1.iso. Configure the NIC to autoselect it's sync speed using "ifconfig nve0 media autoselect". Bring the NIC up using "ifconfig nve0 up" It should sync at 1000baseTX full-duplex, but not be able to communicate at all via the interface. >Fix: I could not find a fix for the problem. I also could not figure out why explicitly setting the NIC to sync at 100baseTX full-duplex made the NIC work, but only at a fraction of 100Mbps capacity. A work around is to cause the switch port the NIC is plugged into to only allow 100baseTX, so that the NIC will autoselect at 100baseTX and work at reasonable speed. You could also do as I did and stick small 100baseTX switch in between the machine and gigabit switch. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 04:30:35 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9AD1F16A401 for ; Wed, 7 Feb 2007 04:30:34 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4B8C713C474 for ; Wed, 7 Feb 2007 04:30:34 +0000 (UTC) (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 l174UYYU020290 for ; Wed, 7 Feb 2007 04:30:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l174UYhn020289; Wed, 7 Feb 2007 04:30:34 GMT (envelope-from gnats) Date: Wed, 7 Feb 2007 04:30:34 GMT Message-Id: <200702070430.l174UYhn020289@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Cy Schubert Cc: Subject: Re: amd64/108848: Motherboard MSI K9NGM-L X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Cy Schubert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 04:30:35 -0000 The following reply was made to PR amd64/108848; it has been noted by GNATS. From: Cy Schubert To: "Ruslan A. Afanasiev" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/108848: Motherboard MSI K9NGM-L Date: Tue, 06 Feb 2007 19:51:14 -0800 In message <200702062117.l16LHmhC056879@www.freebsd.org>, "Ruslan A. Afanasiev" writes: > > >Number: 108848 > >Category: amd64 > >Synopsis: Motherboard MSI K9NGM-L > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Feb 06 21:20:21 GMT 2007 > >Closed-Date: > >Last-Modified: > >Originator: Ruslan A. Afanasiev > >Release: FreeBSD 6.2-RELEASE #3 > >Organization: > Indigo > >Environment: > FreeBSD indigo-odessa 6.2-RELEASE FreeBSD 6.2-RELEASE #3: Tue Feb 6 18:21:50 > UTC 2007 root@indigo-odessa:/usr/src/sys/i386/compile/ROUTER i386 > > >Description: > Today has established system FreeBSD 6.2-RELEASE #3 on motherboard by MSI MSI > K9NGM-L with CPU(AM2) - AMD Sempron(tm) Processor 2800+. The LAN and SATA - > works perfectly. The sound card - was not tested. > >How-To-Repeat: > > >Fix: > > >Release-Note: > >Audit-Trail: > >Unformatted: I have a similar board in my testbed, K9VGM-V, Semron 3000+. Sound is supposed to work under 7.0-CURRENT. I've yet to test it though, too much other stuff on my plate. You might want to try 7.0. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 15:20:25 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D286516A400 for ; Wed, 7 Feb 2007 15:20:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE0813C474 for ; Wed, 7 Feb 2007 15:20:25 +0000 (UTC) (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 l17FKPcw076907 for ; Wed, 7 Feb 2007 15:20:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l17FKPuZ076906; Wed, 7 Feb 2007 15:20:25 GMT (envelope-from gnats) Date: Wed, 7 Feb 2007 15:20:25 GMT Message-Id: <200702071520.l17FKPuZ076906@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Angelo Turetta" Cc: Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Angelo Turetta List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 15:20:25 -0000 The following reply was made to PR amd64/108861; it has been noted by GNATS. From: "Angelo Turetta" To: lstewart@room52.net Cc: bug-followup@FreeBSD.org Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Wed, 7 Feb 2007 15:43:52 +0100 (CET) Could you please test the alternative driver mentioned at http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html It's already been commited to -current, and I'd certainly hope it will be MFC to 6-STABLE soon. Angelo Turetta From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 15:20:35 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4920F16A401 for ; Wed, 7 Feb 2007 15:20:35 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id E5F3113C4B9 for ; Wed, 7 Feb 2007 15:20:34 +0000 (UTC) (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 l17FKYFR076953 for ; Wed, 7 Feb 2007 15:20:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l17FKYY0076952; Wed, 7 Feb 2007 15:20:34 GMT (envelope-from gnats) Date: Wed, 7 Feb 2007 15:20:34 GMT Message-Id: <200702071520.l17FKYY0076952@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Angelo Turetta" Cc: Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Angelo Turetta List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 15:20:35 -0000 The following reply was made to PR amd64/108861; it has been noted by GNATS. From: "Angelo Turetta" To: lstewart@room52.net Cc: bug-followup@FreeBSD.org Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Wed, 7 Feb 2007 15:43:58 +0100 (CET) Could you please test the alternative driver mentioned at http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html It's already been commited to -current, and I'd certainly hope it will be MFC to 6-STABLE soon. Angelo Turetta From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 18:47:31 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A213616A401 for ; Wed, 7 Feb 2007 18:47:31 +0000 (UTC) (envelope-from ecrit-bounces@ietf.org) Received: from megatron.ietf.org (optimus.ietf.ORG [156.154.16.145]) by mx1.freebsd.org (Postfix) with ESMTP id 80EB813C494 for ; Wed, 7 Feb 2007 18:47:31 +0000 (UTC) (envelope-from ecrit-bounces@ietf.org) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HErYu-0003fh-Tr for freebsd-amd64@freebsd.org; Wed, 07 Feb 2007 13:30:32 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: ecrit-bounces@ietf.org To: freebsd-amd64@freebsd.org Message-ID: Date: Wed, 07 Feb 2007 13:30:31 -0500 Precedence: bulk X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.5 X-List-Administrivia: yes Errors-To: ecrit-bounces@ietf.org Subject: Your message to Ecrit awaits moderator approval X-BeenThere: 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: Wed, 07 Feb 2007 18:47:31 -0000 Your mail to 'Ecrit' with the subject TEST Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://www1.ietf.org/mailman/confirm/ecrit/c6df1d91ccf2f0d3fd44996df687f27714e5d557 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 23:01:18 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9BA416A400 for ; Wed, 7 Feb 2007 23:01:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id C9E8913C478 for ; Wed, 7 Feb 2007 23:01:18 +0000 (UTC) (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 l17N1IZo010629 for ; Wed, 7 Feb 2007 23:01:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l17N1IGa010628; Wed, 7 Feb 2007 23:01:18 GMT (envelope-from gnats) Date: Wed, 7 Feb 2007 23:01:18 GMT Message-Id: <200702072301.l17N1IGa010628@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Scot Hetzel" Cc: Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scot Hetzel List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 23:01:18 -0000 The following reply was made to PR amd64/108861; it has been noted by GNATS. From: "Scot Hetzel" To: "Lawrence Stewart" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Wed, 7 Feb 2007 16:58:36 -0600 On 2/6/07, Lawrence Stewart wrote: > I could not find a fix for the problem. > > I also could not figure out why explicitly setting the NIC to sync at 100baseTX full-duplex made the NIC work, but only at a fraction of 100Mbps capacity. > > A work around is to cause the switch port the NIC is plugged into to only allow 100baseTX, so that the NIC will autoselect at 100baseTX and work at reasonable speed. You could also do as I did and stick small 100baseTX switch in between the machine and gigabit switch. > Have you tried forcing the switch switch and the NIC to 1000baseT Full Duplex? Sometime times auto-negotiation fails, so forcing speed should fix it. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 23:04:28 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B5B816A403 for ; Wed, 7 Feb 2007 23:04:28 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34510.mail.mud.yahoo.com (web34510.mail.mud.yahoo.com [66.163.178.176]) by mx1.freebsd.org (Postfix) with SMTP id 4509013C4A7 for ; Wed, 7 Feb 2007 23:04:28 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 71946 invoked by uid 60001); 7 Feb 2007 23:04:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=SSP/QD6zREBeXU8GMNkw4ND4lvwW+5eb9/zKgGGDdtFH9Rk4zvdAfFzcawUAXWxGRCsBIRn5PPyQt1fBS4d68sYJRlCtbWA60IS2YU4V/FLkW1tzbs2YiDuZHATE/gstMqrf7lKBJ5ndVs2il9SQGoL0/o29rmQUMenfpe5EMvE=; X-YMail-OSG: .wtROqYVM1ltCxvYuWHC6Qam242pkhcfwgYJrPf4BlQal8byV7KFopssAuwhRiHs8gHgCe3ueD1QUSrNvRt8QwNxKB2FNo_Dj07lUr_V9GQ9bfZ299.026YkLWueFveXfA_NMFzBXEOBK6aNgMkoXAXgUegDzXZCmAeb5tEu4oteaJIQqsJTGKRg4.nW Received: from [67.112.21.26] by web34510.mail.mud.yahoo.com via HTTP; Wed, 07 Feb 2007 15:04:27 PST Date: Wed, 7 Feb 2007 15:04:27 -0800 (PST) From: Nicole Harrington To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <676973.69182.qm@web34510.mail.mud.yahoo.com> Cc: freebsd-amd64@freebsd.org Subject: Dual Core Or Dual CPU - What's the real difference in performance? 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: Wed, 07 Feb 2007 23:04:28 -0000 Hello all, I have been building/using servers that were dual CPU AMD Opteron systems for some time. (usually 246 Opteron cpu's) Now of course the world is shifting to Dual Core. Using FreeBSD, what is really the difference, besides power and ability to shove in more memory, between having the two seperate CPUS's? What if I did 2, Dual Core cpu's? Would the SMP overhead and sharing to a [Giant Locked] disk and or network erase any benefits? Thanks! Nicole The Large Print Giveth And The Small Print Taketh Away -- Anon From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 7 23:32:56 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23C2B16A400 for ; Wed, 7 Feb 2007 23:32:55 +0000 (UTC) (envelope-from ptroot@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by mx1.freebsd.org (Postfix) with ESMTP id C644A13C441 for ; Wed, 7 Feb 2007 23:32:54 +0000 (UTC) (envelope-from ptroot@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so361440nzh for ; Wed, 07 Feb 2007 15:32:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:subject:date:to:x-mailer:from; b=JAFPZLQW5GRNCD++VXuSasXqZWlwbzfAZGVA9Lko0OSMvJfWoO277HnnQ4/8QWBc8q5Mw2OuRkOp1VgL/xR14KtjUgkJTS4ga8PNNjm6wBeTxLl3yNMwtHQ+bMIJwcVeVjVAeM1kQ74ze898JyAcv8uXUBzrHlWCvTJEb59cF/I= Received: by 10.35.57.5 with SMTP id j5mr2476880pyk.1170889700379; Wed, 07 Feb 2007 15:08:20 -0800 (PST) Received: from ?192.168.0.2? ( [71.220.127.192]) by mx.google.com with ESMTP id 7sm6333940nzn.2007.02.07.15.08.19; Wed, 07 Feb 2007 15:08:19 -0800 (PST) In-Reply-To: <200702072301.l17N1IGa010628@freefall.freebsd.org> References: <200702072301.l17N1IGa010628@freefall.freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Date: Wed, 7 Feb 2007 17:08:52 -0600 To: Scot Hetzel X-Mailer: Apple Mail (2.752.2) From: Paul Root Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC 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: Wed, 07 Feb 2007 23:32:56 -0000 On Feb 7, 2007, at 11:01 PM, Scot Hetzel wrote: > The following reply was made to PR amd64/108861; it has been noted > by GNATS. > > From: "Scot Hetzel" > To: "Lawrence Stewart" > Cc: freebsd-gnats-submit@freebsd.org > Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does > not work at 1Gbps with nForce4 NIC > Date: Wed, 7 Feb 2007 16:58:36 -0600 > > On 2/6/07, Lawrence Stewart wrote: >> I could not find a fix for the problem. >> >> I also could not figure out why explicitly setting the NIC to sync >> at 100baseTX full-duplex made the NIC work, but only at a fraction >> of 100Mbps capacity. >> >> A work around is to cause the switch port the NIC is plugged into >> to only allow 100baseTX, so that the NIC will autoselect at >> 100baseTX and work at reasonable speed. You could also do as I did >> and stick small 100baseTX switch in between the machine and >> gigabit switch. >> > Have you tried forcing the switch switch and the NIC to 1000baseT > Full Duplex? > > Sometime times auto-negotiation fails, so forcing speed should fix > it. If you have a switch set to 100 Full and auto-negotiate for the host, the host will probably come up as 100 Half, and you'll get a bunch of collisions. On cisco switches, it can also cause the switch to turn the port down, requiring the admin to get it back up. If you set one side manually, set the other side, too. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 00:50:00 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2FC416A406 for ; Thu, 8 Feb 2007 00:49:59 +0000 (UTC) (envelope-from andrew.george.hammond@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 5F7C313C441 for ; Thu, 8 Feb 2007 00:49:59 +0000 (UTC) (envelope-from andrew.george.hammond@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so623678nfc for ; Wed, 07 Feb 2007 16:49:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kJqkHplAcAyCHJpss/C5OcJc4GZx24a1fyaTdyd3a8vzz7xolX2zauORypOhhvIUai351R/G0mEOhlS37fn0qcC8HxUrs1A2q0ZGal7oV/BtIalX3wWYqrSc4WVaaq+WQFZGK5aIFY35x0K58LK2n9UW/mu0jNFLihpNEts3dmQ= Received: by 10.82.153.5 with SMTP id a5mr664619bue.1170894119693; Wed, 07 Feb 2007 16:21:59 -0800 (PST) Received: by 10.49.57.17 with HTTP; Wed, 7 Feb 2007 16:21:59 -0800 (PST) Message-ID: <5a0a9d6f0702071621w3badaf54o2aca29c496b379f4@mail.gmail.com> Date: Wed, 7 Feb 2007 16:21:59 -0800 From: "Andrew Hammond" To: "Nicole Harrington" In-Reply-To: <676973.69182.qm@web34510.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <676973.69182.qm@web34510.mail.mud.yahoo.com> Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 08 Feb 2007 00:50:00 -0000 On 2/7/07, Nicole Harrington wrote: > Hello all, > I have been building/using servers that were dual CPU > AMD Opteron systems for some time. (usually 246 > Opteron cpu's) > > Now of course the world is shifting to Dual Core. > > Using FreeBSD, what is really the difference, besides > power and ability to shove in more memory, between > having the two seperate CPUS's? Well, you also have two additional HT buses for memory access. And one additional HT bus for peripheral access although most motherboard manufacturers don't actually do anything with it. > What if I did 2, Dual Core cpu's? Would the SMP > overhead and sharing to a [Giant Locked] disk and or > network erase any benefits? Benefits to what? Your computer can idle quite effectively with a 386 processor while consuming less power, producing less heat and requiring much less capital outlay than any Opteron box. Or did you have a workload in mind? If that's the case then you might want to tell us what it is, what analysis you've done on your current system to figure out where the bottleneck is, and what your performance goals for it are. Andrew From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 01:21:49 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12E7916A40F; Thu, 8 Feb 2007 01:21:48 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id D2AFB13C4AA; Thu, 8 Feb 2007 01:21:47 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l181Llvv080326; Wed, 7 Feb 2007 20:21:47 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id l181Lk1e084478; Wed, 7 Feb 2007 20:21:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A565473039; Wed, 7 Feb 2007 20:21:46 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070208012146.A565473039@freebsd-current.sentex.ca> Date: Wed, 7 Feb 2007 20:21:46 -0500 (EST) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 01:21:49 -0000 TB --- 2007-02-07 23:45:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-02-07 23:45:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-02-07 23:45:00 - cleaning the object tree TB --- 2007-02-07 23:45:51 - checking out the source tree TB --- 2007-02-07 23:45:51 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-02-07 23:45:51 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-02-07 23:57:00 - building world (CFLAGS=-O2 -pipe) TB --- 2007-02-07 23:57:00 - cd /src TB --- 2007-02-07 23:57:00 - /usr/bin/make -B buildworld >>> World build started on Wed Feb 7 23:57:01 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Feb 8 01:13:35 UTC 2007 TB --- 2007-02-08 01:13:35 - generating LINT kernel config TB --- 2007-02-08 01:13:35 - cd /src/sys/amd64/conf TB --- 2007-02-08 01:13:35 - /usr/bin/make -B LINT TB --- 2007-02-08 01:13:35 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-02-08 01:13:35 - cd /src TB --- 2007-02-08 01:13:35 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Feb 8 01:13:35 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/part/g_part.c awk -f /src/sys/tools/makeobjops.awk /src/sys/geom/part/g_part_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue g_part_if.c In file included from g_part_if.c:24: /src/sys/geom/geom.h: In function `g_free': /src/sys/geom/geom.h:307: warning: implicit declaration of function `KASSERT' /src/sys/geom/geom.h:307: warning: nested extern declaration of `KASSERT' /src/sys/geom/geom.h:309: warning: left-hand operand of comma expression has no effect /src/sys/geom/geom.h:309: warning: left-hand operand of comma expression has no effect *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-02-08 01:21:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-02-08 01:21:46 - ERROR: failed to build lint kernel TB --- 2007-02-08 01:21:46 - tinderbox aborted TB --- 0.86 user 3.51 system 5805.46 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 03:10:35 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA86016A402 for ; Thu, 8 Feb 2007 03:10:34 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3F08413C4A8 for ; Thu, 8 Feb 2007 03:10:34 +0000 (UTC) (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 l183AXlc031713 for ; Thu, 8 Feb 2007 03:10:33 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l183AXdg031710; Thu, 8 Feb 2007 03:10:33 GMT (envelope-from gnats) Date: Thu, 8 Feb 2007 03:10:33 GMT Message-Id: <200702080310.l183AXdg031710@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Lawrence Stewart Cc: Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lawrence Stewart List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 03:10:35 -0000 The following reply was made to PR amd64/108861; it has been noted by GNATS. From: Lawrence Stewart To: Angelo Turetta Cc: bug-followup@FreeBSD.org Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Thu, 08 Feb 2007 13:56:21 +1100 Hi Angelo, Thanks very much for the reply. Angelo Turetta wrote: > Could you please test the alternative driver mentioned at > > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > It's already been commited to -current, and I'd certainly hope it will be > MFC to 6-STABLE soon. > > Angelo Turetta > The new driver appears to be working perfectly. I'm running it through some basic stress tests now, but everything so far is all good. It can sync at both 100baseTX and 1000baseTX. When in 100baseTX mode, I can get 11.1 Mb/sec over scp. When in 1000baseTX I can get 24 MB/sec over scp. This was only transferring from a low spec desktop machine, so I think the machine's disk drive was the bottleneck, not the NIC. For the benefit of anyone else that comes across this thread and wants to know how to get the new driver working, here are the steps I followed (lines beginning with a hyphen "-" are comments, not actual shell commands): cd /root fetch http://www.se.hiroshima-u.ac.jp/~shigeaki/software/nfe-20070106.tar.gz - You may need a different patch to the one below depending on the motherboard you have... this patch is the right one for my Asus A8N-E, but all the details are on the patch website http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html fetch http://www.se.hiroshima-u.ac.jp/~shigeaki/software/e1000phy.20061219.fbsd62.patch tar -xzvf nfe-20070106.tar.gz cp -r nfe-20070106 /usr/src/sys/dev/nfe cp e1000phy.20061219.fbsd62.patch /usr/src/sys/dev/mii/ cd /usr/src/sys/dev/mii/ patch < e1000phy.20061219.fbsd62.patch cd /usr/src/sys/amd64/conf/ - Not sure that you need to do the next step, but I thought it would be safer to remove the nve(4) driver from the kernel so it didn't get confused... you can still kldload it later if needed edit GENERIC - Comment out the line "device nve # nVidia nForce MCP on-board Ethernet Networking" rm -rf ../compile/GENERIC config GENERIC cd ../compile/GENERIC make cleandepend && make depend && make && make install cd /usr/src/sys/dev/nfe make make install shutdown -r now - You should now have if_nve.ko in /boot/kernel/ and you can kldload it using "kldload if_nfe" or load it at startup by sticking if_nfe_load="YES" in /boot/loader.conf. - Good times from here on in! Thanks again for the help. Regards, Lawrence Stewart From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 05:07:13 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D83F916A403; Thu, 8 Feb 2007 05:07:11 +0000 (UTC) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.freebsd.org (Postfix) with ESMTP id AD66013C478; Thu, 8 Feb 2007 05:07:11 +0000 (UTC) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 2307D4CCF7; Thu, 8 Feb 2007 04:49:30 +0000 (GMT) Received: from smitch7.jumbuck.com (unknown [206.112.99.82]) by p4.roq.com (Postfix) with ESMTP id ED29E4C666; Thu, 8 Feb 2007 04:49:29 +0000 (GMT) Received: from smitch7.jumbuck.com (mail.jumbuck.com [206.112.99.82]) by smitch7.jumbuck.com (Postfix) with ESMTP id 5939C4111CB; Thu, 8 Feb 2007 04:46:02 +0000 (UTC) Received: from beaste5.jumbuck.com (melbourne.jumbuck.com [150.101.166.27]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smitch7.jumbuck.com (Postfix) with ESMTP id 08769410EA7; Thu, 8 Feb 2007 04:46:02 +0000 (UTC) Received: from beaste5.jumbuck.com (beast5 [192.168.46.105]) by beaste5.jumbuck.com (Postfix) with ESMTP id 87B20209D1A9; Thu, 8 Feb 2007 15:45:59 +1100 (EST) Received: from [192.168.46.102] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by beaste5.jumbuck.com (Postfix) with ESMTP id 61F5A209D195; Thu, 8 Feb 2007 15:45:59 +1100 (EST) Message-ID: <45CAAB06.40907@thebeastie.org> Date: Thu, 08 Feb 2007 15:45:58 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.13) Gecko/20060727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nicole Harrington References: <676973.69182.qm@web34510.mail.mud.yahoo.com> In-Reply-To: <676973.69182.qm@web34510.mail.mud.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 08 Feb 2007 05:07:14 -0000 Nicole Harrington wrote: > Hello all, > I have been building/using servers that were dual CPU >AMD Opteron systems for some time. (usually 246 >Opteron cpu's) > > Now of course the world is shifting to Dual Core. > > Using FreeBSD, what is really the difference, besides >power and ability to shove in more memory, between >having the two seperate CPUS's? > > What if I did 2, Dual Core cpu's? Would the SMP >overhead and sharing to a [Giant Locked] disk and or >network erase any benefits? > > Thanks! > > Nicole > > Dual core or Quad Core CPUs performance are far better compared to more socket CPUs since they get shared access to memory cache and reduce memory latency/probing over AMDs hypertransport bus. Anandtech did a pretty good review of AMD 4x4 system which compares 2 AMD dual cores with a single Intel Quad chip, where the Intel chip clearly outperforms consistantly because of this fact. Even when taking Intel out of the equation the benchmarks consistantly show even better performance with less sockets for AMD. http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2879&p=6 There appears to be no advantage to having seperate CPU socket systems what so ever. And yes the power usage is also bad, even though this example is a quad setup the fact still carriers over to Dual vs 2 socket CPUs. http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2879&p=13 Here we have a Quad AMD setup using a whopping 456watts over Intels Quad 263watt system. Thats a performance per watt difference of 73% if you even choose to see the AMD quad multisocket CPU performance as the same as Intels. Mike From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 05:20:23 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16A9516A401 for ; Thu, 8 Feb 2007 05:20:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 041E413C478 for ; Thu, 8 Feb 2007 05:20:20 +0000 (UTC) (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 l185KJDq043923 for ; Thu, 8 Feb 2007 05:20:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l185KJVR043922; Thu, 8 Feb 2007 05:20:19 GMT (envelope-from gnats) Date: Thu, 8 Feb 2007 05:20:19 GMT Message-Id: <200702080520.l185KJVR043922@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Lawrence Stewart Cc: Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lawrence Stewart List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 05:20:23 -0000 The following reply was made to PR amd64/108861; it has been noted by GNATS. From: Lawrence Stewart To: Scot Hetzel Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/108861: nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Thu, 08 Feb 2007 16:05:14 +1100 Hi Scot, Thanks for the reply. Scot Hetzel wrote: > On 2/6/07, Lawrence Stewart wrote: >> I could not find a fix for the problem. >> >> I also could not figure out why explicitly setting the NIC to sync at >> 100baseTX full-duplex made the NIC work, but only at a fraction of >> 100Mbps capacity. >> >> A work around is to cause the switch port the NIC is plugged into to >> only allow 100baseTX, so that the NIC will autoselect at 100baseTX >> and work at reasonable speed. You could also do as I did and stick >> small 100baseTX switch in between the machine and gigabit switch. >> > Have you tried forcing the switch switch and the NIC to 1000baseT Full > Duplex? > > Sometime times auto-negotiation fails, so forcing speed should fix it. > I don't have access to the actual Cisco switches, as they are maintained by our IT services department. Forcibly setting the switch to 1000 Mbps is kind of besides the point anyway. The problem is that when the NIC is autosensing (default state) and plugged into an autonegotiating 1 Gbps switch port (default for all switches I've ever worked with), the driver appears to be functional for all intensive purposes, except for the fact that no packets can be accessed. That is confusing for the user and is the major problem with the nve(4) driver in its current state. Having to put a call into the IT dept and trying to explain that you need them to manually set the sync speed on a port is unlikely to be well received... it's also simply another work around, rather than a fix. Regards, Lawrence Stewart From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 06:19:13 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97F0416A400 for ; Thu, 8 Feb 2007 06:19:13 +0000 (UTC) (envelope-from mwm-dated-1171778004.1a5f9b@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 3BD4113C46B for ; Thu, 8 Feb 2007 06:19:13 +0000 (UTC) (envelope-from mwm-dated-1171778004.1a5f9b@mired.org) Received: (qmail 80212 invoked by uid 1001); 8 Feb 2007 05:53:24 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 08 Feb 2007 00:53:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17866.47828.219523.71972@bhuda.mired.org> Date: Thu, 8 Feb 2007 00:53:24 -0500 To: Michael Vince In-Reply-To: <45CAAB06.40907@thebeastie.org> References: <676973.69182.qm@web34510.mail.mud.yahoo.com> <45CAAB06.40907@thebeastie.org> X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 08 Feb 2007 06:19:13 -0000 In <45CAAB06.40907@thebeastie.org>, Michael Vince typed: > Nicole Harrington wrote: > > Using FreeBSD, what is really the difference, besides > >power and ability to shove in more memory, between > >having the two seperate CPUS's? > Dual core or Quad Core CPUs performance are far better compared to more > socket CPUs since they get shared access to memory cache and reduce > memory latency/probing over AMDs hypertransport bus. Of course, it's not really that simple. For one thing, the intel quad core CPUS are two dual core chips in one package, and the two chips don't share internal resources - like cache. So any data in cache is only available to two of the four cpus; if the one of the other two cpus needs that data it'll have to go to the external bus. The AMD quad core package is similar - except they don't put the two chips in the same package, but provide a proprietary high-speed interconnect between them. Also, shared access to the memory cache means - well shared access to the memory cache and the memory behind it. Shared access raises the possibility of contention, which will slow things down. If all four CPUs get a cache miss for different data at the same time, one of them is in for a long wait. Yeah, this isn't very likely under most loads. How likely is it under yours? Generally, more processors means things will go faster until you run out of threads. However, if there's some shared resource that is the bottleneck for your load, and the resource doesn't support simultaneous access by all the cores, more cores can slow things down. Of course, it's not really that simple. Some shared resources can be managed so as to make things improve under most loads, even if they don't support simultaneous access. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 07:30:16 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2D8E16A401 for ; Thu, 8 Feb 2007 07:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B0A3F13C471 for ; Thu, 8 Feb 2007 07:30:15 +0000 (UTC) (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 l187UFqG053020 for ; Thu, 8 Feb 2007 07:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l187UFcf053019; Thu, 8 Feb 2007 07:30:15 GMT (envelope-from gnats) Resent-Date: Thu, 8 Feb 2007 07:30:15 GMT Resent-Message-Id: <200702080730.l187UFcf053019@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, Roman V Sopov Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDE9C16A402 for ; Thu, 8 Feb 2007 07:22:37 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id A627813C478 for ; Thu, 8 Feb 2007 07:22:37 +0000 (UTC) (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 l187Mb0q068010 for ; Thu, 8 Feb 2007 07:22:37 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l187MbZW068008; Thu, 8 Feb 2007 07:22:37 GMT (envelope-from nobody) Message-Id: <200702080722.l187MbZW068008@www.freebsd.org> Date: Thu, 8 Feb 2007 07:22:37 GMT From: Roman V Sopov To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/108920: LAN to ASUS M2N32 WS Professional 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, 08 Feb 2007 07:30:16 -0000 >Number: 108920 >Category: amd64 >Synopsis: LAN to ASUS M2N32 WS Professional >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 08 07:30:14 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Roman V Sopov >Release: 6.2 >Organization: >Environment: >Description: Не определяется сетевой адаптер на ASUS M2N32 WS Professional >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 09:33:05 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CBA8916A401 for ; Thu, 8 Feb 2007 09:33:01 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 4AE0813C48E for ; Thu, 8 Feb 2007 09:32:59 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l1894QJe001419; Thu, 8 Feb 2007 20:04:26 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l1894Quu001418; Thu, 8 Feb 2007 20:04:26 +1100 (EST) (envelope-from peter) Date: Thu, 8 Feb 2007 20:04:26 +1100 From: Peter Jeremy To: Neil Doody Message-ID: <20070208090426.GB844@turion.vk2pj.dyndns.org> References: <04d601c74972$37e5b990$a7b12cb0$@com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <04d601c74972$37e5b990$a7b12cb0$@com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: amd64@freebsd.org Subject: Re: Inspecting processes 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, 08 Feb 2007 09:33:05 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Feb-05 22:08:33 -0000, Neil Doody wrote: >I am having a problem in which apache processes are slowly going off on so= me >sort of rampage and I cant trace what is causing it.=A0 Basically over time >httpd processes start hogging 100% cpu and new processes are spawned, until >the apache server is shutdown these remain at 100% and they increase until >they bring the server down. > >I was wondering what tools I can use to see exactly what these processes a= re >doing, why they are stuck and what are they waiting for? Specifically for apache, you could try mod-status (/server-status) with "ExtendedStatus On". This should let you track down the the offending URL. General tools would be ktrace and friends to see what syscalls it is performing. You could also try attaching a debugger and getting a backtrace. This might give you some idea where to start looking. If this isn't a totally static website, my initial guess is that one of the CGI scripts is running amok. --=20 Peter Jeremy --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFyuea/opHv/APuIcRAqaEAJ0eGFw9DU9D/KLFAsbxMVh7+yC1ZwCgrKFb V0enMw+am2BT3gjOVGOVVeo= =r47V -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 15:37:24 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A89216A408 for ; Thu, 8 Feb 2007 15:37:24 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from spqr.komquats.com (S0106002078125c0c.gv.shawcable.net [24.108.150.192]) by mx1.freebsd.org (Postfix) with ESMTP id BE93413C441 for ; Thu, 8 Feb 2007 15:37:23 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by spqr.komquats.com (Postfix) with ESMTP id 9D4494C5C5; Thu, 8 Feb 2007 07:18:40 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.13.8/8.13.8) with ESMTP id l18FIeMR002991; Thu, 8 Feb 2007 07:18:40 -0800 (PST) (envelope-from Cy.Schubert@komquats.com) Message-Id: <200702081518.l18FIeMR002991@cwsys.cwsent.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org In-Reply-To: Message from Mike Meyer of "Thu, 08 Feb 2007 00:53:24 EST." <17866.47828.219523.71972@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Feb 2007 07:18:40 -0800 Sender: Cy.Schubert@komquats.com Cc: Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Cy Schubert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 15:37:24 -0000 In message <17866.47828.219523.71972@bhuda.mired.org>, Mike Meyer writes: > Generally, more processors means things will go faster until you run > out of threads. However, if there's some shared resource that is the > bottleneck for your load, and the resource doesn't support > simultaneous access by all the cores, more cores can slow things > down. > > Of course, it's not really that simple. Some shared resources can be > managed so as to make things improve under most loads, even if they > don't support simultaneous access. Generally speaking the performance increase is not linear. At some point there is no benefit to adding more processors. In a former life when I was an MVS systems programmer the limit was seven processors in a System/370. Today we can use 16, 32, even 64 processors with a standard operating system and current hardware, unless one of the massively parallel architectures is used. To answer the original posters question, there are architectural differences mentioned here, e.g. shared cache, I/O channel, etc., but the reason the chip manufacturers make them is that they're more cost effective than two CPUs. The AMD X2 series of chips (I have one), they're not truely a dual processor chip. They're analogous to the single processor System/370 with an AP (attached processor) in concept. What this means is that both processors can execute all instructions and are just as capable in every way except external interrupts, e.g. I/O interrupts, are handled by the processor 0 as only that processor is "wired" to be interrupted in case of external interrupt. I can't comment about Intel's Dual Core CPUs as I don't know their architecture but I'd suspect the same would be true. Chips in which there are two dual core CPUs on the same die, I believe one of each of the dual core CPUs can handle external interrupts. >From an operating system perspective an AP means that processor 0 will receive the interrupt and put it on it's queue. Then either processor 0 or processor 1 would take the interrupt off the queue and do something with it. To add another dimension to this discussion, hyperthreading uses spare cycles in a single processor to pretend there are two processors, increasing performance for some apps and reducing performance for other apps. For example Sun T2000 systems have multiple CPUs each with multiple cores and each core capable of hyperthreading, presenting to Solaris 32 processors where in fact there are only two CPU chips (I may have the numbers wrong as I spend most of my time in "management" mode at work and you know managers don't have brains). Generally speaking, dual core is an inexpensive way to get SMP into the hands of people who could not normally afford SMP technology as it was. I have a mortgage so spending money on computers is not a high priority in relation to that priority but dual core does give me an opportunity to enter the market relatively inexpensively and get good value for the money I spend on the technology. That's really what it's all about, how much performance you get for the money you spend. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 17:14:53 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F10F216A40A for ; Thu, 8 Feb 2007 17:14:52 +0000 (UTC) (envelope-from mwm-dated-1171817341.aee11a@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 0572113C48E for ; Thu, 8 Feb 2007 17:14:48 +0000 (UTC) (envelope-from mwm-dated-1171817341.aee11a@mired.org) Received: (qmail 89229 invoked by uid 1001); 8 Feb 2007 16:49:01 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 08 Feb 2007 11:49:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17867.21629.224092.189457@bhuda.mired.org> Date: Thu, 8 Feb 2007 11:49:01 -0500 To: Cy Schubert In-Reply-To: <200702081518.l18FIeMR002991@cwsys.cwsent.com> References: <17866.47828.219523.71972@bhuda.mired.org> <200702081518.l18FIeMR002991@cwsys.cwsent.com> X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 08 Feb 2007 17:14:53 -0000 In <200702081518.l18FIeMR002991@cwsys.cwsent.com>, Cy Schubert typed: > In message <17866.47828.219523.71972@bhuda.mired.org>, Mike Meyer writes: > > Generally, more processors means things will go faster until you run > > out of threads. However, if there's some shared resource that is the > > bottleneck for your load, and the resource doesn't support > > simultaneous access by all the cores, more cores can slow things > > down. > > > > Of course, it's not really that simple. Some shared resources can be > > managed so as to make things improve under most loads, even if they > > don't support simultaneous access. > > Generally speaking the performance increase is not linear. At some point > there is no benefit to adding more processors. When some other resources becomes the bottleneck. Which resource depends on the workload. In some cases, adding processors will slow things down. > To add another dimension to this discussion, hyperthreading uses spare > cycles in a single processor to pretend there are two processors, > increasing performance for some apps and reducing performance for other > apps. I think hyperthreading gets a bad rap. It shares lots of resources - like the computing units - so there are lots of workloads that cause things to get worse when you add a processor. But the general case should still be that it gets faster. > Generally speaking, dual core is an inexpensive way to get SMP into the > hands of people who could not normally afford SMP technology as it was. Gee, I thought it was a reaction to losing the clock rate war. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 8 17:46:14 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EDF016A403; Thu, 8 Feb 2007 17:46:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1916A13C4A7; Thu, 8 Feb 2007 17:46:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (jhb@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l18HkC7C097219; Thu, 8 Feb 2007 17:46:12 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l18HkCcR097215; Thu, 8 Feb 2007 17:46:12 GMT (envelope-from jhb) Date: Thu, 8 Feb 2007 17:46:12 GMT From: John Baldwin Message-Id: <200702081746.l18HkCcR097215@freefall.freebsd.org> To: ravi.murty@intel.com, jhb@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/108673: kgdb doesn't work very well very long 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, 08 Feb 2007 17:46:14 -0000 Synopsis: kgdb doesn't work very well very long State-Changed-From-To: patched->closed State-Changed-By: jhb State-Changed-When: Thu Feb 8 17:46:00 UTC 2007 State-Changed-Why: Fix merged to 6.x. http://www.freebsd.org/cgi/query-pr.cgi?pr=108673 From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 9 00:55:29 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 62AE316A403 for ; Fri, 9 Feb 2007 00:55:29 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34514.mail.mud.yahoo.com (web34514.mail.mud.yahoo.com [66.163.178.180]) by mx1.freebsd.org (Postfix) with SMTP id 3523913C4A5 for ; Fri, 9 Feb 2007 00:55:28 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 78132 invoked by uid 60001); 9 Feb 2007 00:55:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=cw0Mkioca7Z5ab5GrBx7yqOC8Z9otwrfu+h63vLjypi65GHdIps6LsV75gu5NnK9wy5fm+z+9gUSrp14U8pPdPKNp4+rtEw+eNo9Lx7v9hCdH07/jNvns+hGrBYp02tPK+1xElrFqIGioIOEJ4MSpYML+PC2Iq7mi2pN/bO8aFw=; X-YMail-OSG: J..rW7QVM1mMYEtm0dfA1YJFUuNnyViyWoVl_WRnoSJ9pfirllnedVGY6E1QyPl3VG6az9_G1ezagWtLkqKYGOk7Y_buSIqLGxZGp2RNk4k_Zej6WvDX05GQHk5K0dWw_WjIk4iUyARxJGLIbocnLVg5JvgZPJKtREySi29INAW6zh8OohTUVG1E0Mxt Received: from [67.112.21.26] by web34514.mail.mud.yahoo.com via HTTP; Thu, 08 Feb 2007 16:55:28 PST Date: Thu, 8 Feb 2007 16:55:28 -0800 (PST) From: Nicole Harrington To: Cy Schubert , freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org In-Reply-To: <200702081518.l18FIeMR002991@cwsys.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <142261.76672.qm@web34514.mail.mud.yahoo.com> Cc: Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 09 Feb 2007 00:55:29 -0000 --- Cy Schubert wrote: > In message > <17866.47828.219523.71972@bhuda.mired.org>, Mike > Meyer writes: > > Generally, more processors means things will go > faster until you run > > out of threads. However, if there's some shared > resource that is the > > bottleneck for your load, and the resource doesn't > support > > simultaneous access by all the cores, more cores > can slow things > > down. > > > > Of course, it's not really that simple. Some > shared resources can be > > managed so as to make things improve under most > loads, even if they > > don't support simultaneous access. > > Generally speaking the performance increase is not > linear. At some point > there is no benefit to adding more processors. In a > former life when I was > an MVS systems programmer the limit was seven > processors in a System/370. > Today we can use 16, 32, even 64 processors with a > standard operating > system and current hardware, unless one of the > massively parallel > architectures is used. > > To answer the original posters question, there are > architectural > differences mentioned here, e.g. shared cache, I/O > channel, etc., but the > reason the chip manufacturers make them is that > they're more cost effective > than two CPUs. > > The AMD X2 series of chips (I have one), they're not > truely a dual > processor chip. They're analogous to the single > processor System/370 with > an AP (attached processor) in concept. What this > means is that both > processors can execute all instructions and are just > as capable in every > way except external interrupts, e.g. I/O interrupts, > are handled by the > processor 0 as only that processor is "wired" to be > interrupted in case of > external interrupt. I can't comment about Intel's > Dual Core CPUs as I don't > know their architecture but I'd suspect the same > would be true. Chips in > which there are two dual core CPUs on the same die, > I believe one of each > of the dual core CPUs can handle external > interrupts. Wow I love ansking questions without too many specifics as I learn so much more. With this however it really seems to be a love hate relationship with dual core. Based on what you stated above, would that mean that when using a dual core system, using polling interupts might be better or perhaps monumanally worse? > I > have a mortgage so spending money on computers is > not a high priority in > relation to that priority but dual core does give me > an opportunity to > enter the market relatively inexpensively and get > good value for the money > I spend on the technology. That's really what it's > all about, how much > performance you get for the money you spend. > Tring to figure out the fud from reality is often the best way to make sure you really get the best value. However, it always seems to "depend" on many variables :) Thanks! Nicole > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: > http://www.FreeBSD.org > > e**(i*pi)+1=0 > > > _______________________________________________ > 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 Fri Feb 9 02:52:01 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C52F516A400; Fri, 9 Feb 2007 02:52:01 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from spqr.komquats.com (S0106002078125c0c.gv.shawcable.net [24.108.150.192]) by mx1.freebsd.org (Postfix) with ESMTP id 009BB13C428; Fri, 9 Feb 2007 02:51:58 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by spqr.komquats.com (Postfix) with ESMTP id 56E3B4C5C5; Thu, 8 Feb 2007 18:51:58 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.13.8/8.13.8) with ESMTP id l192pviU087983; Thu, 8 Feb 2007 18:51:57 -0800 (PST) (envelope-from Cy.Schubert@komquats.com) Message-Id: <200702090251.l192pviU087983@cwsys.cwsent.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Nicole Harrington In-Reply-To: Message from Nicole Harrington of "Thu, 08 Feb 2007 16:55:28 PST." <142261.76672.qm@web34514.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Feb 2007 18:51:57 -0800 Sender: Cy.Schubert@komquats.com Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Cy Schubert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 02:52:01 -0000 In message <142261.76672.qm@web34514.mail.mud.yahoo.com>, Nicole Harrington wri tes: > --- Cy Schubert wrote: > > In message > > <17866.47828.219523.71972@bhuda.mired.org>, Mike > > Meyer writes: > > > Generally, more processors means things will go > > faster until you run > > > out of threads. However, if there's some shared > > resource that is the > > > bottleneck for your load, and the resource doesn't > > support > > > simultaneous access by all the cores, more cores > > can slow things > > > down. > > > > > > Of course, it's not really that simple. Some > > shared resources can be > > > managed so as to make things improve under most > > loads, even if they > > > don't support simultaneous access. > > > > Generally speaking the performance increase is not > > linear. At some point > > there is no benefit to adding more processors. In a > > former life when I was > > an MVS systems programmer the limit was seven > > processors in a System/370. > > Today we can use 16, 32, even 64 processors with a > > standard operating > > system and current hardware, unless one of the > > massively parallel > > architectures is used. > > > > To answer the original posters question, there are > > architectural > > differences mentioned here, e.g. shared cache, I/O > > channel, etc., but the > > reason the chip manufacturers make them is that > > they're more cost effective > > than two CPUs. > > > > The AMD X2 series of chips (I have one), they're not > > truely a dual > > processor chip. They're analogous to the single > > processor System/370 with > > an AP (attached processor) in concept. What this > > means is that both > > processors can execute all instructions and are just > > as capable in every > > way except external interrupts, e.g. I/O interrupts, > > are handled by the > > processor 0 as only that processor is "wired" to be > > interrupted in case of > > external interrupt. I can't comment about Intel's > > Dual Core CPUs as I don't > > know their architecture but I'd suspect the same > > would be true. Chips in > > which there are two dual core CPUs on the same die, > > I believe one of each > > of the dual core CPUs can handle external > > interrupts. > > Wow I love ansking questions without too many > specifics as I learn so much more. With this however > it really seems to be a love hate relationship with > dual core. > > Based on what you stated above, would that mean that > when using a dual core system, using polling interupts > might be better or perhaps monumanally worse? No. CPU 0 would be interrupted. It would schedule the interrupt in the queue. Either CPU could service the interrupt once the interrupt was queued. Some devices need to be polled as they do not generate interrupts or they generate spurious interrupts. Otherwise allowing a device to interrupt the CPU is more efficient as it allows the CPU to do other work rather than spinning its wheels polling. This is the Von Neumann model. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 10 01:46:56 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B43116A407 for ; Sat, 10 Feb 2007 01:46:56 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34514.mail.mud.yahoo.com (web34514.mail.mud.yahoo.com [66.163.178.180]) by mx1.freebsd.org (Postfix) with SMTP id D3F7213C48D for ; Sat, 10 Feb 2007 01:46:55 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 91141 invoked by uid 60001); 10 Feb 2007 01:46:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=xkC6Z7GbmZgCWiYoPGAuc8c/AJYDtNuU4z6LuSRvpEZIQXnJ/lJag87v/6NarFhnIQ3+8yM0QjZRKsGxeWcTN13sZyfZJTu5fGG8ExGhrlAKZj5EZ6omr4R5h6ynmCQiF7DyThEUGlGrTk46qJ+xzsR5E8WD+zPUSbM0zXe3J2k=; X-YMail-OSG: kUvMSZwVM1lldlan1IBtv_iUqp5lhUcgd3b8TFM7CZkT5GcjRGFuZ_TmxAvdwty2PVukYlEjc4zOQmgYAuGOfCGJr5TMrn.jOmp1DLtpheKJrM8OIMVY6dJC0MKK77jGaI4vDZydddfrfhbfkY4eXw1vn8hruJQcsxvLLVaCRDER1CPnjGStdRTxAADh Received: from [67.112.21.26] by web34514.mail.mud.yahoo.com via HTTP; Fri, 09 Feb 2007 17:46:54 PST Date: Fri, 9 Feb 2007 17:46:54 -0800 (PST) From: Nicole Harrington To: Cy Schubert In-Reply-To: <200702090251.l192pviU087983@cwsys.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <935627.87795.qm@web34514.mail.mud.yahoo.com> Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Dual Core Or Dual CPU - What's the real difference in performance? 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, 10 Feb 2007 01:46:56 -0000 --- Cy Schubert wrote: > In message > <142261.76672.qm@web34514.mail.mud.yahoo.com>, > Nicole Harrington > wri > tes: > > --- Cy Schubert wrote: > > > In message > > > <17866.47828.219523.71972@bhuda.mired.org>, Mike > > > Meyer writes: > > > > Generally, more processors means things will > go > > > faster until you run > > > > out of threads. However, if there's some > shared > > > resource that is the > > > > bottleneck for your load, and the resource > doesn't > > > support > > > > simultaneous access by all the cores, more > cores > > > can slow things > > > > down. > > > > > > > > Of course, it's not really that simple. Some > > > shared resources can be > > > > managed so as to make things improve under > most > > > loads, even if they > > > > don't support simultaneous access. > > > > > > Generally speaking the performance increase is > not > > > linear. At some point > > > there is no benefit to adding more processors. > In a > > > former life when I was > > > an MVS systems programmer the limit was seven > > > processors in a System/370. > > > Today we can use 16, 32, even 64 processors with > a > > > standard operating > > > system and current hardware, unless one of the > > > massively parallel > > > architectures is used. > > > > > > To answer the original posters question, there > are > > > architectural > > > differences mentioned here, e.g. shared cache, > I/O > > > channel, etc., but the > > > reason the chip manufacturers make them is that > > > they're more cost effective > > > than two CPUs. > > > > > > The AMD X2 series of chips (I have one), they're > not > > > truely a dual > > > processor chip. They're analogous to the single > > > processor System/370 with > > > an AP (attached processor) in concept. What this > > > means is that both > > > processors can execute all instructions and are > just > > > as capable in every > > > way except external interrupts, e.g. I/O > interrupts, > > > are handled by the > > > processor 0 as only that processor is "wired" to > be > > > interrupted in case of > > > external interrupt. I can't comment about > Intel's > > > Dual Core CPUs as I don't > > > know their architecture but I'd suspect the same > > > would be true. Chips in > > > which there are two dual core CPUs on the same > die, > > > I believe one of each > > > of the dual core CPUs can handle external > > > interrupts. > > > > Wow I love ansking questions without too many > > specifics as I learn so much more. With this > however > > it really seems to be a love hate relationship > with > > dual core. > > > > Based on what you stated above, would that mean > that > > when using a dual core system, using polling > interupts > > might be better or perhaps monumanally worse? > > No. CPU 0 would be interrupted. It would schedule > the interrupt in the > queue. Either CPU could service the interrupt once > the interrupt was queued. > > Some devices need to be polled as they do not > generate interrupts or they > generate spurious interrupts. Otherwise allowing a > device to interrupt the > CPU is more efficient as it allows the CPU to do > other work rather than > spinning its wheels polling. This is the Von Neumann > model. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: > http://www.FreeBSD.org > > e**(i*pi)+1=0 > Yes, I have heard that, thanks. However, how does one know or tell which is the right mode/model for which devices? I have seen people on either side (poll vs interupt) claim one is better or much like an infomercial, just do blah and your system will be so much faster. Altho of course that would be the pro polling side, since by default, interupts are used. Is it all just imperical testing? Take this pill and see let me know how you feel? It seems as though when it's heavy networking, use polling. Otherwise stick with interupts. I have even heard when using X network card, use polling. How would know when one card will do better with polling while another may not? Thanks for helping me understand the debate better. Nicole --- If you make people think they're thinking, they'll love you; but if you really make them think, they'll hate you." -- Don Marquis From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 10 17:56:40 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E13A916A406; Sat, 10 Feb 2007 17:56:40 +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 82B7613C467; Sat, 10 Feb 2007 17:56:40 +0000 (UTC) (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 D0AFD1FFE76; Sat, 10 Feb 2007 18:35:18 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 1BCAA1FFED7; Sat, 10 Feb 2007 18:35:07 +0100 (CET) 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 5F8BA444CD8; Sat, 10 Feb 2007 17:33:57 +0000 (UTC) Date: Sat, 10 Feb 2007 17:33:57 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Sven Willenberger In-Reply-To: <1168211205.22629.6.camel@lanshark.dmv.com> Message-ID: <20070210170533.F47107@maildrop.int.zabbadoz.net> References: <1168211205.22629.6.camel@lanshark.dmv.com> 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: stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Panic in 6.2-PRERELEASE with bge on amd64 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, 10 Feb 2007 17:56:41 -0000 On Sun, 7 Jan 2007, Sven Willenberger wrote: > lock order reversal: (sleepable after non-sleepable) > 1st 0xffffffff8836b010 bge0 (network driver) @ /usr/src/sys/dev/bge/if_bge.c:2675 > 2nd 0xffffffff805f26b0 user map (user map) @ /usr/src/sys/vm/vm_map.c:3074 added with LOD ID 199 to The LOR page: http://sources.zabbadoz.net/freebsd/lor.html#199 I am unsure if this was patched already - if so please let me know. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT