Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Apostolos Dimitromanolakis <apostolos@aei.ca>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ICE1724 & Prodigy  instant reboot..
Date: Sat, 22 Nov 2003 15:08:43 -0500	[thread overview]
Message-ID: <3FBFC24B.6090004@aei.ca> (raw)
In-Reply-To: <s5hn0avjde3.wl@alsa2.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]


Hi,

I tried the same setup with a stock 2.4.22 kernel and CVS and the
problem persists but only in below 48k sampling rates.

arecord -f S32_LE -d ICE1724 -D hw:0,0  -c 2
-r 192000 :  works (?? the card has a maximum 96k sampling rate!)
-r 96000 :  works
-r 48000 : works
-r 44100 : reboot after 2 seconds no data recorded
-r 22050 : same
-r 11025 : same

   I have done some more tests and it seems that adding "--bufer-size
8192" make recording fine. So I guess it is a software bug somewhere in
the ICE1724 driver together with arecord setting some weird
buffer/period size or whatever.  In my sense of a kernel driver,
whatever arecord does, the system shouldn't crash. I've attached the log
from the setup of the recording stream that crashes the system.

Apostolis


Takashi Iwai wrote:

>At Sun, 16 Nov 2003 10:53:17 -0500,
>Apostolos Dimitromanolakis wrote:
>  
>
>>Hi everybody,
>>
>>I'm still working on the audiotrak prodigy driver.  However for some 
>>reason the ice1724 module performs an instant reboot of the kernel when 
>>I try to record at 44khz. Recording at 96khz seems fine but as soon as 
>>you select 44khz on arecord, something odd happens. No data come out and 
>>no error messages from the module but the computers reboots after 1-2 
>>seconds. Experiments on the console revealed some kernel error messages 
>>(something with the word vm inside :) milliseconds before the reboot but 
>>there is
>>no time to read the messages really.  Is this a known problem with the 
>>ice1724 (i guess not) or something else is wrong? Note that the hardware 
>>access of prodigy to the DAC/ADC works fine and the interrupts should be 
>>generated ok. Also the ice1724 configuration is copied directly from the 
>>win driver and should be fine. Any ideas?
>>    
>>
>
>do you use a preemptive kernel?
>there was a mutex in spinlock context, and it was fixed recently on
>cvs.  anyway, please try the cvs version if not yet.
>
>
>Takashi
>
>
>  
>



[-- Attachment #2: log --]
[-- Type: text/plain, Size: 661 bytes --]

Recording WAVE '/dev/null' : Signed 32 bit Little Endian, Rate 44000 Hz, Stereo
Hardware PCM card 0 'Audiotrak Prodigy 7.1' device 0 subdevice 0

Its setup is:
stream       : CAPTURE
access       : RW_INTERLEAVED
format       : S32_LE
subformat    : STD
channels     : 2
rate         : 44100
exact rate   : 44100 (44100/1)
msbits       : 24
buffer_size  : 22050
period_size  : 5513
period_time  : 125011
tick_time    : 10000
tstamp_mode  : NONE
period_step  : 1
sleep_min    : 0
avail_min    : 5513
xfer_align   : 5513
start_threshold  : 1
stop_threshold   : 22050
silence_threshold: 0
silence_size : 0
boundary     : 1445068800
Aborted by signal Interrupt...


      reply	other threads:[~2003-11-22 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 15:53 ICE1724 & Prodigy instant reboot Apostolos Dimitromanolakis
2003-11-17 14:08 ` Takashi Iwai
2003-11-22 20:08   ` Apostolos Dimitromanolakis [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=3FBFC24B.6090004@aei.ca \
    --to=apostolos@aei.ca \
    --cc=alsa-devel@lists.sourceforge.net \
    /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