From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 15:35:23 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B778C16A47A for ; Tue, 5 Jun 2007 15:35:23 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id 678BF13C4BC for ; Tue, 5 Jun 2007 15:35:23 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l55FZMWb012161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Jun 2007 08:35:22 -0700 X-Auth-Received: from [192.168.10.45] (c-67-166-149-71.hsd1.ca.comcast.net [67.166.149.71]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l55FZLIO007930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2007 08:35:22 -0700 Message-ID: <466582BA.5070500@u.washington.edu> Date: Tue, 05 Jun 2007 08:35:22 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: "N. Harrington" References: <798114.3933.qm@web34504.mail.mud.yahoo.com> In-Reply-To: <798114.3933.qm@web34504.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.5.81534 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P2 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' Cc: questions@freebsd.org Subject: Re: How to solve mysterious system lockups? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 15:35:23 -0000 N. Harrington wrote: > --- Garrett Cooper wrote: > > >> N. Harrington wrote: >> >>> Hello >>> I have several systems that are used as squid >>> caching servers. I have some systems that use SCSI >>> disks and some that use SATA disks. They are >>> identical in everyway except for the sata vs SCSI >>> drives. >>> >>> At random times, the sata based systems seem to >>> >> be >> >>> freezing. You can ping them and they respond, but >>> >> you >> >>> cannot log in. Nor are any logs processed during >>> >> that >> >>> time. >>> >>> I figure it mist be something to do with the >>> >> disks, >> >>> but I am not sure how to solve it. There seems to >>> >> be >> >>> little rhyme or reason. It does not happen >>> >> necessarily >> >>> during busy times. It can happen in the middle of >>> >> the >> >>> night. >>> >>> Any pointers in how to track down the cause would >>> >> be >> >>> much appreciated. >>> >>> Tyan S2881 Motherboard - 4gigs mem >>> Using 4 SATA (or scsi) drives >>> FreeBSD amd64 6.2-STABLE. >>> >>> Thanks! >>> >>> Nicole >>> >>> >> Nicole, >> What's the driver in use for the SATA and the >> SCSI drives? >> -Garrett >> > > Hi Garret > Here is the driver info. > > -- SATA > > atapci0: port > 0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f > > mem > 0xfeafec00-0xfeafefff irq 17 at device 5.0 on pci3 > ata2: on atapci0 > ata3: on atapci0 > ata4: on atapci0 > ata5: on atapci0 > pci3: at device 6.0 (no driver > attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at > device 7.1 on pci0 > ata0: on atapci1 > ata1: on atapci1 > pci0: at device 7.2 (no driver > attached) > pci0: at device 7.3 (no driver attached) > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > > -- SCSI > > ahd0: port > 0x8000-0x80ff,0x7800-0x78ff > mem 0xfc89c000-0xfc89dfff irq 24 at device 10.0 on > pci2 > ahd0: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > 67-100Mhz, 512 SCBs > ahd1: port > 0x8800-0x88ff,0x8400-0x84ff > mem 0xfc89e000-0xfc89ffff irq 25 at device 10.1 on > pci2 > ahd1: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > 67-100Mhz, 512 SCBs > pci0: at > device 10.1 (no driver attached) > pcib3: at device 11.0 on pci0 > pci1: on pcib3 > pci0: at > device 11.1 (no driver attached) > > > > Thanks! > > Nicole Ok, so it's an AMD 8111 northbridge versus an Adaptec onboard SCSI controller. 1. What release / version of FreeBSD are you using? You should upgrade to 6.2 STABLE because there have been a variety of issues worked out in previous releases. 2. Do you have any logs for activity during the hours when it locks up (in particular anything interesting / fishy popping up)? 3. What scheduler are you using? 4BSD, ULE? 4. Does your machine (using the SATA controllers) lock up under heavy load? If so, you may have a northbridge cooling issue that you need to put a fan on. For instance, the motherboard that I was using for a while (ASUS P5N-E SLI) was really close to my CPU heatsink, and there was a lot of heat transfer between my northbridge and CPU heatsink, which was raising the onboard temperatures 5~10 degrees C. The new motherboard (ASUS P5B DLX) doesn't do that though. Cheers, -Garrett