From owner-freebsd-questions Wed Apr 23 21:42:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA15098 for questions-outgoing; Wed, 23 Apr 1997 21:42:32 -0700 (PDT) Received: from milehigh.denver.net (jdc@milehigh.denver.net [204.144.180.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA15093; Wed, 23 Apr 1997 21:42:30 -0700 (PDT) Received: (from jdc@localhost) by milehigh.denver.net (8.6.12/8.6.12) id WAA05508; Wed, 23 Apr 1997 22:45:05 -0600 Date: Wed, 23 Apr 1997 22:45:05 -0600 (MDT) From: John-David Childs To: Jamie Rishaw cc: freebsd-questions@freebsd.org, freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Repeated Crashes, news server - SCSI Probs? In-Reply-To: <199704240213.WAA15041@dilbert.iagnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had the same problem with the Adaptec 2940 UW Controller. Jordan and others suggested upgrading to 2.2-REL-ENGINEERING (however that's actually spelled ;). It does seem to have helped SIGNIFICANTLY! I ended up booting from a 2.2-RELEASE-ENG floppy and starting all over, but it was worth it to get rid of the random reboots. -- On Wed, 23 Apr 1997, Jamie Rishaw wrote: > Hi, > > I've been having a problem with one of the FreeBSD machines on our > network. It's the news server.. > > Sorry for the crosspost, btw. > > Up until today it was a Cyrix 6x86 with 128M RAM, yada yada.. today's config > is: > > - P-Pro 200, TYAN mb, 192Mb RAM > - FreeBSD 2.1.7-RELEASE > - Adaptec AHA-2940 Ultra/Ultra W BIOS v1.21 > - 2x9GB ST410800W (News spool) > - Generic 500Mb, Generic 600Mb quantum HD (IDE) (System) > - 2x3COM 3C590 Etherlink III PCI rev 0 int a > > It seems that the server doesn't like to stay online for more than a day > or so before rebooting. This has been the symptom since the day I rescued the > poor server from a life of servitude and slavery running an evil Micros*** > product. No worry, I formatted the disks thrice. :-) > > I'm looking at the messages file (I have them locally and across the network) > and this is the last thing I see before a reboot: > > Apr 21 17:11:00 iagnews /kernel: sd1(ahc0:2:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Apr 21 17:11:00 iagnews /kernel: SEQADDR == 0x8 > (reboot) > Apr 23 13:21:07 iagnews /kernel: sd1(ahc0:2:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Apr 23 13:21:07 iagnews /kernel: SEQADDR == 0xd > (reboot) > Apr 23 17:12:13 iagnews /kernel: sd1(ahc0:2:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Apr 23 17:12:13 iagnews /kernel: SEQADDR == 0xc > (reboot) > Apr 23 19:32:56 iagnews /kernel: sd1(ahc0:2:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Apr 23 19:32:56 iagnews /kernel: SEQADDR == 0xc > John-David Childs (JC612) http://www.denver.net System Administrator jdc@denver.net & Network Engineer Think, Listen, Look, then ACT! "A verbal contract isn't worth the paper it's written on" - Louis B Mayer