From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 16 17:51:57 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFFE9106564A for ; Fri, 16 Jan 2009 17:51:57 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 5EEDD8FC0C for ; Fri, 16 Jan 2009 17:51:57 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA10.westchester.pa.mail.comcast.net with comcast id 4B3J1b00w0QuhwU5AHeibs; Fri, 16 Jan 2009 17:38:42 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA02.westchester.pa.mail.comcast.net with comcast id 4HeY1b00C4Mx3R23NHeaJU; Fri, 16 Jan 2009 17:38:40 +0000 Message-ID: <4970C617.50309@comcast.net> Date: Fri, 16 Jan 2009 12:38:31 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa References: <496CEB13.5040806@comcast.net> In-Reply-To: <496CEB13.5040806@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: amr driver changes in FreeBSD 7.1-RELEASE 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, 16 Jan 2009 17:51:58 -0000 In case anyone is interested, the situation has only gotten weirder. Booting 7.1-R with 'boot -v' mysteriously adds: (probe32:amr1:1:6:0): error 22 (probe32:amr1:1:6:0): Unretryable Error However, amr1 is not the one that is giving us issues. It appears to work fine. amr0 is the one on which 7.1-R fails to find any volumes. Even stranger, a 'camcontrol devlist' manages to display all off the individual SCSI drives attached to amr0. Finally, this problem was solved whilst writing this e-mail. The default for kern.cam.scsi_delay (5000ms) appears to be too aggressive in my circumstances. Increasing it to 15000 solves my issue (and gets rid of "amr0: adapter is busy" messages). Steve Polyack wrote: > Hello, > > We have a Dell PowerEdge 1850 server. It contains two PERC4 RAID > controllers. One is a PERC4e/Si, and the other is a PERC4/DC. Right > now we are running FreeBSD 6.3-RELEASE, with a 36GB RAID-1 on the > PERC4e/Si (amr0), and both a 1TB RAID5 and a 136GB RAID1 on the > PERC4/DC(amr1). Both adapters are running the latest firmware revision. > > When we boot FreeBSD7.1 install media, the amr driver fails to detect > any volumes (disks) attached to amr0, the PERC4e/Si. However, it > picks up the attached disks on the PERC4/DC just fine. However, if I > boot 7.0-RELEASE install media, it picks up all of the attached > volumes, leading me to believe the issue is due to changes in the amr > driver between 7.0 and 7.1. During the 7.1 boot process, before > probing disks, we see the message "amr0: adapter is busy" show up > twice. This also does not occur on the 6.3, 6.4, or 7.0 releases. > > We also have another PE1850 with a very similar configuration, except > the two PERCs get probed in a different order, and it detects all of > the attached volumes without any issues. > > Any suggestions? These are semi-critical systems, so we aren't always > able to test things like this. But, we can schedule downtime once or > twice a week if necessary. > > -Steve Polyack > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >