From: Lee Revell <rlrevell@joe-job.com>
To: Borislav Petkov <petkov@uni-muenster.de>
Cc: pharon@gmail.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.12-rc5-mm1 alsa oops
Date: Thu, 26 May 2005 14:32:19 -0400 [thread overview]
Message-ID: <1117132339.5477.20.camel@mindpipe> (raw)
In-Reply-To: <200505262012.45833.petkov@uni-muenster.de>
On Thu, 2005-05-26 at 20:12 +0200, Borislav Petkov wrote:
> On Thursday 26 May 2005 20:01, Lee Revell wrote:
> > On Thu, 2005-05-26 at 19:44 +0200, Borislav Petkov wrote:
> > > <snip>
> > >
> > > Andrew,
> > >
> > > similar oopses as the one I'm replying to all over the place. At it
> > > happens m in snd_pcm_mmap_data_close(). Here's a stack trace:
> >
> > No one using ALSA CVS or any of the 1.0.9 release candidates ever
> > reported this, but lots of -mm users are... does that help at all? I
> > suspect some upstream bug that ALSA just happens to trigger.
> yeah,
>
> this has to do with alsa indirectly. snd_pcm_mmap_data_close() accesses some
> vm_area_struct->vm_private_data and apparently there have been some
> optimizations to mmap code to avoid fragmentation of vma's so i think there's
> the problem. However, we'll need the smarter ones here :))
Any idea which patches to back out?
Lee
next prev parent reply other threads:[~2005-05-26 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 7:32 2.6.12-rc5-mm1 alsa oops Islam Amer
2005-05-26 17:44 ` Borislav Petkov
2005-05-26 18:01 ` Lee Revell
2005-05-26 18:12 ` Borislav Petkov
2005-05-26 18:32 ` Lee Revell [this message]
2005-05-26 18:35 ` Wolfgang Wander
2005-05-26 18:59 ` Lawrence Walton
2005-05-26 21:24 ` Andrew Morton
2005-05-27 16:42 ` Chen, Kenneth W
2005-05-28 9:10 ` Borislav Petkov
[not found] ` <4296100F.2090202@rentec.com>
2005-05-26 18:33 ` Islam Amer
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 18:42 Colin Harrison
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=1117132339.5477.20.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkov@uni-muenster.de \
--cc=pharon@gmail.com \
/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