Messages in this thread | | | Date | Thu, 1 Jun 2006 10:22:34 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.17-rc5-mm2 |
| |
On Thu, 1 Jun 2006 17:51:16 +0200 "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
> Hi, > > On 01/06/06, Andrew Morton <akpm@osdl.org> wrote: > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc5/2.6.17-rc5-mm2/ > > > > I don't know why, but first bug appears only when avahi-daemon is > started. Second look like a problem with my camera. > http://www.stardust.webpages.pl/files/mm/2.6.17-rc5-mm2/bug_1.jpg
For some reason the lockdep code expected that hardirqs would be enabled.
> http://www.stardust.webpages.pl/files/mm/2.6.17-rc5-mm2/bug_2.jpg
So it's claiming that we're taking multiple i_mutexes.
I can't immediately see where we took the outermost i_mutex there. Nor is it immediately obvious why this is considered to be deadlockable?
(lockdep tells us that a mutex was taken at "mutex_lock+0x8/0xa", which is fairly useless. We need to report who the caller of mutex_lock() was).
> Here is config http://www.stardust.webpages.pl/files/mm/2.6.17-rc5-mm2/mm-config
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |