All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: sbahling@mudgum.net
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Debugging driver modules
Date: Mon, 02 Dec 2002 12:23:29 +0100	[thread overview]
Message-ID: <s5h1y50br66.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DEB8BED.4030002@mudgum.net>

At Mon, 02 Dec 2002 10:35:57 -0600,
Scott Bahling wrote:
> 
> Takashi Iwai wrote:
> 
> >At 30 Nov 2002 16:27:43 -0600,
> >Scott Bahling wrote:
> >  
> >
> >>Hello-
> >>
> >>I have a STAudio DSP24 mkII and I have noticed that recent changes(after
> >>NOV 13) in the CVS creates an ICE1712 driver that locks up my kernel.
> >>Instead of just complaining about this problem I thought I might try to
> >>narrow down the location in the driver that is causing the lockup.
> >>    
> >>
> > 
> >can you confirm the date when the critical change was applied to cvs?
> >the driver before Nov. 13 works really?
> >  
> >
> Actualy the changes happened on the 14th. I have a copy of the cvs 
> tarball from the 13th and the drivers work fine. According to the CVS 
> web interface, on the 14th Jaroslav "Added rate reset & locking for 
> pro-pcm and added internal rate setup"

hmm, does the lock occurs even if you don't register
snd_ice1712_pro_internal_clock control (ice1712.c line 2243) ?
other changes seem harmless...


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2002-12-02 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 22:27 Debugging driver modules Scott Bahling
2002-11-30 17:38 ` Paul Davis
2002-12-01 14:27   ` Matthias Weiss
2002-12-02  9:13 ` Takashi Iwai
     [not found]   ` <3DEB8BED.4030002@mudgum.net>
2002-12-02 11:23     ` Takashi Iwai [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=s5h1y50br66.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=sbahling@mudgum.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 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.