All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Takashi Iwai <tiwai@suse.de>, Pavel Machek <pavel@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode...
Date: Wed, 4 Oct 2006 15:57:43 +0200	[thread overview]
Message-ID: <20061004135743.GA6150@irc.pl> (raw)
In-Reply-To: <451834D0.40304@goop.org>

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

On Mon, Sep 25, 2006 at 12:58:08PM -0700, Jeremy Fitzhardinge wrote:
> I have a ThinkPad X60 which uses the Intel 82801G HDA audio chip.  This 
> used to work for me, but lately (sometime during 2.6.18-rcX series) it 
> stopped working - programs trying to use it tend to just block forever 
> waiting for /dev/dsp.
> 
> The only obvious symptom is:
> 
>    hda_intel: azx_get_response timeout, switching to single_cmd mode...
> 
> appearing in the kernel log when booting.


  Just a blind shot -- do you have modem enabled in BIOS? Sometimes
disabling (hiding) modem breaks sound.

-- 
Tomasz Torcz                        To co nierealne -- tutaj jest normalne.
zdzichu@irc.-nie.spam-.pl          Ziomale na życie mają tu patenty specjalne.


[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]

  parent reply	other threads:[~2006-10-04 13:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 19:58 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode Jeremy Fitzhardinge
2006-09-25 20:26 ` Pavel Machek
2006-09-26  1:12   ` Michael Clark
2006-09-26  1:12     ` Michael Clark
2006-09-26  1:15   ` Jeremy Fitzhardinge
2006-09-26  1:15     ` Jeremy Fitzhardinge
2006-09-26 10:16 ` Takashi Iwai
2006-09-26 10:16   ` Takashi Iwai
2006-09-26 15:37   ` Randy Dunlap
2006-09-26 15:37     ` Randy Dunlap
2006-09-26 15:48     ` Takashi Iwai
2006-09-26 15:48       ` Takashi Iwai
2006-09-26 15:56       ` Randy Dunlap
2006-09-26 15:56         ` Randy Dunlap
2006-09-26 16:09         ` Takashi Iwai
2006-09-26 16:09         ` Takashi Iwai
2006-09-26 16:31   ` Andrew Morton
2006-09-26 16:31   ` Andrew Morton
2006-09-26 16:42     ` Takashi Iwai
2006-09-26 16:42       ` Takashi Iwai
2006-10-01  6:03   ` Jeremy Fitzhardinge
2006-10-01  6:03     ` Jeremy Fitzhardinge
2006-10-04  9:21     ` Takashi Iwai
2006-10-04  9:21       ` Takashi Iwai
2006-10-04 15:16       ` Jeremy Fitzhardinge
2006-10-04 15:16         ` Jeremy Fitzhardinge
2006-10-04 15:38         ` Takashi Iwai
2006-10-04 15:38           ` Takashi Iwai
2006-10-04 19:04         ` Takashi Iwai
2006-10-04 19:04           ` Takashi Iwai
2006-10-04 20:07           ` Jeremy Fitzhardinge
2006-10-04 20:07             ` Jeremy Fitzhardinge
2006-10-05  9:58             ` Takashi Iwai
2006-10-05  9:58               ` Takashi Iwai
2006-10-28  5:07     ` 2.6.18: hda_intel:azx_get_response " Shai Peretz
2006-10-04 13:57 ` Tomasz Torcz [this message]
2006-10-04 15:16   ` 2.6.18: hda_intel: azx_get_response " Jeremy Fitzhardinge
2006-10-04 15:16     ` Jeremy Fitzhardinge

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=20061004135743.GA6150@irc.pl \
    --to=zdzichu@irc.pl \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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 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.