From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Bug #952 - MIDI lockup
Date: Tue, 04 Jul 2006 11:40:34 -0400 [thread overview]
Message-ID: <1152027634.15837.19.camel@mindpipe> (raw)
In-Reply-To: <s5hac7p4c91.wl%tiwai@suse.de>
On Tue, 2006-07-04 at 17:32 +0200, Takashi Iwai wrote:
> At Tue, 04 Jul 2006 11:00:40 -0400,
> Lee Revell wrote:
> >
> > On Mon, 2006-07-03 at 17:56 +0200, Takashi Iwai wrote:
> > > At Sun, 02 Jul 2006 18:45:59 -0400,
> > > Lee Revell wrote:
> > > >
> > > > Can someone take a quick look at:
> > > >
> > > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=952
> > > >
> > > > There is a nice screenshot of the kernel panic. The bug has been
> > > > verified with ALSA 1.0.12-rc1.
> > > >
> > > > It seems to crash while taking a spinlock in snd_timer_interrupt when
> > > > called from rtc_interrupt - maybe the changes to the ALSA RTC timer a
> > > > few months ago are involved?
> > >
> > > Does the patch below fix?
> >
> > No.
>
> Pointer? The test in bug #952 seems inaccurate.
Hmm, it might have fixed it. I think the user did not test correctly.
Lee
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-07-04 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 22:45 Bug #952 - MIDI lockup Lee Revell
2006-07-03 15:56 ` Takashi Iwai
2006-07-03 16:07 ` Lee Revell
2006-07-04 15:00 ` Lee Revell
2006-07-04 15:32 ` Takashi Iwai
2006-07-04 15:40 ` Lee Revell [this message]
2006-07-05 15:08 ` Lee Revell
2006-07-05 16:01 ` 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=1152027634.15837.19.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.