alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: hui.wang@canonical.com, alsa-devel@alsa-project.org,
	kailang@realtek.com, david.henningsson@canonical.com
Subject: Re: Intel HDA audio on EEE PC 1101HGo
Date: Thu, 9 Apr 2015 22:02:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1504092157190.901@localhost.localdomain> (raw)
In-Reply-To: <s5hegntl2cs.wl-tiwai@suse.de>

Hello guys.
I am running kernel 4.0.0-rc7hc+ (the "hc" is my own versioning name).
There seems to be less problems (the card doesn't get stuck at some point): 
this device continues to be a little bit unstable (i.e.: now the internal 
speaker doesn't work):
[   20.841143] snd_hda_intel 0000:00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
[   21.843141] snd_hda_intel 0000:00:1b.0: Codec #0 probe error; disabling it...
[   22.848327] snd_hda_intel 0000:00:1b.0: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f0000
[  148.125849] snd_hda_intel 0000:00:1b.0: Invalid position buffer, using LPIB read method instead.

but I think this is due to the fact I restarted the system with kexec, not with 
a clean bios reboot. But I signaled this since it seems that also a sequence 
like:
sudo modprobe -r snd_hda_intel
# some time
sudo modprobe snd_hda_intel

can trigger strange behaviours.
But guys - this is probably not a problem that can be solved from the driver 
itself (as I imagine looking at the messages i got yesterday from 
pci/access.c).
So - thank you for the help, and the tireless work you all put on this driver.

  parent reply	other threads:[~2015-04-09 20:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 19:40 Intel HDA audio on EEE PC 1101HGo Enrico Mioso
2015-04-08 20:25 ` Enrico Mioso
2015-04-09 15:59 ` Takashi Iwai
2015-04-09 16:02   ` Enrico Mioso
2015-04-09 20:02   ` Enrico Mioso [this message]
2015-04-11  8:13   ` Enrico Mioso
2015-04-12  6:01     ` Takashi Iwai
2015-04-13 20:25       ` Enrico Mioso
2016-11-22 13:09       ` Enrico Mioso
2016-11-22 15:55         ` Mrkiko Rs
2016-11-22 16:41           ` Enrico Mioso
2016-11-23  8:19   ` Enrico Mioso
2016-12-01 10:12     ` Takashi Iwai
2016-12-01 13:50       ` Enrico Mioso
2016-12-01 13:57         ` Takashi Iwai
2016-12-02  9:20           ` Enrico Mioso
2017-01-03 13:49           ` Enrico Mioso
2017-01-10 10:52             ` Takashi Iwai
2017-01-10 13:32               ` Enrico Mioso
2017-01-10 13:34                 ` Enrico Mioso
2017-01-12 14:05               ` Enrico Mioso
2017-01-12 16:10               ` Enrico Mioso
2017-01-12 16:20                 ` Takashi Iwai
2017-01-12 18:11                   ` Enrico Mioso
2017-01-12 20:26                   ` Enrico Mioso
2017-01-13 19:42                   ` Enrico Mioso
2017-01-14  8:44                     ` Takashi Iwai
2017-01-14  9:20                       ` Enrico Mioso
2017-01-14  9:46                         ` Takashi Iwai
2017-01-14 22:43                           ` Enrico Mioso
2017-01-14 22:43                           ` Enrico Mioso
2017-01-15 13:14                           ` Enrico Mioso
2017-01-20 13:00                           ` Enrico Mioso

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=alpine.LNX.2.20.1504092157190.901@localhost.localdomain \
    --to=mrkiko.rs@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=hui.wang@canonical.com \
    --cc=kailang@realtek.com \
    --cc=tiwai@suse.de \
    /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).