From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 11:31:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43330106568F for ; Wed, 19 Nov 2008 11:31:54 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from mail.demax.sk (mail.demax.sk [213.215.102.234]) by mx1.freebsd.org (Postfix) with ESMTP id D492B8FC1B for ; Wed, 19 Nov 2008 11:31:53 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from localhost (localhost [127.0.0.1]) by mail.demax.sk (Postfix) with ESMTP id E3F55873C2 for ; Wed, 19 Nov 2008 12:31:52 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.demax.sk Received: from mail.demax.sk ([127.0.0.1]) by localhost (mail.demax.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gm69rKngwga for ; Wed, 19 Nov 2008 12:31:52 +0100 (CET) Received: from [192.168.0.2] (2D204.demax.sk [195.62.17.204]) by mail.demax.sk (Postfix) with ESMTP id BD72587357 for ; Wed, 19 Nov 2008 12:31:52 +0100 (CET) Message-ID: <4923F928.8010604@demax.sk> Date: Wed, 19 Nov 2008 12:31:52 +0100 From: Jan Sebosik User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: FreeBSD stable References: <491F31B5.90403@demax.sk> <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> In-Reply-To: <4923F7D5.8030409@demax.sk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Frebsd 7-STABLE, atapicd, atapicam and Intel errors [SOLVED] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2008 11:31:54 -0000 Opps, bad mailing-list... excuse me. Jan Sebosik napsal(a): > Yeah > > 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. > > But what about those atapicd problems? Is it related to SATA interface > of DVD/CD drive? Maybe also the LG drive has buggy FW :). > > Best regards > > Jeremy Chadwick napsal(a): >> On Wed, Nov 19, 2008 at 11:55:34AM +0100, Jan Sebosik wrote: >>> Allright, I`ve played again with an HPET in BIOS little bit. >>> >>> Results -> >>> >>> HPET disabled: >>> >>> kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) >>> dummy(-1000000) >>> kern.timecounter.hardware: ACPI-fast >>> >>> HPET enabled: >>> >>> kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) >>> i8254(0) dummy(-1000000) >>> kern.timecounter.hardware: ACPI-fast >>> >>> >>> But now FreeBSD boots also with HPET enabled (really don`t >>> understand what`s going on). >>> >>> When I was trying to mount cd with "mount -t cd9660 /dev/cd0 >>> /mnt/cd0", mount works as expected (atapicd module not loaded). >>> >>> Then I`ve kldload-ed atapicd, "mouunt -t cd9660 /dev/acd0 /mnt/cd0" >>> (acd0, not cd0), but this ended with messages like this: >>> unknown: FAILURE - READ_BIG timeout (retry count 0) >>> >>> Temporary I`ve disabled HPET in BIOS (Linux got problems too-> he >>> created gigabytes of log messages in /var/log/messages :D). >>> >>> Best regards, Jan >>> >>> Jeremy Chadwick napsal(a): >>>> 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. >> >> What this proves is that disabling HPET in the BIOS makes absolutely no >> change to FreeBSD as far as the timecounter goes. It's still using >> ACPI-fast no matter if HPET is disabled or not. Disabling HPET does >> show up in FreeBSD (as you can tell), but the ATA/ATAPI stuff *should >> not* have some direct tie-in to HPET. >> >> I'm left believing you've found a BIOS bug. Please bring this up with >> your motherboard or system vendor. >> > -- Jan Sebosik, Slovakia sebosik@demax.sk