From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001938]: EPIPE on Audigy with surround sound when seeking in 6 channel sound file
Date: Fri, 24 Mar 2006 17:06:44 +0100 [thread overview]
Message-ID: <a22af063217830632ff72214208a53ee@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1938>
======================================================================
Reported By: bambam
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1938
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Distribution: Debian sid with custom x86-64 kernel
Kernel Version: 2.6.16-rc6
======================================================================
Date Submitted: 03-17-2006 20:31 CET
Last Modified: 03-24-2006 17:06 CET
======================================================================
Summary: EPIPE on Audigy with surround sound when seeking in
6 channel sound file
Description:
Seeking in a 6 channel sound or video file using a surround device gives
EPIPE (Broken pipe). This happens with both mplayer and vlc. My soundcard
is an Audigy 1 (SB0090). I'm running a 64-bit kernel with 32-bit
userspace. I've tried libs and modules from CVS two days ago with no
success.
======================================================================
----------------------------------------------------------------------
bambam - 03-24-06 16:55
----------------------------------------------------------------------
I dont know for sure if the patch has already made it into CVS; judging
from the log of pcm_direct.c where it states that revision 1.59 has closed
this bug I assume it has. So I reopen the bug because revision 1.59 does
*not* solve this bug. I can however confirm that this is a 64/32 bit
issue, since 64-bit mplayer doesn't exhibit this issue.
Should, against my expectations, the relevant patch for solving this bug
not be in anon CVS yet, I appologize for reopening this request again.
----------------------------------------------------------------------
tiwai - 03-24-06 17:06
----------------------------------------------------------------------
Let's separate to two bugs. The 100% CPU should be fixed by the patch.
The EPIPE should be fixed by the patch to pcm_hw.c.
Anyway, please try 1.0.11rc4 and recheck whether both problems still exist
or are solved.
Issue History
Date Modified Username Field Change
======================================================================
03-17-06 20:31 bambam New Issue
03-17-06 20:31 bambam Distribution => Debian sid with
custom x86-64 kernel
03-17-06 20:31 bambam Kernel Version => 2.6.16-rc6
03-17-06 20:36 bambam Note Added: 0008656
03-17-06 21:07 bambam Note Added: 0008659
03-17-06 21:53 bambam Note Added: 0008662
03-18-06 01:07 rlrevell Note Added: 0008667
03-18-06 01:11 bambam Note Added: 0008668
03-18-06 14:44 bambam Note Added: 0008671
03-20-06 12:25 tiwai Note Added: 0008715
03-21-06 00:29 bambam Note Added: 0008733
03-21-06 17:30 tiwai Status new => resolved
03-21-06 17:30 tiwai Resolution open => fixed
03-21-06 17:30 tiwai Assigned To => tiwai
03-21-06 17:30 tiwai Note Added: 0008747
03-21-06 20:09 bambam Status resolved => feedback
03-21-06 20:09 bambam Resolution fixed => reopened
03-21-06 20:09 bambam Note Added: 0008759
03-21-06 20:10 tiwai Status feedback => resolved
03-21-06 20:10 tiwai Resolution reopened => fixed
03-21-06 20:10 tiwai Note Added: 0008760
03-24-06 16:55 bambam Status resolved => feedback
03-24-06 16:55 bambam Resolution fixed => reopened
03-24-06 16:55 bambam Note Added: 0008921
03-24-06 17:06 tiwai Note Added: 0008922
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-24 16:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 16:06 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-10 16:22 [ALSA - driver 0001938]: EPIPE on Audigy with surround sound when seeking in 6 channel sound file bugtrack
2006-03-31 11:46 bugtrack
2006-03-30 19:04 bugtrack
2006-03-30 9:41 bugtrack
2006-03-30 8:31 bugtrack
2006-03-29 22:18 Robert Hardy
2006-03-29 16:56 bugtrack
2006-03-27 0:05 bugtrack
2006-03-25 12:16 bugtrack
2006-03-24 19:47 bugtrack
2006-03-24 19:12 bugtrack
2006-03-24 17:07 bugtrack
2006-03-24 16:39 bugtrack
2006-03-24 16:38 bugtrack
2006-03-24 16:36 bugtrack
2006-03-24 16:34 bugtrack
2006-03-24 16:29 bugtrack
2006-03-24 15:55 bugtrack
2006-03-21 19:10 bugtrack
2006-03-21 19:09 bugtrack
2006-03-21 16:30 bugtrack
2006-03-20 23:29 bugtrack
2006-03-20 11:25 bugtrack
2006-03-18 13:44 bugtrack
2006-03-18 0:11 bugtrack
2006-03-18 0:07 bugtrack
2006-03-17 20:53 bugtrack
2006-03-17 20:07 bugtrack
2006-03-17 19:36 bugtrack
2006-03-17 19:31 bugtrack
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=a22af063217830632ff72214208a53ee@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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 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.