amd64/178671: snd_hda stops working as soon as X starts

[John Baldwin]

On Wednesday, May 15, 2013 3:35:01 pm Anton Shterenlikht wrote:
> 
> >Number:         178671
> >Category:       amd64
> >Synopsis:       snd_hda stops working as soon as X starts
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-amd64
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Wed May 15 19:40:02 UTC 2013
> >Closed-Date:
> >Last-Modified:
> >Originator:     Anton Shterenlikht
> >Release:        FreeBSD 10.0-CURRENT amd64
> >Organization:
> University of Bristol 
> >Environment:
> System: FreeBSD mech-aslap239.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-
CURRENT #33 r250633: Tue May 14 20:11:05 BST 2013 root at mech-
aslap239.men.bris.ac.uk:/usr/obj/usr/src/sys/BUZI amd64
> 
> 
> 	
> >Description:
> 
> This is HP Compaq 6715s laptop.
> The sound card is:
> 
> hdac0 at pci0:0:20:2:      class=0x040300 card=0x30c2103c chip=0x43831002 
rev=0x00 hdr=0x00
>     vendor     = 'Advanced Micro Devices [AMD] nee ATI'
>     device     = 'SBx00 Azalia (Intel HDA)'
>     class      = multimedia
>     subclass   = HDA
> 
> I have in the kernel:
> 
> device          sound           # Generic sound driver (required)
> device          snd_hda         # Intel High Definition Audio
> 
> In dmesg:
> 
> hdac0: <ATI SB600 HDA Controller> mem 0xc0000000-0xc0003fff irq 16 at device 
20.2 on pci0
> 
> Before X starts I can get sound via /dev/dsp,
> or play CDs with
> dd if=/dev/cd0 of=/dev/dspcd bs=2352
> 
> HOwever, as soon I start X, e.g. with xdm,
> or simply "X -config /root/xorg.conf.new -retro"
> I cannot get any sound anymore until a reboot.
> 
> On the console I see lots of messages:
> 
> hdac0: Unexpected unsolicited response from address 0: 00000040
> hdac0: Unexpected unsolicited response from address 0: 00400104
> hdac0: Unexpected unsolicited response from address 0: 00000001
> hdac0: Unexpected unsolicited response from address 0: 0000000f
> hdac0: Unexpected unsolicited response from address 0: 410710f0
> hdac0: Unexpected unsolicited response from address 0: 00000010
> hdac0: Unexpected unsolicited response from address 0: 00000040
> hdac0: Unexpected unsolicited response from address 0: 00400083
> hdac0: Unexpected unsolicited response from address 0: 00000000
> hdac0: Unexpected unsolicited response from address 0: 04a12020
> hdac0: Unexpected unsolicited response from address 0: 00001727
> hdac0: Unexpected unsolicited response from address 0: 00000020
> hdac0: Unexpected unsolicited response from address 0: 00400187
> hdac0: Unexpected unsolicited response from address 0: 00000002
> hdac0: Unexpected unsolicited response from address 0: 00000e03
> hdac0: Unexpected unsolicited response from address 0: 0181302e
> hdac0: Unexpected unsolicited response from address 0: 00001737
> hdac0: Unexpected unsolicited response from address 0: 00000020
> hdac0: Unexpected unsolicited response from address 0: 00400301
> hdac0: Unexpected unsolicited response from address 0: 00000001
> hdac0: Unexpected unsolicited response from address 0: 00000002
> hdac0: Unexpected unsolicited response from address 0: 4145f0f0
> hdac0: Unexpected unsolicited response from address 0: 00000010
> hdac0: Unexpected unsolicited response from address 0: 00000040

This sounds like the display driver is DMA'ing to the wrong place or writing 
to the wrong registers.  Can you check the output of pciconf -lcb to make sure 
there are no collisions between BARs?  Also, which GPU hardware/driver is in
your laptop?

-- 
John Baldwin