From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 00:35:04 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 E365A1065675 for ; Wed, 28 Jul 2010 00:35:04 +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 5FA988FC14 for ; Wed, 28 Jul 2010 00:35:04 +0000 (UTC) Received: from lawrence1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 240AC7E899; Wed, 28 Jul 2010 10:35:03 +1000 (EST) Message-ID: <4C4F7B36.8080701@freebsd.org> Date: Wed, 28 Jul 2010 10:35:02 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-AU; rv:1.9.1.10) Gecko/20100704 Thunderbird/3.0.5 MIME-Version: 1.0 To: Anton Shterenlikht References: <20100726132451.GA18443@mech-cluster241.men.bris.ac.uk> <20100726160732.GA37936@mech-cluster241.men.bris.ac.uk> <4C4E8CCD.1010101@freebsd.org> <20100727080957.GB45627@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20100727080957.GB45627@mech-cluster241.men.bris.ac.uk> 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: Wed, 28 Jul 2010 00:35:05 -0000 On 07/27/10 18:09, Anton Shterenlikht wrote: > On Tue, Jul 27, 2010 at 05:37:49PM +1000, Lawrence Stewart wrote: >> 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. > > no, that doesn't help, still the same panic > > Also, I've only FBSD installed on this laptop (HP Compaq 6715s), > no other OS. hmm I'll have to try the patch and see if it resolves the issue for me. I guess in my case resetting the BIOS was causing a different code path to be taken and thus the panic never triggered. Good to here it's resovled for you though. Cheers, Lawrence