From: Takashi Iwai <tiwai@suse.de>
To: Ed Tomlinson <edt@aei.ca>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [LOCKDEP] 33-rc8 Running aplay with pulse as the default
Date: Thu, 18 Feb 2010 14:21:12 +0100 [thread overview]
Message-ID: <s5htytellx3.wl%tiwai@suse.de> (raw)
In-Reply-To: <201002180725.38635.edt@aei.ca>
At Thu, 18 Feb 2010 07:25:38 -0500,
Ed Tomlinson wrote:
>
> On Wednesday 17 February 2010 09:29:37 Takashi Iwai wrote:
> > At Wed, 17 Feb 2010 08:16:32 -0500,
> > Ed Tomlinson wrote:
> > >
> > > On Tuesday 16 February 2010 08:37:46 Takashi Iwai wrote:
> > > > > Thanks for the patch. It helps in that it eliminates the opps but lockdep still triggers and aplay still fails.
> > > > > Here is the new traceback.
> > > >
> > > > Hmm, fixing this isn't so trivial. The same problem occurs on other
> > > > subsystems like NFS over years. And it's still there, AFAIK.
> > > > The mmap mutex appears suddenly in the strange code path at close.
> > > >
> > > > The patch below might fix, but I'm not 100% sure whether this has no
> > > > side effect.
> > > >
> > > > Anyway, I doubt very much it being a regression. There is no change
> > > > in ALSA core side, and also in V4L em28xx code. Maybe the lockdep
> > > > wasn't triggered by some reason. And, this lockdep warning is almost
> > > > harmless...
> > >
> > > Takashi,
> > >
> > > The second patch eliminating the lock causes oppes every time (one follows just in case
> > > its helpful).
> >
> > Are you sure? The patch should causes a compile error, so you must have
> > patched manually in a wrong place ;)
>
> Yes I am sure. I fixed the compile error the same way it is fixed below.
But the Oops looks pretty irrelevant from the code path.
Takashi
prev parent reply other threads:[~2010-02-18 13:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 19:49 Linux 2.6.33-rc8 Linus Torvalds
2010-02-12 20:11 ` Thomas Backlund
2010-02-12 20:26 ` Paul Rolland
2010-02-12 20:39 ` Thomas Backlund
2010-02-12 22:24 ` Stephen Rothwell
2010-02-13 0:31 ` Justin P. Mattock
2010-02-13 9:16 ` Geert Uytterhoeven
2010-02-13 12:43 ` Stephen Rothwell
2010-02-13 17:17 ` [LOCKDEP] 33-rc8 Running aplay with pulse as the default Ed Tomlinson
2010-02-13 19:18 ` Ed Tomlinson
2010-02-15 19:20 ` Takashi Iwai
2010-02-15 19:21 ` Takashi Iwai
2010-02-15 22:24 ` Ed Tomlinson
2010-02-15 22:35 ` Takashi Iwai
2010-02-15 23:21 ` Takashi Iwai
2010-02-16 13:19 ` Ed Tomlinson
2010-02-16 13:37 ` Takashi Iwai
2010-02-17 13:16 ` Ed Tomlinson
2010-02-17 14:29 ` Takashi Iwai
2010-02-18 12:25 ` Ed Tomlinson
2010-02-18 13:21 ` 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=s5htytellx3.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=edt@aei.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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