From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 22 00:26:53 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDDD216A412 for ; Sun, 22 Oct 2006 00:26:53 +0000 (UTC) (envelope-from mureninc@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8FC343D5C for ; Sun, 22 Oct 2006 00:26:51 +0000 (GMT) (envelope-from mureninc@gmail.com) Received: by wx-out-0506.google.com with SMTP id t4so1302852wxc for ; Sat, 21 Oct 2006 17:26:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pQaBWVTuYhBxQ3cLu2HXKxas9UuA2qNESoyQSQLGCZCwZVL5xCSPO7hXbxcb+RbPAUe2mn5tNzlE4iW5tzwQx9bff4Pd715i+LVubgTaxpf1iZyiEtyD700/NliuYpbMMtnhLIJHhDgTXRzBZvgQJCFxk20CZoKyhkh+tqos8VA= Received: by 10.70.22.10 with SMTP id 10mr3854468wxv; Sat, 21 Oct 2006 17:26:50 -0700 (PDT) Received: by 10.70.36.16 with HTTP; Sat, 21 Oct 2006 17:26:50 -0700 (PDT) Message-ID: Date: Sat, 21 Oct 2006 20:26:50 -0400 From: "Constantine A. Murenin" To: "Alexey Bobok" In-Reply-To: <200610111545.20981.sj@ukrintell.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200610111545.20981.sj@ukrintell.net> Cc: freebsd-hardware@freebsd.org Subject: Re: Intell Wireless 3945 driver X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2006 00:26:53 -0000 On 11/10/06, Alexey Bobok wrote: > Hello. > I have bought a laptop Dell Latitude d820 with Intel Wireless Pro 3945 card. > I've tried to install /usr/ports/net/ipw-firmware and then > kldload -v if_ipw > ipwcontrol -i ipw0 -f /boot/firmware/ipw.fw > and get the error: > ipwcontrol: Can't load /boot/firmware/ipw.fw to driver: Device not configured > the problem is that I even don't see any messages about this device in dmesg. > is there any solution? ) thanks Hi Alexey, Intel Pro/Wireless 3945ABG is supported by wpi(4) only, see . damien@ develops ipw(4), iwi(4) and wpi(4), but unfortunately, he no longer works with FreeBSD and thus has no plans on porting wpi(4) to FreeBSD, see http://kerneltrap.org/node/6497. Cheers, Constantine. From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 23 16:00:31 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4ECC16A47B for ; Mon, 23 Oct 2006 16:00:31 +0000 (UTC) (envelope-from girgen@FreeBSD.org) Received: from melon.pingpong.net (melon.pingpong.net [195.178.174.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B2FB43DE9 for ; Mon, 23 Oct 2006 15:57:52 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 4E92F519F0 for ; Mon, 23 Oct 2006 17:57:33 +0200 (CEST) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 88231-01-20 for ; Mon, 23 Oct 2006 17:57:33 +0200 (CEST) Received: from [192.168.1.187] (unknown [213.136.40.204]) by melon.pingpong.net (Postfix) with ESMTP id E4557519E3 for ; Mon, 23 Oct 2006 17:57:32 +0200 (CEST) Date: Mon, 23 Oct 2006 17:57:32 +0200 From: Palle Girgensohn To: freebsd-hardware@freebsd.org Message-ID: <3902C35547ACC1DE7389E3FC@rambutan.pingpong.net> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Subject: NVIDIA nForce 570 SLI mcp X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 16:00:31 -0000 Hi! Seems there's no support for Nvidia's nForce 570 SLI? Is it easy to fix? Best regards, Palle From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 24 12:27:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F7AD16A407; Tue, 24 Oct 2006 12:27:28 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmmtao02.cox.net (eastrmmtao02.cox.net [68.230.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E7243D73; Tue, 24 Oct 2006 12:27:14 +0000 (GMT) (envelope-from conrads@cox.net) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20061024122715.FGMP10599.eastrmmtao02.cox.net@eastrmimpo01.cox.net>; Tue, 24 Oct 2006 08:27:15 -0400 Received: from serene.no-ip.org ([72.200.30.62]) by eastrmimpo01.cox.net with bizsmtp id eCSW1V00R1LR1K40000000 Tue, 24 Oct 2006 08:26:48 -0400 Received: from serene.no-ip.org (localhost [127.0.0.1]) by serene.no-ip.org (8.13.8/8.13.8) with ESMTP id k9OCQTsn035456; Tue, 24 Oct 2006 07:26:45 -0500 (CDT) (envelope-from conrads@cox.net) Date: Tue, 24 Oct 2006 07:26:20 -0500 From: "Conrad J. Sabatier" To: Cheffo Message-ID: <20061024072620.69dac5ab@serene.no-ip.org> In-Reply-To: <4533D000.3020902@sun-fish.com> References: <4533BE2E.4080005@icyb.net.ua> <4533D000.3020902@sun-fish.com> Organization: A Rag-Tag Band of Drug-Crazed Hippies X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; amd64-unknown-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 12:27:28 -0000 On Mon, 16 Oct 2006 21:31:28 +0300, Cheffo wrote: > Andriy Gapon wrote: > > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a > > new SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan > > Ermilov. However, the driver doesn't currently work on all hardware > > that it is to support. The problem is with choosing proper BAR > > registers, which, as it seems, might be different for different > > chipsets/SMB controllers. > > > > If you have a system based on NForce2/3/4, could you please share > > the following information: > > > > 1. find out pci handle of your SMB controller: > > $ pciconf -l | fgrep 0x0c0500 > > and also note chip field value, it should match > > 00(64|84|d4|e4|52)10de. E.g.: > > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b > > chip=0x006410de rev=0xa2 hdr=0x00 > > > > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > > follows: > > $ pciconf -r pci0:1:1 0x20 > > $ pciconf -r pci0:1:1 0x24 > > $ pciconf -r pci0:1:1 0x50 > > $ pciconf -r pci0:1:1 0x54 > > using your pci handle instead of pci0:1:1, e.g.: > > $ pciconf -r pci0:1:1 0x20 > > 00000000 > > $ pciconf -r pci0:1:1 0x24 > > 00000000 > > $ pciconf -r pci0:1:1 0x50 > > 00001001 > > $ pciconf -r pci0:1:1 0x54 > > 00001041 > > > > 3. send chip id and register values here. > > > > Thank you very much in advance. > > > > > none1@pci0:1:1: class=0x0c0500 card=0x815a1043 chip=0x005210de > rev=0xa2 hdr=0x00 > > pciconf -r pci0:1:1 0x20 > 00004c01 > pciconf -r pci0:1:1 0x24 > 00004c41pciconf -r pci0:1:1 0x50 > 00004c01 > pciconf -r pci0:1:1 0x54 > 00004c41 # pciconf -l | fgrep 0x0c0500 nfsmb0@pci0:1:1: class=0x0c0500 card=0x80c51043 chip=0x00d410de rev=0xa4 hdr=0x00 # pciconf -r pci0:1:1 0x20 00005001 # pciconf -r pci0:1:1 0x24 00005041 # pciconf -r pci0:1:1 0x50 00005001 # pciconf -r pci0:1:1 0x54 00005041 Thank you very much for your work on this! -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 24 15:22:03 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D038216A416 for ; Tue, 24 Oct 2006 15:22:03 +0000 (UTC) (envelope-from lists@codeangels.com) Received: from mail.codeangels.com (monkey.codeangels.com [62.2.169.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B293443D5D for ; Tue, 24 Oct 2006 15:21:48 +0000 (GMT) (envelope-from lists@codeangels.com) Received: (qmail-ldap/ctrl 573 invoked from network); 24 Oct 2006 15:21:47 -0000 Received: from monkey.codeangels.com (HELO www.codeangels.com) (xozxzk@[192.168.5.6]) (envelope-sender ) by monkey.codeangels.com (qmail-ldap-1.03) with SMTP for ; 24 Oct 2006 15:21:47 -0000 Message-ID: <2912.195.162.161.36.1161703307.squirrel@www.codeangels.com> Date: Tue, 24 Oct 2006 17:21:47 +0200 (CEST) From: "Kirill Ponazdyr" To: freebsd-hardware@freebsd.org User-Agent: SquirrelMail/Codeangels_GEN MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: I2C / SMBUS Monitoring. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists@codeangels.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 15:22:03 -0000 Hi, I have couple of Operon servers with redundant power supplies, according to very basic HW manual, those power supplies have SMBUS connection build-in which should allow monitoring for falures & co. I configured a kernel to recognize smbus and create /dev/smb0 device, but what's next? What is the easiest way to query status of devices / sensors connected to SMBUS? Kind Regards Kirill From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 24 15:34:01 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C3D816A407 for ; Tue, 24 Oct 2006 15:34:01 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4C8C43D64 for ; Tue, 24 Oct 2006 15:34:00 +0000 (GMT) (envelope-from patpro@patpro.net) Received: from [82.235.12.223] (boleskine.patpro.net [82.235.12.223]) by smtp1-g19.free.fr (Postfix) with ESMTP id 54E495858; Tue, 24 Oct 2006 17:33:57 +0200 (CEST) In-Reply-To: <2912.195.162.161.36.1161703307.squirrel@www.codeangels.com> References: <2912.195.162.161.36.1161703307.squirrel@www.codeangels.com> Mime-Version: 1.0 (Apple Message framework v752.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Patrick Proniewski Date: Tue, 24 Oct 2006 17:33:56 +0200 To: lists@codeangels.com X-Mailer: Apple Mail (2.752.2) Cc: freebsd-hardware@freebsd.org Subject: Re: I2C / SMBUS Monitoring. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 15:34:01 -0000 On 24 oct. 2006, at 17:21, Kirill Ponazdyr wrote: > I have couple of Operon servers with redundant power supplies, > according > to very basic HW manual, those power supplies have SMBUS connection > build-in which should allow monitoring for falures & co. > > I configured a kernel to recognize smbus and create /dev/smb0 > device, but > what's next? What is the easiest way to query status of devices / > sensors > connected to SMBUS? I've never used any of this, but you might want to try ports/sysutils/ mbmon patpro From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 24 16:18:37 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 071B516A417 for ; Tue, 24 Oct 2006 16:18:37 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6957D43D77 for ; Tue, 24 Oct 2006 16:18:36 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id k9OGIXW2096451; Tue, 24 Oct 2006 11:18:33 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <453E3CD9.6090406@centtech.com> Date: Tue, 24 Oct 2006 11:18:33 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.7 (X11/20061019) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2091/Tue Oct 24 08:27:53 2006 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: kramer@centtech.com Subject: BCM5754 recognized incorrectly on 6.2 beta2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 16:18:37 -0000 I have a Precision 390 with a BCM5754, FreeBSD recognizes it as a BCM5787 then panics the machine. I have a screenshot of the panic here, http://users.centtech.com/~kramer/broadcom/bge_prec390.jpg and I've booted the host into a FC3 nfsroot using kernel 2.6.18. Here is the dmesg and scanpci -v output DMESG tg3.c:v3.65 (August 07, 2006) ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:04:00.0 to 64 eth0: Tigon3 [partno(BCM95754) rev b002 PHY(5787)] (PCI Express) 10/100/1000Base T Ethernet 00:13:72:25:67:ec eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth0: dma_rwctrl[76180000] dma_mask[64-bit] SCANPCI -v pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x14e4 device 0x167a Broadcom Corporation Device unknown CardVendor 0x1028 card 0x01de (Card unknown) STATUS 0x0010 COMMAND 0x0006 CLASS 0x02 0x00 0x00 REVISION 0x02 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x10 BASE0 0x00000000eddf0004 addr 0x00000000eddf0000 MEM 64BIT MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0a -- ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 25 22:56:17 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61D5816A407 for ; Wed, 25 Oct 2006 22:56:17 +0000 (UTC) (envelope-from gvanlehn@ccsf.edu) Received: from ns7.ccsf.cc.ca.us (ns7.ccsf.cc.ca.us [147.144.1.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1789443D49 for ; Wed, 25 Oct 2006 22:56:17 +0000 (GMT) (envelope-from gvanlehn@ccsf.edu) Received: from bat-gwpo.ccsf.edu ([10.2.0.249]) by ns7.ccsf.cc.ca.us (8.13.1/8.13.1) with ESMTP id k9PMuGnK018112 for ; Wed, 25 Oct 2006 15:56:16 -0700 Received: from sfccd-MTA by bat-gwpo.ccsf.edu with Novell_GroupWise; Wed, 25 Oct 2006 16:06:19 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Wed, 25 Oct 2006 16:06:01 -0700 From: "Glen Van Lehn" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Install 5.4 CD, Adaptec 2120S, aac0: Command Timeouts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 22:56:17 -0000 Hi, I'm new to the list, but have been using BSD for five+ years. I tried installing 5-STABLE from the 5.4CDs onto a new HP DL140 G2 with an = Adaptec 2120S RAID controller that someone else had already installed with = a Linux OS. Two HDD are config'd as RAID1 set. After the probes for VGA & = mouse, the boot stuck on a repeated series of messages: aac0: COMMAND 0xc39ef000 TIMEOUT AFTER xxx SECONDS # 16 diff hex offsets per set .. each set repeating every 20 seconds aac0: COMMAND 0xc39ef708 TIMEOUT AFTER xxx SECONDS A different boot has a different hex prefix, 0xc3a16, but the same = sequence of 16 trailing digits, 000 to 708. Searching this list, I found a similar post from Chris Knight in January, = but he was on 6 and that was apparently right at a change to the aac = driver. Searching FreeBSD.org turned up a similar problem back in March = 2004 [5.2.1]. Scott Long responded to that one as a known issue being = resolved. The BIOS firmware was 'Build 7244' from May 2004, but I updated = that to Build 8205 [latest for that chipset] and still had the same = problem. Would the pre-existing different OS install mess up the aac0 driver? like = format the array first? I broke the array, re-inited the disks and recreated RAID 1.. but didn't = format drives .. still had problem. something else? I was able to install Fedora4 after failing on 5.4, but = I'd like to use FreeBSD for this project. comments appreciated. glen van lehn From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 26 20:10:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 523F516A4DF for ; Thu, 26 Oct 2006 20:10:20 +0000 (UTC) (envelope-from drue@therub.org) Received: from mali.therub.org (therub.org [66.97.248.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA63743D60 for ; Thu, 26 Oct 2006 20:10:19 +0000 (GMT) (envelope-from drue@therub.org) Received: by mali.therub.org (Postfix, from userid 1002) id 1ABC4147EE7; Thu, 26 Oct 2006 15:10:17 -0500 (CDT) Date: Thu, 26 Oct 2006 15:10:17 -0500 From: Dan Rue To: freebsd-hardware@freebsd.org Message-ID: <20061026201017.GY62981@therub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: asr woes. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 20:10:20 -0000 Recently I had a machine running an Adaptec (asr) raid 5 array lose one drive and subsequently crash. After dealing with the failure, I have brought the machine in question into testing and have discovered that I receive read errors in degraded mode. Lots of em: Oct 26 05:37:44 whiteandnerdy kernel: g_vfs_done():da0s1e[READ(offset=3725403922432, length=16384)] error = 5 Oct 26 05:37:44 whiteandnerdy kernel: g_vfs_done():da0s1e[READ(offset=3725403889664, length=16384)] error = 5 Oct 26 05:37:44 whiteandnerdy kernel: g_vfs_done():da0s1e[READ(offset=3725404168192, length=16384)] error = 5 Oct 26 05:37:44 whiteandnerdy kernel: g_vfs_done():da0s1e[READ(offset=3723171880960, length=16384)] error = 5 The card is an Adaptec 2100S: asr0: mem 0xfc000000-0xfdffffff irq 24 at device 1.0 on pci2 asr0: ADAPTEC 2110S FW Rev. 380E, 1 channel, 256 CCBs, Protocol I2O The system is FreeBSD 6.1-RELEASE with an SMP kernel (i386). Note that I havn't seen any write errors. Could this be a hardware problem or is it more likely an asr bug? Also related, it would be really nice if asr-utils worked (I've tried everything) :-/ Dan From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 27 22:24:10 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF3C616A415 for ; Fri, 27 Oct 2006 22:24:10 +0000 (UTC) (envelope-from jstep@unm.edu) Received: from unm.edu (f5vs2.unm.edu [64.106.76.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A00CF43D53 for ; Fri, 27 Oct 2006 22:24:10 +0000 (GMT) (envelope-from jstep@unm.edu) X-PMX-Host: Regor X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_MEDIA_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.3.0.0, Antispam-Data: 2006.10.27.141432 Received: from [68.65.217.87] (account jstep@unm.edu HELO [68.65.217.87]) by regor.unm.edu (CommuniGate Pro SMTP 4.3.6) with ESMTPSA id 51406945 for freebsd-hardware@freebsd.org; Fri, 27 Oct 2006 16:24:09 -0600 Message-ID: <454286F5.8020408@unm.edu> Date: Fri, 27 Oct 2006 15:23:49 -0700 From: Josh Stephenson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Hardware questions X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 22:24:11 -0000 Hi everyone, I hope this is the right place to send this question. I need to build a web environment for a high traffic content-driven website. My server experience has been somewhat limited to the software and I'm not sure exactly what would be the best hardware configuration for a site like this. I'm thinking I need to have three machines. One web server that sits in the front, one database server and one media (video and image) server. I am asking for suggestions on processing power, hard drive space, raid configurations from anyone who has done this type of thing before. Thanks a bunch, Josh From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 27 23:50:54 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D69A16A40F for ; Fri, 27 Oct 2006 23:50:54 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com [68.142.225.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 0460A43D45 for ; Fri, 27 Oct 2006 23:50:51 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 64722 invoked from network); 27 Oct 2006 23:50:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=qPqSlXgEXC5m9K29YL1ONDxzcuVggcb4gwQsiBFzEZvf3Nryc4h6xE8mApRydohFizS6maqphP9TXjKXvLZF8BNRYaVwsFOAs9ydGgcJKDTWS4VH+2nrbrPGBO1IyaMN1w7gSZDGWjuLM+KM2viViOp85sjokkzjG+/X/sx+Apw= ; Received: from unknown (HELO ?172.16.0.200?) (mikej@rogers.com@74.111.253.239 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 27 Oct 2006 23:50:51 -0000 Message-ID: <45429B67.4020500@rogers.com> Date: Fri, 27 Oct 2006 19:51:03 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: GIANT-FREE ciss X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 23:50:54 -0000 Are there any plans/work to make a giant-less ciss driver? Its a fairly popular driver that is used on some high end systems, and many systems now are running in SMP mode. Its a shame that they have to endure the performance penalty of the GIANT lock. From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 28 00:50:18 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE23D16A403 for ; Sat, 28 Oct 2006 00:50:18 +0000 (UTC) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2BA943D53 for ; Sat, 28 Oct 2006 00:50:18 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [10.1.4.159] (unknown [157.22.41.4]) by elvis.mu.org (Postfix) with ESMTP id AB8DB1A4D83; Fri, 27 Oct 2006 17:50:18 -0700 (PDT) Message-ID: <4542A948.5080809@freebsd.org> Date: Fri, 27 Oct 2006 17:50:16 -0700 From: Paul Saab User-Agent: Mail/News 1.5.0.2 (Macintosh/20060324) MIME-Version: 1.0 To: Mike Jakubik References: <45429B67.4020500@rogers.com> In-Reply-To: <45429B67.4020500@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hardware@freebsd.org Subject: Re: GIANT-FREE ciss X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 00:50:19 -0000 I did experiments and found that ciss did not gain any thing by making it MPSAFE. This may have changed with newer cards, but with all the older cards, there was no gain. Mike Jakubik wrote: > Are there any plans/work to make a giant-less ciss driver? Its a > fairly popular driver that is used on some high end systems, and many > systems now are running in SMP mode. Its a shame that they have to > endure the performance penalty of the GIANT lock. > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 28 01:18:42 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 180DC16A417 for ; Sat, 28 Oct 2006 01:18:42 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 3FC5E43D4C for ; Sat, 28 Oct 2006 01:18:41 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 21739 invoked from network); 28 Oct 2006 01:18:40 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=XlNBK7RggRZzjwfzSUYy1r9hNnKtcDh6Dl+m+OYSUJFOtd0vXt46beAa6uEc6mwzlwVkjIr+TQ1v0DabCMvvhu+MDhva88rRgTk3RalyrE+1ms43r8ecjGHUbi6etkqYtIc3n1excml3Xt9Tk9yInCog4frs5q9ssvayIyR3oyk= ; Received: from unknown (HELO ?172.16.0.200?) (mikej@rogers.com@74.111.253.239 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 28 Oct 2006 01:18:40 -0000 Message-ID: <4542AFFD.7070100@rogers.com> Date: Fri, 27 Oct 2006 21:18:53 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Paul Saab References: <45429B67.4020500@rogers.com> <4542A948.5080809@freebsd.org> In-Reply-To: <4542A948.5080809@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hardware@freebsd.org Subject: Re: GIANT-FREE ciss X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 01:18:42 -0000 Paul Saab wrote: > I did experiments and found that ciss did not gain any thing by making > it MPSAFE. This may have changed with newer cards, but with all the > older cards, there was no gain. Thanks for the information. I wasn't aware that this was a possible case. Wouldn't the GIANT lock have a negative effect on other applications/system? Or is my understanding of the lock flawed?