19:26:54 <tsoome_> hm. some time ago, audiohd on my supermicro used to fail to attach (failed to get some data to set up DMA). now it is complaining WARNING: audiohd#0: timeout when get response from codec: wid=4, verb=0x0f02, param=0x0040
20:33:07 <tsoome_> ok, this audiohd instance may be connected to hdmi, instance 1 seems to be happy.
20:34:21 <rmustacc> I assume it's always done this and isn't a new thing right?
21:29:52 <tsoome_> no, before the audiohd just failed to attach at all - it did not go the number of channels and DMA size was calculated 0, so the allocation failed.
21:30:17 <tsoome_> I'm not even sure when this got changed, but I guess it must have been some change about pci:)
21:31:05 <rmustacc> What bus is it on?
21:32:30 <tsoome_> pciex
21:33:44 <rmustacc> I meant what was the bus number.
21:35:58 <tsoome_> um, how I get it?
21:38:29 <rmustacc> I use pcieadm show-devs or you can parse the register component of the devinfo props. Not too important. Just was thinking back to the fact that SMCI systems didn't properly report bus 255 on Intel systems for a while and that might be why we started seeing it.
21:40:57 <tsoome_> 0/3/0 and 0/1b/0 are audio devices
21:44:34 <rmustacc> Ah, okay. Not ff then which is where some things are on.
21:44:44 <rmustacc> I guess these are built into the chipset, so it makes sense that they're on bus 0.
21:44:49 <tsoome_> yes
21:45:19 <tsoome_> Xeon E3-1200  and 8 Series/C220