From owner-freebsd-questions Thu Mar 6 17:21:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA28360 for questions-outgoing; Thu, 6 Mar 1997 17:21:16 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA28264 for ; Thu, 6 Mar 1997 17:20:38 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA13109; Thu, 6 Mar 1997 20:20:05 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 6 Mar 1997 20:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id TAA16280; Thu, 6 Mar 1997 19:59:08 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA08869; Thu, 6 Mar 1997 20:04:53 -0500 (EST) Date: Thu, 6 Mar 1997 20:04:53 -0500 (EST) From: Thomas David Rivers Message-Id: <199703070104.UAA08869@lakes.water.net> To: ponds!eeyore.lv-hrc.nevada.edu!doon, ponds!time.cdrom.com!jhk Subject: Re: 2.1.5->2.1.7 causes SCSI errors? Cc: ponds!freebsd.org!freebsd-questions, ponds!frii.com!gnat Content-Type: text Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan writes: > You guys just need to update your firmware (at least this is > a definite in Nathan's case). The modern driver takes more advantage > these drives, and firmware bugs in the earlier revisions of them > cause problems for this code. At the time I reported the problem; (Aug. 1996) someone else made the same suggestion. I called adaptec. They informed me I had (as of that time ) the most recent firmware on my 2940UW there was; there was no updating I could possibly do... The problem was still there. - Dave Rivers - > > ftp.qntm.com > > > I experienced this problem also, but with 2.1.6. Had to dump the 2940 :) > > and use a 1542B Ugh! > > Let ne know if you ever find out what happened! > > > > Thanks > > > > Harry Reed > > > > ---------- > > > From: Nathan Torkington > > > To: freebsd-questions@freebsd.org > > > Subject: 2.1.5->2.1.7 causes SCSI errors? > > > Date: Wednesday, March 05, 1997 9:26 AM > > > > > > Our news machine worked just fine under 2.1.5, but barfed miserably > > > when upgraded to 2.1.7. It reboots about every 20 minutes now. > > > > > > The kernel probe finds the disks: > > > kernel: ahc0 rev 3 int a irq 11 on > > pci0:12 > > > kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs > > > kernel: ahc0 waiting for scsi devices to settle > > > kernel: (ahc0:0:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 > > > kernel: sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) > > > kernel: (ahc0:1:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 > > > kernel: sd1(ahc0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) > > > kernel: (ahc0:2:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 > > > kernel: sd2(ahc0:2:0): Direct-Access 2049MB (4197405 512 byte sectors) > > > kernel: (ahc0:3:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 > > > kernel: sd3(ahc0:3:0): Direct-Access 2049MB (4197405 512 byte sectors) > > > kernel: (ahc0:4:0): "QUANTUM XP34300 F81H" type 0 fixed SCSI 2 > > > kernel: sd4(ahc0:4:0): Direct-Access 4101MB (8399520 512 byte sectors) > > > > > > The messages we get before reboots are: > > > > > > kernel: sd4(ahc0:4:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI > > == 0x0 > > > kernel: SEQADDR == 0x8 > > > kernel: panic: ahc0: Timed-out command times out again > > > kernel: > > > kernel: syncing disks... 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 > > 70 70 70 70 giving up > > > kernel: Automatic reboot in 15 seconds - press a key on the console to > > abort > > > kernel: Rebooting... > > > > > > That disk is part of a large CCD device: > > > ccd0 32 0 /dev/sd1s1 /dev/sd2s1 /dev/sd3s1 > > /dev/sd4s1 > > > > > > I copied the old kernel configuration file from 2.1.5 to 2.1.7 and > > > built and installed it without complaints. I couldn't find anything > > > in the 2.1.7 LINT file to suggest that the format of the SCSI device > > > specification has significantly changed between 2.1.5 and 2.1.7. We > > > haven't seen this behaviour on any of our other 5 servers which I > > > upgraded at the same time and in the same manner (the others don't > > > have ccd or the Quantum drive). > > > > > > What did I do wrong and (more importantly) what do I do to fix it? > > > > > > Thanks, > > > > > > Nat > > > (I'm not a list subscriber, just someone who is following the kernel's > > > instructions and is panicking, so please CC: gnat@frii.com on your > > > replies) > > > > >