* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-03 0:46 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-03 0:46 UTC (permalink / raw)
To: alsa-devel
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-03-2005 02:46 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-03 10:18 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-03 10:18 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-03-2005 12:18 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
tiwai - 08-03-05 12:18
----------------------------------------------------------------------
Which version did you use? Chance to try CVS version?
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-04 1:21 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-04 1:21 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-04-2005 03:21 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
tiwai - 08-03-05 12:18
----------------------------------------------------------------------
Which version did you use? Chance to try CVS version?
----------------------------------------------------------------------
herby - 08-04-05 03:21
----------------------------------------------------------------------
While not the CVS version, it is the 1.0.9 version(s) augmented 'b' on the
driver and 'a' on the library (with the patch indicated). Here is how it
is called:
>>>>>
Advanced Linux Sound Architecture Driver Version 1.0.9b.
Compiled on Jun 8 2005 for kernel 2.6.11.7.
/proc/asound/cards:
0 [Revolution71 ]: ICE1724 - M Audio Revolution-7.1
M Audio Revolution-7.1 at 0xdc00, irq 10
1 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with VT1616i at 0xd400, irq 5
Attempted execution of speaker-test:
[tsw@xytar20 ~]$ strace -o speaker-trace speaker-test -c 2
speaker-test 0.0.8
Playback device is plughw:0,0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
(Aborted with ^C after waiting a minute, no sound!)
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-04 12:10 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-04 12:10 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-04-2005 14:10 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
herby - 08-04-05 03:21
----------------------------------------------------------------------
While not the CVS version, it is the 1.0.9 version(s) augmented 'b' on the
driver and 'a' on the library (with the patch indicated). Here is how it
is called:
>>>>>
Advanced Linux Sound Architecture Driver Version 1.0.9b.
Compiled on Jun 8 2005 for kernel 2.6.11.7.
/proc/asound/cards:
0 [Revolution71 ]: ICE1724 - M Audio Revolution-7.1
M Audio Revolution-7.1 at 0xdc00, irq 10
1 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with VT1616i at 0xd400, irq 5
Attempted execution of speaker-test:
[tsw@xytar20 ~]$ strace -o speaker-trace speaker-test -c 2
speaker-test 0.0.8
Playback device is plughw:0,0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
(Aborted with ^C after waiting a minute, no sound!)
----------------------------------------------------------------------
jcdutton - 08-04-05 14:10
----------------------------------------------------------------------
This looks like a bug in the period/buffer size setting.
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
Does not make valid sense.
If there are 4 periods, with period size of 3764, the buffer size should
be 15056 and not 15052.
Do you have similar problems with the other sound card?
E.g.
Card 0
speaker-test -c2 -Dplug:front:0
Card 1
speaker-test -c2 -Dplug:front:1
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-04 18:21 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-04 18:21 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-04-2005 20:21 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
jcdutton - 08-04-05 14:10
----------------------------------------------------------------------
This looks like a bug in the period/buffer size setting.
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
Does not make valid sense.
If there are 4 periods, with period size of 3764, the buffer size should
be 15056 and not 15052.
Do you have similar problems with the other sound card?
E.g.
Card 0
speaker-test -c2 -Dplug:front:0
Card 1
speaker-test -c2 -Dplug:front:1
----------------------------------------------------------------------
herby - 08-04-05 20:21
----------------------------------------------------------------------
It seems that the problem is only on the Revolution 7.1 card, since it
hangs, and the motherboard audio (Via 8235) can generate the audio.
Results of the tests:
<<<Revo 7.1 card test (card #0)>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:0
speaker-test 0.0.8
Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
<<<Hangs, aborted by interupt>>>
<<<Test using the Motherboard audio, card #1>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:1
speaker-test 0.0.8
Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3763
was set buffer_size = 15052
0 - Front Left
1 - Front Right
Time per period = 5.649717
0 - Front Left
1 - Front Right
<<<Audio cycles as intended>>>
Maybe it is the interaction between the Revo 7.1 driver and the speaker
test. Any more test to be run??
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-09 4:58 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-09 4:58 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-09-2005 06:58 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
herby - 08-04-05 20:21
----------------------------------------------------------------------
It seems that the problem is only on the Revolution 7.1 card, since it
hangs, and the motherboard audio (Via 8235) can generate the audio.
Results of the tests:
<<<Revo 7.1 card test (card #0)>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:0
speaker-test 0.0.8
Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
<<<Hangs, aborted by interupt>>>
<<<Test using the Motherboard audio, card #1>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:1
speaker-test 0.0.8
Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3763
was set buffer_size = 15052
0 - Front Left
1 - Front Right
Time per period = 5.649717
0 - Front Left
1 - Front Right
<<<Audio cycles as intended>>>
Maybe it is the interaction between the Revo 7.1 driver and the speaker
test. Any more test to be run??
----------------------------------------------------------------------
herby - 08-09-05 06:58
----------------------------------------------------------------------
Now that I see the problem only happens on the Revo 7.1 card, do we
transfer it to that driver? There are the attempts at trying speaker
test:
[tsw ~]$ speaker-test -c 2 -D plug:front:0 <<Attempting to use Revo 7.1
card>>
speaker-test 0.0.8
Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
<interupt after waiting for sound to appear. No such luck!>
[tsw ~]$ speaker-test -c 2 -D plug:front:1 <<Using working motherboard
audio>>
speaker-test 0.0.8
Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3763
was set buffer_size = 15052
0 - Front Left
1 - Front Right
Time per period = 5.649939
0 - Front Left
<interupted after success at generating white noise. Works OK>
For reference:
[tsw ~]$ more /proc/asound/cards
0 [Revolution71 ]: ICE1724 - M Audio Revolution-7.1
M Audio Revolution-7.1 at 0xdc00, irq 10
1 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with VT1616i at 0xd400, irq 5
Obviously there is a problem in the Revolution-7.1 software. Is there any
hope?
Has the Revo 7.1 driver changed from version 1.0.9b to the present??
I'd like to get the Revo driver functional, as I've got a project that
uses it
(all 8 channels it really should be called a Revo 8.0!).
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-12 6:12 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-12 6:12 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-12-2005 08:12 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
herby - 08-09-05 06:58
----------------------------------------------------------------------
Now that I see the problem only happens on the Revo 7.1 card, do we
transfer it to that driver? There are the attempts at trying speaker
test:
[tsw ~]$ speaker-test -c 2 -D plug:front:0 <<Attempting to use Revo 7.1
card>>
speaker-test 0.0.8
Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 32768
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3764
was set buffer_size = 15052
0 - Front Left
<interupt after waiting for sound to appear. No such luck!>
[tsw ~]$ speaker-test -c 2 -D plug:front:1 <<Using working motherboard
audio>>
speaker-test 0.0.8
Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3763
was set buffer_size = 15052
0 - Front Left
1 - Front Right
Time per period = 5.649939
0 - Front Left
<interupted after success at generating white noise. Works OK>
For reference:
[tsw ~]$ more /proc/asound/cards
0 [Revolution71 ]: ICE1724 - M Audio Revolution-7.1
M Audio Revolution-7.1 at 0xdc00, irq 10
1 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with VT1616i at 0xd400, irq 5
Obviously there is a problem in the Revolution-7.1 software. Is there any
hope?
Has the Revo 7.1 driver changed from version 1.0.9b to the present??
I'd like to get the Revo driver functional, as I've got a project that
uses it
(all 8 channels it really should be called a Revo 8.0!).
----------------------------------------------------------------------
herby - 08-12-05 08:12
----------------------------------------------------------------------
More info:
When speaker-test stalls (on the Revo 7.1) no interrupts get generated
(from /proc/interrupts). When I use 'aplay' (which generates sound!),
interrupts get generated (go figure). When I use the VIA 8233
(motherboard audio) speaker-test all goes well. It seems that there is
something wierd in the buffer counts, or something on the Revo 7.1 card.
Here is some data from /proc/asound/card0/pcm0p/sub0 that might help:
[tsw sub0]$ more *
::::::::::::::
hw_params
::::::::::::::
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 3764
buffer_size: 15052
tick_time: 1000
::::::::::::::
info
::::::::::::::
card: 0
device: 0
subdevice: 0
stream: PLAYBACK
id: ICE1724
name: ICE1724
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0
::::::::::::::
prealloc
::::::::::::::
256
::::::::::::::
status
::::::::::::::
state: PREPARED
trigger_time: 0.000000000
tstamp : 1123826957.287182000
delay : 0
avail : 3760
avail_max : 0
-----
hw_ptr : 0
appl_ptr : 11292
::::::::::::::
sw_params
::::::::::::::
tstamp_mode: NONE
period_step: 1
sleep_min: 0
avail_min: 3764
xfer_align: 1
start_threshold: 15052
stop_threshold: 15052
silence_threshold: 0
silence_size: 0
boundary: 1972895744
(this was taken while the speaker-test was stalled out)
Hope this helps!
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-08-12 13:47 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-08-12 13:47 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 08-12-2005 15:47 CEST
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
herby - 08-12-05 08:12
----------------------------------------------------------------------
More info:
When speaker-test stalls (on the Revo 7.1) no interrupts get generated
(from /proc/interrupts). When I use 'aplay' (which generates sound!),
interrupts get generated (go figure). When I use the VIA 8233
(motherboard audio) speaker-test all goes well. It seems that there is
something wierd in the buffer counts, or something on the Revo 7.1 card.
Here is some data from /proc/asound/card0/pcm0p/sub0 that might help:
[tsw sub0]$ more *
::::::::::::::
hw_params
::::::::::::::
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 3764
buffer_size: 15052
tick_time: 1000
::::::::::::::
info
::::::::::::::
card: 0
device: 0
subdevice: 0
stream: PLAYBACK
id: ICE1724
name: ICE1724
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0
::::::::::::::
prealloc
::::::::::::::
256
::::::::::::::
status
::::::::::::::
state: PREPARED
trigger_time: 0.000000000
tstamp : 1123826957.287182000
delay : 0
avail : 3760
avail_max : 0
-----
hw_ptr : 0
appl_ptr : 11292
::::::::::::::
sw_params
::::::::::::::
tstamp_mode: NONE
period_step: 1
sleep_min: 0
avail_min: 3764
xfer_align: 1
start_threshold: 15052
stop_threshold: 15052
silence_threshold: 0
silence_size: 0
boundary: 1972895744
(this was taken while the speaker-test was stalled out)
Hope this helps!
----------------------------------------------------------------------
tiwai - 08-12-05 15:47
----------------------------------------------------------------------
ICE1724 has the restriction regarding period and buffer size alignment.
It's aligned to 32byte.
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
08-12-05 15:47 tiwai Note Added: 0005773
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-12-30 22:24 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-12-30 22:24 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 12-30-2005 23:24 CET
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
tiwai - 08-12-05 15:47
----------------------------------------------------------------------
ICE1724 has the restriction regarding period and buffer size alignment.
It's aligned to 32byte.
----------------------------------------------------------------------
rlrevell - 12-30-05 23:24
----------------------------------------------------------------------
Any improvement in later releases?
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
08-12-05 15:47 tiwai Note Added: 0005773
12-30-05 23:24 rlrevell Note Added: 0007288
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-12-31 20:38 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-12-31 20:38 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 12-31-2005 21:38 CET
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 23:24
----------------------------------------------------------------------
Any improvement in later releases?
----------------------------------------------------------------------
herby - 12-31-05 21:38
----------------------------------------------------------------------
I had no problems with later versions.
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
08-12-05 15:47 tiwai Note Added: 0005773
12-30-05 23:24 rlrevell Note Added: 0007288
12-31-05 21:38 herby Note Added: 0007360
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 11+ messages in thread
* [ALSA - utils 0001304]: Speaker test hangs
@ 2005-12-31 21:07 bugtrack
0 siblings, 0 replies; 11+ messages in thread
From: bugtrack @ 2005-12-31 21:07 UTC (permalink / raw)
To: alsa-devel
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To: rlrevell
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 12-31-2005 22:07 CET
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 23:24
----------------------------------------------------------------------
Any improvement in later releases?
----------------------------------------------------------------------
herby - 12-31-05 21:38
----------------------------------------------------------------------
I had no problems with later versions.
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
08-12-05 15:47 tiwai Note Added: 0005773
12-30-05 23:24 rlrevell Note Added: 0007288
12-31-05 21:38 herby Note Added: 0007360
12-31-05 22:07 rlrevell Status new => resolved
12-31-05 22:07 rlrevell Resolution open => fixed
12-31-05 22:07 rlrevell Assigned To => rlrevell
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2005-12-31 21:07 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-31 21:07 [ALSA - utils 0001304]: Speaker test hangs bugtrack
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 20:38 bugtrack
2005-12-30 22:24 bugtrack
2005-08-12 13:47 bugtrack
2005-08-12 6:12 bugtrack
2005-08-09 4:58 bugtrack
2005-08-04 18:21 bugtrack
2005-08-04 12:10 bugtrack
2005-08-04 1:21 bugtrack
2005-08-03 10:18 bugtrack
2005-08-03 0:46 bugtrack
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox