From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Christian Trefzer <ctrefzer@gmx.de>,
lkml <linux-kernel@vger.kernel.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: snd-nm256: hard lockup on every second module load after powerup
Date: Mon, 27 Mar 2006 17:59:59 -0500 [thread overview]
Message-ID: <1143500400.1792.314.camel@mindpipe> (raw)
In-Reply-To: <s5hveu0chvy.wl%tiwai@suse.de>
On Mon, 2006-03-27 at 12:16 +0200, Takashi Iwai wrote:
> > Any hints would be greatly appreciated! Thanks a bunch,
>
> Try 2.6.16-git tree. Some patches for this problem are there.
If this does not fix the problem then alsa-devel (cc'ed) is the best
list to discuss the issue.
Lee
next prev parent reply other threads:[~2006-03-27 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 5:45 snd-nm256: hard lockup on every second module load after powerup Christian Trefzer
2006-03-26 6:12 ` Christian Trefzer
2006-03-26 14:11 ` Christian Trefzer
2006-03-27 10:16 ` Takashi Iwai
2006-03-27 22:59 ` Lee Revell [this message]
2006-03-29 14:43 ` Christian Trefzer
2006-03-31 21:12 ` Adrian Bunk
2006-03-31 21:53 ` Lee Revell
2006-04-01 9:21 ` Adrian Bunk
2006-04-03 9:57 ` 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=1143500400.1792.314.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ctrefzer@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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.