All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: alsa-devel@alsa-project.org
Subject: floating point exception triggered by speaker-test on pc-speaker
Date: Sun, 23 Nov 2008 14:30:24 +0500	[thread overview]
Message-ID: <ggb7td$f1a$1@ger.gmane.org> (raw)

Hello,

I have hit a strange bug. To reproduce:

1. Build snd-pcsp.ko.

2. alsamixer -c pcsp, set the base frequency to 37286 Hz

3. $ speaker-test -r 22050 -P 4 -D plughw:pcsp

speaker-test 1.0.18

Playback device is plughw:pcsp
Stream parameters are 22050Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 22050Hz (requested 22050Hz)
Buffer size range from 37 to 38756
Period size range from 18 to 19379
Using max buffer size 38756
Periods = 4
was set period_size = 0
was set buffer_size = 38756
  0 - Front Left
Floating point exception

I.e., as you see, period size somehow became 0. While debugging this with printfs, I 
noticed that the interval for periods in snd_pcm_hw_param_set_near() starts with 4, 
but doesn't include it (i.e., is open).

Also, I found that snd_interval_refine_first() and snd_interval_refine_last(), when 
given an open interval, refine it to something like (n n+1). This is obviously 
wrong, as there are no integer points in this interval. Changing i->max++ and 
i->min-- there to adjust the value by 2 did eliminate the floating point exception, 
but replaced it with "Unable to set nperiods 4 for playback: Invalid argument". So 
there must be something else also wrong, but I can't pinpoint it and give you a 
ready-made patch :(

-- 
Alexander E. Patrakov

             reply	other threads:[~2008-11-23  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  9:30 Alexander E. Patrakov [this message]
2008-11-26 13:37 ` floating point exception triggered by speaker-test on pc-speaker 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='ggb7td$f1a$1@ger.gmane.org' \
    --to=patrakov@gmail.com \
    --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.