From owner-freebsd-current Thu Mar 20 00:17:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA02020 for current-outgoing; Thu, 20 Mar 1997 00:17:43 -0800 (PST) Received: from rr.zippo.com (rr.pathlink.com [204.30.237.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA02015 for ; Thu, 20 Mar 1997 00:17:40 -0800 (PST) Received: from data.zippo.com (data.zippo.com [204.30.237.162]) by rr.zippo.com (8.8.5/8.8.5) with SMTP id AAA14407; Thu, 20 Mar 1997 00:21:04 -0800 (PST) Date: Thu, 20 Mar 1997 00:21:04 -0800 (PST) Message-Id: <199703200821.AAA14407@rr.zippo.com> X-Sender: kachun@dopey.pathlink.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Justin T. Gibbs" From: Kachun Lee Subject: Re: ahc crashes Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:51 PM 3/19/97 -0700, you wrote: >Which AHC options are you using in your kernel config? I did not use any... should I try some? I am using the Intel Venus Pro 200 MB and 3940W - with 3 Seagate 4G on 1 channel and 6 4G on the other. >>Thank you for trying, but sorry to say the 970318 kernel crashed also. >>Actually, even more often - every 3-4 hours... the 2.2-REL only during INN >>expireover. And, when the system crashed, no log messages made into >>/var/log/messages. I caught the reboot once and it said something about >>ahc... timeout... the screen erase before I could write it down. >> [snip] Thanks for the help