From: Lee Revell <rlrevell@joe-job.com>
To: Dominique Dumont <domi.dumont@free.fr>
Cc: Francesco Peeters <Francesco@FamPeeters.com>,
alsa-user <alsa-user@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
Date: Thu, 05 Oct 2006 16:45:10 -0400 [thread overview]
Message-ID: <1160081110.2481.104.camel@mindpipe> (raw)
In-Reply-To: <87y7rusddc.fsf@gandalf.hd.free.fr>
On Thu, 2006-10-05 at 22:42 +0200, Dominique Dumont wrote:
> "Francesco Peeters" <Francesco@FamPeeters.com> writes:
>
> > Have you tried using a different slot for the SB Live?
>
> Yes. No change at all. (Sorry for the delay).
This is going to be a problem with the SATA driver not ALSA. I've heard
that some motherboards do evil stuff like implementing legacy drive
access modes using SMM which would cause dropouts without xruns
reported.
Please report it on LKML.
Lee
next prev parent reply other threads:[~2006-10-05 20:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 11:55 Pb with simultaneous SATA and ALSA I/O Dominique Dumont
2006-09-25 12:17 ` [Alsa-user] " Francesco Peeters
2006-10-05 20:42 ` Dominique Dumont
2006-10-05 20:45 ` Lee Revell [this message]
2006-10-05 21:01 ` Dominique Dumont
2006-10-05 21:12 ` Lee Revell
2006-10-05 21:50 ` Alan Cox
2006-10-08 10:38 ` PCM distorsion snapshots from SATA/ALSA conflict (was: [Alsa-user] Pb with simultaneous SATA and ALSA I/O) Dominique Dumont
2006-10-08 16:41 ` Lee Revell
2006-10-14 15:04 ` [Alsa-user] PCM distorsion snapshots from SATA/ALSA conflict Dominique Dumont
2006-10-05 21:18 ` [Alsa-user] Pb with simultaneous SATA and ALSA I/O Lee Revell
2006-10-07 12:03 ` Dominique Dumont
2006-10-07 17:08 ` Lee Revell
2006-10-05 21:52 ` Alan Cox
2006-10-05 21:45 ` Lee Revell
2006-09-25 14:38 ` Lennart Sorensen
2006-09-25 14:50 ` Lee Revell
2006-09-26 14:29 ` Thierry Vignaud
2006-09-26 14:37 ` Dominique Dumont
2006-09-26 14:44 ` Lee Revell
2006-10-04 10:45 ` [Alsa-user] " Dominique Dumont
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=1160081110.2481.104.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Francesco@FamPeeters.com \
--cc=alsa-user@lists.sourceforge.net \
--cc=domi.dumont@free.fr \
--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