From owner-freebsd-scsi Sun Apr 6 00:36:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA01839 for freebsd-scsi-outgoing; Sun, 6 Apr 1997 00:36:29 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA01824 for ; Sun, 6 Apr 1997 00:36:21 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00440; Sun, 6 Apr 1997 10:36:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA08150; Sat, 5 Apr 1997 08:08:34 +0200 (MET DST) Message-ID: <19970405080834.AH60250@uriah.heep.sax.de> Date: Sat, 5 Apr 1997 08:08:34 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: ejc@bazzle.com (Eric J. Chet) Subject: Re: ahc errors after lite2 upgrade References: <199704050346.UAA09792@pluto.plutotech.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199704050346.UAA09792@pluto.plutotech.com>; from Justin T. Gibbs on Apr 4, 1997 20:43:43 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Justin T. Gibbs wrote: > This is your drive trying to tell you that it is starting to go bad. It > had to retry a few times in order to get either a read or write to complete > successfully. But since these are recovered errors, it means turning on ARRE should help. (It's on mode page 1, Eric. RTFM scsi(8)) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Apr 7 04:29:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA09248 for freebsd-scsi-outgoing; Mon, 7 Apr 1997 04:29:34 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09242 for ; Mon, 7 Apr 1997 04:29:31 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by who.cdrom.com (8.8.5/8.6.11) with SMTP id EAA29436 for ; Mon, 7 Apr 1997 04:29:27 -0700 (PDT) Received: from synge.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa22426; 7 Apr 97 12:27 +0100 To: freebsd-scsi@freebsd.org Subject: Re: SCSI freezes in 2.2-STABLE In-reply-to: Your message of "Sun, 06 Apr 1997 00:58:21 BST." <9704060058.aa08317@salmon.maths.tcd.ie> Date: Mon, 07 Apr 1997 12:27:40 +0100 From: David Malone Message-ID: <9704071227.aa22426@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'll grab the delta as soon as it appears. I've tried the a kernel from source code CVSup'ed at 9am GMT this moring ( 7/4/97 ), and we're still getting hangs when we restart news. It didn't produce any log messages this time either. If it produces any more info I'll send it on. David. From owner-freebsd-scsi Mon Apr 7 11:45:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA01826 for freebsd-scsi-outgoing; Mon, 7 Apr 1997 11:45:28 -0700 (PDT) Received: from gnomme.pjwstk.waw.pl (gnomme.pjwstk.waw.pl [195.116.101.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA01816 for ; Mon, 7 Apr 1997 11:45:25 -0700 (PDT) Received: from inwar2.pjwstk.waw.pl (dhcp-59.pjwstk.waw.pl [195.116.101.59]) by gnomme.pjwstk.waw.pl (8.8.5/8.8.5) with SMTP id UAA29849 for ; Mon, 7 Apr 1997 20:46:44 +0200 (MET DST) Message-ID: <334940D5.22A8@pjwstk.waw.pl> Date: Mon, 07 Apr 1997 20:45:41 +0200 From: Grzegorz Dobrowolski X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: 2.2.1 - problem with adaptec aic7770 ? Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hej I have scsi aic7770 controler and it have worked perfectly with 2.1.(5-7), but I have a problem with 2.2.1-RELEASE. When I make intensive I/o operation ( like backup ) i get a message like this: sd0(ahc0:0:0):SCB 0x1 - timed out in datain phase. SCSISIGI == 0x44 SEQ ADDR == 0x12e sd0(ahc0:0:0):abort message in message buffer sd0(ahc0:0:0):SCB 0x0 - timed out while recovery in progress sd0(ahc0:0:0):SCB 0x1 - timed out in datain phase. SCSISIGI == 0x54 SEQ ADDR == 0x12d and after this message the system is halted. Could anyone tell me what to do? Thanks Greg From owner-freebsd-scsi Mon Apr 7 12:25:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA03853 for freebsd-scsi-outgoing; Mon, 7 Apr 1997 12:25:21 -0700 (PDT) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03842; Mon, 7 Apr 1997 12:25:09 -0700 (PDT) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id WAA25636; Mon, 7 Apr 1997 22:25:27 +0300 (EEST) Date: Mon, 7 Apr 1997 22:25:27 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Satoshi Asami , se@freebsd.org cc: hackers@freebsd.org, scsi@freebsd.org Subject: Intel XXpress again (was: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-Reply-To: Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi again, sorry for "replying" to my own message, but now the possibility of FreeBSD-2.2.1 to occupy this Big Box forever has grown to almost 100%... if only I knew the way to get FreeBSD recognize 2 PCI busses. :(( HEEEELP!!!! :) On Wed, 2 Apr 1997, Andrew Stesin wrote: > On Wed, 2 Apr 1997, Satoshi Asami wrote: > > > * 3. 2.2.1 has some problem with two PCI busses? (while both AICs are > > * on the second bus??? or on EISA???) What I see at boot > > * after the "Probing devices on the pci:0 bus" message: > > > > It might be that it can't recognize the PCI-PCI bridge. What do the > > markings on the chip say? I know FreeBSD can deal with DEC and IBM > > chips. > > Unfortunately (or vice versa? ;) I have no access to the > box' internals, I'm not authorized to open the case > and look inside. But: the box is "genuine Intel", > the model is Magellan W/15", base board (kinda of > backplane) is XXpress 15" Rel 2, with 1 P166 CPU module. > > I'll try to find what the bridge chip is. Now I can tell you what are the major (just biggest ones :) chips on the backplane, all have "INTEL" on them: 1. PCIset S82374SB (I suspice that this chip is a clue..) 2. PCIset S82375SB (gets recognized as 82375EB? EISA works anyway) 3. A|M|I 9637LZR (chip is (c)1994 Intel, no idea what's it) 4. XPC 637909-001 (no idea) 5. XPD 637910-001 2 parts (no idea) ... and Adaptec: 6. AIC-7870 2 parts (we all know them :) > > Boot with "-v" and send the output to se@freebsd.org. Just now I'm trying to boot a GENERIC with the increased size of vty' history buffer -- otherwise no way to catch all the messages esp. with "-v", PCI ones fly away, too many of them. Unfortunately, building a "true" FreeBSD boot floppy isn't so trivial. :( So no success yet... > > You may want to > > hack /sys/pci/pcisupport.c by yourself (grep for "IBM") to see if you > > can get it to work. I'm considering this, but I don't trust my own skills of hacking pretty unfamiliar kernel code to get production system running in 2-3 days... I still hope that there already is a solution... Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-scsi Tue Apr 8 00:28:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA21462 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 00:28:13 -0700 (PDT) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA21457 for ; Tue, 8 Apr 1997 00:28:08 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id KAA00538; Tue, 8 Apr 1997 10:28:05 +0300 (EEST) Date: Tue, 8 Apr 1997 10:28:05 +0300 (EEST) Message-Id: <199704080728.KAA00538@silver.sms.fi> From: Petri Helenius To: freebsd-scsi@freebsd.org CC: gibbs@plutotech.org Subject: Latest round around the AIC7xxx Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My system synced at: FreeBSD silver.sms.fi 2.2-STABLE FreeBSD 2.2-STABLE #0: Mon Apr 7 23:03:24 EEST 1997 pete@silver.sms.fi:/usr/src/sys/compile/SILVER i386 Spits out the following when I use CDD: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x9 Queuing an abort SCB Abort message sent SCB 0 - Abort completed panic: Couldn't find busy SCB And obviously reboots shortly after.... Any clues here? It's again different from previous round :-) (that is code about a week before) Pete From owner-freebsd-scsi Tue Apr 8 01:33:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA25083 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 01:33:23 -0700 (PDT) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25075 for ; Tue, 8 Apr 1997 01:33:16 -0700 (PDT) Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie via local-salmon id aa02376; 8 Apr 97 9:33 +0100 To: freebsd-scsi@freebsd.org Subject: Re: Latest round around the AIC7xxx In-reply-to: Your message of "Tue, 08 Apr 1997 10:28:05 +0300." <199704080728.KAA00538@silver.sms.fi> Date: Tue, 08 Apr 1997 09:33:12 +0100 From: David Malone Message-ID: <9704080933.aa02376@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We got a three crashes last night after moving to the most recent version ( cvsup'ed last night - it hasn't changes since then I think ). I've included the log messages from the first two. The last one was some sort of silent reboot, which never came back up again ( I think it was stuck at the bit where the card's BIOS stuff is installed, but the graphics card was in a funny mode so I can't tell ). As someone else pointed we are using CCD for a news spool disk, if this can possibly be related. We're using it with the CCD_OFFSET=0 flag, which should be OK, as neither of the partitions used are at the start of the disk. Also all the hassel we've got log messages for has been on the second controler. Though as /var/ is on the first controler I guess we wouldn't see any messages if that got stuck. David. =============================================================================== Apr 7 23:33:33 synge /kernel: ahc1:A:1: no active SCB for reconnecting target - issuing ABORT Apr 7 23:33:33 synge /kernel: SAVED_TCL == 0x10 Apr 7 23:33:34 synge /kernel: ahc1:A:0: no active SCB for reconnecting target - issuing ABORT Apr 7 23:33:34 synge /kernel: SAVED_TCL == 0x10 Apr 7 23:33:34 synge /kernel: ahc1:A:0: Target did not send an IDENTIFY message . LASTPHASE = 0xc0, SAVED_TCL == 0x10 Apr 7 23:33:34 synge /kernel: ahc1: Issued Channel A Bus Reset. 4 SCBs aborted Apr 7 23:33:34 synge /kernel: Clearing bus reset Apr 7 23:33:34 synge /kernel: Clearing 'in-reset' flag Apr 7 23:33:34 synge /kernel: sd8(ahc1:0:0): UNIT ATTENTION asc:29,0 Apr 7 23:33:34 synge /kernel: sd8(ahc1:0:0): Power on, reset, or bus device re set occurred field replaceable unit: 14 Apr 7 23:33:34 synge /kernel: , retries:3 =============================================================================== Scecond one: =============================================================================== Apr 8 00:17:07 synge /kernel: ahc1:A:1: no active SCB for reconnecting target - issuing ABORT Apr 8 00:17:07 synge /kernel: SAVED_TCL == 0x10 Apr 8 00:17:17 synge /kernel: sd9(ahc1:1:0): SCB 0x2 - timed out in message out phase, SCSISIGI == 0x0 Apr 8 00:17:17 synge /kernel: SEQADDR == 0x99 Apr 8 00:17:17 synge /kernel: sd9(ahc1:1:0): abort message in message buffer Apr 8 00:17:17 synge /kernel: sd8(ahc1:0:0): SCB 0x0 timedout while recovery in progress Apr 8 00:17:17 synge /kernel: sd9(ahc1:1:0): SCB 0x2 - timed out in message out phase, SCSISIGI == 0x0 Apr 8 00:17:17 synge /kernel: SEQADDR == 0x99 Apr 8 00:17:17 synge /kernel: ahc1: Issued Channel A Bus Reset. 4 SCBs aborted Apr 8 00:17:17 synge /kernel: Clearing bus reset Apr 8 00:17:18 synge /kernel: Clearing 'in-reset' flag Apr 8 00:17:18 synge /kernel: sd9(ahc1:1:0): no longer in timeout Apr 8 00:17:18 synge /kernel: sd8(ahc1:0:0): UNIT ATTENTION asc:29,0 Apr 8 00:17:18 synge /kernel: sd8(ahc1:0:0): Power on, reset, or bus device re set occurred field replaceable unit: 14 Apr 8 00:17:18 synge /kernel: , retries:3 =============================================================================== From owner-freebsd-scsi Tue Apr 8 09:26:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA16617 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 09:26:32 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16605 for ; Tue, 8 Apr 1997 09:26:28 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id KAA25178; Tue, 8 Apr 1997 10:26:15 -0600 (MDT) Message-Id: <199704081626.KAA25178@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Petri Helenius cc: gibbs@plutotech.com, scsi@FreeBSD.org Subject: Re: Latest round around the AIC7xxx In-reply-to: Your message of "Tue, 08 Apr 1997 10:41:15 +0300." <199704080741.KAA00570@silver.sms.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Apr 1997 10:24:35 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Okay, I have a fix for that panic, but I'm still looking for reasons leading to the original timeout. >panic: Couldn't find busy SCB -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Apr 8 11:58:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA23870 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 11:58:04 -0700 (PDT) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23865 for ; Tue, 8 Apr 1997 11:57:59 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id VAA02087; Tue, 8 Apr 1997 21:57:49 +0300 (EEST) Date: Tue, 8 Apr 1997 21:57:49 +0300 (EEST) Message-Id: <199704081857.VAA02087@silver.sms.fi> From: Petri Helenius To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Latest round around the AIC7xxx In-Reply-To: <199704081626.KAA25178@pluto.plutotech.com> References: <199704080741.KAA00570@silver.sms.fi> <199704081626.KAA25178@pluto.plutotech.com> Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > Okay, I have a fix for that panic, but I'm still looking for reasons > leading to the original timeout. > > >panic: Couldn't find busy SCB > That might be easier to figure out when the system does not panic when the error occurs. Is the fix committed to 2.2-STABLE? I could cvsup my tree and build a new kernel and test it. Pete From owner-freebsd-scsi Tue Apr 8 15:00:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA04628 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 15:00:39 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-15.ix.netcom.com [199.35.213.207]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04600; Tue, 8 Apr 1997 15:00:16 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id OAA27677; Tue, 8 Apr 1997 14:58:31 -0700 (PDT) Date: Tue, 8 Apr 1997 14:58:31 -0700 (PDT) Message-Id: <199704082158.OAA27677@silvia.HIP.Berkeley.EDU> To: stesin@gu.net CC: se@freebsd.org, hackers@freebsd.org, scsi@freebsd.org, davidg@freebsd.org In-reply-to: (message from Andrew Stesin on Mon, 7 Apr 1997 22:25:27 +0300 (EEST)) Subject: Re: Intel XXpress again (was: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Hi again, * * sorry for "replying" to my own message, but now the possibility * of FreeBSD-2.2.1 to occupy this Big Box forever has grown to almost * 100%... if only I knew the way to get FreeBSD recognize 2 PCI busses. :(( * * HEEEELP!!!! :) I wonder if DavidG on the lists. * Now I can tell you what are the major (just biggest ones :) * chips on the backplane, all have "INTEL" on them: * * 1. PCIset S82374SB (I suspice that this chip is a clue..) * 2. PCIset S82375SB (gets recognized as 82375EB? EISA works anyway) I think the "823*B" chips are PCI- bridges. The one I have says: chip1 rev 1 on pci0:1:0 chip2 rev 0 on pci0:1:1 (It is only one chip.) * 3. A|M|I 9637LZR (chip is (c)1994 Intel, no idea what's it) * 4. XPC 637909-001 (no idea) * 5. XPD 637910-001 2 parts (no idea) Justin suggested the motherboard may have two host-PCI bridges, so maybe these are those. * Just now I'm trying to boot a GENERIC with the increased size * of vty' history buffer -- otherwise no way to catch * all the messages esp. with "-v", PCI ones fly away, * too many of them. Unfortunately, building a "true" * FreeBSD boot floppy isn't so trivial. :( So no success yet... Can you get it to a point that it can run "dmesg"? * I'm considering this, but I don't trust my own skills of * hacking pretty unfamiliar kernel code to get production * system running in 2-3 days... I still hope that there already is * a solution... Well, let's see if David can help you. Satoshi From owner-freebsd-scsi Tue Apr 8 17:23:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14815 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 17:23:30 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14807; Tue, 8 Apr 1997 17:23:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA21738; Wed, 9 Apr 1997 09:52:57 +0930 (CST) From: Michael Smith Message-Id: <199704090022.JAA21738@genesis.atrad.adelaide.edu.au> Subject: Re: Intel XXpress again (was: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-Reply-To: from Andrew Stesin at "Apr 7, 97 10:25:27 pm" To: stesin@gu.net Date: Wed, 9 Apr 1997 09:52:57 +0930 (CST) Cc: asami@vader.cs.berkeley.edu, se@freebsd.org, hackers@freebsd.org, scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andrew Stesin stands accused of saying: > > sorry for "replying" to my own message, but now the possibility > of FreeBSD-2.2.1 to occupy this Big Box forever has grown to almost > 100%... if only I knew the way to get FreeBSD recognize 2 PCI busses. :(( It should anyway - you want Stefan Esser's phone number though 8) > Now I can tell you what are the major (just biggest ones :) > chips on the backplane, all have "INTEL" on them: > > 1. PCIset S82374SB (I suspice that this chip is a clue..) That's almost certainly the PCI interface and PCI/ISA bridge. > 2. PCIset S82375SB (gets recognized as 82375EB? EISA works anyway) Yup, EISA bridge. > 3. A|M|I 9637LZR (chip is (c)1994 Intel, no idea what's it) That's probably the BIOS with an American Megatrends logo on it 8) > 4. XPC 637909-001 (no idea) > 5. XPD 637910-001 2 parts (no idea) Um, they sound a lot like FPGA or some other gate array parts. Do they have logos on them? > Just now I'm trying to boot a GENERIC with the increased size > of vty' history buffer -- otherwise no way to catch > all the messages esp. with "-v", PCI ones fly away, > too many of them. Unfortunately, building a "true" > FreeBSD boot floppy isn't so trivial. :( So no success yet... Stick a serial cable on com1 leading to another machine, and use the '-hv' boot flags to get it to use the serial console. > I'm considering this, but I don't trust my own skills of > hacking pretty unfamiliar kernel code to get production > system running in 2-3 days... I still hope that there already is > a solution... 2-3 days on a new platform? Is this your timeframe or your customer's? Whoever, they gotta be _nuts_! > Andrew Stesin -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Tue Apr 8 17:24:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14978 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 17:24:53 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14973 for ; Tue, 8 Apr 1997 17:24:50 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id SAA29661; Tue, 8 Apr 1997 18:24:46 -0600 (MDT) Message-Id: <199704090024.SAA29661@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Petri Helenius cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Latest round around the AIC7xxx In-reply-to: Your message of "Tue, 08 Apr 1997 21:57:49 +0300." <199704081857.VAA02087@silver.sms.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Apr 1997 18:23:03 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Justin T. Gibbs writes: > > Okay, I have a fix for that panic, but I'm still looking for reasons > > leading to the original timeout. > > > > >panic: Couldn't find busy SCB > > >That might be easier to figure out when the system does not panic when >the error occurs. > >Is the fix committed to 2.2-STABLE? I could cvsup my tree and build a >new kernel and test it. > >Pete No. It won't be fixed until I get back in town late tomorrow. I don't think that fixing the panic will give any indication of why the timeout is occurring though. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Apr 8 22:05:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA26160 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 22:05:56 -0700 (PDT) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26154 for ; Tue, 8 Apr 1997 22:05:53 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id IAA24321; Wed, 9 Apr 1997 08:05:45 +0300 (EEST) Date: Wed, 9 Apr 1997 08:05:45 +0300 (EEST) Message-Id: <199704090505.IAA24321@silver.sms.fi> From: Petri Helenius To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Latest round around the AIC7xxx In-Reply-To: <199704090024.SAA29661@pluto.plutotech.com> References: <199704081857.VAA02087@silver.sms.fi> <199704090024.SAA29661@pluto.plutotech.com> Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > > No. It won't be fixed until I get back in town late tomorrow. I don't > think that fixing the panic will give any indication of why the timeout is > occurring though. > But it will allow collection of error messages and other information (SCSI debugging) without having to type in the collected information from panicked console... Pete From owner-freebsd-scsi Wed Apr 9 04:28:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA13558 for freebsd-scsi-outgoing; Wed, 9 Apr 1997 04:28:27 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA13551; Wed, 9 Apr 1997 04:28:19 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-8.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA12295 (5.67b/IDA-1.5); Wed, 9 Apr 1997 13:28:16 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA02904; Wed, 9 Apr 1997 13:02:00 +0200 (CEST) Message-Id: <19970409130200.12143@x14.mi.uni-koeln.de> Date: Wed, 9 Apr 1997 13:02:00 +0200 From: Stefan Esser To: stesin@gu.net Cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.68 In-Reply-To: ; from Andrew Stesin on Wed, Apr 02, 1997 at 01:03:25PM +0300 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Apr 2, Andrew Stesin wrote: Sorry for the late reply, I just returned from a vacation ... > The box: Intel XXpress-, 2 AIC7870 chips onboard, EISA bus present. Is this a Pentium or PPro system ? > neither of AICs are recognized at boot. ??? I have the following guesses: > > 1. neither of the 2 SCSI busses has anything attached yet (disk drives will > come in a day or two, they ordered drives separately, and no Wide > drives here to try). Should not cause any trouble ... > 3. 2.2.1 has some problem with two PCI busses? (while both AICs are > on the second bus??? or on EISA???) What I see at boot > after the "Probing devices on the pci:0 bus" message: > > chip0 \ > rev 2 on pci0:0 > chip1 rev 5 on pci0:14 > pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ > [no driver assigned] > .....^^^^.... > This last message is repeated exactly for all pci0:15:[0-7] > values. This may be caused by (incorrectly) assuming, that chip was a multi-function device. This does not cause any problems, though ... > What I am missing? Any comments and explanations are appreciated! Seems you have some way of obtaining the boot message log. Could you please provide me with VERBOSE boot messages ? (Eenter "-v" at the "Boot: " prompt.) The problem you are facing comes from the fact, that PCI specifies a single bus directly attached to the CPU, and a tree structure of seconfary buses connected to it. Since this limits the number of low-latency slots to at most 5, server machines often come with more than one bus directly attached to the CPU. But there is no standard way of telling, how many buses are actually connected to a CPU (1 is assumed), and while the bus numbers behing PCI to PCI bridges can be determined in a chip-independent way, this is not possible in the case of multiple CPU to PCI chips. Device specific code has to be added for each of them. (The information on the number of buses can be queried by calling the PCI BIOS, but I'd prefer, if I not have to, for a number of reasons ...) I need more information on the chip set used on that mother board. The Orion should be supported out of the box, but if this is a system with multiple PCI buses directly attached to the CPU based on some other chip set, a small addition to the PCI probe code will be required. Regards, STefan From owner-freebsd-scsi Wed Apr 9 14:19:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA18704 for freebsd-scsi-outgoing; Wed, 9 Apr 1997 14:19:08 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18679; Wed, 9 Apr 1997 14:18:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id OAA22425; Wed, 9 Apr 1997 14:18:41 -0700 (PDT) Message-Id: <199704092118.OAA22425@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: stesin@gu.net, se@freebsd.org, hackers@freebsd.org, scsi@freebsd.org Subject: Re: Intel XXpress again (was: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-reply-to: Your message of "Tue, 08 Apr 1997 14:58:31 PDT." <199704082158.OAA27677@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: dg@root.com Date: Wed, 09 Apr 1997 14:18:41 -0700 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * I'm considering this, but I don't trust my own skills of > * hacking pretty unfamiliar kernel code to get production > * system running in 2-3 days... I still hope that there already is > * a solution... > >Well, let's see if David can help you. I am, of course. I've attached the fix I used on the Intel Alder box, but I don't know if the patch will even apply cleanly anymore...so you might have to do this by hand. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project Index: pci.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pci.c,v retrieving revision 1.23.4.5 diff -c -r1.23.4.5 pci.c *** 1.23.4.5 1996/01/19 19:21:03 --- pci.c 1996/01/30 08:18:14 *************** *** 158,163 **** --- 158,173 ---- 0x4000000, 0xFFFFFFFFu, /* nonprefetch membase/limit */ 0x4000000, 0xFFFFFFFFu /* prefetch membase/limit */ }; + #define SECOND_BUS 1 + static struct pcicb pcibus1 = { + NULL, NULL, NULL, + { 0 }, + 0, SECOND_BUS, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0, /* real allocation */ + 0, 0xFFFF, /* iobase/limit */ + 0x2000000, 0xFFFFFFFFu, /* nonprefetch membase/limit */ + 0x2000000, 0xFFFFFFFFu /* prefetch membase/limit */ + }; static struct pcicb *pcicb; /*======================================================== *************** *** 207,212 **** --- 217,238 ---- if (pcicb) pcicb = pcicb->pcicb_next; } + #if 1 + for (pcicb = &pcibus1; pcicb != NULL;) { + pci_bus_config (); + + if (pcicb->pcicb_down) { + pcicb = pcicb->pcicb_down; + continue; + }; + + while (pcicb && !pcicb->pcicb_next) + pcicb = pcicb->pcicb_up; + + if (pcicb) + pcicb = pcicb->pcicb_next; + } + #endif pci_conf_count++; } From owner-freebsd-scsi Thu Apr 10 00:56:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA22589 for freebsd-scsi-outgoing; Thu, 10 Apr 1997 00:56:18 -0700 (PDT) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA22584; Thu, 10 Apr 1997 00:56:08 -0700 (PDT) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id KAA09186; Thu, 10 Apr 1997 10:57:04 +0300 (EEST) Date: Thu, 10 Apr 1997 10:57:04 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Stefan Esser cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-Reply-To: <19970409130200.12143@x14.mi.uni-koeln.de> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello Stefan, On Wed, 9 Apr 1997, Stefan Esser wrote: > > Sorry for the late reply, I just returned from a vacation ... > Stefan, thanks for replying at all, don't make my cheeks shine red with the above disclaimer :) > > The box: Intel XXpress-, 2 AIC7870 chips onboard, EISA bus present. > > Is this a Pentium or PPro system ? "Normal" Pentium. 1 CPU module, P5/166. > > What I am missing? Any comments and explanations are appreciated! > > Seems you have some way of obtaining the boot message log. > Could you please provide me with VERBOSE boot messages ? > (Eenter "-v" at the "Boot: " prompt.) I was a bit ill for last few days, wasn't able to do anything creative then... now I feel myself much better, will do this todays evening. > The problem you are facing comes from the fact, that PCI > specifies a single bus directly attached to the CPU, and > a tree structure of seconfary buses connected to it. > Since this limits the number of low-latency slots to at > most 5, server machines often come with more than one bus > directly attached to the CPU. Seems this is exactly what Intel did... > But there is no standard way > of telling, how many buses are actually connected to a CPU > (1 is assumed), and while the bus numbers behing PCI to PCI > bridges can be determined in a chip-independent way, this > is not possible in the case of multiple CPU to PCI chips. > Device specific code has to be added for each of them. What I'm able to tell you for sure is that RedHat Linux 4.1 installation floppies are seeing AICs (and disks) and using them; while FreeBSD-2.2.1 doesn't. > (The information on the number of buses can be queried by > calling the PCI BIOS, but I'd prefer, if I not have to, > for a number of reasons ...) > > I need more information on the chip set used on that mother > board. The Orion should be supported out of the box, but if > this is a system with multiple PCI buses directly attached > to the CPU based on some other chip set, a small addition > to the PCI probe code will be required. I'll set up a serial console and send a boot -v for this box to you this evening. > > Regards, STefan > Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-scsi Thu Apr 10 06:31:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA05011 for freebsd-scsi-outgoing; Thu, 10 Apr 1997 06:31:02 -0700 (PDT) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA05004; Thu, 10 Apr 1997 06:30:52 -0700 (PDT) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id QAA10649; Thu, 10 Apr 1997 16:31:50 +0300 (EEST) Date: Thu, 10 Apr 1997 16:31:50 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Stefan Esser cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-Reply-To: Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Stefan, as I told you earlier today, > I'll set up a serial console and send a boot -v > for this box to you this evening. here it goes. [... boot prompt, "uncompressing kernel", userconfig, [Q] ...] avail memory = 61059072 (59628K bytes) eisa0: Probing for devices on the EISA bus pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x80007804 pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=12258086) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 2 on \ pci0:0 vx0 <3COM 3C900 Etherlink XL PCI> rev 0 int a irq 10 on pci0:12 mapreg[10] type=1 addr=0000ef00 size=0040. utp/aui/bnc[*utp*]: disable 'auto select' with DOS util! \ address 00:60:97:25:f7:47 chip1 rev 5 on pci0:14:0 pci0:15:0: Intel Corporation, device=0x0008, class=0xff, subclass=0x00 \ [no driver assigned] map(10): mem32(ffe6fc08) map(14): mem32(ffe6fc08) map(18): mem32(ffe6fc08) map(1c): mem32(ffe6fc08) map(20): mem32(ffe6fc08) map(24): mem32(ffe6fc08) pci0:15:1: Intel Corporation, device=0x0008, class=0xff, subclass=0x00 \ [no driver assigned] map(10): mem32(ffe6fc08) map(14): mem32(ffe6fc08) map(18): mem32(ffe6fc08) map(1c): mem32(ffe6fc08) map(20): mem32(ffe6fc08) map(24): mem32(ffe6fc08) [... absolutely the same output follows for pci0:15:[2-7] ...] pci0: uses 64 bytes of I/O space from ef00 upto ef3f. Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0065 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard [... and pretty usual ISA stuff, than sysinstall menu screen ...] Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-scsi Thu Apr 10 07:25:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA08197 for freebsd-scsi-outgoing; Thu, 10 Apr 1997 07:25:03 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08184 for ; Thu, 10 Apr 1997 07:24:52 -0700 (PDT) Received: (from bsdstab@localhost) by shadows.aeon.net (8.8.5/8.8.3) id RAA18325 for scsi@freebsd.org; Thu, 10 Apr 1997 17:23:23 +0300 (EET DST) Message-Id: <199704101423.RAA18325@shadows.aeon.net> Subject: scsi error To: scsi@freebsd.org Date: Thu, 10 Apr 1997 17:23:23 +0300 (EET DST) From: bsdscsi@aeon.net (mika ruohotie) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk should i assume my drive is broken? (was flooded with these when running bonnie on 4 drive ccd filesystem) Apr 10 17:05:40 pluto /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:90065 asc:13,0 Address mark not found for data field sks:80,22 Apr 10 17:05:40 pluto /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:90065 asc:13,0 Address mark not found for data field sks:80,22 Apr 10 17:05:40 pluto /kernel: , FAILURE Apr 10 17:05:40 pluto /kernel: , FAILURE and i got it every time running bonnie in 2040 meg filesystem, if i tell bonnie to use file size over 512 megs (next one i tried was 990 megs) system is latest cvsup:ed 2.1-STABLE (as of apr 9th 1pm GMT) i use adaptec 2940UW, fujitsu 2gig ultra drives. (same server i had 3940UW but had to take it out coz of errors worse than that) machine didnt lock up or anything. mickey From owner-freebsd-scsi Thu Apr 10 13:39:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28661 for freebsd-scsi-outgoing; Thu, 10 Apr 1997 13:39:33 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA28651 for ; Thu, 10 Apr 1997 13:39:30 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04091; Thu, 10 Apr 1997 22:39:24 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.8.5/8.8.5) id WAA00676; Thu, 10 Apr 1997 22:26:17 +0200 (CEST) Message-ID: <19970410222613.AW12587@jette.heep.sax.de> Date: Thu, 10 Apr 1997 22:26:13 +0200 From: j@jette.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: bsdscsi@aeon.net (mika ruohotie) Subject: Re: scsi error References: <199704101423.RAA18325@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199704101423.RAA18325@shadows.aeon.net>; from mika ruohotie on Apr 10, 1997 17:23:23 +0300 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > should i assume my drive is broken? > Apr 10 17:05:40 pluto /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:90065 asc:13,0 Address mark not found for data field sks:80,22 Yep. Low-level format it (/sbin/scsiformat). -- bye, J"org ...just travelling around. Don't try reaching me except by mail. :) From owner-freebsd-scsi Thu Apr 10 15:29:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA04506 for freebsd-scsi-outgoing; Thu, 10 Apr 1997 15:29:29 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04496 for ; Thu, 10 Apr 1997 15:29:26 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id QAA12423; Thu, 10 Apr 1997 16:29:15 -0600 (MDT) Message-Id: <199704102229.QAA12423@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: bsdscsi@aeon.net (mika ruohotie) cc: scsi@FreeBSD.ORG Subject: Re: scsi error In-reply-to: Your message of "Thu, 10 Apr 1997 17:23:23 +0300." <199704101423.RAA18325@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Apr 1997 16:27:43 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >i use adaptec 2940UW, fujitsu 2gig ultra drives. (same server i had 3940UW >but had to take it out coz of errors worse than that) You mentioned before of problems with the 3940. They seem to work fine. The only difference I know of between the 3940 and the 2940 is that on systems that don't properly setup the bridge chip, you must use PIO (i.e. don't put AHC_ALLOW_MEMIO in your kernel config file). This "caveat" is documented in the ahc.4 man page. >mickey -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Apr 12 08:39:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA07756 for freebsd-scsi-outgoing; Sat, 12 Apr 1997 08:39:36 -0700 (PDT) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA07744 for ; Sat, 12 Apr 1997 08:39:21 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id TAA00348; Sat, 12 Apr 1997 19:38:54 +0300 (EEST) Date: Sat, 12 Apr 1997 19:38:54 +0300 (EEST) Message-Id: <199704121638.TAA00348@silver.sms.fi> From: Petri Helenius To: scsi@freebsd.org CC: gibbs@plutotech.com Subject: latest round around the aic7xxx Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've: FreeBSD silver.sms.fi 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri Apr 11 20:39:10 EEST 1997 pete@silver.sms.fi:/usr/src/sys/compile/SILVER i386 And the latest gives me: cd0(ahc 0:6:0) SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x4 cd0(ahc0:6:0): Queuing an abort SCB cd0(ahc0:6:0): Abort message sent cd0(ahc0:6:0): SCB 0 - Abort completed panic: Couldn't find busy SCB syncing disks... ahc0: Unexpected busfree LASTPHASE == 0xa0 SEQADDR == 0xa1 Timed out SCB handled by another timeout sd0(ahc0:0:0) SCB 0x5 timed out while recovery in process sd0(ahc0:0:0) SCB 0x5 timed out while recovery in process ...So the panic changed a little but didn't go away... Pete