From owner-freebsd-current Wed Feb 23 11:40:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 4FEF637B92B for ; Wed, 23 Feb 2000 11:40:45 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id OAA76986; Wed, 23 Feb 2000 14:40:33 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000223143725.01c6ecb0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 23 Feb 2000 14:37:25 -0500 To: karsten@rohrbach.de, freebsd-current@FreeBSD.ORG From: Mike Tancsa Subject: Re: Panic #3 (ffs) (MegaRAID) In-Reply-To: <20000223203037.A2298@rohrbach.de> References: <20000223153629.H18964@lucifer.bart.nl> <20000223153629.H18964@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:30 PM 2/23/00 +0100, Karsten W. Rohrbach wrote: >which megaraid adapter do you use in this box (hw, fw ver, bios ver, >cntl-m ver)... > >i've seen those panics on our old news box when there where errors on >the scsi busses which did not get detected properly. mainly termination >issues *sigh* I dont think its necessarily a termination issue. I have swapped the exact same chain onto a Mylex DAC960 and can pound the box without issue. I have a nasty feeling my 466 might not like my MB chipset. I am using a 466 PERC2/SC on BX chipset ECS MB and its throwing all sorts of fits. When I used a 428 on another box (a plain old Pentium), I didnt have nearly this many problems. Soon as my co-worker is finished with the older Pentium, I can test this theory to see if this is the case. Looking at the release notes for the BIOS revs at AMI, it seems older BIOS revs might have problems with newer MBs From ftp://ftp.megatrends.com/MegaRAID/drivers/466/readme-gh6d.txt >Changes in this release: >----------------------- >1. CTRL-M is not invoked until after the system BIOS is completed > on newer systems that support PMM (POST Memory Management). > The system would hang at different places in CTRL-M on these > systems prior to these changes. Until I flashed it to this new rev, I was seeing this behaviour. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message