From owner-aic7xxx Fri Sep 17 21:10:47 1999 Delivered-To: aic7xxx@freebsd.org Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [207.175.42.154]) by hub.freebsd.org (Postfix) with ESMTP id 1D9F21550D for ; Fri, 17 Sep 1999 21:10:42 -0700 (PDT) (envelope-from dledford@redhat.com) Received: from aic-cvs.devel.redhat.com (dledford.corp.redhat.com [10.0.0.25]) by lacrosse.corp.redhat.com (8.9.3/8.9.3) with ESMTP id AAA32060; Sat, 18 Sep 1999 00:10:32 -0400 Received: from redhat.com (IDENT:dledford@localhost [127.0.0.1]) by aic-cvs.devel.redhat.com (8.9.3/8.9.3) with ESMTP id AAA20210; Sat, 18 Sep 1999 00:19:35 -0400 Message-ID: <37E312D3.D55D48DC@redhat.com> Date: Sat, 18 Sep 1999 00:19:31 -0400 From: Doug Ledford Organization: Red Hat, Inc. X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5-22 i686) X-Accept-Language: en MIME-Version: 1.0 To: The Darkness Cc: aic7xxx@FreeBSD.ORG Subject: Re: umax ubdx-as mboard, aic 7880 scsi problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Darkness wrote: > > Hi All, > > I am experiencing quite a bit of trouble getting any linux kernel from > the 2.2.x or 2.3.x series to run on my server. The server stats are as > follows: > > motherboard: umax UDBX-AS with integrated scsi - (AIC 7880) > ram: 96M > disks 2* seagate ST39140W > > The kernel will boot and load happily until it reaches the scsi initialisation > phase. It happily detects the the onboard scsi, but dies part way through > the initialisation phase. Here is an example of what appears on the > console: > ... > > (scsi0) found at PCI 12/0 > (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs > scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4 > > SCSI: aborting command due to timeout: pid 0, scsi0, channel 0, id 0, lun 0 > Test Unit Ready 00 00 00 00 00 > SCSI host 0 abort (pid 0) timed out - resetting > SCSI bus is being reset for host 0 channel 0 > SCSI host 0 abort (pid 0) timed out - resetting - trying harder > ... > > It will continue to do this until the kernel panics. This is a bug in the ioapic setup. Use the option "noapic" when booting the linux kernel and the problem will go away. -- Doug Ledford 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