Date: Thu, 25 Feb 1999 18:15:55 -0600 (CST) From: "christian.klein" <klein002@bama.ua.edu> To: Doug Ledford <dledford@redhat.com> Cc: "Robert G. Brown" <rgb@phy.duke.edu>, Maxwell Spangler <maxwell@clark.net>, AIC7xxx@FreeBSD.ORG Subject: Re: Adaptec 7890 and RAID portIII RAID controller Linux Support Message-ID: <Pine.SOL.4.02A.9902251811520.6848-100000@bama.ua.edu> In-Reply-To: <36D5B02F.B9E0605C@redhat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Does this only happen with SMP? or on other machines too? i have a 2940UW and a buslogic bt-932 (dual channel narrow) and have never had a problem on my older P2 266 machine (440fx, 128mb edo ram). or am i just lucky? I would be more than happy to be a test bed for any patches you make regarding this problem though i have never experienced it myself. christian klein002@bama.ua.edu > totally different scsi low level drivers (in this case, BusLogic and > aic7xxx). I have a system were I can reliably produce lockups and other > errors by mixing the two brands of controllers and drivers, but where either > one by themselves works fine with the same setup. Aka, 2 aic7xxx cards to > handle the two busses works fine, 2 buslogics cards to handle the two busses > works fine, 1 buslogic and 1 aic7xxx based cards spells problems. This > happens to be very high on my list of things to fix. Unfortunately, I'm > afraid the answer may be that it will show up in 2.3 with other mid level > modifications. However, since I can cite at least one system that acts this > way reliably, I'm recommending people try and be homogeneous in the SCSI/IDE > configuration on a single linux system for the time being. Note, very few > people have even considered that this might be a problem, so that gives some > sort of indication about how many people have mixed scsi systems. I also > suspect that some scsi drivers, like the aha152x driver, that are polling > based driver and essentially force serialization of the complete SCSI > subsystem by the fact that the driver locks the CPU down and spins for a long > time instead of queueing things up and doing everything simply on completion > interrupts also plays a part in this. I suspect that those drivers can > peacefully co-exist with the likes of the aic7xxx driver. It's only the > mixing of two SMP optimized, parallel operating drivers that causes problems. > When I actually get this pinned down, then I'll comment further. > > -- > Doug Ledford <dledford@redhat.com> > Opinions expressed are my own, but > they should be everybody's. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe aic7xxx" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.4.02A.9902251811520.6848-100000>