[alsa-devel] hda_intel:azx_get_response timeout, switching to single_cmd mode: last cmd=0x00070503
Takashi Iwai
tiwai at suse.de
Thu Feb 16 10:40:31 CET 2012
At Thu, 16 Feb 2012 17:34:08 +0800,
joey.jiaojg wrote:
>
> Ooops, but I haven't faced this problem now (I happen once when I debug
> yesterday I think). So forget about it for the relation to another post
> (HP B1900).
OK. The fallback to the single_cmd happens usually when invalid
access to the codec chip occurs. In most cases, the verbs sent by the
static model don't match with the actual hardware. Or, the verbs are
sent in the bad power-state (e.g. during PM). Or whatever strange
reason.
In this particular case, the verb 0x0070503 is really wrong
(i.e. NID=0).
Takashi
> On 2012年02月16日 17:31, Takashi Iwai wrote:
> > At Thu, 16 Feb 2012 17:21:20 +0800,
> > joey.jiaojg wrote:
> >> I had similar issue from dmesg once.
> >> The NID,VERB,PARM works if I use hda-verb, So I think it's not a big
> >> problem since everything works.
> > No, no, it's a big problem. Switching to polling mode is OK. It's
> > usually harmless. But falling back to single_cmd mode is basically a
> > fatal error. If this happens, the unsolicited events will be never
> > handled any longer.
> >
> >
> > Takashi
> >
> >> On 2012?02?16? 17:18, Paul Menzel wrote:
> >>> Dear Sirus,
> >>>
> >>>
> >>> Am Donnerstag, den 16.02.2012, 04:29 +0000 schrieb Sirus Jolt:
> >>>> Hi, I've got some problems to start session, because i've got the message like
> >>>> subject:
> >>>>
> >>>> hda_intel: azx_get_response timeout, switching to single_cmd mode: last
> >>>> cmd=0x00070503
> >>>>
> >>>> I have no idea about the problem, I need your help. In some threat mention it
> >>>> but don't have the answer.
> >>> your message misses a lot of useful information which would help
> >>> developers (not me) to help you.
> >>>
> >>> Also do you notice any problems? That means, does audio work for you?
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Paul
> >>>
> >>>
> >>> [1] http://alsa-project.org/main/index.php/Help_To_Debug
> >>> (Please attach that file to your next answer *and* upload it.)
> >>>
> >>>
> >>> _______________________________________________
> >>> Alsa-devel mailing list
> >>> Alsa-devel at alsa-project.org
> >>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel at alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>
>
More information about the Alsa-devel
mailing list