[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd18b0c30807131804g6b5b9a5by4468eef8c310cab5@mail.gmail.com>
Date: Mon, 14 Jul 2008 01:04:56 +0000
From: "Justin Mattock" <justinmattock@...il.com>
To: Valdis.Kletnieks@...edu
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Kernel Testers List" <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #10954] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c
On Mon, Jul 14, 2008 at 12:50 AM, <Valdis.Kletnieks@...edu> wrote:
> On Sun, 13 Jul 2008 20:00:46 +0200, "Rafael J. Wysocki" said:
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.25. Please verify if it still should be listed.
>>
>>
>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=10954
>> Subject : hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c
>> Submitter : Justin Mattock <justinmattock@...il.com>
>> Date : 2008-06-21 2:05 (23 days old)
>> References : http://marc.info/?l=linux-kernel&m=121401399622190&w=4
>> http://marc.info/?t=121416231700010&r=1&w=4
>
> Not sure if it's the same bug or not, this one's been there since before
> 2.6.25 but I haven't bothered chasing it down before. It's still in 26-rc9-mmotd.
>
> Jul 13 05:53:47 turing-police kernel: [ 1459.168266] ALSA sound/pci/hda/hda_intel.c:588: hda_intel: No response from codec, disabling MSI: last cmd=0x012f1c00
> Jul 13 05:53:48 turing-police kernel: [ 1460.169265] ALSA sound/pci/hda/hda_intel.c:601: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x012f1c00
>
> Dell Latitude D820, x86_64 kernel. Audio device is:
>
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
>
> dmidecode says it's a "Sigmatel 9200".
>
> I've been lazy chasing this one, because all that happens is that MSI gets
> turned off, and it keeps going without it...
>
Could be.
Yeah I must admit too about being lazy with this one;
(spent a few days updating my system with SID);
With Googling a little bit, isn't msi disabled by default?
if not then maybe setting the boot param is something to look into,
as well as tweaking the .config.
--
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists