Date: Tue, 13 Jan 2009 12:01:28 -0800 From: Cameron <hiryu@neo-zeon.de> To: freebsd-hardware@freebsd.org Cc: Mike Tancsa <freebsd-stable@freebsd.org>, Steve Polyack <korvus@comcast.net> Subject: Re: amr driver changes in FreeBSD 7.1-RELEASE Message-ID: <200901131201.28226.hiryu@neo-zeon.de> In-Reply-To: <496CEB13.5040806@comcast.net> References: <496CEB13.5040806@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, This seems related to a problem I had with a 7.1-PRERELEASE (I have since upgraded to 7.1-RELEASE, but haven't not tested if the problem is still there). If I compiled the kernel with only the amr driver, it would not see my raid volume. If I enabled a separate scsi driver (I think it was some LSI Logic scsi driver) in addition to amr, the amr driver would work fine. I wish I could give some exact details (like the name of the other scsi driver), but this is on my home machine, and I'm currently at work. While a generic 7.1-PRERELEASE kernel had both of these compiled in (of course), and worked fine for me, I suspect our problems are related. I have an LSI Logic 150-4 SATA raid controller. -Cameron n Tuesday 13 January 2009 11:27:15 am 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-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901131201.28226.hiryu>