From: Lee Revell <rlrevell@joe-job.com>
To: Christian Trefzer <ctrefzer@gmx.de>
Cc: alsa-devel@lists.sourceforge.net, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] nm256: register strangeness related to lockups
Date: Sun, 26 Mar 2006 21:26:31 -0500 [thread overview]
Message-ID: <1143426392.1792.167.camel@mindpipe> (raw)
In-Reply-To: <20060326182607.GB11408@hermes.uziel.local>
On Sun, 2006-03-26 at 20:26 +0200, Christian Trefzer wrote:
> Hi folks,
>
> in the process of analyzing the frequent crashes during the snd-nm256
> module insertion I stumbled across the following register values
> (reading 32bit words at a time in a loop with pcitweak):
Just to make sure, you are testing with 1.0.11-rc4 or CVS? The nm256
lockup problems were thought to be fixed. Or is this a different bug?
Lee
prev parent reply other threads:[~2006-03-27 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 18:26 nm256: register strangeness related to lockups Christian Trefzer
2006-03-27 2:26 ` Lee Revell [this message]
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=1143426392.1792.167.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ctrefzer@gmx.de \
--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