All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: `hda-intel: spurious response` several times in output of `dmesg`
Date: Mon, 12 Sep 2011 11:28:26 +0200	[thread overview]
Message-ID: <s5h8vpu85z9.wl%tiwai@suse.de> (raw)
In-Reply-To: <CACTFLANPdSzg9KMhjdgn_=kuQZq+EnwA2cw0t+QT1RoWQ=nwCA@mail.gmail.com>

At Wed, 31 Aug 2011 12:37:28 +0200,
Daniel Mack wrote:
> 
> On Wed, Aug 31, 2011 at 12:19 PM, Paul Menzel
> <paulepanter@users.sourceforge.net> wrote:
> > Dear ALSA folks,
> >
> >
> > Am Donnerstag, den 25.08.2011, 17:01 +0200 schrieb Paul Menzel:
> >
> > […]
> >
> >> I just want to add that I also see these messages with Linux kernel
> >> 3.0.2 and say seem to be related to suspend and resume.
> >>
> >> The values seem to differ though every time.
> >>
> >>         [ 1130.984969] hda-intel: spurious response 0x0:0x0, last cmd=0x620000
> >>         [ 1130.984990] hda-intel: spurious response 0x1003c:0x0, last cmd=0x620000
> >>         [ 1130.985011] hda-intel: spurious response 0x0:0x0, last cmd=0x620000
> >>         [ 1130.985032] hda-intel: spurious response 0x10034:0x0, last cmd=0x620000
> >>         [ 1130.985053] hda-intel: spurious response 0x0:0x0, last cmd=0x620000
> >>
> >>         [ … another suspend/resume … ]
> >>
> >>         [ 2726.277102] hda-intel: spurious response 0x0:0x0, last cmd=0x1e70700
> >>         [ 2726.277123] hda-intel: spurious response 0x0:0x0, last cmd=0x1e70700
> >>         [ 2726.277144] hda-intel: spurious response 0x0:0x0, last cmd=0x1e70700
> >>         [ 2726.277165] hda-intel: spurious response 0xb:0x0, last cmd=0x1e70700
> >>
> >> Please find the output of `alsa-info.sh` [1] with this Linux version at
> >> the end.
> >
> > who is the correct person to address these things to?
> 
> Takashi is maintaining this driver, but he is on vacation right now.
> I'm sure he'll answer once he's back :)

Now swimming in the sea of pending mails and bugzilla :)

The verb 0x620000 is to set a stream format to NID 0x06.
For further debugging, more detailed information is needed.

I seem to have lost the original post, so could you attach
alsa-info.sh output again, Paul?


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2011-09-12  9:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 11:35 Report by PulseAudio: `alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.` Paul Menzel
2011-08-25 15:01 ` `hda-intel: spurious response` several times in output of `dmesg` (was: Report by PulseAudio: `alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.`) Paul Menzel
2011-08-31 10:19   ` `hda-intel: spurious response` several times in output of `dmesg` Paul Menzel
2011-08-31 10:37     ` Daniel Mack
2011-08-31 10:59       ` Paul Menzel
2011-09-12  9:28       ` Takashi Iwai [this message]
2011-09-13 22:11         ` Paul Menzel
2011-09-18 18:28           ` Paul Menzel
2011-09-19  9:27             ` Takashi Iwai
2011-09-19 12:50               ` Paul Menzel
2011-09-19 13:19                 ` Takashi Iwai
2011-09-19 18:39                   ` Paul Menzel
2011-09-27 12:52                     ` Takashi Iwai
2011-09-27 20:44                       ` In what branch is work for non-snooping mode? (was: `hda-intel: spurious response` several times in output of `dmesg`) Paul Menzel
2011-09-27 20:48                         ` Takashi Iwai
2011-09-29 13:27                       ` `hda-intel: spurious response` several times in output of `dmesg` Paul Menzel
2011-09-29 13:33                         ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h8vpu85z9.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=paulepanter@users.sourceforge.net \
    --cc=zonque@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.