From: Lee Revell <rlrevell@joe-job.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, perex@suse.cz,
alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] Re: ALSA regression: oops on shutdown
Date: Sun, 23 Apr 2006 22:39:19 -0400 [thread overview]
Message-ID: <1145846360.31507.50.camel@mindpipe> (raw)
In-Reply-To: <b6fcc0a0604231937h6f2754f9k68ec76dc19c7ddb9@mail.gmail.com>
On Sun, 2006-04-23 at 19:37 -0700, Alexey Dobriyan wrote:
> On 4/23/06, Andrew Morton <akpm@osdl.org> wrote:
> > Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > >
> > > ALSA oops I reported against 2.6.16-rc1-mm4 [1] sneaked into mainline
> > > after release.
> >
> > One wonders why the ALSA developers merged up which was known to cause
> > oopses.
>
> To be fair, I bisected it only to git-alsa.patch back then and only
> now found enough time, so
> blame me.
Do you have procfs disabled? Full config is needed to debug this more.
Lee
next prev parent reply other threads:[~2006-04-24 2:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 23:57 ALSA regression: oops on shutdown Alexey Dobriyan
2006-04-24 1:57 ` Andrew Morton
2006-04-24 1:57 ` Andrew Morton
2006-04-24 2:37 ` Alexey Dobriyan
2006-04-24 2:37 ` Alexey Dobriyan
2006-04-24 2:39 ` Lee Revell [this message]
2006-04-24 3:11 ` Alexey Dobriyan
2006-04-24 3:11 ` [Alsa-devel] " Alexey Dobriyan
2006-04-24 3:51 ` Alexey Dobriyan
2006-04-24 3:51 ` [Alsa-devel] " Alexey Dobriyan
2006-04-24 13:34 ` Takashi Iwai
2006-04-24 13:34 ` [Alsa-devel] " Takashi Iwai
2006-04-24 14:26 ` Takashi Iwai
2006-04-24 14:26 ` [Alsa-devel] " Takashi Iwai
2006-04-24 15:30 ` Alexey Dobriyan
2006-04-24 15:30 ` [Alsa-devel] " Alexey Dobriyan
2006-04-24 16:34 ` Takashi Iwai
2006-04-24 16:34 ` [Alsa-devel] " Takashi Iwai
2006-04-24 18:42 ` Alexey Dobriyan
2006-04-24 18:42 ` [Alsa-devel] " Alexey Dobriyan
2006-04-24 2:39 ` Lee Revell
2006-04-24 13:00 ` [Alsa-devel] " Takashi Iwai
2006-04-24 13:00 ` 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=1145846360.31507.50.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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.