Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Aug 1998 20:17:23 +0200 (CEST)
From:      Søren Schmidt <sos@FreeBSD.ORG>
To:        krygier@kph.uni-mainz.de (Klaus Werner Krygier)
Cc:        freebsd-smp@FreeBSD.ORG
Subject:   Re: system lock-up
Message-ID:  <199808081817.UAA28524@sos.freebsd.dk>
In-Reply-To: <Pine.BSF.3.96.980808190517.411C-100000@krygierpc.kph.uni-mainz.de> from Klaus Werner Krygier at "Aug 8, 98 07:18:22 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Klaus Werner Krygier who wrote:

Hmm, I run two SMP systems here:

2*200Mhz P6 on TYAN S1662D NCR875 SCSI 4Gnarrow 96M
2*233Mhz P6 on TYAN S1668D EIDE UDMA 2*4.3G 1*11.5G 256M

Both systems are rock stable, no bad symptoms whatsoever.

Are you sure your SCSI cables/termination are OK ??


> Hello,
> 
> here is a mail which I posted a few days ago to freebsd-current. I got
> very few answers which didn't help. Perhaps in this mailing list there is
> someone who can help me.
> Do these problems occur only on a few SMP systems?
> Are they specific for Gigabyte boards?
> Which other hardware allows a stable system (like my computer as it worked 
> with a SNAP of May 1997 for about one year)?
> 
> Klaus Werner Krygier
> 
> ---------- Forwarded message ----------
> Date: Thu, 6 Aug 1998 20:58:34 +0200 (CEST)
> From: Klaus Werner Krygier <krygier@kph.uni-mainz.de>
> To: Philippe Regnauld <regnauld@deepo.prosa.dk>
> Cc: freebsd-current@FreeBSD.ORG
> Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates)
> 
> On Sun, 2 Aug 1998, Philippe Regnauld wrote:
> 
> > System: GigaByte 586-DX, 2xP5-133, 48MB, on-board 7880 SCSI,
> >         4GB IBM DCAS-34330W.
> > Current as of CTM src-cur 3477 (< 48 hours).
> > 
> > Softupdates enabled on _all_ filesystems: no problem, did
> > two make buildworlds/installworld in a row, as long
> > as AHC_TAGENABLE is off.
> > 
> > If I enable AHC_TAGENABLE, and push the system a bit (lots
> > of FS activity) -> freeze.  Last time it happened was with X,
> > so I'd have to do it again in text mode to write down the AHC
> > TAG messages...
>  
> I have a very similar hardware setup on several machines (Gigabyte
> 586-DX, 2 x P5-200, 64 MB, on-board 7880 SCSI, several different disks
> (2GB, 4GB, 9GB)) and I have the same problems:
> 
> If I do a lot of disk activity my computers freeze. Sometimes a SCSI
> bus reset seems to be initiated (which I can recogize on the loading
> activity of my CD changer). This problem occurs on standard 3.0-SNAP
> kernels without softupdates and almost SMP-GENERIC configuration. I
> tried several SNAPs, but the problem remained - I have the impression
> it has become worse with newe versions :-(. At last I damaged one of
> my disks.
> 
> My last hope was CAM. Here (3.0CAM-19980712-SNAP) the system does not
> freeze completely but becomes very slow on disk access and is also not
> usable. One positive aspect: I get kernel messages. Every few seconds
> the following message is printed out for ever:
> 
> Timedout SCB handled by another timeout
> Timedout SCB handled by another timeout
> last message repeated 4 times
> last message repeated 13 times
> last message repeated 30 times
> Timedout SCB handled by another timeout
> Timedout SCB handled by another timeout
> 
> etc.
> 
> With older 3.0-SNAPs (e.g. May 97) a SMP system was very stable on my
> first board and did not show such effects for almost a year. Because of
> other problems and to use new features and improvements I had to upgrade
> and have now very instable systems.
> 
> Klaus Werner Krygier
> 
> +-----------------------------------------------------------------------+
> | Dr. Klaus Werner Krygier            | Email: krygier@kph.uni-mainz.de |
> | Institut für Kernphysik             |                                 |
> | Johannes Gutenberg-Universität      | Tel:   +49-6131-39-2960         |
> | J.J.Becher-Weg 45                   |        +49-6131-39-5868         |
> | D-55099 Mainz                       | Fax:   +49-6131-39-2964         |
> +-----------------------------------------------------------------------+
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-smp" in the body of the message
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end?
..

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808081817.UAA28524>