Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-08-04 Thread John-Mark Gurney
User Freebsd wrote this message on Mon, Jul 31, 2006 at 22:44 -0300:
 For those that haven't been following the discussion on this, the iir(4) 
 driver in FreeBSD 6.x appears to have a deadlock issue under medium to 
 heavy load, where the 'blocked' state just continues to rise until file 
 accesses just no longer work ...
 
 So, if you are running a server that is using the iir(4) device driver and 
 are considering upgrading to FreeBSD 6.x and beyond, or are looking to 
 build a new machine using a device that relies on this driver, do so at 
 your own peril ...
 
 Please note that this deadlock issue exists on *both* the ICP Vortex 
 cards, *and* the Intel based RAID controllers ...

Have you tried the driver in -current and/or 6.1-R?  Specificly v1.14
and v1.13.2.1 of iir.c that limits the simq to 32 commands?  We are
running w/ this modifications w/o issues on 6.0-R w/ SRCU31A and SRCU42L
cards...  We have a few GDT cards also that I don't believe we are
having any issues with...

Infact, scottl tracked down that change after a bit of proding from me
on behalf of my employer nCircle...  (Though it helped that he was able
to reproduce it in his lab.)...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-08-04 Thread User Freebsd

On Fri, 4 Aug 2006, John-Mark Gurney wrote:


User Freebsd wrote this message on Mon, Jul 31, 2006 at 22:44 -0300:

For those that haven't been following the discussion on this, the iir(4)
driver in FreeBSD 6.x appears to have a deadlock issue under medium to
heavy load, where the 'blocked' state just continues to rise until file
accesses just no longer work ...

So, if you are running a server that is using the iir(4) device driver and
are considering upgrading to FreeBSD 6.x and beyond, or are looking to
build a new machine using a device that relies on this driver, do so at
your own peril ...

Please note that this deadlock issue exists on *both* the ICP Vortex
cards, *and* the Intel based RAID controllers ...


Have you tried the driver in -current and/or 6.1-R?  Specificly v1.14
and v1.13.2.1 of iir.c that limits the simq to 32 commands?  We are
running w/ this modifications w/o issues on 6.0-R w/ SRCU31A and SRCU42L
cards...  We have a few GDT cards also that I don't believe we are
having any issues with...


Yes, this was the first thing ScottL asked when we narrowed the problem 
down ... this appears to be a different issue then the one you were seeing 
:(



Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-08-01 Thread Rico Secada
On Mon, 31 Jul 2006 22:44:01 -0300 (ADT)
User Freebsd [EMAIL PROTECTED] wrote:

Seems to me like the best solution is to boykott Adaptec like OpenBSD did.

 
 'k, I finally got ahold of someone @ adaptec, and the official word seems 
 to be:
 
 FreeBSD 6 is not officially supported for the GDT based ICP RAID
   controllers. Nevertheless the inbox driver should work.
 
 Great, well, the inbox driver doesn't work with FreeBSD 6.x, and support 
 doesn't exist to get it fixed, mainly since, as most ppl here know, the 
 specs are closed, so even a non-Adaptec person can't do much to fix the 
 problem(s) ...
 
 For those that haven't been following the discussion on this, the iir(4) 
 driver in FreeBSD 6.x appears to have a deadlock issue under medium to 
 heavy load, where the 'blocked' state just continues to rise until file 
 accesses just no longer work ...
 
 So, if you are running a server that is using the iir(4) device driver and 
 are considering upgrading to FreeBSD 6.x and beyond, or are looking to 
 build a new machine using a device that relies on this driver, do so at 
 your own peril ...
 
 Please note that this deadlock issue exists on *both* the ICP Vortex 
 cards, *and* the Intel based RAID controllers ...
 
 If anyone from Adaptec is out there and is actually interested in seeing 
 this problem fixed, *please* let me know ... I have three servers, all 
 three exhibiting this problem, and one of them is fully loaded with the 
 kernel debug stuff so that I can (I think) give you almost *anything* you 
 want in the way of information concerning the problem ...
 
 
 
 Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
 Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
 Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-08-01 Thread User Freebsd


A quick follow up on this email ... please note that I have not, in this 
email, pointed to anything but the iir(4) driver, and, more specifically, 
the GDT controller card ...


I have been using Adaptec products since the early 90's, and, until 
upgrading to FreeBSD 6.x, *never* had a complaint with them ... this email 
was meant to be a 'caveat emptor' for anyone looking to use the iir(4) 
driver, and is not meant to apply to *all* Adaptec cards, as they don't 
all use the iir(4) driver ...


Apologies to all who took this as a broad attack against Adaptec, it was 
not meant as such ...


On Mon, 31 Jul 2006, User Freebsd wrote:



'k, I finally got ahold of someone @ adaptec, and the official word seems to 
be:


FreeBSD 6 is not officially supported for the GDT based ICP RAID
controllers. Nevertheless the inbox driver should work.

Great, well, the inbox driver doesn't work with FreeBSD 6.x, and support 
doesn't exist to get it fixed, mainly since, as most ppl here know, the specs 
are closed, so even a non-Adaptec person can't do much to fix the problem(s) 
...


For those that haven't been following the discussion on this, the iir(4) 
driver in FreeBSD 6.x appears to have a deadlock issue under medium to heavy 
load, where the 'blocked' state just continues to rise until file accesses 
just no longer work ...


So, if you are running a server that is using the iir(4) device driver and 
are considering upgrading to FreeBSD 6.x and beyond, or are looking to build 
a new machine using a device that relies on this driver, do so at your own 
peril ...


Please note that this deadlock issue exists on *both* the ICP Vortex cards, 
*and* the Intel based RAID controllers ...


If anyone from Adaptec is out there and is actually interested in seeing this 
problem fixed, *please* let me know ... I have three servers, all three 
exhibiting this problem, and one of them is fully loaded with the kernel 
debug stuff so that I can (I think) give you almost *anything* you want in 
the way of information concerning the problem ...




Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]




Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-08-01 Thread User Freebsd

On Tue, 1 Aug 2006, Rico Secada wrote:


On Mon, 31 Jul 2006 22:44:01 -0300 (ADT)
User Freebsd [EMAIL PROTECTED] wrote:

Seems to me like the best solution is to boykott Adaptec like OpenBSD did.


Actually, based on the thread going on on -stable right now, from ppl that 
are talking to Adaptec, the issue is that the cards that use the iir(4) 
driver, at least as far as I'm reading things, are no longer considered 
supported ... Adaptec / ICP Vortex *is* coming out with newer cards, that 
will be supported by FreeBSD, but they won't fall under the iir(4) driver 
...


So the problem is more 'older cards with newer operating system' ...



 


'k, I finally got ahold of someone @ adaptec, and the official word seems
to be:

FreeBSD 6 is not officially supported for the GDT based ICP RAID
  controllers. Nevertheless the inbox driver should work.

Great, well, the inbox driver doesn't work with FreeBSD 6.x, and support
doesn't exist to get it fixed, mainly since, as most ppl here know, the
specs are closed, so even a non-Adaptec person can't do much to fix the
problem(s) ...

For those that haven't been following the discussion on this, the iir(4)
driver in FreeBSD 6.x appears to have a deadlock issue under medium to
heavy load, where the 'blocked' state just continues to rise until file
accesses just no longer work ...

So, if you are running a server that is using the iir(4) device driver and
are considering upgrading to FreeBSD 6.x and beyond, or are looking to
build a new machine using a device that relies on this driver, do so at
your own peril ...

Please note that this deadlock issue exists on *both* the ICP Vortex
cards, *and* the Intel based RAID controllers ...

If anyone from Adaptec is out there and is actually interested in seeing
this problem fixed, *please* let me know ... I have three servers, all
three exhibiting this problem, and one of them is fully loaded with the
kernel debug stuff so that I can (I think) give you almost *anything* you
want in the way of information concerning the problem ...



Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]




Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


[IMPORTANT] Adaptec no longer supporting iir(4) driver ...

2006-07-31 Thread User Freebsd


'k, I finally got ahold of someone @ adaptec, and the official word seems 
to be:


FreeBSD 6 is not officially supported for the GDT based ICP RAID
 controllers. Nevertheless the inbox driver should work.

Great, well, the inbox driver doesn't work with FreeBSD 6.x, and support 
doesn't exist to get it fixed, mainly since, as most ppl here know, the 
specs are closed, so even a non-Adaptec person can't do much to fix the 
problem(s) ...


For those that haven't been following the discussion on this, the iir(4) 
driver in FreeBSD 6.x appears to have a deadlock issue under medium to 
heavy load, where the 'blocked' state just continues to rise until file 
accesses just no longer work ...


So, if you are running a server that is using the iir(4) device driver and 
are considering upgrading to FreeBSD 6.x and beyond, or are looking to 
build a new machine using a device that relies on this driver, do so at 
your own peril ...


Please note that this deadlock issue exists on *both* the ICP Vortex 
cards, *and* the Intel based RAID controllers ...


If anyone from Adaptec is out there and is actually interested in seeing 
this problem fixed, *please* let me know ... I have three servers, all 
three exhibiting this problem, and one of them is fully loaded with the 
kernel debug stuff so that I can (I think) give you almost *anything* you 
want in the way of information concerning the problem ...




Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]