From owner-freebsd-current@FreeBSD.ORG Tue Aug 5 20:26:05 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0728DAC; Tue, 5 Aug 2014 20:26:05 +0000 (UTC) Received: from mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.auburn.protected-networks.net", Issuer "Protected Networks Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7137B21D8; Tue, 5 Aug 2014 20:26:05 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA v2" (verified OK)) (Authenticated sender: imb@protected-networks.net) by mail.auburn.protected-networks.net (Postfix) with ESMTPSA id 4928258; Tue, 5 Aug 2014 16:25:56 -0400 (EDT) Message-ID: <53E13DD2.2020109@protected-networks.net> Date: Tue, 05 Aug 2014 16:25:54 -0400 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: John Baldwin , David Wolfskill Subject: Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515] References: <20140804194759.GT1228@albert.catwhisker.org> <20140805142914.GJ1228@albert.catwhisker.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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, 05 Aug 2014 20:26:05 -0000 On 08/05/14 16:02, John Baldwin wrote: >> Given that my build machine did not exhibit the symptoms, and given the >> references to atpic, it may be relevant to point out that the machine >> where I see the panic is a Dell Precision M4400 laptop. > > My guess is that the recent Xen changes tickled something. However, can you capture a verbose dmesg from your working kernel? I have the same (or similar) symptom on an old core-duo Toshiba. It seems to occur just before hwpmc would normally show in the log: kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 kernel: ada0: ATA-8 SATA 2.x device kernel: ada0: Serial Number 101105PCK404VLKU1WXJ kernel: ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) kernel: uhub2: 2 ports with 2 removable, self powered kernel: uhub3: 2 ports with 2 removable, self powered kernel: ada0: Command Queueing enabled kernel: ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) kernel: ada0: Previously was known as ad4 kernel: SMP: AP CPU #1 Launched! ** non working kernel panics here ** kernel: hwpmc: SOFT/16/64/0x67 TSC/1/64/0x20 IAP/2/40/0x3ff kernel: Timecounter "TSC" frequency 1662542340 Hz quality 1000 kernel: Root mount waiting for: usbus4 On another machine, which has 4 drives in two geom mirrors, it refuses to find ada0 or ada1. It reports a CAM timeout on the ATA-IDENTIFY phase with an apparently non-functioning interrupt problem. Reverting to a kernel built on July 27th restores normal behaviour, imb