Date: Wed, 28 Jul 2010 10:35:02 +1000 From: Lawrence Stewart <lstewart@freebsd.org> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-current@freebsd.org Subject: Re: amd64 panic snd_hda - hdac_get_capabilities: Invalid corb size (0) Message-ID: <4C4F7B36.8080701@freebsd.org> In-Reply-To: <20100727080957.GB45627@mech-cluster241.men.bris.ac.uk> 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>
index | next in thread | previous in thread | raw e-mail
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: <ATI SB600 High Definition Audion Controller> 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, Lawrencehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C4F7B36.8080701>