From: Takashi Iwai <tiwai@suse.de>
To: Apostolos Dimitromanolakis <apostolos@aei.ca>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ICE1724 & Prodigy instant reboot..
Date: Mon, 17 Nov 2003 15:08:52 +0100 [thread overview]
Message-ID: <s5hn0avjde3.wl@alsa2.suse.de> (raw)
In-Reply-To: <3FB79D6D.3050006@aei.ca>
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
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
next prev parent reply other threads:[~2003-11-17 14: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 [this message]
2003-11-22 20:08 ` Apostolos Dimitromanolakis
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=s5hn0avjde3.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=apostolos@aei.ca \
/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.