From owner-freebsd-current@FreeBSD.ORG Tue Oct 1 07:40:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09940172; Tue, 1 Oct 2013 07:40:36 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id B739124FB; Tue, 1 Oct 2013 07:40:35 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3cpspV1rbTzFTPr; Tue, 1 Oct 2013 09:40:34 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OgDYchhEti4h; Tue, 1 Oct 2013 09:40:32 +0200 (CEST) Received: from vwg82.hq.ignesti.it (unknown [77.246.14.163]) by winston.madpilot.net (Postfix) with ESMTPSA; Tue, 1 Oct 2013 09:40:32 +0200 (CEST) Message-ID: <524A7C6C.2070606@madpilot.net> Date: Tue, 01 Oct 2013 09:40:28 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Boris Samorodov , gahr@FreeBSD.org Subject: Re: r255873: ahcich7: Timeout on slot 0 port 0 FLOODING kernel messages References: <20130926085326.72b53660@thor.walstatt.dyndns.org> <20130926154026.4be04064@laptop.minsk.domain> <20130926130718.GH41229@kib.kiev.ua> <20130927083647.39956586@laptop.minsk.domain> <977CE1C1-B96C-4553-8C08-0077E1738496@samsco.org> <20130927145251.6532d339@laptop.minsk.domain> <0B95678C-4C3A-4234-B2EA-77156ED905B9@samsco.org> <20130927125934.GA87559@gahrfit.gahr.ch> <52458A41.6040004@passap.ru> In-Reply-To: <52458A41.6040004@passap.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Konstantin Belousov , "Sergey V. Dyatko" , FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 01 Oct 2013 07:40:36 -0000 On 09/27/13 15:38, Boris Samorodov wrote: > 27.09.2013 16:59, Pietro Cerutti пишет: >> On 2013-Sep-27, 05:57, Scott Long wrote: >>> >>> On Sep 27, 2013, at 5:52 AM, Sergey V. Dyatko wrote: >>> >>>>>> >>>>>> yes, these messages disappeared after revert 255870 and r255871 >>>>>> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Nothing that I changes should have affected the ahci driver. In >>>>> fact, I tested this driver specifically during my development. Can >>>>> you confirm that you built both kernel and modules from a clean state? >>>> >>>> [tiger@laptop]:/usr/src%svn st >>>> M sys/boot/i386/zfsboot/zfsboot.c >>>> [tiger@laptop]:/usr/src%svn diff >>>> Index: sys/boot/i386/zfsboot/zfsboot.c >>>> =================================================================== >>>> --- sys/boot/i386/zfsboot/zfsboot.c (revision 255873) >>>> +++ sys/boot/i386/zfsboot/zfsboot.c (working copy) >>>> @@ -302,6 +302,7 @@ >>>> * region in the SMAP, use the last 3MB of 'extended' memory as a >>>> * high heap candidate. >>>> */ >>>> + high_heap_size = 0; >>>> if (bios_extmem >= HEAP_MIN && high_heap_size < HEAP_MIN) { >>>> high_heap_size = HEAP_MIN; >>>> high_heap_base = bios_extmem + 0x100000 - HEAP_MIN; >>>> [tiger@laptop]:/usr/src% >>>> >>>> nothing more. >>>> >>> >>> Yes, no local source changes, but are you loading the cam or ahci drivers >>> a loadable modules that might be out of sync now, or did you use a short- >>> cut for building your kernel, like NO_CLEAN? >> >> I had the same problem with a clean src tree. After commenting out the >> ahci line from my kernel conf file, I got these instead: >> >> Sep 27 14:32:10 SN2000 kernel: ata3: setting up DMA failed >> Sep 27 14:32:12 SN2000 kernel: ata3: FAILURE - zero length DMA transfer attempte >> >> reverting those two commits solved the issue. > > In my case just rebuilding and restarting of sysutils/hal helped. > sysutils/smartmontools needs the same treatment. BTW thanks for finding this fix :) -- Guido Falsi