From owner-aic7xxx Thu Nov 27 05:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23062 for aic7xxx-outgoing; Thu, 27 Nov 1997 05:50:42 -0800 (PST) (envelope-from owner-aic7xxx) Received: from dfunms.rus.uni-stuttgart.de (dfunms.rus.uni-stuttgart.de [129.69.1.162]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23054 for ; Thu, 27 Nov 1997 05:50:37 -0800 (PST) (envelope-from bauer@kirk.lampoldshausen.de) Received: from itsms2.itsm.uni-stuttgart.de (itsms2.itsm.uni-stuttgart.de [129.69.62.7]) by dfunms.rus.uni-stuttgart.de (8.8.7/8.8.7) with SMTP id OAA12425; Thu, 27 Nov 1997 14:50:15 +0100 (MET) env-from (bauer@kirk.lampoldshausen.de) Received: from dial11.rz.fh-heilbronn.de by itsms2.itsm.uni-stuttgart.de via SMTP (/BelWue-2.0SGI) (for jc@info-systems.com) id AA22152; Thu, 27 Nov 97 14:50:07 +0100 Received: (from bauer@localhost) by kirk.lampoldshausen.de (8.8.4/8.8.4) id OAA00411; Thu, 27 Nov 1997 14:47:34 +0100 Message-Id: <199711271347.OAA00411@kirk.lampoldshausen.de> From: Holger Bauer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jakob Curdes Cc: aic7xxx@FreeBSD.ORG Subject: Re: Problems with 7880 and smp system Date: Thu, 27 Nov 1997 14:10:21 +0100 Sender: owner-aic7xxx@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jakob> most 2.0 kernels seem to have deadlock problems with smp, I Jakob> decided to give it a try and switch to the latest Jakob> development kernel. I assume that there these problems are Jakob> fixed ?! But, running on 2.1.66 my system is rather less Jakob> stable than before. I suspect that the scsi driver for my Is your kerneld running? Have you really applied make modules and make install_modules in the /usr/src/linux directory? If you haven't this might explain the missing logs and the occuring deadlocks. I am running a Gigabyte DX586 with kernel version 2.1.23, 2.1.63 and 2.1.65 and have problems if I compile the 2.1.65 kernel with verbose /proc/scsi/aic7xxx/0 reporting mechanism. The first time I apply cat /proc/scsi/aic7xxx/0 I'll get all my setting, everyting is fine. However it might happen that in the middle of another 'cat' browsing the system gets in some deadlock state. Well, I thought I might find out why the MHz-report in the startup process (up to kernel 2.1.2X) disappeared and if I really run my SOOOOOOO Slow Fireball TM3200S in the appropriate mode. I won't try my cat command before I've send out this message :-) though. Anyway, does anybody know, what Nov 27 08:27:16 kirk kernel: aic7xxx: possible overflow at loop 6:8 means? This only occured in kernel 2.1.65 during the startup message and will only be reported to the /var/log/messages file. To come back to the original question. NO, besides the cat problem I've never had any problems with my Dual-Pentium Gigabyte 586 DX SMP setup. Even some people claimed that the two processors should come out of the same series. This is not true in my case. One Intel Pentium 133 in the box and the second plain one bought about 1 year later from a different seller. I'm running our parallel flow simulation package (MPI) on it. Holger