Re: amd64 panic snd_hda - hdac_get_capabilities: Invalid corb size (0)

From: Andriy Gapon <avg_at_icyb.net.ua>
Date: Wed, 28 Jul 2010 19:33:44 +0300
on 28/07/2010 19:17 Anton Shterenlikht said the following:
> On Wed, Jul 28, 2010 at 07:07:34PM +0300, Andriy Gapon wrote:
>> on 28/07/2010 19:01 Anton Shterenlikht said the following:
>>> here it is:
>> So did it work? :)
> 
> not as far as I can tell
> 
>>> % dmesg|fgrep -i hda
>>> pci0: <multimedia, HDA> at device 20.2 (no driver attached)
>>> pci0: <multimedia, HDA> at device 20.2 (no driver attached)
>>> hdac0: <ATI SB600 High Definition Audio Controller> irq 16 at device 20.2 on pci0
>>> hdac0: HDA Driver Revision: 20100226_0142
>>> hdac0: [ITHREAD]
>>> hdac0: hdac_get_capabilities: Invalid rirb size (0)
>>> device_attach: hdac0 attach returned 6
>> I presume the above is from previous load attempt?
> 
> yes, probably. I think /var/run/dmesg used
> to contain only the current boot, but some
> time ago I noticed that quite a few previous
> boots are stored. Or maybe it's my misconfiguration..

Did you just kldload the module?
Or do you have hda in your kernel and you performed a reboot?
If you didn't reboot, can you do it now?

>>> hdac0: <ATI SB600 High Definition Audio Controller> irq 16 at device 20.2 on pci0
>>> hdac0: HDA Driver Revision: 20100226_0142
>>> hdac0: [ITHREAD]
>>> hdac0: hdac_get_capabilities: Invalid rirb size (0)
>>> hdac0: Resetting rirb size to 256
>> Hmm, so no message about corb, just rirb?

So no corb message?
This seems very strange, especially given the subject line.

>> Also, no codec and pcm output lines?  Did the driver get attached?
> 
> As far as I can (cannot) see, the driver didn't attach.
> There's no /dev/dsp or /dev/pcm.

What is output of the following command?
kldstat -v | egrep 'sound|snd'

> % cat /dev/sndstat 
> FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64)
> Installed devices:
> %
> 
> I also get (probably not related)
> 
> % dmesg|grep dead
> Event timer "i8254" is dead.
> %

You can try to use a different timer.
See sysctl kern.eventtimer, you can override timer1 and timer2 in your loader.conf.

-- 
Andriy Gapon
Received on Wed Jul 28 2010 - 14:33:55 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:05 UTC