From owner-freebsd-current@FreeBSD.ORG Thu Jul 23 19:45:58 2009 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 6147F1065673 for ; Thu, 23 Jul 2009 19:45:57 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 1FBEB8FC18 for ; Thu, 23 Jul 2009 19:45:56 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 249582825; Thu, 23 Jul 2009 22:45:53 +0300 Message-ID: <4A68BDD7.60408@FreeBSD.org> Date: Thu, 23 Jul 2009 22:45:27 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: Yoshihiro Ota References: <1235218982.00077642.1235207402@10.7.7.3> <499FFC5F.3020903@FreeBSD.org> <47d0403c0902210949i74473bc5j57c923e13c85e89@mail.gmail.com> <49A04510.5030405@FreeBSD.org> <7d6fde3d0902211356h66b05cfcxf2ebbe9b2a6fd0f0@mail.gmail.com> <20090224004110.e4ad76f4.ota@j.email.ne.jp> <49A45127.3000108@FreeBSD.org> <20090225211656.75c546c3.ota@j.email.ne.jp> <49A6F609.20901@FreeBSD.org> <20090226223106.b56ad289.ota@j.email.ne.jp> <49A7D1C2.6070608@FreeBSD.org> <20090228015207.d7432c0a.ota@j.email.ne.jp> <20090723153734.e1a8bff1.ota@j.email.ne.jp> In-Reply-To: <20090723153734.e1a8bff1.ota@j.email.ne.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Annoying whitenoise sound coming from snd_hda enabled chipset 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: Thu, 23 Jul 2009 19:45:58 -0000 Yoshihiro Ota wrote: > This problem was gone once back in Febrary. > > I was away from 8-current and came back to 8-BETA1/2. > Then, now I hear this noise again. > > Alexander, do you have any ideas for this time, too? Can you remind me what are you talking about? You are talking about some noise, but following messages about detection problems. > On Sat, 28 Feb 2009 01:52:07 -0500 > Yoshihiro Ota wrote: > >> On Fri, 27 Feb 2009 13:42:58 +0200 >> Alexander Motin wrote: >> >>> Yoshihiro Ota wrote: >>>> On Thu, 26 Feb 2009 22:05:29 +0200 >>>> Alexander Motin wrote: >>>> >>>>> Yoshihiro Ota wrote: >>>>>> On Tue, 24 Feb 2009 21:57:27 +0200 >>>>>> Alexander Motin wrote: >>>>>>> Yoshihiro Ota wrote: >>>>>>>> In my case, with hdac or pcm device, 8-CURRENT fails to boot very requentry. >>>>>>>> It fails to prove a device and doesn't proceed farthar than that point. >>>>>>>> Now it only boots once in 5 or 10 reboots. >>>>>>>> >>>>>>>> When it boots, it prints lots of following messages. >>>>>>>> >>>>>>>> hdac0: HDA Codec #0: Conexant CX20549 (Venice) >>>>>>>> hdac0: unable to allocate widgets! >>>>>>>> hdac0: unable to allocate widgets! >>>>>>>> hdac0: unable to allocate widgets! >>>>>>>> hdac0: unable to allocate widgets! >>>>>>>> hdac0: unable to allocate widgets! >>>>>>>> hdac0: hdac_command_send_internal: TIMEOUT numcmd=1, sent=1, received=0 >>>>>>>> hdac0: hdac_command_send_internal: TIMEOUT numcmd=1, sent=1, received=0 >>>>>>>> hdac0: hdac_command_send_internal: TIMEOUT numcmd=1, sent=1, received=0 >>>>>>>> hdac0: hdac_command_send_internal: TIMEOUT numcmd=1, sent=1, received=0 >>>>>>>> hdac0: hdac_command_send_internal: TIMEOUT numcmd=1, sent=1, received=0 >>>>>>>> >>>>>>>> I think this started happening about a week ago or so, sometime between >>>>>>>> 13 and 16th. >>>>>>> The only significant change last time was enabling MSI by default. But I >>>>>>> don't think it should lead to such errors. I have tried even operation >>>>>>> completely without interrupts working and there is not such errors. Can >>>>>>> you send me complete verbose dmesg with the problem and `pciconf -lvc` >>>>>>> output? >>>>>>> >>>>>>> Also you may try to disable MSI by setting 'hint.hdac.0.msi=0' hint. >>>>>> Once I disabled snd_hda_load="YES" in /boot/loader.conf, it comes up >>>>>> all times. However, when I run "kldload snd_hda", the system stops responding, >>>>>> i.e. crashes. >>>>>> >>>>>> So, now I added 'hint.hdac.0.msi="0"' in the hint; then, system comes up fine. >>>>>> I tried "kldload snd_hda" and got the following output. >>>>>> System didn't crash after adding the hint so that I added snd_hda_load="YES" >>>>>> back to /boot/loader.conf. >>>>> I have committed a patch to the CURRENT that should disable MSI for your >>>>> HDA controller by default. Test it please. >>>> That's r189086, isn't it? >>>> >>>> So, for testing, I will remove hint.hdac.0.msi and add 'snd_hda_load="YES"' back. >>>> Does that sound valid test? >>> Yes. 'snd_hda_load="YES"' is on your wish. >> System comes up without problems now. >> >> Thanks, >> Hiro -- Alexander Motin