From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 19 11:53:14 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF1C41065670 for ; Wed, 19 Nov 2008 11:53:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 919848FC1C for ; Wed, 19 Nov 2008 11:53:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA07.westchester.pa.mail.comcast.net with comcast id gznu1a0040mv7h057zsQLy; Wed, 19 Nov 2008 11:52:24 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA11.westchester.pa.mail.comcast.net with comcast id gztC1a0032P6wsM3XztCen; Wed, 19 Nov 2008 11:53:13 +0000 X-Authority-Analysis: v=1.0 c=1 a=iEC9EsK3-bUA:10 a=WT13RI0SYF8A:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=MfEOsngDDIU9FJIy-d0A:9 a=OQz5nJVaB4hLIpREnJUA:7 a=rwkn8Eci3BwvCDjBLsmVH_DN2ygA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id E335633C36; Wed, 19 Nov 2008 03:53:11 -0800 (PST) Date: Wed, 19 Nov 2008 03:53:11 -0800 From: Jeremy Chadwick To: Jan Sebosik Message-ID: <20081119115311.GA85626@icarus.home.lan> References: <4923E5A2.2060402@demax.sk> <20081119101530.GA82861@icarus.home.lan> <4923E839.7090001@demax.sk> <20081119102552.GA83022@icarus.home.lan> <4923F0A6.9080304@demax.sk> <20081119112102.GA84963@icarus.home.lan> <4923F7D5.8030409@demax.sk> <4923F928.8010604@demax.sk> <4923FA30.5000303@modulus.org> <4923FB4D.7090505@demax.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4923FB4D.7090505@demax.sk> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Andrew Snow , freebsd-hardware@freebsd.org Subject: Re: Frebsd 7-STABLE, atapicd, atapicam and Intel errors [SOLVED] X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2008 11:53:15 -0000 On Wed, Nov 19, 2008 at 12:41:01PM +0100, Jan Sebosik wrote: > Andrew Snow napsal(a): >> >> Hi >> >> I have a P45 chipset but haven't noticed those problems. I use AHCI >> mode because it enabled hotswap SATA. >> >> But do you also get error messages on the console about timecount going >> backwards for some processes? I can't make it go away, even if I force >> HPET as a counter >> >> - Andrew > > Hi > > obviously no, I don`t get any messages about time going backwards. > > I`ve also tryied AHCI mode, but after some mailing with Intel technical > support they claimed to downgrade to native SATA mode (non-AHCI > operation). Andrew: "Time going backwards" is known to happen on certain systems which use features like Intel SpeedStep. I can reproduce the problem on all sorts of server hardware. It's documented in my Wiki under "Kernel": http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Power-save modes such as C1E might also cause it, but I've enabled this on systems without any repercussions. Just EIST appears to behave oddly, on RELENG_7. (I've tried EIST on CURRENT, and it seems to behave better. I remember reading about major improvements jhb@ completed there which might explain CURRENT working) Jan: (Quoting you from your misplaced mail to -stable) > I thought also about bios bug... it`s pretty new piece of HW with modern > chipset (Q45). I believe that the next release of BIOS comes soon. The chipset has nothing to do with it. I can show you two identical systems, chipset-wise, and show you BIOS bugs. The system manufacturer is who maintains the BIOS, not the chipset manufacturer. > But what about those atapicd problems? Is it related to SATA interface > of DVD/CD drive? Maybe also the LG drive has buggy FW :). Now I'm confused. Didn't we just determine that your acd0 problems disappear if you disable HPET in the BIOS (which makes no sense, but it works, and is probably a BIOS bug)? If so, then what's that got to do with SATA interfaces or LG optical drives? Please help me understand. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |