From owner-aic7xxx Wed Jan 20 15:36:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03349 for aic7xxx-outgoing; Wed, 20 Jan 1999 15:36:28 -0800 (PST) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03341 for ; Wed, 20 Jan 1999 15:36:27 -0800 (PST) (envelope-from rhl@emily.hdtv.lucent.com) Received: by auemlsrv.firewall.lucent.com (8.9.1/EMS-1.4.1 sol2) id SAA24721 for AIC7xxx@FreeBSD.ORG.smtp; Wed, 20 Jan 1999 18:36:19 -0500 (EST) Received: from emailbox.hdtv.lucent.com by auemlsrv.firewall.lucent.com (8.9.1/EMS-1.4.1 sol2) id SAA24717 for ; Wed, 20 Jan 1999 18:36:19 -0500 (EST) Received: from soul.hdtv.lucent.com by emailbox.hdtv.lucent.com (8.8.8+Sun/EMS-1.4.1 sol2) id SAA18773; Wed, 20 Jan 1999 18:36:18 -0500 (EST) Received: from emily.hdtv.lucent.com by soul.hdtv.lucent.com (SMI-8.6/EMS-1.4.1 client sol2) id SAA08118; Wed, 20 Jan 1999 18:36:18 -0500 Message-ID: <36A66848.1C1A343B@emily.hdtv.lucent.com> Date: Wed, 20 Jan 1999 18:35:36 -0500 From: "Roger H. Levy" Organization: Bell Laboratories - Lucent Technologies X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: AIC7xxx@FreeBSD.ORG Subject: Re: Adaptec 2920C boot problem References: <36A61F2D.CA1B353A@emily.hdtv.lucent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found a local expert who solved this problem for me. The AIC-7xxx driver was compiled into the kernel and was also being loaded as a module at boot time. This apparently created the conflict observed. The expert guided me through the process of making a new init ramdisk that would not cause the module to get loaded. That solved the problem. Roger Levy Roger H. Levy wrote: > > I'm relatively new to Linux and completely new to building Linux > kernels. However, there is an application that I want to run which I > obtained from NIST (US Gov't) that requires kernel hacking via patches > they supply. I don't think my problem has anything to do specifically > with these hacks. > > The machine that was available to me is a 200MHz Micron with an Adaptec > 2920C SCSI adapter, Seagate ST32171N (2G) drive and Toshiba XM-5701TA > SCSI CRROM. Note that contrary to the AIC7xxx README, the 7920C does > use a 7xxx chip - the AIC7856 (Perhaps earlier 7920s did not use 7xxx > chips??). The NIST distribution specified a 2.0.27 - 2.0.33 kernel > which corresponds to Redhat 5.0 (2.0.32 kernel). My configuration > (SCSI, low level) specified Y for 7xxx support and N for all other SCSI > adapters. > > After figuring out the errors in the NIST instructions, I was able to > build the kernel and application. Following the kernel HOWTO, I did a > "make zdisk" and the system booted well from floppy and after installing > a NIST module, the application started. However, the same kernel panics > after it is installed on the hard disk and booted. > > The messages preceding the panic are: > aic7xxx: at PCI 17 > aic7xxx: Warning: detected auto-termination. Please verify driver > detected settings and use manual termination if necessary. > aic7xxx: BIOS enabled, IO Port 0xf800, IO Mem 0xfdeff000, IRQ 9 > aic7xxx: Single Channel, SCSI ID 7, 3/3 SCBs, QFull 8, QMask 0xf > scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.1/3.2 > scsi : 2 hosts > scsi1 : Scanning channel A for devices. > Kernel panic: aic7xxx: AWAITING_MSG for an SCB that does not have a > waiting message. > In swapper task - not syncing. > > Note that I believe I see a very similar or identical set of messages > without the panic sweeping across the screen about 35 lines earlier in > the boot. > > So, why does this happen when booting from the HD but not from the FD? > How can I correct this? > > Roger Levy > > 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