From owner-freebsd-current@FreeBSD.ORG Sat May 16 13:27:15 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 51527F70; Sat, 16 May 2015 13:27:15 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 16707164E; Sat, 16 May 2015 13:27:14 +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 6936A1FE023; Sat, 16 May 2015 15:27:12 +0200 (CEST) Message-ID: <555745DD.8080506@selasky.org> Date: Sat, 16 May 2015 15:27:57 +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> In-Reply-To: <20150515200727.GV1215@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:27:15 -0000 On 05/15/15 22:07, David Wolfskill wrote: > On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: >> ... >> Hummm, the only recent change is 281544, but that should be in your working >> kernel. > > Yes; that dates from 14 April, and I had been doing daily build/boots of > head/i386 through thta period without incident. Absent something > compelling, I'm pretty sure that experience alone removes 281544 from > plausibly being implicated. > >> It does mess with the layout of pins though so maybe try reverting it >> anyway? >> >> It might also be worth trying to revert just the one commit you identified >> earlier. It just seems odd for 'as[cnt]' to fault here but not earlier. >> .... > > OK; I tried reverting 282650, but the result wouldn't build because the > AFMT_CHANNEL_MAX token wasn't defined. > > Turns out it had been used by 282651, so I reverted that (and found that > it would have been cleaner had I reverted them in reverse sequence, but > "svn patch" seemed to merely whine a bit, but cope anyway). > > 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. --HPS