From owner-freebsd-scsi Thu Jan 6 20:25:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 21E3014E65 for ; Thu, 6 Jan 2000 20:25:41 -0800 (PST) (envelope-from up@3.am) Received: (qmail 73309 invoked by uid 1825); 7 Jan 2000 04:20:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jan 2000 04:20:56 -0000 Date: Thu, 6 Jan 2000 23:20:56 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Doug White Cc: scsi@freebsd.org Subject: Re: stuck traffic light on l440gx+ mobo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Jan 2000, Doug White wrote: > Hey all... > > We have several servers with Intel L440GX+ motherboards. These have a > builtin AIC-7896 controler running v2.20S1B1 of their BIOS. > > I installed a kernel on them today with ahc support compiled in (haven't > before, we don't use the onboard SCSI until today) and noticed that > machines with this board and only IDE channels (ie nothing plugged into > the mobo SCSI ports) have the disk access light stuck on. > > The machine operates normally otherwise, but the stuck light is masking > the acitivity I really want to see :-) It sticks on just after the > 'Waiting 2 seconds for SCSI devices to settle' prompt. This is on a late > 3.2-STABLE. > > Curious to know if this is fixed or if there's a simple workaround beyond > compiling out ahc. :) Thanks! I noticed the same thing (same hardware and FBSD version here). It went away, and the light flickers with access now, when I put an externat tape drive and terminator on the second SCSI bus. I'd guess it was termination of that bus that did it.... James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message