From owner-freebsd-current Sun Aug 2 10:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29180 for freebsd-current-outgoing; Sun, 2 Aug 1998 10:21:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29175 for ; Sun, 2 Aug 1998 10:21:04 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id TAA04919; Sun, 2 Aug 1998 19:25:30 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id TAA28979; Sun, 2 Aug 1998 19:26:00 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id TAA28638; Sun, 2 Aug 1998 19:23:27 +0200 (CEST) Message-ID: <19980802192327.02628@deepo.prosa.dk> Date: Sun, 2 Aug 1998 19:23:27 +0200 From: Philippe Regnauld To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) References: <19980802172204.50682@deepo.prosa.dk> <199808021711.LAA07746@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199808021711.LAA07746@narnia.plutotech.com>; from Justin T. Gibbs on Sun, Aug 02, 1998 at 11:11:39AM -0600 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin T. Gibbs writes: > > Assuming it is an AHC problem. I had a freeze not to long ago Well, last time I had these problems (before USENIX) I was running without SOFTUPDATES, and I had error messages like: ordered tag queued ordered tag send SCB 0x4 timed out ... (machine locked, with messages looping). This does not happen with a NCR875 and the maximum number of tags enabled. > Using tagged queuing may exacerbate the problem (most likely by tying > up more kernel resources for pending I/O), but I doubt it is the root > of the problem. I'll do more tests. -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message