From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 19 10:25:55 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 52C66106567A for ; Wed, 19 Nov 2008 10:25:55 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id EB22C8FC0A for ; Wed, 19 Nov 2008 10:25:54 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA03.westchester.pa.mail.comcast.net with comcast id gyLg1a0081HzFnQ53yQwCx; Wed, 19 Nov 2008 10:24:56 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA14.westchester.pa.mail.comcast.net with comcast id gyRX1a0042P6wsM3ayRXPa; Wed, 19 Nov 2008 10:25:32 +0000 X-Authority-Analysis: v=1.0 c=1 a=iEC9EsK3-bUA:10 a=WT13RI0SYF8A:10 a=QycZ5dHgAAAA:8 a=EC0tx85mvDtDZa_4e4wA:9 a=2PCAGCOO7TPv-mTEHD8A:7 a=KU0Km1u_FqLOtPgdK6Tow_2L0qcA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 0F24A33C37; Wed, 19 Nov 2008 02:25:52 -0800 (PST) Date: Wed, 19 Nov 2008 02:25:52 -0800 From: Jeremy Chadwick To: Jan Sebosik Message-ID: <20081119102552.GA83022@icarus.home.lan> References: <491F31B5.90403@demax.sk> <4923E5A2.2060402@demax.sk> <20081119101530.GA82861@icarus.home.lan> <4923E839.7090001@demax.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4923E839.7090001@demax.sk> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: sos@freebsd.org, 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 10:25:55 -0000 On Wed, Nov 19, 2008 at 11:19:37AM +0100, Jan Sebosik wrote: > Hi > > Yeah, I`ve tested it 2 times (switching it in BIOS). To me it seems bit > mysterious, why there is a relationship between HPET setting and acd/cd > problems in FreeBSD. > > > Jeremy Chadwick napsal(a): >> On Wed, Nov 19, 2008 at 11:08:34AM +0100, Jan Sebosik wrote: >>> Hi again >>> >>> so it seems to be a problem with HPET timer which is onboard and was >>> enabled. If I turned him off, (acd | cd) problems went away. >>> >>> >>> Jan Sebosik napsal(a): >>>> Hi all >>>> >>>> OS: Freebsd 7-STABLE from CVS of today >>>> Problematic HW: Intel DQ45CB (Q45 chipset, ICH10, SATA in native >>>> mode, but not AHCI), LG SATA DVD-RW GH20NS15 >>>> >>>> Problem: if I run freebsd without LG DVD connected to any SATA port >>>> onboard everything works allright. When I connect SATA DVD to >>>> board, then freebsd refuses to boot with messages similar to >>>> those: >>>> >>>> acd0: FAILURE-READ_BIG timed out >>>> unknown: FAILURE-READ_BIG timed out >>>> cddone: goit error 0x5 back >>>> >>>> Messages are repeating forever. >>>> >>>> Anybody knows where should be a bug? >>>> Temporary I`ve disconnected LG SATA burner from system board. >>>> >>>> Thanks for any idea. >>>> >>>> Best regards >> >> Are you ***absolutely 100% certain*** this is true? The time counter >> selected shouldn't have anything to do with the errors you see. >> Please thoroughly test this. >> >> I'd CC jhb@ to get confirmation of my statement, but I've promised >> myself I wouldn't bother him until 2009. :-) This is very bizarre. The errors being returned from acd0 are that an ATAPI/ATA command (READ_BIG, whatever the code for that is) did not receive a response from the controller or device within 5 seconds (assuming the ata(4) timeout values here; it could be something larger for ATAPI, I don't know). Maybe some a BIOS bug... Can you show us output from the following two commands? sysctl kern.timecounter.choice sysctl kern.timecounter.hardware Soren, do you know how/if the HPET time counter could cause this oddity? All of my systems use ACPI-fast, so I can't test this. -- | 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 |