From owner-freebsd-current@FreeBSD.ORG Sat May 16 13:49:17 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA69D56D; Sat, 16 May 2015 13:49:17 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9A5B618B4; Sat, 16 May 2015 13:49:17 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 561CC1FE023; Sat, 16 May 2015 15:49:15 +0200 (CEST) Message-ID: <55574B08.9010202@selasky.org> Date: Sat, 16 May 2015 15:50:00 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: David Wolfskill , John Baldwin , freebsd-current@freebsd.org Subject: Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again References: <20150509142751.GV1158@albert.catwhisker.org> <3725154.XnIHrZucd0@ralph.baldwin.cx> <20150515183956.GU1215@albert.catwhisker.org> <1567746.I7cSSt5lv5@ralph.baldwin.cx> <20150515200727.GV1215@albert.catwhisker.org> <555745DD.8080506@selasky.org> <20150516133744.GF1215@albert.catwhisker.org> In-Reply-To: <20150516133744.GF1215@albert.catwhisker.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 16 May 2015 13:49:17 -0000 On 05/16/15 15:37, David Wolfskill wrote: > On Sat, May 16, 2015 at 03:27:57PM +0200, Hans Petter Selasky wrote: >> ... >>> After reverting both 282650 & 282651, the resulting kernel built. >>> >> >> Hi, >> >> I'm seeing two of my commits mentioned here, r282650 & r282651. Are >> these what is causing the problem? You are sure the built the kernel and >> all modules from clean, hence some structures are changed, panic would >> be expected if you don't. >> .... > Hi, > I'll admit that the vast bulk of my builds are done with -DNOCLEAN -- I > actually want to use my laptop for things other than rebuilding FreeBSD > (4x/day) and rebuilding updated installed ports (2x/day). Then it will possibly trigger bad, because AFMT_CHANNELS() returns part of the old EXT channels, which is used in the HDAA driver. If you want to save time, you need to rebuild all of "modules/sound" only, w/o -DNO_CLEAN and doing "clean" first. The rest of the kernel is fine with -DNO_CLEAN. > After I finish the build I'm presently doing, I will try re-doing > r282650 & r282651, then rebuilding cleanly. > > I noted that r282650 included a bump to param.h to force all modules to > be rebuilt. > > I also note that the panic was only seen in head/i386 -- head/amd64 on > the same hardware, using the same procedures, sources updated from the > same local private mirror of the SVN repo, using a copy of the same > "CANARY" kernel config file, had no issue. Send output from bootverbose! Let's hunt this bug down :-) --HPS