From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 22:18:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1153216A4CE; Fri, 15 Oct 2004 22:18:32 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE8BF43D1F; Fri, 15 Oct 2004 22:18:31 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id IBA74465; Fri, 15 Oct 2004 15:18:31 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 669195D09; Fri, 15 Oct 2004 15:18:28 -0700 (PDT) To: "Alexandre \"Sunny\" Kovalenko" In-reply-to: Your message of "Fri, 15 Oct 2004 18:08:42 EDT." <1097878121.812.3.camel@RabbitsDen> Date: Fri, 15 Oct 2004 15:18:28 -0700 From: "Kevin Oberman" Message-Id: <20041015221828.669195D09@ptavv.es.net> cc: freebsd-current@freebsd.org cc: Thomas Quinot Subject: Re: atapicam(4) as KLD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 22:18:32 -0000 > From: "Alexandre \"Sunny\" Kovalenko" > Date: Fri, 15 Oct 2004 18:08:42 -0400 > Sender: owner-freebsd-current@freebsd.org > > On Fri, 2004-10-15 at 13:03, Thomas Quinot wrote: > > * Alexandre Sunny Kovalenko, 2004-10-15 : > > > > > be fair, I do not know if it still is the case. If there is enough > > > interest out there, I can plug it back in. > > > > If you can do that experiment and le tme know what happens, I'd > > certainly be interested in fixing this issue. > > > > Thomas. > > I have added device atapicam back into my config, rebuilt the kernel and > have been running for about an hour of light use with no visible ill > effects. I will keep it in at least through couple of buildworlds and CD > burns, but for now I would like to apologize for spreading FUD. Not really FUD, but old data. There certainly were problems with ATAPICAM for some time after the introduction of ATAng to RELENG_5. I have not seen any problems with it on any of my V5 systems for at least 3 months and probably longer. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634