From owner-freebsd-current@FreeBSD.ORG Fri Sep 27 13:56:50 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 9159E762; Fri, 27 Sep 2013 13:56:50 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FA1E2337; Fri, 27 Sep 2013 13:56:50 +0000 (UTC) Received: from [127.0.0.1] (Scott4long@pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id r8RDukYn068241; Fri, 27 Sep 2013 07:56:47 -0600 (MDT) (envelope-from scottl@samsco.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: r255873: ahcich7: Timeout on slot 0 port 0 FLOODING kernel messages From: Scott Long In-Reply-To: <52458A41.6040004@passap.ru> Date: Fri, 27 Sep 2013 07:56:45 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: 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> To: Boris Samorodov X-Mailer: Apple Mail (2.1510) Cc: Konstantin Belousov , "Sergey V. Dyatko" , FreeBSD CURRENT , gahr@FreeBSD.org 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: Fri, 27 Sep 2013 13:56:50 -0000 On Sep 27, 2013, at 7:38 AM, Boris Samorodov wrote: > 27.09.2013 16:59, Pietro Cerutti =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> On 2013-Sep-27, 05:57, Scott Long wrote: >>>=20 >>> On Sep 27, 2013, at 5:52 AM, Sergey V. Dyatko = wrote: >>>=20 >>>>>>=20 >>>>>> yes, these messages disappeared after revert 255870 and r255871 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> 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? >>>>=20 >>>> [tiger@laptop]:/usr/src%svn st >>>> M sys/boot/i386/zfsboot/zfsboot.c >>>> [tiger@laptop]:/usr/src%svn diff=20 >>>> Index: sys/boot/i386/zfsboot/zfsboot.c >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> --- 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 =3D 0; >>>> if (bios_extmem >=3D HEAP_MIN && high_heap_size < HEAP_MIN) { >>>> high_heap_size =3D HEAP_MIN; >>>> high_heap_base =3D bios_extmem + 0x100000 - HEAP_MIN; >>>> [tiger@laptop]:/usr/src% >>>>=20 >>>> nothing more.=20 >>>>=20 >>>=20 >>> 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? >>=20 >> 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: >>=20 >> 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 >>=20 >> reverting those two commits solved the issue. >=20 > In my case just rebuilding and restarting of sysutils/hal helped. Interesting. I didn't test hal, probably should have. The compat shims = I put in place should have made it work without a rebuild. I wonder if it's = somehow corrupting kernel state. Are others who are experiencing problems also = running the hal package? Scott