From owner-freebsd-current@FreeBSD.ORG Tue Jul 27 07:37:52 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1133F1065673 for ; Tue, 27 Jul 2010 07:37:52 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id C92708FC1B for ; Tue, 27 Jul 2010 07:37:51 +0000 (UTC) Received: from lstewart.caia.swin.edu.au (lstewart.caia.swin.edu.au [136.186.229.95]) by lauren.room52.net (Postfix) with ESMTPSA id 9D7197E87D; Tue, 27 Jul 2010 17:37:49 +1000 (EST) Message-ID: <4C4E8CCD.1010101@freebsd.org> Date: Tue, 27 Jul 2010 17:37:49 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100726 Thunderbird/3.0.6 MIME-Version: 1.0 To: Anton Shterenlikht References: <20100726132451.GA18443@mech-cluster241.men.bris.ac.uk> <20100726160732.GA37936@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20100726160732.GA37936@mech-cluster241.men.bris.ac.uk> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: amd64 panic snd_hda - hdac_get_capabilities: Invalid corb size (0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2010 07:37:52 -0000 On 07/27/10 02:07, Anton Shterenlikht wrote: > On Mon, Jul 26, 2010 at 02:24:52PM +0100, Anton Shterenlikht wrote: >> On amd64 r210496 I get this panic when booting a kernel >> with snd_hda(4). I haven't used this driver before, so >> can't say if this is a regression. >> >> (copied by hand) >> >> hdac0: irq 16 at device 20.2 on pci0 >> hdac0: HDA Driver Revision: 20100226_0142 >> hdac0: [ITHREAD] >> hdac0: hdac_get_capabilities: Invalid corb size (0) >> device_attach: hdac0 attach returned 6 >> Slab at 0xffffff000261eb18, freei 3 = 0 >> panic: Duplicate free of item 0xffffff0002661c00 from zone 0xffffff00b7f9a500(1024) >> >> cpuid = 0 >> KDB: enter: panic >> [ thread pid 0 tid 100000 ] >> Stopped at kdb_enter+0x3d: movq $0,0x74f360(%rip) >> db>bt >> >> (very long output.. ending in) >> >> mi_startup() at mi_startup_0x59 >> btext() at btext+0x2c > > I moved back as far as r204000, still the same panic. > > Please advise I get this same panic on my Toshiba Portege R600 laptop when I boot it into Windows and then reboot it into FreeBSD. My guess is that the Windows drivers leave the hardware in a state which the FreeBSD code doesn't know how to deal with. I don't run Windows often so haven't hit this panic in a while, but the trick that always worked for me was to go into the BIOS and "Reset to defaults", then boot into FreeBSD. Cheers, Lawrence