Date: Thu, 6 Mar 1997 06:45:36 -0500 (EST) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!eeyore.lv-hrc.nevada.edu!doon, ponds!freebsd.org!freebsd-questions, ponds!frii.com!gnat Subject: Re: 2.1.5->2.1.7 causes SCSI errors? Message-ID: <199703061145.GAA06439@lakes.water.net>
next in thread | raw e-mail | index | archive | help
> > > 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! Yes, I reported this problem when I got my 2940 with a 2.1-STABLE just before 2.1.6(.1) was released. I'm happy to say that I've tested 2.2-GAMMA (around last Jan.) and found that the panic part of the problem had gone away. I still got mysterious messages about restarting the SCSI bus, etc... but the machine recovered. You might also experience spontaneous SCSI lock-outs at that time. You might want to give 2.2-GAMMA a try and see what behaviour you see. Also, a quick perusal of the mail archives (look for SCSI in the subject) will relate my findings. - Dave Rivers - > > Thanks > > Harry Reed > > ---------- > > From: Nathan Torkington <gnat@frii.com> > > 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 <Adaptec 2940 SCSI host adapter> 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) > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703061145.GAA06439>