From owner-freebsd-questions Mon Oct 13 08:24:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA00254 for questions-outgoing; Mon, 13 Oct 1997 08:24:48 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from Central.KeyWest.MPGN.COM (Central.TanSoft.COM [208.194.145.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA00239 for ; Mon, 13 Oct 1997 08:24:43 -0700 (PDT) (envelope-from rwm@tansoft.com) Received: from devious.Tansoft.com (Devious.TanSoft.COM [208.194.145.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id LAA25624 for ; Mon, 13 Oct 1997 11:24:11 -0400 Message-Id: <3.0.3.32.19971013112410.00819100@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 13 Oct 1997 11:24:10 -0400 To: freebsd-questions@freebsd.org From: Rob Miracle Subject: Installing 2.2.1 problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just recieved two new pentium II-300's and I am having problems installing FreeBSD on them. They have an Adaptec 2940 Ultra SCSI host adapter with a 4.3gb IBM SCSI drive. It has some 3D graphics adapter and an Intel EtherExpress 10/100+ Ethernet PCI card. The set up is identical to some 8 other boxes we have gotten from this company (SAG). Partially through the CD install I get a message on VT-2 that says: sd0(ahc0:0:0): SCB 0x0 timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SCOADDR == 0x6 sd0(ahc0:0:0): Queueing an Abort SCB and the system locks up. The CD wont even eject when pressing the eject button. It seems to lock up the same place, and its happening on two identical machines and that is about 66 % of they way through the documents being installed. I have had it happen once about 52% into /bin's install, but most of the time and on both boxes it happens at the 66% of the docs. Any clues? We have stayed at 2.2.1 because of a potential shared memory bug in 2.2.2 that causes our very large game app to panic the system. We have never caught the panic and nothing gets logged, though we may be on the trail with a third machine we are installing. Any way, I really can't move forward to 2.2.2 and I am going to try 2.2.5 on one of the machines to see if its something with the 300mhz and the 2.2.1 drivers, but if 2.2.5 has the same reboot bug that 2.2.2 has, I really can't use it. Thanks Rob