From owner-freebsd-bugs Wed Feb 25 11:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00126 for freebsd-bugs-outgoing; Wed, 25 Feb 1998 11:54:35 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00115 for ; Wed, 25 Feb 1998 11:54:33 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id LAA19101; Wed, 25 Feb 1998 11:53:54 -0800 (PST) To: Jeffery Gallagher cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Install of 2.2.5 In-reply-to: Your message of "Wed, 25 Feb 1998 13:51:39 -0330." Date: Wed, 25 Feb 1998 11:53:54 -0800 Message-ID: <19097.888436434@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If you have any knowledge of this problem or have any solution > suggestions they would be welcome. Hmm. None of my 2940s have ever behaved this way with 2.2.5, so I'm really not inclined to think that it's FreeBSD at fault here. Have you tried swapping the controller? You may simply have a bad one - it's been known to happen. Also, make *sure* the controller is properly configured vis-a-vis termination; it's not just the devices that need to be properly terminated. If swapping the controller doesn't help then I'd suspect some interaction with the MB. Swap the MB next and see what happens. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message