From owner-freebsd-current@FreeBSD.ORG Tue Jul 7 20:03:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D58CF106566C for ; Tue, 7 Jul 2009 20:03:51 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from mtaout03-winn.ispmail.ntl.com (mtaout03-winn.ispmail.ntl.com [81.103.221.49]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4C08FC13 for ; Tue, 7 Jul 2009 20:03:50 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090707200349.KZNF5579.mtaout03-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com> for ; Tue, 7 Jul 2009 21:03:49 +0100 Received: from cpc1-cove3-0-0-cust909.sol2.cable.ntl.com ([86.20.31.142]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090707200349.DIUV13254.aamtaout01-winn.ispmail.ntl.com@cpc1-cove3-0-0-cust909.sol2.cable.ntl.com> for ; Tue, 7 Jul 2009 21:03:49 +0100 X-Virus-Scanned: amavisd-new at cpc2-cove3-0-0-cust311.sol2.cable.ntl.com Received: from localhost (localhost [127.0.0.1]) by cpc1-cove3-0-0-cust909.sol2.cable.ntl.com (8.14.3/8.14.3) with ESMTP id n67K3jhj001870 for ; Tue, 7 Jul 2009 21:03:45 +0100 (BST) (envelope-from ianjhart@cpc1-cove3-0-0-cust909.sol2.cable.ntl.com) Received: from gamma.private.lan (gamma.private.lan [192.168.0.12]) by webmail.private.lan (Horde Framework) with HTTP; Tue, 07 Jul 2009 21:03:45 +0100 Message-ID: <20090707210345.13681mi2dwvan78k@webmail.private.lan> Date: Tue, 07 Jul 2009 21:03:45 +0100 From: Ian J Hart To: freebsd-current@freebsd.org References: <20090624153442.137934uzyotkb5og@10.248.192.16> In-Reply-To: <20090624153442.137934uzyotkb5og@10.248.192.16> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.3.3 / FreeBSD-7.2 X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on cpc1-cove3-0-0-cust909.sol2.cable.ntl.com X-Cloudmark-Analysis: v=1.0 c=1 a=ERehf_AEJYYA:10 a=NLZqzBF-AAAA:8 a=6I5d2MoRAAAA:8 a=VRdyzA9mAAAA:8 a=zd2uoN0lAAAA:8 a=6mGpWblYiIphEkupZzAA:9 a=hhl8yR7ykOPd4GsQp6AA:7 a=9b12fJnQ7G6RXEiHeUUZFmuqybYA:4 a=_dQi-Dcv4p4A:10 a=SV7veod9ZcQA:10 Subject: Re: zpool scrub errors on 3ware 9550SXU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2009 20:03:52 -0000 Quoting ianjhart@ntlworld.com: > Quoting ianjhart@ntlworld.com: > >> Quoting Kip Macy : >> >>>> >>>> As usual scrubs cleanly on 7.2. Started throwing errors within a >>>> few minutes under 8. Then it paniced, possibly due to scrub -s. >>>> >>>> It's sat at the DB prompt if there's anything I can do. I'll need >>>> idiots guide level instruction. I have a screen dump if someone >>>> want to step up. Off list? >>>> >>>> Highlight seems to be... >>>> >>>> Memory modified after free 0xffffff0004da0c00(248) val=3000000 @ >>>> 0xffffff0004dc00 >>>> Panic: most recently used by none >>> >>> Can you test with recent 7-STABLE? That would tell me whether or not >>> your hitting a general HEAD issues or problems with the v13 import. >> >> It's doing a scrub under 7.2 following another failed test. I'll >> pull it up to stable after that. >> >> Have more data will post that once I've done a couple a jobs. >> >>> >>> Thanks, >>> Kip > > Here's that extra data. > > Updated 3ware/AMCC card firmware. > > Enable onboard SATA and fit a 300GB SATA disk. Remove the floppy and > fit a second 300GB SATA disk. > > Remove the two 500GB disks and replace with 1.5TB units. I can now > create two 8 disk raidz2 giving the same 12 disks worth of storage I > had with one 14 disk raidz2. > > Reinstall the two O/S on the 300GB drives. > > > May be of use to someone, so bear with me. > > Reset to BIOS defaults. Some issues! Disabling sound helps. > > Now suspect motherboard BIOS may be part of the problem. Removed > both cards and tested each version in turn. > > ref: http://www.tyan.com.tw/support_download_bios.aspx?model=S.S2895 > > Started with 1.04 ended up with 1.04. Versions after, detect the > internal; SATA disks as 150 not 300. Most versions lock the keyboard > (KVM) when legacy USB is enabled. That's a PITA when you've just > taken the floopy disk out.No internal SATA disk settings. Be nice to > check the geometry as 7 and 8 sysinstall seem to be behaving > differently. > > With the cards back in. > > Add an ATA disk and CDROM while testing.Easyboot order is SATA0 ATA0 > SATA1. Fdisk the so far blank ATA disk :) > > On board audio clashes with something. BIOS 1.03 and later supports > 16 SCSI boot devices. I disabled booting from the RAID card to allow > the onboard SATA drives to boot. > > Out of space for option ROM error has gone. > > AFAIK CPUs are late enough to support DDR400. Check anyway. Clock > down to 333Mhz. Still fails. > > > > There's one last thing, this BIOS (1.04) does not supply the fix for > AMD errata 169. Later BIOS incorrectly detect the onboard SATA disks. > > Northbridge System Request Queue may stall. > > ref: > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25759.pdf > > We don't seem to have /dev/msr. Could I fix this using (the shiny > new) cpucontrol? > > Thanks > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > FWIW this is still reproducable with 8.0-BETA1. -- ian j hart ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.