alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: `hda-intel: spurious response` several times in output of `dmesg`
Date: Wed, 31 Aug 2011 12:19:01 +0200	[thread overview]
Message-ID: <1314785943.3769.30.camel@mattotaupa> (raw)
In-Reply-To: <1314284537.26121.6.camel@mattotaupa>


[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]

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?


Thanks,

Paul

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2011-08-31 10:19 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   ` Paul Menzel [this message]
2011-08-31 10:37     ` `hda-intel: spurious response` several times in output of `dmesg` Daniel Mack
2011-08-31 10:59       ` Paul Menzel
2011-09-12  9:28       ` Takashi Iwai
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=1314785943.3769.30.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).