mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
To: linux-kernel@vger.kernel.org
Cc: jwoithe@physics.adelaide.edu.au (Jonathan Woithe)
Subject: 2.6.15-rt16: possible sound-related side-effect
Date: Fri, 10 Feb 2006 12:42:14 +1030 (CST)	[thread overview]
Message-ID: <200602100212.k1A2CEat012522@auster.physics.adelaide.edu.au> (raw)

Hi all

In the last week I have updated the kernel on our laptop to 2.6.15-rt16.
By and large this worked well and had the attractive side effect of making
the clock run at the correct speed once more.

During development of an ALSA patch I had the need to remove and reinsert
the hda-intel and hda-codec modules on numerous occasions.  Every so often
(perhaps once every 5 or 6 times on average) the initialisation sequence of
hda-intel would get hung up and the associated insmod would never return.  A
reboot was required to clear the problem.  The following messages were
written to syslog repeatedly and often:

  Feb  5 21:36:24: ALSA sound/pci/hda/hda_intel.c:511: azx_get_response timeout
  Feb  5 21:36:26 halite last message repeated 9 times
  Feb  5 21:36:29 halite kernel: printk: 31 messages suppressed.

I have noticed the "azx_get_response timeout" messages in earlier kernels
as well, but up until now the hda initialisation hasn't gotten hung up.

The latching up of the hda-intel initialisation does not appear to occur
when doing the same thing under a non-RT 2.6.15 kernel.  Furthermore, I have
had an instance where the lockup occured while cold-booting an unmodified
2.6.15-rt16, which rules out any changes I made to ALSA as the cause of the
problem.  In any case the changes I was making to ALSA don't affect the
initialisation code.

Prior to this kernel I was running an unmodified 2.6.14-rt21 kernel and
while these messages did occur they didn't cause hda-intel to lock up.

Any suggestions as to what might be causing this and/or of further tests
which might help narrow down the cause?

Regards
  jonathan

             reply	other threads:[~2006-02-10  2:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10  2:12 Jonathan Woithe [this message]
2006-02-10  8:04 ` Steven Rostedt
2006-02-15 23:39   ` Jonathan Woithe
2006-02-16  7:55     ` Steven Rostedt
2006-02-16  9:37       ` Bill Huey
2006-02-17  1:45       ` Jonathan Woithe
2006-02-24  1:31       ` Jonathan Woithe
2006-02-24  7:38         ` Steven Rostedt
2006-02-26 23:27           ` Jonathan Woithe

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=200602100212.k1A2CEat012522@auster.physics.adelaide.edu.au \
    --to=jwoithe@physics.adelaide.edu.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®